CC-SG Clustering

When the optional CC-SG clustering feature is used, the following ports must be available for the inter-connecting sub-networks. If the optional clustering feature is not used, none of these ports has to be open.

Each CC-SG in the cluster may be on a separate LAN. However, the inter-connection between the units should be very reliable and not prone to periods of congestion.

Several TCP/IP connections are maintained and initiated by the Primary to the Backup in a CC-SG cluster. These connections may be idle for extended periods of time, but they are necessary for the cluster to operate.

Ensure that all CC-SG to CC-SG cluster connections over VPN or firewalls do not time out or become blocked. Timing out these connections will cause the cluster to fail.

Communication Direction

Port Number

Protocol

Configurable?

Details

CC-SG to Local Broadcast

10000

UDP

no

heartbeat

CC-SG to Remote LAN IP

10000

UDP

no

heartbeat

CC-SG to CC-SG

5432

TCP

no

From HA-JDBC on Primary to Backup PostgreSQL DB server.

Not encrypted.

CC-SG to CC-SG

8732

TCP

no

Primary-Backup server sync clustering control data exchange.

MD5 encrypted.

CC-SG to CC-SG

3232

TCP

no

Primary-Backup SNMP sync configuration changes forwarding.

Not encrypted.

See Also

CC-SG Communication Channels

CC-SG and Raritan Devices

Access to Infrastructure Services

PC Clients to CC-SG

PC Clients to Nodes

CC-SG and Client for IPMI, iLO/RILOE, DRAC, RSA

CC-SG and SNMP

CC-SG Internal Ports

CC-SG Access via NAT-enabled Firewall

RDP Access to Nodes

VNC Access to Nodes

SSH Access to Nodes

Remote System Monitoring Port