AP3802 Trouble Join to WLC

[fdharmawan]

Hi Guys,

Recently one of my AP3802 on the deployment suddenly went boot loop. When I console the AP, the following message constantly showing up.

[*09/14/2019 03:32:04.1960] Discovery Response from "WLC_IP"
[*09/14/2019 03:32:04.1960] Discovery response from MWAR ''running version 0.0.0.0 is rejected.
[*09/14/2019 03:32:04.1960] Failed to decode discovery response(status = 4).
[*09/14/2019 03:32:04.1961] CAPWAP SM handler: Failed to process message type 2 state 2.
[*09/14/2019 03:32:04.1961] Failed to handle capwap control message from controller - status 4
[*09/14/2019 03:32:04.1961] Failed to process unencrypted capwap packet 0x2115000 from "WLC_IP"
[*09/14/2019 03:32:04.1961] Failed to send message to CAPWAP state machine, msgId 0
[*09/14/2019 03:32:04.1962] Failed to send capwap message 0 to the state machine. Packet already freed.
[*09/14/2019 03:32:04.1962] IPv4 wtpProcessPacketFromSocket returned 4

The WLC was running with 8.5.151.0. Any of you guys experiencing this? Thank you.

[Scott Fella]

Here is my opinion. If I troubleshoot an ap for over two days, I will rma that ap. There are a small percentage of AP’s that are troublesome. Without any support support it’s hard if you can’t download various images when you troubleshoot.

[fdharmawan]

Hi Scott,

Unfortunately I do not have a Cisco contract right now. Using your approach, I believe buying a new one is the fastest solution, right? And might be the only way

[Jurgens L]

With our instance, we had to replace the 2800 AP, but this AP was brand new out of the box. So if yours have been in production and only now give you issues, you may have a "different family" of that bug if I use the Cisco TAC language.

Like Scott mentioned it will be hard for you to resolve this problem if you can't download other software images such as the ones TAC recommend:
https://www.cisco.com/c/en/us/support/docs/wireless/wireless-lan-controller-software/200046-tac-recommended-aireos.html

[fdharmawan]

Hi Jurgens,

Well, I am using the 8.5.151.0, the recommended one. Maybe it's the AP, not the image. Not sure.