08-03-2023 05:44 AM
Hello,
I am looking for solution how to solve problem with Cisco AP - AIR-AP1852I-E-K9, which for some reason disconnect from the WLC and cannot register again.
I tried to reset it on factory - but still.
Version of WLC
AIR-CT5520-K9 |
8.2.166.0 |
Here is a part of Console output
[*03/30/2023 05:55:50.9172] Discovery response from MWAR ''running version 0.0.0.0 is rejected.
[*03/30/2023 05:55:50.9172] Failed to decode discovery response.
[*03/30/2023 05:55:50.9172] CAPWAP SM handler: Failed to process message type 2 state 2.
[*03/30/2023 05:55:50.9172] Failed to handle capwap control message from controller - status 4
[*03/30/2023 05:55:50.9172] Failed to process unencrypted capwap packet from 10.1.2.251
[*03/30/2023 05:55:50.9172] Failed to send capwap message 0 to the state machine. Packet already freed.
[*03/30/2023 05:55:50.9172] wtpProcessPacketFromSocket returned 4
[*03/30/2023 05:56:00.4142] CAPWAP State: Discovery
[*03/30/2023 05:56:00.4142] Discovery Request sent to 10.1.2.251, discovery type STATIC_CONFIG(1)
[*03/30/2023 05:56:00.4142] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*03/30/2023 05:56:00.4142] Discovery Response from 10.1.2.251
[*03/30/2023 05:56:00.4142]
[*03/30/2023 05:56:00.4142] This AP model is supported by controller version newer than 7.0.0.0!
[*03/30/2023 05:56:00.4142]
[*03/30/2023 05:56:00.4142] Discovery response from MWAR ''running version 0.0.0.0 is rejected.
[*03/30/2023 05:56:00.4142] Failed to decode discovery response.
[*03/30/2023 05:56:00.4142] CAPWAP SM handler: Failed to process message type 2 state 2.
[*03/30/2023 05:56:00.4142] Failed to handle capwap control message from controller - status 4
[*03/30/2023 05:56:00.4142] Failed to process unencrypted capwap packet from 10.1.2.251
[*03/30/2023 05:56:00.4142] Failed to send capwap message 0 to the state machine. Packet already freed.
[*03/30/2023 05:56:00.4142] wtpProcessPacketFromSocket returned 4
[*03/30/2023 05:56:00.4142] Discovery Response from 10.1.2.251
[*03/30/2023 05:56:00.4142]
[*03/30/2023 05:56:00.4142] This AP model is supported by controller version newer than 7.0.0.0!
[*03/30/2023 05:56:00.4142]
[*03/30/2023 05:56:00.4142] Discovery response from MWAR ''running version 0.0.0.0 is rejected.
[*03/30/2023 05:56:00.4142] Failed to decode discovery response.
[*03/30/2023 05:56:00.4142] CAPWAP SM handler: Failed to process message type 2 state 2.
[*03/30/2023 05:56:00.4142] Failed to handle capwap control message from controller - status 4
[*03/30/2023 05:56:00.4142] Failed to process unencrypted capwap packet from 10.1.2.251
[*03/30/2023 05:56:00.4142] Failed to send capwap message 0 to the state machine. Packet already freed.
[*03/30/2023 05:56:00.4142] wtpProcessPacketFromSocket returned 4
Mar 30 05:56:01 apsw_watchdog: secs_no_lighttpd: 0
Mar 30 05:56:01 apsw_watchdog: secs_no_slowfcgi: 0
Mar 30 05:56:01 apsw_watchdog: secs_no_sync_log: 0
Mar 30 05:56:01 apsw_watchdog: secs_no_syslogd: 0
Mar 30 05:56:01 apsw_watchdog: secs_no_hostapd: 0
Mar 30 05:56:01 apsw_watchdog: secs_no_gateway: 0
Mar 30 05:56:01 apsw_watchdog: secs_no_dnsmasq: 0
Mar 30 05:56:01 apsw_watchdog: secs_no_xmit_mon0: 0
Mar 30 05:56:01 apsw_watchdog: secs_no_xmit_mon1: 0
Mar 30 05:56:01 apsw_watchdog: secs_no_xmit_mon2: 0
Writing reload timestamp (Thu Mar 30 05:56:06 UTC 2023) to disk
[03/30/2023 05:56:07.7919] UBIFS: un-mount UBI device 0, volume 3
The system is going down NOW!
Sent SIGTERM to all processes
[*03/30/2023 05:56:07.9219] device capwap0 left promiscuous mode
[*03/30/2023 05:56:07.9619] device capwap1 left promiscuous mode
Sent SIGKILL to all processes
Requesting system reboot16]
[03/30/2023 05:56:09.9113] Restarting system.
[03/30/2023 05:56:09.9513] Going down for restart now
Solved! Go to Solution.
08-07-2023 06:07 AM
KWC23150300:
[*04/16/2023 21:50:59.6214] DOT11_DRV[1]: wifi1 acfg cmd 2 failed for wifi1 errno 19(No such device)
KWC2201078X:
[*04/12/2023 12:37:10.9503] DOT11_DRV[1]: wcp/RadDrv1 :: Dot11BaseDriver get_vap_if_index ioctl SIOCGIFINDEX failed for apr1v0 error No such device
And various other similar messages. The hardware has failed - RMA the APs.
08-03-2023 05:52 AM
- The controller software version is very old use :
https://software.cisco.com/download/home/286284738/type/280926587/release/8.10.185.0
(upgrade the wireless controller software)
M.
08-03-2023 07:37 AM
08-03-2023 11:22 AM
- Checkout https://bst.cisco.com/
M.
08-05-2023 06:16 AM - edited 08-05-2023 06:16 AM
This is almost certainly a hardware failure of the AP requiring RMA.
Attach the complete log from the AP console from power here as a .txt file (don't paste the whole log in here).
That should show when the AP detects hardware failure (eg missing radios) which causes the AP join to fail because it sends malformed join requests to the WLC. The hardware failure rate on the 18xx APs is higher than on other models - we RMA about 20 per month on average.
08-07-2023 02:45 AM
08-07-2023 06:07 AM
KWC23150300:
[*04/16/2023 21:50:59.6214] DOT11_DRV[1]: wifi1 acfg cmd 2 failed for wifi1 errno 19(No such device)
KWC2201078X:
[*04/12/2023 12:37:10.9503] DOT11_DRV[1]: wcp/RadDrv1 :: Dot11BaseDriver get_vap_if_index ioctl SIOCGIFINDEX failed for apr1v0 error No such device
And various other similar messages. The hardware has failed - RMA the APs.
09-08-2023 04:02 AM
Yes, probably it is hardware failure.
Thank you !
08-12-2023 07:38 PM
Try switching it back to Mobility Express mode
video tutorials:
https://www.youtube.com/watch?v=zo91OsLpwwY
08-13-2023 04:45 AM
@Do Tien Dung are you suggesting that converting the AP to Mobility Express will magically repair the failed hardware?
08-14-2023 04:38 AM
If the hardware is faulty, I think RMA should be, and if the Access Point's software is faulty, I think it should be updated to the latest version.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide