Multi-vendor troubleshooting lab 5 of 12
Spanning-tree interoperability with PVST MST and RSTP
Larkfield's campus is half way through a move to one MST region: one Cisco switch still runs Rapid PVST+, Arista and Aruba have typed their region differently, and the MikroTik only speaks RSTP. Find the boundaries, join the region, and prove the same digest on three vendors.
Run this lab
It needs Standard: its 7 nodes are set to 8 vCPU and 7,936 MB in total.
In your workspace: Shared, then Multi-vendor interoperability and troubleshooting guided labs, then 05 - Spanning-tree interoperability with PVST MST and RSTP
- Level
- Advanced
- Time
- About 80 minutes
- Nodes need
- 8 vCPU, 7,936 MB
- Smallest plan
- Standard
The scenario
Larkfield has decided that the Leeds campus will run one MST region, called LARKFIELD, revision 1. SW1 has been converted. SW2 is still on Rapid PVST+ and was the old root for VLAN 10. The Arista and Aruba switches were set up by different contractors. The MikroTik CHR1 has a plain RSTP bridge and stays that way, as RouterOS bridges at this site aren't in the region.
Since the change, H1 can't reach H2, and SW1 shut its port to CHR1 as soon as the MikroTik came up.
| Device | Role | Target |
|---|---|---|
| SW1 | Region root | Root for instances 0 and 1 (priority 4096) |
| SW2 | Secondary root | Root for instance 2 (priority 4096); 8192 for instances 0 and 1 |
| EOS1, CX1 | Access | Default priority, in the region |
| CHR1 | RSTP bridge, outside the region | Default priority |
| MST setting | Value |
|---|---|
| Region name | LARKFIELD (case matters) |
| Revision | 1 |
| Instance 1 | VLAN 10 |
| Instance 2 | VLAN 20 |
| Host | Address | Attached to |
|---|---|---|
| H1 | 10.10.0.101/24 | EOS1 Ethernet4, VLAN 10 |
| H2 | 10.10.0.102/24 | CX1 1/1/3, VLAN 10 |
| CHR1 | 10.10.0.4/24 | vlan10 on bridge br1 |
What you’ll practise
- Read root, role and region on IOSvL2, EOS, AOS-CX and RouterOS
- Recognise a PVST simulation inconsistency at an MST boundary
- Compare MST configuration digests across vendors
- Explain how each vendor expresses bridge priority
- Recover a port shut by BPDU guard, and explain why RSTP on a router triggered it
- Place the root for each MST instance
The tasks
- Give the hosts their addresses
- Map the tree as it is
- The PVST boundary between SW1 and SW2
- One region needs one digest
- BPDU guard against a router
- Read priority in each vendor's units
The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.
Topology and devices
The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.
Every link, as text
- SW1
Gi0/0to SW2Gi0/0 - SW2
Gi0/1to CX11/1/1 - CX1
1/1/2to EOS1Ethernet2 - EOS1
Ethernet1to SW1Gi0/1 - CHR1
ether1to SW1Gi0/2 - CHR1
ether2to EOS1Ethernet3 - EOS1
Ethernet4to H1eth0 - CX1
1/1/3to H2eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| SW1 | Cisco IOSvL2 | viosl2-adventerprisek9-m.ssa.high_iron_20200929 | 1 vCPU, 768 MB |
| SW2 | Cisco IOSvL2 | viosl2-adventerprisek9-m.ssa.high_iron_20200929 | 1 vCPU, 768 MB |
| EOS1 | Arista vEOS | veos-4.33.1.1F | 1 vCPU, 2,048 MB |
| CX1 | Aruba AOS-CX virtual switch | arubacx-10.14 | 2 vCPU, 3,072 MB |
| CHR1 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| H1 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
| H2 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
Multi-vendor interoperability and troubleshooting guided labs.Open
05 - Spanning-tree interoperability with PVST MST and RSTPand start its nodes, then open Lab Tasks for the scenario and the steps.
The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.
More Multi-vendor troubleshooting labs
All Multi-vendor troubleshooting labs
Related labs in other courses
CloudLabBox is independent of Arista Networks, Cisco, CompTIA, Fortinet, HPE, Juniper Networks and MikroTik. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.