Upgrading Cluster
The Live Upgrades feature allows you to upgrade the managed devices and APs in a cluster to the latest ArubaOS version. Managed devices in a cluster can be seamlessly upgraded by specifying the new image file and a target partition. This is a real-time network upgrade where managed devices and APs upgrade automatically without any planned maintenance downtime.
You can also schedule an upgrade to a specified time to avoid manual intervention. The cluster is upgraded automatically at the scheduled time. You can view, delete, or reschedule the scheduled cluster upgrade.
When a cluster is upgraded, the following actions take place:
1. The cluster upgrade manager sends information of the APs to AirMatch.
2. The AirMatch creates logical groups of APs and updates the cluster upgrade manager with this information.
3. A target managed device is assigned to all APs in each partition.
4. The managed devices download the new firmware. The following events happen after the firmware download:
a. One of the target managed devices is rebooted.
b. All APs on the managed device that is rebooted move to their standby managed device.
c. APs for which the target managed device is rebooted are preloaded.
5. The AP image is preloaded on the APs.
6. All APs in one partition are upgraded first.
7. The upgraded APs are then moved to the managed device.
8. Subsequently, all APs belonging to different partitions are preloaded, rebooted, and moved to the upgraded managed device.
9. The second target managed device is also reloaded.
10. Steps 4a to 9 are repeated till all the managed devices in the cluster are upgraded.
Following section describes how to configure Live upgrade and the limitations of live upgrade:
Configuring Live Upgrade
The following procedure describes how to upgrade the cluster:
1. Log in to a Mobility Master.
2. In the node hierarchy, navigate to ..
3. Select one or multiple clusters from the table. The table only lists the clusters and not the cluster members.
|
|
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. |
4. In the menu, select .
5. In the section, specify the image file location, name, and the protocol to use. Enter values for the following parameters:
—IP address of the server
—Path of image file
—Version to upgrade to
—Protocol to use to transfer file. Valid values are: FTP File Transfer Protocol. A standard network protocol used for transferring files between a client and server on a computer network. , TFTP Trivial File Transfer Protocol. The TFTP is a software utility for transferring files from or to a remote host. , and SCP Secure Copy Protocol. SCP is a network protocol that supports file transfers between hosts on a network.. Default value is FTP File Transfer Protocol. A standard network protocol used for transferring files between a client and server on a computer network. .
—Username of the account on the image server.
—Password of the account on the server.
6. Click
7. In the section, specify the managed device partition where you want to install the firmware and where you want it to boot from. Select any one of the following partitions:
8. Click to start the cluster upgrade process.
9. To check the status of the upgrade, in the node hierarchy, navigate to .
10. The section is displayed with the status of the upgrade. The status of the upgrade can be any of the following values:
11. The status of each managed device is displayed. Similarly, the status for each AP in the cluster is also displayed.
12. You can also upgrade a cluster using the shortcut icon by navigating to and selecting the cluster you want to upgrade.
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; corresponds to the managed devices and APs associated to the cluster that needs to be upgraded.
img_version: The target image version, such as 8.2.1_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 is not specified, it automatically picks the alternate boot partition.
|
|
The fileserver is configured in upgrade profile. Ensure that the is configured before upgrading the cluster using the CLI Command-Line Interface. A console interface with a command line shell that allows users to execute text input as commands and convert these commands to appropriate functions.. |
To check the status of the upgrade, for Cluster1, execute the following show commands:
(host)#show lc-cluster cluster1 controller details
(host)#show lc-cluster cluster1 ap details
(host)#show lc-cluster cluster1 upgrade status
(host)#show lc-cluster cluster1 upgrade status verbose
(host)#show lc-cluster cluster1 upgrade stats
Limitation
This feature has the following limitations:
As there is an image preload limitation, cluster upgrade cannot be done 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 subclusters.
Cluster Rolling Upgrade is not supported on mesh nodes. Therefore, a cluster upgrade cannot be performed for mesh deployments.
It is not recommended to use live upgrade in MultiZone deployments. Each zone can use live upgrade but the upgrade on datazone is not hitless.
