CCNA lab 13 of 46
Protecting spanning tree with PortFast and the STP guards
Someone has plugged a switch into a desk port and it wants to be root. Watch it hijack the spanning tree, then stop it with root guard and BPDU guard, speed up host ports with PortFast, and add loop guard and (carefully) BPDU filter.
Run this lab
It needs Lite: its 6 nodes are set to 6 vCPU and 6,144 MB in total. That fits the free demo too.
In your workspace: Shared, then CCNA 200-301 guided labs, then 13 - Protecting spanning tree with PortFast and the STP guards
- Level
- Intermediate
- Time
- About 55 minutes
- Nodes need
- 6 vCPU, 6,144 MB
- Smallest plan
- Lite
The scenario
At Fenwick Solicitors, a trainee brought in a small switch to get more ports at their desk and plugged it into desk port ASW1 Gi1/1. That switch (ROGUE) has a bridge priority of 0 for VLAN 10, so it will try to become the root of the whole network. You'll see what that does, then lock the access layer down so it can't happen again.
| Device | Port | Role |
|---|---|---|
| DSW1 | Gi0/0, Gi0/1 | trunks to ASW1 and ASW2; SVI VLAN 10 10.13.10.1/24; intended root (4096) |
| ASW1 | Gi0/0 to DSW1, Gi0/1 to ASW2; Gi1/0 PC1; Gi1/1 desk port | access switch |
| ASW2 | Gi0/0 to DSW1, Gi0/1 to ASW1; Gi1/0 PC2 | access switch |
| ROGUE | Gi0/0 to ASW1 Gi1/1 (starts shut down = unplugged) | rogue switch, priority 0 |
| PC1, PC2 | VLAN 10 | 10.13.10.11, 10.13.10.12 |
"Plugging in" the rogue switch means no shutdown on ROGUE Gi0/0; "unplugging" it means shutdown.
What you’ll practise
- Configure PortFast on host ports and explain edge ports
- See a rogue switch take over as root and contain it with root guard
- Err-disable a rogue switch port with BPDU guard and recover the port
- Explain and enable loop guard
- Explain BPDU filter and why it is dangerous on an interface
The tasks
- Make host ports edge ports with PortFast
- See the rogue switch take over
- Contain it with root guard
- Shut it out with BPDU guard
- Know BPDU filter (and why to avoid it)
- Add loop guard
- Protect the distribution layer
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
- DSW1
Gi0/0to ASW1Gi0/0 - DSW1
Gi0/1to ASW2Gi0/0 - ASW1
Gi0/1to ASW2Gi0/1 - ASW1
Gi1/0to PC1eth0 - ASW1
Gi1/1to ROGUEGi0/0 - ASW2
Gi1/0to PC2eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| DSW1 | Cisco IOSvL2 | viosl2-adventerprisek9-m.ssa.high_iron_20200929 | 1 vCPU, 1,024 MB |
| ASW1 | Cisco IOSvL2 | viosl2-adventerprisek9-m.ssa.high_iron_20200929 | 1 vCPU, 1,024 MB |
| ASW2 | Cisco IOSvL2 | viosl2-adventerprisek9-m.ssa.high_iron_20200929 | 1 vCPU, 1,024 MB |
| ROGUE | Cisco IOSvL2 | viosl2-adventerprisek9-m.ssa.high_iron_20200929 | 1 vCPU, 1,024 MB |
| PC1 | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
| PC2 | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
CCNA 200-301 guided labs.Open
13 - Protecting spanning tree with PortFast and the STP guardsand 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 CCNA labs
Related labs in other courses
CloudLabBox is independent of Cisco. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.