AOS 6 Basic controller upgrade.
The below document is something very simple I put together for anyone having issues with AOS 6 as simple mistakes can be made.
Below is a basic step-by-step guide on how to upgrade your controller successfully.
The below is how to upgrade controllers in 8 easy steps:
1. Be sure to check the release notes of the code version you are on, and the code version you are upgrading too. To ensure you can upgrade directly to this new code version or if you need to confirm the code version “hop” that you have to upgrade to. Checking the release notes carefully is always useful to ensure that there are no severe reported issues in the code release. NOTE: If you have more than one controller, make sure that you upgrade the master controller first. It is advised to upgrade them one at a time but if you are confident with the process these can be done at the same time, ensuring that the master was started a little earlier than the local or the backups.
2. Go to the Aruba support portal (http://support.arubanetworks.com/) and search for the appropriate code version for the appropriate appliance. Once you have found this please download and save locally. These are the code versions you would need to download for the various controller models: 7000 series controller will use this code file:
ArubaOS_70xx_ 7200 series controller will use this code file: ArubaOS_72xx_
7280 series controller will use this code file: ArubaOS_7280_
3600 series controller will use this code file: ArubaOS_MMC_
600 series controller will use this code file: ArubaOS_6xx_
3. Navigate to “Maintenance > Backup Flash > Click “Create Backup”. Then click “Copy Backup” and from the “Source selection” select the backup you have created from the drop-down menu, then under “Destination selection” select to send the backup to an external source on your network or you can send it to a TFTP server on your network.
4. Navigate to “Maintenance > Copy Files > select “Running Configuration” under source selection then under “destination selection” select an external location to send the backup to. This is so you can have the running configuration of the current controller.
5. Go to Image management > Select “local File” and then upload the correct code version. Please select the opposite partition to the one that you are currently on. This will ensure that the non-boot partition is upgraded. Recommended to select yes for Reboot Switch after Upgrade Save Current Configuration before Reboot It is recommended to select this so the new code version can take effect immediately. If you cannot reboot now you can schedule a reboot during a maintenance window.
6. Select “upgrade”. If you have chosen to automatically reboot the controller there will be a 10-second countdown after the configuration applied and then it will automatically reboot.
7. If you did not choose the “upgrade” option, go to “Maintenance > Reboot controller” and then click reboot. The partitions will automatically swap once the controller is rebooted. You only do this if you have upgraded but were not able to reboot the controller at that time.
8. The controller should come back up and be functioning within 15 minutes of going down. Once back up, the AP’s will go down roughly five at a time to upgrade their code versions. This will take longer if you have more access points on your network. If you have any issues with the upgrade, the controller doesn’t come back online after the upgrade, or after the upgrade, you are experiencing issues. Please either speak with your support company or directly with Aruba support. For more in-depth instructions, please visit the release notes for the code version you are upgrading too.
I will be making more documents like this to help other Aruba beginners, for AOS 6 and AOS 8 so please let me know if you have a request for any specific documentation.