Re: Cisco AIR-AP2802I-E-K9 Failing to Join Controller - Page 2

calluuml · ‎06-10-2019

Hi,

We are having an issue where our AP will not join any of our Wireless LAN controllers.

Console output shows;

[*01/18/2019 15:05:13.3086] CAPWAP State: Discovery
[*01/18/2019 15:05:13.3088] Got WLC address 172.16.1.5 from DHCP.
[*01/18/2019 15:05:13.3088] IP DNS query for CISCO-CAPWAP-CONTROLLER.ourdomain.com
[*01/18/2019 15:05:13.3124] Discovery Request sent to 172.16.1.5, discovery type DHCP(2)
[*01/18/2019 15:05:13.3126] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*01/18/2019 15:05:13.3137] Discovery Response from 172.16.1.3
[*01/18/2019 15:05:13.3137] Discovery response from MWAR ''running version 0.0.0.0 is rejected.
[*01/18/2019 15:05:13.3137] Failed to decode discovery response(status = 4).
[*01/18/2019 15:05:13.3137] CAPWAP SM handler: Failed to process message type 2 state 2.
[*01/18/2019 15:05:13.3138] Failed to handle capwap control message from controller - status 4
[*01/18/2019 15:05:13.3138] Failed to process unencrypted capwap packet 0x26fc000 from 172.16.1.3
[*01/18/2019 15:05:13.3138] Failed to send message to CAPWAP state machine, msgId 0
[*01/18/2019 15:05:13.3138] Failed to send capwap message 0 to the state machine. Packet already freed.
[*01/18/2019 15:05:13.3138] IPv4 wtpProcessPacketFromSocket returned 4
[*01/18/2019 15:05:13.3139] Discovery Response from 172.16.1.4
[*01/18/2019 15:05:13.3139] Discovery response from MWAR ''running version 0.0.0.0 is rejected.
[*01/18/2019 15:05:13.3139] Failed to decode discovery response(status = 4).
[*01/18/2019 15:05:13.3139] CAPWAP SM handler: Failed to process message type 2 state 2.
[*01/18/2019 15:05:13.3139] Failed to handle capwap control message from controller - status 4
[*01/18/2019 15:05:13.3139] Failed to process unencrypted capwap packet 0x26f6000 from 172.16.1.4
[*01/18/2019 15:05:13.3139] Failed to send message to CAPWAP state machine, msgId 0
[*01/18/2019 15:05:13.3140] Failed to send capwap message 0 to the state machine. Packet already freed.
[*01/18/2019 15:05:13.3140] IPv4 wtpProcessPacketFromSocket returned 4

From the log it looks like a version mismatch - https://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html

The compatibility matrix shows that version 8.2.110.0 is supported and the AP is running 8.5.135.0

cisco AIR-AP2802I-E-K9 ARMv7 Processor rev 1 (v7l) with 1028584/672912K bytes of memory.
Processor board ID XXX
AP Running Image : 8.5.135.0
Primary Boot Image : 8.5.135.0
Backup Boot Image : 8.3.143.0
2 Gigabit Ethernet interfaces
1 802.11 Radios
Radio Driver version : 9.0.5.5-W8964
Radio FW version : 9.1.8.1
NSS FW version : 2.4.24

Could somebody point me in the right direction?

Thanks

cameronmyers · ‎07-13-2020

Mine died again. After my fix that got it running it started being bad again. Same issue.

Weird that it is just this AP and not any others. I guess it will have to go back to Cisco. No one seems to have an answer.

patoberli · ‎07-14-2020

And you are still running 8.5.135.0? If yes, first try to upgrade to the latest 8.5 release. If that doesn't help, the unit might be broken (if it only happens to one) and needs to be replaced.

cameronmyers · ‎07-14-2020

Yep, after clearing the CAPWAP config again it completely stopped responding. It gets DHCP and shows up in CDP neighbors but is non-responsive to the cli. Can't get better info until it returns from the site. Starting an RMA.