|
|
|
|
|
A CC-SG cluster uses two CC-SG nodes, one Primary node and one Secondary node, for backup security in case of Primary node failure. Both nodes share common data for active users and active connections, and all status data is replicated between the two nodes.
Devices in a CC-SG cluster must be aware of the IP of the Primary CC-SG node in order to be able to notify the Primary node of status change events. If the Primary node fails, the Secondary node immediately assumes all Primary node functionality. This requires initialization of the CC-SG application and user sessions and all existing sessions originating on the Primary CC-SG node will terminate. The devices connected to the Primary node will recognize that the Primary node is not responding and will respond to requests initiated by the Secondary node.
Note: When accessing CC-SG using the thick client, you will not be redirected to the backup node automatically if the primary node fails. You must enter the IP address of the backup node manually for thick client access.