MST Region Configuration Mismatch — Treated as Different Regions
Presenting Symptom
Spanning-tree topology loops occur intermittently, and some VLANs are unreachable despite all switches being configured with the same MST region name and revision number.
Network Context
A small enterprise campus network with three Cisco Catalyst 2960 switches (IOS 15.0) running MSTP. The switches are interconnected via trunk links. The network has 10 VLANs, and MSTP is configured to map VLANs 1-5 to instance 1 and VLANs 6-10 to instance 2. All switches are configured with the same region name 'CAMPUS' and revision number 1.
Diagnostic Steps
Check MST region configuration on each switch
show spanning-tree mst configurationName [CAMPUS] Revision 1 Instances configured 2 Instance Vlans mapped -------- ----------------------------------------------------------------- 0 1-5 1 6-10 -----------------------------
Verify that the region name, revision number, and VLAN-to-instance mapping are identical on all switches. Any difference (e.g., extra space in name, different revision, or mismatched VLAN mapping) will cause switches to treat each other as different regions, breaking MSTP interoperability.
Check MST region status on each switch
show spanning-tree mst##### MST0 vlans mapped: 1-5 Bridge address 0011.2233.4455 priority 32768 Root address 0011.2233.4455 priority 32768 Interface Role Sts Cost Prio.Nbr Type ------------------- ---- --- --------- -------- -------------------------------- Gi0/1 Desg FWD 200000 128.1 P2p Gi0/2 Desg FWD 200000 128.2 P2p ##### MST1 vlans mapped: 6-10 Bridge address 0011.2233.4455 priority 32768 Root address 0011.2233.4455 priority 32768 Interface Role Sts Cost Prio.Nbr Type ------------------- ---- --- --------- -------- -------------------------------- Gi0/1 Desg FWD 200000 128.1 P2p Gi0/2 Desg FWD 200000 128.2 P2p
If the switches are in different regions, each switch will consider itself the root for all instances (since they don't receive BPDUs from other regions). Look for multiple roots per instance across switches. Also check if any ports are in BLK (blocking) state; in a properly working MST region, some ports should be blocking to prevent loops.
Check MST BPDU details on trunk interfaces
show spanning-tree mst interface gigabitEthernet 0/1 detailPort 1 (GigabitEthernet0/1) of MST0 is forwarding Port path cost 200000, Port priority 128, Port identifier 128.1. Designated root has priority 32768, address 0011.2233.4455 Designated bridge has priority 32768, address 0011.2233.4455 Designated port id is 128.1, designated path cost 0 Timers: message age 0, forward delay 0, hold 0 BPDU: sent 123, received 456 ...
Check the 'BPDU: sent 123, received 456' line. If BPDUs are being received from the neighbor, but the MST region is mismatched, the switch will treat those BPDUs as from a different region and may ignore them or cause topology changes. Also check the 'Designated root' address; if it differs from the expected root, it indicates the neighbor is not part of the same region.
Verify MST region consistency using debug
debug spanning-tree mst eventsMST: received MST BPDU on Gi0/1 with mismatched region name (received: CAMPUS, expected: CAMPUS ) MST: received MST BPDU on Gi0/1 with mismatched revision (received: 1, expected: 2)
Enable debug to see if the switch logs mismatched region parameters. The output will show exactly what is different (e.g., extra space in name, different revision). This confirms the root cause. Note: Use debug cautiously in production.
Root Cause
One or more switches have a subtle mismatch in MST region configuration: either an extra space in the region name (e.g., 'CAMPUS ' vs 'CAMPUS'), a different revision number, or a different VLAN-to-instance mapping. This causes the switches to treat each other as belonging to different MST regions, breaking MSTP interoperability and causing each switch to run MSTP independently, leading to loops and VLAN reachability issues.
Resolution
Verification
1. Run 'show spanning-tree mst configuration' on all switches to confirm identical output. 2. Run 'show spanning-tree mst' to verify that the root bridge is the same for each instance across all switches and that appropriate ports are blocking. 3. Check connectivity: ping between hosts in different VLANs to confirm reachability.
Prevention
1. Use a consistent configuration template or automation to deploy MST region settings across all switches. 2. Always copy-paste region name carefully to avoid hidden spaces; use 'show running-config | include name' to verify. 3. Document the MST region configuration and include it in change management procedures.
CCNA Exam Relevance
On the CCNA 200-301 exam, this scenario may appear as a troubleshooting question where you must identify why MSTP is not working despite seemingly identical configurations. The exam tests your ability to recognize that MST region parameters must match exactly (name, revision, VLAN mapping) for switches to be in the same region. A common distractor is that the region name looks the same but has a trailing space.
Exam Tips
Memorize that MST region matching requires exact match of name, revision, and VLAN-to-instance mapping; even a trailing space breaks the region.
When troubleshooting MSTP, always start with 'show spanning-tree mst configuration' on all switches to compare.
Be aware that 'show spanning-tree mst' will show each switch as root if they are in different regions, which is a key indicator.
Test Your CCNA Knowledge
Practice with scenario-based questions to prepare for the CCNA 200-301 exam.
Practice CCNA Questions