Setup guide

Page 7 of 10 Dominion KX FAQ
Q. How do I ensure that only
authorized users can access
servers from the local port?
A. Dominion KX offers the very best local port authentication scheme available on the
market: users attempting to use the local port must pass the same level of authentication
as those accessing remotely. This means that:
If you have configured Dominion KX to interact with an external RADIUS,
LDAP, or Active Directory server, users attempting to access the local port
will authenticate against the same server.
If you have configured Dominion KX to be managed by Raritan’s
CommandCenter management appliance, users attempting to access the
local port will authenticate against CommandCenter (which in turn can
also integrate with RADIUS, LDAP, Active Directory, or TACACS [see
CommandCenter data sheet and FAQ for more details]).
In either of the above scenarios, if the external authentication servers are
unavailable, Dominion KX fails-over to its own internal authentication
database.
Dominion KX has its own standalone authentication, enabling instant on,
out-of-the-box installation.
Q. If I use the local port to
change the name of a connect
server, does this change
propagate to remote access
clients as well? Does it
propagate to the optional
CommandCenter appliance?
A. Yes. The local port presentation is identical and completely in sync with remote access
clients, as well as Raritan’s optional CommandCenter management appliance. To be
clear, if you change the name of a server via the Dominion KX on-screen display, this
updates all remote clients and external management servers in real-time.
Q. If I use Dominion KX’s
remote administration tools to
change the name of a
connected server, does that
change propagate to the local
port OSD as well?
A. Yes, if you change the name of a server remotely, or via Raritan’s optional
CommandCenter management appliance, this update immediately affects Dominion KX’s
on-screen display.
Power Control
Q. What type of power control
capabilities does Dominion KX
offer?
A. Because Dominion KX enables you to remotely manage servers; it also incorporates
the critical functionality of hard power control to servers. Instead of using a third-party tool
for power control (likely with lower security and fail-safe capabilities as Dominion KX), you
can use Dominion KX’s fully integrated remote power control.
When remotely connected to an appropriately configured Dominion KX, simply select the
power control options to hard reboot a hung server. Note that a hard reboot provides the
physical equivalent of unplugging the server from the AC power line, and re-inserting the
plug.
Q. Does Dominion KX support
servers with multiple power
supplies? What if each power
supply is connected to a
different power strip?
A. Yes. Dominion KX can be easily configured to support multiple power supplies
connected to multiple power strips.
Q. Does remote power control
require any special server
configuration?
A. Some servers ship with default BIOS settings such that the server does not
restart
after losing and regaining power. See your server user manual for more details.