IntermediatePublished 2026-06-30
Three-VLAN Router-on-a-Stick: Build, Harden & Verify
Bundle lab
Build and verify a three-VLAN router-on-a-stick design: one IOS router provides inter-VLAN routing via 802.1Q subinterfaces to a single Layer-2 access switch, with three Alpine hosts in VLANs 10, 20, and 30. The starter environment does not yet forward traffic correctly between all three VLANs, so you will apply a disciplined router-switch-host verification method to diagnose and fix the problem, then briefly break and restore one VLAN's connectivity before finishing with an enterprise-clean, hardened trunk.
Learning objectives
- Configure inter-VLAN routing using router-on-a-stick (ROAS) on a single IOS router.
- Assign access ports to VLANs 10, 20, and 30 on an L2 switch and trunk all routed VLANs to the router.
- Apply trunk hardening: dot1Q, explicit allowed VLANs, native VLAN 999, and nonegotiate.
- Use a disciplined cross-device verification checklist (router, switch, hosts) to prove forwarding.
- Diagnose and resolve faults caused by an incorrect trunk allow-list and an incorrect host VLAN assignment.
Troubleshooting focus
- Trace end-to-end failures from the host perspective; confirm where traffic first fails.
- Correlate router subinterfaces and IP gateways to switch VLAN membership and trunk state.
- Identify and correct switch trunk allow-list omissions that strand a VLAN.
- Identify and correct an access port in the wrong VLAN.
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.