CAPWAP - Failed to decode discovery response

[Heitkamp]

Hi Guys!

I did a WLC (WLC 2504) Update to version 8.3.150.0 and after the update 2 of our 30 access points (AIR-AP1852I-E-K9) cannot connect to the WLC. I connected via console to the access points and get following error message:

[*05/03/2020 15:39:37.4246] Discovery Response from 192.168.219.130
[*05/03/2020 15:39:37.4246]
[*05/03/2020 15:39:37.4246] This AP model is supported by controller version newer than 7.0.0.0!
[*05/03/2020 15:39:37.4246]
[*05/03/2020 15:39:37.4246] Discovery response from MWAR ''running version 0.0.0.0 is rejected.
[*05/03/2020 15:39:37.4246] Failed to decode discovery response.
[*05/03/2020 15:39:37.4246] CAPWAP SM handler: Failed to process message type 2 state 2.
[*05/03/2020 15:39:37.4246] Failed to handle capwap control message from controller - status 4
[*05/03/2020 15:39:37.4246] Failed to process unencrypted capwap packet 0x1803000 from 192.168.219.130
[*05/03/2020 15:39:37.4246] Failed to send capwap message 0 to the state machine. Packet already freed.
[*05/03/2020 15:39:37.4246] IPv4 wtpProcessPacketFromSocket returned 4
[*05/03/2020 15:39:37.4246] Discovery Response from 192.168.219.130
[*05/03/2020 15:39:37.4246]
[*05/03/2020 15:39:37.4246] This AP model is supported by controller version newer than 7.0.0.0!
[*05/03/2020 15:39:37.4246]
[*05/03/2020 15:39:37.4246] Discovery response from MWAR ''running version 0.0.0.0 is rejected.
[*05/03/2020 15:39:37.4246] Failed to decode discovery response.
[*05/03/2020 15:39:37.4246] CAPWAP SM handler: Failed to process message type 2 state 2.
[*05/03/2020 15:39:37.4246] Failed to handle capwap control message from controller - status 4
[*05/03/2020 15:39:37.4246] Failed to process unencrypted capwap packet 0x1801000 from 192.168.219.130
[*05/03/2020 15:39:37.4246] Failed to send capwap message 0 to the state machine. Packet already freed.
[*05/03/2020 15:39:37.4246] IPv4 wtpProcessPacketFromSocket returned 4

I manually updated the version of one access point to 8.3.150.0 because I already found this bug page .

sh version
cisco AIR-AP1852I-E-K9 ARMv7 Processor rev 0 (v7l) with 967420/800844K bytes of memory.
Processor board ID XXXXXXXXXX
AP Running Image : 8.3.150.0
Primary Boot Image : 8.3.150.0
Backup Boot Image : 8.3.143.0

What do I need to do?

Kind regards

Heitkamp

[razeev rohilla]

same issue i have faced, is their any solution of it.

[Gaurav Kansal]

Hello

Discovery response from MWAR ''running version 0.0.0.0 is rejected.

This error means its a hardware issue.Please open a TAC and replace the AP with new one.

Good Luck

[razeev rohilla]

Hi, Heitkamp,

can you please guide me, how and which IOS image is upgrade in AIR-AP1852I-D-K9 access point. manufacturing date is 11/2016.

[Rich R]

@razeev rohilla the links in my signature below provide all the information you need.  Simply stating the AP model is not enough info to provide any answer - the WLC model and other AP models are the minimum required to determine what software version you could use.

Note that the original bug mentioned (CSCvu20765) is fixed via CSCvu25264 which is only fixed in 8.10 and later code.  So if you are using older APs or older WLC then there is no fix available for that bug for you.

You should also make sure you do a factory default reset on your AP - that can cure many join issues.  If your AP was working before and then stopped working you might have a hardware failure (common on 1830 and 1850 APs) in which case you should RMA the AP.