A network technician receives a report that hosts on VLAN 10 attached to Switch-1 are unexpectedly receiving untagged traffic from VLAN 20 attached to Switch-2 across a point-to-point trunk link. Console logs on Switch-1 frequently display `%CDP-4-NATIVE_VLAN_MISMATCH` notifications for interface GigabitEthernet 0/1. Which of the following is the root cause of this behavior?
- A mismatch in the configured 802.1Q native VLAN between the two interconnecting switch interfaces.Answer
- BA duplex mismatch on the trunk link causing frames to leak across collision domains.
- CThe lack of an active Layer 3 router to maintain broadcast domain boundaries across the switch ports.
- DAn incorrect Spanning Tree Protocol priority configuration causing the trunk link to operate in a backup blocking state.
Answer
A mismatch in the configured 802.1Q native VLAN between the two interconnecting switch interfaces.
On an 802.1Q trunk, traffic belonging to the designated native VLAN is transmitted without an 802.1Q header tag. If Switch-1 has its native VLAN set to 10 while Switch-2 has its native VLAN set to 20, untagged frames sent from VLAN 20 on Switch-2 will be received by Switch-1 and placed into VLAN 10. This native VLAN mismatch causes cross-VLAN leakage and triggers CDP native VLAN mismatch syslog errors.
Step-by-Step Solution
Key Concept
802.1Q Native VLAN Operation and Mismatch Troubleshooting