AdvancedPublished 2026-07-04
Discovery & Monitoring Troubleshooting Capstone
Bundle lab
Lab 10 of 10 in Network Discovery & Monitoring · ← Previous
CCNA exam domain: IP Services
Advanced discovery and monitoring capstone, run as a fault hunt. The NMS has stopped seeing this site: neighbours are missing from the topology map, no traps are arriving, and syslog went quiet — while every device is reachable and pingable. You get symptoms and the required end state — no fault list. Faults span both routers and the switch they all peer through, and more than one of them leaves the monitoring configuration looking complete.
Learning objectives
- Diagnose a monitoring outage from operational state alone, with no list of what was changed
- Check discovery on the device in the middle before concluding the endpoints are at fault
- Recognise per-interface suppression of a protocol that is still enabled globally
- Know that a trap destination configured with an undefined community sends nothing anybody will accept
- Repair faults across a switch and two routers
Troubleshooting focus
- If pings fail across the LAN: verify interfaces are up/up and IP addresses/masks match the 10.0.0.0/24 plan. Ensure no default gateway is assumed on the server—it’s a flat LAN.
- If
show logginglists a remote host that is not the NMS: you’ve found a deterministic misconfiguration—correct the remote destination IP. - If
show snmp hostlists the NMS but no traps arrive: verify global trap generation is enabled, not just the host target. - If discovery seems odd: ensure CDP/LLDP are globally enabled and allowed on the LAN interface. Discovery is not graded here, but it’s part of a complete management stance.
- If DNS lookups fail: confirm ip name-server points at 10.0.0.100 and any ip host entry for the NMS matches the addressing plan.
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.