Controller Based WLANs

Introduction :

This article speaks about changing the boot partition from Cpboot> mode. use case scenario's where controller get stuck in one boot partition can be made to boot from other. This reduces down time and controller can be brought up and running with an image in other partition.

Feature Notes :

• Flash contains two partitions:  0:0 and 0:1
•  Console access to the device is required.

Environment :

This article applies to all Aruba Mobility Controller irrespective of ArubaOS code version.

Network Topology :

Computer with Serial port connected to console port on Controller.

Configuration Steps :

There are two system partitions dedicated to store the controller image files. These partitions are named 0:0 and 0:1 respectively.
 
To change the boot partition from the cpboot, follow these steps:
 
1. Obtain access to the controller via console access.
2. Break the auto boot sequence during the controller reboot.
 
To break into the cpboot mode, when the following prompt appears on the console screen, hit any key to go into the cpboot mode.
 
Hit any key to stop autoboot: 0
 
To change the boot partition to 0:0, type the following command on the cpboot prompt:
 
cpboot> bootf 0:0
 
To change the boot partition to 0:1, type the following command on the cpboot prompt:
 
cpboot> bootf 0:1
 

Example:

Changing the boot partition to 0:0
 
<-- Output Truncated -->

 
Hit any key to stop autoboot: 0

cpboot>
cpboot> bootf 0:1
Loading image 0:1#####################
<-- Output Truncated -->

Verification :