VLAN Trunk Troubleshooting Without Guessing
A focused checklist for missing VLANs, native VLAN mismatches, tagging problems and trunk path failures.
Prove the VLAN exists end to end
Follow the intended Layer 2 path from source to destination. Confirm the VLAN exists, is active, and is allowed on every trunk that should carry it. One missing allowed-VLAN entry can break a service while every other VLAN on the link remains healthy.
Check operational state as well as configuration. Pruning, spanning-tree state, or bundle problems can prevent forwarding even when the VLAN is configured.
Check tagging expectations at every boundary
Access versus trunk mode, native VLAN behavior, service tags, QinQ, and provider handoffs depend on both sides agreeing about what is tagged. A frame arriving untagged where a tag is expected can land in the wrong broadcast domain or be discarded.
At carrier or data-center handoffs, document outer and inner tags explicitly rather than relying on “VLAN 200” as the full description.
Use MAC learning to follow the frame
MAC tables can show whether the source is learned on the expected access port and whether the destination appears across the correct trunk. Where learning stops, you have a useful fault boundary.
Also verify spanning-tree state and port-channel membership for that VLAN. After the repair, confirm the actual service, MAC learning, and VLAN counters across the path.