↪️
ccie.nyquist.eu
  • Table of Contents
  • Layer 2 Technologies
    • Ethernet Switching
      • L2 Switch Operations
      • Spanning Tree
        • 802.1d – STP
        • 802.1w – RSTP
        • 802.1s – MSTP
      • VTP 101
      • Private VLANs
      • VLANs
      • EtherChannel 101
    • Layer 2 WAN Protocols
      • HDLC
        • HDLC 101
      • PPP
        • PPP 101
        • PPP Authentication - PAP
        • PPP Authentication – CHAP
        • PPP Authentication – EAP
        • PPP Multilink
        • PPPoFR – PPP over Frame Relay
        • PPPoE – PPP over Ethernet
      • Frame Relay
        • Frame Relay 101
        • Frame Relay 102
        • Frame Relay Encapsulations – IETF vs Cisco
        • Multilink Frame Relay
        • Frame Relay Switching
        • Routing over Frame Relay
      • Bridging
        • Bridging on a router
        • MTU 101
    • Wireless
      • Wireless Principles
      • Wireless Implementations
      • Wireless Roaming
      • Wireless Authentication
        • WPA2 PSK
        • WPA2 802.1X
  • IPv4
    • IPv4 Addressing
      • Backup Interfaces
      • FHRP 101
      • DHCP 101
      • DNS 101
      • ARP 101
      • IPv4 101
      • Tunnel Interfaces
        • GRE Tunnels
      • BFD – Bidirectional Forwarding Detection
    • IPv4 Routing
      • How the routing table is built
        • How CEF works
        • Routing Order of Operations
        • NSF – Non Stop Forwarding
      • RIP
        • RIP 101
      • EIGRP
        • EIGRP 101
        • EIGRP Metric
        • More EIGRP Features
      • OSPF
        • OSPF 101
        • OSPF Areas
        • OSPF LSAs
        • OSPF Mechanics
      • IS-IS
        • IS-IS 101
        • IS-IS Mechanics – CLNP
      • BGP
        • BGP 101
        • BGP Attributes
        • More BGP
      • Route Redistribution
      • Policy based Routing
      • PfR 101 – Perfromance Routing
      • ODR
  • IPv6
    • IPv6-101
    • IPv6 Routing
    • Interconnecting IPv6 and IPv4
  • MPLS
    • MPLS 101
    • MPLS L3 VPN
  • Multicast
    • Multicast 101
    • PIM 101
    • IGMP 101
    • Inter Domain Multicast
    • IPv6 Multicast
    • Multicast features on switches
  • Security
    • NAT 101
    • NAT for Overlapping Networks
    • ACLs 101
    • ACLs 102
    • Cisco IOS Firewall
    • Zone Based Firewall
    • AAA 101
    • Controlling CLI Access
    • Control Plane
    • Switch Security
      • Switchport Traffic Control
      • Switchport Port Security
      • DHCP Snooping and DAI
      • 802.1x
      • Switch ACLs
    • IPSec VPN 101
      • IKE / ISAKMP 101
      • IPSEC Crypto Maps 101
      • IPSEC VTI 101
      • DMVPN 101
    • EAP 101
  • Network Services
    • NTP 101
    • HTTP 101
    • File Transfer 101 – TFTP & FTP
    • WCCP 101
  • QoS
    • QoS 101
    • Classification and Marking
    • Congestion Management
      • Legacy Congestion Management
      • SPD – Selective Packet Discard
      • CBWFQ
      • IP RTP Priority
    • Congestion Avoidance – WRED
    • Policing and Shaping
      • CAR 101
    • Compression and LFI
      • Header and Payload Compression
      • LFI for MultiLink PPP
    • Frame Relay QoS
      • Per VC Frame Relay QoS
    • RSVP 101
    • Switching QoS
  • Network Optimization
    • NetFlow 101 – TNF – Traditional NetFlow
    • NetFlow 102 – FNF – Flexible NetFlow
    • IP SLA 101
    • IP Accounting 101
    • Logging 101
    • SNMP and RMON 101
    • Cisco CLI Tips and Tricks
    • AutoInstall
    • Enhanced Object Tracking
    • Troubleshooting 101
    • SPAN, RSPAN, ERSPAN
  • Network Architecture
    • Hierarchical Network Architecture
    • SD Access
    • SD WAN
Powered by GitBook
On this page
  • MST Regions
  • MST Instances
  • IST
  • MSTIs
  • MST Hop Count
  • MST Configuration
  • Interoperability with other STP flavours

Was this helpful?

  1. Layer 2 Technologies
  2. Ethernet Switching
  3. Spanning Tree

802.1s – MSTP

The number of STP or RSTP instances that can run on a switch is limited. It is usually enough for most implementations but if you need to run STP on more VLANs, then MSTP is the solution. MSTP maps multiple VLANs to the same STP instance. Even when PVST or Rapid PVST is used, chances are that more than one instance will use the same loop-free topology and this is a waste of resources.

In PVST+ and Rapid PVST, one BPDU is sent on each VLAN on a trunk port. In 802.1q – there was only one STP instance, the CST, so only one BPDU was sent for all VLANs over the 802.1q links. To enable MSTP, use:

Sw(config)# spanning-tree mode mst

MST Regions

802.1s – MSTP uses the concept of regions. A MST region is represented by all connected switches that have the same VLAN to MSTP instance mapping. A MST Region is identified by:

  • a 32 Bytes alpahnumeric identifier

  • a 2 Bytes revision number

  • a table that maps each VLAN to a STP instance

Switches that share the same identification information are part of the same MST Region. When sending BPDUs, switches send a message digest of the VLAN-to-instance table. If the received digest is different then the one computed using its own data, the port where this BPDU is received is considered a Boundary Port.

MST Instances

Cisco’s implementation of 802.1s supports 16 instances, 1 IST (Internal Spanning Tree) and 15 MSTIs(MST Instances). To configure the MST instances, use:

Sw(config)# spanning-tree mst configuration
Sw(config-mst)# name MST-DOMAIN-NAME
Sw(config-mst)# revision MST-DOMAIN-REVISION
Sw(config-mst)# instance INSTANCE-ID vlan VLAN-LIST

Configuration will only be applied when you exit the mst configuration mode. To verify pending config, use:

Sw(config-mst)# show pending

When you first enable MSTP, Instance 0 is created and all VLANs are allocated to it.

IST

The IST runs on all bridges inside a MST Region and also provides interaction with the other MST Regions or other STP flavours (802.1d STP, 802.1q CST, PVST+). IST runs like a RSTP instance, but it also carries timer information in order to interact with legacy STP regions.

MSTIs

The MSTIs are RSTP instances that exist only within a MST region, with no outside interaction. MSTIs do not send their own BPDUs, instead MSTI information is attached to the IST BPDUs as M-Records. M-Records do not contain timer information so all instances use the same timers as the IST. MSTIs follow the IST topology at boundary port, so a boundary port will FWD or BLK for all VLANs.

MST Hop Count

MSTP Root Bridges send BPDUs with a default hop count of 20, and each bridge along the way decrements this value. If the hop count reaches 0, the incoming BPDU is discarded. To change the default value, use:

Sw(config)# spanning-tree mst max-hops HOP-COUNT

MST Configuration

MST Configuration is similar to the other STP flavours but it uses the mst keyword, like this:

! Configuring Root Bridge
Sw(config)# spanning-tree mst INSTANCE-LIST root {primary|secondary} [diameter DIA [hello-time HELLO]]
! Configuring Bridge Priority
Sw(config)# spanning-tree mst INSTANCE-LIST priority PRI
! Configuring Port Priority
Sw(config-if)# spanning-tree mst INSTANCE-LIST port-priority PRI
! Configuring Port Cost
Sw(config-if)# spanning-tree mst INSTANCE-LIST cost COST

Timers are only configured for IST, so there is no configuration per-instance:

Sw(config)# spanning-tree mst {hello-time HELLO|forward-time FORWARD|max-age MAXAGE}

RSTP Link Types are configured just link in RapidPVST

Sw(config-if)# spanning-tree link-type {point-to-point|shared}

Interoperability with other STP flavours

MSTP seamlessly interoperates with 802.1q CST. When interconnected with a PVST bridge, the MST bridge will replicate the IST out all VLANs. Not all possible configurations will be considered valid and an invalid configuration will put the boundary ports into a Root Inconsistent mode. A valid configuration can be achieved in the following cases:

  • If the MSTP is the root bridge, it must be the root for all VLANs (recommended)

  • If the PVST+ is the root bridge, it must be the root for all VLANs

Any other configuration will fail. (E.g. when the MSTP bridge is the root for the CST while the PVST+ bridge is the root for one or more VLANs) You can manually set the neighbor type to non-MSTP, using:

Sw(config)#spanning-tree mst pre-standard
Previous802.1w – RSTPNextVTP 101

Last updated 3 years ago

Was this helpful?