Controller Based WLANs

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

Sometimes an Aruba 3000 Series controller boots up and the partition or configuration has been corrupted and only the cpboot prompt is displayed.

 To bring up the controller in this situation, you must assign the static parameters to the controller and upload the image from a TFTP server. 

Generally, what is happening is that the Gig port  is not communicating to the TFTP server or PC and we will not be able to communicate to the server. Even a ping is not possible.

To resolve this issue, we must activate the Gig port. Four Gig ports are available in the controller and in cpboot mode they are referred to as Gmac0, Gmac1, Gmac2, and Gmac3.

According to the internal board design, Gmac3 is referred to as port0 mentioned on the front panel of the controller. By default, the controller communicates through port0/Gmac3 of the controller with the PC.

Connect the Ethernet cable to the port0 of the controller, assign the static parameters to the controller, and activate all the Gig/Gmac ports referred in cpboot mode.

 To activate the Gig port, start the interfaces by issuing the following command:

 Cpboot>xlr start

This command resets the interfaces and you will be able to communicate to the PC/TFTP server.

If it failed, execute the same command two or three times and communicate to the PC/server.