Specifications

CommandCenter SG (Ver 3.1) Frequently asked questions 3/4
Questions Answers
What is the impact on other
usage that would be blocked
through the active usage of
the console port?
A console is generally considered a secure and reliable access path of last
resort. Some UNIX systems allow root login only from the console. For
security reasons, other systems might prevent multiple logins, so that if
the administrator is logged in from the console, other means of access
are denied.
In addition, from the console, the administrator can also disable the network
interfaces when/if necessary to block all other access.
What is the bandwidth usage
per client?
Remote access to a serial console over TCP/IP is about the same level
of network activity as a telnet session. However, it is limited to the
RS232 bandwidth of the console port itself, plus SSL/TCP/IP overhead.
The Raritan Remote Client (RRC) controls remote access to a
KVM console. This application provides tunable bandwidth from
LAN levels down to a level suitable for a remote dial-up user.
Using direct mode on CC-SG the bandwidth usage is between the
CC-SG client and the device, not the CC-SG server.
Specifically what type of
changes can a management
system monitor and alert on?
CC-SG will log user activity (login/logout, connect/disconnect) and
configuration changes at both CC-SG and managed Raritan appliances,
and status changes of the connected appliances. All of the above can be
forwarded to a network management system or enterprise notification
system via SNMP or syslog.
What is the recommended
use of Computer Interface
Modules (CIMs) being
moved / swapped at the
physical level with changes
to the logical database?
Each CIM includes a serial number and a target system name. Raritan
systems devices assume that a CIM remains connected to its named target
when its connection is moved to another switch. This move is automatically
reflected in the system configuration and is propagated to CC-SG. If the
CIM is moved to another server, an administrator must rename the CIM.
How does CC-SG integrate
with Blade Chassis products?
CC-SG can support any device with a KVM or serial interface as a
transparent pass-through. All blade chassis come with one KVM connection
for the management of the blade system. Some blade servers allow KVM
connections on a blade basis through a proprietary add on connector from
the blade server manufacturer. This would allow access and control of the
blade server through Raritan devices. In addition, CC-SG can incorporate
access and power management through embedded cards such as
iLO/RiLOE . Typically, these cards are located on the blade chassis and
control the whole enclosure. CC-SG also provides power management
through power strips connected to Raritan devices. CC-SG can also provide
centralized access to individual blades with RDP, VNC, or SSH.
What options are available
for authentication with
directory services and
security tools, e.g., LDAP,
AD, Radius, etc.?
CommandCenter Secure Gateway permits local authentication as well as
remote authentication.
Supported remote authentication servers include:
• AD
• TACACS+
• RADIUS
• LDAP
Will the current Paragon
solution work with CC-SG?
Raritan has introduced an interface device – Paragon II System Controller
(P2-SC) -- that integrates Raritan’s Paragon II analog Cat5 KVM switches
with CC-SG. To find out more about the Paragon II System Controller go to
www.raritan.info/paragonII