Specifications

CHAPTER 13: ADVANCED ADMINISTRATION 183
and active connections, and all status data is replicated between the two nodes. The primary and
secondary nodes in a cluster must be running the same version of software, on the same version
of hardware (G1, V1, or E1). Unless defined by the user, CC-SG will assign a default name to
each cluster node.
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 CC-SG unit will recognize that the Primary
node is not responding and will respond to requests initiated by the Secondary node.
Note: In a cluster configuration, only the Primary CC-SG communicates with CC-NOC.
Whenever a CC-SG becomes primary, it sends its IP address, in addition to the IP address of the
Secondary CC-SG, to CC- NOC.
Create a Cluster
In the event of a failover, the administrator should send an email to all CC-SG users, notifying
them to use the IP address of the new Primary CC-SG node.
Important: It is recommended to backup your configuration on both nodes
before setting up a cluster configuration.
Note: A CC-SG must be running its network ports in Primary/Backup mode in order to be used
for clustering. Clustering will not work with an Active/Active configuration. Please refer to About
Network Setup in this chapter for additional information.
Set Primary CC-SG Node
1. On the Administration menu, click Cluster Configuration.