IBM BLADE console

BladeCenter Advanced Management ModuleBladeCenter T Advanced Management Module

Command-Line Interface Reference Guide

��

BladeCenter Advanced Management ModuleBladeCenter T Advanced Management Module

Command-Line Interface Reference Guide

��

Note: Before using this information and the product it supports, read the general information in “Getting help andtechnical assistance,” on page 475, “Notices” on page 479, the Warranty Information document, and the Safety Information andEnvironmental Notices and User Guide documents on the IBM Documentation CD.

Twenty-second Edition (February 2011)

© Copyright IBM Corporation 2011.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Chapter 1. Introduction . . . . . . . . 1Before you begin . . . . . . . . . . . . . 2Accessibility features for the BladeCentermanagement module . . . . . . . . . . . 2

Chapter 2. Using the command-lineinterface . . . . . . . . . . . . . . 5Command-line interface guidelines . . . . . . . 5Selecting the command target. . . . . . . . . 6Commands and user authority . . . . . . . . 8Cabling the management module . . . . . . . 12

Networked connection. . . . . . . . . . 13Direct connection . . . . . . . . . . . 13Serial connection . . . . . . . . . . . 14

Starting the command-line interface . . . . . . 14IPv6 addressing for initial connection. . . . . 15Telnet connection . . . . . . . . . . . 16Serial connection . . . . . . . . . . . 17Secure Shell (SSH) connection . . . . . . . 18

BladeCenter unit configuration . . . . . . . . 20Configuring the management module . . . . . 21Starting an SOL session . . . . . . . . . . 22Ending an SOL session . . . . . . . . . . 23

Chapter 3. Command reference . . . . 25Alphabetic command list . . . . . . . . . . 25Command list by function . . . . . . . . . 27Command syntax . . . . . . . . . . . . 29

accseccfg command. . . . . . . . . . . 30advfailover command . . . . . . . . . . 40airfilter command (BladeCenter S only) . . . . 42alarm command (BladeCenter T and HT only). . 43alertcfg command . . . . . . . . . . . 51alertentries command . . . . . . . . . . 53autoftp command . . . . . . . . . . . 60baydata command . . . . . . . . . . . 63bofm command . . . . . . . . . . . . 66boot command . . . . . . . . . . . . 72bootmode command . . . . . . . . . . 74bootseq command . . . . . . . . . . . 75buildidcfg command . . . . . . . . . . 80chconfig command . . . . . . . . . . . 87chlog command . . . . . . . . . . . . 93chmanual command . . . . . . . . . . 95cin command . . . . . . . . . . . . . 97cinstatus command . . . . . . . . . . 102clear command . . . . . . . . . . . . 103clearlog command . . . . . . . . . . . 105clock command. . . . . . . . . . . . 106config command . . . . . . . . . . . 111console command . . . . . . . . . . . 115dhcpinfo command . . . . . . . . . . 117displaylog command . . . . . . . . . . 119displaysd command . . . . . . . . . . 124dns command . . . . . . . . . . . . 126

env (environment) command . . . . . . . 131ethoverusb command. . . . . . . . . . 137eventinfo command . . . . . . . . . . 138events command . . . . . . . . . . . 140exit command . . . . . . . . . . . . 143feature command . . . . . . . . . . . 144files command . . . . . . . . . . . . 147fuelg command. . . . . . . . . . . . 149groups command . . . . . . . . . . . 159health command . . . . . . . . . . . 163help command . . . . . . . . . . . . 166history command . . . . . . . . . . . 168identify (location LED) command . . . . . 169ifconfig command . . . . . . . . . . . 171info (configuration information) command . . 203iocomp command . . . . . . . . . . . 206kvm (keyboard, video, mouse) command . . . 208ldapcfg command . . . . . . . . . . . 210led command . . . . . . . . . . . . 220list (system physical configuration) command 225mcad command . . . . . . . . . . . 227modactlog command . . . . . . . . . . 228monalerts command . . . . . . . . . . 229mt (media tray) command . . . . . . . . 239nat command . . . . . . . . . . . . 241ntp (network time protocol) command . . . . 245ping command . . . . . . . . . . . . 248pmpolicy command . . . . . . . . . . 251portcfg command . . . . . . . . . . . 253ports command. . . . . . . . . . . . 255power command . . . . . . . . . . . 272rdoc command . . . . . . . . . . . . 278read command . . . . . . . . . . . . 280remotechassis command . . . . . . . . . 283reset command . . . . . . . . . . . . 286scale command . . . . . . . . . . . . 291sddump command . . . . . . . . . . 299sdemail command . . . . . . . . . . . 301security command. . . . . . . . . . . 303service command . . . . . . . . . . . 304shutdown command . . . . . . . . . . 306slp command . . . . . . . . . . . . 307smtp command. . . . . . . . . . . . 309snmp command . . . . . . . . . . . 312sol (serial over LAN) command . . . . . . 328sshcfg command . . . . . . . . . . . 335sslcfg command . . . . . . . . . . . 337syslog command . . . . . . . . . . . 347tcpcmdmode command . . . . . . . . . 351telnetcfg (Telnet configuration) command . . . 354temps command . . . . . . . . . . . 355trespass command. . . . . . . . . . . 356uicfg command. . . . . . . . . . . . 359update (update firmware) command . . . . 363uplink (management module failover) command 373users command . . . . . . . . . . . 377

© Copyright IBM Corp. 2011 iii

volts command . . . . . . . . . . . . 400write command . . . . . . . . . . . 401zonecfg command . . . . . . . . . . . 403

Chapter 4. Error messages . . . . . 407Common errors . . . . . . . . . . . . 409accseccfg command errors . . . . . . . . . 411advfailover command errors . . . . . . . . 412alarm command errors . . . . . . . . . . 413alertcfg command errors. . . . . . . . . . 414alertentries command errors . . . . . . . . 414autoftp command errors . . . . . . . . . . 415baydata command errors . . . . . . . . . 415bofm command errors . . . . . . . . . . 416boot command errors. . . . . . . . . . . 417bootmode command errors . . . . . . . . . 417bootseq command errors . . . . . . . . . 418buildidcfg command errors . . . . . . . . . 418chconfig command errors . . . . . . . . . 419chlog command errors . . . . . . . . . . 420chmanual command errors . . . . . . . . . 421cin command errors . . . . . . . . . . . 421clear command errors . . . . . . . . . . 423clearlog command errors . . . . . . . . . 423clock command errors . . . . . . . . . . 423config command errors . . . . . . . . . . 424console command errors. . . . . . . . . . 425dhcpinfo command errors . . . . . . . . . 426displaylog command errors. . . . . . . . . 426displaysd command errors . . . . . . . . . 427dns command errors . . . . . . . . . . . 428env command errors . . . . . . . . . . . 428ethoverusb command errors . . . . . . . . 428eventinfo command errors . . . . . . . . . 429events command errors . . . . . . . . . . 429exit command errors . . . . . . . . . . . 430feature command errors . . . . . . . . . . 430files command errors . . . . . . . . . . . 432fuelg command errors . . . . . . . . . . 433groups command errors . . . . . . . . . . 436health command errors . . . . . . . . . . 436help command errors. . . . . . . . . . . 437history command errors . . . . . . . . . . 437identify command errors . . . . . . . . . 437ifconfig command errors . . . . . . . . . 438info command errors . . . . . . . . . . . 442iocomp command errors. . . . . . . . . . 443kvm command errors. . . . . . . . . . . 443ldapcfg command errors. . . . . . . . . . 443led command errors . . . . . . . . . . . 444list command errors . . . . . . . . . . . 445mcad command errors . . . . . . . . . . 445modactlog command errors . . . . . . . . 445monalerts command errors . . . . . . . . . 445monalertsleg command errors . . . . . . . . 446mt command errors . . . . . . . . . . . 446nat command errors . . . . . . . . . . . 446ntp command errors . . . . . . . . . . . 447ping command errors . . . . . . . . . . 447pmpolicy command errors . . . . . . . . . 448portcfg command errors . . . . . . . . . . 448

ports command errors . . . . . . . . . . 448power command errors . . . . . . . . . . 450rdoc command errors. . . . . . . . . . . 450read command errors. . . . . . . . . . . 451remotechassis command errors . . . . . . . 452reset command errors . . . . . . . . . . 452scale command errors . . . . . . . . . . 453sddump command errors . . . . . . . . . 454sdemail command errors . . . . . . . . . 454security command errors . . . . . . . . . 455service command errors . . . . . . . . . . 455shutdown command errors . . . . . . . . . 455slp command errors . . . . . . . . . . . 455smtp command errors . . . . . . . . . . 455snmp command errors . . . . . . . . . . 456sol command errors . . . . . . . . . . . 457sshcfg command errors . . . . . . . . . . 458sslcfg command errors . . . . . . . . . . 459syslog command errors . . . . . . . . . . 461tcpcmdmode command errors . . . . . . . . 462telnetcfg command errors . . . . . . . . . 462temps command errors . . . . . . . . . . 463thres command errors . . . . . . . . . . 463trespass command errors . . . . . . . . . 463uicfg command errors . . . . . . . . . . 464update command errors . . . . . . . . . . 465uplink command errors . . . . . . . . . . 467users command errors . . . . . . . . . . 468volts command errors . . . . . . . . . . 472write command errors . . . . . . . . . . 472zonecfg command errors . . . . . . . . . 473

Appendix. Getting help and technicalassistance. . . . . . . . . . . . . 475Before you call . . . . . . . . . . . . . 475Using the documentation . . . . . . . . . 476Getting help and information from the World WideWeb . . . . . . . . . . . . . . . . 476Software service and support . . . . . . . . 476Hardware service and support . . . . . . . 476IBM Taiwan product service . . . . . . . . 477

Notices . . . . . . . . . . . . . . 479Trademarks . . . . . . . . . . . . . . 479Important notes . . . . . . . . . . . . 480Particulate contamination . . . . . . . . . 481Documentation format . . . . . . . . . . 482Electronic emission notices . . . . . . . . . 482

Federal Communications Commission (FCC)statement. . . . . . . . . . . . . . 482Industry Canada Class A emission compliancestatement. . . . . . . . . . . . . . 483Avis de conformité à la réglementationd'Industrie Canada . . . . . . . . . . 483Australia and New Zealand Class A statement 483European Union EMC Directive conformancestatement. . . . . . . . . . . . . . 483Germany Class A statement . . . . . . . 483Japan VCCI Class A statement. . . . . . . 484

iv IBM BladeCenter Advanced Management Module: Command-Line Interface Reference Guide

Korea Communications Commission (KCC)statement. . . . . . . . . . . . . . 485Russia Electromagnetic Interference (EMI) ClassA statement . . . . . . . . . . . . . 485People's Republic of China Class A electronicemission statement . . . . . . . . . . 485

Taiwan Class A compliance statement . . . . 485

Index . . . . . . . . . . . . . . . 487

Contents v

vi IBM BladeCenter Advanced Management Module: Command-Line Interface Reference Guide

Chapter 1. Introduction

This topic provides a short introduction to the BladeCenter advanced managementmodule command-line interface. Information about the command-line interface formanagement modules other than the advanced management module is in aseparate document.

The IBM® BladeCenter® advanced management-module command-line interface(CLI) provides direct access to BladeCenter management functions as an alternativeto using the web-based user interface. Using the command-line interface, you canissue commands to control the power and configuration of the managementmodule and other components that are in a BladeCenter unit.

All IBM BladeCenter units are referred to throughout this document as theBladeCenter unit. All management modules are referred to throughout thisdocument as the management module. Unless otherwise noted, all commands canbe run on all management-module and BladeCenter unit types.v When a command is labeled "BladeCenter H only", it can run on all types of

BladeCenter H units (BladeCenter H and BladeCenter HT).v When a command is labeled "BladeCenter T only", it can run on all types of

BladeCenter T units (BladeCenter T and BladeCenter HT).v When a command is labeled "Blade Center S only", it can run on all types of

BladeCenter S units.

The command-line interface also provides access to the text-console commandprompt on each blade server through a serial over LAN (SOL) connection. See theIBM BladeCenter Serial Over LAN Setup Guide for information about SOL and setupinstructions.

You access the management-module CLI by establishing a Telnet connection to theIP address of the management module or through a Secure Shell (SSH) connection.You can initiate connections from the client system by using standard remotecommunication software; no special programs are required. Users are authenticatedby the management module before they can issue commands. You enter commandsone at a time; however, you can use command scripting to enter multiplecommands. The interface does not support keyboard shortcuts, except for thespecial key sequence, Esc (, that terminates an SOL session.

The most recent versions of all BladeCenter documentation are available fromhttp://www.ibm.com/systems/support/.

IBM Redbooks publications are developed and published by the IBM InternationalTechnical Support Organization (ITSO). The ITSO develops and delivers skills,technical know-how, and materials to IBM technical professionals, BusinessPartners, clients, and the marketplace in general. For IBM Redbooks publicationsfor your BladeCenter, go to http://www.redbooks.ibm.com/portals/bladecenter.

© Copyright IBM Corp. 2011 1

http://www.ibm.com/systems/support/

http://www.redbooks.ibm.com/portals/bladecenter

Before you beginThe following hardware and software is required for the command-line interface:

Hardware:

No special hardware is required to use the management-modulecommand-line interface.

To use the SOL feature, an Ethernet I/O module that supports SOL mustbe installed in I/O-module bay 1. You can use the console command tocontrol a blade server through SOL only on blade server types that supportSOL functionality and have an integrated service processor firmware levelof version 1.00 or later. See the IBM BladeCenter Serial Over LAN SetupGuide for information.

Firmware:

Make sure that you are using the latest versions of device drivers,firmware, and BIOS code for your blade server, management module, andother BladeCenter components. Go to http://www.ibm.com/systems/support/ for the latest information about upgrading the device drivers,firmware, and BIOS code for BladeCenter components. The latestinstructions are in the documentation that comes with the updates.

The management-module CLI is supported by BladeCentermanagement-module firmware level version 1.08 or later. All versions ofBladeCenter T management-module firmware and advanced managementmodule firmware support the command-line interface. The SOL feature hasadditional firmware requirements. See the IBM BladeCenter Serial Over LANSetup Guide for information.

Accessibility features for the BladeCenter management moduleAccessibility features help users who have a disability, such as restricted mobilityor limited vision, to use information technology products successfully.

Accessibility features

Accessibility for the BladeCenter management module interface is providedthrough the command-line interface. The remote control video feed is notaccessible to a screen reader.

The BladeCenter Information Center is accessibility-enabled. The accessibilityfeatures of the information center include:v Keyboard-only operationv Interfaces that are commonly used by screen readers. (The Java access bridge

must be installed to make Java applets available to the JAWS screen reader.)v The attachment of alternative input and output devices

Keyboard navigation

This product uses standard Microsoft® Windows® navigation keys.

Related accessibility information

You can view the publications for IBM BladeCenter in Adobe® Portable DocumentFormat (PDF) using the Adobe Acrobat® Reader. The PDFs are provided on a CD

2 IBM BladeCenter Advanced Management Module: Command-Line Interface Reference Guide



that is packaged with the product, or you can access them through the IBMBladeCenter Information Center.

IBM and accessibility

See the IBM Human Ability and Accessibility Center for more information aboutthe commitment that IBM has to accessibility.

Chapter 1. Introduction 3

http://www.ibm.com/able


Chapter 2. Using the command-line interface

This topic tells you how to use the management module command-line interface.

The IBM management-module command-line interface (CLI) provides a convenientmethod for entering commands that manage and monitor BladeCentercomponents. This chapter contains the following information about using thecommand-line interface:v “Command-line interface guidelines”v “Selecting the command target” on page 6v “Commands and user authority” on page 8v “Cabling the management module” on page 12v “Starting the command-line interface” on page 14v “BladeCenter unit configuration” on page 20v “Configuring the management module” on page 21v “Starting an SOL session” on page 22v “Ending an SOL session” on page 23

See Chapter 3, “Command reference,” on page 25 for detailed information aboutcommands that are used to monitor and control BladeCenter components.Command-line interface error messages are in Chapter 4, “Error messages,” onpage 407. See the IBM BladeCenter Serial Over LAN Setup Guide for SOL setupinstructions and the documentation for your operating system for informationabout commands that you can enter through an SOL connection.

Command-line interface guidelinesThis topic gives general guidelines for using the BladeCenter command-lineinterface.

All commands have the following basic structure:

command -option parameter

Some commands do not require options and some command options do notrequire parameters. You can add multiple options to a command on one line toavoid repeating the same command. Options that display a value and options thatset a value must not be used together in the same command. The followingexamples illustrate valid command option syntax:v commandv command -option_setv command -option_set parameterv command -option1_set parameter -option2_set parameter

The information for each option is returned in the order in which it was enteredand is displayed on separate lines.


Observe the following general guidelines when you use the command-lineinterface:v Case sensitivity

All commands, command options, and predefined command option parametersare case sensitive.

Note: If you receive a Command not found error, make sure that you are typingthe command in the correct case. For a list of valid commands, type help or ?.

v Data typesThe ip_address data type uses a predefined formatted string of xxx.xxx.xxx.xxx,where xxx is a number from 0 to 255.

v Delimiters– Options are delimited with a minus sign.– In a command that requires parameters, a single space is expected between an

option and its parameter. Any additional spaces are ignored.v Output format

– Failed commands generate failure messages.– Successful commands are indicated by the message OK or by the display of

command results.v Strings

– Strings that contain spaces must be enclosed in quotation marks, for example,snmp -cn "John B. Doe".

– String parameters can be mixed case.v The help command lists all commands and a brief description of each command.

You can also issue the help command by typing ?. Adding the -h parameter toany command displays its syntax.

v You can use the Up Arrow and Down Arrow keys in the command-line interfaceto access the last eight commands that you entered.

Selecting the command targetThis topic describes command targets and the persistent command environment.

You can use the command-line interface to target commands to the managementmodule or to other devices in the BladeCenter unit. The command-line promptindicates the persistent command environment: the environment in whichcommands are entered unless they are otherwise redirected. When a command-lineinterface session is started, the persistent command environment is system; thisindicates that commands are being directed to the BladeCenter unit.

Command targets are specified hierarchically, as shown in the followingillustration. This illustration shows command targets for all management moduleand BladeCenter unit types.


You can change the persistent command environment for the remainder of acommand-line interface session by using the env command (see “env(environment) command” on page 131). When you list the target as a commandattribute by using the -T option, you change the target environment for thecommand that you are entering, temporarily overriding the persistent commandenvironment. You can specify target environments by using the full path name orby using a partial path name that is based on the persistent commandenvironment. Full path names always begin with "system". The levels in a pathname are divided using a colon (:).

For example:v Use the -T system:mm[1] option to redirect a command to the management

module in bay 1.v Use the -T system:switch[1] option to redirect a command to the I/O (switch)

module in I/O (switch) module bay 1.v Use the -T sp option to redirect a command to the integrated service processor

in the blade server in blade server bay 3, when the persistent commandenvironment is set to the blade server in blade server bay 3.

Most management-module commands must be directed to the primarymanagement module. If only one management module is installed in theBladeCenter unit, it always acts as the primary management module. Eithermanagement module can function as the primary management module; however,only one management module can be primary at one time. You can determine

BladeCenterunit

system

Power module

power[x]where x = 1 to n

Media tray

mt[x]where x = 1 to 2

Blade server

blade[x]where x = 1 to n

Managementmodule

mm[x]where x = 1 to 2

I/O module(switch module)

switch[x]where x = 1 to n

Blower

blower[x]where x = 1 to n

Alarm panelmodule

tap (BladeCenter HTonly)

Multiplexerexpansion module

mux[x]where x = 1 to 2(BladeCenter HTonly)

Network clockmodule

ncc[x]where x = 1 to 2(BladeCenter HTonly)Storage module

storage[x]where x = 1 to n(BladeCenter S only)

Integrated systemmanagement

processor(service

processor)

sp

Microprocessor

cpu[x]where x = 1 to n

Memory

memory[x

]where x = 1 to n(AMM only)

Management card

mgmtcrd(AMM only)

Storageexpansion unit

be[x]where x = 1 to n

High-speedexpansion card

hsdc (not AMM)hsec[x] (AMM only)where x = 1 to n

Concurrent KVMfeature card

ckvm (AMM only)

Double-widthblade servermezzanine

sb (AMM only)

I/O expansion card

dtr[x] (not AMM)exp[x] (AMM only)where x = 1 to n

Battery BackupUnit

bbu[x]where x = 1 to n(BladeCenter S only)

Disk Drive

disk[x]where x = 1 to n

only)(BladeCenter S

High-speedexpansion card

hsec[x]

(AMM only)where x = 1 to n

I/O expansioncard

exp[x]

(AMM only)where x = 1 to n

Chapter 2. Using the command-line interface 7

which management module is acting as the primary management module by usingthe list command (see “list (system physical configuration) command” on page225).

Commands and user authorityThis topic lists command-line interface commands and the user authority levelsneeded to run them.

Some commands in the command-line interface can be executed only by users whoare assigned a required level of authority. Users with Supervisor commandauthority can execute all commands. Commands that display information do notrequire any special command authority; however, users can be assigned restrictedread-only access, as follows:v Users with Operator command authority can execute all commands that display

information.v Users with Chassis Operator custom command authority can execute commands

that display information about the common BladeCenter unit components.v Users with Blade Operator custom command authority can execute commands

that display information about the blade servers.v Users with Switch Operator custom command authority can execute commands

that display information about the I/O modules.

Table 1 on page 9 shows the command-line interface commands and their requiredauthority levels. To use the table, observe the following guidelines:v The commands in this table apply only to the command variants that set values

or cause an action and require a special command authority: display variants ofthe commands do not require any special command authority.

v If a command requires only one command authority at a time, each of theapplicable command authorities is indicated by a dot (v). If a command requiresa combination of two or more command authorities, the applicable commandauthorities are indicate by L or ‡. For example, the boot -c command isavailable to a user with the Supervisor command authority and to a user withboth the Blade Administration and Blade Remote Presence command authorities.

Important: Command authority definitions might change between firmwareversions. Make sure that the command authority level for each user is correct afteryou update the management-module firmware.

Notes:

1. LDAP (lightweight directory access protocol) authority levels are not supportedby management modules other than the advanced management module.

2. LDAP authority levels are not supported by the management-module webinterface.

3. To use the LDAP authority levels, you must make sure that the version ofLDAP security that is used by the management module is set to v2 (enhancedrole-based security model). See “ldapcfg command” on page 210 forinformation.


Table 1. Command authority relationships

Command

Authority

Su

per

viso

r

Ch

assi

sA

ccou

nt

Man

agem

ent

Ch

assi

sL

ogM

anag

emen

t

Ch

assi

sA

dm

inis

trat

ion

Ch

assi

sC

onfi

gura

tion

Bla

de

Ad

min

istr

atio

n

Bla

de

Con

figu

rati

on

Bla

de

Rem

ote

Pre

sen

ce

I/O

Mod

ule

Ad

min

istr

atio

n

I/O

Mod

ule

Con

figu

rati

on

accseccfg v v

advfailover v v

airfilter v v v v v

alarm -c, -r, -s v v v v

alarm -q -g v v v

alertcfg v v

alertentries v v

alertentries -test v v v v v v v v v

autoftp v v

baydata v v

bofm v v

boot(blade server)

v v

boot -c v L L

boot -p v v

bootmode v v

bootseq v v

buildidcfg v v v v

chconfig v v

chlog v v

chmanual v v v v v v v v v v

cin v L L

clear v L L ‡ ‡

clearlog v v

clock v v

config(blade server)

v v

config(management module orBladeCenter unit)

v v

console v v

displaylog -lse v v

dns v v


Table 1. Command authority relationships (continued)

Command

Authority

Su

per

viso

r

Ch

assi

sA

ccou

nt

Man

agem

ent

Ch

assi

sL

ogM

anag

emen

t

Ch

assi

sA

dm

inis

trat

ion

Ch

assi

sC

onfi

gura

tion

Bla

de

Ad

min

istr

atio

n

Bla

de

Con

figu

rati

on

Bla

de

Rem

ote

Pre

sen

ce

I/O

Mod

ule

Ad

min

istr

atio

n

I/O

Mod

ule

Con

figu

rati

on

ethoverusb v v

events -che v v v v v v v v v v

events -che -add -rm v v

feature v v

files -d v v v v v v v

fuelg v v

groups v v

identify v v v

ifconfig (blade server target) v v

ifconfig (blade server ISMP,management module, andsystem targets)

v v

ifconfig (I/O module target) v v

ifconfig -pip (I/O moduletarget)

v v v

kvm -b v v

kvm -local v v

ldapcfg v v

led -info, -d, -loc(system target)

v v v v v

led -info, -loc(blade server target)

v v v v

mcad v v

monalerts v v

mt -b v v

mt -local, -remote v v

nat v v

ntp v v

ping -i(see Note 1)

v v v

pmpolicy v v

portcfg v v

ports v v



Command

Authority

Su

per

viso

r

Ch

assi

sA

ccou

nt

Man

agem

ent

Ch

assi

sL

ogM

anag

emen

t

Ch

assi

sA

dm

inis

trat

ion

Ch

assi

sC

onfi

gura

tion

Bla

de

Ad

min

istr

atio

n

Bla

de

Con

figu

rati

on

Bla

de

Rem

ote

Pre

sen

ce

I/O

Mod

ule

Ad

min

istr

atio

n

I/O

Mod

ule

Con

figu

rati

on

ports (I/O module target) v

power -on, -off, -softoff, -cycle v v v

power -on -c, -cycle -c v L L

power -wol, -local v v v

power -fp(global)

v v

power -fp(I/O module)

v v

rdoc v v

read v v

reset(blade server or ISMP)

v v

reset(I/O module)

v v

reset(management module)

v v

reset -c, -clr, -dg, -ddg, -sft,(blade server)

v L L

reset -sms(blade server)

v v

reset -exd, -full, -std(I/O module)

v v

reset -f, -standby, -force(management module)

v v

scale v v

sddump v v

sdemail v v v v v v v v v v

security v v

service v v

shutdown v v

slp v v

smtp v v

snmp v v

sol v v v



Command

Authority

Su

per

viso

r

Ch

assi

sA

ccou

nt

Man

agem

ent

Ch

assi

sL

ogM

anag

emen

t

Ch

assi

sA

dm

inis

trat

ion

Ch

assi

sC

onfi

gura

tion

Bla

de

Ad

min

istr

atio

n

Bla

de

Con

figu

rati

on

Bla

de

Rem

ote

Pre

sen

ce

I/O

Mod

ule

Ad

min

istr

atio

n

I/O

Mod

ule

Con

figu

rati

on

sshcfg v v

sslcfg v v

syslog v v

tcpcmdmode v v

telnetcfg v v

trespass v v

uicfg v v

update v v v v

uplink v v

users v v

users -disable, -enable, -unlock v v v v

write v v

zonecfg v v

Note:

1. All users can execute the ping -i command directed to a specific IP address.Users with Supervisor, Operator (general operator), I/O ModuleAdministration, I/O Module Configuration, or I/O Module Operator authoritycan execute the ping -i command option with no arguments or ping a specificIP address that is identified using its index number.

Cabling the management moduleThis topic describes how to cable the management module.

You must connect a client system to the management module to configure andmanage operation of the BladeCenter unit. All management modules support aremote management and console (Ethernet) connection. The advanced managementmodule also supports connection through the serial management port.

You can manage the BladeCenter unit by using by using the command-lineinterface that you access through Telnet or through the serial management port.You can also use the graphical user interface that is provided by themanagement-module web interface to manage the BladeCenter unit and bladeservers that support KVM. To make management connections to blade servers thatdo not support KVM, use an SOL session through the management-modulecommand-line interface.


To access the management-module command-line interface, you need the followingequipment and information:v A system with Ethernet or serial connection capability. To facilitate connections

at multiple locations, you can use a notebook computer.v The management-module MAC address (listed on the label on the management

module).v For networked connection to the management module, you need a standard

Ethernet cable and a local Ethernet network port (facility connection).v For direct connection of a system to the advanced management-module remote

management and console (Ethernet) connector, you can use either a standardEthernet cable or an Ethernet crossover cable.

v For serial connection of a system to the advanced management-module serialconnector, you need a serial cable. See the Installation Guide for yourmanagement module for cabling information and instructions.

For information about accessing the management-module web interface, see theBladeCenter Advanced Management Module User’s Guide.

The following topics describe how to cable to the management module to performinitial configuration of the BladeCenter unit. See the Installation Guide for yourmanagement module for specific cabling instructions.

Networked connectionThis topic describes how to connect the management module to a network.

Connect one end of a Category 5 or higher Ethernet cable to the remotemanagement and console (Ethernet) connector of the management module.Connect the other end of the Ethernet cable to the facility network.

Direct connectionThis topic tells you how to connect a client computer directly to the managementmodule.

Connect one end of a Category 5 or higher Ethernet cable or a Category 5 orhigher Ethernet crossover cable to the remote management and console (Ethernet)connector of the management module. Connect the other end of the cable to theEthernet connector on the client system.

Note: An advanced management module can perform an automatic mediadependent interface (MDI) crossover, eliminating the need for crossover cables orcross-wired (MDIX) ports. You might have to use a crossover cable to connect yoursystem to the advanced management module if the network interface card in theclient system is very old.


Serial connectionYou can connect a serial cable to the advanced management module.

Connect one end of a serial cable to the serial connector on the managementmodule. Connect the other end of the serial cable to the serial connector on theclient system. See the Installation Guide for your management module for cablinginformation and instructions.

Starting the command-line interfaceAccess the management-module command-line interface from a client system byestablishing a Telnet connection to the IP address of the management module or byestablishing a Secure Shell (SSH) connection.

For the advanced management module, you can also access the command-lineinterface using a serial connection. You can establish up to 20 separate Telnet,serial, or SSH sessions to the BladeCenter management module, giving you theability to have 20 command-line interface sessions active at the same time.

Although a remote network administrator can access the management-modulecommand-line interface through Telnet, this method does not provide a secureconnection. As a secure alternative to using Telnet to access the command-lineinterface, use a serial or SSH connection. SSH ensures that all data that is sent overthe network is encrypted and secure.

The following SSH clients are available. Although some SSH clients have beentested, support or nonsupport of any particular SSH client is not implied.v The SSH clients that are distributed with operating systems such as Linux, AIX®,

and UNIX (see your operating-system documentation for information). The SSHclient of Red Hat Linux 8.0 Professional was used to test the command-lineinterface.

v The SSH client of cygwin (see http://www.cygwin.com for information)v Putty (see http://www.chiark.greenend.org.uk/~sgtatham/putty for

information)

The following table shows the types of encryption algorithms that are supported,depending on the client software version that is being used.

Algorithm SSH version 2.0 clients

Public key exchange Diffie-Hellman-group 1-sha-1

Host key type DSA - 2048-bit

Bulk cipher algorithms 3-des-cbc or blowfish-cbc

MAC algorithms Hmac-sha1


http://www.cygwin.com

http://www.chiark.greenend.org.uk/~sgtatham/putty

The following topics describe how to connect your system to the managementmodule to perform initial configuration of the BladeCenter unit. The managementmodule has the following default settings:

Note: The advanced management module does not have a fixed static IPv6 IPaddress by default. For initial access to the advanced management module in anIPv6 environment, users can either use the IPv4 IP address or the IPv6 link-localaddress. See “IPv6 addressing for initial connection” for information aboutdetermining IPv6 addressing for initial connection.v IPv4 IP address: 192.168.70.125 (primary and secondary management module)v IPv4 Subnet: 255.255.255.0v User ID: USERID (all capital letters)v Password: PASSW0RD (note the number zero, not the letter O, in PASSW0RD)

For IPv4, the system that you are connecting to the management module must beconfigured to operate on the same subnet as the BladeCenter management module.If the IP address of the management module is outside of your local domain, youmust change the Internet protocol properties on the system that you areconnecting.

Note: For advanced management modules, the available password options dependon the password options that are configured for the BladeCenter unit.

IPv6 addressing for initial connectionWhen using IPv6 addressing, the only way to initially connect to the advancedmanagement module is by using the IPv6 link-local address.

The link-local address is a unique IPv6 address for the advanced managementmodule that is automatically generated based on its MAC address. It is of theform: FE80::3BA7:94FF:FE07:CBD0.

The link-local address for the advanced management module can be determined inone of the following ways:v Some advanced management modules will list the link-local address on a label

that is attached to the advanced management module.v If you are able to log in to the management module command-line interface

(CLI) using IPv4 addressing, the link-local address can be viewed using theifconfig command (see “ifconfig command” on page 171 for information).

v If you are able to log in to the management module web interface using IPv4addressing, the link-local address can be viewed in the Primary ManagementModule, IPv6 section of the MM Control → Network Interfaces page (see theBladeCenter Advanced Management Module User's Guide for information).

If the advanced management module does not have a label listing the link-localaddress and you are unable to access the advanced management module usingIPv4, complete the following steps to calculate link-local address:1. Write down the MAC address of the advanced management module. It is on a

label on the management module, below the IP reset button. The label readsMMxxxxxxxxxxxx, where xxxxxxxxxxxx is the MAC address. For example,39-A7-94-07-CB-D0

2. Split the MAC address into two parts and insert FF-FE in the middle. Forexample,39-A7-94-FF-FE-07-CB-D0


3. Convert the two hexadecimal digits at the left end of the string to binary. Forexample,v 39-A7-94-FF-FE-07-CB-D0

v 00111001-A7-94-FF-FE-07-CB-D0

4. Invert the value for bit 7 of the binary string. For example,v 00111001-A7-94-FF-FE-07-CB-D0

v 00111011-A7-94-FF-FE-07-CB-D0

5. Convert the binary digits at the left end of the string back to hexadecimal. Forexample,v 00111011-A7-94-FF-FE-07-CB-D0

v 3B-A7-94-FF-FE-07-CB-D0

6. Combine the hexadecimal digit pairs into 4-digit groups. For example,v 3B-A7-94-FF-FE-07-CB-D0

v 3BA7-94FF-FE07-CBD0

7. Replace dash (-) separators with colon (:) separators. For example,v 3BA7-94FF-FE07-CBD0

v 3BA7:94FF:FE07:CBD0

8. Add FE80:: to the left of the string. For example,FE80::3BA7:94FF:FE07:CBD0

For a MAC address of 39-A7-94-07-CB-D0, the link-local address used for initialIPv6 access is FE80::3BA7:94FF:FE07:CBD0.

Telnet connectionThis topic tells you how to establish a Telnet session with the managementmodule.

To log on to the management module by using Telnet, complete the followingsteps:1. From a command-line prompt on the network-management workstation, type

telnet ip_address (where ip_address is the management module IP address),and press Enter. For the first connection to the management module, use thedefault IP address of the management module; if a new IP address has beenassigned to the management module, use that one instead.

Note: The factory-defined static IPv4 IP address is 192.168.70.125, the defaultIPv4 subnet address is 255.255.255.0, and the default host name isMMxxxxxxxxxxxx, where xxxxxxxxxxxx is the burned-in MAC address. TheMAC address is on a label on the management module, below the IP resetbutton. See “IPv6 addressing for initial connection” on page 15 for informationabout determining IPv6 addressing for initial connection.

2. At the login prompt, type the management-module user ID. At the passwordprompt, type the management-module password. The user ID and passwordare case sensitive and are the same as those that are used formanagement-module web access. The default management-module user nameis USERID, and the default password is PASSW0RD (note the number zero, notthe letter O, in PASSW0RD).

The CLI command prompt is displayed. You can now enter commands for themanagement module.


Serial connectionYou can set up a serial connection with the management module.

After you connect a serial cable from the management module to the client system,complete the following steps:1. Open a terminal session on the client system, and make sure that the serial port

settings for the client system match the settings for the serial port on themanagement module. The default management-module serial port settings areas follows:v Baud rate (BPS): 57600v Data bits: 8v Parity: no parityv Stop bits: 1v Flow control: none

2. If any of the serial port settings for the client system were changed, reset themanagement module (see the Installation Guide for your management modulefor instructions).

3. At the login prompt, type the management-module user ID. At the passwordprompt, type the management-module password. The user ID and passwordare case sensitive and are the same as those that are used formanagement-module web access. The default management-module user nameis USERID, and the default password is PASSW0RD (note the number zero, notthe letter O, in PASSW0RD).



Secure Shell (SSH) connectionThis topic tell you how to establish a Secure Shell (SSH) connection with themanagement module.

To log on to the management module using SSH, complete the following steps:1. Make sure that the SSH service on the network-management workstation is

enabled. See your operating-system documentation for instructions.2. Make sure that the SSH server on the BladeCenter management module is

enabled. See the BladeCenter Advanced Management Module User's Guide forinstructions.

3. Start an SSH session to the management module, using the SSH client of yourchoice. For example, if you are using the cygwin client, from a commandprompt on the network-management workstation, type ssh ip_address (whereip_address is the management module IP address), and press Enter. For the firstconnection to the management module, use the default IP address of themanagement module; if a new IP address has been assigned to themanagement module, use that one instead.

Note: The factory-defined static IPv4 IP address is 192.168.70.125, the defaultIPv4 subnet address is 255.255.255.0, and the default host name isMMxxxxxxxxxxxx, where xxxxxxxxxxxx is the burned-in MAC address. TheMAC address is on a label on the management module, below the IP resetbutton. See “IPv6 addressing for initial connection” on page 15 for informationabout determining IPv6 addressing for initial connection.

4. Type the management-module user ID when you are prompted. At thepassword prompt, type the management-module password. The user ID andpassword are case sensitive and are the same as those that are used formanagement-module web access. The default management-module user nameis USERID, and the default password is PASSW0RD (note the number zero, notthe letter O, in PASSW0RD).


Using the Secure Shell serverThis topic tells you how to use the management module Secure Shell server.

The following SSH clients are available. Although some SSH clients have beentested, support or nonsupport of any particular SSH client is not implied.v The SSH clients that are distributed with operating systems such as Linux, AIX®,

and UNIX® (see your operating-system documentation for information).v The SSH client of cygwin (see http://www.cygwin.com for information).

If you are using the Secure Shell client that is based on OpenSSH, such as theclient that is included in Red Hat Linux version 7.3, to start an interactivecommand-line Secure Shell session to a management module with network address192.168.70.2, type a command similar to the following example:

ssh -x -l USERID 192.168.70.2

where -x indicates no X Window System forwarding and -l indicates that thesession is to use the login ID USERID.


http://www.cygwin.com

The advanced management module supports non-interactive Secure Shell sessions.This is most useful when it is combined with public key authentication. Use thiscapability to issue a single CLI command by adding the command to the end ofthe ssh command. For example, to get a list of the current users of the advancedmanagement module type

ssh -l USERID 192.168.70.2 users -T mm[1] -curr

If the CLI command requires special characters such as quotation marks, you mustescape them so that they are not consumed by the command shell on your clientsystem. For example, to set a new trespass warning, type a command similar to thefollowing example:

ssh -l USERID 192.168.70.2 trespass -T mm[1] -tw \"New WARNING\"

To start a Serial over LAN text redirection session to a blade server, the process issimilar, but in this case you must specify that the Secure Shell server session uses apseudo-terminal (PTY) to get the correct output formatting and keystrokehandling. In the following example, which starts a Serial over LAN session to theblade server in slot 2, the -t SSH client option specifies that a PTY is to beallocated.

ssh -t -l USERID 192.168.70.1 console -T blade[2]

Using SMASHYou can use the System Management Architecture for Server Hardware CommandLine Protocol (SMASH CLP) for the advanced management module. See the IBMSMASH Proxy Installation and User's Guide for more information.

To start an interactive SMASH CLP session by using an SSH client such asOpenSSH client with an advanced management module with networking address192.168.70.2, type a command similar to the following example:

ssh -p 50022 -l USERID 192.168.70.2

where -p 50022 specifes TCP port 50022, the default port number for SecureSMASH on the advanced management module, and -l USERID specifies one of the12 local account login IDs.

The advanced management module supports non-interactive Secure SMASHsessions. This is most useful when it is combined with public key authentication.Use this capability to issue a single SMASH CLP command. To start anon-interactive SMASH session, you must specify that the Secure SMASH serveruses a pseudo-terminal (PTY). If you fail to specify a PTY for the session the InputRedirection not Supported error message is displayed. For example, to get a listof the SMASH-addressable entities, type a command similar to the followingexample:

ssh -t -p 50022 -l USERID 192.168.70.2 show /modular1

where -t specifies that a PTY is required for the session and show /modular1 is theSMASH command that is to be executed on the advanced management module.

If you are using a Telnet client to start an interactive SMASH CLP session, youmust specify the correct TCP port number. By default, the port that is assigned tothe SMASH protocol is 50023.


SSH CLI exit codesThe SSH CLI commands return exit codes.

All CLI commands that are run in an SSH client single-command environmentprovide exit codes to indicate their outcomes. The following table shows exit codesthat are supported; other exit codes are reserved for future use.

Table 2. SSH CLI exit codes

NameValue(decimal) Description

EX_OK 0 Successful command execution.

EX_USAGE 64 Command-line usage error: syntax error, wrong command argumentsor number of arguments, or invalid command target.

EX_DATAERR 65 Input data error: invalid configuration file or SSH key parsing error.

EX_NOINPUT 66 The input file does not exist or is not readable.

EX_UNAVAILABLE 69 The command-line interface is not available: CLI oversubscribed, CLIdisabled, or the data returned by a command has an unexpected value.

EX_SOFTWARE 70 Internal software error. Check the management-module event log forother error indications.

EX_TEMPFAIL 75 The command could not perform a write operation because the deviceor management module was not in the correct state. Check forconflicting tasks or conditions and try to run the command again.

CLI_ERR_NOT_AUTHORIZED 126 Authorization error: the user does not have sufficient privileges toexecute command.

CLI_ERR_CNF 127 Command not found.

BladeCenter unit configurationYou must configure the BladeCenter unit for command-line interface operation.

The BladeCenter unit automatically detects the modules and blade servers that areinstalled and stores the vital product data (VPD). When the BladeCenter unit isstarted, the management module automatically configures the remote managementport of the management module, so that you can configure and manageBladeCenter components. You configure and manage BladeCenter componentsremotely by using the management-module command-line interface (CLI) or themanagement-module web interface.

To communicate with network resources and with the I/O modules in theBladeCenter unit, you must configure IP addresses for the management moduleand I/O modules. You can configure management-module IP addresses by usingthe web interface or command-line interface. You can configure the I/O modulesthrough the management-module web interface or through an external I/O-moduleport that is enabled through the management module, using a Telnet interface, aserial connection, or a web browser. See the documentation that comes with eachI/O module for information and instructions.

To communicate with the blade servers for functions such as deploying anoperating system or application program over a network, you must also configureat least one external (in-band) port on an Ethernet switch module in I/O-modulebay 1 or 2.


Note: If a pass-thru module is installed in I/O-module bay 1 or 2 (instead of anEthernet I/O module), you must configure the network switch that the pass-thrumodule is connected to; see the documentation that comes with the network switchfor instructions.

Configuring the management moduleYou must configure the management module for command-line interface operation.

You configure only the primary (active) management module. The standby(redundant) management module, if present, receives the configuration and statusinformation automatically from the primary management module when necessary.The configuration information in this topic applies to the primary managementmodule, which might be the only management module in the BladeCenter unit.

If the management module that you installed is a replacement for the onlymanagement module in the BladeCenter unit and you saved the configuration filebefore you replaced the management module, you can apply the savedconfiguration file to the replacement management module. For advancedmanagement modules, see “read command” on page 280 for information aboutapplying a saved configuration file.

For the primary management module to communicate, you must configure the IPaddress for the external Ethernet (remote management) port (eth0) of themanagement module. The initial automatic management module configurationenables a remote console to connect to the management module to configure theport completely and to configure the rest of the BladeCenter unit.

Note: The internal Ethernet ports (eth1) for the advanced management modulecannot be configured.

After you connect the primary management module to the network, the Ethernetport connection is configured in one of the following ways. Either of these actionsenables the Ethernet connection on the primary management module.v If you have an accessible, active, and configured dynamic host configuration

protocol (DHCP) server on the network, the IP address, gateway address, subnetmask, and DNS server IP address are set automatically. The host name is set tothe management-module MAC address by default, and the domain servercannot change it.

v If the DHCP server does not respond within 2 minutes after the port isconnected, the management module uses the factory-defined static IP addressand default subnet address.

Note: If the management-module DHCP setting is set to try the DHCP serverand then use the static IP address, the management module uses the static IPaddress when the DHCP server is not available during management-modulestartup. When this occurs, the IP address might not be reachable if multiplemanagement modules were started with the same static IP address.

Important: You cannot connect your system to the management module by usingthe factory-defined static IP address and default subnet address until at least 3minutes after management-module startup.

Note: If the IP configuration is assigned by the DHCP server, you can use theMAC address of the management-module network interface to find out what IP


address is assigned.

To configure the management-module Ethernet ports, complete the following steps:1. Connect your system to the management-module command-line interface (see

“Starting the command-line interface” on page 14 for more information).2. Configure the external Ethernet interface (eth0), using the ifconfig command

(see “ifconfig command” on page 171 for instructions).

Notes:

v The internal Ethernet management port on each I/O module provides forcommunication with the management module. You configure this port byconfiguring the IP address for the I/O module (see the BladeCenter AdvancedManagement Module User's Guide and the User's Guide for your I/O moduletype for information and instructions). Some types of I/O modules, such asthe pass-thru module, have no management port. See the documentation thatcomes with each I/O module to determine what else you must configure inthe I/O module.

v For I/O-module communication with a remote management station, such asan IBM® Systems Director management server, through themanagement-module external Ethernet port, the I/O-module internalnetwork interface and the management-module internal and externalinterfaces must be on the same subnet.

v To communicate with the blade servers for functions such as deploying anoperating system or application program, you also must configure at leastone external (in-band) port on an Ethernet I/O module.

Starting an SOL sessionAfter you start a Telnet or SSH session to the BladeCenter management module,you can start an SOL session to any individual blade server that supports SOL.

Note: Serial over LAN (SOL) must be enabled for both the BladeCenter unit andthe blade server before you can start an SOL session with the blade server. See “sol(serial over LAN) command” on page 328 and the BladeCenter Serial over LAN SetupGuide for information about setting up and enabling SOL.

Because you can start up to 20 separate web interface, Telnet, serial, or SSHsessions to the BladeCenter management module, simultaneous SOL sessions canbe active for each blade server installed in the BladeCenter unit.

Start an SOL session by using the console command, from the command line,indicating the target blade server. For example, to start an SOL connection to theblade server in blade bay 6, typeconsole -T system:blade[6]

Note: A blade server assembly that occupies more than one blade server bay isidentified by the lowest bay number that it occupies.

After an SOL session is started, all commands are sent to the blade server that isspecified by the console command until the SOL session is ended, regardless of thepersistent command target that was in effect before the SOL session.

See “sol (serial over LAN) command” on page 328 and the IBM BladeCenter Serialover LAN Setup Guide for information about configuring a blade server for SOL. See


your operating-system documentation for information about SOL commands thatyou can enter by using the command-line interface.

Ending an SOL sessionTo end an SOL session, press Esc followed by an opening parenthesis.

When the SOL session ends, the command-line interface returns to the persistentcommand target that was in effect before the SOL session. If you want to end theTelnet or SSH command-line session, type exit.

Note: Exiting an SOL session does not stop the flow of serial data.



Chapter 3. Command reference

This topic contains command function, usage information, and examples.

Commands in “Command syntax” on page 29 are listed in alphabetic order. Thecommands are also listed in the following two topics:v “Alphabetic command list”v “Command list by function” on page 27

Adding a -h, -help, or ? option to a command displays syntax help for thatcommand. For example, to display help for the environment command, type one ofthe following commands:v env -hv env -helpv env ?

You can target a command to a device other than the one that is set as the defaultby adding a -T option to a command. See “Selecting the command target” on page6 for information.

Alphabetic command list

In alphabetic order, the commands are as follows:v “accseccfg command” on page 30v “advfailover command” on page 40v “airfilter command (BladeCenter S only)” on page 42v “alarm command (BladeCenter T and HT only)” on page 43v “alertcfg command” on page 51v “alertentries command” on page 53v “autoftp command” on page 60v “baydata command” on page 63v “bofm command” on page 66v “boot command” on page 72v “bootmode command” on page 74v “bootseq command” on page 75v “buildidcfg command” on page 80v “chconfig command” on page 87v “chlog command” on page 93v “chmanual command” on page 95v “cin command” on page 97v “cinstatus command” on page 102v “clear command” on page 103v “clearlog command” on page 105v “clock command” on page 106v “config command” on page 111v “console command” on page 115v “dhcpinfo command” on page 117v “displaylog command” on page 119v “displaysd command” on page 124v “dns command” on page 126v “env (environment) command” on page 131v “ethoverusb command” on page 137


v “eventinfo command” on page 138v “events command” on page 140v “exit command” on page 143v “feature command” on page 144v “files command” on page 147v “groups command” on page 159v “fuelg command” on page 149v “health command” on page 163v “help command” on page 166v “history command” on page 168v “identify (location LED) command” on page 169v “ifconfig command” on page 171v “info (configuration information) command” on page 203v “iocomp command” on page 206v “kvm (keyboard, video, mouse) command” on page 208v “ldapcfg command” on page 210v “led command” on page 220v “list (system physical configuration) command” on page 225v “mcad command” on page 227v “modactlog command” on page 228v “monalerts command” on page 229v “mt (media tray) command” on page 239v “nat command” on page 241v “ntp (network time protocol) command” on page 245v “ping command” on page 248v “pmpolicy command” on page 251v “portcfg command” on page 253v “ports command” on page 255v “power command” on page 272v “rdoc command” on page 278v “read command” on page 280v “remotechassis command” on page 283v “reset command” on page 286v “scale command” on page 291v “sddump command” on page 299v “sdemail command” on page 301v “security command” on page 303v “service command” on page 304v “shutdown command” on page 306v “slp command” on page 307v “smtp command” on page 309v “snmp command” on page 312v “sol (serial over LAN) command” on page 328v “sshcfg command” on page 335v “sslcfg command” on page 337v “syslog command” on page 347v “tcpcmdmode command” on page 351v “telnetcfg (Telnet configuration) command” on page 354v “temps command” on page 355v “trespass command” on page 356v “uicfg command” on page 359v “update (update firmware) command” on page 363v “uplink (management module failover) command” on page 373v “users command” on page 377v “volts command” on page 400v “write command” on page 401


v “zonecfg command” on page 403

Command list by functionBy function, the commands are as follows:v Built-in commands

Use these commands to perform top-level functions within the command-lineinterface:– “env (environment) command” on page 131– “help command” on page 166– “history command” on page 168– “list (system physical configuration) command” on page 225

v Common commands

Use these commands to monitor and control operation of BladeCentercomponents:– “cinstatus command” on page 102– “health command” on page 163– “info (configuration information) command” on page 203– “iocomp command” on page 206– “modactlog command” on page 228– “ping command” on page 248– “temps command” on page 355– “volts command” on page 400

v Configuration commands

Use these commands to view and configure network settings, Ethernetinterfaces, and other functions:– “accseccfg command” on page 30– “advfailover command” on page 40– “alertcfg command” on page 51– “alertentries command” on page 53– “autoftp command” on page 60– “baydata command” on page 63– “bofm command” on page 66– “bootmode command” on page 74– “bootseq command” on page 75– “buildidcfg command” on page 80– “cin command” on page 97– “cinstatus command” on page 102– “clock command” on page 106– “config command” on page 111– “dhcpinfo command” on page 117– “displaysd command” on page 124– “dns command” on page 126– “ethoverusb command” on page 137– “feature command” on page 144– “files command” on page 147– “groups command” on page 159– “health command” on page 163– “ifconfig command” on page 171– “info (configuration information) command” on page 203– “iocomp command” on page 206– “kvm (keyboard, video, mouse) command” on page 208– “ldapcfg command” on page 210– “mcad command” on page 227

Chapter 3. Command reference 27

– “modactlog command” on page 228– “monalerts command” on page 229– “mt (media tray) command” on page 239– “nat command” on page 241– “ntp (network time protocol) command” on page 245– “pmpolicy command” on page 251– “ping command” on page 248– “portcfg command” on page 253– “ports command” on page 255– “read command” on page 280– “rdoc command” on page 278– “remotechassis command” on page 283– “scale command” on page 291– “sddump command” on page 299– “security command” on page 303– “service command” on page 304– “slp command” on page 307– “chconfig command” on page 87– “chmanual command” on page 95– “smtp command” on page 309– “snmp command” on page 312– “sol (serial over LAN) command” on page 328– “sshcfg command” on page 335– “sslcfg command” on page 337– “tcpcmdmode command” on page 351– “telnetcfg (Telnet configuration) command” on page 354– “temps command” on page 355– “trespass command” on page 356– “uicfg command” on page 359– “uplink (management module failover) command” on page 373– “users command” on page 377– “volts command” on page 400– “zonecfg command” on page 403

v Discovery commands

Use these commands to locate other resources on the network:– “ping command” on page 248– “remotechassis command” on page 283

v Event log commands

Use these commands to view and clear primary management-module event logentries:– “clearlog command” on page 105– “displaylog command” on page 119– “eventinfo command” on page 138– “events command” on page 140– “modactlog command” on page 228– “chlog command” on page 93– “syslog command” on page 347


v LED commands

Use these commands to monitor and control operation of BladeCenter unitLEDs:– “identify (location LED) command” on page 169– “led command” on page 220

v Memory commands

Use these commands to reset the management-module configuration andperform firmware updates:– “clear command” on page 103– “update (update firmware) command” on page 363

v Power-control commands

Use these commands to control operation of the BladeCenter unit, blade servers,and I/O (switch) modules:– “boot command” on page 72– “power command” on page 272– “reset command” on page 286– “shutdown command” on page 306

v Power-management commands

Use these commands to monitor power consumption of the BladeCenter unitand installed components:– “fuelg command” on page 149– “pmpolicy command” on page 251– “volts command” on page 400

v Save and restore configuration commands

Use these commands to save and restore the management-module configuration:– “read command” on page 280– “write command” on page 401

v Session commands

Use these commands to start an SOL connection to the command console of aspecific blade server or to end a command console session:– “console command” on page 115– “exit command” on page 143

v Systems-management commands (BladeCenter T only)

Use these commands to manage alarms for monitored parameters of theBladeCenter T unit:– “alarm command (BladeCenter T and HT only)” on page 43

Command syntaxEach of the following topics describes a command-line interface command and itssyntax. Each command description also includes an example of command use.


accseccfg commandThis command displays and configures account security settings for the advancedmanagement module.

Table 3. accseccfg command

Function What it does Command Valid targets

Display account securitysettings

Displays the user account securitysettings for the advancedmanagement module. Returnedvalues:

v Default security settings used(legacy, high, or custom)

v -am: user authentication method(local, ldap, localldap, orldaplocal)

v -alt: authentication loggingtimeout (in seconds)

v -cp: complex password (on, off)

v -ct: CLI inactivity session timeout(in seconds)

v -dc: minimum differentcharacters in the password(when -cp is enabled)

v -de: default administrationpassword expiration (on, off)

v -ia: account inactivity alert timeperiod (in days)

v -ici: log new login events fromsame user (on, off)

v -id: account inactivity disabletime period (in days)

v -lf: maximum login failures

v -lp: lockout period aftermaximum login failures (inminutes)

v -mls: maximum simultaneoususer sessions

v -pc: password change on firstaccess (on, off)

v -pe: password expiration timeperiod (in days)

v -pi: minimum password changeinterval (in hours)

v -pr: password required (on, off)

v -rc: password reuse cycle

v -wt: web inactivity sessiontimeout (in minutes, none, orbased on length of user session)

accseccfg -T system:mm[x]

where x is the primarymanagement-modulebay number.


Table 3. accseccfg command (continued)


Set account defaults tolegacy level

Sets management-module accountsecurity to a predefined legacy setof default values. Legacy defaultvalues:v -alt: retains set valuev -am: retains set valuev -cp: offv -ct: retains set valuev -dc: 0v -de: offv -ia: 0v -ici: retains set valuev -id: 0v -lf: 5v -lp: 2v -mls: retains set valuev -pc: offv -pe: 0v -pi: 0v -pr: offv -rc: 0v -wt: retains set value

Note:

v The user who is running theaccseccfg -legacy command musthave a password assigned.

v The -legacy option must be runalone and not in conjunctionwith any other accseccfgcommand options.

accseccfg -legacy

This command can onlybe run by users who haveone or more of thefollowing commandauthorities:v Supervisorv Chassis configuration

See “Commands and userauthority” on page 8 foradditional information.

-T system:mm[x]





Set account defaults tohigh level

Sets management-module accountsecurity to a predefined high set ofdefault values. High default valuesare:v -am: retains set valuev -cp: onv -ct: retains set valuev -dc: 2v -de: onv -ia: 120v -id: 180v -lf: 5v -lp: 60v -pc: onv -pe: 90v -pi: 24v -pr: onv -rc: 5v -wt: retains set value

Note:

v The user who is running theaccseccfg -high command musthave a password assigned.

v The -high option must be runalone and not in conjunctionwith any other accseccfgcommand options.

accseccfg -high



-T system:mm[x]


Set authenticationlogging timeout

Sets a custom value for the amountof time that the managementmodule will not log repeated loginsby the same user.

accseccfg -alt timeout

where timeout is 0, 5, 30,60, 300, 600, 1800, 3600,43200, or 86400 seconds. Ifno value is entered, loginlogging is disabled.



-T system:mm[x]





Set user authenticationmethod

Sets a custom value formanagement module userauthentication method.

accseccfg -am method

where method isv localv ldapv localldapv ldaplocal



-T system:mm[x]


Enable / disable complexpassword

Enables or disables the complexpassword for management-moduleuser authentication.Note: Enabling the complexpassword also turns on thepassword required (-pr) commandoption.

accseccfg -cp state

where state is on or off.



-T system:mm[x]


Set CLI inactivitytimeout

Sets the custom value formanagement-module CLI inactivitysession timeout.

accseccfg -ct timeout

where timeout is from 0 to4,294,967,295 seconds,inclusive.

This command can onlybe run by users who havethe following commandauthorities:v Supervisorv Chassis configuration


-T system:mm[x]





Set minimum number ofdifferent characters forpassword

Sets custom value for the minimumnumber of different characters to beused in a management-modulepassword.Note: The minimum number ofdifferent characters applies onlywhen complex passwords areenabled.

accseccfg -dc number

where number is from 0 to15, inclusive.



-T system:mm[x]


Enable / disable defaultadministration passwordexpiration

Enables or disables the defaultadministration password expirationfor the management module.

accseccfg -de state




-T system:mm[x]


Set account inactivityalert time

Sets custom value for managementmodule account inactivity alerttime.Note: The accseccfg -ia value mustbe less than the accseccfg -id value.

accseccfg -ia time

where time is from 0 to365 days, inclusive.



-T system:mm[x]





Set state for logging oflogin events from sameIP address

Enables or disables logging of newlogin events from the same userfrom the same IP address.Note: This value applies only if thevalue set by the -alt commandoption is set to something otherthan 0 or none.

accseccfg -ici state




-T system:mm[x]


Set account inactivitydisable time

Sets the custom value formanagement-module accountinactivity disable time.Note: The accseccfg -id value mustbe greater than the accseccfg -iavalue.

accseccfg -id time




-T system:mm[x]


Set maximum number oflogin failures

Sets the custom value for themaximum number of login failuresbefore the management modulelocks out a user.

accseccfg -lf number

where number is from 0 to10, inclusive.



-T system:mm[x]





Set lockout period Sets the custom value formanagement-module accountlockout period, used when themaximum number of login failuresis exceeded.

accseccfg -lp time

where time is from 0 to2880 minutes, inclusive.



-T system:mm[x]


Set maximum LDAPsessions for user

Sets the custom value for themaximum number of simultaneouslogin sessions allowed for a singleLDAP user

accseccfg -mlsmax_sessions

where max_sessions is from0 to 20, inclusive.



-T system:mm[x]


Enable / disablepassword change at firstlogin

Enables or disables the mandatorypassword change at firstmanagement-module login.

accseccfg -pc state




-T system:mm[x]





Set password expirationtime

Sets custom value for themanagement module passwordexpiration time.

accseccfg -pe time




-T system:mm[x]


Set password minimumchange interval

Sets custom value for the minimumamount of time betweenmanagement module passwordchanges.

accseccfg -pi time

where time is from 0 to1440 hours, inclusive, andless than passwordexpiration period whenthat period is greater than0.



-T system:mm[x]


Enable / disablepassword required

Enables or disables the passwordrequired for management module.Notes:v The user that is running the

accseccfg -pr command musthave a password assigned.

v Disabling password required alsoturns off the complex password(-cp) command option.

accseccfg -pr state




-T system:mm[x]





Set password reuse cycle Sets custom value for themanagement module passwordreuse cycle. This setting determineshow many times a password mustbe changed before being reused.

accseccfg -rcnumber_reuses

where number_reuses isfrom 0 to 5, inclusive.



-T system:mm[x]


Set web interfaceinactivity timeout

Sets custom value for managementmodule web interface inactivitysession timeout.

accseccfg -wt timeout

where timeout is 1, 5, 10,15, or 20 minutes, none (notimeout), or user (userpicks timeout each timethey log in to the webinterface).



-T system:mm[x]


Example:

To set management-module account security to use the high level defaults, whilemanagement module 1 is set as the persistent command environment, at thesystem:mm[1]> prompt, typeaccseccfg -high

To display the account security settings for the management module, whilemanagement module 1 is set as the persistent command environment, at thesystem:mm[1]> prompt, typeaccseccfg


The following example shows the information that is returned from these twocommands:system:mm[1]> accseccfg -highOKsystem:mm[1]> accseccfg-high-alt 600-am local-cp on-ct 0-dc 2-de on-ia 120-ici on-id 180-lf 5-lp 60-mls 5-pc on-pe 90-pi 24-pr on-rc 5-wt usersystem:mm[1]>


advfailover commandThis command displays and configures the advanced failover settings for theadvanced management module.

Table 4. advfailover command


Display managementmodule advancedfailover settings

Displays the advanced failoversettings for the managementmodule. Possible return values are:

v off - disable network interface forthe standby management module

v swap - enable the standbymanagement module networkinterface and swap IP addressesbetween the two managementmodules during failover

v noswap - enable the standbymanagement module networkinterface and do not swap IPaddresses between the twomanagement modules duringfailover

Note: This command does notapply to the BladeCenter S unit,which supports only a singleadvanced management module.

advfailover -T system:mm[x]


Disable networkinterface for standbymanagement module

Disables the network interface forthe standby management module,preventing failover.

advfailover -ip off



-T system:mm[x]


Enable network interfaceand allow IP addressswap during failover

Enables the network interface forthe standby management moduleand allows the IP addresses toswap between the twomanagement modules duringfailover.

advfailover -ip swap



-T system:mm[x]



Table 4. advfailover command (continued)


Enable network interfaceand prevent IP addressswap during failover

Enables the network interface forthe standby management moduleand prevents the IP addresses fromswapping between the twomanagement modules duringfailover.

advfailover -ip noswap



-T system:mm[x]


Example:

To disable the network interface for the standby management module, whilemanagement module 1 is set as the persistent command environment, at thesystem:mm[1]> prompt, typeadvfailover -ip off

To display the management module advanced failover setting, while managementmodule 1 is set as the persistent command environment, at the system:mm[1]>prompt, typeadvfailover

The following example shows the information that is returned from these twocommands:system:mm[1]> advfailover -ip offOKsystem:mm[1]> advfailover-ip offsystem:mm[1]>


airfilter command (BladeCenter S only)This command sets the interval for air filter change notifications for a BladeCenterS unit.

Table 5. airfilter (set notification interval) command


Display air filter changenotification interval

Displays the frequency of thechassis air filter reminder.

airfilter -T system:mm[x]


Set air filter changenotification interval

Configures the frequency of thechassis air filter reminder.Note: The 1 month replacementinterval is recommended forenvironments with a high amountof dust. Replacement every 3months is recommended forenvironments with mediumamounts of dust. Replacementevery 6 months is recommendedfor environments with lowamounts of dust.

airfilter -freq frequency

where frequency is theinterval, in months,between reminders tochange the chassis airfilter. Valid values are 0, 1,3, and 6.

This command can onlybe run by users who haveone or more of thefollowing commandauthorities:v Supervisorv Chassis account

managementv Chassis log

managementv Chassis administrationv Chassis configuration


-T system:mm[x]


Example: To view the current notification interval, while management module 1 isset as the persistent command environment, at the system:mm[1]> prompt, typeairfilter

To set the notification interval to three months, while management module 1 is setas the persistent command environment, at the system:mm[1]> prompt, typeairfilter -freq 3

The following example shows the information that is returned when thesecommands are entered:system:mm[1]> airfilter-freq 1system:mm[1]>

system:mm[1]> airfilter -freq 3OKsystem:mm[1]>


alarm command (BladeCenter T and HT only)This command displays alarm information, acknowledges alarms, and clearsalarms for the specified command target.

Table 6. alarm command


Display all alarms Display all alerts generated by thetarget component. When directedto the BladeCenter unit, thecommand returns a summary ofalarms for all BladeCentercomponents. When directed to acomponent installed in theBladeCenter unit, the commandreturns a detailed alarm listing forthat component.

Detailed alarm listings include analarm key that can be used toacknowledge or clear an alarm.

alarm -q -T system

-T system:mm[x]

-T system:blade[x]

-T system:switch[x]

-T system:power[x]

-T system:blower[x]

where x is the primarymanagement-module,blade server, I/Omodule, powermodule, or blower baynumber.

Display power alarms Display all power related alertsgenerated by the target component.When directed to the BladeCenterunit, the command returns asummary of alarms for allBladeCenter components. Whendirected to a component installedin the BladeCenter unit, thecommand returns a detailed alarmlisting for that component.

Detailed alarm listings include analarm key that can be used toacknowledge or clear an alarm.Note: The -p option can becombined with the -q option toquery power related alarms.

alarm -p -T system

-T system:mm[x]

-T system:blade[x]

-T system:switch[x]

-T system:power[x]

-T system:blower[x]


Display alarminformation (specifiedby alarm generator ID)

Display information for alarmspecified by the generator ID.

alarm -q -g value

where value is thegenerator ID.

This command can onlybe run by users who haveone or more of thefollowing commandauthorities:v Supervisorv Blade administrationv Blade remote presence


-T system:mm[x]

-T system:blade[x]

-T system:switch[x]

-T system:power[x]

-T system:blower[x]



Table 6. alarm command (continued)


Display alarminformation (specifiedby alarm ID)

Display information for alarmspecified by the alarm ID.

alarm -q -a value

where value is the alarmID.

-T system:mm[x]

-T system:blade[x]

-T system:switch[x]

-T system:power[x]

-T system:blower[x]


Display detailed alarminformation (specifiedby generatorinformation)

Display detailed information foralarm specified by the alarmgenerator information. Informationreturned includes the alarmdescription that is shown by themanagement-module web interfaceand other information such as thealarm severity, power source,software indicator, and an alarmkey.

alarm -q -o value

where value is thegenerator information.

-T system:mm[x]

-T system:blade[x]

-T system:switch[x]

-T system:power[x]

-T system:blower[x]


Display alarminformation (specifiedby complete alarm key)

Display information for alarmspecified by the complete alarmkey.

alarm -q -k m:g:o:a

where m:g:o:a is thecomplete alarm key:v m is the module IDv g is the generator IDv o is the generator

informationv a is the alarm ID

-T system:mm[x]

-T system:blade[x]

-T system:switch[x]

-T system:power[x]

-T system:blower[x]





Acknowledge alarm(specified by alarmgenerator ID)

Acknowledge the alarm specifiedby the generator ID.

alarm -r -g value



(for managementmodule, power module,or blower)

v Blade configuration (forblade server)

v I/O moduleconfiguration (for I/Omodule)


-T system:mm[x]

-T system:blade[x]

-T system:switch[x]

-T system:power[x]

-T system:blower[x]


Acknowledge alarm(specified by generatorinformation)

Acknowledge the alarm specifiedby the generator information.

alarm -r -o value







-T system:mm[x]

-T system:blade[x]

-T system:switch[x]

-T system:power[x]

-T system:blower[x]





Acknowledge alarm(specified by alarm ID)

Acknowledge the alarm specifiedby the alarm ID.

alarm -r -a value







-T system:mm[x]

-T system:blade[x]

-T system:switch[x]

-T system:power[x]

-T system:blower[x]


Acknowledge alarm(specified by completealarm key)

Acknowledge the alarm specifiedby the complete alarm key.

alarm -r -k m:g:o:a








-T system:mm[x]

-T system:blade[x]

-T system:switch[x]

-T system:power[x]

-T system:blower[x]





Clear alarm (specifiedby alarm generator ID)

Clear the alarm specified by thegenerator ID.

alarm -c -g value







-T system:mm[x]

-T system:blade[x]

-T system:switch[x]

-T system:power[x]

-T system:blower[x]


Clear alarm (specifiedby generatorinformation)

Clear the alarm specified by thegenerator information.

alarm -c -o value







-T system:mm[x]

-T system:blade[x]

-T system:switch[x]

-T system:power[x]

-T system:blower[x]





Clear alarm (specifiedby alarm ID)

Clear the alarm specified by thealarm ID.

alarm -c -a value







-T system:mm[x]

-T system:blade[x]

-T system:switch[x]

-T system:power[x]

-T system:blower[x]


Clear alarm (specifiedby complete alarm key)

Clear the alarm specified by thecomplete alarm key.

alarm -c -k m:g:o:a








-T system:mm[x]

-T system:blade[x]

-T system:switch[x]

-T system:power[x]

-T system:blower[x]





Set alarm Set an alarm for the specifiedtarget, including severity level anddescription.

alarm -s -l level desc

wherev level is the severity

level:– CRT (critical)– MJR (major)– MNR (minor)

v desc is a short textdescription of the alarm






-T system:mm[x]

-T system:blade[x]

-T system:switch[x]

-T system:power[x]

-T system:blower[x]


Example: To display the alarm status for the BladeCenter T unit, while theBladeCenter T unit is set as the persistent command environment, at the system>prompt, typealarm -q

To display the power alarm status for the BladeCenter T unit, while theBladeCenter T unit is set as the persistent command environment, at the system>prompt, typealarm -p

To display detailed power alarm status for the power module in power bay 2,while the BladeCenter T unit is set as the persistent command environment, at thesystem> prompt, typealarm -T system:power[2] -q


The following example shows the information that is returned from a series ofalarm commands.system> alarm -qAlarms Summary ListModule ACK Severity Power Software=========== === ======== ===== ========mm[1] No Major No Nopower[2] No Critical Yes No

system> alarm -q -pAlarms Summary ListModule ACK Severity Power Software=========== === ======== ===== ========power[2] No Critical Yes No

system> alarm -q -T mm[1]Alarms Detailed ListACK Severity PWR SW Descript Key=== ======= === === ============================================== ============No Major No No (05/21/08, 13:46:11) Insufficient chassis power 255:81:1:2:3No Minor No No (05/21/08, 13:45:26) Event log full 255:81:1:1:1

system>


alertcfg commandThis command displays and configures the global remote alert settings for theadvanced management module.

Table 7. alertcfg command


Display global remotealert settings

Displays the global remote alertsettings for the advancedmanagement module.

alertcfg -T system:mm[x]


Set remote alert retrydelay interval andnumber of retries

Sets the remote alert retry delayinterval and permitted number ofretries.

alertcfg -dr delay -rllimit

where:

v delay is from 0.5minutes to 4.0 minutes,inclusive, in 0.5 minuteincrements. If you entera value less than 0.5minute, the retryinterval will be set to0.5 minute. If you entera value greater than 4.0minutes, the retryinterval will be set to4.0 minutes.

v limit is the remote alertretry limit, ranging from0 to 8.



-T system:mm[x]


Include / exclude serviceinformation with emailalerts

Enables or disables inclusion ofservice information with emailalerts.

alertcfg -si state

where state is enabled ordisabled.



-T system:mm[x]



Table 7. alertcfg command (continued)


Set remote alert retrylimit

Sets the maximum number of timesthe system will attempt to send aremote alert, if previous attemptswere unsuccessful.

alertcfg -rl value

where value is from 0 to 8,inclusive. If you enter avalue of 0, no retries willbe attempted. If you entera value greater than 8, anerror will be displayed.



-T system:mm[x]


Example: To view the remote alert configuration, while management module 1 isset as the persistent command environment, at the system:mm[1]> prompt, typealertcfg

To set the retry interval to 3.5 minutes, include service information in the alert, andset the remote alert retry limit to 7, while management module 1 is set as thepersistent command environment, at the system:mm[1]> prompt, typealertcfg -dr 3.5 -si enabled -rl 7

The following example shows the information that is returned from thesecommands:system:mm[1]> alertcfg-dr 2.0-si disabled-rl 6system:mm[1]> alertcfg -dr 3.5 -si enabled -rl 7OKsystem:mm[1]> alertcfg-dr 3.5-si enabled-rl 7system:mm[1]>


alertentries commandThis command manages the recipients of alerts generated by the primarymanagement module.

Table 8. alertentries command


Display alert propertiesfor all recipients

Displays alert properties for allmanagement-module alertrecipients. Returned values for eachalert recipient are:

v recipient name

v notification method (Email overLAN/Systems Directorcomp./SNMP over LAN)

v type of alerts received (Receivescritical alerts only/Receives allalerts/Disabled)

alertentries -T system:mm[x]


Display alert propertiesfor alert recipients

Displays alert properties for thespecified management-module alertrecipient profile. Returned valuesare:

v -status alert_recipient_status(on/off)

v -n alert_recipient_name

v -f alert_type (critical/none)

v -t notification_method(email/director/snmp)

v -e email_address (used for emailnotifications)

v -i static_IP_addr/hostname (usedfor IBM Systems Directornotifications)

alertentries-recip_number

where recip_number is anumber from 1 to 12 thatcorresponds to therecipient number assignedin the "Display alertproperties for allrecipients" list.

-T system:mm[x]


Delete alert recipient Delete the specified alert recipient. alertentries-recip_number -del

where recip_number is anumber from 1 to 12 thatcorresponds to therecipient number assignedin the "Display alertproperties for allrecipients" list. It ispossible to delete anempty alert recipient.



-T system:mm[x]



Table 8. alertentries command (continued)


Create alert recipient Create the specified alert recipient.

All fields must be specified whencreating an alert recipient.

alertentries-recip_number -nrecip_name -statusalert_status -f filter_type -tnotification_method -eemail_addr -iip_addr/hostname

where:v recip_number is a

number from 1 to 12that corresponds to anunused recipientnumber in the "Displayalert properties for allrecipients" list.

v recip_name is aalphanumeric string upto 31 characters inlength containing anycharacter, includingspaces, except for anglebrackets ( < and > ). Ifthe string includesspaces it must beenclosed indouble-quotes.

v alert_status is on or offfor receipt of alerts.

v filter_type filters the alerttypes received: critical(receive critical alertsonly) or none (receiveall alerts).

v notification_method isemail, director (IBMSystems Director) orsnmp.– For email, you must

specify an emailaddress (-eargument).

– For director youmust specify an IPaddress (-iargument).

– If snmp is selected,the -e and -iarguments are notneeded.

v email_addr is a validemail address string upto 63 characters inlength.

(continued on next page)

-T system:mm[x]





Create alert recipient

(continued)

v ip_addr/hostname is avalid static IP addressor an alphanumerichostname string for therecipient that is up to 49characters in length thatcan include periods ( . ),hyphens ( - ), andunderscores ( _ ).



Set alert recipient name Sets a name for the specified alertrecipient.

alertentries-recip_number -n recip_name


number from 1 to 12that corresponds to therecipient numberassigned in the "Displayalert properties for allrecipients" list.

v recip_name is aalphanumeric string upto 31 characters inlength that can includeany character, includingspaces, except for anglebrackets ( < and > ). Ifthe name includesspaces, it must beenclosed indouble-quotes.



-T system:mm[x]





Set alert recipient status Sets status for the specified alertrecipient. The status determines if arecipient will receive alarmnotifications.

alertentries-recip_number -statusalert_status



v alert_status is on or off.



-T system:mm[x]


Set alert types received Filters the types of alert that arereceived by the specified alertrecipient.

alertentries-recip_number -f filter_type



v alert_type filters the alerttypes received: critical(receive critical alertsonly) or none (receiveall alerts).



-T system:mm[x]





Set alert notificationmethod

Sets the alert notification methodfor the specified alert recipient.

alertentries-recip_number -tnotification_method



v notification_method is– email– director (IBM

Systems Director)– snmp



-T system:mm[x]


Set alert recipient emailaddress

Sets the email address for thespecified alert recipient. This emailaddress is used to send alerts to therecipient via email.

The email address can be set onlyif the alert notification method (-toption) is set to email. The -t and -eoptions can be combined within thesame command.

alertentries-recip_number -eemail_addr



v email_addr is a validemail address string upto 63 characters inlength.



-T system:mm[x]





Set alert recipient IPaddress or hostname

Sets the IP address or hostnameused to send alert notifications tothe specified alert recipient usingIBM Systems Director.

The IP address or hostname usedto send alert notifications can be setonly if the alert notification method(-t option) is set to director (IBMSystems Director). The -t and -ioptions can be combined within thesame command.

alertentries-recip_number -iip_addr/hostname



v ip_addr/hostname is avalid static IP addressor an alphanumerichostname string up to49 characters in lengththat can include periods( . ), hyphens ( - ), andunderscores ( _ ).



-T system:mm[x]


Generate test alert Generates a test alert to verifycorrect alert response.Notes:v The alertentries -test

command option must be usedalone.

v If autoftp is enabled, sending atest alert will cause the system tosend out service data as well.

alertentries -test

This command can onlybe run by users who haveone or more of thefollowing commandauthorities:v Supervisorv Chassis log

managementv Chassis administrationv Chassis configurationv Blade administrationv Blade configurationv Blade remote presencev I/O module

administrationv I/O module

configuration


-T system:mm[x]



Example: To view the configuration for alert recipient 1, while managementmodule 1 is set as the persistent command environment, at the system:mm[1]>prompt, typealertentries -1

To configure alert recipient 2 to receive only critical alert notifications by email,while management module 1 is set as the persistent command environment, at thesystem:mm[1]> prompt, typealertentries -2 -n test2 -status on -f critical -t email -e [email protected]

To configure alert recipient 3 to receive all alert notifications through IBM SystemsDirector, while management module 1 is set as the persistent commandenvironment, at the system:mm[1]> prompt, typealertentries -3 -n test3 -status on -f none -t director -i 192.168.70.140

To configure alert recipient 4 to receive all alert notifications through SNMP, whilemanagement module 1 is set as the persistent command environment, at thesystem:mm[1]> prompt, typealertentries -4 -n test4 -status on -f none -t snmp

The following example shows the information that is returned from thesecommands:system:mm[1]> alertentries -1-status on-n test1-f critical-t email-e [email protected]:mm[1]> alertentries -2 -n test2 -status on -f critical -t email-e [email protected]:mm[1]> alertentries -3 -n test3 -status on -f none -t director-i 192.168.70.140OKsystem:mm[1]> alertentries -4 -n test4 -status on -f none -t snmpOKsystem:mm[1]>


autoftp commandThis command displays and configures the automated FTP/TFTP problem reportsettings for the advanced management module.

Table 9. autoftp command


Display call-homesettings for autoftp callhome

Displays the Automated FTP/TFTPProblem Report settings that allowthe advanced management moduleto automatically put service dataonto a specified server when a callhome event is detected.

autoftp -T system:mm[x]



Table 9. autoftp command (continued)


Configure call-homesettings for autoftp callhome

Configures the AutomatedFTP/TFTP Problem Report settingsthat allow the advancedmanagement module toautomatically put service data ontoa specified server when a call homeevent is detected.Note: The system will wait fivedays before sending duplicateevents if they are leftunacknowledged in the activity log.

autoftp -m mode -iip_address -p port -u“user_name” -pw“password”

where:v mode is one of the

following automatedproblem reportingmodes:– ftp– tftp– disabled

v ip_address is the IPaddress of the FTP orTFTP server

v port is the FTP or TFTPtransmission port, anumber from 1 to 65535,inclusive. If you enter avalue outside this range,an error message will bedisplayed.

v “user_name” is thequote-delimited FTPUser Name forautomated problemreporting (63 charactersmaximum).

v “password” is thequote-delimited FTPpassword for automatedproblem reporting (63characters maximum).

Notes:v For FTP, all fields must

be set.v For TFTP, only -i and -p

are needed.



-T system:mm[x]



Example:

To view the settings of the automated call-home message feature, whilemanagement module 1 is set as the persistent command environment, at thesystem:mm[1]> prompt, typeautoftp

To configure the automated call-home message feature to report call-home eventsusing TFTP to tftp.ibm.com over transmission port 69, while management module1 is set as the persistent command environment, at the system:mm[1]> prompt, typeautoftp -m tftp -i tftp.ibm.com -p 69

The following example shows the information that is returned from thesecommands:system:mm[1]> autoftp-m ftp-i ftp.ibm.com-p 6-u smlitesystem:mm[1]> autoftp -m tftp -i tftp.ibm.com -p 69OKsystem:mm[1]>


baydata commandThis command allows a user to set, assign, and display informational dataassigned to the blade server bays.

Table 10. baydata command


Display bay data for allblade servers

Displays blade server bay data forbay number, bay data status, anddefined bay data for all bays.

baydata -T system

Display blade server baydata for a specific bay

Displays the information assignedto the specified blade bay using the-b option.

baydata -b bay_num

where bay_num is thenumber of the specific bayto display. The baynumber must be withinthe scope assigned to theuser.

This command can onlybe run by users who haveone or more of thefollowing commandauthorities:v Supervisorv Blade configuration


-T system

Clear bay data Clears the blade bay definitionstrings for all bays.

baydata -clear

The bay number must bewithin the scope assignedto the user.



-T system


Table 10. baydata command (continued)


Clear bay data forspecific bay

Clears the blade bay definitionstrings for the specified blade bay.

baydata -b bay_num-clear

where bay_num is thenumber of the specifiedbay to clear of data. Thebay number must bewithin the scope of theuser.



-T system

Set bay data Sets blade bay data for all bladeservers within the user's scope.This information can include: dataabout drivers or software, theBladeCenter unit shelf number andIP address, and whether the bladeserver is a master or member in ahigh-availability system.

Note: To apply changes to theBIOS/SMBIOS structure, power-offand power-on the blade server,restart the blade server, or removeand reinstall the blade server.

baydata -data"data_definition"

where "data definition" isthe ASCII string of up to60 characters enclosed indouble quotationmarks–"data definition".The quotation marks arenot stored.



-T system


Table 10. baydata command (continued)


Set blade bay datadefinition for specificblade server

Sets blade bay data for thespecified blade server using the -boption.

Note: To apply changes to theBIOS/SMBIOS structure, power-offand power-on the blade server,restart the blade server, or removeand reinstall the blade server.

If the command is issued to aspecific bay, data is written to thatblade server if it is in the user'sscope.

baydata -b bay_num -data"data_definition"

where:v bay_num is the blade

bayv where "data definition" is

the quote-delimitedASCII string of up to 60characters



-T system

Example: To view the bay data for all blades, while the management module is setas the persistend command environment, at the system> prompt, typebaydata

The following example shows the information that is returned from this command:system> baydataBay Status Definition1 Unsupported2 No blade present3 No blade present4 No blade present5 No blade present6 No blade present7 No blade present8 No blade present9 No blade present10 No blade present11 No blade present12 No blade present13 No blade present14 No blade presentsystem>


bofm commandThis command applies a new BladeCenter Open Fabric Manager (BOFM)configuration to all the specified BladeCenter units, bays, and ports.

Notes:

1. Open Fabric Manager is not a standard management module feature; it isoffered and documented separately. See the BladeCenter Open Fabric ManagerInstallation and Users Guide for more detailed information.

2. If the number of advanced management module TCP command modeconnections is zero, or if all available TCP command mode connections are inuse, a connection failure message is generated by the BOFM feature. Make surethat the advanced management module TCP command mode connection limitis positive and that no more than the available number of connections are inuse. See the BladeCenter Open Fabric Manager Installation and Users Guide foradditional information.

Table 11. bofm command


Apply BOFMconfiguration tospecified BladeCenterunits, bays, and ports

Copies a configuration file from aTFTP server to the specifiedmanagement module, which thenconfigures BladeCenter units,blade servers, and I/O modules.

The configuration file is acomma-separated values (CSV) filethat assigns IP addresses and othervalues to BladeCenter units, bays,and ports.

bofm -l filename -iip_address

where:v filename is the name of

the configuration file.v ip_address is the IPv4 or

IPv6 IP address of theTFTP server where theconfiguration file islocated.

Note: Both the -l filenameoption and the -iip_address option need tobe specified.

This command can only berun by users who haveone or more of thefollowing commandauthorities:v Supervisorv Chassis configuration


-T system:mm[x]



Table 11. bofm command (continued)


Apply BOFMconfiguration tospecified BladeCenterunits, bays and portswhile ignoring duplicatelines in theconfiguration file

Copies a configuration file from aTFTP server to the specifiedmanagement module, which thenconfigures BladeCenter units,blade servers, and I/O modules,even if it encounters duplicatelines in the configuration file.


bofm -l filename -iip_address -d off




v The -d off optioncauses bofm to ignoreduplicate lines in theconfiguration file.




-T system:mm[x]





Apply BOFMconfiguration tospecified BladeCenterunits, bays, and portsunless there areduplicate lines in theconfiguration file

Copies a configuration file from aTFTP server to the specifiedmanagement module, which thenconfigures BladeCenter units,blade servers, and I/O modules,but halts the operation if itencounters duplicate lines in theconfiguration file.


bofm -l filename -iip_address -d on




v The -d on option haltsbofm if there areduplicate lines in theconfiguration file.




-T system:mm[x]





Apply BOFMconfiguration tospecified BladeCenterunits, bays, and portseven if the bays arepowered on

Copies a configuration file from aTFTP server to the specifiedmanagement module, which thenconfigures BladeCenter units,blade servers, and I/O modules,after checking to make sure thatthe bays are not powered on.


bofm -l filename -iip_address -p on




v The -p on option haltsthe bofm command ifbays are powered on.




-T system:mm[x]





Apply BOFMconfiguration tospecified BladeCenterunits, bays, and portsunless bays are poweredon

Copies a configuration file from aTFTP server to the specifiedmanagement module, which thenconfigures BladeCenter units,blade servers, and I/O modules,without checking if the bays arepowered on.

The configuration file is acomma-separated values (CSV) filethat assigns IP addresses and othervalues to BladeCenter units, bays,and ports.Note: Do not change the BOFMconfiguration while a blade serveris powered on.

bofm -l filename -iip_address -p off




v The -p off option forcesBOFM to apply theconfiguration file toblade servers that arepowered on.




-T system:mm[x]





Apply BOFMconfiguration tospecified BladeCenterunits, bays, and ports(verbose)

Copies a configuration file from aTFTP server to the specifiedmanagement module, which thenconfigures BladeCenter units,blade servers, and I/O modules, aprocess which might take severalminutes. The detailed informationis shown after the update iscomplete.

bofm -l filename -iip_address -v







-T system:mm[x]


Example:

To apply a new BOFM configuration file to a set of BladeCenter units and viewdetails of the procedure, while management module 1 is set as the persistentcommand environment, at the system:mm[1]> prompt, typebofm -i 9.148.8.2 -l apply.csv -v

The following example shows the information that is returned from this command:system:mm[1]> bofm -i 9.148.8.2 -l apply.csv -vTFTP file upload successful.Starting to apply new BOFM configuration on MMPercent complete: 100%Status: Confirmed configuration change.Percent complete: 100%Status: Configuration applied.Applying new BOFM configuration on MM - Completed.system:mm[1]>


boot commandThis command resets blade servers with several different restart options.

Table 12. boot command


Reset blade server Performs an immediate reset andrestart of the specified blade server.

This command will start a bladeserver that is turned off.

boot

This command can onlybe run by users who haveone or more of thefollowing commandauthorities:v Supervisorv Blade administration


-T system:blade[x]

where x is the bladeserver bay number.

Reset blade server tocommand console

Resets the specified blade server,causing it to open a commandconsole with an SOL session whenit restarts.


boot -c


and blade remotepresence


-T system:blade[x]


Power cycle Cycles power for the specifiedblade server. If the blade server isoff, it will turn on. If the bladeserver is on, it will turn off andthen turn on.

boot -p powercycle



-T system:blade[x]


Reset blade server Performs an immediate reset andrestart of the specified blade server.


boot -p reset



-T system:blade[x]



Example: To boot the blade server in blade bay 3, while management module 1 isset as the persistent command environment, at the system:mm[1]> prompt, typeboot -T system:blade[3]

The following example shows the information that is returned:system:mm[1]> boot -T system:blade[3]OKsystem:mm[1]>


bootmode commandThis command sets and displays the boot mode settings for blade servers installedin the BladeCenter unit that support this feature.

Table 13. bootmode command


Display blade serverboot mode

Displays the boot mode settings ofthe specified blade server.Note: This command will executeonly on blade servers that supportthe bootmode feature.

bootmode -T system:blade[x]


Set blade server bootmode

Sets the copy of firmware that thespecified blade server will use toboot:v Temporary: booting from the

temporary copy is recommendedsince it typically contains thelatest enhancements and fixes.

v Permanent: booting from thepermanent copy should be usedonly when booting from thetemporary copy is no longerpossible.

Changes to the boot mode settingtake effect after the next restart ofthe blade server.Note: This command will executeonly on blade servers that supportthe bootmode feature.

bootmode -p mode

where mode is:v temp for temporary

firmware copy.v perm for permanent

firmware copy.



-T system:blade[x]


Example: To view the boot mode of the blade server in bay 2, while this bladeserver is set as the persistent command environment, at the system:blade[2]>prompt, typebootmode

To set the boot mode of the blade server in bay 2 to permanent, while this bladeserver is set as the persistent command environment, at the system:blade[2]>prompt, typebootmode -p perm

The following example shows the information that is returned from thesecommands:system:blade[2]> bootmodeactive: temporarypending: Invalid boot mode typesystem:blade[2]> bootmode -p permSet the blade boot mode to permanent succeeded.The setting will become active after the next reboot of the blade.system:blade[2]> bootmodeactive: temporarypending: permanentsystem:blade[2]>


bootseq commandThis command sets and displays the boot sequence settings for blade serversinstalled in the BladeCenter unit.

Table 14. bootseq command


Display blade serverboot sequence

Displays the boot sequence of thespecified blade server. Possiblereturn values are:v floppy (diskette drive)v usbdisk (USB device)v iscsi (iSCSI)v iscsicrt (iSCSI critical)v nw (network)v nodev (no device)v hd0 (hard disk drive 0)v hd1 (hard disk drive 1)v hd2 (hard disk drive 2v hd3 (hard disk drive 3)v hd4 (hard disk drive 4)v cd (CD-ROM drive)v usb (media tray)v hyper (hypervisor)v uefi (unified extensible firmware

interface)v legacy (UEFI-specified legacy

sequence)

bootseq -T system:blade[x]



Table 14. bootseq command (continued)


Set boot sequence forblade server

Sets the boot sequence of thespecified blade server.

bootseq devicelist

where devicelist has one ormore of the following bootdevices specified, in orderof preference:v floppy for the diskette

drive(non-POWER-basedblade servers only)

v usbdisk for a USBdevice (not supportedby all blade servers)

v iscsi for iSCSIv iscsicrt for iSCSI

criticalv nw for network - PXEv nodev for no devicev hd0 for hard disk drive

0v hd1 for hard disk drive




4v cd for the CD-ROM

drivev usb for the media tray

(non-POWER-basedblade servers installedin BladeCenter T unitsonly)

v hyper for hypervisor(only for blade serversthat use hypervisorvirtualization)

v uefi for unifiedextensible firmwareinterface (UEFI) (onlyfor blade servers thatsupport this feature)

v legacy for theUEFI-specified legacyboot sequence (only forblade servers thatsupport this feature)


-T system:blade[x]





Set boot sequence forblade server

(continued)

A boot sequence of up tofour boot devices can bespecified. If fewer thanfour devices are specified,the remaining items in thesequence are set to nodev.






Set boot sequence for allblade servers

Sets the same boot sequence for allblade servers installed in theBladeCenter unit.

bootseq -all devicelist

where devicelist has one ormore of the following bootdevices specified, in orderof preference:v floppy for the diskette

drive(non-POWER-basedblade servers only)

v usbdisk for a USBdevice (not supportedby all blade servers)

v iscsi for iSCSIv iscsicrt for iSCSI

criticalv nw for network - PXEv nodev for no devicev hd0 for hard disk drive





4v cd for the CD-ROM

drivev usb for the media tray

(non-POWER-basedblade servers installedin BladeCenter T unitsonly)

v hyper for hypervisor(only for blade serversthat use hypervisorvirtualization)

v uefi for unifiedextensible firmwareinterface (only for bladeservers that support thisfeature)


-T system:blade[x]





Set boot sequence for allblade servers

(continued)

v legacy for theUEFI-specified legacyboot sequence (only forblade servers thatsupport this feature)

A boot sequence of up tofour boot devices can bespecified. If fewer thanfour devices are specified,the remaining items in thesequence are set to nodev.



Example: To set a boot sequence of diskette drive, CD-ROM drive, and hard diskdrive 0 for the blade server in blade bay 3, while the blade server in blade bay 3 isset as the persistent command environment, at the system:blade[3]> prompt, typebootseq floppy cd hd0

To display the boot sequence for the blade server in blade bay 3, while the bladeserver in blade bay 3 is set as the persistent command environment, at thesystem:blade[3]> prompt, typebootseq

The following example shows the information that is returned from these twocommands:system:blade[3]> bootseq floppy cd hd0OKsystem:blade[3]> bootseqfloppycdhd0nodevsystem:blade[3]>


buildidcfg commandThis command creates, displays, and configures the list of firmware build IDs forthe blade servers.

Table 15. buildidcfg command


Display blade serverfirmware build IDs

Displays list of blade serverfirmware build IDs.Note: The build ID list must bebuilt using the -create commandoption before it can be displayed.

buildidcfg -T system

Create blade serverbuild ID list

Creates an initial firmware build IDlist for all blade servers installed inthe BladeCenter unit.Note: The build ID list containsinformation for only those bladeservers that have VPD which isfully accessible by the advancedmanagement module. Any bladeservers with VPD that isunavailable or failed will beignored and not appear in the list..

buildidcfg -create

This command can onlybe run by users who haveone or more of thefollowing commandauthorities:v Supervisorv Blade administrationv Blade configurationv Blade remote presence


-T system


Table 15. buildidcfg command (continued)


Add blade server buildID list entry

Adds a new blade server firmwarebuild ID entry to the list.Note: All options must be specifiedwhen adding a new firmware buildID entry. The arguments formanufacturer, machine type,firmware type, and build ID cannotbe blank or unspecified; however,the argument for build revision canbe blank or not set.

buildidcfg -ab -mfgmanufacturer -mtmachine_type -ft type -idbuild_id -rev build_rev

where:v manufacturer is a

manufacturer name, upto 31 characters inlength, enclosed inquotation marks. Themanufacturer name cancontain spaces, but noleading or trailingspaces are allowed.

v machine_type is amachine type, up to 31characters in length,enclosed in quotationmarks. The machinetype can contain spaces,but no leading ortrailing spaces areallowed.

v firmware_type is bios,diags, or bmc.

v build_id is a firmwarebuild ID, up to 31characters in length,enclosed in quotationmarks. The firmwarebuild ID can containspaces, but no leadingor trailing spaces areallowed.

v build_rev is a firmwarebuild revision, up to 31characters in length,enclosed in quotationmarks. The firmwarebuild revision cancontain spaces, but noleading or trailingspaces are allowed.



-T system




Update blade serverbuild ID list entry -manufacturer

Update the manufacturer for thespecified blade server firmwarebuild ID entry.Note:v The index number for each entry

in the list is found by runningthe buildidcfg command withno options.

v The argument for manufacturercannot be blank or unspecified.

buildidcfg -ub index-mfg manufacturer

where:v index is the index of the

build ID list entry.v manufacturer is a

manufacturer name, upto 31 characters inlength, enclosed inquotation marks. Themanufacturer name cancontain spaces, but noleading or trailingspaces are allowed.



-T system

Update blade serverbuild ID list entry -machine type

Update the machine type for thespecified blade server firmwarebuild ID entry.Note:v The index number for each entry


v The argument for machine typecannot be blank or unspecified.

buildidcfg -ub index -mtmachine_type


build ID list entry.v machine_type is a

machine type, up to 31characters in length,enclosed in quotationmarks. The machinetype can contain spaces,but no leading ortrailing spaces areallowed.



-T system




Update blade serverbuild ID list entry -firmware type

Update the firmware type for thespecified blade server firmwarebuild ID entry.Note:v The index number for each entry


v The argument for firmware typecannot be blank or unspecified.

buildidcfg -ub index -ftfirmware_type


build ID list entry.v firmware_type is bios,

diags, or bmc.



-T system

Update blade serverbuild ID list entry -firmware build ID

Update the firmware build ID forthe specified blade server firmwarebuild ID entry.Note:v The index number for each entry


v The argument for build IDcannot be blank or unspecified.

buildidcfg -ub index -idbuild_id


build ID list entry.v build_id is a firmware

build ID, up to 31characters in length,enclosed in quotationmarks. The firmwarebuild ID can containspaces, but no leadingor trailing spaces areallowed.



-T system




Update blade serverbuild ID list entry -firmware build revision

Update the firmware build revisionfor the specified blade serverfirmware build ID entry.Note:v The index number for each entry


v The argument for the buildrevision can be blank or not set.

buildidcfg -ub index-rev build_rev


build ID list entry.v build_rev is a firmware

build revision, up to 31characters in length,enclosed in quotationmarks. The firmwarebuild revision cancontain spaces, but noleading or trailingspaces are allowed.



-T system

Delete all entries fromblade server build IDlist

Delete all blade server firmwarebuild ID entries from the list.

buildidcfg -db all



-T system




Delete entry from bladeserver build ID list

Delete a specific blade serverfirmware build ID entry from thelist.Note: The index number for eachentry in the list is found byrunning the buildidcfg commandwith no options.

buildidcfg -db index

where index is the indexnumber of a specific buildID list entry to delete.



-T system

Import blade serverbuild ID list

Import a firmware build ID listfrom file.

The file name to import mustspecify a qualified location for thebuild ID list image that indicatesthe protocol to be used. Forexample, tftp://192.168.0.1/tmp/buildid.txt.

buildidcfg -importfilename

where filename is aqualified location of up to256 characters in lengththat indicates the protocolto be used (tftp, ftp, ftps,http, or https) andcontains any characterexcept the percent sign (% ) or double-quote ( " ).



-T system




Export blade serverbuild ID list

Export the current build ID list to aspecified TFTP server.

The build ID list to export mustspecify a qualified location,including an IP address for thebuild ID list image. For example,tftp://192.168.0.1/tmp/buildid.txt.

buildidcfg -exportip_address

where ip_address is aqualified location of up to256 characters in lengththat indicates the TFTPprotocol and a valid filename. It can contain anycharacter except thepercent sign ( % ) ordouble-quote ( " ).



-T system

Example: To create the initial build ID list, while the BladeCenter unit is set as thepersistent command environment, at the system> prompt, typebuildidcfg -create

To view the build ID list, while the BladeCenter unitis set as the persistentcommand environment, at the system> prompt, typebuildidcfg

The following example shows the information that is returned from thesecommands:system> buildidcfg -createOKsystem> buildidcfgIndex Manufacture Machine Type Firmware Type Build ID Revision1 IBM 8853 Blade Sys Mgmt Processor BCBT58A 1.18

2 IBM 8853 Diagnostics BCYT28AUS 1.06

3 IBM 8853 FW/BIOS BCE141AUS 1.17

4 IBM 7971 Blade Sys Mgmt Processor BABT55A 1.32

5 IBM 7971 Diagnostics BAYT37AUS 1.06

6 IBM 7971 FW/BIOS BAE155AUS 1.10

system>


chconfig commandThis command configures the BladeCenter unit Service Advisor feature.

Table 16. chconfig command


Display Service Advisorconfiguration

Displays the contact informationfor the Service Advisor feature.Service Advisor resides on youradvanced management module andmonitors your BladeCenter unit forhardware events. Upon detecting ahardware event, Service Advisorcaptures the event, error logs, andservice data, and can automaticallyreport the event to IBM support. Tosend call home event to IBMsupport, you must enable andconfigure Service Advisor. For eachcall home event IBM receives, aservice ticket will opened, and afollow-up call will be made. Thisfeature will generate a message toIBM when events occur in theBladeCenter unit or one of itscomponents that usually can beresolved without additionalproblem determination.Note: The system will wait fivedays before sending duplicateevents if they are leftunacknowledged in the activity log.

chconfig -T system:mm[x]


Display / accept ServiceAdvisor terms andconditions

Displays or accepts the terms of theService Advisor terms andconditions.

chconfig -li license

where license is

v view to view the ServiceAdvisor terms andconditions.

v accept to accept theService Advisor termsand conditions.



-T system:mm[x]



Table 16. chconfig command (continued)


Enable / disable ServiceAdvisor terms andconditions

Enables or disables the call-hometerms and conditions.Notes:v All contact information fields are

required before the ServiceAdvisor can be enabled.

v Call Home will connect to IBMthrough HTTPS and HTTP.HTTP Proxy fields must be set topermit for outbound traffic.

v Service Advisor also needs to setup DNS server address on theadvanced management module.

v Changing the Service Advisorsetting from disabled to enabledwill automatically trigger a testcall home and the ServiceAdvisor Activity Log will recordthis test call home.

chconfig -sa setting -scsupport_center

wherev setting is

– enable to activate theService Advisorterms and conditions.

– disable to suspendthe Service Advisorterms and conditions.

v support_center is the2–character ISO 3166country code of the IBMsupport center location.For example, thecountry code for theUnited States is US.

Notes:v Go to

http://www.iso.org/iso/country_codes/iso_3166_code_lists/ fora complete list ofcountry codes.

v Valid country codesmust refer to countriesthat have IBM supportcenters.



-T system:mm[x]



http://www.iso.org/iso/country_codes/iso_3166_code_lists/





Set contact informationfor Service Advisor

Sets contact information for theService Advisor.

chconfig -co "company"-cn "name" -cph "phone"-ce email -ca "address"-cci "city" -cs state -scsupport_center -cz"postalcode"

where:v "company" is the

quote-delimited contactcompany name, of up to30 characters in length.

v "name" is thequote-delimited contactname, of 1 to 30characters in length.

v "phone" is thequote-delimited contactphone number, of 5 to30 characters in length.

v email is email address ofthe contact person inthe formuserid@hostname (30characters maximum).The userid can bealphanumericcharacters, ".", "-", or "_"but must begin and endwith alphanumericcharacters. Thehostname can bealphanumericcharacters, ".", "-", or "_".It must contain at leasttwo domain items.Every domain itemshould begin and endwith an alphanumericcharacter and the lastdomain item should befrom 2 to 20 alphabeticcharacters.

v "address" is thequote-delimited streetaddress of the machinelocation, of 1 to 30characters in length.

v "city" is thequote-delimited city ofthe machine location, of1 to 30 characters inlength.


-T system:mm[x]





Set contact informationfor Service Advisor

(continued)

v state is the state of themachine location, of 2to 3 characters inlength.

v "postalcode" is thequote-delimited postalcode of the machinelocation, of 1 to 9alphanumeric charactersin length.






Set up HTTP proxy forService Advisor

Sets up HTTP proxy for ServiceAdvisor.

chconfig -ps setting -lochostname -po port -u“username” -pw “password”

where:

v setting is enabled ordisabled

v hostname is the fullyqualified host name orIP address of the HTTPproxy, of 1 to 63characters in length.

v port is the port of theHTTP proxy, a numberfrom 1 to 65535,inclusive.

v “username” is thequote-delimited username, of 1 to 30characters in length.

v “password” is thequote-delimitedpassword of the HTTPproxy, of up to 15characters in length



-T system:mm[x]


Example:

To accept the Service Advisor terms and conditions, while management module 1is set as the persistent command environment, at the system:mm[1]> prompt, typechconfig -li accept

To display the current configuration of the Service Advisor, while managementmodule 1 is set as the persistent command environment, at the system:mm[1]>prompt, typechconfig


The following example shows the information that is returned from these twocommands:system:mm[1]> chconfig -li acceptOKsystem:mm[1]> chconfig-sa enabled-sc US-ca No 399, Keyuan Rd,-cci Dallas-ce [email protected] bob-co IBM-cph 800-555-1111-cs TX-cz 75210-loc google.cn-po 8080-ps disabled-u User-001system:mm[1]>


chlog commandThis command is used to display up to five call-home activity log entries and tomark a call-home event entry as acknowledged or unacknowledged.

Table 17. chlog (display call-home activity log) command


Display call-homeactivity log entries

Displays the last five entries fromthe call-home activity log.Notes:v The entries are displayed in

reverse chronological order (mostrecent call-home entry first).

v The system will wait 5 daysbefore sending duplicate eventsif they are not acknowledged ascorrected in the activity log.

v Call-home events are usuallythose that can be resolvedwithout additional problemdetermination.

chlog -T system:mm[x]


Display FTP/TFTPserver call-home activitylog entries

Displays the last five FTP/TFTPserver entries from the call-homeactivity log.Notes:v The entries are displayed in



chlog -f -T system:mm[x]


Display IBM Supportcall-home activity logentries

Displays the last five IBM Supportentries from the call-home activitylog.Notes:v The entries are displayed in



v Call-home events are usuallythose that can be resolvedwithout additional problemdetermination.

chlog -s -T system:mm[x]



Table 17. chlog (display call-home activity log) command (continued)


Acknowledge /unacknowledgecall-home activity logentries

Marks the selected call-home eventas acknowledged (yes) orunacknowledged (no) when thecall-home event has been corrected.Note: The system will wait fivedays before sending duplicateevents if they are leftunacknowledged in the activity log.

chlog -index -ack option

where:

v index is the index of thecall-home event entry

v option is yes or no



-T system:mm[x]


Example: To display five call-home activity log entries, while management module1 is set as the persistent command environment, at the system:mm[1]> prompt, typechlog

To mark the call-home event with index number 14 as acknowledged, typechlog -14 -ack yes

The following example shows the information that is returned from these twocommands:system:mm[1]> chlogIndex Ack Send Result Assigned Num Event ID Sev Source

Time Message14 No Success NULL 0x00016802 I CHASSIS06/04/08 09:11:11 Test Call Home generated by USERID.15 No Pending NULL 0x00016802 I CHASSIS06/04/08 09:11:12 Test Call Home generated by USERID.

system:mm[1]>chlog -14 -ack yesOKsystem:mm[1]>


chmanual commandThis command tests the BladeCenter unit call-home feature setup.

Table 18. chmanual command


Create call-homeproblem message

Create a call-home problemmessage for a management moduleor blade server.

chmanual -desc"description"

where "description" is aquote-delimited problemdescription of 1 to 100characters in length.





configuration


-T system

-T system:blade[x]



Table 18. chmanual command (continued)


Generate call-home testcall home

Manually generate a test call-homeevent that transmits the samplecall-home problem message.

chmanual -test





configuration


-T system

Example:

To create a call-home test message, at the system:> prompt, typechmanual -desc "This is a test."

To manually send a test message, while the system is set as the persistentcommand environment, at the system> prompt, typechmanual -test

The following example shows the information that is returned from these twocommands:system> chmanual -desc "This is a test."OKsystem> chmanual -testOKsystem>


cin commandThis command can be used to view and configure the chassis internal network forup to 14 supported chassis internal network (CIN) configurations, globally, or forspecified entries. You can define a CIN by creating a pool of VLAN (virtual localarea network) ID/IP address pairs, each of which is a CIN entry.

Table 19. cin command


Display CINconfiguration table

Displays the configuration table forthe chassis internal network.Possible return values are:v Global CIN enabled or disabled

statusv CIN index

– VLAN ID– IP address– index entry enabled or disabled

status

cin -T system

Set global CIN state Sets the global state of CIN toenabled or disabled.

cin -global -en state

where state isv onv off


management andchassis configuration


-T system

Clear all CINconfiguration entries

Deletes all CIN configurationentries.

cin all -clear




-T system


Table 19. cin command (continued)


Turn all index entries onor off

Turns all CIN index entries on oroff.

cin all -en state

where state isv onv off




-T system

Delete CINconfiguration entry

Deletes the specified CINconfiguration entry.

cin -entry_index -clear

where entry_index is anumber between 1 and 14(inclusive).




-T system

Set CIN configurationentry to enable ordisable

Enables or disables a CINconfiguration entry.

If you enable or disable anon-existent entry, the action isignored and no error message isreturned.

cin -entry_index -en statewhere:v entry_index is a number

between 1 and 14, andv state is

– on– off




-T system




Create a CINconfiguration entry

Creates a CIN index entry.

If the CIN index is currently empty,both -id and -ip must be specified.Note: The VLAN ID must bedifferent from that of the bladeserver management module.

cin -entry_index -id vlan_id-ip ip_address

where:v entry_index is a number

between 1 and 14,v vlan_id is a VLAN ID

number between 3 and4094 (inclusive),

v ip_address is a valid IPaddress.




-T system

Specify valid IP addressfor CIN index entry

Specifies the IP address of the CINindex entry. The CIN IP addressmust be a valid IP address. An erroris displayed if the IP address isinvalid.

Note:v If the index is not empty, the IP

address can be specifiedseparately.

v CIN entries cannot have matchingIP addresses unless they are0.0.0.0. and have different VLANIDs.

v If the CIN IP address is 0.0.0.0,the blade server IP address forCIN which is configured in theblade server operating systemcannot be in the same subnet asthat of the advanced managementmodule.

v The IP address cannot bemulti-cast and cannot match theIP address of the managementmodule.

cin -entry_index -ipip_address


between 1 and 14v ip_address is a valid IP

address.

You can overwriteparameters of an existingdefinition; for example,cin -1 -ip 0.0.0.0overwrites the currentCIN IP address of the firstcin entry. If the entry doesnot exist, an error isreturned.




-T system




Specify VLAN ID forCIN entry

Set the VLAN ID for the specifiedCIN entry.

Note:v If the index is not empty, the ID

can be specified separately.v The VLAN ID must be different

from that of the managementmodule.

cin -entry_index -idvlan_id


between 1 and 14v vlan_id is a number

between 3 and 4094(inclusive).




-T system

Example:

To view chassis internal network information for the management module, whilethis management module is set at the persistent command environment, at thesystem> prompt, typecin

The following example shows the information that is returned from this command:system> cin-global -en off

Index 1-id 11-ip 11.1.1.1-en on

Index 2-id 12-ip 22.1.1.1-en on

Index 3not used

Index 4not used

Index 5not used

Index 6not used

Index 7not used


Index 8not used

Index 9not used

Index 10not used

Index 11not used

Index 12-id 123-ip 23.1.1.1-en on

Index 13not used

Index 14not usedsystem>


cinstatus commandThis command displays a table listing the VLAN ID, the IP address, the MACaddress, and the status of each chassis internal network (CIN) connection.

Table 20. cinstatus command


Display entries of theCIN status table

Reads entries of the CIN statustable, five at a time. Each entry ofthe table returns:

v CIN VLAN ID

v CIN IP address

v CIN MAC address

v CIN status text

cinstatus -T system

Display status of firstfive CIN entries

Displays the first five entries of theCIN status table.

cinstatus -f -T system

Display entire CINstatus table

Displays all the entries in the CINstatus table.

cinstatus -a -T system

Note: An asterisk * next to an IP address indicates a learned entry.

Example:

To display five entries of the CIN status table, while the BladeCenter unit is set asthe persistent environment, at the system> prompt, typecinstatus

The following example shows the information that is returned from this commandsystem> cinstatus

Note: * next to IP address indicates a learned entry

VLAN IP Address MAC Address Status---- ---------------- ------------------ --------------------

1. 4094 0.0.0.1 Not Operational2. 4094 0.0.0.2 Not Operational3. 4 0.0.0.0 Operational4. 4093 0.0.0.1 Not Operational5. 4094 0.0.0.0 Operational

Last entry reachedsystem>


clear commandThis command restores the primary management module configuration or an I/O(switch) module configuration to the default settings.

The command must always include the -cnfg or -config option.

Table 21. clear command


Restore defaultconfiguration of primarymanagement moduleand keep logs

Restores the default configurationof the primary managementmodule, retaining log information;then, resets the managementmodule.

No results are returned from thiscommand because it resets themanagement module.

When you restore themanagement-module configuration,the Ethernet configuration methodis set to a value of dthens. After themanagement module resets, thiscauses the management module totry dhcp configuration and thendefault to the static IPconfiguration, which might causethe management module to remainoffline for longer than normal. Seethe “ifconfig command” on page171 for information.

clear -cnfg

This command can onlybe run by users who haveone or more of thefollowing commandauthorities:v Supervisorv Chassis administration

and chassisconfiguration


-T system:mm[x]


Restore defaultconfiguration of I/Omodule

Restores the configuration of thespecified I/O module to the defaultsettings.

clear -cnfg

This command can onlybe run by users who haveone or more of thefollowing commandauthorities:v Supervisorv I/O module

administration and I/Omodule configuration


-T system:switch[x]

where x is theI/O-module baynumber.


Example: To restore the primary management-module configuration to defaultsettings and retain log information, while management module 1 is set as thepersistent command environment, at the system:mm[1]> prompt, typeclear -cnfg

No results are returned from this command. After the management module resets,you will need to start a new command-line session.


clearlog commandThis command clears the management-module audit event log, the system eventlog, or both.

Table 22. clearlog (clear management-module event log) command


Clearmanagement-moduleevent log

Clears the management-moduleevent log and displays a messageconfirming that the specified eventlog was cleared.

clearlog


management


-T system:mm[x]


Clear advancedmanagement-moduleaudit or system eventlog

Clears the management-moduleaudit event log, the system eventlog, or both, and displays amessage confirming that thespecified event log was cleared.Notes:

v Audit log events are created bythe actions of users.

v If the log_type is not specified,this command will clear bothlogs.

v Although system events andaudit events are stored internallyin separate log files, they arepresented to the user as a singlelog that can be filtered.

clearlog -l log_type

where log_type is audit orsystem.


management


-T system:mm[x]


Example: To clear the management-module audit log, while management module 1is set as the persistent command environment, at the system:mm[1]> prompt, typeclearlog -1 audit

The following example shows the information that is returned:system:mm[1]> clearlog -1 auditOKsystem:mm[1]>


clock commandThis command configures and displays the advanced management-module clocksettings.

Table 23. clock command


Display advancedmanagement moduleclock information

Displays the following informationfor the advanced managementmodule clock:v current date and timev GMT (Greenwich-Mean Time)

offsetv daylight-savings time setting

clock -T system:mm[x]


Set advancedmanagement moduledate

Sets the date for the advancedmanagement module clock.

clock -d date

where date is the currentcalendar date inmm/dd/yyyy format.

The month and day can beinput as single digits. Theyear must be a four-digitnumber between 2000 and2089, inclusive.

This command can only berun by users who have thefollowing commandauthorities:v Supervisorv Chassis configuration


-T system:mm[x]


Set advancedmanagement moduletime

Sets the time for the advancedmanagement module clock.

clock -t time

where time is the currenttime in 24-hour hh:mm:ssformat.

The hours, minutes, andseconds can all be input assingle digits.



-T system:mm[x]



Table 23. clock command (continued)


Set advancedmanagement moduleclock GMT offset

Sets the time for the advancedmanagement module clock.

clock -g offset

where offset is a valuebetween +12 and -12, inhours and minutes.Positive offsets are enteredusing the form:GMT+hh:mm, +hh:mm,+hh, hh:mm, or hh; where,the hours and minutes canbe input as single digits.Negative offsets areentered using the form:GMT-hh:mm, -hh:mm, or-hh; where, the hours andminutes can be input assingle digits. Valid offsetsare:v GMT+0:00v GMT+1:00v GMT+2:00v GMT+3:00v GMT+3:30v GMT+4:00v GMT+4:30v GMT+5:00v GMT+5:30v GMT+6:00v GMT+7:00v GMT+8:00v GMT+9:00v GMT+9:30v GMT+10:00v GMT+11:00v GMT+12:00v GMT-12:00v GMT-11:00v GMT-10:00v GMT-9:00v GMT-8:00v GMT-7:00v GMT-6:00v GMT-5:00v GMT-4:00v GMT-3:30v GMT-3:00v GMT-2:00v GMT-1:00


-T system:mm[x]





Set advancedmanagement moduleclock GMT offset

(continued)

For some time zones thatuse daylight-savings time(GMT +10, +2, -5, -6, -7, -8,-9), a special value for the-dst option must bespecified to identify thecorrect daylight-savingstime scheme to use in thattime zone.

This command can only berun by users who have thefollowing commandauthorities:v Supervisorv Chassis configuration





Set advancedmanagement moduleclock daylight-savingstime mode

Sets the daylight-savings time modefor the advanced managementmodule clock.

clock -dst dst_mode

where dst_mode is one ofthe following:v offv onv for GMT+2:00:

– off– ee (Eastern Europe)– gtb (Great Britain)– egt (Egypt)– fle (Finland)

v for GMT+10:00:– off– ea (Eastern Australia)– tas (Tasmania)– vlad (Vladivostok)

v for GMT-9:00 toGMT-5:00:– off– uc (United States and

Canada)– other (other

locations)v for GMT-4:00:

– off– can (Canada)– other (other

locations)

Daylight-savings time isnot observed in thefollowing GMT offsets:GMT+4:00, GMT+4:30,GMT+5:30, GMT+6:00,GMT+7:00, GMT+8:00,GMT+11:00, GMT-12:00,GMT-11:00, andGMT-10:00.



-T system:mm[x]



Example: To set the management-module for operation in the US Eastern timezone in compliance with new daylight-savings time rules, while managementmodule 1 is set as the persistent command environment, at the system:mm[1]>prompt, typeclock -g +5 -dst uc

To display the clock information for the primary management module, whilemanagement module 1 is set as the persistent command environment, at thesystem:mm[1]> prompt, typeclock

The following example shows the information that is returned from these twocommands:system:mm[1]> clock -g +5 -dst ucOKsystem:mm[1]> clock10/17/2006 02:27:11 GMT+5:00 dst ucsystem:mm[1]>


config commandThis command sets and displays the name of the advanced management moduleor blade server and the location and contact name for the advanced managementmodule.

Table 24. config command


Display name of bladeserver

Displays the name of the specifiedblade server.

config -T system:blade[x]


Display name ofmanagement module

Displays the following informationfor the command target:v Namev Locationv Contact name

config -T system:mm[x]


Display identifyinginformation forBladeCenter unit

Displays the following informationfor the command target:v Universally unique identifierv Serial numberv Type/model

config -T system

Set name ofmanagement module orblade server

Sets the name of the primarymanagement module or specifiedblade server.

config -name name

where name is up to 15characters in length.

Blade server names cannotcontain angle brackets ("<"and ">"), and advancedmanagement modulenames can only containalphanumeric characters,hyphens, pound signs,underscores, and periods.


(for managementmodule)



-T system:mm[x]

-T system:blade[x]

where x is the primarymanagement-moduleor a blade server baynumber.


Table 24. config command (continued)


Set location ofmanagement module

Sets the location of the primaryadvanced management module.

config -loc "location"

where "location" is up to47 characters in lengthand contained withindouble-quotes.

Advanced managementmodule locations cancontain any characterother than "<" and ">".



-T system:mm[x]


Set contact name foradvanced managementmodule

Sets the contact name for theprimary advanced managementmodule.

config -contact"contact_name"

where "contact_name" isup to 47 characters inlength and containedwithin double-quotes.

Advanced managementmodule contact names cancontain any characterother than "<" and ">".



-T system:mm[x]





Set universally uniqueidentifier (UUID) forBladeCenter unit

Sets the universally uniqueidentifier for the BladeCenter unit.Notes:

v Change the -uuid value only ifyou are certain it was notprogrammed correctly on thehardware. To prevent disruptingthe operation of IBM SystemsDirector, you should edit thisfield only if the midplane ofyour system has been replacedwith a new midplane that doesnot have this informationprogrammed on it.

v If you change the UUID on anexisting system to a random newvalue, IBM Systems Director willtreat this as a new system,distinct from the one identifiedby the old UUID.

v Changes to the UUID take effectafter the next restart of theadvanced management module.

config -uuid "unique_id"

where "unique_id" is 32hexadecimal digits and iscontained withindouble-quotes.



-T system

Set type/model forBladeCenter unit

Sets the type or model designatorfor the BladeCenter unit.Notes:

v Change the -tm value only if youare certain it was notprogrammed correctly on thehardware. To prevent disruptingthe operation of IBM SystemsDirector, you should edit thisfield only if the midplane ofyour system has been replacedwith a new midplane that doesnot have this informationprogrammed on it.

v Changes to the type/model takeeffect after the next restart of theadvanced management module.

config -tm "type_model"

where "type_model" is upto seven characters inlength and containedwithin double-quotes.

Advanced managementmodule type / modeldesignators can containany character other than"<" and ">".



-T system




Set serial number forBladeCenter unit

Sets the serial number for theBladeCenter unit.Notes:

v Change the -sn value only if youare certain it was notprogrammed correctly on thehardware. To prevent disruptingthe operation of IBM SystemsDirector, you should edit thisfield only if the midplane ofyour system has been replacedwith a new midplane that doesnot have this informationprogrammed on it.

v Changes to the serial numbertake effect after the next restartof the advanced managementmodule.

config -sn "serial_number"

where "serial_number" isup to seven characters inlength and containedwithin double-quotes.

Advanced managementmodule serial numberscan contain any characterother than "<" and ">".



-T system

Example:

To set the management module name to IBM_lab, while management module 1 isset as the persistent command environment, at the system:mm[1]> prompt, typeconfig -name IBM_lab

To display the management module name, location, and contact name, whilemanagement module 1 is set as the persistent command environment, at thesystem:mm[1]> prompt, typeconfig

The following example shows the information that is returned from these twocommands:system:mm[1]> config -name IBM_labOKsystem:mm[1]> config-name IBM_lab-contact John_Doe-loc Main_Labsystem:mm[1]>


console commandThis command sets up a serial over LAN connection to the command console of ablade server.

To end an SOL session, press Esc followed by an open parenthesis:

Esc (

Table 25. console command


Create SOL session withblade server

Creates an SOL connection to thespecified blade server.Note: The advanced managementmodule supports a persistent SOLconnection that remains intact untilyou escape from the SOL console,or another user uses the overrideoption to take over your SOLconsole. A persistent command, ifdropped, automatically attempts toreconnect.

console

This command can onlybe run by users who haveone or more of thefollowing commandauthorities:v Supervisorv Blade remote presence


-T system:blade[x]


Create override SOLsession with bladeserver

Creates an SOL connection to thespecified blade server, with theoverride option enabled. Thisenables you to end an existing SOLsession to that blade server andstart a new one.Note: The advanced managementmodule supports combing this isoption with the -l option tooverride an existing session, andnot reconnect if the connectiondrops.

console -o



-T system:blade[x]


Create non-persistentSOL session with bladeserver

Creates an SOL connection to thespecified blade server for userswho do not want to use apersistent session.Note: This option can be combinedwith the -o option to override anexisting session, and not reconnectif the connection drops.

console -l



-T system:blade[x]



Example: To start an SOL connection to the blade server in blade bay 14, while thisblade server is set as the persistent command environment, at the system:mm[x]>prompt, typeconsole -T system:blade[14]


dhcpinfo commandThis command displays the IP configuration that is assigned by a DHCP server tothe primary management module external network interface, blade servermanagement network interfaces, and I/O module DHCPv6 server.

Note: The dhcpinfo command does not apply to management module channeleth1, which always uses a static IP configuration.

Table 26. dhcpinfo command


Display Ethernetchannel 0 DHCPconfiguration formanagement module

If the IP configuration formanagement module eth0 isassigned by a DHCP server, theconfiguration that is assigned bythe DHCP server and DHCP serverinformation is displayed. If the IPconfiguration for eth0 is notassigned by a DHCP server, anerror message is displayed. Possibleconfiguration values returned are:v -server dhcp_ip_addressv -n hostnamev -i ip_addressv -g gateway_addressv -s subnet_maskv -d domainnamev -dns1 primary_dns_ip_addressv -dns2 secondary_dns_ip_addressv -dns3 tertiary_dns_ip_1addressv -server6 IPv6_dhcp_ip_addressv -i6 IPv6_addressv -d6 IPv6_domainnamev -dns61

IPv6_primary_dns_ip_addressv -dns62

IPv6_secondary_dns_ip_addressv -dns63

IPv6_tertiary_dns_ip_1address

dhcpinfo -eth0 -T system:mm[x]


Display managementnetwork DHCPconfiguration for bladeserver

If the IPv6 configuration for thespecified blade server managementnetwork Ethernet channel isassigned by a DHCP server, theIPv6 IP address is displayed. If theIP configuration for the specifiedblade server management networkEthernet channel is not assigned bya DHCP server, an error message isdisplayed.

dhcpinfo -ethx

where x is the blade servermanagement networkchannel number todisplay.

-T system:blade[x]


Display DHCPconfiguration for I/Omodule

If the IPv6 configuration for thespecified I/O module is assignedby a DHCP server, the IPv6 IPaddress is displayed. If the IPv6configuration for the I/O module isnot assigned by a DHCP server, anerror message is displayed.

dhcpinfo -T system:switch[x]



Example: To display the DHCP server assigned network settings that do notsupport IPv6 for Ethernet channel 0, while management module 1 is set as thepersistent command environment, at the system:mm[1]> prompt, typedhcpinfo -eth0

The following example shows the information that is returned:system:mm[1]> dhcpinfo -eth0-server 192.168.70.29-n MM00096BCA0C80-i 192.168.70.183-g 192.168.70.29-s 255.255.255.0-d linux-sp.raleigh.ibm.com-dns1 192.168.70.29-dns2 0.0.0.0-dns3 0.0.0.0system:mm[1]>

To display the DHCP server assigned network settings that support IPv6 forEthernet channel 0, while management module 1 is set as the persistent commandenvironment, at the system:mm[1]> prompt, typedhcpinfo -eth0

The following example shows the information that is returned:system:mm[1]> dhcpinfo -eth0DHCP is disabled-server6 FE80:0000:0000:0000:0202:55FF:FE21:0F23-i6 2000:1013:0000:0000:DDDD:CCCC:D7C8:F925-d6 datacentertech.net-dns61 2000:1013:0000:0000:0000:0000:0100:0100-dns62 2000:1013:0000:0000:0000:0000:0100:0101-dns63 2000:1013:0000:0000:0000:0000:0100:0102system:mm[1]>


displaylog commandThis command displays management-module event log entries.

Note: Event descriptions and suggested user actions for items shown by thedisplaylog command can be viewed using the “eventinfo command” on page 138.

Table 27. displaylog (display management-module event log) command


Displaymanagement-moduleevent log entries

Displays five entries from themanagement-module event log.The first time the command isexecuted, the five most recent logentries are displayed. Eachsubsequent time the command isissued, the next five entries in thelog display.

displaylog -T system:mm[x]


Displaymanagement-moduleevent log entries (resetcounter)

Resets the counter and displays thefirst five most recent entries in themanagement-module event log.

displaylog -f -T system:mm[x]


Display log entries withEvent ID

Displays log entries with Event ID. displaylog -e -T system:mm[x]


Display log entries withtheir call-home flag

Displays log entries with theircall-home flag.

displaylog -c -T system:mm[x]


Display allmanagement-moduleevent log entries

Displays all entries in themanagement module event log.

displaylog -a -T system:mm[x]


Display all event logfilters

Displays all filters that can be usedto control management moduleevent log output.

displaylog -filters -T system:mm[x]



Table 27. displaylog (display management-module event log) command (continued)


Display event log entriesfiltered by date

Displays management moduleevent log information that meetsthe specified date filter criteria.Note:v This command displays the first

five most recent entries in themanagement-module event logthat meet the specified filtercriteria. Adding the -a option tothe command displays all entriesthat meet the specified filtercriteria.

v If the filter criteria entered doesnot match the criteria previouslyspecified, this resets the counterand displays the first five mostrecent log entries that match thespecified filter criteria.

v The index number displayed foreach filtered log entry might notmatch the index number shownfor the same log entry displayedin an unfiltered list.

displaylog -datedate_filter

where date_filter is a pipe (| ) separated list of datefilters in mm/dd/yyformat.

-T system:mm[x]


Display event log entriesfiltered by severity level

Displays management moduleevent log information that meetsthe specified severity level filtercriteria.Note:v This command displays the first




displaylog -sevseverity_filter

where severity_filter is apipe ( | ) separated list ofseverity filters:v I (information)v E (error)v W (warning)

-T system:mm[x]


Display event log entriesfiltered by source

Displays management module loginformation that stored in the auditlog.

displaylog -src Audit -T system:mm[x]





Display event log entriesfiltered by every flagexcept the one specified

Displays management module loginformation that is stored in logsother than the specified log.Note:v This command displays the first




displaylog -src!filter_out

where filter_out is thecategory of event logentries that is not to bedisplayed. Use thedisplaylog -filterscommand to discoverexcludable event logcategories.

-T system:mm[x]


Display audit log entriesfiltered by source

Displays management moduleaudit log information that meetsthe specified source filter criteria.Note:v This command displays the first




displaylog -srcsource_filter

where source_filter is apipe ( | ) separated list ofsource filters. To specify arange of blade servers asthe source, use a hyphen (- ), as follows:Blade_01-08.

-T system:mm[x]





Display log entriesfiltered by call-homeflag

Displays log entries that meet thespecified call-home events filtercriteria.Note:v This command displays the five

most recent entries in themanagement-module event logthat meet the specified filtercriteria. Adding the -a option tothe command displays all entriesthat meet the specified filtercriteria.



displaylog -ch option

where option are:v C (call home)v N (no call home)

-T system:mm[x]


Display the state of thelog state event option

Displays the state (enabled ordisabled) of the log state eventoption, which generates an eventwhen the event log becomes 75%or 100% full.

displaylog -lse -T system:mm[x]


Enable / disablemonitoring of event logstate

Enables or disables the monitoringof the event log state to generate anevent when the log becomes 75%or 100% full.Note: The displaylog -lsecommand must be run exclusive ofother log-reading command options(-f, -a, -filters, -date, -sev, - src, -i,and -l).

displaylog -lse state



management


-T system:mm[x]


Save event log to TFTPserver

Saves the event log with thespecified filename to the specifiedTFTP server.Note: The -i and -l commandoptions must be run together andexclusive of other commandoptions.

displaylog -i ip_address-l filename

where:v ip_address is the IPv4 or

IPv6 IP address of theTFTP server where theevent log is beingsaved.

v filename is the name ofthe event log file.

-T system:mm[x]



Example:

To display all log entries generated by the management module in bay 1 otherthan those in the audit log, while the BladeCenter unit is set as the persistentcommand environment, at the system> prompt, typedisplaylog -src !Audit -T mm[1]

To display audit log entries generated by the management module in bay 1, whilethe BladeCenter unit is set as the persistent command environment, at the system>prompt, typedisplaylog -src Audit -T mm[1]

The following example shows the information that is returned from thesecommands:system> displaylog -src !Audit -T mm[1]1 I SERVPROC 08/04/08 14:18:06 Recovery Event log full2 I SERVPROC 08/04/08 14:18:06 Alarm Manager removed a MNR

alert during recovery of Eventlog full

(There are no more entries in the event log.)system> displaylog -src audit -T mm[1]1 I Audit 08/04/08 14:28:38 Remote logoff successful for

user ’spdev’from Telnet atIP 9.44.124.157

2 I Audit 08/04/08 14:28:18 Remote login successful foruser ’spdev’ from Telnet atIP 9.44.124.157

3 I Audit 08/04/08 14:18:15 Audit log cleared by ’spdev’.(There are no more entries in the event log.)system>


displaysd commandThis command captures and displays service information.

Service information for the management modules includes BladeCenter VPD, themanagement-module event log, connection status, and self-test results. If multipleuser interface sessions issue the displaysd command, the commands will beprocessed in the order that they are received. Some types of service information aredisplayed for only the primary management module.

Table 28. displaysd command


Capture and displayservice information

Capture and display serviceinformation on page from theprimary or standby managementmodule.

displaysd -T system:mm[x]

where x is the primaryor standbymanagement-modulebay number.

Display managementmodule connection andself-test status

Displays connection status andlatest self-test results for theprimary management module.

displaysd -mmstat -T system:mm[x]


Save service informationto TFTP server

Saves service information fromprimary management module withthe specified filename to thespecified TFTP server.Note: The -save and -i commandoptions must be run together.

displaysd -save filename-i ipaddress

where:v filename is the location

where serviceinformation will besaved. The filenameshould use a .tgzextension to allowsupport personnel toidentify the file.

v ip_address is the IPv4 orIPv6 IP address of theTFTP server.

-T system:mm[x]


Display all blade serverSRC records

Displays a list of the most recent(up to 32) SRCs for the specifiedblade server.Note: SRC information is availablefor only those blade servers thatsupport this feature.

displaysd -src list -T system:blade[x]

where x is the bladeserverbay number.

Display specific bladeserver SRC record

Displays a specific SRC, based onthe specified record number, for thespecified blade server.Note: SRC information is availablefor only those blade servers thatsupport this feature.

displaysd -src index

where index is the SRCrecord number to display,between 1 and 32.

-T system:blade[x]

where x is the bladeserverbay number.


Example: To capture and display service information from the managementmodule in bay 1, while the chassis is set as the persistent command environment,at the system> prompt, typedisplaysd -T system:mm[1]

To capture service information from the management module in bay 1 and save itto a file named sdc.tgz on a TFTP server with a IP address of 9.67.22.176, while thechassis is set as the persistent command environment, at the system> prompt, typedisplaysd -T system:mm[1] -save sdc.tgz -i 9.67.22.176

The following example shows the information that is returned from thesecommands:system> displaysd -T system:mm[1]SPAPP Capture AvailableTime: 10/04/2005 21:47:43UUID: Not Available•••system> displaysd -T system:mm[1] -save sdc.tgz -i 9.67.22.176OKsystem>

Note: If a large amount of service information is available, display could exceedthe capacity of your command-prompt window, resulting in loss of informationdisplayed at the start of the data set. If this happens, you will need to clear themanagement-module event log to reduce the amount of information beingcaptured.


dns commandThis command configures and displays the management-module DNS settings.

Table 29. dns command


Display DNSconfiguration ofmanagement module

Displays the current DNSconfiguration of the managementmodule. Possible return values are:v enabledv disabledv -i1 IPv4_first_ip_addressv -i2 IPv4_second_ip_addressv -i3 IPv4_third_ip_addressv -i61 IPv6_first_ip_addressv -i62 IPv6_second_ip_addressv -i63 IPv6_third_ip_addressv -ddns dynamic_DNS_state

(enabled/disabled)v -p DNS_server_priority

(ipv4/ipv6)

dns -T system:mm[x]


DNS - enable / disable Enables or disables themanagement-module DNSconfiguration.

dns -state




-T system:mm[x]


Dynamic DNS - enable /disable

Enables or disables dynamic DNSfor the management module.

dns -ddns state




-T system:mm[x]



Table 29. dns command (continued)


DNS first IPv4 IPaddress - set

Sets the first IPv4 IP address. dns -i1 ip_address

where ip_address is thefirst IP address in dotteddecimal IP address format.



-T system:mm[x]


DNS second IPv4 IPaddress - set

Sets the second IPv4 IP address. dns -i2 ip_address

where ip_address is thesecond IP address indotted decimal IP addressformat.



-T system:mm[x]


DNS third IPv4 IPaddress - set

Sets the third IPv4 IP address. dns -i3 ip_address

where ip_address is thethird IP address in dotteddecimal IP address format.



-T system:mm[x]





DNS first IPv6 IPaddress - set

Sets the first IPv6 IP address. dns -i61 ip_address

where ip_address is thefirst IP address in IPv6format.



-T system:mm[x]


DNS second IPv6 IPaddress - set

Sets the second IPv6 IP address. dns -i62 ip_address

where ip_address is thesecond IP address in IPv6format.



-T system:mm[x]


DNS third IPv6 IPaddress - set

Sets the third IPv6 IP address. dns -i63 ip_address

where ip_address is thethird IP address in IPv6format.



-T system:mm[x]





DNS server priority - set Sets the DNS server priority for themanagement module to IPv4 orIPv6..

dns -p priority

where priority is ipv4 oripv6.



-T system:mm[x]


Example: To set the first IP address of the management-module DNS server to192.168.70.29 and enable DNS on the primary management module that does nothave IPv6 support, while management module 1 is set as the persistent commandenvironment, at the system:mm[1]> prompt, typedns -i1 192.168.70.29 -on

To display the DNS status of the primary management module, while managementmodule 1 is set as the persistent command environment, at the system:mm[1]>prompt, typedns

The following example shows the information that is returned from these twocommands:system:mm[1]> dns -i1 192.168.70.29 -onChanges to the network settings will take effect after the next reset of the MM.system:mm[1]> dnsEnabled-i1 192.168.70.29-i2 0.0.0.0-i3 0.0.0.0system:mm[1]>

To display the DNS status of a primary management module that supports IPv6,while management module 1 is set as the persistent command environment, at thesystem:mm[1]> prompt, typedns


The following example shows the information that is returned from this command:system:mm[1]> dnsEnabledEnabled-i1 192.168.70.230-i2 0.0.0.0-i3 0.0.0.0-i61 2002:1013::211:25ff:fec3:227d-i62 ::-i63 ::-ddns disabled-p ipv4system:mm[1]>


env (environment) commandThis command sets the persistent environment for commands that are enteredduring the remainder of the current session.

The persistent command environment is indicated by the command prompt. Whenyou start the command-line interface, the persistent command environment is theBladeCenter unit, denoted as system by the command prompt. You can target asingle command to an environment other than the one that is set as the default byadding a -T option to the command that includes a valid target destination (see“Selecting the command target” on page 6 for information). Target environmentscan be specified using the full path name, or using a partial path name based onthe persistent command environment. Full path names always begin with system.The levels in a path name are divided by using a colon ( : ).

The following table lists BladeCenter components and the command paths that aresupported as targets by the env command.

Table 30. Components and command paths

Component Target path

BladeCenter unit system

Management module system:mm[x]

Blade server system:blade[x]

Blade server integrated system management processor(BMC or service processor)

system:blade[x]:sp

Blade server I/O-expansion card system:blade[x]:exp[y]

Blade server management card system:blade[x]:mgmtcrd

Blade server microprocessor system:blade[x]:cpu[y]

Blade server storage expansion unit system:blade[x]:be[y]

Blade server high-speed expansion card system:blade[x]:hsec[y]

Blade server memory system:blade[x]:memory[y]

Blade server mezzanine for double-width form factor system:blade[x]:sb

Blade server concurrent KVM feature card system:blade[x]:ckvm

I/O (switch) module system:switch[x]

Power module system:power[x]

Blower system:blower[x]

Media tray system:mt[x]

Media tray battery backup unit system:mt[x]:bbu[y]

Alarm panel (BladeCenter HT only) system:tap

Multiplexer expansion module (BladeCenter HT only) system:mux[x]

Network clock module (BladeCenter HT only) system:ncc[x]

Storage module (BladeCenter S unit only) system:storage[x]

Storage module disk drive (BladeCenter S unit only) system:storage[x]:disk[y]


Table 31. env (environment) command


Set BladeCenter unit ascommand target

Sets the BladeCenter unit as thepersistent target for commandsduring the current session. This isthe persistent commandenvironment you are in at thebeginning of each command-lineinterface session, indicated by thesystem> prompt.

env

env -T system

The env command canbe directed to anyinstalled device.

Set management moduleas command target

Sets the management module asthe persistent target for commandsduring the current session.

env -T system:mm[x]

where x is the bay (1 or 2)that identifies themanagement module.

The env command canbe directed to anyinstalled device, in thiscase

-T system:mm[x]

where x is themanagement-modulebay number.

Set blade server ascommand target

Sets the specified blade server asthe persistent target for commandsduring the current session.

env -T system:blade[x]

where x is the blade baythat identifies the bladeserver. A blade server thatoccupies more than oneblade bay is identified bythe lowest bay numberthat it occupies.


-T system:blade[x]

where x is the bladebay that identifies theblade server.


Table 31. env (environment) command (continued)


Set blade serversub-component ascommand target

Sets the specified sub-componenton the specified blade server as thepersistent target for commandsduring the current session. Validsub-components are:v Integrated system management

processor (BMC or serviceprocessor)

v I/O-expansion cardv Microprocessorv Storage expansion unitv High-speed expansion cardv Memoryv Mezzanine assembly for

double-width form factor bladeservers

env -Tsystem:blade[x]:comp

where x is the blade baythat identifies the bladeserver on which thesub-component isinstalled. A blade serverthat occupies more thanone blade bay is identifiedby the lowest bay numberthat it occupies.

where comp is thesub-component:v sp for BMC or service

processorv exp[x] for

I/O-expansion card(where x identifies theexpansion card)

v cpu[x] formicroprocessor (where xidentifies themicroprocessor)

v be[x] for storageexpansion unit (where xidentifies the expansionunit)

v ckvm for concurrentKVM feature card

v hsec[x] for high-speedexpansion card (where xidentifies the high-speedexpansion card)

v memory[x] for memory(where x identifies thememory module)

v mgmtcrd formanagement card

v sb for mezzanineassembly fordouble-width formfactor blade servers )


-Tsystem:blade[x]:comp

where x is the bladebay that identifies theblade server on whichthe integrated systemmanagement processoris installed.

where comp is thesub-component:v sp for BMC or

service processorv exp[x] for

I/O-expansion card(where x identifiesthe expansion card)

v cpu[x] formicroprocessor(where x identifiesthe microprocessor)

v be[x] for storageexpansion unit(where x identifiesthe expansion unit)

v ckvm for concurrentKVM feature card

v hsec[x] forhigh-speedexpansion card(where x identifiesthe high-speedexpansion card)

v memory[x] formemory (where xidentifies thememory module)

v mgmtcrd formanagement card

v sb for mezzanineassembly fordouble-width formfactor blade servers )




Set I/O module ascommand target

Sets the specified I/O module asthe persistent target for commandsduring the current session.

env -T system:switch[x]

where x is the I/O-modulebay where the I/Omodule is installed.


-T system:switch[x]

where x is theI/O-module bay wherethe I/O module isinstalled.

Set power module ascommand target

Sets the specified power module asthe persistent target for commandsduring the current session.

env -T system:power[x]

where x is the powermodule bay where thepower module is installed.


-T system:power[x]

where x is the powermodule bay where thepower module isinstalled.

Set blower as commandtarget

Sets the specified blower as thepersistent target for commandsduring the current session.

env -T system:blower[x]

where x is the blower baywhere the blower isinstalled.


-T system:blower[x]

where x is the blowerbay where the bloweris installed.

Set media tray ascommand target

Sets the media tray as thepersistent target for commandsduring the current session.

env -T system:mt[x]

where x is the media-traybay where the media trayis installed.


-T system:mt[x]

where x is themedia-tray bay wherethe media tray isinstalled.

Set media tray batterybackup unit ascommand target

Sets the specified battery backupunit on the specified media tray asthe persistent target for commandsduring the current session.

env -Tsystem:mt[x]:bbu[y]

where x is the media trayon which the batterybackup unit is installed.

where y is the batterybackup unit number:


-Tsystem:mt[x]:bbu[y]

where x is the mediatray on which thebattery backup unit isinstalled.

where y is the batterybackup unit number:




Set alarm panel ascommand target

(BladeCenter HT unitsonly)

Sets the alarm panel as thepersistent target for commandsduring the current session.

env -T system:tap The env command canbe directed to anyinstalled device, in thiscase

-T system:tap

Set multiplexerexpansion module ascommand target


Sets the multiplexer expansionmodule as the persistent target forcommands during the currentsession.

env -T system:mux[x]

where x is the multiplexerexpansion modulenumber.


-T system:mux[x]

where x is themultiplexer expansionmodule number.

Set network clockmodule as commandtarget


Sets the network clock module asthe persistent target for commandsduring the current session.

env -T system:ncc[x]

where x is the networkclock module number.


-T system:ncc[x]

where x is the networkclock module number.

Set storage module ascommand target

(BladeCenter S unitsonly)

Sets the storage module as thepersistent target for commandsduring the current session.

env -T system:storage[x]

where x is thestorage-module bay wherethe storage module isinstalled.


-T system:storage[x]

where x is thestorage-module baywhere the storagemodule is installed.

Set storage module diskdrive as command target


Sets the specified disk drive in thespecified storage module as thepersistent target for commandsduring the current session.

env -Tsystem:storage[x]:disk[y]

where x is the storagemodule on which the diskdrive is installed.

where y is the disk drivenumber:


-T system:storage[x]:disk[y]

where x is the storagemodule on which thedisk drive is installed.

where y is the diskdrive number:


Example: To set the persistent target of commands to the service processor on theblade server in blade bay 5, while the BladeCenter unit is set as the defaultcommand target, at the system> prompt, typeenv -T system:blade[5]:sp

The following example shows the information that is returned:system> env -T system:blade[5]:spOKsystem:blade[5]:sp>

To set the persistent target of commands to the service processor on the bladeserver in blade bay 5, while the BladeCenter unit is set as the default commandtarget, at the system> prompt, you can also typeenv -T blade[5]:sp

The following example shows the information that is returned:system> env -T blade[5]:spOKsystem:blade[5]:sp>

To issue the reset command on the blade server in blade bay 5, while themanagement module is set as the default command target, at the system:mm[x]>prompt, typereset -T system:blade[5]


ethoverusb commandThis command sets and displays the setting for the Ethernet-over-USB commandinterface of a blade server service processor, for blade servers that support thisfeature.

Table 32. ethoverusb command


Display blade serverEthernet-over-USBsetting

Displays the Ethernet-over-USBcommand interface setting for theservice processor of the specifiedblade server.Note: This command will executeonly on blade servers that supportan Ethernet-over-USB commandinterface for the service processor.

ethoverusb -T system:blade[x]


Set blade serverEthernet-over-USBsetting

Enables or disables theEthernet-over-USB commandinterface setting for the serviceprocessor of the specified bladeserver.Note: This command will executeonly on blade servers that supportan Ethernet-over-USB commandinterface for the service processor.

ethoverusb -s state




-T system:blade[x]


Example: To view the Ethernet-over-USB command interface setting for the serviceprocessor of the blade server in bay 2, while this blade server is set as thepersistent command environment, at the system:blade[2]> prompt, typeethoverusb

To disable the Ethernet-over-USB command interface setting for the serviceprocessor of the blade server in bay 2, while this blade server is set as thepersistent command environment, at the system:blade[2]> prompt, typeethoverusb -s disabled

The following example shows the information that is returned from thesecommands:system:blade[2]> ethoverusbenabledsystem:blade[2]> ethoverusb -s disabledOKsystem:blade[2]> ethoverusbdisabledsystem:blade[2]>


eventinfo commandThis command displays advanced management module event information andsuggested user actions. See the BladeCenter Advanced Management Module MessagesGuide for a complete list of all non-device specific events and recommendedactions, sorted by event ID. Device specific event information is in thedocumentation for the device.

Table 33. eventinfo command


Display eventdescription and useraction

Displays the event description andsuggested user action for thespecified event ID.

eventinfo -id

where id is the event IDdisplayed from the“displaylog command” onpage 119.

Event IDs are of the form0xnnnnnnnn, wherennnnnnnn is ahexadecimal number thatidentifies the specificevent (the 0x prefix is notentered). Leading zerosneed not be entered whenusing the eventinfocommand: in thisexample, specifying anevent ID of 00104204, or104204 would return thesame result.

-T system:mm[x]


Display eventdescription

Displays the event description forthe specified event ID.

eventinfo -id -d



-T system:mm[x]



Table 33. eventinfo command (continued)


Display event useraction

Displays the suggested user actionfor the specified event ID.

eventinfo -id -u



-T system:mm[x]


Example: To view the event description and suggested user action for an eventwith an ID of 0x00104204, while the BladeCenter unit is set as the persistentcommand environment, at the system:> prompt, typeeventinfo -T mm[1] -00104204

The following example shows the information that is returned from this command:system> eventinfo -T mm[1] -00104204Event Description:The primary advanced management module was reset.Recommended Action:Information only; no action is required.system>


events commandThis command manages the Call Home events exclusion list for the advancedmanagement module.

Table 34. events command


Display Call Homeevents list and freespace

Displays a list of Call Home eventIDs that will not be reported by theCall Home feature, and how manymore events can be added to thisCall Home events exclusion list.This Call Home exclusion listallows a maximum of 20 events.

events -che





configuration


-T system:mm[x]


Add a Call Home eventto the Call HomeExclusion list

Adds a Call Home event to theCall Home exclusion list. Events onthis list are specified by an eventID, and are not included in the CallHome reports.Note: The Service Advisor termsand conditions must first beaccepted, or the AutomatedFTP/TFTP Report of Service Datamust be enabled before using thiscommand.

events -che -add event_ID

where event_ID is aneight-digit hexadecimalnumber with an optionalprefix of 0x or 0X.



-T system:mm[x]



Table 34. events command (continued)


Remove a Call Homeevent from the CallHome Exclusion list

Removes a Call Home event fromthe Call Home exclusion list.Events removed from this list areincluded in the Call Home reports.Note: The Service Advisor termsand conditions must first beaccepted, or the AutomatedFTP/TFTP Report of Service Datamust be enabled before using thiscommand.

events -che -rm event_ID

where event_ID isv an eight-digit

hexadecimal numberwith an optional prefixof 0x or 0X to remove asingle Call Home event

v all to remove all theCall Home events fromthe exclusion list



-T system:mm[x]


Example: To view the Call Home exclusion list and the number of remainingevents can be added to the list, while the BladeCenter unit is set as the persistentcommand environment, at the system:> prompt, typeevents -T mm[1] -che

To add Call Home event number 0x00020003 to the Call Home exclusion list, whilethe BladeCenter unit is set as the persistent command environment, at the system>prompt, typeevents -T mm[1] -che -add 0x00020003

To remove Call Home event number 0x00020001 from the Call Home exclusion list,while the BladeCenter unit is set as the persistent command environment, at thesystem> prompt, typeevents -T mm[1] -che -rm 0x00020001

The following example shows the information that is returned from thesecommands:system> events -T mm[1] -cheA maximum of 20 events can be added to this exclusion list, currently18 more events can be added.Call Home Exclusion List is illustrated as follows:Index Event ID1 0x000200012 0x00020002system> events -T mm[1] -che -add 0x00020003OKsystem> events -T mm[1] -cheA maximum of 20 events can be added to this exclusion list, currently17 more events can be added.Call Home Exclusion List is illustrated as follows:Index Event ID1 0x000200012 0x00020002


3 0x00020003system> events -T mm[1] -che -rm 0x00020001OKsystem> events -T mm[1] -cheA maximum of 20 events can be added to this exclusion list, currently18 more events can be added.Call Home Exclusion List is illustrated as follows:Index Event ID1 0x000200022 0x00020003system>


exit commandThis command exits the command-line interface, terminating the current session.

Table 35. exit command


Exit Terminates the currentcommand-line interface session.

exitNote: You can also usethe Ctrl-D keycombination to end thecurrent session and exitthe command-lineinterface.

Any installed device.

Example: To terminate the current command-line interface session, typeexit


feature commandThis command manages licensing for advanced features for the advancedmanagement module.

Table 36. feature command


Display feature list andlicense status

Displays a list of advanced featuresfor the management module andtheir licensing status.

feature -T system:mm[x]


Add a feature license Adds a license for a managementmodule advanced feature. Featureson this list are specified using thefeature index number that appearsat the left of the feature list.

feature -index -add -keylisc_key

where:v index is the number for

the feature at the left ofthe feature listdisplayed by thefeature command.

v lisc_key is the7-character part numberof the feature.



-T system:mm[x]


Remove a feature license Removes a license for amanagement module advancedfeature. Features on this list arespecified using the feature indexnumber that appears at the left ofthe feature list.

feature -index -remove

where index is the numberfor the feature at the leftof the feature listdisplayed by the featurecommand.



-T system:mm[x]



Table 36. feature command (continued)


Import datacenterfeature licenses

Import a datacenter featurelicensing file for use by theBladeCenter unit.

The file name to import mustspecify a qualified location for thelicensing file that indicates theprotocol to be used. For example,tftp://192.168.0.1/license.csv

feature -applyfile_location

where file_location is aqualified location for thelicense file of up to 256characters in length thatindicates the protocol tobe used (tftp, ftp, ftps,http, or https) andcontains any characterexcept the percent sign (% ) or double-quote ( � ).



-T system:mm[x]


Export datacenter featurelicenses

Export a BladeCenter featurelicensing file for use by otherBladeCenter units in the datacenter.

The file name to export mustspecify a qualified location for thelicensing file that indicates theprotocol to be used. For example,tftp://192.168.0.1/license.csvNote: While the licensing file isexporting, a string of periods willdisplay on the screen to indicateprogress; a new period beingadded every three seconds.

feature -retrievefile_location

where file_location is aqualified location for thelicense file of up to 256characters in length thatindicates the protocol tobe used (tftp, ftp, ftps,http, or https) andcontains any characterexcept the percent sign (% ) or double-quote ( � ).



-T system:mm[x]



Example: To view the feature list, while the BladeCenter unit is set as thepersistent command environment, at the system:> prompt, typefeature -T mm[1]

To remove the license for the first feature in the list, while the BladeCenter unit isset as the persistent command environment, at the system> prompt, typefeature -T mm[1] -1 -remove

To export a licensing file to the location tftp://10.11.20.23/IBMtest.csv, while theBladeCenter unit is set as the persistent command environment, at the system>prompt, typefeature -retrieve -T mm[1] tftp://10.11.20.23/IBMtest.csv

The following example shows the information that is returned from thesecommands:system> feature -T mm[1]1. IBM BladeCenter Open Fabric Manager-serial 2304369License Status: Activesystem> feature -T mm[1] -1 -removeOKsystem> feature -T mm[1]1. IBM BladeCenter Open Fabric ManagerLicense Status: No Licensesystem> feature -retrieve -T mm[1] tftp://10.11.20.23/IBMtest.csv................OKsystem>


files commandThis command manages files uploaded to the advanced management module.

Table 37. files command


Display file list and freespace

Displays a list of files and spaceremaining in the advancedmanagement module file system.

files -T system:mm[x]


Delete file Deletes a file from the advancedmanagement module file system.Note: This command can only beused to delete files: it will notdelete directories.

files -d filename

where filename is a valid,existing filename of lessthan 256 characters inlength.

This command can onlybe run by users who haveone or more of thefollowing commandauthorities:v Supervisorv Chassis administrationv Chassis configurationv Blade administrationv Blade configurationv I/O module


configuration


-T system:mm[x]


Example: To view the files and remaining space in the management module filesystem, while management module 1 is set as the persistent commandenvironment, at the system:mm[1]> prompt, typefiles

To delete the file tftproot/tftp_file.pkt from the management module filesystem, while management module 1 is set as the persistent commandenvironment, at the system:mm[1]> prompt, typefiles -d tftproot/tftp_file.pkt


The following example shows the information that is returned from thesecommands:system:mm[1]> files

12288 Thu Jan 05 13:28:23 2006 lost+found/1024 Thu Jul 06 19:32:51 2006 tftproot/1024 Thu Jul 06 19:34:15 2006 tftproot/manu/1024 Thu Jul 06 19:34:15 2006 tftproot/manu/manu2/

0 Sat Aug 19 09:22:02 2006 tftproot/tftp_file.pkt0 Sun Oct 01 07:57:19 2006 tftproot/.Do_not_delete_this_directory0 Tue Dec 15 11:07:19 2009 test0 Thu Apr 13 23:45:40 2006 bob.pkt

1024 Tue Feb 02 15:29:17 2010 pubkeys/426 Tue Feb 02 15:29:17 2010 pubkeys/ssh_key.pub5652 Fri May 12 00:56:36 2006 asm.cfg

Total space: 73108480 bytesUsed: 24576 bytesAvailable: 73083904 bytessystem:mm[1]> files -d tftproot/tftp_file.pktOKsystem:mm[1]>


fuelg commandThis command displays power domain information, listing the power modules thatare installed in the BladeCenter unit and information about how the power in eachdomain is used. This command also configures the power domain policies forpower redundancy loss and limiting fan noise during thermal events.

Note: For scripting purposes, the -qm and -os fuelg options for managementmodules other than the advanced management module are supported by theadvanced management module.

Table 38. fuelg command


Display power domainstatus overview

Displays health status, total powerusage, total dc power available,total ac power in use, thermalresponse (acoustic mode) settings,total thermal output in BTU/hour,and the polling intervals used fortrending for all power domains.Note: For the BladeCenter S unit,output will indicate whether thechassis is running in 220 V ac or110 V ac mode.

fuelg -T system

Display blade serverpower status overview

Displays the power managementand capping setting (on/off) andpower management capability forthe specified blade server.Depending on the powermanagement capability of thespecified blade server, thefollowing information will alsodisplay:v CPU duty cyclesv Effective and maximum CPU

speedsv Power capping value (minimum

and maximum)v Maximum, minimum, and

average power levelsv Time when above data was

capturedv Power saver mode status (on,

off)

fuelg -T system:blade[x]

where x is theblade-server baynumber.

Display I/O modulepower status

Displays the maximum, minimum,and average power information forthe specified I/O module.

fuelg -T system:switch[x]


Display blower powerstatus and temperature

Displays the maximum power,minimum power, average power,and current temperatureinformation for the specifiedblower module.

fuelg -T system:blower[x]

where x is the blowerbay number.

Display media traytemperature

Displays the current temperaturefor the specified media tray.

fuelg -T system:mt[x]

where x is the mediatray number.


Table 38. fuelg command (continued)


Display detailed powerdomain status

Displays detailed status and usageinformation for the specified powerdomains, including the policysetting for that domain, themaximum power limit, and thepower in use. The valid states forcomponents in the domain are:v * - blade server might throttlev C - communication errorv D - discoveringv Hib - hibernatev NP - module is not presentv SB - standbyv T - throttledv U - unable to power up

Note: For the BladeCenter S,output will indicate whether thechassis is running in 220 V ac or110 V ac mode.

fuelg domain

where domain is:v pd1 for power domain 1.v pd2 for power domain 2.v If no domain is specified,

a status overview for allpower domains displays.

Note: The BladeCenter Sunit has only one powerdomain. Use either pd orpd1 to specify the powerdomain for theBladeCenter S unit.

-T system




Set power domainredundancy loss policy

Sets how the BladeCenter unitresponds to a condition that couldcause a loss of redundant powNote: For the BladeCenter S,output will indicate whether thechassis is running in 220 V or 110V ac mode.er.

fuelg domain -pm policy

where:v domain is:

– pd1 for power domain1.


– If no domain isspecified, the policy isapplied to all powerdomains.

v policy of:– nonred (default)

allows loss ofredundancy.

– redwoperf preventscomponents fromturning on that willcause loss of powerredundancy.

– redwperf powerthrottles componentsto maintain powerredundancy andprevents componentsfrom turning on thatwill cause loss ofpower redundancy.

This command can only berun by users who have oneor more of the followingcommand authorities:v Supervisorv Chassis configuration


-T system

Display power trendingfor specified time periodand power domain

Displays power trendinginformation for the selected timeinterval and selected powerdomain for the BladeCenter unit.

fuelg domain -pt period

where:v domain is:



– If no domain isspecified, the period isapplied to all powerdomains.

v period is 1, 6, 12, or 24hours.

-T system




Display power trendingfor specified time period

Displays power trendinginformation for the selected timeinterval for the specified commandtarget.

fuelg -pt period

where period is 1, 6, 12, or24 hours.

-T system

-T system:blade[x]

-T system:switch[x]

-T system:blower[x]

where x is the bladeserver, I/O module, orblower bay number.

Set power pollinginterval

Sets the amount of time betweenthermal and power samples thatare taken to build trending data.

fuelg -int interval

where interval is between10 and 60 minutes,inclusive, in 5-minuteincrements.



-T system

Display thermal trendingfor specified time period

Displays thermal trendinginformation for the selected timeinterval for the specified commandtarget.

fuelg -tt period

where period is 1, 6, 12, or24 hours.

-T system:mt[x]

-T system:blower[x]

where x is the bladeserver or blower baynumber.




Thermal event response(acoustic mode)

Sets the acoustic mode ofBladeCenter-unit blowers responseto thermal events.

fuelg -am setting

where the acoustic-modesetting of:v off (default) allows

blowers to increasespeed to provideadditional cooling.

v on keeps blowers at afixed speed and powerthrottles BladeCentercomponents to reducepower consumption(only for BladeCentercomponents that supportpower throttling).



-T system

Thermal event response(Telco environment)

Sets the Telco environment of theBladeCenter-unit blowers responseto thermal events.Note: When the environmentmode is set to nebs, the -am modeis automatically turned off.

fuelg -e environment

where the thermal-eventresponse environment of:v nebs allows blowers to

increase speed toprovide additionalcooling.

v enterprise allowsacoustic mode.



-T system




Set power capping valuefor blade server

Sets the power capping value for aspecified blade server that supportthis feature.Note: A blade server must beturned on before you can set itspower capping value.

fuelg -pcap setting

where the power cappingsetting is a numeric valuethat falls within the rangeof power capping valuesdisplayed when runningthe fuelg -T blade[x]command on a bladeserver.



-T system:blade[x]


Power management andcapping - enable ordisable for blade server

Turns power management andcapping for the specified bladeserver on or off.Note: A blade server must beturned on before you can enablepower management and cappingfor it.

fuelg -pme setting

where a setting of:v off (default) disables

power management andcapping for the bladeserver.

v on enables powermanagement andcapping for the bladeserver.



-T system:blade[x]





Static low power savermode - enable or disablefor blade server

Turns the static low power savermode for the specified blade serveron or off.Notes:v A blade server must be turned

on before you can enable powersaver mode for it.

v Not all blade servers support thepower saver mode.

fuelg -ps setting


power saver mode forthe blade server.

v on enables power savermode for the bladeserver.



-T system:blade[x]


Dynamic poweroptimizer - enable ordisable for blade server

Turns dynamic power optimizer forthe specified blade server on or off.Notes:v A blade server must be turned

on before you can enabledynamic power optimizer for it.

v Not all blade servers support thedynamic power optimizer.

fuelg -dps setting


dynamic poweroptimizer for the bladeserver.

v on enables dynamicpower optimizer for theblade server.



-T system:blade[x]





Favor performance overpower - enable or disablefor blade server

Turns the favor performance overpower feature on or off for thespecified blade server.Notes:v A blade server must be turned

on before you can enable thefavor performance over powerfeature for it.

v Not all blade servers support thefavor performance over powerfeature.

v This feature can only be active ifthe dynamic power optimizer isenabled.

fuelg -fpop setting


favor performance overpower for the bladeserver.

v on enables favorperformance over powerfor the blade server.



-T system:blade[x]


Example: To view a power domain status overview, while the BladeCenter unit isset as the persistent command environment, at the system> prompt, typefuelg

To view the detailed power domain status for power domain 1, while theBladeCenter unit is set as the persistent command environment, at the system>prompt, typefuelg pd1

To view BladeCenter unit power trending information for the past 6 hours, whilethe BladeCenter unit is set as the persistent command environment, at the system>prompt, typefuelg -pt 6

To view the power status for the blade server in blade bay 1, while theBladeCenter unit is set as the persistent command environment, at the system>prompt, typefuelg -T blade[1]

The following example shows the information that is returned from thesecommands when the fuelg command is run on an advanced management module.system> fuelgNote: All power values are displayed in Watts.

Total DC Power Available: 8000Total AC Power In Use: 1603 (+/- 16.0%)Total Thermal Output: 5469 BTU/hour

Power Domain 1--------------Status: This power domain has mismatched power modules.

Replace the power module.Modules:Bay 1: 2880


Bay 2: 3160Power Management Policy: Basic Power ManagementPower in Use: 1313 (+/- 16.0%)Total Power: 4000Allocated Power (Max): 1423Remaining Power: 2577

Power Domain 2--------------Status: Power domain status is good.Modules:Bay 3: 2880Bay 4: 2880Power Management Policy: Basic Power ManagementPower in Use: 73 (+/- 16.0%)Total Power: 4000Allocated Power (Max): 1082Remaining Power: 2918

-am on-e enterprise-int 10

system> fuelg pd1Maximum Power Limit: 1450Power In Use: 856

Power -- Allocated Power --Bay(s) Module State Current Max Min====== ============================= ===== ======= ===== =====Chassis Components

Midplane On 10 10 101 Media Tray 1 On 10 10 10

Chassis Cooling Devices1 Chassis Cooling Device 1 On 11 68 682 Chassis Cooling Device 2 On 11 68 683 Chassis Cooling Device 3 On 11 68 684 Chassis Cooling Device 4 On 11 68 68

Power Module Cooling Devices1 PM Cooling Device 1 On 10 10 102 PM Cooling Device 2 On 10 10 103 PM Cooling Device 3 On 10 10 104 PM Cooling Device 4 (NP) 0 10 10

Storage1 Storage Module 1 (NP) 0 120 1202 Storage Module 2 On 0 100 100

Management Module1 SN#YK168082H25F On 25 25 25

I/O Modules1 Ethernet SM On 45 45 452 Ethernet SM On 45 45 453 I/O Module 3 (NP) 0 45 454 Server Conn Mod On 45 45 45

Blades1 Maui A On 236 236 236

(100%,100%,100%,100%)2 LewisA1-LS21 (T) (CA) On 71 75 753 Lucas_55 (T) (CA) On 66 76 764 Mongoose-2 (T) (CA) On 108 127 1215 Crichton8 (T) (CA) On 99 109 1086 Mongoose-3 (T) (CA) On 142 34 34

Domain totals:Allocated Power 856 1414 1407

Note: (T) means "throttled", (U) means "unable to power up",* means "the blade may throttle", (NP) means "the module is not present",(D) means "discovering", (C) means "comm error", (SB) means "Standby"


(CA) means “capped max power allocation”

-pm nonred

system> fuelg -pt 6Date Time Avg Pwr-------- -------- -------07/17/07 08:09:44 293007/17/07 08:24:44 292607/17/07 08:39:48 291607/17/07 08:54:44 290607/17/07 09:09:44 292207/17/07 09:24:44 292607/17/07 09:39:44 292607/17/07 09:54:44 292607/17/07 10:09:44 291407/17/07 10:24:44 292807/17/07 10:39:48 293007/17/07 10:54:44 291407/17/07 11:09:43 276207/17/07 11:24:44 292407/17/07 11:39:44 292607/17/07 11:54:44 293207/17/07 12:09:44 292807/17/07 12:24:44 292207/17/07 12:39:43 276207/17/07 12:54:43 277207/17/07 13:09:43 277007/17/07 13:24:44 276607/17/07 13:39:44 276807/17/07 13:54:47 2926

system> fuelg -T blade[1]-pme offPM Capability: Dynamic Power Measurement with cappingEffective CPU Speed: 2955 MHzMaximum CPU Speed: 3000 MHz-pcap 190 (min: 174, max: 280)Maximum Power: 235Minimum Power: 199Average Power: 235Data captured at 07/17/07 13:59:05system>


groups commandThis command displays and configures Active Directory groups of the primarymanagement module. This group information is used only when LDAP servers areenabled for authentication with local authorization.

Table 39. groups (Active Directory groups) command


Display all ActiveDirectory groups

Displays all Active Directorygroups, up to 16, configured for theBladeCenter unit.

groups -T system:mm[x]


Display specific ActiveDirectory group

Displays information for thespecified Active Directory group.

groups -group_num

where group_num is anumber from 1 to 16,inclusive, that identifiesthe Active Directorygroup.

-T system:mm[x]


Set Active Directorygroup name

Sets a name for the specified ActiveDirectory group.

groups -group_num -ngroup_name

where:v group_num is a number

from 1 to 16, inclusive,that identifies the ActiveDirectory group.

v group_name is aalphanumeric string upto 63 characters inlength that can includeperiods ( . ) andunderscores ( _ ). Eachof the 16 group namesmust be unique.



-T system:mm[x]



Table 39. groups (Active Directory groups) command (continued)


Set Active Directorygroup authority level

Sets the authority level for thespecified Active Directory group.

groups -group_num -agroup_authority

where:v group_num is a number

from 1 to 16, inclusive,that identifies the ActiveDirectory group.

v group_authority uses thefollowing syntax:– operator (Operator)– rbs:levels:scope

where the levels areone or more of thefollowing authoritylevels, separated by avertical bar ( | ):- super (Supervisor)- cam (Chassis User

AccountManagement)

- clm (Chassis LogManagement)

- co (ChassisOperator)

- cc (ChassisConfiguration)

- ca (ChassisAdministration)

- bo (BladeOperator)

- brp (Blade RemotePresent)

- bc (BladeConfiguration)

- ba (BladeAdministration)

- so (I/O ModuleOperator)

- sc (I/O ModuleConfiguration)

- sa (I/O ModuleAdministration)


-T system:mm[x]



Table 39. groups (Active Directory groups) command (continued)


Set Active Directorygroup authority level

(continued)

where the scope is one ormore of the followingdevices, separated by avertical bar ( | ). Rangesof devices are separatedby a dash ( - ).v cn (Chassis n, where n

is 1 for the ActiveDirectory environment.)

v bn (Blade n, where n isa valid blade baynumber in the chassis)

v sn (I/O module n,where n is a valid I/Omodule bay number inthe chassis)



Delete Active Directorygroup

Delete the specified ActiveDirectory group.

groups -group_num -clear

where group_num is anumber from 1 to 16,inclusive, that identifiesthe Active Directorygroup.



-T system:mm[x]



Example: To create Active Directory group number 3 with a group name of group3that has supervisor rights to all BladeCenter components, while managementmodule 1 is set as the persistent command environment, at the system:mm[1]>prompt, typegroups -3 -n group3 -a rbs:super:c1|b1-b14|s1-s4

To display information for group3, while management module 1 is set as thepersistent command environment, at the system:mm[1]> prompt, typegroups -3

The following example shows the information that is returned from thesecommands:system:mm[1]> groups -3 -n group3 -a rbs:super:c1|b1-b14|s1-s4OKsystem:mm[1]> groups -3-n group3-a Role:supervisor

Blades:1|2|3|4|5|6|7|8|9|10|11|12|13|14Chassis:1Modules:1|2|3|4

system:mm[1]>


health commandThis command displays the current health status of the command target. It canalso be used to display the alerts that are active for the command target.

You can only specify one command target each time you run the health command.

Table 40. health command


Display health status Displays the current health statusof the command target. Returnvalues are different for theBladeCenter and BladeCenter Tconfigurations.v Possible return values for the

BladeCenter configuration are:– ok– warning– critical

v Possible return values for theBladeCenter T configurations are:– ok– minor– major– critical

health -T system

-T system:mm[x]

-T system:blade[x]

-T system:switch[x]

-T system:power[x]

-T system:blower[x]

-T system:storagex](for BladeCenterS units)

where x is the primarymanagement-module,blade server, I/Omodule, powermodule, blower bay, orstorage bay number.

Display health status fortree

Displays the current health statusof the tree structure of devicespresent in the BladeCenter unit,starting at the command targetlevel. If management-module baysare part of the tree, they will beidentified as primary or standby(redundant). Return values aredifferent for the BladeCenter andBladeCenter T configurations.v Possible return values for the

BladeCenter configuration are:– ok– warning– critical

v Possible return values for theBladeCenter T configurations are:– ok– minor– major– critical

health -l depth

where depth

v 1 displays health statusof the current commandtarget

v 2, all, or a displays afull tree display, startingat the command targetlevel

-T system

-T system:mm[x]

-T system:blade[x]

-T system:switch[x]

-T system:power[x]

-T system:blower[x]



Table 40. health command (continued)


Display health statusand alerts

Displays the current health statusand active alerts for the commandtarget. Return values are differentfor the BladeCenter andBladeCenter T configurations.v Possible return values for the

health status of the BladeCenterconfiguration are:– ok– warning– critical

v Possible return values for thehealth status of the BladeCenterT configurations are:– ok– minor– major– critical

v Active alert information providesshort text descriptions of alertsthat are active for eachmonitored component.

The total amount of informationreturned from the health -fcommand is limited to 1024 bytes.

health -f -T system

-T system:mm[x]

-T system:blade[x]

-T system:switch[x]

-T system:power[x]

-T system:blower[x]


Display results withtimestamp

(BladeCenter E unitsonly)

Adds display of timestampinformation to status commandoutput.

health -tNote: The -t option mustbe used with the -f option.

-T system

-T system:mm[x]

-T system:blade[x]

-T system:switch[x]

-T system:power[x]

-T system:blower[x]


Example: To display the overall health status of the BladeCenter T unit, while theBladeCenter T unit is set as the default command target, at the system> prompt,typehealth

To display the health status of all components installed in the BladeCenter T unit,that are valid command targets, while the BladeCenter T unit is set as the defaultcommand target, at the system> prompt, typehealth -l a

To display the health status of the blade server installed in blade bay 5, while theBladeCenter T unit is set as the default command target, at the system> prompt,typehealth -T system:blade[5]


To display the health status and alerts for all components installed in theBladeCenter T unit, that are valid command targets, while the BladeCenter T unitis set as the default command target, at the system> prompt, typehealth -l a -f

The following example shows the information that is returned from thesecommands:system> healthsystem:majorsystem> health -l asystem: Major

mm[1] : OKblade[1] : OKblade[3] : OKblade[5] : Minorpower[1] : OKpower[2] : Minorblower[1] : OKblower[2] : OKblower[3] : OKblower[4] : OKswitch[1] : Major

system> health -T system:blade[5]system: blade[5] : Minorsystem> health -l a -fsystem: Major

blade[5] : Minor5V over voltageCPU1 temperature warningpower[2] : Minor5V over voltageswitch[1] : Majortemperature fault

system>


help commandThis command displays a list of all commands that are available in thecommand-line interface with a brief description of each command.

You can also issue the help command by typing ?. Adding a -h, -help, or ? optionto a command displays syntax help for the command.

Table 41. help command


Help Displays a list of commands and abrief description of each command.

help Any installed device.

? Any installed device.

Example: To display a list of commands, while the advanced management modulein bay 1 is set as the default command target, at the system:mm[1]> prompt, typehelp

The following example shows the information that is returned:system> help

? -- Display commandsaccseccfg -- View/edit account security config

advfailover -- View/edit advanced failover modealertcfg -- Displays/Configures the global remote alert settings

alertentries -- View/edit remote alert recipientsautoftp -- View/Edit auto ftp/tftp settingbaydata -- View/edit Blade Bay Data string

bofm -- Apply new BOFM configurationboot -- Boot target

bootmode -- Boot modebootseq -- View/edit the blade boot sequence settings

buildidcfg -- View/Edit the Blade Firmware Build ID Listchconfig -- View/edit Service Advisor Settings

chlog -- Display Service Advisor Activity Log entireschmanual -- Manually generate call home request

cin -- Displays/Configures Chassis Internal Networkcinstatus -- Displays Status of Chassis Internal Network

clear -- Clear the configclearlog -- Clear the event log

clock -- View/edit date, time, GMT offset, and dst settingconfig -- View/edit general settingsconsole -- Start SOL session to a bladedhcpinfo -- View DHCP server assigned settings

displaylog -- Display log entriesdisplaysd -- Display service data

dns -- View/edit DNS configenv -- Set persistent command target

ethoverusb -- View/edit the status of a blade SP’s interface on Ethernet-over-USBeventinfo -- Display event description and user action

events -- View/edit Events configexit -- Log off

feature -- View/edit licensed featuresfiles -- Displays and deletes files stored on the AMMfuelg -- Power managementgroups -- View/edit Active Directory groupshealth -- View system health status

help -- Display command listhistory -- Display command historyidentify -- Control target location LEDifconfig -- View/edit network interface config

info -- Display identity and config of targetiocomp -- View I/O compatibility for blades and switches

kvm -- Controls the kvm owner


ldapcfg -- View/edit LDAP configled -- Display and control Ledslist -- Display installed targetsmcad -- Displays and configures MCAD

modactlog -- Displays module activity logmonalerts -- Displays and configures monitored alerts

mt -- Controls the media tray ownernat -- Display and configure NATntp -- View/edit NTP configping -- Pings targeted switch module

pmpolicy -- View/edit power management policy settingsportcfg -- Serial port configuration

ports -- Port configurationpower -- Control target powerrdoc -- Controls the remote DiskOnCardread -- Restore configuration from the chassis or a file

remotechassis -- Chassis discovered over the networkreset -- Reset targetscale -- Display and configure the settings of scalable complexessddump -- Initiate service data dumpsdemail -- Send service information using emailsecurity -- View/edit security configservice -- Enable debugging by service personnelshutdown -- Shutdown target

slp -- View/edit SLP parameterssmtp -- View/edit SMTP configsnmp -- View/edit SNMP configsol -- View SOL status and view/edit SOL config

sshcfg -- View/edit SSH configsslcfg -- View/edit SSL configsyslog -- View/edit syslog config

tcpcmdmode -- View/edit TCP command mode configtelnetcfg -- View/edit telnet config

temps -- View temperaturestrespass -- View/edit trespassing warning config

uicfg -- View/edit user interface configurationupdate -- Update firmware from remote locationuplink -- View/edit failover on network uplink loss configusers -- View/edit user login profilesvolts -- View voltageswrite -- Save configuration to chassis or a local file

zonecfg -- Zone configuration for I/O modules

Type "Type "<command> -h" for individual command syntax help.[ ] is used for indexing (by bay number)< > denotes a variable{ } denotes optional arguments| denotes choice

system>

To obtain help about the env command, type one of the following commands:v env -hv env -helpv env ?


history commandThis command displays the last eight commands that were entered, allowing theuser to choose and re-enter one of these commands.

You choose the command to re-enter from the displayed list by typing anexclamation point (!) followed immediately by the numeric designation thecommand is assigned in the list. You can also recall one of the past eightpreviously entered commands using the up-arrow and down-arrow keys.

Table 42. history command


Command history Displays the last eight commandsthat were entered.

history Any installed device.

Re-enter previouscommand using numericdesignation

Re-enters a numerically-specifiedcommand from the commandhistory.

!x

where x is the number ofthe command (0 - 7) tore-enter from thecommand history list.


Example: To display a list of the last eight commands entered, while managementmodule 1 is set as the default command target, at the system:mm[1]> prompt, typehistory

To re-enter the command designated by "2" in the command history, type!2

The following example shows the information that is returned from these twocommands:system:mm[1]> history0 dns1 dns -on2 dns3 dns -i1 192.168.70.294 dns5 dns -i1 192.168.70.29 -on6 dns7 historysystem:mm[1]> !2Enabled-i1 192.168.70.29-i2 0.0.0.0-i3 0.0.0.0system:mm[1]>


identify (location LED) commandThis command controls operation of the location LED in a blade server or in theBladeCenter unit. It can also be used to display the state of a location LED.

Table 43. identify (location LED) command


Display location LEDstate

Displays the current state of thelocation LED in the commandtarget.

Possible LED states are:v offv onv blink

identify -T system

-T system:blade[x]

where x is the bladebay number.

Set location LED state Sets the state of the location LED inthe command target.

identify -s state

where state isv onv offv blink


(for BladeCenter unit)v Blade configuration (for

blade server)


-T system

-T system:blade[x]


Turn on BladeCenterunit location LED forspecified period of time

Turns on the location LED in theBladeCenter unit for a specifiedperiod of time before turning it offautomatically.

identify -s on -d time

where time is the numberof seconds the locationLED will remain lit.



-T system


Example: To display the status of the location LED in the blade server in blade bay4, while the BladeCenter unit is set as the persistent command environment, at thesystem> prompt, typeidentify -T system:blade[4]

To light the location LED in the blade server in blade bay 4, while the BladeCenterunit is set as the persistent command environment, at the system> prompt, typeidentify -s on -T system:blade[4]

The following example shows the information that is returned from a series ofidentify commands:system> identify -T system:blade[4]-s offsystem> identify -s on -T system:blade[4]OKsystem> identify -T system:blade[4]-s onsystem>


ifconfig commandThis command configures and displays the network interface settings for themanagement-module Ethernet interface, I/O-module Ethernet interface, and theblade server integrated system management processors and installed options.

Table 44. ifconfig command


Display primarymanagement moduleEthernet channel 0configuration

Displays the current configurationof Ethernet channel 0 for theprimary management module.Possible return values are:v enabledv disabledv -i static_ip_address (dotted

decimal IPv4 IP address format)v -g gateway_address (dotted

decimal IPv4 IP address format)v -s subnet_mask (dotted decimal

IPv4 IP address format)v -n hostnamev -c config_methodv -r data_ratev -d duplex_modev -m mtuv -l locally_administered_mac_addrv -b burnedin_mac_addressv -dn domain_namev -ipv6 ipv6_statev -ipv6static static_ipv6_statev -i6 static_ip_address (IPv6 format)v -p6 address_prefix_lengthv -g6 gateway-default_routev -dhcp6 dhcpv6_statev -sa6 ipv6_stateless_autoconfig_state

If IPv6 is enabled, the link-localaddress link_local_address (for IPv6connection) also displays.

If IPv6 and statelessauto-configuration (-sa6) are bothenabled, the Stateless auto-config IPAddresses / Prefix Lengthaddress_table (table listingauto-generated IPv6 addresses andtheir prefix lengths) also displays.

ifconfig -eth0 -T system:mm[x]



Table 44. ifconfig command (continued)


Display standbymanagement moduleEthernet channel 0configuration

Displays the current configurationof Ethernet channel 0 for thestandby management module.Note: This option does not applyto the BladeCenter S unit.Possiblereturn values are:v enabledv disabledv -i static_ip_address (dotted



IPv4 IP address format)v -n hostnamev -c config_methodv -r data_ratev -d duplex_modev -m mtuv -l locally_administered_mac_addrv -b burnedin_mac_addressv -dn domain_namev -ipv6 ipv6_statev -ipv6static static_ipv6_statev -i6 static_ip_address (IPv6 format)v -p6 address_prefix_lengthv -g6 gateway-default_routev -dhcp6 dhcpv6_statev -sa6 ipv6_stateless_autoconfig_state



ifconfig -eth0 -o -T system:mm[x]

where x is the primarymanagement-modulebay number.Note: Even thoughthis command displaysinformation for thestandby managementmodule, it still mustspecify the primarymanagement moduleas the command target.




Set management moduleEthernet channel 0 staticIP address (IPv4)

Sets the IPv4 static IP address forEthernet channel 0 for themanagement module.Note: Changes made to the IPconfiguration of the primarymanagement module take effectafter the next reset of the primarymanagement module.

ifconfig -eth0 -iip_address

where ip_address is thestatic IP address forEthernet channel 0 indotted decimal IP addressformat.



-T system:mm[x]



Sets the IPv6 static IP address forEthernet channel 0 for themanagement module.

ifconfig -eth0 -i6ip_address

where ip_address is thestatic IP address forEthernet channel 0 in IPv6format.



-T system:mm[x]


Set standby managementmodule Ethernet channel0 static IP address (IPv4)

Sets the IPv4 static IP address forEthernet channel 0 for the standbymanagement module.Note: This option does not applyto the BladeCenter S unit.

ifconfig -eth0 -o -iip_address




-T system:mm[x]





Set standby managementmodule Ethernet channel0 static IP address (IPv6)

Sets the IPv6 static IP address forEthernet channel 0 for the standbymanagement module.Note: This option does not applyto the BladeCenter S unit.

ifconfig -eth0 -o -i6ip_address

where ip_address is thestatic IP address forEthernet channel 0 in IPv6format.



-T system:mm[x]


Set management moduleEthernet channel 0gateway IP address(IPv4)

Sets the IPv4 gateway IP addressfor Ethernet channel 0 for themanagement module.Note: Changes made to the IPconfiguration of the primarymanagement module take effectafter the next reset of the primarymanagement module.

ifconfig -eth0 -gip_address

where ip_address is thegateway IP address forEthernet channel 0 indotted decimal IP addressformat.



-T system:mm[x]


Set management moduleEthernet channel 0gateway/default route(IPv6)

Sets the IPv6 gateway/defaultroute for Ethernet channel 0 for themanagement module.

ifconfig -eth0 -g6ip_address

where ip_address is thegateway/default route forEthernet channel 0 in IPv6format.



-T system:mm[x]





Set management moduleEthernet channel 0subnet mask (IPv4)

Sets the IPv4 subnet mask forEthernet channel 0 for themanagement module.Note: Changes made to the IPconfiguration of the primarymanagement module take effectafter the next reset of the primarymanagement module.

ifconfig -eth0 -ssub_mask

where sub_mask is thesubnet mask for Ethernetchannel 0 in dotteddecimal IP address format.



-T system:mm[x]


Set management moduleEthernet channel 0hostname

Sets the host name for Ethernetchannel 0 for the managementmodule.Note: Changes made to the IPconfiguration of the primarymanagement module take effectafter the next reset of the primarymanagement module.

ifconfig -eth0 -nhostname

where hostname is the hostname for Ethernet channel0. The hostname can be astring up to 63 charactersin length that includesalphanumeric characters,hyphens, and underscores.



-T system:mm[x]





Set standby managementmodule Ethernet channel0 hostname

Sets the host name for Ethernetchannel 0 for the standbymanagement module.Note: This option does not applyto the BladeCenter S unit.

ifconfig -eth0 -o -nhostname

where hostname is the hostname for Ethernet channel0. The hostname can be astring up to 63 charactersin length that includesalphanumeric characters,hyphens, and underscores.



-T system:mm[x]


Set management moduleEthernet channel 0configuration method

Sets the configuration method forEthernet channel 0 for themanagement module.

A value of dthens will try theDHCP configuration and default tothe static IP configuration if DHCPis unsuccessful after 2 minutes.Note:v If the management module

DHCP setting is set to try theDHCP server and then use thestatic IP address, themanagement module will use thestatic IP address when the DHCPserver is not available duringmanagement module start up.When this occurs, the IP addressmight not be reachable ifmultiple management moduleswere started with the same staticIP address.

v Changes made to the IPconfiguration of the primarymanagement module take effectafter the next reset of theprimary management module.

ifconfig -eth0 -cconfig_method

where config_method isv dhcpv staticv dthens



-T system:mm[x]





Set management moduleEthernet channel 0 datarate

Sets the data rate for Ethernetchannel 0 for the managementmodule.

ifconfig -eth0 -rdata_rate

where data_rate isv autov 10v 100



-T system:mm[x]


Set management moduleEthernet channel 0duplex mode

Sets the duplex mode for Ethernetchannel 0 for the managementmodule.

ifconfig -eth0 -dduplex_mode

where duplex_mode isv autov halfv full



-T system:mm[x]


Set management moduleEthernet channel 0 MTU

Sets the MTU (maximumtransmission unit) for Ethernetchannel 0 for the managementmodule.

ifconfig -eth0 -m mtu

where mtu is between 60and 1500, inclusive.



-T system:mm[x]





Set management moduleEthernet channel 0 staticMAC address (locallyadministered)

Sets the locally administered MACaddress to the specified MACaddress for Ethernet channel 0 forthe management module.Note: Changes made to the IPconfiguration of the primarymanagement module take effectafter the next reset of the primarymanagement module.

ifconfig -eth0 -l address

where address is the locallyadministered MACaddress for Ethernetchannel 0. The MACaddress is 6 bytes inlength, hexadecimal,separated by colons. TheMAC address can not be amulticast address (the firstbyte must be even).



-T system:mm[x]

where x is the standbymanagement-modulebay number.

Set standby managementmodule Ethernet channel0 static MAC address(locally administered)

Sets the locally administered MACaddress to the specified MACaddress for Ethernet channel 0 forthe standby management module.Note: This option is not availableon the BladeCenter S.

ifconfig -eth0 -o -laddress




-T system:mm[x]





Set management moduleEthernet channel 0domain name

Sets the domain name for Ethernetchannel 0 for Ethernet channel 0 forthe management module.Note: Changes made to the IPconfiguration of the primarymanagement module take effectafter the next reset of the primarymanagement module.

ifconfig -eth0 -dndomain

where domain is analphanumeric string up to127 characters in length.The domain name mustcontain at least one dot (.).



-T system:mm[x]


Enable / disable IPv6addressing formanagement moduleEthernet channel 0

Enable or disable IPv6 addressingfor Ethernet channel 0 for themanagement module.

ifconfig -eth0 -ipv6state




-T system:mm[x]


Enable / disable staticIPv6 configuration formanagement moduleEthernet channel 0

Enable or disable static IPv6configuration for Ethernet channel0 for the management module.

ifconfig -eth0-ipv6static state




-T system:mm[x]





Set management moduleEthernet channel 0address prefix length

Sets the IPv6 address prefix lengthfor Ethernet channel 0 for themanagement module.

ifconfig -eth0 -p6 length

where length is between 1and 128 (inclusive).



-T system:mm[x]


Enable / disableDHCPv6 formanagement moduleEthernet channel 0

Enable or disable static DHCPv6for Ethernet channel 0 for themanagement module.

ifconfig -eth0 -dhcp6state




-T system:mm[x]


Enable / disable IPv6statelessauto-configuration formanagement module forEthernet channel 0

Enable or disable IPv6 statelessauto-configuration for Ethernetchannel 0 for the managementmodule.

ifconfig -eth0 -sa6 state




-T system:mm[x]





Display primarymanagement moduleEthernet channel 1configuration

Displays the current configurationof Ethernet channel 1 for theprimary management module.Possible return values are:v up (enabled)v down (disabled)v -i static_ip_address (dotted



IPv4 IP address format)v -r data_ratev -d duplex_modev -m mtuv -l locally_administered_mac_addrv -b burnedin_mac_address

ifconfig -eth1 -T system:mm[x]



Sets the static IP address (IPv4) forEthernet channel 1 for themanagement module.Note: Changes made to the IPconfiguration of the primarymanagement module take effectafter the next reset of the primarymanagement module.

ifconfig -eth1 -iip_address




-T system:mm[x]


Set management moduleEthernet channel 1gateway IP address(IPv4)

Sets the gateway IP address (IPv4)for Ethernet channel 1 for themanagement module.Note: Changes made to the IPconfiguration of the primarymanagement module take effectafter the next reset of the primarymanagement module.

ifconfig -eth1 -gip_address

where ip_address is thegateway IP address forEthernet channel 1 indotted decimal IP addressformat.



-T system:mm[x]





Set management moduleEthernet channel 1subnet mask (IPv4)

Sets the subnet mask (IPv4) forEthernet channel 1 for themanagement module.Note: Changes made to the IPconfiguration of the primarymanagement module take effectafter the next reset of the primarymanagement module.

ifconfig -eth1 -ssub_mask

where sub_mask is thesubnet mask for Ethernetchannel 1 in dotteddecimal IP address format.



-T system:mm[x]


Set management moduleEthernet channel 1 datarate

Sets the data rate for Ethernetchannel 1 for the managementmodule.

ifconfig -eth1 -rdata_rate

where data_rate isv autov 10v 100



-T system:mm[x]


Set management moduleEthernet channel 1duplex mode

Sets the duplex mode for Ethernetchannel 1 for the managementmodule.

ifconfig -eth1 -dduplex_mode

where duplex_mode isv autov halfv full



-T system:mm[x]





Set management moduleEthernet channel 1 MTU

Sets the MTU (maximumtransmission unit) for Ethernetchannel 1 for the managementmodule.

ifconfig -eth1 -m mtu

where mtu is between 60and 1500, inclusive.



-T system:mm[x]


Set management moduleEthernet channel 1 staticMAC address (locallyadministered)

Sets the locally administered MACaddress to the specified MACaddress for Ethernet channel 1 forthe management module.Note: Changes made to the IPconfiguration of the primarymanagement module take effectafter the next reset of the primarymanagement module.

ifconfig -eth1 -l address




-T system:mm[x]


Enable managementmodule Ethernet channel1

Enables the Ethernet channel 1interface for the managementmodule.

ifconfig -eth1 -up



-T system:mm[x]





Disable managementmodule Ethernet channel1

Disables the Ethernet channel 1interface for the managementmodule.

ifconfig -eth1 -down



-T system:mm[x]


Display cKVM andnetwork configurationstatus for blade server

Displays the cKVM status andnetwork status for the specifiedblade server.v Valid cKVM states include:

– Enabled– Disabled

v If the blade server supportsnetwork configuration, thiscommand also displays the NICnumbers (such as -eth0 and-eth1), NIC states (up or down),and other NIC configurationinformation for the blade serverand all network cards connectedto the blade server.

ifconfig -T system:blade[x]


Display networkconfigurationinformation for networkcard

Displays the NIC number (such as-eth0 and -eth1), NIC state (up ordown), and other NICconfiguration information for thespecified network card in thespecified blade server.

ifconfig -ethx

where x is the NICnumber.

-T system:blade[x]


Set I/O module for bladeserver managementtraffic

Sets the I/O module that will beused to route management trafficfor the specified blade server.Note: This command will run onlyif the target blade server supportsmanual configuration of itsmanagement network interface.

ifconfig -eth1 -i IO_bay

where IO_bay is the baynumber of the I/Omodule that should beused to route managementtraffic.



-T system:blade[x]





Enable / disable cKVMfeature for blade server

Enable or disable cKVM feature forthe specified blade server.Note: The cKVM feature requiresspecial hardware and is notavailable for all blade servers.

ifconfig -ckvm state




-T system:blade[x]


Set blade server Ethernetchannel static IP address(IPv4)

Sets the IPv4 static IP address forthe specified Ethernet channel ofthe specified blade server.Note: This command will run onlyif the target blade server supportsmanual configuration of itsmanagement network interface.

ifconfig -ethx -iip_address

where:v x is the NIC number.v ip_address is the static IP

address for Ethernetchannel x in dotteddecimal IP addressformat.



-T system:blade[x]





Set blade server Ethernetchannel static IP address(IPv6)

Sets the IPv6 static IP address forthe specified Ethernet channel ofthe specified blade server.Note:v This command will run only if

the target blade server supportsmanual IPv6 configuration of itsmanagement network interface.

v A static IPv6 configuration ID isrequired for network interfacesthat support more than one staticconfiguation.

ifconfig -ethx -i6ip_address -id id

where:v x is the NIC number.v ip_address is the static IP

address for Ethernetchannel x in IPv6format.

v id is the static IPv6configuration ID.



-T system:blade[x]


Set blade server Ethernetchannel gateway IPaddress (IPv4)

Sets the IPv4 gateway IP addressfor the specified Ethernet channelof the specified blade server.Note: This command will run onlyif the target blade server supportsmanual configuration of itsmanagement network interface.

ifconfig -ethx -gip_address

where:v x is the NIC number.v ip_address is the

gateway IP address forEthernet channel x indotted decimal IPaddress format.



-T system:blade[x]





Set blade server Ethernetchannel gateway/defaultroute (IPv6)

Sets the IPv6 gateway/defaultroute for the specified Ethernetchannel of the specified bladeserver.Note:v This command will run only if

the target blade server supportsmanual IPv6 configuration of itsmanagement network interface..


ifconfig -ethx -g6ip_address -id id

where:v x is the NIC number.v ip_address is the

gateway/default routefor Ethernet channel xin IPv6 format.

v id is the static IPv6configuration ID.



-T system:blade[x]


Set blade server Ethernetchannel subnet mask(IPv4)

Sets the IPv4 subnet mask for thespecified Ethernet channel of thespecified blade server.Note: This command will run onlyif the target blade server supportsmanual configuration of itsmanagement network interface.

ifconfig -ethx -ssub_mask

where:v x is the NIC number.v sub_mask is the subnet

mask for Ethernetchannel x in dotteddecimal IP addressformat.



-T system:blade[x]





Set blade server Ethernetchannel configurationmethod

Sets the configuration method forthe specified Ethernet channel ofthe specified blade server.

A value of dthens will try theDHCP configuration and default tothe static IP configuration if DHCPis unsuccessful after 2 minutes.Note:v This command will run only if

the target blade server supportsmanual configuration of itsmanagement network interface.

v If the DHCP setting is set to trythe DHCP server and then usethe static IP address, the NICwill use the static IP addresswhen the DHCP server is notavailable during start up. Whenthis occurs, the IP address mightnot be reachable if multipledevices were started with thesame static IP address.

v Blade servers based on thePower PC chip, including theJS12 and JS22, only support thestatic and DHCP options.

ifconfig -ethx -cconfig_method

where:v x is the NIC number.v config_method is

– dhcp– static– dthens



-T system:blade[x]


Set management moduleEthernet channel VLANID

Sets the VLAN ID for the specifiedEthernet channel of the specifiedblade server.Note: This command will run onlyif the target blade server supportsmanual configuration of itsmanagement network interface.

ifconfig -ethx -v vlan_id

where:v x is the NIC number.v vlan_id is from 1 to

4095, inclusive. If youenter a value outsidethis range, an error willbe displayed.



-T system:blade[x]





Set state for blade serverEthernet channel VLANID

Enables or disables the VLAN IDfor the specified Ethernet channelof the specified blade server.Note: This command will run onlyif the target blade server supportsmanual configuration of itsmanagement network interface.

ifconfig -ethx -ve state

where:v x is the NIC number.v state is enable or

disable.



-T system:blade[x]


Set blade server Ethernetchannel hostname

Sets the host name for the specifiedEthernet channel of the specifiedblade server.Note: This command will run onlyif the target blade server supportsmanual configuration of itsmanagement network interface.

ifconfig -ethx -nhostname

where:v x is the NIC number.v hostname is the host

name. The hostnamecan be a string up to 63characters in length thatincludes alphanumericcharacters, hyphens,and underscores.



-T system:blade[x]


Enable blade serverEthernet channel

Enables the specified Ethernetchannel interface of the specifiedblade server.Note: This command will run onlyif the target blade server supportsmanual configuration of itsmanagement network interface.

ifconfig -ethx -up




-T system:blade[x]





Disable blade serverEthernet channel

Disables the specified Ethernetchannel interface of the specifiedblade server.Note: This command will run onlyif the target blade server supportsmanual configuration of itsmanagement network interface.

ifconfig -ethx -down




-T system:blade[x]


Enable / disable IPv6addressing for bladeserver

Enable or disable IPv6 addressingfor the specified Ethernet channelinterface of the specified bladeserver.Note: This command will run onlyif the target blade server supportsmanual IPv6 configuration of itsmanagement network interface.

ifconfig -ethx -ipv6state

where:v x is the NIC number.v state is enabled or

disabled.



-T system:blade[x]


Set blade server addressprefix length

Sets the IPv6 address prefix lengthfor the specified Ethernet channelinterface of the specified bladeserver.Note:v This command will run only if

the target blade server supportsmanual IPv6 configuration of itsmanagement network interface.


ifconfig -ethx -p6 length-id id

where:v x is the NIC number.v length is between 1 and

128 (inclusive).v id is the static IPv6

configuration ID.



-T system:blade[x]





Enable / disableDHCPv6 for bladeserver

Enable or disable static DHCPv6for the specified Ethernet channelinterface of the specified bladeserver.Note: This command will run onlyif the target blade server supportsmanual IPv6 configuration of itsmanagement network interface.

ifconfig -ethx -dhcp6state


disabled.



-T system:blade[x]


Enable / disable IPv6statelessauto-configuration forblade server

Enable or disable IPv6 statelessauto-configuration for the specifiedEthernet channel interface of thespecified blade server.Note: This command will run onlyif the target blade server supportsmanual IPv6 configuration of itsmanagement network interface.

ifconfig -ethx -sa6 state


disabled



-T system:blade[x]


Set blade server ISMPstatic IP address (IPv4)

Sets the IPv4 static IP address forthe integrated system managementprocessor (ISMP) of the specifiedblade server.Note: This command will run onlyif the target blade server supportsmanual configuration of itsmanagement network interface.

ifconfig -i ip_address

where ip_address is thestatic IP address for theblade server ISMP indotted decimal IP addressformat.



-T system:blade[x]:sp





Display network settingsfor BladeCenter unit

Displays network settings for theBladeCenter unit. Valid returnvalues are:v -v VLAN-idv -maxv enabled/disabled

ifconfig -T system

Enable / disablemultiple video sessionsfor blade servers

Set state to allow only a singleremote video session or allow up tofour remote video sessions for eachblade server.

ifconfig -maxv state

where state is enabled(allow multiple videosessions) or disabled(allow only one videosession).



-T system

VLAN ID forBladeCenter unit

Sets the VLAN ID for theBladeCenter unit.

ifconfig -v VLAN-id

where VLAN-id is from 1to 4095, inclusive. If youenter a value outside thisrange, an error will bedisplayed.



-T system

Set state for BladeCenterunit VLAN ID

Enables or disables the VLAN IDfor the BladeCenter unit.

ifconfig -ve state




-T system




Enable / disable globalcKVM feature forBladeCenter unit

Enable or disable cKVM featureglobally for the BladeCenter unit.(This is the same as running theifconfig -ckvm enable commanddirected to each blade server.)Note: The cKVM feature requiresspecial hardware and is notavailable for all blade servers.

ifconfig -ckvm state




-T system

Display network settingsfor I/O module

Displays network settings for thespecified I/O module. Valid returnvalues are:v I/O-module typev -i ip_address (dotted decimal IPv4

IP address format)v -s subnet_mask (dotted decimal

IPv4 IP address format)v -g gateway_address (dotted

decimal IPv4 IP address format)v -em ext_mgt_statusv -ep ext_port_statusv -pm enabled/disabled (protected

mode)v -pip enabled/disabledv -c config_methodv -ipv6 ipv6_statev -ipv6static static_ipv6_statev -i6 static_ip_address (IPv6 format)v -p6 address_prefix_length (IPv6

format)v -g6 gateway-default_route (IPv6

format)v -dhcp6 dhcpv6_statev -sa6 ipv6_stateless_autoconfig_state



ifconfig -T system:switch[x]





Set starting IP addressfor I/O module (IPv4)

Sets the IPv4 IP addresses for thespecified I/O module.

ifconfig -i ip_address

where ip_address is the IPaddress of the specifiedI/O module in dotteddecimal IP address format.


configuration


-T system:switch[x]


Set starting IP addressfor I/O module (IPv6)

Sets the IPv6 static IP address forthe specified I/O module.

ifconfig -i6 ip_address

where ip_address is thestatic IP address for thespecified I/O module inIPv6 format.


configuration


-T system:switch[x]


Set I/O-module gatewayIP address (IPv4)

Sets the gateway IPv4 IP addressfor the specified I/O module.

ifconfig -g ip_address

where ip_address is thegateway IP address for theI/O module in dotteddecimal IP address format.


configuration


-T system:switch[x]





Set I/O-module gatewayIP address (IPv6)

Sets the IPv6 gateway/defaultroute for the specified I/O module.

ifconfig -g6 ip_address

where ip_address is thegateway IP address for theI/O module in IPv6format.


configuration


-T system:switch[x]


Keep new IP addressconfiguration forI/O-module after reset

Retains a new IP addressconfiguration after the specifiedI/O module is reset.Note: Make sure a valid NewStatic IP Configuration is enteredfor this I/O module so that whenthe module's factory defaults arerestored, or when a reset isinitiated by a source other than themanagement module, the NewStatic IP Configuration will beconfigured. In these casesmanagement modulecommunication with the I/Omodule will be preserved.

ifconfig -pip enabled



configuration


-T system:switch[x]


Revert to old IP addressconfiguration forI/O-module after reset

Reverts IP address to oldconfiguration after the specifiedI/O module is reset.Note: The factory default IPconfiguration will become activewhen the I/O module is reset tofactory defaults by either themanagement module or the I/Omodule. If an I/O module reset isinitiated by a source other than themanagement module, then theprevious IP configuration will be inaffect. In both of these cases themanagement module will lose IPcommunications with the I/Omodule.

ifconfig -pip disabled



configuration


-T system:switch[x]





Set I/O-module subnetmask (IPv4)

Sets the IPv4 subnet mask for thespecified I/O module.

ifconfig -s sub_mask

where sub_mask is thesubnet mask for the I/Omodule in dotted decimalIP address format.


configuration


-T system:switch[x]


Enable / disable externalmanagement for I/Omodule

Enables or disables externalmanagement on all ports for thespecified I/O module.

ifconfig -em state



configuration


-T system:switch[x]


Enable / disable externalports for I/O module

Enables or disables external portsfor the specified I/O module.

ifconfig -ep state



configuration


-T system:switch[x]





Enable / disableprotected mode for I/Omodule

Enables or disables protected modefor the specified I/O module.

ifconfig -pm state



configuration


-T system:switch[x]


Enable / disable IPv6addressing for I/Omodule

Enable or disable IPv6 addressingfor the specified I/O module.

ifconfig -ipv6 state



configuration


-T system:switch[x]


Enable / disable staticIPv6 configuration forI/O module

Enable or disable static IPv6configuration for the specified I/Omodule.

ifconfig -ipv6staticstate



configuration


-T system:switch[x]





Set I/O module addressprefix length

Sets the IPv6 address prefix lengthfor the specified I/O module.

ifconfig -p6 length

where length is between 1and 128 (inclusive).


configuration


-T system:switch[x]


Enable / disableDHCPv6 for I/O module

Enable or disable static DHCPv6for the specified I/O module.

ifconfig -dhcp6 state



configuration


-T system:switch[x]


Enable / disable IPv6statelessauto-configuration forI/O module

Enable or disable IPv6 statelessauto-configuration for the specifiedI/O module.

ifconfig -sa6 state



configuration


-T system:switch[x]





Set IP addresses forRAID controller andSAS system (IPv4)


Sets IPv4 IP addresses for RAIDcontroller and SAS system.

ifconfig -i ip_address_a-ir ip_address_b

wherev ip_address_a is the IP

address of the specifiedSAS system in dotteddecimal IP addressformat.

v ip_address_b is the IPaddress of theassociated RAIDcontroller in dotteddecimal IP addressformat.


configuration


-T system:switch[x]

where x is the RAIDcontroller bay number.

Set gateway IP addressesfor RAID controller andSAS system (IPv4)


Sets the IPv4 gateway IP addressesfor RAID controller and SASsystem.

ifconfig -g ip_address_a-gr ip_address_b

wherev ip_address_a is the

gateway IP address ofthe specified SASsystem in dotteddecimal IP addressformat.

v ip_address_b is thegateway IP address ofthe associated RAIDcontroller in dotteddecimal IP addressformat.


configuration


-T system:switch[x]





Set subnet masks forRAID controller andSAS system (IPv4)


Sets the IPv4 subnet masks for theRAID controller and SAS system.

ifconfig -s sub_mask_a-sr sub_mask_b

wherev sub_mask_a is the subnet

mask of the specifiedSAS system in dotteddecimal IP addressformat.

v sub_mask_b is the subnetmask of the associatedRAID controller indotted decimal IPaddress format.


configuration


-T system:switch[x]


Example:

To display the configuration for Ethernet channel 0, that does not support IPv6,while management module 1 is set as the persistent command environment, at thesystem:mm[1]> prompt, typeifconfig -eth0

To set the IPv4 static IP address for Ethernet channel 0 to 192.168.70.133, whilemanagement module 1 is set as the persistent command environment, at thesystem:mm[1]> prompt, typeifconfig -eth0 -i 192.168.70.133 -c static

To set the IPv4 IP addresses for the BladeCenter S SAS subsystem to 9.186.10.16and the IPv4 IP address for the RAID controller to 9.186.10.17, while switchmodule 3 is set as the persistent command environment, at the system:switch[3]>prompt, typeifconfig -i 9.186.10.16 -ir 9.186.10.17


To set the IPv4 gateway address for the BladeCenter S SAS subsystem to 9.186.10.1and the IPv4 gateway address for the RAID controller to 9.186.11.1, while switchmodule 3 is set as the persistent command environment, at the system:switch[3]>prompt, typeifconfig -g 9.186.10.1 -gr 9.186.11.1

The following example shows the information that is returned from thesecommands:system:mm[1]> ifconfig -eth0Enabled-i 10.10.10.10-g 0.0.0.0-s 255.255.255.0-n MM00096BCA0C80-c Try DHCP server. If it fails, use static IP config.-r Auto-d Auto-m 1500-l 00:00:00:00:00:00-b 00:09:6B:CA:0C:80system:mm[1]> ifconfig -eth0 -i 192.168.70.133 -c staticChanges to the network settings will take effect after the next reset of the MM.system:mm[1]>

system:switch[3]>ifconfig -i 9.186.10.16 -ir 9.186.10.17OKsystem:switch[3]>ifconfig -g 9.186.10.1 -gr 9.186.11.1OKsystem:mm[1]>

To display the configuration for Ethernet channel 0, that supports IPv6, whilemanagement module 1 is set as the persistent command environment, at thesystem:mm[1]> prompt, typeifconfig -eth0

The following example shows the information that is returned from thesecommands:system:mm[1]> ifconfig -eth0Enabled-i 10.13.3.230-g 10.13.1.1-s 255.255.0.0-n primaryAMM-c static-r auto-d auto-m 1500-l 00:00:00:00:00:00-b 00:14:5E:DF:0F:CE-dn primaryAMM.com-ipv6 enabled-ipv6static disabled-i6 6::6-p6 1-g6 ::-dhcp6 enabled-sa6 enabledLink-local address: fe80::214:5eff:fedf:fceStateless auto-config IP Addresses Prefix Length--------------------------------------- -------------


2000:1013::214:5eff:fedf:fce 642001:1013::214:5eff:fedf:fce 642002:1013::214:5eff:fedf:fce 64system:mm[1]>


info (configuration information) commandThis command displays information about BladeCenter components and theirconfiguration, and how to reload the component information.

Table 45. info (configuration information) command


Display componentinformation

Displays identification andconfiguration information for thecommand target.

info

Note: Only one target at atime can be viewed withthe info command.

-T system

-T system:mm[x]

-T system:blade[x]

-T system:blower[x]

-T system:ncc[x]

-T system:mux[x]

-T system:tap

-T system:blade[x]:exp[y]

-T system:blade[x]:mgmtcrd


-T system:blade[x]:be[y]

-T system:blade[x]:be[y]:exp[z]

-T system:blade[x]:be[y]:hsec[z]

-T system:blade[x]:sb

-T system:blade[x]:cpu[y]

-T system:blade[x]:memory[y]

-T system:blade[x]:hsec[y]

-T system:blade[x]:ckvm

-T system:switch[x]

-T system:power[x]

-T system:mt[x]

-T system:mt[x]:bbu[y]

-T system:storage[x]

-T system:storage[x]:disk[y]



Table 45. info (configuration information) command (continued)


Display componentinformation

(continued)

where:

v x is themanagement-modulebay number, bladeserver bay number,I/O-module baynumber,microprocessornumber, power modulebay number,media-tray baynumber, storage baynumber , ordaughter-card number.

v y or z is the:

– blade server storageexpansion unitnumber (be).

– blade server I/Oexpansion cardnumber (exp).

– microprocessornumber (CPU).

– memory DIMMnumber.

– high-speedexpansion cardnumber (hsec).

– battery backup unitnumber (bbu).

– disk drive number(disk).

Display managementchannel pathinformation

Displays the management channelpath information for theBladeCenter unit.

info -path -T system

Reload componentinformation forfirmware

Reloads vital product data (VPD)for firmware.

info -reload fw -T system

Reload componentinformation forhardware

Reloads vital product data (VPD)for hardware.

info -reload hw -T system

Reload information onMAC addresses

Reloads vital product data (VPD)for MAC addresses.

info -reload mac -T system

Reload WWN andGUID information

Reloads vital product data (VPD)for world-wide name (WWN) andglobally-unique identifier (GUID).

info -reload wwn -T system

Reload all componentinformation

Forces reload of all VPD andMAC address information.

info -reload all -T system


Notes:

1. The command target -T system:blade[x]:exp[y] is shown with a line breakbefore the :exp[y]. When this command target is entered, the entire entry mustall be on one line.

2. This command returns vital product data (VPD) information that is unique foreach command target. For some targets, additional VPD information isavailable when using the advanced management module.

3. Even if the command target is specified, the -reload option acts globally,reloading information not just for the specified target but for all targets in thecorresponding category; for example, all MAC addresses are reloaded for alltargets when the command is info -reload mac with system:blade[x] as thetarget.

Example: To view the information about an advanced management module inmanagement-module bay 1, while this management module is set as the persistentcommand environment, at the system:mm[1]> prompt, typeinfo

The following example shows the information that might be returned from the infocommand:system:mm[1]> info

Name: AMM_KPManufacturer: Not Available (Not Available)Manufacturer ID: 288Product ID: 1Mach type/model: Management ModuleMach serial number: Not AvailableManuf date: 3005Hardware rev: 51Part no.: 26R099000000FRU no.: 25R5777FRU serial no.: 0J1U9E584130CLEI: Not AvailableAMM firmware

Build ID: BPET30UFile name: CNETCMUS.PKTRel date: 08-09-07Rev: 30

AMM firmware (Flashed - pending restart)Build ID: BPET30xFile name: CNETCMUS.PKTRel date: 09-09-08Rev: 30

system:mm[1]>


iocomp commandThis command displays the compatibility between all blade servers and their I/Omodules. It can also display detailed interface information for an individual bladeserver or I/O module.

Table 46. iocomp command


Display compatibilitybetween all blade serversand I/O modules

Displays I/O module compatibilityinformation for all blade serversand I/O modules.

iocomp -T system

Display blade servercompatibility details

Displays detailed I/O modulecompatibility information for thespecified blade server.

iocomp -T system:blade[x]


Display I/O modulecompatibility details

Displays detailed compatibilityinformation for the specified I/Omodule.

iocomp -T system:switch[x]


Example: To view I/O module compatibility information for all blade servers andI/O modules, while management module 1 is set as the persistent commandenvironment, at the system:mm[1]> prompt, typeiocomp -T system

To view I/O module compatibility information for the blade server in blade bay 1,while management module 1 is set as the persistent command environment, at thesystem:mm[1]> prompt, typeiocomp -T system:blade[1]

To view I/O module compatibility information for the I/O module in bay 2, whilemanagement module 1 is set as the persistent command environment, at thesystem:mm[1]> prompt, typeiocomp -T system:switch[2]

The following example shows the information that is returned from thesecommands:system:mm[1]> iocomp -T systemBlades1 xPert1 OK2 xPert2 OK3 Development OK4 Marketing OK5 xpert3 OK6 Sales OK7 xPert4 OK9 xPert5 OK11 Finance OK12 HR OK13 xPert6 OK14 xPert7 OK

I/O Modules1 OK2 OK3 OK4 OK


system:mm[1]> iocomp -T system:blade[1]Bay Power Fabric Type Fabric on Blade Compt

------- ------- ---------------------- --------------- -------IOM 1 On Ethernet Switch Module Ethernet OKIOM 2 On Ethernet Switch Module Ethernet OKsystem:mm[1]> iocomp -T system:switch[1]

Bay Power Fabric Type Compat---------- ------- -------------- ----------Blade 1 On Ethernet OKBlade 2 On Ethernet OKBlade 3 On Ethernet OKBlade 4 On Ethernet OKBlade 5 Off Ethernet OKBlade 6 On Ethernet OKBlade 7 On Ethernet OK

n/a No FabricBlade 9 On Ethernet OK

Ethernet OKBlade 11 On Ethernet OKBlade 12 On Ethernet OKBlade 13 On Ethernet OKBlade 14 On Ethernet OKsystem:mm[1]>


kvm (keyboard, video, mouse) commandThis command sets and displays the blade server that is in control of theBladeCenter unit shared KVM.

Table 47. kvm command


Display KVM owner Displays the number of the bladeserver that has KVM ownershipand the global local KVMswitching state for all blade servers.A blade server that occupies morethan one blade bay is identified bythe lowest bay number that itoccupies. A return value of 0indicates that no owner is set.

kvm -T system

Set KVM owner Sets a blade server as the KVMowner.

kvm -b blade_server

where blade_server is theblade-bay number thatidentifies the blade server.A blade server thatoccupies more than oneblade bay is identified bythe lowest bay numberthat it occupies. A settingof 0 sets no owner.



-T system

Enable / disable localKVM switching globally

Enable or disable local KVMswitching globally for all bladeservers.

kvm -local state




-T system


Example:

To set the KVM owner to the blade server in blade bay 1, while managementmodule 1 is set as the persistent command environment, at the system:mm[1]>prompt, typekvm -T system -b 1

To display the KVM owner and global local KVM switching state for all bladeservers, while management module 1 is set as the persistent commandenvironment, at the system:mm[1]> prompt, typekvm -T system

The following example shows the information that is returned from these twocommands:system:mm[1]> kvm -T system -b 1OKsystem:mm[1]> kvm -T system-b 1-local enabledsystem:mm[1]>


ldapcfg commandThis command sets and displays the LDAP configuration settings for the advancedmanagement module.

Table 48. ldapcfg command


Display LDAP settings Displays the LDAP settings for themanagement module.

ldapcfg -T system:mm[x]


Set LDAP securityversion

Sets version of LDAP security usedby the management module.

ldapcfg -v version

where version is:v v1 for old user

permission modelv v2 for the enhanced

role-based securitymodel



-T system:mm[x]


Set LDAP name Sets the LDAP name for themanagement module.Note: For an LDAP name to beused, LDAP security must be set tov2 using the -v command option.

ldapcfg -t name

where name is analphanumeric string up to63 characters in lengthcontaining any characterexcept for angle brackets (< and > ) and spaces.



-T system:mm[x]



Table 48. ldapcfg command (continued)


Set LDAP serverdiscovery method

Sets the method to use fordiscovering LDAP servers thatprovide user authentication.Note:v If the dns method is specified,

the following values must alsobe set:– A domain source using the

-ds command option.– A service name using the -sn

command option.– A search domain must be set

using the -sd commandoption.

v If the preconf method isspecified, the following valuesmust also be set:– An LDAP server hostname or

IP address using the -i1, -i2,and -i3 command options.

– A port for each LDAP serverhostname or IP address usingthe -p1, -p2, and -p3command options.

ldapcfg -server method

where method is:v dns for dynamic

discoveryv preconf to use an LDAP

server that wasmanuallypre-configured



-T system:mm[x]


Set LDAP server domainname

Sets the search domain to use forDomain Controller (DC) dynamicdiscovery.

ldapcfg -dn domain

where domain is analphanumeric string up to31 characters in length.



-T system:mm[x]


Set LDAP server forestname

Sets the forest name to use forGlobal Catalog (GC) dynamicdiscovery.

ldapcfg -fn forestname

where forestname is analphanumeric string up to63 characters in length.



-T system:mm[x]





First LDAP server hostname or IP address - set

Checks syntax and sets the firstLDAP server host name or IPaddress to use for pre-configuredLDAP server discovery.Note: A port for this LDAP serverhostname or IP address must be setusing the -p1 command option.

ldapcfg -i1hostname/ip_address

where hostname/ip_addressis the first host name or IPaddress.



-T system:mm[x]


Second LDAP serverhost name or IP addressset

Checks syntax and sets the secondLDAP server host name or IPaddress to use for pre-configuredLDAP server discovery.Note: A port for this LDAP serverhostname or IP address must be setusing the -p2 command option.


where hostname/ip_addressis the second host name orIP address.



-T system:mm[x]


Third LDAP server hostname or IP address - set

Checks syntax and sets the thirdLDAP server host name or IPaddress to use for pre-configuredLDAP server discovery.Note: A port for this LDAP serverhostname or IP address must be setusing the -p3 command option.


where hostname/ip_addressis the third host name orIP address.



-T system:mm[x]





Fourth LDAP server hostname or IP address - set

Checks syntax and sets the fourthLDAP server host name or IPaddress to use for pre-configuredLDAP server discovery.Note: A port for this LDAP serverhostname or IP address must be setusing the -p4 command option.


where hostname/ip_addressis the fourth host name orIP address.



-T system:mm[x]


First LDAP server portnumber - set

Sets the port number of the firstLDAP server to use forpre-configured LDAP serverdiscovery.

ldapcfg -p1 port

where port is from 1 to65535, inclusive. If youenter a value outside thisrange, an error will bedisplayed.



-T system:mm[x]


Second LDAP serverport number - set

Sets the port number of the secondLDAP server to use forpre-configured LDAP serverdiscovery.

ldapcfg -p2 port




-T system:mm[x]





Third LDAP server portnumber - set

Sets the port number of the thirdLDAP server to use forpreconfigured LDAP serverdiscovery.

ldapcfg -p3 port




-T system:mm[x]


Fourth LDAP server portnumber - set

Sets the port number of the fourthLDAP server to use forpreconfigured LDAP serverdiscovery.

ldapcfg -p4 port




-T system:mm[x]


Set LDAP rootdistinguished name

Sets the root distinguished namefor the root entry of the LDAPdirectory tree that is used as thebase object for all searches.

ldapcfg -rd "name"

where "name" is up to 63characters in length andcontained withindouble-quotes. Names cancontain any character,including spaces.



-T system:mm[x]





Set LDAP UID searchattribute

Sets the UID search attribute thatrepresents the user IDs stored onthe LDAP server.

On Active Directory servers, theUID search attribute is typically setto "sAMAccountName". On NovelleDirectory and OpenLDAP servers,it is typically set to "uid".

ldapcfg -usa "UID"

where "UID" is up to 23characters in length andcontained withindouble-quotes. The UIDcan contain only letters,numbers, spaces, and thefollowing characters: "-","(", ")", "+", ",", ".", "/", ":",and"?".



-T system:mm[x]


Set LDAP serverbinding method

Sets the binding method for initialconnection to the LDAP server.Note:v If the binding method is set to

anon, a UID search attributemust be set using the -usacommand option.

v If the binding method is set tocc, the following values mustalso be set:– A UID search attribute using

the -usa command option– A client distinguished name

using the -cd commandoption.

– A client password using the-p and -cp command options.

ldapcfg -bm version

where version is:v anon for anonymousv cc for configured

credentialsv lc for login credentials



-T system:mm[x]


Set LDAP server to beused for authenticationonly

Enables the authentication mode touse the LDAP server forauthentication only with localauthorization. This automaticallydisables the authentication modethat uses the LDAP Server for bothauthentication and authorization.

LDAP server authentication usesthe settings configured by the“groups command” on page 159.

ldapcfg -aom state

where state is enabled ordisabled



-T system:mm[x]





Set LDAP clientdistinguished name

Sets the client distinguished name(DN) for initial connection to theLDAP server.Note: A client password must alsobe set using the -p and -cpcommand options.

ldapcfg -cd domain

where domain is analphanumeric string up to63 characters in lengthcontaining any characterexcept for angle brackets (< and > ) and spaces.



-T system:mm[x]


Set LDAP clientdistinguished namepassword

Sets the client distinguished namepassword for initial connection tothe LDAP server.Note: The passwords must bespecified by both the -p and -cpcommand options and must match.

ldapcfg -p password

where password is analphanumeric string up to15 characters in length.



-T system:mm[x]


Set (confirm) LDAPclient distinguishedname password

Sets, for confirmation purposes, theclient distinguished name passwordfor initial connection to the LDAPserver.Note: The passwords must bespecified by both the -p and -cpcommand options and must match.

ldapcfg -cp password

where password is analphanumeric string up to15 characters in length.



-T system:mm[x]





Set LDAP group filter Sets the group filter for themanagement module that can beused for authentication duringLDAP server login.

ldapcfg -gf "filter"

where "filter" is aquote-delimited string ofup to 511 characters inlength and consists of oneor more group names. Thecolon (:) character is usedto delimit multiple groupnames. Leading spacesand trailing spaces areignored. Other spaces aretreated as part of thegroup name. The wildcardcharacter (*) is notsupported for securityreasons. A group namecan be specified as a fulldomain name or by usingthe common name (cn)portion.



-T system:mm[x]


Set LDAP group searchattribute

Sets the group search attribute thatrepresents groups of user IDsstored on the LDAP server.

On Active Directory servers, thegroup search attribute is typicallyset to "memberOf". On eDirectoryservers, it is typically set to"groupMembership".

In an OpenLDAP serverenvironment, users are typicallyassigned to groups whoseobjectClass equals "PosixGroup". Inthis case, the group search attributeidentifies members of a particularPosixGroup that is typically"memberUid".

ldapcfg -gsa "GSA"

where "GSA" is aquote-delimitedalphanumeric string of upto 23 characters in length.



-T system:mm[x]





Set LDAP loginpermission attribute

Sets the login permission attributethat is used to determine retrieveuser permissions on the LDAPserver.

ldapcfg -lpa "permission"

where "permission" is aquote-delimitedalphanumeric string up to23 characters in length.



-T system:mm[x]


Note: The -ds, -sd, and -sn options for the ldapcfg command have been deletedand replaced by the -dn and -fn command options. To implement this transition,the items specified for dynamic discovery have changed and must be modified tomatch the syntax required by the new command options.

Example:

To display the management module LDAP settings, while management module 1is set as the persistent command environment, at the system:mm[1]> prompt, typeldapcfg

To enable the authentication mode to use the LDAP server for authentication onlywith local authorization, while management module 1 is set as the persistentcommand environment, at the system:mm[1]> prompt, typeldapcfg -aom enabled

The following example shows the information that is returned from these twocommands:system:mm[1]> ldapcfg-server preconfParameters for ’-server dns’ configuration:

-dn-fn test_fn

Parameters for ’-server preconf’ configuration:-i1-p1-i2-p2-i3-p3-i4 192.168.1.23-p4 11

Miscellaneous Parameters:-rd 11-usa-bm cc-aom enabled


Parameters for ’-bm cc’ configuration:-cd

-v v1Parameters for ’-v v1’ configuration:

-gf-gsa-lpa

Parameters for ’-v v2’ configuration:-t

system:mm[1]> ldapcfg -aom enabledOKsystem:mm[1]>


led commandThis command displays and sets the LED states for a specified command target, ifthis command target supports the LED.

Table 49. led command


Display various LEDstates

Displays various LED states. Valuesreturned are:v status of all LEDs on the target

blade and its subcomponentsv status of info LEDv status of location LED

(on/off/blink)v status of the identification LED

of the system for a specifiednumber of seconds

led -T system

-T system:blade[x]

where x is the bladeserver number.

Display state forfanpack fault LED

Displays the state of the fan packfault LED of the BladeCenter HTunit.

led -T system:power[x]

where x is the powermodule (fanpack)number.

Display state for blowerfault LED

Displays the state of the blowerfault LED of the BladeCenter HTunit.

led -T system:blower[x]

where x is the blowernumber.

Display front panel LEDstate for blade server

Displays the state of the front panelLEDs on the specified blade server.

led -T system:blade[x]


Display external portlink status LED state forI/O module

Displays state of the external andinternal port link status LEDs forthe specified I/O module.

led -T system:switch[x]

where x is the I/Omodule (switch) baynumber.

Display fault LED state

(for BladeCenter HTunits only)

Displays the state of the fault LEDfor the specified command target.Possible return values are:v The state of the requested LED is

onv The state of the requested LED is

off

led -e -T system:tap

-T system:ncc[x]

-T system:mux[x]

-T system:mt[x]

where x is the alarmpanel module, networkclock module,multiplexer expansionmodule, or media traynumber.

Display safe-to-removeLED state

(for BladeCenter HTunits only)

Displays the state of thesafe-to-remove LED, that is on theBladeCenter unit and somecomponents, for the specifiedcommand target. Possible returnvalues are:v onv off

led -r -T system:tap

-T system:ncc[x]

-T system:mux[x]

where x is the alarmpanel module, networkclock module, ormultiplexer expansionmodule.


Table 49. led command (continued)


Display LED state forblade server and allsub-components

Displays the state of all LEDs onthe specified blade server and itssubcomponents. Possible returnvalues are:

v on

v off

v blink

led -l -T system:blade[x]


Turn off informationLED

Turns off the information LED, thatis on the BladeCenter unit andsome components, for the specifiedcommand target

led -info off


management (forBladeCenter unit,network clock module,multiplexer expansionmodule, or media tray)

v Chassis logmanagement (forBladeCenter unit,network clock module,multiplexer expansionmodule, or media tray)

v Chassis administration(for BladeCenter unit,network clock module,multiplexer expansionmodule, or media tray)

v Chassis configuration(for BladeCenter unit,network clock module,multiplexer expansionmodule, or media tray)

v Blade administration(for blade server)


v Blade remote presence(for blade server)


-T system

-T system:blade[x]

-T system:ncc[x] (forBladeCenter HT unitsonly)

-T system:mux[x] (forBladeCenter HT unitsonly)

-T system:mt[x]

where x is the bladeserver, network clockmodule, multiplexerexpansion module, ormedia tray number.




Set location LED state Sets the state of the location LED,that is on the BladeCenter unit andsome blade servers, for thecommand target.

led -loc state

where state isv onv offv blink

Note: A state of blink canonly be used for the -Tsystem command targetand for the blade servers.


management (forBladeCenter unit)

v Chassis logmanagement (forBladeCenter unit)

v Chassis administration(for BladeCenter unit)

v Chassis configuration(for BladeCenter unit)



v Blade remote presence(for blade server)


-T system

-T system:blade[x]





Turn on location LEDfor specified period oftime

Turns on the location LED, that ison the BladeCenter unit and someblade servers, for a specified periodof time before turning it offautomatically.

led -loc on -d time

where time is the numberof seconds the locationLED will remain lit.





-T system

Example: To display the failure LED status for the blade server in bay 1, while theBladeCenter HT unit is set as the persistent command environment, at the system>prompt, typeled -T system:blade[1]

To display status of the front-panel LEDs for the blade server in bay 1, while theBladeCenter HT unit is set as the persistent command environment, at the system>prompt, typeled -T blade[1]

To display status of all LEDs for the blade server in bay 1, while the BladeCenterHT unit is set as the persistent command environment, at the system> prompt,typeled -l -T blade[1]

The following example shows the information that is returned from thesecommands:system> led -T blade[1]hs21_345678Error: offInformation: offKVM: offMT: offLocation: blinksystem> led -T blade[1] -lComponent Label State LocationProcessor1 CPU1 Off System boardProcessor2 CPU2 Off System boardBlade1 Fault Off Front panelBlade2 Information Off Front panelBlade3 Location Blink Front panelBlade4 Power On Front panel

KVM Off Front panelBlade5 Media Tray Off Front panel


Blade7 Over Temp Off System boardBlade8 N/A Off System boardBlade1 N/A Off System boardStorage1 DASD1 Off System boardMemory1 DIMM1 Off System boardMemory2 DIMM2 Off System boardMemory3 DIMM3 Off System boardMemory4 DIMM4 Off System boardMemory5 DIMM5 Off System boardMemory6 DIMM6 Off System boardMemory7 DIMM7 Off System boardMemory8 DIMM8 Off System boardPanel1 N/A Off System boardExpansion1 N/A Off FRU

N/A Off FRUExpansion2 N/A Off FRU

N/A Off FRUN/A Off FRUN/A Off FRU

Expansion3 N/A Off FRUsystem>


list (system physical configuration) commandThis command displays a list of devices present within the command target. It canbe used to determine how many management modules are installed in theBladeCenter unit and which management module is set as primary.

Table 50. list (system physical configuration) command


View command target Displays the current commandtarget. If a management-modulebay is the current command target,it will be identified as primary orstandby (redundant).

list Any installed device.

View systemconfiguration tree

Displays the tree structure ofdevices present in the BladeCenterunit, starting at the commandtarget level. If management-modulebays are part of the tree, they willbe identified as primary or standby(redundant). For components thathave been assigned a name, thisname will be displayed next to thecomponent bay number.

list -l depth

where depth isv all or a for full tree

display, starting at thecommand target level

v 1 to display the currentcommand target

v 2 displays the content ofthe current commandtarget plus one levelbelow it


Example: To display a list of devices installed in the BladeCenter unit, while theBladeCenter unit is set as the persistent command environment, at the system>prompt, typelist -l a

(This is the command syntax that can be used to determine the primarymanagement module.)

The following example shows the information that is returned when the commandis run on an advanced management module:system> list -l asystem

mm[1] primarymm[2] standbypower[1]power[2]power[3]power[4]blower[1]blower[2]switch[1]switch[2]switch[3]switch[4]blade[1] Accounting

spcpu[1]cpu[2]

blade[2] HRspcpu[1]cpu[2]

blade[3] Developmentsp


cpu[1]blade[4] Marketing

spckvmcpu[1]cpu[2]

blade[5] Salesspcpu[1]cpu[2]

blade[6] TechSupportspexp[2]cpu[1]cpu[3]cpu[4]

mt[1]system>

Note: The BladeCenter S unit supports one management module. The listcommand for this unit does not refer to primary and standby managementmodules.


mcad commandThis command configures and displays the auto-discovery setting for theBladeCenter unit management channel.

Note: See the BladeCenter Advanced Management Module User's Guide for additionalinformation about management channel auto discovery.

Table 51. mcad command


Display managementchannel auto-discoverystatus for BladeCenterunit

Displays the auto-discovery settingfor the BladeCenter unitmanagement channel. Valid statesinclude:v Enabledv Disabled

mcad -T system:mm[x]


Enable / disablemanagement channelauto-discovery forBladeCenter unit

Enable or disable managementchannel auto-discovery for theBladeCenter unit.

mcad -e state




-T system:mm[x]


Example:

To display the auto-discovery setting for the BladeCenter unit managementchannel, while the BladeCenter unit is set as the persistent command environment,at the system> prompt, typemcad -T mm[1]

To enable management channel auto-discovery for the BladeCenter unit, while theBladeCenter unit is set as the persistent command environment, at the system>prompt, typemcad -T mm[1] -e enabled

The following example shows the information that is returned from thesecommands:system> mcad -T mm[1]-e disabledsystem> mcad -T mm[1] -e enabledOKsystem>


modactlog commandThis command displays information about modules installed in all of the bladeservers.

Table 52. modactlog command


Display blade servermodule information andactivity

Displays a list of modules installedin all blade servers, along withtheir activity and VPD information.

modactlog -T system

Example: To view the list of modules installed in all blade servers, along with theiractivity and VPD information, while the BladeCenter unit is set as the defaultcommand target, at the system> prompt, typemodactlog

The following example shows the information that is returned from this command:system> modactlogBay Name FRU Number FRU Serial No Manuf. ID Action Timestamp--- ----------------------------- ------------ ------------- --------- ------- -------------------14 Fibre Channel Expansion Card 59P6624 J1RJH3CY18N SLRM Added 15:51:18 02/09/200711 cKVM card 13N0842 YK328064418F IBM Added 15:51:07 02/09/2007system>

Note: The BladeCenter S unit will also display information about the Direct SerialAttach Module and the storage modules.


monalerts commandThis command displays and configures alerts that are monitored by the advancedmanagement module.

Important: The monalertsleg command is no longer supported by the advancedmanagement module firmware. Legacy alert monitoring that uses the monalertslegcommand must transition to use of the monalerts command. Existing legacy alertsettings are automatically mapped to the new alert categories as part of thetransition.

Table 53. monalerts command


Display monitored alertstates

Displays the state of all alerts beingmonitored by the managementmodule.

monalerts -T system:mm[x]


Set state for enhancedlegacy alert categories

Enables enhanced legacy alertcategories.v If enhanced legacy alert

categories are enabled, alerts areconfigured using the monalertscommand.

v If enhanced legacy alertcategories can not be disabledonce they have been enabled.

monalerts -ec state

where state is enabled.



-T system:mm[x]


Set monitoring state forall critical alerts

Enables or disables monitoring ofall critical alerts.

monalerts -ca state




-T system:mm[x]



Table 53. monalerts command (continued)


Set monitoring state forblade device criticalalerts

Enables or disables monitoring ofblade device critical alerts.

monalerts -cb state




-T system:mm[x]


Set monitoring state forI/O-module critical alerts

Enables or disables monitoring ofI/O-module critical alerts.

monalerts -ciom state




-T system:mm[x]


Set monitoring state forstorage-module criticalalerts


Enables or disables monitoring ofstorage-module critical alerts.

monalerts -cstg state




-T system:mm[x]





Set monitoring state forchassis or systemmanagement criticalalerts

Enables or disables monitoring ofchassis or system managementcritical alerts.

monalerts -ccsm state




-T system:mm[x]


Set monitoring state forcooling device criticalalerts

Enables or disables monitoring ofcooling device critical alerts.

monalerts -ccd state




-T system:mm[x]


Set monitoring state forpower module criticalalerts

Enables or disables monitoring ofpower module critical alerts.

monalerts -cpm state




-T system:mm[x]





Set monitoring state forall warning alerts

Enables or disables monitoring ofall warning alerts.

monalerts -wa state




-T system:mm[x]


Set monitoring state forblade device warningalerts

Enables or disables monitoring ofblade device warning alerts.

monalerts -wb state




-T system:mm[x]


Set monitoring state forI/O-module warningalerts

Enables or disables monitoring ofI/O-module warning alerts.

monalerts -wiom state




-T system:mm[x]





Set monitoring state forstorage-module warningalerts


Enables or disables monitoring ofstorage-module warning alerts.

monalerts -wstg state




-T system:mm[x]


Set monitoring state forchassis or systemmanagement warningalerts

Enables or disables monitoring ofchassis or system managementwarning alerts.

monalerts -wcsm state




-T system:mm[x]


Set monitoring state forevent log warning alerts

Enables or disables monitoring ofevent log warning alerts.

monalerts -wel state




-T system:mm[x]





Set monitoring state forcooling device warningalerts

Enables or disables monitoring ofcooling device warning alerts.

monalerts -wcd state




-T system:mm[x]


Set monitoring state forpower module warningalerts

Enables or disables monitoring ofpower module warning alerts.

monalerts -wpm state




-T system:mm[x]


Set monitoring state forall informational alerts

Enables or disables monitoring ofall informational alerts.

monalerts -ia state




-T system:mm[x]





Set monitoring state forblade deviceinformational alerts

Enables or disables monitoring ofblade device informational alerts.

monalerts -ib state




-T system:mm[x]


Set monitoring state forI/O-moduleinformational alerts

Enables or disables monitoring ofI/O-module informational alerts.

monalerts -iiom state




-T system:mm[x]


Set monitoring state forstorage-moduleinformational alerts


Enables or disables monitoring ofstorage-module informationalalerts.

monalerts -istg state




-T system:mm[x]





Set monitoring state forchassis or systemmanagementinformational alerts

Enables or disables monitoring ofchassis or system managementinformational alerts.

monalerts -icsm state




-T system:mm[x]


Set monitoring state forpower stateinformational alerts

Enables or disables monitoring ofpower state (on/off) informationalalerts.

monalerts -ipon state




-T system:mm[x]


Set monitoring state forinventory changeinformational alerts

Enables or disables monitoring ofinventory change (installedcomponents) informational alerts.

monalerts -iinv state




-T system:mm[x]





Set monitoring state forevent log informationalalerts

Enables or disables monitoring ofevent log informational alerts.

monalerts -iel state




-T system:mm[x]


Set monitoring state fornetwork changeinformational alerts

Enables or disables monitoring ofnetwork change informationalalerts.

monalerts -inc state




-T system:mm[x]


Set monitoring state foruser activityinformational alerts

Enables or disables monitoring ofuser activity informational alerts.

monalerts -iua state




-T system:mm[x]





Set monitoring state forcooling deviceinformational alerts

Enables or disables monitoring ofcooling device informational alerts.

monalerts -icd state




-T system:mm[x]


Set monitoring state forpower moduleinformational alerts

Enables or disables monitoring ofpower module informational alerts.

monalerts -ipm state




-T system:mm[x]


Example: To enable monitoring of all critical alerts and event log warning alertsand disable monitoring of all informational alerts, while management module 1 isset as the persistent command environment, at the system:mm[1]> prompt, typemonalerts -ca enabled -wel enabled -ia disabled

The following example shows the information that is returned from this command:system:mm[1]> monalerts -ca enabled -wel enabled -ia disabledOKsystem:mm[1]>


mt (media tray) commandThis command sets and displays the blade server that is in control of theBladeCenter unit shared media tray.

Table 54. mt command


Display media trayowner

Displays the number of the bladeserver that has media trayownership and the global local andremote media tray switching statesfor all blade servers. A blade serverthat occupies more than one bladebay is identified by the lowest baynumber that it occupies. A returnvalue of 0 indicates that no owneris set.

mt -T system

Set media tray owner Sets a blade server as the mediatray owner.

mt -b blade_server

where blade_server is theblade bay that identifiesthe blade server. A bladeserver that occupies morethan one blade bay isidentified by the lowestbay number that itoccupies. A setting of 0sets no owner.



-T system

Enable / disable localmedia tray switchingglobally

Enable or disable local media trayswitching globally for all bladeservers.

mt -local state




-T system


Table 54. mt command (continued)


Enable / disable remotemedia tray switchingglobally

Enable or disable remote mediatray switching globally for all bladeservers.

mt -remote state




-T system

Example:

To set the media tray owner to the blade server in blade bay 1, while managementmodule 1 is set as the persistent command environment, at the system:mm[1]>prompt, typemt -T system -b 1

To display the media tray owner and the global local and remote media trayswitching states for all blade servers, while management module 1 is set as thepersistent command environment, at the system:mm[1]> prompt, typemt -T system

The following example shows the information that is returned from these twocommands:system:mm[1]> mt -T system -b 1OKsystem:mm[1]> mt -T system-b 1-local enabled-remote enabledsystem:mm[1]>


nat commandThis command sets and displays the network address table (NAT) settings for thespecified I/O module.

Notes:

1. If the nat command is directed to an I/O module that does not support thenetwork address table, the "NAT configuration is not supported on this I/Omodule" message is returned.

2. When setting values for an empty row in the network address table, all optionsmust be specified together using a single command.

Table 55. nat command


Display I/O-modulenetwork protocolsettings

Displays the network port settingsfor the specified I/O module.Returned values include those inTable 56 on page 244.

nat -T system:switch[x]


Reset I/O-modulenetwork protocolsettings

Resets all network address tablesettings for the specified I/Omodule to the default values.Default values are in Table 56 onpage 244.

You must activate any changes tothe network protocol settingsbefore they take effect.

nat -reset


configuration


-T system:switch[x]


Activate I/O-modulenetwork protocolsettings

Activates all network port settingsfor the specified I/O module,putting them into effect.

nat -activate


configuration


-T system:switch[x]



Table 55. nat command (continued)


Set protocol name forrow in I/O-module NATtable

Sets a protocol name for thespecified row in the NAT table forthe specified I/O module.

nat -index -pnprotocol_name

where:v index is a number from

1 to 10 that correspondsto a row in the NATtable.

v protocol_name is a textstring with a maximumlength of 19 charactersand no spaces.


configuration


-T system:switch[x]


Set protocol ID for rowin NAT table

Sets a protocol ID for the specifiedrow in the NAT table for thespecified I/O module.

nat -index -pi protocol_id



v protocol_id is TCP orUDP.


configuration


-T system:switch[x]





Set internal port numberfor row in NAT table

Sets the internal port number forthe specified row in the NAT tablefor the specified I/O module.

nat -index -ipport_number



v port_number is between1 and 65534, inclusive.


configuration


-T system:switch[x]


Set external port numberfor row in NAT table

Sets the external port number forthe specified row in the NAT tablefor the specified I/O module.

nat -index -ep port_number



v port_number is between1000 and 65534,inclusive.


configuration


-T system:switch[x]





Set state for row in NATtable

Enables or disables the specifiedrow in the NAT table for thespecified I/O module.

nat -index -en state



v state is enabled ordisabled.


configuration


-T system:switch[x]


Table 56. Default NAT table values for nat command

IndexProtocolName Protocol ID Internal Port External Port State

1 HTTP TCP 80 1080 Enabled

2 TELNET TCP 23 1023 Enabled

3 HTTPS TCP 43 1043 Enabled

4 SSH TCP 22 1022 Enabled

5 SNMP UDP 161 1161 Enabled

6 through 10 Unset

Example:

To display network protocol settings for the I/O module in I/O-module bay 3,while I/O-module bay 3 is set as the persistent command environment, at thesystem:switch[3]> prompt, typenat

The following example shows the information that is returned from this command:system:switch[3]> natIndex Protocol Name Protocol ID Internal Port External Port Enabled1 HTTP TCP 80 1080 enabled2 TELNET TCP 23 1023 enabled3 HTTPS TCP 43 1043 enabled4 SSH TCP 22 1022 enabled5 SNMP UDP 161 1161 enabledsystem:switch[3]>


ntp (network time protocol) commandThis command configures and displays the management-module network timeprotocol (NTP) settings.

Table 57. ntp command


Display managementmodule NTP settings

Displays the NTP settings for thespecified I/O module. Possiblereturn values are:v -en state (enabled, disabled)v -i ipaddress/hostname (IP address

or hostname of the NTP server)v -f update_frequency (NTP update

frequency, in minutes)v -v3en state (enabled, disabled)v -v3 key_info (NTP v3

authentication entry)

ntp -T system:mm[x]


Enable / disable NTP Enables or disables NTP for themanagement-module.

ntp -en state




-T system:mm[x]


NTP server IP address orhostname - set

Checks syntax and sets the IPaddress or hostname of the NTPserver.

ntp -i ipaddress/hostname

where ipaddress/hostname isthe IP address orhostname of the NTPserver.



-T system:mm[x]



Table 57. ntp command (continued)


NTP update frequency -set

Sets how often the managementmodule clock is automaticallyupdated by the NTP server.

ntp -f time

where time is the NTPupdate frequency, inminutes with a maximumvalue of 45000.



-T system:mm[x]


NTP - Enable / disableV3 authentication

Enables or disables V3authentication between themanagement-module and the NTPserver.Note: The NTP serverauthentication key must be set,using the ntp -v3 command option,before enabling V3 authentication.

ntp -v3en state




-T system:mm[x]


NTP serverauthentication key - set

Sets the v3 authentication key thatthe management module uses toaccess the NTP server. Theauthentication key contains thefollowing values:v Key index: An NTP server can be

configured with one or more keyentries. The key index specifieswhich key the server expects theclient to authenticate with.

v Key type: The advancedmanagement module supportsonly the MD5 key type.

v Key: The key is an 8-characterASCII string.

ntp -v3 key_index key_typekey

where:v key_index is from 1 to

65535, inclusive. If youenter a value outsidethis range, an error willbe displayed.

v key_type is M (MD5).v key is a 8-character

ASCII string.



-T system:mm[x]



Table 57. ntp command (continued)


NTP clock- synchronize Synchronizes themanagement-module clock with theNTP server. (You must configure avalid NTP server before you cansynchronize.)

ntp -synch



-T system:mm[x]


Example:

To display NTP settings for the management module, while management module 2is set as the persistent command environment, at the system:mm[2]> prompt, typentp

The following example shows the information that is returned from this command:system:mm[2]> ntp-en enabled-i timeserver-f 5-v3en disabled-v3 Not configuredNTP is disabled.system:mm[2]>


ping commandThis command tests the internal communication path between the advancedmanagement module and a BladeCenter component by sending it a ping request.

Table 58. ping command


Display I/O module IPaddresses

Displays a list of IP addresses forthe specified I/O module.

ping -i

This command can onlybe run by users who haveone or more of thefollowing commandauthorities:v Supervisor,v Operator (general

operator, not chassisoperator)

v I/O moduleadministration,

v I/O moduleconfiguration

v I/O module operator


-T system:switch[x]


Ping IP address Pings the specified IP address totest communication between it andthe management module.Note: This command testscommunication paths, including IPaddresses outside of theBladeCenter unit.

ping -i ip_address

where ip_address is the IPaddress for a componentinstalled in theBladeCenter unit.

All users can attempt toping a specific IP address.

This command willattempt to ping thespecified IP address,regardless of commandtarget, including IPaddresses outside ofthe BladeCenter unit.


Table 58. ping command (continued)


Ping I/O-module IPaddress

Pings the specified IP address of anI/O module to test communication.

ping -i index

where index is the indexnumber for theI/O-module IP address toping. Use the ping -icommand, with noarguments, to list availableIP addresses and theirindex numbers.

This command can onlybe run by users who haveone or more of thefollowing commandauthorities:v Supervisor,v Operator (general

operator, not chassisoperator)

v I/O moduleadministration,

v I/O moduleconfiguration

v I/O module operator


-T system:switch[x]


Example: To display list of IP addresses for the I/O module in bay 1, while theBladeCenter unit is set as the persistent command environment, at the system>prompt, typeping -i -T switch[1]

To ping the first IP address of the I/O module in bay 1 using an index number,while the BladeCenter unit is set as the persistent command environment, at thesystem> prompt, typeping -i 1 -T switch[1]

To ping the first IP address of the I/O module in bay 1 using an IP address, whilethe BladeCenter unit is set as the persistent command environment, at the system>prompt, typeping -i 10.13.3.171


The following example shows the information that is returned from thesecommands:system> ping -i -T switch[1]1. 10.13.3.1712. FE80:0000:0000:0000:0218:B1FF:FE9F:9000system> ping -i 1 -T switch[1]Reply from 10.13.3.171: bytes=64 time=4.150msReply from 10.13.3.171: bytes=64 time=0.392msReply from 10.13.3.171: bytes=64 time=0.400msReply from 10.13.3.171: bytes=64 time=0.389mssystem> ping -i 10.13.3.171Reply from 10.13.3.171: bytes=64 time=0.418msReply from 10.13.3.171: bytes=64 time=0.417msReply from 10.13.3.171: bytes=64 time=0.362msReply from 10.13.3.171: bytes=64 time=6.90mssystem>


pmpolicy commandThis command displays and sets the power management policies for theBladeCenter unit.

Table 59. pmpolicy command


Display powermanagement policy

Displays the current powermanagement policy for alldomains.

pmpolicy -T system

Display powermanagement policy for aBladeCenter S unit

Displays both the current andavailable power managementpolicies for a BladeCenter S unit,that has a single power domain.

pmpolicy domain

where domain is pd

-T system

Display powermanagement policy fordomain

Displays both the current andavailable power managementpolicies for the specified powerdomain in a BladeCenter unit thatsupports two power domains.

pmpolicy domain

where domain is:v pd1 (power domain 1)v pd2 (power domain 2)

-T system

Set power managementpolicy for domain

Set power management policy forspecified power domain.

pmpolicy domain -pm policy

where domain is:v pd1 (power domain 1)v pd2 (power domain 2)

where policy is:v acred (ac power source

redundancy policy -BladeCenter S unitsonly)

v acredov (ac powersource redundancypolicy, with bladethrottling - BladeCenterS units only)

v redwoperf (powermodule redundancy, nooversubscription)

v redwperf (powermodule redundancywith power throttling)

v nonred (no powermanagement policy)



-T system


Example:

To view the current policy and the available policies for a power domain 1, whilethe BladeCenter unit is set as the persistent command environment, at the system>prompt, type

pmpolicy pd1

The following example shows the output generated by this command.system> pmpolicy pd1

Power Domain 1--------------

*** Current Policy ***

Power Management Policy:Power Module Redundancy with Blade Throttling Allowed (redwperf)

Description:Very similar to Power Module Redundancy. This policy allows you todraw more total power; however, capable blades may be allowed tothrottle down if one Power Module fails.

Power Supply Failure Limit: 1Maximum Power Limit (Watts): 3380Your Estimated Utilization: 5%

*** Available Policies ***

Power Management Policy:Power Module Redundancy (redwoperf)

Description:Intended for a single AC power source into the chassis where eachPower Module is on its own dedicated circuit. Total allowed powerdraw is limited to one less than the number of Power Modules whenmore than one Power Module is present. One Power Module can failwithout affecting blade operation. Multiple Power Module failures cancause the chassis to power off. Note that some blades may not beallowed to power on if doing so would exceed the policy power limit.


Power Management Policy:Basic Power Management (nonred)

Description:Total allowed power is higher than other policies and is limited onlyby the total power capacity of all the Power Modules up to themaximum of chassis power rating. This is the least conservativeapproach, since it does not provide any protection for AC powersource or Power Module failure. If any single power supply fails,blade and/or chassis operation may be affected.


NOTE:Power Supply Failure Limit: This is the maximum number of power supplies

that can fail while still guaranteeing theoperation of the domain in the selected policy.

Your Estimated Utilization: The estimated utilization is based on the maximumpower limit allowed in this policy and the currentaggregated power in use of all components in thedomain.

system>


portcfg commandThis command configures and displays the settings for the advancedmanagement-module serial port.

Table 60. portcfg command


Displaymanagement-moduleserial port configuration

Displays the current configurationof the management-module serialport. Possible return values are:v -b baud_ratev -p parityv -s stop_bits

portcfg -com1 -T system:mm[x]


Set management-moduleserial port baud rate

Checks syntax and sets the baud(communications) rate of themanagement-module serial port.

portcfg -com1 -bbaud_rate

where baud_rate is 2400,4800, 9600, 19200, 38400,or 57600.



-T system:mm[x]


Set management-moduleserial port parity

Checks syntax and sets the parityof the management-module serialport.

portcfg -com1 -p parity

where parity isv nonev oddv evenv markv space



-T system:mm[x]



Table 60. portcfg command (continued)


Set management-moduleserial port stop bits

Checks syntax and sets the numberof stop bits for themanagement-module serial port.

portcfg -com1 -s stop_bits

where stop_bits is 1 or 2.



-T system:mm[x]


Example:

To display the configuration for the management-module serial port, whilemanagement module 1 is set as the persistent command environment, at thesystem:mm[1]> prompt, typeportcfg -com1

To set the baud rate for the management-module serial port to 9600, whilemanagement module 1 is set as the persistent command environment, at thesystem:mm[1]> prompt, typeportcfg -com1 -b 9600

The following example shows the information that is returned from these twocommands:system:mm[1]> portcfg -com1-b 2400-p none-s 1system:mm[1]> portcfg -com1 -b 9600These configuration changes will become active after the next reset of the MM.system:mm[1]>


ports commandThis command sets and displays the network port configuration settings for theadvanced management module.

Note: Changes to the -ftpdp, -ftpe, -ftpp, -httpp, -httpsp, -rpp, -smashse,-smashsp, -smashte, -smashtp, -snmp1ae, -snmp3ae, -snmpap, -snmpte, -snmptp,-sshe, -sshp, -tcme, -telnete, -telnetp, -telnett, or -tftpp settings become activeimmediately. Changes to the remaining settings become active after the next resetof the advanced management module.

Table 61. ports command


Display network portsettings

Displays the network port settingsfor the management module.Returned values are:v -ftpp FTP_prt_numv -ftpdp FTP_data_prt_numv -httpp HTTP_prt_numv -httpsp HTTPS_prt_numv -rpp rpp_prt_numv -slpp SLP_prt_numv -smashsp

secSMASH_SSH_prt_numv -smashtp SMASH_telnet_prt_numv -snmpap SNMP_agent_prt_numv -snmptp SNMP_traps_prt_numv -sshp SSH_prt_numv -stcmp secure_tcmpv -tcmp TCP_cmd_md_portv -telnetp _Telnet_prt_numv -tftpp TFTP_prt_numv -ftpe FTP_statev -httpse HTTPS_prt_statev -kvme KVM_statev -ntpe NTP_statev -rde rd_statev -rdoce rdoc_statev -slpe SLP_state.v -smashse sec_SMASH_SSH_statev -smashte SMASH_telnet_statev -snmp1ae SNMPv1_agent_statev -snmp3ae SNMPv3_agent_statev -snmpte SNMP_traps_statev -sshe SSH_prt_statev -stcme secure_TCP_cmd_modev -tcme TCP_cmd_mode_statev -telnete Telnet_prt_state-v -tftpe TFTP_statev -ftpt FTP_timeoutv -tcmt TCP_cmd_mode_timeoutv -telnett Telnet_prt_timeout

ports -T system:mm[x]


Display openmanagement moduleports

Displays the management moduleports that are currently open.

ports -open -T system:mm[x]



Table 61. ports command (continued)


Reset network portsettings

Resets all network port settings forthe management module to thedefault values. Default values are:v -ftpp: 21v -ftpdp: 20v -httpp: 80v -httpsp: 443v -rpp: 3900v -slpp: 427v -tcmp: 6090v -smashtp: 50023v -smashsp: 50022v -snmpap: 161v -snmptp: 162v -sshp: 22v -stcmp: 6091v -telnetp: 23v -tftpp: 69

ports -reset



-T system:mm[x]


Set FTP port number Sets the port number for themanagement module FTP port.

ports -ftpp FTP_prt_num

where FTP_prt_num isfrom 1 to 65535, inclusive.If you enter a valueoutside this range, anerror will be displayed.



-T system:mm[x]


Set FTP data portnumber

Sets the port number for themanagement module FTP dataport.

ports -ftpdpFTP_data_prt_num

where FTP_data_prt_numis from 1 to 65535,inclusive. If you enter avalue outside this range,an error will be displayed.



-T system:mm[x]





Set HTTP port number Sets the port number for themanagement module HTTP port.

ports -httppHTTP_prt_num

where HTTP_prt_num isfrom 1 to 65535, inclusive.If you enter a valueoutside this range, anerror will be displayed.



-T system:mm[x]


Set HTTPS port number Sets the port number for themanagement module HTTPS port.

ports -httpspHTTPS_prt_num

where HTTPS_prt_num isfrom 1 to 65535, inclusive.If you enter a valueoutside this range, anerror will be displayed.



-T system:mm[x]


Set Remote Presenceport number

Sets the remote presence portnumber for the managementmodule remote presence port.

ports -rpp rpp_prt_num

where rpp_prt_num is from1 to 65535, inclusive. Ifyou enter a value outsidethis range, an error will bedisplayed.



-T system:mm[x]





Set SLP port number Sets the SLP port number. ports -slpp SLP_prt_num

where SLP_prt_num isfrom 1 to 65535, inclusive.If you enter a valueoutside this range, anerror will be displayed.



-T system:mm[x]


Set SMASH Telnet portnumber

Sets the port number for themanagement module SMASHcommand-line processor overTelnet port.

ports -smashtpSMASH_telnet_prt_num

whereSMASH_telnet_prt_num isfrom 1 to 65535, inclusive.If you enter a valueoutside this range, anerror will be displayed.



-T system:mm[x]





Set SNMP agent portnumber

Sets the port number for themanagement module SNMP agentport.

ports -snmpapSNMP_agent_prt_num

whereSNMP_agent_prt_num isfrom 1 to 65535, inclusive.If you enter a valueoutside this range, anerror will be displayed.



-T system:mm[x]


Set SNMP traps portnumber

Sets the port number for themanagement module SNMP trapsport.

ports -snmptpSNMP_traps_prt_num

whereSNMP_traps_prt_num isfrom 1 to 65535, inclusive.If you enter a valueoutside this range, anerror will be displayed.



-T system:mm[x]





Set command mode portnumber

Sets the TCP command mode portnumber.

ports -tcmpTCP_cmd_md_prt_num

whereTCP_cmd_md_prt_num isfrom 1 to 65535, inclusive.If you enter a valueoutside this range, anerror will be displayed.



-T system:mm[x]


Set secure commandmode port number

Sets the secure TCP commandmode port number.

ports -stcmp secure_tcmp

where secure_tcmp is from1 to 65535, inclusive. Ifyou enter a value outsidethis range, an error will bedisplayed.



-T system:mm[x]


Set SSH port number Sets the port number for themanagement module SSH port.

ports -sshp SSH_prt_num

where SSH_prt_num isfrom 1 to 65535, inclusive.If you enter a valueoutside this range, anerror will be displayed.



-T system:mm[x]





Set Telnet port number Sets the port number for themanagement module Telnet port.

ports -telnetpTelnet_prt_num

where Telnet_prt_num isfrom 1 to 65535, inclusive.If you enter a valueoutside this range, anerror will be displayed.



-T system:mm[x]


Set TFTP port number Sets the port number for themanagement module TFTP port.

ports -tftppTFTP_prt_num

where TFTP_prt_num isfrom 1 to 65535, inclusive.If you enter a valueoutside this range, anerror will be displayed.



-T system:mm[x]


Enable / disable FTP Enables or disables FTP for themanagement module.

ports -ftpe state




-T system:mm[x]





Enable / disable HTTPSport

Enables or disables themanagement module HTTPS port.

ports -httpse state




-T system:mm[x]


Set KVM port state Sets the KVM port state to on oroff.

ports -kvme state




-T system:mm[x]


Enable / disable NTP Enables or disables NTP for themanagement module.

ports -ntpe state




-T system:mm[x]





Enable / disable RDE Enables or disables remote disk forthe management module.

ports -rde state




-T system:mm[x]


Enable / disable RDOCE Enables or disables remote disk oncard for the management module.

ports -rdoce state




-T system:mm[x]


Enable / disables SLP Enables or disables SLP for themanagement module.

ports -slpe state




-T system:mm[x]





Enable / disable secureSMASH over SSH

Enables or disables the secureSMASH command-line processorover SSH for the managementmodule.

ports -smashse state




-T system:mm[x]


Enable / disable SMASHover Telnet

Enables or disables SMASHcommand-line processor overTelnet for the management module.

ports -smashte state




-T system:mm[x]


Enable / disableSNMPv1 agent

Enables or disables the SNMPv1agent for the management module.

ports -snmp1ae state




-T system:mm[x]





Enable / disableSNMPv3 agent

Enables or disables the SNMPv3agent for the management module.

ports -snmp3ae state




-T system:mm[x]


Enable / disable SNMPtraps

Enables or disables the SNMP trapsfor the management module.

ports -snmpte state




-T system:mm[x]


Enable / disable SSHport

Enables or disables themanagement module SSH port.

ports -sshe state




-T system:mm[x]





Enable / disable TCPcommand mode

Enables or disables the TCPcommand mode for themanagement module.

ports -tcme state




-T system:mm[x]


Set number of TCPcommand modeconnections

Turns the TCP command mode onor off, or sets the maximumnumber of connections explicitly.Note: Any number of connections(1 through 20) displays a status ofon. Zero connections displays astatus of off.

ports -tcme port_mode

where port_mode is on (1connection), off (noconnections), or a numberbetween 0 and 20,inclusive, that indicatesthe maximum number ofTCP session connections.



-T system:mm[x]


Enable / disable secureTCP command mode

Enables or disables the secure TCPcommand mode for themanagement module.

ports -stcme state




-T system:mm[x]





Set number of secureTCP command modeconnections

Turns the secure TCP commandmode on or off, or sets themaximum number of connections.Notes:v On a write operation, the

maximum number ofconnections can be set explicitly(0-20), or it can be turned on (1connection) or off (0connections).

v On a read operation, off means 0connections, and on means 1 ormore connections.

v The total session count of TCMand STCM is limited to 20.

ports -stcme port_mode

where port_mode is on (1connection), off (noconnections), or a numberbetween 0 and 20,inclusive, that indicatesthe maximum number ofTCP session connections.



-T system:mm[x]


Enable / disable Telnetport

Enables or disables themanagement module Telnet port.

ports -telnete state




-T system:mm[x]


Enable / disable TFTP Enables or disables TFTP for themanagement module.

ports -tftpe state




-T system:mm[x]





Set FTP timeout Sets the FTP timeout value for themanagement module.

ports -ftpt timeout

where timeout is from 0seconds (no timeout) to4294295967 seconds,inclusive.



-T system:mm[x]


Set TCP command-modetimeout

Sets the TCP command-modetimeout value for the managementmodule.

ports -tcmt timeout




-T system:mm[x]


Set Telnet port timeout Sets the Telnet port timeout valuefor the management module.

ports -telnett timeout




-T system:mm[x]





Display network portsettings for I/O module

Displays the network port settingsfor the I/O module. These settingscan include:v cable compatibilityv cable lengthv cable typev data ratev labelv port indexv port mediav port widthv protocolv speedv speed settingv available speedsv statev state settingv typev vendor

Note: Other device specific valuesmight be returned.

ports -T system:switch[x]


Enable or disable portfor I/O module

Enables or disables specified porton specified I/O module.

ports -port_index -statestate

wherev port_index is from 1 to

65535, inclusive.v state is on or off.


configuration


-T system:switch[x]

where x is the I/Omodule bay number.




Sets speed of port forI/O module

Sets speed of specified port on I/Omodules that support this feature.

ports -port_index -speedspeed_setting

wherev port_index is from 1 to

65535, inclusive.v speed_setting specifies

the port speed, in termsof:– multiplier– units, m or g for

megabits or gigabits– duplex mode, h or f

for half or full

For example, 100mh setsthe port speed to 100Mbps half-duplex.


configuration


-T system:switch[x]


Example:

To display the management module network port settings, while managementmodule 1 is set as the persistent command environment, at the system:mm[1]>prompt, typeports

To disable FTP for the management module, while management module 1 is set asthe persistent command environment, at the system:mm[1]> prompt, typeports -ftpe off

The following example shows the information that is returned from these twocommands:system:mm[1]> ports-ftpp 21-ftpdp 20-httpp 80-httpsp 443-rpp 3900-slpp 427-smashsp 50022-smashtp 50023-snmpap 161-snmptp 162-sshp 22


-stcmp 6091-tcmp 6090-telnetp 23-tftpp 69-ftpe on-httpse off-kvme on-ntpe off-rde off-rdoce on-slpe on-smashse on-smashte on-snmp1ae on-snmp3ae on-snmpte on-sshe off-stcme off-tcme off-telnete on-tftpe off-tcmt 0-telnett 10000-ftpt 300system:mm[1]> ports -ftpe offChanges to -sshe, -sshp, -smashse, -smashte, -smashsp, -telnete, -telnetp,-telnett, -smashtp, -snmpte, -tcme, -tcmp, -tcmt, -stcme, -stcmp, -rpp,-httpp,-httpse, -httpsp, -ftpe or -tftpe will become active immediately.OKsystem>


power commandThis command turns on and turns off blade servers and I/O modules. Foradvanced management modules installed in BladeCenter HT units, it also turns onand turns off the alarm panel module and network clock module.

Table 62. power command


Power on Turns on the specified commandtarget.

power -on


(for blade server)v I/O module

administration (for I/Omodule)


-T system:blade[x]

-T system:switch[x]

-T system:tap(BladeCenter HT unitsonly)

-T system:ncc[x](BladeCenter HT unitsonly)

where x is the bladeserver, I/O-modulebay, or network clockmodule number.

Power on to commandconsole

Opens a command console with anSOL session when the specifiedblade server is turned on.

power -on -c




-T system:blade[x]


Power off Turns off the specified commandtarget.

power -off





-T system:blade[x]

-T system:switch[x]

-T system:tap(BladeCenter HT unitsonly)

-T system:ncc[x](BladeCenter HT unitsonly)

where x is the bladeserver, I/O-modulebay, or network clockmodule number.


Table 62. power command (continued)


Shutdown and poweroff blade server

Shuts down the operating systemand turns off the specified bladeserver.

power -softoff



-T system:blade[x]


Power cycle Cycles power for the specifiedblade server or I/O module. If theblade server or I/O module is off,it will turn on. If the blade serveror I/O module is on, it will turnoff and then turn on.

power -cycle





-T system:blade[x]

-T system:switch[x]

where x is the bladeserver or I/O-modulebay number.

Power cycle to commandconsole

Cycles power for the specifiedblade server. If the blade server isoff, it opens a command consolewith an SOL session when it isturned on. If the blade server is on,it will turn off and then turn on.

power -cycle -c




-T system:blade[x]


Display power state Displays the current power statefor the specified blade server orI/O module. Possible return valuesare off, on, standby, or hibernate.

power -state -T system:blade[x]

-T system:switch[x]





Enable / disable Wakeon LAN globally

Enables or disables Wake on LANglobally for all blade servers.

power -wol state




-T system

Enable / disable Wakeon LAN for blade server

Enables or disables Wake on LANfor the specified blade server.

power -wol state




-T system:blade[x]


Enable / disable localpower control globally

Enables or disables local powercontrol globally for all bladeservers.

power -local state




-T system




Enable / disable localpower control for bladeserver

Enables local power control for thespecified blade server.

power -local state




-T system:blade[x]


Set automatic power-onpolicy for BladeCenterunit

Sets the automatic power-on policyfor the BladeCenter unit.

Changes to the power-on policysetting take effect after the nextcold start of the BladeCenter unit.

power -ap policy

where policy is:v restore: all blade

servers that werepreviously on will bepowered on

v auto: when power isapplied to theBladeCenter unit, allblade servers will bepowered on

v manual: all blade serverswill remain off untilmanually powered on



-T system

Display fast POSTsetting for I/O module

Displays the current fast POSTsetting for specified I/O module.Note: This target works only forsome I/O modules.

power -T system:switch[x]





Enable / disable fastPOST for I/O module

Enables or disables fast POSTglobally for the specified I/Omodule.Note: This option works only forsome I/O modules.

power -fp state



administration


-T system:switch[x]


Display POST status forI/O module

Displays the POST status for thespecified I/O module. If thecommand is run while POST is inprogress, it returns the level ofPOST that is currently in process. Ifthe command is run after POST iscomplete, it displays one of thefollowing return values:v The POST results could not be

read. message displays if therewas an internal error duringPOST.

v The POST results not complete:hex_code message displays ifPOST results are not availableafter POST completes.

v If POST returns valid results, oneof the following messagesdisplays:– hex_code: Base internal

function failure detected.– hex_code: Internal

interface failure detected.– hex_code: External

interface failure detected.– hex_code: Module completed

POST successfully.– hex_code: Cannot decode

POST result code.v The Invalid POST results.

message displays if none of theabove conditions is true.

Where hex_code is a hexadecimalcode. See the documentation thatcomes with your I/O module forinformation.Note: This command option is notsupported for serial concentratorI/O modules.

power -state -post -T system:switch[x]



Example:

To display the power state for the blade server in blade bay 5, while this bladeserver is set as the persistent command environment, at the system:blade[5]>prompt, typepower -state

To turn on the blade server in blade bay 5, while this blade server is set as thepersistent command environment, at the system:blade[5]> prompt, typepower -on

To display the power state for the blade server in blade bay 5 again, while thisblade server is set as the persistent command environment, at thesystem:blade[5]> prompt, typepower -state

The following example shows the information that is returned from these threecommands:system:blade[5]> power -stateOffsystem:blade[5]> power -onOKsystem:blade[5]> power -stateOnsystem:blade[5]>


rdoc commandThis command displays volume information for remote disk-on-card local storageon the advanced management module. The command also allows you to mount,unmount, or map a file image to this device.

Table 63. rdoc command


Display advancedmanagement modulevolume information

Displays the remote disk-on-cardvolume information for localstorage on the advancedmanagement module. Volumeinformation returned includes:v Health conditionv Sizev Amount of free space

rdoc -T system:mm[x]

where x is the primarymanagement modulebay number.

Map file as advancedmanagement modulevolume image

Maps the specified file as the activeimage for the remote disk-on-cardlocal storage volume on theadvanced management module.

rdoc -map filename

where filename is the nameof the file to be mapped asthe active remotedisk-on-card image.



-T system:mm[x]


Mount advancedmanagement modulevolume

Mounts the remote disk-on-cardlocal storage volume on theadvanced management module.Note: The advanced managementmodule will only mount the firstpartition, if the volume hasmultiple partitions.

rdoc -mount



-T system:mm[x]


Unmount advancedmanagement modulevolume

Unmounts the remote disk-on-cardlocal storage volume on theadvanced management module.

rdoc -unmount



-T system:mm[x]



Example: To display volume information for local storage on the advancedmanagement module in bay 1, while this management module is set as thepersistent command environment, at the system:mm[1]> prompt, typerdoc

The following example shows the information that is returned from this command:system:mm[1]> rdocVolume 0Health: goodVolume Size: 73108480 (Bytes)Free Size: 69120000 (Bytes)system:mm[1]>


read commandThis command restores the management-module configuration that was previouslysaved to the BladeCenter unit chassis or to a file.

Configurations are saved to the BladeCenter unit chassis or to a file using the“write command” on page 401.

Table 64. read command


Displaymanagement-moduleautomatic configurationsetting

Displays the automaticconfiguration setting (-autocommand option) of themanagement module.

read -T system:mm[x]


Restoremanagement-moduleconfiguration fromBladeCenter unitmidplane

Restores the management-moduleconfiguration from an image thatwas previously saved to theBladeCenter unit midplane.

read -config chassis



-T system:mm[x]


Restoremanagement-moduleconfiguration from file(no encryption)

Restores the management-moduleconfiguration from an image thatwas previously saved to a filewhile data encryption was notenabled for the BladeCenter unit.

read -config file -lfilename -i ip_address






-T system:mm[x]



Table 64. read command (continued)


Restoremanagement-moduleconfiguration from file(encryption)

Restores the management-moduleconfiguration from an image thatwas previously saved to a filewhile data encryption was enabledfor the BladeCenter unit.Note: When a configuration filewas created with a pass-phrase(encryption enabled), if thisconfiguration file is restored on thesame management module, thepass-phrase entered duringrestoration is ignored.

read -config file -lfilename -i ip_address -ppassphrase




v "passphrase" is thequote-delimitedpass-phrase that wasused to save theoriginal configurationfile. Maximumpass-phrase length is1600 characters.



-T system:mm[x]


Enable automaticmanagement-moduleconfiguration

Enables automatic configuration ofthe management module, based onsettings stored in the BladeCenterunit midplane, when themanagement module is installed.Note: The -auto option can only beused when themanagement-module configurationwas stored to the BladeCenter unitmidplane.

read -config chassis-auto on



-T system:mm[x]



Table 64. read command (continued)


Disable automaticmanagement-moduleconfiguration

Disables automatic configuration ofthe management module, based onsettings stored in the BladeCenterunit midplane, when themanagement module is installed.

read -config chassis-auto off



-T system:mm[x]


Example:

To restore the management-module configuration from an image previously savedto the BladeCenter unit chassis, while management module 1 is set as thepersistent command environment, at the system:mm[1]> prompt, typeread -config chassis

The following example shows the information that is returned from this command:system:mm[1]> read -config chassisOKConfiguration restore from the chassis was successfulRestart the MM for the new settings to take effectsystem:mm[1]>


remotechassis commandThis command displays and manages the list of BladeCenter units that themanagement module discovers on the network.

Note: The advanced management module that runs the remotechassis command isalso included in all lists.

Table 65. remotechassis command


Display complete list Displays a list of all BladeCenterunits that the management modulediscovers on the network. The listincludes the following informationabout each BladeCenter unit:v Namev IP addressv Statusv Firmware levelv Typev Serial numberv FRU numberv Chassis serial numberv Chassis FRU numberv Chassis machine-type model

(MTM)v Chassis UUID

remotechassis -T system:mm[x]


Display list grouped byhealth status

Displays a list of names forBladeCenter units that themanagement module discovers onthe network. The list is grouped byhealth status.

remotechassis -health -T system:mm[x]


Display list filtered byIP address

Displays a list of BladeCenter unitsthat the management modulediscovers on the network, filteredby the specified IP address. The listincludes the following informationabout each BladeCenter unit:v Namev IP addressv Statusv Firmware levelv Typev Serial numberv FRU numberv Chassis serial numberv Chassis FRU numberv Chassis machine-type model

(MTM)v Chassis UUID

remotechassis -ipip_address

where ip_address is an IPaddress pattern that usesthe asterisk (*) as awildcard (for example;201.47.123.*).

-T system:mm[x]



Table 65. remotechassis command (continued)


Display list filtered byname

Displays a list of BladeCenter unitsthat the management modulediscovers on the network, filteredby the specified name. The listincludes the following informationabout each BladeCenter unit:v Namev IP addressv Statusv Firmware levelv Typev Serial numberv FRU numberv Chassis serial numberv Chassis FRU numberv Chassis machine-type model

(MTM)v Chassis UUID

remotechassis -name name

where name is a namepattern that uses theasterisk (*) as a wildcard(for example; WebServer*).

-T system:mm[x]


Clear list Clears the list of BladeCenter unitsthat the management modulediscovered on the network.

remotechassis -clear -T system:mm[x]


Example:

To list all BladeCenter units on the network with a name starting with"WebServer", while management module 1, that does not support IPv6, is set as thepersistent command environment, at the system:mm[1]> prompt, typeremotechassis -name WebServer*

The following example shows the information that is returned from this command:system:mm[1]> remotechassis -name WebServer*Running chassis discovery...------------------------------------------------Name: WebServer001IP: 145.48.204.212Status: normalFirmware: BPET25L,CNETMNUS.PKT,01-08-07,37,1Type: management-moduleSerial: 0J1M9E585630FRU: 25R5777Chassis Serial: 23A2343Chassis FRU: 25R5780R5780Chassis MTM: 885222ZChassis UUID: 4E349451FA8011D9B10C89E0183AD13D------------------------------------------------Name: WebServer002IP: 145.48.204.222Status: normalFirmware: BPET25L,CNETMNUS.PKT,01-08-07,37,1Type: management-moduleSerial: 0J1M9E585656FRU: 25R5777Chassis Serial: 23A2356Chassis FRU: 25R5780R5780


Chassis MTM: 885222ZChassis UUID: 4E325951FA8011D9B86C89E0183AD02D------------------------------------------------system:mm[1]>

To list all BladeCenter units on the network with a name starting with "SYSTEM*",while management module 1, that supports IPv6, is set as the persistent commandenvironment, at the system:mm[1]> prompt, typeremotechassis -name SYSTEM*

The following example shows the information that is returned from this command:system:mm[1]> remotechassis -name SYSTEM*Running chassis discovery...------------------------------------------------Name: SYSTEMIP: 10.13.1.190IPv6: 2002:1013::211:25ff:fec3:227c

2001:1013::211:25ff:fec3:227c2000:1013::211:25ff:fec3:227cfe80::211:25ff:fec3:227c2000:1013::a1be:a348:7672:2def2000:1013::1:191

Status: criticalFirmware: BPET002,CNETMNUS.PKT,02-17-10,1Type: management-moduleSerial: YK118165A117FRU: 39Y9661Chassis Serial: KQWPLB9Chassis FRU: 44X2302Chassis MTM: 8852HC1Chassis UUID: E13112E1829448E29999DA2066681D89------------------------------------------------Name: SYSTEMIP: 10.13.1.30IPv6: 2000:1013::fc58:325c:c8b4:9c4c

2000:1013::214:5eff:fed0:2e1c2000:1013::1:30fe80::5652:ff:fe69:d7632002:1013::211:25ff:fec3:8cfa2001:1013::211:25ff:fec3:8cfa2000:1013::211:25ff:fec3:8cfafe80::211:25ff:fec3:8cfa

Status: attentionFirmware: BPET54A,CNETMNUS.PKT,02-17-10,84Type: management-module-telcoSerial: YK118269Y115FRU: 39Y9661Chassis Serial: 23A0052Chassis FRU: 42C3673Chassis MTM: 87501RZChassis UUID: B5BAEC01A10B11DB9F3BC1BE8FFF3B3C------------------------------------------------system:mm[1]>


reset commandThis command resets blade servers, blade server integrated system managementprocessors (service processors), I/O modules, or the primary management module.For advanced management modules installed in BladeCenter HT units, it alsoresets the multiplexer expansion module.

Table 66. reset command


Reset Performs an immediate reset andrestart of the specified device.

reset


(for blade server orblade server ISMP)

v I/O moduleadministration (for I/Omodule)


-T system:blade[x]

-T system:switch[x]



Reset primarymanagement module

Performs an immediate reset andrestart of the primary managementmodule.

reset



-T system:mm[x]


Reset standbymanagement module

Performs an immediate reset of thestandby management module.Note: This option does not applyto the BladeCenter S unit.

reset -standby



-T system:mm[x]

where x is the primarymanagement-modulebay number.Note: Even thoughthis command resetsthe standbymanagement module,it still must specify theprimary managementmodule as thecommand target.


Table 66. reset command (continued)


Reset blade server tocommand console

Opens a command console with anSOL session when the specifiedblade server is reset.

reset -c




-T system:blade[x]


Reset with failover Resets the specified commandtarget, enabling failover if aredundant (stanfdby) componentfor the command target is present.

An error message is displayed ifyou try to failover a managementmodule when a standbymanagement module is notinstalled or if the firmware in theone of the management modules isupdating.Note: This option does not applyto the BladeCenter S unit.

reset -f



-T system:mm[x]

-T system:mux[x] (foradvanced managementmodules inBladeCenter HT unitsonly)

where x is the primarymanagement-modulebay or multiplexerexpansion modulenumber.

Reset managementmodule with forcedfailover

Resets the primary managementmodule with failover to thestandby management module.

An error message is displayed ifyou try to force failover for amanagement module when astandby management module is notinstalled or if the firmware in theprimary management module isupdating.Note: This option does not applyto the BladeCenter S unit.

reset -force



-T system:mm[x]


Reset I/O module withstandard diagnostics

Performs an immediate reset andrestart of the specified device,running standard diagnostics onthe I/O module after it restarts.

Running the reset -std commandgives the same result as runningthe reset command on a I/Omodule.

reset -std


administration


-T system:switch[x]





Reset I/O module withextended diagnostics

Performs an immediate reset andrestart of the specified device,running extended diagnostics onthe I/O module after it restarts.

reset -exd


administration


-T system:switch[x]


Reset I/O module withfull diagnostics

Performs an immediate reset andrestart of the specified device,running full diagnostics on the I/Omodule after it restarts.

reset -full


administration


-T system:switch[x]


Restart blade server withNMI

Performs an immediate reset andrestart of the specified blade server.Command results depend on theblade server model that isspecified:v For a JS12 or JS22 blade server,

this option is not available.v For a JS20 blade server, the

command performs animmediate reset and restart ofthe specified blade server withnon-maskable interrupt (NMI).

v For all other blade servers, thecommand performs animmediate reset and restart ofthe specified blade server.

reset -sft




-T system:blade[x]





Restart blade server andclear NVRAM



command performs animmediate reset and restart ofthe specified JS20 blade serverand clears all settings stored innon-volatile memory (NVRAM).


reset -clr




-T system:blade[x]


Restart blade server andrun diagnostics



command performs animmediate reset and restart ofthe specified JS20 blade serverand runs diagnostics.


reset -dg




-T system:blade[x]


Restart blade server andrun diagnostics usingdefault boot sequence



command performs animmediate reset and restart ofthe specified JS20 blade serverand runs diagnostics using thedefault boot sequence configuredfor the blade server.


reset -ddg




-T system:blade[x]





Restart blade server andenter SMS menu

Performs an immediate reset andrestart of the specified blade serverand enters the System ManagementServices (SMS) firmware menu.Note: This option applies to allJSxx blade servers other than theJS20 blade server.

reset -sms



-T system:blade[x]


Example: To reset the service processor on the blade server in blade bay 5, whilethe BladeCenter unit is set as the persistent command environment, at the system>prompt, typereset

The following example shows the information that is returned:system> reset -T blade[5]:spOKsystem>


scale commandThis command sets and displays the partition control and configuration settings formultiple blade servers or nodes in a scalable complex, for blade servers installed inthe BladeCenter unit that support this feature.

Note:

v The scale command will execute only on blade servers that support scalablecomplexes.

v All blade servers in a scalable complex must be at the same firmware level.When scripting firmware updates for blade servers in a scalable complex, makesure that the update commands are included for each node in the complex.

Table 67. scale command


Display all scalablecomplex information

Displays all scalable complexinformation for the BladeCenterunit.

scale -T system

Display information forspecific scalable complex

Displays information for thespecified scalable complex.Note:v The complex_id is found by

running the scale commandwith no options.

v The -compid command option isrequired for only blade-serversystems that can have multiplescalable complexes defined in thesame BladeCenter unit. Thisoption does not need to bespecified for stand-alone systems.

scale -compid complex_id

where complex_id is aunique complex identifier(hexadecimal string offour alphanumericcharacters), assigned bythe blade complex.

-T system

Display information forspecific node in ascalable complex

Displays information for a specificnode in the scalable complex.Note:v The complex_id and node_id are

found by running the scalecommand with no options.


scale -node node_id-compid complex_id

where :v node_id is the checksum

or blade server baynumber, of the node.

v complex_id is a uniquecomplex identifier(hexadecimal string offour alphanumericcharacters), assigned bythe blade complex.

-T system

Display information forspecific partition in ascalable complex

Displays information for a specificnode in the scalable complex.Note:v The complex_id and partition_id

are found by running the scalecommand with no options.


scale -compid complex_id-partition partition_id

where :v complex_id is a unique

complex identifier(hexadecimal string offour alphanumericcharacters), assigned bythe blade complex.

v partition_id is a partitionidentifier, assigned bythe blade complex.

-T system


Table 67. scale command (continued)


Automatically createpartition in scalablecomplex

Automatically creates a partition inthe scalable complex.Note:v Creating a partition with nodes

(blade servers) that are enabledfor Blade Open Fabric Manager(BOFM) might cause loss ofports configured for Open FabricManager.

v The complex_id is found byrunning the scale commandwith no options.


scale -auto -compidcomplex_id

where complex_id is aunique complex identifier(hexadecimal string offour alphanumericcharacters), assigned bythe blade complex



-T system

Automatically createstand-alone partition inscalable complex

Automatically creates a stand-alonepartition in the scalable complex.Single blade servers set up as astand-alone partition will performconsistently if they are installed inanother BladeCenter unit.Note:v Creating a partition with nodes


v The complex_id andpri_node_chksum are found byrunning the scale commandwith no options.


scale -autopri_node_chksum -compidcomplex_id

where :v pri_node_chksum is a

checksum that identifiesthe node where thepartition is to becreated.




-T system




Create stand-alonepartition in scalablecomplex

Creates stand-alone partitions forspecified blade servers or nodes inthe scalable complex. Single bladeservers set up as a stand-alonepartition will perform consistentlyif they are installed in anotherBladeCenter unit.Note:v Creating a partition with nodes


v The comma-separated-valueformat of this command isprimarily used to createstand-alone partitions, sincethese systems are not contiguouslike blade-server systems. Forblade-server systems, thecommand can accept acomma-separated-value list ofblade server bay numbers, butthese bay numbers must becontiguous.

v The checksums, blade server baynumbers and complex_id arefound by running the scalecommand with no options.

v The namespace for a nodechecksum and blade server baynumber should not overlap.


scale -create id_x,id_y-compid complex_id

where:v id_x and id_y are

checksums or bladeserver bay numbers,separated by commas,that identify the nodewhere the partition is tobe created. The list cancontain one or morecomma-separatedvalues. Both checksumsand bay numbers canbe used in the same list.




-T system




Create partition inscalable complex

Creates partitions for specifiedblade servers in the scalablecomplex.Note:v Creating a partition with nodes


v For blade-server systems, acontiguous range of blade-serverbays can be specified.

v The blade server bay numbersand complex_id are found byrunning the scale commandwith no options.


scale -createstart_bay-end_bay -compidcomplex_id

where:v start_bay and end_bay

are blade server baynumbers, separated by ahyphen, that identifythe range of bladeserver bays wherepartitions are to becreated. The range cancontain a single baynumber.




-T system

Delete all partitionsfrom scalable complex

Deletes all partitions in the scalablecomplex.Note:v All partitions must be powered

off to delete them.v The blade server bay numbers

and complex_id are found byrunning the scale commandwith no options.


scale -delete -compidcomplex_id

where complex_id is aunique complex identifier(hexadecimal string offour alphanumericcharacters), assigned bythe blade complex.



-T system




Delete partition fromscalable complex

Deletes a specific partition in thescalable complex.Note:v A partition must be powered off

to delete it.v The complex_id and partition_id



scale -delete -compidcomplex_id -partidpartition_id






-T system

Set partition mode tostand alone

Sets the mode for a specificpartition in the scalable complex tostandalone. A partition set tostand-alone mode operates as asingle blade server system. Singleblade servers set up as astand-alone partition will performconsistently if they are installed inanother BladeCenter unit.Note:v A partition must be powered off

to change its mode.v The complex_id and partition_id



scale -mode standalone-compid complex_id-partid partition_id






-T system




Set partition mode topartition

Sets the mode for a specificpartition in the scalable complex topartition.Note:v A partition must be powered off

to change its mode.v The complex_id and partition_id



scale -mode partition-compid complex_id-partid partition_id






-T system

Power on partition inscalable complex

Turns on a specific partition in thescalable complex.Note:v The complex_id and partition_id



scale -on -compidcomplex_id -partidpartition_id






-T system




Power off partition inscalable complex

Turns off a specific partition in thescalable complex.Note:v The complex_id and partition_id



scale -off -compidcomplex_id -partidpartition_id






-T system

Power cycle partition inscalable complex

Cycles power for a specificpartition in the scalable complex. Ifthe partition is off, it will turn on.If the partition is on, it will turn offand then turn on.Note:v The complex_id and partition_id



scale -cycle -compidcomplex_id -partidpartition_id






-T system


Example: To view all scalable complexes in the system, while the BladeCenter unitis set as the persistent command environment, at the system> prompt, typescale

To power on a partition targeted by the complex ID “06EC” and the partition ID“1”, while the BladeCenter unit is set as the persistent command environment, atthe system> prompt, typescale -on -compid 06EC -partid 1

The following example shows the information that is returned from thesecommands:system> scale

--- Complex ID: 06EC ---

Partition ID: 1Assigned Nodes:---------------

Bay: 2Name: HX5 SDV #3Processors/Memory: 2 Intel Xeon/4 DIMMs 2GBLogical Node ID: 0Status: powered onMode: partitionPrimary: Yes

Bay: 3Name: HX5 SDV #4Processors/Memory: 2 Intel Xeon/4 DIMMs 2GBLogical Node ID: 1Status: powered onMode: partitionPrimary: No

system> scale -on -compid 06EC -partid 1Note: The power operation may take a few moments to complete.OKsystem>


sddump commandThis command initiates a dump of service data from blade servers that supportthis function.

Table 68. sddump command


Dump service data Dumps service data of the specifiedtype from the specified bladeserver target.Note: Data dumps can be initiated,but are not collected, from theadvanced management module.

sddump -init type

where type is:v sd for a service data

dump.v sp for a service

processor data dump.v pf for a platform data

dump.v pt for a partition data

dump.



-T system:blade[x]


Get service data Collects and displays service data,from the last generated service-datadump, of the specified type fromthe specified blade server target.

sddump -coll type

where type is:v sd to collect and display

service data from lastdump.

v sp to collect and displayservice processor datafrom last dump.

v pf to collect and displayplatform data from lastdump.

v pt to collect and displaypartition data from lastdump.



-T system:blade[x]



Example: To initiate a data dump from the service processor of the blade server inbay 2, while this blade server is set as the persistent command environment, at thesystem:blade[2]> prompt, typesddump -init sp

The following example shows the information that is returned from this command:system:blade[2]> sddump -init spOKsystem:blade[2]>


sdemail commandThis command sends an email with the service information to the specifiedrecipients.

Table 69. sdemail command


Send service informationusing email to specifiedrecipients

Send an email with serviceinformation to the specifiedrecipients. You assign a subject andan email address. When you runthis command, it attaches theservice log to the message.

sdemail -subj "subject"-to address

where:v "subject" is a

quote-delimited textstring up to 119characters in length.

v address is the recipientsemail address. Multipleaddresses separatedwith a comma can beentered (119 charactersmaximum).





configuration


-T system:mm[x]


Example:

To send a service information email message, while management module 1 is setas the persistent command environment, at the system:mm[1]> prompt, typesdemail -to [email protected] -subj "Blade 8 Reboot"


The following example shows the information that is returned from this command:system:mm[1]> sdemail -to [email protected] -subj "Blade 8 Reboot"OK


security commandThis command enables and displays the state of the data encryption feature forsensitive information stored in the advanced management module, such aspasswords and keys.

Once enabled, the security feature can not be disabled without resetting allmanagement module settings to their default configuration.

Table 70. security command


Display managementmodule security setting

Displays the security setting formanagement module dataencryption (on or off).

security -T system:mm[x]


Enable data encryptionfor management module

Enables data encryption for themanagement module.

Attention: If you enable dataencryption, you can not disable itwithout resetting the managementmodule to the defaultconfiguration.

security -e



-T system:mm[x]


Example:

To enable data encryption for the management module, while management module1 is set as the persistent command environment, at the system:mm[1]> prompt, typesecurity -e

To display the data encryption setting for the management module, whilemanagement module 1 is set as the persistent command environment, at thesystem:mm[1]> prompt, typesecurity

The following example shows the information that is returned from these twocommands:system:mm[1]> security -eOKsystem:mm[1]> security-e onsystem:mm[1]>


service commandThis command configures and displays the management-module service setting.

Table 71. service command


Display service setting Displays the service setting fortechnician debug of the advancedmanagement module with a USBkey (enable or disable).

service -T system:mm[x]


Enable technician debug Configure service setting to enabletechnician debug of the advancedmanagement module with a USBkey.

service -enable



-T system:mm[x]


Disable techniciandebug

Configure service setting to disable(default setting) technician debugof the advanced managementmodule with a USB key.

service -disable



-T system:mm[x]


Example:

To enable technician debug of the advanced management module with a USB key,while management module 1 is set as the persistent command environment, at thesystem:mm[1]> prompt, typeservice -enable

To display the service setting of the advanced management module, whilemanagement module 1 is set as the persistent command environment, at thesystem:mm[1]> prompt, typeservice


The following example shows the information that is returned from these twocommands:system:mm[1]> service -enableOKsystem:mm[1]> serviceDebug with USB key: Enabledsystem:mm[1]>


shutdown commandThis command forces a blade server to shut down.

Table 72. shutdown command


Shutdown blade server Forces a shutdown for the specifiedblade server.

shutdown -f



-T system:blade[x]


Example:

To force a shutdown for the blade server in blade bay 5, while this blade server isset as the persistent command environment, at the system:blade[5]> prompt, typeshutdown -f

The following example shows the information that is returned from this command:system:blade[5]> shutdown -fOKsystem:blade[5]>


slp commandThis command sets and displays the service location protocol (SLP) settings for themanagement module.

Table 73. slp command


Displaymanagement-moduleSLP settings

Displays the SLP settings for theprimary management module.Returned values are:v -t address_typev -i multicast_addr

slp -T system:mm[x]


Set management-moduleSLP address type

Sets the SLP address type for theprimary management module.

slp -t address_type

where address_type ismulticast or broadcast.



-T system:mm[x]


Set management-moduleSLP multicast address

Sets the SLP multicast address forthe primary management module.

slp -i multicast_addr

where multicast_addr is themulticast IP address.



-T system:mm[x]


Example:

To set the SLP address type of the advanced management module to multicast,while management module 1 is set as the persistent command environment, at thesystem:mm[1]> prompt, typeslp -t multicast

To display the SLP settings of the advanced management module, whilemanagement module 1 is set as the persistent command environment, at thesystem:mm[1]> prompt, typeslp


The following example shows the information that is returned from these twocommands:system:mm[1]> slp -t multicastOKsystem:mm[1]> slp-t multicast-i 255.255.255.255system:mm[1]>


smtp commandThis command configures and displays the management-module SMTP settings.

Table 74. smtp command


Display SMTP serverhost name or IP address

Displays the SMTP server hostname or IP address.

smtp -T system:mm[x]


Server host name or IPaddress - set

Checks syntax and sets the serverhost name or IP address.

smtp -shostname/ip_address

where hostname/ip_addressis the host name or IPaddress of the server.



-T system:mm[x]



Table 74. smtp command (continued)


SMTP e-mail serverdomain name - set

Checks syntax and sets the SMTPe-mail server domain name.

smtp -d domainname

where domainname is avalid domain name thatmeets the followingcriteria:

v Alphanumeric string upto 63 characters inlength.

v Can contain dots (.),dashes (-), orunderscores (_).

v Must contain at leastone dot.

v No consecutive dots areallowed.

v Quotes are not required.

v Value can be cleared bysetting it to an empty,double-quote limitedstring ("").



-T system:mm[x]


Example:

To set the SMTP server host name to us.ibm.com, while management module 1 isset as the persistent command environment, at the system:mm[1]> prompt, typesmtp -s us.ibm.com

To display the SMTP configuration, while management module 1 is set as thepersistent command environment, at the system:mm[1]> prompt, typesmtp


The following example shows the information that is returned from these twocommands:system:mm[1]> smtp -s us.ibm.comOKsystem:mm[1]> smtp-s us.ibm.comsystem:mm[1]>


snmp commandThis command configures and displays the management-module SNMP settings.

Table 75. snmp command


Display SNMPconfiguration ofmanagement module

Displays the current SNMPconfiguration of the managementmodule.

snmp -T system:mm[x]


SNMPv1 agent -enable/disable

Enables or disables themanagement-module SNMPv1agent.Note: Before you can enable theSNMPv1 agent, the following mustbe specified:v management module contact

namev management module locationv at least one community namev at least one valid IP address for

that community

(see “config command” on page111)

snmp -a -state




-T system:mm[x]


SNMPv3 agent -enable/disable

Enables or disables themanagement-module SNMPv3agent.Note: Before you can enable theSNMPv3 agent, the following mustbe specified:v management module contact

namev management module location

(see “config command” on page111)

snmp -a3 -state




-T system:mm[x]


SNMP traps -enable/disable

Enables or disables themanagement-module SNMP traps.

snmp -t -state




-T system:mm[x]



Table 75. snmp command (continued)


SNMP community 1name - set

Sets the name of community 1. snmp -c1 name

where name is a descriptivename of community 1.v Arguments containing

spaces must be enclosedin quotation marks. Noleading or trailing spacesare allowed inarguments.

v If this argument is notspecified, the snmpcommand clears thisoption.

v You can also clear thisoption by assigning anempty string as its value.



-T system:mm[x]





SNMP community 1first host name or IPaddress - set

Checks syntax and sets the firsthost name or IP address ofcommunity 1.

snmp -c1i1hostname/ip_address

where hostname/ip_address isthe first host name or IPaddress of community 1.v The first IP address of

the first community canbe set to 0.0.0.0 if thecommunity access type isset to GET (for allmanagement moduletypes) or SET.

v Arguments containingspaces must be enclosedin quotation marks. Noleading or trailing spacesare allowed inarguments.





-T system:mm[x]





SNMP Community 1,first host name - setaccess to SET(wildcard)

Sets the access type for community1 to SET.

snmp –ca1 set -c1i10.0.0.0v With the access type of

SET, anyone can querythe managementinformation base (MIB)and set MIB values.Using 0.0.0.0 IP addresswith SET access allowsopen access to themanagement module forwrite (SET) operations. A0.0.0.0 address cannot bea trap receiver.






-T system:mm[x]





SNMP Community 1,first host name or IPaddress - set access toGET (wildcard)

Sets the access type for community1 to GET.

snmp –ca1 get -c1i10.0.0.0v With the access type of

GET, anyone can querythe MIB. Using 0.0.0.0 IPaddress with GET accessallows open access to themanagement module forread (GET). A 0.0.0.0address cannot be a trapreceiver.






-T system:mm[x]





SNMP community 1second host name or IPaddress - set

Checks syntax and sets the secondhost name or IP address ofcommunity 1.


where hostname/ip_address isthe second host name or IPaddress of community 1.v Arguments containing






-T system:mm[x]





SNMP community 1third host name or IPaddress - set

Checks syntax and sets the thirdhost name or IP address ofcommunity 1.


where hostname/ip_address isthe third host name or IPaddress of community 1.v Arguments containing






-T system:mm[x]


SNMPv3 community 1view type - set

Sets the SNMPv3 view type forcommunity 1.

snmp -ca1 type

where type isv getv setv trap



-T system:mm[x]













-T system:mm[x]





where hostname/ip_address isthe first host name or IPaddress of community 2.v Arguments containing






-T system:mm[x]














-T system:mm[x]














-T system:mm[x]




snmp -ca2 type




-T system:mm[x]













-T system:mm[x]





where hostname/ip_address isthe first host name or IPaddress of community 3.v Arguments containing






-T system:mm[x]














-T system:mm[x]














-T system:mm[x]




snmp -ca3 type




-T system:mm[x]





SNMP contact name -set

Sets the contact name. snmp -cn contact_name

where contact_name is thename of the party to becontacted when SNMPtraps an event.v Arguments containing






-T system:mm[x]





SNMP location - set Sets the location. snmp -l hostname/ip_address

where hostname/ip_addressidentifies the websitesupporting SNMP for thismanagement module.v Arguments containing






-T system:mm[x]


Example: To view the SNMP configuration, while advanced management module 1is set as the persistent command environment, at the system:mm[1]> prompt, typesnmp

To enable the SNMP agent and SNMP traps, while advanced management module1 is set as the persistent command environment, at the system:mm[1]> prompt, typesnmp -a -on -t -on

The following example shows the information that is returned from these twocommands:system:mm[1]> snmp-a Enabled-a3 Enabled-t Enabled-l Raleigh,NC-cn Mr. Smith-c1 public-c1i1 9.44.146.157-c1i2 9.44.147.24-c1i3 9.49.165.217-ca1 set-c2 private-c2i1 9.42.226.4-c2i2-c2i3-ca2 get-c3 test


-c3i1 9.44.247.64-c3i2-c3i3-ca3 getsystem:mm[1]> snmp -a -on -t -onsystem:mm[1]>


sol (serial over LAN) commandThis command configures SOL functions and indicates SOL status.

Table 76. sol (serial over LAN) command


Display SOL status Displays the SOL status for thetargeted device:v When the command target is the

primary management module, itdisplays the following values:– -status on/off (global SOL

status)– -c retry_count– -e CLI_key_sequence– -i retry_interval– -r reset_blade_key_seq– -s send_threshold– -t accumulate_timeout– -v VLAN_id

Note: For the advancedmanagement module, theVLAN_id is identified as "VLANID".

v When the command target is ablade server, it displays thefollowing:– -status enabled/disabled (SOL

status for the blade server)– Status of any SOL sessions for

that blade server:- Not ready- Ready- Active

sol -T system:mm[x]

-T system:blade[x]

where x is the primarymanagement-moduleor blade server baynumber.

SOL retry interval - set Sets the SOL retry interval to theinput value.

sol -i value

where value is from 10 msto 2550 ms, inclusive, in 10ms increments. If youenter a value less than 10ms, the retry interval willbe set to 10 ms. If youenter a value greater than2550 ms, the retry intervalwill be set to 2550 ms.

This command can onlybe run by users who haveone or more of thefollowing commandauthorities:v Supervisorv Chassis configurationv Blade configuration


-T system:mm[x]



Table 76. sol (serial over LAN) command (continued)


SOL retry count - set Sets the SOL retry count to theinput value.

sol -c value

where value is from 0 to 7,inclusive. If you enter avalue of 0, no retries willbe attempted. If you entera value greater than 7, anerror will be displayed.



-T system:mm[x]


SOL send threshold - set Sets the SOL send threshold to theinput value. Setting the thresholdvalue to 1 causes the blade serverintegrated system managementprocessor to send an SOL packet assoon as the first character isreceived.

sol -s value

where value is from 1 to251, inclusive. If you entera value outside this range,an error will be displayed.



-T system:mm[x]





SOL accumulate timeoutset

Sets the SOL accumulate timeout tothe input value.

sol -t value

where value is from 5 msto 1275 ms, inclusive. Ifyou enter a value less than5 ms, the accumulatetimeout will be set to 5ms. If you enter a valuegreater than 1275 ms, anerror will be displayed.



-T system:mm[x]


SOL enable - global Enables SOL globally for theBladeCenter unit. The global SOLenable command does not affectthe SOL session status for eachblade server.

sol -status enabled



-T system:mm[x]


SOL enable - bladeserver

Enables SOL for the specified bladeserver.

sol -status enabled



-T system:blade[x]





SOL disable - global Disables SOL globally for theBladeCenter unit. The global SOLdisable command does not affectthe SOL session status for eachblade server.

sol -status disabled



-T system:mm[x]


SOL disable - bladeserver

Disables SOL for the specifiedblade server.

sol -status disabled



-T system:blade[x]





CLI key sequence - set Sets the key sequence that is usedto enter the CLI while a Telnetsession in SOL mode.

sol -e value

where value is the keysequence. In this sequence,a ^ (the carat symbol)indicates a Ctrl that mapsto control-key sequences;for example:v ^[ (the carat symbol

followed by a leftbracket) means Esc

v ^M (the carat symbolfollowed by a capitolM) means carriagereturn.

Refer to an ASCII-to-keyconversion table for acomplete listing ofcontrol-key sequences.



-T system:mm[x]





Reset blade server keysequence - set

Sets the key sequence that willreset a blade server while a Telnetsession in SOL mode.

sol -r value

where value is the keysequence. In this sequence,a ^ (the carat symbol)indicates a Ctrl that mapsto control-key sequences;for example:v ^[ (the carat symbol

followed by a leftbracket) means Esc

v ^M (the carat symbolfollowed by a capitolM) means carriagereturn.

Refer to an ASCII-to-keyconversion table for acomplete listing ofcontrol-key sequences.



-T system:mm[x]


Example:

To set the SOL accumulate timeout to 25 ms, while management module 1 is set asthe persistent command environment, at the system:mm[1]> prompt, typesol -t 25

To set the reset blade server key sequence to Esc R Esc r Esc R, while managementmodule 1 is set as the persistent command environment, at the system:mm[1]>prompt, typesol -r ^[R^[r^[R

To display the SOL settings for the management module, while the managementmodule 1 is set as the persistent command environment, at the system:mm[1]>prompt, typesol

To display the SOL settings for the server blade in the third bay, while blade 3 isset as the persistent command environment, at the system:blade[3]> prompt, typesol


The following example shows the information that is returned from thesecommands:system:mm[1]> sol -t 25OKsystem:mm[1]> sol-status enabled-c 3-e ^[(-i 250-r ^[R^[r^[R-s 250-t 5VLAN ID 4095system:mm[1]>

system:blade[3]> sol-status enabledSOL Session: Not ReadySOL retry interval: 250 msSOL retry count: 3SOL bytes sent: 0SOL bytes received: 0SOL destination IP address: 10.10.10.80SOL destination MAC: 00:00:00:00:00:00SOL I/O module slot number: 0SOL console user ID:SOL console login from:SOL console session started:SOL console session stopped:Blade power state: OnSOL recommended action: Internal network path between the AMM and thisblade server is currently not available. Please refer to AMM user guide fortroubleshooting information.system:blade[3]>


sshcfg commandThis command sets and displays the SSH status of the management module.

Table 77. sshcfg command


Display SSH status Displays the SSH status of themanagement module. Returnedvalues are:

v -v1 off

v -cstatus: state of CLI SSH server(enabled, disabled)

v CLI SSH port number

v -sstatus: state of SMASH SSHserver (enabled, disabled)

v SMASH SSH port number

v ssh-dss fingerprint

v ssh-rsa fingerprint

v number of SSH public keysinstalled

v number of locations available tostore SSH keys

Note: For scripting purposes, the"-v1 off" state is always displayed.

sshcfg -T system:mm[x]


Display RSA host keyinformation

Displays RSA host key informationfor the management module.

sshcfg -hk rsa -T system:mm[x]


Display DSA host keyinformation

Displays DSA host key informationfor the management module.

sshcfg -hk dsa -T system:mm[x]


Generate host key Generates a host key for themanagement module.

sshcfg -hk gen



-T system:mm[x]



Table 77. sshcfg command (continued)


Set state of CLI SSHserver

Sets the state of the CLI SSH serverfor the management module.

sshcfg -cstatus state




-T system:mm[x]


Set state of SMASHSSH server

Sets the state of the SMASH SSHserver for the management module.

sshcfg -sstatus state




-T system:mm[x]


Example:

To display SSH status, while management module 1 is set as the persistentcommand environment, at the system:mm[1]> prompt, typesshcfg

The following example shows the information that is returned from this command:system:mm[1]> sshcfg-v1 off-cstatus enabledCLI SSH port 22-sstatus disabledSMASH SSH port 50024ssh-dss 2048 bit fingerprint: 27:ee:bd:a9:27:28:d8:a5:93:03:3d:8e:77:d0:38:2cssh-rsa 2048 bit fingerprint: 66:c9:73:4f:18:11:02:10:f3:05:6e:d7:27:05:a5:012 SSH public keys installed10 locations available to store SSH public keyssystem:mm[1]>


sslcfg commandThis command sets and displays the Secure Sockets Layer (SSL) status of theadvanced management module.

Table 78. sslcfg command


Display managementmodule SSL status

Displays the SSL status of thespecified management module.This status includes informationabout SSL certificates.

sslcfg -T system:mm[x]


Set SSL certificatehandling for standbymanagement module

Enables or disables use of anadditional SSL certificate for thestandby management module. Ifdisabled, the standby managementmodule uses the same SSLcertificate as the primarymanagement module.Note: An additional SSL certificatecan only be configured whenmanagement module advancedfailover is set to "swap" and thestandby management module has avalid SSL certificate set up.

sslcfg -ac state

where state is:v on to use an additional

certificatev off to use the same

certificate



-T system:mm[x]


Set SSL state formanagement moduleweb server

Enables or disables SSL for themanagement module web server.Note: The SSL for themanagement module web servercan only be enabled if a valid SSLcertificate is set up.

sslcfg -server state




-T system:mm[x]



Table 78. sslcfg command (continued)


Set SSL state for LDAPclient

Enables or disables SSL for theLDAP client.Note: The SSL for the LDAP clientcan only be enabled if a valid SSLcertificate is set up.

sslcfg -client state




-T system:mm[x]





Generate self-signedcertificate

Generates a self-signed certificatefor the management module webserver or the LDAP client.

The following values must be setwhen generating a self-signedcertificate:v Country using the -c command

option.v State or province using the -sp

command option.v City or locality using the -cl

command option.v Organization name using the -on

command option.v Management module host name

using the -hn command option.Note: This host name mustmatch the host name that is usedby a web browser to connect tothe management module.

The following optional values canbe set when generating aself-signed certificate:v Contact person using the -cp

command option.v Email address of the contact

person using the -ea commandoption.

v Unit within a company ororganization using the -oucommand option.

v Additional information such as asurname using the -s commandoption.

v Additional information such as agiven name using the -gncommand option.

v Additional information such asinitials using the -in commandoption.

v Additional information such as adistinguished name qualifierusing the -dq command option.

sslcfg -cert type -ccountry -sp "state" -cl"city" -on "org" -hnhostname -cp "name" -eaemail -ou "org_unit" -s"surname" -gn"given_name" -in "initial"-dq "dn_qualifier"

where the followingrequired options are:v type is:

– server for amanagement moduleweb server certificate.

– client for an LDAPclient certificate.

v country is two-characteralphabetic code for thecountry.

v "state" is a state orprovince name of up to60 characters in length.

v "city" is a city orlocality name of up to50 characters in length.

v "org" is an organizationname of up to 60characters in length.

v hostname is a valid hostname of up to 60characters in length.

where the followingoptional options are:v "name" is up to 60

characters in length.v email is a valid email

address of up to 60characters.

v "org_unit" is up to 60characters.

v "surname" is up to 60characters.

v "given_name" is up to 60characters.

v "initial" is up to 20characters.

v "dn_qualifier" is up to 60characters.


-T system:mm[x]





Generate self-signedcertificate

(continued)






Generate CSR Generates a certificate signingrequest (CSR) for the managementmodule web server or the LDAPclient.

The following values must be setwhen generating a CSR:v Country using the -c command

option.v State or province using the -sp

command option.v City or locality using the -cl

command option.v Organization name using the -on

command option.v Management module host name

using the -hn command option.Note: This host name mustmatch the host name that is usedby a web browser to connect tothe management module.

The following optional values canbe set when generating a CSR:v Contact person using the -cp

command option.v Email address of the contact

person using the -ea commandoption.

v Unit within a company ororganization using the -oucommand option.

v Additional information such as asurname using the -s commandoption.

v Additional information such as agiven name using the -gncommand option.

v Additional information such as ainitials using the -in commandoption.

v Additional information such as adistinguished name qualifierusing the -dq command option.

v Additional information such as aCSR password using the -cpwdcommand option.


sslcfg -csr type -ccountry -sp "state" -cl"city" -on "org" -hnhostname -cp "name" -eaemail -ou "org_unit" -s"surname" -gn"given_name" -in "initial"-dq "dn_qualifier" -cpwdpassword -un "un_name"

where the followingrequired options are:v type is:

– server for amanagement moduleweb server CSR.

– client for an LDAPclient CSR.

v country is two-characteralphabetic code for thecountry.

v "state" is a state orprovince name of up to60 characters in length.

v "city" is a city orlocality name of up to50 characters in length.

v "org" is an organizationname of up to 60characters in length.

v hostname is a valid hostname of up to 60characters in length.

where the followingoptional options are:v "name" is up to 60

characters in length.v email is a valid email

address of up to 60characters.

v "org_unit" is up to 60characters.

v "surname" is up to 60characters.

v "given_name" is up to 60characters.


-T system:mm[x]





Generate CSR

(continued)

v Additional information such asan unstructured name qualifierusing the -un command option.

v "initial" is up to 20characters.

v "dn_qualifier" is up to 60characters.

v password is between 6and 30 characters.

v "un_name" is up to 60characters.

Note: Arguments thatmust be quote-delimitedare shown in quotationmarks.



Download certificate file Downloads the specified certificatefile.

The IP address of the TFTP serverfor downloading an SSL self-signedcertificate or CSR must be set usingthe -i command.

The file name for downloading anSSL self-signed certificate or CSRcan be set using the -l command.If no file name is specified, thedefault file name for the file will beused.

sslcfg -dnld -cert_type -lfilename -i ipaddress

where:v cert_type is

– cert for an SSLself-signed certificate

– csr for a CSRv filename is a valid

filename of up to 256characters in lengthcontaining any characterexcept the percent sign (% ), forward-slash ( / ),or double-quote ( " ).

v ipaddress is the IPv4 orIPv6 IP address of theTFTP server.



-T system:mm[x]





Import certificate file Import (upload) the specifiedcertificate file.

The IP address of the TFTP serverfor uploading an SSL self-signedcertificate must be set using the -icommand.

The file name for uploading an SSLself-signed certificate can be setusing the -l command.

sslcfg -upld -cert -lfilename -i ipaddress

where:v filename is a valid

filename of up to 256characters in lengthcontaining any characterexcept the percent sign (% ), forward-slash ( / ),or double-quote ( " ).

v ipaddress is the IPv4 orIPv6 IP address of theTFTP server.



-T system:mm[x]





Import/download/remove trustedcertificate 1

Perform the specified operation ontrusted certificate 1 for the SSLclient. Valid operations are:v import (upload)v downloadv remove

The IP address of the TFTP serverfor uploading or downloading atrusted certificate must be set usingthe -i command.

The file name for uploading ordownloading a trusted certificatecan be set using the -l command.

sslcfg -tc1 operation

where operation is:v importv downloadv remove

Note: The -tc1 optionmust be used with thefollowing options:v -i ipaddressv -l filename

where:v ipaddress is the IPv4 or

IPv6 IP address of theTFTP server.

v filename is a validfilename of up to 256characters in lengthcontaining any characterexcept the percent sign (% ), forward-slash ( / ),or double-quote ( " ).



-T system:mm[x]








The file name for uploading ordownloading a trusted certificatecan be set using the -l command.









-T system:mm[x]








The file name for uploading ordownloading a trusted certificatecan be set using the -l command.For importing a certificate "-l<filename>" is required.









-T system:mm[x]


Example: To view SSL information for the management module in bay 1, whilethis management module is set as the persistent command environment, at thesystem:mm[1]> prompt, typesslcfg

The following example shows the information that is returned from this command:system:mm[1]> sslcfg-server disabled-client disabledSSL Server Certificate status:A CA-signed certificate is installedSSL Client Certificate status:No certificate has been generatedSSL Client Trusted Certificate status:Trusted Certificate 1: Not availableTrusted Certificate 2: Not availableTrusted Certificate 3: Not availablesystem:mm[1]>


syslog commandThis command manages how the advanced management module handlestransmission of event log messages to networked syslog event collectors.

Table 79. syslog command


Display syslogconfiguration

Displays the syslog event logtransmission configuration of theadvanced management module.

syslog -T system:mm[x]


Set syslog filter level Set severity filtering levels forsyslog event log transmission.

syslog -sev level

where level is:v i selects error, warning,

and informational logsv w selects error and

warning logsv e selects error logs



-T system:mm[x]


Set syslog event logtransmission state forcollector 1

Enables or disables syslog event logtransmission to collector 1.

syslog -coll1 state




-T system:mm[x]



Table 79. syslog command (continued)


Set syslog event logtransmission state forcollector 2

Enables or disables syslog event logtransmission to collector 2.

syslog -coll2 state




-T system:mm[x]


syslog event logcollector 1 host name orIP address - set

Sets the host name or IP addressfor syslog event collector 1.

syslog -i1hostname/ip_address

where hostname/ip_addressis the collector 1 hostname or IP address.



-T system:mm[x]


syslog event logcollector 2 host name orIP address - set

Sets the host name or IP addressfor syslog event collector 2.

syslog -i2hostname/ip_address

where hostname/ip_addressis the collector 2 hostname or IP address.



-T system:mm[x]





syslog event logcollector 1 port number -set

Sets the port number for syslogevent collector 1.

syslog -p1 port

where port is the collector1 port number from 1 to65535, inclusive. If youenter a value outside thisrange, an error will bedisplayed.



-T system:mm[x]


syslog event logcollector 2 port number -set

Sets the port number for syslogevent collector 2.

syslog -p2 port

where port is the collector2 port number from 1 to65535, inclusive. If youenter a value outside thisrange, an error will bedisplayed.



-T system:mm[x]





Generate test message Generates a test syslog message totest the configuration.Note: The -test command optionsmust be run exclusive of othercommand options.

syslog -test





configuration


-T system:mm[x]


Example: To view the syslog event log transmission configuration of the primaryadvanced management module in bay 1, while this management module is set asthe persistent command environment, at the system:mm[1]> prompt, typesyslog

The following example shows the information that is returned from this command:system:mm[1]> syslog-sev 1-coll1 enabled-coll2 disabled-i1 253.245.45.1-i2-p1 514-p2 514system:mm[1]>


tcpcmdmode commandThis command displays and changes the timeout of the TCP command-modesessions that are used by IBM Systems Director software for out-of-bandcommunication with the management module. This command is also used toenable or disable the TCP command-mode sessions.

Table 80. tcpcmdmode command


Display TCPcommand-mode sessionstatus and timeout

Displays the secure and non-secureTCP command-mode session status(maximum number of sessions) andtimeout.

tcpcmdmode -T system:mm[x]


Set TCP command-modesession timeout

Sets the secure and non-secure TCPcommand-mode session timeoutvalue.

tcpcmdmode -t timeout

where timeout is from 0seconds (no timeout) to4294967295 seconds,inclusive. If you enter avalue outside this range,an error will be displayed.



-T system:mm[x]


Disable TCPcommand-mode sessions

Disables TCP command-modesessions that are used by IBMSystems Director software forout-of-band communication withthe management module. Thisapplies to both read and writeoperations.

tcpcmdmode -status 0



-T system:mm[x]



Table 80. tcpcmdmode command (continued)


Enable and set numberof TCP command-modesessions

Enables TCP command-mode andsets the maximum number ofsessions that can be used by IBMSystems Director software forout-of-band communication withthe management module. For readoperations, all of the values from 1to 20, inclusive, mean enabled.Note: The advanced managementmodule supports a combined totalof up to 20 secure and non-secureTCP command-mode sessions.

tcpcmdmode -statusnumber_sessions

where number_sessions isfrom 1 to 20, inclusive. (Avalue of 0 disables TCPcommand-mode sessions.)If you enter a valueoutside this range, anerror will be displayed.



-T system:mm[x]


Disable secure TCPcommand-mode sessions

Disables secure TCPcommand-mode sessions that areused by IBM Systems Directorsoftware for out-of-bandcommunication with themanagement module. This appliesto both read and write operations.

tcpcmdmode -sstatus 0



-T system:mm[x]


Enable and set numberof secure TCPcommand-mode sessions

Enables secure TCPcommand-mode and sets themaximum number of sessions thatcan be used by IBM SystemsDirector software for out-of-bandcommunication with themanagement module. For readoperations, all of the values from 1to 20, inclusive, mean enabled.Note: The advanced managementmodule supports a combined totalof up to 20 secure and non-secureTCP command-mode sessions.

tcpcmdmode -sstatusnumber_sessions

where number_sessions isfrom 1 to 20, inclusive. (Avalue of 0 disables secureTCP command-modesessions.) If you enter avalue outside this range,an error will be displayed.



-T system:mm[x]



Example: To enable a maximum of three TCP command-mode sessions for theprimary management module, while management module 1 is set as the persistentcommand environment, at the system:mm[1]> prompt, typetcpcmdmode -status 3

To enable a maximum of five secure TCP command-mode sessions for the primarymanagement module, while management module 1 is set as the persistentcommand environment, at the system:mm[1]> prompt, typetcpcmdmode -sstatus 5

To set the TCP command-mode session timeout for the primary managementmodule to 6 minutes, while management module 1 is set as the persistentcommand environment, at the system:mm[1]> prompt, typetcpcmdmode -t 360

To display the TCP command-mode session status and timeout for the primarymanagement module, while management module 1 is set as the persistentcommand environment, at the system:mm[1]> prompt, typetcpcmdmode

The following example shows the information that is returned from thesecommands:system:mm[1]> tcpcmdmode -status 3OKsystem:mm[1]> tcpcmdmode -sstatus 5OKsystem:mm[1]> tcpcmdmode -t 360OKsystem:mm[1]> tcpcmdmode-status 3 connections-sstatus 5 connections-t 360 secondssystem:mm[1]>


telnetcfg (Telnet configuration) commandThis command displays and configures the command-line session parameters ofthe primary management module.

Table 81. telnetcfg (Telnet configuration) command


Display command-linesession configuration

Displays the command-line sessionconfiguration of the primarymanagement module.

telnetcfg -T system:mm[x]


Set command-linesession timeout forprimary managementmodule

Sets the command-line sessiontimeout value for the primarymanagement module.

telnetcfg -t timeout

where timeout is from 0seconds (no timeout) to4294967295 seconds,inclusive. If you enter avalue outside this range,an error will be displayed.



-T system:mm[x]


Example: To set the command-line session timeout for the primary managementmodule to 6 minutes, while management module 1 is set as the persistentcommand environment, at the system:mm[1]> prompt, typetelnetcfg -t 360

To display the command-line session configuration for the primary managementmodule, while management module 1 is set as the persistent commandenvironment, at the system:mm[1]> prompt, typetelnetcfg

The following example shows the information that is returned from these twocommands:system:mm[1]> telnetcfg -t 360OKsystem:mm[1]> telnetcfg-t 360system:mm[1]>


temps commandThis command displays actual temperatures and temperature threshold values forBladeCenter components.

Table 82. temps command


Display temperaturevalues

Displays the current temperatureand temperature threshold settingsfor the specified component:v The management module target

displays the managementmodule ambient temperature.

v The blade server target displaysthe temperature values forcomponents in the specifiedblade server, such asmicroprocessors and expansionmodules.

v The media tray target displaysvalues for the temperature sensorin the media tray.

temps -T system:mm[x]

-T system:blade[x]

-T system:mt


Example: To view the current temperature and temperature thresholds for theblade server in bay 3, while this blade server is set as the persistent commandenvironment, at the system:blade[3]> prompt, typetemps

The following example shows the information that is returned from this command:system:blade[3]> temps

Hard WarningComp Value Warning Shutdown Reset---- ----- ------- -------- -------CPU1 38.00 85.00 95.00 78.00CPU2 35.00 85.00 95.00 78.00BEM ----- ----- ----- -----system:blade[3]>


trespass commandThis command sets and displays the status and message for the advancedmanagement module trespass feature that can display a warning message to userswhen they log in.

Table 83. trespass command


Display status ofmanagement moduletrespass feature

Displays status of the trespassfeature for the managementmodule. Possible return values are:

v -twe (on or off)

v -tw warning_message

Note: The warning_message isshown only when the trespassfeature is enabled (-twe on).

trespass -T system:mm[x]


Enable / disablemanagement moduletrespass feature

Enables or disables trespass featurefor management module.

trespass -twe state




-T system:mm[x]


Set management moduletrespass message

Sets message that is displayed tousers who log in to themanagement module when thetrespass feature is enabled.Note: Setting a newwarning_message permanentlyreplaces the default warningmessage.

trespass -tw"warning_message"

where "warning_message"is up to 1600 characters inlength and enclosed indouble-quotation marks.



-T system:mm[x]



Table 83. trespass command (continued)


Set management moduletrespass feature todefault values

Sets trespass feature to defaultvalues:

v -twe: off

v -tw (warning message):WARNING! This computersystem and network is PRIVATEAND PROPRIETARY and mayonly be accessed by authorizedusers. Unauthorized use of thiscomputer system or network isstrictly prohibited and may besubject to criminal prosecution,employee discipline up to andincluding discharge, or thetermination of vendor/servicecontracts. The owner, or itsagents , may monitor anyactivity or communication on thecomputer system or network.The owner, or its agents, mayretrieve any information storedwithin the computer system ornetwork. By accessing and usingthis computer system ornetwork, you are consenting tosuch monitoring and informationretrieval for law enforcement andother purposes. Users shouldhave no expectation of privacy asto any communication on orinformation stored within thecomputer system or network,including information storedlocally or remotely on a harddrive or other media in use withthis computer system ornetwork.

trespass -twd



-T system:mm[x]


Example:

To enable the management module trespass feature, while management module 1is set as the persistent command environment, at the system:mm[1]> prompt, typetrespass -twe on

To set the trespass feature message to 'Authorized Access only', while managementmodule 1 is set as the persistent command environment, at the system:mm[1]>prompt, typetrespass -tw "Authorized Access only"

To display the management module trespass feature status, while managementmodule 1 is set as the persistent command environment, at the system:mm[1]>prompt, typetrespass


The following example shows the information that is returned from thesecommands:system:mm[1]> trespass -twe onOKsystem:mm[1]> trespass -tw "Authorized Access only"-tw OKsystem:mm[1]> trespass-twe on-tw Authorized Access onlysystem:mm[1]>


uicfg commandThis command displays and configures the management module user interfacesettings.

Table 84. uicfg command


Display managementmodule user interfacesettings

Displays the user interface settingsfor the management module.Returned values indicate enabledor disabled status for the followinginterfaces:v -cliv -snmpv -tcm (TCP command mode)v -stcm (secure TCP command

mode)v -web (web interface)

uicfg -T system:mm[x]


Enable / disablecommand-line interface

Enables or disables themanagement modulecommand-line interface (usingTelnet or SSH).

uicfg -cli state




-T system:mm[x]


Enable / disableSNMPv1 and SNMPv3

Enables or disables SNMPv1 andSNMPv3 connections to themanagement module.

uicfg -snmp state




-T system:mm[x]



Table 84. uicfg command (continued)


Enable / disable TCPcommand mode

Enables or disables TCP commandmode (used by IBM SystemsDirector) for the managementmodule.

uicfg -tcm state




-T system:mm[x]


Set number of TCPcommand modeconnections

Enable or disable the TCPcommand mode, or sets themaximum number of connectionsexplicitly.Note: Any number of connections(1 through 20) displays a status ofenabled. Zero connections displaysa status of disabled.

uicfg -tcm port_mode

where port_mode isenabled (1 connection),disabled (no connections),or a number between 0and 20, inclusive, thatindicates the maximumnumber of non-secure TCPsession connections.



-T system:mm[x]


Enable / disable secureTCP command mode

Enables or disables secure TCPcommand mode (used by IBMSystems Director) for themanagement module.

uicfg -stcm state




-T system:mm[x]



Table 84. uicfg command (continued)


Set number of secureTCP command modeconnections

Enable or disable the secure TCPcommand mode, or sets themaximum number of connectionsexplicitly.Notes:

v On a write operation, themaximum number ofconnections can be set explicitly(0-20), or it can be enabled (1connection) or disabled (0connections).

v On a read operation, disabledmeans 0 connections, andenabled means 1 or moreconnections.

v The total session count of TCMand STCM is limited to 20.

uicfg -stcm port_mode

where port_mode isenabled (1 connection),disabled (no connections),or a number between 0and 20, inclusive, thatindicates the maximumnumber of secure TCPsession connections.



-T system:mm[x]


Enable / disable webinterface

Enables or disables themanagement module web interface.

uicfg -web state




-T system:mm[x]


Example: To disable Secure TCP command mode for the management module,while management module 1 is set as the persistent command environment, at thesystem:mm[1]> prompt, typeuicfg -stcm disabled

To display the user interface configuration for the management module, whilemanagement module 1 is set as the persistent command environment, at thesystem:mm[1]> prompt, typeuicfg


The following example shows the information that is returned from these twocommands:system:mm[1]> uicfg -stcm disabledWarning: Communication with IBM Systems Director via Secure TCP Command Modehas been disabled.OKsystem:mm[1]> uicfg-cli enabled (telnet only)-snmp enabled-stcm enabled-tcm disabled-web enabledsystem:mm[1]>


update (update firmware) commandThis command updates firmware using the uniform resource locator (URL) of aTFTP, FTP, HTTP, or HTTPS server and displays information about firmwareinstalled in BladeCenter components.

Important:

v Some cluster solutions require specific code levels or coordinated code updates.If the device is part of a cluster solution, verify that the latest level of code issupported for the cluster solution before you update the code.

v Scalable complexes in a BladeCenter unit require a consistent firmware level onall blade servers in a complex. When scripting firmware updates for bladeservers in a scalable complex, make sure that the update commands are includedfor each node in the complex.

Table 85. update (update firmware) command


Display firmwareattributes

Displays attributes of the firmwareinstalled in the command target.Return values are:v Firmware typev Build IDv Filenamev Release datev Revision level

Notes:v When the command target is the

primary management module,this command will return thevalues for the currently activefirmware and for the pendingfirmware, that will become activeafter the next managementmodule reboot.

v For standby advancedmanagement modules, thereturned value will also indicateif a firmware update is inprogress and the percentage thatis complete.

v For I/O modules that support it,this command will also displayfirmware image information.

update -a -T system:mm[x]


-T system:switch[x]

where x is the primarymanagement-modulenumber, standbymanagement-modulenumber, blade serverbay number, or I/Omodule bay number.


Table 85. update (update firmware) command (continued)


Update firmware usingURL

Update firmware for the commandtarget using a uniform resourcelocator (URL).Important: Command authoritydefinitions might change betweenfirmware versions. Make sure thatthe command authority level set foreach user is correct after updatingmanagement-module firmware (see“Commands and user authority”on page 8).Notes:v Updating to older firmware

levels may cause loss of certainfunctionality

v The JS22 or JS12 blade serverfirmware is too large to beupdated using this command.See the User's Guide for yourJS22 or JS12 blade server forinformation about updatingfirmware.

update -u U_R_L

where U_R_L is fullyqualified uniform resourcelocator of a tftp, ftp, http,or https server where thefirmware update image islocated.






-T system:mm[x]


-T system:switch[x]

where x is the primarymanagement-module,blade server baynumber, orI/O-module baynumber.

Update firmware andreboot

Update firmware and reboot theadvanced management module touse new firmware if the updatesucceeds.Important: Command authoritydefinitions might change betweenfirmware versions. Make sure thatthe command authority level set foreach user is correct after updatingmanagement-module firmware.

update -u U_R_L -r




-T system:mm[x]

where x is the primarymanagement-module.




Update firmware(verbose)

Update firmware for the commandtarget, showing details of thefirmware download and flashoperations. The detailedinformation is not shown until theupdate is complete, which mighttake several minutes.Important: Command authoritydefinitions might change betweenfirmware versions. Make sure thatthe command authority level set foreach user is correct after updatingmanagement-module firmware.Notes:v Updating to older firmware

levels may cause loss of certainfunctionality

v The JS22 or JS12 blade serverfirmware is too large to beupdated using this command.See the User's Guide for yourJS22 or JS12 blade server forinformation about updatingfirmware.

update -u U_R_L -v







-T system:mm[x]


-T system:switch[x]

where x is the primarymanagement-module,blade server baynumber, orI/O-module baynumber.

Update I/O modulefirmware

Directly update I/O modulefirmware image.Note: Only some I/O moduleshave this capability.

update -u U_R_L -imgimg_index

where:v U_R_L is fully qualified

uniform resource locatorof a tftp, ftp, http, orhttps server where thefirmware update imageis located.

v img_index is the imageindex you are updating.Use the update -acommand to listavailable images andtheir index numbers.


administration


-T system:switch[x]





Update I/O modulefirmware (verbose)

Directly update I/O modulefirmware image, showing details ofthe firmware download and flashoperations. The detailedinformation is not shown until theupdate is complete, which mighttake several minutes.

update -u U_R_L -imgimg_index -v



v img_index is the imageindex to the I/Omodule firmware youare updating. Use theupdate -a command tolist available imagesand their indexnumbers.


administration


-T system:switch[x]


Activate I/O modulefirmware

Directly activate I/O modulefirmware image.Note: Only some I/O moduleshave this capability.

update -activateimg_index

where img_index is theimage index you areactivating. Use the update-a command to listavailable images and theirindex numbers.


administration


-T system:switch[x]





Update and activate I/Omodule firmware

Directly update I/O module andactivate the firmware image.Notes:v Only some I/O modules have

this capability.v The activate option can be used

with the other options. You canflash first, then activate thespecified index.

v The image index you activatecan be different from the oneyou update.

update -u U_R_L -imgimg_index -activateimg_index



v img_index is the imageindex you areactivating. Use theupdate -a command tolist available imagesand their indexnumbers.


administration


-T system:switch[x]





Update firmware

(Obsolete command. SeeNote following table.)

Update firmware for the commandtarget.Important: Command authoritydefinitions might change betweenfirmware versions. Make sure thatthe command authority level set foreach user is correct after updatingmanagement-module firmware.Note: The P6 blade serverfirmware is too large to be updatedusing this command. See the User'sGuide for your P6 blade server forinformation about updatingfirmware.

update -i ip_address -lfilelocation



v filelocation is the locationof the firmware updatefile.






-T system:mm[x]


-T system:switch[x]

where x is the primarymanagement-module,blade server baynumber, or I/O(switch) module baynumber.

Update firmware(verbose)


Update firmware for the commandtarget, showing details of thefirmware download and flashoperations. The detailedinformation is not shown until theupdate is complete, which mighttake several minutes.Important: Command authoritydefinitions might change betweenfirmware versions. Make sure thatthe command authority level set foreach user is correct after updatingmanagement-module firmware.Note: The P6 blade serverfirmware is too large to be updatedusing this command. See the User'sGuide for your P6 blade server forinformation about updatingfirmware.

update -i ip_address -lfilelocation -v









-T system:mm[x]


-T system:switch[x]

where x is the primarymanagement-module,blade server baynumber, or I/O(switch) module baynumber.




Update I/O modulefirmware


Directly update I/O modulefirmware image.Note: Only some I/O moduleshave this capability.

update -i ip_address -lfilelocation -img img_index




v img_index is the imageindex you are updating.Use the update -acommand to listavailable images andtheir index numbers.


administration


-T system:switch[x]

where x is the I/O(switch) module baynumber.




Update I/O modulefirmware (verbose)


Directly update I/O modulefirmware image, showing details ofthe firmware download and flashoperations. The detailedinformation is not shown until theupdate is complete, which mighttake several minutes.Note: Only some I/O moduleshave this capability.

update -i ip_address -lfilelocation -img img_index-v




v img_index is the imageindex to the I/Omodule firmware youare updating. Use theupdate -a command tolist available imagesand their indexnumbers.


administration


-T system:switch[x]


Activate I/O modulefirmware


Directly activate I/O modulefirmware image.Note: Only some I/O moduleshave this capability.

update -activateimg_index

where img_index is theimage index you areactivating. Use the update-a command to listavailable images and theirindex numbers.


administration


-T system:switch[x]





Update and activate I/Omodule firmware


Directly update I/O module andactivate the firmware image.Notes:v Only some I/O modules have

this capability.v The activate option can be used

with the other options. You canflash first, then activate thespecified index.

v The image index you activatecan be different from the oneyou update.

update -i ip_address -lfilelocation -img img_index-activate img_index




v img_index is the imageindex you areactivating. Use theupdate -a command tolist available imagesand their indexnumbers.


administration


-T system:switch[x]


Note: The -i and -l options for the update command have been replaced by the-u command option. While the -i and -l options will remain active for a fewreleases before being removed, users are encouraged to transition to the -u optionas soon as possible.

To accomplish this transition, the IP address and file location of the firmwareupdate file or image, specified by the arguments to the -i and -l options, must bereplaced by the -u option followed by an argument that specifies the fullyqualified uniform resource locator (URL) of a tftp, ftp, http, or https server wherethe firmware update file or image is located.

Example: To update the advanced management module firmware from a TFTPserver and reboot the advanced management module in management-module bay1 after a successful update, type the following command at the system:> prompt.For this example, the IP address of the TFTP server is 9.37.177.215 and thefirmware file containing the update is named CNETMNUS.pkt. The verbose modeand reboot flag are also specified.update -u tftp://9.37.177.215/temp/CNETMNUS.pkt -T mm[1] -v -r


The following example shows the information that is returned from the updatecommand:system> update -u tftp://9.37.177.215/temp/CNETMNUS.pkt -T mm[1] -v -r100% transferred (100/100)transfer completed successfullyflashing firmware to target deviceStarting flash packet preparation.Flash preparation - packet percent complete 4.Flash preparation - packet percent complete 8.Flash preparation - packet percent complete 12.Flash preparation - packet percent complete 16.Flash preparation - packet percent complete 20.Flash preparation - packet percent complete 24.Flash preparation - packet percent complete 28.Flash preparation - packet percent complete 32.Flash preparation - packet percent complete 36.Flash preparation - packet percent complete 40.Flash preparation - packet percent complete 44.Flash preparation - packet percent complete 50.Flash preparation - packet percent complete 54.Flash preparation - packet percent complete 58.Flash preparation - packet percent complete 62.Flash preparation - packet percent complete 66.Flash preparation - packet percent complete 70.Flash preparation - packet percent complete 74.Flash preparation - packet percent complete 78.Flash preparation - packet percent complete 82.Flash preparation - packet percent complete 86.Flash preparation - packet percent complete 90.Flash preparation - packet percent complete 94.Flash preparation - packet percent complete 98.Flash operation phase starting.Flashing - packet percent complete 34.Flashing - packet percent complete 50.Flashing - packet percent complete 50.Flashing - packet percent complete 50.Flashing - packet percent complete 50.Flashing - packet percent complete 50.Flashing - packet percent complete 50.Flashing - packet percent complete 50.Flashing - packet percent complete 82.Update of AMM Main Application firmware was successful.

The new firmware will become active after the next reset of the MM.

Rebooting AMM...


uplink (management module failover) commandThis command displays and configures the management-module uplink failoverfeature. If the external network interface of the primary management module fails,this feature forces a failover to the standby management module, if one is installed.

Note: This command does not apply to the BladeCenter S unit.

Table 86. uplink command


Display uplink failoverstatus

Displays the management-moduleuplink failover status (enabled ordisabled) and the failover delay.

uplink -T system

-T system:mm[x]


Set physical networkuplink failover delay

Sets the amount of time betweendetection of a management-modulephysical uplink failure and failoverto the standby managementmodule.

uplink -dps delay

where delay is from 10 to172800 seconds, inclusive.If you enter a valueoutside this range, anerror will be displayed.



-T system

-T system:mm[x]


Enable / disable physicaluplink failover

Enables or disables failover to thestandby management module if theexternal physical network interfaceof the primary managementmodule fails.

uplink -ep state




-T system

-T system:mm[x]



Table 86. uplink command (continued)


Set logical networkuplink failover delay

Sets the amount of time betweendetection of a management-modulelogical uplink failure and failoverto the standby managementmodule.

uplink -dls delay

where delay is from 60 to172800 seconds, inclusive.If you enter a valueoutside this range, anerror will be displayed.



-T system

-T system:mm[x]


Enable / disable logicaluplink failover

Enables or disables failover to thestandby management module if theexternal logical network interface ofthe primary management modulefails.

You must enter a non-zero IPaddress (-ip command option) orIPv6 IP address (-ip6 commandoption) for a device that themanagement module can access tocheck its logical network linkbefore you can enable logicaluplink failover.

uplink -el state




-T system

-T system:mm[x]


Set IP address to checklogical network uplink

Sets the IPv4 IP address of thedevice that the managementmodule accesses to check its logicalnetwork link.

uplink -ip ip_address

where ip_address is a validIPv4 IP address. You mustenter a non-zero IPv4 IPaddress, in dotted decimalIP address format, beforeyou can enable logicaluplink failover.



-T system

-T system:mm[x]



Table 86. uplink command (continued)


Set IPv6 IP address tocheck logical networkuplink

Sets the IPv6 IP address of thedevice that the managementmodule accesses to check its logicalnetwork link.

uplink -ip6 ip_address

where ip_address is a validIPv6 IP address. You mustenter a non-zero IPaddress, in IPv6 format,before you can enablelogical uplink failover.



-T system

-T system:mm[x]


Set logical link loss alertand failover policy

Sets the alert and failover policy forlogical link loss to check either theIPv4 IP address, the IPv6 IPaddress, or both of these IPaddresses.Note: The -alert command optionapplies only when both the -ip and-ip6 command options are set.

uplink -alert setting

where setting is:v either to check either

the IPv4 IP address orthe IPv6 IP address.

v both to check both theIPv4 IP address and theIPv6 IP address.



-T system

-T system:mm[x]


Example: To enable failover to the standby management module if the externalphysical network interface of a primary management module fails, whilemanagement module 1 is set as the persistent command environment, at thesystem:mm[1]> prompt, typeuplink -ep enabled


To display the uplink failover configuration, while management module 1 is set asthe persistent command environment, at the system:mm[1]> prompt, typeuplink

The following example shows the information that is returned from thesecommands:system:mm[1]> uplink -ep enabledOKsystem:mm[1]> uplinkFailover on network uplink loss is enabled for physical detectionUplink delay for physical detection: 60 seconds

Failover on network uplink loss is enabled for logical detectionUplink delay for logical detection: 1800 secondsDestination IP for MM to check its logical link: 1.1.1.0Destination IPv6 IP for MM to check its logical link: 1::2Alert and failover if both IPv4 and IPv6 link checks failsystem:mm[1]>


users commandThis command displays and configures user accounts, also called user profiles, ofthe primary management module.

Important: Command authority definitions might change between firmwareversions. Make sure that the command authority level set for each user is correctafter updating management-module firmware.

Table 87. users (management-module users) command


Display all user profiles Displays all 12management-module user profiles.Returned values are:v User namev Authority levelv Current log in or log out statev Password compliancev State of account (active or

inactive)v Number of SSH public keys

installed for user

users -T system:mm[x]


Display active users Displays all users that are currentlylogged in to the managementmodule. Returned values include:v User namev User IP addressv Connection type (SNMPv1,

SNMPv3, SSH, TCP commandmode, Telnet, Web)

v Session ID

users -curr -T system:mm[x]


Terminate user session Terminates the specified user loginsession.Note: The session ID is found byrunning the users -curr command.

users -ts sessionID

where sessionID is anumber that correspondsto the user session ID.


management


-T system:mm[x]



Table 87. users (management-module users) command (continued)


Display single userprofile

Displays the specifiedmanagement-module user profile.Returned values are:v User namev Authority levelv Context namev Authentication protocolv Privacy protocolv Access typev Hostname/IP addressv Maximum simultaneous sessions

allowedv Number of active sessionsv Password compliancev Password expiration datev Account statev Number of SSH public keys

installed for this userv Last time this user logged in

users -user_number

where user_number is anumber from 1 to 12 thatcorresponds to the usernumber assigned in the"Display all user profiles"list.

-T system:mm[x]


Delete user profile Delete the specifiedmanagement-module user profile.

users -user_number -clear

where user_number is anumber from 1 to 12 thatcorresponds to the usernumber assigned in the"Display all user profiles"list. It is possible to deletean empty user profile.


management


-T system:mm[x]





Disable user account Disable the specifiedmanagement-module user account.

users -user_number-disable





-T system:mm[x]


Enable user profile Enable a disabledmanagement-module user account.

users -user_number-enable





-T system:mm[x]





Unlock user profile Unlock a lockedmanagement-module user account.

users -user_number-unlock





-T system:mm[x]





Create user profile Create the specifiedmanagement-module user profile.

All fields must be specified whencreating a user profile for theBladeCenter T managementmodule.

For management modules otherthan those installed in aBladeCenter T unit, only thefollowing user-profile fields arerequired:v -user_numberv -n user_namev -a user_authorityv -p user_password

users -user_number

-n user_name -puser_password -auser_authority -cncontext_name -apauth_protocol -ppprivacy_protocol -ppwprivacy_pwd -at access_type-i ip_addr/hostname -msmax_sessions

where:v user_number is a number

from 1 to 12 thatcorresponds to anunused user number inthe "Display all userprofiles" list.

v user_name is analphanumeric string upto 15 characters inlength that can includeperiods ( . ) andunderscores ( _ ). Eachof the 12 user namesmust be unique.

v user_password can beblank or analphanumeric string upto 15 characters inlength that can includeperiods ( . ) andunderscores ( _ ), andmust include at leastone alphabetic and onenon-alphabeticcharacter.

v user_authority is one ofthe following:– operator (read-only)– rbs (see Set user

authority level formore information)


-T system:mm[x]





Create user profile

(continued)

v context_name is analphanumeric string upto 31 characters inlength that can includeperiods ( . ) andunderscores ( _ ).

v auth_protocol choices are:– md5– sha– none

v privacy_protocol choicesare:– des– aes– none

v privacy_pwd is analphanumeric string upto 31 characters inlength that can includeperiods ( . ) andunderscores ( _ ).

v access_type choices are:– get– set– trap

v ip_addr/hostname is up to63 characters in length.

v max_sessions is anumber from 0 to 20.


management





Set user name Sets a user name in the specifiedmanagement-module user profile.

users -user_number -nuser_name


from 1 to 12 thatcorresponds to the usernumber assigned in the"Display all userprofiles" list.

v user_name is aalphanumeric string upto 15 characters inlength that can includeperiods ( . ) andunderscores ( _ ). Eachof the 12 user namesmust be unique.


management


-T system:mm[x]





Set user password Sets a user password in thespecified management-module userprofile.

users -user_number -puser_password



v user_password can beblank or analphanumeric string upto 15 characters inlength that can includeperiods ( . ) andunderscores ( _ ), andmust include at leastone alphabetic and onenon-alphabeticcharacter.


management


-T system:mm[x]





Change user password Changes the user password in thespecified management-module userprofile.Note: Users can change their ownpassword even if they do not haveauthority to manage accounts. The-op option is only used whenchanging your own password

users -user_number -opold_password -pnew_password



v old_password is thecurrent password forthe specified user.

v new_password can beblank or analphanumeric string upto 15 characters inlength that can includeperiods ( . ) andunderscores ( _ ), andmust include at leastone alphabetic and onenon-alphabeticcharacter.


management


-T system:mm[x]





Set user authority level Sets a user authority level in thespecified management-module userprofile.

users -user_number -auser_authority



v user_authority is one ofthe following:– operator (read-only)– rbs (custom)

The custom authority levelparameter is specifiedusing the followingsyntax:

rbs:levels:devices

where the levels are one ormore of the followingauthority levels, separatedby a vertical bar ( | ):v super (Supervisor)v cam (Chassis User

Account Management)v clm (Chassis Log

Management)v co (Chassis Operator)v cc (Chassis

Configuration)v ca (Chassis

Administration)v bo (Blade Operator)v brp (Blade Remote

Present)v bc (Blade Configuration)v ba (Blade

Administration)v so (I/O Module

Operator)v sc (I/O Module

Configuration)v sa (I/O Module

Administration)


-T system:mm[x]





Set user authority level

(continued)

Notes:

v The LDAP authority levels arenot supported by themanagement-module webinterface.

v To use the LDAP authoritylevels, make sure that the versionof LDAP security used by themanagement module is set to v2(enhanced role-based securitymodel). See “ldapcfg command”on page 210 for information.

The levels can also includeone or more of thefollowing authority levelswhen using LDAP.v brpv (Blade Remote

Presence View Video)v brpk (Blade Remote

Presence KVM)v brpr (Blade Remote

Presence Remote DriveRead)

v crpru (Blade RemotePresence Remote DriveRead or Write)

v rps (Remote PresenceSupervisor)

where the devices are oneor more of the followingdevices, separated by avertical bar ( | ). Rangesof devices are separatedby a dash ( - ).v cn (Chassis n, where n

is a valid chassisnumber. Use c1 forsingle-chassisenvironments.)

v bn (Blade n, where n isa valid blade baynumber in the chassis)

v sn (I/O module n,where n is a valid I/Omodule bay number inthe chassis)


management





Set maximum number ofsimultaneous sessionsfor user

Sets the maximum number ofsimultaneous login sessions for thespecified user.

users -user_number -msmax-session



v max-session is a numberfrom 0 to 20 that setsthe maximum numberof simultaneous sessionsfor the user. A value of0 means that there is nosession limit for theuser.


management


-T system:mm[x]


Set SNMPv3 usercontext name

Sets an SNMPv3 context name inthe specified management-moduleuser profile.

The context name defines thecontext the SNMPv3 user isworking in. A context name can beshared by multiple users.

users -user_number -cncontext_name



v context_name is a stringup to 31 characters inlength. Each of the 12context names must beunique.


management


-T system:mm[x]





Set SNMPv3 userauthentication protocol

Sets the SNMPv3 authenticationprotocol to be used for thespecified management-module userprofile.

users -user_number -apauth_protocol



v auth_protocol is:– sha– md5– none


management


-T system:mm[x]


Set SNMPv3 userprivacy protocol

Sets the SNMPv3 privacy protocolto be used for the specifiedmanagement-module user profile.

If the privacy protocol is set tonone, no -ppw command option(privacy password) is required.

users -user_number -ppprivacy_protocol



v privacy_protocol is:– aes– des– none


management


-T system:mm[x]





Set privacy password forSNMPv3 user

Sets an SNMPv3 privacy passwordin the specifiedmanagement-module user profile.

users -user_number -ppwprivacy_pwd



v privacy_pwd is a stringup to 31 characters inlength.


management


-T system:mm[x]


Set access type forSNMPv3 user

Sets an SNMPv3 access type for thespecified management-module userprofile.

This command supports thefollowing access types:v get: the user can query

Management Information Base(MIB) objects and receive traps.

v set: the user can query and setMIB objects and receive traps.

v trap: the user can only receivetraps.

users -user_number -ataccess_type



v access_type is– get– set– trap


management


-T system:mm[x]





Set IP address orhostname for SNMPv3trap receiver

Sets the IP address or hostnamethat will receive SNMPv3 traps forthe specified management-moduleuser profile.

users -user_number -iip_addr/hostname



v ip_addr/hostname is avalid static IP addressor an alphanumerichostname string up to63 characters in length.


management


-T system:mm[x]


Display SSH public key Displays the entire specified SSHpublic key for the specified user inOpenSSH format.Note: The -pk and -e options mustbe used exclusive of all other userscommand options.

users -user_number -pk-key_index -e



v key_index identifies thekey number from 1 to12 to display. If the-key_index is all, thenall keys for the user aredisplayed.


management


-T system:mm[x]





Add SSH public key Adds an SSH public key for thespecified user.Notes:

v The -pk and -add options mustbe used exclusive of all otherusers command options.

v The SSH Public Key is added tothe first available storagelocation. Each advancedmanagement module cansupport up to 12 SSH publickeys.

v Each user is permitted amaximum of four SSH publickeys, if the space is available.

users -user_number -pk-add key



v key is a valid key inOpenSSH format.


management


-T system:mm[x]


Add specific SSH publickey

Adds a specific SSH public key forthe specified user.Note: The -pk and -add optionsmust be used exclusive of all otherusers command options.

users -user_number -pk-key_index -add key



v key_index identifies thekey number from 1 to12 to add.

v key is a valid key inOpenSSH format.


management


-T system:mm[x]





Remove SSH public key Removes an SSH public key for thespecified user.Note: The -pk and -remove optionsmust be used exclusive of all otherusers command options.

users -user_number -pk-key_index -removev user_number is a number


v key_index identifies thekey number from 1 to12 to remove. If the-key_index is "all", thenall keys for the user areremoved.


management


-T system:mm[x]





Upload SSH public key Uploads a new SSH public key. users -user_number -pk-upld -i ip_addr/hostname-l filenamev user_number is a number


v ip_addr/hostname is avalid static IPv4 or IPv6IP address or analphanumeric hostnamestring up to 63characters in length ofthe TFTP server.

v filename is the filenameof the key file. Keysmust be in OpenSSHformat.


management


-T system:mm[x]





Replace SSH public key Replaces an existing SSH publickey.

users -user_number -pk-key_index -upld -iip_addr/hostname -lfilenamev user_number is a number


v key_index identifies thekey number from 1 to12 to replace.


v filename is the filenameof the key file. Keysmust be in OpenSSHformat.


management


-T system:mm[x]





Download SSH publickey

Downloads a specific SSH publickey to a TFTP server.Note: The -pk and -dnld optionsmust be used exclusive of all otherusers command options.

users -user_number -pk-key_index -dnld -iip_addr/hostname -lfilenamev user_number is a number

from 1 to 12 thatcorresponds to the usernumber assigned in theDisplay all userprofiles list.

v key_index identifies thekey number from 1 to12 to upload.


v filename is the filenameof the key file.


management


-T system:mm[x]





Connect to SSH publickey

Accept connections from SSHpublic key host.

users -user_number -pk-key_index -af from="list"v user_number is a number


v key_index identifies thekey number from 1 to12 to connect.

v "list" is acomma-separate list ofhostnames and IPaddresses. The list is analphanumeric string upto 511 characters inlength that can includealphanumericcharacters, commas,asterisks, questionmarks, exclamationpoints, periods, andhyphens. The stringmust be enclosed indouble-quotes.


management


-T system:mm[x]





Comment SSH publickey

Add comment to an SSH publickey.

users -user_number -pk-key_index -cm "comment"v user_number is a number


v key_index identifies thekey number from 1 to12 to comment.

v "comment" is up to 255characters in length,enclosed indouble-quotes.


management


-T system:mm[x]


Example: To create user number 3 with a user name of user3 who has supervisorrights to all BladeCenter components, while management module 1 is set as thepersistent command environment, at the system:mm[1]> prompt, typeusers -3 -n user3 -p passw0rd -a rbs:super:c1|b1-b14|s1-s4 -cn joe -ap md5 -pp des

-ppw passw0rd -at get -I 192.168.70.129

Note: The entry beginning with users -3 -n... is shown with a line break after-pp des. When this command is entered, the entire entry must all be on one line.

To display all users, while management module 1 is set as the persistent commandenvironment, at the system:mm[1]> prompt, typeusers

The following example shows the information that is returned from thesecommands:

Note: The entry beginning with users -3 -n... is shown with a line break after-a rbs:super:c1|b1-b14|s1-s4. When this command is entered, the entire entrymust all be on one line.system:mm[1]> users -3 -n user3 -p passw0rd -a rbs:super:c1|b1-b14|s1-s4-cn joe -ap md5 -pp des -ppw passw0rd -at get -I 192.168.70.129OK

system:mm[1]> users0 active session(s)Password compliantAccount active


Role:camBlades:1|2|3|4|5|6|7|8|9|10|11|12|13|14Chassis:1Modules:1|2|3|4|5|6|7|8|9|10

There are no SSH public keys installed for this user2. kprevent0 active session(s)Password compliantAccount active

Role:supervisorBlades:1|2|3|4|5|6|7|8|9|10|11|12|13|14Chassis:1Modules:1|2|3|4|5|6|7|8|9|10

There are no SSH public keys installed for this user3. johnh0 active session(s)Password compliantAccount active


There are no SSH public keys installed for this user4. toms1 active session(s)Password compliantAccount active


Number of SSH public keys installed for this user: 35. <not used>6. <not used>7. <not used>8. <not used>9. <not used>10. <not used>11. <not used>12. <not used>system:mm[1]>


volts commandThis command displays actual voltages and voltage threshold values forBladeCenter components.

Table 88. volts command


Display voltage values Displays the current voltage andvoltage threshold settings for thespecified component:v The management module target

displays the voltage values forthe BladeCenter unit.

v The blade server target displaysthe internal voltage values forthe specified blade server.

Note: The voltage values thatdisplay will vary based onBladeCenter unit and blade servertype.

volts -T system:mm[x]

-T system:blade[x]


Example: To view the current voltage and voltage thresholds for the blade serverin bay 3, while this blade server is set as the persistent command environment, atthe system:blade[3]> prompt, typevolts

The following example shows the information that is returned from this command:system:blade[3]> volts

Source Value Warning----------- ------- ----------------1.8V Sense +1.79 (+1.61,+1.97)1.8VSB Sense +1.83 (+1.61,+1.97)12V Sense +12.33 (+10.79,+13.21)12VSB Sense +12.30 (+10.74,+13.19)3.3V Sense +3.31 (+2.96,+3.62)5V Sense +5.06 (+4.39,+5.48)system:blade[3]>


write commandThis command saves the management-module configuration to the chassis of theBladeCenter unit or to a file.

Table 89. write command


Savemanagement-moduleconfiguration to chassis

Saves an image of themanagement-module configurationto the BladeCenter unit chassis.

write -config chassis



-T system:mm[x]


Savemanagement-moduleconfiguration to file (noencryption)

Saves an image of themanagement-module configurationto a file while data encryption isnot enabled for the BladeCenterunit.

write -config file -lfilename -i ip_address




Note: If the -l filenameoption is not specified, thedefault filename ofasm.cfg is used.



-T system:mm[x]



Table 89. write command (continued)


Savemanagement-moduleconfiguration to file(encryption)

Saves an image of themanagement-module configurationto a file while data encryption isenabled for the BladeCenter unit.Note: When a configuration file iscreated with a pass-phrase(encryption enabled), if thisconfiguration file is restored on thesame management module, thepass-phrase entered duringrestoration is ignored.

write -config file -lfilename -i ip_address -ppassphrase




v passphrase is adouble-quote delimitedpass-phrase that will beneeded to restore theconfiguration file.Maximum pass-phraselength is 1600characters.

Note: If the -l filenameoption is not specified, thedefault filename ofasm.cfg is used.



-T system:mm[x]


Example:

To save the management-module configuration to an image on the BladeCenterchassis, while management module 1 is set as the persistent commandenvironment, at the system:mm[1]> prompt, typewrite -config chassis

The following example shows the information that is returned from this command:system:mm[1]> write -config chassisOKConfiguration settings were successfully saved to the chassissystem:mm[1]>


zonecfg commandThis command sets and displays the serial attached SCSI (SAS) device informationfor BladeCenter components that is stored in I/O modules that support thisfeature.

Table 90. zonecfg command


Display SAS zone list Displays a list of SAS device zonesand their information that is storedin the specified I/O module.

zonecfg -T system:switch[x]


Activate SAS zone -single SAS switch

Activates a SAS zone, selected byindex number, for the specifiedSAS switch module.Note: If the I/O module is not inan operating condition that allowsa zone to be activated, thecommand returns an advisorymessage.

zonecfg -activate zone

where zone is the indexnumber for a valid zone.Use the zonecfgcommand, with nooptions, to list valid zonesand their index numbers.


configuration


-T system:switch[x]


Activate SAS zone - allSAS switches

Activates a SAS zone, selected byindex number, for all SAS switchmodules.Note: If the I/O module is not inan operating condition that allowsa zone to be activated, thecommand returns an advisorymessage.

zonecfg -activate zone

where zone is the indexnumber for a valid zone.Use the zonecfgcommand, with nooptions, on all I/Omodules to determine thevalid zones that arecommon to all SAS switchmodules and their indexnumbers.


configuration


-T system


Table 90. zonecfg command (continued)


Display SAS zoneinformation

Displays information about a SASzone, selected by index number,that is stored in the specified I/Omodule.

zonecfg -view zone

where zone is the indexnumber for a valid zone.

-T system:switch[x]


Note: If you install both RAID SAS (RSS) and Non-RAID SAS (NSS) mass storagedevices, you can only power on and manage the zone configuration for one at atime.

Example: To view the list of SAS zones stored in the I/O module in bay 1, whilethis I/O module is set as the persistent command environment, at thesystem:switch[1]> prompt, typezonecfg

To activate SAS zone 5 for the I/O module in bay 1, while this I/O module is setas the persistent command environment, at the system:switch[1]> prompt, typezonecfg –activate 5

The following example shows the information that is returned from thesecommands:system:switch[1]> zonecfgIndex: 3Name: Name3Description string for zone config 3Status: InactiveType: PredefinedDate: <mm>

Index: 5Name: Name5Description string for zone config 5Status: InactiveType: ConfigurableDate: <mm>


Index: 24Name: Name24Description string for zone config 24Status: ActiveType: ConfigurableDate: <mm>system:switch[1]> zonecfgIndex: 3Name: Name3Description string for zone config 3Status: InactiveType: PredefinedDate: <mm>

Index: 5


Name: Name5Description string for zone config 5Status: PendingType: ConfigurableDate: <mm>


Index: 24Name: Name24Description string for zone config 24Status: ActiveType: ConfigurableDate: <mm>system:switch[1]> zonecfg –activate 5OKsystem:switch[1]>



Chapter 4. Error messages

This topic lists error messages for the BladeCenter command-line interface.

The command-line interface provides error messages specific to each command.The following topics list the common error messages that apply to all commandsand command-specific error messages, along with their definitions.v “Common errors” on page 409v “accseccfg command errors” on page 411v “advfailover command errors” on page 412v “alarm command errors” on page 413v “alertcfg command errors” on page 414v “alertentries command errors” on page 414v “autoftp command errors” on page 415v “baydata command errors” on page 415v “bofm command errors” on page 416v “boot command errors” on page 417v “bootmode command errors” on page 417v “bootseq command errors” on page 418v “buildidcfg command errors” on page 418v “chconfig command errors” on page 419v “chlog command errors” on page 420v “chmanual command errors” on page 421v “cin command errors” on page 421v “clear command errors” on page 423v “clearlog command errors” on page 423v “clock command errors” on page 423v “config command errors” on page 424v “console command errors” on page 425v “dhcpinfo command errors” on page 426v “displaylog command errors” on page 426v “displaysd command errors” on page 427v “dns command errors” on page 428v “env command errors” on page 428v “ethoverusb command errors” on page 428v “eventinfo command errors” on page 429v “events command errors” on page 429v “exit command errors” on page 430v “feature command errors” on page 430v “files command errors” on page 432v “fuelg command errors” on page 433v “groups command errors” on page 436v “health command errors” on page 436v “help command errors” on page 437


v “history command errors” on page 437v “identify command errors” on page 437v “ifconfig command errors” on page 438v “info command errors” on page 442v “iocomp command errors” on page 443v “kvm command errors” on page 443v “ldapcfg command errors” on page 443v “led command errors” on page 444v “list command errors” on page 445v “modactlog command errors” on page 445v “monalerts command errors” on page 445v “monalertsleg command errors” on page 446v “mcad command errors” on page 445v “mt command errors” on page 446v “nat command errors” on page 446v “ntp command errors” on page 447v “ping command errors” on page 447v “pmpolicy command errors” on page 448v “portcfg command errors” on page 448v “ports command errors” on page 448v “power command errors” on page 450v “rdoc command errors” on page 450v “read command errors” on page 451v “remotechassis command errors” on page 452v “reset command errors” on page 452v “scale command errors” on page 453v “sddump command errors” on page 454v “sdemail command errors” on page 454v “security command errors” on page 455v “service command errors” on page 455v “shutdown command errors” on page 455v “slp command errors” on page 455v “smtp command errors” on page 455v “snmp command errors” on page 456v “sol command errors” on page 457v “sshcfg command errors” on page 458v “sslcfg command errors” on page 459v “syslog command errors” on page 461v “tcpcmdmode command errors” on page 462v “telnetcfg command errors” on page 462v “temps command errors” on page 463v “thres command errors” on page 463v “trespass command errors” on page 463v “uicfg command errors” on page 464v “update command errors” on page 465


v “uplink command errors” on page 467v “users command errors” on page 468v “volts command errors” on page 472v “write command errors” on page 472v “zonecfg command errors” on page 473

Common errorsThis topic lists error messages that apply to all commands.

Each command that has unique errors will also have a list of command-specificerror messages.

Table 91. Common errors

Error message Definition

Alarm panel card is not present in this slot. The user tries to issue a command to an empty alarmpanel card slot.

Backplane Mux card is not present in this slot. The user tries to issue a command to an emptybackplane mux card slot.

Command cannot be issued to this target. Type env - hfor help on changing targets.

The user tries to issue a command to a target that doesnot support that command.

Command line contains extraneous arguments. Extra command arguments were entered.

Duplicate option: option

where option identifies the command option that wasentered more than once.

A user tries to enter the same command option in asingle command multiple times. For example, dns -i192.168.70.29 -i

Each option can only be used once per command. A user tries to enter the same command option in asingle command multiple times. For example, env -Tsystem:blade[4] -T system:blade[5].

Error: Command not recognized. Type 'help' to get a listof supported commands.

A user tries to enter a command that does not exist.

Error reading data for the option - option

where option identifies the command option that isreturning an error.

An error occurs while the management module isreading data of a option.

Error writing data for the option option

where option identifies the command option that isreturning an error.

An error occurs while the management module iswriting a command option value.

Firmware update is in progress. Try again later. Firmware update is in progress.

Illegal option: option

where option identifies the illegal short command optionthat was entered.

An illegal short command option is entered.

Integer argument out of range (range - range) for option:argument

where:v range identifies the range limitsv option identifies the command optionv argument identifies the integer that is out of range

An integer is entered that is out of range.

Internal error. An internal error occurs.

Chapter 4. Error messages 409

Table 91. Common errors (continued)


Invalid integer argument for option: argument

where:v option identifies the command optionv argument identifies the invalid argument

An invalid integer is entered.

Invalid option. An invalid command option is entered.

Invalid option argument for option: argument

where:v option identifies the command optionv argument identifies the invalid argument

An invalid argument for a command option is entered.

Invalid option for this target: option

where option identifies the option that is invalid.

A user tries to issue a command with an invalid optionfor the target.

Invalid parameter. Input must be numeric. A user tries to enter a non-numeric argument.

Invalid syntax. Type command - h for help.

where command identifies the command that is returningan error.

A user tries to enter a command that is not syntacticallycorrect.

Invalid target path. A user tries to issue a command to a target that is notvalid.

Long option option requires an argument

where option identifies the long command option that ismissing an argument.

A long command option is entered without a requiredargument.

Missing option name A dash (-) is entered without a command option name.

Network Clock card is not present in this slot. The user tries to issue a command to an empty networkcard slot.

Read/write command error. An error occurs while the management module isexecuting the command.

Short option option requires an argument

where option identifies the short command option that ismissing an argument.

A short command option is entered without a requiredargument.

Syntax error. Type command -h for help.

where command identifies the command that is returningan error.

A user tries to enter a command improperly.

That blade is presently not available. Please try againshortly.

A user tries to connect to a blade that is already in use.

The argument for the option arg is outside the validrange.

where arg identifies the command option that is out ofrange.

A user tries to enter an arg outside the option's validrange.

The target bay is empty. The user tries to issue a command to an empty bladebay, blower bay, I/O-module bay, management-modulebay, or power bay.

The target bay is out of range. A user tries to issue a command to a target that is out ofrange for that target. For example, the env -Tsystem:blade[15] command is out of range because theBladeCenter unit has only 14 blade bays.


Table 91. Common errors (continued)


The target slot is out of range. The user tries to issue a command to a target which isout of range for that target.

There is no blade present in that bay. The user tries to issue a command to an empty bladebay.

There is no blower present in that bay. The user tries to issue a command to an empty chassiscooling unit bay.

There is no management module present in that bay. The user tries to issue a command to an emptymanagement module bay.

There is no power source present in that bay. The user tries to issue a command to an empty powermodule bay.

There is no switch present in that bay. The user tries to issue a command to an empty I/Omodule bay.

Unknown long option: option

where option identifies the command option that isunknown.

A user tries to enter a long option that is not valid forthe command.

Unknown option: option

where option identifies the command option that isunknown.

An unknown option is used.

Unrecognized long option: option

where option identifies the illegal long command optionthat was entered.

An illegal long command option is entered.

Unsupported target type. A user tries to issue a command to an unsupportedtarget.

User does not have the authority to issue this command. A user lacks the authority level necessary to execute acommand.

accseccfg command errorsThis topic lists error messages for the accseccfg command.

See “Common errors” on page 409 for a list of error messages that apply to allcommands.

Table 92. accseccfg command errors


'Password required' is currently disabled. A user without a password tries to change the securitylevel to -high. User must have a password to performthis action.

'Password required' is currently enabled. A user without a password tries to change the securitylevel to -legacy. User must have a password to performthis action.

Reading account security level failed. An error occurs while the management module isreading the security level.

Setting account defaults to high level failed. An error occurs while the management module is settingthe security level to -high.


Table 92. accseccfg command errors (continued)


Setting account defaults to legacy level failed. An error occurs while the management module is settingthe security level to -legacy.

The -high option cannot be used with other options. The user tries to set the account security to high settingswhile changing individual option values.

The -legacy option cannot be used with other options. The user tries to set the account security to legacysettings while changing individual option values.

The account inactivity disable time period must begreater than the account inactivity alert time period.

A user tries to set the account inactivity disable timeperiod to be less than the account inactivity alert timeperiod.

The argument for the option -dc is outside the validrange.

The user tries to set the -dc option to a value outside ofits valid range.

The argument for the option -ia is outside the validrange.

The user tries to set the -ia option to a value outside ofits valid range.

The argument for the option -id is outside the validrange.

The user tries to set the -id option to a value outside ofits valid range.

The argument for the option -lf is outside the validrange.

The user tries to set the -lf option to a value outside ofits valid range.

The argument for the option -lp is outside the validrange.

The user tries to set the -lp option to a value outside ofits valid range.

The argument for the option -pe is outside the validrange.

The user tries to set the -pe option to a value outside ofits valid range.

The argument for the option -rc is outside the validrange.

The user tries to set the -rc option to a value outside ofits valid range.

The minimum password change interval must be lessthan the password expiration period (%d days or %dhours).

A user tries to set the -pc option to a value greater thanthe -pe option.

The password expiration period (%d days or %d hours)must be greater than the minimum password changeinterval.

A user tries to set the -pe option to a value less than the-pc option.

User must have a password to change the 'Passwordrequired' setting.

A user without a password tries to change the -proption.

advfailover command errorsThis topic lists error messages for the advfailover command.


Table 93. advfailover command errors


Operation failed. An error occurs while the management module isprocessing the command.

Operation not allowed, since the standby MM is notpresent.

The user tries to enable advanced failover when there isno standby management module installed in theBladeCenter unit.


Table 93. advfailover command errors (continued)


Unknown option: option

where option identifies the illegal command option thatwas entered.

The user tries to enter an illegal command option.

alarm command errorsThis topic lists error messages for the alarm command.


Table 94. alarm command errors


A duplicate option is found in the requested command. A duplicate argument is entered.

Alarm Description must be provided for setting analarm.

The user tries to set an alarm without providing analarm description.

Alarm ID must be from 1 to 255. An invalid alarm ID is entered.

Category must be from 1 to 255. An invalid category argument is entered.

Generator ID must be from 1 to 255. An invalid generator ID is entered.

Generator ID must be provided. A generator information ID is provided without agenerator ID.

Module ID must be from 1 to 255. An invalid module ID is entered.

No active alarm. No active alarm is found for the command target.

No matching alarm. No matching alarm is found for the command target.

Reading system health summary failed. An error occurs while the management module is gettingthe system health summary.

Severity level must be provided for setting an alarm. The user tries to set an alarm without specifying theseverity level.

Software Generator ID must be from 1 to 255. The user tries to enter an invalid generator information.

The entered Alarm Key is not in proper format. The user tries to enter an invalid alarm key.

Unable to acknowledge the requested alarm. An error occurs while the management module isacknowledging an alarm.

Unable to clear the requested alarm. An error occurs while the management module isclearing an alarm.

Unable to set the requested alarm. An error occurs while the management module is settingan alarm.


alertcfg command errorsThis topic lists errors for the alertcfg command.

There are no unique errors for the alertcfg command. See “Common errors” onpage 409 for a list of error messages that apply to all commands.

alertentries command errorsThis topic lists error messages for the alertentries command.


Table 95. alertentries command errors


-test must be used exclusive of other options. The user tries to issue a command with the -test optionat the same time as the other options.

An entry cannot be modified and deleted in the samecommand.

A user tries to modify an entry and delete it in the samecommand.

Arguments containing spaces must be enclosed inquotation marks.

A user tries to enter a string containing spaces that hasan opening quotation mark without a closing quotationmark.

Enabling the application alert failed. An error occurs while the management module isenabling the application alert.

Generating test alert failed. An error occurs while the management module isgenerating a test alert.

Invalid input. Angle brackets are not allowed in thename field.

A user tries to enter a string parameter containing < or >for the -n (name) command option.

Invalid option. An invalid command option is entered. This includesnumeric options for the alert recipient that are not from 1through 12.

Invalid parameter. Input must be numeric. A user tries to enter a parameter value containingnon-numeric characters for a command option requiringnumeric input.

Restoring previous configured value for the applicationalert failed.

An error occurs while the management module isrestoring previous configured value for the applicationalert.

Syntax error. -e can only be used in conjunction with theemail argument.

A user tries to enter an invalid email address for the -ecommand option.

Syntax error. -i can only be used in conjunction with thedirector argument.

A user tries to enter an invalid IP address for the -icommand option.

Syntax error. Type alertentries -h for help. An alert entry number is entered without the leadingdash ( - ).

The name must be less than 32 characters long. A user tries to enter too many characters in an inputfield.

When creating a new entry, all options are required. A required command option is missing when creating auser.


autoftp command errorsThis topic lists errors for the autoftp command.


Table 96. autoftp command errors


Autoftp is disabled, -i, -p, -u and -pw options areinvalid.

A user tries to enter -i, -p, -u, or -pw options when theFTP/TFTP mode is set to disabled.

Invalid FTP/TFTP address. A user tries to enter an FTP or TFTP address that is notvalid.

Invalid input. Address must be less than 64 characters. A user tries to enter an address that is 64 or morecharacters long.

Invalid input. Password must be less than 64 characters. A user tries to enter a password that is 64 or morecharacters long.

Invalid input. Userid must be less than 64 characters. A user tries to enter a user id that is 64 or morecharacters long.

Password must be enclosed in quotation marks.Displayed when the argument of option -p is notquote_delimited.

A user tries to enter a password without quotationmarks.

Read autoftp configuration failed. The management module was unable to read the autoftpconfiguration.

Read autoftp mode failed. The management module was unable to read the autoftpmode status.

The mode is tftp, -u and -pw options are invalid. A user tries to enter a user name or password when themode is set to TFTP.

User Name must be enclosed in quotation marks. A user tries to enter a user name without quotationmarks.

When disabling autoftp, the -i, -p, -u and -pw optionsare invalid.

A user tries to enter -i, -p, -u, or -pw options whensetting the FTP/TFTP mode to disabled in the samecommand.

When setting -m to tftp, the -u and -pw options areinvalid.

A user tries to enter a user name or password whensetting the FTP/TFTP mode to TFTP in the samecommand.

baydata command errorsThis topic lists error messages for the baydata command.


Table 97. baydata command errors


Error writing bay data to blade bay bayNum.

where bayNum is the blade bay number.

An internal error occurs while the user is changing baydata for the specified blade server.

Invalid blade bay number The command has an invalid bay number.


Table 97. baydata command errors (continued)


Invalid input. The bay data string must be less than themaximum number of characters allowed.

User enters bay data with -data option for a blade serverthat exceeds the maximum length of 60 characters.

The -clear and -data options cannot be used in the samecommand.

User issues a command with both -clear and -dataoptions.

The bay data must be quote-delimited. User enters bay data with -data option for a blade serverwithout double quotation marks.

User not authorized to change bay data for bay number. An unauthorized user issues a command to change baydata for the specified blade server.

bofm command errorsThis topic lists errors for the bofm command.

Notes:

1. The BOFM command displays parsing errors and duplicate addresses thatpoint to flaws in the comma-separated values (csv) configuration database file.The BladeCenter Open Fabric Manager is not a standard management modulefeature; it is offered and documented separately. See the BladeCenter Open FabricManager Installation and Users Guide for more detailed information.

2. If the number of advanced management module TCP command modeconnections is zero, or if all available TCP command mode connections are inuse, a connection failure message is generated by the BOFM feature. Make surethat the advanced management module TCP command mode connection limitis positive and that no more than the available number of connections are inuse. See the BladeCenter Open Fabric Manager Installation and Users Guide foradditional information.


Table 98. bofm command errors


Applying new configuration on MM failed. An error occurs while the advanced managementmodule is applying the BOFM configuration.

Confirming configuration change failed. An error occurs while the advanced managementmodule is confirming a configuration change.

File transfer failed. An error occurs while transferring a file during fileupload.

Getting BOFM status failed. An error occurs while the advanced managementmodule is getting BOFM status.

Getting duplicates failed. An error occurs while the advanced managementmodule is getting duplicates.

Getting parsing errors failed. An error occurs while the advanced managementmodule is getting parsing errors.

-i and -l are both required to upload a BOFMconfiguration file.

A user issues a command to apply BOFM configurationto the advanced management module without both -iand -l options.


Table 98. bofm command errors (continued)


Login failed. Login fails while the management module is applyingthe BOFM configuration to the advanced managementmodule.

Parsing errors. An error occurs while the advanced managementmodule is parsing the BOFM status.

Resetting BOFM configuration on MM failed. An error occurs while the advanced managementmodule is resetting the BOFM configuration.

Retrieving the file from TFTP server failed. An error occurs while the advanced managementmodule is retrieving the configuration file from a TFTPserver.

Update Failed, there was a problem retrieving the file. An error occurs while the advanced managementmodule is uploading a file.

boot command errorsThis topic lists errors for the boot command.

There are no unique errors for the boot command. See “Common errors” on page409 for a list of error messages that apply to all commands.

bootmode command errorsThis topic lists errors for the bootmode command.


Table 99. bootmode command errors


Boot mode not supported on blade[x]

where x is the number of the blade-server bay.

The command is directed to a blade server that does notsupport the bootmode feature.

Error retrieving the boot mode of this blade. The management module is unable read the boot modeof the blade server.

Set the blade boot mode to option failed

where option is the selected boot mode.

The management module is unable to set the bladeserver boot mode to the specified value.


bootseq command errorsThis topic lists error messages for the bootseq command.


Table 100. bootseq command errors


Error writing boot sequence. An error occurs while the management module isprocessing the command.

First device cannot be set to 'nodev'. The user tries to set the first boot device to 'nodev'.

Invalid device for this blade or chassis. The user tries to set a boot device to an invalid choice.

No duplicate settings are allowed. The user tries to set multiple slots in the boot sequenceto the same device.

Second device cannot be set to 'nodev' when third orfourth device is set.

The user tries to set the second boot device to 'nodev'.

Third device cannot be set to 'nodev' when fourth deviceis set.

The user tries to set the third boot device to 'nodev'.

buildidcfg command errorsThis topic lists error messages for the buildidcfg command.


Table 101. buildidcfg command errors


-create must be used exclusive of other options. A user tries to create the blade firmware build ID listwhile using another command option. The -createcommand option must be run alone.

Adding an entry failed. Please check for duplicates or aninvalid format.

An error occurs while adding an entry to the bladefirmware build ID list.

Build ID must be enclosed in quotation marks. A user tries to enter a blade firmware build ID withoutquotation marks.

Build revision must be enclosed in quotation marks. A user tries to enter a blade firmware build revisionwithout quotation marks.

Error creating the initial build ID list. An error occurs while creating the blade firmware buildID list.

Error removing all the build ID entries. An error occurs while removing all blade firmware buildID list entries.

Error removing build ID entry identifier.

where the identifier identifies the build ID entry specified.

An error occurs while removing a blade firmware buildID list entry.

Importing list failed. Check for duplicates or an invalidformat on line line_number

where the line_number identifies the line numberspecified.

An error occurs during blade firmware build ID listimport.

Machine type must be enclosed in quotation marks. A user tries to enter a machine type without quotationmarks.


Table 101. buildidcfg command errors (continued)


Manufacturer must be enclosed in quotation marks. A user tries to enter a manufacturer name withoutquotation marks.

Modifying entry identifier failed. Please check forduplicates or an invalid format.

where the identifier identifies the entry specified.

A user tries to modify an blade firmware build ID listentry with duplicate or wrong information.

No entries in the list. The blade firmware build ID list is empty.

Operating error “export identifier”

where the identifier identifies the information to export.

An error occurs during blade firmware build ID listinformation export.

Operating error “import identifier”

where the identifier identifies the information to import.

An error occurs during blade firmware build ID listinformation import.

Some required options for the –ab command are missing. A user tries to add a blade firmware build ID list entry,but does not include all of the required options.

chconfig command errorsThis topic lists errors for the chconfig command.


Table 102. chconfig command errors


Address must be enclosed in quotation marks. A user tries to enter an address that is not enclosed inquotation marks

City must be enclosed in quotation marks. A user tries to enter a city name that is not enclosed inquotation marks

IBM Support Center: invalid input. Please input 2characters ISO country code for the IBM Support Center.

A user tries to enter a country code that is not valid.

Contact Company must be enclosed in quotation marks. A user tries to enter a company name that is notenclosed in quotation marks

Contact Name must be enclosed in quotation marks. A user tries to enter a contact name that is not enclosedin quotation marks

Email must be enclosed in quotation marks. A user tries to enter an email that is not enclosed inquotation marks

Email: invalid input. Please make sure your input is notempty and within 30 characters.

A user tries to enter an email with a length that is notvalid

Error to enable/disable Service Agent. An error occurs while the advanced managementmodule is enabling or disabling the service agent.

Error to enable Service Agent. You have not set all of therequired contact Information fields yet.

A user tries to issue a command to enable a service agentthat does not have the required contact information set.

HTTP Proxy is disabled now, you can not change proxysettings, please enable http proxy first.

A user tries to change proxy settings when the HTTPproxy is disabled.

Invalid HTTP Proxy location. A user tries to enter a proxy address that is not a validIP address or hostname

Invalid input. -loc should be less than 64 characters. A user tries to enter a proxy address that is 64 or morecharacters long.


Table 102. chconfig command errors (continued)


Invalid input. -pw should be less than 16 characters. A user tries to enter a proxy password that is 16 or morecharacters long.

Invalid input. Password may not contain angle brackets. A user tries to enter a proxy password that contains "<"or "�>".

Invalid input. User Name must be less than 30characters.

A user tries to enter a user name that is 30 or morecharacters long.

Invalid option argument for -li: A user tries to use the -li option without the "view" or"accept" argument.

Terms and conditions is not accepted yet, please viewand accept the terms and conditions first.

A user attempts to change the service advisor settingsbefore accepting the terms and conditions.

The Terms and Conditions should be accepted firstbefore using this command.

A user attempts to change the service manager settingsbefore accepting the license agreement.

Phone number must be enclosed in quotation marks. A user tries to enter a phone number that is not enclosedin quotation marks

Phone number: invalid input. Please make sure yourinput is not empty and 5-30 characters.

A user tries to enter a phone number that is not valid

Postalcode must be enclosed in quotation marks. A user tries to enter a postal code that is not enclosed inquotation marks.

Postalcode: invalid input. Please make sure your input isnot empty and within 9 characters.

A user tries to enter a postal code is not valid in length.

State must be enclosed in quotation marks and has 2 or 3characters.

A user tries to enter a state that is not enclosed inquotation marks, or is not two or three characters inlength.

chlog command errorsThis topic lists errors for the chlog command.


Table 103. chlog command errors


-f must be used exclusive of other options. The user tries to use the -f option at the same time asother options.

-s must be used exclusive of other options. The user tries to use the -s option at the same time asother options.

A call home event with index number was not found.

where number is the decimal number that specifies theserviceable activity log entry that the user is attemptingto acknowledge or unacknowledge.

The management module was unable to find a specifiedcall-home event activity log entry.

Error reading data for Terms and Conditions. An error occurs while the management module isreading the terms and conditions information.

Fail to read Service Advisor Activity Log The management module was unable to read thecall-home event activity log.

Invalid syntax. Type 'chlog -h' for help. A user fails to specify the parameter for the call-homeactivity log entry that they are attempting toacknowledge or unacknowledge.


Table 103. chlog command errors (continued)


Terms and Conditions not accepted yet. The user attempts to view the call-home event activitylog but has not yet accepted the Terms and Conditions.

chmanual command errorsThis topic lists errors for the chmanual command.


Table 104. chmanual command errors


-test must be used exclusive of other options The user attempts to run this command with otheroptions in addition to -test.

Error generating a manual Call Home This command fails when the user attempts the manualcall home operation.

Error generating a test Call Home This command fails when the user attempts the test callhome operation.

Invalid syntax. Type 'chmanual -h' for help. The user attempts to use this command but usesimproper syntax.

Problem description must be enclosed in quotationmarks

The user attempts to run this command when theproblem description is not enclosed in quotation marks.

Test Call Home should be operated on SYSTEM target The user attempts to use this command when thecommand is not targeted on ‘system’ for test call home.

Terms and Conditions not accepted yet. The user attempts to use this command but has not yetaccepted the Terms and Conditions.

The Service Agent is disabled now, please enable itbefore calling 'chmanual'

The user attempts to use this command before theservice advisor is enabled.

cin command errorsThis topic lists error messages for the cin command.


Table 105. cin command errors


-id cannot be the same as the blade management VLANID. Please try again.

A user tries to enter a command with a VLAN ID whichis the same as the VLAN ID of the blade management.

-ip cannot be multicast. Please try again. A user issues a command with an IP address which isthe same as the IP address of the multicast.

-ip cannot be the same as the management module IPaddress. Please try again

A user tries to enter a command with an IP addresswhich is the same as the IP address of the advancedmanagement module.

An error occurred while changing CIN global statussetting

An error occurs while user is changing CIN global statussetting.

An error occurred while clearing CIN entry An error occurs while the user is clearing a CIN entry.


Table 105. cin command errors (continued)


An error occurred while enabling/disabling CIN entry. An error occurs while the user is enabling/disabling aCIN entry.

An error occurred while setting CIN entry. An error occurs while configuring a CIN entry.

Both -id and -ip are required for adding a CIN entry. A user tries to enter a command to add an entry withoutboth -id and -ip options.

CIN blade pair TLV get failed An error occurs while the management module is gettingCIN blade server configuration parameters.

CIN global TLV get failed. An error occurs while the management module is gettinga CIN global configuration parameter.

CIN command failed. An error occurs while the management module isexecuting a CIN command.

cin -index -en state cannot be used with other options.

wherev index identifies the cin index entryv state is on or off

The user tries to enter a command with the -en optionwith along with other options.

Duplicate CIN (-id, 0.0.0.0) pairs are not allowed. Pleasetry again.

A user tries to enter a command with a duplicated-id/0.0.0.0 pair.

Duplicate -ip is not allowed. Please try again. A user tries to enter a command with a duplicated IPaddress.

Internal error checking CIN entry. An error occurs while the system checks user input forthe CIN entry configuration.

Internal error getting CIN entry An error occurs while the management module is gettingCIN entry configuration parameters.

Invalid index parameter. Input must be numeric. A user tries to enter a command with a non-numericindex.

Invalid index parameter. Input out of range. A user tries to enter a command with an index which isout of range.

Invalid IP argument for an option. Enter 4 bytesseparated by 3 dots.

A user tries to enter a command argument for IP addressoption which is invalid because it is too long, too short,or not numeric.

Invalid IP argument for an option. Too many bytes. A user tries to enter a command with an invalidargument for IP address option which has more thanfour parts.

Invalid IP argument for an option. Too few bytes A user tries to enter a command with an invalidargument for IP address option which has fewer thanfour parts.

Invalid IP argument for an option. Each byte has to be inthe range (0-255).

A user tries to enter a command with an invalidargument for IP address option, each part of which is notin the range of 0-255.

Invalid option argument for -global -en: A user issues a command with an invalid argument for-global -en option.

Invalid option argument for -en to enable an entry. An error occurs while the user is enabling/disabling aCIN entry.


clear command errorsThis topic lists error messages for the clear command.


Table 106. clear command errors


Firmware update is in progress. Try again later. The user tries to reset the management module to itsdefault configuration during a firmware update. Theerror message displays and the management-moduleconfiguration does not reset.

Internal error resetting to defaults. An error occurs while the management module isresetting the management module to its defaultconfiguration. The error message displays and themanagement-module configuration does not reset.

clearlog command errorsThis topic lists error messages for the clearlog command.


Table 107. clearlog command errors


Error clearing the event log. An error occurs while the management module isclearing the event log.

clock command errorsThis topic lists error messages for the clock command.


Table 108. clock command errors


GMT+2:00 requires one of the following dst values: off,ee, gtb, egt, or fle

The user tries to change the Greenwich mean-time(GMT) offset to +2:00 without adjusting the DST setting.

GMT+10:00 requires one of the following dst values: off,ea, tas, or vlad

The user tries to change the GMT offset to +10:00without adjusting the DST setting.

GMToffset requires one of the following dst values: off,uc, other

where offset is the daylight-savings time offset.

The user tries to change the GMT offset to -9, -8, -7, -6,or -5 without adjusting the DST setting.

Invalid dst setting for GMT+10:00: setting

where setting is the illegal daylight-savings time settingthat was entered.

The user tries to enter an invalid -dst setting for a GMToffset of 10.


Table 108. clock command errors (continued)


Invalid dst setting for GMT+2:00: setting

where setting is the illegal daylight-savings time settingthat was entered.

The user tries to enter an invalid -dst setting for a GMToffset of 2.

Invalid dst setting for GMToffset: setting

where setting is the daylight-savings time offset andsetting is the illegal daylight-savings time setting thatwas entered.

The user tries to enter an invalid -dst setting for a GMToffset of -9, -8, -7, -6, or -5.

Invalid dst setting. The gmt offset does not support dst. The user tries to turn on dst for a GMT offset that doesnot support daylight-savings time.

Invalid input for -dst. A user tries to enter an invalid argument for the option-dst.

Reading date and time failed. An error occurs while the management module isreading the date and time.

Reading GMT offset failed. An error occurs while the management module isreading the GMT offset.

Reading status of daylight savings time failed. An error occurs while the management module isreading the daylight savings time status.

The gmt offset you entered does not support dst. Turningdst off.

A user tries to enter a GMT offset that does not supportdaylight savings time.

config command errorsThis topic lists error messages for the config command.


Table 109. config command errors



The user tries to enter an advanced management moduleContact or Location without ending double quotes.

Contact must be enclosed in quotation marks. The user tries to enter an advanced management moduleContact without enclosing it in double quotes.

Invalid input. Contact may not contain angle brackets. The user tries to enter an advanced management moduleContact containing angle brackets ("<" and ">").

Invalid input. Location may not contain angle brackets. The user tries to enter an advanced management moduleLocation containing angle brackets ("<" and ">").

Invalid input. Name must be less than 16 characters. The user tries to enter a name that is more than 15characters in length.

Invalid input. Name may not contain angle brackets. The user tries to enter a blade server name that containsangle brackets: "<" or ">".

Invalid input. Only alphanumeric characters,underscores, hyphens, pound signs, and periods areallowed.

The user tries to enter a name for the advancedmanagement module that is not valid.

Invalid input. -sn should have exactly sevenalphanumeric characters.

The user tries to enter a serial number that is not exactlyseven alphanumeric characters.


Table 109. config command errors (continued)


Invalid input. -tm should have exactly sevenalphanumeric characters.

The user tries to enter a type or model name that is notexactly seven alphanumeric characters.

Invalid input. -uuid should have exactly 32 hex digits. The user tries to enter a universally unique ID that is notexactly 32 hex digits.

Location must be enclosed in quotation marks. The user tries to enter an advanced management moduleLocation without enclosing it in double quotes.

Reading SNMPv1/SNMPv3 status failed. An internal errors occurs while the advancedmanagement module is reading the SNMPv1/v3status.

System location and contact must be defined whenSNMPv1 or SNMPv3 agent is enabled.

The user tries to undefine the system location or contactinformation while an SNMPv1 or SNMPv3 agent isenabled.

console command errorsThis topic lists error messages for the console command.


Table 110. console command errors


A SOL session socket was not available. The command-line interface fails to establish an SOLconnection to a blade server.

Error entering console mode. An error occurs while the management module is tryingto establish an SOL connection.

Global SOL is not enabled SOL is not enabled globally.

Internal Error An error occurs while the management module isprocessing the command.

SOL is not ready The blade server is not available, or when a socketneeded to establish a connection to the blade server isnot available.

SOL on blade is not enabled SOL is not enabled on the blade server where the user istrying to start an SOL session.

SOL session is already active The user cannot start an SOL session with a blade serverbecause an SOL session with that blade server is alreadyin progress.

The maximum number of sessions to this blade has beenreached.

The blade server has no available sessions for a user toconnect to.

Unknown error occurred while attempting to connect. An unknown error occurs when connecting to a bladeserver.


dhcpinfo command errorsThis topic lists errors for the dhcpinfo command.


Table 111. dhcpinfo command errors


Advanced failover must be enabled before viewing thestandby MM's DHCPv6 config.

A user tries to view the configuration of the standbymanagement module when advanced failover isdisabled.

Command cannot be issued to this type of Blade. Typeenv –h for help on changing targets.

A user issues the dhcpinfo command to a blade serverthat does not support IPv6.

DHCPv6 information is not available. DHCPv6 is enabled, but the command target is notreceiving any DHCPv6 settings.

DHCPv6 is disabled The DHCPv6 assigned configuration can not be retrievedbecause DHCPv6 is disabled.

IPv6 is disabled The DHCPv6 assigned config can not be retrievedbecause IPv6 is disabled.

This management network interface is not installed. A user issues the dhcpinfo command to a blade serverthat does not support a management network interface.

displaylog command errorsThis topic lists error messages for the displaylog command.


Table 112. displaylog command errors


(There are no more entries in the event log.) There are no more event log entries to display.

-f and -a cannot be used at the same time. The user tries to use the -f and -a options in the samecommand.

-l and -i options must be used exclusive of the otheroptions.

The user tries to issue a command with the -l and -ioptions at the same time as other options.

-lse option must be used exclusive of the other options The user tries to set the -lse option at the same time asother options.

Both -l and -i options must be provided to save eventlog.

The user tries to issue a command to save the event logwithout -l and -i provided.

Cannot open file: filename

where filename is the name of the file that was enteredwhen the error occurred.

An error occurs while the management module is tryingto open a file.

Duplicate date filter: filter

where filter is the duplicate date filter that was entered.

The user tries to use duplicate date filters.

Duplicate call home filter: filter

where filter is N or C.

The user tries to use duplicate call-home filters.


Table 112. displaylog command errors (continued)


Duplicate severity filter: filter

where filter is the duplicate severity filter that wasentered.

The user tries to use duplicate severity filters.

Duplicate source filter: filter

where filter is the duplicate source filter that was entered.

The user tries to use duplicate source filters.

Invalid date filter: filter

where filter is the invalid date filter that was entered.

The user tries to use an invalid date filter.

Invalid call home filter: filter

where filter is the invalid filter that was entered.

The user tries to use an invalid call-home filter.

Invalid severity filter: filter

where filter is the invalid severity filter that was entered.

The user tries to use an invalid severity filter.

Invalid source filter: filter

where filter is the invalid source filter that was entered.

The user tries to use an invalid source filter.

Putting event log file filename to tftp server ipaddressfailed

where:v filename is the name of the log filev ip_address is the IP address of the TFTP server

An error occurs while the management module is tryingto put the event log file to TFTP server.

Reading log entries failed. An error occurs while the management module isreading log entries.

displaysd command errorsThis topic lists error messages for the displaysd command.


Table 113. displaysd command errors


-save and -i must both be specified when saving theservice data.

A user tries to save the service data without specifyingboth the file name and IP address of the TFTP server.

Can not get the SRC's detail information. The advanced management module fails to get the SRCdetail information.

Error retrieving blade type. The advanced management module fails to read theblade server type.

Error transferring file. An unspecified TFTP error occurs.

No additional information for this SRC. The advanced management module tries to get the detailinformation of a SRC which does not have detailinformation.

Read/write command error. An error occurs while the management module isprocessing the command.

The format of the received data is wrong. The advanced management module receives wronglyformatted data.


dns command errorsThis topic lists error messages for the dns command.


Table 114. dns command errors


-on and -off cannot both be used in the same command. A user tries to enable and disable DNS in the samecommand.

At least one address is required to enable DNS. A user tries to enable DNS without configuring at leastone address.

DNS State Can not be determined. An error occurs while the management module isreading the DNS state.

Input length is greater than the maximum charactersallowed.

A user tries to enter too many characters in an inputfield.

Invalid ip address A user tries to set an invalid IP address.

IPv6 configuration changes will not take effect until IPv6is enabled.

A user attempts to configure the IPv6 DNS settings whileIPv6 is disabled.

Reading status of DNS failed. An error occurs while the management module isreading the DNS state.

Reading status of interface failed. An error occurs while the management module isreading the status of an interface.

env command errorsThis topic lists errors for the env command.

There are no unique errors for the env command. See “Common errors” on page409 for a list of error messages that apply to all commands.

ethoverusb command errorsThis topic lists errors for the ethoverusb command.


Table 115. ethoverusb command errors


Blade SP's command interface on Ethernet-over-USB isnot supported on blade blade_number

where blade_number identifies the blade server.

The command is directed to a blade server that does notsupport Ethernet-over-USB.

Notice: This operation may take a short while tocomplete. Please view the status to determine when theoperation has completed.

Confirmation message indicating that the command isprocessing and might take a short time to complete.


eventinfo command errorsThis topic lists errors for the eventinfo command.


Table 116. eventinfo command errors


Error reading eventinfo. An error occurs when reading event information.

Invalid event ID. A user attempts to enter an invalid event ID.

events command errorsThis topic lists errors for the events command.


Table 117. events command errors


-add and -rm should be used exclusively of each other. A user attempts to issue a command with both options-add and -rm.

Call Home Exclusion List has reached its maximum sizeof max entries. No more events can be added to the list.

where max is a decimal number.

A user attempts to add an entry while Call HomeExclusion List has reached its maximum size.

Error reading ftp/tftp of Service Data configuration. An error occurs while the management module isreading the FTP/TFTP service data configuration.

Error reading data for Terms and Conditions. An error occurs while the management module isreading the terms and conditions data.

Event id already exists in Call Home Exclusion List.

where id is a hexadecimal number that identifies acall-home event.

A user attempts to add an entry which already exists inCall Home Exclusion List.

Event id does not exist in the Call Home Exclusion List.


A user attempts to remove an entry which does not existin Call Home Exclusion List.

Event id is invalid to be added into Call Home ExclusionList.


A user attempts to add an entry with an invalid event id.

ftp/tftp of Service Data must be enabled before usingthis command.

A user attempts to issue an events command while theFTP/TFTP Report of Service Data is disabled

Read Call Home Exclusion List failed. An error occurs while the management module isreading the Call Home Exclusion List.

The terms and conditions should be accepted first beforeusing this command.

A user attempts to issue an events command before theterms and conditions have been accepted.


exit command errorsThis topic lists errors for the exit command.

There are no unique errors for the exit command. See “Common errors” on page409 for a list of error messages that apply to all commands.

feature command errorsThis topic lists errors for the feature command.


Table 118. feature command errors


-add option requires -key option The user tries to add a feature license without specifyingthe feature license key.

-key option must contain 7 alphanumeric characters An invalid value was entered for the -key option.

Apply operation timed out Applying a license file times out..

Error applying license file. Applying a license file fails.

Error getting errors. An error occurs while retrieving errors when applying alicense file.

Error getting status. An error occurs while getting status when applying orretrieving a license file.

Error parsing license file. An error occurs while applying or retrieving a licensefile.

Error retrieving license file. The license file fails to retrieve.

Error transferring license file. The license file fails to transfer.

Failed to apply license to chassis ip_address

where ip_address is the IP address for the BladeCenterunit on which the operation is being performed

An error occurs while applying a license file.

Failed to login to chassis ip_address



Failed to read license status An error occur occurs while the advanced managementmodule is reading the status of the feature license.

Failed to remove license for chassis ip_address



Failed to retrieve data for chassis ip_address



Failed to retrieve status for chassis ip_address



Failed to set license key An error occur occurs while the advanced managementmodule is setting the feature license key.


Table 118. feature command errors (continued)


Failed to validate chassis serial number An error occur occurs while the advanced managementmodule is validating the BladeCenter unit serial number.Make sure that the serial number is correct and retry thecommand.

Internal error. An error occurs while retrieving a license file.

Internal error. Something was wrong with the file. An error occurs while applying a license file.

Invalid error data returned Error data is not valid.

Invalid license key An error occur occurs while the advanced managementmodule is validating the feature license key. Make surethat the license key is correct and retry the command.

line number: CSV read error.

where number indicates the line in the license file that isin error.

An error occurs while applying a license file. Errorlocation in license file is specified in the error message.

line number: File open error.



line number: Incomplete line.



line number: Invalid IP.



line number: Line too long.



line number: Unknown error: code

where number indicates the line in the license file that isin error and code indicates the type of error.


Remove license failed An error occur occurs while the advanced managementmodule is removing a feature license.

Unknown error for chassis ip_address


Error type is unknown.

Unknown error type Error type is unknown.


files command errorsThis topic lists error messages for the files command.


Table 119. files command errors


%, /, and \" are not allowed in the filename. The user tries to enter a filename that is invalid.

Directory does not exist. The user tries to enter a directory that does not exist.

Error deleting file filename

where filename is the name of the file that was enteredfor deletion.

An error occurs while the management module is tryingto delete a file.

Error deleting file filename

where filename is the name of the file that was enteredfor deletion.

The user tries to delete a directory or delete a file thatdoes not exist.

Error reading file list. An error occurs while the management module isreading the directory file list.

Error reading file system space. An error occurs while the management module isreading the file system space.

Error reading first file in dir directory.

where directory is the name of the directory that wasentered.

An error occurs while the management module isreading the first file in the directory.

File index out of sequence. An error occurs while the management module isreading the index.

File list exhausted. An error occurs while the management module isreading the file list.

File not found. The specified file is not found.

Filename must be less than 256 characters The user tries to enter a filename that is longer than 256characters.

General, unknown error. A command is rejected for unknown reasons.

Invalid command sent. The user tries to enter an invalid command.

Invalid directory, filename. The user tries to enter an invalid directory and filename.

Invalid file or directory name. The user tries to enter an invalid directory or filename.

The directory name must be less than 256 characters. A user tries to enter a directory name that is more than256 characters in length.

Unknown caller id. The caller ID is not recognized.

Unknown command. The user tries to enter a command that is not recognized.

Unknown directory path. The user tries to enter a directory path that is notrecognized.


fuelg command errorsThis topic lists error messages for the fuelg command.


Table 120. fuelg command errors


-am cannot be enabled while -e is set to nebs. The user attempts to enable the acoustic mode while theenvironment is set to nebs.

-ps and -dps cannot be enabled at the same time. The user attempts to enable -ps and idps at the sametime.

A power module failure in domain domain_number canresult in an immediate shutdown.

where domain_number identifies the power domain.

A power module fails and the domain in which it isinstalled loses redundancy. The BladeCenter unit mightturn itself off, based on the power managementconfiguration.

Blade blade_number is not allowed to power on becauseof insufficient power.


There is insufficient power available in the powerdomain to turn on this blade server.

Blade blade_number is throttled.


The specified blade server has reduced power (powerthrottling) in response to a thermal event oroversubscription condition.

Blade blade_number was instructed to power off due topower budget restrictions.


BladeCenter power management turns off a blade serverthat is already on in response to a oversubscriptioncondition.

Blade must be powered on to enable/disable dps. The user attempts to enable or disable dynamic powerserver mode for a blade server while its power is off.

Checking if power is preallocated to switch numberfailed.

where the number I/O-module bay number.

An error occurs while the management module ischecking if power is preallocated for the specified I/Omodule.

Demand exceeds a single power module. Throttling canoccur in power domain domain_number.


The power requirements of components installed in apower domain exceed the level required for redundantoperation. Power throttling of BladeCenter componentsmight be able to correct the problem.

Effective CPU Speed not available. An error occurs while the management module isreading the effective CPU Speed.

Error reading blade power management capability. An error occurs while the management module isreading the blade server power management capability.

Error reading soft minimum. An error occurs while the management module isreading the soft minimum value.

Error reading soft minimum, using guaranteed minimuminstead.

An error occurs while the management module isreading the soft minimum value.

Error writing data for the option -pme

Please make sure the blade is powered on

The user attempts to enable power management andcapping for a blade server that is turned off.

Getting blade health state parameters failed. An error occurs while the management module isreading the blade server health state parameters.

Getting blade pcap maximum value failed. An error occurs while the management module isreading the blade server power cap maximum value.


Table 120. fuelg command errors (continued)


Getting blade pcap minimum value failed. An error occurs while the management module isreading the blade server power cap minimum value.

Getting blade power cap level failed. An error occurs while the management module isreading the blade server power cap level.

Getting data of domain 1 (or 2 ) failed. An error occurs while the management module isreading the data of power domain 1 (or 2).

Getting domain latest power sample failed. An error occurs while the management module isreading the latest power domain sample.

Getting duty cycle numbers failed. An error occurs while the management module isreading the duty cycle numbers.

Getting duty cycle numbers of blade blade_number failed.


An error occurs while the management module isreading the duty cycle numbers of specified blade server.

Getting dynamic power management capabilty ofbladeblade_number failed.


An error occurs while the management module isreading the dynamic power management capability ofspecified blade server.

Getting information of powernumber failed.

where the number identifies the specified power module.

An error occurs while the management module isreading data of specified power module.

Getting module domain map for blowernumber failed.

where the number identifies the specified chassis coolingunit.

An error occurs while the management module isreading module domain map of specified chassis coolingunit.

Getting module domain map for midplane failed. An error occurs while the management module isreading the module domain map for midplane.

Getting module domain map for MMnumber failed.

where the number identifies the specified managementmodule.

An error occurs while the management module isreading the module domain map of specifiedmanagement module.

Getting module domain map for muxnumber failed.

where the number identifies the location of thecomponent.

An error occurs while the management module isreading the module domain map of specified mux.

Getting module domain map for NCnumber failed.


An error occurs while the management module isreading the module domain map of specified networkclock module.

Getting module domain map of mtnumber failed.

where the number identifies the specified mt.

An error occurs while the management module isreading the module domain map of specified mt.

Getting module domain map of PM Cooling Devicenumber failed.

where number identifies the blade server.

An error occurs while the management module isreading the module domain map of specified powermodule Cooling Device.

Getting module domain map of switchnumber failed.

where the number represents the specified I/O module.

An error occurs while the management module isreading the module domain map of specified I/Omodule.

Getting module domain map of Telco alarm panel failed. An error occurs while the management module isreading the module domain map of Telco alarm panel.




Getting power management policy for domaindomain_number failed

where domain_number is the number of the domain thatwas entered.

An error occurs while the management module isreading the power management policy of specifieddomain.

Getting power state of bladeblade_number failed.


An error occurs while the management module isreading the power state of specified blade server.

Getting power values for blowernumber failed.


An error occurs while the management module isreading the power values of specified chassis coolingunit.

Getting power values for DSSnumber failed.

where the number represents the specified DSS.

An error occurs while the management module isreading the power values of specified DSS.

Getting power values for MMnumber failed.


An error occurs while the management module isreading the power values of specified managementmodule.

Getting power values for NCnumber failed.

where the number represents the specified NC.

An error occurs while the management module isreading the power values of specified network clockmodule.

Getting power values for switchnumber failed.

where the number represents the specified I/O module.

An error occurs while the management module isreading the power values of specified I/O module.

Getting power values of midplane within domain failed. An error occurs while the management module isreading the power values of midplane within domain.

Getting power values of mtnumber within domain failed.

where the number represents the specified mt.

An error occurs while the management module isreading the power values within domain of specifiedmedia tray.

Getting power values of muxnumber within domainfailed.

where the number represents the specified mux.

An error occurs while the management module isreading the power values within domain of specifiedmux.

Getting power values of PM Cooling Device numberfailed

where the number represents the specified PM coolingdevice.

An error occurs while the management module isreading the power values of specified power modulecooling device.

Getting power values of Telco alarm panel withindomain failed.

An error occurs while the management module isreading the power values of Telco alarm panel withindomain.

Getting status of domain domain_number failed


An error occurs while the management module isreading the status of specified domain.

Getting the power control setting on blade failed. An error occurs while the management module isreading the power control setting on blade server.

Invalid option for this blade: option

where option identifies the unacceptable option.

The user attempts to issue a command with an optionwhich is invalid for the targeted blade server.

Maximum CPU Speed not available. An error occurs while the management module isreading maximum CPU Speed.




pcap must be between min and max Watts.

where min and max represent the minimum andmaximum wattage values permitted.

The user input for power cap is out of the range.

Power value is not in the guaranteed capping range. The user attempts to set a power value that is out ofrange.

Setting -e to nebs automatically disables -am, so "-am on"will be ignored.

The user attempts to set the environment to nebs and toenable the acoustic mode at the same time.

There are mismatched power modules in power domaindomain_number.


The power modules installed in a power domain havedifferent ratings.

There is no thermal trending data to display. An error occurs while the management module isreading thermal trending data.

There is no trending data to display. An error occurs while the management module isreading power trending data.

Unable to change power management settings, domainmay be oversubscribed.

An error occurs while the management module isconfiguring the power management policy.

groups command errorsThis topic lists errors for the groups command.


Table 121. groups command errors


When creating a new group, a group name and authoritylevel must be specified.

A user tries to create a new group without specifying agroup name or authority level.

health command errorsThis topic lists errors for the health command.


Table 122. health command errors


Getting system health summary failed. An error occurs while the management module isreading the system health summary.


help command errorsThis topic lists errors for the help command.

There are no unique errors for the help command. See “Common errors” on page409 for a list of error messages that apply to all commands.

history command errorsThis topic lists errors for the history command.

There are no unique errors for the history command. See “Common errors” onpage 409 for a list of error messages that apply to all commands.

identify command errorsThis section lists error messages for the identify command.


Table 123. identify command errors


-d can only be used on the system target. The user tries to issue a command with the -d option toa target other than system.

-d can only be used with the -s on. The user tries to issue a command with the -d optionwithout -s on setting.

Delay value must be less than max

where max is the preset maximum.

The user input for option -d exceeds the maximum.

Delay value must be less than 60. A user tries to enter a -d value that is greater than 60seconds.

Error accessing remote LED. An error occurs while the management module isaccessing a remote LED.

Error getting LED status. An error occurs while the management module isreading the blade LED status.

Error reading system LED state. An error occurs while the management module isreading the system LED status.

Error setting system LED. An error occurs while the management module is settingthe system LED.

Error unknown command. The user tries to enter unrecognized command.

Identify: Error accessing remote LED. An error occurs while the management module isprocessing the command.

Identify: error getting LED status. An error occurs while the management module isprocessing the command.

Identify: error setting Management Module LED. An error occurs while the management module isprocessing the command.

Identify: Error unknown command. An error occurs while the management module isprocessing the command.

Identify: LED status not supported. The user tries to get the status of an LED that is notsupported by a blade server.


Table 123. identify command errors (continued)


Identify: unknown LED state state

where state identifies the LED state that was returned.

An LED state other than on, off, or blinking is returned.

Identify: Unknown return status status

where the status value varies based on the problem thatwas encountered.

An error occurs while the management module isprocessing the command.

Syntax error. The user tries to enter an invalid command option. Typeidentify -h for command help.

The chassis identification LED cannot be turned off atthis time because one or more blades have their locationLED active.

The user tries to turn off the chassis identification LEDunder conditions that do not permit this action.

ifconfig command errorsThis topic lists error messages for the ifconfig command.


Table 124. ifconfig command errors


-em cannot be reconfigured while Stacking Mode isenabled on the AMM.

The user tries to issue a command with the -em optionwhile Stacking Mode is enabled on the advancedmanagement module.

-ep cannot be reconfigured while Stacking Mode isenabled on the AMM.

The user tries to issue a command with the -ep optionwhile Stacking Mode is enabled on the advancedmanagement module.

-ipv6static, -dhcp6, and -sa6 can't all be disabled. A user attempts to issue a command that disables-ipv6static, -dhcp6, and -sa6 at the same time.

-option is not supported by this type of I/O Module.

where option is ir, gr, or sr.

The user tries to issue a command with an option -ir, -gr,or -sr which is not supported by the targeted I/Omodule.

-pip cannot be reconfigured while Stacking Mode isenabled on the AMM.

The user tries to issue a command with the -pip optionwhile Stacking Mode is enabled on the advancedmanagement module.

-up and -down can not be both used in same line. The user tries to issue a command with both the -up and-down options.

Cannot apply network configuration. Blade inconfiguration phase.

An error occurs while the management module is settingthe network configuration.

Configuration not supported on this I/O Module type. The user tries to issue a command for the configurationwhich is not supported by targeted I/O module type.

Configuration not supported on this switch type. The user tries to issue a command to an unsupportedI/O module type.

Error converting the i6 address from string to bytes. An error occurs while converting the i6 address from astring to bytes.

Enabling/Disabling new IP configuration failed. An error occurs while the management module isenabling or disabling the new IP configuration.


Table 124. ifconfig command errors (continued)


Error reading gateway address. An error occurs while the management module isreading the gateway address of a network interface (eth0or eth1).

Error reading IP Address. An error occurs while the management module isreading the IP address of the integrated systemmanagement processor on a blade server, or whilereading the IP address of a network interface (eth0 oreth1).

Error reading data for Link-local address. An error occurs while the management module isreading data for the link-local address.

Error reading data for Link-local address prefix length. An error occurs while the management module isreading data for the link-local address prefix length.

Error reading data for Stateless auto-config IP Addresses. An error occurs while the management module isreading the stateless auto-configuration IP address.

Error reading the burned-in MAC address. An error occurs while the management module isreading the burned-in MAC address of a networkinterface (eth0 or eth1).

Error reading the data rate. An error occurs while the management module isreading the data rate setting of a network interface (eth0or eth1).

Error reading the DHCP configuration. An error occurs while the management module isreading the DHCP setting of a network interface (eth0).

Error reading the duplex setting. An error occurs while the management module isreading the duplex setting of a network interface (eth0 oreth1).

Error reading the hostname. An error occurs while the management module isreading the host name of a network interface (eth0).

Error reading the locally administered MAC address. An error occurs while the management module isreading the locally administered MAC address of anetwork interface (eth0 or eth1).

Error reading the maximum transmission unit. An error occurs while the management module isreading the maximum transmission unit (MTU) setting ofa network interface (eth0 or eth1).

Error reading the subnet mask. An error occurs while the management module isreading the subnet mask of a network interface (eth0 oreth1).

Error writing IP Address. An error occurs while the management module is settingthe IP address of the integrated system managementprocessor on a blade server.

Getting blade cKVM status for blade blade_number failed.


An error occurs while the management module isreading the cKVM status of targeted blade.

Getting interface status failed. An error occurs while the management module isreading the interface status.

I/O Module is in Stacking Mode and cannot change itsGateway configuration.

The user tries to issue a command to change theGateway configuration with the I/O Module in StackingMode.

I/O Module is in Stacking Mode and cannot change itsIP configuration.

The user tries to issue a command to change the IPconfiguration with the I/O Module in Stacking Mode.




I/O Module is in Stacking Mode and cannot change itsSubnet configuration.

The user tries to issue a command to change Subnetconfiguration with I/O Module in Stacking Mode.

Invalid gateway address. The user tries to enter an invalid gateway address.

Invalid hostname. The user tries to enter an invalid hostname.

Invalid hostname arg for option: hostname. Consecutivedots

where:v option identifies the command optionv hostname identifies the invalid hostname argument

The user tries to enter consecutive periods (. ) as part ofa hostname.

Invalid hostname arg for option: hostname. Length has tobe < 64 characters


The user tries to enter a hostname longer than 63characters.

Invalid hostname arg for option: hostname. Onlyalphanumeric chars and._- allowed


The user tries to enter an hostname that contains invalidcharacters. Valid characters that can be used in ahostname are letters, numbers, periods ( . ), dashes ( - ),and underscores ( _ ).

Invalid ip address. Displays for one of the following errors:v A user tries to set the IP address of system:blade[1]:sp

to an invalid IP address.v A user tries to set an IP address whose last part is

greater than 255 (the maximum number of bladeservers).

v A user tries to enter an invalid IP address for the -i(static IP address) command option.

Invalid IP arg for option: ip_address. Each byte has to bein the range (0-255)

where:v option identifies the command optionv ip_address identifies the invalid IP address argument

The user tries to enter an IP address that is out of range.IP addresses must follow the standard format:xxx.xxx.xxx.xxx, where each xxx is a number from 0 to255.

Invalid IP arg for option: ip_address. Enter 4 bytesseparated by 3 dots


The user tries to enter an IP address that is too long. IPaddresses must follow the standard format:xxx.xxx.xxx.xxx, where each xxx is a number from 0 to255.

Invalid IP arg for option: ip_address. Too few bytes


The user tries to enter an IP address with too few bytes.IP addresses must follow the standard format:xxx.xxx.xxx.xxx, where each xxx is a number from 0 to255.

Invalid IP arg for option: ip_address. Too many bytes


The user tries to enter an IP address with too manybytes. IP addresses must follow the standard format:xxx.xxx.xxx.xxx, where each xxx is a number from 0 to255.

Invalid mac address. The user tries to enter an invalid MAC address.




Invalid MAC arg for option: address. Invalid syntax

where:v option identifies the command optionv address identifies the invalid MAC address argument

The user tries to enter an invalid MAC address.

Invalid MAC arg for option: address. Multicast addressesnot allowed


The user tries to enter a multicast address.

Invalid MAC arg for option: address. Too few bytes


The user tries to enter a MAC address with too fewbytes.

Invalid MAC arg for option: address. Too many bytes


The user tries to enter a MAC address with too manybytes.

Invalid option for ethernet interface. A user tries to change a static property of eth1(hostname, DHCP, data rate, duplex).

Invalid parameter. The locally administered MACaddress cannot be a multicast address.

The user tries to set the locally administered MACaddress to a multicast address.

Invalid parameter. The MTU must be between 60 and1500, inclusive.

The user tries to enter an MTU outside the valid range.

Invalid parameter. Valid values for -c are dhcp, static, ordthens.

A user tries to enter an invalid parameter for the -c(Ethernet configuration method) command option.

Invalid parameter. Valid values for -d are auto, half, andfull.

The user tries to enter an invalid parameter with the -doption.

Invalid parameter. Valid values for -r are auto, 10, and100.

The user tries to enter an invalid parameter with the -roption.

Invalid subnet mask. The user tries to enter an invalid subnet mask.

Maybe blade network configuration is still in discoveryphase. Please check and try again.

An error occurs while the management module isreading the blade network configuration.

Option: -bsmp is not supported any more. The user tries to direct the command to the -bsmpcommand target that is no longer supported.

Please check blade health status and try again. An error occurs while the management module isreading the blade health status.

The target must be system:blade[1]:sp for this command A user tries to issue the ifconfig -i ip address -Tsystem:blade[x]:sp to a blade server other than blade[1].

where ip address is a valid ip address and x identifies theselected blade server.

This target is no longer supported by the ifconfigcommand.

The user tries to direct the command to an invalidcommand target.

When setting –i6, -p6, or –g6, -id must be included. A user tries to configure a blade server static IPv6configuration and does not include the staticconfiguration ID number.


info command errorsThis topic lists error messages for the info command.


Table 125. info command errors


Device not found No VPD is available for the targeted device.

Getting blade H8 firmware VPD data of bladeblade_number failed.


An error occurs while the management module isreading the blade H8 firmware VPD data of the targetedblade server.

Getting compact flash cards information failed. An error occurs while the management module isreading the compact flash cards information.

Getting firmware version of cKVM bay_number failed.

where the bay_number specifies the cKVM.

An error occurs while the management module isreading the firmware version of targeted cKVM.

Getting firmware's VPD data of type failed. An error occurs while the management module isreading the firmware's VPD data of targeted type.

Getting name of blade blade_number failed.


An error occurs while the management module isreading the name of the targeted blade server.

Getting name of mm bay_number failed.

where the bay_number specifies the management module.

An error occurs while the management module isreading the name of the targeted management module.

Reload Firmware VPD failed. An error occurs while the management module isreloading the firmware VPD.

Reload Hardware VPD failed. An error occurs while the management module isreloading the hardware VPD.

Reload all failed. An error occurs while the management module isreloading all VPD and MAC addresses.

Reload MAC address failed. An error occurs while the management module isreloading the MAC address.

Reload WWN failed. An error occurs while the management module isreloading WWN.

Status: Unable to read status. An error occurs while the management module isreading the firmware update status.

Unable to read firmware VPD. An error occurs while the management module isreading the firmware VPD.

Unable to read hardware VPD. An error occurs while the management module isreading the hardware VPD.

Unknown device type. The command is targeted to an unknown device type.


iocomp command errorsThis topic lists errors for the iocomp command.


Table 126. iocomp command errors


Error reading I/O Compatibility Detail for bladeblade_number


An error occurs while the management module isreading I/O compatibility for targeted blade server.

Error reading I/O Compatibility Detail for switchbay_number

where the bay_number identifies the I/O module.

An error occurs while the management module isreading I/O compatibility for targeted I/O module.

ERROR!!! IOM bay_number reports incorrect width!sw_width = sw_width

wherev the bay_number identifies the I/O modulev sw_width identifies the invalid width

An error occurs while the management module isreading I/O compatibility for targeted I/O module.

I/O Compatibility Detail or blade blade_number:unknown


An error occurs while the management module is gettingthe width of the targeted blade server.

kvm command errorsThis topic lists errors for the kvm command.

There are no unique errors for the kvm command. See “Common errors” on page409 for a list of error messages that apply to all commands.

ldapcfg command errorsThis topic lists error messages for the ldapcfg command.


Table 127. ldapcfg command errors


A Client DN password is configured, client DN must beconfigured too.

The user tries to issue a command to remove the clientDN setting with the client DN password configured.

AMM target name is limited to 63 characters. A user tries to set an advanced management moduletarget name that is longer than 63 characters.

Argument of option -arguments must be enclosed inquotation marks.

where arguments is the name of the improperly enteredarguments

The user tries to issue a command with arguments forthe options that are not enclosed in quotation marks.


The user tries to issue a command with arguments foroptions without ending double quotes.


Table 127. ldapcfg command errors (continued)


Both password and confirm password must be provided. The user tries to issue a command without providingboth the password and the confirm password.

Client DN password mismatch. Please reenterpasswords.

The user tries to issue a command with both -p and -cpoptions, but their arguments do not match.

Client DN password mismatch. Please reenterpasswords.

The user tries to issue a command with both -p and -cpoptions, but their arguments do not match.

If a Client DN password is configured, client DN mustbe configured too.

The user tries to issue a command to configure the clientDN password while the client DN is not configured.

Invalid option argument for -option:argument. format

where:v option identifies the optionv argument identifies the invalid argumentv format identifies the format of argument

The user tries to issue a command with invalidarguments for the options which do not conform to theformat specified.

You are configuring Client DN password, but no ClientDN. Please configure a Client DN.

The user tries to issue a command to set Client DNpassword while the Client DN is not configured.

You must configure a Search Domain given yourselection of 'option' for Domain Source.

where option is sd or ltsd.

The user tries to issue a command for -ds option settingswithout the Source Domain configured.

led command errorsThis topic lists errors for the led command.


Table 128. led command errors


-d can only be used with the -loc on. A user tries to issue a command to set the -d while the-loc setting is off.

Delay value must be less than max.

where max is 60.

User input for the option -d exceeds the maximum.

Error getting LED status. An error occurs while the management module is gettingthe system LED status.

Error reading system LED state. An error occurs while the management module isreading the system LED state.

Error setting system LED. An error occurs while the management module isconfiguring the system LED.

Invalid option argument for -loc. A user tries to enter an invalid argument for the option-loc.

Error setting -loc for blade[slot] An error occurs while setting location LED for thetargeted blade.

-l can only be used by itself. User issues a command with -l option inclusive of anargument or other options.

Error turning off information LED An error occurs while the user is setting informationLED to off.


Table 128. led command errors (continued)


The chassis location LED cannot be turned off at thistime because one or more blades have their location LEDactive.

A user issues a command to turn off the chassis locationLED under conditions when this is not allowed.

list command errorsThis topic lists error messages for the list command.


Table 129. list command errors


The level must be non-zero. The user tries to enter a level of depth for tree-structuredisplay of 0.

mcad command errorsThis topic lists error messages for the mcad command.

There are no unique errors for the mcad command. See “Common errors” on page409 for a list of error messages that apply to all commands.

modactlog command errorsThis topic lists errors for the modactlog command.


Table 130. modactlog command errors


Unable to read the Module Activity Log. No module activity log is found in the database.

monalerts command errorsThis topic lists errors for the monalerts command.


Table 131. monalerts command errors


-option must be used exclusive of its sub-options.

where option is -ca, -wa, or -ia.

A user tries to issue a command with the -ca, -wa, or -iaoption at the same time as its sub-options.

Invalid syntax. -ec is only allowed to be enabled. A user tries to disable -ec (legacy alerts).

Note: If -ec is disabled, monalertsleg should be used. A user tries to issue a monalerts command with the -ecdisabled setting.


monalertsleg command errorsThis topic lists errors for the monalertsleg command.


Important: The monalertsleg command is no longer supported by the advancedmanagement module firmware. Legacy alert monitoring that uses the monalertslegcommand must transition to use of the monalerts command.

Table 132. monalertsleg command errors


Invalid syntax. -ec is only allowed to be enabled. A user tries to disable -ec (legacy alerts).

Note: If -ec is enabled, monalerts should be used. A user tries to issue a monalertsleg command with the-ec enable setting.

mt command errorsThis topic lists errors for the mt command.


Table 133. mt command errors


Remote media tray switching must be enabled to changethe media tray owner.

A user tries to issue a command to change the mediatray owner while media tray switching is not enabled.

nat command errorsThis topic lists error messages for the nat command.


Table 134. nat command errors


Adding code authority failed. A user tries to add code authority.

External port: Valid range is 1000 through 65534. The user tries to set the external port number to a valueoutside of its valid range.

I/O Module is in protected mode and cannot be restoredto its default configuration.

The user tries to restore the default configuration of anI/O module while it is in protected mode.

I/O Module is in Protected Mode and cannot change itsNAT configuration.

The user tries to change the configuration of an I/Omodule while it is in protected mode.

Internal port: Valid range is 1 through 65534. The user tries to set the internal port number to a valueoutside of its valid range.

NAT configuration is not supported on this IO module. The user tries to direct a nat command to an I/O modulethat does not support the network address table.

The first two rules' protocol names cannot be changed. The user tries to change the protocol names for HTTP orTelnet.


Table 134. nat command errors (continued)


When creating a new rule, all fields must be specified. The user does not specify all the fields when attemptingto make a new rule.

Invalid input. '-pn' must be less than maximum_numbercharacters.

where maximum_number is the maximum number ofcharacters allowed for the protocol name.

The user tries to enter a protocol name with a stringlength of more than the maximum allowed.

ntp command errorsThis topic lists error messages for the ntp command.


Table 135. ntp command errors


Invalid value passed to -en flag. Valid values areenable/disable

The user input for the -en option is invalid.

Please set NTP server name or IP address beforeenabling NTP

The user tries to enable NTP before setting the servername or IP address.

Please set NTP server name or IP address beforesynchronizing the clock

The user tries to synchronize the clock before setting theNTP server name or IP address.

Please set NTP update frequency before enabling NTP The user tries to enable NTP before setting the updatefrequency.

Please set NTP v3 authentication entry before enablingNTP authentication

The user tries to enable NTP authentication beforeconfiguring the v3 authentication.

ping command errorsThis topic lists errors for the ping command.


Table 136. ping command errors


Error reading IP address of switch bay_number

where the bay_number designates the I/O module.

An error occurs while the management module is gettingthe current IP address of the targeted switch.

Error reading I/O Module's capabilities. An error occurs while the management module isreading the I/O Module's capabilities.

Error reading I/O Module's second ip configuration. An error occurs while the management module isreading the I/O Module's second ip configuration.

Error reading second IP address of I/O Modulebay_number

where the bay_number identifies the I/O module.

An error occurs while the management module isreading the second IP address of the I/O Modulespecified.


Table 136. ping command errors (continued)


The I/O module cannot be pinged while the IP config isprotected.

The user tries to ping a protected member of an I/Omodule stack.

pmpolicy command errorsThis topic lists errors for the pmpolicy command.


Table 137. pmpolicy command errors


Error getting number of domains. An error occurs while the advanced managementmodule is getting the number of domains.

Getting current policy failed. An error occurs while the advanced managementmodule is getting the current policy for a domain.

Getting valid policies failed. An error occurs while the advanced managementmodule is getting the valid policies for powermanagement.

portcfg command errorsThis topic lists errors for the portcfg command.

There are no unique errors for the portcfg command. See “Common errors” onpage 409 for a list of error messages that apply to all commands.

ports command errorsThis topic lists error messages for the ports command.


Table 138. ports command errors


A certificate must first be in place before SSL can beenabled.

The user tries to enable SSL before setting up a valid SSLcertificate.

An SSH server key must first be in place before SSH canbe enabled.

The user tries to enable SSH before setting up a validSSH server key.

Duplicate port number entered. The user tries to enter a command with a port numberthat is already in use.

Enabling SNMPv1 failed The SNMPv1 configuration does not meet requiredcriteria.

Enabling SNMPv3 failed The SNMPv3 configuration does not meet requiredcriteria.

Error: A community is configured without an IP addressor host name. Please use ‘snmp' command for snmpconfiguration.

Attempted to configure community without an IPaddress or host name.


Table 138. ports command errors (continued)


Error: A duplicate community name is configured. Pleaseuse ‘snmp' command for snmp configuration.

Attempted to configure a community name that wasalready defined.

Error: At least one configured community is required toenable SNMPv1. Please use ‘snmp' command for snmpconfiguration.

Attempted to enable SNMPv1 without configuring atleast one community.

Error: IP address of 0.0.0.0, 0::0 is allowed only when thefirst community is configed as Get or Set access type.Please use ‘snmp' command for snmp configuration.

IP address of 0.0.0.0 or 0::0 is allowed only when the firstcommunity is configured as a GET or SET access type.

Error: System contact must be defined to enableSNMPv1. Please use ‘snmp' command for snmpconfiguration.

Attempted to enable SNMPv1 without defining a systemcontact.

Error: System location must be defined to enableSNMPv1. Please use ‘snmp' command for snmpconfiguration.

Attempted to enable SNMPv1 without defining a systemlocation.

Error: System contact must be defined to enableSNMPv3. Please use ‘snmp' command for snmpconfiguration.

Attempted to enable SNMPv3 without defining a systemcontact.

Error: System location must be defined to enableSNMPv3. Please use ‘snmp' command for snmpconfiguration.

Attempted to enable SNMPv3 without defining a systemlocation.

Error sanity checking of SNMP configuration. An error occurs while the management module ischecking the SNMP configuration.

Invalid parameter. The timeout must be between 0 and4294967295 seconds.

The user tries to enter a timeout that is outside of thevalid range.

Maximum connections can not exceed 20. A user attempts to configure more than 20 connections.

No valid server certificate is in place for Secure TCPCommand Mode. Use the sslcfg command to generate acertificate.

A user tries to change the state of stcm without a validcertificate in place.

Port number out of range. A user tries to enter a port number that is outside of thevalid range.

Resetting all ports to default values failed. An error occurs while the management module isresetting all ports to their default values.

Secure SMASH CLP cannot be enabled without a validSSH server key in place.

The user tries to enable the secure SMASH CLP beforesetting up a valid SSH server key.

The -prior option has been deprecated. Please use the-rpp option instead.

where prior is kvmp, rdp, rdocp, or sdsp.

The user tries to enter a command with a deprecatedoption, such as -kvmp, -rdp, -rdocp, or -sdsp.

The total number of secure and legacy connections ofTCP Command Mode cannot exceed 20

A user attempted to configure more than 20 TCPCommand Mode connections.

This I/O module does not support port speedconfiguration.

The user tries to enter a command for a speedconfiguration which not supported by the targeted I/Omodule.

Warning: Communication with IBM Director via SecureTCP Command Mode has been disabled.

A user has disabled the Secure TCP command mode.

Warning: Communication with IBM Director via TCPCommand Mode has been disabled.

A user has disabled the TCP command mode.


power command errorsThis topic lists error messages for the power command.


Table 139. power command errors


Invalid POST results. The POST results are not valid.

Not supported by this type of I/O module. Type env -hfor help on changing targets.

The user attempts to apply the -fp option to an I/Omodule that does not support this option.

POST results could not be read. An error occurs during POST.

POST results not complete: hex_code

where the hex_code value varies based on the problemthat was encountered.

The POST results are not available. See thedocumentation that comes with the device that failed torespond correctly to the power command for informationabout the hex_code value.

Powering on/off blade failed. An error occurs while powering the blade server on oroff.

Powering on/off I/O Module failed. An error occurs while the management module ispowering the I/O module on or off.

Powering on/off network clock failed. An error occurs while the management module ispowering the network clock on or off.

Powering on/off Telco Alarm Panel failed. An error occurs while the management module ispowering the Telco Alarm Panel on or off.

Resetting blade failed. An error occurs while the management module isresetting the blade server.

Shutting down OS and powering off blade failed. An error occurs while the management module isshutting down the operating system and powering offthe blade server.

The I/O Module is powering off. The user tries to power on, power off, or restart a RAIDSAS module which is in the process of powering off.(BladeCenter S only)

rdoc command errorsThis topic lists error messages for the rdoc command.


Table 140. rdoc command errors


Error getting rdoc status information. An error occurred while retrieving status information.

Internal error. Please try again. The command failed to execute.


read command errorsThis topic lists error messages for the read command.


Table 141. read command errors


Both the -i and -l options must be specified with the-config file.

The user does not specify both the -i and -l options whenrestoring configuration from a file.

Configuration restore from the chassis failed: i2c busread error.

An error occurs while the management module isrestoring the management module configuration from theBladeCenter unit midplane due to an i2c read error.

Configuration restore from the chassis failed: operationnot supported.

An error occurs while the management module isrestoring the management module configuration from theBladeCenter unit midplane due to a failed system check.

Configuration restore from the chassis failed: NVRAMcompression error.

An error occurs while the management module isrestoring the management module configuration from theBladeCenter unit midplane due to an EEPROMcompression error.

Configuration restore from the chassis failed:unsupported midplane data format.

An error occurs while the management module isrestoring the management module configuration from theBladeCenter unit midplane due to an unsupportedEEPROM format.

Could not retrieve encryption data from theconfiguration file successfully.

The user tries to enter a passphrase that does not matchthe one that was used to create the backup configurationfile.

Error writing autoread flag. An error occurs while the management module iswriting autoread flag.


Firmware update is in progress. Try again later. The user tries to restore the management moduleconfiguration from the BladeCenter unit midplane whilethe management module firmware is updating.

Please make sure you enter the correct passphrase forthis configuration file.

The user tries to enter a passphrase that does not matchthe one that was used to create the backup configurationfile.

Resource allocation failure! Memory allocation failed forconfiguration read.

An error occurs while the management module isallocating memory.

The -auto option can only be used with the -configchassis.

The user tries to set the -auto option when restoring theconfiguration from a file.

The -config option and a config source is required. The user tries to issue a command to read configurationfrom a file without specifying both the -config optionand config source.

The -config option is required. The user does not include a required -config option forthe command.

The -i, -l, and -p options can only be used with the-config file.

The user tries to specify a TFTP server and aconfiguration file when restoring the configuration fromthe BladeCenter unit midplane.

The passphrase is greater than 1600 characters. The user tries to input a passphrase that exceeds themaximum length.


Table 141. read command errors (continued)


The passphrase must be quote-delimited. The user tries to input a passphrase that is notquote-delimited.

There was a problem retrieving the file. TFTP encounters an error when transferring theconfiguration file.


remotechassis command errorsThis topic lists error messages for the remotechassis command.


Table 142. remotechassis command errors


Clearing the internal discovered list of MM's failed. An error occurs while the management module isclearing the internal discovered list of managementmodules.

Discovery cannot be run until SLP has been enabled. The user tries to discover other BladeCenter units on thenetwork when SLP is disabled.

Error running discovery. An error occurs while the management module isrunning discovery.

Getting last discovery time failed. An error occurs while the management module isreading last discovery time.

Getting the first entry of the internal discovered list ofMM's failed.

An error occurs while the management module isreading the first entry of the internal discovered list ofmanagement modules.

Getting the internal discovered list of MM's failed. An error occurs while the management module isreading the internal discovered list of managementmodules.

Unable to read SLP settings. An error occurs while the management module isreading SLP settings.

reset command errorsThis topic lists error messages for the reset command.


Table 143. reset command errors


An error occurred while disabling failover. An error occurs while the management module isdisabling failover.

An error occurred while enabling failover. An error occurs while the management module isenabling failover.


Table 143. reset command errors (continued)


Firmware update is in progress. Try again later. The user tries to reset the management module during afirmware update. The error message displays and themanagement module does not reset.

Rebooting blade failed. An error occurs while the management module isrebooting the blade server.

Resetting and running standard/extended/fulldiagnostics for I/O module failed.

An error occurs while the management module isresetting and running diagnostics for the I/O module.

Resetting I/O module failed. An error occurs while the management module isresetting the I/O module.

There is no backup management module installed. A user tries to enable failover on a management-modulereset and there is no standby management module.

Resetting blade blade_number with NMI not supported.

where the blade_number identifies the blade server.

A user tries to reset a blade server that does not supportnon-maskable interrupts (NMI).

Resetting blade blade_number with NMI failed.

where the blade_number identifies the blade server.

An error occurs while the management module isresetting a blade server with NMI.

scale command errorsThis topic lists errors for the scale command.


Table 144. scale command errors


Auto-create partition failed: error_detail

where error_detail provides additional information aboutthe error.

An error occurs while creating a partition.

Clearing complex failed: error_detail


An error occurs while clearing a complex.

Create a partition failed: error_detail


An error occurs while creating a partition.

Deleting a partition failed: error_detail


An error occurs while deleting a partition.

Getting complex information failed: error_detail


An error occurs while gathering complex information.

Invalid node slot. A user tries to enter a slot number for a node or bladeserver that is not valid. Make sure that the nodeinformation specified is valid.


Table 144. scale command errors (continued)


Invalid range of node slots. A user tries to enter a range of slot numbers for a nodeor blade server that is not valid. Make sure that the nodeinformation specified is valid.

Power controlling a partition failed: error_detail


An error occurs while changing the power state of apartition.

Setting mode failed: error_detail


An error occurs while changing the power state of apartition.

sddump command errorsThis topic lists errors for the sddump command.


Table 145. sddump command errors


Initiate data collection of type type not supported onblade[x]

where type is the type of data requested and x is thenumber of the blade-server bay.

The management module is unable to collect therequested data from the specified blade server.

Initiate data collection type failed. The management module is unable initiate datacollection of the JS12 or JS22 blade server.

sdemail command errorsThis topic lists errors for the sdemail command.


Table 146. sdemail command errors


-to must be specified. A user tries to send a service data email message withoutspecifying the recipient.

Error sending service data email. An error occurs when the management module tries tosend a service data email message.

Invalid email address. A user tries to enter an email address that is not valid.

Invalid input. Email address must be less than 120characters.

A user tries to enter an email address that is 120 or morecharacters long.

Invalid syntax. Please type 'sdemail -h' for help. A user enters the sdemail command without specifyingthe required options.

Subject must be enclosed in quotation marks. A user tries to send a service data email message with asubject option that is not enclosed in quotation marks.


security command errorsThis topic lists errors for the security command.

There are no unique errors for the security command. See “Common errors” onpage 409 for a list of error messages that apply to all commands.

service command errorsThis topic lists errors for the service command.


Table 147. service command errors


Getting status of debug with USB key failed. An error occurs while the management module isreading the status of debug with a USB key.

shutdown command errorsThis topic lists errors for the shutdown command.


Table 148. shutdown command errors


Invalid option. This command must have the -f option. The user tries to issue a command without the -f option.

slp command errorsThis topic lists errors for the slp command.

There are no unique errors for the slp command. See “Common errors” on page409 for a list of error messages that apply to all commands.

smtp command errorsThis topic lists error messages for the smtp command.


Table 149. smtp command errors


Getting SMTP server host name or IP address failed. An error occurs while the management module isreading the SMTP server host name or IP address.



Invalid host name or ip address. A user tries to set the SMTP host name or IP address toan invalid value.


Table 149. smtp command errors (continued)


Removing SMTP server name or IP address failed. An error occurs while the management module isremoving an SMTP server host name or IP address.

Setting SMTP server name or IP address failed. An error occurs while the management module is settingan SMTP server host name or IP address.

SMTP server host name or IP address is not set. A user tries to view the SMTP host name or IP addresswhen the values are not set.

snmp command errorsThis topic lists error messages for the snmp command.


Table 150. snmp command errors


Arguments containing spaces must be enclosed inquotation marks

A user tries to enter a string containing spaces that hasan opening quotation mark without a closing quotationmark.

At least one configured community is required to enableSNMP.

A user tries to enable SNMP without configuring at leastone community name.

Config failed. IP address of 0.0.0.0 is allowed only for thefirst host name in the first community.

A user tries to set an IP address of 0.0.0.0 for somethingother than the first host name of the first community.

Config failed. IP address of 0.0.0.0 is allowed only whenthe first community is configured as Get access type.

A user tries to set an IP address of 0.0.0.0 for the firsthost name of the first community when the firstcommunity is not configured with the Get access type.

Config failed. You defined a community without an IPaddress or host name.

A user tries to define a community without specifying anIP address or host name.

Config failed. You defined a duplicate community name. A user tries to define a two communities with the samename.

Enabling/Disabling snmp interface failed. An error occurs while the management module isenabling or disabling an snmp interface.

Enabling/Disabling snmp traps failed. An error occurs while the management module isenabling or disabling the snmp traps.

Enabling/Disabling SNMPv3 Agent failed. An error occurs while the management module isenabling or disabling the SNMPv3 Agent.



Invalid community name. A user tries to set a community name to an invalidvalue.

Invalid host name or ip address. A user tries to set the SNMP host name or IP address toan invalid value.

Setting access type of type for SNMPv3 failed

where type is the type of SNMPv3 access desired.

An error occurs while the management module is settingaccess type for an SNMPv3.

Setting location/contact of the SNMP agent failed. An error occurs while the management module is settingthe location or contact of the SNMP agent.


sol command errorsThis topic lists error messages for the sol command.


Table 151. sol command errors


An error occurred while disabling SOL globally. An error occurs while the management module isdisabling SOL globally.

An error occurred while disabling SOL on that blade. An error occurs while the management module isdisabling SOL on a blade server.

An error occurred while enabling SOL globally. An error occurs while the management module isenabling SOL globally.

An error occurred while enabling SOL on that blade. An error occurs while the management module isenabling SOL on a blade server.

An error occurred while reading the global SOL status. An error occurs while the management module isreading the global SOL status.

An error occurred while reading the SOL accumulatetimeout.

An error occurs while the management module isreading the SOL accumulate timeout.

An error occurred while reading the SOL retry count. An error occurs while the management module isreading the SOL retry count.

An error occurred while reading the SOL retry interval. An error occurs while the management module isreading the SOL retry interval.

An error occurred while reading the SOL send threshold. An error occurs while the management module isreading the SOL send threshold.

An error occurred while reading the SOL session statuson that blade.

An error occurs while the management module isreading the SOL session status on a blade server.

An error occurred while reading the SOL VLAN ID. An error occurs while the management module isreading the SOL VLAN ID.

An error occurred while setting the SOL accumulatetimeout.

An error occurs while the management module is settingthe SOL accumulate timeout.

An error occurred while setting the SOL blade resetsequence.


An error occurred while setting the SOL escapesequence.


An error occurred while setting the SOL retry count. An error occurs while the management module is settingthe SOL retry count.

An error occurred while setting the SOL retry interval. An error occurs while the management module is settingthe SOL retry interval.

An error occurred while setting the SOL send threshold. An error occurs while the management module is settingthe SOL send threshold.

An error occurred while setting the SOL vlan id. An error occurs while the management module isprocessing the command.

Checking if this blade supports SOL failed. An error occurs while the management module ischecking if the selected blade supports SOL.

Invalid arg for -status. Must be on or off. A user tries to enter an invalid argument for the -statuscommand option.


Table 151. sol command errors (continued)


Invalid arg for -status. Must be enabled or off. A user tries to enter an invalid argument for the -statuscommand option.

Invalid parameter. The accumulate timeout must bebetween 1 and 251 inclusive.

A user tries to enter an accumulate timeout that isoutside of the valid range.

Invalid parameter. The retry count must be between 0and 7, inclusive.

A user tries to enter a retry count that is outside of thevalid range.

Invalid parameter. The send threshold must be between 1and 251 inclusive.

A user tries to enter a send threshold that is outside ofthe valid range.

Invalid parameter. The vlan id must be between 1 and4095 inclusive.

A user tries to enter a VLAN ID that is out of range.

Retry interval range is too large. Setting to 2550. A user tries to enter a retry interval that is greater than2550 ms. If the user tries to enter a retry interval greaterthan 2550 ms, the retry interval will be set to 2550 ms.

Setting retry interval to 2500 failed. An error occurs while the management module is settingthe retry interval to 2550.

This blade does not support SOL. A user tries to issue the SOL command to a blade serverthat does not support SOL.

sshcfg command errorsThis topic lists errors for the sshcfg command.


Table 152. sshcfg command errors


Getting CLI SSH port failed. An error occurs while the management module isreading the CLI SSH port.

Getting DSA host key failed. An error occurs while the management module isreading the DSA host key.

Getting host key size failed. An error occurs while the management module isreading the host key size.

Getting installed key status failed. An error occurs while the management module isreading the installed key status.

Getting number of SSH public keys installed failed. An error occurs while the management module isreading the number of SSH public keys installed.

Getting SMASH SSH port failed. An error occurs while the management module isreading the SMASH SSH port.

When displaying host keys, -hk must be used by itself. The user tries to issue a command to display the hostkeys with option -hk.


sslcfg command errorsThis topic lists errors for the sslcfg command.


Table 153. sslcfg command errors


-dnld must be used with the -cert/-csr (server, client) aswell as -i and optionally -l

A user tries to issue a download certificate or certificatesigning request command without the -cert or -csr, and -ioptions.

-i must be provided to download a trusted certificate. A user tries to issue a downloading trusted certificatecommand without the -i option.

-upld must be used with the -cert (server, client) as wellas -i and -l

A user tries to issue an import certificate commandwithout the -cert, -l and -i options.

Cannot open file: filename

where filename is the name of the file that was enteredfor opening.

An error occurs while the management module is tryingto open a file.

Cert generation for server/client failed

where server/client specifies whether the certificate wasbeing generated for a server or client.

An error occurs while the management module isgenerating a certificate for the server or client.

CLI map failed error = error

where error specifies error.

An error occurs while the management module ismapping the file to memory.

Converting DER back to X509 format failed. An error occurs while the management module isconverting DER back to X509 format.

CSR generation for server/client failed

where server/client specifies whether the certificatesigning request was being generated for a server orclient.

An error occurs while the management module isgenerating a certificate signing request for a server orclient.

Downloading Cert/CSR to tftp server argument is failed

where:v Cert/CSR specifies whether the user tried to download

a certificate or certificate signing request.v argument identifies the IP address of the tftp server

An error occurs while the management module isdownloading a certificate or certificate signing request tothe tftp server for the SSL server or client.

Error: unknown application An error occurs because an unknown certificate type isreferred to.

Exporting Cert/CSR failed

where Cert/CSR specifies whether the user tried to exporta certificate or certificate signing request.

An error occurs while the management module isexporting a certificate or certificate signing request.


Getting filename from tfpt server argument failed

where:v filename identifies the name of the requested filev argument identifies the IP address of the tftp server

An error occurs while the management module is gettinga file from the tftp server.


Table 153. sslcfg command errors (continued)


Getting certificate status of standby AMM failed. An error occurs while the management module isreading the certificate status of the standby advancedmanagement module.

Getting failover mode failed. An error occurs while the management module isreading the failover mode.

Getting SSL Server/Client Certificate/CSR status failed. An error occurs while the management module isreading the SSL server or client certificate or certificatesigning request status.

Importing certFileName is failed

where certFileName is the name of the certificate that wasbeing imported.

An error occurs while the management module isimporting a certificate.


A user tries to issue a command with an invalidargument for the option. The length of the input isgreater than maximum.

Invalid IP arg for -option: argument. Each byte has to bein the range (0-255)

where:v option identifies the command optionv argument identifies the invalid IP address argument

A user tries to issue a command with an invalidargument for the IP Address option. One or more parts isnot in the range of 0-255.

Invalid IP arg for -option: argument. Enter 4 bytesseparated by 3 dots


A user tries to issue a command with an invalidargument for the IP Address option. Invalid argumentscould be too long, too short, or not numeric in all parts.

Invalid IP arg for -option: argument. Too few bytes


A user tries to issue a command with an invalidargument for the IP Address option, an argument whichhas fewer than four parts.

Invalid IP arg for -option: argument. Too many bytes


A user tries to issue a command with an invalidargument for the IP Address option, an argument whichhas more than four parts.

Invalid option for Cert generation: -cpwd A user tries to issue a command with an invalid option-cpwd for certification generation.

Invalid option for Cert generation: -un A user tries to issue a command with an invalid option-un for certification generation.

IPs Swaps is not configured. A user tries to issue a command for the SSLconfiguration against the Standby Server target withoutthe IPs Swaps configured.

Missing required options. A user tries to issue a command for the SSLconfiguration without entering all the required options.

No Cert/CSR available.

where Cert/CSR specifies whether the user specified acertificate or certificate signing request.

A user tries to issue a command to download anonexistent certificate or certificate signing request.


Table 153. sslcfg command errors (continued)


No tcindex available.

where index is the number of the selected trustedcertificate.

A user tries to issue a command to remove or downloada nonexistent trusted certificate.

No valid client certificate is in place. Type 'sslcfg -h' forsyntax help of the SSLclient Certificate generationcommand.

A user tries to issue a command to enable the SSL clientwithout a valid client certificate in place.

No valid server certificate is in place. Type 'sslcfg -h' forsyntax help of the SSL server Certificate generationcommand.

A user tries to issue a command to enable the SSL serverwithout a valid server certificate in place.

No valid trusted certificate is in place. Type 'sslcfg -h' forsyntax help of the SSL trusted Certificate importingcommand.

A user tries to issue a command to enable the SSL clientwithout a valid trusted certificate in place.

Putting filename to tfpt server ip_address failed.

where:v filename identifies the command optionv ip_address identifies the IP address of the tftp server

An error occurs while the management module isputting a file to the tftp server.


Writing X509 format certificate to file failed. An error occurs while the management module iswriting the X509 format certificate to File.

syslog command errorsThis topic lists errors for the syslog command.


Table 154. syslog command errors



A user tries to enter too many characters for an inputfield.

Invalid host name or ip address. A user tries to enter an invalid hostname or ip address.

Port number out of range. A user tries to enter an invalid port number.


tcpcmdmode command errorsThis topic lists error messages for the tcpcmdmode command.


Table 155. tcpcmdmode command errors


Error changing TCP command mode connection. An error occurs while the management module ischanging the TCP command mode Connection.

Error disabling tcpcmdmode. An error occurs while the management module isdisabling the TCP command mode.

Error enabling TCP command mode. An error occurs while the management module isenabling the TCP command mode.

Invalid parameter. Input must be numeric. A user tries to enter a parameter value for the -t(timeout) command option containing non-numericcharacters. For example, tcpcmdmode -t 200m.


A user tries to enter a parameter value for the -t(timeout) command option that is outside of the validrange.

Maximum connections can not exceed maximum

where maximum designates the total number of permittedconnections.

A user attempted to configure more connections than themaximum number of connections supported.


The user issues a command to enable the Secure TCPCommand Mode when a valid server certificate is not inplace.

The total number of secure and legacy connections ofTCP Command Mode cannot exceed maximum


A user attempted to configure more TCP CommandMode connections than the maximum number of secureand legacy connections supported.





telnetcfg command errorsThis topic lists error messages for the telnetcfg command.


Table 156. telnetcfg command errors


Invalid parameter. Input must be numeric. A user tries to enter a Telnet timeout value containingnon-numeric characters. For example, telnetcfg -t 200w.

Invalid parameter. The telnet timeout range must be lessthan 4294967295.

The user tries to enter a timeout value greater than4294967295 seconds.


Table 156. telnetcfg command errors (continued)



A user tries to enter a Telnet timeout value that is out ofrange.

temps command errorsThis topic lists errors for the temps command.


Table 157. temps command errors


Blade blade_number: Too many SDRs found.


A database error occurs when too many SDRs are found.

Getting power state of blade blade_number failed.


An error occurs while the management module isreading the power state of the specified blade server.

thres command errorsThis topic lists errors for the thres command.


Table 158. threshold command errors


A duplicate option is found in the requested command. The user tries to enter a duplicate argument.

Invalid threshold value. The user tries to enter an invalid threshold value.

Unable to query the threshold request. An error occurs during the query threshold request.

Unable to set the requested threshold. An error occurs during the set threshold request.

trespass command errorsThis topic lists error messages for the trespass command.


Table 159. trespass command errors


twe must be enabled to modify the trespassing warning. The user tries to issue a command to modify thetrespassing warning without the -twe enabled setting.

The trespassing warning must be quote-delimited. The user tries to enter a trespassing warning that is notenclosed in double-quotation marks.

The trespassing warning is greater than 1600 characters. The user tries to enter a trespassing warning that islonger than 1600 characters.


uicfg command errorsThe following table lists error messages for the uicfg command.


Table 160. uicfg command errors


Enabling SNMPv1/v3 failed. The SNMPv1/v3 configuration does not meet requiredcriteria. Possible configuration errors include:v A community is configured without an IP address or

host name.v A duplicate community name is configured.v At least one configured community is required to

enable SNMPv1.v IP address of 0.0.0.0 is allowed only for the first host

name in the first community.v IP address of 0.0.0.0 is allowed only when the first

community is configured as GET or SET access type.v System contact must be defined to enable

SNMPv1/v3.v System location must be defined to enable

SNMPv1/v3.

Error sanity checking of SNMP configuration. An error occurs while the management module issanity-checking the SNMP configuration.

Maximum connections can not exceed maximum


A user has attempted to configure more connections thanthe maximum number of connections supported.


The user issues a command to configure the Secure TCPCommand Mode when a valid server certificate is not inplace

Reading telnet/ssh/snmpv1/snmpv3 status failed. An error occurs while the management module isreading the telnet, ssh, snmpv1, or snmpv3 status.

The total number of secure and legacy connections ofTCP Command Mode cannot exceed maximum


A user attempted to configure more TCP CommandMode connections than the maximum number of secureand legacy connections supported.






update command errorsThis topic lists error messages for the update command.


Table 161. update command errors


-r must be used with -u to update firmware to AMM andautomatically reboot AMM if firmware update succeeds.

A user tries to enter a command with the -r option toupdate firmware to a primary advanced managementmodule, but fails to include the -u option.

Cannot perform this command right now. The agent isnot active.

A user tries to enter a command while the agent is notactive.

Disabling failover failed. An error occurs while the management module isturning off the automatic failover feature.

Error reading information for firmware imageindex.maximum

where index specifies the firmware image.

An error occurs while the management module isreading information for a specified firmware image.

Error reading the number of firmware images. An error occurs while the management module isreading the number of firmware images.

Flash operation failed. An error occurs during the flash firmware update.

Flash operation failed status percentage

where the percentage value varies based on when theproblem was encountered.

An error occurs during the flash firmware update.

Flash operation not in process or status unavailable. An error occurs during the flash firmware update.

Flash operation timed out percentage.



Flash preparation - error sending packet file filename.

where filename identifies the file being updated.


Flash preparation error. Packet percent completepercentage. Flash percent complete percentage.



Flash preparation error. Timeout on packet preparationoperation percentage.



Flashing not supported on this target. A user attempts to run the update command on amodule that does not support flash firmware updates.

Getting data encryption setting failed. If data encryptionis enabled and you are updating the firmware to a levelwhich does not support data encryption, you will lose allyour configuration settings as a result.

An error occurs while the management module isreading the data encryption setting.


Table 161. update command errors (continued)


Getting name of mm bay_number failed.

where the bay_number identifies the management modulespecified.

An error occurs while the management module isreading the name of the management module indesignated bay.

Invalid image index. Index must be less than maximum

where maximum designates the largest permitted indexvalue.

A user tries to enter an image index that is greater thanthe maximum permitted index value.

Invalid option. An invalid command option is entered. For the updatecommand, invalid command option errors include:v the -i (IP address) command option does not have an

IP address parameterv the -i (IP address) command option specifies an

invalid IP addressv attempting to enter the -i (IP address) command

option without the -n (filename) command optionv the -n (filename) command option does not have a file

name parameterv attempting to enter the -n (filename) command option

without the -i (IP address) command optionv attempting to enter the -v (verbose) command option

without the -i (IP address) command option and -n(filename) command option

v attempting to enter the -v (verbose) command optionwith the -a command option

Invalid syntax. The user tries to execute a command without specifyinga command option.

Management Module bay_number is not installed.

where the bay_number identifies the management modulespecified.

The command is targeted to a management module baywhere no management module is installed.

Rebooting AMM failed. An error occurs while the advanced managementmodule is trying to reboot.

Status: Unable to read status. An error occurs while the management module isreading status.

TFTP Error: error_code.

where the error_code can have one of the followingvalues:v Access violation.v Connection failure.v Disk full or allocation exceeded.v File already exists.v File error.v File not found.v Illegal option negotiation.v Illegal TFTP operation.v Unable to allocate memory.v Unknown transfer ID.v Unknown user.

An error occurs when the user attempts to set up theTFTP connection.

Unable to read blade server VPD bay bay_number name.

where the bay_number and name identify the blade serverby location and name.

The command specifies an empty blade server bay or anerror occurs when reading the VPD.


Table 161. update command errors (continued)


Unable to read I/O Module VPD bay bay_number name.

where the bay_number and name identify the I/O moduleby location and name.

The command specifies an empty I/O-module bay or anerror occurs when reading the VPD.

Unable to read MM VPD bay bay_number name.

where the bay_number and name identify the managementmodule by location and name.

The command specifies an empty management modulebay or an error occurs when reading the VPD.

Unable to read VPD for Blade blade_number name.

where the blade_number and name identify the bladeserver by location and name.

An error occurs while the management module isreading the VPD of the targeted blade server.

Unknown device type. The command is targeted to an unknown device type.

Update error. Invalid destination. A user tries to issue a command to a target that is notvalid.

Update Failed, there was a problem retrieving the file. The management module was unable to complete theupdate because it was unable to retrieve the file from theTFTP server.

uplink command errorsThis topic lists error messages for the uplink command.


Table 162. uplink command errors


-ip must be a valid IP address before enabling -el A user tries to issue a command to enable the -el withouta valid -ip setting.

A non-zero IP address must be set before enabling -el. A user tries to enable -el while both -ip and -ip6 are zero.

At least one IP address must be non-zero when -el isenabled.

A user tries to set both -ip and -ip6 to zero while -el isenabled.

Error converting the IPv6 address from string to bytes. An error occurs while converting the IPv6 address froma string to bytes.

Getting status of failver on Lose/Logical of Physical Linkfailed.

An error occurs while the management module isreading status of failver on Lose/Logical of PhysicalLink.

Invalid uplink delay value. A user tries to enter a delay value that is less than 1 orgreater than 255. For example, uplink -del 0.

No option argument for option

where option is the command option for which noargument was specified.

A user tries to enter a command option without itsrequired argument.

The option argument for option is out of the valid range(between 1 and 2880 minutes).

where option is the number of minutes specified.

The user input for an option is out of the range.


Table 162. uplink command errors (continued)


The option argument for option is out of the valid range(between 10 and 172800 seconds).

where option is the number of seconds specified.

The user input for an option is out of the range.

users command errorsThis topic lists error messages for the users command.


Table 163. users command errors


-af contains invalid characters. Only alphanumeric,comma, asterisk, question mark, hyphen, period, andexclamation point characters are valid.

The user input for the -af option is invalid.

-af must start with from=. The user input for the -af option is invalid.

-cm is greater than 255 characters. The user input for the -cm option exceeds the maximum.

-cm must be quote-delimited. The user input for the -cm option is not quote-delimited.

An entry cannot be modified and deleted in the samecommand.

A user tries to simultaneously modify and delete a userin the same command.


A user tries to enter a context name containing spacesthat does not have opening and closing quotation marks.

Deleting user failed. An error occurs while the management module isdeleting an user.

Error converting RBS permissions. An error occurs while the management module isconverting permissions data to the role-based security(RBS) format.

Error creating user. An error occurs while the management module iscreating a user.

Error creating user: The authentication protocol cannotbe none because the security settings require passwords.

The user tries to issue a command to create a user withno authentication protocol when the security settingsrequire passwords.

Error reading certificate details. An error occurs while the management module isreading certificate details.

Error reading key. An error occurs while the management module isreading the key.

Error setting the access type. An error occurs while the management module is settingthe access type.

Error setting the authentication protocol. An error occurs while the management module is settingthe authentication protocol.

Error setting the authority level. An error occurs while the management module is settingthe authority level.

Error setting the context name. An error occurs while the management module is settingthe context name.

Error setting the hostname/IP address. An error occurs while the management module is settingthe hostname or IP address.


Table 163. users command errors (continued)


Error setting the password. An error occurs while the management module is settingthe password.

Error setting the password. The new password is notcompliant.

The user tries to issue a command to set the newpassword which is not compliant.

Error setting the privacy password. An error occurs while the management module is settingthe privacy password.

Error setting the privacy protocol. An error occurs while the management module is settingthe privacy protocol.

Error setting the username. An error occurs while the management module is settingthe username.

Error transferring file. An error occurs while the management module istransferring file.


Getting a summary of all keys of user index failed.

where the index value varies based on the problem thatwas encountered.

An error occurs while the management module isreading a summary of all keys of the targeted user.

Getting authority level of user index failed.


An error occurs while the management module isreading authority level of the targeted user.

Getting role-based security level of user index failed.


An error occurs while the management module isreading role-based security level of the targeted user.

Incorrect login permission option: permission

where the permission value varies based on the problemthat was encountered.

A user tries to specify an invalid login permission for the-a command option.

Invalid argument. Valid arguments for -at are read, write,and traps.

A user tries to set an invalid argument for the -atcommand option.

Invalid argument. Valid choices are des or <none>. A user tries to set an invalid argument for the -ppcommand option.

Invalid argument. Valid choices are md5, sha, or <none>. A user tries to set an invalid argument for the -apcommand option.

Invalid authority level. This error message indicates one of the following errors:v A user tries to set an authority level that is invalid.v A user tries to set a custom authority level without

specifying any customization information.

Invalid device number (first number must be smaller):device_A-device_B.

where device_A and device_B identify the ends of theinvalid device range being specified.

A user specifies an invalid device range while trying tocreate or modify a user.

Invalid device number: device_number.

where device_number identifies the device number that isinvalid.

A user provides a device number that is out of rangewhile trying to create or modify a user.

Invalid hostname or ip address. A user tries to set an invalid host name or IP address forthe -i command option.




Invalid key index for this command. The user input for index is invalid.

Invalid rbs device: device.

where device identifies the device that is invalid.

A user specifies an invalid device while trying to createor modify a user.

Invalid rbs device: Must specify device number A user specifies an invalid device number while trying tocreate or modify a user.

Invalid rbs device list. A user does not specify a device list while trying tocreate or modify a user.

Invalid rbs device (must be same device): device.

where device identifies the device that is invalid.

A user specifies an invalid device while trying to createor modify a user.

Invalid rbs role: role.

where role identifies the role that is invalid.

A user specifies an invalid role while trying to create ormodify a user.

Invalid rbs role list. A user fails to specify a role list while trying to modifyor create a user.

Invalid username. The username can only containnumbers, letters, dots, and underscores.

The user tries to enter The username that containsinvalid characters. Valid characters that can be used in ausername are letters, numbers, periods (. ), andunderscores ( _ ).

Max retries changing password reached. The user tries to issue a command to change a passwordafter the max retries of changing password limit isreached.

Must be set at least one rbs role for this user. The user tries to issue a command to create a userwithout the rbs role settings.

Old password is incorrect. The user tries to issue a command to change a passwordwith an incorrect old password.

Old password must be specified by long option op. The user tries to issue a command to change a passwordwithout the -op option.

Specify your new password with '-p' option. The user tries to issue a command to change a passwordwithout the -p option.

Syntax error. -a option must have an argument. A user tries to attempt to enter the command with an -acommand option that has no argument.

Syntax error. -at option must have an argument. A user tries to attempt to enter the command with an -atcommand option that has no argument.

Syntax error. -cn option must have an argument. A user tries to attempt to enter the command with a -cncommand option that has no argument.

Syntax error. -i option must have an argument. A user tries to attempt to enter the command with an -icommand option that has no argument.

Syntax error. -n option must have an argument. A user tries to attempt to enter the command with an -ncommand option that has no argument.

Syntax error. -ppw option must have an argument. A user tries to attempt to enter the command with a-ppw command option that has no argument.

Syntax error. Multiple -a options found. A user tries to enter the -a command option in a singlecommand multiple times.

Syntax error. Multiple -ap options found. A user tries to enter the -ap option flag in a singlecommand multiple times.

Syntax error. Multiple -at options found. A user tries to enter the -at option flag in a singlecommand multiple times.




Syntax error. Multiple -cn options found. A user tries to enter the -cn option flag in a singlecommand multiple times.

Syntax error. Multiple -i options found. A user tries to enter the -i option flag in a singlecommand multiple times.

Syntax error. Multiple -n options found. A user tries to enter the -n option flag in a singlecommand multiple times.

Syntax error. Multiple -p options found. A user tries to enter the -p option flag in a singlecommand multiple times.

Syntax error. Multiple -pp options found. A user tries to enter the -pp option flag in a singlecommand multiple times.

Syntax error. Multiple -ppw options found. A user tries to enter the -ppw option flag in a singlecommand multiple times.

Syntax error. Type users -h for help. A user tries to set an invalid value for a commandoption.

The context name must be less than 32 characters long. A user tries to set a context name that is longer than 31characters.

The -i and -l options must both be specified when using-upld.

The user tries to issue a -upld command without -i and-l.

The accept_from_string must be quote-delimited. The user input for the -af option is not quote-delimited.

The key is greater than 6000 bytes. The user input for the key exceeds the maximum.

The password must be at least 5 characters long, but nomore than 15 characters long.

The user tries to enter a password that is too short or toolong.

The password must contain at least one alphabetic andone non-alphabetic character.

The user tries to enter a password that does not have atleast one alphabetic and one non-alphabetic character.

The privacy password must also be set when setting theprivacy protocol.

Displays if the user tries to set the privacy protocol todes without a specifying a privacy password (-ppwcommand option).

The privacy password must be less than 32 characterslong.

A user tries to set a privacy password that is longer than31 characters.

The user index must be different than that of the currentuser.

The user tries to issue a command to delete the accountof current user.

The username cannot be longer than 15 characters. A user tries to set a user name that is longer than 15characters.

There was a problem retrieving the file. An error occurs while the management module isretrieving the file.

Unable to change password. The minimum passwordchange interval has not expired. Please try again later.

The user tries to issue a command to change a passwordwhile the minimum password change interval has notexpired.

Unable to read the complex password requirement. An error occurs while the management module isreading the complex password requirement.

Unable to read the password required setting. An error occurs while the management module isreading the password required setting.

Unexpected error: Unable to change password. An error occurs while the management module ischanging the password.





When creating a new user, a username and authoritylevel must be specified.

The user tries to issue a command to create a userwithout the -n and -a options.

When creating a new user, all options are required. A user tries to create a new user without defining all ofthe command options and arguments.

volts command errorsThis topic lists errors for the volts command.


Table 164. volts command errors


Getting power state of blade blade_number failed.


An error occurs while the management module isreading the power state of the targeted blade server.

write command errorsThis topic lists error messages for the write command.


Table 165. write command errors


Failed to save configuration settings to the chassis. An error occurs while the management module is savingthe management module configuration to theBladeCenter unit midplane.

Firmware update is in progress. Try again later. A user tries to save the management moduleconfiguration to the BladeCenter unit midplane while themanagement module firmware is updating.

Getting security status failed. An error occurs while the management module isreading the security status.

The -config option is required. The user does not include a required -config option forthe command.

The -i, -l, and -p options can only be used with the-config file.

The user tries to specify a TFTP server and aconfiguration file when saving the configuration to theBladeCenter unit midplane.

The -i option is required with the -config file. A user tries to use the -i option with the -config chassisoption.

The -p option is required when encryption is enabled. The user tries to issue a command without the -p optionwhile encryption is enabled.

Error creating file in memory. The management module is unable to create theconfiguration file.

Error locking file. The management module is unable to lock theconfiguration file.


Table 165. write command errors (continued)


Error opening file. The management module is unable to open theconfiguration file.

Error transferring file. The management module is unable to transfer theconfiguration file.

Error generating file. The management module is unable to generate theconfiguration file.

Error allocating memory for file. The management module is unable to allocate memoryfor the configuration file.

The passphrase is greater than 1600 characters. The user input for the passphrase exceeds the maximumpermitted length.

The passphrase must be quote-delimited. The user input for the passphrase is not quote-delimited.

zonecfg command errorsThis topic lists errors for the zonecfg command.


Table 166. zonecfg command errors


Activating zone configuration xxx on I/O module yyyfailed.

The management module is unable activate the specifiedzone configuration on the specified I/O module.

Getting current active zone number failed. An error occurs while the management module isreading the current active zone number.

Getting specified configuration of switch slot failed.

where slot identifies the targeted I/O module.

An error occurs while the management module isreading the specified configuration of the targeted I/Omodule.

Getting zone configuration failed. An error occurs while the management module isreading the zone configuration.

Invalid slot number for this command. The I/O module is not in slot 3 or 4.

The index must be 32 or less. The configuration index is bigger than 32.

Zone configuration not supported on this switch type. The user tries to use this command on a non-SAS switchmodule.

The I/O Module is currently not powered on or in afault state.

The user tries to show or activate a zone configurationfor an RSS or NSS which is in the power-off state and afault state.

Error retrieving data for I/O module bay_number.

where bay_number identifies the targeted I/O module.

An error occurs while the management module isreading the data for the specified I/O module.



Appendix. Getting help and technical assistance

If you need help, service, or technical assistance or just want more informationabout IBM products, you will find a wide variety of sources available from IBM toassist you.

Use this information to obtain additional information about IBM and IBMproducts, determine what to do if you experience a problem with your IBM systemor optional device, and determine whom to call for service, if it is necessary.

Before you callBefore you call, make sure that you have taken these steps to try to solve theproblem yourself.

If you believe that you require IBM to perform warranty service on your IBMproduct, the IBM service technicians will be able to assist you more efficiently ifyou prepare before you call.v Check for updated firmware and operating-system device drivers for your IBM

product. The IBM Warranty terms and conditions state that you, the owner ofthe IBM product, are responsible for maintaining and updating all software andfirmware for the product (unless it is covered by an additional maintenancecontract). Your IBM service technician will request that you upgrade yoursoftware and firmware if the problem has a documented solution within asoftware upgrade.You can obtain the latest downloads for your IBM product fromhttp://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=MIGR-63017 .

v If you have installed new hardware or software in your environment, checkhttp://www.ibm.com/servers/eserver/serverproven/compat/us/eserver.html tomake sure that the hardware and software is supported by your IBM product.

v Use the troubleshooting information in your system documentation, and use thediagnostic tools that come with your IBM product. Information about diagnostictools is in the Problem Determination and Service Guide on the IBM DocumentationCD that comes with your product.

v Go to http://www.ibm.com/systems/support/ to check for information to helpyou solve the problem.

v Gather the following information to provide to IBM service. This data will helpIBM service quickly provide a solution to your problem and ensure that youreceive the level of service for which you might have contracted.– Hardware and Software Maintenance agreement contract numbers, if

applicable– Machine type number (IBM 4-digit machine identifier)– Model number– Serial number– Current system UEFI (or BIOS) and firmware levels– Other pertinent information such as error messages and logs

v Go to http://www.ibm.com/support/electronic/portal/ to submit an ElectronicService Request. Submitting an Electronic Service Request will start the process


http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=MIGR-63017

http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=MIGR-63017

http://www.ibm.com/servers/eserver/serverproven/compat/us/


http://www.ibm.com/support/electronic/

of determining a solution to your problem by making the pertinent informationavailable to IBM service quickly and efficiently. IBM service technicians can startworking on your solution as soon as you have completed and submitted anElectronic Service Request.

Using the documentationInformation about your IBM system and preinstalled software, if any, or optionaldevice is available in the documentation that comes with the product. Thatdocumentation can include printed documents, online documents, readme files,and help files.

See the troubleshooting information in your system documentation for instructionsfor using the diagnostic programs. The troubleshooting information or thediagnostic programs might tell you that you need additional or updated devicedrivers or other software. IBM maintains pages on the World Wide Web where youcan get the latest technical information and download device drivers and updates.To access these pages, go to http://www.ibm.com/systems/support/.

You can find the most up-to-date information for BladeCenter products athttp://publib.boulder.ibm.com/infocenter/bladectr/documentation/index.jsp.

Getting help and information from the World Wide Web

On the World Wide Web, up-to-date information about IBM systems, optionaldevices, services, and support is available at http://www.ibm.com/systems/support/.

You can find the most up-to-date product information for BladeCenter products athttp://publib.boulder.ibm.com/infocenter/bladectr/documentation/index.jsp.

Software service and supportThrough IBM Support Line, you can get telephone assistance, for a fee, with usage,configuration, and software problems with your IBM products.

For information about which products are supported by Support Line in yourcountry or region, see http://publib.boulder.ibm.com/infocenter/bladectr/documentation/index.jsp.

For more information about Support Line and other IBM services, seehttp://www.ibm.com/services/us/index.wss or see http://www.ibm.com/planetwide/ for support telephone numbers. In the U.S. and Canada, call1-800-IBM-SERV (1-800-426-7378).

Hardware service and supportYou can receive hardware service through your IBM reseller or IBM Services.

To locate a reseller authorized by IBM to provide warranty service, go tohttp://www.ibm.com/partnerworld/ and click Find Business Partners on theright side of the page. For IBM support telephone numbers, seehttp://www.ibm.com/planetwide/. In the U.S. and Canada, call 1-800-IBM-SERV(1-800-426-7378).



http://publib.boulder.ibm.com/infocenter/bladectr/documentation/index.jsp






http://www.ibm.com/services/us/index.wss

http://www.ibm.com/planetwide/


http://www.ibm.com/partnerworld/


In the U.S. and Canada, hardware service and support is available 24 hours a day,7 days a week. In the U.K., these services are available Monday through Friday,from 9 a.m. to 6 p.m.

IBM Taiwan product serviceUse this information to contact IBM Taiwan product service.

IBM Taiwan product service contact information:

IBM Taiwan Corporation3F, No 7, Song Ren Rd.Taipei, TaiwanTelephone: 0800-016-888

Appendix. Getting help and technical assistance 477


Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not applyto you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM websites are provided forconvenience only and do not in any manner serve as an endorsement of thosewebsites. The materials at those websites are not part of the materials for this IBMproduct, and use of those websites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corporation in the United States, other countries,or both. If these and other IBM trademarked terms are marked on their firstoccurrence in this information with a trademark symbol (® or ™), these symbolsindicate U.S. registered or common law trademarks owned by IBM at the time thisinformation was published. Such trademarks may also be registered or commonlaw trademarks in other countries.


A current list of IBM trademarks is available on the web at “Copyright andtrademark information” at http://www.ibm.com/legal/copytrade.shtml.

Adobe and PostScript are either registered trademarks or trademarks of AdobeSystems Incorporated in the United States and/or other countries.

Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc., inthe United States, other countries, or both and is used under license therefrom.

Intel, Intel Xeon, Itanium, and Pentium are trademarks or registered trademarks ofIntel Corporation or its subsidiaries in the United States and other countries.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc., inthe United States, other countries, or both.

Linux is a registered trademark of Linus Torvalds in the United States, othercountries, or both.

Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation inthe United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Other company, product, or service names may be trademarks or service marks ofothers.

Important notesProcessor speed indicates the internal clock speed of the microprocessor; otherfactors also affect application performance.

This product is not intended to be connected directly or indirectly by any meanswhatsoever to interfaces of public telecommunications networks, nor is it intendedto be used in a public services network.

CD or DVD drive speed is the variable read rate. Actual speeds vary and are oftenless than the possible maximum.

When referring to processor storage, real and virtual storage, or channel volume,KB stands for 1024 bytes, MB stands for 1,048,576 bytes, and GB stands for1,073,741,824 bytes.

When referring to hard disk drive capacity or communications volume, MB standsfor 1,000,000 bytes, and GB stands for 1,000,000,000 bytes. Total user-accessiblecapacity can vary depending on operating environments.

Maximum internal hard disk drive capacities assume the replacement of anystandard hard disk drives and population of all hard disk drive bays with thelargest currently supported drives that are available from IBM.

Maximum memory might require replacement of the standard memory with anoptional memory module.


http://www.ibm.com/legal/copytrade.shtml

IBM makes no representation or warranties regarding non-IBM products andservices that are ServerProven®, including but not limited to the implied warrantiesof merchantability and fitness for a particular purpose. These products are offeredand warranted solely by third parties.

IBM makes no representations or warranties with respect to non-IBM products.Support (if any) for the non-IBM products is provided by the third party, not IBM.

Some software might differ from its retail version (if available) and might notinclude user manuals or all program functionality.

Particulate contaminationAttention: Airborne particulates (including metal flakes or particles) and reactivegases acting alone or in combination with other environmental factors such ashumidity or temperature might pose a risk to the device that is described in thisdocument.

Risks that are posed by the presence of excessive particulate levels orconcentrations of harmful gases include damage that might cause the device tomalfunction or cease functioning altogether. This specification sets forth limits forparticulates and gases that are intended to avoid such damage. The limits must notbe viewed or used as definitive limits, because numerous other factors, such astemperature or moisture content of the air, can influence the impact of particulatesor environmental corrosives and gaseous contaminant transfer. In the absence ofspecific limits that are set forth in this document, you must implement practicesthat maintain particulate and gas levels that are consistent with the protection ofhuman health and safety. If IBM determines that the levels of particulates or gasesin your environment have caused damage to the device, IBM may conditionprovision of repair or replacement of devices or parts on implementation ofappropriate remedial measures to mitigate such environmental contamination.Implementation of such remedial measures is a customer responsibility.

Table 167. Limits for particulates and gases

Contaminant Limits

Particulate v The room air must be continuously filtered with 40% atmosphericdust spot efficiency (MERV 9) according to ASHRAE Standard 52.21.

v Air that enters a data center must be filtered to 99.97% efficiency orgreater, using high-efficiency particulate air (HEPA) filters that meetMIL-STD-282.

v The deliquescent relative humidity of the particulate contaminationmust be more than 60%2.

v The room must be free of conductive contamination such as zincwhiskers.

Gaseous v Copper: Class G1 as per ANSI/ISA 71.04-19853

v Silver: Corrosion rate of less than 300 Å in 30 days

Notices 481

Table 167. Limits for particulates and gases (continued)

Contaminant Limits

1 ASHRAE 52.2-2008 - Method of Testing General Ventilation Air-Cleaning Devices forRemoval Efficiency by Particle Size. Atlanta: American Society of Heating, Refrigeratingand Air-Conditioning Engineers, Inc.

2 The deliquescent relative humidity of particulate contamination is the relative humidityat which the dust absorbs enough water to become wet and promote ionic conduction.

3 ANSI/ISA-71.04-1985. Environmental conditions for process measurement and controlsystems: Airborne contaminants. Instrument Society of America, Research Triangle Park,North Carolina, U.S.A.

Documentation formatThe publications for this product are in Adobe Portable Document Format (PDF)and should be compliant with accessibility standards. If you experience difficultieswhen you use the PDF files and want to request a web-based format or accessiblePDF document for a publication, direct your mail to the following address:

Information DevelopmentIBM Corporation205/A0153039 E. Cornwallis RoadP.O. Box 12195Research Triangle Park, North Carolina 27709-2195U.S.A.

In the request, be sure to include the publication part number and title.

When you send information to IBM, you grant IBM a nonexclusive right to use ordistribute the information in any way it believes appropriate without incurring anyobligation to you.

Electronic emission notices

Federal Communications Commission (FCC) statementNote: This equipment has been tested and found to comply with the limits for aClass A digital device, pursuant to Part 15 of the FCC Rules. These limits aredesigned to provide reasonable protection against harmful interference when theequipment is operated in a commercial environment. This equipment generates,uses, and can radiate radio frequency energy and, if not installed and used inaccordance with the instruction manual, may cause harmful interference to radiocommunications. Operation of this equipment in a residential area is likely to causeharmful interference, in which case the user will be required to correct theinterference at his own expense.

Properly shielded and grounded cables and connectors must be used in order tomeet FCC emission limits. IBM is not responsible for any radio or televisioninterference caused by using other than recommended cables and connectors or byunauthorized changes or modifications to this equipment. Unauthorized changesor modifications could void the user's authority to operate the equipment.


This device complies with Part 15 of the FCC Rules. Operation is subject to thefollowing two conditions: (1) this device may not cause harmful interference, and(2) this device must accept any interference received, including interference thatmight cause undesired operation.

Industry Canada Class A emission compliance statementThis Class A digital apparatus complies with Canadian ICES-003.

Avis de conformité à la réglementation d'Industrie CanadaCet appareil numérique de la classe A est conforme à la norme NMB-003 duCanada.

Australia and New Zealand Class A statement

Attention: This is a Class A product. In a domestic environment this product maycause radio interference in which case the user may be required to take adequatemeasures.

European Union EMC Directive conformance statementThis product is in conformity with the protection requirements of EU CouncilDirective 2004/108/EC on the approximation of the laws of the Member Statesrelating to electromagnetic compatibility. IBM cannot accept responsibility for anyfailure to satisfy the protection requirements resulting from a nonrecommendedmodification of the product, including the fitting of non-IBM option cards.

Attention: This is an EN 55022 Class A product. In a domestic environment thisproduct may cause radio interference in which case the user may be required totake adequate measures.

Responsible manufacturer:

International Business Machines Corp.New Orchard RoadArmonk, New York 10504914-499-1900

European Community contact:

IBM Technical Regulations, Department M456IBM-Allee 1, 71137 Ehningen, GermanyTelephone: +49 7032 15-2937Email: [email protected]

Germany Class A statementDeutschsprachiger EU Hinweis: Hinweis für Geräte der Klasse A EU-Richtliniezur Elektromagnetischen Verträglichkeit

Dieses Produkt entspricht den Schutzanforderungen der EU-Richtlinie2004/108/EG zur Angleichung der Rechtsvorschriften über die elektromagnetischeVerträglichkeit in den EU-Mitgliedsstaaten und hält die Grenzwerte der EN 55022Klasse A ein.

Um dieses sicherzustellen, sind die Geräte wie in den Handbüchern beschrieben zuinstallieren und zu betreiben. Des Weiteren dürfen auch nur von der IBM

Notices 483

empfohlene Kabel angeschlossen werden. IBM übernimmt keine Verantwortung fürdie Einhaltung der Schutzanforderungen, wenn das Produkt ohne Zustimmung derIBM verändert bzw. wenn Erweiterungskomponenten von Fremdherstellern ohneEmpfehlung der IBM gesteckt/eingebaut werden.

EN 55022 Klasse A Geräte müssen mit folgendem Warnhinweis versehen werden:“Warnung: Dieses ist eine Einrichtung der Klasse A. Diese Einrichtung kann imWohnbereich Funk-Störungen verursachen; in diesem Fall kann vom Betreiberverlangt werden, angemessene Maßnahmen zu ergreifen und dafüraufzukommen.”

Deutschland: Einhaltung des Gesetzes über dieelektromagnetische Verträglichkeit von Geräten

Dieses Produkt entspricht dem “Gesetz über die elektromagnetische Verträglichkeitvon Geräten (EMVG)”. Dies ist die Umsetzung der EU-Richtlinie 2004/108/EG inder Bundesrepublik Deutschland.

Zulassungsbescheinigung laut dem Deutschen Gesetz über dieelektromagnetische Verträglichkeit von Geräten (EMVG) (bzw. derEMC EG Richtlinie 2004/108/EG) für Geräte der Klasse A

Dieses Gerät ist berechtigt, in Übereinstimmung mit dem Deutschen EMVG dasEG-Konformitätszeichen - CE - zu führen.

Verantwortlich für die Einhaltung der EMV Vorschriften ist der Hersteller:

International Business Machines Corp.New Orchard RoadArmonk, New York 10504914-499-1900

Der verantwortliche Ansprechpartner des Herstellers in der EU ist:

IBM DeutschlandTechnical Regulations, Department M456IBM-Allee 1, 71137 Ehningen, GermanyTelephone: +49 7032 15-2937Email: [email protected]

Generelle Informationen:

Das Gerät erfüllt die Schutzanforderungen nach EN 55024 und EN 55022 KlasseA.

Japan VCCI Class A statement


This is a Class A product based on the standard of the Voluntary Control Councilfor Interference (VCCI). If this equipment is used in a domestic environment, radiointerference may occur, in which case the user may be required to take correctiveactions.

Korea Communications Commission (KCC) statement

Please note that this equipment has obtained EMC registration for commercial use.In the event that it has been mistakenly sold or purchased, please exchange it forequipment certified for home use.

Russia Electromagnetic Interference (EMI) Class A statement

People's Republic of China Class A electronic emissionstatement

Taiwan Class A compliance statement

Notices 485


Index

Special characters! 168? 166

Aaccessibility features for this product 2accessible documentation 482account inactivity alert time

set for management module 34account inactivity disable time

set for management module 35account lockout period

set for management module 36account security commands 30account security settings

display for management module 30enable complex password for

management module userauthentication 33

enable default administrationpassword expiration formanagement module 34

enable password change at first loginto management module 36

enable password required formanagement module 37

set management module accountinactivity alert time 34

set management module accountinactivity disable time 35

set management module accountlockout period 36

set management moduleauthentication logging timeout 32

set management module CLIinactivity timeout 33

set management module default tohigh 32

set management module default tolegacy 31

set management module maximumLDAP sessions for user 36

set management module maximumnumber of login failures 35

set management module minimumnumber of different characters forpassword 34

set management module passwordexpiration time 37

set management module passwordminimum change interval 37

set management module passwordreuse cycle 38

set management module userauthentication method 33

set management module web interfaceinactivity timeout 38

accseccfg 30

accseccfg (continued)options

alt 32am 33cp, on 33ct 33dc 34de, on 34high 32ia 34ici 35id 35legacy 31lf 35lp 36mls 36pc, on 36pe 37pi 37pr, on 37rc 38wt 38

accseccfg command errors 411accseccfg commands 30

example 38accumulate timeout

set for SOL 330acknowledge alarms

alarm ID 46complete alarm key 46generator ID 45generator information 45

acknowledge call-home activity log entrymanagement module 94

acoustic mode, disable 153acoustic mode, enable 153activate firmware

I/O module 367, 371switch 367, 371

activate I/O module SAS zone 403activate network protocol settings

I/O module 241activate SAS zone

I/O module 403Active Directory group, delete 161Active Directory group, set authority

level 160Active Directory group, set name 159Active Directory groups, display

(all) 159Active Directory groups, display

(specific) 159add Call Home events

management module 140, 141add feature license

management module 144add firmware build ID list entry

blade server 81add SSH public key 392add SSH public key (specific) 392

additional SSL certificatedisable for standby management

module 337enable for standby management

module 337address

IPv6 initial connection 15link local 15

address prefix lengthset for blade server 190set for channel 0 of management

module 180set for I/O module 198

advanced failover settingsdisable network interface for standby

management module 40display for management module 40enable network interface for standby

management module and allow IPswap during failover 40

enable network interface for standbymanagement module and prevent IPswap during failover 41

advanced management moduledisable logical uplink failover 374enable logical uplink failover 374enable physical uplink failover 373logical uplink failover delay 374logical uplink failover IP address 374logical uplink failover IPv6 IP

address 375network interface management

commands 66physical uplink failover delay 373set logical link loss alert and failover

policy 375advfailover 40

optionsip. noswap 41ip. off 40ip. swap 40

advfailover command 40example 41

advfailover command errors 412air filter

set notification interval 42view notification interval 42

air filter notification 42airfilter

example 42management module 42

airfilter command0, 1, 3, 6 months 42notification interval 42

alarmacknowledge (alarm ID) 46acknowledge (complete alarm

key) 46acknowledge (generator ID) 45acknowledge (generator

information) 45


alarm (continued)clear (alarm ID) 48clear (complete alarm key) 48clear (generator ID) 47clear (generator information) 47display (alarm ID) 44display (all) 43display (complete alarm key) 44display (generator ID) 43display (generator information) 44display (power) 43options

c, a 48c, g 47c, k 48c, o 47p 43q 43q, a 44q, g 43q, k 44q, o 44r, a 46r, g 45r, k 46r, o 45s, l 49

set 49alarm command 43alarm command errors 413alarm commands

example 49alarm panel

command target 135alarm panel module

power off 272power on 272turn off 272turn on 272

alerttest 58

alert categories (enhanced legacy)disable 229enable 229

alert notification method, set 57alert recipient, create 54alert recipient, delete 53alert recipient, set email address 57alert recipient, set hostname for

alerts 58alert recipient, set IP address for

alerts 58alert recipient, set name 55alert recipient, set status 56alert recipients, manage 53alert state

display all 229alert type, filter 56alert type, set 56alertcfg 51

optionsdr 51rl 51, 52si 51

alertcfg command errors 414alertcfg commands 51

example 52

alertentries 53options

1 through 12 53create (n, status, f, t, e, i) 54del 53e 57f 56i 58n 55status 56t 57test 58

alertentries command 53alertentries command errors 414alertentries commands

example 59alerts

disable monitoring for all critical 229disable monitoring for all

informational 234disable monitoring for all

warning 232disable monitoring for blade device

critical 230disable monitoring for blade device

informational 235disable monitoring for blade device

warning 232disable monitoring for chassis

critical 231disable monitoring for chassis

informational 236disable monitoring for chassis

warning 233disable monitoring for cooling device

critical 231disable monitoring for cooling device

informational 238disable monitoring for cooling device

warning 234disable monitoring for event log

informational 237disable monitoring for event log

warning 233disable monitoring for I/O module

critical 230disable monitoring for I/O module

informational 235disable monitoring for I/O module

warning 232disable monitoring for inventory

change informational 236disable monitoring for network

change informational 237disable monitoring for power module

critical 231disable monitoring for power module

informational 238disable monitoring for power module

warning 234disable monitoring for power state

informational 236disable monitoring for storage module

critical 230disable monitoring for storage module

informational 235

alerts (continued)disable monitoring for storage module

warning 233disable monitoring for system

management critical 231disable monitoring for system

management informational 236disable monitoring for system

management warning 233disable monitoring for user activity

informational 237display all states 229enable monitoring for all critical 229enable monitoring for all

informational 234enable monitoring for all

warning 232enable monitoring for blade device

critical 230enable monitoring for blade device

informational 235enable monitoring for blade device

warning 232enable monitoring for chassis

critical 231enable monitoring for chassis

informational 236enable monitoring for chassis

warning 233enable monitoring for cooling device

critical 231enable monitoring for cooling device

informational 238enable monitoring for cooling device

warning 234enable monitoring for event log

informational 237enable monitoring for event log

warning 233enable monitoring for I/O module

critical 230enable monitoring for I/O module

informational 235enable monitoring for I/O module

warning 232enable monitoring for inventory

change informational 236enable monitoring for network change

informational 237enable monitoring for power module

critical 231enable monitoring for power module

informational 238enable monitoring for power module

warning 234enable monitoring for power state

informational 236enable monitoring for storage module

critical 230enable monitoring for storage module

informational 235enable monitoring for storage module

warning 233enable monitoring for system

management critical 231enable monitoring for system

management informational 236


alerts (continued)enable monitoring for system

management warning 233enable monitoring for user activity

informational 237exclude service information with

email alerts 51include service information with email

alerts 51alerts, display 164

timestamp 164algorithms, encryption 14all information reload 204assistance, getting 475attributes, display for firmware 363Australia Class A statement 483authentication logging timeout

set for management module 32authentication method

LDAP 215authority, command 8autoftp

optionsdesc 60i 61m 61p 61pw 61u 61

autoftp command errors 415autoftp commands 60

example 62autoftp settings

call-home 60, 61automatic configuration setting

display for management module 280automatic power-on policy

set for BladeCenter unit 275

Bbattery backup unit

command target 134baud rate

set for serial port of managementmodule 253

bay datablade server 63clear bay data 63clear bay data for specific bay 64display bay data 63display bay data for specific bay 63set bay data 64set data definition to specific blade

server 65baydata 63

optionsb bay_num 63b bay_num -clear 64b bay_num -data

"data_definition" 65clear 63data "data_definition" 64

baydata command errors 415baydata commands 63

example 65

binding methodLDAP 215

blade mezzaninecommand target 133

blade server 185, 186add firmware build ID list entry 81all blade servers 78bay data 63boot 72boot (to console) 72collect service data 299command target 132config command 111, 114

example 114create firmware build ID list 80cycle power 72, 273delete all entries from firmware build

ID list 84delete entry from firmware build ID

list 85dhcpinfo commands 117disable cKVM 185disable DHCPv6 191disable Ethernet channel 190disable IPv6 190disable IPv6 stateless

auto-configuration 191display all SRC records 124display bay data 63display boot mode 74display boot sequence 75display cKVM status 184display Ethernet-over-USB

setting 137display firmware build IDs 80display management network DHCP

configuration 117display name 111display network configuration

status 184display power state 273display service data 299display specific SRC record 124display temperature 355display voltage 400dump service data 299enable cKVM 185enable DHCPv6 configuration 191enable dynamic power optimizer 155enable dynamic power optimizer,

extended 156enable Ethernet channel 189enable IPv6 190enable IPv6 stateless

auto-configuration 191enable local power control 275enable power capping 154enable power management 154enable power saver mode 155enable Wake on LAN 274export firmware build ID list 86get service data 299import firmware build ID list 85power off 272, 273power on 272, 273power on (to console) 272, 273reset 72, 286

blade server (continued)reset (clear NVRAM) 289reset (enter SMS menu) 290reset (run diagnostics with boot

sequence) 289reset (run diagnostics) 289reset (to console) 72, 287reset (with NMI) 288set address prefix length 190set as KVM owner 208set as media tray owner 239set boot mode 74set boot sequence 76, 78set Ethernet channel configuration

method 188set Ethernet channel gateway IP

address (IPv4) 186set Ethernet channel gateway/default

route (IPv6) 187set Ethernet channel hostname 189set Ethernet channel subnet mask

(IPv4) 187set Ethernet channel VLAN ID 188set Ethernet-over-USB setting 137set I/O module for blade server

management traffic 184set IP address (IPv4) 185set IP address (IPv6) 186set name 111set power capping 154shutdown 273, 306turn off 272, 273turn on 272, 273turn on (to console) 272, 273update firmware build ID in firmware

build ID list 83update firmware build revision in

firmware build ID list 84update firmware type in firmware

build ID list 83update machine type in firmware

build ID list 82update manufacturer in firmware

build ID list 82blade server ISMP

set IP address (IPv4) 191blade server module

display activity 228display information 228

blade server power information display(overview) 149

blade server, display powertrending 151, 152

blade serversdisable multiple video sessions 192enable multiple video sessions 192

BladeCenter Open Fabric ManagerBladeCenter units 66I/O modules 66management module 66, 67, 68, 69,

70, 71network interface management

commands 66NIC allocation 66

BladeCenter S 150display

power management policies 251

Index 489

BladeCenter T specific commands 29BladeCenter unit

command target 132configuring 20disable global cKVM 193disable management channel

auto-discovery 227display management channel

auto-discovery status 227display network settings 192display serial number 111display type/model 111display uuid 111enable global cKVM 193enable management channel

auto-discovery 227set automatic power-on policy 275set VLAN ID 192

BladeCenter unitsclear list of discovered 284display all discovered 283display filtered by IP address 283display filtered by name 284display health for all discovered 283

blink location LED 169, 222blower

command target 134blower power information display 149blower temperature display 149blower, display power trending 151, 152BMC

command target 133bofm

optionsl , i 66l , i, d 67l , i, d on 68l , i, p off 70l , i, p on 69l , i, v 71

bofm commandexample 71

bofm command errors 416bofm commands 66boot 72

blade server 72options

c 72p powercycle 72p reset 72

boot (to console)blade server 72

boot command errors 417boot commands 72

example 73boot mode

display for blade server 74set for blade server 74

boot sequencedisplay for blade server 75set for all blade servers 78set for blade server 76

bootmode 74options

p 74bootmode command errors 417bootmode commands 74

bootmode commands (continued)example 74

bootseq 75cd 76floppy 76hd0 76hd1 76hd2 76hd3 76hd4 76hyper 76iscsi 76iscsicrt 76legacy 76nodev 76nw 76options

all 78uefi 76usbdisk 76

bootseq command errors 418bootseq commands 75

example 79buildidcfg 80

optionsab 81create 80db 84, 85export 86import 85ub, ft 83ub, id 83ub, mfg 82ub, mt 82ub, rev 84

buildidcfg command errors 418buildidcfg commands 80

example 86built-in commands 27

Ccall-home

autoftp settings 60, 61problem description 95test call home 96

call-home activity logacknowledge call-home activity log

entry for management module 94display for management module 93display FTP/TFTP server entries for

management module 93display IBM Support entries for

management module 93unacknowledge call-home activity log

entry for management module 94capture service information 124certificate file (SSL CSR)

download 342import 343upload 343

certificate file (SSL self-signed certificate)download 342import 343upload 343

change command environment 25, 131change user password 385

chassis internal network commandcin 97

chassis internal networkconfiguration 97

chassis internal network status 102chassis internal network status

command 102chconfig 87

optionsca 89cci 89ce 89cn 89co 89cph 89cs 89cz 89li 87loc 91po 91ps 91pw 91sa 88sc 89u 91

chconfig command errors 419chconfig commands 87

example 91China Class A electronic emission

statement 485chlog 93

optionsack 94f 93s 93

chlog command errors 420chlog commands 93

example 94chmanual

optionsdesc 95, 96

chmanual command errors 421chmanual commands 95

example 96cin 97

optionsentry_index -ip ip_address 99entry_index clear 98entry_index en 98entry_index id 99global en 97id 100vlan_id -ip ip_address 99

CINturn all index entries on or off 98

cin alloptions

clear 97en state 98

cin commandchassis internal network 97

cin command errors 421cin commands

example 100cin configuration

Specify VLAN ID 100CIN configuration 98


CIN configuration entries 97CIN configuration entry

create 99delete 98disable 98enable 98Specify IP address 99

CIN configuration tabledisplay for management module 97

CIN index entrycreate 99Specify IP address 99

CIN stateset for enable or disable 97

CIN status table entries 102cinstatus 102cinstatus command 102cinstatus commands

example 102cKVM

disable for blade server 185disable globally for BladeCenter

unit 193enable for blade server 185enable globally for BladeCenter

unit 193cKVM status

display for blade server 184Class A electronic emission notice 482clear

optionscnfg 103

clear alarmsalarm ID 48complete alarm key 48generator ID 47generator information 47

clear CIN configurationmanagement module 97

clear command 103clear command errors 423clear commands

example 104clear event log

management module 105clear for management module 97clear management module event log

commands 105example 105

clearlogl 105

clearlog command errors 423clearlog commands 105

example 105CLI

exit codes for SSH 20CLI inactivity timeout

set for management module 33CLI key sequence

set for SOL 332CLI SSH server

disable for management module 336enable for management module 336

clock 106options

d 106dst 109

clock (continued)options (continued)

g 107t 106

clock command errors 423clock commands 106

example 110clock settings

display for management module 106collect service data

blade server 299command

health 163, 164system physical configuration 225

command authority 8command environment selecting 6command history 168command redirect 25, 131command syntax 29command target 25, 131

alarm panel 135battery backup unit 134blade mezzanine 133blade server 132BladeCenter unit 132blower 134BMC 133disk drive 135high-speed expansion card 133I/O module 134I/O-expansion card 133integrated system management

processor 133management card 133management module 132media tray 134memory 133microprocessor 133multiplexer expansion module 135network clock module 135power module 134service processor 133storage expansion unit 133storage module 135switch module 134temporary 7view 225

command target selection 6command-line interface

enable for management module 359errors 407guidelines 5

case sensitivity 6command history 6data types 6delimiters 6help 6options 5output format 6strings 6

introduction 1starting 14using 5, 25

command-line session configurationdisplay for management module 354

command-line timeoutset for management module 354

commandsaccseccfg 30, 38Active Directory, group

authentication 159advfailover 40, 41airfilter 42alarm 43, 49alertcfg 51, 52alertentries 53, 59autoftp 60, 62baydata 63, 65bofm 66, 71boot 72, 73bootmode 74bootseq 75, 79buildidcfg 80, 86built-in 27chconfig 87, 91chlog 93, 94chmanual 95, 96cin 100cin command 97cinstatus 102cinstatus command 102clear 103, 104clear management module event

log 105clearlog 105clock 106, 110common 27config 111, 114configuration 27console 115, 116dhcpinfo 117, 118discovery 28display management module

call-home events in events log 93display management module event

log 119, 123displaylog 119, 123displaysd 124, 125dns 126, 129environment 131, 136ethoverusb 137event log, clear for management

module 105event log, display for management

module 93, 119, 123eventinfo 138, 139events 140, 141examples

account security 38accseccfg 38advfailover 41alarm 49, 223alertcfg 52alertentries 59autoftp 62baydata 65blade server name 114BladeCenter Open Fabric

Management 71bofm 71boot 73bootmode 74bootseq 79buildidcfg 86

Index 491

commands (continued)examples (continued)

chconfig 91chlog 94chmanual 96cin 100cinstatus 102clear 104clear management module event

log 105clearlog 105clock 110config 114configure automated message

settings 62console 116DHCP settings for management

module 118dhcpinfo 118display automated message

settings 62display call-home owner 96display KVM owner 209display management module event

log 123display management module

security 303display media tray owner 240display Service Advisor owner 91display service information

owner 301displaylog 123displaysd 125DNS 129env 136environment 136environment redirect 136Ethernet network settings for

management module 200ethoverusb 137eventinfo 139events 141exit 143feature 146files 147fuelg 156groups 162health 164help 166history 168I/O management 71I/O module network protocol

configuration 244identify 170ifconfig 200info 205iocomp 206kvm 209LDAP configuration for

management module 218ldapcfg 218list 225management module DHCP

settings 118management module DNS 129management module Ethernet

network settings 200


management module event logclear 105

management module event logdisplay 123

management module LDAPconfiguration 218

management module name 114management module network port

configuration 270management module restore

configuration 282management module save

configuration 402management module serial port

settings 254management module service 304management module SLP

configuration 307management module SMTP

settings 310management module SNMP

settings 326management module SSH 336management module telnet

configuration 354management module uplink

failover 375mcad 227modactlog 228monalerts 238mt 240name for blade server 114name for management

module 114nat 244network port configuration for

management module 270network protocol configuration for

I/O module 244ntp 247ping 249pmpolicy 252portcfg 254ports 270power 277rdoc 279read 282remotechassis 284reset 290restore configuration for

management module 282save configuration for

management module 402scale 298sddump 300sdemail 301security 303Serial Over LAN 333serial port settings for

management module 254service 304set call-home 96set KVM owner 209set management module

security 303


set media tray owner 240set Service Advisor 91set service information 301shutdown 306slp 307SLP configuration for management

module 307smtp 310SMTP settings for management

module 310snmp 326SNMP settings for management

module 326sol 333SSH configuration for management

module 336sshcfg 336sslcfg 346syntax help 166syslog 350tcpcmdmode 353telnetcfg 354temps 355trespass 357uicfg 361update 371uplink 375user account security 38user interface configuration 361users 398volts 400write 402zonecfg 404

exit 143feature 144, 146files 147fuelg 149, 156group authentication, Active

Directory 159groups 159, 162help 166history 168identify 169, 170ifconfig 171, 200info 203, 205iocomp 206kvm 208, 209ldapcfg 210, 218led 220, 223LED 29list 225management module event log 28management module failover 373,

375mcad 227memory 29modactlog 228monalerts 229, 238monalertsleg 229mt 239, 240nat 241, 244ntp 245, 247ping 248, 249pmpolicy 251, 252portcfg 253, 254


commands (continued)ports 255, 270power 272, 277power control 29power management 29power management policy 251rdoc 278, 279read 280, 282remotechassis 283, 284reset 286, 290reset command 29restore configuration 29save configuration 29scale 291, 298sddump 299, 300sdemail 301security 303Serial Over LAN 328, 333service 304session command 29shutdown 306slp 307smtp 309, 310snmp 312, 326SOL 328, 333sshcfg 335, 336sslcfg 337, 346syslog 347, 350system management command 29tcpcmdmode 351, 353telnet configuration 354telnetcfg 354temps 355trespass 356, 357uicfg 359, 361update 363, 371uplink 373, 375user interface configuration 359, 361users 377, 398volts 400write 401, 402zonecfg 403, 404

comment SSH public key 398common commands 27common errors 409communicating with IBM Systems

Director 351communication

out-of-band 351test I/O-module IP address 249test IP address 248test IP address (I/O-module) 249

communication rateset for serial port of management

module 253compatibility

I/O moduledisplay details for blade

server 206display details for I/O

module 206display for all components 206

component and reloadinginformation 203

component information display 203config 111

config (continued)options

contact 112, 113, 114loc 112name 111

config command 111example 114

config command errors 424configuration

disable automatic for managementmodule 282

enable automatic for managementmodule 281

save for management module (tochassis) 401

view for management module 225view tree for system 225

configuration (encryption)save for management module (to

file) 402configuration (no encryption)

save for management module (tofile) 401

configuration commands 27configuration from file (encryption)

restore for management module 281configuration from file (no encryption)

restore for management module 280configuration from midplane

restore for management module 280configuration information

display for network card 184configuration method

set for channel 0 of managementmodule 176

set for channel of blade server 188configure LDAP command

example 218configure network ports command

example 270configure network protocols command

example 244configure SLP command

example 307confirm password

LDAP distinguished name 216connect to SSH public key 397console 115

create override SOL session 115create SOL session 115non-persistent session 115options

l 115o 115

persistent console 115console command 115console command errors 425console commands

example 116contact information

Service Advisor 89contact information, Service Advisor

city 89company 89contact name 89country 89email address 89

contact information, Service Advisor(continued)

phone number 89postal code 89state 89street address 89

contact namedisplay for management module 111set for management module 112, 113,

114contamination, particulate and

gaseous 481create alert recipient 54create CIN configuration entry 99create CIN index entry 99create firmware build ID list

blade server 80create override SOL session 115create partition

scalable complex 294create partition (automatically)

scalable complex 292create SOL session 115

persistent console 115create stand-alone partition

scalable complex 293create stand-alone partition

(automatically)scalable complex 292

create user 381critical alerts

disable monitoring for all 229disable monitoring for blade

device 230disable monitoring for chassis 231disable monitoring for cooling

device 231disable monitoring for I/O

module 230disable monitoring for power

module 231disable monitoring for storage

module 230disable monitoring for system

management 231enable monitoring for all 229enable monitoring for blade

device 230enable monitoring for chassis 231enable monitoring for cooling

device 231enable monitoring for I/O

module 230enable monitoring for power

module 231enable monitoring for storage

module 230enable monitoring for system

management 231CSR

generate for LDAP client 341generate for management module web

server 341CSR (SSL)

download certificate file 342import certificate file 343upload certificate file 343

Index 493

cycle powerblade server 72, 273I/O module 273switch module 273

Ddata encryption

display management modulesetting 303

enable for management module 303data rate



datedisplay for management module 106set for management module 106

daylight-savings time modeset for management module 109

daylight-savings time settingdisplay for management module 106

default IP address 15delete Active Directory group 161delete alert recipient 53delete all entries from firmware build ID

listblade server 84

delete all partitionsscalable complex 294

delete CIN configuration 98delete entry from firmware build ID list

blade server 85delete file

management module 147delete partition

scalable complex 295delete user 378DHCP configuration

display for I/O module 117DHCP settings for management module

commandsexample 118

dhcpinfo 117options

eth0 117dhcpinfo command errors 426dhcpinfo commands 117

example 118DHCPv6

disable for blade server 191disable for I/O module 198disable for management module 180enable for blade server 191enable for I/O module 198enable for management module 180

disableadditional SSL certificate for standby

management module 337blade server Ethernet channel VLAN

ID 189BladeCenter unit VLAN ID 192CLI SSH server for management

module 336enhanced legacy alert categories 229

disable (continued)logging of login events from same IP

address 35monitoring for all critical alerts 229monitoring for all informational

alerts 234monitoring for all warning alerts 232monitoring for blade device critical

alerts 230monitoring for blade device

informational alerts 235monitoring for blade device warning

alerts 232monitoring for chassis critical

alerts 231monitoring for chassis informational

alerts 236monitoring for chassis warning

alerts 233monitoring for cooling device critical

alerts 231monitoring for cooling device

informational alerts 238monitoring for cooling device warning

alerts 234monitoring for event log informational

alerts 237monitoring for event log warning

alerts 233monitoring for I/O module critical

alerts 230monitoring for I/O module

informational alerts 235monitoring for I/O module warning

alerts 232monitoring for inventory change

informational alerts 236monitoring for network change

informational alerts 237monitoring for power module critical

alerts 231monitoring for power module

informational alerts 238monitoring for power module

warning alerts 234monitoring for power state

informational alerts 236monitoring for storage module critical

alerts 230monitoring for storage module

informational alerts 235monitoring for storage module

warning alerts 233monitoring for system management

critical alerts 231monitoring for system management

informational alerts 236monitoring for system management

warning alerts 233monitoring for user activity

informational alerts 237secure TCP command mode 352Service Advisor 88SMASH SSH server for management

module 336SSL for LDAP client 338

disable (continued)SSL for management module web

server 337syslog event log transmission for

collector 1 347syslog event log transmission for

collector 2 348TCP command mode 351

disable automatic configurationmanagement module 282

disable CIN configuration entry 98disable cKVM

blade server 185disable DHCPv6

blade server 191I/O module 198management module 180

disable Ethernet channelblade server 190

disable Ethernet channel 1management module 184

disable global cKVMBladeCenter unit 193

disable IPv6blade server 190I/O module 197management module 179

disable IPv6 stateless auto-configurationblade server 191I/O module 198management module 180

disable logical uplink failoveradvanced management module 374management module (advanced) 374

disable management channelauto-discovery

BladeCenter unit 227disable multiple video sessions

blade servers 192disable NAT table

I/O module 244disable NEBS environment mode 153disable network interface

management module (standby) 40disable power domain acoustic

mode 153disable SOL

global 331disable static IPv6 configuration

I/O module 197management module 179

disable technician debugmanagement module 304

disable user 379discovered BladeCenter units

clear list 284display all 283display filtered by IP address 283display filtered by name 284display health for all 283

discovery commands 28disk drive 135display

alert state 229clock settings, management

module 106date, management module 106


display (continued)daylight-savings time setting,

management module 106GMT offset, management

module 106management channel path

information 204power management policy

all domains 251BladeCenter S 251specified power domain 251

TCP command-mode sessionstatus 351

TCP command-mode sessiontimeout 351

time, management module 106display (reset counter) event log

management module 119display active users 377display activity

blade server module 228display advanced failover settings

management module 40display alarms

alarm ID 44all 43complete alarm key 44generator ID 43generator information 44power 43

display alert properties (allrecipients) 53

display alert properties (singlerecipient) 53

display alerts 164timestamp 164

display all Active Directory groups 159display all BladeCenter units on

network 283display all event log entries

management module 119display all event log filters

management module 119display all information

scalable complex 291display all users 377display automatic configuration setting

management module 280display blade server power information

overview 149display blade server SRC record

(specific) 124display blade server SRC records

(all) 124display blower power information 149display blower temperature 149display boot mode

blade server 74display call-home activity log

management module 93display call-home event management

module event log entries 93display CIN configuration table 97display cKVM status

blade server 184

display command-line sessionconfiguration

management module 354display component information 203display configuration information

network card 184display contact name

management module 111display DHCP configuration

I/O module 117display DNS configuration

management module 126display DSA host key information

management module 335display entries of CIN status table 102display Ethernet channel 0 configuration

management module (primary) 171management module (standby) 172

display Ethernet channel 0 DHCPconfiguration

management module 117display Ethernet channel 1 configuration

management module (primary) 181display Ethernet-over-USB setting

blade server 137display event description

management module 138display event log

management module 119display event log entries filtered by date

management module 120display event log entries filtered by

severity levelmanagement module 120

display event log entries filtered bysource

management module 120, 121display event user action

management module 138, 139display events list

management module 140display failover configuration

management module 373display features

management module 144display file list

management module 147display firmware attributes 363display firmware build IDs

blade server 80display free space

management module 140, 147display FTP/TFTP server call-home

activity logmanagement module 93

display global remote alert settingsmanagement module 51

display health for BladeCenter units onnetwork 283

display health status 163, 164timestamp 164

display health status (tree) 163display I/O module compatibility

all components 206display I/O module compatibility details

blade server 206I/O module 206

display I/O module powerinformation 149

display I/O module SAS zoneinformation 404

display I/O module SAS zone list 403display IBM Support call-home activity

logmanagement module 93

display informationblade server module 228

display IP addressesI/O module 248

display KVM owner 208display LDAP settings

management module 210display LED state

blower fault 220external port link status 220fanpack fault 220fault 220for blade server and all

sub-components 221for blade server front panel 220safe-to-remove 220

display licensesmanagement module 144

display locationmanagement module 111

display log entries with call-home eventsmanagement module 119

display log entries with Event IDmanagement module 119

display management channelauto-discovery status

BladeCenter unit 227display management module account

security settings 30display management module data

encryption setting 303display management module event log

commands 119example 123

display management modulesecurity 303

display management module status 124display management network DHCP

configurationblade server 117

display media tray owner 239display media tray temperature 149display name

blade server 111management module 111

display network configuration statusblade server 184

display network port settingsmanagement module 255switch 269

display network protocol settingsI/O module 241

display network settingsBladeCenter unit 192I/O module 193

display node informationscalable complex 291

display NTP configurationmanagement module 245

Index 495

display open portsmanagement module 255

display partition informationscalable complex 291

display POST statusI/O module 276switch module 276

display power domain informationdetails 150

display power domain informationoverview 149

display power stateblade server 273I/O module 273switch module 273

display power trending (bladeserver) 151, 152

display power trending (blower) 151,152

display power trending (I/Omodule) 151, 152

display power trending (media tray) 152display power trending (power

domain) 151, 152display power trending (system) 151,

152display RSA host key information

management module 335display SAS zone information

I/O module 404display SAS zone list

I/O module 403display serial number

BladeCenter unit 111display serial port configuration

management module 253display Service Advisor 87display service data

blade server 299display service data command 124display service information 124display service setting

management module 304display single user 378display SLP settings

management module 307display SMTP server host name

management module 309display SMTP server IP address

management module 309display SNMP configuration

management module 312display specific Active Directory

groups 159display specific complex information

scalable complex 291display SSH public key 391display SSH status

management module 335display state

location LED 169display state of -lse option

management module 122Display status of first five CIN

entries 102display syslog configuration

management module 347

display telnet configurationmanagement module 354

display temperatureblade server 355management module 355media tray 355

display trespass feature statusmanagement module 356

display type/modelBladeCenter unit 111

display uplink configurationmanagement module 373

display user interface settingsmanagement module 359

display uuidBladeCenter unit 111

display various LED statesLED states 220

display voltageblade server 400management module 400

displaylog 119display log entries with call-home

events 119display log entries with Event ID 119display state of -lse option 122filter log entries by call-home events

flag 122options

-lse 122a 119c 119ch 122date 120e 119f 119filters 119i 122i, l 122l 122l, i 122lse 122sev 120src 120, 121

displaylog command errors 426displaylog commands 119

example 123displaysd 124

optionsi 124i, save 124mmstat 124save 124save, i 124src 124

displaysd command errors 427displaysd commands 124

example 125distinguished name

LDAP client 216distinguished name password

LDAP client 216distinguished name password (confirm)

LDAP client 216dns 126

options-ddns 126

dns (continued)options (continued)

i1 127i2 127i3 127i61 128i62 128i63 128on 126p 129

DNSenable for management module 126

dns command errors 428dns commands 126

example 129DNS configuration

display for management module 126DNS first IPv4 IP address

set for management module 127DNS first IPv6 IP address

set for management module 128DNS second IPv4 IP address

set for management module 127DNS second IPv6 IP address

set for management module 128DNS server priority

set for management module 129DNS third IPv4 IP address

set for management module 127DNS third IPv6 IP address

set for management module 128documentation

using 476documentation format 482Domain Catalog discovery

set search domain 211domain name


set for management module LDAPserver 211

download 344, 345, 346download certificate file

SSL CSR 342SSL self-signed certificate 342

download SSH public key 396DSA host key information

display for management module 335dump service data

blade server 299duplex mode



dynamic DNSenable for management module 126

dynamic power optimizer, enable forblade server 155

dynamic power optimizer, extended ,enable for blade server 156

Eelectronic emission Class A notice 482Electronic emission notices 482


email alertsexclude service information 51include service information 51

enableadditional SSL certificate for standby

management module 337blade server Ethernet channel VLAN

ID 189BladeCenter unit VLAN ID 192CLI SSH server for management

module 336enhanced legacy alert categories 229monitoring for all critical alerts 229monitoring for all informational

alerts 234monitoring for all warning alerts 232monitoring for blade device critical

alerts 230monitoring for blade device

informational alerts 235monitoring for blade device warning

alerts 232monitoring for chassis critical

alerts 231monitoring for chassis informational

alerts 236monitoring for chassis warning

alerts 233monitoring for cooling device critical

alerts 231monitoring for cooling device

informational alerts 238monitoring for cooling device warning

alerts 234monitoring for event log informational

alerts 237monitoring for event log warning

alerts 233monitoring for I/O module critical

alerts 230monitoring for I/O module

informational alerts 235monitoring for I/O module warning

alerts 232monitoring for inventory change

informational alerts 236monitoring for logging of login events

from same IP address 35monitoring for network change

informational alerts 237monitoring for power module critical

alerts 231monitoring for power module

informational alerts 238monitoring for power module

warning alerts 234monitoring for power state

informational alerts 236monitoring for storage module critical

alerts 230monitoring for storage module

informational alerts 235monitoring for storage module

warning alerts 233monitoring for system management

critical alerts 231

enable (continued)monitoring for system management

informational alerts 236monitoring for system management

warning alerts 233monitoring for user activity

informational alerts 237secure TCP command mode 352Service Advisor 88SMASH SSH server for management

module 336SSL for LDAP client 338SSL for management module web

server 337syslog event log transmission for

collector 1 347syslog event log transmission for

collector 2 348TCP command mode 352

enable automatic configurationmanagement module 281

enable CIN configuration entry 98enable cKVM

blade server 185enable command-line interface

management module 359enable complex password for


enable data encryptionmanagement module 303

enable default administration passwordexpiration for management module 34

enable DHCPv6blade server 191I/O module 198management module 180

enable DNSmanagement module 126

enable dynamic DNSmanagement module 126

enable dynamic power optimizer forblade server 155

enable dynamic power optimizer,extended, for blade server 156

enable Ethernet channelblade server 189

enable Ethernet channel 1management module 183

enable external managementI/O module 196

enable external portsI/O module 196

enable fast POSTI/O module 275, 276

enable FTPmanagement module 261

enable global cKVMBladeCenter unit 193

enable HTTPS portmanagement module 262

enable IPv6blade server 190I/O module 197management module 179

enable IPv6 stateless auto-configurationblade server 191

enable IPv6 stateless auto-configuration(continued)

I/O module 198management module 180

enable local KVM switchingglobally 208

enable local media tray switchingglobally 239

enable local power controlblade server 275globally 274

enable logical uplink failoveradvanced management module 374management module (advanced) 374

enable management channelauto-discovery

BladeCenter unit 227enable monitoring of event log state

management module 122enable multiple video sessions

blade servers 192enable NAT table

I/O module 244enable NEBS environment mode 153enable network interface and allow IP

swapmanagement module (standby) 40

enable network interface and prevent IPswap

management module (standby) 41enable NTP

management module 245, 262enable password change at first login to

management module 36enable password required for

management module 37enable physical uplink failover

advanced management module 373management module (advanced) 373

enable portswitch 269

enable power capping for bladeserver 154

enable power domain acousticmode 153

enable power management for bladeserver 154, 155

enable power saver mode for bladeserver 155

enable protected modeI/O module 197

enable RDEmanagement module 263

enable RDOCEmanagement module 263

enable remote media tray switchingglobally 240

enable secure SMASH over SSHmanagement module 264

enable secure TCP command modemanagement module 266, 360

enable securitymanagement module 303

enable SLPmanagement module 263

enable SMASH over Telnetmanagement module 264

Index 497

enable SNMP agentmanagement module (SNMPv1) 312management module (SNMPv3) 312

enable SNMP trapsmanagement module 265, 312

enable SNMPv1management module 359

enable SNMPv1 agentmanagement module 264

enable SNMPv3management module 359

enable SNMPv3 agentmanagement module 265

enable SOLglobal 330

enable SSH portmanagement module 265

enable static IPv6 configurationI/O module 197management module 179

enable TCP command modemanagement module 266, 360

enable technician debugmanagement module 304

enable Telnet portmanagement module 267

enable TFTPmanagement module 267

enable trespass featuremanagement module 356

enable user 379enable V3 authentication for NTP

management module 246enable Wake on LAN

blade server 274globally 274

enable web interfacemanagement module 361

encryption algorithms 14end session 143ending an SOL session 23, 115enhanced legacy alert categories

disable 229enable 229

entries of the CIN status tabledisplay for management module 102

env 132, 133options

bbu 134be 133blade 132blower 134ckvm 133cpu 133disk 135exp 133hsec 133mgmtcrd 133mt 134mux 135ncc 135power 134sb 133sp 133storage 135switch 134

env (continued)options (continued)

system (managementmodule) 132

tap 135env command errors 428env commands

example 136environment

alarm panel 135blade mezzanine 133blade server 132BladeCenter unit 132blower 134BMC 133disk drive 135high-speed expansion card 133I/O module 134I/O-expansion card 133integrated system management

processor 133management card 133management module 132media tray 134memory 133microprocessor 133multiplexer expansion module 135network clock module 135power module 134service processor 133storage expansion unit 133storage module 135switch module 134

environment commands 131example 136

errorsaccseccfg command 411advfailover command 412alarm command 413alertcfg command 414alertentries command 414autoftp command 415baydata command 415bofm command 416boot command 417bootmode command 417bootseq command 418buildidcfg command 418chconfig command 419chlog command 420chmanual command 421cin command 421clear command 423clearlog command 423clock command 423command-line interface 407common 409config command 424console command 425dhcpinfo command 426displaylog command 426displaysd command 427dns command 428env command 428ethoverusb command 428eventinfo command 429events command 429

errors (continued)exit command 430feature command 430files command 432fuelg command 433groups command 436health command 436help command 437history command 437identify command 437ifconfig command 438info command 442iocomp command 443kvm command 443ldapcfg command 443led command 444list command 445mcad command 445modactlog command 445monalerts command 445monalertsleg command 446mt command 446nat command 446ntp command 447ping command 447pmpolicy command 448portcfg command 448ports command 448power command 450rdoc command 450read command 451remotechassis command 452reset command 452scale command 453sddump command 454sdemail command 454security command 455service command 455shutdown command 455slp command 455smtp command 455snmp command 456sol command 457sshcfg command 458sslcfg command 459syslog command 461tcpcmdmode command 462telnetcfg command 462temps command 463thres command 463trespass command 463uicfg command 464update command 465uplink command 467users command 468volts command 472write command 472zonecfg command 473

Ethernetconfiguring remote connection 21

Ethernet channeldisable for blade server 190enable for blade server 189

Ethernet channel 0 address prefix lengthset for management module 180


Ethernet channel 0 configurationdisplay for management module

(primary) 171display for management module

(standby) 172Ethernet channel 0 configuration method

set for management module 176Ethernet channel 0 data rate

set for management module 177Ethernet channel 0 DHCP configuration

display for management module 117Ethernet channel 0 domain name

set for management module 179Ethernet channel 0 duplex mode

set for management module 177Ethernet channel 0 gateway IP address

(IPv4)set for management module 174

Ethernet channel 0 gateway/default route(IPv6)

set for management module 174Ethernet channel 0 hostname

set for management module 175set for standby management

module 176Ethernet channel 0 MAC address

set for management module 178set for standby management

module 178Ethernet channel 0 MTU

set for management module 177Ethernet channel 0 static IP address

(IPv4)set for management module 173set for standby management

module 173Ethernet channel 0 static IP address

(IPv6)set for management module 173set for standby management

module 174Ethernet channel 0 subnet mask (IPv4)

set for management module 175Ethernet channel 1


Ethernet channel 1 configurationdisplay for management module

(primary) 181Ethernet channel 1 data rate

set for management module 182Ethernet channel 1 duplex mode

set for management module 182Ethernet channel 1 gateway IP address

(IPv4)set for management module 181

Ethernet channel 1 MAC addressset for management module 183

Ethernet channel 1 MTUset for management module 183

Ethernet channel 1 static IP address(IPv4)

set for management module 181Ethernet channel 1 subnet mask (IPv4)

set for management module 182Ethernet channel configuration method

set for blade server 188

Ethernet channel gateway IP address(IPv4)

set for blade server 186Ethernet channel gateway/default route

(IPv6)set for blade server 187

Ethernet channel hostnameset for blade server 189

Ethernet channel static IP address (IPv4)set for blade server 185

Ethernet channel static IP address (IPv6)set for blade server 186

Ethernet channel subnet mask (IPv4)set for blade server 187

Ethernet channel VLAN IDset for blade server 188

Ethernet network settings formanagement module commands

example 200Ethernet-over-USB setting

display for blade server 137set for blade server 137

ethoverusb 137options

s 137ethoverusb command errors 428ethoverusb commands 137

example 137European Union EMC Directive

conformance statement 483event description

display 138event log

clear for management module 105display (reset counter) for

management module 119display all entries for management

module 119display all filters for management

module 119display entries for management

module, filtered by date 120display entries for management

module, filtered by severitylevel 120

display entries for managementmodule, filtered by source 120, 121

display for management module 119enable monitoring of state 122save to TFTP server 122

event log, clear for management modulecommands 105

event log, display for call-home eventmanagement module entries 93

event log, display for managementmodule commands 119

event user actiondisplay 138, 139

eventinfo 138, 139eventinfo command errors 429eventinfo commands 138

example 139events 140

options-add 140-rm 141

events command errors 429

events commands 140example 141

exit 143exit codes (CLI)

Secure Shell server 20exit command 143exit command errors 430exit commands

example 143export datacenter feature licenses

management module 145export firmware build ID list

blade server 86external management

enable for I/O module 196external ports

enable for I/O module 196

Ffailover configuration

display for management module 373fast POST

enable for I/O module 275, 276FCC Class A notice 482feature 144

options-add 144-apply 145-remove 144-retrieve 145

feature command errors 430feature commands 144

example 146feature license

add for management module 144remove from management

module 144feature licenses

export for datacenter 145import from datacenter 145

featuresdisplay for management module 144

files 147options

d 147files command errors 432files commands 147

example 147filter alert type 56filter log entries by call-home events flag

management module 122firmware

display attributes 363update 364, 368

I/O module 365, 366, 367, 369,370, 371

switch 365, 366, 367, 369, 370, 371verbose 366, 370

update (verbose) 365, 368firmware build ID

update in firmware build ID list 83firmware build ID list

add entry for blade server 81create for blade server 80delete all entries 84delete entry 85

Index 499

firmware build ID list (continued)export for blade server 86import for blade server 85update firmware build ID for blade

server 83update firmware build revision for

blade server 84update firmware type for blade

server 83update machine type for blade

server 82update manufacturer for blade

server 82firmware build IDs

display for blade server 80firmware build revision

update in firmware build ID list 84firmware requirements 2firmware type

update in firmware build ID list 83firmware update 363flash location LED 169, 222forest name

set for Global Catalog discovery 211set for management module LDAP

server 211FTP

enable for management module 261FTP data port number

set for management module 256FTP port number

set for management module 256FTP timeout

set for management module 268fuelg 149, 150

optionsam 153dps 155e 153fpop 156int 152pcap 154pm 151pme 154, 155pt 151, 152tt 152

fuelg command errors 433fuelg commands 149

example 156

Ggaseous contamination 481gateway IP address (IPv4)



set for channel of blade server 186set for I/O module 194, 199

gateway IP address (IPv6)set for I/O module 195

gateway/default route (IPv6)set for channel 0 of management

module 174set for channel of blade server 187

generateCSR (LDAP client) 341CSR (management module web

server) 341self-signed certificate (LDAP

client) 339self-signed certificate (management

module web server) 339generate host key

management module 335generate syslog test message

management module 350generate test alert 58Germany Class A statement 483get service data

blade server 299getting help 476global

enable local KVM switching 208enable local media tray

switching 239enable local power control 274enable remote media tray

switching 240enable Wake on LAN 274

Global Catalog discoveryset forest name 211

global disableSOL 331

global enableSOL 330

GMT offsetdisplay for management module 106set for management module 107

group filterLDAP 217

group LDAP authentication, managementmodule 159

group search attributeLDAP 217

groups 159options

a 160clear 161n 159

groups command 159groups command errors 436groups commands

example 162guidelines

case sensitivity 6command history 6data types 6delimiters 6help 6options 5output format 6overview of 5strings 6

Hhardware requirements 2hardware service and support telephone

numbers 476health 163

health (continued)display for all BladeCenter units on

network 283display status 163display status (tree) 163display status and alerts 164display status and alerts with

timestamp 164options

f 164l 163t 164

health command 163, 164example 164

health command errors 436help 25, 166

getting 475help command 166help command errors 437help commands

example 166help, World Wide Web 476high-speed expansion card

command target 133history 168history command 168history command errors 437history commands

example 168host key

generate for managementmodule 335

host nameset for blade server 189set for channel 0 of management

module 175set for channel 0 of standby

management module 176HTTP port number

set for management module 257HTTP proxy setup

Service Advisor 91HTTPS port

enable for management module 262HTTPS port number

set for management module 257

II/O module

activate network protocolsettings 241

activate SAS zone 403BladeCenter Open Fabric

Manager 66bofm 66, 67, 68, 69, 70, 71bofm commands 66command target 134cycle power 273dhcpinfo commands 117disable DHCPv6 198disable IPv6 197disable IPv6 stateless

auto-configuration 198disable NAT table 244disable static IPv6 configuration 197display DHCP configuration 117


I/O module (continued)display IP addresses 248display network protocol

settings 241display network settings 193display POST status 276display power state 273display SAS zone information 404display SAS zone list 403enable DHCPv6 configuration 198enable external management 196enable external ports 196enable fast POST 275, 276enable IPv6 197enable IPv6 stateless

auto-configuration 198enable NAT table 244enable protected mode 197enable static IPv6 configuration 197I/O management commands 66keep new IP address configuration

after reset 195nat command 241, 244

example 244power off 272power on 272, 273reset 286reset (extended diagnostics) 288reset (full diagnostics) 288reset (standard diagnostics) 287reset configuration 103reset network protocol settings 241revert to old IP address configuration

after reset 195set address prefix length 198set gateway IP address (IPv4) 194set gateway IP address (IPv6) 195set IP address (IPv4) 194set IP address (IPv6) 194set NAT external port number 243set NAT internal port number 243set NAT protocol ID 242set NAT protocol name 242set RAID IP address (IPv4) 199set subnet mask (IPv4) 196turn off 272turn on 273

I/O module compatibilitydisplay details for blade server 206display details for I/O module 206display for all components 206

I/O module for blade servermanagement traffic

set for blade server 184I/O module power information

display 149I/O module, display power

trending 151, 152I/O-expansion card

command target 133I/O-module IP address

ping 249test communication 249

IBM Systems Directorcommunication 351

IBM Taiwan product service 477identify 169

identify (continued)options

s 169s, d 169

identify command 169identify command errors 437identify commands

example 170ifconfig 184, 192, 193

optionsckvm 185ckvm, enabled 193dhcp6 198em, enabled 196ep, enabled 196eth0 171eth0, c 176eth0, d 177eth0, dhcp6 180eth0, dn 179eth0, g 174eth0, g6 174eth0, i 173eth0, i6 173eth0, ipv6 179eth0, ipv6static 179eth0, l 178eth0, m 177eth0, n 175eth0, o 172eth0, o, i 173eth0, o, i6 174eth0, o, l 178eth0, o, n 176eth0, p6 180eth0, r 177eth0, s 175eth0, sa6 180eth1 181eth1, d 182eth1, down 184eth1, g 181eth1, i 181eth1, iom 184eth1, l 183eth1, m 183eth1, r 182eth1, s 182eth1, up 183ethx 184ethx, c 188ethx, dhcp6 191ethx, down 190ethx, g 186ethx, g6 187ethx, i 185ethx, i6 186ethx, ipv6 190ethx, n 189ethx, p6 190ethx, s 187ethx, sa6 191ethx, up 189ethx, v 188ethx, ve 189g 194, 199g6 195

ifconfig (continued)options (continued)

i 191, 194, 199i6 194ipv6 197ipv6static 197ir 199maxv 192p6 198pip 195pm, enabled 197s 196, 200sa6 198v 192ve 192

ifconfig command errors 438ifconfig commands 171

example 200import 344, 345, 346import certificate file


import datacenter feature licensesmanagement module 145

import firmware build ID listblade server 85

important notices 480Industry Canada Class A emission

compliance statement 483info 203

optionspath 204reload, all 204reload, fw 204reload, hw 204reload, mac 204reload, wwn 204

info command 203info command errors 442info commands

example 205information

display for specific scalablecomplex 291

information (all)display for scalable complex 291

information about components andreloading components 203

information center 476information display, blade server power

(overview) 149information display, blower power 149information display, component 203information display, I/O module

power 149information display, power domain

(detailed) 150information display, power domain

(overview) 149information LED

turn off 221information reload, all 204information reload, firmware 204information reload, hardware 204information reload, MAC addresses 204information reload, WWN 204

Index 501

informational alertsdisable monitoring for all 234disable monitoring for blade


device 238disable monitoring for event log 237disable monitoring for I/O

module 235disable monitoring for inventory

change 236disable monitoring for network

change 237disable monitoring for power


state 236disable monitoring for storage


management 236disable monitoring for user

activity 237enable monitoring for all 234enable monitoring for blade


device 238enable monitoring for event log 237enable monitoring for I/O

module 235enable monitoring for inventory

change 236enable monitoring for network

change 237enable monitoring for power


state 236enable monitoring for storage


management 236enable monitoring for user

activity 237integrated system management processor

command target 133iocomp 206iocomp command errors 443iocomp commands 206

example 206IP address

CIN configuration entry 99CIN index entry 99display BladeCenter units on network

filtered by 283ping 248test communication 248

IP address (I/O-module)ping 249test communication 249

IP address (IPv4)set for blade server 185set for blade server ISMP 191set for I/O module 194

IP address (IPv4) (continued)set for management module 173set for standby management

module 173IP address (IPv6)

set for blade server 186set for I/O module 194set for management module 173set for standby management

module 174IP address configuration

keep new after reset 195revert to old after reset 195

IP address, default 15IP addresses

display for I/O module 248IPv6

disable for blade server 190disable for I/O module 197disable for management module 179enable for blade server 190enable for I/O module 197enable for management module 179

IPv6 configuration (static)disable for I/O module 197disable for management module 179enable for I/O module 197enable for management module 179

IPv6 stateless auto-configurationdisable for blade server 191disable for I/O module 198disable for management module 180enable for blade server 191enable for I/O module 198enable for management module 180

ISMPreset 286

JJapan VCCI Class A statement 484Japan Voluntary Control Council for

Interference Class A statement 484JS20 blade server commands

reset (clear NVRAM) 289reset (run diagnostics with boot

sequence) 289reset (run diagnostics) 289reset (with NMI) 288

JSxx blade server commandsreset (enter SMS menu) 290

Kkeep new IP address configuration after

resetI/O module 195

Korea Communications Commissionstatement 485

kvm 208options

b 208local 208

KVMdisplay owner 208set owner 208

kvm command errors 443kvm commands 208

example 209KVM port

set state for managementmodule 262

LLDAP client

generate CSR 341generate self-signed certificate 339

LDAP client distinguished nameset for management module 216

LDAP client distinguished namepassword

set for management module 216LDAP client distinguished name

password (confirm)set for management module 216

LDAP group filterset for management module 217

LDAP group search attributeset for management module 217

LDAP login permission attributeset for management module 218

LDAP nameset for management module 210

LDAP root distinguished nameset for management module 214

LDAP security versionset for management module 210

LDAP server (first) host nameset for management module 212

LDAP server (first) IP addressset for management module 212

LDAP server (first) port numberset for management module 213

LDAP server (fourth) host nameset for management module 213

LDAP server (fourth) IP addressset for management module 213

LDAP server (fourth) port numberset for management module 214

LDAP server (second) host nameset for management module 212

LDAP server (second) IP addressset for management module 212

LDAP server (second) port numberset for management module 213

LDAP server (third) host nameset for management module 212

LDAP server (third) IP addressset for management module 212

LDAP server (third) port numberset for management module 214

LDAP server authentication methodset for management module 215

LDAP server binding methodset for management module 215

LDAP server discovery methodset for management module 211

LDAP server domain nameset for management module 211

LDAP server forest nameset for management module 211


LDAP settingsdisplay for management module 210

LDAP UID search attributeset for management module 215

ldapcfg 210options

aom 215bm 215cd 216cp 216dn 211fn 211gf 217gsa 217i1 212i2 212i3 212i4 213lpa 218p 216p1 213p2 213p3 214p4 214rd 214server 211t 210usa 215v 210

ldapcfg command 210example 218

ldapcfg command errors 443led 220

optionse 220info 220info off 221l 220, 221loc 220, 222loc, d 223r 220

LED (information)turn off 221

LED (location), control 169led command 220led command errors 444led commands

example 223LED commands 29LED state

display (blade server frontpanel) 220

display (external port linkstatus) 220

display (fault) 220display (for blade server and all

sub-components) 221display (safe-to-remove) 220display (state for blower fault

LED) 220display (state for fanpack fault

LED) 220display various LED states 220

licensesdisplay for management module 144

light location LED 169, 222time period 223

light location LED (BladeCenter unit)time period 169

link local address 15list 225

optionsl 225

list commandexample 225

list command errors 445local KVM switching

enable globally 208local media tray switching

enable globally 239local power control

enable for blade server 275enable globally 274

locationdisplay for management module 111set for management module 112

location LEDblink 169, 222display state 169flash 169, 222light 169, 222

time period 223light (BladeCenter unit)

time period 169turn off 169, 222

location LED control 169logging

disable for logging of login eventsfrom same IP address 35

enable for logging of login eventsfrom same IP address 35

logical link loss alert and failover policyset for advanced management

module 375set for management module

(advanced) 375login permission attribute

LDAP 218

MMAC address


set for channel 0 of standbymanagement module 178


machine typeupdate in firmware build ID list 82

manage alert recipients 53management card

command target 133management channel auto-discovery

disable for BladeCenter unit 227enable for BladeCenter unit 227

management channel auto-discoverystatus

display for BladeCenter unit 227management channel path information

display 204management module

account security commands 30, 66accseccfg 30

management module (continued)accseccfg commands 30, 38acknowledge call-home activity log

entry 94add Call Home events 140, 141add feature license 144add SSH public key 392add SSH public key (specific) 392advfailover command 40, 41

example 41airfilter 42autoftp commands 60, 62bay data 63bofm 66, 67, 68, 69, 70, 71bofm commands 66, 71cabling 12change user password 385chconfig commands 87, 91chmanual commands 95, 96cin commands 97cinstatus commands 102clear CIN configuration entries 97clear event log 105clear event log commands

example 105command target 132command-line session

configuration 354command-line timeout 354comment SSH public key 398config command 111, 114

example 114configuring 21connect to SSH public key 397create alert recipient 54create user 381default IP address 15delete Active Directory group 161delete alert recipient 53delete CIN configuration 98delete file 147delete user 378DHCP settings commands

example 118dhcpinfo commands 117, 118direct connection 13disable automatic configuration 282disable CIN configuration entry 98disable CLI SSH server 336disable DHCPv6 180disable Ethernet channel 1 184disable IPv6 179disable IPv6 stateless

auto-configuration 180disable network interface for

standby 40disable SMASH SSH server 336disable static IPv6 configuration 179disable technician debug 304disable user 379display (reset counter) event log 119display account security settings 30display active users 377display advanced failover settings 40display alert properties (all

recipients) 53

Index 503

management module (continued)display alert properties (single

recipient) 53display all Active Directory

groups 159display all event log entries 119display all event log filters 119display all users 377display automatic configuration

setting 280display call-home activity log 93display CIN configuration table 97display clock settings 106display contact name 111display date 106display daylight-savings time

setting 106display DNS configuration 126display DSA host key

information 335display entries of CIN status

table 102display Ethernet channel 0 DHCP

configuration 117display event description 138display event log 119display event log commands

example 123display event log entries filtered by

date 120display event log entries filtered by

severity level 120display event log entries filtered by

source 120, 121display event user action 138, 139display events list 140display features 144display file list 147display free space 140, 147display FTP/TFTP server call-home

activity log 93display global remote alert

settings 51display GMT offset 106display IBM Support call-home

activity log 93display LDAP settings 210display licenses 144display location 111display log entries with call-home

events 119display log entries with Event ID 119display name 111display network port settings 255display NTP configuration 245display open ports 255display RSA host key

information 335display serial port configuration 253display service setting 304display single user 378display SLP settings 307display SMTP server host name 309display SMTP server IP address 309display SNMP configuration 312display specific Active Directory

groups 159

management module (continued)display SSH public key 391display SSH status 335display state of -lse option 122display status 124Display status of first five CIN

entries 102display syslog configuration 347display temperature 355display time 106display trespass feature status 356display user interface settings 359display voltage 400display volume information 278dns commands 126, 129

example 129download SSH public key 396enable automatic configuration 281enable CIN configuration entry 98enable CLI SSH server 336enable command-line interface 359enable complex password 33enable data encryption 303enable default administration

password expiration 34enable DHCPv6 configuration 180enable DNS 126enable dynamic DNS 126enable Ethernet channel 1 183enable FTP 261enable HTTPS port 262enable IPv6 179enable IPv6 stateless

auto-configuration 180enable monitoring of event log

state 122enable network interface for standby

and allow IP swap 40enable network interface for standby

and prevent IP swap 41enable NTP 245, 262enable password change at first

login 36enable password required 37enable RDE 263enable RDOCE 263enable secure SMASH over SSH 264enable secure TCP command

mode 266, 360enable security 303enable SLP 263enable SMASH over Telnet 264enable SMASH SSH server 336enable SNMP agent (SNMPv1) 312enable SNMP agent (SNMPv3) 312enable SNMP traps 265, 312enable SNMPv1 359enable SNMPv1 agent 264enable SNMPv3 359enable SNMPv3 agent 265enable SSH port 265enable static IPv6 configuration 179enable TCP command mode 266, 360enable technician debug 304enable Telnet port 267enable TFTP 267enable trespass feature 356

management module (continued)enable user 379enable V3 authentication for

NTP 246enable web interface 361Ethernet network settings commands

example 200export datacenter feature

licenses 145failover configuration 373filter alert type 56filter log entries by call-home events

flag 122generate host key 335generate syslog test message 350IBM Systems Director

communication 351ifconfig commands 171, 200import datacenter feature

licenses 145kvm commands 208, 209ldapcfg command 210, 218

example 218map image 278mcad commands 227mount volume 278mt commands 239, 240network connection 13portcfg commands 253, 254ports command 255, 270

example 270read CIN status table entries 102read command 280, 282

example 282remotechassis command 283, 284

example 284remove feature license 144remove SSH public key 393replace SSH public key 395reset (failover) 287reset (force failover) 287reset (primary) 286reset (standby) 286reset configuration (keep logs) 103reset network port settings 256restore configuration from file

(encryption) 281restore configuration from file (no

encryption) 280restore configuration from

midplane 280save configuration to chassis 401save configuration to file

(encryption) 402save configuration to file (no

encryption) 401save event log to TFTP server 122sdemail commands 301security commands 30, 303serial connection 14, 17serial port settings commands

example 254service command

example 304service commands 304set account inactivity alert time 34set account inactivity disable time 35


management module (continued)set account lockout period 36set account security default to

high 32set account security default to

legacy 31set Active Directory group authority

level 160set Active Directory group name 159set alert notification method 57set alert recipient email address 57set alert recipient name 55set alert recipient status 56set alert type 56set authentication logging timeout 32set CIN state for global enable or

disable 97set CLI inactivity timeout 33set contact name 112, 113, 114set date 106set daylight-savings time mode 109set DNS first IPv4 IP address 127set DNS first IPv6 IP address 128set DNS second IPv4 IP address 127set DNS second IPv6 IP address 128set DNS server priority 129set DNS third IPv4 IP address 127set DNS third IPv6 IP address 128set Ethernet channel 0 address prefix

length 180set Ethernet channel 0 configuration

method 176set Ethernet channel 0 data rate 177set Ethernet channel 0 domain

name 179set Ethernet channel 0 duplex

mode 177set Ethernet channel 0 gateway IP

address (IPv4) 174set Ethernet channel 0

gateway/default route (IPv6) 174set Ethernet channel 0 hostname 175set Ethernet channel 0 MAC

address 178set Ethernet channel 0 MTU 177set Ethernet channel 0 static IP

address (IPv4) 173set Ethernet channel 0 static IP

address (IPv6) 173set Ethernet channel 0 subnet mask

(IPv4) 175set Ethernet channel 1 data rate 182set Ethernet channel 1 duplex

mode 182set Ethernet channel 1 gateway IP

address (IPv4) 181set Ethernet channel 1 MAC

address 183set Ethernet channel 1 MTU 183set Ethernet channel 1 static IP

address (IPv4) 181set Ethernet channel 1 subnet mask

(IPv4) 182set first LDAP server host name 212set first LDAP server IP address 212set first LDAP server port

number 213

management module (continued)set fourth LDAP server host

name 213set fourth LDAP server IP

address 213set fourth LDAP server port

number 214set FTP data port number 256set FTP port number 256set FTP timeout 268set GMT offset 107set hostname for alerts 58set HTTP port number 257set HTTPS port number 257set IP address (IPv4) 173set IP address (IPv6) 173set IP address for alerts 58set LDAP client distinguished

name 216set LDAP client distinguished name

password 216set LDAP client distinguished name

password (confirm) 216set LDAP group filter 217set LDAP group search attribute 217set LDAP login permission

attribute 218set LDAP name 210set LDAP root distinguished

name 214set LDAP security version 210set LDAP server binding method 215set LDAP server discovery

method 211set LDAP server domain name 211set LDAP server for authentication

only 215set LDAP server forest name 211set LDAP UID search attribute 215set location 112set maximum LDAP sessions for

user 36set maximum number of login

failures 35set maximum number of simultaneous

sessions for user 388set minimum number of different

characters for password 34set name 111set NTP server hostname 245set NTP server IP address 245set NTP server key 246set NTP update frequency 246set password expiration time 37set password minimum change

interval 37set password reuse cycle 38set privacy password (SNMPv3) 390set Remote Presence port

number 257set second LDAP server host

name 212set second LDAP server IP

address 212set second LDAP server port

number 213

management module (continued)set secure TCP command mode port

number 260set serial port baud rate 253set serial port communication

rate 253set serial port parity 253set serial port stop bits 254set server host name 309set server IP address 309set SLP address type 307set SLP multicast address 307set SLP port number 258set SMASH Telnet port number 258set SMTP e-mail server domain

name 310set SNMP agent port number 259set SNMP community 1 first host

name 314set SNMP community 1 first host

name - get 316set SNMP community 1 first host

name to set 315set SNMP community 1 IP address

(first host) 314set SNMP community 1 IP address

(first host) to get 316set SNMP community 1 IP address

(first host) to set 315set SNMP community 1 IP address

(second host) 317set SNMP community 1 IP address

(third host) 318set SNMP community 1 name 313set SNMP community 1 second host

name 317set SNMP community 1 third host

name 318set SNMP community 1 view type

(SNMPv3) 318set SNMP community 2 first host

name 319set SNMP community 2 IP address




name 320set SNMP community 2 third host


(SNMPv3) 321set SNMP community 3 first host

name 322set SNMP community 3 IP address




name 323

Index 505

management module (continued)set SNMP community 3 third host


(SNMPv3) 324set SNMP contact name 325set SNMP location 326set SNMP traps port number 259set SSH port number 260set state for KVM port 262set syslog event log collector 1 IP

address 348set syslog event log collector 1 port

number 349set syslog event log collector 2 IP

address 348set syslog event log collector 2 port

number 349set syslog filter level 347set TCP command mode port

number 260set TCP command-mode timeout 268set Telnet port number 261set Telnet port timeout 268set TFTP port number 261set third LDAP server host name 212set third LDAP server IP address 212set third LDAP server port

number 214set time 106set trespass feature message 356set trespass feature to default 357set tsyslog event log collector 1 host

name 348set tsyslog event log collector 2 host

name 348set user access type (SNMPv3) 390set user authentication method 33set user authentication protocol

(SNMPv3) 389set user authority level 386set user context name (SNMPv3) 388set user hostname (SNMPv3

traps) 391set user IP address (SNMPv3

traps) 391set user name 383set user password 384set user privacy protocol

(SNMPv3) 389set web interface inactivity

timeout 38slp command 307

example 307smtp commands 309, 310SMTP settings commands

example 310snmp commands 312, 326SNMP settings commands

example 326SSH connection 18sshcfg command 335, 336

example 336SSL certificate status 337SSL status 337synchronize with NTP server 247telnet configuration 354

management module (continued)telnet timeout 354terminate user session 377trespass command 356, 357

example 357turn secure TCP command mode on

or off 267, 361turn TCP command mode on or

off 266, 360unacknowledge call-home activity log

entry 94unlock user 380unmount volume 278uplink configuration 373upload SSH public key 394view configuration 225view power management policy 252write command 401, 402

example 402management module (advanced)

disable logical uplink failover 374enable logical uplink failover 374enable physical uplink failover 373logical uplink failover delay 374logical uplink failover IP address 374logical uplink failover IPv6 IP

address 375physical uplink failover delay 373set logical link loss alert and failover

policy 375management module (primary)

display Ethernet channel 0configuration 171


reset 286management module (standby)


reset 286set Ethernet channel 0 hostname 176set Ethernet channel 0 MAC

address 178set Ethernet channel 0 static IP


address (IPv6) 174set IP address (IPv4) 173set IP address (IPv6) 174

management module air filtercommand 42

management module event logcommands 28

management module failovercommands 373

management module telnet configurationcommands

example 354management module uplink failover

commandsexample 375

management module web servergenerate CSR 341generate self-signed certificate 339

management module, group LDAPauthentication 159

management module, user accounts 377

management network DHCPconfiguration

display for blade server 117management-module firmware 2manufacturer

update in firmware build ID list 82map image

advanced management modulevolume 278

maximum LDAP sessions for userset for management module 36

maximum number of login failuresset for management module 35

mcad 227options

e 227mcad command errors 445mcad commands 227

example 227media tray

command target 134display owner 239display temperature 355set owner 239

media tray temperature display 149media tray, display power trending 152memory

command target 133memory commands 29microprocessor

command target 133minimum number of different characters

for passwordset for management module 34

modactlog 228modactlog command errors 445modactlog commands 228

example 228module (blade server)

display activity 228display information 228

monalerts 229options

ca 229cb 230ccd 231ccsm 231ciom 230, 233, 235cpm 231ec 229ia 234ib 235icd 238icsm 236iel 237iinv 236iiom 235inc 237ipm 238ipon 236iua 237wa 232wb 232wcd 234wcsm 233wel 233wiom 232


monalerts (continued)options (continued)

wpm 234monalerts command errors 445monalerts commands 229

example 238monalertsleg command errors 446monalertsleg commands 229monitoring

disable for all critical alerts 229disable for all informational

alerts 234disable for all warning alerts 232disable for blade device critical

alerts 230disable for blade device informational

alerts 235disable for blade device warning

alerts 232disable for chassis critical alerts 231disable for chassis informational

alerts 236disable for chassis warning alerts 233disable for cooling device critical

alerts 231disable for cooling device

informational alerts 238disable for cooling device warning

alerts 234disable for event log informational

alerts 237disable for event log warning

alerts 233disable for I/O module critical

alerts 230disable for I/O module informational

alerts 235disable for I/O module warning

alerts 232disable for inventory change

informational alerts 236disable for network change

informational alerts 237disable for power module critical

alerts 231disable for power module

informational alerts 238disable for power module warning

alerts 234disable for power state informational

alerts 236disable for storage module critical

alerts 230disable for storage module

informational alerts 235disable for storage module warning

alerts 233disable for system management

critical alerts 231disable for system management

informational alerts 236disable for system management

warning alerts 233disable for user activity informational

alerts 237enable for all critical alerts 229

monitoring (continued)enable for all informational

alerts 234enable for all warning alerts 232enable for blade device critical

alerts 230enable for blade device informational

alerts 235enable for blade device warning

alerts 232enable for chassis critical alerts 231enable for chassis informational

alerts 236enable for chassis warning alerts 233enable for cooling device critical

alerts 231enable for cooling device

informational alerts 238enable for cooling device warning

alerts 234enable for event log informational

alerts 237enable for event log warning

alerts 233enable for I/O module critical

alerts 230enable for I/O module informational

alerts 235enable for I/O module warning

alerts 232enable for inventory change

informational alerts 236enable for network change

informational alerts 237enable for power module critical

alerts 231enable for power module

informational alerts 238enable for power module warning

alerts 234enable for power state informational

alerts 236enable for storage module critical

alerts 230enable for storage module

informational alerts 235enable for storage module warning

alerts 233enable for system management critical

alerts 231enable for system management

informational alerts 236enable for system management

warning alerts 233enable for user activity informational

alerts 237mount volume

advanced management module 278mt 239

optionsb 239local 239remote 240

mt command errors 446mt commands 239

example 240

MTUset for channel 0 of management

module 177set for channel 1 of management

module 183multiple video sessions

disable for blade servers 192enable for blade servers 192

multiplexer expansion modulecommand target 135reset (failover) 287

Nname

display BladeCenter units on networkfiltered by 284

display for blade server 111display for management module 111set for blade server 111set for management module 111

name (contact)set for management module 112, 113,

114nat 241

optionsactivate 241en 244ep 243ip 243pi 242pn 242reset 241

nat command 241example 244

nat command errors 446NAT external port number

set for I/O module 243NAT internal port number

set for I/O module 243NAT protocol ID

set for I/O module 242NAT protocol name

set for I/O module 242NAT table

disable for I/O module 244enable for I/O module 244

NEBS, disable 153network card

display configurationinformation 184

network clock modulecommand target 135power off 272power on 272turn off 272turn on 272

network configuration statusdisplay for blade server 184

network interfacedisable for standby management


module and allow IP swap duringfailover 40

Index 507

network interface (continued)enable for standby management

module and prevent IP swap duringfailover 41

network port settingsdisplay for management module 255display for switch 269reset for management module 256

network protocol settingsactivate for I/O module 241display for I/O module 241reset for I/O module 241

network settingsdisplay for BladeCenter unit 192display for I/O module 193

New Zealand Class A statement 483node information

display for scalable complex 291notes, important 480notices 479

electronic emission 482FCC, Class A 482

notification method, set for alerts 57ntp 245

optionsen, enabled 245f 246i 245synch 247v3 246v3en, enabled 246

NTPenable for management module 245,

262ntp command 245

example 247ntp command errors 447NTP configuration

display for management module 245NTP server

synchronize management moduleclock 247

NTP server hostnameset for management module 245

NTP server IP addressset for management module 245

NTP server keyset for management module 246

NTP update frequencyset for management module 246

Oonline documentation 1open ports

display for management module 255options

a 102f 102

out-of-band communication, IBM SystemsDirector 351

override persistent commandenvironment 7

Pparity

set for serial port of managementmodule 253

particulate contamination 481partition

create for scalable complex 294delete all from scalable complex 294delete from scalable complex 295power cycle in scalable complex 297power off in scalable complex 297power on in scalable complex 296

partition (automatic)create for scalable complex 292

partition informationdisplay for scalable complex 291

partition modeset to partition for scalable

complex 296set to stand alone for scalable

complex 295password

change for user 385LDAP distinguished name 216

password (confirm)LDAP distinguished name 216

password expiration timeset for management module 37

password minimum change intervalset for management module 37

password reuse cycleset for management module 38

path informationdisplay for management channel 204

People's Republic of China Class Aelectronic emission statement 485

persistent command environmentoverride 7

persistent command target 6ping

I/O-module IP address 249IP address 248IP address (I/O-module) 249r 248, 249

ping command errors 447ping commands 248

example 249pmpolicy 251

optionspd 251pdx 251

view for management module 252pmpolicy command

example 252pmpolicy command errors 448polling interval, set for power

trending 152portcfg

optionscom1 253com1, b 253com1, p 253com1, s 254

portcfg command errors 448portcfg commands 253

example 254ports 255

ports (continued)options

-kvme, state 262ftpdp 256ftpe, on 261ftpp 256ftpt 268httpp 257httpse, on 262httpsp 257ntpe, on 262open 255rde, on 263rdoce, on 263reset 256rpp 257slpe , on 263slpp 258smashse, on 264smashte, on 264smashtp 258snmp1ae, on 264snmp3ae, on 265snmpap 259snmpte, on 265snmptp 259sshe, on 265sshp 260stcme, on 266stcme, port mode 267stcmp 260tcme, on 266tcme, port mode 266tcmp 260tcmt 268telnete, on 267telnetp 261telnett 268tftpe, on 267tftpp 261

switch 269, 270ports (open)

display for management module 255ports command 255

example 270ports command errors 448POST status

display for I/O module 276display for switch module 276

poweroptions

ap 275cycle 273cycle, c 273fp 275, 276local 274, 275off 272on 272on, c 272softoff 273state 273state, post 276wol 274

power capping, enable for bladeserver 154

power capping, set for blade server 154power command errors 450


power commands 272example 277

power control commands 29power cycle partition

scalable complex 297power domain

disable acoustic mode 153disable NEBS environment mode 153enable acoustic mode 153enable NEBS environment mode 153

power domain information display(detailed) 150

power domain information display(overview) 149

power domain redundancy loss policy,set 151

power domain, display powertrending 151, 152

power management commands 29power management policy

displayall 251BladeCenter S policies 251specified power domain

policies 251set

for specified power domain 251power management, enable for blade

server 154, 155power module

command target 134power off

alarm panel module 272blade server 272, 273I/O module 272network clock module 272switch module 272, 273

power off partitionscalable complex 297

power onalarm panel module 272blade server 272, 273I/O module 272, 273network clock module 272switch module 272, 273

power on (to console)blade server 272, 273

power on partitionscalable complex 296

power polling interval, set 152power saver mode, enable for blade

server 155power state

display for blade server 273display for I/O module 273display for switch module 273

power trending, display (bladeserver) 151, 152

power trending, display (blower) 151,152

power trending, display (I/Omodule) 151, 152

power trending, display (powerdomain) 151, 152

power trending, display (system) 151,152

primary management module 7

problem descriptioncall-home 95email 301service information 301

product service, IBM Taiwan 477protected mode

enable for I/O module 197

RRAID controller

set gateway IP address (IPv4) 199set subnet mask (IPv4) 200

RAID IP address (IPv4)set for I/O module 199

RDEenable for management module 263

rdoc 278options

map 278mount 278unmount 278

rdoc command errors 450rdoc commands 278

example 279RDOCE

enable for management module 263read 280

optionsconfig 280config, auto, off 282config, auto, on 281config, l , i 280config, l , i, p 281

read CIN configuration status tableentries 102

read CIN status table entries formanagement module 102

read command 280example 282

read command errors 451redirect command 25, 131redundancy loss policy, power domain

(set) 151reload all information 204reload firmware information 204reload hardware information 204reload MAC address information 204reload MAC addresses information 204reload WNN information 204remote alert

set retry interval 51set retry limit 52

remote media tray switchingenable globally 240

Remote Presence port numberset for management module 257

remotechassis 283options

clear 284health 283ip 283name 284

remotechassis command 283example 284

remotechassis command errors 452remove 344, 345, 346

remove feature licensemanagement module 144

remove SSH public key 393replace SSH public key 395required, firmware 2required, hardware 2reset 286

blade server 72, 286I/O module 286ISMP 286management module (primary) 286management module (standby) 286options

c 287clr 289ddg 289dg 289exd 288f 287force 287full 288sft 288sms 290standby 286std 287

service processor 286switch module 286

reset (clear NVRAM)blade server 289

reset (enter SMS menu)blade server 290

reset (extended diagnostics)I/O module 288switch module 288

reset (failover)management module 287multiplexer expansion module 287

reset (force failover)management module 287

reset (full diagnostics)I/O module 288switch module 288

reset (run diagnostics with bootsequence)

blade server 289reset (run diagnostics)

blade server 289reset (standard diagnostics)

I/O module 287switch module 287

reset (to console)blade server 72, 287

reset (with NMI)blade server 288

reset blase server key sequenceset for SOL 333

reset command 29reset command errors 452reset commands 286

example 290reset configuration

I/O module 103switch module 103

reset configuration (keep logs)management module 103

reset default configuration 103

Index 509

reset network port settingsmanagement module 256

reset network protocol settingsI/O module 241

responding to thermal events 153restore configuration

management module (from file withencryption) 281

management module (from file withno encryption) 280

management module (frommidplane) 280

restore configuration commands 29restore management module

configuration commandexample 282

retry countset for SOL 329

retry intervalset for remote alerts 51set for SOL 328

retry limitset for remote alerts 52

retry numberset for remote alerts 51

revert to old IP address configurationafter reset

I/O module 195RSA host key information

display for management module 335Russia Class A electromagnetic

interference statement 485Russia Electromagnetic Interference (EMI)

Class A statement 485

SSAS system

set gateway IP address (IPv4) 199set subnet mask (IPv4) 200

SAS zoneactivate for I/O module 403

SAS zone informationdisplay for I/O module 404

SAS zone listdisplay for I/O module 403

save configuration commands 29save configuration to chassis

management module 401save configuration to file (encryption)

management module 402save configuration to file (no encryption)

management module 401save event log to TFTP server

management module 122save management module configuration

commandexample 402

save service informationsave to TFTP server 124

scalable complexcreate partition 294create partition (automatically) 292create stand-alone partition 293create stand-alone partition

(automatically) 292delete all partitions 294

scalable complex (continued)delete partition 295display all information 291display node information 291display partition information 291display specific complex

information 291power cycle partition 297power off partition 297power on partition 296set partition mode to partition 296set partition mode to stand alone 295

scale 291options

auto 292compid 291compid, partition 291create 293, 294cycle 297delete 294, 295mode 295, 296node 291off 297on 296

scale command errors 453scale commands 291

example 298sddump

optionscoll 299init 299

sddump command errors 454sddump commands 299

example 300sdemail

optionssubj 301to 301

sdemail command errors 454sdemail commands 301

example 301search domain

set for Domain Catalogdiscovery 211

secure command-line interface 14Secure Shell connection clients 14secure shell server

disabling 19Secure Shell server

exit codes (CLI) 20using 18

secure SMASHenabling 19

secure SMASH over SSHenable for management module 264

secure TCP command modedisable 352enable 352enable for management module 266,

360set number of sessions 352turn secure TCP command mode on

or off for the managementmodule 267, 361

secure TCP command mode port numberset for management module 260

security 14, 303

security (continued)display management module account

settings 30display management module

setting 303enable complex password for


enable default administrationpassword expiration formanagement module 34

enable for management module 303enable password change at first login

to management module 36enable password required for

management module 37options

e 303set management module account

default to high 32set management module account

default to legacy 31set management module account

inactivity alert time 34set management module account

inactivity disable time 35set management module account

lockout period 36set management module

authentication logging timeout 32set management module CLI

inactivity timeout 33set management module maximum

LDAP sessions for user 36set management module maximum

number of login failures 35set management module minimum

number of different characters forpassword 34



set management module passwordreuse cycle 38



security command errors 455security commands 303

account security 30example 303

selecting command environment 6selecting command target 6self-signed certificate

generate for LDAP client 339generate for management module web

server 339self-signed certificate (SSL)


send thresholdset for SOL 329

Serial Over LAN 22Serial Over LAN commands 328


Serial Over LAN commands (continued)example 333

serial port baud rateset for management module 253

serial port communication rateset for management module 253

serial port configurationdisplay for management module 253

serial port parityset for management module 253

serial port settings for managementmodule commands

example 254serial port stop bits

set for management module 254server host name

set for management module 309server IP address

set for management module 309service 304

optionsdisable 304enable 304

Service Advisorcontact information 89disable 88display owner 87enable 88HTTP proxy setup 91

service and supportbefore you call 475hardware 476software 476

service commandexample 304

service command errors 455service commands 304service data

collect for blade server 299display command 124display for blade server 299dump from blade server 299get for blade server 299

service informationcapture 124display 124email 301exclude from email alerts 51include with email alerts 51problem description 301save to TFTP server 124

service processorcommand target 133reset 286

service settingdisplay for management module 304

session command 29set

date, management module 106daylight-savings time mode,

management module 109GMT offset, management

module 107power management policy

specified power domain 251TCP command-mode session

timeout 351

set (continued)time, management module 106

set accumulate timeoutSOL 330

set Active Directory group authoritylevel 160

set Active Directory group name 159set address prefix length

blade server 190I/O module 198

set alarm 49set alert notification method 57set alert recipient email address 57set alert recipient name 55set alert recipient status 56set alert type 56set automatic power-on policy

BladeCenter unit 275set boot mode

blade server 74set CIN state for disable

management module 97set CIN state for enable

management module 97set CLI key sequence

SOL 332set command-line timeout

management module 354set contact name

management module 112, 113, 114set DNS first IPv4 IP address

management module 127set DNS first IPv6 IP address

management module 128set DNS second IPv4 IP address

management module 127set DNS second IPv6 IP address

management module 128set DNS server priority

management module 129set DNS third IPv4 IP address

management module 127set DNS third IPv6 IP address

management module 128set Ethernet channel 0 address prefix

lengthmanagement module 180

set Ethernet channel 0 configurationmethod

management module 176set Ethernet channel 0 data rate

management module 177set Ethernet channel 0 domain name

management module 179set Ethernet channel 0 duplex mode

management module 177set Ethernet channel 0 gateway IP

address (IPv4)management module 174

set Ethernet channel 0 gateway/defaultroute (IPv6)

management module 174set Ethernet channel 0 hostname

management module 175standby management module 176

set Ethernet channel 0 MAC addressmanagement module 178

set Ethernet channel 0 MAC address(continued)

standby management module 178set Ethernet channel 0 MTU

management module 177set Ethernet channel 0 static IP address

(IPv4)management module 173standby management module 173

set Ethernet channel 0 static IP address(IPv6)

management module 173standby management module 174

set Ethernet channel 0 subnet mask (IPv4)management module 175

set Ethernet channel 1 data ratemanagement module 182

set Ethernet channel 1 duplex modemanagement module 182

set Ethernet channel 1 gateway IPaddress (IPv4)

management module 181set Ethernet channel 1 MAC address

management module 183set Ethernet channel 1 MTU

management module 183set Ethernet channel 1 static IP address

(IPv4)management module 181

set Ethernet channel 1 subnet mask (IPv4)management module 182

set Ethernet channel configurationmethod

blade server 188set Ethernet channel gateway IP address

(IPv4)blade server 186

set Ethernet channel gateway/defaultroute (IPv6)

blade server 187set Ethernet channel hostname

blade server 189set Ethernet channel static IP address

(IPv4)blade server 185

set Ethernet channel static IP address(IPv6)

blade server 186set Ethernet channel subnet mask (IPv4)

blade server 187set Ethernet channel VLAN ID

blade server 188set Ethernet-over-USB setting

blade server 137set first LDAP server host name

management module 212set first LDAP server IP address

management module 212set first LDAP server port number

management module 213set fourth LDAP server host name

management module 213set fourth LDAP server IP address

management module 213set fourth LDAP server port number


Index 511

set FTP data port numbermanagement module 256

set FTP port numbermanagement module 256

set FTP timeoutmanagement module 268

set gateway IP address (IPv4)I/O module 194RAID controller 199SAS system 199

set gateway IP address (IPv6)I/O module 195

set hostname for alerts 58set HTTP port number

management module 257set HTTPS port number

management module 257set I/O module for blade server

management trafficblade server 184

set IP address (IPv4)blade server 185blade server ISMP 191I/O module 194management module 173standby management module 173

set IP address (IPv6)blade server 186I/O module 194management module 173standby management module 174

set IP address for alerts 58set KVM owner 208set LDAP client distinguished name

management module 216set LDAP client distinguished name

passwordmanagement module 216

set LDAP client distinguished namepassword (confirm)

management module 216set LDAP group filter

management module 217set LDAP group search attribute

management module 217set LDAP login permission attribute

management module 218set LDAP name

management module 210set LDAP security version

management module 210set LDAP server binding method

management module 215set LDAP server discovery method

management module 211set LDAP server domain name

management module 211set LDAP server for authentication only

management module 215set LDAP server forest name

management module 211set LDAP server root distinguished name

management module 214set LDAP UID search attribute

management module 215set location


set logical link loss alert and failoverpolicy

advanced management module 375management module (advanced) 375

set logical uplink failover delayadvanced management module 374management module (advanced) 374

set logical uplink failover IP addressadvanced management module 374management module (advanced) 374

set logical uplink failover IPv6 IP addressadvanced management module 375management module (advanced) 375

set management module accountinactivity alert time 34

set management module accountinactivity disable time 35

set management module account lockoutperiod 36

set management module account securitydefault

high 32legacy 31

set management module authenticationlogging timeout 32

set management module CLI inactivitytimeout 33

set management module maximumLDAP sessions for user 36

set management module maximumnumber of login failures 35

set management module minimumnumber of different characters forpassword 34



set management module password reusecycle 38



set maximum number of simultaneoussessions for user 388

set media tray owner 239set name

blade server 111management module 111

set NAT external port numberI/O module 243

set NAT internal port numberI/O module 243

set NAT protocol IDI/O module 242

set NAT protocol nameI/O module 242

set NTP server hostnamemanagement module 245

set NTP server IP addressmanagement module 245

set NTP server keymanagement module 246

set NTP update frequencymanagement module 246

set number of sessionssecure TCP command mode 352TCP command mode 352

set partition mode to partitionscalable complex 296

set partition mode to stand alonescalable complex 295

set physical uplink failover delayadvanced management module 373management module (advanced) 373

set port speedswitch 270

set power capping for blade server 154set power domain redundancy loss

policy 151set power polling interval 152set privacy password (SNMPv3) 390set Remote Presence port number

management module 257set reset blase server key sequence

SOL 333set retry count

SOL 329set retry interval 51

SOL 328set retry limit

remote alerts 52set retry number 51

remote alerts 51set SAS controller IP address (IPv4)

I/O module 199set second LDAP server host name

management module 212set second LDAP server IP address

management module 212set second LDAP server port number

management module 213set secure TCP command mode port

numbermanagement module 260

set send thresholdSOL 329

set serial port baud ratemanagement module 253

set serial port communication ratemanagement module 253

set serial port paritymanagement module 253

set serial port stop bitsmanagement module 254

set server host namemanagement module 309

set server IP addressmanagement module 309

set SLP address typemanagement module 307

set SLP multicast addressmanagement module 307

set SLP port numbermanagement module 258

set SMASH Telnet port numbermanagement module 258

set SMTP e-mail server domain namemanagement module 310

set SNMP agent port numbermanagement module 259


set SNMP community 1 first host namemanagement module 314

set SNMP community 1 first host name-get

management module 316set SNMP community 1 first host name

to setmanagement module 315

set SNMP community 1 IP address (firsthost)

management module 314set SNMP community 1 IP address (first

host) to getmanagement module 316

set SNMP community 1 IP address (firsthost) to set

management module 315set SNMP community 1 IP address

(second host)management module 317

set SNMP community 1 IP address (thirdhost)

management module 318set SNMP community 1 name

management module 313set SNMP community 1 second host

namemanagement module 317

set SNMP community 1 third host namemanagement module 318

set SNMP community 1 view type(SNMPv3)

management module 318set SNMP community 2 first host name

management module 319set SNMP community 2 IP address (first

host)management module 319

set SNMP community 2 IP address(second host)

management module 320set SNMP community 2 IP address (third

host)management module 321

set SNMP community 2 namemanagement module 319

set SNMP community 2 second hostname

management module 320set SNMP community 2 third host name

management module 321set SNMP community 2 view type

(SNMPv3)management module 321

set SNMP community 3 first host namemanagement module 322

set SNMP community 3 IP address (firsthost)

management module 322set SNMP community 3 IP address

(second host)management module 323

set SNMP community 3 IP address (thirdhost)

management module 324set SNMP community 3 name


set SNMP community 3 second hostname

management module 323set SNMP community 3 third host name

management module 324set SNMP community 3 view type

(SNMPv3)management module 324

set SNMP contact namemanagement module 325

set SNMP locationmanagement module 326

set SNMP traps port numbermanagement module 259

set SSH port numbermanagement module 260

set state for KVM portmanagement module 262

set static IP address (IPv4)blade server ISMP 191

set subnet mask (IPv4)I/O module 196RAID controller 200SAS system 200

set syslog event log collector 1 host namemanagement module 348

set syslog event log collector 1 IP addressmanagement module 348

set syslog event log collector 1 portnumber

management module 349set syslog event log collector 2 host name

management module 348set syslog event log collector 2 IP address

management module 348set syslog event log collector 2 port

numbermanagement module 349

set syslog filter levelmanagement module 347

set TCP command mode port numbermanagement module 260

set TCP command-mode timeoutmanagement module 268

set Telnet port numbermanagement module 261

set Telnet port timeoutmanagement module 268

set telnet timeoutmanagement module 354

set TFTP port numbermanagement module 261

set third LDAP server host namemanagement module 212

set third LDAP server IP addressmanagement module 212

set third LDAP server port numbermanagement module 214

set trespass feature messagemanagement module 356

set trespass feature to defaultmanagement module 357

set user access type (SNMPv3) 390set user authentication protocol

(SNMPv3) 389set user authority level 386set user context name (SNMPv3) 388

set user hostname (SNMPv3 traps) 391set user IP address (SNMPv3 traps) 391set user name 383set user password 384set user privacy protocol (SNMPv3) 389set VLAN ID

BladeCenter unit 192shutdown

blade server 273, 306options

f 306shutdown command errors 455shutdown commands 306

example 306simultaneous sessions

set maximum number for user 388slp 307

optionsi 307t 307

SLPenable for management module 263

SLP address typeset for management module 307

slp command 307example 307

slp command errors 455SLP multicast address

set for management module 307SLP port number

set for management module 258SLP settings

display for management module 307SMASH (secure) over SSH

enable for management module 264SMASH CLP

enabling 19SMASH over Telnet

enable for management module 264SMASH SSH server


SMASH Telnet port numberset for management module 258

smtp 309options

d 310s 309

smtp command errors 455smtp commands 309

example 310SMTP e-mail server domain name

set for management module 310SMTP server host name

display for management module 309SMTP server IP address

display for management module 309SMTP settings for management module

commandsexample 310

snmp 312options

-ca1 get -c1i1 0.0.0.0 316-ca1 set -c1i1 0.0.0.0 315a, on 312a3, on 312c1 313

Index 513

snmp (continued)options (continued)

c1i1 314c1i2 317c1i3 318c2 319c2i1 319c2i2 320c2i3 321c3 322c3i1 322c3i2 323c3i3 324ca1 318ca2 321ca3 324cn 325l 326t, on 312

SNMP agentenable for management module

(SNMPv1)SNMPv1 312

enable for management module(SNMPv3)

SNMPv3 312SNMP agent port number

set for management module 259snmp command errors 456snmp commands 312

example 326SNMP community 1 first host name

set for management module 314set to get for management

module 316SNMP community 1 first host name to

setset for management module 315

SNMP community 1 IP address (firsthost)

set for management module 314SNMP community 1 IP address (first

host) to getset to get for management

module 316SNMP community 1 IP address (first

host) to setset for management module 315

SNMP community 1 IP address (secondhost)

set for management module 317SNMP community 1 IP address (third

host)set for management module 318

SNMP community 1 nameset for management module 313

SNMP community 1 second host nameset for management module 317

SNMP community 1 third host nameset for management module 318

SNMP community 1 view typeset for management module

(SNMPv3) 318SNMP community 2 first host name



set for management module 319SNMP community 2 IP address (second


SNMP community 2 IP address (thirdhost)

set for management module 321SNMP community 2 name

set for management module 319SNMP community 2 second host name

set for management module 320SNMP community 2 third host name

set for management module 321SNMP community 2 view type

set for management module(SNMPv3) 321

SNMP community 3 first host nameset for management module 322


set for management module 322SNMP community 3 IP address (second


SNMP community 3 IP address (thirdhost)

set for management module 324SNMP community 3 name

set for management module 322SNMP community 3 second host name

set for management module 323SNMP community 3 third host name

set for management module 324SNMP community 3 view type

set for management module(SNMPv3) 324

SNMP configurationdisplay for management module 312

SNMP contact nameset for management module 325

SNMP locationset for management module 326

SNMP settings for management modulecommands

example 326SNMP traps

disable for management module 312enable for management module 265,

312SNMP traps port number

set for management module 259SNMPv1

enable for management module 359SNMPv1 agent

enable for management module 264SNMPv3

community 1 view type 318community 2 view type 321community 3 view type 324enable for management module 359privacy password 390trap receiver IP address or

hostname 391user access type 390user authentication protocol 389

SNMPv3 (continued)user context name 388user privacy protocol 389

SNMPv3 agentenable for management module 265

software service and support telephonenumbers 476

sol 328options

c 329e 332i 328r 333s 329status 330, 331t 330

SOL 22, 23, 115global disable 331global enable 330set accumulate timeout 330set CLI key sequence 332set reset blase server key

sequence 333set retry count 329set retry interval 328set send threshold 329status 328

sol command errors 457sol commands

example 333SOL commands 328SOL session

ending 23, 115starting 22

Specify IP addressCIN configuration entry 99

Specify VLAN IDCIN configuration 100

SRC recorddisplay specific for blade server 124

SRC recordsdisplay all for blade server 124

SSHdisabling 19

SSH clients 14SSH connection 18SSH port

enable for management module 265SSH port number

set for management module 260SSH public key add 392SSH public key add (specific) 392SSH public key comment 398SSH public key connection 397SSH public key display 391SSH public key download 396SSH public key remove 393SSH public key replace 395SSH public key upload 394SSH status

display for management module 335sshcfg 335

optionscstatus 336hk, dsa 335hk, gen 335hk, rsa 335


sshcfg (continued)options (continued)

sstatus 336sshcfg command 335

example 336sshcfg command errors 458SSL

disable for LDAP client 338enable for LDAP client 338

SSL certificate (additional)disable for standby management


module 337SSL certificate status

management module 337SSL CSR


SSL for LDAP clientdisable 338enable 338

SSL for management module web serverdisable 337enable 337

SSL for web serverdisable for management module 337enable for management module 337

SSL self-signed certificatedownload certificate file 342import certificate file 343upload certificate file 343

SSL statusmanagement module 337

SSL trusted certificate 1 344download 344import 344remove 344upload 344



sslcfg 337options

ac 337c 339, 341cert 339cl 339, 341client 338cp 339, 341cpwd 341csr 341dnld 342dq 339, 341ea 339, 341gn 339, 341hn 339, 341i 342, 343, 344, 345, 346in 339, 341

sslcfg (continued)options (continued)

l 342, 343, 344, 345, 346on 339, 341ou 339, 341s 339, 341server 337sp 339, 341tc1 344tc2 345tc3 346un 341upld 343

sslcfg command errors 459sslcfg commands 337

example 346stand-alone partition

create for scalable complex 293stand-alone partition (automatic)

create for scalable complex 292standby management module

disable additional SSL certificate 337enable additional SSL certificate 337set Ethernet channel 0 hostname 176set Ethernet channel 0 MAC

address 178set Ethernet channel 0 static IP


address (IPv6) 174set IP address (IPv4) 173set IP address (IPv6) 174

standby management modules 7starting a session using SSH 18starting a session using Telnet 16starting an SOL session 22starting command-line interface 14static IP address (IPv4)

set for blade server ISMP 191set for channel 0 of management


management module 173set for channel 1 of management

module 181set for channel of blade server 185

static IP address (IPv6)set for channel 0 of management


management module 174set for channel of blade server 186

static IPv6 configurationdisable for I/O module 197disable for management module 179enable for I/O module 197enable for management module 179

statusdisplay for management module 124SOL 328

stop bitsset for serial port of management

module 254storage expansion unit

command target 133storage module

command target 135

subnet mask (IPv4)set for channel 0 of management

module 175set for channel 1 of management

module 182set for channel of blade server 187set for I/O module 196set for RAID controller 200set for SAS system 200

switchdisplay network port settings 269enable port 269set port speed 270

switch modulecommand target 134cycle power 273display POST status 276display power state 273power off 272, 273power on 272, 273reset 286reset (extended diagnostics) 288reset (full diagnostics) 288reset (standard diagnostics) 287reset configuration 103turn off 272, 273turn on 272, 273

synchronize clock with NTP servermanagement module 247

syntax help 166syntax help commands

example 166syslog 347

optionscoll1 347coll2 348i1 348i2 348p1 349p2 349sev 347test 350

syslog command errors 461syslog commands 347

example 350syslog configuration

display for management module 347syslog event log collector 1 host name

set for management module 348syslog event log collector 1 IP address

set for management module 348syslog event log collector 1 port number

set for management module 349syslog event log collector 2 host name

set for management module 348syslog event log collector 2 IP address

set for management module 348syslog event log collector 2 port number

set for management module 349syslog event log transmission for collector

1disable 347disable for management module 347enable 347enable for management module 347

Index 515

syslog event log transmission for collector2

disable 348disable for management module 348enable 348enable for management module 348

syslog filter levelset for management module 347

syslog test messagegenerate for management

module 350system

view configuration tree 225system management command 29system physical configuration

command 225system power management policy

command 251system, display power trending 151, 152

TTaiwan Class A compliance

statement 485target 25, 131TCP command mode

disable 351enable 352enable for management module 266,

360set number of sessions 352turn TCP command mode on or off

for the management module 266,360

TCP command mode port numberset for management module 260

TCP command-mode session statusdisplay 351

TCP command-mode session timeoutdisplay 351set 351

TCP command-mode timeoutset for management module 268

tcpcmdmode 351options

status, 0 351, 352status, 1 to 20 352t 351

tcpcmdmode command errors 462tcpcmdmode commands 351

example 353technician debug


Telco environment 153telnet configuration

display for management module 354telnet configuration commands 354Telnet connection 14, 16Telnet port

enable for management module 267Telnet port number

set for management module 261Telnet port timeout

set for management module 268telnet timeout


telnetcfg 354options

t 354telnetcfg command errors 462telnetcfg commands 354

example 354temperature

display for blade server 355display for management module 355display for media tray 355

temperature display, blower 149temperature display, media tray 149temporary command target 7temps 355temps command errors 463temps commands 355

example 355terminate 377terminate session 143terminate user session

management module 377test alert

generate 58test call home

call-home 96test communication

I/O-module IP address 249IP address 248IP address (I/O-module) 249

TFTPenable for management module 267

TFTP port numberset for management module 261

thermal event response 153thermal trending, display (blower) 152thermal trending, display (media

tray) 152thres command errors 463time

display for management module 106set for management module 106

trademarks 480trespass 356

optionstw 356twd 357twe 356

trespass command 356example 357

trespass command errors 463trespass feature

enable for management module 356trespass feature default

set for management module 357trespass feature message

set for management module 356trespass feature status

display for management module 356trusted certificate 1 (SSL)

download 344import 344remove 344upload 344

trusted certificate 2 (SSL)download 345import 345remove 345

trusted certificate 2 (SSL) (continued)upload 345

trusted certificate 3 (SSL)download 346import 346remove 346upload 346

turn all CIN index entries on or off 98turn off

alarm panel module 272blade server 272, 273I/O module 272network clock module 272switch module 272, 273

turn off LEDinformation 221

turn off location LED 169, 222turn on

alarm panel module 272blade server 272, 273I/O module 272, 273network clock module 272switch module 272, 273

turn on (to console)blade server 272, 273

turn secure TCP command mode on oroff

management module 267, 361turn TCP command mode on or off

management module 266, 360

Uuicfg 359

optionscli, enabled 359snmp, enabled 359stcm, enabled 360stcm, port mode 361tcm, enabled 360tcm, port mode 360web, enabled 361

uicfg command errors 464uicfg commands 359

example 361unacknowledge call-home activity log

entrymanagement module 94

United States electronic emission Class Anotice 482

United States FCC Class A notice 482unlock user 380unmount volume

advanced management module 278update

optionsa 363activate 366i, l 368i, l, img 369, 370i, l, img, activate 370, 371i, n 368u 364u, img 365, 366u, img, activate 367u, r 364u, v 365


update command 363update command errors 465update commands

example 371update firmware 363, 364, 368

I/O module 365, 366, 367, 369, 370,371

switch 365, 366, 367, 369, 370, 371verbose 366, 370

update firmware (verbose) 365, 368update firmware build ID in firmware

build ID listblade server 83

update firmware build revision infirmware build ID list

blade server 84update firmware type in firmware build

ID listblade server 83

update machine type in firmware buildID list

blade server 82update manufacturer in firmware build

ID listblade server 82

uplink 373options

alert 375dls 374dps 373el, enabled 374ep, enabled 373ip 374ip6 375

uplink command errors 467uplink commands 373

example 375uplink configuration

display for management module 373uplink failover (logical)

disable for advanced managementmodule 374

disable for management module(advanced) 374

enable for advanced managementmodule 374

enable for management module(advanced) 374

uplink failover (physical)enable for advanced management

module 373enable for management module

(advanced) 373uplink failover delay (logical)

set for advanced managementmodule 374

set for management module(advanced) 374

uplink failover delay (physical)set for advanced management


(advanced) 373uplink failover IP address (logical)

set for advanced managementmodule 374

uplink failover IP address (logical)(continued)

set for management module(advanced) 374

uplink failover IPv6 IP address (logical)set for advanced management


(advanced) 375upload 344, 345, 346upload certificate file


upload SSH public key 394user authentication method

enable complex password 33set for management module 33

user interface configuration 359example 361

user interface settingsdisplay for management module 359

user session 377users 377

options1 through 12 378a 386ap 389at 390clear 378cn 388create (n, p, a, cn, ap, pp, ppw, at,

i) 381curr 377disable 379enable 379i 391ms 388n 383op 385p 384pk, add 392pk, af 397pk, cm 398pk, dnld 396pk, e 391pk, remove 393pk, upld 394, 395pp 389ppw 390ts 377unlock 380

users command 377users command errors 468users commands

example 398users, change password 385users, create 381users, delete 378users, disable 379users, display (active) 377users, display (all) 377users, display (single) 378users, enable 379users, management module 377users, set access type (SNMPv3) 390users, set authentication protocol

(SNMPv3) 389

users, set authority level 386users, set context name (SNMPv3) 388users, set hostname (SNMPv3 traps) 391users, set IP address (SNMPv3

traps) 391users, set maximum number of

simultaneous sessions 388users, set name 383users, set password 384users, set privacy password

(SNMPv3) 390users, set privacy protocol

(SNMPv3) 389users, unlock 380using

Secure Shell server 18using the command-line interface 5

VV3 authentication for NTP

enable for management module 246view command target 225VLAN ID

CIN configuration 100disable for blade server Ethernet

channel 189disable for BladeCenter unit 192enable for blade server Ethernet

channel 189enable for BladeCenter unit 192set for BladeCenter unit 192set for channel of blade server 188

voltagedisplay for blade server 400display for management module 400

volts 400volts command errors 472volts commands 400

example 400volume information

display for management module 278

WWake on LAN

enable for blade server 274enable globally 274

warning alertsdisable monitoring for all 232disable monitoring for blade


device 234disable monitoring for event log 233disable monitoring for I/O


module 234disable monitoring for storage


management 233enable monitoring for all 232

Index 517

warning alerts (continued)enable monitoring for blade


device 234enable monitoring for event log 233enable monitoring for I/O


module 234enable monitoring for storage


management 233web interface

enable for management module 361web interface inactivity timeout

set for management module 38WNN information reload 204write

optionsconfig 401config, l ,i 401, 402

write command 401example 402

write command errors 472

Zzonecfg 403

optionsactivate 403view 404

zonecfg command errors 473zonecfg commands 403

example 404


��

Part Number: 16Y6037

Printed in USA

(1P) P/N: 16Y6037

Documents

IBM BLADE console