SOP B

This section provides information on upgrade paths, preconditions, the applicable topology, and the upgrade for SOP B.

SZ Upgrade Path

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

Preconditions

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

  • SZ300: SUP_SZ300_HA_EU or SUP_SZ300_HA_PTNR
  • vSZ-H: SUPPORT_HA_EU or SUPPORT_HA_PTNR

SOP B Applicable Topology

Cluster Upgrade Flow
  1. Rehome any AP from the standby cluster and ensure all the APs are on the active cluster.
  2. Disable cluster redundancy from the active cluster and check if all APs are online and up-to-date.
  3. Upgrade the active cluster and ensure the active SZ is successfully upgraded.
  4. From the Active cluster, go to Events and Alarms > Events and check the details of event code 814
  5. From the active cluster, go to Administration > Upgrade > Upgrade History to verify previous cluster upgrades.
  6. Ensure all APs are online and up-to-date after the upgrade.
  7. Upgrade the standby cluster, and ensure it is successfully upgraded.
  8. Repeat and .
  9. Enable cluster redundancy on the active cluster.
  10. Verify if the active SZ engages the latest cluster redundancy resource-type admin activities.
    If the new SZ version is 5.2.x (including 5.2), the standby cluster will automatically switch to Backup mode after cluster redundancy is enabled. The standby cluster will take some time to restore the configuration of the latest active cluster.
  11. In the standby cluster interface, go to Network > Data and Control Plane > Cluster.
  12. Repeat .
  13. Select the cluster root, and click the Configuration tab.
Parent topic: Geo Redundancy Upgrade Operation Flow