Controller Based WLANs

How do I recover a controller that fails to boot when the file system is full or if the partition is corrupt?

Aruba Employee

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

Several reasons could prevent a controller from booting to a point where a user cannot log into the CLI:

  • A corrupted startup configuration is uploaded and attempted to be booted. Search the KB for the procedure to boot from a dummy configuration file to try to recover from this error.
  • When the file system is full, the ArubaOS may not fully load to a point that will allow a user to login.
  • Hardware damage.

The flash can be recovered by formatting the entire file system, but the recovery process would require the restore of the ArubaOS that will delay the recovery process. For accidental upload of a corrupt configuration file, search the KB for the procedure to boot from a dummy configuration file.

The recovery process can be abbreviated by just formatting the partition where the file-system is full or damage. Partition 0:0 and 0:1 is where the two ArubaOS is stored. Partition 0:2 contains the full file system or a corrupted configuration file.

To try to recover the controller, follow these steps:

1) Power cycle the controller and break into the CPBoot by hitting the enter key on startup (console access).


CPBoot 1.2.0.0 (build 20527)
Built: 2009-01-20 at 18:55:40
DRAM: Operating at 533 MHz
DRAM: Channel 0: 512 MB
DRAM: Channel 2: 0 MB
DRAM: Total = 512 MB
POST: Memory test: Physical 0 - 0x10000000 - quick test
Memory test: Physical 0x10000000 - 0x20000000 - quick test
PASS
CPU: XLR508 rev. B2 Clock: 800MHz
Board: A3200
CPLD: rev: 1.1
SMP: All 8 cpus successfully started
Boot: Primary bootflash partition
POST2: OK
Net: xlr_gmac0 xlr_gmac1 xlr_gmac2 xlr_gmac3
IDE: Bus 0: OK
Device 0: Model: CF 512MB Firm: 06/07/29 Ser#: GHS3ABPCF07101500007
Type: Removable Hard Disk
Capacity: 502.0 MB = 0.4 GB (1028160 x 512)

Hit any key to stop autoboot: 0
cpboot>


2) Format Partition 0:2, which is where the configuration file is stored.

cpboot> format 0:2
Format will erase everything on the internal flash's partition 2.
Are you sure you want to continue (y/n)?y
Formating.....................................................................................................................................................................................................................................................................................................................................................................................................................
done
Partition Start Sector Num Sectors Type
1 63 98721 83
2 98784 98784 83
3 197568 830592 83
cpboot>


3) Reload the controller and follow the start-up wizard to regain IP connectivity to the controller.

4) Restore the last offline flash backup and reload the unit.

5) Verify the images in the two partitions by issuing the following command:

(Desk) #show image version
----------------------------------
Partition : 0:0 (/dev/hda1) **Default boot**
Software Version : ArubaOS 3.3.2.13 (Digitally Signed - Production Build)
Build number : 20989
Label : 20989
Built on : Tue Mar 24 18:29:57 PDT 2009
----------------------------------
Partition : 0:1 (/dev/hda2)
Software Version : ArubaOS 3.3.2.13 (Digitally Signed - Production Build)
Build number : 20989
Label : 20989
Built on : Tue Mar 24 18:29:57 PDT 2009

(Desk) #

 

If this procedure does not work, consult Aruba Support.

Version history
Revision #:
1 of 1
Last update:
‎06-30-2014 04:55 PM
Updated by:
 
Labels (1)
Contributors
Search Airheads
cancel
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.