Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

request received on wrong vlan


We have two WLC's 5508. Following are its interfaces & details:

mgmt on wlc1 & .252 on wlc2

accessp on wlc1 & .252 on wlc2

there is no AP manager interface seen on both wlc's nor configured.

both wlc1 & wlc2 are connected each to two switch ports, configured as normal trunk link each.

LAG is enabled on both WLC's.

I get the following error message when a root access point is connected to the network.

c6:f4:f2:60:4c:00 Discovery Request from

c6:f4:f2:60:4c:00 Discovery request: Total msgEleLen = 96

c6:f4:f2:60:4c:00 Discovery Type = Unknown

c6:f4:f2:60:4c:00 Discovery request: Vendor payload type = 5, length = 19

c6:f4:f2:60:4c:00 Discovery Request received on wrong VLAN '6' on interface '13', mgmt VLAN = '0', AP Manager VLAN = '0', dropping the packet

c6:f4:f2:60:4c:00 State machine handler: Failed to process  msg type = 1 state = 0 from

c6:f4:f2:60:4c:00 Failed to parse CAPWAP packet from

Strange is both mgmt vlan & AP manager vlan shows as zero.

Please help, the root access point doesn't register.

Thanks in advance.


request received on wrong vlan

Your WLC has an interface in VLAN 6, and the AP is seeing it via an L2 Broadcast.

You can have the AP on teh management VLAN, but it shouldn't be on any dynamic interface.  If you can, move the AP to a VLAN that the WLC is not configured to use, or if VLAN 6 is just for the AP, remove it from the WLC


Please remember to rate useful posts, and mark questions as answered

HTH, Steve ------------------------------------------------------------------------------------------------ Please remember to rate useful posts, and mark questions as answered
Cisco Employee

request received on wrong vlan


- Yes, as Stephen mentioned the error you see is because you have vlan 6 configured as a dynamic interface on the controller and the discovery requests from the AP are coming in as L2 broadcast on the controller vlan 6.

- To get the APs registered, I would suggest removing this vlan interface from the controller.

Next, since the controller mgmt and the AP are on different vlans, what is the discovery mechanism you have in place-

dhcp option 43


ip helper-address??

You need one of the above configured pointing to the controller mgmt interface for the AP to talk to the controller.

You can read more on these mechanisms here-