Raritan Engineering Command Center CC-SG ユーザーズマニュアル
A
PPENDIX B
:
CC
-
SG AND NETWORK CONFIGURATION
231
CC-SG Communication Channels
The communication channels are partitioned as follows:
• CC-SG ↔ Raritan Devices
• CC-SG ↔ Raritan Devices
• CC-SG ↔ CC-SG Clustering (optional)
• CC-SG ↔ Infrastructure Services
• Clients ↔ CC-SG
• Clients ↔ CC-SG
• Clients ↔ Targets (Direct Mode)
• Clients ↔ Targets (Proxy Mode)
• Clients ↔ Targets (In-Band)
• CC-SG ↔ CC-NOC
• Clients ↔ Targets (In-Band)
• CC-SG ↔ CC-NOC
For each communication channel, the tables in the sections that follow:
• Represents the symbolic IP Addresses used by the communicating parties. These addresses
• Represents the symbolic IP Addresses used by the communicating parties. These addresses
have to be allowed over any communication path between the entities.
• Indicates the Direction in which the communication is initiated. This may be important for
your particular site policies. For a given CC-SG role, the path between the corresponding
communicating parties must be available and for any alternate re-route paths that might be used
in the case of a network outage.
communicating parties must be available and for any alternate re-route paths that might be used
in the case of a network outage.
• Provides the Port Number and Protocol used by CC-SG.
• States the Purpose of the port.
• Indicates if the port is Configurable, which means the GUI or Diagnostic Console provides a
• Indicates if the port is Configurable, which means the GUI or Diagnostic Console provides a
field where you can change the port number to a different value from the default listed due to
conflicts with other applications on the network or for security reasons.
conflicts with other applications on the network or for security reasons.
CC-SG and Raritan Devices
A main role of CC-SG is to manage and control Raritan devices (for example, Dominion KX,
KSX, etc.). 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:
KSX, etc.). 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
Number
Protocol
Purpose
Configurable?
CC-SG → Local Broadcast
5000
UDP
Device
Discovery
Discovery
yes
CC-SG → Remote LAN IP
5000
UDP
Device
Discovery
Discovery
yes
CC-SG → Raritan Device
5000
TCP
Device
Control
Control
yes
Raritan Device → CC-SG
5001
UDP
Device
Events
Events
no
CC-SG Clustering
When the optional CC-SG clustering feature is used (that is, two CC-SGs are inter-connected and
function as one unit), the following ports must be available for the inter-connecting sub-
networks. {If the optional clustering feature is not used, none of these ports need to be made
available in the network.}
function as one unit), the following ports must be available for the inter-connecting sub-
networks. {If the optional clustering feature is not used, none of these ports need to be made
available in the network.}