Your team supports a small campus access layer: two switches, one 802.1Q trunk. The help desk reports VLAN 20 users cannot reach their peers while VLAN 10 users can, and both ends read up and trunking. Campus design: VLANs 10 and 20 are the only VLANs any trunk carries; every trunk's native VLAN is 999.
Start here — freeCCNA Break/Fix: Diagnose and Repair
Seven hands-on repair labs — each ships a working network with a fault already in it. Read the symptom, find the cause, and prove the fix.
Topics
What you'll learn
- Diagnose a trunk that forwards one VLAN and drops another
- Isolate where a trunk's operational state departs from the campus design using show interfaces trunk
- Distinguish an access-port VLAN error from a trunk problem presenting the same symptom
- Verify every trunk parameter agrees at both ends of the link
- Diagnose which switch holds root for each VLAN with `show spanning-tree`.
- Trace the VLAN 10 path from CLIENT10-A to CLIENT10-B and the blocked port.
- Distinguish an election result from a trunk inconsistency with `show interfaces trunk`.
- Verify both VLANs converge on the intended root and the blocked port moves.
Included labs
A campus triangle of one distribution and two access switches carries VLAN 10 and VLAN 20. After an access-switch replacement, users report slower cross-campus response: hosts still reach each other, and the layer 2 path no longer matches a design that roots both VLANs at SW-CAMPUS-DIST1.
View lab detailsA regional retailer's branch lost core access after last night's maintenance window. Users reach their gateway and the routers ping across the transit, but no OSPF neighbour appears and the branch LAN is missing from the core's table. The documented design is OSPF process 1, area 0 on both routers. Restore the adjacency without changing addressing or adding static routes.
View lab detailsBranch staff cannot work: no workstation on the user LAN holds an address. By design, clients there lease from the hub router's scope and the two sites route to each other statically. Find why no lease arrives; change nothing else.
View lab detailsA branch reaches its provider through one edge router that hides the user LAN behind its upstream address. Since a change window, everyone on 192.168.10.0/24 reports that nothing beyond the branch answers, while the router itself reaches the provider's test address. Find what is wrong.
View lab detailsBranch staff cannot reach the server at 172.16.100.100, and they cannot close a day's tickets without it. Policy also requires Telnet from the user LAN to that server be denied while everything else passes, and the security review cannot confirm it is being enforced. Work the path from a client and find what is wrong.
View lab detailsA branch user in VLAN 10 cannot reach the data center's line-of-business server, stalling the end-of-day batch upload. Two faults sit behind the one complaint, and clearing either alone leaves the user where they started. The client gets no answer from its own gateway either.
View lab detailsFrequently asked questions
What's included in the CCNA Break/Fix: Diagnose and Repair bundle?
7 hands-on, auto-graded CCNA labs spanning 14 topics — each one a real Cisco Modeling Labs scenario you build on Cisco IOS.
Can I buy this bundle?
No — a subscription is the only plan we sell, and it includes every lab in this bundle for as long as it's active.
Do I need my own Cisco CML to run these labs?
Yes — each lab is a Cisco Modeling Labs (CML) topology you import and build on real Cisco IOS, and the CML free tier is enough. You download the topology and lab guide, then build it yourself.
How does the grading work?
Every lab ships as a problem to solve. You build it in CML, then submit your config to grade it against the answer key — you get a pass/fail on each objective, so you know exactly what's right and what to fix instead of guessing.
Which certification is this bundle for?
CCNA. The labs are sequenced to build the hands-on configuration and troubleshooting skills CCNA candidates are expected to demonstrate on real gear.