BeginnerPublished 2026-06-24
Layer 2 Access Hardening: PortFast, BPDU Guard & Sticky MAC
Archive lab
Hands-on CCNA Layer 2 switching lab: build VLANs, access ports, hardened 802.1Q trunks, and basic port-security across two access switches and an L2 core. Verify segmentation end-to-end from real hosts and practice troubleshooting native-VLAN and port/VLAN mismatches.
Learning objectives
- Create and name VLANs for Users, Servers, Management, and a secure native VLAN.
- Assign switchports to access VLANs and enable PortFast, BPDU Guard, and sticky port security.
- Build 802.1Q trunks with explicit allowed-vlan lists and a non-default native VLAN.
- Verify VLAN membership and trunk status and observe MAC learning behavior.
- Troubleshoot VLAN misassignments and trunk/native VLAN mismatches using symptoms from end hosts.
Troubleshooting focus
- Pings between PC-USER01 and SRV-APP01 unexpectedly succeed: both ports may sit in the same VLAN, or the trunk carries only one VLAN and both hosts landed there. Check access port VLANs with
show vlan briefand the allow-lists withshow interfaces trunk. - The VLAN 99 SVI is down/down on a switch: confirm VLAN 99 exists and is allowed on the trunks, and that at least one trunk carrying VLAN 99 is up — an SVI needs an active member port in that VLAN.
- Native VLAN mismatch messages appear on the console: confirm all trunk ends use native VLAN 999. A mismatch can cause untagged traffic to be misdelivered or blackholed.
- A host port flaps or goes err-disabled: port-security or BPDU Guard has triggered. Investigate with
show port-security interface <interface>andshow errdisable recovery, then clear by shutting/no shutting the interface once the cause is fixed. - The port-security check fails even though every port-security line is present:
show port-security interface <interface>must reportPort Security: Enabled. An interface accepts the options (violation mode, sticky learning, maximum addresses) while the feature itself is switched off.
Topology
Subscribe to preview this lab's topology.
See plansGrade your work
How this lab is graded
- Build it your way. Where a lab lets you choose a value — a VLAN name, an interface description — grading checks that you configured it, not which name you picked. Names that another line has to reference, like an ACL applied with
access-class, are stated in the guide and do have to match. - Addresses, modes and protocol keywords are exact. An IP address, a subnet mask,
switchport mode trunk, an encapsulation — these carry the meaning of the lab, so they are graded as written in the guide. - Grading reads your saved configuration. Export the lab from CML after you have configured it, and make sure anything you set is in the running-config — a change that only exists in a terminal session never reaches the grader.
- You can submit as many times as you like. Your best score stands, and each attempt tells you which checks passed so you can work the gaps.
- Scored something you believe is correct? Use Report an issue on this page — that is exactly how the grading fixes in the changelog got found.
Create a free account to submit your lab for grading.
Create a free accountFound a problem with this lab?
Please sign in to report a problem — tying it to your attempts lets us reproduce and fix it faster.