SOP A

This section provides information on upgrade paths, preconditions, the applicable topology, and the upgrade flow for Standard Operating Procedure (SOP) A.

SZ Upgrade Path

  • 5.0.x to 5.1.x
  • 5.1.x to 5.2.x
  • 5.2.x to 6.0.x

Precondition

The standby cluster must have the following license in order to be upgraded:

  • vSZ-H: SUPPORT_HA_EU or SUPPORT_HA_PTNR

SOP A Applicable Topology

Cluster Upgrade Flow
  1. Turn off the monitoring status of each active cluster from the standby cluster. In the standby cluster interface, go to Network > Data and Control Plane > Cluster.
  2. Select the cluster root, and click the Configuration tab.
    For example, select the active cluster in the table and click Switch monitor. Ensure the Monitoring Status is set to Off.

    Turning Off Monitoring Status

  3. Upgrade the Active 1 cluster and make sure it is successfully upgraded.
  4. From the active cluster, go to Monitor > Events and Alarms > Events and check the details of event code 814. Refer Performing the Upgrade.
  5. Repeat steps 2 and 3 to upgrade the Active 2 cluster and the Active 3 cluster.
  6. Upgrade the standby cluster after all the active clusters are successfully upgraded.
  7. Click Sync Now in each active cluster after all the active and standby clusters are successfully upgraded.
  8. From the active cluster, go to Monitor > Events and Alarms > Events and check the details of event code 814. Refer Performing the Upgrade.
  9. Turn on the monitoring status of each active cluster from the standby cluster after the standby cluster is successfully upgraded.
  10. If the new SZ version is 5.2.x (including 5.2), and the standby cluster monitors only one active cluster, the standby cluster will automatically switch to Backup mode regardless of the number of nodes of the Active cluster. After cluster redundancy is enabled, the standby cluster will take some time to restore the configuration of the latest active cluster.
Parent topic: Geo Redundancy Upgrade Operation Flow