Controller Based WLANs

What information should I collect before I reboot the controller?

by on ‎06-30-2014 05:39 PM

Product and Software: This article applies to all Aruba controllers and ArubaOS 3.3 and 3.4.

 

You might have a network emergency and decide to reboot the controller before you call Aruba TAC (Aruba Technical Assistent Center). You might do this as a quick troubleshooting step to see if the issue gets resolved after rebooting the controller.

 

However, Aruba strongly recommends that you capture the following information before the reboot. Capture this information before the reboot, because all the logs and the audit-trail information on the controller are lost when the controller is rebooted. These logs help TAC to understand the issues better. In certain cases, TAC may be able to identify the root cause on the issues reported.

To collect the required information before a reboot, follow these steps:

 

1) Determine if any crash is present on the controller. Issue the following command:

#show switchinfo
Hostname is Bharath@RN

Location not configured
.............
.......

switchrole:master
Configuration Changed since last save
Crash information available.
Reboot Cause: User reboot.

If there is crash information available, run the following command to have the crash file saved to the flash on the controller.

#tar crash
Please wait while we tar the crash directory...
Done.

You can check if the file is present in the flash on the controller.

#dir

-rw-r--r-- 1 root root 229282 Apr 17 2009 AP_techsupport.txt
-rw-r--r-- 1 root root 2507 Jul 24 12:30 a
-rw-r--r-- 1 root root 7524352 Jan 5 09:29 crash.tar
-rw-r--r-- 1 root root 11303 Dec 18 15:40 default.cfg
........

Copy the file out of the switch and save it on a local machine.

2) Provide the controller logs and output of the tech-support command using the WebUI Maintenance tab or using the CLI (the 'tar logs tech-support' command).

 

3) Provide the syslog server file of the controller at the time of the problem.

Note: Aruba strongly recommends that you add a syslog server to capture logs of the controller, if you do not already have one.

4) If the access points have any issues, capture the AP tech-support information from the controller for these APs multiple times in a span of 10 seconds.

#show ap tech-support ap-name <Name of the Access point>

5) Capture the flash backup from the controller to have the configuration from the controller prior to rebooting the controller. Issue the following command:

#backup flash
Please wait while we tar relevant files from flash...
Please wait while we compress the tar file...
Checking for free space on flash...
Copying file to flash...
File flashbackup.tar.gz created successfully on flash.
Please copy it out of the switch and delete it when done.

Copy the file out of the switch and save it on a local machine.

6) If the issue is with the WebUI, capture screen shots that show the exact problem with the web interface.

 

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.