Blade Server Configuration Guide
Dominion KX II Blade Server Configuration Guide – Release 2.1.10, v1.0
Version: Dominion KX Release 2.1.10
Date: July 9, 2009
Applicable Dominion KX II models:
DKX2-108, DKX2-116, DKX2-132
DKX2-216, DKX2-232
DKX2-416, DKX2-432, DKX2-464
DKX2-832, DKX2-864
Overview:
This guide contains instructions on the configuration of IBM and Dell blade server
chassis KVM and management modules to enable integration with the Dominion KX II
blade server feature introduced in Release 2.1. The guide provides supplemental
information to the Dominion KX II Users Guide featuring screen shots and detailed
instructions.
Contents:
The guide contains instructions and screenshots for configuration of the following blade
server types:
• IBM BladeCenter E or H with Advanced Management Module)
• Dell 1855/1955 with Analog KVM Module
• Dell M1000e with iKVM Module
Related Documents:
Dominion KX II User Guide (Release 2.1.10)
Dominion KX II CIM Guide (Release 2.1.10)
Dominion KX II Release Notes (Release 2.1.10)
Caution:
This guide has been prepared based on specific versions of the IBM and Dell blade
servers, which may differ from the version you may have. Consult the manufacturer
documentation for your particular version for more information.
Proprietary and Confidential
IBM Advanced Management Module Setup
This section describes the configuration required for the IBM BladeCenter Advanced
Management Module to integrate with Raritan’s Dominion KX II.
For the IBM BladeCenter, the Advanced Management Module (AMM) is supported. The older
Management Module has not been certified in this release. The KX II only supports autodiscovery for AMM[1] as the acting primary management module.
The following IBM BladeCenter minimum AMM firmware is recommended:
Management Module Firmware
Main application: BPET36K
Released: 04-22-08
Name: CNETMNUS.PKT
Rev: 54
Under MM Control, access the Login Profiles to verify or create a user account for access from
the Dominion KX II.
Proprietary and Confidential
Certain operations performed via the SSH connection require “Supervisor” (administrator level)
privileges (e.g. setting idle timeout), so the account has to be created accordingly.
Here are some typical errors if Supervisor level control is not provided:
Communication
Error
Communication
Error
Error communicating with 'IBM-H-CHASSIS' connected to port '12' failed to 'failed to set Media Tray', <-7014:User does not have the authority to issue this
command.>.
Error communicating with 'IBM-H-CHASSIS' connected to port '12' failed to 'connect to target', <-7014:User does not have the authority to issue this
command.>.
For example, “new_user” has been assigned a “Supervisor” role.
The login ID can be created by selecting a login id that is currently “not used”, and can
subsequently be edited by selecting it.
Proprietary and Confidential
Proprietary and Confidential
Under Network Protocols, ensure that SSH Server is Enabled. SSH will be used to access the
command line interface to control blade chassis operations
The Administrative Management Module firmware version can be verified by accessing Service
Tools > AMM Service Data.
Proprietary and Confidential