AdvancedPublished 2026-07-04
L2 Security Troubleshooting Capstone: Trust Boundary
Bundle lab
Advanced Layer-2 security capstone. Neither PC on the access switch can get an address, and the help desk has already 'checked the DHCP server'. You get the symptoms and the requirements — no fault list. Work from show output to find every misconfiguration across the switch and the router, repair them, and prove both hosts recover. Several faults are layered: fixing the first one changes the symptom without ending the outage.
Learning objectives
- Diagnose a DHCP outage end to end from operational state alone, without a list of what was broken
- Read DHCP Snooping and Dynamic ARP Inspection state to locate a trust boundary that is inverted in two directions
- Recognise that DHCP Snooping stamps Option 82 by default and that a non-relay server drops those requests
- Find a second-order fault that only becomes visible once the first is fixed, rather than stopping at the first success
- Correct configuration on whichever device is at fault — the switch is not the only suspect
Troubleshooting focus
- Correlate DHCP failure symptoms (no lease) with DHCP Snooping trust on the uplink
- Correlate legitimate ARP drops with DAI enforcement and missing/incorrect trust placement
- Leverage show ip dhcp snooping, show ip dhcp snooping binding, show ip arp inspection, and show running-config interface to triangulate the boundary
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.