IntermediatePublished 2026-06-30
VLAN Trunking 6: DTP and Trunk Hardening
Bundle lab
Hands-on DTP negotiation and trunk hardening across a 3-switch path. You will observe dynamic trunking behavior (auto vs desirable), fix an allow-list drift that blocks user VLAN transport, and then harden the trunks to static with nonegotiate and a non-default native VLAN. End-to-end host reachability in the same VLAN proves success.
Learning objectives
- Differentiate DTP dynamic auto vs dynamic desirable and predict whether a trunk will form.
- Use show interfaces switchport and show interfaces trunk to verify negotiation and trunk state.
- Detect and remediate a trunk allowed-VLAN drift that breaks end-to-end VLAN transport.
- Standardize the native VLAN and verify mismatch detection and resolution.
- Harden trunks to a permanent static 802.1Q configuration so DTP no longer negotiates the trunk, using a non-default native VLAN.
- Harden access ports with portfast, bpduguard, and sticky port-security.
Troubleshooting focus
- The ACC1–DIST1 uplink never trunks during the DTP exploration:
show interfaces switchportreports dynamic auto on both ends. Auto+auto will not trunk — set one side to dynamic desirable. ping -c 3 10.10.10.20from CLIENT-A still fails after both links appear inshow interfaces trunk: confirm both trunks allow VLAN 10 on both ends. A one-sided allow-list is enough to block it.- Native VLAN mismatch messages appear: make both sides of that trunk use the same native VLAN, 999. Avoid native VLAN 1.
- One host is still down while the other works: confirm the correct access VLAN on its port, and that sticky port-security has learned only one MAC with no violations.
- The symptom does not match what you configured: re-check with
show interfaces trunk,show interfaces switchportandshow vlan briefon each switch.
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.