16-3
Catalyst 2960 Switch SoftwareConfiguration Guide
78-16881-01
Chapter16 Configuring MSTP
Understanding MSTP
IST, CIST, and CST
Unlike PVST+ and rapid PVST+ in which all the spanning-tree instances are independent, the MSTP
establishes and maintains two types of spanning trees:
An internal spanning tree (IST), which is the spanning tree that runs in an MST region.
Within each MST region, the MSTP maintains multiple spanning-tree instances. Instance 0 is a
special instance for a region, known as the internal spanning tree (IST). All other MST instances are
numbered from 1 to 15.
The IST is the only spanning-tree instan ce that sends and receives BPDUs. All of the ot her
spanning-tree instance information is contained in M-records, which are encapsulated within MSTP
BPDUs. Because the MSTP BPDU carries information for all instances, the number of BPDUs that
need to be processed to support multiple spanning-tree instances is significantly reduced.
All MST instances within the same region share the same protocol timers, but each MST instance
has its own topology parameters, such as root switch ID, root path cost, and so forth. By default, all
VLANs are assigned to the IST.
An MST instance is local to the region; for example, MST instance 1 in r egion A is independent of
MST instance 1 in region B, even if regions A and B are interconnected.
A common and internal spanning tree (CIST), which is a coll ection of the ISTs in each MST region,
and the common spanning tree (CST) that interconnects the MST regions and single spannin g trees.
The spanning tree computed in a region appears as a subtree in the CST that encompasses the entire
switched domain. The CIST is formed by the spanning-tree algorithm running among switches that
support the IEEE 802.1w, IEEE 802.1s, and IEEE 802.1D standards. The CIST insi de an MST
region is the same as the CST outside a region.
For more information, see the “Operations Within an MST Region” section on page16-3 and the
“Operations Between MST Regions” section on page 16-4.

Operations Within an MST Region

The IST connects all the MSTP switches in a region. When the IST converges, the root of the IST
becomes the IST master as shown in Figure 16-1 on page 16-4. It is the switch within the region with
the lowest switch ID and path cost to the CST root. The IST master is also the CST root if there is only
one region in the network. If the CIST root is outside the region, one of the MSTP switches at the
boundary of the region is selected as the IST master.
When an MSTP switch initializes, it sends BPDUs claiming itself as the root of the CIST and the IST
master, with both of the path costs to the CST root and to the IST master set to zero. The switch also
initializes all of its MST instances and claims to be the root for all of them. If the switch receives superior
MST root information (lower switch ID, lower path cost, and so forth) than curre ntly stored for the port,
it relinquishes its claim as the IST master.
During initialization, a region might have many subregions, each with its own IST master. As switches
receive superior IST information, they leave their old subregions and join the new subregion that
contains the true IST master. Thus all subregions shrink except f or the one that contains the true IST
master.
For correct operation, all switches in the MST region must agree on the same IST master. Therefore, any
two switches in the region only synchronize their port roles for an MST instance if they converge to a
common IST master.