04-17-2020 05:14 AM - edited 07-05-2021 11:57 AM
I have two access points Catalyst C9115AXI-E connected to a virtual wireless LAN controller (vWLC). One of these two access points reboots every 4 hours 17 minutes and 10 seconds, which is every 15'430 seconds (+/- 5 seconds). And this, consistent over several days. The AP is configures in FlexConnect mode, has two WLANs and authentication is done through a radius server (EAP) and for the second WLAN with WPA3-SAE.
On the vWLC I get the heartbeat timeout as follows:
*spamApTask5: Apr 17 08:19:34.006: %CAPWAP-3-ECHO_ERR: capwap_ac_sm.c:8266 Did not receive heartbeat reply; AP: [AP MAC]
*spamApTask5: Apr 17 08:19:34.006: %CAPWAP-3-DTLS_CLOSED_ERR: capwap_ac_sm.c:7516 [AP MAC]: DTLS connection closed for AP [AP IP] (5259), Controller: [Controller IP] (5246) Echo Timer Expiry
I think that the reboots started after I upgraded the software from 8.10.105.0 to 8.10.121.0. But I am not sure as for COVID-19 reasons, almost nobody uses the office with the rebooting AP. After the rebook the AP properly connects to the vWLC and works perfectly fine again for 4h17'10".
The second access point, connected to same vWLC and configured the same way, is already up for 9 days without any reboots. Also the virtual WLC works fine, without any issues.
Software version: 8.10.121.0
Boot Version: 1.1.2.4
Any idea where that consistent time could come from?
Solved! Go to Solution.
05-01-2020 02:30 AM
Finally TAC resolved the case - it is a bug on the firmware.
The access point requires ICMP (ping) access to the standard gateway of the management interface. If the ICMP is not returned, the access point reboots after the 4 hours.
Once I allowed the access point to ping the router everything was fine.
Thanks for all help.
04-17-2020 06:34 AM
I would recommend falling back the the previous version of code if possible to see if the error goes away. 8.10 code has a lot of know bugs. If you can't revert back I would hit TAC to see if you are hitting one of these bugs
04-17-2020 11:05 PM
Hi d.friday
I was thinking about going back, but then I may just postpone the issue. Currently nobody is in the office, so I have some time to analyze and hope to find the issue.
Thanks,
Roland
04-17-2020 06:14 PM
Remote into the offending AP and post the complete output to the following commands:
sh version sh flash syslog
04-17-2020 11:03 PM
Hi Leo
Thanks for the feedback, here the output of the commands:
sh version (I removed the copyright text)
04-18-2020 02:12 AM
Meanwhile, I checked more logs and found the reboot reason to be listed as "apsw_watchdog about to reboot with reason: no_gateway_connection". However, the network connection looks fine, at least I have not found any indication it stops.
Besides, I disconnected the switch for a couple minutes and reconnected it and there was no reboot of the access point.
So, I have still no clue where these reboots comes from.
Apr 18 05:14:44 apsw_watchdog: apsw_watchdog about to reboot with reason: no_gateway_connection
Apr 18 05:14:44 kernel: [*04/18/2020 05:14:44.0950]
Apr 18 05:14:44 kernel: [*04/18/2020 05:14:44.0950] !!!!! {watchdogd} apsw_watchdog about to reboot with reason: no_gateway_connection
Apr 18 05:14:44 kernel: [*04/18/2020 05:14:44.0950]
Apr 18 05:14:44 kernel: [*04/18/2020 05:14:44.0950] you have 10 seconds to run this to stop this process. Good luck.
Apr 18 05:14:44 kernel: [*04/18/2020 05:14:44.0950] freeze -w
Apr 18 05:14:54 apsw_watchdog: generation: 738199564
Apr 18 05:14:54 apsw_watchdog: reason: no_gateway_connection
Apr 18 05:14:54 apsw_watchdog: watchdog bit, rebooting in 5 seconds...
Apr 18 05:14:54 apsw_watchdog: secs_lowmem: 0
Apr 18 05:14:54 apsw_watchdog: secs_no_kclick: 0
Apr 18 05:14:54 apsw_watchdog: secs_no_klogd: 0
Apr 18 05:14:54 apsw_watchdog: secs_no_sxpd: 0
Apr 18 05:14:54 apsw_watchdog: secs_no_hostapd: 0
Apr 18 05:14:54 apsw_watchdog: secs_no_gateway: 14460
Apr 18 05:14:54 apsw_watchdog: secs_no_xmit_mon0: 0
Apr 18 05:14:54 apsw_watchdog: secs_no_xmit_mon1: 0
Apr 18 05:14:54 apsw_watchdog: secs_no_xmit_mon2: 0
Apr 18 05:14:54 apsw_watchdog: secs_absent_mon0: 0
Apr 18 05:14:54 apsw_watchdog: secs_absent_mon1: 0
Apr 18 05:14:54 apsw_watchdog: secs_watchdog_running: 15430
Apr 18 05:14:54 apsw_watchdog: freemem: 1138118656
Apr 18 05:14:54 apsw_watchdog: ticks: 2893
04-18-2020 05:49 AM
When rebooting the access point the timer is reset and it takes again 15430 seconds.
Further I checked more logs and the watchdog counter (apsw_watchdog: secs_watchdog_running: 15430) always shows 15430 seconds, when the reboot is initiated by "no_gateway_connection".
04-18-2020 07:15 AM
05-01-2020 02:30 AM
Finally TAC resolved the case - it is a bug on the firmware.
The access point requires ICMP (ping) access to the standard gateway of the management interface. If the ICMP is not returned, the access point reboots after the 4 hours.
Once I allowed the access point to ping the router everything was fine.
Thanks for all help.
08-10-2023 02:27 AM
Hi I have a similar issue but are using a physical WLC
The AP is running
cisco C9115AXI-E ARMv8 Processor rev 0 (v8l) with 1971660/1185988K bytes of memory.
Processor board ID FCW2614YF7H
AP Running Image : 17.3.5.42
Primary Boot Image : 17.3.5.42
Backup Boot Image : 8.10.130.0
No errors on the upstream switches ( C9300 Stack ) and no console msgs/ logs on AP
08-10-2023 02:28 AM
Which version of Firmware are you running now ? Would you have the Cisco bug ref at all ?
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