Re: Cisco 1832i - Not detected in CONtroller - DIscovery Response fail

hydarali972 · ‎06-04-2020

I have 1832i APs which are running on ios 8.5.161 and suddenly 30 of them have gone down with no discovery on controller, below errors are shown in CLI of the controller. Can anyone help?

▒ff▒昆▒▒x▒▒▒x▒▒▒▒[*05/29/2020 04:55:10.3246]

[*05/29/2020 04:55:10.3246] CAPWAP State: Discovery

[*05/29/2020 04:55:10.3246] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)

[*05/29/2020 04:55:10.3346] Discovery Response from 172.30.31.250

[*05/29/2020 04:55:10.3346] Discovery response from MWAR ''running version 0.0.0 .0 is rejected.

[*05/29/2020 04:55:10.3346] Failed to decode discovery response(status = 4).

[*05/29/2020 04:55:10.3346] CAPWAP SM handler: Failed to process message type 2 state 2.

[*05/29/2020 04:55:10.3346] Failed to handle capwap control message from control ler - status 4

[*05/29/2020 04:55:10.3346] Failed to process unencrypted capwap packet 0x29a300 0 from 172.30.31.250

[*05/29/2020 04:55:10.3346] Failed to send message to CAPWAP state machine, msgI d 0

[*05/29/2020 04:55:10.3346] Failed to send capwap message 0 to the state machine . Packet already freed.

[*05/29/2020 04:55:10.3346] IPv4 wtpProcessPacketFromSocket returned 4

[*05/29/2020 04:55:19.8317]

[*05/29/2020 04:55:19.8317] CAPWAP State: Discovery

[*05/29/2020 04:55:19.8317] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)

[*05/29/2020 04:55:19.8317] Discovery Response from 172.30.31.250

[*05/29/2020 04:55:19.8317] Discovery response from MWAR ''running version 0.0.0 .0 is rejected.

[*05/29/2020 04:55:19.8317] Failed to decode discovery response(status = 4).

[*05/29/2020 04:55:19.8317] CAPWAP SM handler: Failed to process message type 2 state 2.

[*05/29/2020 04:55:19.8317] Failed to handle capwap control message from control ler - status 4

[*05/29/2020 04:55:19.8317] Failed to process unencrypted capwap packet 0x299f00 0 from 172.30.31.250

[*05/29/2020 04:55:19.8317] Failed to send message to CAPWAP state machine, msgI d 0

[*05/29/2020 04:55:19.8317] Failed to send capwap message 0 to the state machine . Packet already freed.

[*05/29/2020 04:55:19.8317] IPv4 wtpProcessPacketFromSocket returned 4

[*05/29/2020 04:55:29.3387]

[*05/29/2020 04:55:29.3387] CAPWAP State: Discovery

[*05/29/2020 04:55:29.3387] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)

[*05/29/2020 04:55:29.3387] Discovery Response from 172.30.31.250

[*05/29/2020 04:55:29.3387] Discovery response from MWAR ''running version 0.0.0 .0 is rejected.

[*05/29/2020 04:55:29.3387] Failed to decode discovery response(status = 4).

[*05/29/2020 04:55:29.3387] CAPWAP SM handler: Failed to process message type 2 state 2.

[*05/29/2020 04:55:29.3387] Failed to handle capwap control message from control ler - status 4

[*05/29/2020 04:55:29.3387] Failed to process unencrypted capwap packet 0x29a100 0 from 172.30.31.250

[*05/29/2020 04:55:29.3387] Failed to send message to CAPWAP state machine, msgI d 0

[*05/29/2020 04:55:29.3387] Failed to send capwap message 0 to the state machine . Packet already freed.

[*05/29/2020 04:55:29.3387] IPv4 wtpProcessPacketFromSocket returned 4

[*05/29/2020 04:55:29.5886]

[*05/29/2020 04:55:29.5886] !!!!! {watchdogd} Process wcpd gone for 240s

[*05/29/2020 04:55:38.8357]

[*05/29/2020 04:55:38.8357] CAPWAP State: Discovery

[*05/29/2020 04:55:38.8357] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)

[*05/29/2020 04:55:38.8457] Discovery Response from 172.30.31.250

[*05/29/2020 04:55:38.8457] Discovery response from MWAR ''running version 0.0.0 .0 is rejected.

Leo Laohoo · ‎06-04-2020

Look at the time and date of the the logs. They are wrong.
Is NTP configured on the controller?

hydarali972 · ‎06-04-2020

yes, date and time were wrong and were corrected later in WLC. NTP IS Not configured.

Sandeep Choudhary · ‎06-04-2020

paste the output of these commands:

sh sysinfo from wlc

sh version from AP

Regards

Dont forget to rate helpful posts

hydarali972 · ‎06-04-2020

files are attached for the commands results. Pls note that the version of the WLC was 8.3.143 at the time of the AP mishap. 8.5.161 was upgraded on WLC at later stage.

Sandeep Choudhary · ‎06-04-2020

Cany ou paste the complete boot-up process logs from AP console.

Also paste the output of the acommand "Sh time" from wlc

AP still not joined after WLC software upgrade ?

Regards

Dont forget to rate helpful posts

hydarali972 · ‎06-04-2020

NO, the APs do not even show up in the WLC in the statistics, forget about being added to the working APs after the upgrade.

Leo Laohoo · ‎06-04-2020

@hydarali972 wrote:

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

Contact Cisco TAC and organize for an RMA. The AP is as good as dead.

孙先生 · ‎08-03-2022

请问后续怎么解决的，我现在遇到同样的问题

Cisco 1832i - Not detected in CONtroller - DIscovery Response failure