AdvancedPublished 2026-07-04
Static Routing Capstone: Two Sites Over a /30 WAN
Archive lab
Advanced static-routing capstone, run as a fault hunt. Two suites were cut over last night and now Suite-B is unreachable, Suite-A gets replies only sometimes, and one client cannot even reach its own gateway. Nothing was written down. You get symptoms and the required end state — no fault list. The faults span both routers and the access switch, and the routing table being present does not mean it is right.
Learning objectives
- Diagnose a broken inter-suite path from operational state alone, with no list of what was changed
- Tell a black-holed route apart from a missing return route — both look like 'it does not work' from a client
- Recognise asymmetric reachability as evidence about which direction is actually broken
- Check Layer 2 before blaming Layer 3: a port in the wrong VLAN presents as a routing failure
- Repair faults on whichever device holds them, across two routers and a switch
Troubleshooting focus
- Detect and fix missing return routes that cause one-way pings
- Correct interface shutdowns and wrong port/VLAN assignments on the switch
- Resolve wrong masks or next-hop IPs that break adjacency or blackhole traffic
- Identify routing loops or defaults pointing to the wrong neighbor
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.