Raritan Dominion KX II User Manual page 187

Hide thumbs Also See for Dominion KX II:
Table of Contents

Advertisement

Chapter 8: Device Management
178
When a new blade server is added to the chassis.
When an existing blade server is removed from the chassis.
Note: In the case of IBM Blade Center Models E and H, the KX II only
supports auto-discovery for AMM[1] as the acting primary management
module.
The use of hot key sequences to switch KVM access to a blade chassis
is also supported. For blade chassis that allow users to select a hot key
sequence, those options will be provided on the Port Configuration page.
For blade chassis that come with predefined hot key sequences, those
sequences will be prepopulated on the Port Configuration page once the
blade chassis is selected. For example, the default hot key sequence to
switch KVM access to an IBM BladeCenter H is NumLock + NumLock +
SlotNumber, so this hot key sequence is applied by default when IBM
BladeCenter H is selected during the configuration. See your blade
chassis documentation for hot key sequence information.
You are able to configure the connection to a blade chassis web browser
interface if one is available. At the chassis level, up to four links can be
defined. The first link is reserved for connection to the blade chassis
administrative module GUI. For example, this link may be used by
technical support to quickly verify a chassis configuration.
Blade chassis can be managed from the Virtual KVM Client (VKC), the
Active KVM Client (AKC), Raritan's Multi-Platform Client (MPC), and CC-
SG. Managing blade severs via VKC, AKC and MPC is the same as
managing standard target servers. See Working with Target Servers
(on page 41) and the CC-SG Administrators Guide for more
information. Any changes made to the blade chassis configuration in will
be propagated to these client applications.
Important: When the CIM connecting the blade chassis to the
Dominion device is powered down or disconnected from the
Dominion device, all established connections to the blade chassis
will be dropped. When the CIM is reconnected or powered up you
will need to re-establish the connection(s).
Important: If you move a blade chassis from one Dominion device
port to another Dominion device port, interfaces that were added to
the blade chassis node in CC-SG will be lost in CC-SG. All other
information will be retained.

Advertisement

Table of Contents
loading

Table of Contents