An administrator notices CDP log messages indicating a native VLAN mismatch on an 802.1Q trunk link between two switches. Switch-1 is configured with native VLAN 99 on interface GigabitEthernet0/1, while Switch-2 uses the default native VLAN 1 on interface GigabitEthernet0/1. If a host in VLAN 99 on Switch-1 transmits untagged frames across the trunk link, how will Switch-2 process this traffic?
- Switch-2 receives the untagged frames and forwards them into VLAN 1, leading to cross-VLAN traffic leakage.Answer
- BSwitch-2 automatically drops the untagged frames because 802.1Q encapsulation requires all frames on a trunk link to carry a 4-byte VLAN tag header.
- CCDP detects the mismatch and immediately places interface GigabitEthernet0/1 on both switches into the err-disabled operational state.
- DSpanning Tree Protocol automatically enables PortFast on interface GigabitEthernet0/1 to bypass trunk tag processing for mismatched traffic.
Answer
Switch-2 receives the untagged frames and forwards them into VLAN 1, leading to cross-VLAN traffic leakage.
Under IEEE 802.1Q trunking rules, frames belonging to the native VLAN are sent untagged across the link. When a receiving switch receives untagged frames, it automatically maps them to its own configured native VLAN. Consequently, traffic originating from VLAN 99 on Switch-1 will be placed into VLAN 1 on Switch-2, resulting in unintended cross-VLAN traffic leakage.
Step-by-Step Solution
Key Concept
802.1Q Native VLAN Tagging Mechanics and Traffic Leakage