Upgrading Cluster

The Live Upgrades feature allows the managed devices and APs in a cluster to automatically upgrade the software from ArubaOS 8.1 version to higher ArubaOS versions. Managed Devices in a cluster can be seamlessly upgraded by specifying the new image file and a target partition. You can configure a cluster upgrade using the WebUI or command-line interfaces.

Upgrading Cluster using WebUI

Perform the following steps to upgrade the cluster:

1. Login to a Mobility Master.
2. In a Managed Network node hierarchy, navigate to Configuration > Tasks.
3. Click Upgrade Cluster.
4. In the Cluster section lists the currently defined clusters in a table, select the cluster to upgrade.

The table displays the Name of the cluster, the number of managed devices, the number of APs in the cluster and the version of software running on the managed devices of the cluster.

5. Click Next.
6. In the Image File section, specify the image file location, name, and the protocol to use. Enter values for the following parameters:

IP address - IP address of the server

Image path - Path of image file

Upgrade to version - Version to upgrade to

Protocol - Protocol to use to transfer file. Valid values are: FTP, TFTP and SCP. Default value is FTP.

Username - Username of the account on the image server.

Password - Password of the account on the server.

7. Click Next.
8. In the Target Partition section, specify the managed device partition to install firmware and boot from. Select any one of the following partitions:

Partition 0

Partition 1

Alternate Partition

9. Click Upgrade cluster to start the cluster upgrade process.
10. To check the status of the upgrade, in the Managed Network node hierarchy, navigate to Configuration > Services > Cluster.
11. The upgrade status for cluster name section is displayed with the status of the upgrade. The status of the upgrade could be any of the following values:

Upgrade pending

AP partitioning in progress

Upgrade in progress

Upgrade failed

Upgrade completed

12. The status of each managed device is displayed. Similarly, the status for each AP in the cluster is also displayed.

Upgrading Cluster using CLI

Execute the following command to trigger the cluster upgrade in the Mobility Master:

(host) [mm] [cluster1] #lc-cluster <cluster_name> initiate upgrade version <img_version> partition <partition_id>

cluster_name: The configured cluster profile name, the managed devices and APs associated to the cluster that needs to be upgraded.

img_version: The target image version, such as 8.1.1-svcs-ctrl_XXXXX.

partition_id: The partition on the managed device to which the new image is to be copied, valid values are 0 or 1 and this is optional. If the partition not specified, it will automatically pick the alternate boot partition.

 

The fileserver is automatically selected to be the fileserver configured in the upgrade-profile. Ensure that the upgrade-profile is configured before upgrading the cluster using the CLI.

To check the status of the upgrade, for Cluster1, execute the following show commands:

#show lc-cluster cluster1 controller details

#show lc-cluster cluster1 ap details

#show lc-cluster cluster1 upgrade status

#show lc-cluster cluster1 upgrade status verbose

Limitation

This feature has the following limitations:

As there is a image preload limitation, cluster upgrade cannot be used with two different versions without reloading the managed devices. Only one preload per managed device reboot is allowed currently.

The state of the AP preload is not displayed in the WebUI during the cluster upgrade.

Cluster upgrade cannot be triggered if a previous upgrade resulted in split sub clusters.