BeginnerPublished 2026-06-23
VLANs for Two Departments: Trunking & Sticky MAC Security
Archive lab
Hands-on CCNA lab: build VLANs for Sales and Engineering, implement 802.1Q trunks with a hardened native VLAN, assign access ports, and apply sticky MAC port-security on access interfaces. The design uses a compact, realistic branch topology with a router-on-a-stick gateway, a distribution L2 switch, one access L2 switch, and two end hosts. Students deploy, verify, and troubleshoot VLAN reachability, trunk integrity, and port-security violations.
Learning objectives
- Configure and verify VLANs and switchport modes on Cisco switches
- Implement and test IEEE 802.1Q trunks with an explicit allowed VLAN list and a secured native VLAN
- Assign access ports to VLANs and connect endpoint devices
- Configure, verify, and troubleshoot basic sticky MAC port-security on access ports
Troubleshooting focus
- CLIENT-SALES01 pings its gateway 10.10.10.1 but not 10.20.20.10: check the access port VLANs on SW-SITE-ACC1, that trunks allow VLANs 10 and 20, and that RTR-SITE-ROAS has Ethernet0/0.10 and Ethernet0/0.20.
- The console logs a native VLAN mismatch, or traffic is intermittent: confirm every trunk uses native VLAN 999 on both ends and that VLAN 1 is pruned from the allowed lists.
show interfaces trunkshows both. - A user port went err-disabled: port-security caught a violation. Shut and no-shut the interface to clear it, and clear the sticky learned MAC if the host's MAC changed. Confirm with
show port-security interface. - 10.100.100.2 and 10.100.100.3 are unreachable: verify VLAN 100 is on the trunks, RTR-SITE-ROAS has Ethernet0/0.100, and both switches have
ip default-gatewayset to 10.100.100.1. show port-security interface <interface>reportsPort Security: Disabledalthough the violation, sticky and maximum lines are all present: the interface accepts those options with the feature switched off.; The graded check needsPort Security: Enabled, and it fails while the report readsDisabled.
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.