LAB 6.1: MST Region Configuration & IST Fundamentals

🎯 Lab Duration: 75-90 minutes

📊 Difficulty Level: Intermediate-Advanced

🔧 Equipment Required: 5 Cisco Switches (2 Core + 3 Access)

✅ CCNP Exam Alignment: 350-401 (ENCOR) - Spanning Tree Protocol Advanced Features [1]

📚 Learning Objectives

Enable Multiple Spanning Tree (MST) mode on Cisco switches [1]
Configure MST region attributes: region name, revision number, and VLAN-to-instance mapping [1]
Understand and configure the Internal Spanning Tree (IST/Instance 0) [1]
Select IST root bridge using primary and secondary methods
Verify MST configuration using show commands
Troubleshoot MST region mismatches and BPDU issues
Compare MST efficiency gains over legacy PVST+ implementations

🏢 Lab Scenario

Your enterprise campus network consists of a two-tier architecture with 2 core switches and 3 access-layer switches. The network currently operates with legacy PVST+, causing high CPU overhead. You must implement a unified MST region to optimize resource utilization and improve convergence time [1].

ℹ️ Real-World Application: By consolidating 30 VLANs into a single MST region, you reduce CPU overhead by 40-60% compared to PVST+, while maintaining loop-free topology and enabling asymmetric load balancing [1].

🔗 Network Topology Diagram

LAB 5.2: ACCESS LAYER REDUNDANCY - PORT PRIORITY CONFIGURATION

⚙️ Equipment Setup & Requirements

Physical Equipment Requirements

Device Role	Hostname	Interfaces	VLAN Assignments	Priority
Core Switch 1	CORE-SW-1	G0/0,	All VLANs (1-50)	4096 (Primary)
Core Switch 2	CORE-SW-2	G0/0,	All VLANs (1-50)	8192 (Secondary)
Access Switch 1	ACCESS-SW-1	Eth1/1, Eth1/2	Mixed (1-50)	16384
Access Switch 2	ACCESS-SW-2	Eth1/1, Eth1/2	Mixed (1-50)	16384

🔧 Step-by-Step Configuration

⚠️ Pre-Lab Warning:
Reset all switches: write erase then reload

Phase 1: Initial Setup & Basic Configuration

Access CORE-SW-1 and Set Hostname

Switch> enable
Switch# configure terminal
Switch(config)# hostname CORE-SW-1
CORE-SW-1(config)# no ip domain-lookup
CORE-SW-1(config)# line console 0
CORE-SW-1(config-line)# logging synchronous
CORE-SW-1(config-line)# exit

✓ Verification: Prompt shows CORE-SW-1(config)#

Create VLAN Database on CORE-SW-1

CORE-SW-1(config)# vlan 10
CORE-SW-1(config-vlan)# name Finance
CORE-SW-1(config-vlan)# exit
CORE-SW-1(config)# vlan 20
CORE-SW-1(config-vlan)# name HR
CORE-SW-1(config-vlan)# exit
CORE-SW-1(config)# vlan 30,40,50
CORE-SW-1(config)# exit

✓ Verify: show vlan brief

Configure Trunk Links (Core to Access)

CORE-SW-1(config)# interface range ethernet 1/1-2
CORE-SW-1(config-if-range)# description Links to Access Layer
CORE-SW-1(config-if-range)# switchport mode trunk
CORE-SW-1(config-if-range)# switchport trunk allowed vlan 1-50
CORE-SW-1(config-if-range)# no shutdown
CORE-SW-1(config-if-range)# exit

✓ Verify: show interface trunk

Configure Inter-Core Links

CORE-SW-1(config)# interface G0/0
CORE-SW-1(config-if-range)# description Core-to-Core IST Link
CORE-SW-1(config-if-range)# switchport mode trunk
CORE-SW-1(config-if-range)# switchport trunk allowed vlan 1-50
CORE-SW-1(config-if-range)# no shutdown
CORE-SW-1(config-if-range)# exit

✓ Verify: show interface status | include up

Phase 2: Enable MST Mode & Configure Region [1]

Enable MST Mode on CORE-SW-1

CORE-SW-1(config)# spanning-tree mode mst

✓ Mode changed to MST. IST (Instance 0) now active for all VLANs.

Configure MST Region Attributes [1]

All switches MUST have identical region configuration.

CORE-SW-1(config)# spanning-tree mst configuration
CORE-SW-1(config-mst)# name CCNP-Region
CORE-SW-1(config-mst)# revision 1
CORE-SW-1(config-mst)# instance 0 vlan 1-50
CORE-SW-1(config-mst)# exit

🎓 Key Points [1]:
• Region Name: "CCNP-Region" (case-sensitive)
• Revision Number: Tracks configuration changes
• All switches MUST have identical attributes
• Mismatch = separate STP domains

✓ Verify: show spanning-tree mst configuration

Phase 3: Configure IST Root Bridge Selection [1]

Set CORE-SW-1 as IST (Instance 0) Primary Root Bridge [1]

CORE-SW-1(config)# spanning-tree mst 0 root primary

✓ IST Root Set. Priority automatically set to 4096 (24576 with system ID).

✓ Verify: show spanning-tree mst 0 | include "This bridge is"

Phase 4: Configure Remaining Switches

Replicate Configuration on CORE-SW-2 (Steps 1-6)

! On CORE-SW-2:
Switch# configure terminal
Switch(config)# hostname CORE-SW-2
CORE-SW-2(config)# vlan 10,20,30,40,50
CORE-SW-2(config)# interface range G0/0
CORE-SW-2(config-if-range)# switchport mode trunk
CORE-SW-2(config-if-range)# switchport trunk allowed vlan 1-50
CORE-SW-2(config-if-range)# no shutdown
CORE-SW-2(config)# interface range E1/1-2
CORE-SW-2(config-if-range)# switchport mode trunk
CORE-SW-2(config-if-range)# switchport trunk allowed vlan 1-50
CORE-SW-2(config-if-range)# no shutdown
CORE-SW-2(config-if-range)# exit
CORE-SW-2(config)# spanning-tree mode mst
CORE-SW-2(config)# spanning-tree mst configuration
CORE-SW-2(config-mst)# name CCNP-Region
CORE-SW-2(config-mst)# revision 1
CORE-SW-2(config-mst)# instance 0 vlan 1-50
CORE-SW-2(config-mst)# exit

⚠️ Critical: Region name and revision MUST exactly match CORE-SW-1.

Set CORE-SW-2 as IST Secondary Root Bridge [1]

CORE-SW-2(config)# spanning-tree mst 0 root secondary

✓ IST Secondary Root Set. Priority: 8192 (28672 with system ID). Failover ready.

Configure ACCESS-SW-1, ACCESS-SW-2, ACCESS-SW-3

Execute steps 1-6 on all access switches with identical MST region config.

! On each ACCESS switch (1, 2):
Switch# configure terminal
Switch(config)# hostname ACCESS-SW-X
ACCESS-SW-X(config)# vlan 10,20,30,40,50
ACCESS-SW-X(config)# interface range ethernet 1/1-2
ACCESS-SW-X(config-if-range)# switchport mode trunk
ACCESS-SW-X(config-if-range)# switchport trunk allowed vlan 1-50
ACCESS-SW-X(config-if-range)# no shutdown
ACCESS-SW-X(config-if-range)# exit
ACCESS-SW-X(config)# spanning-tree mode mst
ACCESS-SW-X(config)# spanning-tree mst configuration
ACCESS-SW-X(config-mst)# name CCNP-Region
ACCESS-SW-X(config-mst)# revision 1
ACCESS-SW-X(config-mst)# instance 0 vlan 1-50
ACCESS-SW-X(config-mst)# exit
ACCESS-SW-X(config)# spanning-tree mst 0 priority 32768

✅ Verification & Validation Checklists

Verification Checklist 1: MST Region Configuration

All 5 switches have hostname configured All 5 switches have MST mode enabled: show spanning-tree mst Region name "CCNP-Region" matches on all switches [1] Revision number "1" matches on all switches [1] All VLANs (1-50) are mapped to Instance 0 [1] Switches recognize each other in same region

Verification Checklist 2: Trunk Links & Connectivity

All trunk links operational: show interface trunk Trunks allow VLANs 1-50 No interface errors: show interfaces status err-disabled All 5 switches can ping each other

Verification Checklist 3: Root Bridge Selection & BPDUs

CORE-SW-1 is IST root [1] CORE-SW-1 priority is 4096 (24576 with system ID) CORE-SW-2 priority is 8192 (28672 with system ID) Access switches show CORE-SW-1 as regional root [1] IST BPDUs being sent/received on all ports

📋 Critical Verification Commands

1. MST General Status:
show spanning-tree mst
show spanning-tree mst 0

2. MST Configuration Details [1]:
show spanning-tree mst configuration
Shows region name, revision, VLAN-instance mapping

3. Detailed MST Information:
show spanning-tree mst detail
Displays bridge role, port roles, costs, interface details [1]

4. Port-Level MST Status:
show spanning-tree mst interface ethernet 1/1
Displays role, state, and cost for specific interface

5. Region Membership Verification:
show spanning-tree mst configuration
Confirm matches on all switches [1]

🔍 Troubleshooting Guide

Issue 1: Switches Show Different MST Regions

Symptom: show spanning-tree mst configuration shows different region names or revision numbers.

Root Cause: Configuration mismatch prevents region formation [1].

Solution:

! On mismatched switch:
Switch(config)# spanning-tree mst configuration
Switch(config-mst)# name CCNP-Region
Switch(config-mst)# revision 1
Switch(config-mst)# exit

Issue 2: Not All Switches Recognize IST Root

Symptom: show spanning-tree mst 0 shows different root on different switches.

Root Cause: Region not fully converged or VLAN mapping mismatch.

Solution:

Wait 30-60 seconds for IST BPDUs to propagate [1]
Verify all switches have identical Instance 0 VLAN mapping [1]
Check: debug spanning-tree events | include mst

Issue 3: Trunk Links Show as "Blocking"

Symptom: show spanning-tree mst detail shows trunk port in "Blocking" state on all access switches.

Root Cause: This is EXPECTED in a basic two-tier topology. Only one path per VLAN should be forwarding to prevent loops [1].

Issue 4: High BPDU Activity / CPU Spike

Symptom: Switches show high CPU utilization or excessive BPDU transmission.

Root Cause: Loop or misconfigured trunk (probably not set to trunk mode).

Solution:

! Verify all trunk ports are correctly configured:
Switch# show interface trunk

! If any port is missing, reconfigure:
Switch(config)# interface ethernet 1/1
Switch(config-if)# switchport mode trunk
Switch(config-if)# exit

📊 Expected Lab Outcomes

Outcome	Expected Result	Verification Command
MST Region Unified	All 5 switches in "CCNP-Region" (Revision 1)	show spanning-tree mst configuration
IST Root Selected	CORE-SW-1 priority 4096, IST root [1]	show spanning-tree mst 0
Secondary Root Ready	CORE-SW-2 priority 8192 as backup	show spanning-tree mst 0
BPDU Efficiency	Only 1 BPDU per port (all VLANs inside IST) [1]	show spanning-tree mst detail
Loop-Free Topology	No blocked interfaces on core links	show spanning-tree blocked
Trunk Connectivity	All 5 switches interconnected via trunks	show interface trunk

📈 Performance Improvement Metrics

Comparing MST (Lab Result) vs. Legacy PVST+:

Metric	PVST+ (Legacy)	MST (After Lab)	Improvement
STP Processes	50 (1 per VLAN)	1 (Instance 0)	98% reduction [1]
CPU Load	45% baseline	12-18% baseline	60% reduction
Memory Usage	28 MB	8 MB	71% reduction [1]
BPDU Overhead	50 BPDUs/port/sec	1 BPDU/port/sec	98% reduction [1]
Convergence Time	30-50 seconds	6-10 seconds (RSTP-based)	~80% faster [1]

✅ Lab Completion Criteria [1]

Successfully Complete This Lab When:
✓ All 5 switches unified in single region (CCNP-Region, Rev 1) [1]
✓ IST root bridge selected and verified (CORE-SW-1)
✓ Secondary root bridge configured (CORE-SW-2)
✓ All trunk links operational and loop-free [1]
✓ MST configuration consistent across all switches
✓ No region mismatch or convergence delays detected
✓ All verification commands execute successfully
✓ Lab can be replicated consistently

🔐 Access Restricted