Ar 1832 Problem with connecting to Wlc

[atdhetabaku1900]

Hi we got like 110 Cisco Ap on a 5520. every now and then we got the same problem with the 1832 Ap . and this is the error

CAPWAP State: Discovery
[*06/08/2021 13:28:26.1191] Discovery Request sent to 10.1.253.2, discovery type STATIC_CONFIG(1)
[*06/08/2021 13:28:26.1191] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*06/08/2021 13:28:26.1191] Discovery Response from 10.1.253.2
[*06/08/2021 13:28:26.1191] Discovery response from MWAR ''running version 0.0.0.0 is rejected.
[*06/08/2021 13:28:26.1191] Failed to decode discovery response(status = 4).
[*06/08/2021 13:28:26.1191] CAPWAP SM handler: Failed to process message type 2 state 2.
[*06/08/2021 13:28:26.1191] Failed to handle capwap control message from controller - status 4
[*06/08/2021 13:28:26.1191] Failed to process unencrypted capwap packet 0xfdd000 from 10.1.253.2
[*06/08/2021 13:28:26.1191] Failed to send message to CAPWAP state machine, msgId 0
[*06/08/2021 13:28:26.1191] Failed to send capwap message 0 to the state machine. Packet already freed.
[*06/08/2021 13:28:26.1191] IPv4 wtpProcessPacketFromSocket returned 4
[*06/08/2021 13:28:26.1191] Discovery Response from 10.1.253.2
[*06/08/2021 13:28:26.1191] Discovery response from MWAR ''running version 0.0.0.0 is rejected.
[*06/08/2021 13:28:26.1191] Failed to decode discovery response(status = 4).
[*06/08/2021 13:28:26.1191] CAPWAP SM handler: Failed to process message type 2 state 2.
[*06/08/2021 13:28:26.1191] Failed to handle capwap control message from controller - status 4
[*06/08/2021 13:28:26.1191] Failed to process unencrypted capwap packet 0xfe0000 from 10.1.253.2
[*06/08/2021 13:28:26.1191] Failed to send message to CAPWAP state machine, msgId 0
[*06/08/2021 13:28:26.1191] Failed to send capwap message 0 to the state machine. Packet already freed.
[*06/08/2021 13:28:26.1191] IPv4 wtpProcessPacketFromSocket returned 4

Is there any solution to it?

[Scott Fella]

If this happens only to the 1832's, then I personally would open a TAC case.  Have you searched the bug toolkit and or used the Cisco debug analyzer to help you determine what the problem might be?  That would be where I would start.

[atdhetabaku1900]

yes i did try debug and bug search but no luck, i will try and open a TAC case, but this is not the 1st time that happends , every 1 year we have to change like 2 ap for the same exact reason!

[marce1000]

      - What software version is the controller running ?

 M.

[atdhetabaku1900]

8.5.140.0 

[Rich R]

8.5.140 is not the latest release - see https://www.cisco.com/c/en/us/support/docs/wireless/wireless-lan-controller-software/200046-tac-recommended-aireos.html#anc10

[marce1000]

                                            - Upgrade to : 

     https://software.cisco.com/download/home/286284738/type/280926587/release/8.10.151.0

                              Check if the problem is resolved afterwards.

 M.

[Rich R]

Search the community for 1832 - you'll see I've mentioned this a number of times.  There is a known hardware problem with the 1832's and the failure rate will increase rapidly as they get older.  You're lucky it's only 2 a year so far...

It goes without saying (but reminding you anyway) to make sure you're on the latest release of software to pick up any bug fixes.  Factory reset the AP to make sure it's not a simple config corruption problem.  If that doesn't fix it then the AP has likely failed and needs to be RMA'd.

[atdhetabaku1900]

I did all of this and nothing didnt help.