Cisco Aironet 1815i - Discovery response from MWAR ''running version 0.0.0.0 is rejected

[BrendonFranca]

Hello, guys. 

I'm having a problem registering an AP 1815i on the controller. 

It already had a registry but after a reboot of the controller, when it tries to register, the following errors are listed:

[*04/23/2019 08:20:48.4499] CAPWAP State: Discovery

[*04/23/2019 08:20:48.4499] Discovery Request sent to 192.168.8.8, discovery type STATIC_CONFIG(1)

[*04/23/2019 08:20:48.4499] Discovery Request sent to 192.168.8.8, discovery type STATIC_CONFIG(1)

[*04/23/2019 08:20:48.4499] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)

[*04/23/2019 08:20:48.4499] Discovery Response from 192.168.8.8

[*04/23/2019 08:20:48.4499] Discovery response from MWAR ''running version 0.0.0.0 is rejected.

[*04/23/2019 08:20:48.4499] Failed to decode discovery response(status = 4).

[*04/23/2019 08:20:48.4499] CAPWAP SM handler: Failed to process message type 2 state 2.

[*04/23/2019 08:20:48.4499] Failed to handle capwap control message from controller - status 4

[*04/23/2019 08:20:48.4499] Failed to process unencrypted capwap packet 0x1900000 from 192.168.8.8

[*04/23/2019 08:20:48.4499] Failed to send message to CAPWAP state machine, msgId 0

[*04/23/2019 08:20:48.4499] Failed to send capwap message 0 to the state machine. Packet already freed.

[*04/23/2019 08:20:48.4499] IPv4 wtpProcessPacketFromSocket returned 4

[*04/23/2019 08:20:48.4499] Discovery Response from 192.168.8.8

I have already tried to reset the factory, however, without success.

Would anyone have any idea to do to solve this case ?

I've seen some posts about the error "Discovery response from MWAR ''running version 0.0.0.0 is rejected", but all the directions were to get in touch with this TAC. 

Thanks for your help.

[Leo Laohoo]

Post the complete output to the following commands:
1. WLC: sh sysinfo;
2. WLC: sh time;
3. AP: sh version;
4. AP: sh capwap ap client rcb

[BrendonFranca]

Hello Leo. 

Thanks for your attention. 

Attached is the files with the requested information. 

One thing I forgot to mention ins that on the same controller, more APs like this one are registered witch the same firmware. 

Thanks for your help. 

[Leo Laohoo]

Product Version.................................. 8.5.131.0

(Sorry for the late response, I was sick.)

Is it possible to upgrade the firmware of the WLC to, say, 8.5.151.0?

[BrendonFranca]

Hi, Leo.
Do not worry.
I estimate improvements for your health.

Regarding the Controller Firmware, we can rule out this possibility.
I tried to register the AP in another 1815i converted to Mobility Express and the same thing happens.
I registered another AP 1815i in the same control console as an interim measure and there were no problems.
This proves that the problem is in the AP, correct?

Thank you in advance for your help and attention.

[hanchenglie]

hello,Do you have a solution to this problem？

[SudhakarGanapareddy26654]

It seems like BUG

Cisco Bug: CSCvf71074 - T domain AP1562 Failed to decode discovery response

Last Modified

Jul 16, 2020

Products (1)

• Cisco Aironet 1850 Series Access Points

Known Affected Releases

8.3(122.0) 8.5(103.0)

Description (partial)

Symptom:
Capwap discovery state fails causing ap join failure.

AP console log:

Discovery response from MWAR ''running version 0.0.0.0 is rejected.
Failed to decode discovery response.
CAPWAP SM handler: Failed to process message type 2 state 2.
Failed to handle capwap control message from controller - status 4

Conditions:
1. AP starts and attempts to join the controller.
2. AP is T domain (Taiwan)

Related Community Discussions

1852 failed to join WLC

Hi all, I have few 1852 AP that suddenly failed to work with WLC2504 - 8.5.140.0   I tried to upgrade the AP to a different version and reinstall the 8.5.140 but nothing, same failure:   [*11/30/2019 18:02:13.2147] CAPWAP State: DTLS Teardown [*11/30/2019 18:02:17.9732] [*11/30/2019 18:02:17.9732] CAPWAP State: Discovery [*11/30/2019 18:02:17.9732] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0) [*11/30/2019 18:02:17.9732] Discovery Response from 10.***.***.1 [*11/30/2019 18:02:17.9732] ...

Latest activity: Feb 26, 2020

View Bug Details in Bug Search Tool  

Why Is Login Required?

Bug Details Include

• Full Description (including symptoms, conditions and workarounds)
• Status
• Severity
• Known Fixed Releases
• Related Community Discussions
• Number of Related Support Cases

Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.

Learn More About Cisco Service Contracts

[Giorgos_Mama]

Hi Folks,

Any news regarding the above? I face the same today. One out of 65 APs went down suddenly. From the AP console I see the below.

Running 8.5.161 with 1852i APs

Discovery Response from 10.24.10.20
Discovery response from MWAR ''running version 0.0.0.0 is rejected.
Failed to decode discovery response(status = 4).
CAPWAP SM handler: Failed to process message type 2 state 2.
Failed to handle capwap control message from controller - status 4
Failed to process unencrypted capwap packet 0x1b33000 from 10.24.10.20

Failed to send message to CAPWAP state machine, msgId 0
Failed to send capwap message 0 to the state machine. Packet already freed.
IPv4 wtpProcessPacketFromSocket returned 4

[Giorgos_Mama]

As reply to my previous commend, I upgraded the WLC to 8.5.171 (no result), I also upgraded manually the ap with the command archive download-sw /reload tftp://192.168.101.121/ap1g4-k9w8… but again nothing changed. I opened a TAC case and they RMA it.

[David Ritter]

It would appear that the only solution to this issue is to RMA the device(s)

I have had 1810w's, 1832i's, and 1852i's all experience the issue.  So far my 2802i's and 3802i's are well.

[DavidZhang47328]

What happened to Cisco? I have 12 unit of 1562i AP, but recently, 3 of them were broken...