Specifications

APPENDIX G: FAQS 263
Interoperability
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.
To what level is CC-SG
able to integrate with 3rd
party KVM tools, down to
3rd party KVM port level
or simply box level?
3
rd
party KVM switch 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 CC-SG. 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.
Authorization
Can authorization be
achieved via
RADIUS/TACACS/
LDAP?
LDAP and TACACS are used for remote authentication only,
not authorization.
User Experience
Regarding console
management via network
port or local serial port (for
example, COM2): What
happens to the logging,
does CC-SG capture local
management or is this lost?
Logging on to CC-SG through the CC-SG console itself is the
same as gaining the root privilege of the operating system
(Linux) upon with CC-SG is running. Syslog will record such
event, but what the user types at the CC-SG console itself will
be lost.