General FAQs

Question

Answer

General

Why would I need CC-SG?

As you deploy more and more data center servers and devices, their management becomes exponentially complex. CC-SG allows a systems administrator or manager to access and manage all servers, equipment, and users from a single device.

Is the status of CC-SG limited by the status of the devices which it proxies?

No. Because CC-SG software resides on a dedicated server, even if a device being proxied by the CC-SG is turned off, you will still be able to access CC-SG.

What do I do if I am unable to add a console/serial port to CC-SG?

Assuming the console/serial device is a Dominion, ensure that the following conditions are met:

- The Dominion device is active.

- The Dominion device has not reached the maximum number of configured user accounts.

How do I access CC-SG from outside a firewall?

 

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

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?

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.

How do I merge the blade server node and the virtual host node if they refer to the same server?

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.

See Also

FAQs

Authentication FAQs

Security FAQs

Accounting FAQs

Performance FAQs

Grouping FAQs

Interoperability FAQs

Authorization FAQs

User Experience FAQs

Licensing FAQs