Migrating Controller Managed APs to AOS 10

Convert controller managed APs by using the existing infrastructure or by using a separate controller set up for the purpose. If the existing infrastructure is not running a correct software version to support the conversion, the APs can be re-provisioned statically to a separate, temporary controller that has been loaded with one of the required software versions.

When using a cluster and planning which APs are to be converted, consider which controller the APs are connected to. The AP conversion process can be started only from the currently active controller for the AP. If a large cluster is in production, consider using a separate, non-clustered controller for AP staging and upgrading.

The conversion from AOS 8 to AOS 10 uses the “ap convert” command.

ap convert
  active {all-aps|specific-aps}
  add {ap-group|ap-name}
  cancel
  clear-all
  delete {ap-group|ap-name}
  pre-validate {all-aps|specific-aps}

Upgrade process

Using the CLI on the controller:

1. Add APs to the conversion list by specifying the AP Group using the command:

   (host) [mynode] #ap convert add ap-group <group-name>

   or add individual APs into the conversion list using the command:

   (host) [mynode] #ap convert add ap-name <ap-name>

2. Pre-validate the APs added to the conversion list:

   (host) [mynode] #ap convert pre-validate specific-aps

   This command checks the connectivity to Central before attempting to push the firmware conversion. This command prompts the APs to check NTP, Activate, and Central URL reachability and checks if the APs are licensed on Central with a group assigned. This can be useful in narrowing down issues that might occur during the conversion process.

3. Verify the conversion pre-validation status:

   (host) [mynode] #show ap convert-status

   If the pre-validation is successful, the ‘Upgrade Status’ should read ‘Pre Validate Success’, and the assigned ‘Aruba Central Group’ is displayed.

4. The pre-validation job continues until canceled. After all APs have been tested, issue the command to cancel the job and move forward:

   (host) (host) [mynode] #ap convert cancel

5. Download the AOS 10 firmware files for the AP models to be upgraded. Download image files from HPE Networking Support Portal or with assistance of an HPE Aruba Networking account team.

6. Firmware images can be specified individually by AP type, or a TAR file containing all the images can be created to simplify file handling.

7. Firmware images are delivered to the APs by a file server or directly from the controller

   • If using the ‘server’ option, use an ftp, tftp, http, https, or scp server and copy the AOS 10 image files to the server.

   • If using the ‘local-flash’ option, the AOS 10 firmware image file(s) must be copied to the controller’s flash using the ‘copy’ command on the CLI or under Controller > Diagnostics > Technical Support > Copy Files on the GUI.

   • In addition to the local options, the firmware can be pulled from the web using the Central software repository at common.cloud.hpe.com/ccssvc/ccs-system-firmware-registry/IAP

8. Execute the command to trigger the conversion using ftp, tftp, http, https, or scp as one of the available options for the server.

   Examples:

   (host) [mynode] #ap convert active specific-aps server scp username <username> <hostname> <image filename>

   or

   (host) [mynode] #ap convert active specific-aps server http common.cloud.hpe.com path ccssvc/ccs-system-firmware-registry/IAP <image filename>

   Note

   Multiple filenames can be used in the command above if there is more than one model of AP present in the group by using a semi-colon “;” delimiter, e.g.:

   (host) [mynode] #ap convert active specific-aps server scp username admin 1.2.3.4 firmware1;firmware2

   or a TAR file containing multiple images can be used e.g.:

   (host) [mynode] #ap convert active specific-aps server scp username admin 1.2.3.4 ImageFile.tar

   or

   (host) [mynode] #ap convert active specific-aps local-flash <image filename>

   Note

   Multiple filenames can be specified in the local-flash if there is more than one model of AP present in the group by using a semi-colon “;” delimiter, e.g.:

   (host) [mynode] #ap convert active specific-aps local-flash firmware1;firmware2

   or a TAR file containing multiple images can be used e.g.:

   (host) [mynode] #ap convert active specific-aps local-flash ImageFile.tar

   A third option, ‘activate’, is available but not currently recommended for use.

9. Verify the conversion status using:

   (host) [mynode] #show ap convert-status

10. The firmware upgrade process follows these steps:

    • The controller upgrades the APs to AOS 10.

    • The APs boot to AOS 10, receive the provisioning rule to connect to Central from Activate, and connect to Central which places the AP in the assigned group.

    • Central performs a config audit and pushes the group configuration.

    • Central cleans up any old configuration on the APs except for the uplink parameters.

Troubleshooting

AP groups or individual APs can be removed from the conversion list using the relevant command below:

(host) [mynode] #ap convert delete ap-group <ap-group>

(host) [mynode] #ap convert delete ap-name <ap-name>

To clear all APs from the conversion list, execute the following command:

(host) [mynode] #ap convert clear-all

To abort the conversion of APs or stop the pre-validation tasks:

(host) [mynode] #ap convert cancel

Revert to AOS 8 firmware version

If needed, convert the APs back to AOS 8:

1. Make sure that the target controller is licensed and has the capacity to add the APs.

2. Make sure no conversion tasks are pending on the controller from previous conversions; otherwise APs will try to convert back to AOS 10.

   (host) [mynode] #show ap convert-status

   If the current status is ‘Active,’ the running job must be canceled:

   (host) [mynode] #ap convert cancel

3. Open the AP’s console using serial, SSH, or Central Remote Console.

4. Issue the command to the AP for conversion back to controller-based:

   convert-aos-ap cap <controller-address>

   • The AP will download the AOS 8 image from the controller and reboot.

   • The AP will sync configuration based on provisioning status

5. After the APs are successfully converted back to AOS 8, remove the Central subscription using the HPE GreenLake console to remove the APs from Central management