Upgrading Cisco ACI Multi-Site Orchestrator Guidelines
-
Ensure that you have upgraded the Cisco APICs in each site to Release 4.0(1) before upgrading Cisco ACI Multi-Site Orchestrator.
Cisco ACI Multi-Site does not support different APIC release versions in different sites for extended operation. Mixed APIC Release 3.2(x) and 4.0(x) deployments are supported for a limited duration during the entire Multi-Site fabric upgrade process. During this mixed operation, Cisco ACI Multi-Site Orchestrator must continue to run the version that is supported by the earliest APIC Release.
-
Ensure that you are running at least Cisco ACI Multi-Site Orchestrator, Release 1.2(1). If you are running an earlier release, you must first upgrade it as described in Upgrading Cisco ACI Multi-Site Orchestrator to Release 1.2(x) .
-
Ensure that your current Cisco ACI Multi-Site Orchestrator installation is running properly and each node in the cluster has at least 15 GB of free disk space.
-
Ensure that all Cisco ACI Multi-Site Orchestrator node VMs have been upgraded to any new minimum CPU and RAM requirements that are listed in Deploying Cisco ACI Multi-Site Orchestrator Guidelines.
Note
When upgrading the virtual machines:
-
It is recommended that all virtual machine CPU and RAM changes are done when the VM is powered down, as such we recommend updating the VMs one at a time to ensure that the cluster remains available.
-
Do not change the hard disk size of the Cisco ACI Multi-Site Orchestrator VMs.
-
You can upgrade Cisco ACI Multi-Site Orchestrator in two ways, using Python or upgrade.sh
script. While all versions can be upgraded using upgrade.sh
, we recommend using the Python script for upgrading to Release 2.0(1) or later as it automates several manual steps and supports
remote execution of the upgrades.
-
Upgrading using Python is described in Upgrading Cisco ACI Multi-Site Orchestrator to Release 2.0(x) Using Python.
-
Upgrading using
upgrade.sh
is described in Upgrading Cisco ACI Multi-Site Orchestrator to Release 2.0(x) Using upgrade.sh.