AP doesn't join the controller after I try to reset it.

[frankfurttt]

Before I used it, I don't know what the previous person did, so I did a reset. After I plugged the console into the AP, then the commands came up:

[*05/09/2022] Waiting for uplink IPv4 configuration
[*05/09/2022] Waiting for uplink IPv4 configuration
[*05/09/2022] Waiting for uplink IPv4 configuration
[*05/09/2022] Resetting wired0 and restart DHCP client
[*05/09/2022] ADDRCONF(NETDEV_UP): wired0: link is not ready
[*05/09/2022] ADDRCONF(NETDEV_CHANGE): wired0: link becomes ready
[*05/09/2022] wired0: 1000 Mbps Full Duplex

After these commands keep coming up Then I thought the AP reconnected itself.

So, I did some research to fix it. until I can find a way to join the controller. I thought my problems would be over but not at all.

I thought my problems would be over but not at all. after that I think I made it connect to the controller, but I think I still can't because I see commands.

[*05/09/2022 03:18:22.1709] AP IPv4 Address updated from 0.0.0.0 to 192.168.99.111
[*05/09/2022 03:18:22.1909] send CAPWAP ctrl msg to the socket: Socket operation on non-socket
[*05/09/2022 03:18:22.1909] send_msg_to_capwap_sm: Capwap SM restart message send failed for message: 9
[*05/09/2022 03:18:22.1909] dtls_init: Use MIC certificate
[*05/09/2022 03:18:22.1909]
[*05/09/2022 03:18:22.1909] CAPWAP State: Init
[*05/09/2022 03:18:22.2009]
[*05/09/2022 03:18:22.2009] Config not found, PNP is required, Starting PNP
[*05/09/2022 03:18:22.2009]
[*05/09/2022 03:18:28.9188] PNP:Server not reachable, Start CAPWAP Discovery
[*05/09/2022 03:18:28.9188]
[*05/09/2022 03:18:28.9188] CAPWAP State: Discovery
[*05/09/2022 03:18:28.9188] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*05/09/2022 03:18:28.9188]
[*05/09/2022 03:18:28.9188] CAPWAP State: Discovery
[*05/09/2022 03:18:28.9288] Discovery Response from 192.168.99.250
[*05/09/2022 03:18:28.9288] Discovery response from MWAR ''running version 0.0.0.0 is rejected.
[*05/09/2022 03:18:28.9288] Failed to decode discovery response(status = 4).
[*05/09/2022 03:18:28.9288] CAPWAP SM handler: Failed to process message type 2 state 2.
[*05/09/2022 03:18:28.9288] Failed to handle capwap control message from controller - status 4
[*05/09/2022 03:18:28.9288] Failed to process unencrypted capwap packet 0x15e2000 from 192.168.99.250
[*05/09/2022 03:18:28.9288] Failed to send message to CAPWAP state machine, msgId 0
[*05/09/2022 03:18:28.9288] Failed to send capwap message 0 to the state machine. Packet already free d.
[*05/09/2022 03:18:28.9288] IPv4 wtpProcessPacketFromSocket returned 4
[*05/09/2022 03:18:38.4958]
[*05/09/2022 03:18:38.4958] CAPWAP State: Discovery
[*05/09/2022 03:18:38.4958] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*05/09/2022 03:18:38.4958] Discovery Response from 192.168.99.250
[*05/09/2022 03:18:38.4958] Discovery response from MWAR ''running version 0.0.0.0 is rejected.
[*05/09/2022 03:18:38.4958] Failed to decode discovery response(status = 4).
[*05/09/2022 03:18:38.4958] CAPWAP SM handler: Failed to process message type 2 state 2.
[*05/09/2022 03:18:38.4958] Failed to handle capwap control message from controller - status 4
[*05/09/2022 03:18:38.4958] Failed to process unencrypted capwap packet 0x15e4000 from 192.168.99.250
[*05/09/2022 03:18:38.4958] Failed to send message to CAPWAP state machine, msgId 0
[*05/09/2022 03:18:38.4958] Failed to send capwap message 0 to the state machine. Packet already free d.
[*05/09/2022 03:18:38.4958] IPv4 wtpProcessPacketFromSocket returned 4
[*05/09/2022 03:18:48.0029]
[*05/09/2022 03:18:48.0029] CAPWAP State: Discovery
[*05/09/2022 03:18:48.0029] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*05/09/2022 03:18:48.0029] Discovery Response from 192.168.99.250
[*05/09/2022 03:18:48.0029] Discovery response from MWAR ''running version 0.0.0.0 is rejected.
[*05/09/2022 03:18:48.0029] Failed to decode discovery response(status = 4).
[*05/09/2022 03:18:48.0029] CAPWAP SM handler: Failed to process message type 2 state 2.
[*05/09/2022 03:18:48.0029] Failed to handle capwap control message from controller - status 4
[*05/09/2022 03:18:48.0029] Failed to process unencrypted capwap packet 0x15e6000 from 192.168.99.250
[*05/09/2022 03:18:48.0029] Failed to send message to CAPWAP state machine, msgId 0
[*05/09/2022 03:18:48.0029] Failed to send capwap message 0 to the state machine. Packet already free d.
[*05/09/2022 03:18:48.0029] IPv4 wtpProcessPacketFromSocket returned 4
[*05/09/2022 03:18:57.4999]
[*05/09/2022 03:18:57.4999] CAPWAP State: Discovery
[*05/09/2022 03:18:57.4999] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*05/09/2022 03:18:57.4999] Discovery Response from 192.168.99.250
[*05/09/2022 03:18:57.4999] Discovery response from MWAR ''running version 0.0.0.0 is rejected.
[*05/09/2022 03:18:57.4999] Failed to decode discovery response(status = 4).
[*05/09/2022 03:18:57.4999] CAPWAP SM handler: Failed to process message type 2 state 2.
[*05/09/2022 03:18:57.4999] Failed to handle capwap control message from controller - status 4
[*05/09/2022 03:18:57.4999] Failed to process unencrypted capwap packet 0x15e2000 from 192.168.99.250
[*05/09/2022 03:18:57.4999] Failed to send message to CAPWAP state machine, msgId 0
[*05/09/2022 03:18:57.4999] Failed to send capwap message 0 to the state machine. Packet already free d.

It's a lot but it's all the same. Until finally I think the AP tried to reconnect. But it went on and on like this.

I try to leave it with all day researching. I'm still not sure about this solution. Do you guys have any advice? Please help enlighten me. I'm newbie and I don't have enough knowledge to fix it yet.

If you guys need any other information, please tell me.

[marce1000]

  - Please include :  1) access point model  , 2) Controller model , 3) Controller software version , 

 M.

[frankfurttt]

Thank you for your reply.

1. Access point model: AIR-AP1852i-s-k9 (IOS Version 8.5.161.0)

2. Controller model: Cisco 2500 Series Model 2504

3. Controller software version: 8.5.161.0

I hope this information matches what you need.

[marce1000]

 - FYI : https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvh85082  , also have a look at this thread for other related topics ,https://community.cisco.com/t5/wireless/ap1562i-t-cannot-join-5508-8-5-110-ap-log-mwar-running-version-0/td-p/3306814   , advising to use https://software.cisco.com/download/home/283848165/type/280926587/release/8.5.171.0 on the controller ,

M;

[frankfurttt]

Thank you for your help, M. 

I tried to learn about the information you've responded to. But I still have another's APs with the same version and the same model that can still connect to the controller and still active. Can you explain more about the information to bring?

I'm sorry to ask more, because I'm a beginner for this.

[marce1000]

  - You may try to factory reset the access point too and try again,

 M:

[Rich R]

I would advise to update software to 8.5.182.7
@marce1000 it's very risky to recommend anything earlier than that now because they could be affected by the field notice (below) depending on what APs are in use.  This is also the TAC recommended release now (link below) so we should only recommend that 8.5 release now - nothing earlier.   The software download page will probably never be updated because (1.) 8.5 is End of Life and (2.) 8.5.182.7 is a hidden release only linked from TAC recommended and FN pages.  So the golden * for 8.5.171.0 suggested release is just misleading and wrong.

If still no progress after software update and factory default reset of AP then you might have a faulty AP which needs RMA.