Secondary (Standby) HySecure Cluster Manager Node Failure

The node can fail because of following reasons:

  1. Host crash because of hardware failure or virtual machine corruption
  2. Network lost from production network

When Secondary HySecure Cluster Manager Node fails, following is the cluster behaviour:

  1. It takes 18 seconds (default value, configuration value) for the primary (active) Cluster Manager host to detect that secondary node is no more available.
  2. There is no change in cluster configuration
  3. There is no impact on user sessions
  4. All user connections handled by the HySecure Gateway module on the failed secondary Cluster Manager node are terminated and user or the application must initiate reconnect of the connection. When Secondary HySecure Cluster Manager is available again (restart, connect back to network), following is the behaviour of the cluster
  5. The Secondary HySecure Cluster node, after reboot or reconnection of network, detects that an Active Cluster Manager is already available in the cluster
  6. The secondary node continues to remain standby Cluster Manager.
  7. The Secondary node receives the updated configuration from primary Cluster Manager
  8. There is no change in cluster configuration
  9. There is no impact on user sessions