Legal Disclaimer: The resource assets in this website may include abbreviated and/or legacy terminology for HPE Aruba Networking products. See www.arubanetworks.com for current and complete HPE Aruba Networking product lines and names.
Handling Upgrade for Datacenter Redundancy
Disaster Recovery is essential to resume business operations followed by any unexpected failure that might damage or destroy data in a network. In case of Aruba Central On-Premises upgrade from one version to another it is beneficial to have a secondary cluster for safe management of software and hardware systems. For more information on Aruba Central On-Premises disaster recovery, see Datacenter Redundancy.
If only one Aruba Central On-Premises cluster is upgraded, then the Redundancy Status is displayed as Version Mismatch. It indicates that the peer Aruba Central On-Premises cluster must also be upgraded.
Aruba Central On-Premises can be upgraded in two ways:
In order to upgrade Aruba Central On-Premises from one version to another, you should first upgrade the primary cluster. Aruba Central On-Premises secondary cluster can only be upgraded after the primary cluster is updated. The upgrade version of the secondary cluster must be the same as the primary cluster. Secondary cluster acts in maintenance mode, and is beneficial in case of any disaster scenario in the network whereas, primary cluster is the functional one.
For more information, see the following topics:
