Cluster Redundancy
When an active cluster becomes inaccessible for APs, external DPs (vSZ-D and SZ144-D), and ICX switches, a standby cluster restores the latest configuration of the Out-Of-Service (OOS) active cluster, and then takes over all external devices (including APs, external DPs, and ICX switches). The AP or ICX switch capacity is limited by the AP or ICX switch High Availability (HA) licenses on the standby cluster and the services license limits from the failed active cluster. When the active cluster returns to the in-service state, the end user can "rehome" all APs, external DPs, and ICX switches back to the active cluster.
The behavior of the standby cluster changes automatically when there is a configuration change in the following deployment types:
- One-to-one (one active cluster to one
standby cluster) deployment
The standby cluster restores the configuration from the active cluster after the configuration synchronization is completed. The standby cluster is always in backup mode and ready to receive the APs, external DPs, and ICX switches from the out-of-service active cluster.
6.0 updateDuring a system upgrade, the ICX switches from the active cluster may fail over to a standby cluster.To remedy this situation, use the Rehome or Switchover features on the standby cluster to move these ICX switches back to the active cluster.
6.1 updateBy default, the standby cluster will be in Monitor mode and serve the active cluster only when the active cluster is out-of-service.
- Many-to-one (two or three active
clusters to one standby cluster) deployment
The time taken by Standby cluster from detecting Active cluster is out-of-service to it's being ready to serve APs and external-DPs is enhanced.
When upgrading from SmartZone R3.6.x to SmartZone R5.2 with geo-redundancy enabled, first upgrade the active cluster and then the standby cluster. Once both clusters are upgraded, from the geo-redundancy page of the active cluster, click Sync Now to synchronize the configuration of the active and standby clusters.
6.1
updateStandby Cluster Default Mode When Cluster Redundancy Is
Enabled
When there are multiple clusters, one cluster can be the configuration source cluster, and all other active cluster restores its configuration periodically to be sure the configuration between the clusters are synchronized continually. When the active cluster becomes inaccessible for APs and external DPs (vSZ-D and SZ100-D), they failover to the target active cluster with priority
A single standby cluster serves as a failover option for one or many distributed active clusters. Different AAA servers can be configured on active and standby clusters.
Active-Standby cluster redundancy can be enabled only when matching the following conditions:
- All cluster nodes on both the active and standby clusters must be in service.
- The system version of both clusters must be the same.
- The IP mode must be the same.
- Both clusters must apply the same KSPs on all nodes.
- The control interface of the standby cluster can build a connection to that of the active cluster.
Active-Active cluster redundancy can be enabled only when the source active cluster and target active cluster match the following conditions:
- All the cluster nodes must be in service.
- The system version of both clusters must be the same.
- The model (vSZ-H) must be the same.
- The network interface number must be equal.
- The IP mode must be the same.
- Both cluster must apply the same KSPs on all nodes.
- "Schedule Configuration Sync" can be enabled only in one cluster.
An active cluster can assign only one standby cluster, and the standby cluster can monitor up to three active clusters.
Each cluster in Active-Active redundancy can configure up to three target clusters. "Schedule Configuration Sync" can be enabled only in one cluster.
It is highly recommended that you update the configuration from the source cluster until it is eventually synchronized.
-
An active cluster works as a normal cluster and the standby cluster is in read-only mode. Only a few configurations can be configured on a standby cluster.
-
All clusters work as a normal clusters.
-
An active cluster can back up its configuration and periodically transfer it to a standby cluster if a scheduled task is configured.
-
A source active cluster can back up its configuration and periodically transfer it to a target active cluster if a scheduled task is configured.
-
SME to verify if rows 1 and 4 can be removed? Additionally, confirm if references to 5.1.0 can be removed and ensure there are no changes to the table content.
Beginning with SmartZone 5.1.0, the implementations in the following table are allowed for Active-Standby mode.
SZ300 (Active) SZ300 (Standby) LBO and Tunneled WLANs supported vSZ-H (Active) vSZ-H (Standby) LBO only vSZ-H/vSZ-D (Active) vSZ-H/vSZ-D (Standby) LBO and Tunneled WLANs supported SZ300 (Active) vSZ-H (Standby) LBO only A standby cluster can be reset as a normal cluster if you set to the factory default after disabling cluster redundancy from the active cluster. Once an Active cluster is set to factory default, it can only be made an Active cluster again either by restoring the entire cluster or by enabling cluster redundancy again. Once a Standby cluster is set to factory default, it can only be made as a Standby cluster again either by restoring the cluster or by clicking “Sync Now” on the active cluster. You can still enable the Active-Standby cluster redundancy again from the active cluster, to set Standby cluster after it has been set to factory default.
A cluster operating in Active-Active mode must run on one of the vSZ-H platforms.
- Active-Standby mode
You must manually sync the license on a standby cluster after it has been set as standby cluster by the active cluster. The standby cluster restores the latest configuration backup files from the out-of-service active cluster, and leverages the license with the active cluster profile, except for the following types of licenses:
- Active-Active mode
Licenses in each active cluster are independent.