Specifications

240 COMMANDCENTER SECURE GATEWAY ADMINISTRATOR GUIDE
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.
Communication Direction Port
Number
Protocol Configurable?
CC-SG → Local Broadcast 10000 UDP no
CC-SG → Remote LAN IP 10000 UDP no
CC-SG ↔ CC-SG 5432 TCP no
CC-SG ↔ CC-SG
8732 TCP
no
CC-SG ↔ CC-SG
3232 TCP
no
Access to Infrastructure Services
The CC-SG can be configured to use several industry-standard services like DHCP, DNS, and
NTP. In order for CC-SG to communicate with these optional servers, these ports and protocols
are used:
PC Clients to CC-SG
PC Clients connect to the CC-SG in one of these three modes:
• Web / Java Applet CC-SG GUI interface
• CC-SG Command Line Interface via SSH
• CC-SG Diagnostic Console
Web access via the CC-SG GUI is the primary means for users and administrators to connect to
CC-SG. The other two modes, CLI and Diagnostic Console, are less frequently used. These
modes require the following networking configuration:
Communication Direction Port
Number
Protocol Configurable?
Client → CC-SG GUI 443 TCP no
Client → CC-SG GUI 80 TCP no
Client → CC-SG GUI 8080 TCP no
Client → CC-CLI SSH 22 TCP yes
Client → CC Diagnostic
Console
23 TCP yes
Communication Direction Port
Number
Protocol Configurable?
DHCP Server → CC-SG 68 UDP no
CC-SG → DHCP Server 67 UDP no
NTP Time Server ↔ CC-SG 123 UDP no
CC-SG → DNS 53 UDP no