Access Point not joining to WLC

[raghu0001]

1832i-D-K9 AP not joining to WLC 2504

Getting AP CLI errors as below

AP Running Image version  8.5.171.0

WLC  version 8.5.171.0

[*04/06/2021 14:40:49.7089] CAPWAP State: Discovery

[*04/06/2021 14:40:49.7089] Discovery Request sent to 192.168.0.15, discovery type STATIC_CONFIG(1)

[*04/06/2021 14:40:49.7089] Discovery Request sent to 192.168.0.15, discovery type STATIC_CONFIG(1)

[*04/06/2021 14:40:49.7089] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)

[*04/06/2021 14:40:49.7089] Discovery Response from 192.168.0.15

[*04/06/2021 14:40:49.7089] Discovery response from MWAR ''running version 0.0.0.0 is rejected.

[*04/06/2021 14:40:49.7089] Failed to decode discovery response(status = 4).

[*04/06/2021 14:40:49.7089] CAPWAP SM handler: Failed to process message type 2 state 2.

[*04/06/2021 14:40:49.7089] Failed to handle capwap control message from controller - status 4

[*04/06/2021 14:40:49.7089] Failed to process unencrypted capwap packet 0xd9d000 from 192.168.0.15

[*04/06/2021 14:40:49.7089] Failed to send message to CAPWAP state machine, msgId 0

[*04/06/2021 14:40:49.7089] Failed to send capwap message 0 to the state machine. Packet already freed.

[*04/06/2021 14:40:49.7089] IPv4 wtpProcessPacketFromSocket returned 4

[*04/06/2021 14:40:49.7089] Discovery Response from 192.168.0.15

[*04/06/2021 14:40:49.7089] Discovery response from MWAR ''running version 0.0.0.0 is rejected.

[*04/06/2021 14:40:49.7089] Failed to decode discovery response(status = 4).

[*04/06/2021 14:40:49.7089] CAPWAP SM handler: Failed to process message type 2 state 2.

[*04/06/2021 14:40:49.7089] Failed to handle capwap control message from controller - status 4

[*04/06/2021 14:40:49.7089] Failed to process unencrypted capwap packet 0xd99000 from 192.168.0.15

[*04/06/2021 14:40:49.7089] Failed to send message to CAPWAP state machine, msgId 0

[*04/06/2021 14:40:49.7089] Failed to send capwap message 0 to the state machine. Packet already freed.

[*04/06/2021 14:40:49.7089] IPv4 wtpProcessPacketFromSocket returned 4

[*04/06/2021 14:40:49.7089] Discovery Response from 192.168.0.15

[*04/06/2021 14:40:49.7089] Discovery response from MWAR ''running version 0.0.0.0 is rejected.

[*04/06/2021 14:40:49.7089] Failed to decode discovery response(status = 4).

[*04/06/2021 14:40:49.7089] CAPWAP SM handler: Failed to process message type 2 state 2.

[*04/06/2021 14:40:49.7089] Failed to handle capwap control message from controller - status 4

[*04/06/2021 14:40:49.7089] Failed to process unencrypted capwap packet 0xd97000 from 192.168.0.15

[*04/06/2021 14:40:49.7089] Failed to send message to CAPWAP state machine, msgId 0

[*04/06/2021 14:40:49.7089] Failed to send capwap message 0 to the state machine. Packet already freed.

[*04/06/2021 14:40:49.7089] IPv4 wtpProcessPacketFromSocket returned 4

[Sandeep Choudhary]

can you check if the date & time on controller is correct or not ?

[raghu0001]

ON CONTROLLER TIME AND DATE ARE CORRECT  BUT, IN AP TIME AND DATE WRONG 

[Leo Laohoo]

---

@raghu0001 wrote:

[*01/01/1970 00:00:30.5606] Current value of FACTORY_RESET=0
[*05/12/2017 23:59:59.0099] Last reload time: Apr 6 14:39:10 2021
[*04/06/2021 14:39:10.0000] Setting system time Tue Apr  6 14:39:10 UTC 2021

---

Look at the timestamps taken from the AP.  The time and date changed three times. 

Configure NTP first.

If the AP still does not join the controller, factory-reset the AP using the command "capwap ap erase all". 

From the controller, post the complete output to the following command "sh ap join detail <AP MAC ADDRESS>".

[raghu0001]

NTP SERVER CONFIGURED

AP WAS FACTORY RESETTED BY COMMAND capwap ap erase all

from controller "show time" output and "sh ap join detail <AP MAC ADDRESS>". output was attached

[Leo Laohoo]

"no join info"????
Can the AP ping 192.168.0.15 successfully?

[raghu0001]

Ap is pinging to controller and from controller to AP is also pinging

[Rich R]

And if @Leo Laohoo suggestions don't help then see my post in https://community.cisco.com/t5/wireless/ap-showing-under-direct-aps/td-p/4196011

You'll need to capture the full logs from power on (well before capwap join starts) to catch the telltale logs of the hardware failure.

Just looked at your logs and don't see that there but you do have "DOT11_DRV[1]: wcp/RadDrv1 :: Dot11BaseDriver get_vap_if_index ioctl SIOCGIFINDEX failed for apr1v0 error No such device" so I wonder if it might be related.

I saw that on 8.5MR6 and yours is 8.5MR7 so they might have changed the logs you see when you hit that problem.

We are currently seeing around 10 of these failures each month on 1832 APs (orders of magnitude higher than other models) although Cisco insist that it's still within expected MTBF.

Either way TAC will be able to confirm if Leo's suggestions don't help.

[raghu0001]

how to check if the device has bugs or not. Any tool from cisco to know the status of AP if it has bug or not. how to know the AP is faulty any tool ???