Raritan COMMANDCENTER 2.20 -, Руководство пользователя

Страница: 148 / 150

136 C
OMMAND
C
ENTER
U
SER
G
UIDE
Q
UESTION
: A
NSWER
:
What is the bandwidth usage
per client? Particularly as they
aggregate up over many
systems. Remote access to a serial console over TCI/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 something suitable for a remote dial-up user.
Grouping
Is it possible to put a given
server in more than one
group? It should be possible. Just as one user can belong to multiple groups,
one device can belong to multiple groups.
Edge port groups are simply boolean expressions of attributes. For
example, a Sun in NYC could be part of Group Sun: "Ostype =
Solaris" and Group New York: "location = NYC"
What impact to other usage
that would be blocked through
the active usage of the console
port, for example, some UNIX
variants not allowing admin
over network interfaces? A console is generally considered a secure and reliable access path of
last resort. Some UNIX systems allow root login only on the console.
For security reasons, other systems might prevent multiple logins, so
that if the administrator is logged in on the console, other access is
denied. Finally, from the console, the administrator can also disable the
network interfaces when/if necessary to block all other access.
Normal command activity on the console has no greater impact than
the equivalent command run from any other interface. However, since
it is not dependent upon the network, a system that is too overloaded to
be able to respond to a network login may still support console login.
So another benefit of console access is trouble-shooting and diagnosis
of system and network problems.
How do you recommend the
issue of CIMs being moved /
swapped at the physical level
with changes to the logical
database? Each CIM includes a serial number and target system name. Our
systems assume that a CIM remains connected to its named target
when its connection is moved between switches. This movement is
automatically reflected in the system configuration and is propagated
to CommandCenter. If, instead, the CIM is moved to another server,
an administrator must rename it.
Interoperability
How does CommandCenter
integrate with Blade Chassis
products? CommandCenter can support any device with a KVM or serial
interface as a transparent pass-through.
To what level is
CommandCenter able to
integrate with 3rd party KVM
tools, down to 3rd party KVM
port level or simply box level? 3
rd
party KVM switches integration is typically done through keyboard
macros when the 3
rd
party KVM vendors do not publicize the
communications protocols for the 3
rd
party KVM switches. Depending
on the capability of the 3
rd
party KVM switches, the tightness of
integration will vary.
How would I mitigate the
restriction of four
simultaneous paths through
any IP-Reach box, including
the roadmap for the potential
8-path box? Currently, the best possible implementation is to aggregate IP-Reach
boxes with CommandCenter. In the future, Raritan plans to increase
simultaneous access paths per box. These plans have yet to complete
development as other projects have taken priority, but we welcome
comments about the market demand and use cases of an 8-path
solution.
Will the current Paragon
boxes work with
CommandCenter? If not, what
is the upgrade path? The CommandCenter V2.0 will work with Paragon that has 3.0 HW
and firmware version 3.2 and above. If older versions exist, they must
be replaced.
Authorization
Can authorization be achieved
via RADIUS/TACACS/
LDAP?
LDAP and TACACS are used for remote authentication only, not
authorization.