CommandCenter Secure Gateway - Admin Guide - Version ... - Raritan

Appendix H: FAQs
Question
How will the Windows desktop
be supported in the future?
What are some design
guidelines for large-scale
systems? Any constraints or
assumptions?
Will CC-SG auto-detect and
update the blade chassis
configuration when I move the
blade chassis from one KX2
port to another KX2 port?
How to merge the blade
server node and the virtual
host node if they refer to the
same server?
Answer
Accessing CC-SG from outside the firewall can be
achieved by configuring the right ports on the
firewall. The following ports are standard ports:
80: for HTTP access via web browser
443: for HTTPS access via web browser
8080: for CC-SG server operations
2400: for Proxy mode connections
5001: for IPR/DKSX/DKX/ P2-SC event notification
If there is firewall between two cluster nodes, the
following ports should be opened for cluster to be
worked properly:
8732: for cluster nodes heartbeat
5432: for cluster nodes DB replication
Raritan provides two models for server scalability:
the datacenter model and the network model.
The datacenter model uses Paragon to scale to
thousands of systems in a single datacenter. This is
the most effective and cost-efficient way to scale a
single location. It also supports the network model
with IP-Reach and the IP User Station (UST-IP).
The network model scales through use of the
TCP/IP network and aggregates access through
CC-SG, so users don't have to know IP addresses
or the topology of access devices. It also provides
the convenience of single sign-on.
CC-SG does not auto-detect and update the blade
chassis configuration when you move it to another
KX2 port or device. The configuration is lost so you
must configure the blade chassis in CC-SG once
again.
You should configure the Virtualization feature prior
to configuring the blade slots. When configuring the
blade slot, enter the same name as the virtual host
node, and choose to add this interface to the
existing node when a message appears.
307