A network administrator is deploying a Cisco Lightweight Access Point (AP) connected to a Layer 2 switch port configured as an 802.1Q trunk. The AP is intended to exchange CAPWAP control messages with the Wireless LAN Controller (WLC) management interface over the native VLAN while carrying client traffic on tagged VLANs. Switch syslogs immediately report a 'Native VLAN mismatch' notification on the interface, and the AP fails to join the controller. Which condition explains why management access between the AP and the WLC is failing?
- Untagged CAPWAP discovery and management packets sent by the AP arrive on a mismatched native VLAN at the switch, placing management traffic into an unintended VLAN segment.Answer
- BEnabling PortFast on the switch port automatically revokes trunking capabilities, preventing tagged client traffic and untagged management traffic from reaching the WLC.
- CLightweight APs strictly reject untagged frames on trunk interfaces and mandate that management CAPWAP traffic carry an explicit 802.1Q VLAN tag for VLAN 1.
- DCDP detects the neighbor interface architecture mismatch and forces the switch port into an err-disabled state to prevent CAPWAP control plane corruption.
Answer
Untagged CAPWAP discovery and management packets sent by the AP arrive on a mismatched native VLAN at the switch, placing management traffic into an unintended VLAN segment.
Cisco Lightweight Access Points transmit their initial CAPWAP discovery and management control traffic as untagged frames by default. When connected to an 802.1Q trunk port, these untagged frames are mapped directly to the switch port's native VLAN. A native VLAN mismatch causes the switch to place the AP's management frames into an incorrect VLAN segment, preventing IP communication with the Wireless LAN Controller (WLC) management interface.
Step-by-Step Solution
Key Concept
AP and WLC Management Access over 802.1Q Native VLANs