User manual

Appendix B: CC-SG and Network Configuration
315
CC-SG and Raritan Devices
A main role of CC-SG is to manage and control Raritan devices, such as
Dominion KX II. Typically, CC-SG communicates with these devices over
a TCP/IP network (local, WAN, or VPN) and both TCP and UDP
protocols are used as follows:
Communication Direction Port Number Protocol Configurable? Details
CC-SG to Local Broadcast 5000 UDP yes heartbeat
CC-SG to Remote LAN IP 5000 UDP yes heartbeat
CC-SG to Raritan Device 5000 TCP yes RDM protocol
RC4/AES-128/AES-
256 encrypted
Raritan Device to CC-SG 5001 UDP no heartbeat
CC-SG to Dominion PX 623
443
UDP no
no
CC-SG to Dominion KXII in
Direct Mode
443 TCP no
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