The Multiple Spanning Tree Protocol (MSTP) and algorithm, provides both simple and full connectivity assigned to any given virtual LAN (VLAN) throughout a bridged local area network. MSTP uses bridge protocol data unit (BPDUs) to exchange information between spanning-tree compatible devices, to prevent loops in each Multiple Spanning Tree instance (MSTI) and in the Common and Internal Spanning Tree (CIST), by selecting active and blocked paths. This is done as well as in Spanning Tree Protocol (STP) without the need of manually enabling backup links and getting rid of switching loop danger. MSTP allows frames assigned to different VLANs to follow separate paths, each based on an independent MSTI, within MST regions composed of local area networks (LANs) and MST bridges. These regions and the other bridges and LANs are connected into a single common spanning tree (CST).
History and motivation It was originally defined in IEEE 802.1s as an amendment to 802.1Q, 1998 edition, and later merged into IEEE 802.1Q-2005 Standard, and clearly defines an extension or an evolution of Radia Perlman's Spanning Tree Protocol (STP) and the Rapid Spanning Tree Protocol (RSTP). It has some similarities with Cisco Systems' Multiple Instances Spanning Tree Protocol (MISTP), but there are some differences. The original STP and RSTP work on the physical link level, preventing bridge loops when redundant paths are present. However, when a LAN is virtualized using VLAN trunking, each physical link represents multiple logical connections. Blocking a physical link blocks all its logical links and forces all traffic through the remaining physical links within the spanning tree. Redundant links cannot be utilized at all. Moreover, without careful network design, seemingly redundant links on the physical level may be used to connect different VLANs and blocking any of them may disconnect one or more VLANs, causing bad paths. Instead, MSTP provides a potentially better utilization of alternate paths by enabling the use of alternate spanning trees for different VLANs or groups of VLANs.
Main entities
Multiple Spanning Tree instances (MSTI)
As MSTP enables grouping and mapping VLANs into different spanning tree instances, there is an urge to determine a group or set of VLANs that are all using the same spanning tree; this is an MSTI. Each instance defines a single forwarding topology for an exclusive set of VLANs; by contrast, STP or RSTP networks contain only a single spanning tree instance for the entire network, which contains all the VLANs. A region can include:
Internal spanning-tree instance (IST): Default spanning tree instance in any MST region. All VLANs in this IST instance form a single spanning tree topology, allowing only one forwarding path between any two nodes. It also provides the root switch for any VLAN-configured switches that are not specifically assigned to an MSTI. Multiple Spanning Tree instance (MSTI): Unlike IST, this kind of instance comprises all static VLANs specifically assigned to it and must include at least one VLAN. While each MSTI can have multiple VLANs, each VLAN can be associated with only one MSTI.
MSTP regions
A set of interconnected switches that must have been configured with the same VLANs and MSTIs, also have the same following parameters:
MST Configuration Name Revision Level Configuration Digest: Mapping of which VLAN are mapped to which MST instances. An MSTI is unable to span across MST regions because of its inherent locality to a single MST region. This is done by an identifying number for each MSTI. For achieving the task of assigning each bridge to a region, each switch/bridge must compare its MST Configuration Identifiers (Format Selector, Region Name, Revision Level and Configuration Digest), either of which represents VLAN to MSTIs mapping for each bridge.
Common and Internal Spanning Tree (CST/CIST)
We can differentiate two kinds of conformated Spanning Trees into the different networks created by MSTP, these are:
Common Spanning Tree (CST): Administers the connectivity among MST regions, STP LANs and RSTP LANs in a bridged network. Common Internal Spanning Tree (CIST): Identifies regions in a network and administers the CIST root bridge for the network, for each region, and for each spanning tree instance in each region. It's also the default spanning tree instance of MSTP so that any VLAN that isn't a member of a particular MSTI will be a member of the CIST. Furthermore, works as well as the spanning tree that runs between regions and between MST regions and Single Spanning Tree (SST) entities. The role of the Common Spanning Tree (CST) in a network, and the Common and Internal Spanning Tree (CIST) configured on each device, is to prevent loops within a wider network that may span more than one MSTP Region and parts of the network running in legacy STP or RSTP mode.
MSTP BPDUs
The main function of bridge protocol data units (BPDUs) is to enable MSTP to select its root bridges for the proper CIST and each MSTI. MSTP includes all its spanning tree information in a single BPDU format. Not only does it reduce the number of BPDUs required on a LAN to communicate spanning tree information for each VLAN, but it also ensures backward compatibility with RSTP (and, in effect, classic STP too). BPDUs' general format comprises a common generic portion, octets 1 to 36, that are based on those defined in IEEE Standard 802.1D, 2004, followed by components that are specific to CIST, octets 37 to 102. Components specific to each MSTI are added to this BPDUs data block.
MSTP configuration identification In case there is an allocation of VIDs (VLAN IDs) into an MST Region which differs within the different bridges that compose it, frames for some VIDs might be duplicated or even not delivered to some LANs at all. To avoid this, MST Bridges check that they are allocating VIDs to the same spanning trees as their neighboring MST Bridges in the same Region by transmitting and receiving MST Configuration Identifiers along with the spanning tree information. These MST Configuration Identifiers, while compact, are designed so that two matching identifiers have a very high probability of denoting the same configuration even in the absence of any supporting management practice for identifier allocation. Either one of this objects contains the following:
… excerpt ends here. Continue reading the full article.





