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

Appendix H: FAQs
Question
To what level is CC-SG able
to integrate with third party
KVM tools, down to third
party KVM port level or
simply box level?
How would I mitigate the
restriction of four
simultaneous paths through
any IP-Reach box, including
the roadmap for the potential
8-path box?
Answer
Third party KVM switch integration is typically done
through keyboard macros when the third party KVM
vendors do not publicize the communications protocols
for the third party KVM switches. Depending on the
capability of the third party KVM switches, the tightness
of integration will vary.
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 FAQs
Question
Authorization
Can authorization be
achieved via
RADIUS/TACACS/LDAP?
Answer
LDAP and TACACS are used for remote authentication
only, not authorization.
User Experience FAQs
Question
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?
Answer
Logging into 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 this event, but what the user types at
the CC-SG console itself will be lost.
312