AdvancedPublished 2026-08-30
CCNA Break/Fix Capstone: One Symptom, Two Faults
Today's daily lab
Advanced CCNA troubleshooting capstone: a user on VLAN 10 can reach the gateway but not a remote server. Two independent faults exist on different layers; fixing either alone does not restore end-to-end reachability. Diagnose the full path, implement the minimal, design-aligned repair on each device, and prove bi-directional traffic works.
Learning objectives
- Trace end-to-end forwarding across L2 and L3 boundaries using show and ping/traceroute tools.
- Validate router-on-a-stick design: subinterface tags vs. switch uplink trunking.
- Diagnose asymmetric routing and install the correct return path via static routing.
- Differentiate a symptom from its root causes; identify when multiple faults produce one user complaint.
- Prove the repair with both forward and reverse traffic tests from hosts, not just device-to-device pings.
Troubleshooting focus
- Users in VLAN 10 can ping their default gateway but cannot reach the server subnet across the router-to-router link. The failure persists even though local ARP and the gateway respond; the issue is not on the host. The operator sees one symptom; the path has more than one fault. Work hop-by-hop: confirm VLAN tagging on the switch uplink toward the router-on-a-stick subinterface, then confirm a return route exists on the remote router.
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.