Upgrading HySecure Cluster

Follow the sequence below to upgrade the HySecure cluster

1. Upgrade the HySecure Access Server node
2. Upgrade the HySecure Standby Config node
3. Upgrade the HySecure Active Config node

Important

It is recommended to upgrade the HySecure Gateway using the method outlined in the respective release notes, as it ensures a controlled, downtime-based upgrade. Use this alternative method only when a full downtime is not feasible.

Scenario	Impact/Behavior
Upgrade HySecure Access Server Node	The load on this HySecure Gateway node is temporarily disrupted and redistributed to other gateway nodes in the cluster. The cluster status remains unaffected. Active user connections to this node will be disconnected, but users will not need to re-login.
Upgrade Standby Config Node	The status of the cluster remains unchanged. If the HySecure Gateway is active on this node, the load will be disrupted and redistributed to other gateway nodes within the cluster. Active user connections to this node will be disconnected, but users will not need to re-login.
Upgrade HySecure Active Config Node	A cluster failover may occur, causing a temporary delay as connections are rerouted from the active node to the standby node, which then assumes the active role. The load will be redistributed across other nodes. Active user connections to the affected node will be disconnected, and new sessions initiated during the upgrade may fail, requiring users to log in again. Additionally, any configuration changes made on the active node will not be preserved.