Wireless Access

I recently had a 575 AP showing as down in AirWave and on the WLC. Looking at the switchport for it the port was Up/Up and the AP was pingable from the WLC and Switch. It was showing "CPU2 jiffies have stopped" in the WLC logs when filtered for that AP. The device was scheduled to be rebooted this morning but to my surprise when going to check on the device it showed a 15 day uptime.

Any thoughts as to why the device would be getting the error and then randomly come back online without any action taking place? This is the first time this has happened with this AP (and hopefully the only time it occurs).

CPU jiffies have stopped is not enough to go on for a bug search. What version of code? Is there any crash-info present for the AP? What was the last reboot reason? Check the output of show ap debug system-status ap-name <ap-name> | begin Reboot

------------------------------
Josh

Original Message:
Sent: Nov 28, 2023 09:47 AM
From: McBehr
Subject: CPU2 jiffies have stopped

I recently had a 575 AP showing as down in AirWave and on the WLC. Looking at the switchport for it the port was Up/Up and the AP was pingable from the WLC and Switch. It was showing "CPU2 jiffies have stopped" in the WLC logs when filtered for that AP. The device was scheduled to be rebooted this morning but to my surprise when going to check on the device it showed a 15 day uptime.

Any thoughts as to why the device would be getting the error and then randomly come back online without any action taking place? This is the first time this has happened with this AP (and hopefully the only time it occurs).

There is no reboostrap information and the last reboot reason was "SomeCrash Warm-Reset". It's a 575 on Boot Version 2.5.5.1 and AOS 8.9.0.3.

CPU jiffies have stopped is not enough to go on for a bug search. What version of code? Is there any crash-info present for the AP? What was the last reboot reason? Check the output of show ap debug system-status ap-name <ap-name> | begin Reboot

------------------------------
Josh

Original Message:
Sent: Nov 28, 2023 09:47 AM
From: McBehr
Subject: CPU2 jiffies have stopped

I recently had a 575 AP showing as down in AirWave and on the WLC. Looking at the switchport for it the port was Up/Up and the AP was pingable from the WLC and Switch. It was showing "CPU2 jiffies have stopped" in the WLC logs when filtered for that AP. The device was scheduled to be rebooted this morning but to my surprise when going to check on the device it showed a 15 day uptime.

Any thoughts as to why the device would be getting the error and then randomly come back online without any action taking place? This is the first time this has happened with this AP (and hopefully the only time it occurs).

There is a bug for the AP-575 with that reboot reason linked to AOS-248121 fixed in 8.10.0.9. https://www.arubanetworks.com/techdocs/ArubaOS/Consolidated_8.x_RN/Content/8.10/09/resolved_8.10.0.9.htm

There is no reboostrap information and the last reboot reason was "SomeCrash Warm-Reset". It's a 575 on Boot Version 2.5.5.1 and AOS 8.9.0.3.

CPU jiffies have stopped is not enough to go on for a bug search. What version of code? Is there any crash-info present for the AP? What was the last reboot reason? Check the output of show ap debug system-status ap-name <ap-name> | begin Reboot

------------------------------
Josh

Original Message:
Sent: Nov 28, 2023 09:47 AM
From: McBehr
Subject: CPU2 jiffies have stopped

I recently had a 575 AP showing as down in AirWave and on the WLC. Looking at the switchport for it the port was Up/Up and the AP was pingable from the WLC and Switch. It was showing "CPU2 jiffies have stopped" in the WLC logs when filtered for that AP. The device was scheduled to be rebooted this morning but to my surprise when going to check on the device it showed a 15 day uptime.

Any thoughts as to why the device would be getting the error and then randomly come back online without any action taking place? This is the first time this has happened with this AP (and hopefully the only time it occurs).