Controller Based WLANs

How do I find out why the AP reboots or rebootstraps?

Product and Software: This article applies to Aruba OS 3.1 and later.

 

When the AP reboots or rebootstraps, it stores the trigger on its flash when it does so. Use the following command to display this information:

 

show ap debug system-status ap-name <name_of_AP>

 

Example:

(Aruba5000) #show ap debug system-status ap-name d70

Reboot Information
------------------
AP rebooted Tue Apr 29 05:48:42 PST 2008: SAPD: Reboot requested by controller
------------------------------------------------------------------------------

Rebootstrap Information
-----------------------
(none found)
------------

Descriptor Usage
----------------
Interface Queue    Alloc  Free   In-use Max Failed
--------- -----    -----  ----   ------ --- ------
wifi0     0        0      0      0      0   0
wifi0     1        0      0      0      0   0
wifi0     2        0      0      0      0   0
wifi0     3        92535  92535  0      6   0
wifi0     7(UAPSD) 0      0      0      0   0
wifi0     8(CAB)   0      0      0      0   0

:

:

:

:

 

The output of this command can be filtered to view just reboot or rebootstrap information as shown here:

 

(Aruba5000) #show ap debug system-status ap-name d70 | include Reboot
Reboot Information
AP rebooted Tue Apr 29 05:48:42 PST 2008: SAPD: Reboot requested by controller
Rebootstrap Information

 

Different Reboot or Rebootstrap Reasons

 

  1. AP rebooted Tue Apr 29 10:22:30 PST 2008: SAPD: Unable to contact switch. Called by sapd_hello_cb:4

 

Indicates that the AP had problems communicating with switch; possible L2 / L3 issues.

 

  1. AP rebooted Tue Apr 29 10:25:31 PST 2008: SAPD: Rebooting after provisioning

 

Indicates that the AP rebooted after being provisioned or reprovisioned.

 

  1. AP rebooted Tue Apr 29 10:41:55 PST 2008: SAPD: Reboot requested by controller

 

Indicates that the AP is rebooted from the controller from WebUI or CLI using the 'apboot' command.

 

  1. AP rebooted Fri Dec 31 16:05:23 PST 1999: SAPD: Reboot after image upgrade

 

Indicates that the AP rebooted after upgrading its image.

 

  1. 2008-04-29 10:33:42 Missed heartbeats on radio 0 VAP 0

 

In this case, the AP rebootstrapped because it missed heartbeats, which indicates network issues.

 

6. Sometimes no reboot or rebootstrap information is found, which happens when the AP did not have time to write the information to flash memory.

 

Reboot Information
------------------
(none found)
------------

Rebootstrap Information
-----------------------
(none found)
------------

 

This is normally seen when AP loses power. Another rare possibility is an AP kernel crash.

Version History
Revision #:
1 of 1
Last update:
‎07-06-2014 08:13 AM
Updated by:
 
Labels (1)
Contributors
Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.