Management subsystem two data center upgrade to v10.0.5.5 and later

Upgrades to v10.0.5.5 and later: How to upgrade your management subsystem in a two data center deployment.

About this task

Follow the steps in this topic, along with the steps documented in Upgrading to the latest release on VMware.

Some steps in the upgrade process are run from the project directory with the apicup command. Other steps require you to login to the management VMs as root user. To login as root, follow these steps:

Use SSH to login to the VM as the apicadm user:
```
ssh apicadm@<hostname>
```
Switch to the root user with sudo:
```
sudo -i
```

Procedure

Review the Upgrade considerations on VMware.
Complete the Preparing to upgrade on VMware steps.
Run the upgrade command on both sites with the --skip-operand-update flag:
```
apicup subsys install <subsystem name> <subsystem upgrade tar archive> --skip-operand-update
```
Note: If any Control Plane files are needed for your upgrade, you must append the files to the install command. For example:
```
apicup subsys install <subsystem name> <subsystem upgrade tar archive> <path to control plane file 1> <path to control plane file 2> --skip-operand-update
```
The --skip-operand-update flag tells the subsystem to update only the API Connect operator on the VMs, and not the management software on the VM (the operand).
Login to the VMs on both sites and monitor the status. Verify that the subsystem status reaches the Running state.
```
kubectl get mgmt

NAME         READY   STATUS    VERSION    RECONCILED VERSION AGE
management   n/n     Running   <current version>   <current version>   5h2m
```
The RECONCILED VERSION/VERSION should still show your current version, not the version you are upgrading to.
Disable 2DCDR on the warm-standby management subsystem:
```
apicup subsys set <warm-standby management subsystem> multi-site-ha-enabled=false
apicup subsys install <warm-standby management subsystem>
```
Conversion from warm-standby to a stand-alone management subsystem can take some time. Run the health check to ensure that the deployment is in a good state before proceeding:
```
apicup subsys health-check <warm-standby management subsystem>
```
an empty response means no detected problems.
Disable 2DCDR on the active management subsystem.
```
apicup subsys set <active management subsystem> multi-site-ha-enabled=false
apicup subsys install <active management subsystem>
```
Conversion from active to a stand-alone management subsystem can take some time. Run the health check to ensure that the deployment is in a good state before proceeding:
```
apicup subsys health-check <active management subsystem>
```
an empty response means no detected problems.
Run the upgrade command on both sites without the --skip-operand-update flag:
```
apicup subsys install <subsystem name> <subsystem_upgrade_tar_archive>
```
Continue following the standard management subsystem upgrade steps, from step 10.a on Upgrading to the latest release on VMware.

After the upgrades on both sites are complete, re-enable 2DCDR on the previously active management subsystem.

apicup subsys set <active management subsystem> multi-site-ha-enabled=true
apicup subsys install <active management subsystem>

kubectl get mgmt

NAME         READY   STATUS    VERSION    RECONCILED VERSION AGE
management   n/n     Running   <new version>   <new version>   5h2m

Enable 2DCDR on the previously warm-standby management subsystem.

apicup subsys set <warm-standby management subsystem> multi-site-ha-enabled=true
apicup subsys install <warm-standby management subsystem>

kubectl get mgmt

NAME         READY   STATUS    VERSION    RECONCILED VERSION AGE
management   n/n     Running   <new version>   <new version>   5h2m