44 R 5231

IBM BladeCenter Management Module BladeCenter T Management Module Advanced Management Module BladeCenter T Advanced Management Module
Command-Line Interface Reference Guide
IBM BladeCenter Management Module BladeCenter T Management Module Advanced Management Module BladeCenter T Advanced Management Module
Command-Line Interface Reference Guide
Note: Before using this information and the product it supports, read the general information in Notices.
Eleventh Edition (December 2007) Copyright International Business Machines Corporation 2007. All rights reserved. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents
Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . 1 Before you begin . . . . . . . . . . . . . . . . . . . . . . . . 2 Chapter 2. Using the command-line interface . . . . . Command-line interface guidelines . . . . . . . . . . Selecting the command target . . . . . . . . . . . . Commands and user authority . . . . . . . . . . . . Cabling the management module . . . . . . . . . . Networked connection . . . . . . . . . . . . . Direct connection . . . . . . . . . . . . . . . Serial connection (advanced management module only) . Starting the command-line interface . . . . . . . . . Telnet connection . . . . . . . . . . . . . . . Serial connection . . . . . . . . . . . . . . . Secure Shell (SSH) connection . . . . . . . . . . Using SMASH . . . . . . . . . . . . . . . SSH CLI exit codes . . . . . . . . . . . . . BladeCenter unit configuration . . . . . . . . . . . Configuring the management module . . . . . . . . . Starting an SOL session . . . . . . . . . . . . . Ending an SOL session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 . 3 . 4 . 6 . 13 . 14 . 14 . 15 . 15 . 16 . 16 . 17 . 18 . 19 . 19 . 20 . 21 . 22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 23 26 28 29 36 38 44 46 52 54 58 59 60 64 68 69 71 72 73 77 79 80 81 85 87 89 94 95
Chapter 3. Command reference . . . . . . . . . . . . . Alphabetical command list . . . . . . . . . . . . . . . . Command list by function . . . . . . . . . . . . . . . . Command syntax . . . . . . . . . . . . . . . . . . . accseccfg command (advanced management module only) . . advfailover command (advanced management module only) . . alarm command (BladeCenter T only) . . . . . . . . . . alertcfg command (advanced management module only) . . . alertentries command . . . . . . . . . . . . . . . . baydata command (advanced management module only) . . . bofm command (advanced management module only) . . . . boot command . . . . . . . . . . . . . . . . . . . bootmode command (advanced management module only) . . bootseq command (advanced management module only) . . . cin command (advanced management module only) . . . . . cinstatus command (advanced management module only) . . . clear command (management modules other than the advanced management module) . . . . . . . . . . . . . . . clear command (advanced management module only) . . . . clearlog command . . . . . . . . . . . . . . . . . . clock command (advanced management module only) . . . . config command (advanced management module only) . . . . console command . . . . . . . . . . . . . . . . . . dhcpinfo command . . . . . . . . . . . . . . . . . displaylog command . . . . . . . . . . . . . . . . . displaysd command (advanced management module only) . . . dns command . . . . . . . . . . . . . . . . . . . env (environment) command . . . . . . . . . . . . . . exit command . . . . . . . . . . . . . . . . . . . files command (advanced management module only) . . . . .
Copyright IBM Corp. 2007
iii
fuelg command (management modules other than the advanced management module) . . . . . . . . . . . . . . . . . . . . 96 fuelg command (advanced management module only) . . . . . . . . . 99 health command . . . . . . . . . . . . . . . . . . . . . . . 106 help command . . . . . . . . . . . . . . . . . . . . . . . 109 history command . . . . . . . . . . . . . . . . . . . . . . . 111 identify (location LED) command . . . . . . . . . . . . . . . . . 112 ifconfig command (management modules other than the advanced management module) . . . . . . . . . . . . . . . . . . . . 113 ifconfig command (advanced management module only) . . . . . . . . 118 info (configuration information) command . . . . . . . . . . . . . . 128 iocomp command (advanced management module only) . . . . . . . . 132 kvm (keyboard, video, mouse) command (advanced management module only) . . . . . . . . . . . . . . . . . . . . . . . . . . 134 ldapcfg command (advanced management module only) . . . . . . . . 136 led command (advanced management module) . . . . . . . . . . . 142 list (system physical configuration) command . . . . . . . . . . . . 146 modactlog command (advanced management module only) . . . . . . . 148 monalerts command (advanced management module only) . . . . . . . 149 monalertsleg command (advanced management module only) . . . . . . 154 mt (media tray) command (advanced management module only) . . . . . 159 nat command (advanced management module only) . . . . . . . . . 161 ntp (network time protocol) command (advanced management module only) 164 ping command (advanced management module only) . . . . . . . . . 166 pmpolicy command (advanced management module only) . . . . . . . 167 portcfg command (advanced management module only) . . . . . . . . 170 ports command (advanced management module only) . . . . . . . . . 172 power command . . . . . . . . . . . . . . . . . . . . . . . 181 read command (advanced management module only) . . . . . . . . . 185 remotechassis command (advanced management module only) . . . . . 187 reset command . . . . . . . . . . . . . . . . . . . . . . . 190 sddump command (advanced management module only) . . . . . . . . 194 security command (advanced management module only) . . . . . . . . 195 service command (advanced management module only) . . . . . . . . 196 shutdown command (advanced management module only) . . . . . . . 197 slp command (advanced management module only). . . . . . . . . . 198 smtp command . . . . . . . . . . . . . . . . . . . . . . . 199 snmp command . . . . . . . . . . . . . . . . . . . . . . . 200 sol (serial over LAN) command . . . . . . . . . . . . . . . . . 205 sshcfg command (advanced management module only) . . . . . . . . 210 sslcfg command (advanced management module only) . . . . . . . . 212 syslog command (advanced management module only) . . . . . . . . 218 tcpcmdmode command (management modules other than the advanced management module) . . . . . . . . . . . . . . . . . . . . 220 tcpcmdmode command (advanced management module only) . . . . . . 222 telnetcfg (Telnet configuration) command . . . . . . . . . . . . . . 224 temps command (advanced management module only) . . . . . . . . 225 trespass command (advanced management module only) . . . . . . . 226 uicfg command (advanced management module only) . . . . . . . . . 228 update (update firmware) command . . . . . . . . . . . . . . . . 230 uplink (management module failover) command (management modules other than the advanced management module) . . . . . . . . . . . 233 uplink (management module failover) command (advanced management module only) . . . . . . . . . . . . . . . . . . . . . . . 235 users command (management modules other than the advanced management module) . . . . . . . . . . . . . . . . . . . . 238
iv
IBM BladeCenter: Management Module Command-Line Interface Reference Guide
users command (advanced management module only) . . volts command (advanced management module only) . . write command (advanced management module only) . . zonecfg command (advanced management module only) . Chapter 4. Error messages . Common errors . . . . . . accseccfg command errors . . advfailover command errors. . alarm command errors . . . alertcfg command errors . . . alertentries command errors . baydata command errors . . . bofm command errors . . . . boot command errors . . . . bootmode command errors . . bootseq command errors . . . cin command errors . . . . clear command errors . . . . clearlog command errors . . . clock command errors . . . . config command errors . . . console command errors . . . dhcpinfo command errors . . displaylog command errors . . displaysd command errors . . dns command errors . . . . env command errors . . . . exit command errors . . . . files command errors . . . . fuelg command errors . . . . health command errors . . . help command errors . . . . history command errors . . . identify command errors . . . ifconfig command errors . . . info command errors . . . . iocomp command errors . . . kvm command errors . . . . ldapcfg command errors . . . led command errors . . . . list command errors. . . . . modactlog command errors . . monalerts command errors . . monalertsleg command errors . mt command errors . . . . . nat command errors . . . . ntp command errors . . . . ping command errors . . . . pmpolicy command errors . . portcfg command errors . . . ports command errors . . . . power command errors . . . read command errors . . . . remotechassis command errors reset command errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
247 262 263 265 267 269 271 272 273 273 274 275 275 276 276 277 277 278 279 279 280 280 281 281 282 283 283 283 283 284 287 288 288 288 289 292 293 293 293 294 295 295 295 295 296 296 296 297 297 297 297 298 299 300 300
Contents
sddump command errors . . security command errors . . service command errors . . shutdown command errors . slp command errors . . . smtp command errors . . . snmp command errors . . sol command errors . . . sshcfg command errors . . sslcfg command errors . . syslog command errors . . tcpcmdmode command errors telnetcfg command errors . temps command errors . . thres command errors . . . trespass command errors . uicfg command errors . . . update command errors . . uplink command errors . . users command errors . . volts command errors . . . write command errors . . . zonecfg command errors . .
. . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
301 301 301 302 302 302 303 304 305 306 308 308 309 309 310 310 310 311 313 313 318 318 319 321 321 321 321 322 322 322
Appendix A. Getting help and technical assistance . Before you call . . . . . . . . . . . . . . . Using the documentation . . . . . . . . . . . . Getting help and information from the World Wide Web Software service and support . . . . . . . . . . Hardware service and support . . . . . . . . . . IBM Taiwan product service . . . . . . . . . . .
Appendix B. Notices . . . . . . . . . . . . . . . . . . . . . . 323 Trademarks. . . . . . . . . . . . . . . . . . . . . . . . . . 323 Important notes . . . . . . . . . . . . . . . . . . . . . . . . 324 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
vi
Chapter 1. Introduction
This topic provides a short introduction to the BladeCenter command-line interface. The IBM BladeCenter management-module command-line interface (CLI) provides direct access to BladeCenter management functions as an alternative to using the Web-based user interface. Using the command-line interface, you can issue commands to control the power and configuration of the management module and other components that are in a BladeCenter unit. All IBM BladeCenter units are referred to throughout this document as the BladeCenter unit. All management modules are referred to throughout this document as the management module. Unless otherwise noted, all commands can be run on all management module and BladeCenter unit types. v When a command is labeled as BladeCenter H only, it can run on all types of BladeCenter H units (BladeCenter H and BladeCenter HT). v When a command is labeled as BladeCenter T only, it can run on all types of BladeCenter T units (BladeCenter T and BladeCenter HT). v When a command is labeled as Blade Center Sonly, it can run on all types of BladeCenter S units (BladeCenter S). The command-line interface also provides access to the text-console command prompt on each blade server through a serial over LAN (SOL) connection. See the IBM BladeCenter Serial Over LAN Setup Guide for information about SOL and setup instructions. You access the management-module CLI by establishing a Telnet connection to the IP address of the management module or through a Secure Shell (SSH) connection. You can initiate connections from the client computer using standard remote communication software; no special programs are required. Users are authenticated by the management module before they can issue commands. You enter commands one at a time; however, you can use command scripting to enter multiple commands. The interface does not support keyboard shortcuts, except for the special key sequence (pressing Esc then () that terminates an SOL session. The most recent versions of all BladeCenter documentation are available from http://www.ibm.com/systems/support/.
Before you begin

This topic lists the hardware and software required to use the BladeCenter command-line interface. Hardware and software required for the command-line interface are as follows: Hardware: No special hardware is required to use the management-module command-line interface. To use the SOL feature, an Ethernet I/O module that supports SOL must be installed in I/O-module bay 1. You can use the console command to control a blade server through SOL only on blade server types that support SOL functionality and have an integrated system management processor firmware level of version 1.00 or later. See the IBM BladeCenter Serial Over LAN Setup Guide for information. Firmware: Make sure you are using the latest versions of device drivers, firmware, and BIOS code for your blade server, management module, and other 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 latest instructions are in the documentation that comes with the updates. The management-module CLI is supported by BladeCenter management-module firmware level version 1.08 or later. All versions of BladeCenter T management-module firmware support the command-line interface. The SOL feature has additional firmware requirements. See the IBM BladeCenter Serial Over LAN Setup Guide for information.
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 convenient method for entering commands that manage and monitor BladeCenter components. This chapter contains the following information about using the command-line interface: v Command-line interface guidelines v Selecting the command target on page 4 v Commands and user authority on page 6 v Cabling the management module on page 13 v Starting the command-line interface on page 15 v BladeCenter unit configuration on page 19 v Configuring the management module on page 20 v Starting an SOL session on page 21 v Ending an SOL session on page 22 See Chapter 3, Command reference, on page 23 for detailed information about commands that are used to monitor and control BladeCenter components. Command-line interface error messages are in Chapter 4, Error messages, on page 267. See the IBM BladeCenter Serial Over LAN Setup Guide for SOL setup instructions and the documentation for your operating system for information about commands you can enter through an SOL connection.
Command-line interface guidelines

This topic gives general guidelines for using the BladeCenter command-line interface. All commands have the following basic structure:
command -option parameter
Some commands do not require options and some command options do not require parameters. You can add multiple options to a command on one line to avoid repeating the same command. Options that display a value and options that set a value must not be used together in the same command. Some examples of valid command option syntax are: v command v command -option_set v command -option_set parameter v command -option1_set parameter -option2_set parameter For example, telnetcfg -t 360. The information for each option is returned in the order in which it was entered and is displayed on separate lines.
Observe the following general guidelines when using the command-line interface: v Case sensitivity All commands, command options, and pre-defined command option parameters are case sensitive. Note: If you receive a Command not found error, make sure that you are typing the commands in the correct case; they are case sensitive. For a list of valid commands, type help or ?. v Data types The 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 the option and the parameter. Any additional spaces are ignored. Output format Failed commands generate failure messages. Successful commands are indicated by the message OK, or by the display of command results. Strings Strings containing spaces should be enclosed in quotation marks, such as in snmp -cn "John B. Doe". String parameters can be mixed case. 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 to any command displays its syntax. You can use the up arrow and down arrow keys in the command-line interface to access the last eight commands that were entered.
Selecting the command target

This topic describes command targets and the persistent command environment. You can use the command-line interface to target commands to the management module or to other devices installed in the BladeCenter unit. The command-line prompt indicates the persistent command environment: the environment where commands are entered unless otherwise redirected. When a command-line interface session is started, the persistent command environment is system; this indicates that commands are being directed to the BladeCenter unit.
Command targets are specified hierarchically, as shown in the following illustration.

BladeCenter unit
system
Storage module storage[x] where x = 1 to n (BladeCenter S only) Management module I/O module (switch module) Blade server Power module Media tray Blower Alarm panel module Multiplexer expansion module ncc [x] mux [x] where x = 1 to 2 where x = 1 to 2 (BladeCenter (BladeCenter HT only) HT only) Network clock module
mm[x] switch[x] where x = 1 to 2 where x = 1 to n
tap blade[x] blower[x] power[x] mt [x] where x = 1 to n where x = 1 to n where x = 1 to 2 where x = 1 to n (BladeCenter HT only)
Integrated system management processor (service processor) sp
I/O expansion card
Microprocessor
Storage expansion unit
dtr[x] (not AMM) cpu[x] exp[x] (AMM only) where x =1 to n where x =1 to n
High-speed expansion card
Concurrent KVM feature card
Double-width blade server mezzanine sb (AMM only)
Management card mgmtcrd (AMM only)
be [x] hsec (AMM only) ckvm (AMM only) where x = 1 to n
You can change the persistent command environment for the remainder of a command-line interface session by using the env command (see env (environment) command on page 89). When you list the target as a command attribute using the -T option, you change the target environment for the command that you are entering, temporarily overriding the persistent command environment. Target environments can be specified using the full path name, or using a partial path name based on the persistent command environment. Full path names always begin with system. The levels in a path name 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 system management processor (service processor) of the blade server in blade bay 3, when the persistent command environment is set to the blade server in blade bay 3. Most management-module commands must be directed to the primary management module. If only one management module is installed in the BladeCenter unit, it will always act as the primary management module. Either management module can function as the primary management module; however, only one management module can be primary at one time. You can determine which management module is acting as the primary management module using the list command (see list (system physical configuration) command on page 146).
Commands and user authority

This topic lists command-line interface commands and the user authority levels needed to run them. Some commands in the command-line interface can only be successfully executed by users who are assigned a required level of authority. Users with Supervisor command authority can successfully execute all commands. Commands that display information do not require any special command authority; however, users can be assigned restricted read-only access, as follows: v Users with Operator command authority can successfully execute all commands that display information. v Users with Chassis Operator custom command authority can successfully execute commands that display information about the common BladeCenter unit components. v Users with Blade Operator custom command authority can successfully execute commands that display information about the blade servers. v Users with Switch Operator custom command authority can successfully execute commands that display information about the I/O modules. Table 1 on page 7 shows the command-line interface commands and their required authority levels. To use the table, observe the following guidelines: v The commands listed in this table only apply to the command variants that set values or cause an action: display variants of the commands do not require any special command authority. v When only one command authority at a time is required to execute a command, this is indicated by a v entry in a table row. v When a command has several rows associated with it, each row indicates one of the valid user command authorities needed to successfully execute the command. For example, the clearlog command is available to users with the Supervisor command authority or to users with the Chassis Log Administration command authority. v When a combination of two or more command authorities at a time is required to execute a command, this is indicated by multiple L entries in a table row. The user must be assigned both of these command authorities to successfully execute the command. For example, one available authority combination for the power -on -c command is the Blade Server Remote Presence command authority and the Blade Administration command authority. Important: Command authority definitions might change between firmware versions. Make sure that the command authority level set for each user is correct after updating management-module firmware. Notes: 1. LDAP (lightweight directory access protocol) authority levels are not supported by management modules other than the advanced management module. 2. LDAP authority levels are not supported by the management-module Web interface. 3. To use the LDAP authority levels, you must make sure that the version of LDAP security used by the management module is set to v2 (enhanced role-based security model). See ldapcfg command (advanced management module only) on page 136 for information.
Table 1. Command authority relationships Authority Chassis Account Management
I/O Module Administration
Chassis Log Management
Command accseccfg
v v v advfailover v v v alarm -c, -r, -s v v v alarm -q -g v v alertcfg v v alertentries v v v v v alertentries -test v v v v v baydata v v bofm v v boot (blade server) v v v
I/O Module Configuration
Blade Remote Presence
Chassis Administration
Chassis Configuration
Blade Administration
Blade Configuration
Supervisor
Table 1. Command authority relationships (continued) Authority Chassis Account Management
Command boot -c
v L v boot -p v v bootmode v v bootseq v v cin v v clear L L L v clearlog v v clock v config (blade server) config (management module) console v v displaylog -lse v v dns v v v v v v L L
Blade Configuration
Supervisor
Command
v v v files -d v v v v v fuelg v v identify v v v ifconfig (blade server target) v ifconfig (blade server ISMP, management module, and system targets) ifconfig (I/O module target) v v ifconfig -pip (I/O module target) v v v kvm -b v v kvm -local v v ldapcfg v v v v
Blade Configuration
Supervisor
Command
v v led -d, -loc (system target) v v v led -info, -loc (blade server target) v v v v monalerts v v monalertsleg v v mt -b v v mt -local, -remote v v nat v v ntp v ping (see Note 1) v pmpolicy v v portcfg v v ports v v v v v
10
Blade Configuration
Supervisor
Command power -on, -off, -softoff, -cycle
v v v power -on -c, -cycle -c L v power -wol, -local v power -fp (global) power -fp (I/O module) read v v reset (blade server or ISMP) v reset (I/O module) v reset (management module) v reset -c, -clr, -dg, -ddg, -sft (blade server) v reset -exd, -full, -std (I/O module) v reset -f, -standby (management module) v sddump v v v L L v v v v v v v v L
Blade Configuration
Supervisor
11
Command security
v v v service v v shutdown v v slp v v smtp v v snmp v v sol v v v sshcfg v v sslcfg v v syslog v v tcpcmdmode v v telnetcfg v v trespass v v uicfg v
12
Blade Configuration
Supervisor
Command update (see Note 2)
v v v v v uplink v v users v v v users -disable, -enable, -unlock v v v write v v zonecfg v
Note: 1. Users with Chassis Operator authority can execute the ping command. 2. Firmware operations for the Server Connectivity Module for IBM BladeCenter require Chassis Administration authority.
Cabling the management module

This topic describes how to cable the management module. You must connect a client computer to the management module to configure and manage operation of the BladeCenter unit. All management modules support a remote management and console (Ethernet) connection. The advanced management module also supports connection through the serial management port. You can manage the BladeCenter unit by using by using the command-line interface that you access through Telnet or through the serial management port (advanced management module only). You can also use the graphical user interface that is provided by the management-module Web interface to manage the
Blade Configuration
Supervisor
13
BladeCenter unit and blade servers that support KVM. Management connections to blade servers that do not support KVM are made using an SOL session through the management-module command-line interface. To connect to the management-module command-line interface, you need the following equipment and information: v A computer 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 the following equipment: A standard Ethernet cable A local Ethernet network port (facility connection) v For direct connection of a computer to the management-module remote management and console (Ethernet) connector, an Ethernet crossover cable. The advanced management module can use either a standard Ethernet cable or an Ethernet crossover cable to make this connection. v For serial connection of a computer to the advanced management-module serial connector, you need a serial cable. See the Installation Guide for your management module for cabling information and instructions. For information about accessing the management-module Web interface, see the BladeCenter Management Module Users Guide. The following topics describe how to cable to the management module to perform initial configuration of the BladeCenter unit. See the Installation Guide for your management module for specific cabling instructions.
Networked connection
This topic describes how to connect the management module to a network. Connect one end of a Category 5 or higher Ethernet cable to the remote management and console (Ethernet) connector of the management module. Connect the other end of the Ethernet cable to the facility network.
Direct connection
This topic tells you how to connect a client computer directly to the management module. For the advanced management module, connect one end of a Category 5 or higher Ethernet cable or a Category 5 or higher Ethernet crossover cable to the remote management and console (Ethernet) connector of the management module. For management modules other than the advanced management module, connect one end of a Category 5 or higher Ethernet crossover cable to the remote management and console (Ethernet) connector of the management module. Connect the other end of the cable to the Ethernet connector on the client computer. Note: The advanced management module can perform an automatic media dependent interface (MDI) crossover, eliminating the need for crossover cables or cross-wired (MDIX) ports. You might need to use a crossover cable to connect to the advanced management module if the network interface card in the client computer is very old.
14
Serial connection (advanced management module only)

This topic tells you how to connect a serial cable to the advanced management module. Connect one end of a serial cable to the serial connector on the management module. Connect the other end of the serial cable to the serial connector on the client computer. See the Installation Guide for your management module for cabling information and instructions.
Starting the command-line interface

This topic tells how to start a command-line interface session. Access the management-module command-line interface from a client computer by establishing a Telnet connection to the IP address of the management module or by establishing a Secure Shell (SSH) connection. For the advanced management module, you can also access the command-line interface using a serial connection. You can establish up to 20 separate Telnet, serial, or SSH sessions to the BladeCenter management module, giving you the ability to have 20 command-line interface sessions active at the same time. Although a remote network administrator can access the management-module command-line interface through Telnet, this method does not provide a secure connection. As a secure alternative to using Telnet to access the command-line interface, use a serial or SSH connection. SSH ensures that all data that is sent over the network is encrypted and secure. The following SSH clients are available. While some SSH clients have been tested, support or non-support of any particular SSH client is not implied. v The SSH clients distributed with operating systems such as Linux, AIX, and UNIX (see your operating-system documentation for information). The SSH client of Red Hat Linux 8.0 Professional was used to test the command-line interface. 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, based on the client software version that is being used.
SSH version 1.5 clients (management modules other than the advanced management module) SSH 1-key exchange algorithm RSA - 1024-bit
Algorithm Public key exchange Host key type
SSH version 2.0 clients Diffie-Hellman-group 1-sha-1 v DSA - 1024-bit (management modules other than the advanced management module) v DSA - 2048-bit (advanced management modules only)
Bulk cipher algorithms MAC algorithms
3-des 32-bit crc
3-des-cbc or blowfish-cbc Hmac-sha1
15
The following topics describe how to connect to the management module to perform initial configuration of the BladeCenter unit. The management module has the following default settings: v IP address: 192.168.70.125 (primary management module) v IP address: 192.168.70.124 (standby management module) v Subnet: 255.255.255.0 v User ID: USERID (all capital letters) v Password: PASSW0RD (note the number zero, not the letter O, in PASSW0RD) The computer that you are connecting to the management module must be configured 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, you must change the Internet protocol properties on the computer that you are connecting. Note: For advanced management modules, the password options presented might vary based on the password options that are configured for the BladeCenter unit.
Telnet connection
This topic tells you how to establish a Telnet session with the management module. To log on to the management module using Telnet, complete the following steps: 1. From a command-line prompt on the network-management workstation, type telnet 192.168.70.125, and press Enter. The IP address 192.168.70.125 is the default IP address of the management module; if a new IP address has been assigned to the management module, use that one instead. 2. At the login prompt, type the management-module user ID. At the password prompt, type the management-module password. The user ID and password are case sensitive and are the same as those that are used for management-module Web access. The default management-module user name is USERID and the default password is PASSW0RD (note the number zero, not the letter O, in PASSW0RD). The CLI command prompt is displayed. You can now enter commands for the management module.
Serial connection
This topic describes how to set up a serial connection with the management module. After connecting a serial cable from the management module to the client computer, complete the following steps: 1. Open a terminal session on the client computer, and make sure that the serial port settings for the client computer match the settings for the serial port on the management module. The default management-module serial port settings are as follows: v Baud rate (BPS): 57600 v v v v Data bits: 8 Parity: no parity Stop bits: 1 Flow control: none
16
2. If any of the serial port settings for the client computer were changed, reset the management module (see the Management Module Installation Guide for instructions). 3. At the login prompt, type the management-module user ID. At the password prompt, type the management-module password. The user ID and password are case sensitive and are the same as those that are used for management-module Web access. The default management-module user name is USERID and the default password is PASSW0RD (note the number zero, not the letter O, in PASSW0RD). The CLI command prompt is displayed. You can now enter commands for the management module.
Secure Shell (SSH) connection

This topic tell you how to establish a Secure Shell (SSH) connection with the management 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 Management Module Users Guide for instructions. 3. Start an SSH session to the management module using the SSH client of your choice. For example, if you are using the cygwin client, from a command-line prompt on the network-management workstation, type ssh 192.168.70.125, and press Enter. The IP address 192.168.70.125 is the default IP address of the management module; if a new IP address has been assigned to the management module, use that one instead. 4. Type the management-module user ID when prompted. At the password prompt, type the management-module password. The user ID and password are case sensitive and are the same as those that are used for management-module Web access. The default management-module user name is USERID and the default password is PASSW0RD (note the number zero, not the letter O, in PASSW0RD). The CLI command prompt is displayed. You can now enter commands for the management module.
Using the Secure Shell server

This topic tells you how to use the management module Secure Shell server. The following SSH clients are available. Although some SSH clients have been tested, 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).
17
If you are using the Secure Shell client based on OpenSSH such as the client that is included in Red Hat Linux version 7.3, to start an interactive command line Secure Shell session to a management module with network address 192.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 the session is to use the login ID USERID. The advanced management module supports non-interactive Secure Shell sessions. This is most useful when combined with public key authentication. Use this capability to issue a single CLI command by adding the command to the end of the ssh command. For example, to get a list of the current users of the advanced management 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 must escape them so that they are not consumed by the command shell on your client machine. For example, to set a new trespass warning, type a command similar to the following:
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 is similar, but in this case it is important to specify that the Secure Shell server session uses a pseudo-terminal (PTY) to get the correct output formatting and keystroke handling. In the following example, which starts a Serial over LAN session to the blade server in slot 2, the -t ssh client option specifies that a PTY should be allocated.
ssh -t -l USERID 192.168.70.1 console -T blade[2]
Using SMASH
This topic explains how to use the System Management Architecture for Server Hardware Command Line Protocol (SMASH CLP) for the advanced management module. See the IBM SMASH Installation and Users Guide for more information. To start an interactive SMASH CLP session using an SSH client such as OpenSSH client with an advanced management module with networking address 192.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 Secure SMASH on the advanced management module and -l USERID specifies one of the 12 local account login IDs. The advanced management module supports non-interactive Secure SMASH sessions. This is most useful when combined with public key authentication. Use this capability to issue a single SMASH CLP command. To start a non-interactive SMASH session it is important to specify that the Secure SMASH server uses a pseudo-terminal (PTY). If you fail to specify a PTY for the session the Input Redirection not Supported error message displays. For example, to get a list of the SMASH-addressable entities, type a command similar to the following:
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 the SMASH command to be executed on the advanced management module.
18
If you are using a Telnet client to start an interactive SMASH CLP session you must specify the correct TCP port number. By default the port assigned to the SMASH protocol is 50023.
SSH CLI exit codes

This topic tells you how to interpret the exit codes returned from SSH CLI commands. All CLI commands that are run in an SSH client single-command environment provide exit codes to indicate their outcome. The following table shows exit codes that are currently supported; other exit codes are reserved for future use.
Table 2. SSH CLI exit codes Name EX_OK EX_USAGE EX_DATAERR EX_NOINPUT EX_UNAVAILABLE EX_SOFTWARE EX_TEMPFAIL Value (decimal) Description 0 64 65 66 69 70 75 Successful command execution. Command-line usage error: syntax error, wrong command arguments or number of arguments, or invalid command target. Input data error: invalid configuration file or SSH key parsing error. Input file did not exist or was not readable. Command-line interface is not available: CLI oversubscribed, CLI disabled, or the data returned by a command has an unexpected value. Internal software error. Check the management module event log for other error indications. Command could not perform a write operation because the device or management module was not in the correct state. Check for conflicting tasks or conditions and try to rerun the command. Authorization error: the user does not have sufficient privileges to execute command. Command not found.
CLI_ERR_NOT_AUTHORIZED CLI_ERR_CNF
126 127
BladeCenter unit configuration

This topic describes how to configure the BladeCenter unit for command-line interface operation. The BladeCenter unit automatically detects the modules and blade servers that are installed and stores the vital product data (VPD). When the BladeCenter unit is started, the management module automatically configures the remote management port of the management module, so that you can configure and manage BladeCenter components. You configure and manage BladeCenter components remotely using the management-module command-line interface (CLI) or the management-module Web interface. To communicate with network resources and with the I/O modules in the BladeCenter unit, you must configure IP addresses for the management module and I/O modules. Management-module IP addresses can be configured using the Web interface or command-line interface. There are several ways to configure the I/O modules: through the management-module Web interface, or through an external I/O-module port enabled through the management module, using a Telnet interface, serial connection (advanced management module only), or a Web browser. See the documentation that comes with each I/O module for information and instructions.
19
To communicate with the blade servers for functions such as deploying an operating system or application program over a network, you must also configure at least one external (in-band) port on an Ethernet switch module in I/O-module bay 1 or 2. Note: If a pass-thru module is installed in I/O-module bay 1 or 2 (instead of an Ethernet I/O module), you will need to configure the network switch that the pass-thru module is connected to; see the documentation that comes with the network switch for instructions.
Configuring the management module

This topic describes how to configure the management module for command-line interface operation. You configure only the primary (active) management module. The redundant management module, if present, receives the configuration and status information automatically from the primary management module when necessary. The configuration information in this topic applies to the primary management module, which might be the only management module in the BladeCenter unit. If the management module that you installed is a replacement for the only management module in the BladeCenter unit, and you saved the configuration file before replacing the management module, you can apply the saved configuration file to the replacement management module. For advance management modules, see read command (advanced management module only) on page 185 for information about applying a saved configuration file. Management modules other than the advance management module must have their configurations restored using the management-module Web interface (see the BladeCenter Management Module Users Guide for information). For the primary management module to communicate, you must configure the IP addresses for the following internal and external ports: v The external Ethernet (remote management) port (eth0) of the management module. The initial automatic management module configuration enables a remote console to connect to the management module to configure the port completely and to configure the rest of the BladeCenter unit. v The internal Ethernet port (eth1) on the management module for communication with the I/O modules. Internal Ethernet ports for the advanced management module cannot be configured. After you connect the primary management module to the network, the Ethernet port connection is configured in one of the following ways. Either of these actions enables 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, IP address, gateway address, subnet mask, and DNS server IP address are set automatically. The host name is set to the management-module MAC address by default, and the domain server cannot change it. v If the DHCP server does not respond within 2 minutes after the port is connected, the management module uses the factory-defined static IP address and default subnet address. Note: If the management module DHCP setting is set to try the DHCP server and then use the static IP address, the management module will use the static IP address when the DHCP server is not available during
20
management module start up. When this occurs, the IP address might not be reachable if multiple management modules were started with the same static IP address. Important: You can not connect to the management module using the factory-defined static IP address and default subnet address until after this 3-minute period passes. Note: If the IP configuration is assigned by the DHCP server, the network administrator can use the MAC address of the management-module network interface to find out what IP address is assigned. To configure the management-module internal and external Ethernet ports, complete the following steps: 1. Connect to the management-module command-line interface (see Starting the command-line interface on page 15 for more information). 2. Configure the external Ethernet interface (eth0), using the ifconfig command (see ifconfig command (advanced management module only) on page 118 for instructions). 3. For management modules other than the advanced management module, configure the internal Ethernet interface (eth1), using the ifconfig command (see ifconfig command (management modules other than the advanced management module) on page 113 for instructions). Note: 1. The internal Ethernet management port on each I/O module provides for communication with the management module. You configure this port by configuring the IP address for the I/O module (see the BladeCenter Management Module Users Guide and the Users Guide for your I/O module type for information and instructions). Some types of I/O modules, such as the pass-thru module, have no management port. See the documentation that comes with each I/O module to determine what else you must configure in the I/O module. 2. For I/O module communication with a remote management station, such as the IBM Director server, through the management-module external Ethernet port, the I/O module internal network interface and the management-module internal and external interfaces must be on the same subnet. 3. To communicate with the blade servers for functions such as deploying an operating system or application program, you also will need to configure at least one external (in-band) port on an Ethernet I/O module.
Starting an SOL session

This topic has instructions for starting an SOL session. Note: Serial over LAN (SOL) must be enabled for both the BladeCenter unit and the blade server before you can start an SOL session with the blade server. See sol (serial over LAN) command on page 205 and the BladeCenter Serial over LAN Setup Guide for information about setting up and enabling SOL. After 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.
21
Since you can start up to 20 separate Web interface, Telnet, serial (advanced management module only), or SSH sessions to the BladeCenter management module, this gives you the ability to have simultaneous SOL sessions active for each blade server installed in the BladeCenter unit. Start an SOL session using the console command, from the command line, indicating the target blade server. For example, to start an SOL connection to the blade server in blade bay 6, type
console -T system:blade[6]
Note: A blade server assembly that occupies more than one blade bay is identified by the lowest bay number that it occupies. Once an SOL session is started, all commands are sent to the blade server specified by the console command until the SOL session is ended, regardless of the persistent command target that was in effect before the SOL session. See sol (serial over LAN) command on page 205 and the IBM BladeCenter Serial over LAN Setup Guide for information about configuring a blade server for SOL. See your operating-system documentation for information about SOL commands that you can enter using the command-line interface.
Ending an SOL session

This topic has instructions for ending an SOL session. To end an SOL session, press Esc followed by an open parenthesis: Esc ( When the SOL session ends, the command-line interface will return to the persistent command target that was in effect before the SOL session. If you want to end the Telnet or SSH command-line session, type exit. Note: Exiting an SOL session does not stop the flow of serial data.
22
Chapter 3. Command reference

This topic contains command function, usage information, and examples. Commands in Command syntax on page 28 are listed in alphabetical order. The following two subtopics provide: v Alphabetical command list v Command list by function on page 26 Adding a -h, -help, or ? option to a command displays syntax help for that command. For example, to display help for the environment command, type one of the following commands: v env -h v env -help v env ? You can target a command to a device other than the one that is set as the default by adding a -T option to a command. See Selecting the command target on page 4 for information.
Alphabetical command list

This topic lists BladeCenter command-line interface commands, in alphabetical order. The commands are as follows: v accseccfg command (advanced management module only) on page 29 v advfailover command (advanced management module only) on page 36 v alarm command (BladeCenter T only) on page 38 v alertcfg command (advanced management module only) on page 44 v alertentries command on page 46 v baydata command (advanced management module only) on page 52 v bofm command (advanced management module only) on page 54 v boot command on page 58 v bootmode command (advanced management module only) on page 59 v bootseq command (advanced management module only) on page 60 v cin command (advanced management module only) on page 64 v cinstatus command (advanced management module only) on page 68 v clear command (management modules other than the advanced management module) on page 69 v clear command (advanced management module only) on page 71 v clearlog command on page 72 v clock command (advanced management module only) on page 73 v config command (advanced management module only) on page 77 v console command on page 79 v dhcpinfo command on page 80 v displaylog command on page 81 v displaysd command (advanced management module only) on page 85 v dns command on page 87 v env (environment) command on page 89 v exit command on page 94 v files command (advanced management module only) on page 95
23
v fuelg command (management modules other than the advanced management module) on page 96 v fuelg command (advanced management module only) on page 99 v health command on page 106 v help command on page 109 v history command on page 111 v identify (location LED) command on page 112 v ifconfig command (management modules other than the advanced management module) on page 113 v ifconfig command (advanced management module only) on page 118 v info (configuration information) command on page 128 v iocomp command (advanced management module only) on page 132 v kvm (keyboard, video, mouse) command (advanced management module only) on page 134 v ldapcfg command (advanced management module only) on page 136 v led command (advanced management module) on page 142 v list (system physical configuration) command on page 146 v modactlog command (advanced management module only) on page 148 v monalerts command (advanced management module only) on page 149 v monalertsleg command (advanced management module only) on page 154 v mt (media tray) command (advanced management module only) on page 159 v nat command (advanced management module only) on page 161 v ntp (network time protocol) command (advanced management module only) on page 164 v ping command (advanced management module only) on page 166 v pmpolicy command (advanced management module only) on page 167 v portcfg command (advanced management module only) on page 170 v ports command (advanced management module only) on page 172 v power command on page 181 v read command (advanced management module only) on page 185 v remotechassis command (advanced management module only) on page 187 v reset command on page 190 v sddump command (advanced management module only) on page 194 v security command (advanced management module only) on page 195 v service command (advanced management module only) on page 196 v shutdown command (advanced management module only) on page 197 v slp command (advanced management module only) on page 198 v smtp command on page 199 v snmp command on page 200 v sol (serial over LAN) command on page 205 v sshcfg command (advanced management module only) on page 210 v sslcfg command (advanced management module only) on page 212 v syslog command (advanced management module only) on page 218 v tcpcmdmode command (management modules other than the advanced management module) on page 220 v tcpcmdmode command (advanced management module only) on page 222 v telnetcfg (Telnet configuration) command on page 224 v temps command (advanced management module only) on page 225 v trespass command (advanced management module only) on page 226 v uicfg command (advanced management module only) on page 228 v update (update firmware) command on page 230 v uplink (management module failover) command (management modules other than the advanced management module) on page 233 v uplink (management module failover) command (advanced management module only) on page 235
24
v users command (management modules other than the advanced management module) on page 238 v users command (advanced management module only) on page 247 v volts command (advanced management module only) on page 262 v write command (advanced management module only) on page 263 v zonecfg command (advanced management module only) on page 265
25
Command list by function

This topic lists BladeCenter command-line interface commands, based on their function. The commands are as follows: v Built-in commands Use these commands to perform top-level functions within the command-line interface: env (environment) command on page 89 help command on page 109 history command on page 111 list (system physical configuration) command on page 146 v Common commands Use these commands to monitor and control operation of BladeCenter components: health command on page 106 info (configuration information) command on page 128 v Configuration commands Use these commands to view and configure network settings, Ethernet interfaces, and other functions: accseccfg command (advanced management module only) on page 29 advfailover command (advanced management module only) on page 36 alertcfg command (advanced management module only) on page 44 alertentries command on page 46 baydata command (advanced management module only) on page 52 bofm command (advanced management module only) on page 54 bootmode command (advanced management module only) on page 59 bootseq command (advanced management module only) on page 60 cin command (advanced management module only) on page 64 cinstatus command (advanced management module only) on page 68 clock command (advanced management module only) on page 73 config command (advanced management module only) on page 77 dhcpinfo command on page 80 displaysd command (advanced management module only) on page 85 dns command on page 87 files command (advanced management module only) on page 95 ifconfig command (management modules other than the advanced management module) on page 113 ifconfig command (advanced management module only) on page 118 iocomp command (advanced management module only) on page 132 kvm (keyboard, video, mouse) command (advanced management module only) on page 134 ldapcfg command (advanced management module only) on page 136 monalerts command (advanced management module only) on page 149 monalertsleg command (advanced management module only) on page 154 mt (media tray) command (advanced management module only) on page 159 nat command (advanced management module only) on page 161 ntp (network time protocol) command (advanced management module only) on page 164 pmpolicy command (advanced management module only) on page 167 portcfg command (advanced management module only) on page 170 ports command (advanced management module only) on page 172
26
read command (advanced management module only) on page 185 remotechassis command (advanced management module only) on page 187 sddump command (advanced management module only) on page 194 security command (advanced management module only) on page 195 service command (advanced management module only) on page 196 slp command (advanced management module only) on page 198 smtp command on page 199 snmp command on page 200 sol (serial over LAN) command on page 205 sshcfg command (advanced management module only) on page 210 sslcfg command (advanced management module only) on page 212 tcpcmdmode command (management modules other than the advanced management module) on page 220 tcpcmdmode command (advanced management module only) on page 222 telnetcfg (Telnet configuration) command on page 224 temps command (advanced management module only) on page 225 trespass command (advanced management module only) on page 226 uicfg command (advanced management module only) on page 228 uplink (management module failover) command (management modules other than the advanced management module) on page 233 uplink (management module failover) command (advanced management module only) on page 235 users command (management modules other than the advanced management module) on page 238 users command (advanced management module only) on page 247 zonecfg command (advanced management module only) on page 265 v Discovery commands Use these commands to locate other resources on the network: ping command (advanced management module only) on page 166 remotechassis command (advanced management module only) on page 187 v Event log commands Use these commands to view and clear primary management-module event log entries: clearlog command on page 72 displaylog command on page 81 modactlog command (advanced management module only) on page 148 syslog command (advanced management module only) on page 218 v LED Commands Use these commands to monitor and control operation of BladeCenter unit LEDs: identify (location LED) command on page 112 led command (advanced management module) on page 142 v Memory Commands Use these commands to reset the management module configuration and perform firmware updates: clear command (management modules other than the advanced management module) on page 69 clear command (advanced management module only) on page 71 update (update firmware) command on page 230
27
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 58 power command on page 181 reset command on page 190 shutdown command (advanced management module only) on page 197 v Power management commands Use these commands to monitor power consumption of the BladeCenter unit and installed components: fuelg command (management modules other than the advanced management module) on page 96 fuelg command (advanced management module only) on page 99 volts command (advanced management module only) on page 262 v Save and restore configuration commands Use these commands to save and restore the management module configuration: read command (advanced management module only) on page 185 write command (advanced management module only) on page 263 v Session commands Use these commands to start an SOL connection to the command console of a specific blade server or to end a command console session: console command on page 79 exit command on page 94 v System management commands (BladeCenter T only) Use these commands to manage alarms for monitored parameters of the BladeCenter T unit: alarm command (BladeCenter T only) on page 38
Command syntax
Each of the following topics describes a command-line interface command and its syntax. Each command description also includes an example of command use.
28
accseccfg command (advanced management module only)

This command displays and configures account security settings for the advanced management module.
Table 3. accseccfg command Function Display account security settings What it does Displays the user account security settings for the advanced management module. Returned values are: v Default security settings used (legacy, high, or custom) v -am: user authentication method (local, ldap, localldap, or ldaplocal) v -alt: authentication logging timeout (in seconds) v -cp: complex password (on, off) v -ct: CLI inactivity session timeout (in seconds) v -dc: minimum different characters in the password (when -cp is enabled) v -de: default administration password expiration (on, off) v -ia: account inactivity alert time period (in days) v -ici: log new login events from same user (on, off) v -id: account inactivity disable time period (in days) v -lf: maximum login failures v -lp: lockout period after maximum login failures (in minutes) v -mls: maximum simultaneous user sessions v -pc: password change on first access (on, off) v -pe: password expiration time period (in days) v -pi: minimum password change interval (in hours) v -pr: password required (on, off) v -rc: password reuse cycle v -wt: Web inactivity session timeout (in minutes, none, or based on length of user session) Command accseccfg Valid targets -T system:mm[x] where x is the primary management-module bay number.
29
Table 3. accseccfg command (continued) Function Set account defaults to legacy level What it does Sets management module account security to a predefined legacy set of default values. Legacy default values are: v -alt: retains set value v -am: local v -cp: off v -ct: 10000 v -dc: 0 v -de: off v -ia: 0 v -ici: retains set value v -id: 0 v -lf: 5 v -lp: 2 v -mls: retains set value v -pc: off v -pe: 0 v -pi: 0 v -pr: off v -rc: 0 v -wt: user Note: v The user that is running the accseccfg -legacy command must have a password assigned. v The -legacy option must be run alone and not in conjunction with any other accseccfg command options. Command accseccfg -legacy Valid targets -T system:mm[x]
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number.
30
Table 3. accseccfg command (continued) Function Set account defaults to high level What it does Sets management module account security to a predefined high set of default values. High default values are: v -am: local v -cp: on v -ct: 10000 v -dc: 2 v -de: on v -ia: 120 v -id: 180 v -lf: 5 v -lp: 60 v -pc: on v -pe: 90 v -pi: 24 v -pr: on v -rc: 5 v -wt: user Note: v The user that is running the accseccfg -high command must have a password assigned. v The -high option must be run alone and not in conjunction with any other accseccfg command options. Set authentication logging timeout Sets custom value for the amount of time that the management module will not log repeated logins by the same user. accseccfg -alt timeout where timeout is 0, 5, 30, 60, 300, 600, 1800, 3600, 43200, or 86400 seconds. If no value is entered, login logging is disabled. Command use restricted (see Commands and user authority on page 6). Set user authentication method Sets custom value for management accseccfg -am method module user authentication method. where method is local, ldap, localldap or ldaplocal. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. Command accseccfg -high Valid targets -T system:mm[x]
31
Table 3. accseccfg command (continued) Function Enable complex password What it does Enable complex password for management module user authentication. Note: Enabling the complex password also turns on the password required (-pr) command option. Disable complex password for management module user authentication. Command accseccfg -cp on Valid targets -T system:mm[x]
Disable complex password
accseccfg -cp off
-T system:mm[x]
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. -T system:mm[x] where x is the primary management-module bay number.
Set CLI inactivity timeout
Sets custom value for management accseccfg -ct timeout module CLI inactivity session where timeout is from 0 to timeout. 4,294,967,295 seconds, inclusive. Command use restricted (see Commands and user authority on page 6).
Set minimum number of Sets custom value for the minimum different characters for number of different characters to be password used in a management module password. Note: The minimum number of different characters applies only when complex passwords are enabled. Enable default administration password expiration Enable default administration password expiration for management module.
accseccfg -dc number
-T system:mm[x]
where number is from 0 to where x is the primary 15, inclusive. management-module bay number. Command use restricted (see Commands and user authority on page 6). accseccfg -de on -T system:mm[x]
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. accseccfg -de off -T system:mm[x]
Disable default administration password expiration
Disable default administration password expiration for management module.
Set account inactivity alert time
Sets custom value for management accseccfg -ia time module account inactivity alert time. where time is from 0 to Note: The accseccfg -ia value must be less than the accseccfg -id 365 days, inclusive. value. Command use restricted (see Commands and user authority on page 6). Enables or disables logging of new login events from the same user from the same IP address. Note: This value applies only if the value set by the -alt command option is set to something other than 0 or none. accseccfg -ici state where state is on or off. Command use restricted (see Commands and user authority on page 6).
Set state for logging of login events from same IP address
-T system:mm[x] where x is the primary management-module bay number.
32
Table 3. accseccfg command (continued) Function Set account inactivity disable time What it does Sets custom value for management module account inactivity disable time. Note: The accseccfg -id value must be less than the accseccfg -ia value. Command accseccfg -id time where time is from 0 to 365 days, inclusive. Command use restricted (see Commands and user authority on page 6). Valid targets -T system:mm[x] where x is the primary management-module bay number.
Set maximum number of login failures
Sets custom value for the maximum accseccfg -lf number -T system:mm[x] number of login failures before the where number is from 0 to where x is the primary management module locks out a 10, inclusive. user. management-module bay number. Command use restricted (see Commands and user authority on page 6). Sets custom value for management accseccfg -lp time module account lockout period, used when the maximum number of where time is from 0 to 2880 minutes, inclusive. login failures is exceeded. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number.
Set lockout period
Set maximum LDAP sessions for user
Sets custom value for the maximum accseccfg -mls number of simultaneous login max_sessions sessions allowed for a single LDAP where max_sessions is user from 0 to 20, inclusive. Command use restricted (see Commands and user authority on page 6).
Enable password change at first login
Enable mandatory password accseccfg -pc on change at first management module Command use restricted login. (see Commands and user authority on page 6). Disable mandatory password accseccfg -pc off change at first management module Command use restricted login. (see Commands and user authority on page 6). accseccfg -pe time where time is from 0 to 365 days, inclusive. Command use restricted (see Commands and user authority on page 6).
-T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number.
Disable password change at first login
Set password expiration Sets custom value for the time management module password expiration time.
33
Table 3. accseccfg command (continued) Function Set password minimum change interval What it does Sets custom value for the minimum amount of time between management module password changes. Command accseccfg -pi time Valid targets -T system:mm[x]
where time is from 0 to where x is the primary 1440 hours, inclusive, and management-module less than password bay number. expiration period when that period is greater than 0. Command use restricted (see Commands and user authority on page 6).
Enable password required
Enable password required for management module. Note: The user that is running the accseccfg -pr command must have a password assigned. Disable password required for management module. Note: v The user that is running the accseccfg -pr command must have a password assigned. v Disabling password required also turns off the complex password (-cp) command option.
accseccfg -pr on
-T system:mm[x]
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. accseccfg -pr off -T system:mm[x]
Disable password required
Set password reuse cycle
Sets custom value for the management module password reuse cycle. This setting determines how many times a password must be changed before being reused.
accseccfg -rc number_reuses where number_reuses is from 0 to 5, inclusive. Command use restricted (see Commands and user authority on page 6).
Set Web interface inactivity timeout
Sets custom value for management accseccfg -wt timeout module Web interface inactivity where timeout is 1, 5, 10, session timeout. 15, or 20 minutes, none (no timeout), or user (user picks timeout each time they log in to the Web interface). Command use restricted (see Commands and user authority on page 6).
34
Example: To set management module account security to use the high level defaults, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
accseccfg -high
To display the account security settings for the management module, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
accseccfg
The following example shows the information that is returned from these two commands:
system:mm[1]> accseccfg -high OK system: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 user system:mm[1]>
35
advfailover command (advanced management module only)

This command displays and configures the advanced failover settings for the advanced management module.
Table 4. advfailover command Function Display management module advanced failover settings What it does Displays the advanced failover settings for the management module. Possible return values are: v off - disable network interface for the redundant management module v swap - enable the redundant management module network interface and swap IP addresses between the two management modules during failover v noswap - enable the redundant management module network interface and do not swap IP addresses between the two management modules during failover Note: This command does not apply to the BladeCenter S, which only supports a single advanced management module. Disable network interface for redundant management module Disables the network interface for the redundant management module, preventing failover. advfailover -ip off -T system:mm[x] Command advfailover Valid targets -T system:mm[x] where x is the primary management-module bay number.
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. advfailover -ip swap -T system:mm[x]
Enable network interface and allow IP address swap during failover
Enables the network interface for the redundant management module and allows the IP addresses to swap between the two management modules during failover.
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. advfailover -ip noswap -T system:mm[x]
Enable network Enables the network interface for interface and prevent IP the redundant management module address swap during and prevents the IP addresses from failover swapping between the two management modules during failover.
36
Example: To disable the network interface for the redundant management module, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
advfailover -ip off
To display the management module advanced failover setting, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
advfailover
system:mm[1]> advfailover -ip off OK system:mm[1]> advfailover -ip off system:mm[1]>
37
alarm command (BladeCenter T only)

This command displays alarm information, acknowledges alarms, and clears alarms for the specified command target.
Table 5. alarm command Function Display all alarms (management modules other than the advanced management module) What it does Command Valid targets -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 primary management-module, blade server, I/O (switch) module, power module, or blower bay number. -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 primary management-module, blade server, I/O (switch) module, power module, or blower bay number. -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 primary management-module, blade server, I/O (switch) module, power module, or blower bay number.
Display all alerts generated by the alarm target component. When directed to the BladeCenter unit, the command returns a summary of alarms for all BladeCenter components. When directed to a component installed in the BladeCenter unit, the command returns a detailed alarm listing for that component. Detailed alarm listings include an alarm key that can be used to acknowledge or clear an alarm.
Display all alarms (advanced management module only)
Display all alerts generated by the alarm -q target component. When directed to the BladeCenter unit, the command returns a summary of alarms for all BladeCenter components. When directed to a component installed in the BladeCenter unit, the command returns a detailed alarm listing for that component. Detailed alarm listings include an alarm key that can be used to acknowledge or clear an alarm.
Display power alarms
Display all power related alerts alarm -p generated by the target component. When directed to the BladeCenter unit, the command returns a summary of alarms for all BladeCenter components. When directed to a component installed in the BladeCenter unit, the command returns a detailed alarm listing for that component. Detailed alarm listings include an alarm key that can be used to acknowledge or clear an alarm.
38
Table 5. alarm command (continued) Function Display alarm information (specified by alarm generator ID) What it does Display information for alarm specified by the generator ID. Command alarm -q -g value where value is the generator ID. Valid targets -T system:mm[x] -T system:blade[x] -T system:switch[x]
-T system:power[x] Command use restricted (see Commands and user -T system:blower[x] authority on page 6). where x is the primary management-module, blade server, I/O (switch) module, power module, or blower bay number. Display alarm information (specified by alarm ID) Display information for alarm specified by the alarm ID. alarm -q -a value where value is the alarm ID. -T system:mm[x] -T system:blade[x] -T system:switch[x] -T system:power[x] -T system:blower[x] where x is the primary management-module, blade server, I/O (switch) module, power module, or blower bay number. Display detailed alarm information (specified by generator information) Display detailed information for alarm -q -o value alarm specified by the alarm where value is the generator information. Information generator information. returned includes the alarm description that is shown by the management-module Web interface and other information such as the alarm severity, power source, software indicator, and an alarm key. -T system:mm[x] -T system:blade[x] -T system:switch[x] -T system:power[x] -T system:blower[x] where x is the primary management-module, blade server, I/O (switch) module, power module, or blower bay number. -T system:mm[x] -T system:blade[x] -T system:switch[x] -T system:power[x] -T system:blower[x] where x is the primary management-module, blade server, I/O (switch) module, power module, or blower bay number.
Display alarm information (specified by complete alarm key)
Display information for alarm specified by the complete alarm key.
alarm -q -k m:g:o:a where m:g:o:a is the complete alarm key: v m is the module ID v g is the generator ID v o is the generator information v a is the alarm ID
39
Table 5. alarm command (continued) Function Acknowledge alarm (specified by alarm generator ID) What it does Command Valid targets -T system:mm[x] -T system:blade[x] -T system:switch[x]
Acknowledge the alarm specified by alarm -r -g value the generator ID. where value is the generator ID.
-T system:power[x] Command use restricted (see Commands and user -T system:blower[x] authority on page 6). where x is the primary management-module, blade server, I/O (switch) module, power module, or blower bay number. Acknowledge alarm (specified by generator information) Acknowledge the alarm specified by alarm -r -o value the generator information. where value is the generator information. -T system:mm[x] -T system:blade[x] -T system:switch[x]
-T system:power[x] Command use restricted (see Commands and user -T system:blower[x] authority on page 6). where x is the primary management-module, blade server, I/O (switch) module, power module, or blower bay number. Acknowledge alarm (specified by alarm ID) Acknowledge the alarm specified by alarm -r -a value the alarm ID. where value is the alarm ID. -T system:mm[x] -T system:blade[x] -T system:switch[x]
-T system:power[x] Command use restricted (see Commands and user -T system:blower[x] authority on page 6). where x is the primary management-module, blade server, I/O (switch) module, power module, or blower bay number. Acknowledge alarm (specified by complete alarm key) Acknowledge the alarm specified by alarm -r -k m:g:o:a the complete alarm key. where m:g:o:a is the complete alarm key: v m is the module ID v g is the generator ID v o is the generator information v 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]
where x is the primary management-module, blade server, I/O Command use restricted (switch) module, power (see Commands and user module, or blower bay authority on page 6). number.
40
Table 5. alarm command (continued) Function Clear alarm (specified by alarm generator ID) What it does Clear the alarm specified by the generator ID. Command alarm -c -g value where value is the generator ID. Valid targets -T system:mm[x] -T system:blade[x] -T system:switch[x]
-T system:power[x] Command use restricted (see Commands and user -T system:blower[x] authority on page 6). where x is the primary management-module, blade server, I/O (switch) module, power module, or blower bay number. Clear alarm (specified by generator information) Clear the alarm specified by the generator information. alarm -c -o value where value is the generator information. -T system:mm[x] -T system:blade[x] -T system:switch[x]
-T system:power[x] Command use restricted (see Commands and user -T system:blower[x] authority on page 6). where x is the primary management-module, blade server, I/O (switch) module, power module, or blower bay number. Clear alarm (specified by alarm ID) Clear the alarm specified by the alarm ID. alarm -c -a value where value is the alarm ID. -T system:mm[x] -T system:blade[x] -T system:switch[x]
-T system:power[x] Command use restricted (see Commands and user -T system:blower[x] authority on page 6). where x is the primary management-module, blade server, I/O (switch) module, power module, or blower bay number. Clear alarm (specified by complete alarm key) Clear the alarm specified by the complete alarm key. alarm -c -k m:g:o:a where m:g:o:a is the complete alarm key: v m is the module ID v g is the generator ID v o is the generator information v 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]
where x is the primary management-module, blade server, I/O Command use restricted (switch) module, power (see Commands and user module, or blower bay authority on page 6). number.
41
Table 5. alarm command (continued) Function Set alarm What it does Set an alarm for the specified target, including severity level and description. Command alarm -s -l level desc where v level is the severity level: CRT (critical) MJR (major) MNR (minor) v desc is a short text description of the alarm Valid targets -T system:mm[x] -T system:blade[x] -T system:switch[x] -T system:power[x] -T system:blower[x]
where x is the primary management-module, blade server, I/O (switch) module, power Command use restricted module, or blower bay (see Commands and user number. authority on page 6).
Example: To display the alarm status for the BladeCenter T unit, while the BladeCenter T unit is set as the persistent command environment, at the system> prompt, type
alarm -q
To display the power alarm status for the BladeCenter T unit, while the BladeCenter T unit is set as the persistent command environment, at the system> prompt, type
alarm -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 the system> prompt, type
alarm -T system:power[2] -q
The following example shows the information that is returned from a series of alarm commands. This example assumes that the blade server in blade bay 3 has a major over-temperature fault and that the power module in power bay 2 has a critical fault.
system> alarm -q Alarms Summary List Module Severity Power S/W power[2] CRT Yes No blade[3] MJR No No system> alarm -p Alarms Summary List Module Severity Power S/W power[2] CRT Yes No system> alarm -T system:power[2] -q Alarms Detailed List Severity Power S/W Description Key CRT Yes No Under Voltage 2:1:3:2 system> alarm -c -k 2:1:3:2 -T system:power[2] Alarm Cleared system> alarm -T system:power[2] -q No Active Alarms system> alarm Alarms Summary List Module Severity Power S/W blade[3] MJR No No system> alarm -T system:blade[3] -q Alarms Detailed List Severity Power S/W Description Key
42
MJR system> OK system> OK system> Failed. system>
No No alarm -s -l CRT
Over temperature
3:3:1:3
alarm -s -l MNR -p Investigate Watts -T system:blade[2] alarm -s -l CRT -p Under Voltage -T system:blade[2] AlarmID is being used
43
alertcfg command (advanced management module only)

This command displays and configures the global remote alert settings for the advanced management module.
Table 6. alertcfg command Function Display global remote alert settings What it does Displays the global remote alert settings for the advanced management module. Command alertcfg Valid targets -T system:mm[x] where x is the primary management-module bay number. alertcfg -dr delay -T system:mm[x]
Set interval between remote alert retries
Sets the remote alert retry interval to the input delay value.
where delay is from 0.5 where x is the primary minutes to 4.0 minutes, management-module inclusive, in 0.5 minute bay number. increments. If you enter a value less than 0.5 minute, the retry interval will be set to 0.5 minute. If you enter a value greater than 4.0 minutes, the retry interval will be set to 4.0 minutes. Command use restricted (see Commands and user authority on page 6). Include event log with email alerts Enables inclusion of the event log with email alerts. alertcfg -el enabled -T system:mm[x]
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. Exclude event log from email alerts Disables inclusion of the event log with email alerts. alertcfg -el disabled -T system:mm[x]
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. Set remote alert retry limit Sets the maximum number of times alertcfg -rl value the system will attempt to send a where value is from 0 to 8, remote alert, if previous attempts inclusive. If you enter a were unsuccessful. value of 0, no retries will be attempted. If you enter a value greater than 8, an error will be displayed. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number.
44
Example: To view the remote alert configuration, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
alertcfg
To set the remote alert retry limit to 2, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
alertcfg -rl 2
The following example shows the information that is returned from these commands:
system:mm[1]> alertcfg -dr 1.0 -el disabled -rl 5 system:mm[1]> alertcfg -rl 2 OK system:mm[1]> alertcfg -dr 1.0 -el disabled -rl 2 system:mm[1]>
45
alertentries command
This command manages the recipients of alerts generated by the primary management module.
Table 7. alertentries command Function Display alert properties for all recipients What it does Command Valid targets -T system:mm[x] where x is the primary management-module bay number.
Displays alert properties for all alertentries management-module alert recipients. Returned values for each alert recipient are: v recipient name v notification method (E-Mail over LAN/Director comp./SNMP over LAN) v type of alerts received (Receives critical alerts only/Receives all alerts/Disabled)
Display alert properties for alert recipients
Displays alert properties for the alertentries -recip_number specified management-module alert where recip_number is a recipient profile. Returned values number from 1 to 12 that are: corresponds to the v -status alert_recipient_status recipient number assigned (on/off) in the Display alert v -n alert_recipient_name properties for all recipients list. v -f alert_type (critical/none) v -t notification_method (email/director/snmp) v -e email_address (used for e-mail notifications) v -i static_IP_addr/hostname (used for IBM Director notifications)
Delete alert recipient
Delete the specified alert recipient.
alertentries -recip_number -del where recip_number is a number from 1 to 12 that corresponds to the recipient number assigned in the Display alert properties for all recipients list. It is possible to delete an empty alert recipient. Command use restricted (see Commands and user authority on page 6).
46
Table 7. alertentries command (continued) Function Create alert recipient What it does Create the specified alert recipient. All fields must be specified when creating an alert recipient. Command alertentries -recip_number -n recip_name -status alert_status -f filter_type -t notification_method -e email_addr -i ip_addr/hostname where: v recip_number is a number from 1 to 12 that corresponds to an unused recipient number in the Display alert properties for all recipients list. v recip_name is a alphanumeric string up to 31 characters in length containing any character, including spaces, except for angle brackets ( < and > ). If the string includes spaces it must be enclosed in double-quotes. v alert_status is on or off for receipt of alerts. v filter_type filters the alert types received: critical (receive critical alerts only) or none (receive all alerts). v notification_method is email, director (IBM Director) or snmp. For e-mail, you must specify an e-mail address (-e argument). For director, you must specify an IP address (-i argument). If snmp is selected, the -e and -i arguments are not needed. v email_addr is a valid e-mail address string up to 63 characters in length. (continued on next page) Valid targets -T system:mm[x] where x is the primary management-module bay number.
47
Table 7. alertentries command (continued) Function Create alert recipient (continued) What it does Command v ip_addr/hostname is a valid static IP address or an alphanumeric hostname string for the recipient that is up to 49 characters in length that can include periods ( . ), hyphens ( - ), and underscores ( _ ). Command use restricted (see Commands and user authority on page 6). Set alert recipient name Sets a name for the specified alert recipient. alertentries -recip_number -n recip_name -T system:mm[x] Valid targets
where x is the primary where: management-module v recip_number is a bay number. number from 1 to 12 that corresponds to the recipient number assigned in the Display alert properties for all recipients list. v recip_name is a alphanumeric string up to 31 characters in length that can include any character, including spaces, except for angle brackets ( < and > ). If the name includes spaces it must be enclosed in double-quotes. Command use restricted (see Commands and user authority on page 6). Set alert recipient status Sets status for the specified alert alertentries -recip_number recipient. The status determines if a -status alert_status recipient will receive alarm where: notifications. v recip_number is a number from 1 to 12 that corresponds to the recipient number assigned in the Display alert properties for all recipients list. v alert_status is on or off. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number.
48
Table 7. alertentries command (continued) Function Set alert types received What it does Filters the types of alert that are received by the specified alert recipient. Command alertentries -recip_number -f filter_type Valid targets -T system:mm[x]
where x is the primary where: management-module v recip_number is a bay number. number from 1 to 12 that corresponds to the recipient number assigned in the Display alert properties for all recipients list. v alert_type filters the alert types received: critical (receive critical alerts only) or none (receive all alerts). Command use restricted (see Commands and user authority on page 6).
Set alert notification method
Sets the alert notification method for the specified alert recipient.
alertentries -recip_number -t notification_method
-T system:mm[x]
where x is the primary where: management-module v recip_number is a bay number. number from 1 to 12 that corresponds to the recipient number assigned in the Display alert properties for all recipients list. v notification_method is email, director (IBM Director) or snmp. Command use restricted (see Commands and user authority on page 6). Set alert recipient e-mail address Sets the e-mail address for the specified alert recipient. This e-mail address is used to send alerts to the recipient via e-mail. alertentries -recip_number -e email_addr -T system:mm[x]
where x is the primary where: management-module v recip_number is a bay number. The e-mail address can be set only number from 1 to 12 if the alert notification method (-t that corresponds to the option) is set to email. The -t and -e recipient number options can be combined within the assigned in the Display same command. alert properties for all recipients list. v email_addr is a valid e-mail address string up to 63 characters in length. Command use restricted (see Commands and user authority on page 6).
49
Table 7. alertentries command (continued) Function Set alert recipient IP address or hostname What it does Sets the IP address or hostname used to send alert notifications to the specified alert recipient using IBM Director. Command alertentries -recip_number -i ip_addr/hostname Valid targets -T system:mm[x]
where x is the primary where: management-module v recip_number is a bay number. The IP address or hostname used number from 1 to 12 to send alert notifications can be that corresponds to the set only if the alert notification recipient number method (-t option) is set to director assigned in the Display (IBM Director). The -t and -i options alert properties for all can be combined within the same recipients list. command. v ip_addr/hostname is a valid static IP address or an alphanumeric hostname string up to 49 characters in length that can include periods ( . ), hyphens ( - ), and underscores ( _ ). Command use restricted (see Commands and user authority on page 6). Generate test alert (advanced management module only) Generates a test alert to verify correct alert response. Note: The alertentries -test command option must be used alone. alertentries -test -T system:mm[x]
Example: To view the configuration for alert recipient 1, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
alertentries -1
To configure alert recipient 2 to receive only critical alert notifications by e-mail, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
alertentries -2 -n test2 -status on -f critical -t email -e test2@us.ibm.com
To configure alert recipient 3 to receive all alert notifications through IBM Director, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
alertentries -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, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
alertentries -4 -n test4 -status on -f none -t snmp
50
system:mm[1]> alertentries -status on -n test1 -f critical -t email -e test1@us.ibm.com system:mm[1]> alertentries -e test2@us.ibm.com OK system:mm[1]> alertentries -i 192.168.70.140 OK system:mm[1]> alertentries OK system:mm[1]> -1
-2 -n test2 -status on -f critical -t email -3 -n test3 -status on -f none -t director -4 -n test4 -status on -f none -t snmp
51
baydata command (advanced management module only)

This command allows a user to set, assign, and display informational data assigned to the blade server bays.
Table 8. baydata command Function Display bay data for all blade servers Display blade server bay data for a specific bay What it does Displays blade server bay data for bay number, bay data status, and defined bay data for all bays. Command baydata Valid targets -T system
Displays the information assigned baydata -b bay_num -T system to the specified blade bay using the where bay_num is the -b option. number of the specific bay to display. The bay number must be within the scope assigned to the user. Command use restricted (see Commands and user authority on page 6).
Clear bay data
Clears the blade bay definition strings for all bays.
baydata -clear The bay number must be within the scope assigned to the user. Command use restricted (see Commands and user authority on page 6).
-T system
Clear bay data for specific bay
Clears the blade bay definition strings for the specified blade bay.
baydata -b bay_num -clear -T system where bay_num is the number of the specified bay to clear of data. The bay number must be within the scope of the user. Command use restricted (see Commands and user authority on page 6).
Set bay data
Sets blade bay data for all blade servers within the users scope. This information can include: data about drivers or software, the BladeCenter unit shelf number and IP address, and whether the blade server position in a high-availability applications. Note: To apply changes to the BIOS/SMBIOS structure, power-off and power-on the blade server, restart the blade server, or remove and reinstall the blade server.
baydata -data data_definition where data definition is the ASCII string of up to 60 characters enclosed in double quotation marksdata definition. The quotation marks are not stored. Command use restricted (see Commands and user authority on page 6).
-T system
52
Table 8. baydata command (continued) Function Set blade bay data definition for specific blade server What it does Sets blade bay data for the specified blade server using the b option. Note: To apply changes to the BIOS/SMBIOS structure, power-off and power-on the blade server, restart the blade server, or remove and reinstall the blade server. If the command is issued to a specific bay, data is written to that blade server if it is in the users scope. Command baydata -b bay_num -data data_definition where: v bay_num is the blade bay v where data definition is the ASCII string of up to 60 characters enclosed in double quotation marksdata definition. The quotation marks are not stored. Command use restricted (see Commands and user authority on page 6). Valid targets -T system
Example: To view the bay data for all blades, while the management module is set as the persistend command environment, at the system> prompt, type
baydata
The following example shows the information that is returned from this command:
Bay Status Definition 1 Unsupported 2 No blade present 3 No blade present 4 No blade present 5 No blade present 6 No blade present 7 No blade present 8 No blade present 9 No blade present 10 No blade present 11 No blade present 12 No blade present 13 No blade present 14 No blade present system>
53
bofm command (advanced management module only)

This command applies a new BladeCenter Open Fabric Manager (BOFM) configuration to all the specified BladeCenter units, bays, and ports. Note: Open Fabric Manager is not a standard management module feature; it is offered and documented separately. See the BladeCenter Open Fabric Manager Installation and Users Guide for more detailed information.
Table 9. bofm command Function Apply BOFM configuration to specified BladeCenter units, bays, and ports What it does Copies a configuration file from a TFTP server to the specified management module, which then configures BladeCenter units, blade servers, and I/O modules. The configuration file is a comma-separated values (CSV) file that assigns IP addresses and other values to BladeCenter units, bays, and ports. Command bofm -l filename -i ip_address where: v filename is the name of the configuration file. v ip_address is the IP address of TFTP server where the configuration file is located. Note: Both the -l filename option and the -i ip_address option need to be specified. Command use restricted (see Commands and user authority on page 6). Apply BOFM configuration to specified BladeCenter units, bays and ports while ignoring duplicate lines in the configuration file Copies a configuration file from a TFTP server to the specified management module, which then configures BladeCenter units, blade servers, and I/O modules, even if it encounters duplicate lines in the configuration file. The configuration file is a comma-separated values (CSV) file that assigns IP addresses and other values to BladeCenter units, bays, and ports. bofm -l filename -i ip_address -d off -T system:mm[x] Valid targets -T system:mm[x] where x is the primary management-module bay number.
where x is the primary where: management-module v filename is the name of bay number. the configuration file. v ip_address is the IP address of TFTP server where the configuration file is located. v The -d off option causes bofm to ignore duplicate lines in the configuration file. Note: Both the -l filename option and the -i ip_address option need to be specified. Command use restricted (see Commands and user authority on page 6).
54
Table 9. bofm command (continued) Function Apply BOFM configuration to specified BladeCenter units, bays, and ports unless there are duplicate lines in the configuration file What it does Copies a configuration file from a TFTP server to the specified management module, which then configures BladeCenter units, blade servers, and I/O modules, but halts the operation if it encounters duplicate lines in the configuration file. The configuration file is a comma-separated values (CSV) file that assigns IP addresses and other values to BladeCenter units, bays, and ports. Command bofm -l filename -i ip_address -d on where: v filename is the name of the configuration file. v ip_address is the IP address of TFTP server where the configuration file is located. v The -d on option halts bofm if there are duplicate lines in the configuration file. Note: Both the -l filename option and the -i ip_address option need to be specified. Command use restricted (see Commands and user authority on page 6). Apply BOFM configuration to specified BladeCenter units, bays, and ports even if the bays are powered on Copies a configuration file from a TFTP server to the specified management module, which then configures BladeCenter units, blade servers, and I/O modules, unless the bays are powered on. The configuration file is a comma-separated values (CSV) file that assigns IP addresses and other values to BladeCenter units, bays, and ports. bofm -l filename -i ip_address -p on where: v filename is the name of the configuration file. v ip_address is the IP address of TFTP server where the configuration file is located. v The -p on option halts the bofm command if bays are powered on. Note: Both the -l filename option and the -i ip_address option need to be specified. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number. Valid targets -T system:mm[x] where x is the primary management-module bay number.
55
Table 9. bofm command (continued) Function Apply BOFM configuration to specified BladeCenter units, bays, and ports unless bays are powered on What it does Copies a configuration file from a TFTP server to the specified management module, which then configures BladeCenter units, blade servers, and I/O modules, without checking if the bays are powered on. Command bofm -l filename -i ip_address -p off Valid targets -T system:mm[x] where x is the primary management-module bay number.
where: v filename is the name of the configuration file. v ip_address is the IP address of TFTP server The configuration file is a where the configuration comma-separated values (CSV) file is located. file that assigns IP addresses and v The -p off option forces other values to BladeCenter units, BOFM to apply the bays, and ports. configuration file to Note: If the BOFM configuration is blade servers that are applied to bays that are powered powered on. on, the system may acquire Note: Both the -l filename duplicate addresses and option and the -i demonstrate unexpected results. ip_address option need to be specified. Command use restricted (see Commands and user authority on page 6).
Apply BOFM configuration to specified BladeCenter units, bays, and ports (verbose)
Copies a configuration file from a TFTP server to the specified management module, which then configures BladeCenter units, blade servers, and I/O modules, a process which might take several minutes. The detailed information is shown after the update is complete.
bofm -l filename -i ip_address -v where: v filename is the name of the configuration file. v ip_address is the IP address of TFTP server where the configuration file is located. Note: Both the -l filename option and the -i ip_address option need to be specified. Command use restricted (see Commands and user authority on page 6).
Example: To apply a new BOFM configuration file to a set of BladeCenter units and view details of the procedure, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
bofm -i 9.148.8.2 -l apply.csv -v
56
system:mm[1]> bofm -i 9.148.8.2 -l apply.csv -v TFTP file upload successful. Starting to apply new BOFM configuration on MM Percent complete: 100% Status: Confirmed configuration change. Percent complete: 100% Status: Configuration applied. Applying new BOFM configuration on MM - Completed. system:mm[1]>
57
boot command
This command resets blade servers with several different restart options.
Table 10. boot command Function Reset blade server What it does Command Valid targets
Performs an immediate reset and boot -T system:blade[x] restart of the specified blade server. Command use restricted where x is the blade This command will start a blade (see Commands and user server bay number. server that is turned off. authority on page 6). Resets the specified blade server, causing it to open a command console with an SOL session when it restarts. This command will start a blade server that is turned off. boot -c -T system:blade[x]
Reset blade server to command console
Command use restricted where x is the blade (see Commands and user server bay number. authority on page 6).
Power cycle
Cycles power for the specified blade server. If the blade server is off, it will turn on. If the blade server is on, it will turn off and then turn on.
boot -p powercycle
-T system:blade[x]
Reset blade server
Performs an immediate reset and boot -p reset -T system:blade[x] restart of the specified blade server. Command use restricted where x is the blade This command will start a blade (see Commands and user server bay number. server that is turned off. authority on page 6).
Example: To boot the blade server in blade bay 3, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
boot -T system:blade[3]
The following example shows the information that is returned:

system:mm[1]> OK system:mm[1]> boot -T system:blade[3]
58
bootmode command (advanced management module only)

This command sets and displays the boot mode settings for blade servers installed in the BladeCenter unit that support this feature.
Table 11. bootmode command Function Display blade server boot mode What it does Displays the boot mode settings of the specified blade server. Note: This command will execute only on blade servers that support the bootmode feature. Sets the copy of firmware that the specified blade server will use to boot: v Temporary: booting from the temporary copy is recommended since it typically contains the latest enhancements and fixes. v Permanent: booting from the permanent copy should be used only when booting from the temporary copy is no longer possible. Changes to the boot mode setting take effect after the next restart of the blade server. Note: This command will execute only on blade servers that support the bootmode feature. Command bootmode Valid targets -T system:blade[x] where x is the blade server bay number. bootmode -p mode where mode is: v temp for temporary firmware copy. v perm for permanent firmware copy. Command use restricted (see Commands and user authority on page 6). -T system:blade[x] where x is the blade server bay number.
Set blade server boot mode
Example: To view the boot mode of the blade server in bay 2, while this blade server is set as the persistent command environment, at the system:blade[2]> prompt, type
bootmode
To set the boot mode of the blade server in bay 2 to permanent, while this blade server is set as the persistent command environment, at the system:blade[2]> prompt, type
bootmode -p perm
system:blade[2]> bootmode active: temporary pending: Invalid boot mode type system:blade[2]> bootmode -p perm Set the blade boot mode to permanent succeeded. The setting will become active after the next reboot of the blade. system:blade[2]> bootmode active: temporary pending: permanent system:blade[2]>
59
bootseq command (advanced management module only)

This command sets and displays the boot sequence settings for blade servers installed in the BladeCenter unit.
Table 12. bootseq command Function Display blade server boot sequence What it does Displays the boot sequence of the specified blade server. Possible return 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 2 v hd3 (hard disk drive 3) v hd4 (hard disk drive 4) v cd (CD-ROM drive) v usb (media tray) Command bootseq Valid targets -T system:blade[x] where x is the blade server bay number.
60
Table 12. bootseq command (continued) Function Set boot sequence for blade server What it does Sets the boot sequence of the specified blade server. Command bootseq devicelist Valid targets -T system:blade[x]
where devicelist has one where x is the blade or more of the following server bay number. boot devices specified, in order of preference: v floppy for the diskette drive (non-POWER-based blade servers only) v usbdisk for a USB device (not supported by all blade servers) v iscsi for iSCSI v iscsicrt for iSCSI critical v nw for network - PXE v nodev for no device v hd0 for hard disk drive 0 v hd1 for hard disk drive 1 v hd2 for hard disk drive 2 v hd3 for hard disk drive 3 v hd4 for hard disk drive 4 v cd for the CD-ROM drive v usb for the media tray (non-POWER-based blade servers installed in BladeCenter T units only) A boot sequence of up to four boot devices can be specified. If less than four devices are specified, the remaining items in the sequence are set to nodev. Command use restricted (see Commands and user authority on page 6).
61
Table 12. bootseq command (continued) Function Set boot sequence for all blade servers What it does Sets the same boot sequence for all blade servers installed in the BladeCenter unit. Command bootseq -all devicelist Valid targets -T system:blade[x]
where devicelist has one where x is the blade or more of the following server bay number. boot devices specified, in order of preference: v floppy for the diskette drive (non-POWER-based blade servers only) v usbdisk for a USB device (not supported by all blade servers) v iscsi for iSCSI v iscsicrt for iSCSI critical v nw for network v nodev for no device v hd0 for hard disk drive 0 v hd1 for hard disk drive 1 v hd2 for hard disk drive 2 v hd3 for hard disk drive 3 v hd4 for hard disk drive 4 v cd for the CD-ROM drive v usb for the media tray (non-POWER-based blade servers installed in BladeCenter T units only) A boot sequence of up to four boot devices can be specified. If less than four devices are specified, the remaining items in the sequence are set to nodev. Command use restricted (see Commands and user authority on page 6).
62
Example: To set a boot sequence of diskette drive, CD-ROM drive, and hard disk drive 0 for the blade server in blade bay 3, while the blade server in blade bay 3 is set as the persistent command environment, at the system:blade[3]> prompt, type
bootseq floppy cd hd0
To display the boot sequence for the blade server in blade bay 3, while the blade server in blade bay 3 is set as the persistent command environment, at the system:blade[3]> prompt, type
bootseq
system:blade[3]> OK system:blade[3]> floppy cd hd0 nodev system:blade[3]> bootseq floppy cd hd0 bootseq
63
cin command (advanced management module only)

This command can be used to view and configure the chassis internal network for up to 14 supported chassis internal network (CIN) configurations, globally, or for specified entries. You can define a CIN by creating a pool of VLAN (virtual local area network) ID/IP address pairs, each of which is a CIN entry.
Table 13. cin command Function Display CIN configuration table What it does Command Valid targets -T system
Displays the configuration table for cin the chassis internal network. Possible return values are: v Global CIN enabled or disabled status v CIN index VLAN ID IP address index entry enabled or disabled status Sets the global state of CIN to enabled or disabled. cin -global -en state where state is: v on v off Command use restricted (see Commands and user authority on page 6).
Set global CIN state
-T system
Clear all CIN configuration entries
Deletes all CIN configuration entries. cin all -clear Command use restricted (see Commands and user authority on page 6).
-T system
Turn all index entries on or off
Turns all CIN index entries on or off.
cin all -en state where state is: v on v off Command use restricted (see Commands and user authority on page 6).
-T system
Delete CIN configuration entry
Deletes the specified CIN configuration entry.
cin -entry_index -clear where: entry_index is a number between 1 and 14 (inclusive). Command use restricted (see Commands and user authority on page 6).
-T system
64
Table 13. cin command (continued) Function Set CIN configuration entry to enable or disable What it does Enables or disables a CIN configuration entry. If you enable or disable a non-existent entry, the action is ignored and no error message is returned. Command cin -entry_index -en state where: v entry_index is a number between 1 and 14, and v state is: on off Command use restricted (see Commands and user authority on page 6). Create a CIN configuration entry Creates a CIN index entry. cin -entry_index -id vlan_id -ip ip_address -T system Valid targets -T system
If the CIN index is currently empty, both -id and -ip must be specified. where: Note: The VLAN ID must be v entry_index is a number different from that of the blade server between 1 and 14, management module. v vlan_id is a VLAN ID number between 3 and 4094 (inclusive), v ip_address is a valid IP address. Command use restricted (see Commands and user authority on page 6). Specify valid IP address for CIN index entry Specifies the IP address of the CIN index entry. The CIN IP address must be a valid IP address. An error is displayed if the IP address is invalid. Note: v If the index is not empty, the IP address can be specified separately. v CIN entries cannot have matching IP addresses unless they are 0.0.0.0. and have different VLAN IDs. v The IP address cannot be multi-cast and cannot match the IP address of the management module. cin -entry_index -ip ip_address where: v entry_index is a number between 1 and 14 v ip_address is a valid IP address. You can overwrite parameters of an existing definition; for example, cin -1 -ip 0.0.0.0 overwrites the current CIN IP address of the first cin entry. If the entry does not exist, an error is returned. Command use restricted (see Commands and user authority on page 6). -T system
65
Table 13. cin command (continued) Function Specify VLAN ID for CIN entry What it does Set the VLAN ID for the specified CIN 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 blade management module. Command cin -entry_index -id vlan_id where: v entry_index is a number between 1 and 14 v vlan_id is a number between 3 and 4094 (inclusive). Command use restricted (see Commands and user authority on page 6). Valid targets -T system
Example: To view chassis internal network information for the management module, while this management module is set at the persistent command environment, at the system> prompt, type
cin
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 3 not used Index 4 not used Index 5 not used Index 6 not used Index 7 not used Index 8 not used Index 9 not used Index 10 not used
66
Index 11 not used Index 12 -id 123 -ip 23.1.1.1 -en on Index 13 not used Index 14 not used system>
67
cinstatus command (advanced management module only)

This command displays a table listing the VLAN ID, the IP address, the MAC address, and the status of each chassis internal network (CIN) connection.
Table 14. cinstatus command Function Display entries of the CIN status table What it does Reads entries of the CIN status table, five at a time. Each entry of the table returns: v CIN VLAN ID v CIN IP address v CIN MAC address v CIN status text Display status of first five CIN entries Display entire CIN status table Displays the first five entries of the CIN status table. Displays all the entries in the CIN status table. cinstatus -f cinstatus -a -T system -T system Command cinstatus Valid targets -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 as the persistent environment, at the system> prompt, type
cinstatus
The following example shows the information that is returned from this command
system> cinstatus Note: * next to IP address indicates a learned entry VLAN ---4094 4094 4 4093 4094 IP Address ---------------0.0.0.1 0.0.0.2 0.0.0.0 0.0.0.1 0.0.0.0 MAC Address Status ------------------ -------------------Not Operational Not Operational Operational Not Operational Operational
1. 2. 3. 4. 5.
Last entry reached system>
68
clear command (management modules other than the advanced management module)
This command restores the primary management module configuration or an I/O (switch) module configuration to the default settings. Note: The clear command operates differently for the advanced management module and for other management module types. The following command description is for management modules other than the advanced management module. See clear command (advanced management module only) on page 71 for command syntax for the advanced management module. The clear command must always include the -config option.
Table 15. clear command (management modules other than the advanced management module) Function What it does Command clear -config Valid targets -T system:mm[x]
Restore default Restores the default configuration configuration of primary of the primary management management module module; then, resets the management module. No results are returned from this command because it resets the management module. When you restore the management-module configuration, the Ethernet configuration method is set to a value of dthens. After the management module resets, this causes the management module to try dhcp configuration and then default to the static IP configuration, which might cause the management module to remain offline for longer than normal. See ifconfig command (management modules other than the advanced management module) on page 113 for information. Restore default configuration of I/O (switch) module Restores the configuration of the specified I/O (switch) module to the default settings.
clear -config
-T system:switch[x]
Command use restricted where x is the I/O (see Commands and user (switch) module bay authority on page 6). number.
69
Example: To restore the primary management-module configuration to default settings, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
clear -config
No results are returned from this command. After the management module resets, you will need to start a new command-line session.
70
clear command (advanced management module only)

This command restores the primary management module configuration or an I/O (switch) module configuration to the default settings. Note: The clear command operates differently for the advanced management module and for other management module types. The following command description is for the advanced management module. See clear command (management modules other than the advanced management module) on page 69 for command syntax for management modules other than the advanced management module. The command must always include the -cnfg or -config option.
Table 16. clear command (advanced management module only) Function Restore default configuration of primary management module and keep logs What it does Restores the default configuration of the primary management module, retaining log information; then, resets the management module. No results are returned from this command because it resets the management module. When you restore the management-module configuration, the Ethernet configuration method is set to a value of dthens. After the management module resets, this causes the management module to try dhcp configuration and then default to the static IP configuration, which might cause the management module to remain offline for longer than normal. See the ifconfig command (advanced management module only) on page 118 for information. Restore default configuration of I/O (switch) module Restores the configuration of the specified I/O (switch) module to the default settings. clear -cnfg -T system:switch[x] Command clear -cnfg Valid targets -T system:mm[x]
Command use restricted where x is the I/O (see Commands and user (switch) module bay authority on page 6). number.
Example: To restore the primary management-module configuration to default settings and retain log information, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
clear -cnfg
No results are returned from this command. After the management module resets, you will need to start a new command-line session.
71
clearlog command
This command clears the management-module event log.
Table 17. clearlog (clear management-module event log) command Function Clear management-module event log What it does Clears the management-module event log and displays a message confirming that the event log was cleared. Command clearlog Valid targets -T system:mm[x]
Example: To clear the management-module event log, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
clearlog

system:mm[1]> clearlog OK system:mm[1]>
72
clock command (advanced management module only)

This command configures and displays the advanced management-module clock settings.
Table 18. clock command Function Display advanced management module clock information What it does Displays the following information for the advanced management module clock: v current date and time v GMT (Greenwich-Mean Time) offset v daylight-savings time setting Sets the date for the advanced management module clock. Command clock Valid targets -T system:mm[x] where x is the primary management-module bay number.
Set advanced management module date
clock -d date where date is the current calendar date in mm/dd/yyyy format. The month and day can be input as single digits. The year must be 4-digits between 2000 and 2089, inclusive. Command use restricted (see Commands and user authority on page 6).
Set advanced management module time
Sets the time for the advanced management module clock.
clock -t time where time is the current time in 24-hour hh:mm:ss format. The hours, minutes, and seconds can all be input as single digits. Command use restricted (see Commands and user authority on page 6).
73
Table 18. clock command (continued) Function Set advanced management module clock GMT offset What it does Sets the time for the advanced management module clock. Command clock -g offset Valid targets -T system:mm[x]
where offset is a value where x is the primary between +12 and -12, in management-module hours and minutes. bay number. Positive offsets are entered using the form: GMT+hh:mm, +hh:mm, +hh, hh:mm, or hh; where, the hours and minutes can be input as single digits. Negative offsets are entered using the form: GMT-hh:mm, -hh:mm, or -hh; where, the hours and minutes can be input as single digits. Valid offsets are: v GMT+0:00 v GMT+1:00 v GMT+2:00 v GMT+3:00 v GMT+3:30 v GMT+4:00 v GMT+4:30 v GMT+5:00 v GMT+5:30 v GMT+6:00 v GMT+7:00 v GMT+8:00 v GMT+9:00 v GMT+9:30 v GMT+10:00 v GMT+11:00 v GMT+12:00 v GMT-12:00 v GMT-11:00 v GMT-10:00 v GMT-9:00 v GMT-8:00 v GMT-7:00 v GMT-6:00 v GMT-5:00 v GMT-4:00 v GMT-3:30 v GMT-3:00 v GMT-2:00 v GMT-1:00 (continued on next page)
74
Table 18. clock command (continued) Function Set advanced management module clock GMT offset (continued) What it does Command For some time zones that use daylight-savings time (GMT +10, +2, -5, -6, -7, -8, -9), a special value for the -dst option must be specified to identify the correct daylight-savings time scheme to use in that time zone. Command use restricted (see Commands and user authority on page 6). Set advanced management module clock daylight-savings time mode Sets the daylight-savings time mode clock -dst dst_mode for the advanced management where dst_mode is one of module clock. the following: v off v on v 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 to GMT-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 is not observed in the following 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, and GMT-10:00. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number. Valid targets
75
Example: To set the management-module for operation in the US Eastern time zone in compliance with new daylight-savings time rules, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
clock -g +5 -dst uc
To display the clock information for the primary management module, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
clock
system:mm[1]> clock -g +5 -dst uc OK system:mm[1]> clock 10/17/2006 02:27:11 GMT+5:00 dst uc system:mm[1]>
76
config command (advanced management module only)

This command sets and displays the name of the advanced management module or blade server and the location and contact name for the advanced management module.
Table 19. config command Function Display name of blade server What it does Displays the name of the specified blade server. Command config Valid targets -T system:blade[x] where x is the blade server bay number. Display name of management module Displays the name, location, and contact name of the primary management module. config -T system:mm[x] where x is the primary management-module bay number. config -name name where name is up to 15 characters in length. Blade server names cannot contain angle brackets (< and >), and advanced management module names can only contain alphanumeric characters, hyphens, pound signs, underscores, and periods. Command use restricted (see Commands and user authority on page 6). Set location of management module Sets the location of the primary advanced management module. config -loc location where location is up to 47 characters in length and contained within double-quotes. Advanced management module locations can contain any character other than < and >. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] -T system:blade[x] where x is the primary management-module or a blade server bay number.
Set name of Sets the name of the primary management module or management module or specified blade server blade server.
77
Table 19. config command (continued) Function Set contact name for advanced management module What it does Sets the contact name for the primary advanced management module. Command config -contact contact_name where contact_name is up to 47 characters in length and contained within double-quotes. Advanced management module contact names can contain any character other than < and >. Command use restricted (see Commands and user authority on page 6). Valid targets -T system:mm[x] where x is the primary management-module bay number.
Example: To set the management module name to IBM_lab, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
config -name IBM_lab
To display the management module name, location, and contact name, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
config
system:mm[1]> config -name IBM_lab OK system:mm[1]> config -name IBM_lab -contact John_Doe -loc Main_Lab system:mm[1]>
78
console command
This command sets up a serial over LAN connection to the command console of a blade server. To end an SOL session, press Esc followed by an open parenthesis: Esc (
Table 20. console command Function Create SOL session with blade server What it does Creates an SOL connection to the specified blade server. Command console Valid targets -T system:blade[x]
Command use restricted where x is the blade (see Commands and user server bay number. authority on page 6). Create override SOL session with blade server Creates an SOL connection to the specified blade server, with the override option enabled. This enables you to end an existing SOL session to that blade server and start a new one. console -o -T system:blade[x]
Example: To start an SOL connection to the blade server in blade bay 14, while this blade server is set as the persistent command environment, at the system:mm[x]> prompt, type
console -T system:blade[14]
79
dhcpinfo command
This command displays the IP configuration that is assigned to the primary management module by the DHCP server. Note: The dhcpinfo command does not apply to eth1, which always uses a static IP configuration.
Table 21. dhcpinfo command Function Display Ethernet channel 0 DHCP configuration What it does Command Valid targets -T system:mm[x] where x is the primary management-module bay number.
If the IP configuration for eth0 is dhcpinfo -eth0 assigned by a DHCP server, the configuration that is assigned by the DHCP server and DHCP server information is displayed. If the IP configuration for eth0 is not assigned by a DHCP server, an error message is displayed. Possible configuration values returned are: v -server dhcp_ip_address v -n hostname v -i ip_address v -g gateway_address v -s subnet_mask v -d domainname v -dns1 primary _dns_ip_address v -dns2 secondary _dns_ip_address v -dns3 tertiary _dns_ip_1address
Example: To display the DHCP server assigned network settings for Ethernet channel 0, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
dhcpinfo -eth0

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.0 system:mm[1]>
80
displaylog command
This command displays management-module event log entries.
Table 22. displaylog (display management-module event log) command Function Display management-module event log entries What it does Command Valid targets -T system:mm[x] where x is the primary management-module bay number.
Displays five entries from the displaylog management-module event log. The first time the command is executed, the five most recent log entries are displayed. Each subsequent time the command is issued, the next five entries in the log display. Resets the counter and displays the displaylog -f first five most recent entries in the management-module event log.
Display management-module event log entries (reset counter) Display management-module Display the state of the -lse option Display all management-module event log entries (advanced management module only) Display all event log filters (advanced management module only) Display event log entries filtered by date (advanced management module only)
Displays the state of the -lse option. displaylog -lse state where -T system:mm[x] state is enabled or disabled. Displays all entries in the management module event log. displaylog -a -T system:mm[x] where x is the primary management-module bay number. Displays all filters that can be used to control management module event log output. displaylog -filters -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number.
Displays management module displaylog -date date_filter event log information that meets the where date_filter is a pipe specified date filter criteria. ( | ) separated list of date Note: filters in mm/dd/yy format. 1. This command displays the first five most recent entries in the management-module event log that meet the specified filter criteria. Adding the -a option to the command displays all entries that meet the specified filter criteria. 2. If the filter criteria entered does not match the criteria previously specified, this resets the counter and displays the first five most recent log entries that match the specified filter criteria. 3. The index number displayed for each filtered log entry might not match the index number shown for the same log entry displayed in an unfiltered list.
81
Table 22. displaylog (display management-module event log) command (continued) Function Display event log entries filtered by severity level (advanced management module only) What it does Command Valid targets -T system:mm[x] where x is the primary management-module bay number.
Displays management module displaylog -sev event log information that meets the severity_filter specified severity level filter criteria. where severity_filter is a Note: pipe ( | ) separated list of 1. This command displays the first severity filters: five most recent entries in the v I (information) management-module event log v E (error) that meet the specified filter v W (warning) criteria. Adding the -a option to the command displays all entries that meet the specified filter criteria. 2. If the filter criteria entered does not match the criteria previously specified, this resets the counter and displays the first five most recent log entries that match the specified filter criteria. 3. The index number displayed for each filtered log entry might not match the index number shown for the same log entry displayed in an unfiltered list.
Display event log entries filtered by source (advanced management module only)
Displays management module displaylog -src event log information that meets the source_filter specified source filter criteria. where source_filter is a Note: pipe ( | ) separated list of 1. This command displays the first source filters. A range of five most recent entries in the blade servers is specified management-module event log using a hyphen ( - ), such that meet the specified filter as: Blade_01-08. criteria. Adding the -a option to the command displays all entries that meet the specified filter criteria. 2. If the filter criteria entered does not match the criteria previously specified, this resets the counter and displays the first five most recent log entries that match the specified filter criteria. 3. The index number displayed for each filtered log entry might not match the index number shown for the same log entry displayed in an unfiltered list.
Enable monitoring of event log state (advanced management module only)
Enables monitoring of the event log state and generates an event when the log becomes 75% or 100% full. Note: The displaylog -lse command must be run exclusive of other log-reading command options (-f, -a, -filters, -date, -sev, - src, -i, and -l).
displaylog -lse enabled
-T system:mm[x]
82
Table 22. displaylog (display management-module event log) command (continued) Function Disable monitoring of event log state (advanced management module only) What it does Disables monitoring of the event log state. No events are generated when the log becomes 75% or 100% full. Note: The displaylog -lse command must be run exclusive of other log-reading command options (-f, -a, -filters, -date, -sev, - src, -i, and -l). Command displaylog -lse disabled Valid targets -T system:mm[x]
Display the monitoring of the event log state
Displays the monitoring of the event displaylog -lse log state
Save event log to TFTP server (advanced management module only)
Saves the event log with the specified filename to the specified TFTP server. Note: The -i and -l command options must be run together and exclusive of other command options.
displaylog -i ip_address -l filename where: v ip_address is the IP address of the TFTP server where the event log is being saved. v filename is the name of the event log file.
Example: To display the first five primary management-module event log entries, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
displaylog -f
To display the next five management-module event log entries, type (a second time)
displaylog
To display the next five management-module event log entries, type

displaylog
The following example shows the information that is returned from these three commands:
system:mm[1]> displaylog -f 1 I SERVPROC 10/27/06 19:45:57 Remote Login Successful. Login ID:USERID CLI authenticated from 192.168.70.231 (Telnet). 2 E SERVPROC 10/27/06 19:42:58 Failure reading I2C device. Check devices on bus 4. 3 E SERVPROC 10/27/06 19:42:58 Failure reading I2C device. Check devices on bus 3. 4 E SERVPROC 10/27/06 19:42:58 Failure reading I2C device. Check devices on bus 2. 5 I SERVPROC 10/27/06 19:41:54 Remote Login Successful. Login ID:USERID from WEB browser at IP@=192.168.70.231 system:mm[1]> displaylog 6 E SERVPROC 10/27/06 19:41:53 Blower 2 Fault Multiple blower failures 7 E SERVPROC 10/27/06 19:41:53 Blower 1 Fault Single blower failure 8 I SERVPROC 10/27/06 19:41:48 Ethernet[1]
83
Link Established at 100Mb, Full Duplex. 9 I SERVPROC 10/27/06 19:41:48 configured to do 100Mb/Full Duplex. 10 I SERVPROC 10/27/06 19:41:48 MAC Address currently being used: 0x00-09-6B-CA-0C-81 system:mm[1]> displaylog 11 I SERVPROC 10/27/06 19:41:48 Link Established at 100Mb, Full Duplex. 12 I SERVPROC 10/27/06 19:41:48 configured to do Auto Speed/Auto Duplex. 13 I SERVPROC 10/27/06 19:41:48 MAC Address currently being used: 0x00-09-6B-CA-0C-80 14 I SERVPROC 10/27/06 19:41:48 Module Network Initialization Complete. 15 I SERVPROC 10/27/06 19:41:46 IP-Cfg:HstName=MM00096BCA0C81, IP@=192.168.70.126 ,GW@=0.0.0.0, system:mm[1]>
Ethernet[1] Ethernet[1] Ethernet[0] Ethernet[0] Ethernet[0] Management ENET[1] NetMsk=255.255.255.0
The following example shows the information that is returned if the displaylog command is run after the event log is cleared:
system:mm[1]> displaylog -f 1 I SERVPROC 10/27/06 log cleared. (There are no more entries in the event log.) system:mm[1]> 19:53:02 System
84
displaysd command (advanced management module only)

This command captures and displays service information. Service information for the management modules includes BladeCenter VPD, the management-module event log, connection status, and self-test results. If multiple user interface sessions issue the displaysd command, the commands will be processed in the order that they are received. Some types of service information are displayed for only the primary management module.
Table 23. displaysd command Function Capture and display service information What it does Capture and display service information on screen from the primary or standby management module. Command displaysd Valid targets -T system:mm[x] where x is the primary or standby management-module bay number. displaysd -mmstat -T system:mm[x] where x is the primary management-module bay number. displaysd -save filename -i -T system:mm[x] ipaddress where x is the primary where: management-module v filename is the location bay number. where service information will be saved. The filename should use a .tgz extension to allow support personnel to identify the file. v ipaddress is the IP address of the TFTP server. displaysd -src list -T system:blade[x] where x is the blade serverbay number.
Display management module connection and self-test status
Displays connection status and latest self-test results for the primary management module.
Save service information to TFTP server
Saves service information from primary management module with the specified filename to the specified TFTP server. Note: The -save and -i command options must be run together.
Display all blade server SRC records
Displays a list of the most recent (up to 32) SRCs for the specified blade server. Note: SRC information is available for only those blade servers that support this feature. Displays a specific SRC, based on the specified record number, for the specified blade server. Note: SRC information is available for only those blade servers that support this feature.
Display specific blade server SRC record
displaysd -src index where index is the SRC record number to display, between 1 and 32.
-T system:blade[x] where x is the blade serverbay number.
85
Example: To capture and display service information from the management module in bay 1, while the chassis is set as the persistent command environment, at the system> prompt, type
displaysd -T system:mm[1]
To capture service information from the management module in bay 1 and save it to a file named sdc.tgz on a TFTP server with a IP address of 9.67.22.176, while the chassis is set as the persistent command environment, at the system> prompt, type
displaysd -T system:mm[1] -save sdc.tgz -i 9.67.22.176
system> displaysd -T system:mm[1] SPAPP Capture Available Time: 10/04/2005 21:47:43 UUID: Not Available system> displaysd -T system:mm[1] -save sdc.tgz -i 9.67.22.176 OK system>
Note: If a large amount of service information is available, display could exceed the capacity of your command-prompt window, resulting in loss of information displayed at the start of the data set. If this happens, you will need to clear the management-module event log to reduce the amount of information being captured.
86
dns command
This command configures and displays the management-module DNS settings.
Table 24. dns command Function Display DNS configuration of management module What it does Displays the current DNS configuration of the management module. Possible return values are: v enabled v disabled v -i1 first ip_address v -i2 second ip_address v -i3 third ip_address Enables the management-module DNS configuration. Command dns Valid targets -T system:mm[x] where x is the primary management-module bay number.
DNS - enable
dns -on
-T system:mm[x]
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. DNS - disable Disables the management-module DNS configuration. dns -off -T system:mm[x]
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. DNS first IP address set Checks syntax and sets the first IP address. dns -i1 ip_address where ip_address is the first IP address. Command use restricted (see Commands and user authority on page 6). DNS second IP address Checks syntax and sets the second dns -i2 ip_address - set IP address. where ip_address is the second IP address. Command use restricted (see Commands and user authority on page 6). DNS third IP address set Checks syntax and sets the third IP dns -i3 ip_address address. where ip_address is the third IP address. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number.
87
Example: To set the first IP address of the management-module DNS server to 192.168.70.29 and enable DNS on the primary management module, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
dns -i1 192.168.70.29 -on
To display the DNS status of the primary management module, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
dns
system:mm[1]> dns -i1 192.168.70.29 -on Changes to the network settings will take effect after the next reset of the MM. system:mm[1]> dns Enabled -i1 192.168.70.29 -i2 0.0.0.0 -i3 0.0.0.0 system:mm[1]>
88
env (environment) command

This command sets the persistent environment for commands that are entered during the remainder of the current session. The persistent command environment is indicated by the command prompt. When you start the command-line interface, the persistent command environment is the BladeCenter unit, denoted as system by the command prompt. You can target a single command to an environment other than the one that is set as the default by adding a -T option to the command that includes a valid target destination (see Selecting the command target on page 4 for information). Target environments can be specified using the full path name, or using a partial path name based on the 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 are supported as targets by the env command.
Table 25. Components and command paths Component BladeCenter unit Management module Blade server Blade server integrated system management processor (BMC or service processor) Blade server I/O-expansion card Target path system system:mm[x] system:blade[x] system:blade[x]:sp system:blade[x]:exp[y] (advanced management modules only) system:blade[x]:dtr[y] (management modules other than the advanced management module) Blade server management card (advanced management module only) Blade server microprocessor Blade server storage expansion unit system:blade[x]:mgmtcrd system:blade[x]:cpu[y] system:blade[x]:be[y] (advanced management modules only) system:blade[x]:be (management modules other than the advanced management module) Blade server storage module (advanced management modules only) BladeCenter S unit only Blade server high-speed expansion card (advanced management module only) Blade server mezzanine for double-width form factor (advanced management module only) Blade server concurrent KVM feature card (advanced management module only) I/O module Power module Blower Media tray system:storage[x] system:blade[x]:hsec system:blade[x]:sb system:blade[x]:ckvm system:switch[x] system:power[x] system:blower[x] system:mt[x] (advanced management modules only) system:mt (management modules other than the advanced management module)
89
Table 25. Components and command paths (continued) Component Alarm panel (BladeCenter HT only) Multiplexer expansion module (BladeCenter HT only) Network clock module (BladeCenter HT only) Table 26. env (environment) command Function What it does Command env env -T system Valid targets The env command can be directed to any installed device. Target path system:tap system:mux[x] system:ncc[x]
Set BladeCenter unit as Sets the BladeCenter unit as the command target persistent target for commands during the current session. This is the persistent command environment you are in at the beginning of each command-line interface session, indicated by the system> prompt. Set management module as command target Sets the management module as the persistent target for commands during the current session.
env -T system:mm[x]
The env command can be directed to any where x is the bay (1 or 2) installed device, in this that identifies the case management module. -T system:mm[x] where x is the management-module bay number.
Set blade server as command target
Sets the specified blade server as the persistent target for commands during the current session.
env -T system:blade[x] where x is the blade bay that identifies the blade server. A blade server that occupies more than one blade bay is identified by the lowest bay number that it occupies.
The env command can be directed to any installed device, in this case -T system:blade[x] where x is the blade bay that identifies the blade server.
90
Table 26. env (environment) command (continued) Function Set blade server sub-component as command target What it does Sets the specified sub-component on the specified blade server as the persistent target for commands during the current session. Valid sub-components are: v Integrated system management processor (BMC or service processor) v I/O-expansion card v Microprocessor v Storage expansion unit v High-speed expansion card (advanced management module only) v Mezzanine assembly for double-width form factor blade servers (advanced management module only) Command env -T system:blade[x]:comp where x is the blade bay that identifies the blade server on which the sub-component is installed. A blade server that occupies more than one blade bay is identified by the lowest bay number that it occupies. where comp is the sub-component: v sp for BMC or service processor v exp[x] for I/O-expansion card (where x identifies the expansion card) (advanced management module only) v dtr[x] for I/O-expansion card (where x identifies the expansion card) (management modules other than the advanced management module) v cpu[x] for microprocessor (where x identifies the microprocessor) v be[x] for storage expansion unit (where x identifies the expansion unit) v ckvm for concurrent KVM feature card (advanced management module only) v hsec for high-speed expansion card (advanced management module only) v mgmtcrd for management card (advanced management module only) v sb for mezzanine assembly for double-width form factor blade servers (advanced management module only) Valid targets The env command can be directed to any installed device, in this case -T system:blade[x]:sp where x is the blade bay that identifies the blade server on which the integrated system management processor is installed.
91
Table 26. env (environment) command (continued) Function Set I/O (switch) module as command target What it does Sets the specified I/O (switch) module as the persistent target for commands during the current session. Command env -T system:switch[x] where x is the I/O (switch) module bay where the I/O (switch) module is installed. Valid targets The env command can be directed to any installed device, in this case -T system:switch[x] where x is the I/O (switch) module bay where the I/O (switch) module is installed. Set power module as command target Sets the specified power module as env -T system:power[x] the persistent target for commands where x is the power during the current session. module bay where the power module is installed. The env command can be directed to any installed device, in this case -T system:power[x] where x is the power module bay where the power module is installed. Set blower as command Sets the specified blower as the target persistent target for commands during the current session. env -T system:blower[x] where x is the blower bay where the blower is installed. The env command can be directed to any installed device, in this case -T system:blower[x] where x is the blower bay where the blower is installed. Set media tray as command target Sets the media tray as the persistent target for commands during the current session. For advanced management modules: env -T system:mt[x] where x is the media-tray bay where the media tray is installed (advanced management modules only). For management modules other than the advanced management module: env -T system:mt The env command can be directed to any installed device, in this case -T system:mt[x] (for advanced management modules) -T system:mt (management modules other than the advanced management module) where x is the media tray bay where the media tray is installed (advanced management modules only). The env command can be directed to any installed device, in this case -T system:tap
Set alarm panel as Sets the alarm panel as the command target persistent target for commands (Advanced management during the current session. modules and BladeCenter HT units only)
env -T system:tap
92
Table 26. env (environment) command (continued) Function Set multiplexer expansion module as command target (Advanced management modules and BladeCenter HT units only) What it does Sets the multiplexer expansion module as the persistent target for commands during the current session. Command env -T system:mux[x] Valid targets
The env command can be directed to any where x is the multiplexer installed device, in this expansion module number. case -T system:mux[x] where x is the multiplexer expansion module number.
Set network clock Sets the network clock module as module as command the persistent target for commands target (Advanced during the current session. management modules and BladeCenter HT units only)
env -T system:ncc[x] where x is the network clock module number.
The env command can be directed to any installed device, in this case -T system:blower[x] where x is the network clock module number.
Example: To set the persistent target of commands to the service processor on the blade server in blade bay 5, while the BladeCenter unit is set as the default command target, at the system> prompt, type
env -T system:blade[5]:sp

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

system> env -T blade[5]:sp OK system:blade[5]:sp>
To issue the reset command on the blade server in blade bay 5, while the management module is set as the default command target, at the system:mm[x]> prompt, type
reset -T system:blade[5]
93
exit command
This command exits the command-line interface, terminating the current session.
Table 27. exit command Function Exit What it does Terminates the current command-line interface session. Command exit Valid targets Any installed device.
Example: To terminate the current command-line interface session, type

exit
94
files command (advanced management module only)

This command manages files uploaded to the advanced management module.
Table 28. files command Function What it does Command files Valid targets -T system:mm[x] where x is the primary management-module bay number. files -d filename where filename is a valid, existing filename of less than 256 characters in length. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number.
Display file list and free Displays a list of files and space space remaining in the advanced management module file system.
Delete file
Deletes a file from the advanced management module file system. Note: This command can only be used to delete files: it will not delete directories.
Example: To view the files and remaining space in the management module file system, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
files
To delete the file tftproot/tftp_file.pkt from the management module file system, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
files -d tftproot/tftp_file.pkt
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.pkt 0 Sun Oct 01 07:57:19 2006 tftproot/.Do_not_delete_this_directory 0 Tue Dec 15 11:07:19 2009 test 0 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.pub 5652 Fri May 12 00:56:36 2006 asm.cfg Total space: 73108480 bytes Used: 24576 bytes Available: 73083904 bytes system:mm[1]> files -d tftproot/tftp_file.pkt OK system:mm[1]>
95
fuelg command (management modules other than the advanced management module)
This command displays power domain information, listing the power modules that are installed in the BladeCenter unit and information about how the power in each domain is used. This command also configures the power domain policies for oversubscription and quiet mode. Note: The fuelg command operates differently for the advanced management module and for other management module types. The following command description is for management modules other than the advanced management module. See fuelg command (advanced management module only) on page 99 for command syntax for the advanced management module.
Table 29. fuelg command (management modules other than the advanced management module) Function Display power domain status overview Display detailed power domain status What it does Displays health status and total power usage information for all power domains Displays detailed status and usage information for the specified power domains Command fuelg Valid targets -T system
fuelg domain where domain is pd1 for power domain 1 and pd2 for power domain 2. If no domain is specified, a status overview for all power domains displays. fuelg domain -os policy where: v domain is pd1 for power domain 1 and pd2 for power domain 2. If no domain is specified, the policy is applied to all power domains. v policy of: none (default) allows loss of redundancy. nonrecov prevents components from turning on that will cause loss of power redundancy. recov power throttles components to maintain power redundancy and prevents components from turning on that will cause loss of power redundancy. Command use restricted (see Commands and user authority on page 6).
-T system
Set power domain redundancy loss policy
Sets how the BladeCenter unit responds to a condition that could cause a loss of redundant power.
-T system
96
Table 29. fuelg command (management modules other than the advanced management module) (continued) Function What it does Command fuelg -qm setting where the quiet-mode setting of: v off (default) allows blowers to increase speed to provide additional cooling. v on keeps blowers at a fixed speed and power throttles BladeCenter components to reduce power consumption (only for BladeCenter components that support power throttling). Command use restricted (see Commands and user authority on page 6). Valid targets -T system
Thermal event response Sets how the BladeCenter unit (quiet mode) blowers respond to thermal events.
Example: To view a power domain status overview, while the BladeCenter unit is set as the persistent command environment, at the system> prompt, type
fuelg
To reduce fan noise during thermal events for all power domains, while the BladeCenter unit is set as the persistent command environment with a management module other than an advanced management module, at the system> prompt, type
fuelg -qm on
To view the detailed power domain status for power domain 1, while the BladeCenter unit is set as the persistent command environment, at the system> prompt, type
fuelg pd1
The following example shows the information that is returned when the fuelg command is run on a management module other than an advanced management module.
system> fuelg Note: All power values are displayed in Watts. Power Domain 1 -------------Status: Power domain status is good. Modules: Bay 1: 2000 Bay 2: 2000 Power Budget: 3200 Reserved Power: 400 Remaining Power: 2800 Power in Use: 400 Power Domain 2 -------------Status: Power domain status is good.
97
Modules: Bay 3: 1800 Bay 4: 1800 Power Budget: 2880 Reserved Power: 0 Remaining Power: 2880 Power in Use: 0 -qm off system> OK system> fuelg -qm on fuelg pd1 Power -- Allocated Power -State Current Max Min ===== ======= ===== ===== On On On On 10 120 120 25 25 45 45 390 10 120 120 25 25 45 45 390 10 120 120 25 25 45 45 390
Bay(s) Module ====== =================== Chassis Components Midplane no media tray Blowers 1 Blower 1 (NP) 2 Blower 2 (NP) Management Modules 1 WMN315619689 2 Backup MM (NP) I/O Modules 1 I/O Module 2 (NP) 2 I/O Module 2 (NP) Domain totals: Allocated Power
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" -os none system>
98
fuelg command (advanced management module only)

This command displays power domain information, listing the power modules that are installed in the BladeCenter unit and information about how the power in each domain is used. This command also configures the power domain policies for power redundancy loss and limiting fan noise during thermal events. Notes: 1. The fuelg command operates differently for the advanced management module and for other management module types. The following command description is for the advanced management module. See fuelg command (management modules other than the advanced management module) on page 96 for command syntax for management modules other than the advanced management module. 2. For scripting purposes, the -qm and -os fuelg options for management modules other than the advanced management module are supported by the advanced management module.
Table 30. fuelg command (advanced management module only) Function Display power domain status overview What it does Displays health status, total power usage, total dc power available, total ac power in use, thermal response (acoustic mode) settings, total thermal output in BTU/hour, and the polling intervals used for trending for all power domains. Command fuelg Valid targets -T system Note: For the BladeCenter S, output will indicate whether the chassis is running in 220 V ac or 110 V ac mode. -T system:blade[x] where x is the blade server bay number.
Display blade server power status overview
Displays the power management fuelg and capping setting (on/off) and power management capability for the specified blade server. Depending on the power management capability of the specified blade server, the following information will also display: v CPU duty cycles v Effective and maximum CPU speeds v Power capping value (minimum and maximum) v Maximum, minimum, and average power levels v Time when above data was captured v Power saver mode status (on, off) Displays the maximum, minimum, and average power information for the specified I/O module. fuelg
Display I/O module power status
-T system:switch[x] where x is the I/O (switch) module bay number. -T system:blower[x] where x is the blower bay number.
Display blower power status and temperature
Displays the maximum power, fuelg minimum power, average power, and current temperature information for the specified blower module.
99
Table 30. fuelg command (advanced management module only) (continued) Function Display media tray temperature What it does Command Valid targets -T system:mt[x] where x is the media tray number. Display detailed power domain status Displays detailed status and usage information for the specified power domains, including the policy setting for that domain, the maximum power limit, and the power in use. The valid states for components in the domain are: v * - blade server might throttle v C - communication error v D - discovering v Hib - hibernate v NP - module is not present v SB - standby v T - throttled v U - unable to power up Sets how the BladeCenter unit responds to a condition that could cause a loss of redundant power. fuelg domain where domain is pd1 for power domain 1 and pd2 for power domain 2. If no domain is specified, a status overview for all power domains displays. Note: The BladeCenter S unit has only one power domain. Use either pd or pd1 to specify the power domain for the BladeCenter S unit. fuelg domain -pm policy where: v domain is pd1 for power domain 1 and pd2 for power domain 2. v policy of: nonred (default) allows loss of redundancy. redwoperf prevents components from turning on that will cause loss of power redundancy. redwperf power throttles components to maintain power redundancy and prevents components from turning on that will cause loss of power redundancy. Command use restricted (see Commands and user authority on page 6). -T system Note: For the BladeCenter S, output will indicate whether the chassis is running in 220 V or 110 V ac mode. -T system Note: For the BladeCenter S, output will indicate whether the chassis is running in 220 V ac or 110 V ac mode.
Displays the current temperature for fuelg the specified media tray.
Set power domain redundancy loss policy
100
Table 30. fuelg command (advanced management module only) (continued) Function What it does Command Valid targets -T system
Display power trending Displays power trending information fuelg domain -pt period for specified time period for the selected time interval and where: and power domain selected power domain for the v domain is pd1 for BladeCenter unit. power domain 1 and pd2 for power domain 2. If no domain is specified, the period is applied to all power domains. v period is 1, 6, 12, or 24 hours. Command use restricted (see Commands and user authority on page 6).
Display power trending Displays power trending information fuelg -pt period -T system for specified time period for the selected time interval for the where period is 1, 6, 12, or -T system:blade[x] specified command target. 24 hours. -T system:switch[x] Command use restricted (see Commands and user authority on page 6). -T system:blower[x] where x is the blade server, I/O (switch) module, or blower bay number. -T system
Set power polling interval
Sets the amount of time between thermal and power samples that are taken to build trending data.
fuelg -int interval where interval is between 10 and 60 minutes, inclusive, in 5-minute increments. Command use restricted (see Commands and user authority on page 6).
Display thermal trending Displays thermal trending for specified time period information for the selected time interval for the specified command target.
fuelg -tt period
-T system:mt[x]
-T system:blower[x] where period is 1, 6, 12, or 24 hours. where x is the blade server or blower bay Command use restricted number. (see Commands and user authority on page 6).
101
Table 30. fuelg command (advanced management module only) (continued) Function What it does Command fuelg -am setting where the acoustic-mode setting of: v off (default) allows blowers to increase speed to provide additional cooling. v on keeps blowers at a fixed speed and power throttles BladeCenter components to reduce power consumption (only for BladeCenter components that support power throttling). Command use restricted (see Commands and user authority on page 6). Set power capping value for blade server Sets the power capping value for a specified blade server that support this feature. Note: A blade server must be turned on before you can set its power capping value. fuelg -pcap setting -T system:blade[x] Valid targets -T system
Thermal event response Sets how the BladeCenter unit (acoustic mode) blowers respond to thermal events.
where the power capping where x is the blade setting is a numeric value server bay number. that falls within the range of power capping values displayed when running the fuelg -T blade[x] command on a blade server. Command use restricted (see Commands and user authority on page 6).
Power management and Turns power management and capping - enable or capping for the specified blade disable for blade server server on or off. Note: A blade server must be turned on before you can enable power management and capping for it.
fuelg -pme setting where a setting of: v off (default) disables power management and capping for the blade server. v on enables power management and capping for the blade server. Command use restricted (see Commands and user authority on page 6).
-T system:blade[x] where x is the blade server bay number.
102
Table 30. fuelg command (advanced management module only) (continued) Function Power saver mode enable or disable for blade server What it does Turns power saver mode for the specified blade server on or off. Notes: v A blade server must be turned on before you can enable power saver mode for it. v Not all blade servers support the power saver mode. Command fuelg -ps setting where a setting of: v off (default) disables power saver mode for the blade server. v on enables power saver mode for the blade server. Command use restricted (see Commands and user authority on page 6). Valid targets -T system:blade[x] where x is the blade server bay number.
Example: To view a power domain status overview, while the BladeCenter unit is set as the persistent command environment, at the system> prompt, type
fuelg
To view the detailed power domain status for power domain 1, while the BladeCenter unit is set as the persistent command environment, at the system> prompt, type
fuelg pd1
To view BladeCenter unit power trending information for the past 6 hours, while the BladeCenter unit is set as the persistent command environment, at the system> prompt, type
fuelg -pt 6
To view the power status for the blade server in blade bay 1, while the BladeCenter unit is set as the persistent command environment, at the system> prompt, type
fuelg -T blade[1]
The following example shows the information that is returned from these commands when the fuelg command is run on an advanced management module.
system> fuelg Note: All power values are displayed in Watts. Total DC Power Available: 5000 Total AC Power In Use: 2938 Total Thermal Output: 10024 BTU/hour Power Domain 1 -------------Status: Power domain status is good. Modules: Bay 1: 2000 Bay 2: 2000 Power Management Policy: Non-redundant Power in Use: 1296 Total Power: 2650 Allocated Power (Max): 1610 Remaining Power: 1040 Power Domain 2 -------------Status: Power domain status is good.
103
Modules: Bay 3: 1875 Bay 4: 1875 Power Management Policy: Non-redundant Power in Use: 1304 Total Power: 2350 Allocated Power (Max): 1464 Remaining Power: 886 -am off -int 15 system> fuelg pd1 Maximum Power Limit: 2650 Power In Use: 1258 Bay(s) Module ====== ============================= Chassis Components Midplane 1 Media Tray 1 Chassis Cooling Devices 1 Chassis Cooling Device 1 2 Chassis Cooling Device 2 Management Modules 1 bc-amm 2 Standby MM I/O Modules 1 Ethernet SM 2 Ethernet SM 3 Fibre Channel SM 4 Fibre Channel SM Blades 1 Accounting 2 HR 3 Development 4 Marketing 5 Sales 6 TechSupport Domain totals: Allocated Power Power -- Allocated Power -State Current Max Min ===== ======= ===== ===== On On On On On On On On On On On On On On On On 10 10 26 27 25 15 45 45 45 45 254 220 61 139 220 80 1267 10 10 120 120 25 15 45 45 45 45 280 220 125 217 220 68 1610 10 10 120 120 25 15 45 45 45 45 174 220 85 161 220 68 1408
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" -pm nonred system> fuelg -pt 6 Date Time Avg Pwr -------- -------- ------07/17/07 08:09:44 2930 07/17/07 08:24:44 2926 07/17/07 08:39:48 2916 07/17/07 08:54:44 2906 07/17/07 09:09:44 2922 07/17/07 09:24:44 2926 07/17/07 09:39:44 2926 07/17/07 09:54:44 2926 07/17/07 10:09:44 2914 07/17/07 10:24:44 2928 07/17/07 10:39:48 2930 07/17/07 10:54:44 2914 07/17/07 11:09:43 2762 07/17/07 11:24:44 2924 07/17/07 11:39:44 2926 07/17/07 11:54:44 2932
104
07/17/07 12:09:44 2928 07/17/07 12:24:44 2922 07/17/07 12:39:43 2762 07/17/07 12:54:43 2772 07/17/07 13:09:43 2770 07/17/07 13:24:44 2766 07/17/07 13:39:44 2768 07/17/07 13:54:47 2926 system> fuelg -T blade[1] -pme off PM Capability: Dynamic Power Measurement with capping Effective CPU Speed: 2955 MHz Maximum CPU Speed: 3000 MHz -pcap 190 (min: 174, max: 280) Maximum Power: 235 Minimum Power: 199 Average Power: 235 Data captured at 07/17/07 13:59:05 system>
105
health command
This command displays the current health status of the command target. It can also 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 31. health command Function Display health status What it does Command Valid targets -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 BladeCenter S units) where x is the primary management-module, blade server, I/O (switch) module, power module, blower bay, or storage bay number. -T system
Displays the current health status of health the command target. Return values are different for the BladeCenter and BladeCenter T configurations. v Possible return values for the BladeCenter configuration are: ok warning critical v Possible return values for the BladeCenter T configurations are: ok minor major critical
Display health status for tree
Displays the current health status of the tree structure of devices present in the BladeCenter unit, starting at the command target level. If management-module bays are part of the tree, they will be identified as primary or redundant. Return values are different for the BladeCenter and BladeCenter T configurations. v Possible return values for the BladeCenter configuration are: ok warning critical v Possible return values for the BladeCenter T configurations are: ok minor major critical
health -l depth
where depth is 2, all, or -T system:mm[x] a for full tree display, -T system:blade[x] starting at the command -T system:switch[x] target level. -T system:power[x] Specifying a depth of 1 displays health status of the current command target. -T system:blower[x] where x is the primary management-module, blade server, I/O (switch) module, power module, or blower bay number.
106
Table 31. health command (continued) Function Display health status and alerts What it does Displays the current health status and active alerts for the command target. Return values are different for the BladeCenter and BladeCenter T configurations. v Possible return values for the health status of the BladeCenter configuration are: ok warning critical v Possible return values for the health status of the BladeCenter T configurations are: ok minor major critical v Active alert information provides short text descriptions of alerts that are active for each monitored component. The total amount of information returned from the health -f command is limited to 1024 bytes. Command health -f Valid targets -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 primary management-module, blade server, I/O (switch) module, power module, or blower bay number.
Example: To display the overall health status of the BladeCenter T unit, while the BladeCenter T unit is set as the default command target, at the system> prompt, type
health
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 default command target, at the system> prompt, type
health -l a
To display the health status of the blade server installed in blade bay 5, while the BladeCenter T unit is set as the default command target, at the system> prompt, type
health -T system:blade[5]
To display the health status and alerts for all components installed in the BladeCenter T unit, that are valid command targets, while the BladeCenter T unit is set as the default command target, at the system> prompt, type
health -l a -f
107
system> health system:major system> health -l a system: Major mm[1] : OK blade[1] : OK blade[3] : OK blade[5] : Minor power[1] : OK power[2] : Minor blower[1] : OK blower[2] : OK blower[3] : OK blower[4] : OK switch[1] : Major system> health -T system:blade[5] system: blade[5] : Minor system> health -l a -f system: Major blade[5] : Minor 5V over voltage CPU1 temperature warning power[2] : Minor 5V over voltage switch[1] : Major temperature fault system>
108
help command
This command displays a list of all commands that are available in the command-line interface with a brief description of each command. You can also issue the help command by typing ?. Adding a -h, -help, or ? option to a command displays syntax help for the command.
Table 32. help command Function Help What it does Displays a list of commands and a brief description of each command. Command help ? Valid targets Any installed device. Any installed device.
Example: To display a list of commands, while the advanced management module in bay 1 is set as the default command target, at the system:mm[1]> prompt, type
help

system:mm[1]> ? accseccfg advfailover alertcfg alertentries baydata bofm boot bootmode bootseq cin cinstatus clear clearlog clock config console dhcpinfo displaylog displaysd dns env exit files fuelg health help history identify ifconfig info iocomp kvm ldapcfg led list modactlog monalerts monalertsleg mt nat ntp ping help -- Display commands -- View/edit account security config -- View/edit advanced failover mode -- Displays/Configures the global remote alert settings -- View/edit remote alert recipients -- View/edit Blade bay data string -- View/edit data in comma-separated value files -- Boot target -- Boot mode -- View/edit the blade boot sequence settings -- Displays/configures Chassis Internal Network -- Displays status of Chassis Internal Network -- Clear the config -- Clear the event log -- View/edit date, time, GMT offset, and dst setting -- View/edit general settings -- Start SOL session to a blade -- View DHCP server assigned settings -- Display log entries -- Display service data -- View/edit DNS config -- Set persistent command target -- Log off -- Displays and deletes files stored on the AMM -- Power management -- View system health status -- Display command list -- Display command history -- Control target location LED -- View/edit network interface config -- Display identity and config of target -- View I/O compatibility for blades and switches -- Controls the kvm owner -- View/edit LDAP config -- Display and control Leds -- Display installed targets -- Displays module activity log -- Displays and configures monitored alerts -- Displays and configures legacy monitored alerts -- Controls the media tray owner -- Display and configure NAT -- View/edit NTP config -- Pings targeted switch module
109
portcfg pmpolicy ports power read remotechassis reset sddump security service shutdown slp smtp snmp sol sshcfg sslcfg syslog tcpcmdmode telnetcfg temps trespass uicfg update uplink users volts write zonecfg
------------------------------
Serial port configuration View/edit power management policy settings Port configuration Control target power Restore configuration from the chassis or a file Chassis discovered over the network Reset target Initiate service data dump View/edit security config Enable debugging by service personnel Shutdown target View/edit SLP parameters View/edit SMTP config View/edit SNMP config View SOL status and view/edit SOL config View/edit SSH config View/edit SSL config View/edit syslog config View/edit TCP command mode config View/edit telnet config View temperatures View/edit trespassing warning config View/edit user interface configuration Update firmware from TFTP server View/edit failover on network uplink loss config View/edit user login profiles View voltages Save configuration to chassis or a local file Zone configuration for I/O modules for individual command syntax help. for indexing (by bay number) a variable optional arguments choice
Type "<command> -h" [ ] is used < > denotes { } denotes | denotes system:mm[1]>
To v v v
obtain help about the env command, type one of the following commands: env -h env -help env ?
110
history command
This command displays the last eight commands that were entered, allowing the user to choose and re-enter one of these commands. You choose the command to re-enter from the displayed list by typing an exclamation point (!) followed immediately by the numeric designation the command is assigned in the list. You can also recall one of the past eight previously entered commands using the up-arrow and down-arrow keys.
Table 33. history command Function Command history Re-enter previous command using numeric designation What it does Displays the last eight commands that were entered. Re-enters a numerically-specified command from the command history. Command history !x where x is the number of the command (0 - 7) to re-enter from the command history list. Valid targets Any installed device. Any installed device.
Example: To display a list of the last eight commands entered, while management module 1 is set as the default command target, at the system:mm[1]> prompt, type
history
To re-enter the command designated by 2 in the command history, type

!2
system:mm[1]> history 0 dns 1 dns -on 2 dns 3 dns -i1 192.168.70.29 4 dns 5 dns -i1 192.168.70.29 -on 6 dns 7 history system:mm[1]> !2 Enabled -i1 192.168.70.29 -i2 0.0.0.0 -i3 0.0.0.0 system:mm[1]>
111
identify (location LED) command

This command controls operation of the location LED in a blade server or in the BladeCenter unit. It can also be used to display the state of a location LED.
Table 34. identify (location LED) command Function Display location LED state What it does Displays the current state of the location LED in the command target. Possible LED states are: v off v on v blink Set location LED state Sets the state of the location LED in the command target. identify -s state where state is on, off, or blink. Command use restricted (see Commands and user authority on page 6). Turn on BladeCenter Turns on the location LED in the unit location LED for BladeCenter unit for a specified specified period of time period of time before turning it off automatically. identify -s on -d time where time is the number of seconds the location LED will remain lit. Command use restricted (see Commands and user authority on page 6). Command identify Valid targets -T system -T system:blade[x] where x is the blade bay number.
-T system -T system:blade[x] where x is the blade bay number.
-T system
Example: To display the status of the location LED in the blade server in blade bay 4, while the BladeCenter unit is set as the persistent command environment, at the system> prompt, type
identify -T system:blade[4]
To light the location LED in the blade server in blade bay 4, while the BladeCenter unit is set as the persistent command environment, at the system> prompt, type
identify -s on -T system:blade[4]
The following example shows the information that is returned from a series of identify commands:
system> identify -T system:blade[4] -s off system> identify -s on -T system:blade[4] OK system> identify -T system:blade[4] -s on system>
112
ifconfig command (management modules other than the advanced management module)
This command configures and displays the network interface settings for the management-module Ethernet interface and the blade server integrated system management processors. Note: The ifconfig command operates differently for the advanced management module and for other management module types. The following command description is for management modules other than the advanced management module. See ifconfig command (advanced management module only) on page 118 for command syntax for the advanced management module.
Table 35. ifconfig command (management modules other than the advanced management module) Function What it does Command Valid targets -T system:mm[x] where x is the primary management-module bay number.
Display Ethernet Displays the current configuration of ifconfig -eth0 channel 0 configuration Ethernet channel 0. Possible return values are: v enabled v disabled v -i static_ip_address v -g gateway_address v -s subnet_mask v -n hostname v -c config_method v -r data_rate v -d duplex_mode v -m mtu v -l locally_administered_mac_addr v -b burnedin_mac_address Set Ethernet channel 0 static IP address Checks syntax and sets the static IP address for Ethernet channel 0.
ifconfig -eth0 -i ip_address -T system:mm[x] where ip_address is the static IP address for Ethernet channel 0. Command use restricted (see Commands and user authority on page 6). where x is the primary management-module bay number.
Set Ethernet channel 0 gateway IP address
Checks syntax and sets the gateway IP address for Ethernet channel 0.
ifconfig -eth0 -g ip_address where ip_address is the gateway IP address for Ethernet channel 0. Command use restricted (see Commands and user authority on page 6).
Set Ethernet channel 0 subnet mask
Checks syntax and sets the subnet mask for Ethernet channel 0.
ifconfig -eth0 -s sub_mask where sub_mask is the subnet mask for Ethernet channel 0. Command use restricted (see Commands and user authority on page 6).
113
Table 35. ifconfig command (management modules other than the advanced management module) (continued) Function Set Ethernet channel 0 hostname What it does Checks syntax and sets the host name for Ethernet channel 0. Command ifconfig -eth0 -n hostname where hostname is the host name for Ethernet channel 0. Command use restricted (see Commands and user authority on page 6). Set Ethernet channel 0 configuration method Checks syntax and sets the configuration method for Ethernet channel 0. A value of dthens will try the DHCP configuration and default to the static IP configuration if DHCP is unsuccessful. A value of dthens will try the DHCP configuration and default to the static IP configuration if DHCP is unsuccessful after 2 minutes. Note: If the management module DHCP setting is set to try the DHCP server and then use the static IP address, the management module will use the static IP address when the DHCP server is not available during management module start up. When this occurs, the IP address might not be reachable if multiple management modules were started with the same static IP address. Set Ethernet channel 0 data rate Checks syntax and sets the data rate for Ethernet channel 0. ifconfig -eth0 -r data_rate where data_rate is auto, 10, or 100. Command use restricted (see Commands and user authority on page 6). Set Ethernet channel 0 duplex mode Checks syntax and sets the duplex mode for Ethernet channel 0. ifconfig -eth0 -d duplex_mode where duplex_mode is auto, half, or full. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number. ifconfig -eth0 -c config_method where config_method is dhcp, static, or dthens. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number. Valid targets -T system:mm[x] where x is the primary management-module bay number.
114
Table 35. ifconfig command (management modules other than the advanced management module) (continued) Function Set Ethernet channel 0 MTU What it does Checks syntax and sets the MTU (maximum transmission unit) for Ethernet channel 0. Command ifconfig -eth0 -m mtu where mtu is between 60 and 1500, inclusive. Command use restricted (see Commands and user authority on page 6). Set Ethernet channel 0 static MAC address (locally administered) Checks syntax and sets the locally ifconfig -eth0 -l address administered MAC address to the specified MAC address for Ethernet where address is the locally administered MAC channel 0. address for Ethernet channel 0. Command use restricted (see Commands and user authority on page 6). Display Ethernet Displays the current configuration of ifconfig -eth1 channel 1 configuration Ethernet channel 1. Possible return values are: v enabled v disabled v -i static_ip_address v -g gateway_address v -s subnet_mask v -r data_rate v -d duplex_mode v -m mtu v -l locally_administered_mac_addr v -b burnedin_mac_address Set Ethernet channel 1 static IP address Checks syntax and sets the static IP address for Ethernet channel 1. -T system:mm[x] where x is the primary management-module bay number. Valid targets -T system:mm[x] where x is the primary management-module bay number.
Set Ethernet channel 1 gateway IP address
Checks syntax and sets the gateway IP address for Ethernet channel 1.
ifconfig -eth1 -g ip_address where ip_address is the gateway IP address for Ethernet channel 1. Command use restricted (see Commands and user authority on page 6).
115
Table 35. ifconfig command (management modules other than the advanced management module) (continued) Function Set Ethernet channel 1 subnet mask What it does Checks syntax and sets the subnet mask for Ethernet channel 1. Command ifconfig -eth1 -s sub_mask where sub_mask is the subnet mask for Ethernet channel 1. Command use restricted (see Commands and user authority on page 6). Set Ethernet channel 1 static MAC address (locally administered) Checks syntax and sets the locally ifconfig -eth1 -l address administered MAC address to the specified MAC address for Ethernet where address is the locally administered MAC channel 1. address for Ethernet channel 1. Command use restricted (see Commands and user authority on page 6). Enable Ethernet channel 1 Enables Ethernet channel 1. ifconfig -eth1 -up -T system:mm[x] -T system:mm[x] where x is the primary management-module bay number. Valid targets -T system:mm[x] where x is the primary management-module bay number.
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. Disable Ethernet channel 1 Disables Ethernet channel 1. ifconfig -eth1 -down -T system:mm[x]
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. Set starting IP address for blade server integrated system management processor Sets the starting point of the integrated system management processor IP addresses for blade servers that are installed in the BladeCenter unit. ifconfig -i ip_address where ip_address is the starting IP address for all blade servers that are installed in the BladeCenter unit. Command use restricted (see Commands and user authority on page 6). -T system:blade[1]:sp
Example: To display the configuration for Ethernet channel 0, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
ifconfig -eth0
To set the static IP address for Ethernet channel 0 to 192.168.70.133, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
ifconfig -eth0 -i 192.168.70.133 -c static
116
system:mm[1]> ifconfig -eth0 Enabled -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:80 system:mm[1]> ifconfig -eth0 -i 192.168.70.133 -c static Changes to the network settings will take effect after the next reset of the MM. system:mm[1]>
117
ifconfig command (advanced management module only)

This command configures and displays the network interface settings for the management-module Ethernet interface, I/O-module Ethernet interface, and the blade server integrated system management processors and installed options. Note: The ifconfig command operates differently for the advanced management module and for other management module types. The following command description is for the advanced management module. See ifconfig command (management modules other than the advanced management module) on page 113 for command syntax for management modules other than the advanced management module.
Table 36. ifconfig command (advanced management module only) Function Display primary management module Ethernet channel 0 configuration What it does Command Valid targets -T system:mm[x] where x is the primary management-module bay number.
Displays the current configuration of ifconfig -eth0 Ethernet channel 0 for the primary management module. Possible return values are: v enabled v disabled v -i static_ip_address v -g gateway_address v -s subnet_mask v -n hostname v -c config_method v -r data_rate v -d duplex_mode v -m mtu v -l locally_administered_mac_addr v -b burnedin_mac_address Displays the current configuration of ifconfig -eth0 -o Ethernet channel 0 for the standby management module. Possible return values are: v enabled v disabled v -i static_ip_address v -g gateway_address v -s subnet_mask v -n hostname v -c config_method v -r data_rate v -d duplex_mode v -m mtu v -l locally_administered_mac_addr v -b burnedin_mac_address Checks syntax and sets the static IP address for Ethernet channel 0 for the management module.
Display standby management module Ethernet channel 0 configuration
-T system:mm[x] where x is the standby management-module bay number.
Set management module Ethernet channel 0 static IP address
118
Table 36. ifconfig command (advanced management module only) (continued) Function Set standby management module Ethernet channel 0 static IP address What it does Checks syntax and sets the static IP address for Ethernet channel 0 for the standby management module. Command ifconfig -eth0 -o -i ip_address where ip_address is the static IP address for Ethernet channel 0. Command use restricted (see Commands and user authority on page 6). Set management module Ethernet channel 0 gateway IP address Checks syntax and sets the gateway IP address for Ethernet channel 0 for the management module. ifconfig -eth0 -g ip_address where ip_address is the gateway IP address for Ethernet channel 0. Command use restricted (see Commands and user authority on page 6). Set management module Ethernet channel 0 subnet mask Checks syntax and sets the subnet ifconfig -eth0 -s sub_mask mask for Ethernet channel 0 for the where sub_mask is the management module. subnet mask for Ethernet channel 0. Command use restricted (see Commands and user authority on page 6). Set management module Ethernet channel 0 hostname Checks syntax and sets the host ifconfig -eth0 -n hostname name for Ethernet channel 0 for the where hostname is the management module. host name for Ethernet channel 0. Command use restricted (see Commands and user authority on page 6). Set standby management module Ethernet channel 0 hostname Checks syntax and sets the host ifconfig -eth0 -o -n name for Ethernet channel 0 for the hostname standby management module. where hostname is the host name for Ethernet channel 0. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the standby management-module bay number. -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. Valid targets -T system:mm[x] where x is the standby management-module bay number.
119
Table 36. ifconfig command (advanced management module only) (continued) Function Set management module Ethernet channel 0 configuration method What it does Checks syntax and sets the configuration method for Ethernet channel 0 for the management module. A value of dthens will try the DHCP configuration and default to the static IP configuration if DHCP is unsuccessful after 2 minutes. Note: If the management module DHCP setting is set to try the DHCP server and then use the static IP address, the management module will use the static IP address when the DHCP server is not available during management module start up. When this occurs, the IP address might not be reachable if multiple management modules were started with the same static IP address. Set management module Ethernet channel 0 data rate Checks syntax and sets the data rate for Ethernet channel 0 for the management module. Command ifconfig -eth0 -c config_method where config_method is dhcp, static, or dthens. Command use restricted (see Commands and user authority on page 6). Valid targets -T system:mm[x] where x is the primary management-module bay number.
ifconfig -eth0 -r data_rate where data_rate is auto, 10, or 100. Command use restricted (see Commands and user authority on page 6).
Set management module Ethernet channel 0 duplex mode
Checks syntax and sets the duplex ifconfig -eth0 -d mode for Ethernet channel 0 for the duplex_mode management module. where duplex_mode is auto, half, or full. Command use restricted (see Commands and user authority on page 6).
Set management module Ethernet channel 0 MTU
Checks syntax and sets the MTU (maximum transmission unit) for Ethernet channel 0 for the management module.
ifconfig -eth0 -m mtu where mtu is between 60 and 1500, inclusive. Command use restricted (see Commands and user authority on page 6).
Set management module Ethernet channel 0 static MAC address (locally administered)
Checks syntax and sets the locally administered MAC address to the specified MAC address for Ethernet channel 0 for the management module.
ifconfig -eth0 -l address where address is the locally administered MAC address for Ethernet channel 0. Command use restricted (see Commands and user authority on page 6).
-T system:mm[x] where x is the standby management-module bay number.
120
Table 36. ifconfig command (advanced management module only) (continued) Function Set standby management module Ethernet channel 0 static MAC address (locally administered) What it does Checks syntax and sets the locally administered MAC address to the specified MAC address for Ethernet channel 0 for the standby management module. Note: This option is not available on the BladeCenter S. Command ifconfig -eth0 -o -l address where address is the locally administered MAC address for Ethernet channel 0. Command use restricted (see Commands and user authority on page 6). ifconfig -eth0 -up -T system:mm[x] Valid targets -T system:mm[x] where x is the primary management-module bay number.
Enable management module Ethernet channel 0
Enables the Ethernet channel 0 interface for the management module.
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. ifconfig -eth0 -down -T system:mm[x]
Disable management module Ethernet channel 0
Disables the Ethernet channel 0 interface for the management module.
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. ifconfig -T system:blade[x]:sp where x is the blade server bay number. ifconfig -i ip_address -T system:blade[x]:sp
Display starting IP address for blade server integrated system management processor Set starting IP address for blade server integrated system management processor
Displays the starting point of the integrated system management processor IP addresses for blade servers that are installed in the BladeCenter unit. Sets the starting point of the integrated system management processor IP addresses for blade servers that are installed in the BladeCenter unit. Note: This command has similar function to the ifconfig -bsmp ip_address command.
where ip_address is the IP where x is the blade address of the specified server bay number. blade server. The IP addresses for all other blade servers that are installed in the BladeCenter unit will be calculated based on this address. Command use restricted (see Commands and user authority on page 6).
121
Table 36. ifconfig command (advanced management module only) (continued) Function Display cKVM and network configuration status for blade server What it does Displays the cKVM status for the specified blade server. Valid states include: v Enabled v Disabled Note: This command will run only if cKVM is enabled for the target blade server. If the blade server supports network configuration, the command also displays the NIC numbers (such as -eth0 and -eth1), NIC states (up or down), and other NIC configuration information for all network cards connected to the blade server. Display network configuration information for network card Displays the NIC number (such as -eth0 and -eth1), NIC state (up or down), and other NIC configuration information for the specified network card in the specified blade server. Enable cKVM feature for the specified blade server. Note: The cKVM feature requires special hardware and is not available for all blade servers. Disable cKVM feature for the specified blade server. ifconfig -ethx where x is the NIC number. -T system:blade[x] where x is the blade server bay number. Command ifconfig Valid targets -T system:blade[x] where x is the blade server bay number.
Enable cKVM feature for blade server
ifconfig -ckvm enabled
-T system:blade[x]
Command use restricted where x is the blade (see Commands and user server bay number. authority on page 6). ifconfig -ckvm disabled -T system:blade[x]
Disable cKVM feature for blade server
Command use restricted where x is the blade (see Commands and user server bay number. authority on page 6). Set blade server Ethernet channel static IP address Checks syntax and sets the static IP address for the specified Ethernet channel of the specified blade server. Note: This command will run only if the target blade server is network configurable. ifconfig -ethx -i ip_address where: v x is the NIC number. v ip_address is the static IP address for Ethernet channel x. Command use restricted (see Commands and user authority on page 6). Set blade server Ethernet channel gateway IP address Checks syntax and sets the gateway IP address for the specified Ethernet channel of the specified blade server. Note: This command will run only if the target blade server is network configurable. ifconfig -ethx -g ip_address -T system:blade[x] where: v x is the NIC number. v ip_address is the gateway IP address for Ethernet channel x. Command use restricted (see Commands and user authority on page 6). where x is the blade server bay number. -T system:blade[x] where x is the blade server bay number.
122
Table 36. ifconfig command (advanced management module only) (continued) Function Set blade server Ethernet channel subnet mask What it does Checks syntax and sets the subnet mask for the specified Ethernet channel of the specified blade server. Note: This command will run only if the target blade server is network configurable. Command ifconfig -ethx -s sub_mask where: v x is the NIC number. v sub_mask is the subnet mask for Ethernet channel x. Command use restricted (see Commands and user authority on page 6). Set blade server Ethernet channel configuration method Checks syntax and sets the configuration method for the specified Ethernet channel of the specified blade server. ifconfig -ethx -c config_method where: v x is the NIC number. v config_method is dhcp, static, or dthens. -T system:blade[x] where x is the blade server bay number. Valid targets -T system:blade[x] where x is the blade server bay number.
A value of dthens will try the DHCP configuration and default to the static IP configuration if DHCP is Command use restricted unsuccessful after 2 minutes. (see Commands and user Note: v This command will run only if the authority on page 6). target blade server is network configurable. v If the DHCP setting is set to try the DHCP server and then use the static IP address, the NIC will use the static IP address when the DHCP server is not available during start up. When this occurs, the IP address might not be reachable if multiple devices were started with the same static IP address. Set management module Ethernet channel VLAN ID Checks syntax and sets the VLAN ID for the specified Ethernet channel of the specified blade server. Note: This command will run only if the target blade server is network configurable. ifconfig -ethx -v vlan_id where: v x is the NIC number. v vlan_id is from 1 to 4095, inclusive. If you enter a value outside this range, an error will be displayed. Command use restricted (see Commands and user authority on page 6). Set state for blade Enables or disables the VLAN ID ifconfig -ethx -ve state server Ethernet channel for the specified Ethernet channel where: VLAN ID of the specified blade server. Note: This command will run only if v x is the NIC number. v state is enable or the target blade server is network disable. configurable. Command use restricted (see Commands and user authority on page 6). -T system:blade[x] where x is the blade server bay number. -T system:blade[x] where x is the blade server bay number.
123
Table 36. ifconfig command (advanced management module only) (continued) Function Enable blade server Ethernet channel What it does Command Valid targets
Enables the specified Ethernet ifconfig -ethx -up -T system:blade[x] channel interface of the specified where x is the NIC blade server. where x is the blade Note: This command will run only if number. server bay number. the target blade server is network Command use restricted configurable. (see Commands and user authority on page 6). Disables the specified Ethernet ifconfig -ethx -down -T system:blade[x] channel interface of the specified where x is the NIC blade server. where x is the blade Note: This command will run only if number. server bay number. the target blade server is network Command use restricted configurable. (see Commands and user authority on page 6). Displays network settings for the BladeCenter unit. Valid return values are: v -bsmp base_bsmp_ip_address v -v VLAN-id v -maxv enabled/disabled Allows up to four remote video sessions for each blade server. ifconfig -T system
Disable blade server Ethernet channel
Display network settings for BladeCenter unit
Enable multiple video sessions for blade servers
ifconfig -maxv enabled Command use restricted (see Commands and user authority on page 6).
-T system
Disable multiple video sessions for blade servers
Allows only a single remote video session for each blade server.
ifconfig -maxv disabled Command use restricted (see Commands and user authority on page 6).
-T system
Set starting IP address for blade server integrated system management processor
Sets the starting point of the integrated system management processor IP addresses for blade servers that are installed in the BladeCenter unit. Note: This command has similar function to the ifconfig -i ip_address command.
ifconfig -bsmp ip_address where ip_address is the starting IP address for all blade servers installed in the BladeCenter unit. Command use restricted (see Commands and user authority on page 6). ifconfig -v VLAN-id where VLAN-id is from 1 to 4095, inclusive. If you enter a value outside this range, an error will be displayed. Command use restricted (see Commands and user authority on page 6).
-T system
VLAN ID for BladeCenter unit
Checks syntax and sets the VLAN ID for the BladeCenter unit.
-T system
124
Table 36. ifconfig command (advanced management module only) (continued) Function Enable global cKVM feature for BladeCenter unit What it does Enable cKVM feature globally for the BladeCenter unit. (This is the same as running the ifconfig -ckvm enable command directed to each blade server.) Disable cKVM feature globally for the BladeCenter unit. (This is the same as running the ifconfig -ckvm disable command directed to each blade server.) Displays network settings for the specified I/O module. Valid return values are: v I/O-module type v Config. Method config_method v -i ip_address v -s subnet_mask v -g gateway_address v -em ext_mgt_status v -ep ext_port_status v -pm enabled/disabled (protected mode) v -pip enabled/disabled Sets the IP addresses for the specified I/O module. Command ifconfig -ckvm enabled Command use restricted (see Commands and user authority on page 6). ifconfig -ckvm disabled Command use restricted (see Commands and user authority on page 6). ifconfig -T system:switch[x] where x is the I/O-module bay number. -T system Valid targets -T system
Disable global cKVM feature for BladeCenter unit
Display network settings for I/O module
Set starting IP address for I/O module
ifconfig -i ip_address
-T system:switch[x]
where ip_address is the IP where x is the address of the specified I/O-module bay I/O module. number. Command use restricted (see Commands and user authority on page 6). Set I/O-module gateway Checks syntax and sets the IP address gateway IP address for the specified I/O module. ifconfig -g ip_address -T system:switch[x]
where ip_address is the where x is the gateway IP address for the I/O-module bay I/O module. number. Command use restricted (see Commands and user authority on page 6).
Keep new IP address configuration for I/O-module after reset
Retains a new IP address configuration after the specified I/O module is reset.
ifconfig -pip enabled
-T system:switch[x]
Command use restricted where x is the (see Commands and user I/O-module bay authority on page 6). number. ifconfig -pip disabled -T system:switch[x]
Revert to old IP address Reverts IP address to old configuration for configuration after the specified I/O I/O-module after reset module is reset.
Command use restricted where x is the (see Commands and user I/O-module bay authority on page 6). number.
125
Table 36. ifconfig command (advanced management module only) (continued) Function Set I/O-module subnet mask What it does Checks syntax and sets the subnet mask for the specified I/O module. Command ifconfig -s sub_mask where sub_mask is the subnet mask for the I/O module. Command use restricted (see Commands and user authority on page 6). Enable external management for I/O module Enables external management on all ports for the specified I/O module. ifconfig -em enabled -T system:switch[x] Valid targets -T system:switch[x] where x is the I/O-module bay number.
Command use restricted where x is the (see Commands and user I/O-module bay authority on page 6). number. ifconfig -em disabled -T system:switch[x]
Disable external management for I/O module
Disables external management on all ports for the specified I/O module.
Command use restricted where x is the (see Commands and user I/O-module bay authority on page 6). number. ifconfig -ep enabled -T system:switch[x]
Enable external ports for I/O module
Enables external ports for the specified I/O module.
Command use restricted where x is the (see Commands and user I/O-module bay authority on page 6). number. Disable external ports for I/O module Disables external ports for the specified I/O module. ifconfig -ep disabled -T system:switch[x]
Command use restricted where x is the (see Commands and user I/O-module bay authority on page 6). number. Enable protected mode for I/O module Enables protected mode for the specified I/O module. ifconfig -pm enabled -T system:switch[x]
Command use restricted where x is the (see Commands and user I/O-module bay authority on page 6). number. Disable protected mode Disables protected mode for the for I/O module specified I/O module. ifconfig -pm disabled -T system:switch[x]
Example: To display the configuration for Ethernet channel 0, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
ifconfig -eth0
To set the static IP address for Ethernet channel 0 to 192.168.70.133, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
ifconfig -eth0 -i 192.168.70.133 -c static
126
system:mm[1]> ifconfig -eth0 Enabled -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:80 system:mm[1]> ifconfig -eth0 -i 192.168.70.133 -c static Changes to the network settings will take effect after the next reset of the MM. system:mm[1]>
127
info (configuration information) command

This command displays information about BladeCenter components and their configuration, and how to reload the component information.
Table 37. info (configuration information) command Function Display component information What it does Displays identification and configuration information for the command target. Command info Note: Only one target at a time can be viewed with the info command. Valid targets -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] (for advanced management modules) -T system:blade[x] :dtr[y] (for management modules other than the advanced management module -T system:blade[x] :mgmtcrd (for advanced management modules) -T system:blade[x]:sp -T system:blade[x]:be[y] (for advanced management modules) -T system:blade[x]:be (for management modules other than the advanced management module) -T system:blade[x]:sb (for advanced management modules) -T system:blade[x]: cpu[y] (continued on next page)
128
Table 37. info (configuration information) command (continued) Function Display component information (continued) What it does Command Valid targets -T system:blade[x]:hsec (for advanced management modules) -T system:blade[x]:ckvm (for advanced management modules) -T system:switch[x] -T system:power[x] -T system:mt[x] (for advanced management modules) -T system:mt (management modules other than the advanced management module) -T system:storage[x] (for advanced management modulesBladeCenter S units only). where: v x is the management-module bay number, blade server bay number, I/O (switch) module bay number, microprocessor number, power module bay number, media-tray bay number, storage bay number (advanced management modules only), or daughter-card number. v y is the: blade server storage expansion unit number (be). (advanced management modules only). blade server I/O expansion card number (exp and dtr). microprocessor number (CPU).
129
Table 37. info (configuration information) command (continued) Function Reload component information for firmware Reload component information for hardware Reload information on MAC addresses Reload WWN and GUID information Reload all component information What it does Reloads vital product data (VPD) for firmware. Reloads vital product data (VPD) for hardware. Reloads vital product data (VPD) for MAC addresses. Reloads vital product data (VPD) for world-wide name (WWN) and globally-unique identifier (GUID). Command info -reload fw Valid targets -T system
info -reload hw
-T system
info -reload mac info -reload wwn
-T system -T system
Forces reload of all VPD and MAC info -reload all address information.
-T system
Notes: 1. The command targets -T system:blade[x]:exp[y], -T system:blade[x]:dtr[y], and are shown with a line break before the :exp[y] or:dtr[y]. When these command targets are entered, the entire entry must all be on one line. 2. This command returns vital product data (VPD) information that is unique for each command target. For some targets, additional VPD information is available 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 the corresponding category; for example, all MAC addresses are reloaded for all targets when the command is info -reload mac with system:blade[x] as the target. Example: To view the information about an advanced management module in management-module bay 1, while this management module is set as the persistent command environment, at the system:mm[1]> prompt, type
info
The following example shows the information that might be returned from the info command:
system:mm[1]> info Name: AMM_KP Manufacturer: Not Available (Not Available) Manufacturer ID: 288 Product ID: 1 Mach type/model: Management Module Mach serial number: Not Available Manuf date: 3005 Hardware rev: 51 Part no.: 26R099000000 FRU no.: 25R5777 FRU serial no.: 0J1U9E584130 CLEI: Not Available AMM firmware Build ID: BPET30U File name: CNETCMUS.PKT
130
Rel date: Rev: system:mm[1]>
08-09-07 30
131
iocomp command (advanced management module only)

This command displays the compatibility between all blade servers and their I/O modules. It can also display detailed interface information for an individual blade server or I/O module.
Table 38. iocomp command Function What it does Command Valid targets -T system
Display compatibility Displays I/O module compatibility iocomp between all blade information for all blade servers and servers and I/O modules I/O modules. Display blade server compatibility details Displays detailed I/O module compatibility information for the specified blade server. Displays detailed compatibility information for the specified I/O module. iocomp
-T system:blade[x] where x is the blade server bay number.
Display I/O module compatibility details
iocomp
-T system:switch[x] where x is the I/O (switch) module bay number.
Example: To view I/O module compatibility information for all blade servers and I/O modules, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
iocomp -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 the system:mm[1]> prompt, type
iocomp -T system:blade[1]
To view I/O module compatibility information for the I/O module in bay 2, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
iocomp -T system:switch[2]
system:mm[1]> iocomp Blades 1 xPert1 2 xPert2 3 Development 4 Marketing 5 xpert3 6 Sales 7 xPert4 9 xPert5 11 Finance 12 HR 13 xPert6 14 xPert7 I/O Modules 1 OK 2 OK 3 OK 4 OK -T system OK OK OK OK OK OK OK OK OK OK OK OK
132
system:mm[1]> iocomp -T system:blade[1] Bay Power Fabric Type Fabric on Blade Compt ------- ------- ---------------------- --------------- ------IOM 1 On Ethernet Switch Module Ethernet OK IOM 2 On Ethernet Switch Module Ethernet OK system:mm[1]> iocomp -T system:switch[1] Bay Power Fabric Type Compat ---------- ------- -------------- ---------Blade 1 On Ethernet OK Blade 2 On Ethernet OK Blade 3 On Ethernet OK Blade 4 On Ethernet OK Blade 5 Off Ethernet OK Blade 6 On Ethernet OK Blade 7 On Ethernet OK n/a No Fabric Blade 9 On Ethernet OK Ethernet OK Blade 11 On Ethernet OK Blade 12 On Ethernet OK Blade 13 On Ethernet OK Blade 14 On Ethernet OK system:mm[1]>
133
kvm (keyboard, video, mouse) command (advanced management module only)

This command sets and displays the blade server that is in control of the BladeCenter unit shared KVM.
Table 39. kvm command Function Display KVM owner What it does Displays the number of the blade server that has KVM ownership and the global local KVM switching state for all blade servers. A blade server that occupies more than one blade bay is identified by the lowest bay number that it occupies. A return value of 0 indicates that no owner is set. Sets a blade server as the KVM owner. Command kvm Command use restricted (see Commands and user authority on page 6). Valid targets -T system
Set KVM owner
kvm -b blade_server where blade_server is the blade bay that identifies the blade server. A blade server that occupies more than one blade bay is identified by the lowest bay number that it occupies. A setting of 0 sets no owner. Command use restricted (see Commands and user authority on page 6).
-T system
Enable local KVM switching globally
Enable local KVM switching globally kvm -local enable -T system for all blade servers. Command use restricted (see Commands and user authority on page 6). Disable local KVM switching globally for all blade servers. kvm -local disable Command use restricted (see Commands and user authority on page 6). -T system
Disable local KVM switching globally
Example: To set the KVM owner to the blade server in blade bay 1, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
kvm -T system -b 1
To display the KVM owner and global local KVM switching state for all blade servers, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
kvm -T system
134
system:mm[1]> kvm -T system -b 1 OK system:mm[1]> kvm -T system -b 1 -local enabled system:mm[1]>
135
ldapcfg command (advanced management module only)

This command sets and displays the LDAP configuration settings for the advanced management module.
Table 40. ldapcfg command Function Display LDAP settings What it does Displays the LDAP settings for the management module. Command ldapcfg Valid targets -T system:mm[x] where x is the primary management-module bay number. Set LDAP security version Sets version of LDAP security used ldapcfg -v version by the management module. where version is: v v1 for old user permission model v v2 for the enhanced role-based security model Command use restricted (see Commands and user authority on page 6). Set LDAP name Sets the LDAP name for the management module. Note: For an LDAP name to be used, LDAP security must be set to v2 using the -v command option. ldapcfg -t name -T system:mm[x] -T system:mm[x] where x is the primary management-module bay number.
where name is an where x is the primary alphanumeric string up to management-module 63 characters in length bay number. containing any character except for angle brackets ( < and > ) and spaces. Command use restricted (see Commands and user authority on page 6).
Set LDAP server discovery method
Sets the method to use for discovering LDAP servers that provide user authentication. Note: v If the dns method is specified, the following values must also be 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 command option. v If the preconf method is specified, the following values must also be set: A LDAP server hostname or IP address using the -i1, -i2, and -i3 command options. A port for each LDAP server hostname or IP address using the -p1, -p2, and -p3 command options.
ldapcfg -server method
-T system:mm[x]
where method is: where x is the primary v dns for dynamic management-module discovery bay number. v preconf to use an LDAP server that was manually pre-configured Command use restricted (see Commands and user authority on page 6).
136
Table 40. ldapcfg command (continued) Function Set LDAP server domain source What it does Sets the domain source to use for dynamic (DNS) LDAP server discovery. Note: If an sd or ltsd source is specified, the following values must also be set: v A search domain using the -sd command option. v A LDAP server hostname or IP address using the -i1, -i2, and -i3 command options. v A port for each LDAP server hostname or IP address using the -p1, -p2, and -p3 command options. Command ldapcfg -ds source where source is: v login to extract the search domain from the login ID v sd to use a pre-configured search domain v ltsd to try the login id first and then use a pre-configured value Command use restricted (see Commands and user authority on page 6). ldapcfg -sd domain where domain is an alphanumeric string up to 31 characters in length. Command use restricted (see Commands and user authority on page 6). Set LDAP server service name Sets the service name to use for dynamic (DNS) LDAP server discovery. ldapcfg -sn service where service is an alphanumeric string up to 15 characters in length. Command use restricted (see Commands and user authority on page 6). First LDAP server host name or IP address set Checks syntax and sets the first LDAP server host name or IP address to use for pre-configured LDAP server discovery. Note: A port for this LDAP server hostname or IP address must be set using the -p1 command option. ldapcfg -i1 hostname/ip_address where hostname/ip_address is the first host name or IP address. Command use restricted (see Commands and user authority on page 6). Second LDAP server host name or IP address - set Checks syntax and sets the second LDAP server host name or IP address to use for pre-configured LDAP server discovery. Note: A port for this LDAP server hostname or IP address must be set using the -p2 command option. ldapcfg -i2 hostname/ip_address where hostname/ip_address is the second host name or IP address. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. Valid targets -T system:mm[x] where x is the primary management-module bay number.
Set LDAP server search Sets the search domain to use for domain dynamic (DNS) LDAP server discovery.
137
Table 40. ldapcfg command (continued) Function Third LDAP server host name or IP address set What it does Checks syntax and sets the third LDAP server host name or IP address to use for pre-configured LDAP server discovery. Note: A port for this LDAP server hostname or IP address must be set using the -p3 command option. Command ldapcfg -i3 hostname/ip_address where hostname/ip_address is the third host name or IP address. Command use restricted (see Commands and user authority on page 6). First LDAP server port number - set Sets the port number of the first LDAP server to use for pre-configured LDAP server discovery. ldapcfg -p1 port where port is from 1 to 65535, inclusive. If you enter a value outside this range, an error will be displayed. Command use restricted (see Commands and user authority on page 6). Second LDAP server port number - set Sets the port number of the second ldapcfg -p2 port LDAP server to use for where port is from 1 to pre-configured LDAP server 65535, inclusive. If you discovery. enter a value outside this range, an error will be displayed. Command use restricted (see Commands and user authority on page 6). Third LDAP server port number - set Sets the port number of the third LDAP server to use for pre-configured LDAP server discovery. ldapcfg -p3 port where port is from 1 to 65535, inclusive. If you enter a value outside this range, an error will be displayed. Command use restricted (see Commands and user authority on page 6). Set LDAP root distinguished name Sets the root distinguished name for the root entry of the LDAP directory tree that is used as the base object for all searches. ldapcfg -rd name -T system:mm[x] -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. Valid targets -T system:mm[x] where x is the primary management-module bay number.
where name is up to 63 where x is the primary characters in length and management-module contained within bay number. double-quotes. Names can contain any character, including spaces. Command use restricted (see Commands and user authority on page 6).
138
Table 40. ldapcfg command (continued) Function Set LDAP UID search attribute What it does Sets the UID search attribute that represents the user IDs stored on the LDAP server. On Active Directory servers, the UID search attribute is typically set to sAMAccountName. On Novell eDirectory and OpenLDAP servers, it is typically set to uid. Command ldapcfg -usa UID where UID is up to 23 characters in length and contained within double-quotes. The UID can contain only letters, numbers, spaces, and the following characters: -, (, ), +, ,, ., /, :, and?. Command use restricted (see Commands and user authority on page 6). Set LDAP server binding method Sets the binding method for initial connection to the LDAP server. Note: v If the binding method is set to anon , a UID search attribute must be set using the -usa command option. v If the binding method is set to cc, the following values must also be set: A UID search attribute using the -usa command option A client distinguished name using the -cd command option. A client password using the -p and -cp command options. Sets the client distinguished name (DN) for initial connection to the LDAP server. Note: A client password must also be set using the -p and -cp command options. ldapcfg -bm version where version is: v anon for anonymous v cc for configured credentials v lc for login credentials Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number. Valid targets -T system:mm[x] where x is the primary management-module bay number.
Set LDAP client distinguished name
ldapcfg -cd domain
-T system:mm[x]
where domain is an where x is the primary alphanumeric string up to management-module 63 characters in length bay number. containing any character except for angle brackets ( < and > ) and spaces. Command use restricted (see Commands and user authority on page 6).
Set LDAP client distinguished name password
Sets the client distinguished name password for initial connection to the LDAP server. Note: The passwords must be specified by both the -p and -cp command options and must match.
ldapcfg -p password where password is an alphanumeric string up to 15 characters in length. Command use restricted (see Commands and user authority on page 6).
139
Table 40. ldapcfg command (continued) Function Set (confirm) LDAP client distinguished name password What it does Sets, for confirmation purposes, the client distinguished name password for initial connection to the LDAP server. Note: The passwords must be specified by both the -p and -cp command options and must match. Command ldapcfg -cp password where password is an alphanumeric string up to 15 characters in length. Command use restricted (see Commands and user authority on page 6). ldapcfg -gf filter where filter is up to 511 characters in length and consists of one or more group names. The colon (:) character is used to delimit multiple group names. Leading spaces and trailing spaces are ignored. Other spaces are treated as part of the group name. The wildcard character (*) is not supported for security reasons. A group name can be specified as a full domain name or by using the common name (cn) portion. Command use restricted (see Commands and user authority on page 6). Set LDAP group search attribute (advanced management module only) Sets the group search attribute that represents groups of user IDs stored on the LDAP server. On Active Directory servers, the group search attribute is typically set to memberOf. On eDirectory servers, it is typically set to groupMembership. In an OpenLDAP server environment, users are typically assigned to groups whose objectClass equals PosixGroup. In this case, the group search attribute identifies members of a particular PosixGroup that is typically memberUid. ldapcfg -gsa GSA where GSA is an alphanumeric string up to 23 characters in length. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. Valid targets -T system:mm[x] where x is the primary management-module bay number.
Set LDAP group filter
Sets the group filter for the management module that can be used for authentication during LDAP server login.
140
Table 40. ldapcfg command (continued) Function Set LDAP login permission attribute (advanced management module only) What it does Sets the login permission attribute that is used to determine retrieve user permissions on the LDAP server. Command ldapcfg -lpa permission where permission is an alphanumeric string up to 23 characters in length. Command use restricted (see Commands and user authority on page 6). Valid targets -T system:mm[x] where x is the primary management-module bay number.
Example: To set the management module LDAP security version to v1, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
ldapcfg -v v1
To display the management module LDAP settings, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
ldapcfg
system:mm[1]> ldapcfg -v v1 OK system:mm[1]> ldapcfg -server preconf Parameters for -server dns configuration: -ds login -sd -sn ldap Parameters for -server preconf configuration: -i1 -p1 -i2 -p2 -i3 -p3 Miscellaneous Parameters: -rd -usa -bm cc Parameters for -bm cc configuration: -cd -v v1 Parameters for -v v1 configuration: -gf BladeCenter -gsa -lpa Parameters for -v v2 configuration: -t system:mm[1]>
141
led command (advanced management module)

This command displays and sets the LED states for a specified command target, if this command target supports the LED.
Table 41. led command Function Display various LED states What it does Command Valid targets -T system -T system:blade[x] where x is the blade server number.
Displays various LED states. Values led returned are: v status of all LEDs on the target blade and its sub-components v status of info LED v status of location LED (on/off/blink) v status of the identification LED of the system for a specified number of seconds
Display state for fanpack fault LED
Displays the state of the fan pack fault LED of the BladeCenter HT unit.
led
-T system:power[x] (fanpack for BladeCenter HT units only) where x is the power module (fanpack) number.
Display state for blower Displays the state of the blower fault LED fault LED of the BladeCenter HT unit.
led
-T system:blower[x](for BladeCenter HT units only) where x is the blower number.
Display front panel LED Displays the state of the front panel led state for blade server LEDs on the specified blade server.
-T system:blade[x] where x is the blade server number.
Display external port link status LED state for I/O module
Displays state of the external and led internal port link status LEDs for the specified I/O module.
-T system:switch[x] where x is the I/O module (switch) bay number.
142
Table 41. led command (continued) Function Display fault LED state What it does Command led -e Valid targets -T system:tap (for BladeCenter HT units only) -T system:ncc[x] (for BladeCenter HT units only) -T system:mux[x] (for BladeCenter HT units only) -T system:mt[x] (for BladeCenter HT units only) where x is the network clock module, multiplexer expansion module, or media tray number. Display safe-to-remove LED state Displays the state of the safe-to-remove LED, that is on the BladeCenter unit and some (for BladeCenter HT units components, for the specified only) command target. Possible return values are: v On v Off -T system:mux[x] (for BladeCenter HT units only) where x is the network clock module, or multiplexer expansion module. Display LED state for blade server and all sub-components Displays the state of all LEDs on the specified blade server and its subcomponents. Possible return values are: v On v Off v Blink Turn off information LED Turns off the information LED, that led -info off -T system is on the BladeCenter unit and -T system:blade[x] some components, for the specified Command use restricted (see Commands and user command target where x is the blade authority on page 6). server, network clock module, multiplexer expansion module, or media tray number. led -l -T system:blade[x] where x is the blade server number. led -r -T system:tap (for BladeCenter HT units only) -T system:ncc[x] (for BladeCenter HT units only)
Displays the state of the fault LED for the specified command target. (for BladeCenter HT units Possible return values are: only) v The state of the requested LED is ON v The state of the requested LED is OFF
143
Table 41. led command (continued) Function Set location LED state What it does Sets the state of the location LED, that is on the BladeCenter unit and some blade servers, for the command target. Command led -loc state where state is on, off, or blink. Note: A state of blink can only be used for the -T system command target and for the blade servers. Command use restricted (see Commands and user authority on page 6). Turn on location LED for specified period of time Turns on the location LED, that is on the BladeCenter unit and some blade servers, for a specified period of time before turning it off automatically. led -loc on -d time where time is the number of seconds the location LED will remain lit. Command use restricted (see Commands and user authority on page 6). -T system Valid targets -T system -T system:blade[x] where x is the blade bay number.
Example: To display the failure LED status for the blade server in bay 1, while the BladeCenter HT unit is set as the persistent command environment, at the system> prompt, type
led -T system:blade[1]
To display status of the front-panel LEDs for the blade server in bay 1, while the BladeCenter HT unit is set as the persistent command environment, at the system> prompt, type
led -T blade[1]
To display status of all LEDs for the blade server in bay 1, while the BladeCenter HT unit is set as the persistent command environment, at the system> prompt, type
led -l -T blade[1]
system> led -T blade[1] b47-Mongoose Error: off Information: off KVM: off MT: off Location: blink system> led -T blade[1] -l Component Label Processor1 CPU1 Processor2 CPU2 Blade1 Fault Blade2 Information Blade3 Location Blade4 Power KVM Blade5 Media Tray
State Off Off Off Off Blink On Off Off
Location System board System board Front panel Front panel Front panel Front panel Front panel Front panel
144
Blade7 Blade8 Blade1 Storage1 Memory1 Memory2 Memory3 Memory4 Memory5 Memory6 Memory7 Memory8 Panel1 Expansion1 Expansion2
Expansion3 system>
Over Temp N/A N/A DASD1 DIMM1 DIMM2 DIMM3 DIMM4 DIMM5 DIMM6 DIMM7 DIMM8 N/A N/A N/A N/A N/A N/A N/A N/A
Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off Off
System System System System System System System System System System System System System FRU FRU FRU FRU FRU FRU FRU
board board board board board board board board board board board board board
145
list (system physical configuration) command

This command displays a list of devices present within the command target. It can be used to determine how many management modules are installed in the BladeCenter unit and which management module is set as primary.
Table 42. list (system physical configuration) command Function View command target What it does Displays the current command target. If a management-module bay is the current command target, it will be identified as primary or redundant. Displays the tree structure of devices present in the BladeCenter unit, starting at the command target level. If management-module bays are part of the tree, they will be identified as primary or redundant. For components that have been assigned a name, this name will be displayed next to the component bay number. Command list Valid targets Any installed device.
View system configuration tree
list -l depth where depth is all or a for full tree display, starting at the command target level. Specifying a depth of 1 displays the current command target. Specifying a depth of 2 displays the content of the current command target plus one level below it.
Any installed device.
Example: To display a list of devices installed in the BladeCenter unit, while the BladeCenter unit is set as the persistent command environment, at the system> prompt, type
list -l a
(This is the command syntax that can be used to determine the primary management module.) The following example shows the information that is returned when the command is run on an advanced management module:
system> list -l a system mm[1] primary mm[2] standby power[1] power[2] power[3] power[4] blower[1] blower[2] switch[1] switch[2] switch[3] switch[4] blade[1] Accounting sp cpu[1] cpu[2] blade[2] HR sp cpu[1] cpu[2]
146
blade[3] Development sp cpu[1] blade[4] Marketing sp ckvm cpu[1] cpu[2] blade[5] Sales sp cpu[1] cpu[2] blade[6] TechSupport sp exp[2] cpu[1] cpu[3] cpu[4] mt[1] system>
Note: The BladeCenter S unit supports one management module. The list command for this unit does not refer to primary and standby management modules.
147
modactlog command (advanced management module only)

This command displays information about modules installed in all of the blade servers.
Table 43. modactlog command Function What it does Command Valid targets -T system
Display blade server Displays a list of modules installed modactlog module information and in all blade servers, along with their activity activity and VPD information.
Example: To view the list of modules installed in all blade servers, along with their activity and VPD information, while the BladeCenter unit is set as the default command target, at the system> prompt, type
modactlog
system> modactlog Bay Name FRU Number --- ----------------------------- -----------14 Fibre Channel Expansion Card 59P6624 11 cKVM card 13N0842 system> FRU Serial No ------------J1RJH3CY18N YK328064418F Manuf. ID --------SLRM IBM Action Timestamp ------- ------------------Added 15:51:18 02/09/2007 Added 15:51:07 02/09/2007
Note: The BladeCenter S unit will also display information about the Direct Serial Attach Module and the storage modules.
148
monalerts command (advanced management module only)

This command displays and configures alerts that are monitored by the advanced management module.
Table 44. monalerts command Function Display monitored alert states What it does Command Valid targets -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number.
Displays the state of all alerts being monalerts monitored by the management module.
Set state for enhanced legacy alert categories
Enables or disables enhanced legacy alert categories. v If enhanced legacy alert categories are disabled, alerts are configured using the monalertsleg command. v If enhanced legacy alert categories are enabled, alerts are configured using the monalerts command.
monalerts -ec state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6).
Set monitoring state for Enables or disables monitoring of all critical alerts all critical alerts.
monalerts -ca state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6).
Set monitoring state for Enables or disables monitoring of blade device critical blade device critical alerts. alerts
monalerts -cb state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6).
Set monitoring state for Enables or disables monitoring of I/O-module critical I/O-module critical alerts. alerts
monalerts -ciom state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6).
Set monitoring state for Enables or disables monitoring of storage-module critical storage-module critical alerts. alerts (BladeCenter S units only)
monalerts -cstg state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6).
149
Table 44. monalerts command (continued) Function What it does Command monalerts -ccsm state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of cooling device critical cooling device critical alerts. alerts monalerts -ccd state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of power module critical power module critical alerts. alerts monalerts -cpm state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of all warning alerts all warning alerts. monalerts -wa state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of blade device warning blade device warning alerts. alerts monalerts -wb state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of I/O-module warning I/O-module warning alerts. alerts monalerts -wiom state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of storage-module warning storage-module warning alerts. alerts (BladeCenter S units only) monalerts -wstg state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. Valid targets -T system:mm[x] where x is the primary management-module bay number.
Set monitoring state for Enables or disables monitoring of chassis or system chassis or system management management critical critical alerts. alerts
150
Table 44. monalerts command (continued) Function What it does Command monalerts -wcsm state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of event log warning alerts event log warning alerts. monalerts -wel state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of cooling device warning cooling device warning alerts. alerts monalerts -wcd state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of power module warning power module warning alerts. alerts monalerts -wpm state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of all informational alerts all informational alerts. monalerts -ia state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of blade device blade device informational alerts. informational alerts monalerts -ib state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of I/O-module I/O-module informational alerts. informational alerts monalerts -iiom state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. Valid targets -T system:mm[x] where x is the primary management-module bay number.
Set monitoring state for Enables or disables monitoring of chassis or system chassis or system management management warning warning alerts. alerts
151
Table 44. monalerts command (continued) Function What it does Command Valid targets -T system:mm[x] where x is the primary management-module bay number.
Set monitoring state for Enables or disables monitoring of monalerts -istg state storage-module storage-module informational alerts. where state is enabled or informational alerts disabled. (BladeCenter S units Command use restricted only) (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of chassis or system chassis or system management management informational alerts. informational alerts monalerts -icsm state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of power state power state (on/off) informational informational alerts alerts. monalerts -ipon state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of inventory change inventory change (installed informational alerts components) informational alerts. monalerts -iinv state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of event log informational event log informational alerts. alerts monalerts -iel state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of monalerts -inc state network change network change informational alerts. where state is enabled or informational alerts disabled. Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of user activity user activity informational alerts. informational alerts monalerts -iua state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6).
152
Table 44. monalerts command (continued) Function What it does Command monalerts -icd state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of power module power module informational alerts. informational alerts monalerts -ipm state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number. Valid targets -T system:mm[x] where x is the primary management-module bay number.
Set monitoring state for Enables or disables monitoring of cooling device cooling device informational alerts. informational alerts
Example: To enable monitoring of all critical alerts and event log warning alerts and disable monitoring of all informational alerts, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
monalerts -ca enabled -wel enabled -ia disabled
system:mm[1]> monalerts -ca enabled -wel enabled -ia disabled OK system:mm[1]>
153
monalertsleg command (advanced management module only)

This command displays and configures the legacy alerts that are monitored by the advanced management module.
Table 45. monalertsleg command Function Display monitored legacy alert states What it does Displays the state of all legacy alerts being monitored by the management module. Command monalertsleg Valid targets -T system:mm[x] where x is the primary management-module bay number. monalertsleg -ec state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number.
Set state for enhanced legacy alert categories
Enables or disables enhanced legacy alert categories. v If enhanced legacy alert categories are disabled, alerts are configured using the monalertsleg command. v If enhanced legacy alert categories are enabled, alerts are configured using the monalerts command.
Set monitoring state for Enables or disables monitoring of all critical legacy alerts all critical legacy alerts.
monalertsleg -ca state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6).
Set monitoring state for Enables or disables monitoring of monalertsleg -hdd state hard disk drive critical hard disk drive critical legacy alerts. where state is enabled or legacy alerts disabled. Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of multiple chassis multiple chassis cooling device cooling device critical critical legacy alerts. legacy alerts monalertsleg -mccdf state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of multiple I/O-module multiple I/O-module failure critical failure critical legacy legacy alerts. alerts monalertsleg -miomf state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6).
154
Table 45. monalertsleg command (continued) Function What it does Command monalertsleg -pf state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of critical temperature critical temperature legacy alerts. legacy alerts monalertsleg -ct state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of critical voltage legacy critical voltage legacy alerts alerts monalertsleg -cv state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of VRM failure critical VRM failure critical legacy alerts. legacy alerts monalertsleg -vf state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of invalid configuration invalid configuration critical legacy critical legacy alerts alerts. monalertsleg -ic state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of all warning legacy all warning legacy alerts. alerts monalertsleg -wa state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of single chassis cooling single chassis cooling device device warning legacy warning legacy alerts. alerts monalertsleg -sccdf state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. Valid targets -T system:mm[x] where x is the primary management-module bay number.
Set monitoring state for Enables or disables monitoring of power failure critical power failure critical legacy alerts. legacy alerts
155
Table 45. monalertsleg command (continued) Function What it does Command monalertsleg -wt state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of warning voltage legacy warning voltage legacy alerts alerts monalertsleg -wv state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of monalertsleg -kmsf state KVM/media tray KVM or media tray switching failure where state is enabled or switching failure warning legacy alerts. disabled. warning legacy alerts Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of redundant module redundant module failure warning failure warning legacy legacy alerts. alerts monalertsleg -rmf state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of event log full warning event log 100-percent full warning legacy alerts legacy alerts. monalertsleg -elf state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of all system legacy alerts all system legacy alerts. monalertsleg -sa state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of power on system power on system legacy alerts. legacy alerts monalertsleg -pon state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. Valid targets -T system:mm[x] where x is the primary management-module bay number.
Set monitoring state for Enables or disables monitoring of warning temperature warning temperature legacy alerts. legacy alerts
156
Table 45. monalertsleg command (continued) Function What it does Command monalertsleg -poff state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of predictive failure predictive failure analysis system analysis system legacy legacy alerts. alerts monalertsleg -pfa state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of inventory system inventory system legacy alerts. legacy alerts monalertsleg -inv state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of event log full system event log 75-percent full system legacy alerts legacy alerts. monalertsleg -el state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of network change system network change system legacy legacy alerts alerts. monalertsleg -nc state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of monalertsleg -bt state blade server throttled blade server throttled system legacy where state is enabled or system legacy alerts alerts. disabled. Command use restricted (see Commands and user authority on page 6). Set monitoring state for Enables or disables monitoring of power management power management system legacy system legacy alerts alerts. monalertsleg -pm state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. Valid targets -T system:mm[x] where x is the primary management-module bay number.
Set monitoring state for Enables or disables monitoring of power off system power off system legacy alerts. legacy alerts
157
Table 45. monalertsleg command (continued) Function What it does Command monalertsleg -rl state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). Valid targets -T system:mm[x] where x is the primary management-module bay number.
Set monitoring state for Enables or disables monitoring of remote login system remote login system legacy alerts. legacy alerts
Example: To display legacy alert information, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
monalertsleg
To disable monitoring of enhanced alert categories, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
monalertsleg -ec disabled
system:mm[1]> monalertsleg -ec is currently enabled, monalerts should be used. system:mm[1]> monalertsleg -ec disabled OK system:mm[1]> monalertsleg -ec disabled Critical Alerts -hdd disabled -mccdf disabled -pf disabled -ct disabled -cv disabled -vf disabled -miomf disabled -ic disabled Warning Alerts -sccdf disabled -wt disabled -wv disabled -kmsf disabled -rmf disabled -elf disabled System Alerts -pon disabled -poff disabled -pfa disabled -inv disabled -el disabled -nc disabled -bt disabled -pm disabled -rl disabled system:mm[1]>
158
mt (media tray) command (advanced management module only)

This command sets and displays the blade server that is in control of the BladeCenter unit shared media tray.
Table 46. mt command Function Display media tray owner What it does Command Valid targets -T system
Displays the number of the blade mt server that has media tray ownership and the global local and remote media tray switching states for all blade servers. A blade server that occupies more than one blade bay is identified by the lowest bay number that it occupies. A return value of 0 indicates that no owner is set. Sets a blade server as the media tray owner. mt -b blade_server where blade_server is the blade bay that identifies the blade server. A blade server that occupies more than one blade bay is identified by the lowest bay number that it occupies. A setting of 0 sets no owner. Command use restricted (see Commands and user authority on page 6).
Set media tray owner
-T system
Enable local media tray switching globally
Enable local media tray switching globally for all blade servers.
mt -local enabled Command use restricted (see Commands and user authority on page 6).
-T system
Disable local media tray Disable local media tray switching switching globally globally for all blade servers.
mt -local disabled Command use restricted (see Commands and user authority on page 6).
-T system
Enable remote media tray switching globally
Enable remote media tray switching mt -remote enabled -T system globally for all blade servers. Command use restricted (see Commands and user authority on page 6). Disable remote media tray switching globally for all blade servers. mt -remote disabled Command use restricted (see Commands and user authority on page 6). -T system
Disable remote media tray switching globally
159
Example: To set the media tray owner to the blade server in blade bay 1, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
mt -T system -b 1
To display the media tray owner and the global local and remote media tray switching states for all blade servers, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
mt -T system
system:mm[1]> mt -T system -b 1 OK system:mm[1]> mt -T system -b 1 -local enabled -remote enabled system:mm[1]>
160
nat command (advanced management module only)

This command sets and displays the network address table (NAT) settings for the specified I/O module. Notes: 1. If the nat command is directed to an I/O module that does not support the network address table, the NAT configuration is not supported on this I/O module message is returned. 2. When setting values for an empty row in the network address table, all options must be specified together using a single command.
Table 47. nat command Function Display I/O-module network protocol settings What it does Displays the network port settings for the specified I/O module. Returned values include those in Table 48 on page 163. Command nat Valid targets -T system:switch[x] where x is the I/O-module bay number. -T system:switch[x] where x is the I/O-module bay number.
Reset I/O-module network protocol settings
Resets all network address table nat -reset settings for the specified I/O module to the default values. Default values Command use restricted (see Commands and user are in Table 48 on page 163. authority on page 6). You must activate any changes to the network protocol settings before they take effect. Activates all network port settings nat -activate for the specified I/O module, putting Command use restricted them into effect. (see Commands and user authority on page 6). Sets a protocol name for the specified row in the NAT table for the specified I/O module. nat -index -pn protocol_name
Activate I/O-module network protocol settings
-T system:switch[x] where x is the I/O-module bay number. -T system:switch[x]
Set protocol name for row in I/O-module NAT table
where x is the where: I/O-module bay v index is a number from number. 1 to 10 that corresponds to a row in the NAT table. v protocol_name is FTP, HTTP, HTTPS, NTP, RADIUS, SSH, SNMP, SNMP-TRAP, SYSLOGD, TACACS+, TELNET, or TFTP. Command use restricted (see Commands and user authority on page 6).
161
Table 47. nat command (continued) Function Set protocol ID for row in NAT table What it does Sets a protocol ID for the specified row in the NAT table for the specified I/O module. Command nat -index -pi protocol_id Valid targets -T system:switch[x]
where: where x is the v index is a number from I/O-module bay 1 to 10 that corresponds number. to a row in the NAT table. v protocol_id is TCP or UDP. Command use restricted (see Commands and user authority on page 6).
Set internal port number for row in NAT table
Sets the internal port number for the specified row in the NAT table for the specified I/O module.
nat -index -ip port_number -T system:switch[x] where: where x is the v index is a number from I/O-module bay 1 to 10 that corresponds number. to a row in the NAT table. v port_number is between 1 and 65534, inclusive. Command use restricted (see Commands and user authority on page 6).
Set external port number for row in NAT table
Sets the external port number for the specified row in the NAT table for the specified I/O module.
nat -index -ep port_number
-T system:switch[x]
where x is the where: I/O-module bay v index is a number from number. 1 to 10 that corresponds to a row in the NAT table. v port_number is between 1000 and 65534, inclusive. Command use restricted (see Commands and user authority on page 6).
Set state for row in NAT Enables or disables the specified table row in the NAT table for the specified I/O module.
nat -index -en state
-T system:switch[x]
where: where x is the v index is a number from I/O-module bay 1 to 10 that corresponds number. to a row in the NAT table. v state is enabled or disabled. Command use restricted (see Commands and user authority on page 6).
162
Table 48. Default NAT table values for nat command Index 1 2 3 4 5 6 through 10 Protocol Name HTTP TELNET HTTPS SSH SNMP Protocol ID TCP TCP TCP TCP UDP Internal Port 80 23 43 22 161 Unset External Port State 1080 1023 1043 1022 1161 Enabled Enabled Enabled Enabled Enabled
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 the system:switch[3]> prompt, type
nat
system:switch[3]> nat Index Protocol Name 1 HTTP 2 TELNET 3 HTTPS 4 SSH 5 SNMP system:switch[3]> Protocol ID TCP TCP TCP TCP UDP Internal Port 80 23 43 22 161 External Port 1080 1023 1043 1022 1161 Enabled enabled enabled enabled enabled enabled
163
ntp (network time protocol) command (advanced management module only)

This command configures and displays the management-module network time protocol (NTP) settings.
Table 49. ntp command Function Display management module NTP settings What it does Displays the NTP settings for the specified I/O module. Possible return values are: v -en enabled/disabled v -i ipaddress/hostname v -f update_frequency v -v3en enabled/disabled v -v3 key_info Enables NTP for the management-module. Command ntp Valid targets -T system:mm[x] where x is the primary management-module bay number.
NTP - enable
ntp -en enabled
-T system:mm[x]
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. NTP - disable Disables NTP for the management-module. ntp -en disabled -T system:mm[x]
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. NTP server IP address or hostname - set Checks syntax and sets the IP address or hostname of the NTP server. ntp -i ipaddress/hostname -T system:mm[x]
where ipaddress/hostname where x is the primary is the IP address or management-module hostname of the NTP bay number. server. Command use restricted (see Commands and user authority on page 6).
NTP update frequency - Sets how often the management set module clock is automatically updated by the NTP server.
ntp -f time where time is the NTP update frequency, in minutes with a maximum value of 45000. Command use restricted (see Commands and user authority on page 6).
NTP - enable V3 authentication
Enables V3 authentication between the management-module and the NTP server. Note: The NTP server authentication key must be set, using the ntp -v3 command option, before enabling V3 authentication.
ntp -v3en enabled
-T system:mm[x]
164
Table 49. ntp command (continued) Function NTP - disable V3 authentication What it does Command Valid targets -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number.
Disables V3 authentication between ntp -v3en disabled the management-module and the Command use restricted NTP server. (see Commands and user authority on page 6). Sets the v3 authentication key that the management module uses to access the NTP server. The authentication key contains the following values: v Key index: An NTP server can be configured with one or more key entries. The key index specifies which key the server expects the client to authenticate with. v Key type: The advanced management module supports only the MD5 key type. v Key: The key is an 8-character ASCII string. ntp -v3 key_index key_type key where: v key_index is from 1 to 65535, inclusive. If you enter a value outside this range, an error will be displayed. v key_type is M (MD5). v key is a 8-character ASCII string. Command use restricted (see Commands and user authority on page 6). ntp -synch
NTP server authentication key - set
NTP clock- synchronize Synchronizes the management-module clock with the NTP server. (You must configure a valid NTP server before you can synchronize.)
-T system:mm[x]
Example: To display NTP settings for the management module, while management module 2 is set as the persistent command environment, at the system:mm[2]> prompt, type
ntp
system:mm[2]> ntp -en enabled -i timeserver -f 5 -v3en disabled -v3 Not configured NTP is disabled. system:mm[2]>
165
ping command (advanced management module only)

This command tests the internal communication path between the advanced management module and an I/O module by sending it a ping request.
Table 50. ping command Function Ping I/O module What it does Pings the specified I/O module to test communication. Command ping Valid targets -T system:switch[x]
Example: To ping the I/O module in bay 1, while the BladeCenter unit is set as the persistent command environment, at the system> prompt, type
ping -T switch[1]
system> Pinging Pinging Pinging Pinging system> ping -T switch[1] 192.168.70.55: request 192.168.70.55: request 192.168.70.55: request 192.168.70.55: request timed timed timed timed out out out out
166
pmpolicy command (advanced management module only)

This command displays and sets the power management policies for the BladeCenter unit.
Table 51. pmpolicy command Function Display power management policy Display power management policy for a BladeCenter S unit Display power management policy for domain What it does Command Valid targets -T system -T system
Displays the current power pmpolicy management policy for all domains. Displays both the current and available power management policies for a BladeCenter S unit, that has a single power domain. Displays both the current and available power management policies for the specified power domain in a BladeCenter unit that supports two power domains. Set power management policy for specified power domain. pmpolicy domain where domain is pd. pmpolicy domain where domain is: v pd1 (power domain 1) v pd2 (power domain 2) 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 with oversubscription BladeCenter S units only) v acredov (ac power source redundancy policy, no oversubscription BladeCenter S units only) v redwoperf (power module redundancy, no oversubscription) v redwperf (power module redundancy with oversubscription) v nonred (no power management policy)
-T system
Set power management policy for domain
-T system
Set ac power supply redundancy policy to oversubscription (BladeCenter S units only) Set ac power supply redundancy policy to no oversubscription (BladeCenter S units only)
Sets total allowable power draw to that supplied by one of two independent ac sources, with some oversubscription. Sets total allowable power draw to that supplied by one of two independent ac sources.
pmpolicy -pm acred Command use restricted (see Commands and user authority on page 6). pmpolicy -pm acredov Command use restricted (see Commands and user authority on page 6).
-T system
-T system
167
Table 51. pmpolicy command (continued) Function Set power module redundancy to no oversubscription What it does Sets total allowable power draw to one less than the number of power modules, with no oversubscription. For environments with single ac power feeds. Sets total allowable power draw to a certain amount above the rated capacity of the BladeCenter unit. Allows power oversubscription. Blade servers may throttle if a power module fails. Permits total allowable power draw to equal what all power modules can provide. Allowable power draw is not managed. This does not provide any protection against power module failure. Command pmpolicy -pm redwoperf Command use restricted (see Commands and user authority on page 6). pmpolicy -pm redwperf Command use restricted (see Commands and user authority on page 6). pmpolicy -pm nonred Command use restricted (see Commands and user authority on page 6). -T system -T system Valid targets -T system
Set power module redundancy to oversubscription
Set power management to none
Example: To view the current policy and the available policies for a power domain 1, while the BladeCenter unit is set as the persistent command environment, at the system> prompt, type pmpolicy pdx Note: x can be either blank or 1 for the BladeCenter S unit, that has a single power domain. x can be either 1 or 2 for other BladeCenter units, that have two power domains. The following example shows a policy applied by this command, and the information that is returned by the advanced management module after the policy is applied.
system> pmpolicy -pm acred OK system> pmpolicy Power Domain -------------Power Management Policy: AC Power Redundancy (acred) Description: Intended for dual AC power feeds into the chassis. Total allowed power draw is limited to that of half the number of power supplies. This is the most conservative approach. When the chassis is correctly wired with dual AC power feeds, one AC feed can fail without affecting your blade server operation. (N+N no OVS) Power Supply Failure Limit: 2 Maximum Power Limit (Watts)}: 2400 Your Estimated Utilization: 70% NOTE: Power Supply Failure Limit: This is the maximum number of power supplies that can fail in your chassis while still providing redundancy.
168
Your Estimated Utilization: The estimated utilization is based on the maximum worse case and measured power based on the capability of all components. system>
169
portcfg command (advanced management module only)

This command configures and displays the settings for the advanced management-module serial port.
Table 52. portcfg command Function What it does Command Valid targets -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x]
Display Displays the current configuration of portcfg -com1 management-module the management-module serial port. serial port configuration Possible return values are: v -b baud_rate v -p parity v -s stop_bits Set managementChecks syntax and sets the baud module serial port baud (communications) rate of the rate management-module serial port. portcfg -com1 -b baud_rate
where x is the primary where baud_rate is 2400, management-module 4800, 9600, 19200, 38400, bay number. or 57600. Command use restricted (see Commands and user authority on page 6).
Set managementmodule serial port parity
Checks syntax and sets the parity of the management-module serial port.
portcfg -com1 -p parity where parity is none, odd, even, mark, or space. Command use restricted (see Commands and user authority on page 6).
Set managementmodule serial port stop bits
Checks syntax and sets the number portcfg -com1 -s stop_bits of stop bits for the where stop_bits is 1 or 2. management-module serial port. Command use restricted (see Commands and user authority on page 6).
Example: To display the configuration for the management-module serial port, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
portcfg -com1
To set the baud rate for the management-module serial port to 9600, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
portcfg -com1 -b 9600
170
system:mm[1]> portcfg -com1 -b 2400 -p odd -s 1 system:mm[1]> portcfg -com1 -b 9600 OK system:mm[1]>
171
ports command (advanced management module only)

This command sets and displays the network port configuration settings for the advanced management module.
Table 53. ports command Function Display network port settings What it does Command Valid targets -T system:mm[x] where x is the primary management-module bay number.
Displays the network port settings ports for the management module. Returned values are: v -ftpp FTP_port_num v -ftpdp FTP_data_port_num v -httpp HTTP_port_num v -httpsp HTTPS_port_num v -kvmp KVM_port_num v -rdp rem_dsk_port_num v -rdocp rem_dsk_on_chp_port_num v -sdsp stor_des_stor_port v -slpp SLP_port_num v -smashsp secSMASH_SSH_prt_num v -smashtp SMASH_telnet_port_num v -snmpap SNMP_agent_port_num v -snmptp SNMP_traps_port_num v -sshp SSH_port_num v -tcmp TCP_cmd_md_port v -telnetp _Telnet_port_num v -tftpp TFTP_port_num v -ftpe FTP_state v -httpse HTTPS_port_state v -kvme KVM_state v -ntpe NTP_state v -smashse sec_SMASH_SSH_state v -smashte SMASH_telnet_state v -snmp1ae SNMPv1_agent_state v -snmp3ae SNMPv3_agent_state v -snmpte SNMP_traps_state v -sshe SSH_port_state v -tcme TCP_cmd_mode_state v -telnete Telnet_port_statev -tftpe TFTP_state v -ftpt FTP_timeout v -tcmt TCP_cmd_mode_timeout v -telnett Telnet_port_timeout Displays the management module ports that are currently open. ports -open
Display open management module ports
172
Table 53. ports command (continued) Function Reset network port settings What it does Resets all network port settings for the management module to the default values. Default values are: v -ftpp: 21 v -ftpdp: 20 v -httpp: 80 v -httpsp: 443 v -kvmp: 3900 v -rdp: 1044 v -rdocp: 1045 v -sdsp: 1046 v -slpp: 427 v -tcmp: 6090 v -snmpap: 161 v -snmptp: 162 v -sshp: 22 v -telnetp: 23 v -tftpp: 69 Sets the port number for the management module FTP port. Command ports -reset Valid targets -T system:mm[x]
Set FTP port number
ports -ftpp FTP_port_num
-T system:mm[x]
where FTP_port_num is where x is the primary from 1 to 65535, inclusive. management-module If you enter a value bay number. outside this range, an error will be displayed. Command use restricted (see Commands and user authority on page 6). Set FTP data port number Sets the port number for the management module FTP data port. ports -ftpdp FTP_data_port_num -T system:mm[x]
where x is the primary where management-module FTP_data_port_num is bay number. from 1 to 65535, inclusive. If you enter a value outside this range, an error will be displayed. Command use restricted (see Commands and user authority on page 6).
Set HTTP port number
Sets the port number for the management module HTTP port.
ports -httpp HTTP_port_num
-T system:mm[x]
where x is the primary where HTTP_port_num is management-module from 1 to 65535, inclusive. bay number. If you enter a value outside this range, an error will be displayed. Command use restricted (see Commands and user authority on page 6).
173
Table 53. ports command (continued) Function What it does Command ports -httpsp HTTPS_port_num Valid targets -T system:mm[x]
Set HTTPS port number Sets the port number for the management module HTTPS port.
where x is the primary where HTTPS_port_num is management-module from 1 to 65535, inclusive. bay number. If you enter a value outside this range, an error will be displayed. Command use restricted (see Commands and user authority on page 6). Set KVM port number Sets the port number for the management module KVM port. ports -kvmp KVM_port_num -T system:mm[x]
where x is the primary where KVM_port_num is management-module from 1 to 65535, inclusive. bay number. If you enter a value outside this range, an error will be displayed. Command use restricted (see Commands and user authority on page 6). Set remote disk port number Sets the port number for the management module remote disk port. ports -rdp rem_dsk_port_num where rem_dsk_port_num is from 1 to 65535, inclusive. If you enter a value outside this range, an error will be displayed. Command use restricted (see Commands and user authority on page 6). Set remote disk on card Sets the port number for the port number management module remote disk on card port. ports -rdocp rem_on_card_port_num -T system:mm[x] -T system:mm[x] where x is the primary management-module bay number.
where x is the primary where management-module rem_on_card_port_num is bay number. from 1 to 65535, inclusive. If you enter a value outside this range, an error will be displayed. Command use restricted (see Commands and user authority on page 6).
174
Table 53. ports command (continued) Function Set storage description storage port What it does Command Valid targets -T system:mm[x]
Sets the storage description storage ports -sdsp port. stor_des_stor_port_num
where x is the primary where management-module stor_des_stor_port_num is bay number. from 1 to 65535, inclusive. If you enter a value outside this range, an error will be displayed. Set SLP port number Sets the SLP port number. ports -slpp SLP_port_num -T system:mm[x]
where SLP_port_num is where x is the primary from 1 to 65535, inclusive. management-module If you enter a value bay number. outside this range, an error will be displayed. Set SMASH Telnet port number Sets the port number for the management module SMASH command-line processor over Telnet port. ports -smashtp SMASH_telnet_port_num where SMASH_telnet_port_num is from 1 to 65535, inclusive. If you enter a value outside this range, an error will be displayed. Command use restricted (see Commands and user authority on page 6). Set SNMP agent port number Sets the port number for the management module SNMP agent port. ports -snmpap SNMP_agent_port_num -T system:mm[x] -T system:mm[x] where x is the primary management-module bay number.
where x is the primary where management-module SNMP_agent_port_num is bay number. from 1 to 65535, inclusive. If you enter a value outside this range, an error will be displayed. Command use restricted (see Commands and user authority on page 6).
Set SNMP traps port number
Sets the port number for the management module SNMP traps port.
ports -snmptp SNMP_traps_port_num
-T system:mm[x]
where x is the primary where management-module SNMP_traps_port_num is bay number. from 1 to 65535, inclusive. If you enter a value outside this range, an error will be displayed. Command use restricted (see Commands and user authority on page 6).
175
Table 53. ports command (continued) Function Set command mode port number What it does Sets the TCP command mode port number Command ports -tcmp TCP_cmd_md_port_num where TCP_cmd_md_port_num is from 1 to 65535, inclusive. If you enter a value outside this range, an error will be displayed. Command use restricted (see Commands and user authority on page 6). Set SSH port number Sets the port number for the management module SSH port. ports -sshp SSH_port_num -T system:mm[x] where SSH_port_num is where x is the primary from 1 to 65535, inclusive. management-module If you enter a value bay number. outside this range, an error will be displayed. Command use restricted (see Commands and user authority on page 6). Set Telnet port number Sets the port number for the management module Telnet port. ports -telnetp Telnet_port_num -T system:mm[x] Valid targets -T system:mm[x] where x is the primary management-module bay number.
where x is the primary where Telnet_port_num is management-module from 1 to 65535, inclusive. bay number. If you enter a value outside this range, an error will be displayed. Command use restricted (see Commands and user authority on page 6). Set TFTP port number Sets the port number for the management module TFTP port. ports -tftpp TFTP_port_num -T system:mm[x]
where x is the primary where TFTP_port_num is management-module from 1 to 65535, inclusive. bay number. If you enter a value outside this range, an error will be displayed. Command use restricted (see Commands and user authority on page 6). Enable FTP Enables FTP for the management module. ports -ftpe on -T system:mm[x]
176
Table 53. ports command (continued) Function Disable FTP What it does Disables FTP for the management module. Command ports -ftpe off Valid targets -T system:mm[x]
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. Enable HTTPS port Enables the management module HTTPS port. ports -httpse on -T system:mm[x]
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. Disable HTTPS port Disables the management module HTTPS port. ports -httpse off -T system:mm[x]
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. Set KVM port state Sets the KVM port state to on or off. ports -kvme state where state is v on v off Enable NTP Enables NTP for the management module. ports -ntpe on -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x]
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. Disable NTP Disables NTP for the management module. ports -ntpe off -T system:mm[x]
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. Enable secure SMASH over SSH Enables the secure SMASH command-line processor over SSH for the management module. ports -smashse on -T system:mm[x]
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. ports -smashse off -T system:mm[x]
Disable secure SMASH over SSH
Disables the secure SMASH command-line processor over SSH for the management module.
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. ports -smashte on -T system:mm[x]
Enable SMASH over Telnet
Enables SMASH command-line processor over Telnet for the management module.
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. ports -smashte off -T system:mm[x]
Disable SMASH over Telnet
Disables SMASH command-line processor over Telnet for the management module.
177
Table 53. ports command (continued) Function Enable SNMPv1 agent What it does Enables the SNMPv1 agent for the management module. Command ports -snmp1ae on Valid targets -T system:mm[x]
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. Disable SNMPv1 agent Disables the SNMPv1 agent for the management module. ports -snmp1ae off -T system:mm[x]
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. Enable SNMPv3 agent Enables the SNMPv3 agent for the management module. ports -snmp3ae on -T system:mm[x]
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. Disable SNMPv3 agent Disables the SNMPv3 agent for the management module. ports -snmp3ae off -T system:mm[x]
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. Enable SNMP traps Enables the SNMP traps for the management module. ports -snmpte on -T system:mm[x]
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. Disable SNMP traps Disables the SNMP traps for the management module. ports -snmpte off -T system:mm[x]
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. Enable SSH port Enables the management module SSH port. ports -sshe on -T system:mm[x]
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. Disable SSH port Disables the management module SSH port. ports -sshe off -T system:mm[x]
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. Enable TCP command mode Enables the TCP command mode for the management module. ports -tcme on -T system:mm[x]
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. Disable TCP command mode Disables the TCP command mode for the management module. ports -tcme off -T system:mm[x]
178
Table 53. ports command (continued) Function Turn TCP command mode on or off What it does Command Valid targets -T system:mm[x] where x is the primary management-module bay number.
Turns the TCP command mode on ports -tcme port_mode or off, or sets the maximum number where port_mode is on of connections explicitly. (one connection), off (no Note: connections), or a number v The maximum number of between 0 and 20, connections can be set explicitly inclusive, that indicates the (0-20), or the port can be turned maximum number of TCP on (1 connection) or off (0 session connections. connections). v Any number of connections (1 through 20) displays a status of ON. Zero connections displays a status of OFF. Command use restricted (see Commands and user authority on page 6). ports -telnete on
Enable Telnet port
Enables the management module Telnet port.
-T system:mm[x]
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. Disable Telnet port Disables the management module Telnet port. ports -telnete off -T system:mm[x]
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. Enable TFTP Enables TFTP for the management module. ports -tftpe on -T system:mm[x]
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. Disable TFTP Disables TFTP for the management ports -tftpe off module. Command use restricted (see Commands and user authority on page 6). Sets the FTP timeout value for the management module. ports -ftpt timeout where timeout is from 0 seconds (no timeout) to 4294295967 seconds, inclusive. Command use restricted (see Commands and user authority on page 6). Set TCP Sets the TCP command-mode command-mode timeout timeout value for the management module. ports -tcmt timeout where timeout is from 0 seconds (no timeout) to 4294295967 seconds, inclusive. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number.
Set FTP timeout
179
Table 53. ports command (continued) Function Set Telnet port timeout What it does Sets the Telnet port timeout value for the management module. Command ports -telnett timeout where timeout is from 0 seconds (no timeout) to 4294295967 seconds, inclusive. Command use restricted (see Commands and user authority on page 6). Valid targets -T system:mm[x] where x is the primary management-module bay number.
Example: To disable FTP for the management module, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
ports -ftpe off
To display the management module network port settings, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
ports
system:mm[1]> ports -ftpe off These configuration changes will become active after the next reset of the MM. system:mm[1]> ports -ftpp 21 -ftpdp 20 -httpp 80 -httpsp 443 -kvmp 3900 -rdp 1044 -rdocp 1045 -smashsp 50022 -smashtp 50023 -snmpap 161 -snmptp 162 -sshp 22 -telnetp 23 -tftpp 69 -ftpe off -httpse off -ntpe off -smashse off -smashte off -ftpp 21 -snmp1ae on -snmp3ae on -snmpte on -sshe off -tcme on -telnete on -tftpe off -ftpt 60 -tcmt 0 -telnett 10000 system:mm[1]>
180
power command
This command turns on and turns off blade servers and I/O (switch) modules. For advanced management modules installed in BladeCenter HT units, it also turns on and turns off the alarm panel module and network clock module.
Table 54. power command Function Power on What it does Turns on the specified command target. Command power -on Valid targets -T system:blade[x]
-T system:switch[x] Command use restricted (see Commands and user -T system:tap (for authority on page 6). advanced management modules installed in BladeCenter HT units only) -T system:ncc[x] (for advanced management modules installed in BladeCenter HT units only) where x is the blade server, I/O (switch) module bay, or network clock module number.
Power on to command console
Opens a command console with an SOL session when the specified blade server is turned on.
power -on -c
-T system:blade[x]
Command use restricted where x is the blade (see Commands and user server bay number. authority on page 6). power -off -T system:blade[x]
Power off
Turns off the specified command target.
-T system:switch[x] Command use restricted (see Commands and user -T system:tap (for authority on page 6). advanced management modules installed in BladeCenter HT units only) -T system:ncc[x] (for advanced management modules installed in BladeCenter HT units only) where x is the blade server, I/O (switch) module bay, or network clock module number.
Shutdown and power off blade server
Shuts down the operating system and turns off the specified blade server.
power -softoff
-T system:blade[x]
Command use restricted where x is the blade (see Commands and user server number. authority on page 6).
181
Table 54. power command (continued) Function Power cycle What it does Cycles power for the specified blade server or I/O (switch) module. If the blade server or I/O (switch) module is off, it will turn on. If the blade server or I/O (switch) module is on, it will turn off and then turn on. Cycles power for the specified blade server. If the blade server is off, it opens a command console with an SOL session when it is turned on. If the blade server is on, it will turn off and then turn on. Command power -cycle Valid targets -T system:blade[x]
-T system:switch[x] Command use restricted (see Commands and user where x is the blade authority on page 6). server or I/O (switch) module bay number. power -cycle -c -T system:blade[x]
Power cycle to command console
Command use restricted where x is the blade (see Commands and user server bay number. authority on page 6). -T system:blade[x] -T system:switch[x] where x is the blade server or I/O (switch) module bay number. -T system
Display power state
Displays the current power state for power -state the specified blade server or I/O (switch) module. Possible return values are off, on, standby, or hibernate. Enables Wake on LAN globally for all blade servers. power -wol enabled Command use restricted (see Commands and user authority on page 6).
Enable Wake on LAN globally
Disable Wake on LAN globally
Disables Wake on LAN globally for all blade servers.
power -wol disabled Command use restricted (see Commands and user authority on page 6).
-T system
Enable Wake on LAN for blade server
Enables Wake on LAN for the specified blade server.
power -wol enabled
-T system:blade[x]
Command use restricted where x is the blade (see Commands and user server bay number. authority on page 6). Disable Wake on LAN for blade server Disables Wake on LAN for the specified blade server. power -wol disabled -T system:blade[x]
Command use restricted where x is the blade (see Commands and user server bay number. authority on page 6). Enable local power control globally Enables local power control globally power -local enabled -T system for all blade servers. Command use restricted (see Commands and user authority on page 6). Disables local power control globally for all blade servers. power -local disabled Command use restricted (see Commands and user authority on page 6). Enable local power control for blade server Enables local power control for the specified blade server. power -local enabled -T system:blade[x] -T system
Disable local power control globally
182
Table 54. power command (continued) Function Disable local power control for blade server What it does Disables local power control for the specified blade server. Command power -local disabled Valid targets -T system:blade[x]
Command use restricted where x is the blade (see Commands and user server bay number. authority on page 6). Enable fast POST for I/O module Enables fast POST globally for the specified I/O module. power -fp enabled -T system:switch[x]
Command use restricted where x is the I/O (see Commands and user (switch) module bay authority on page 6). number. Disable fast POST for I/O module Disables fast POST globally for the specified I/O module. power -fp disabled -T system:switch[x]
Command use restricted where x is the I/O (see Commands and user (switch) module bay authority on page 6). number. Display POST status for Displays the POST status for the power -state -post I/O (switch) module specified I/O (switch) module. If the command is run while POST is in progress, it returns the level of POST that is currently in process. If the command is run after POST is complete, it displays one of the following return values: v The POST results could not be read. message displays if there was an internal error during POST. v The POST results not complete: hex_code message displays if POST results are not available after POST completes. v If POST returns valid results, one of the following messages displays: 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 the above conditions is true. Where hex_code is a hexadecimal code. See the documentation that comes with your I/O module for information. Note: This command option is not supported for serial concentrator I/O (switch) modules. -T system:switch[x] where x is the I/O (switch) module bay number.
183
Example: To display the power state for the blade server in blade bay 5, while this blade server is set as the persistent command environment, at the system:blade[5]> prompt, type
power -state
To turn on the blade server in blade bay 5, while this blade server is set as the persistent command environment, at the system:blade[5]> prompt, type
power -on
To display the power state for the blade server in blade bay 5 again, while this blade server is set as the persistent command environment, at the system:blade[5]> prompt, type
power -state
system:blade[5]> power -state Off system:blade[5]> power -on OK system:blade[5]> power -state On system:blade[5]>
184
read command (advanced management module only)

This command restores the management-module configuration that was previously saved 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 (advanced management module only) on page 263.
Table 55. read command Function What it does Command Valid targets -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x]
Display Displays the automatic configuration read management-module setting (-auto command option) of automatic configuration the management module. setting Restore management-module configuration from BladeCenter unit midplane Restore management-module configuration from file (no encryption) Restores the management-module configuration from an image that was previously saved to the BladeCenter unit midplane. Restores the management-module configuration from an image that was previously saved to a file while data encryption was not enabled for the BladeCenter unit. read -config chassis
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. read -config file -l filename -T system:mm[x] -i ip_address where x is the primary where: management-module v filename is the name of bay number. the configuration file. v ip_address is the IP address of TFTP server where the configuration file is located. Command use restricted (see Commands and user authority on page 6).
Restore management-module configuration from file (encryption)
Restores the management-module configuration from an image that was previously saved to a file while data encryption was enabled for the BladeCenter unit. Note: When a configuration file was created with a pass-phrase (encryption enabled), if this configuration file is restored on the same management module, the pass-phrase entered during restoration is ignored.
read -config file -l filename -T system:mm[x] -i ip_address -p where x is the primary passphrase management-module where: bay number. v filename is the name of the configuration file. v ip_address is the IP address of TFTP server where the configuration file is located. v passphrase is the double-quote delimited pass-phrase that was used to save the original configuration file. Maximum pass-phrase length is 1600 characters. Command use restricted (see Commands and user authority on page 6).
185
Table 55. read command (continued) Function Enable automatic management-module configuration What it does Enables automatic configuration of the management module, based on settings stored in the BladeCenter unit midplane, when the management module is installed. Note: The -auto option can only be used when the management-module configuration was stored to the BladeCenter unit midplane. Disables automatic configuration of the management module, based on settings stored in the BladeCenter unit midplane, when the management module is installed. Command read -config chassis -auto on Valid targets -T system:mm[x]
where x is the primary Command use restricted management-module (see Commands and user bay number. authority on page 6).
Disable automatic management-module configuration
read -config chassis -auto off
-T system:mm[x]
where x is the primary Command use restricted management-module (see Commands and user bay number. authority on page 6).
Example: To restore the management-module configuration from an image previously saved to the BladeCenter unit chassis, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
read -config chassis
system:mm[1]> read -config chassis OK Configuration restore from the chassis was successful Restart the MM for the new settings to take effect system:mm[1]>
186
remotechassis command (advanced management module only)

This command displays and manages the list of BladeCenter units that the management module discovers on the network. Note: The advanced management module that runs the remotechassis command is also included in all lists.
Table 56. remotechassis command Function Display complete list What it does Displays a list of all BladeCenter units that the management module discovers on the network. The list includes the following information about each BladeCenter unit: v Name v IP address v Status v Firmware level v Type v Serial number v FRU number v Chassis serial number v Chassis FRU number v Chassis machine-type model (MTM) v Chassis UUID Displays a list of names for BladeCenter units that the management module discovers on the network. The list is grouped by health status. Displays a list of BladeCenter units that the management module discovers on the network, filtered by the specified IP address. The list includes the following information about each BladeCenter unit: v Name v IP address v Status v Firmware level v Type v Serial number v FRU number v Chassis serial number v Chassis FRU number v Chassis machine-type model (MTM) v Chassis UUID Command remotechassis Valid targets -T system:mm[x] where x is the primary management-module bay number.
Display list grouped by health status
remotechassis -health
Display list filtered by IP address
remotechassis -ip ip_address where ip_address is an IP address pattern that uses the asterisk (*) as a wildcard (for example; 201.47.123.*).
187
Table 56. remotechassis command (continued) Function Display list filtered by name What it does Displays a list of BladeCenter units that the management module discovers on the network, filtered by the specified name. The list includes the following information about each BladeCenter unit: v Name v IP address v Status v Firmware level v Type v Serial number v FRU number v Chassis serial number v Chassis FRU number v Chassis machine-type model (MTM) v Chassis UUID Clears the list of BladeCenter units that the management module discovered on the network. Command remotechassis -name name where name is a name pattern that uses the asterisk (*) as a wildcard (for example; WebServer*). Valid targets -T system:mm[x] where x is the primary management-module bay number.
Clear list
remotechassis -clear
Example: To list all BladeCenter units on the network with a name starting with WebServer, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
remotechassis -name WebServer*
system:mm[1]> remotechassis -name WebServer* Running chassis discovery... -----------------------------------------------Name: WebServer001 IP: 145.48.204.212 Status: normal Firmware: BPET25L,CNETMNUS.PKT,01-08-07,37,1 Type: management-module Serial: 0J1M9E585630 FRU: 25R5777 Chassis Serial: 23A2343 Chassis FRU: 25R5780R5780 Chassis MTM: 885222Z Chassis UUID: 4E349451FA8011D9B10C89E0183AD13D -----------------------------------------------Name: WebServer002 IP: 145.48.204.222 Status: normal Firmware: BPET25L,CNETMNUS.PKT,01-08-07,37,1 Type: management-module Serial: 0J1M9E585656 FRU: 25R5777 Chassis Serial: 23A2356 Chassis FRU: 25R5780R5780
188
Chassis MTM: 885222Z Chassis UUID: 4E325951FA8011D9B86C89E0183AD02D -----------------------------------------------system:mm[1]>
189
reset command
This command resets blade servers, blade server integrated system management processors (service processors), I/O (switch) modules, or the primary management module. For advanced management modules installed in BladeCenter HT units, it also resets the multiplexer expansion module.
Table 57. reset command Function Reset What it does Performs an immediate reset and restart of the specified device. Command reset Valid targets -T system:blade[x]
-T system:switch[x] Command use restricted (see Commands and user -T system:blade[x]:sp authority on page 6). where x is the blade server or I/O (switch) module bay number. reset -T system:mm[x]
Reset primary management module
Performs an immediate reset and restart of the primary management module.
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. reset -standby -T system:mm[x]
Reset standby management module (advanced management module only)
Performs an immediate reset of the standby management module.
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. Note: Even though this command is resetting the standby management module, it still must be specify the primary management module as the command target. Opens a command console with an SOL session when the specified blade server is reset. reset -c -T system:blade[x]
Reset blade server to command console
Command use restricted where x is the blade (see Commands and user server bay number. authority on page 6). reset -f -T system:mm[x]
Reset with failover(does Resets the specified command not apply to the target, enabling failover if a BladeCenter S unit) redundant component for the command target is present. An error message is displayed if you try to failover a management module when a redundant management module is not installed or if the firmware in the one of the management modules is updating.
Command use restricted -T system:mux[x] (for (see Commands and user advanced management authority on page 6). modules in BladeCenter HT units only) where x is the primary management-module bay or multiplexer expansion module number.
190
Table 57. reset command (continued) Function Reset management module with forced failover (advanced management modules only) What it does Resets the primary management module with failover to the standby management module. An error message is displayed if you try to force failover for a management module when a redundant management module is not installed or if the firmware in the primary management module is updating. Command reset -force Valid targets -T system:mm[x]
Reset I/O (switch) module with standard diagnostics
Performs an immediate reset and reset -std restart of the specified device, running standard diagnostics on the Command use restricted I/O (switch) module after it restarts. (see Commands and user authority on page 6). Running the reset -std command gives the same result as running the reset command on a I/O (switch) module. Performs an immediate reset and restart of the specified device, running extended diagnostics on the I/O (switch) module after it restarts. Performs an immediate reset and restart of the specified device, running full diagnostics on the I/O (switch) module after it restarts. Performs an immediate reset and restart of the specified blade server. Command results depend on the blade server model that is specified: v For a P6 blade server, this option is not available. v For a JS20 blade server, the command performs an immediate reset and restart of the specified blade server with non-maskable interrupt (NMI). v For all other blade servers, the command performs an immediate reset and restart of the specified blade server. reset -exd
-T system:switch[x] where x is the I/O (switch) module bay number.
Reset I/O (switch) module with extended diagnostics
-T system:switch[x]
Command use restricted where x is the I/O (see Commands and user (switch) module bay authority on page 6). number. reset -full -T system:switch[x]
Reset I/O (switch) module with full diagnostics
Command use restricted where x is the I/O (see Commands and user (switch) module bay authority on page 6). number. reset -sft -T system:blade[x]
Restart blade server with NMI
191
Table 57. reset command (continued) Function Restart blade server and clear NVRAM What it does Performs an immediate reset and restart of the specified blade server. Command results depend on the blade server model that is specified: v For a P6 blade server, this option is not available. v For a JS20 blade server, the command performs an immediate reset and restart of the specified JS20 blade server and clears all settings stored in non-volatile memory (NVRAM). v For all other blade servers, the command performs an immediate reset and restart of the specified blade server. Performs an immediate reset and restart of the specified blade server. Command results depend on the blade server model that is specified: v For a P6 blade server, this option is not available. v For a JS20 blade server, the command performs an immediate reset and restart of the specified JS20 blade server and runs diagnostics. v For all other blade servers, the command performs an immediate reset and restart of the specified blade server. Performs an immediate reset and restart of the specified blade server. Command results depend on the blade server model that is specified: v For a P6 blade server, this option is not available. v For a JS20 blade server, the command performs an immediate reset and restart of the specified JS20 blade server and runs diagnostics using the default boot sequence configured for the blade server. v For all other blade servers, the command performs an immediate reset and restart of the specified blade server. Command reset -clr Valid targets -T system:blade[x]
Restart blade server and run diagnostics
reset -dg
-T system:blade[x]
Restart blade server and run diagnostics using default boot sequence
reset -ddg
-T system:blade[x]
192
Example: To reset the service processor on the blade server in blade bay 5, while the BladeCenter unit is set as the persistent command environment, at the system> prompt, type
reset

system> reset -T blade[5]:sp OK system>
193
sddump command (advanced management module only)

This command initiates a dump of service data from blade servers that support this function.
Table 58. sddump command Function Dump service data What it does Dumps service data of the specified type from the specified blade server target. Note: Data dumps can be initiated, but are not collected, from the advanced management module. Command sddump -init type where type is: v sp for a service processor data dump. v pf for a platform data dump. v pt for a partition data dump. Command use restricted (see Commands and user authority on page 6). Valid targets -T system:blade[x] where x is the blade server bay number.
Example: To initiate a data dump from the service processor of the blade server in bay 2, while this blade server is set as the persistent command environment, at the system:blade[2]> prompt, type
sddump -init sp
system:blade[2]> sddump -init sp OK system:blade[2]>
194
security command (advanced management module only)

This command enables and displays the state of the data encryption feature for sensitive information stored in the advanced management module, such as passwords and keys. Once enabled, the security feature can not be disabled without resetting all management module settings to their default configuration.
Table 59. security command Function Display management module security setting What it does Displays the security setting for management module data encryption (on or off). Command security Valid targets -T system:mm[x] where x is the primary management-module bay number. security -e -T system:mm[x]
Enable data encryption for management module
Enables data encryption for the management module. Attention: If you enable data encryption, you can not disable it without resetting the management module to the default configuration.
Example: To enable data encryption for the management module, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
security -e
To display the data encryption setting for the management module, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
security
system:mm[1]> security -e OK system:mm[1]> security -e on system:mm[1]>
195
service command (advanced management module only)

This command configures and displays the management-module service setting.
Table 60. service command Function Display service setting What it does Displays the service setting for technician debug of the advanced management module with a USB key (enable or disable). Configure service setting to enable technician debug of the advanced management module with a USB key. Command service Valid targets -T system:mm[x] where x is the primary management-module bay number. service -enable -T system:mm[x]
Enable technician debug
Disable technician debug
Configure service setting to disable service -disable (default setting) technician debug of the advanced management module Command use restricted (see Commands and user with a USB key. authority on page 6).
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 the system:mm[1]> prompt, type
service -enable
To display the service setting of the advanced management module, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
service
system:mm[1]> service -enable OK system:mm[1]> service Debug with USB key: Enabled system:mm[1]>
196
shutdown command (advanced management module only)

This command forces a blade server to shut down.
Table 61. shutdown command Function Shutdown blade server What it does Command Valid targets
Forces a shutdown for the specified shutdown -f -T system:blade[x] blade server. Command use restricted where x is the blade (see Commands and user server bay number. authority on page 6).
Example: To force a shutdown for the blade server in blade bay 5, while this blade server is set as the persistent command environment, at the system:blade[5]> prompt, type
shutdown -f
system:blade[5]> shutdown -f OK system:blade[5]>
197
slp command (advanced management module only)

This command sets and displays the service location protocol (SLP) settings for the management module.
Table 62. slp command Function Display management-module SLP settings What it does Displays the SLP settings for the primary management module. Returned values are: v -t address_type v -i multicast_addr Sets the SLP address type for the primary management module. Command slp Valid targets -T system:mm[x] where x is the primary management-module bay number. slp -t address_type where address_type is multicast or broadcast. Command use restricted (see Commands and user authority on page 6). Set managementmodule SLP multicast address Sets the SLP multicast address for the primary management module. slp -i multicast_addr where multicast_addr is the multicast IP address. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number.
Set managementmodule SLP address type
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 the system:mm[1]> prompt, type
slp -t multicast
To display the SLP settings of the advanced management module, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
slp
system:mm[1]> slp -t multicast OK system:mm[1]> slp -t multicast -i 255.255.255.255 system:mm[1]>
198
smtp command
This command configures and displays the management-module SMTP settings.
Table 63. smtp command Function Display SMTP server host name or IP address What it does Displays the SMTP server host name or IP address. Command smtp Valid targets -T system:mm[x] where x is the primary management-module bay number. Checks syntax and sets the server host name or IP address. smtp -s hostname/ip_address where hostname/ip_address is the host name or IP address of the server. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number.
Server host name or IP address - set
Example: To set the SMTP server host name to us.ibm.com, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
smtp -s us.ibm.com
To display the SMTP configuration, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
smtp
system:mm[1]> smtp -s us.ibm.com OK system:mm[1]> smtp -s us.ibm.com system:mm[1]>
199
snmp command
This command configures and displays the management-module SNMP settings.
Table 64. snmp command Function Display SNMP configuration of management module What it does Displays the current SNMP configuration of the management module. Command snmp Valid targets -T system:mm[x] where x is the primary management-module bay number. snmp -a -on Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number.
SNMPv1 agent enable
Enables the management-module SNMPv1 agent. Note: SNMPv1 community setup required (see the snmp -cx commands, starting on page bc_cli_snmp/#bc_cli_snmp-a-on, for information). Disables the management-module SNMPv1 agent.
SNMPv1 agent disable
snmp -a -off Command use restricted (see Commands and user authority on page 6).
-T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number.
SNMPv3 agent enable
Enables the management-module SNMPv3 agent. Note: SNMPv3 user setup required. See the users command for your management module for information: v 239 v 249 Disables the management-module SNMPv3 agent.
snmp -a3 -on Command use restricted (see Commands and user authority on page 6).
SNMPv3 agent disable
snmp -a3 -off Command use restricted (see Commands and user authority on page 6).
-T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x]
SNMP traps - enable
Enables the management-module SNMP traps.
snmp -t -on Command use restricted (see Commands and user authority on page 6).
SNMP traps - disable
Disables the management-module SNMP traps.
snmp -t -off Command use restricted (see Commands and user authority on page 6).
SNMP community 1 name - set
Sets the name of community 1.
snmp -c1 name
where name is a descriptive where x is the primary name of community 1. management-module bay number. Command use restricted (see Commands and user authority on page 6).
200
Table 64. snmp command (continued) Function SNMP community 1 first host name or IP address - set What it does Checks syntax and sets the first host name or IP address of community 1. Note: The first IP address of the first community can be set to 0.0.0.0 if the community access type is set to GET (for all management module types) or SET (advanced management module only). Sets the access type for community 1 to SET. Note: With the access type of SET, anyone can query the management information base (MIB) and set MIB values. Using 0.0.0.0 IP address with SET access allows open access to the management module for write (SET) operations. A 0.0.0.0 address cannot be a trap receiver. Sets the access type for community 1 to GET. Note: With the access type of GET, anyone can query the MIB. Using 0.0.0.0 IP address with GET access allows open access to the management module for read (GET). A 0.0.0.0 address cannot be a trap receiver. Command snmp -c1i1 hostname/ip_address Valid targets -T system:mm[x]
where x is the primary where hostname/ip_address management-module is the first host name or IP bay number. address of community 1. Command use restricted (see Commands and user authority on page 6). snmp ca1 set -c1i1 0.0.0.0 -T system:mm[x] Command use restricted (see Commands and user authority on page 6). where x is the primary management-module bay number.
SNMP Community 1, first host name - set access to SET(wildcard)
SNMP Community 1, first host name or IP address - set access to GET (wildcard)
snmp ca1 get -c1i1 0.0.0.0 -T system:mm[x] Command use restricted (see Commands and user authority on page 6). where x is the primary management-module bay number.
SNMP community 1 second host name or IP address - set
Checks syntax and sets the second snmp -c1i2 host name or IP address of hostname/ip_address community 1. where hostname/ip_address is the second host name or IP address of community 1. Command use restricted (see Commands and user authority on page 6).
SNMP community 1 third host name or IP address - set
Checks syntax and sets the third host name or IP address of community 1.
snmp -c1i3 hostname/ip_address
-T system:mm[x]
where x is the primary where hostname/ip_address management-module is the third host name or IP bay number. address of community 1. Command use restricted (see Commands and user authority on page 6).
201
Table 64. snmp command (continued) Function SNMPv3 community 1 view type - set What it does Sets the SNMPv3 view type for community 1. Command snmp -ca1 type where type is get, set, or trap. Command use restricted (see Commands and user authority on page 6). SNMP community 2 name - set Sets the name of community 2. snmp -c2 name Valid targets -T system:mm[x] where x is the primary management-module bay number.
-T system:mm[x]
where name is a descriptive where x is the primary name of community 2. management-module bay number. Command use restricted (see Commands and user authority on page 6). SNMP community 2 first host name or IP address - set Checks syntax and sets the first host name or IP address of community 2. snmp -c2i1 hostname/ip_address -T system:mm[x]
where x is the primary where hostname/ip_address management-module is the first host name or IP bay number. address of community 2. Command use restricted (see Commands and user authority on page 6).
-T system:mm[x]
SNMPv3 community 2 view type - set
Sets the SNMPv3 view type for community 2.
snmp -ca2 type where type is get, set, or trap. Command use restricted (see Commands and user authority on page 6).
202
Table 64. snmp command (continued) Function SNMP community 3 name - set What it does Sets the name of community 3. Command snmp -c3 name Valid targets -T system:mm[x]
where name is a descriptive where x is the primary name of community 3. management-module bay number. Command use restricted (see Commands and user authority on page 6). SNMP community 3 first host name or IP address - set Checks syntax and sets the first host name or IP address of community 3. snmp -c3i1 hostname/ip_address -T system:mm[x]
where x is the primary where hostname/ip_address management-module is the first host name or IP bay number. address of community 3. Command use restricted (see Commands and user authority on page 6).
-T system:mm[x]
SNMPv3 community 3 view type - set
Sets the SNMPv3 view type for community 3.
snmp -ca3 type where type is get, set, or trap. Command use restricted (see Commands and user authority on page 6).
SNMP contact name set
Sets the contact name.
snmp -cn contact_name Command use restricted (see Commands and user authority on page 6).
-T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number.
SNMP location - set
Sets the location.
snmp -l hostname/ip_address Command use restricted (see Commands and user authority on page 6).
203
Example: To view the SNMP configuration, while advanced management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
snmp
To enable the SNMP agent and SNMP traps, while advanced management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
snmp -a -on -t -on
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 -on Changes to the network settings will take effect after the next reset of the MM. system:mm[1]>
204
sol (serial over LAN) command

This command configures SOL functions and indicates SOL status.
Table 65. sol (serial over LAN) command Function Display SOL status What it does Displays the SOL status for the targeted device: v When the command target is the primary management module, it displays 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 advanced management module, the VLAN_id is identified as VLAN ID. For management modules other than the advanced management module, the VLAN_id is identified by the -v value that is returned. v When the command target is a blade server when using a management module other than an advanced management module, it displays the following: -status on/off (SOL status for the blade server) Status of any SOL sessions for that blade server: - There is no SOL session opening for that blade. - There is an SOL session opening for that blade. - There is an SOL session opening and it is connected to a Telnet session. v When the command target is a blade server when using an advanced management module, it displays the following: -status enabled/disabled (SOL status for the blade server) Status of any SOL sessions for that blade server: - Not ready - Ready - Active Command sol Valid targets -T system:mm[x] -T system:blade[x] where x is the primary management-module or blade server bay number.
205
Table 65. sol (serial over LAN) command (continued) Function SOL retry interval - set What it does Sets the SOL retry interval to the input value. Command sol -i value Valid targets -T system:mm[x]
where value is from 10 ms where x is the primary to 2550 ms, inclusive, in management-module 10 ms increments. If you bay number. enter a value less than 10 ms, the retry interval will be set to 10 ms. If you enter a value greater than 2550 ms, the retry interval will be set to 2550 ms. Command use restricted (see Commands and user authority on page 6). SOL retry count - set Sets the SOL retry count to the input value. sol -c value -T system:mm[x]
where value is from 0 to 7, where x is the primary inclusive. If you enter a management-module value of 0, no retries will bay number. be attempted. If you enter a value greater than 7, an error will be displayed. Command use restricted (see Commands and user authority on page 6). SOL send threshold set Sets the SOL send threshold to the input value. Setting the threshold value to 1 causes the blade server integrated system management processor to send an SOL packet as soon as the first character is received. sol -s value -T system:mm[x]
where value is from 1 to where x is the primary 251, inclusive. If you enter management-module a value outside this range, bay number. an error will be displayed. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number.
SOL accumulate timeout - set
Sets the SOL accumulate timeout to sol -t value the input value. where value is from 5 ms to 1275 ms, inclusive. If you enter a value less than 5 ms, the accumulate timeout will be set to 5 ms. If you enter a value greater than 1275 ms, an error will be displayed. Command use restricted (see Commands and user authority on page 6).
SOL enable - global (management modules other than the advanced management module)
Enables SOL globally for the BladeCenter unit. The global SOL enable command does not affect the SOL session status for each blade server.
sol -status on
-T system:mm[x]
206
Table 65. sol (serial over LAN) command (continued) Function SOL enable - blade server (management modules other than the advanced management module) SOL disable - global (management modules other than the advanced management module) SOL disable - blade server (management modules other than the advanced management module) SOL enable - global (advanced management module only) SOL enable - blade server (advanced management module only) SOL disable - global (advanced management module only) SOL disable - blade server (advanced management module only) SOL VLAN ID - set (This command is not available for the advanced management module. For the advanced management module, the SOL VLAN ID is set using the ifconfig command (advanced management module only) on page 118.) Sets the SOL VLAN ID to the input value. Enables SOL globally for the BladeCenter unit. The global SOL enable command does not affect the SOL session status for each blade server. What it does Command Valid targets
Enables SOL for the specified blade sol -status on -T system:blade[x] server. Command use restricted where x is the blade (see Commands and user server bay number. authority on page 6). Disables SOL globally for the BladeCenter unit. The global SOL disable command does not affect the SOL session status for each blade server. Disables SOL for the specified blade server. sol -status off -T system:mm[x]
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. sol -status off -T system:blade[x]
Command use restricted where x is the blade (see Commands and user server bay number. authority on page 6). sol -status enabled -T system:mm[x]
Enables SOL for the specified blade sol -status enabled -T system:blade[x] server. Command use restricted where x is the blade (see Commands and user server bay number. authority on page 6). Disables SOL globally for the BladeCenter unit. The global SOL disable command does not affect the SOL session status for each blade server. Disables SOL for the specified blade server. sol -status disabled -T system:mm[x]
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. sol -status disabled -T system:blade[x]
Command use restricted where x is the blade (see Commands and user server bay number. authority on page 6). sol -v value where value is from 1 to 4095, inclusive. If you enter a value outside this range, an error will be displayed. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number.
207
Table 65. sol (serial over LAN) command (continued) Function CLI key sequence - set What it does Sets the key sequence that is used to enter the CLI while a Telnet session in SOL mode. Command sol -e value where value is the key sequence. In this sequence, a ^ (the carat symbol) indicates a Ctrl that maps to control-key sequences; for example: v ^[ (the carat symbol followed by a left bracket) means Esc v ^M (the carat symbol followed by a capitol M) means carriage return. Refer to an ASCII-to-key conversion table for a complete listing of control-key sequences. Command use restricted (see Commands and user authority on page 6). Reset blade server key sequence - set Sets the key sequence that will reset a blade server while a Telnet session in SOL mode. sol -r value where value is the key sequence. In this sequence, a ^ (the carat symbol) indicates a Ctrl that maps to control-key sequences; for example: v ^[ (the carat symbol followed by a left bracket) means Esc v ^M (the carat symbol followed by a capitol M) means carriage return. Refer to an ASCII-to-key conversion table for a complete listing of control-key sequences. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number. Valid targets -T system:mm[x] where x is the primary management-module bay number.
208
Example: To set the SOL accumulate timeout to 25 ms, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
sol -t 25
To set the reset blade server key sequence to Esc R Esc r Esc R, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
sol -r ^[R^[r^[R
To display the SOL settings, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
sol
The following example shows the information that is returned from these two commands run on an advanced management module:
system:mm[1]> sol -t 25 OK system:mm[1]> sol -status enabled -c 3 -e ^[( -i 250 -r ^[R^[r^[R -s 250 -t 5 VLAN ID 4095 system:mm[1]>
209
sshcfg command (advanced management module only)

This command sets and displays the SSH status of the management module.
Table 66. sshcfg command Function Display SSH status What it does Displays the SSH status of the management module. Returned values are: v -v1 off v -cstatus: state of CLI SSH server (enabled, disabled) v CLI SSH port number v -sstatus: state of SMASH SSH server (enabled, disabled) v SMASH SSH port number v ssh-dss fingerprint v ssh-rsa fingerprint v number of SSH public keys installed v number of locations available to store SSH keys Note: For scripting purposes, the -v1 off state is always displayed. Display RSA host key information Displays RSA host key information for the management module. sshcfg -hk rsa -T system:mm[x] where x is the primary management-module bay number. Display DSA host key information Displays DSA host key information for the management module. sshcfg -hk dsa -T system:mm[x] where x is the primary management-module bay number. Generate host key Generates a host key for the management module. sshcfg -hk gen -T system:mm[x] Command sshcfg Valid targets -T system:mm[x] where x is the primary management-module bay number.
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. Set state of CLI SSH server Sets the state of the CLI SSH sshcfg -cstatus state server for the management module. where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). Set state of SMASH SSH server Sets the state of the SMASH SSH sshcfg -sstatus state server for the management module. where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number.
210
Example: To display SSH status, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
sshcfg
system:mm[1]> sshcfg -v1 off -cstatus enabled CLI SSH port 22 -sstatus disabled SMASH SSH port 50024 ssh-dss 2048 bit fingerprint: 27:ee:bd:a9:27:28:d8:a5:93:03:3d:8e:77:d0:38:2c ssh-rsa 2048 bit fingerprint: 66:c9:73:4f:18:11:02:10:f3:05:6e:d7:27:05:a5:01 2 SSH public keys installed 10 locations available to store SSH public keys system:mm[1]>
211
sslcfg command (advanced management module only)

This command sets and displays the Secure Sockets Layer (SSL) status of the advanced management module.
Table 67. sslcfg command Function Display management module SSL status What it does Command Valid targets -T system:mm[x] where x is the primary or standby management-module bay number. -T system:mm[x]
Displays the SSL status of the sslcfg specified management module. This status includes information about SSL certificates.
Set SSL certificate handling for standby management module
Enables or disables use of an additional SSL certificate for the standby management module. If disabled, the standby management module uses the same SSL certificate as the primary management module. Note: An additional SSL certificate can only be configured when management module advanced failover is set to swap and the standby management module has a valid SSL certificate set up. Enables or disables SSL for the management module Web server. Note: The SSL for the management module Web server can only be enabled if a valid SSL certificate is set up.
sslcfg -ac state
where state is: where x is the standby v on to use an additional management-module certificate. bay number. v off to use the same certificate. Command use restricted (see Commands and user authority on page 6).
Set SSL state for management module Web server
sslcfg -server state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6).
-T system:mm[x] where x is the primary or standby management-module bay number.
Set SSL state for LDAP client
Enables or disables SSL for the sslcfg -client state LDAP client. Note: The SSL for the LDAP client where state is enabled or can only be enabled if a valid SSL disabled. certificate is set up. Command use restricted (see Commands and user authority on page 6).
-T system:mm[x] where x is the primary or standby management-module bay number.
212
Table 67. sslcfg command (continued) Function Generate self-signed certificate What it does Generates a self-signed certificate for the management module Web server or the LDAP client. The following values must be set when generating a self-signed certificate: 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 must match the host name that is used by a Web browser to connect to the management module. The following optional values can be set when generating a self-signed certificate: v Contact person using the -cp command option. v Email address of the contact person using the -ea command option. v Unit within a company or organization using the -ou command option. v Additional information such as a surname using the -s command option. v Additional information such as a given name using the -gn command option. v Additional information such as a initials using the -in command option. v Additional information such as a distinguished name qualifier using the -dq command option. Command sslcfg -cert type -c country -sp state -cl city -on org -hn hostname -cp name -ea email -ou org_unit -s surname -gn given_name -in initial -dq dn_qualifier where the following required options are: v type is: server for a management module Web server certificate. client for an LDAP client certificate. v country is two-character alphabetic code for the country. v state is a state or province name of up to 60 characters in length. v city is a city or locality name of up to 50 characters in length. v org is an organization name of up to 60 characters in length. v hostname is a valid host name of up to 60 characters in length. where the following optional options are: v name is up to 60 characters in length. v email is a valid email address of less than 60 characters. v org_unit is less than 60 characters. v surname is less than 60 characters. v given_name is less than 60 characters. v initial is less than 20 characters. v dn_qualifier is less than 60 characters. Command use restricted (see Commands and user authority on page 6). Valid targets -T system:mm[x] where x is the primary or standby management-module bay number.
213
Table 67. sslcfg command (continued) Function Generate CSR What it does Generates a certificate signing request (CSR) for the management module Web server or the LDAP client. The following values must be set when 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 must match the host name that is used by a Web browser to connect to the management module. The following optional values can be set when generating a CSR: v Contact person using the -cp command option. v Email address of the contact person using the -ea command option. v Unit within a company or organization using the -ou command option. v Additional information such as a surname using the -s command option. v Additional information such as a given name using the -gn command option. v Additional information such as a initials using the -in command option. v Additional information such as a distinguished name qualifier using the -dq command option. v Additional information such as a CSR password using the -cpwd command option. v Additional information such as an unstructured name qualifier using the -un command option. Command sslcfg -csr type -c country -sp state -cl city -on org -hn hostname -cp name -ea email -ou org_unit -s surname -gn given_name -in initial -dq dn_qualifier -cpwd password -un un_name where the following required options are: v type is: server for a management module Web server CSR. client for an LDAP client CSR. v country is two-character alphabetic code for the country. v state is a state or province name of up to 60 characters in length. v city is a city or locality name of up to 50 characters in length. v org is an organization name of up to 60 characters in length. v hostname is a valid host name of up to 60 characters in length. where the following optional options are: v name is up to 60 characters in length. v email is a valid email address of less than 60 characters. v org_unit is less than 60 characters. v surname is less than 60 characters. v given_name is less than 60 characters. v initial is less than 20 characters. v dn_qualifier is less than 60 characters. (continued on next page) Valid targets -T system:mm[x] where x is the primary or standby management-module bay number.
214
Table 67. sslcfg command (continued) Function Generate CSR (continued) What it does Command v password is between 6 and 30 characters. v un_name is less than 60 characters. Note: Arguments that must be quote-delimited are shown in quotation marks. Command use restricted (see Commands and user authority on page 6). Download certificate file Downloads the specified certificate file. The IP address of the TFTP server for downloading an SSL self-signed certificate or CSR must be set using the -i command. The file name for downloading an SSL self-signed certificate or CSR can be set using the -l command. If no file name is specified, the default file name for the file will be used. sslcfg -dnld -cert_type -l filename -i ipaddress -T system:mm[x] Valid targets
where x is the primary where: or standby v cert_type is management-module cert for an SSL bay number. self-signed certificate csr for a CSR v filename is a valid filename of less than 256 characters in length containing any character except the percent sign ( % ), forward-slash ( / ), or double-quote ( ). v ipaddress is the IP address of the TFTP server. Command use restricted (see Commands and user authority on page 6).
Import certificate file
Import (upload) the specified certificate file. The IP address of the TFTP server for uploading an SSL self-signed certificate must be set using the -i command.
sslcfg -upld -cert -l filename -i ipaddress
-T system:mm[x]
where x is the primary where: or standby v filename is a valid management-module filename of less than bay number. 256 characters in length containing any character The file name for uploading an SSL except the percent sign self-signed certificate can be set ( % ), forward-slash ( / using the -l command. ), or double-quote ( ). v ipaddress is the IP address of the TFTP server. Command use restricted (see Commands and user authority on page 6).
215
Table 67. sslcfg command (continued) Function Import/download/ remove trusted certificate 1 What it does Perform the specified operation on trusted certificate 1 for the SSL client. Valid operations are: v import (upload) v download v remove Command sslcfg -tc1 operation where operation is: v import v download v remove Valid targets -T system:mm[x] where x is the primary or standby management-module bay number.
Note: The -tc1 option The IP address of the TFTP server must be used with the for uploading or downloading a following options: trusted certificate must be set using v -i ipaddress the -i command. v -l filename The file name for uploading or downloading a trusted certificate can be set using the -l command. where: v ipaddress is the IP address of the TFTP server. v filename is a valid filename of less than 256 characters in length containing any character except the percent sign ( % ), forward-slash ( / ), or double-quote ( ). Command use restricted (see Commands and user authority on page 6). Import/download/ remove trusted certificate 2 Perform the specified operation on trusted certificate 2 for the SSL client. Valid operations are: v import (upload) v download v remove sslcfg -tc2 operation where operation is: v import v download v remove -T system:mm[x] where x is the primary or standby management-module bay number.
Note: The -tc2 option The IP address of the TFTP server must be used with the for uploading or downloading a following options: trusted certificate must be set using v -i ipaddress the -i command. v -l filename The file name for uploading or downloading a trusted certificate can be set using the -l command. where: v ipaddress is the IP address of the TFTP server. v filename is a valid filename of less than 256 characters in length containing any character except the percent sign ( % ), forward-slash ( / ), or double-quote ( ). Command use restricted (see Commands and user authority on page 6).
216
Table 67. sslcfg command (continued) Function Import/download/ remove trusted certificate 3 What it does Perform the specified operation on trusted certificate 3 for the SSL client. Valid operations are: v import (upload) v download v remove Command sslcfg -tc3 operation where operation is: v import v download v remove Valid targets -T system:mm[x] where x is the primary or standby management-module bay number.
Note: The -tc3 option The IP address of the TFTP server must be used with the for uploading or downloading a following options: trusted certificate must be set using v -i ipaddress the -i command. v -l filename The file name for uploading or downloading a trusted certificate can be set using the -l command. For importing a certificate -l <filename> is required. where: v ipaddress is the IP address of the TFTP server. v filename is a valid filename of less than 256 characters in length containing any character except the percent sign ( % ), forward-slash ( / ), or double-quote ( ). Command use restricted (see Commands and user authority on page 6).
Example: To view SSL information for the management module in bay 1, while this management module is set as the persistent command environment, at the system:mm[1]> prompt, type
sslcfg
system:mm[1]> sslcfg -server disabled -client disabled SSL Server Certificate status: A CA-signed certificate is installed SSL Client Certificate status: No certificate has been generated SSL Client Trusted Certificate status: Trusted Certificate 1: Not available Trusted Certificate 2: Not available Trusted Certificate 3: Not available system:mm[1]>
217
syslog command (advanced management module only)

This command manages how the advanced management module handles transmission of event log messages to networked syslog event collectors.
Table 68. syslog command Function Display syslog configuration What it does Displays the syslog event log transmission configuration of the advanced management module. Command syslog Valid targets -T system:mm[x] where x is the primary management-module bay number. syslog -sev level where version is: v i selects error, warning, and informational logs v w selects error and warning logs v e selects error logs Command use restricted (see Commands and user authority on page 6). Set syslog event log transmission state for collector 1 Enables or disables syslog event log transmission to collector 1. syslog -coll1 state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). Set syslog event log transmission state for collector 2 Enables or disables syslog event log transmission to collector 2. syslog -coll2 state where state is enabled or disabled. Command use restricted (see Commands and user authority on page 6). syslog event log collector 1 host name or IP address - set Sets the host name or IP address for syslog event collector 1. syslog -i1 hostname/ip_address where hostname/ip_address is the collector 1 host name or IP address. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number.
Set syslog filter level
Set severity filtering levels for syslog event log transmission.
218
Table 68. syslog command (continued) Function syslog event log collector 2 host name or IP address - set What it does Sets the host name or IP address for syslog event collector 2. Command syslog -i2 hostname/ip_address where hostname/ip_address is the collector 2 host name or IP address. Command use restricted (see Commands and user authority on page 6). syslog event log collector 1 port number - set Sets the port number for syslog event collector 1. syslog -p1 port where port is the collector 1 port number from 1 to 65535, inclusive. If you enter a value outside this range, an error will be displayed. Command use restricted (see Commands and user authority on page 6). syslog event log collector 2 port number - set Sets the port number for syslog event collector 2. syslog -p2 port where port is the collector 2 port number from 1 to 65535, inclusive. If you enter a value outside this range, an error will be displayed. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. Valid targets -T system:mm[x] where x is the primary management-module bay number.
Example: To view the syslog event log transmission configuration of the primary advanced management module in bay 1, while this management module is set as the persistent command environment, at the system:mm[1]> prompt, type
syslog
system:mm[1]> syslog -sev 1 -coll1 enabled -coll2 disabled -i1 253.245.45.1 -i2 -p1 514 -p2 514 system:mm[1]>
219
tcpcmdmode command (management modules other than the advanced management module)
This command displays and changes the timeout of the TCP command-mode sessions that are used by IBM Director software for out-of-band communication with the management module. This command is also used to enable or disable the TCP command-mode sessions. Note: The tcpcmdmode command operates differently for the advanced management module and for other management module types. The following command description is for management modules other than the advanced management module. See tcpcmdmode command (advanced management module only) on page 222 for command syntax for the advanced management module.
Table 69. tcpcmdmode command (management modules other than the advanced management module) Function Display TCP command-mode session status and timeout Set TCP command-mode session timeout What it does Displays the TCP command-mode session status (on or off) and timeout. Command tcpcmdmode Valid targets -T system:mm[x] where x is the primary management-module bay number. tcpcmdmode -t timeout where timeout is from 0 seconds (no timeout) to 4294967295 seconds, inclusive. If you enter a value outside this range, an error will be displayed. Command use restricted (see Commands and user authority on page 6). Enable TCP command-mode sessions Enables TCP command-mode sessions that are used by IBM Director software for out-of-band communication with the management module. Disables TCP command-mode sessions that are used by IBM Director software for out-of-band communication with the management module. tcpcmdmode -status on -T system:mm[x] -T system:mm[x] where x is the primary management-module bay number.
Sets the TCP command-mode session timeout value.
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. tcpcmdmode -status off -T system:mm[x]
Disable TCP command-mode sessions
Example: To enable a TCP command-mode session for the primary management module, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
tcpcmdmode -status on
To set the TCP command-mode session timeout for the primary management module to 6 minutes, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
tcpcmdmode -t 360
220
To display the TCP command-mode session status and timeout for the primary management module, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
tcpcmdmode
system:mm[1]> tcpcmdmode -status on OK system:mm[1]> tcpcmdmode -t 360 OK system:mm[1]> tcpcmdmode -status on -t 360 system:mm[1]>
221
tcpcmdmode command (advanced management module only)

This command displays and changes the timeout of the TCP command-mode sessions that are used by IBM Director software for out-of-band communication with the management module. This command is also used to enable or disable the TCP command-mode sessions. Note: The tcpcmdmode command operates differently for the advanced management module and for other management module types. The following command description is for the advanced management module. See tcpcmdmode command (management modules other than the advanced management module) on page 220 for command syntax for management modules other than the advanced management module.
Table 70. tcpcmdmode command (advanced management module only) Function Display TCP command-mode session status and timeout Set TCP command-mode session timeout What it does Displays the TCP command-mode session status (maximum number of sessions) and timeout. Command tcpcmdmode Valid targets -T system:mm[x] where x is the primary management-module bay number. tcpcmdmode -t timeout where timeout is from 0 seconds (no timeout) to 4294967295 seconds, inclusive. If you enter a value outside this range, an error will be displayed. Command use restricted (see Commands and user authority on page 6). Disable TCP command-mode sessions Disables TCP command-mode sessions that are used by IBM Director software for out-of-band communication with the management module. Enables TCP command-mode and sets the maximum number of sessions that can be used by IBM Director software for out-of-band communication with the management module. tcpcmdmode -status 0 -T system:mm[x] -T system:mm[x] where x is the primary management-module bay number.
Sets the TCP command-mode session timeout value.
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. tcpcmdmode -status number_sessions -T system:mm[x]
Enable and set number of TCP command-mode sessions
where x is the primary where number_sessions is management-module from 1 to 20, inclusive. (A bay number. value of 0 disables TCP command-mode sessions.) If you enter a value outside this range, an error will be displayed. Command use restricted (see Commands and user authority on page 6).
222
Example: To enable a maximum of three TCP command-mode sessions for the primary management module, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
tcpcmdmode -status 3
To set the TCP command-mode session timeout for the primary management module to 6 minutes, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
tcpcmdmode -t 360
To display the TCP command-mode session status and timeout for the primary management module, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
tcpcmdmode
system:mm[1]> tcpcmdmode -status 3 OK system:mm[1]> tcpcmdmode -t 360 OK system:mm[1]> tcpcmdmode -status 3 connection -t 360 system:mm[1]>
223
telnetcfg (Telnet configuration) command

This command displays and configures the command-line session parameters of the primary management module.
Table 71. telnetcfg (Telnet configuration) command Function Display command-line session configuration What it does Displays the command-line session configuration of the primary management module. Command telnetcfg Valid targets -T system:mm[x] where x is the primary management-module bay number. telnetcfg -t -T system:mm[x] where x is the primary management-module bay number. telnetcfg -t timeout where timeout is from 0 seconds (no timeout) to 4294967295 seconds, inclusive. If you enter a value outside this range, an error will be displayed. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number.
Display command-line session timeout (management modules other than the advanced management module) Set command-line session timeout for primary management module
Displays the command-line session timeout value, in seconds, of the primary management module.
Sets the command-line session timeout value for the primary management module.
Example: To set the command-line session timeout for the primary management module to 6 minutes, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
telnetcfg -t 360
To display the command-line session configuration for the primary management module, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
telnetcfg
system:mm[1]> telnetcfg -t 360 OK system:mm[1]> telnetcfg -t 360 system:mm[1]>
224
temps command (advanced management module only)

This command displays actual temperatures and temperature threshold values for BladeCenter components.
Table 72. temps command Function Display temperature values What it does Displays the current temperature and temperature threshold settings for the specified component: v The management module target displays the management module ambient temperature. v The blade server target displays the temperature values for components in the specified blade server, such as microprocessors and expansion modules. v The media tray target displays values for the temperature sensor in the media tray. Command temps Valid targets -T system:mm[x] -T system:blade[x] -T system:mt where x is the primary management-module or blade server bay number.
Example: To view the current temperature and temperature thresholds for the blade server in bay 3, while this blade server is set as the persistent command environment, at the system:blade[3]> prompt, type
temps
system:blade[3]> temps Comp Value Warning ---- ----- ------CPU1 38.00 85.00 CPU2 35.00 85.00 BEM ----- ----system:blade[3]> Hard Warning Shutdown Reset -------- ------95.00 78.00 95.00 78.00 ---------
225
trespass command (advanced management module only)

This command sets and displays the status and message for the advanced management module trespass feature that can display a warning message to users when they log in.
Table 73. trespass command Function Display status of management module trespass feature What it does Displays status of the trespass feature for the management module. Possible return values are: v -twe (on or off) v -tw warning_message Note: The warning_message is shown only when the trespass feature is enabled (-twe on). Enable management Enable trespass feature for module trespass feature management module. trespass -twe on -T system:mm[x] Command trespass Valid targets -T system:mm[x] where x is the primary management-module bay number.
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. Disable management Disable trespass feature for module trespass feature management module. trespass -twe off -T system:mm[x]
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. Set management module trespass message Sets message that is displayed to users who log in to the management module when the trespass feature is enabled. Note: Setting a new warning_message permanently replaces the default warning message. trespass -tw warning_message -T system:mm[x]
where x is the primary where warning_message management-module is up to 1600 characters in bay number. length and enclosed in double-quotation marks. Command use restricted (see Commands and user authority on page 6).
Example: To enable the management module trespass feature, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
trespass -twe on
To set the trespass feature message to Authorized Access only, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
trespass -tw "Authorized Access only"
To display the management module trespass feature status, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
trespass
226
system:mm[1]> trespass -twe on OK system:mm[1]> trespass -tw "Authorized Access only" -tw OK system:mm[1]> trespass -twe on -tw Authorized Access only system:mm[1]>
227
uicfg command (advanced management module only)

This command displays and configures the management module user interface settings.
Table 74. uicfg command (advanced management module only) Function Display management module user interface settings What it does Command Valid targets -T system:mm[x] where x is the primary management-module bay number.
Displays the user interface settings uicfg for the management module. Returned values indicate enabled or disabled status for the following interfaces: v -cli v -snmp v -tcm (TCP command mode) v -web (Web interface) Enables the management module command-line interface (using Telnet or SSH). uicfg -cli enabled
Enable command-line interface
-T system:mm[x]
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. uicfg -cli disabled -T system:mm[x]
Disable command-line interface
Disables the management module command-line interface (using Telnet or SSH).
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. uicfg -snmp enabled -T system:mm[x]
Enable SNMPv1 and SNMPv3
Enables SNMPv1 and SNMPv3 connections to the management module.
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. uicfg -snmp disabled -T system:mm[x]
Disable SNMPv1 and SNMPv3
Disables SNMPv1 and SNMPv3 connections to the management module.
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. uicfg -tcm enabled -T system:mm[x]
Enable TCP command mode
Enables TCP command mode (used by IBM Director) for the management module.
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. uicfg -tcm disabled -T system:mm[x]
Disable TCP command mode
Disables TCP command mode (used by IBM Director) for the management module.
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. uicfg -web enabled -T system:mm[x]
Enable Web interface
Enables the management module Web interface.
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. Disable Web interface Disables the management module Web interface. uicfg -web disabled -T system:mm[x]
228
Example: To disable TCP command mode for the management module, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
uicfg -tcm disabled
To display the user interface configuration for the management module, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
uicfg
system:mm[1]> uicfg -tcm disabled Warning: Communication with IBM Director has been disabled. OK system:mm[1]> uicfg -cli enabled (telnet only) -snmp enabled -tcm disabled -web enabled system:mm[1]>
229
update (update firmware) command

This command updates firmware using a Trivial File Transfer Protocol (TFTP) server and displays information about firmware installed in BladeCenter components.
Table 75. update (update firmware) command Function Display update command help (management modules other than the advanced management module) What it does Displays information about using the update command. Command update Valid targets -T system:mm[x] -T system:blade[x]:sp -T system:switch[x] where x is the primary management-module, blade server bay number, or I/O (switch) module bay number. Displays attributes of the firmware installed in the command target. Return values are: v Firmware type v Build ID v Filename v Release date v Revision level For standby advanced management modules, the returned value will also indicate if a firmware update is in progress and the percentage that is complete. Update firmware Update firmware for the command target. Important: Command authority definitions might change between firmware versions. Make sure that the command authority level set for each user is correct after updating management-module firmware. Note: The P6 blade server firmware is too large to be updated using this command. See the Users Guide for your P6 blade server for information about updating firmware. update -i ip_address -l filelocation where: update -a -T system:mm[x] -T system:blade[x]:sp -T system:switch[x] where x is the primary management-module number, standby management-module number (advanced management module only), blade server bay number, or I/O (switch) module bay number. -T system:mm[x] -T system:blade[x]:sp -T system:switch[x]
Display firmware attributes
v ip_address is the IP where x is the primary address of TFTP server. management-module, v filelocation is the blade server bay location of the firmware number, or I/O (switch) update file. module bay number. Command use restricted (see Commands and user authority on page 6).
230
Table 75. update (update firmware) command (continued) Function Update firmware (verbose) What it does Update firmware for the command target, showing details of the firmware download and flash operations. The detailed information is not shown until the update is complete, which might take several minutes. Important: Command authority definitions might change between firmware versions. Make sure that the command authority level set for each user is correct after updating management-module firmware. Note: The P6 blade server firmware is too large to be updated using this command. See the Users Guide for your P6 blade server for information about updating firmware. Command update -i ip_address -l filelocation -v where: Valid targets -T system:mm[x] -T system:blade[x]:sp -T system:switch[x]
v ip_address is the IP where x is the primary address of TFTP server. management-module, v filelocation is the blade server bay location of the firmware number, or I/O (switch) update file. module bay number. Command use restricted (see Commands and user authority on page 6).
Example: To update the firmware and display update details for the management module in management-module bay 1, while this management module is set as the persistent command environment, type the following command at the system:mm[1]> prompt. For this example, the IP address of the TFTP server is 192.168.70.120 and the firmware file containing the update is named dev_mm.pkt.
update -v -i 192.168.70.120 -l dev_mm.pkt
To display information about firmware installed in the management module in management-module bay 1, while this management module is set as the persistent command environment, at the system:mm[1]> prompt, type
update -a
To update the service-processor firmware in the blade server in blade bay 8 (not using verbose mode), while the management module in management-module bay 1 is set as the persistent command environment, type the following command at the system:mm[1]> prompt. For this example, the IP address of the TFTP server is 192.168.70.120 and the firmware file containing the update is named h8.pkt.
update -i 192.168.70.120 -l h8.pkt -T system:blade[8]:sp
The following example shows the information that is returned from these three update commands:
system:mm[1]> update -v -i 192.168.70.120 -l dev_mm.pkt TFTP file upload successful 1517829. Starting flash packet preparation. Flash preparation - packet percent complete 24. Flash preparation - packet percent complete 48. Flash preparation - packet percent complete 72. Flash preparation - packet percent complete 96. Flash preparation - packet percent complete 100. Flash operation phase starting. Flashing - packet percent complete 34. Flashing - packet percent complete 38. Flashing - packet percent complete 50. Flashing - packet percent complete 55. Flashing - packet percent complete 80.
231
Flashing - packet percent complete 90. Flash operation complete. The new firmware will become active after the next reset of the MM. OK system:mm[1]> update -a Bay 1 Name 1 Firmware type: Main application Build ID: BRETKD+ Filename: CNETMNUS.PKT Released: 11-17-03 Revision: 16 Firmware type: Boot ROM Build ID: BRBR1B+ Filename: CNETBRUS.PKT Released: 10-27-03 Revision: 16 Firmware type: Remote control Build ID: BRRG1B+ Filename: CNETRGUS.PKT Released: 10-27-03 Revision: 16 OK system:mm[1]> update -i 192.168.70.120 -l h8.pkt -T system:blade[8]:sp OK system:mm[1]>
232
uplink (management module failover) command (management modules other than the advanced management module)
This command displays and configures the management-module uplink failover feature. If the physical external network interface of the primary management module fails, this feature forces a failover to the redundant management module, if one is installed. Note: The uplink command operates differently for the advanced management module and for other management module types. The following command description is for management modules other than the advanced management module. See uplink (management module failover) command (advanced management module only) on page 235 for command syntax for the advanced management module.
Table 76. uplink command (management modules other than the advanced management module) Function Display uplink failover status What it does Displays the management-module uplink failover status (enabled or disabled) and the failover delay. Command uplink Valid targets -T system:mm[x] where x is the primary management-module bay number. uplink -del delay where delay is from 1 to 255 minutes, inclusive. If you enter a value outside this range, an error will be displayed. Command use restricted (see Commands and user authority on page 6). Enable physical uplink failover Enables failover to the redundant management module if the external physical network interface of the primary management module fails. Disables failover to the redundant management module if the external physical network interface of the primary management module fails. uplink -on -T system:mm[x] -T system:mm[x] where x is the primary management-module bay number.
Set physical network uplink failover delay
Sets the amount of time between detection of a management-module physical uplink failure and failover to the redundant management module.
Command use restricted where x is the primary (see Commands and user management-module authority on page 6). bay number. uplink -off -T system:mm[x]
Disable physical uplink failover
Example: To enable failover to the redundant management module if the external network interface of the primary management module fails, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
uplink -on
To set the uplink failover delay to 3 minutes, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
uplink -del 3
To display the uplink failover configuration, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
233
uplink
system:mm[1]> uplink -on OK system:mm[1]> uplink -del 3 Uplink delay set to 3 minute(s). OK system:mm[1]> uplink Failover on network uplink loss is enabled. Uplink delay: 3 minute(s) system:mm[1]>
234
uplink (management module failover) command (advanced management module only)

This command displays and configures the management-module uplink failover feature. If the external network interface of the primary management module fails, this feature forces a failover to the redundant management module, if one is installed. Notes: v The uplink command operates differently for the advanced management module and for other management module types. The following command description is for the advanced management module. See uplink (management module failover) command (management modules other than the advanced management module) on page 233 for command syntax for management modules other than the advanced management module. v This command does not apply to the BladeCenter S unit.
Table 77. uplink command (advanced management module only) Function Display uplink failover status What it does Displays the management-module uplink failover status (enabled or disabled) and the failover delay. Command uplink Valid targets -T system -T system:mm[x] where x is the primary management-module bay number. Set physical network uplink failover delay Sets the amount of time between detection of a management-module physical uplink failure and failover to the redundant management module. uplink -dps delay where delay is from 10 to 172800 seconds, inclusive. If you enter a value outside this range, an error will be displayed. Command use restricted (see Commands and user authority on page 6). Enable physical uplink failover Enables failover to the redundant management module if the external physical network interface of the primary management module fails. uplink -ep enabled -T system -T system -T system:mm[x] where x is the primary management-module bay number.
-T system:mm[x] Command use restricted (see Commands and user where x is the primary authority on page 6). management-module bay number. uplink -ep disabled -T system
Disable physical uplink failover
Disables failover to the redundant management module if the external physical network interface of the primary management module fails.
-T system:mm[x] Command use restricted (see Commands and user where x is the primary authority on page 6). management-module bay number.
235
Table 77. uplink command (advanced management module only) (continued) Function Set logical network uplink failover delay What it does Sets the amount of time between detection of a management-module logical uplink failure and failover to the redundant management module. Command uplink -dls delay where delay is from 60 to 172800 seconds, inclusive. If you enter a value outside this range, an error will be displayed. Command use restricted (see Commands and user authority on page 6). Enable logical uplink failover Enables failover to the redundant management module if the external logical network interface of the primary management module fails. You must enter a non-zero IP address of a device that the management module can access to check its logical network link before you can enable logical uplink failover. Disable logical uplink failover Disables failover to the redundant management module if the external logical network interface of the primary management module fails. uplink -el enabled -T system Valid targets -T system -T system:mm[x] where x is the primary management-module bay number.
-T system:mm[x] Command use restricted (see Commands and user where x is the primary authority on page 6). management-module bay number.
uplink -el disabled
-T system
-T system:mm[x] Command use restricted (see Commands and user where x is the primary authority on page 6). management-module bay number. uplink -ip ip_address where ip_address is a valid IP. You must enter a non-zero IP address before you can enable logical uplink failover. Command use restricted (see Commands and user authority on page 6). -T system -T system:mm[x] where x is the primary management-module bay number.
Set IP address to check Sets the IP address of the device logical network uplink that the management module accesses to check its logical network link.
Example: To enable failover to the redundant management module if the external physical network interface of the primary management module fails, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
uplink -ep enabled
To set the physical uplink failover delay to 30 seconds, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
uplink -dps 30
To display the uplink failover configuration, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
uplink
236
system:mm[1]> uplink -ep enabled OK system:mm[1]> uplink -dps 30 OK system:mm[1]> uplink Failover on network uplink loss is enabled for physical detection Uplink delay for physical detection: 60 seconds Failover on network uplink loss is disabled for logical detection Uplink delay for logical detection: 1800 seconds Destination IP for MM to check its logical link: 0.0.0.0 system:mm[1]>
237
users command (management modules other than the advanced management module)
This command displays and configures user accounts, also called user profiles, of the primary management module. Note: The users command operates differently for the advanced management module and for other management module types. The following command description is for management modules other than the advanced management module. See users command (advanced management module only) on page 247 for command syntax for the advanced management module. Important: Command authority definitions might change between firmware versions. Make sure that the command authority level set for each user is correct after updating management-module firmware.
Table 78. users (management-module users) command (management modules other than the advanced management module) Function What it does Command users Valid targets -T system:mm[x] where x is the primary management-module bay number. users -user_number where user_number is a number from 1 to 12 that corresponds to the user number assigned in the Display all user profiles list. -T system:mm[x] where x is the primary management-module bay number.
Display all user profiles Displays all 12 management-module user profiles. Returned values are: v User name v Authority level Display single user profile Displays the specified management-module user profile. Returned values are: v User name v Authority level v Context name v Authentication protocol v Privacy protocol v Access type v Hostname/IP address Delete the specified management-module user profile.
Delete user profile
users -user_number -clear where user_number is a number from 1 to 12 that corresponds to the user number assigned in the Display all user profiles list. It is possible to delete an empty user profile. Command use restricted (see Commands and user authority on page 6).
238
Table 78. users (management-module users) command (management modules other than the advanced management module) (continued) Function Create user profile What it does Create the specified management-module user profile. All fields must be specified when creating a user profile for the BladeCenter T management module. For management modules other than those installed in a BladeCenter T unit, only the following user-profile fields are required: v -user_number v -n user_name v -a user_authority v -p user_password Command users -user_number -n user_name -p user_password -a user_authority -cn context_name -ap auth_protocol -pp privacy_protocol -ppw privacy_pwd -at access_type -i ip_addr/hostname where: v user_number is a number from 1 to 12 that corresponds to an unused user number in the Display all user profiles list. v user_name is a alphanumeric string up to 15 characters in length that can include periods ( . ) and underscores ( _ ). Each of the 12 user names must be unique. v user_password can be blank or an alphanumeric string up to 15 characters in length that can include periods ( . ) and underscores ( _ ), and must include at least one alphabetic and one non-alphabetic character. v user_authority is one of the following: operator (read-only) rbs (see Set user authority level on page 242 for more information) (continued on next page) Valid targets -T system:mm[x] where x is the primary management-module bay number.
239
Table 78. users (management-module users) command (management modules other than the advanced management module) (continued) Function Create user profile (continued) What it does Command v context_name is a string for SNMPv3 context that is up to 31 characters in length. Each of the 12 context names must be unique. v auth_protocol is an SNMPv3 authentication protocol of sha, md5, or blank (no entry) for none. v privacy_protocol is an SNMPv3 privacy protocol of des or blank (no entry) for none. If the privacy protocol is set to none, no -ppw command option (privacy password) is required. v privacy_pwd is an SNMPv3 privacy password string of up to 31 characters in length. If the privacy protocol is set to none, the -ppw command option does not need to be used unless a privacy password is required. v access_type is an SNMPv3 access type of read, write, or traps. v ip_addr/hostname is a valid SNMPv3 static IP address or an alphanumeric hostname string up to 63 characters in length. Command use restricted (see Commands and user authority on page 6). Valid targets
240
Table 78. users (management-module users) command (management modules other than the advanced management module) (continued) Function Set user name What it does Sets a user name in the specified management-module user profile. Command users -user_number -n user_name where: v user_number is a number from 1 to 12 that corresponds to the user number assigned in the Display all user profiles list. v user_name is a alphanumeric string up to 15 characters in length that can include periods ( . ) and underscores ( _ ). Each of the 12 user names must be unique. Command use restricted (see Commands and user authority on page 6). Set user password Sets a user password in the users -user_number -p specified management-module user user_password profile. where: v user_number is a number from 1 to 12 that corresponds to the user number assigned in the Display all user profiles list. v user_password can be blank or an alphanumeric string up to 15 characters in length that can include periods ( . ) and underscores ( _ ), and must include at least one alphabetic and one non-alphabetic character. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number. Valid targets -T system:mm[x] where x is the primary management-module bay number.
241
Table 78. users (management-module users) command (management modules other than the advanced management module) (continued) Function Set user authority level What it does Command Valid targets -T system:mm[x] where x is the primary management-module bay number.
Sets a user authority level in the users -user_number -a specified management-module user user_authority profile. where: v user_number is a number from 1 to 12 that corresponds to the user number assigned in the Display all user profiles list. v user_authority is one of the following: operator (read-only) rbs (custom) The custom authority level parameter is specified using the following syntax: rbs:levels:devices where the levels are one or more of the following authority levels, separated by 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) (continued on next page)
242
Table 78. users (management-module users) command (management modules other than the advanced management module) (continued) Function Set user authority level (continued) What it does Command where the devices are one or more of the following devices, separated by a vertical bar ( | ). Ranges of devices are separated by a dash ( - ). v cn (Chassis n, where n is a valid chassis number. Use c1 for single-chassis environments.) v bn (Blade n, where n is a valid blade bay number in the chassis) v sn (I/O module n, where n is a valid I/O module bay number in the chassis) Command use restricted (see Commands and user authority on page 6). Set SNMPv3 user context name Sets an SNMPv3 context name in the specified management-module user profile. The context name defines the context the SNMPv3 user is working in. A context name can be shared by multiple users. users -user_number -cn context_name -T system:mm[x] Valid targets
where x is the primary where: management-module v user_number is a bay number. number from 1 to 12 that corresponds to the user number assigned in the Display all user profiles list. v context_name is a string up to 31 characters in length. Each of the 12 context names must be unique. Command use restricted (see Commands and user authority on page 6).
243
Table 78. users (management-module users) command (management modules other than the advanced management module) (continued) Function Set SNMPv3 user authentication protocol What it does Command Valid targets -T system:mm[x] where x is the primary management-module bay number.
Sets the SNMPv3 authentication users -user_number -ap protocol to be used for the specified auth_protocol management-module user profile. where: v user_number is a number from 1 to 12 that corresponds to the user number assigned in the Display all user profiles list. v auth_protocol is sha, md5, or blank (no entry) for none. Command use restricted (see Commands and user authority on page 6).
Set SNMPv3 user privacy protocol
Sets the SNMPv3 privacy protocol to be used for the specified management-module user profile. If the privacy protocol is set to none, no -ppw command option (privacy password) is required.
users -user_number -pp privacy_protocol where: v user_number is a number from 1 to 12 that corresponds to the user number assigned in the Display all user profiles list. v privacy_protocol is des or blank (no entry) for none. Command use restricted (see Commands and user authority on page 6).
Set privacy password for SNMPv3 user
Sets an SNMPv3 privacy password in the specified management-module user profile.
users -user_number -ppw privacy_pwd where: v user_number is a number from 1 to 12 that corresponds to the user number assigned in the Display all user profiles list. v privacy_pwd is a string up to 31 characters in length. Command use restricted (see Commands and user authority on page 6).
244
Table 78. users (management-module users) command (management modules other than the advanced management module) (continued) Function Set access type for SNMPv3 user What it does Sets an SNMPv3 access type for the specified management-module user profile. Command users -user_number -at access_type Valid targets -T system:mm[x]
where x is the primary where: management-module This command supports the v user_number is a bay number. following access types: number from 1 to 12 v read: the user can query that corresponds to the Management Information Base user number assigned (MIB) objects and receive traps. in the Display all user v write: the user can query and set profiles list. MIB objects and receive traps. v access_type is read, v traps: the user can only receive write, or traps. traps. Command use restricted (see Commands and user authority on page 6). Set IP address or hostname for SNMPv3 trap receiver Sets the IP address or hostname that will receive SNMPv3 traps for the specified management-module user profile. users -user_number -i ip_addr/hostname where: v user_number is a number from 1 to 12 that corresponds to the user number assigned in the Display all user profiles list. v ip_addr/hostname is a valid static IP address or an alphanumeric hostname string up to 63 characters in length. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number.
Example: To create user number 3 with a user name of user3 who has supervisor rights to all BladeCenter components, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
users -3 -n user3 -p passw0rd -a rbs:super:c1|b1-b14|s1-s4 -cn joe -ap md5 -pp des -ppw passw0rd -at read -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 set the command authority for an existing user number 4 to Blade Operator for blade 1, blade 2, and blade 3 and Chassis Log Management, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
users -4 -rbs:bo|clm:b1-b3|c1
To display all users, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
users
245
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 read -I 192.168.70.129 OK system:mm[1]> users -4 -rbs:bo|clm:b1-b3|c1 OK system:mm[1]> users 1. USERID Role:supervisor Blades:1|2|3|4|5|6|7|8|9|10|11|12|13|14 Chassis:1 Switches:1|2|3|4 2. <not used> 3. user3 Role:supervisor Blades:1|2|3|4|5|6|7|8|9|10|11|12|13|14 Chassis:1 Switches:1|2|3|4 4. user4 Role:blade operator|chassis log management Blades:1|2|3 Chassis:1 Switches:N/A 5. <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]>
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 entry must all be on one line.
246
users command (advanced management module only)

This command displays and configures user accounts, also called user profiles, of the primary management module. Note: The users command operates differently for the advanced management module and for other management module types. The following command description is for the advanced management module. See users command (management modules other than the advanced management module) on page 238 for command syntax for management modules other than the advanced management module. Important: Command authority definitions might change between firmware versions. Make sure that the command authority level set for each user is correct after updating management-module firmware.
Table 79. users (management-module users) command (advanced management module only) Function What it does Command users Valid targets -T system:mm[x] where x is the primary management-module bay number.
Display all user profiles Displays all 12 management-module user profiles. Returned values are: v User name v Authority level v Current log in or log out state v Password compliance v State of account (active or inactive) v Number of SSH public keys installed for user Display active users Displays all users that are currently logged in to the management module. Returned values include: v User name v User IP address v Connection type (SNMPv1, SNMPv3, SSH, TCP command mode, Telnet, Web) v Session ID Terminates the specified user login session. Note: The session ID is found by running the users -curr command.
users -curr
Terminate user session
users -ts sessionID where sessionID is a number that corresponds to the user session ID. Command use restricted (see Commands and user authority on page 6).
Display single user profile
Displays the specified management-module user profile. Returned values are: v User name v Authority level v Context name v Authentication protocol v Privacy protocol v Access type v Hostname/IP address
users -user_number where user_number is a number from 1 to 12 that corresponds to the user number assigned in the Display all user profiles list.
247
Table 79. users (management-module users) command (advanced management module only) (continued) Function Delete user profile What it does Delete the specified management-module user profile. Command users -user_number -clear where user_number is a number from 1 to 12 that corresponds to the user number assigned in the Display all user profiles list. It is possible to delete an empty user profile. Command use restricted (see Commands and user authority on page 6). Valid targets -T system:mm[x] where x is the primary management-module bay number.
248
Table 79. users (management-module users) command (advanced management module only) (continued) Function Create user profile What it does Create the specified management-module user profile. All fields must be specified when creating a user profile for the BladeCenter T management module. For management modules other than those installed in a BladeCenter T unit, only the following user-profile fields are required: v -user_number v -n user_name v -a user_authority v -p user_password Command users -user_number -n user_name -p user_password -a user_authority -cn context_name -ap auth_protocol -pp privacy_protocol -ppw privacy_pwd -at access_type -i ip_addr/hostname where: v user_number is a number from 1 to 12 that corresponds to an unused user number in the Display all user profiles list. v user_name is a alphanumeric string up to 15 characters in length that can include periods ( . ) and underscores ( _ ). Each of the 12 user names must be unique. v user_password can be blank or an alphanumeric string up to 15 characters in length that can include periods ( . ) and underscores ( _ ), and must include at least one alphabetic and one non-alphabetic character. v user_authority is one of the following: operator (read-only) rbs (see Set user authority level on page 252 for more information) Command use restricted (see Commands and user authority on page 6). Valid targets -T system:mm[x] where x is the primary management-module bay number.
249
Table 79. users (management-module users) command (advanced management module only) (continued) Function Set user name What it does Sets a user name in the specified management-module user profile. Command users -user_number -n user_name where: v user_number is a number from 1 to 12 that corresponds to the user number assigned in the Display all user profiles list. v user_name is a alphanumeric string up to 15 characters in length that can include periods ( . ) and underscores ( _ ). Each of the 12 user names must be unique. Command use restricted (see Commands and user authority on page 6). Set user password Sets a user password in the users -user_number -p specified management-module user user_password profile. where: v user_number is a number from 1 to 12 that corresponds to the user number assigned in the Display all user profiles list. v user_password can be blank or an alphanumeric string up to 15 characters in length that can include periods ( . ) and underscores ( _ ), and must include at least one alphabetic and one non-alphabetic character. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number. Valid targets -T system:mm[x] where x is the primary management-module bay number.
250
Table 79. users (management-module users) command (advanced management module only) (continued) Function Change user password What it does Changes the user password in the specified management-module user profile. Note: Users can change their own password even if they do not have authority to manage accounts. Command users -user_number -op old_password -p new_password where: v user_number is a number from 1 to 12 that corresponds to the user number assigned in the Display all user profiles list. v old_password is the current password for the specified user. v new_password can be blank or an alphanumeric string up to 15 characters in length that can include periods ( . ) and underscores ( _ ), and must include at least one alphabetic and one non-alphabetic character. Command use restricted (see Commands and user authority on page 6). Valid targets -T system:mm[x] where x is the primary management-module bay number.
251
Table 79. users (management-module users) command (advanced management module only) (continued) Function Set user authority level What it does Command Valid targets -T system:mm[x] where x is the primary management-module bay number.
Sets a user authority level in the users -user_number -a specified management-module user user_authority profile. where: v user_number is a number from 1 to 12 that corresponds to the user number assigned in the Display all user profiles list. v user_authority is one of the following: operator (read-only) rbs (custom) The custom authority level parameter is specified using the following syntax: rbs:levels:devices where the levels are one or more of the following authority levels, separated by 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) (continued on next page)
252
Table 79. users (management-module users) command (advanced management module only) (continued) Function Set user authority level (continued) What it does Command the levels can also include one or more of the following authority levels when using LDAP. Notes: 1. The LDAP authority levels are not supported by the management-module Web interface. 2. To use the LDAP authority levels, make sure that the version of LDAP security used by the management module is set to v2 (enhanced role-based security model). See ldapcfg command (advanced management module only) on page 136 for information. v brpv (Blade Remote Presence View Video) v brpk (Blade Remote Presence KVM) v brpr (Blade Remote Presence Remote Drive Read) v crpru (Blade Remote Presence Remote Drive Read or Write) v rps (Remote Presence Supervisor) where the devices are one or more of the following devices, separated by a vertical bar ( | ). Ranges of devices are separated by a dash ( - ). v cn (Chassis n, where n is a valid chassis number. Use c1 for single-chassis environments.) v bn (Blade n, where n is a valid blade bay number in the chassis) v sn (I/O module n, where n is a valid I/O module bay number in the chassis) Command use restricted (see Commands and user authority on page 6).
Valid targets
253
Table 79. users (management-module users) command (advanced management module only) (continued) Function Set maximum number of simultaneous sessions for user What it does Sets the maximum number of simultaneous login sessions for the specified user. Command users -user_number -ms max-session Valid targets -T system:mm[x]
where x is the primary where: management-module v user_number is a bay number. number from 1 to 12 that corresponds to the user number assigned in the Display all user profiles list. v max-session is a number from 0 to 20 that sets the maximum number of simultaneous sessions for the user. A value of 0 means that there is no session limit for the user. Command use restricted (see Commands and user authority on page 6).
Set SNMPv3 user context name
Sets an SNMPv3 context name in the specified management-module user profile. The context name defines the context the SNMPv3 user is working in. A context name can be shared by multiple users.
users -user_number -cn context_name
-T system:mm[x]
where x is the primary where: management-module v user_number is a bay number. number from 1 to 12 that corresponds to the user number assigned in the Display all user profiles list. v context_name is a string up to 31 characters in length. Each of the 12 context names must be unique. Command use restricted (see Commands and user authority on page 6).
Set SNMPv3 user authentication protocol
Sets the SNMPv3 authentication users -user_number -ap protocol to be used for the specified auth_protocol management-module user profile. where: v user_number is a number from 1 to 12 that corresponds to the user number assigned in the Display all user profiles list. v auth_protocol is sha, md5, or blank (no entry) for none. Command use restricted (see Commands and user authority on page 6).
254
Table 79. users (management-module users) command (advanced management module only) (continued) Function Set SNMPv3 user privacy protocol What it does Sets the SNMPv3 privacy protocol to be used for the specified management-module user profile. If the privacy protocol is set to none, no -ppw command option (privacy password) is required. Command users -user_number -pp privacy_protocol where: v user_number is a number from 1 to 12 that corresponds to the user number assigned in the Display all user profiles list. v privacy_protocol is des or blank (no entry) for none. Command use restricted (see Commands and user authority on page 6). Set privacy password for SNMPv3 user Sets an SNMPv3 privacy password in the specified management-module user profile. users -user_number -ppw privacy_pwd where: v user_number is a number from 1 to 12 that corresponds to the user number assigned in the Display all user profiles list. v privacy_pwd is a string up to 31 characters in length. Command use restricted (see Commands and user authority on page 6). Set access type for SNMPv3 user Sets an SNMPv3 access type for the specified management-module user profile. This command supports the following access types: v get: the user can query Management Information Base (MIB) objects and receive traps. v set: the user can query and set MIB objects and receive traps. v trap: the user can only receive traps. users -user_number -at access_type where: v user_number is a number from 1 to 12 that corresponds to the user number assigned in the Display all user profiles list. v access_type is get, set, or trap. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. Valid targets -T system:mm[x] where x is the primary management-module bay number.
255
Table 79. users (management-module users) command (advanced management module only) (continued) Function Set IP address or hostname for SNMPv3 trap receiver What it does Sets the IP address or hostname that will receive SNMPv3 traps for the specified management-module user profile. Command users -user_number -i ip_addr/hostname where: v user_number is a number from 1 to 12 that corresponds to the user number assigned in the Display all user profiles list. v ip_addr/hostname is a valid static IP address or an alphanumeric hostname string up to 63 characters in length. Command use restricted (see Commands and user authority on page 6). Display SSH public key Displays the entire specified SSH public key for the specified user in OpenSSH format. Note: The -pk and -e options must be used exclusive of all other users command options. users -user_number -pk -key_index -e where: v user_number is a number from 1 to 12 that corresponds to the user number assigned in the Display all user profiles list. v key_index identifies the key number from 1 to 12 to display. If the -key_index is all, then all keys for the user are displayed. Command use restricted (see Commands and user authority on page 6). Add SSH public key Adds an SSH public key for the specified user. Note: The -pk and -add options must be used exclusive of all other users command options. users -user_number -pk -add key where: v user_number is a number from 1 to 12 that corresponds to the user number assigned in the Display all user profiles list. v key is a valid key in OpenSSH format. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number. -T system:mm[x] where x is the primary management-module bay number. Valid targets -T system:mm[x] where x is the primary management-module bay number.
256
Table 79. users (management-module users) command (advanced management module only) (continued) Function What it does Command users -user_number -pk -key_index -add key where: v user_number is a number from 1 to 12 that corresponds to the user number assigned in the Display all user profiles list. v key_index identifies the key number from 1 to 12 to add. v key is a valid key in OpenSSH format. Command use restricted (see Commands and user authority on page 6). Remove SSH public key Removes an SSH public key for the users -user_number -pk specified user. -key_index -remove Note: The -pk and -remove options v user_number is a must be used exclusive of all other number from 1 to 12 users command options. that corresponds to the user number assigned in the Display all user profiles list. v key_index identifies the key number from 1 to 12 to remove. If the -key_index is all, then all keys for the user are removed. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number. Valid targets -T system:mm[x] where x is the primary management-module bay number.
Add specific SSH public Adds a specific SSH public key for key the specified user. Note: The -pk and -add options must be used exclusive of all other users command options.
257
Table 79. users (management-module users) command (advanced management module only) (continued) Function Upload SSH public key What it does Uploads a new SSH public key. Command users -user_number -pk -upld -i ip_addr/hostname -l filename v user_number is a number from 1 to 12 that corresponds to the user number assigned in the Display all user profiles list. v ip_addr/hostname is a valid static IP address or an alphanumeric hostname string up to 63 characters in length of the TFTP server. v filename is the filename of the key file. Keys must be in OpenSSH format. Command use restricted (see Commands and user authority on page 6). Replace SSH public key Replaces an existing SSH public key. users -user_number -pk -key_index -upld -i ip_addr/hostname -l filename v user_number is a number from 1 to 12 that corresponds to the user number assigned in the Display all user profiles list. v key_index identifies the key number from 1 to 12 to replace. v ip_addr/hostname is a valid static IP address or an alphanumeric hostname string up to 63 characters in length of the TFTP server. v filename is the filename of the key file. Keys must be in OpenSSH format. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number. Valid targets -T system:mm[x] where x is the primary management-module bay number.
258
Table 79. users (management-module users) command (advanced management module only) (continued) Function Download SSH public key What it does Downloads a specific SSH public key to a TFTP server. Note: The -pk and -dnld options must be used exclusive of all other users command options. Command users -user_number -pk -key_index -dnld -i ip_addr/hostname -l filename v user_number is a number from 1 to 12 that corresponds to the user number assigned in the Display all user profiles list. v key_index identifies the key number from 1 to 12 to upload. v ip_addr/hostname is a valid static IP address or an alphanumeric hostname string up to 63 characters in length of the TFTP server. v filename is the filename of the key file. Command use restricted (see Commands and user authority on page 6). Connect to SSH public key Accept connections from SSH public key host. users -user_number -pk -key_index -af from=list v user_number is a number from 1 to 12 that corresponds to the user number assigned in the Display all user profiles list. v key_index identifies the key number from 1 to 12 to connect. v list is a comma-separate list of hostnames and IP addresses. The list is an alphanumeric string up to 511 characters in length that can include alphanumeric characters, commas, asterisks, question marks, exclamation points, periods, and hyphens. The string must be enclosed in double-quotes. Command use restricted (see Commands and user authority on page 6). -T system:mm[x] where x is the primary management-module bay number. Valid targets -T system:mm[x] where x is the primary management-module bay number.
259
Table 79. users (management-module users) command (advanced management module only) (continued) Function Comment SSH public key What it does Add comment to an SSH public key. Command users -user_number -pk -key_index -cm comment v user_number is a number from 1 to 12 that corresponds to the user number assigned in the Display all user profiles list. v key_index identifies the key number from 1 to 12 to comment. v comment is up to 255 characters in length, enclosed in double-quotes. Command use restricted (see Commands and user authority on page 6). Valid targets -T system:mm[x] where x is the primary management-module bay number.
Example: To create user number 3 with a user name of user3 who has supervisor rights to all BladeCenter components, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
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.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 set the command authority for an existing user number 4 to Blade Operator for blade 1, blade 2, and blade 3 and Chassis Log Management, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
users -4 -rbs:bo|clm:b1-b3|c1
To display all users, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
users
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.129 OK system:mm[1]> users -4 -rbs:bo|clm:b1-b3|c1 OK system:mm[1]> users 1. USERID Role:supervisor Blades:1|2|3|4|5|6|7|8|9|10|11|12|13|14 Chassis:1 Switches:1|2|3|4 2. <not used> 3. user3 Role:supervisor
260
Blades:1|2|3|4|5|6|7|8|9|10|11|12|13|14 Chassis:1 Switches:1|2|3|4 4. user4 Role:blade operator|chassis log management Blades:1|2|3 Chassis:1 Switches:N/A 5. <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]>
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 entry must all be on one line.
261
volts command (advanced management module only)

This command displays actual voltages and voltage threshold values for BladeCenter components.
Table 80. volts command Function Display voltage values What it does Command Valid targets -T system:mm[x] -T system:blade[x] where x is the primary management-module or blade server bay number.
Displays the current voltage and volts voltage threshold settings for the specified component: v The management module target displays the voltage values for the BladeCenter unit. v The blade server target displays the internal voltage values for the specified blade server. Note: The voltage values that display will vary based on BladeCenter unit and blade server type.
Example: To view the current voltage and voltage thresholds for the blade server in bay 3, while this blade server is set as the persistent command environment, at the system:blade[3]> prompt, type
volts
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]>
262
write command (advanced management module only)

This command saves the management-module configuration to the chassis of the BladeCenter unit or to a file.
Table 81. write command Function What it does Command write -config chassis Valid targets -T system:mm[x]
Save Saves an image of the management-module management-module configuration configuration to chassis to the BladeCenter unit chassis.
Save management-module configuration to file (no encryption) (BladeCenter H units only)
Saves an image of the write -config file -l filename management-module configuration -i ip_address to a file while data encryption is not where: enabled for the BladeCenter unit. v filename is the name of the configuration file. v ip_address is the IP address of TFTP server where the configuration file is located. Note: If the -l filename option is not specified, the default filename of asm.cfg is used. Command use restricted (see Commands and user authority on page 6).
Save management-module configuration to file (encryption) (BladeCenter H units only)
Saves an image of the management-module configuration to a file while data encryption is enabled for the BladeCenter unit. Note: When a configuration file is created with a pass-phrase (encryption enabled), if this configuration file is restored on the same management module, the pass-phrase entered during restoration is ignored.
write -config file -l filename -T system:mm[x] -i ip_address -p passphrase where x is the primary management-module where: bay number. v filename is the name of the configuration file. v ip_address is the IP address of TFTP server where the configuration file is located. v passphrase is a double-quote delimited pass-phrase that will be needed to restore the configuration file. Maximum pass-phrase length is 1600 characters. Note: If the -l filename option is not specified, the default filename of asm.cfg is used. Command use restricted (see Commands and user authority on page 6).
263
Table 81. write command (continued) Function Save management-module configuration to file (BladeCenter units other than BladeCenter H units) What it does Saves an image of the management-module configuration to a file. Command Valid targets
write -config file -l filename -T system:mm[x] -i ip_address where x is the primary where: management-module v filename is the name of bay number. the configuration file. v ip_address is the IP address of TFTP server where the configuration file is located. Command use restricted (see Commands and user authority on page 6).
Example: To save the management-module configuration to an image on the BladeCenter chassis, while management module 1 is set as the persistent command environment, at the system:mm[1]> prompt, type
write -config chassis
system:mm[1]> write -config chassis OK Configuration settings were successfully saved to the chassis system:mm[1]>
264
zonecfg command (advanced management module only)

This command sets and displays the serial attached SCSI (SAS) device information for BladeCenter components that is stored in I/O modules that support this feature.
Table 82. zonecfg command Function Display SAS zone list What it does Command Valid targets -T system:switch[x] where x is the I/O-module bay number. -T system:switch[x] where x is the I/O-module bay number.
Displays a list of SAS device zones zonecfg and their information that is stored in the specified I/O module.
Activate SAS zone
Activates a SAS zone, selected by index number, that is stored in the specified I/O module.
zonecfg -activate zone where zone is the index number for a valid zone. Command use restricted (see Commands and user authority on page 6).
Display SAS zone information
Displays information about a SAS zone, selected by index number, that is stored in the specified I/O module.
zonecfg -view zone where zone is the index number for a valid zone. Command use restricted (see Commands and user authority on page 6).
-T system:switch[x] where x is the I/O-module bay number.
Example: To view the list of SAS zones stored in the I/O module in bay 1, while this I/O module is set as the persistent command environment, at the system:switch[1]> prompt, type
zonecfg
system:switch[1]> zonecfg Index: 3 Name: Name3 Description string for zone config 3 Status: Inactive Type: Predefined Date: <mm> Index: 5 Name: Name5 Description string for zone config 5 Status: Inactive Type: Configurable Date: <mm> Index: 2 Name: Name2 Description string for zone config 2 Status: Inactive Type: Configurable Date: <mm> Index: 24 Name: Name24 Description string for zone config 24 Status: Active
265
Type: Configurable Date: <mm> system:switch[1]> zoncfg activate 5 OK system:switch[1]> zonecfg Index: 3 Name: Name3 Description string for zone config 3 Status: Inactive Type: Predefined Date: <mm> Index: 5 Name: Name5 Description string for zone config 5 Status: Pending Type: Configurable Date: <mm> Index: 2 Name: Name2 Description string for zone config 2 Status: Inactive Type: Configurable Date: <mm> Index: 24 Name: Name24 Description string for zone config 24 Status: Active Type: Configurable Date: <mm> system:switch[1]> </mm></mm></mm></mm></mm></mm></mm></mm>
266
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 commands and command-specific error messages, along with their definitions. v Common errors on page 269 v accseccfg command errors on page 271 v advfailover command errors on page 272 v alarm command errors on page 273 v alertcfg command errors on page 273 v alertentries command errors on page 274 v baydata command errors on page 275 v bofm command errors on page 275 v boot command errors on page 276 v v v v v v v v v v v v v v v v v v v v v v v v v v bootmode command errors on page 276 bootseq command errors on page 277 cin command errors on page 277 clear command errors on page 278 clearlog command errors on page 279 clock command errors on page 279 config command errors on page 280 console command errors on page 280 dhcpinfo command errors on page 281 displaylog command errors on page 281 displaysd command errors on page 282 dns command errors on page 283 env command errors on page 283 exit command errors on page 283 files command errors on page 283 fuelg command errors on page 284 health command errors on page 287 help command errors on page 288 history command errors on page 288 identify command errors on page 288 ifconfig command errors on page 289 info command errors on page 292 iocomp command errors on page 293 kvm command errors on page 293 ldapcfg command errors on page 293 led command errors on page 294
v list command errors on page 295 v modactlog command errors on page 295 v monalerts command errors on page 295
267
v v v v v v v v v v v v v v v v v v v v v v v v v v v v v v v v v v v
monalertsleg command errors on page 295 mt command errors on page 296 nat command errors on page 296 ntp command errors on page 296 ping command errors on page 297 pmpolicy command errors on page 297 portcfg command errors on page 297 ports command errors on page 297 power command errors on page 298 read command errors on page 299 remotechassis command errors on page 300 reset command errors on page 300 sddump command errors on page 301 security command errors on page 301 service command errors on page 301 shutdown command errors on page 302 slp command errors on page 302 smtp command errors on page 302 snmp command errors on page 303 sol command errors on page 304 sshcfg command errors on page 305 sslcfg command errors on page 306 syslog command errors on page 308 tcpcmdmode command errors on page 308 telnetcfg command errors on page 309 temps command errors on page 309 thres command errors on page 310 trespass command errors on page 310 uicfg command errors on page 310 update command errors on page 311 uplink command errors on page 313 users command errors on page 313 volts command errors on page 318 write command errors on page 318 zonecfg command errors on page 319
268
Common errors
This topic lists error messages that apply to all commands. Each command that has unique errors will also have a list of command-specific error messages.
Table 83. Common errors Error message Alarm panel card is not present in this slot. Backplane Mux card is not present in this slot. Command cannot be issued to this target. Type env - h for help on changing targets. Command line contains extraneous arguments. Duplicate option: option where option identifies the command option that was entered more than once. Each option can only be used once per command. Definition The user tries to issue a command to an empty alarm panel card slot. The user tries to issue a command to an empty backplane mux card slot. The user tries to issue a command to a target that does not support that command. Extra command arguments were entered. A user tries to enter the same command option in a single command multiple times. For example, dns -i 192.168.70.29 -i A user tries to enter the same command option in a single command multiple times. For example, env -T system:blade[4] -T system:blade[5]. A user tries to enter a command that does not exist. An error occurs while the management module is reading data of a option.
Error: Command not recognized. Type help to get a list of supported commands. Error reading data for the option - option where option identifies the command option that is returning an error. Error writing data for the option option where option identifies the command option that is returning an error. Firmware update is in progress. Try again later. Illegal option: option where option identifies the illegal short command option that was entered. Integer argument out of range (range - range) for option: argument where: v range identifies the range limits v option identifies the command option v argument identifies the integer that is out of range Internal error. Invalid integer argument for option: argument where: v option identifies the command option v argument identifies the invalid argument Invalid option.
An error occurs while the management module is writing a command option value.
Firmware update is in progress. An illegal short command option is entered.
An integer is entered that is out of range.
An internal error occurs. An invalid integer is entered.
An invalid command option is entered.
269
Table 83. Common errors (continued) Error message Invalid option argument for option: argument where: v option identifies the command option v argument identifies the invalid argument Invalid option for this target: option where option identifies the option that is invalid. Invalid parameter. Input must be numeric. Invalid syntax. Type command - h for help. where command identifies the command that is returning an error. Invalid target path. Long option option requires an argument where option identifies the long command option that is missing an argument. Missing option name Network Clock card is not present in this slot. Read/write command error. Short option option requires an argument where option identifies the short command option that is missing an argument. That blade is presently not available. Please try again shortly. The argument for the option arg is outside the valid range. where arg identifies the command option that is out of range. The target bay is empty. The user tries to issue a command to an empty blade bay, blower bay, I/O-module bay, management-module bay, or power bay. A user tries to issue a command to a target that is out of range for that target. For example, the env -T system:blade[15] command is out of range because the BladeCenter unit has only 14 blade bays. The user tries to issue a command to a target which is out of range for that target. The user tries to issue a command to an empty blade bay. The user tries to issue a command to an empty chassis cooling unit bay. The user tries to issue a command to an empty management module bay. A user tries to connect to a blade that is already in use. A user tries to enter an arg outside the options valid range. A dash (-) is entered without a command option name. The user tries to issue a command to an empty network card slot. An error occurs while the management module is executing the command. A short command option is entered without a required argument. A user tries to issue a command to a target that is not valid. A long command option is entered without a required argument. A user tries to enter a non-numeric argument. A user tries to enter a command that is not syntactically correct. A user tries to issue a command with an invalid option for the target. Definition An invalid argument for a command option is entered.
The target bay is out of range.
The target slot is out of range. There is no blade present in that bay. There is no blower present in that bay. There is no management module present in that bay.
270
Table 83. Common errors (continued) Error message There is no power source present in that bay. There is no switch present in that bay. Unknown long option: option where option identifies the command option that is unknown. Unknown option: option where option identifies the command option that is unknown. Unrecognized long option: option where option identifies the illegal long command option that was entered. Unsupported target type. User does not have the authority to issue this command. A user tries to issue a command to an unsupported target. A user lacks the authority level necessary to execute a command. An illegal long command option is entered. An unknown option is used. Definition The user tries to issue a command to an empty power module bay. The user tries to issue a command to an empty I/O module bay. A user tries to enter a long option that is not valid for the command.
accseccfg command errors

This topic lists error messages for the accseccfg command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 84. accseccfg command errors Error message Password required is currently disabled. Definition A user without a password tries to change the security level to -high. User must have a password to perform this action. A user without a password tries to change the security level to -legacy. User must have a password to perform this action. An error occurs while the management module is reading the security level. An error occurs while the management module is setting the security level to -high. An error occurs while the management module is setting the security level to -legacy. The user tries to set the account security to high settings while changing individual option values. The user tries to set the account security to legacy settings while changing individual option values.
Password required is currently enabled.
Reading account security level failed. Setting account defaults to high level failed. Setting account defaults to legacy level failed. The -high option cannot be used with other options. The -legacy option cannot be used with other options.
The account inactivity disable time period must be greater A user tries to set the account inactivity disable time than the account inactivity alert time period. period to be less than the account inactivity alert time period.
271
Table 84. accseccfg command errors (continued) Error message The argument for the option -dc is outside the valid range. Definition The user tries to set the -dc option to a value outside of its valid range.
The argument for the option -ia is outside the valid range. The user tries to set the -ia option to a value outside of its valid range. The argument for the option -id is outside the valid range. The user tries to set the -id option to a value outside of its valid range. The argument for the option -lf is outside the valid range. The user tries to set the -lf option to a value outside of its valid range.
The argument for the option -lp is outside the valid range. The user tries to set the -lp option to a value outside of its valid range. The argument for the option -pe is outside the valid range. The user tries to set the -pe option to a value outside of its valid range.
The argument for the option -rc is outside the valid range. The user tries to set the -rc option to a value outside of its valid range. The minimum password change interval must be less than the password expiration period (%d days or %d hours). The password expiration period (%d days or %d hours) must be greater than the minimum password change interval. User must have a password to change the Password required setting. A user tries to set the -pc option to a value greater than the -pe option. A user tries to set the -pe option to a value less than the -pc option. A user without a password tries to change the -pr option.
advfailover command errors

This topic lists error messages for the advfailover command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 85. advfailover command errors Error message Operation failed. Operation not allowed, since the standby MM is not present. Unknown option: option where option identifies the illegal command option that was entered. Definition An error occurs while the management module is processing the command. The user tries to enable advanced failover when there is no standby management module installed in the BladeCenter unit. The user tries to enter an illegal command option.
272
alarm command errors

This topic lists error messages for the alarm command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 86. alarm command errors Error message A duplicate option is found in the requested command. Alarm Description must be provided for setting an alarm. Alarm ID must be from 1 to 255. Category must be from 1 to 255. Generator ID must be from 1 to 255. Generator ID must be provided. Module ID must be from 1 to 255. No active alarm. No matching alarm. Reading system health summary failed. Severity level must be provided for setting an alarm. Software Generator ID must be from 1 to 255. The entered Alarm Key is not in proper format. Unable to acknowledge the requested alarm. Unable to clear the requested alarm. Unable to set the requested alarm. Definition A duplicate argument is entered. The user tries to set an alarm without providing an alarm description. An invalid alarm ID is entered. An invalid category argument is entered. An invalid generator ID is entered. A generator information ID is provided without a generator ID. An invalid module ID is entered. No active alarm is found for the command target. No matching alarm is found for the command target. An error occurs while the management module is getting the system health summary. The user tries to set an alarm without specifying the severity level. The user tries to enter an invalid generator information. The user tries to enter an invalid alarm key. An error occurs while the management module is acknowledging an alarm. An error occurs while the management module is clearing an alarm. An error occurs while the management module is setting an alarm.
alertcfg command errors

This topic lists errors for the alertcfg command. There are no unique errors for the alertcfg command. See Common errors on page 269 for a list of error messages that apply to all commands.
273
alertentries command errors

This topic lists error messages for the alertentries command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 87. alertentries command errors Error message -test must be used exclusive of other options. An entry cannot be modified and deleted in the same command. Arguments containing spaces must be enclosed in quotation marks. Enabling the application alert failed. Generating test alert failed. Invalid input. Angle brackets are not allowed in the name field. Invalid option. Definition The user tries to issue a command with the -test option at the same time as the other options. A user tries to modify an entry and delete it in the same command. A user tries to enter a string containing spaces that has an opening quotation mark without a closing quotation mark. An error occurs while the management module is enabling the application alert. An error occurs while the management module is generating a test alert. A user tries to enter a string parameter containing < or > for the -n (name) command option. An invalid command option is entered. This includes numeric options for the alert recipient that are not from 1 through 12. A user tries to enter a parameter value containing non-numeric characters for a command option requiring numeric input. An error occurs while the management module is restoring previous configured value for the application alert. A user tries to enter an invalid email address for the -e command option. A user tries to enter an invalid IP address for the -i command option. An alert entry number is entered without the leading dash ( - ). A user tries to enter too many characters in an input field. A required command option is missing when creating a user.
Invalid parameter. Input must be numeric.
Restoring previous configured value for the application alert failed. Syntax error. -e can only be used in conjunction with the email argument. Syntax error. -i can only be used in conjunction with the director argument. Syntax error. Type alertentries -h for help. The name must be less than 32 characters long. When creating a new entry, all options are required.
274
baydata command errors

This topic lists error messages for the baydata command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 88. baydata command errors Error message Invalid blade bay number The bay data must be quote-delimited. Invalid input. The bay data string must be less than the maximum number of characters allowed. The -clear and -data options cannot be used in the same command. User not authorized to change bay data for bay number. Error writing bay data to blade bay bayNum. where bayNum is the blade bay number. Definition The command has an invalid bay number. User enters bay data with -data option for a blade without double quotation marks. User enters bay data with -data option for a blade that exceeds the maximum length of 60 characters. User issues a command with both -clear and -data options. An unauthorized user issues a command to change bay data for the specified blade. An internal error occurs while the user is changing bay data for the specified blade.
bofm command errors

This topic lists errors for the bofm command. Note: The BOFM command displays parsing errors and duplicate addresses that point to flaws in the comma-separated values (csv) configuration database file. The BladeCenter Open Fabric Manager is not a standard management module feature; it is offered and documented separately. See the BladeCenter Open Fabric Manager Installation and Users Guide for more detailed information. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 89. bofm command errors Error message Applying new configuration on MM failed. Confirming configuration change failed. Definition Displayed when an error occurs while the advanced management module is applying the BOFM configuration. Displayed when an error occurs while the advanced management module is confirming a configuration change. Displayed when an error occurs while the advanced management module is getting BOFM status. Displayed when an error occurs while the advanced management module is getting duplicates. Displayed when an error occurs while the advanced management module is getting parsing errors. Displayed when a user issues a command to apply BOFM configuration to the advanced management module without both -i and -l options.
Getting BOFM status failed. Getting duplicates failed. Getting parsing errors failed. -i and -l are both required to upload a BOFM configuration file.
275
Table 89. bofm command errors (continued) Error message Login failed. Parsing errors. Resetting BOFM configuration on MM failed. Retrieving the file from TFTP server failed. Definition Displayed when login fails while applying BOFM configuration to the advanced management module. Displayed when an error occurs while the advanced management module is parsing the BOFM status. Displayed when an error occurs while the advanced management module is resetting the BOFM configuration. Displayed when an error occurs while the advanced management module is retrieving the configuration file from a TFTP server.
boot command errors

This topic lists errors for the boot command. There are no unique errors for the boot command. See Common errors on page 269 for a list of error messages that apply to all commands.
bootmode command errors

This topic lists errors for the bootmode command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 90. bootmode command errors Error message Command cannot be issued to this target. Error retrieving blade type. Error retrieving the boot mode of this blade. Set the blade boot mode to option failed where option is the selected boot mode. The format of the received data is wrong. A wrongly formatted data is received. Definition The command is directed to a blade server that does not support the bootmode feature. The management module is unable to read the blade type. The management module is unable read the boot mode of the blade. The management module is unable to set the blade boot mode to the specified value.
276
bootseq command errors

This topic lists error messages for the bootseq command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 91. bootseq command errors Error message Error writing boot sequence. First device cannot be set to nodev. Invalid device for this blade or chassis. No duplicate settings are allowed. Second device cannot be set to nodev when third or fourth device is set. Third device cannot be set to nodev when fourth device is set. Definition An error occurs while the management module is processing the command. The user tries to set the first boot device to nodev. The user tries to set a boot device to an invalid choice. The user tries to set multiple slots in the boot sequence to the same device. The user tries to set the second boot device to nodev. The user tries to set the third boot device to nodev.
cin command errors

This topic lists error messages for the cin command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 92. cin command errors Error message CIN blade pair TLV get failed CIN global TLV get failed. CIN command failed. Invalid index parameter. Input must be numeric. Invalid index parameter. Input out of range. An error occurred while clearing CIN entry Invalid option argument for -global -en: An error occurred while changing CIN global status setting An error occurred while enabling/disabling CIN entry. Invalid option argument for -en to enable an entry. Definition An internal error occurs while the user is getting CIN blade configuration parameters. An internal error occurs while the user is getting a CIN global configuration parameter. An internal error occurs while the user is executing a CIN command. A user issues a command with a non-numeric index. A user issues a command with an index which is out of range. An internal error occurs while the user is clearing a CIN entry. A user issues a command with an invalid argument for -global -en option. An internal error occurs while user is changing CIN global status setting. An internal error occurs while the user is enabling/disabling a CIN entry. An internal error occurs while the user is enabling/disabling a CIN entry.
277
Table 92. cin command errors (continued) Error message Invalid IP argument for an option. Enter 4 bytes separated by 3 dots. Invalid IP argument for an option. Too many bytes. Invalid IP argument for an option. Too few bytes Invalid IP argument for an option. Each byte has to be in the range (0-255). Both -id and -ip are required for adding a CIN entry. Internal error getting CIN entry Duplicate CIN (-id, 0.0.0.0) pairs are not allowed. Please try again. -id cannot be the same as the blade management VLAN ID. Please try again. Duplicate -ip is not allowed. Please try again. -ip cannot be the same as the management module IP address. Please try again -ip cannot be multicast. Please try again. Internal error checking CIN entry. An error occurred while setting CIN entry. Definition A user issues a command argument for IP address option which is invalid because it is too long, too short, or not numeric. A user issues a command with an invalid argument for IP address option which has more than four parts. A user issues a command with an invalid argument for IP address option which has fewer than four parts. A user issues a command with an invalid argument for IP address option, each part of which is not in the range of 0-255. A user issues a command to add an entry without both -id_ and -ip options. An internal error occurs while the user is getting CIN entry configuration parameters. A user issues a command with a duplicated -id/0.0.0.0 pair. A user issues a command with a VLAN ID which is the same as the VLAN ID of the blade management. A user issues a command with a duplicated IP address. A user issues a command with an IP address which is the same as the IP address of the advanced managment module. A user issues a command with an IP address which is the same as the IP address of the multicast. An internal error occurs while the system checks user input for the CIN entry configuration. An internal error occurs while configuring a CIN entry.
clear command errors

This topic lists error messages for the clear command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 93. clear command errors Error message Firmware update is in progress. Try again later. Definition The user tries to reset the management module to its default configuration during a firmware update. The error message displays and the management-module configuration does not reset. An error occurs while the management module is resetting the management module to its default configuration. The error message displays and the management-module configuration does not reset.
Internal error resetting to defaults.
278
clearlog command errors

This topic lists error messages for the clearlog command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 94. clearlog command errors Error message Error clearing the event log. Definition An error occurs while the management module is clearing the event log.
clock command errors

This topic lists error messages for the clock command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 95. clock command errors Error message GMT+2:00 requires one of the following dst values: off, ee, gtb, egt, or fle GMT+10:00 requires one of the following dst values: off, ea, tas, or vlad GMToffset requires one of the following dst values: off, uc, other where offset is the daylight-savings time offset. Invalid dst setting for GMT+10:00: setting where setting is the illegal daylight-savings time setting that was entered. Invalid dst setting for GMT+2:00: setting where setting is the illegal daylight-savings time setting that was entered. Invalid dst setting for GMToffset: setting where setting is the daylight-savings time offset and setting is the illegal daylight-savings time setting that was entered. Invalid dst setting. The gmt offset does not support dst. Invalid input for -dst. Reading date and time failed. Reading GMT offset failed. Reading status of daylight savings time failed. The user tries to turn on dst for a GMT offset that does not support daylight-savings time. A user tries to enter an invalid argument for the option -dst. An error occurs while the management module is reading the date and time. An error occurs while the management module is reading the GMT offset. An error occurs while the management module is reading the daylight savings time status. The user tries to enter an invalid -dst setting for a GMT offset of -9, -8, -7, -6, or -5. The user tries to enter an invalid -dst setting for a GMT offset of 2. The user tries to enter an invalid -dst setting for a GMT offset of 10. Definition The user tries to change the GMT offset to +2:00 without adjusting the DST setting. The user tries to change the GMT offset to +10:00 without adjusting the DST setting. The user tries to change the GMT offset to -9, -8, -7, -6, or -5 without adjusting the DST setting.
279
Table 95. clock command errors (continued) Error message The gmt offset you entered does not support dst. Turning dst off. Definition A user tries to enter a GMT offset that does not support daylight savings time.
config command errors

This topic lists error messages for the config command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 96. config command errors Error message Arguments containing spaces must be enclosed in quotation marks. Contact must be enclosed in quotation marks. Invalid input. Contact may not contain angle brackets. Invalid input. Location may not contain angle brackets. Invalid input. Name must be less than 16 characters. Invalid input. Name may not contain angle brackets. Definition The user tries to enter an advanced management module Contact or Location without ending double quotes. The user tries to enter an advanced management module Contact without enclosing it in double quotes. The user tries to enter an advanced management module Contact containing angle brackets (< and >). The user tries to enter an advanced management module Location containing angle brackets (< and >). The user tries to enter a name that is more than 15 characters in length. The user tries to enter a blade server name that contains angle brackets: < or >.
Invalid input. Only alphanumeric characters, underscores, The user tries to enter a name for the advanced hyphens, pound signs, and periods are allowed. management module that is not valid. Location must be enclosed in quotation marks. The user tries to enter an advanced management module Location without enclosing it in double quotes.
console command errors

This topic lists error messages for the console command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 97. console command errors Error message A SOL session socket was not available. Error entering console mode. Global SOL is not enabled Internal Error SOL is not ready Definition The command-line interface fails to establish an SOL connection to a blade. An error occurs while the management module is trying to establish an SOL connection. SOL is not enabled globally. An error occurs while the management module is processing the command. The blade server is not available, or when a socket needed to establish a connection to the blade server is not available.
280
Table 97. console command errors (continued) Error message SOL on blade is not enabled SOL session is already active Definition SOL is not enabled on the blade server where the user is trying to start an SOL session. The user cannot start an SOL session with a blade server because an SOL session with that blade server is already in progress.
The maximum number of sessions to this blade has been The blade server has no available sessions for a user to reached. connect to. Unknown error occurred while attempting to connect. An unknown error occurs when connecting to a blade server.
dhcpinfo command errors

This topic lists errors for the dhcpinfo command. There are no unique errors for the dhcpinfo command. See Common errors on page 269 for a list of error messages that apply to all commands.
displaylog command errors

This topic lists error messages for the displaylog command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 98. displaylog command errors Error message (There are no more entries in the event log.) -f and -a cannot be used at the same time. -l and -i options must be used exclusive of the other options. -lse option must be used exclusive of the other options Definition There are no more event log entries to display. The user tries to use the -f and -a options in the same command. The user tries to issue a command with the -l and -i options at the same time as other options. The user tries to issue a command with the -lse option at the same time as other options.
Both -l and -i options must be provided to save event log. The user tries to issue a command to save the event log without -l and -i provided. Cannot open file: filename where filename is the name of the file that was entered when the error occurred. Duplicate date filter: filter where filter is the duplicate date filter that was entered. Duplicate severity filter: filter where filter is the duplicate severity filter that was entered. Duplicate source filter: filter where filter is the duplicate source filter that was entered. The user tries to use duplicate source filters. The user tries to use duplicate severity filters. The user tries to use duplicate date filters. An error occurs while the management module is trying to open a file.
281
Table 98. displaylog command errors (continued) Error message Invalid date filter: filter where filter is the invalid date filter that was entered. Invalid severity filter: filter where filter is the invalid severity filter that was entered. Invalid source filter: filter where filter is the invalid source filter that was entered. Putting event log file filename to tftp server ipaddress failed where: v filename is the name of the log file v ip_address is the IP address of the TFTP server Reading log entries failed. An error occurs while the management module is reading log entries. An error occurs while the management module is trying to put the event log file to TFTP server. The user tries to use an invalid source filter. Displays when the user tries to use an invalid severity filter. Definition The user tries to use an invalid date filter.
displaysd command errors

This topic lists error messages for the displaysd command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 99. displaysd command errors Error message -save and -i must both be specified when saving the service data. Can not get the SRCs detail information. Error retrieving blade type. Error transferring file. No additional information for this SRC. Definition A user tries to save the service data without specifying both the file name and IP address of the TFTP server. The advanced management module fails to get the SRC detail information. The advanced management module fails to read the blade server type. An unspecified TFTP error occurs. The advanced management module tries to get the detail information of a SRC which does not have detail information. An error occurs while the management module is processing the command. The advanced management module receives wrongly formatted data.
Read/write command error. The format of the received data is wrong.
282
dns command errors

This topic lists error messages for the dns command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 100. dns command errors Error message -on and -off cannot both be used in the same command. At least one address is required to enable DNS. DNS State Can not be determined. Input length is greater than the maximum characters allowed. Invalid ip address Reading status of DNS failed. Reading status of interface failed. Definition A user tries to enable and disable DNS in the same command. A user tries to enable DNS without configuring at least one address. An error occurs while the management module is reading the DNS state. A user tries to enter too many characters in an input field. A user tries to set an invalid IP address. An error occurs while the management module is reading the DNS state. An error occurs while the management module is reading the status of an interface.
env command errors

This topic lists errors for the env command. There are no unique errors for the env command. See Common errors on page 269 for a list of error messages that apply to all commands.
exit command errors

This topic lists errors for the exit command. There are no unique errors for the exit command. See Common errors on page 269 for a list of error messages that apply to all commands.
files command errors

This topic lists error messages for the files command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 101. files command errors Error message %, /, and \ are not allowed in the filename. Directory does not exist. Error deleting file filename where filename is the name of the file that was entered for deletion. Definition The user tries to enter a filename that is invalid. The user tries to enter a directory that does not exist. An error occurs while the management module is trying to delete a file.
283
Table 101. files command errors (continued) Error message Error deleting file filename where filename is the name of the file that was entered for deletion. Error reading file list. Error reading file system space. Error reading first file in dir directory. where directory is the name of the directory that was entered. File index out of sequence. File list exhausted. File not found. Filename must be less than 256 characters General, unknown error. Invalid command sent. invalid directory, filename. Invalid file or directory name. The directory name must be less than 256 characters. Unknown caller id. Unknown command. Unknown directory path. An error occurs while the management module is reading the index. An error occurs while the management module is reading the file list. The specified file is not found. The user tries to enter a filename that is longer than 256 characters. A command is rejected for unknown reasons. The user tries to enter an invalid command. The user tries to enter an invalid directory and filename. The user tries to enter an invalid directory or filename. A user tries to enter a directory name that is more than 256 characters in length. The caller ID is not recognized. The user tries to enter a command that is not recognized. The user tries to enter a directory path that is not recognized. An error occurs while the management module is reading the directory file list. An error occurs while the management module is reading the file system space. An error occurs while the management module is reading the first file in the directory. Definition The user tries to delete a directory or delete a file that does not exist.
fuelg command errors

This topic lists error messages for the fuelg command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 102. fuelg command errors Error message A power module failure in domain domain_number can result in an immediate shutdown. where domain_number identifies the power domain. Blade blade_number is not allowed to power on because of insufficient power. where blade_number identifies the blade server. Definition A power module fails and the domain in which it is installed loses redundancy. The BladeCenter unit might turn itself off, based on the power management configuration. There is insufficient power available in the power domain to turn on this blade server.
284
Table 102. fuelg command errors (continued) Error message Blade blade_number is throttled. where blade_number identifies the blade server. Blade blade_number was instructed to power off due to power budget restrictions. where blade_number identifies the blade server. Checking if power is preallocated to switch bay_number failed. where the bay_number I/O module bay number. Demand exceeds a single power module. Throttling can occur in power domain domain_number. where domain_number identifies the power domain. Effective CPU Speed not available. Error reading blade power management capability. Error writing data for the option -pme Please make sure the blade is powered on Getting blade health state parameters failed. Getting blade pcap maximum value failed. Getting blade pcap minimum value failed. Getting blade power cap level failed. Getting data of domain 1 (or 2 ) failed. Getting domain latest power sample failed. Getting duty cycle numbers failed. Getting duty cycle numbers of bladeblade_number failed. where blade_number identifies the blade server. Getting dynamic power management capabilty of bladeblade_number failed. where blade_number identifies the blade server. Getting information of powerbay_number failed. where the bay_number identifies the specified power module. Getting module domain map for blowerbay_number failed. An error occurs while the management module is reading module domain map of specified chassis cooling unit. where the bay_number identifies the specified chassis cooling unit. An error occurs while the management module is reading data of specified power module. An error occurs while the management module is reading the dynamic power management capability of specified blade server. An error occurs while the management module is reading the blade server health state parameters. An error occurs while the management module is reading the blade server power cap maximum value. An error occurs while the management module is reading the blade server power cap minimum value. An error occurs while the management module is reading the blade server power cap level. An error occurs while the management module is reading the data of power domain 1 (or 2). An error occurs while the management module is reading the latest power domain sample. An error occurs while the management module is reading the duty cycle numbers. An error occurs while the management module is reading the duty cycle numbers of specified blade server. The power requirements of components installed in a power domain exceed the level required for redundant operation. Power throttling of BladeCenter components might be able to correct the problem. An error occurs while the management module is reading the effective CPU Speed. An error occurs while the management module is reading the blade server power management capability. The user attempts to enable power management and capping for a blade server that is turned off. An error occurs while the management module is checking if power is preallocated for the specified I/O module. Definition The specified blade server has reduced power (power throttling) in response to a thermal event or oversubscription condition. BladeCenter power management turns off a blade server that is already on in response to a oversubscription condition.
285
Table 102. fuelg command errors (continued) Error message Getting module domain map for midplane failed. Getting module domain map for MMbay_number failed. where the bay_number identifies the specified management module. Getting module domain map for muxbay_number failed. where the bay_number varies based on the problem that was encountered. Getting module domain map for NCbay_number failed. where the bay_number varies based on the problem that was encountered. Getting module domain map of mtbay_number failed. where the bay_number identifies the specified mt. Getting module domain map of PM Cooling Device <slot> An error occurs while the management module is reading failed. the module domain map of specified PM Cooling Device. where bay_number identifies the blade server. Getting module domain map of switchbay_number failed. where the bay_number represents the specified I/O module. Getting module domain map of Telco alarm panel failed. Getting power management policy for domain domain number failed where domain number is the number of the domain that was entered. Getting power state of bladeblade_number failed. where blade_number identifies the blade server. Getting power values for blowerbay_number failed. where the bay_number varies based on the problem that was encountered. Getting power values for DSSbay_number failed. where the bay_number represents the specified DSS. Getting power values for MMbay_number failed. where the bay_number represents the specified management module. Getting power values for NCbay_number failed. where the bay_number represents the specified NC. Getting power values for switchbay_number failed. where the bay_number represents the specified I/O module. An error occurs while the management module is reading the power values of specified I/O module. An error occurs while the management module is reading the power values of specified NC. An error occurs while the management module is reading the power values of specified management module. An error occurs while the management module is reading the power values of specified DSS. An error occurs while the management module is reading the power values of specified chassis cooling unit. An error occurs while the management module is reading the power state of specified blade server. An error occurs while the management module is reading the module domain map of Telco alarm panel. An error occurs while the management module is reading the power management policy of specified domain. An error occurs while the management module is reading the module domain map of specified I/O module. An error occurs while the management module is reading the module domain map of specified mt. An error occurs while the management module is reading the module domain map of specified NC. An error occurs while the management module is reading the module domain map of specified mux. Definition An error occurs while the management module is reading the module domain map for midplane. An error occurs while the management module is reading the module domain map of specified MM.
286
Table 102. fuelg command errors (continued) Error message Getting power values of midplane within domain failed. Getting power values of mtbay_number within domain failed. where the bay_number represents the specified mt. Getting power values of muxbay_number within domain failed. where the bay_number represents the specified mux. Getting power values of PM Cooling Device bay_number failed where the bay_number represents the specified PM cooling device. Getting power values of Telco alarm panel within domain failed. Getting status of domain domain number failed where domain_number identifies the power domain. Getting the power control setting on blade failed. Maximum CPU Speed not available. pcap must be between <min> and <max> Watts. There are mismatched power modules in power domain domain_number. where domain_number identifies the power domain. There is no thermal trending data to display. There is no trending data to display. Unable to change power management settings, domain may be oversubscribed. An error occurs while the management module is reading thermal trending data. An error occurs while the management module is reading power trending data. An error occurs while the management module is configuring the power management policy. An error occurs while the management module is reading the power control setting on blade server. An error occurs while the management module is reading maximum CPU Speed. The user input for power cap is out of the range. The power modules installed in a power domain have different ratings. An error occurs while the management module is reading the power values of Telco alarm panel within domain. An error occurs while the management module is reading the status of specified domain. An error occurs while the management module is reading the power values of specified PM Cooling Device. An error occurs while the management module is reading the power values within domain of specified mux. Definition An error occurs while the management module is reading the power values of midplane within domain. An error occurs while the management module is reading the power values within domain of specified mt.
health command errors

This topic lists errors for the health command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 103. health command errors Error message Getting system health summary failed. Definition An error occurs while the management module is reading system health summary.
287
help command errors

This topic lists errors for the help command. There are no unique errors for the help command. See Common errors on page 269 for a list of error messages that apply to all commands.
history command errors

This topic lists errors for the history command. There are no unique errors for the history command. See Common errors on page 269 for a list of error messages that apply to all commands.
identify command errors

This section lists error messages for the identify command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 104. identify command errors Error message -d can only be used on the system target. -d can only be used with the -s on. Delay value must be less than max where max is the preset maximum. Delay value must be less than 60. Error accessing remote LED. Error getting LED status. Error reading system LED state. Error setting system LED. Error unknown command. Identify: Error accessing remote LED. Identify: error getting LED status. Identify: error setting Management Module LED. Identify: Error unknown command. Identify: LED status not supported. A user tries to enter a -d value that is greater than 60 seconds. An error occurs while the management module is accessing a remote LED. An error occurs while the management module is reading the blade LED status. An error occurs while the management module is reading the system LED status. An error occurs while the management module is setting the system LED. The user tries to enter unrecognized command. An error occurs while the management module is processing the command. An error occurs while the management module is processing the command. An error occurs while the management module is processing the command. An error occurs while the management module is processing the command. The user tries to get the status of an LED that is not supported by a blade server. Definition The user tries to issue a command with the -d option to a target other than system. The user tries to issue a command with the -d option without -s on setting. The user input for option -d exceeds the maximum.
288
Table 104. identify command errors (continued) Error message Identify: unknown LED state state where state identifies the LED state that was returned. Identify: Unknown return status status where the status value varies based on the problem that was encountered. Syntax error. The user tries to enter an invalid command option. Type identify -h for command help. An error occurs while the management module is processing the command. Definition An LED state other than on, off, or blinking is returned.
ifconfig command errors

This topic lists error messages for the ifconfig command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 105. ifconfig command errors Error message -em cannot be reconfigured while Stacking Mode is enabled on the AMM. -ep cannot be reconfigured while Stacking Mode is enabled on the AMM. -up and -down can not be both used in same line. Cannot apply network configuration. Blade in configuration phase. Configuration not supported on this switch type. Enabling/Disabling new IP configuration failed. Error reading gateway address. Definition The user tries to issue a command with the -em option while Stacking Mode is enabled on the advanced management module. The user tries to issue a command with the -ep option while Stacking Mode is enabled on the advanced management module. The user tries to issue a command with both the -up and -down options. An error occurs while the management module is setting the network configuration. The user tries to issue a command to an unsupported I/O module type. An error occurs while the management module is enabling or disabling the new IP configuration. An error occurs while the management module is reading the gateway address of a network interface (eth0 or eth1). An error occurs while reading the IP address of the integrated system management processor on a blade server, or while reading the IP address of a network interface (eth0 or eth1). An error occurs while the management module is reading the burned-in MAC address of a network interface (eth0 or eth1). An error occurs while the management module is reading the data rate setting of a network interface (eth0 or eth1). An error occurs while the management module is reading the DHCP setting of a network interface (eth0). An error occurs while the management module is reading the duplex setting of a network interface (eth0 or eth1).
Error reading IP Address.
Error reading the burned-in MAC address.
Error reading the data rate. Error reading the DHCP configuration. Error reading the duplex setting.
289
Table 105. ifconfig command errors (continued) Error message Error reading the hostname. Error reading the locally administered MAC address. Definition An error occurs while the management module is reading the host name of a network interface (eth0). An error occurs while the management module is reading the locally administered MAC address of a network interface (eth0 or eth1). An error occurs while the management module is reading the maximum transmission unit (MTU) setting of a network interface (eth0 or eth1). An error occurs while the management module is reading the subnet mask of a network interface (eth0 or eth1). An error occurs while the management module is setting the IP address of the integrated system management processor on a blade server.
Error reading the maximum transmission unit.
Error reading the subnet mask. Error writing IP Address.
Getting blade cKVM status for blade blade_number failed. An error occurs while the management module is reading the cKVM status of targeted blade. where blade_number identifies the blade server. Getting interface status failed. I/O Module is in Stacking Mode and cannot change its Gateway configuration. I/O Module is in Stacking Mode and cannot change its IP configuration. I/O Module is in Stacking Mode and cannot change its Subnet configuration. Invalid gateway address. Invalid hostname. Invalid hostname arg for option: hostname. Consecutive dots where: v option identifies the command option v hostname identifies the invalid hostname argument Invalid hostname arg for option: hostname. Length has to The user tries to enter a hostname longer than 63 be < 64 characters characters. where: v option identifies the command option v hostname identifies the invalid hostname argument Invalid hostname arg for option: hostname. Only alphanumeric chars and._- allowed where: v option identifies the command option v hostname identifies the invalid hostname argument The user tries to enter an hostname that contains invalid characters. Valid characters that can be used in a hostname are letters, numbers, periods (. ), dashes ( - ), and underscores ( _ ). An error occurs while the management module is reading the interface status. The user tries to issue a command to change the Gateway configuration with the I/O Module in Stacking Mode. The user tries to issue a command to change the IP configuration with the I/O Module in Stacking Mode. The user tries to issue a command to change Subnet configuration with I/O Module in Stacking Mode. The user tries to enter an invalid gateway address. The user tries to enter an invalid hostname. The user tries to enter consecutive periods (. ) as part of a hostname.
290
Table 105. ifconfig command errors (continued) Error message Invalid ip address. Definition Displays for one of the following errors: v A user tries to set the IP address of system:blade[1]:sp either to an invalid IP address, or an IP address whose last part is greater than 255 (the max number of blade servers). v A user tries to enter an invalid IP address for the -i (static IP address) command option. 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 to 255.
Invalid IP arg for option: ip_address. Each byte has to be in the range (0-255) where: v option identifies the command option v ip_address identifies the invalid IP address argument Invalid IP arg for option: ip_address. Enter 4 bytes separated by 3 dots where: v option identifies the command option v ip_address identifies the invalid IP address argument Invalid IP arg for option: ip_address. Too few bytes where: v option identifies the command option v ip_address identifies the invalid IP address argument Invalid IP arg for option: ip_address. Too many bytes where: v option identifies the command option v ip_address identifies the invalid IP address argument Invalid mac address. Invalid MAC arg for option: address. Invalid syntax where: v option identifies the command option v address identifies the invalid MAC address argument Invalid MAC arg for option: address. Multicast addresses not allowed where: v option identifies the command option v address identifies the invalid MAC address argument Invalid MAC arg for option: address. Too few bytes where: v option identifies the command option v address identifies the invalid MAC address argument Invalid MAC arg for option: address. Too many bytes where: v option identifies the command option v address identifies the invalid MAC address argument Invalid option for ethernet interface.
The user tries to enter an IP address that is too long. IP addresses must follow the standard format: xxx.xxx.xxx.xxx, where each xxx is a number from 0 to 255.
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 to 255. The user tries to enter an IP address with too many bytes. IP addresses must follow the standard format: xxx.xxx.xxx.xxx, where each xxx is a number from 0 to 255. The user tries to enter an invalid MAC address. The user tries to enter an invalid MAC address.
The user tries to enter a multicast address.
The user tries to enter a MAC address with too few bytes.
The user tries to enter a MAC address with too many bytes.
A user tries to change a static property of eth1 (hostname, DHCP, data rate, duplex).
291
Table 105. ifconfig command errors (continued) Error message Invalid parameter. The locally administered MAC address cannot be a multicast address. Invalid parameter. The MTU must be between 60 and 1500, inclusive. Invalid parameter. Valid values for -c are dhcp, static, or dthens. Invalid parameter. Valid values for -d are auto, half, and full. Invalid parameter. Valid values for -r are auto, 10, and 100. Invalid subnet mask. Maybe blade network configuration is still in discovery phase. Please check and try again. Please check blade health status and try again. The target must be system:blade[1]:sp for this command Definition The user tries to set the locally administered MAC address to a multicast address. The user tries to enter an MTU outside the valid range. A user tries to enter an invalid parameter for the -c (Ethernet configuration method) command option. The user tries to enter an invalid parameter with the -d option. The user tries to enter an invalid parameter with the -r option. The user tries to enter an invalid subnet mask. An error occurs while the management module is reading the blade network configuration. An error occurs while the management module is reading the blade health status. A user tries to issue the ifconfig -i <ip address> -T system:blade[x]:sp to a blade server other than blade[1].
info command errors

This topic lists error messages for the info command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 106. info command errors Error message Device not found Getting blade H8 firmware VPD data of blade blade_number failed. where blade_number identifies the blade server. Getting compact flash cards information failed. Getting firmware version of cKVM bay_number failed. where the bay_number specifies the cKVM. Getting firmwares VPD data of type failed. Getting name of blade blade_number failed. where blade_number identifies the blade server. Getting name of mm bay_number failed. where the bay_number specifies the management module. Status: Unable to read status. Unknown device type. An error occurs while the management module is reading the firmware update status. The command is targeted to an unknown device type. An error occurs while the management module is reading the name of the targeted management module. An error occurs while the management module is reading the firmwares VPD data of targeted type. An error occurs while the management module is reading the name of the targeted blade. An error occurs while the management module is reading the compact flash cards information. An error occurs while the management module is reading the firmware version of targeted cKVM. Definition No VPD is available for the targeted device. An error occurs while the management module is reading the blade H8 firmware VPD data of the targeted blade.
292
iocomp command errors

This topic lists errors for the iocomp command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 107. iocomp command errors Error message Error reading I/O Compatibility Detail for blade blade_number where blade_number identifies the blade server. Error reading I/O Compatibility Detail for switch bay_number where the bay_number identifies the I/O module. ERROR!!! IOM bay_number reports incorrect width! sw_width = sw_width where v the bay_number identifies the I/O module v sw_width identifies the invalid width I/O Compatibility Detail or blade blade_number: unknown where blade_number identifies the blade server. An error occurs while the management module is getting the width of the targeted blade. An error occurs while the management module is reading I/O compatibility for targeted I/O module. An error occurs while the management module is reading I/O compatibility for targeted I/O module. Definition An error occurs while the management module is reading I/O compatibility for targeted blade.
kvm command errors

This topic lists errors for the kvm command. There are no unique errors for the kvm command. See Common errors on page 269 for a list of error messages that apply to all commands.
ldapcfg command errors

This topic lists error messages for the ldapcfg command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 108. ldapcfg command errors Error message A Client DN password is configured, client DN must be configured too. AMM target name is limited to 63 characters. Argument of option -arguments must be enclosed in quotation marks. where arguments is the name of the improperly entered arguments Definition The user tries to issue a command to remove the client DN setting with the client DN password configured. A user tries to set an advanced management module target name that is longer than 63 characters. The user tries to issue a command with arguments for the options that are not enclosed in quotation marks.
293
Table 108. ldapcfg command errors (continued) Error message Arguments containing spaces must be enclosed in quotation marks. Both password and confirm password must be provided. Client DN password mismatch. Please reenter passwords. Client DN password mismatch. Please reenter passwords. If a Client DN password is configured, client DN must be configured too. Invalid option argument for -option:argument. format where: v option identifies the option v argument identifies the invalid argument v format identifies the format of argument You are configuring Client DN password, but no Client DN. Please configure a Client DN. You must configure a Search Domain given your selection of [sd/ltsd] for Domain Source. Definition The user tries to issue a command with arguments for options without ending double quotes. The user tries to issue a command without providing both the password and the confirm password. The user tries to issue a command with both -p and -cp options, but their arguments do not match. The user tries to issue a command with both -p and -cp options, but their arguments do not match. The user tries to issue a command to configure the client DN password while the client DN is not configured. The user tries to issue a command with invalid arguments for the options which do not conform to the format specified.
The user tries to issue a command to set Client DN password while the Client DN is not configured. The user tries to issue a command for -ds [sd/ltsd] settings without the Source Domain configured.
led command errors

This topic lists errors for the led command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 109. led command errors Error message -d can only be used with the -loc on. Delay value must be less than max. Error getting LED status. Error reading system LED state. Error setting system LED. Invalid option argument for -loc. Error setting -loc for blade[slot] -l can only be used by itself. Error turning off information LED Definition A user tries to issue a command to set the -d while the -loc setting is off. User input for the option -d exceeds the maximum. An error occurs while the management module is getting the system LED status. An error occurs while the management module is reading the system LED state. An error occurs while the management module is configuring the system LED. A user tries to enter an invalid argument for the option -loc. An internal error occurs while setting location LED for the targeted blade. User issues a command with l option inclusive of an argument or other options. An internal error occurs while the user is setting information LED to off.
294
list command errors

This topic lists error messages for the list command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 110. list command errors Error message The level must be non-zero. Definition The user tries to enter a level of depth for tree-structure display of 0.
modactlog command errors

This topic lists errors for the modactlog command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 111. modactlog command errors Error message Unable to read the Module Activity Log. Definition No module activity log is found in the database.
monalerts command errors

This topic lists errors for the monalerts command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 112. monalerts command errors Error message -[ca/wa/ia] must be used exclusive of its sub-options. Note: If -ec is disabled, monalertsleg should be used. Definition A user tries to issue a command with the -ca, -wa, or -ia option at the same time as its sub-options. A user tries to issue a monalerts command with the -ec disable setting.
monalertsleg command errors

This topic lists errors for the monalertsleg command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 113. monalertsleg command errors Error message Note: If -ec is enabled, monalerts should be used. Definition A user tries to issue a monalertsleg command with the -ec enable setting.
295
mt command errors
This topic lists errors for the mt command. There are no unique errors for the mt command. See Common errors on page 269 for a list of error messages that apply to all commands.
nat command errors

This topic lists error messages for the nat command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 114. nat command errors Error message Adding code authority failed. External port: Valid range is 1000 through 65534. I/O Module is in protected mode and cannot be restored to its default configuration. I/O Module is in Protected Mode and cannot change its NAT configuration. Internal port: Valid range is 1 through 65534. NAT configuration is not supported on this IO module. The first two rules protocol names cannot be changed. When creating a new rule, all fields must be specified. Definition A user tries to add code authority. The user tries to set the external port number to a value outside of its valid range. The user tries to restore the default configuration of an I/O module while it is in protected mode. The user tries to change the configuration of an I/O module while it is in protected mode. The user tries to set the internal port number to a value outside of its valid range. The user tries to direct a nat command to an I/O module that does not support the network address table. The user tries to change the protocol names for HTTP or Telnet. The user does not specify all the fields when attempting to make a new rule.
ntp command errors

This topic lists error messages for the ntp command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 115. ntp command errors Error message Invalid value passed to -en flag. Valid values are enable/disable Please set NTP server name or IP address before enabling NTP Please set NTP server name or IP address before synchronizing the clock Please set NTP update frequency before enabling NTP Please set NTP v3 authentication entry before enabling NTP authentication Definition The user input for the -en option is invalid. The user tries to enable NTP before setting the server name or IP address. The user tries to synchronize the clock before setting the NTP server name or IP address. The user tries to enable NTP before setting the update frequency. The user tries to enable NTP authentication before configuring the v3 authentication.
296
ping command errors

This topic lists errors for the ping command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 116. ping command errors Error message Error reading IP address of switch bay_number where the bay_number designates the I/O module. Definition An error occurs while the management module is getting the current IP address of the targeted switch.
pmpolicy command errors

This topic lists errors for the pmpolicy command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 117. pmpolicy command errors Error message Error getting number of domains. Getting current policy failed. Getting valid policies failed. Definition An internal error occurs while the advanced management module is getting the number of domains. An internal error occurs while the advanced management module is getting the current policy for a domain. An internal error occurs while the advanced management module is getting the valid policies for power management.
portcfg command errors

This topic lists errors for the portcfg command. There are no unique errors for the portcfg command. See Common errors on page 269 for a list of error messages that apply to all commands.
ports command errors

This topic lists error messages for the ports command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 118. ports command errors Error message A certificate must first be in place before SSL can be enabled. Use the web interface to generate one. Definition The user tries to enable SSL before setting up a valid SSL certificate and private encryption key.
An SSH server key must first be in place before SSH can The user tries to enable SSH before setting up a valid be enabled. Use the web interface to generate one. SSH server key. Duplicate port number entered. The user tries to enter a port number that is already in use.
297
Table 118. ports command errors (continued) Error message Invalid parameter. The timeout must be between 0 and 4294967295 seconds. Port number out of range. Reserved port number entered. Secure SMASH CLP cannot be enabled without a valid SSH server key in place. Definition The user tries to enter a timeout that is outside of the valid range. The user tries to enter a port number that is outside of the valid range. The user tries to enter a port number that has been reserved. The user tries to enable the secure SMASH CLP before setting up a valid SSH server key.
power command errors

This topic lists error messages for the power command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 119. power command errors Error message Invalid POST results. POST results could not be read. POST results not complete: hex_code where the hex_code value varies based on the problem that was encountered. Powering on/off blade failed. Powering on/off I/O Module failed. Powering on/off network clock failed. Powering on/off Telco Alarm Panel failed. Resetting blade failed. Shutting down OS and powering off blade failed. Definition The POST results are not valid. An error occurs during POST. The POST results are not available. See the documentation that comes with the device that failed to respond correctly to the power command for information about the hex_code value. An internal error occurs while powering the blade server on or off. An error occurs while the management module is powering the I/O module on or off. An error occurs while the management module is powering the network clock on or off. An error occurs while the management module is powering the Telco Alarm Panel on or off. An error occurs while the management module is resetting the blade server. An error occurs while the management module is shutting down the operating system and powering off the blade server.
298
read command errors

This topic lists error messages for the read command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 120. read command errors Error message Both the -i and -l options must be specified with the -config file. Definition The user does not specify both the -i and -l options when restoring configuration from a file.
Configuration restore from the chassis failed: i2c bus read An error occurs while the management module is error. restoring the management module configuration from the BladeCenter unit midplane due to an i2c read error. Configuration restore from the chassis failed: operation not supported. Configuration restore from the chassis failed: NVRAM compression error. An error occurs while the management module is restoring the management module configuration from the BladeCenter unit midplane due to a failed system check. An error occurs while the management module is restoring the management module configuration from the BladeCenter unit midplane due to an EEPROM compression error.
Configuration restore from the chassis failed: unsupported An error occurs while the management module is midplane data format. restoring the management module configuration from the BladeCenter unit midplane due to an unsupported EEPROM format. Could not retrieve encryption data from the configuration file successfully. Error writing autoread flag. Firmware update is in progress. Try again later. The user tries to enter a passphrase that does not match the one that was used to create the backup configuration file. An error occurs while the management module is writing autoread flag. The user tries to restore the management module configuration from the BladeCenter unit midplane while the management module firmware is updating. The user tries to enter a passphrase that does not match the one that was used to create the backup configuration file. An error occurs while the management module is allocating memory. The user tries to set the -auto option when restoring the configuration from a file. The user tries to issue a command to read configuration from a file without specifying both the -config option and config source. The user does not include a required -config option for the command.
Please make sure you enter the correct passphrase for this configuration file. Resource allocation failure! Memory allocation failed for configuration read. The -auto option can only be used with the -config chassis. The -config option and a config source is required.
The -config option is required.
The -i, -l, and -p options can only be used with the -config The user tries to specify a TFTP server and a file. configuration file when restoring the configuration from the BladeCenter unit midplane. The passphrase is greater than 1600 characters. The passphrase must be quote-delimited. The user tries to input a passphrase that exceeds the maximum length. The user tries to input a passphrase that is not quote-delimited.
299
Table 120. read command errors (continued) Error message There was a problem retrieving the file. Definition TFTP encounters an error when transferring the configuration file.
remotechassis command errors

This topic lists error messages for the remotechassis command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 121. remotechassis command errors Error message Clearing the internal discovered list of MMs failed. Discovery cannot be run until SLP has been enabled. Error running discovery. Getting last discovery time failed. Getting the first entry of the internal discovered list of MMs failed. Getting the internal discovered list of MMs failed. Unable to read SLP settings. Definition An error occurs while the management module is clearing the internal discovered list of management modules. The user tries to discover other BladeCenter units on the network when SLP is disabled. An error occurs while the management module is running discovery. An error occurs while the management module is reading last discovery time. An error occurs while the management module is reading the first entry of the internal discovered list of management modules. An error occurs while the management module is reading the internal discovered list of management modules. An error occurs while the management module is reading SLP settings.
reset command errors

This topic lists error messages for the reset command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 122. reset command errors Error message An error occurred while disabling failover. An error occurred while enabling failover. Firmware update is in progress. Try again later. Definition An error occurs while the management module is disabling failover. An error occurs while the management module is enabling failover. The user tries to reset the management module during a firmware update. The error message displays and the management module does not reset. An error occurs while the management module is rebooting the blade server. An error occurs while the management module is resetting and running diagnostics for the I/O module.
Rebooting blade failed. Resetting and running standard/extended/full diagnostics for I/O module failed.
300
Table 122. reset command errors (continued) Error message Resetting I/O module failed. There is no backup management module installed. Definition An error occurs while the management module is resetting the I/O module. A user tries to enable failover on a management-module reset and there is no standby management module.
sddump command errors

This topic lists errors for the sddump command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 123. sddump command errors Error message Error retrieving blade type. Initiate data collection type failed. The format of the received data is wrong. Definition The management module is unable read the blade server type. The management module is unable initiate data collection type of the p6 blade server. The management module receives wrongly formatted data.
security command errors

This topic lists errors for the security command. There are no unique errors for the security command. See Common errors on page 269 for a list of error messages that apply to all commands.
service command errors

This topic lists errors for the service command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 124. service command errors Error message Getting status of debug with USB key failed. Definition An error occurs while the management module is reading the status of debug with a USB key.
301
shutdown command errors

This topic lists errors for the shutdown command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 125. shutdown command errors Error message Invalid option. This command must have the -f option. Definition The user tries to issue a command without the -f option.
slp command errors

This topic lists errors for the slp command. There are no unique errors for the slp command. See Common errors on page 269 for a list of error messages that apply to all commands.
smtp command errors

This topic lists error messages for the smtp command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 126. smtp command errors Error message Getting SMTP server host name or IP address failed. Input length is greater than the maximum characters allowed. Invalid host name or ip address. Removing SMTP server name or IP address failed. Setting SMTP server name or IP address failed. SMTP server host name or IP address is not set. Definition An error occurs while the management module is reading the SMTP server host name or IP address. A user tries to enter too many characters in an input field. A user tries to set the SMTP host name or IP address to an invalid value. An error occurs while the management module is removing an SMTP server host name or IP address. An error occurs while the management module is setting an SMTP server host name or IP address. A user tries to view the SMTP host name or IP address when the values are not set.
302
snmp command errors

This topic lists error messages for the snmp command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 127. snmp command errors Error message Arguments containing spaces must be enclosed in quotation marks At least one configured community is required to enable SNMP. Definition A user tries to enter a string containing spaces that has an opening quotation mark without a closing quotation mark. A user tries to enable SNMP without configuring at least one community name.
Config failed. IP address of 0.0.0.0 is allowed only for the A user tries to set an IP address of 0.0.0.0 for something first host name in the first community. other than the first host name of the first community. Config failed. IP address of 0.0.0.0 is allowed only when the first community is configured as Get access type. Config failed. You defined a community without an IP address or host name. Config failed. You defined a duplicate community name. Enabling/Disabling snmp interface failed. Enabling/Disabling snmp traps failed. Enabling/Disabling SNMPv3 Agent failed. Input length is greater than the maximum characters allowed. Invalid community name. Invalid host name or ip address. Setting access type of type for SNMPv3 failed where type is the type of SNMPv3 access desired. Setting location/contact of the SNMP agent failed. An error occurs while the management module is setting the location or contact of the SNMP agent. A user tries to set an IP address of 0.0.0.0 for the first host name of the first community when the first community is not configured with the Get access type. A user tries to define a community without specifying an IP address or host name. A user tries to define a two communities with the same name. An error occurs while the management module is enabling or disabling an snmp interface. An error occurs while the management module is enablingor disabling the snmp traps. An error occurs while the management module is enabling or disabling the SNMPv3 Agent. A user tries to enter too many characters in an input field. A user tries to set a community name to an invalid value. A user tries to set the SNMP host name or IP address to an invalid value. An error occurs while the management module is setting access type for an SNMPv3.
303
sol command errors

This topic lists error messages for the sol command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 128. sol command errors Error message An error occurred while disabling SOL globally. An error occurred while disabling SOL on that blade. An error occurred while enabling SOL globally. An error occurred while enabling SOL on that blade. An error occurred while reading the global SOL status. An error occurred while reading the SOL accumulate timeout. An error occurred while reading the SOL retry count. An error occurred while reading the SOL retry interval. An error occurred while reading the SOL send threshold. An error occurred while reading the SOL session status on that blade. An error occurred while reading the SOL VLAN ID. An error occurred while setting the SOL accumulate timeout. An error occurred while setting the SOL blade reset sequence. An error occurred while setting the SOL escape sequence. An error occurred while setting the SOL retry count. An error occurred while setting the SOL retry interval. An error occurred while setting the SOL send threshold. An error occurred while setting the SOL vlan id. Checking if this blade supports SOL failed. Invalid arg for -status. Must be on or off. Definition An error occurs while the management module is disabling SOL globally. An error occurs while the management module is disabling SOL on a blade server. An error occurs while the management module is enabling SOL globally. An error occurs while the management module is enabling SOL on a blade server. An error occurs while the management module is reading the global SOL status. An error occurs while the management module is reading the SOL accumulate timeout. An error occurs while the management module is reading the SOL retry count. An error occurs while the management module is reading the SOL retry interval. An error occurs while the management module is reading the SOL send threshold. An error occurs while the management module is reading the SOL session status on a blade server. An error occurs while the management module is reading the SOL VLAN ID. An error occurs while the management module is setting the SOL accumulate timeout. An error occurs while the management module is processing the command. An error occurs while the management module is processing the command. An error occurs while the management module is setting the SOL retry count. An error occurs while the management module is setting the SOL retry interval. An error occurs while the management module is setting the SOL send threshold. An error occurs while the management module is processing the command. An error occurs while the management module is checking if the selected blade supports SOL. A user tries to enter an invalid argument for the -status command option.
304
Table 128. sol command errors (continued) Error message Invalid arg for -status. Must be enabled or off. Invalid parameter. The accumulate timeout must be between 1 and 251 inclusive. Invalid parameter. The retry count must be between 0 and 7, inclusive. Definition A user tries to enter an invalid argument for the -status command option. A user tries to enter an accumulate timeout that is outside of the valid range. A user tries to enter a retry count that is outside of the valid range.
Invalid parameter. The send threshold must be between 1 A user tries to enter a send threshold that is outside of and 251 inclusive. the valid range. Invalid parameter. The vlan id must be between 1 and 4095 inclusive. Retry interval range is too large. Setting to 2550. A user tries to enter a VLAN ID that is out of range. A user tries to enter a retry interval that is greater than 2550 ms. If the user tries to enter a retry interval greater than 2550 ms, the retry interval will be set to 2550 ms. An error occurs while the management module is setting the retry interval to 2550. A user tries to issue the SOL command to a blade server that does not support SOL.
Setting retry interval to 2500 failed. This blade does not support SOL.
sshcfg command errors

This topic lists errors for the sshcfg command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 129. sshcfg command errors Error message Getting CLI SSH port failed. Getting DSA host key failed. Getting host key size failed. Getting installed key status failed. Getting number of SSH public keys installed failed. Getting SMASH SSH port failed. When displaying host keys, -hk must be used by itself. Definition An error occurs while the management module is reading the CLI SSH port. An error occurs while the management module is reading the DSA host key. An error occurs while the management module is reading the host key size. An error occurs while the management module is reading the installed key status. An error occurs while the management module is reading the number of SSH public keys installed. An error occurs while the management module is reading the SMASH SSH port. The user tries to issue a command to display the host keys with option -hk.
305
sslcfg command errors

This topic lists errors for the sslcfg command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 130. sslcfg command errors Error message -dnld must be used with the -cert/-csr (server, client) as well as -i and optionally -l -i must be provided to download a trusted certificate. -upld must be used with the -cert (server, client) as well as -i and -l Cannot open file: filename where filename is the name of the file that was entered for opening. Cert generation for server/client failed where server/client specifies whether the certificate was being generated for a server or client. CLI map failed error = error where error specifies error. Converting DER back to X509 format failed. CSR generation for server/client failed where server/client specifies whether the certificate signing request was being generated for a server or client. 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 Error: unknown application Exporting Cert/CSR failed where Cert/CSR specifies whether the user tried to export a certificate or certificate signing request. Getting filename from tfpt server argument failed where: v filename identifies the name of the requested file v argument identifies the IP address of the tftp server Getting certificate status of standby AMM failed. An error occurs while the management module is reading the certificate status of the standby advanced management module. An error occurs while the management module is getting a file from the tftp server. An error occurs while the management module is converting DER back to X509 format. An error occurs while the management module is generating a certificate signing request for a server or client. An error occurs while the management module is mapping the file to memory. An error occurs while the management module is generating a certificate for the server or client. Definition A user tries to issue a download certificate or certificate signing request command without the -cert or -csr, and -i options. A user tries to issue a downloading trusted certificate command without the -i option. A user tries to issue an import certificate command without the -cert, -l and -i options. An error occurs while the management module is trying to open a file.
An error occurs while the management module is downloading a certificate or certificate signing request to the tftp server for the SSL server or client.
An error occurs because an unknown certificate type is referred to. An error occurs while the management module is exporting a certificate or certificate signing request.
306
Table 130. sslcfg command errors (continued) Error message Getting failover mode failed. Getting SSL Server/Client Certificate/CSR status failed. Definition An error occurs while the management module is reading the failover mode. An error occurs while the management module is reading the SSL server or client certificate or certificate signing request status. An error occurs while the management module is importing a certificate.
Importing certFileName is failed where certFileName is the name of the certificate that was being imported. Input length is greater than the maximum characters allowed. Invalid IP arg for -option: argument. Each byte has to be in the range (0-255) where: v option identifies the command option v argument identifies the invalid IP address argument Invalid IP arg for -option: argument. Enter 4 bytes separated by 3 dots where: v option identifies the command option v argument identifies the invalid IP address argument Invalid IP arg for -option: argument. Too few bytes where: v option identifies the command option v argument identifies the invalid IP address argument Invalid IP arg for -option: argument. Too many bytes where: v option identifies the command option v argument identifies the invalid IP address argument Invalid option for Cert generation: -cpwd Invalid option for Cert generation: -un IPs Swaps is not configured.
A user tries to issue a command with an invalid argument for the option. The length of the input is greater than maximum. A user tries to issue a command with an invalid argument for the IP Address option. One or more parts is not in the range of 0-255.
A user tries to issue a command with an invalid argument for the IP Address option. Invalid arguments could be too long, too short, or not numeric in all parts.
A user tries to issue a command with an invalid argument for the IP Address option, an argument which has fewer than four parts.
A user tries to issue a command with an invalid argument for the IP Address option, an argument which has more than four parts.
A user tries to issue a command with an invalid option -cpwd for certification generation. A user tries to issue a command with an invalid option -un for certification generation. A user tries to issue a command for the SSL configuration against the Standby Server target without the IPs Swaps configured. A user tries to issue a command for the SSL configuration without entering all the required options. A user tries to issue a command to download a nonexistent certificate or certificate signing request.
Missing required options. No Cert/CSR available. where Cert/CSR specifies whether the user specified a certificate or certificate signing request. No tc[1/2/3] available. where [1/2/3] is the number of the selected trusted certificate.
A user tries to issue a command to remove or download a nonexistent trusted certificate.
307
Table 130. sslcfg command errors (continued) Error message No valid client certificate is in place. Type sslcfg -h for syntax help of the SSLclient Certificate generation command. No valid server certificate is in place. Type sslcfg -h for syntax help of the SSL server Certificate generation command. No valid trusted certificate is in place. Type sslcfg -h for syntax help of the SSL trusted Certificate importing command. Putting filename to tfpt server ip_address failed. where: v filename identifies the command option v ip_address identifies the IP address of the tftp server Writing X509 format certificate to file failed. An error occurs while the management module is writing the X509 format certificate to File. Definition A user tries to issue a command to enable the SSL client without a valid client certificate in place. A user tries to issue a command to enable the SSL server without a valid server certificate in place. A user tries to issue a command to enable the SSL client without a valid trusted certificate in place. An error occurs while the management module is putting a file to the tftp server.
syslog command errors

This topic lists errors for the syslog command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 131. syslog command errors Error message Input length is greater than the maximum characters allowed. Invalid host name or ip address. Port number out of range. Definition A user tries to enter too many characters for an input field. A user tries to enter an invalid hostname or ip address. A user tries to enter an invalid port number.
tcpcmdmode command errors

This topic lists error messages for the tcpcmdmode command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 132. tcpcmdmode command errors Error message Error changing TCP command mode connection. Error disabling tcpcmdmode. Error enabling TCP command mode. Error enabling/disabling Secure TCP command mode. Definition An error occurs while the management module is changing the TCP command mode Connection. An error occurs while the management module is disabling the TCP command mode. An error occurs while the management module is enabling the TCP command mode. An error occurs while the management module is enabling or disabling the Secure TCP command mode.
308
Table 132. tcpcmdmode command errors (continued) Error message Invalid parameter. Input must be numeric. Definition A user tries to enter a parameter value for the -t (timeout) command option containing non-numeric characters. For example, tcpcmdmode -t 200m. A user tries to enter a parameter value for the -t (timeout) command option that is outside of the valid range. The user input for the -status option exceeds the maximum.
Invalid parameter. The timeout must be between 0 and 4294967295 seconds. Maximum connections can not exceed max. where max is the number of permitted connections.
telnetcfg command errors

This topic lists error messages for the telnetcfg command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 133. telnetcfg command errors Error message Invalid parameter. Input must be numeric. Definition A user tries to enter a Telnet timeout value containing non-numeric characters. For example, telnetcfg -t 200w. The user tries to enter a timeout value greater than 4294967295 seconds. A user tries to enter a Telnet timeout value that is out of range.
Invalid parameter. The telnet timeout range must be less than 4294967295. Invalid parameter. The timeout must be between 0 and 4294967295 seconds.
temps command errors

This topic lists errors for the temps command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 134. temps command errors Error message Blade blade_number: Too many SDRs found. where blade_number identifies the blade server. Getting power state of blade blade_number failed. where blade_number identifies the blade server. An error occurs while the management module is reading the power state of the specified blade server. Definition A database error occurs when too many SDRs are found.
309
thres command errors

This topic lists errors for the thres command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 135. threshold command errors Error message A duplicate option is found in the requested command. Invalid threshold value. Unable to query the threshold request. Unable to set the requested threshold. Definition The user tries to enter a duplicate argument. The user tries to enter an invalid threshold value. An error occurs during the query threshold request. An error occurs during the set threshold request.
trespass command errors

This topic lists error messages for the trespass command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 136. trespass command errors Error message twe must be enabled to modify the trespassing warning. The trespassing warning must be quote-delimited. The trespassing warning is greater than 1600 characters. Definition The user tries to issue a command to modify the trespassing warning without the -twe enabled setting. The user tries to enter a trespassing warning that is not enclosed in double-quotation marks. The user tries to enter a trespassing warning that is longer than 1600 characters.
uicfg command errors

The following table lists error messages for the uicfg command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 137. uicfg command errors Error message Reading telnet/ssh/snmpv1/snmpv3 status failed. Warning: Communication with IBM Director has been disabled. Definition An error occurs while the management module is reading the telnet, ssh, snmpv1, or snmpv3 status. A user has disabled the TCP command mode.
310
update command errors

This topic lists error messages for the update command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 138. update command errors Error message Flash operation failed. Flash operation failed status percentage where the percentage value varies based on when the problem was encountered. Flash operation not in process or status unavailable. Flash operation timed out percentage. where the percentage value varies based on when the problem was encountered. Flash preparation - error sending packet file filename. where the filename value varies based on the file being updated. Flash preparation error. Packet percent complete percentage. Flash percent complete percentage. where the percentage value varies based on when the problem was encountered. Flash preparation error. Timeout on packet preparation operation percentage. where the percentage value varies based on when the problem was encountered. Flashing not supported on this target. A user attempts to run the update command on a module that does not support flash firmware updates. An error occurs during the flash firmware update. An error occurs during the flash firmware update. An error occurs during the flash firmware update. An error occurs during the flash firmware update. An error occurs during the flash firmware update. Definition An error occurs during the flash firmware update. An error occurs during the flash firmware update.
Getting data encryption setting failed. If data encryption is An error occurs while the management module is reading enabled and you are updating the firmware to a level the data encryption setting. which does not support data encryption, you will lose all your configuration settings as a result. Getting name of mm bay_number failed. where the bay_number identifies the management module specified. An error occurs while the management module is reading the name of the management module in designated bay.
311
Table 138. update command errors (continued) Error message Invalid option. Definition An invalid command option is entered. For the update command, invalid command option errors include: v the -i (IP address) command option does not have an IP address parameter v the -i (IP address) command option specifies an invalid IP address v attempting to enter the -i (IP address) command option without the -n (filename) command option v the -n (filename) command option does not have a file name parameter v attempting to enter the -n (filename) command option without the -i (IP address) command option v 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 option with the -a command option The user tries to execute a command without specifying a command option. The command is targeted to a management module bay where no management module is installed.
Invalid syntax. Management Module bay_number is not installed. where the bay_number identifies the management module specified. TFTP Error error_code. where the error_code value varies based on the problem that was encountered. TFTP Error. Access violation. TFTP Error. Connection failure. TFTP Error. Disk full or allocation exceeded. TFTP Error. File already exists. TFTP Error. File error. TFTP Error. File not found. TFTP Error. Illegal option negotiation. TFTP Error. Illegal TFTP operation. TFTP Error. Unable to allocate memory. TFTP Error. Unknown transfer ID. TFTP Error. Unknown user.
An error occurs for the TFTP connection.
An error occurs for the TFTP connection. An error occurs for the TFTP connection. An error occurs for the TFTP connection. An error occurs for the TFTP connection. An error occurs for the TFTP connection. An error occurs for the TFTP connection. An error occurs for the TFTP connection. An error occurs for the TFTP connection. An error occurs for the TFTP connection. An error occurs for the TFTP connection. An error occurs for the TFTP connection.
Unable to read blade server VPD bay bay_number name. The command specifies an empty server blade bay or an error occurs when reading the VPD. where the bay_number and name values vary based on the problem that was encountered. Unable to read I/O Module VPD bay bay_number name. where the bay_number and name values vary based on the problem that was encountered. Unable to read MM VPD bay bay_number name. where the bay_number and name values vary based on the problem that was encountered. The command specifies an empty management module bay or an error occurs when reading the VPD. The command specifies an empty I/O module bay or an error occurs when reading the VPD.
312
Table 138. update command errors (continued) Error message Unable to read VPD for Blade blade_number name. where the blade_number and name values vary based on the problem that was encountered. Unknown device type. Update error. Invalid destination. Update Failed, there was a problem retrieving the file. The command is targeted to an unknown device type. A user tries to issue a command to a target that is not valid. The management module was unable to complete the update because it was unable to retrieve the file from the TFTP server. Definition An error occurs while the management module is reading the VPD of the targeted blade.
uplink command errors

This topic lists error messages for the uplink command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 139. uplink command errors Error message -ip must be a valid IP address before enabling -el Getting status of failver on Lose/Logical of Physical Link failed. Invalid uplink delay value. 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 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. Definition The user tries to issue a command to enable the -el without a valid -ip setting. An error occurs while the management module is reading status of failver on Lose/Logical of Physical Link. A user tries to enter a delay value that is less than 1 or greater than 255. For example, uplink -del 0. The user input for an option is out of the range.
users command errors

This topic lists error messages for the users command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 140. users command errors Error message -af contains invalid characters. Only alphanumeric, comma, asterisk, question mark, hyphen, period, and exclamation point characters are valid. -af must start with from=. -cm is greater than 255 characters. Definition The user input for the -af option is invalid.
The user input for the -af option is invalid. The user input for the -cm option exceeds the maximum.
313
Table 140. users command errors (continued) Error message -cm must be quote-delimited. An entry cannot be modified and deleted in the same command. Arguments containing spaces must be enclosed in quotation marks. Checking if passwords are required failed. Deleting user failed. Error: the RBS permissions capability is not enabled. Definition The user input for the -cm option is not quote-delimited. A user tries to simultaneously modify and delete a user in the same command. A user tries to enter a context name containing spaces that does not have opening and closing quotation marks. An error occurs while the management module is checking if passwords are required. An error occurs while the management module is deleting an user. The user tries to run use the -a rbs: command option on management-module firmware that does not support this option. An error occurs while the management module is converting permissions data to the role-based security (RBS) format. An error occurs while the management module is creating a user.
Error converting RBS permissions.
Error creating user.
Error creating user: The authentication protocol cannot be The user tries to issue a command to create a user with none because the security settings require passwords. no authentication protocol when the security settings require passwords. Error reading certificate details. Error reading key. Error setting the access type. Error setting the authentication protocol. Error setting the authority level. Error setting the context name. Error setting the hostname/IP address. Error setting the password. Error setting the password. The new password is not compliant. Error setting the privacy password. Error setting the privacy protocol. Error setting the username. Error transferring file. An error occurs while the management module is reading certificate details. An error occurs while the management module is reading the key. An error occurs while the management module is setting the access type. An error occurs while the management module is setting the authentication protocol. An error occurs while the management module is setting the authority level. An error occurs while the management module is setting the context name. An error occurs while the management module is setting the hostname or IP address. An error occurs while the management module is setting the password. The user tries to issue a command to set the new password which is not compliant. An error occurs while the management module is setting the privacy password. An error occurs while the management module is setting the privacy protocol. An error occurs while the management module is setting the username. An error occurs while the management module is transferring file.
314
Table 140. users command errors (continued) Error message Getting a summary of all keys of user index failed. where the index value varies based on the problem that was encountered. Getting authority level of user index failed. where the index value varies based on the problem that was encountered. Getting role-based security level of user index failed. where the index value varies based on the problem that was encountered. Incorrect login permission option: permission where the permission value varies based on the problem that was encountered. Invalid argument. Valid arguments for -at are read, write, and traps. Invalid argument. Valid choices are des or <none>. Invalid argument. Valid choices are md5, sha, or <none>. Invalid authority level. A user tries to set an invalid argument for the -at command option. A user tries to set an invalid argument for the -pp command option. A user tries to set an invalid argument for the -ap command option. 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. A user specifies an invalid device range while trying to create or modify a user. A user tries to specify an invalid login permission for the -a command option. An error occurs while the management module is reading role-based security level of the targeted user. An error occurs while the management module is reading authority level of the targeted user. Definition An error occurs while the management module is reading a summary of all keys of the targeted user.
Invalid device number (first number must be smaller): device_A-device_B. where device_A and device_B identify the ends of the invalid device range being specified. Invalid device number: device_number. where device_number identifies the device number that is invalid. Invalid hostname or ip address. Invalid key index for this command. Invalid rbs device: device. where device identifies the device that is invalid. Invalid rbs device: Must specify device number Invalid rbs device list. Invalid rbs device (must be same device): device. where device identifies the device that is invalid. Invalid rbs role: role. where role identifies the role that is invalid.
A user provides a device number that is out of range while trying to create or modify a user.
A user tries to set an invalid host name or IP address for the -i command option. The user input for index is invalid. A user specifies an invalid device while trying to create or modify a user. A user specifies an invalid device number while trying to create or modify a user. A user does not specify a device list while trying to create or modify a user. A user specifies an invalid device while trying to create or modify a user. A user specifies an invalid role while trying to create or modify a user.
315
Table 140. users command errors (continued) Error message Invalid rbs role list. Invalid username. The username can only contain numbers, letters, dots, and underscores. Definition A user fails to specify a role list while trying to modify or create a user. The user tries to enter The username that contains invalid characters. Valid characters that can be used in a username are letters, numbers, periods (. ), and underscores ( _ ). The user tries to issue a command to change a password after the max retries of changing password limit is reached. The user tries to issue a command to create a user without the rbs role settings. The user tries to issue a command to change a password with an incorrect old password. The user tries to issue a command to change a password without the -op option. The user tries to issue a command to change a password without the -p option. A user tries to attempt to enter the command with an -a command option that has no argument. A user tries to attempt to enter the command with an -at command option that has no argument. A user tries to attempt to enter the command with a -cn command option that has no argument. A user tries to attempt to enter the command with an -i command option that has no argument. A user tries to attempt to enter the command with an -n command option that has no argument. A user tries to attempt to enter the command with a -ppw command option that has no argument. A user tries to enter the -a command option in a single command multiple times. A user tries to enter the -ap option flag in a single command multiple times. A user tries to enter the -at option flag in a single command multiple times. A user tries to enter the -cn option flag in a single command multiple times. A user tries to enter the -i option flag in a single command multiple times. A user tries to enter the -n option flag in a single command multiple times. A user tries to enter the -p option flag in a single command multiple times. A user tries to enter the -pp option flag in a single command multiple times. A user tries to enter the -ppw option flag in a single command multiple times. A user tries to set an invalid value for a command option.
Max retries changing password reached.
Must be set at least one rbs role for this user. Old password is incorrect. Old password must be specified by long option op. Specify your new password with -p option. Syntax error. -a option must have an argument. Syntax error. -at option must have an argument. Syntax error. -cn option must have an argument. Syntax error. -i option must have an argument. Syntax error. -n option must have an argument. Syntax error. -ppw option must have an argument. Syntax error. Multiple -a options found. Syntax error. Multiple -ap options found. Syntax error. Multiple -at options found. Syntax error. Multiple -cn options found. Syntax error. Multiple -i options found. Syntax error. Multiple -n options found. Syntax error. Multiple -p options found. Syntax error. Multiple -pp options found. Syntax error. Multiple -ppw options found. Syntax error. Type users -h for help.
316
Table 140. users command errors (continued) Error message The context name must be less than 32 characters long. The -i and -l options must both be specified when using -upld. The accept_from_string must be quote-delimited. The key is greater than 6000 bytes. The password must be at least 5 characters long, but no more than 15 characters long. The password must contain at least one alphabetic and one non-alphabetic character. The privacy password must also be set when setting the privacy protocol. The privacy password must be less than 32 characters long. The user index must be different than that of the current user. The username cannot be longer than 15 characters. There was a problem retrieving the file. Unable to change password. The minimum password change interval has not expired. Please try again later. Unable to read the complex password requirement. Unable to read the password required setting. Unexpected error: Unable to change password. When creating a new user, a username and authority level must be specified. When creating a new user, all options are required. Definition A user tries to set a context name that is longer than 31 characters. The user tries to issue a -upld command without -i and -l. The user input for the -af option is not quote-delimited. The user input for the key exceeds the maximum. The user tries to enter a password that is too short or too long. The user tries to enter a password that does not have at least one alphabetic and one non-alphabetic character. Displays if the user tries to set the privacy protocol to des without a specifying a privacy password (-ppw command option). A user tries to set a privacy password that is longer than 31 characters. The user tries to issue a command to delete the account of current user. A user tries to set a user name that is longer than 15 characters. An error occurs while the management module is retrieving the file. The user tries to issue a command to change a password while the minimum password change interval has not expired. An error occurs while the management module is reading the complex password requirement. An error occurs while the management module is reading the password required setting. An error occurs while the management module is changing the password. The user tries to issue a command to create a user without the -n and -a options. A user tries to create a new user without defining all of the command options and arguments.
317
volts command errors

This topic lists errors for the volts command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 141. volts command errors Error message Getting power state of blade blade_number failed. where blade_number identifies the blade server. Definition An error occurs while the management module is reading the power state of the targeted blade server.
write command errors

This topic lists error messages for the write command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 142. write command errors Error message Failed to save configuration settings to the chassis. Definition An error occurs while the management module is saving the management module configuration to the BladeCenter unit midplane. A user tries to save the management module configuration to the BladeCenter unit midplane while the management module firmware is updating. An error occurs while the management module is reading the security status. The user does not include a required -config option for the command.
Firmware update is in progress. Try again later.
Getting security status failed. The -config option is required.
The -i, -l, and -p options can only be used with the -config The user tries to specify a TFTP server and a file. configuration file when saving the configuration to the BladeCenter unit midplane. The -i option is required with the -config file. The -p option is required when encryption is enabled. Error creating file in memory. Error locking file. Error opening file. Error transferring file. Error generating file. Error allocating memory for file. A user tries to use the -i option with the -config chassis option. The user tries to issue a command without the -p option while encryption is enabled. The management module is unable to create the configuration file. The management module is unable to lock the configuration file. The management module is unable to open the configuration file. The management module is unable to transfer the configuration file. The management module is unable to generate the configuration file. The management module is unable to allocate memory for the configuration file.
318
Table 142. write command errors (continued) Error message The passphrase is greater than 1600 characters. The passphrase must be quote-delimited. Definition The user input for the passphrase exceeds the maximum permitted length. The user input for the passphrase is not quote-delimited.
zonecfg command errors

This topic lists errors for the zonecfg command. See Common errors on page 269 for a list of error messages that apply to all commands.
Table 143. zonecfg command errors Error message Activating zone configuration xxx on I/O module yyy failed. Getting current active zone number failed. Getting specified configuration of switchsslot failed. where slot identifies the targeted I/O module. Getting zone configuration failed. Invalid slot number for this command. The index must be 32 or less. Zone configuration not supported on this switch type. An error occurs while the management module is reading the zone configuration. The I/O module is not in slot 3 or 4. The configuration index is bigger than 32. The user tries to use this command on a non-SAS switch module. Definition The management module is unable activate the specified zone configuration on the specified I/O module. An error occurs while the management module is reading the current active zone number. An error occurs while the management module is reading the specified configuration of the targeted I/O module.
319
320
Appendix A. Getting help and technical assistance

If you need help, service, or technical assistance or just want more information about IBM products, you will find a wide variety of sources available from IBM to assist you. This section contains information about where to go for additional information about IBM and IBM products, what to do if you experience a problem with your system, and whom to call for service, if it is necessary.
Before you call

Before you call, make sure that you have taken these steps to try to solve the problem yourself: v Check all cables to make sure that they are connected. v Check the power switches to make sure that the system and any optional devices are turned on. v Use the troubleshooting information in your system documentation, and use the diagnostic tools that come with your system. Information about diagnostic tools is in the Problem Determination and Service Guide on the IBM Documentation CD that comes with your system. v Go to the IBM support Web site at http://www.ibm.com/systems/support/ to check for technical information, hints, tips, and new device drivers or to submit a request for information. You can solve many problems without outside assistance by following the troubleshooting procedures that IBM provides in the online help or in the documentation that is provided with your IBM product. The documentation that comes with IBM systems also describes the diagnostic tests that you can perform. Most systems, operating systems, and programs come with documentation that contains troubleshooting procedures and explanations of error messages and error codes. If you suspect a software problem, see the documentation for the operating system or program.
Using the documentation

Information about your IBM system and preinstalled software, if any, or optional device is available in the documentation that comes with the product. That documentation can include printed documents, online documents, readme files, and help files. See the troubleshooting information in your system documentation for instructions for using the diagnostic programs. The troubleshooting information or the diagnostic programs might tell you that you need additional or updated device drivers or other software. IBM maintains pages on the World Wide Web where you can get the latest technical information and download device drivers and updates. To access these pages, go to http://www.ibm.com/systems/support/ and follow the instructions. Also, some documents are available through the IBM Publications Center at http://www.ibm.com/shop/publications/order/.
Getting help and information from the World Wide Web

On the World Wide Web, the IBM Web site has up-to-date information about IBM systems, optional devices, services, and support. The address for IBM System x and xSeries information is http://www.ibm.com/systems/x/. The address for IBM BladeCenter information is http://www.ibm.com/systems/bladecenter/. The address for IBM IntelliStation information is http://www.ibm.com/intellistation/.
321
You can find service information for IBM systems and optional devices at http://www.ibm.com/systems/support/.
Software service and support

Through IBM Support Line, you can get telephone assistance, for a fee, with usage, configuration, and software problems with System x and xSeries servers, BladeCenter products, IntelliStation workstations, and appliances. For information about which products are supported by Support Line in your country or region, see http://www.ibm.com/services/sl/products/. For more information about Support Line and other IBM services, see http://www.ibm.com/services/, or see http://www.ibm.com/planetwide/ for support telephone numbers. In the U.S. and Canada, call 1-800-IBM-SERV (1-800-426-7378).
Hardware service and support

You can receive hardware service through IBM Services or through your IBM reseller, if your reseller is authorized by IBM to provide warranty service. See http://www.ibm.com/planetwide/ for support telephone numbers, or in the U.S. and Canada, call 1-800-IBM-SERV (1-800-426-7378). 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 service
IBM Taiwan product service contact information: IBM Taiwan Corporation 3F, No 7, Song Ren Rd. Taipei, Taiwan Telephone: 0800-016-888
322
Appendix B. 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 in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the users responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product, and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
Trademarks
The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both:
Active Memory Active PCI Active PCI-X AIX Alert on LAN IBM IBM (logo) IntelliStation NetBAY Netfinity TechConnect Tivoli Tivoli Enterprise Update Connector Wake on LAN
323
BladeCenter Chipkill e-business logo eServer FlashCopy i5/OS
PowerExecutive Predictive Failure Analysis ServeRAID ServerGuide ServerProven System x
XA-32 XA-64 X-Architecture XpandOnDemand xSeries
Intel, Intel Xeon, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Adaptec and HostRAID are trademarks of Adaptec, Inc., in the United States, other countries, or both. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. Red Hat, the Red Hat Shadow Man logo, and all Red Hat-based trademarks and logos are trademarks or registered trademarks of Red Hat, Inc., in the United States and other countries. Other company, product, or service names may be trademarks or service marks of others.
Important notes
Processor speeds indicate the internal clock speed of the microprocessor; other factors also affect application performance. CD or DVD drive speed is the variable read rate. Actual speeds vary and are often less 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 for 1 073 741 824 bytes. When referring to hard disk drive capacity or communications volume, MB stands for 1 000 000 bytes, and GB stands for 1 000 000 000 bytes. Total user-accessible capacity may vary depending on operating environments. Maximum internal hard disk drive capacities assume the replacement of any standard hard disk drives and population of all hard disk drive bays with the largest currently supported drives available from IBM. Maximum memory might require replacement of the standard memory with an optional memory module.
324
IBM makes no representation or warranties regarding non-IBM products and services that are ServerProven, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. These products are offered and 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 may differ from its retail version (if available), and may not include user manuals or all program functionality.
Appendix B. Notices
325
326
Index Special characters

! 111 ? 109 accseccfg (continued) options alt 31 am 31 cp, off 32 cp, on 32 ct 32 dc 32 de, off 32 de, on 32 high 31 ia 32 ici 32 id 33 legacy 30 lf 33 lp 33 mls 33 pc, off 33 pc, on 33 pe 33 pi 34 pr, off 34 pr, on 34 rc 34 wt 34 accseccfg command errors 271 accseccfg commands 29 example 35 accumulate timeout set for SOL 206 acknowledge alarms alarm ID 40 complete alarm key 40 generator ID 40 generator information 40 acoustic mode, disable 102 acoustic mode, enable 102 activate I/O module SAS zone 265 activate network protocol settings I/O module 161 activate SAS zone I/O module 265 add SSH public key 256 add SSH public key (specific) 257 additional SSL certificate disable for standby management module 212 enable for standby management module 212 advanced failover settings disable network interface for redundant management module 36 display for management module 36 enable network interface for redundant management module and allow IP swap during failover 36 enable network interface for redundant management module and prevent IP swap during failover 36 advanced management module disable logical uplink failover 236
A
account inactivity alert time set for management module 32 account inactivity disable time set for management module 33 account lockout period set for management module 33 account security commands 29 account security settings disable complex password for management module user authentication 32 disable default administration password expiration for management module 32 disable password change at first login to management module 33 disable password required for management module 34 display for management module 29 enable complex password for management module user authentication 32 enable default administration password expiration for management module 32 enable password change at first login to management module 33 enable password required for management module 34 set management module account inactivity alert time 32 set management module account inactivity disable time 33 set management module account lockout period 33 set management module authentication logging timeout 31 set management module CLI inactivity timeout 32 set management module default to high 31 set management module default to legacy 30 set management module maximum LDAP sessions for user 33 set management module maximum number of login failures 33 set management module minimum number of different characters for password 32 set management module password expiration time 33 set management module password minimum change interval 34 set management module password reuse cycle 34 set management module user authentication method 31 set management module Web interface inactivity timeout 34 accseccfg 29
327
advanced management module (continued) disable physical uplink failover 235 enable logical uplink failover 236 enable physical uplink failover 235 logical uplink failover delay 236 logical uplink failover IP address 236 network interface management commands physical uplink failover delay 235 advanced management module commands accseccfg 29 advfailover 36 alertcfg 44 baydata 52 bofm 54 bootmode 59 bootseq 60 clear 71 clock 73 config 77 displaysd 85 files 95 fuelg 99 ifconfig 118 iocomp 132 kvm 134 ldapcfg 136 led 142 modactlog 148 monalerts 149 monalertsleg 154 mt 159 nat 161 ntp 164 ping 166 portcfg 170 ports 172 read 185 remotechassis 187 sddump 194 security 195 service 196 shutdown 197 slp 198 sshcfg 210 sslcfg 212 syslog 218 tcpcmdmode 222 temps 225 trespass 226 uicfg 228 uplink 235 users 247 volts 262 write 263 zonecfg 265 advfailover 36 options ip. noswap 36 ip. off 36 ip. swap 36 advfailover command 36
54
advfailover command (continued) example 37 advfailover command errors 272 alarm 38 acknowledge (alarm ID) 40 acknowledge (complete alarm key) 40 acknowledge (generator ID) 40 acknowledge (generator information) 40 clear (alarm ID) 41 clear (complete alarm key) 41 clear (generator ID) 41 clear (generator information) 41 display (alarm ID) 39 display (all) 38 display (complete alarm key) 39 display (generator ID) 39 display (generator information) 39 display (power) 38 options c, a 41 c, g 41 c, k 41 c, o 41 p 38 q 38 q, a 39 q, g 39 q, k 39 q, o 39 r, a 40 r, g 40 r, k 40 r, o 40 s, l 42 set 42 alarm command 38 alarm command errors 273 alarm commands example 42 alarm panel command target 92 alarm panel module power off 181 power on 181 turn off 181 turn on 181 alert test 50 alert categories (enhanced legacy) disable 149, 154 enable 149, 154 alert notification method, set 49 alert recipient, create 47, 48 alert recipient, delete 46 alert recipient, set email address 49 alert recipient, set hostname for alerts 50 alert recipient, set IP address for alerts 50 alert recipient, set name 48 alert recipient, set status 48 alert recipients, manage 46
328
alert state display all 149 alert state (legacy) display all 154 alert type, filter 49 alert type, set 49 alertcfg 44 options dr 44 el 44 rl 44 alertcfg command errors 273 alertcfg commands 44 example 45 alertentries 46 options 1 through 12 46 create (n, status, f, t, e, i) 47 del 46 e 49 f 49 i 50 n 48 status 48 t 49 test 50 alertentries command 46 alertentries command errors 274 alertentries commands example 50 alerts disable monitoring for all critical 149 disable monitoring for all critical legacy 154 disable monitoring for all informational 151 disable monitoring for all system legacy 156 disable monitoring for all warning 150 disable monitoring for all warning legacy 155 disable monitoring for blade device critical 149 disable monitoring for blade device informational 151 disable monitoring for blade device warning 150 disable monitoring for blade server throttled system legacy 157 disable monitoring for chassis critical 150 disable monitoring for chassis informational 152 disable monitoring for chassis warning 151 disable monitoring for cooling device critical 150 disable monitoring for cooling device informational 153 disable monitoring for cooling device warning 151 disable monitoring for critical temperature legacy 155 disable monitoring for critical voltage legacy 155 disable monitoring for event log full system legacy 157 disable monitoring for event log full warning legacy 156 disable monitoring for event log informational 152 disable monitoring for event log warning 151 disable monitoring for hard disk drive critical legacy 154
alerts (continued) disable monitoring for I/O module critical 149 disable monitoring for I/O module informational 151 disable monitoring for I/O module warning 150 disable monitoring for invalid configuration critical legacy 155 disable monitoring for inventory change informational 152 disable monitoring for inventory system legacy 157 disable monitoring for KVM/media tray switching failure warning legacy 156 disable monitoring for multiple chassis cooling device critical legacy 154 disable monitoring for multiple I/O-module failure critical legacy 154 disable monitoring for network change informational 152 disable monitoring for network change system legacy 157 disable monitoring for power failure critical legacy 155 disable monitoring for power management system legacy 157 disable monitoring for power module critical 150 disable monitoring for power module informational 153 disable monitoring for power module warning 151 disable monitoring for power off system legacy 157 disable monitoring for power on system legacy 156 disable monitoring for power state informational 152 disable monitoring for predictive failure analysis system legacy 157 disable monitoring for redundant module failure warning legacy 156 disable monitoring for remote login system legacy 158 disable monitoring for single chassis cooling device warning legacy 155 disable monitoring for storage module critical 149 disable monitoring for storage module informational 152 disable monitoring for storage module warning 150 disable monitoring for system management critical 150 disable monitoring for system management informational 152 disable monitoring for system management warning 151 disable monitoring for user activity informational 152 disable monitoring for VRM failure critical legacy 155 disable monitoring for warning temperature legacy 156 disable monitoring for warning voltage legacy 156 display all states 149 enable monitoring for all critical 149 enable monitoring for all critical legacy 154 enable monitoring for all informational 151 enable monitoring for all system legacy 156 enable monitoring for all warning 150
Index
329
alerts (continued) enable monitoring for all warning legacy 155 enable monitoring for blade device critical 149 enable monitoring for blade device informational 151 enable monitoring for blade device warning 150 enable monitoring for blade server throttled system legacy 157 enable monitoring for chassis critical 150 enable monitoring for chassis informational 152 enable monitoring for chassis warning 151 enable monitoring for cooling device critical 150 enable monitoring for cooling device informational 153 enable monitoring for cooling device warning 151 enable monitoring for critical temperature legacy 155 enable monitoring for critical voltage legacy 155 enable monitoring for event log full system legacy 157 enable monitoring for event log full warning legacy 156 enable monitoring for event log informational 152 enable monitoring for event log warning 151 enable monitoring for hard disk drive critical legacy 154 enable monitoring for I/O module critical 149 enable monitoring for I/O module informational 151 enable monitoring for I/O module warning 150 enable monitoring for invalid configuration critical legacy 155 enable monitoring for inventory change informational 152 enable monitoring for inventory system legacy 157 enable monitoring for KVM/media tray switching failure warning legacy 156 enable monitoring for multiple chassis cooling device critical legacy 154 enable monitoring for multiple I/O-module failure critical legacy 154 enable monitoring for network change informational 152 enable monitoring for network change system legacy 157 enable monitoring for power failure critical legacy 155 enable monitoring for power management system legacy 157 enable monitoring for power module critical 150 enable monitoring for power module informational 153 enable monitoring for power module warning 151 enable monitoring for power off system legacy 157 enable monitoring for power on system legacy 156 enable monitoring for power state informational 152 enable monitoring for predictive failure analysis system legacy 157 enable monitoring for redundant module failure warning legacy 156 enable monitoring for remote login system legacy 158
alerts (continued) enable monitoring for single chassis cooling device warning legacy 155 enable monitoring for storage module critical 149 enable monitoring for storage module informational 152 enable monitoring for storage module warning 150 enable monitoring for system management critical 150 enable monitoring for system management informational 152 enable monitoring for system management warning 151 enable monitoring for user activity informational 152 enable monitoring for VRM failure critical legacy 155 enable monitoring for warning temperature legacy 156 enable monitoring for warning voltage legacy 156 exclude event log with email alerts 44 include event log with email alerts 44 alerts (legacy) display all states 154 alerts, display 107 algorithms, encryption 15 all information reload 130 assistance, getting 321 attributes, display for firmware 230 authentication logging timeout set for management module 31 authority, command 6 automatic configuration setting display for management module 185
B
baud rate set for serial port of management module 170 bay data blade server 52 clear bay data 52 clear bay data for specific bay 52 display bay data 52 display bay data for specific bay 52 set bay data 52 set data definition to specific blade server 53 bay data clear blade server 52 bay data clear bay blade server 52 bay data for specific bay blade server 52 bay set data blade server 52 bay set data definition to specific blade server blade server 53 baydata 52 options b bay_num 52 b bay_num -clear 52 b bay_num -data data_definition 53
330
baydata (continued) options (continued) clear 52 data data_definition 52 baydata command errors 275 baydata commands 52 example 53 binding method LDAP 139 blade mezzanine command target 91 blade server 122 all blade servers 62 bay data 52 bay data clear 52 bay data clear for specific bay 52 bay data for specific bay 52 bay data set data 52 bay data set data definition to specific blade server 53 boot 58 boot (to console) 58 command target 90 config command 77, 78 example 78 cycle power 58, 182 disable cKVM 122 disable Ethernet channel 124 disable local power control 183 disable Wake on LAN 182 display all SRC records 85 display boot mode 59 display boot sequence 60 display cKVM status 122 display name 77 display network configuration status 122 display power state 182 display specific SRC record 85 display temperature 225 display voltage 262 dump service data 194 enable cKVM 122 enable Ethernet channel 124 enable local power control 182 enable power capping 102 enable power management 102 enable power saver mode 103 enable Wake on LAN 182 power off 181, 182 power on 181, 182 power on (to console) 181, 182 reset 58, 190 reset (clear NVRAM) 192 reset (run diagnostics with boot sequence) 192 reset (run diagnostics) 192 reset (to console) 58, 190 reset (with NMI) 191 set as KVM owner 134 set as media tray owner 159 set boot mode 59 set boot sequence 61, 62
blade server (continued) set Ethernet channel configuration method 123 set Ethernet channel gateway IP address 122 set Ethernet channel subnet mask 123 set Ethernet channel VLAN ID 123 set IP address 122 set name 77 set power capping 102 shutdown 181, 197 turn off 181, 182 turn on 181, 182 turn on (to console) 181, 182 blade server module display activity 148 display information 148 blade server power information display (overview) 99 blade server, display power trending 101 blade servers disable multiple video sessions 124 display starting IP address 121 enable multiple video sessions 124 enable single video session 124 set starting IP address 116, 121, 124 BladeCenter Open Fabric Manager management module 54, 55, 56 BladeCenter Open Fabric Manager commands NIC allocation 54 BladeCenter S 100 BladeCenter T specific commands 28 BladeCenter unit command target 90 configuring 19 display global cKVM status 125 display network settings 124 set starting BSMP IP address 124 set VLAN ID 124 BladeCenter units clear list of discovered 188 display all discovered 187 display filtered by IP address 187 display filtered by name 188 display health for all discovered 187 blink location LED 112, 144 blower command target 92 blower power information display 99 blower temperature display 99 blower, display power trending 101 BMC command target 91 bofm options l , i 54 l , i, d 54, 55 l , i, p 55, 56 bofm command example 56 bofm command errors 275 bofm commands 54 boot 58 blade server 58
Index
331
boot (continued) options -p powercycle 58 -p reset 58 c 58 boot (to console) blade server 58 boot command errors 276 boot commands 58 example 58 boot mode display for blade server 59 set for blade server 59 boot sequence display for blade server 60 set for all blade servers 62 set for blade server 61 bootmode 59 options p 59 bootmode command errors 276 bootmode commands 59 example 59 bootseq 60 cd 61 floppy 61 hd0 61 hd1 61 hd2 61 hd3 61 hd4 61 iscsi 61 iscsicrt 61 nodev 61 nw 61 options all 62 usbdisk 61 bootseq command errors 277 bootseq commands 60 example 63 built-in commands 26
C
capture service information 85 certificate file (SSL CSR) download 215 import 215 upload 215 certificate file (SSL self-signed certificate) download 215 import 215 upload 215 change command environment 23, 89 change user password 251 chassis internal network command 64 chassis internal network configuration 64 chassis internal network status 68 chassis internal network status command 68 cin 64
cin (continued) options cin -entry_index id vlan_id -ip ip_address 65 entry_index -ip ip_address 65 entry_index clear 64 entry_index en 65 global en 64 id 66 CIN turn index entries on or off 64 cin all options clear 64 en state 64 cin command 64 cin command errors 277 cin commands example 66 CIN configuration 64 Specify ID 66 CIN configuration entries 64 CIN configuration entry 65 Specify IP 65 CIN configuration table display for management module 64 CIN state set for enable or disable 64 CIN status table entries 68 cinstatus 68 cinstatus command 68 cinstatus commands example 68 cKVM disable for blade server 122 enable for blade server 122 cKVM (global) status display for BladeCenter unit 125 cKVM status display (global) for BladeCenter unit 125 display for blade server 122 clear options cnfg 71 config 69 clear alarms alarm ID 41 complete alarm key 41 generator ID 41 generator information 41 clear CIN configuration management module 64 clear command 69, 71 clear command errors 278 clear commands example 70, 71 clear event log management module 72 clear for management module 64 clear management module event log commands 72 example 72
332
clearlog example 72 clearlog command errors 279 clearlog commands 72 example 72 CLI exit codes for SSH 19 CLI inactivity timeout set for management module 32 CLI key sequence set for SOL 208 CLI SSH server disable for management module 210 enable for management module 210 clock 73 options d 73 dst 75 g 74 t 73 clock command errors 279 clock commands 73 example 76 clock settings display for management module 73 command health 106, 107 power management policy 167 system physical configuration 146 command authority 6 command environment selecting 4 command history 111 command redirect 23, 89 command syntax 28 command target 23, 89 alarm panel 92 blade mezzanine 91 blade server 90 BladeCenter unit 90 blower 92 BMC 91 high-speed expansion card 91 I/O module 92 I/O-expansion card 91 integrated system management processor management card 91 management module 90 media tray 92 microprocessor 91 multiplexer expansion module 93 network clock module 93 power module 92 service processor 91 storage expansion unit 91 switch module 92 temporary 5 view 146 command target selection 4 command-line interface disable for management module 228 enable for management module 228
91
command-line interface (continued) errors 267 guidelines 3 case sensitivity 4 command history 4 data types 4 delimiters 4 help 4 options 3 output format 4 strings 4 introduction 1 starting 15 using 3, 23 command-line session configuration display for management module 224 command-line session timeout display for management module 224 command-line timeout set for management module 224 commands accseccfg 29, 35 advfailover 36, 37 alarm 38, 42 alertcfg 44, 45 alertentries 46, 50 baydata 52, 53 bofm 54, 56 boot 58 bootmode 59 bootseq 60, 63 built-in 26 cin 66 cin command 64 cinstatus 68 cinstatus command 68 clear 69, 70, 71 clear management module event log 72 clearlog 72 clock 73, 76 common 26 config 77, 78 configuration 26 console 79 dhcpinfo 80 discovery 27 display management module event log 81, 83 displaylog 81, 83 displaysd 85, 86 dns 87, 88 environment 89, 93 event log, clear for management module 72 event log, display for management module 81, 83 examples account security 35 accseccfg 35 advfailover 37 alarm 42, 144 alertcfg 45 alertentries 50 baydata 53
Index
333
commands (continued) examples (continued) blade server name 78 BladeCenter Open Fabric Management 56 bofm 56 boot 58 bootmode 59 bootseq 63 cin 66 cinstatus 68 clear 70, 71 clear management module event log 72 clearlog 72 clock 76 config 78 console 79 DHCP settings for management module 80 dhcpinfo 80 display KVM owner 134 display management module event log 83 display management module security 195 display media tray owner 160 displaylog 83 displaysd 86 DNS 88 env 93 environment 93 environment redirect 93 Ethernet network settings for management module 116, 126 exit 94 files 95 fuelg 97, 103 health 107 help 109 history 111 I/O management 56 I/O module network protocol configuration 163 identify 112 ifconfig 116, 126 info 130 iocomp 132 kvm 134 LDAP configuration for management module 141 ldapcfg 141 list 146 management module DHCP settings 80 management module DNS 88 management module Ethernet network settings 116, 126 management module event log clear 72 management module event log display 83 management module LDAP configuration 141 management module name 78 management module network port configuration 180 management module restore configuration 186 management module save configuration 264 management module serial port settings 170 management module service 196 management module SLP configuration 198
commands (continued) examples (continued) management module SMTP settings 199 management module SNMP settings 204 management module SSH 211 management module telnet configuration 224 management module uplink failover 233, 236 modactlog 148 monalerts 153 monalertsleg 158 mt 160 name for blade server 78 name for management module 78 nat 163 network port configuration for management module 180 network protocol configuration for I/O module 163 ntp 165 ping 166 pmpolicy 168 portcfg 170 ports 180 power 184 read 186 remotechassis 188 reset 193 restore configuration for management module 186 save configuration for management module 264 sddump 194 security 195 Serial Over LAN 209 serial port settings for management module 170 service 196 set KVM owner 134 set management module security 195 set media tray owner 160 shutdown 197 slp 198 SLP configuration for management module 198 smtp 199 SMTP settings for management module 199 snmp 204 SNMP settings for management module 204 sol 209 SSH configuration for management module 211 sshcfg 211 sslcfg 217 syntax help 109 syslog 219 tcpcmdmode 220, 223 telnetcfg 224 temps 225 trespass 226 uicfg 229 update 231 uplink 233, 236 user account security 35 user interface configuration 229 users 245, 260
334
commands (continued) examples (continued) volts 262 write 264 zonecfg 265 exit 94 files 95 fuelg 96, 97, 99, 103 help 109 history 111 identify 112 ifconfig 113, 116, 118, 126 info 128, 130 iocomp 132 kvm 134 ldapcfg 136, 141 led 142, 144 LED 27 list 146 management module event log 27 management module failover 233, 235, 236 memory 27 modactlog 148 monalerts 149, 153 monalertsleg 154, 158 mt 159, 160 nat 161, 163 ntp 164, 165 ping 166 pmpolicy 167, 168 portcfg 170 ports 172, 180 power 181, 184 power control 28 power management 28 read 185, 186 remotechassis 187, 188 reset 190, 193 reset command 28 restore configuration 28 save configuration 28 sddump 194 security 195 Serial Over LAN 205, 209 service 196 session command 28 shutdown 197 slp 198 smtp 199 snmp 200, 204 SOL 205, 209 sshcfg 210, 211 sslcfg 212, 217 syslog 218, 219 system management command 28 tcpcmdmode 220, 222, 223 telnet configuration 224 telnetcfg 224 temps 225 trespass 226 uicfg 228, 229
commands (continued) update 230, 231 uplink 233, 235, 236 user interface configuration 228, 229 users 238, 245, 247, 260 volts 262 write 263, 264 zonecfg 265 comment SSH public key 260 common commands 26 common errors 269 communicating with IBM Director 220, 222 communication out-of-band 220, 222 test I/O module 166 communication rate set for serial port of management module 170 compatibility I/O module display details for blade server 132 display details for I/O module 132 display for all components 132 component and reloading information 128 component information display 128 config 77 options contact 78 loc 77 name 77 config command 77 example 78 config command errors 280 configuration disable automatic for management module 186 enable automatic for management module 186 save for management module (to chassis) 263 save for management module (to file) 264 view for management module 146 view tree for system 146 configuration (encryption) save for management module (to file) 263 configuration (no encryption) save for management module (to file) 263 configuration commands 26 configuration from file (encryption) restore for management module 185 configuration from file (no encryption) restore for management module 185 configuration from midplane restore for management module 185 configuration information display for network card 122 configuration method set for channel 0 of management module 114, 120 set for channel of blade server 123 configure LDAP command example 141 configure network ports command example 180 configure network protocols command example 163
Index
335
configure SLP command example 198 confirm password LDAP distinguished name 140 connect to SSH public key 259 console 79 create override SOL session 79 create SOL session 79 options o 79 console command 79 console command errors 280 console commands example 79 contact name display for management module 77 set for management module 78 create a CIN configuration entry create CIN entry 65 create alert recipient 47, 48 create entry CIN configuration entry management module 65 create override SOL session 79 create SOL session 79 create user 239, 240, 249 critical alerts disable monitoring for all 149 disable monitoring for blade device 149 disable monitoring for chassis 150 disable monitoring for cooling device 150 disable monitoring for I/O module 149 disable monitoring for multiple chassis cooling device 154 disable monitoring for power module 150 disable monitoring for storage module 149 disable monitoring for system management 150 enable monitoring for all 149 enable monitoring for blade device 149 enable monitoring for chassis 150 enable monitoring for cooling device 150 enable monitoring for I/O module 149 enable monitoring for power module 150 enable monitoring for storage module 149 enable monitoring for system management 150 critical legacy alerts disable monitoring for all 154 disable monitoring for hard disk drive 154 disable monitoring for invalid configuration 155 disable monitoring for multiple I/O-module failure 154 disable monitoring for power failure 155 disable monitoring for temperature 155 disable monitoring for voltage 155 disable monitoring for VRM failure 155 enable monitoring for all 154 enable monitoring for hard disk drive 154 enable monitoring for invalid configuration 155 enable monitoring for multiple chassis cooling device 154
critical legacy alerts (continued) enable monitoring for multiple I/O-module failure 154 enable monitoring for power failure 155 enable monitoring for temperature 155 enable monitoring for voltage 155 enable monitoring for VRM failure 155 CSR generate for LDAP client 214 generate for management module Web server CSR (SSL) download certificate file 215 import certificate file 215 upload certificate file 215 cycle power blade server 58, 182 I/O module 182 switch module 182
214
D
data encryption display management module setting 195 enable for management module 195 data rate set for channel 0 of management module 114, 120 date display for management module 73 set for management module 73 daylight-savings time mode set for management module 75 daylight-savings time setting display for management module 73 default IP address 16 delete alert recipient 46 delete CIN configuration management module 64 delete file management module 95 delete for management module 64 delete user 238, 248 DHCP settings for management module commands example 80 dhcpinfo options eth0 80 dhcpinfo command errors 281 dhcpinfo commands 80 example 80 disable additional SSL certificate for standby management module 212 blade server Ethernet channel VLAN ID 123 CLI SSH server for management module 210 enhanced legacy alert categories 149, 154 logging of login events from same IP address 32 monitoring for all critical alerts 149 monitoring for all critical legacy alerts 154 monitoring for all informational alerts 151 monitoring for all system legacy alerts 156 monitoring for all warning alerts 150
336
disable (continued) monitoring for all warning legacy alerts 155 monitoring for blade device critical alerts 149 monitoring for blade device informational alerts 151 monitoring for blade device warning alerts 150 monitoring for blade server throttled system legacy alerts 157 monitoring for chassis critical alerts 150 monitoring for chassis informational alerts 152 monitoring for chassis warning alerts 151 monitoring for cooling device critical alerts 150 monitoring for cooling device informational alerts 153 monitoring for cooling device warning alerts 151 monitoring for critical temperature legacy alerts 155 monitoring for critical voltage legacy alerts 155 monitoring for event log full system legacy alerts 157 monitoring for event log full warning legacy alerts 156 monitoring for event log informational alerts 152 monitoring for event log warning alerts 151 monitoring for hard disk drive critical legacy alerts 154 monitoring for I/O module critical alerts 149 monitoring for I/O module informational alerts 151 monitoring for I/O module warning alerts 150 monitoring for invalid configuration critical legacy alerts 155 monitoring for inventory change informational alerts 152 monitoring for inventory system legacy alerts 157 monitoring for KVM/media tray switching failure warning legacy alerts 156 monitoring for multiple chassis cooling device critical legacy alerts 154 monitoring for multiple I/O-module failure critical legacy alerts 154 monitoring for network change informational alerts 152 monitoring for network change system legacy alerts 157 monitoring for power failure critical legacy alerts 155 monitoring for power management system legacy alerts 157 monitoring for power module critical alerts 150 monitoring for power module informational alerts 153 monitoring for power module warning alerts 151 monitoring for power off system legacy alerts 157 monitoring for power on system legacy alerts 156 monitoring for power state informational alerts 152 monitoring for predictive failure analysis system legacy alerts 157 monitoring for redundant module failure warning legacy alerts 156 monitoring for remote login system legacy alerts 158 monitoring for single chassis cooling device warning legacy alerts 155
disable (continued) monitoring for storage module critical alerts 149 monitoring for storage module informational alerts 152 monitoring for storage module warning alerts 150 monitoring for system management critical alerts 150 monitoring for system management informational alerts 152 monitoring for system management warning alerts 151 monitoring for user activity informational alerts 152 monitoring for VRM failure critical legacy alerts 155 monitoring for warning temperature legacy alerts 156 monitoring for warning voltage legacy alerts 156 SMASH SSH server for management module 210 SSL for LDAP client 212 SSL for management module Web server 212 syslog event log transmission for collector 1 218 syslog event log transmission for collector 2 218 TCP command mode 220, 222 disable automatic configuration management module 186 disable CIN configuration entry management module 65 disable cKVM blade server 122 disable command-line interface management module 228 disable complex password for management module user authentication 32 disable default administration password expiration for management module 32 disable DNS management module 87 disable Ethernet channel blade server 124 disable Ethernet channel 0 management module 121 disable external management I/O module 126 disable external ports I/O module 126 disable fast POST I/O module 183 disable for management module 65 disable FTP management module 177 disable HTTPS port management module 177 disable local KVM switching globally 134 disable local media tray switching globally 159 disable local power control blade server 183 globally 182 disable logical uplink failover advanced management module 236 management module (advanced) 236
Index
337
disable monitoring of event log state management module 83 disable multiple video sessions blade servers 124 disable NAT table I/O module 162 disable network interface management module (redundant) 36 disable NTP management module 164, 177 disable password change at first login to management module 33 disable password required for management module 34 disable physical uplink failover advanced management module 235 management module 233 management module (advanced) 235 disable power domain acoustic mode 102 disable power domain quiet mode 97 disable protected mode I/O module 126 disable remote media tray switching globally 159 disable secure SMASH over SSH management module 177 disable SMASH over Telnet management module 177 disable SNMP agent management module (SNMPv1) 200 management module (SNMPv3) 200 disable SNMP traps management module 178, 200 disable SNMPv1 management module 228 disable SNMPv1 agent management module 178 disable SNMPv3 management module 228 disable SNMPv3 agent management module 178 disable SOL global 207 disable SSH port management module 178 disable TCP command mode management module 178, 228 disable technician debug management module 196 disable Telnet port management module 179 disable TFTP management module 179 disable trespass feature management module 226 disable V3 authentication for NTP management module 165 disable Wake on LAN blade server 182 globally 182 disable Web interface management module 228
discovered BladeCenter units clear list 188 display all 187 display filtered by IP address 187 display filtered by name 188 display health for all 187 discovery commands 27 display alert state 149 clock settings, management module 73 date, management module 73 daylight-savings time setting, management module 73 GMT offset, management module 73 legacy alert state 154 TCP command-mode session status 220, 222 TCP command-mode session timeout 220, 222 time, management module 73 display (reset counter) event log management module 81 display active users 247 display activity blade server module 148 display advanced failover settings management module 36 display alarms alarm ID 39 all 38 complete alarm key 39 generator ID 39 generator information 39 power 38 display alert properties (all recipients) 46 display alert properties (single recipient) 46 display alerts 107 display all BladeCenter units on network 187 display all event log entries management module 81 display all event log filters management module 81 display all users 238, 247 display automatic configuration setting management module 185 display blade server power information overview 99 display blade server SRC record (specific) 85 display blade server SRC records (all) 85 display blower power information 99 display blower temperature 99 display boot mode blade server 59 display CIN configuration table management module 64 display CIN status table entries management module 68 display cKVM status blade server 122 display command-line session configuration management module 224 display command-line session timeout management module 224 display component information 128
338
display configuration information network card 122 display contact name management module 77 display DNS configuration management module 87 display DSA host key information management module 210 display Ethernet channel 0 configuration management module 113 management module (primary) 118 management module (standby) 118 display Ethernet channel 0 DHCP configuration management module 80 display Ethernet channel 1 configuration management module 115 display event log management module 81 display event log entries filtered by date management module 81 display event log entries filtered by severity level management module 82 display event log entries filtered by source management module 82 display failover configuration management module 233, 235 display file list management module 95 display firmware attributes 230 display free space management module 95 display global cKVM status BladeCenter unit 125 display global remote alert settings management module 44 display health for BladeCenter units on network 187 display health status 106, 107 display health status (tree) 106 display I/O module compatibility all components 132 display I/O module compatibility details blade server 132 I/O module 132 display I/O module power information 99 display I/O module SAS zone information 265 display I/O module SAS zone list 265 display information blade server module 148 display KVM owner 134 display LDAP settings management module 136 display LED state blower fault 142 external port link status 142 fanpack fault 142 fault 143 for blade server and all sub-components 143 for blade server front panel 142 safe-to-remove 143 display location management module 77
display management module account security settings 29 display management module data encryption setting 195 display management module event log commands 81 example 83 display management module security 195 display management module status 85 display media tray owner 159 display media tray temperature 100 display monitoring of event log state management module 83 display name blade server 77 management module 77 display network configuration status blade server 122 display network port settings management module 172 display network protocol settings I/O module 161 display network settings BladeCenter unit 124 I/O module 125 display NTP configuration management module 164 display open ports management module 172 display POST status I/O module 183 switch module 183 display power domain information details 96, 100 display power domain information overview 96, 99 display power state blade server 182 I/O module 182 switch module 182 display power trending (blade server) 101 display power trending (blower) 101 display power trending (I/O module) 101 display power trending (media tray) 101 display power trending (power domain) 101 display power trending (system) 101 display RSA host key information management module 210 display SAS zone information I/O module 265 display SAS zone list I/O module 265 display serial port configuration management module 170 display service data command 85 display service information 85 display service setting management module 196 display single user 238, 247 display SLP settings management module 198 display SMTP server host name management module 199
Index
339
display SMTP server IP address management module 199 display SNMP configuration management module 200 display SSH public key 256 display SSH status management module 210 display starting IP address blade servers 121 display state location LED 112 display state of -lse option management module 81 Display status of first five entries management module 68 display syslog configuration management module 218 display telnet configuration management module 224 display telnet timeout management module 224 display temperature blade server 225 management module 225 media tray 225 display trespass feature status management module 226 display uplink configuration management module 233, 235 display user interface settings management module 228 display various LED states LED states 142 display voltage blade server 262 management module 262 displaylog 81 display state of -lse option 81 options -lse 81 a 81 date 81 f 81 filters 81 i 83 i, l 83 l 83 l, i 83 lse 82, 83 sev 82 src 82 displaylog command errors 281 displaylog commands 81 example 83 displaysd 85 options i 85 i, save 85 mmstat 85 save 85 save, i 85
displaysd (continued) options (continued) src 85 displaysd command errors 282 displaysd commands 85 example 86 distinguished name LDAP client 139 distinguished name password LDAP client 139 distinguished name password (confirm) LDAP client 140 dns 87 options i1 87 i2 87 i3 87 off 87 on 87 DNS disable for management module 87 enable for management module 87 dns command errors 283 dns commands 87 example 88 DNS configuration display for management module 87 DNS first IP address set for management module 87 DNS second IP address set for management module 87 DNS third IP address set for management module 87 download 216, 217 download certificate file SSL CSR 215 SSL self-signed certificate 215 download SSH public key 259 DSA host key information display for management module 210 dump service data blade server 194 duplex mode set for channel 0 of management module
114, 120
E
email alerts exclude event log 44 include event log 44 enable additional SSL certificate for standby management module 212 blade server Ethernet channel VLAN ID 123 CLI SSH server for management module 210 enhanced legacy alert categories 149, 154 monitoring for all critical alerts 149 monitoring for all critical legacy alerts 154 monitoring for all informational alerts 151 monitoring for all system legacy alerts 156 monitoring for all warning alerts 150
340
enable (continued) monitoring for all warning legacy alerts 155 monitoring for blade device critical alerts 149 monitoring for blade device informational alerts 151 monitoring for blade device warning alerts 150 monitoring for blade server throttled system legacy alerts 157 monitoring for chassis critical alerts 150 monitoring for chassis informational alerts 152 monitoring for chassis warning alerts 151 monitoring for cooling device critical alerts 150 monitoring for cooling device informational alerts 153 monitoring for cooling device warning alerts 151 monitoring for critical temperature legacy alerts 155 monitoring for critical voltage legacy alerts 155 monitoring for event log full system legacy alerts 157 monitoring for event log full warning legacy alerts 156 monitoring for event log informational alerts 152 monitoring for event log warning alerts 151 monitoring for hard disk drive critical legacy alerts 154 monitoring for I/O module critical alerts 149 monitoring for I/O module informational alerts 151 monitoring for I/O module warning alerts 150 monitoring for invalid configuration critical legacy alerts 155 monitoring for inventory change informational alerts 152 monitoring for inventory system legacy alerts 157 monitoring for KVM/media tray switching failure warning legacy alerts 156 monitoring for logging of login events from same IP address 32 monitoring for multiple chassis cooling device critical legacy alerts 154 monitoring for multiple I/O-module failure critical legacy alerts 154 monitoring for network change informational alerts 152 monitoring for network change system legacy alerts 157 monitoring for power failure critical legacy alerts 155 monitoring for power management system legacy alerts 157 monitoring for power module critical alerts 150 monitoring for power module informational alerts 153 monitoring for power module warning alerts 151 monitoring for power off system legacy alerts 157 monitoring for power on system legacy alerts 156 monitoring for power state informational alerts 152 monitoring for predictive failure analysis system legacy alerts 157 monitoring for redundant module failure warning legacy alerts 156 monitoring for remote login system legacy alerts 158
enable (continued) monitoring for single chassis cooling device warning legacy alerts 155 monitoring for storage module critical alerts 149 monitoring for storage module informational alerts 152 monitoring for storage module warning alerts 150 monitoring for system management critical alerts 150 monitoring for system management informational alerts 152 monitoring for system management warning alerts 151 monitoring for user activity informational alerts 152 monitoring for VRM failure critical legacy alerts 155 monitoring for warning temperature legacy alerts 156 monitoring for warning voltage legacy alerts 156 SMASH SSH server for management module 210 SSL for LDAP client 212 SSL for management module Web server 212 syslog event log transmission for collector 1 218 syslog event log transmission for collector 2 218 TCP command mode 220, 222 enable automatic configuration management module 186 enable CIN configuration entry management module 65 enable cKVM blade server 122 enable command-line interface management module 228 enable complex password for management module user authentication 32 enable data encryption management module 195 enable default administration password expiration for management module 32 enable DNS management module 87 enable Ethernet channel blade server 124 enable Ethernet channel 0 management module 121 enable external management I/O module 126 enable external ports I/O module 126 enable fast POST I/O module 183 enable for management module 65 enable FTP management module 176 enable HTTPS port management module 177 enable local KVM switching globally 134 enable local media tray switching globally 159 enable local power control blade server 182
Index
341
enable local power control (continued) globally 182 enable logical uplink failover advanced management module 236 management module (advanced) 236 enable monitoring of event log state management module 82 enable multiple video sessions blade servers 124 enable NAT table I/O module 162 enable network interface and allow IP swap management module (redundant) 36 enable network interface and prevent IP swap management module (redundant) 36 enable NTP management module 164, 177 enable password change at first login to management module 33 enable password required for management module 34 enable physical uplink failover advanced management module 235 management module 233 management module (advanced) 235 enable power capping for blade server 102 enable power domain acoustic mode 102 enable power domain quiet mode 97 enable power management for blade server 102, 103 enable power saver mode for blade server 103 enable protected mode I/O module 126 enable remote media tray switching globally 159 enable secure SMASH over SSH management module 177 enable security management module 195 enable single video session blade servers 124 enable SMASH over Telnet management module 177 enable SNMP agent management module (SNMPv1) 200 management module (SNMPv3) 200 enable SNMP traps management module 178, 200 enable SNMPv1 management module 228 enable SNMPv1 agent management module 178 enable SNMPv3 management module 228 enable SNMPv3 agent management module 178 enable SOL global 206, 207 enable SSH port management module 178 enable TCP command mode management module 178, 228
enable technician debug management module 196 enable Telnet port management module 179 enable TFTP management module 179 enable trespass feature management module 226 enable V3 authentication for NTP management module 164 enable Wake on LAN blade server 182 globally 182 enable Web interface management module 228 encryption algorithms 15 end session 94 ending an SOL session 22, 79 enhanced legacy alert categories disable 149, 154 enable 149, 154 entries of the CIN status table display for management module 68 env 90 options blade 90, 91 blower 92 mt 92 mux 93 ncc 93 power 92 switch 92 system (management module) 90 tap 92 env command errors 283 env commands example 93 environment alarm panel 92 blade mezzanine 91 blade server 90 BladeCenter unit 90 blower 92 BMC 91 high-speed expansion card 91 I/O module 92 I/O-expansion card 91 integrated system management processor management module 90 media tray 92 microprocessor 91 multiplexer expansion module 93 network clock module 93 power module 92 service processor 91 storage expansion unit 91 switch module 92 environment commands 89 example 93 errors accseccfg command 271
91
342
errors (continued) advfailover command 272 alarm command 273 alertcfg command 273 alertentries command 274 baydata command 275 bofm command 275 boot command 276 bootmode command 276 bootseq command 277 cin command 277 clear command 278 clearlog command 279 clock command 279 command-line interface 267 common 269 config command 280 console command 280 dhcpinfo command 281 displaylog command 281 displaysd command 282 dns command 283 env command 283 exit command 283 files command 283 fuelg command 284 health command 287 help command 288 history command 288 identify command 288 ifconfig command 289 info command 292 iocomp command 293 kvm command 293 ldapcfg command 293 led command 294 list command 295 modactlog command 295 monalerts command 295 monalertsleg command 295 mt command 296 nat command 296 ntp command 296 ping command 297 pmpolicy command 297 portcfg command 297 ports command 297 power command 298 read command 299 remotechassis command 300 reset command 300 sddump command 301 security command 301 service command 301 shutdown command 302 slp command 302 smtp command 302 snmp command 303 sol command 304 sshcfg command 305 sslcfg command 306
errors (continued) syslog command 308 tcpcmdmode command 308 telnetcfg command 309 temps command 309 thres command 310 trespass command 310 uicfg command 310 update command 311 uplink command 313 users command 313 volts command 318 write command 318 zonecfg command 319 Ethernet configuring remote connection 20 Ethernet channel disable for blade server 124 enable for blade server 124 Ethernet channel 0 disable for management module 121 enable for management module 121 Ethernet channel 0 configuration display for management module 113 display for management module (primary) 118 display for management module (standby) 118 Ethernet channel 0 configuration method set for management module 114, 120 Ethernet channel 0 data rate set for management module 114, 120 Ethernet channel 0 DHCP configuration display for management module 80 Ethernet channel 0 duplex mode set for management module 114, 120 Ethernet channel 0 gateway IP address set for management module 113, 119 Ethernet channel 0 hostname set for management module 114, 119 set for standby management module 119 Ethernet channel 0 MAC address set for management module 115, 120 set for standby management module 121 Ethernet channel 0 MTU set for management module 115, 120 Ethernet channel 0 static IP address set for management module 113, 118 set for standby management module 119 Ethernet channel 0 subnet mask set for management module 113, 119 Ethernet channel 1 disable for management module 116 enable for management module 116 Ethernet channel 1 configuration display for management module 115 Ethernet channel 1 gateway IP address set for management module 115 Ethernet channel 1 MAC address set for management module 116 Ethernet channel 1 static IP address set for management module 115
Index
343
Ethernet channel 1 subnet mask set for management module 116 Ethernet channel configuration method set for blade server 123 Ethernet channel gateway IP address set for blade server 122 Ethernet channel static IP address set for blade server 122 Ethernet channel subnet mask set for blade server 123 Ethernet channel VLAN ID set for blade server 123 Ethernet network settings for management module commands example 116, 126 event log clear for management module 72 disable monitoring of state 83 display (reset counter) for management module display all entries for management module 81 display all filters for management module 81 display entries for management module, filtered date 81 display entries for management module, filtered severity level 82 display entries for management module, filtered source 82 display for management module 81 display monitoring of state 83 enable monitoring of state 82 exclude from email alerts 44 include with email alerts 44 save to TFTP server 83 event log, clear for management module commands 72 event log, display for management module commands 81 exit 94 exit codes (CLI) Secure Shell server 19 exit command 94 exit command errors 283 exit commands example 94 external management disable for I/O module 126 enable for I/O module 126 external ports disable for I/O module 126 enable for I/O module 126
81
by by by
files command errors 283 files commands 95 example 95 filter alert type 49 firmware display attributes 230 update 230 update (verbose) 231 firmware requirements 2 firmware update 230 flash location LED 112, 144 FTP disable for management module 177 enable for management module 176 FTP data port number set for management module 173 FTP port number set for management module 173 FTP timeout set for management module 179 fuelg 96, 99, 100 options am 102 int 101 os 96 pcap 102 pm 96, 100 pme 102, 103 pt 101 qm 97 tt 101 fuelg command errors 284 fuelg commands 96, 99 example 97, 103
G
gateway IP address set for channel 0 of management module 113, 119 set for channel 1 of management module 115 set for channel of blade server 122 set for I/O module 125 generate CSR (LDAP client) 214 CSR (management module Web server) 214 self-signed certificate (LDAP client) 213 self-signed certificate (management module Web server) 213 generate host key management module 210 generate test alert 50 getting help 321 global disable local KVM switching 134 disable local media tray switching 159 disable local power control 182 disable remote media tray switching 159 disable Wake on LAN 182 enable local KVM switching 134 enable local media tray switching 159 enable local power control 182
F
failover configuration display for management module fast POST disable for I/O module 183 enable for I/O module 183 files 95 options d 95 233, 235
344
global (continued) enable remote media tray switching 159 enable Wake on LAN 182 global disable SOL 207 global enable SOL 206, 207 GMT offset display for management module 73 set for management module 74 group filter LDAP 140 group search attribute LDAP 140 guidelines case sensitivity 4 command history 4 data types 4 delimiters 4 help 4 options 3 output format 4 overview of 3 strings 4
HTTP port number set for management module 173 HTTPS port disable for management module 177 enable for management module 177 HTTPS port number set for management module 174
I
I/O management commands 54 I/O module activate network protocol settings 161 activate SAS zone 265 command target 92 cycle power 182 disable external management 126 disable external ports 126 disable fast POST 183 disable NAT table 162 disable protected mode 126 display network protocol settings 161 display network settings 125 display POST status 183 display power state 182 display SAS zone information 265 display SAS zone list 265 enable external management 126 enable external ports 126 enable fast POST 183 enable NAT table 162 enable protected mode 126 keep new IP address configuration after reset nat command 161, 163 example 163 ping 166 power off 181 power on 181, 182 reset 190 reset (extended diagnostics) 191 reset (full diagnostics) 191 reset (standard diagnostics) 191 reset configuration 69, 71 reset network protocol settings 161 revert to old IP address configuration after reset 125 set gateway IP address 125 set IP address 125 set NAT external port number 162 set NAT internal port number 162 set NAT protocol ID 162 set NAT protocol name 161 set subnet mask 126 test communication 166 turn off 181 turn on 182 I/O module compatibility display details for blade server 132 display details for I/O module 132 display for all components 132 I/O module power information display 99
Index
H
hardware requirements 2 hardware service and support 322 health 106 display for all BladeCenter units on network 187 display status 106 display status (tree) 106 display status and alerts 107 options f 107 l 106 health command 106, 107 example 107 health command errors 287 help 23, 109 help command 109 help command errors 288 help commands example 109 help for update command 230 help, getting 321 high-speed expansion card command target 91 history 111 history command 111 history command errors 288 history commands example 111 host key generate for management module 210 host name set for channel 0 of management module 114, 119 set for channel 0 of standby management module 119
125
345
I/O module, display power trending I/O modules bofm 54, 55, 56 I/O-expansion card command target 91 IBM Director communication 220, 222 IBM Support Line 322 identify 112 options s 112 s, d 112 identify command 112 identify command errors 288 identify commands example 112 ifconfig 121, 122, 124, 125 options bsmp 124 ckvm, disabled 122, 125 ckvm, enabled 122, 125 em, disabled 126 em, enabled 126 ep, disabled 126 ep, enabled 126 eth0 113, 118 eth0, c 114, 120 eth0, d 114, 120 eth0, down 121 eth0, g 113, 119 eth0, i 113, 118 eth0, l 115, 120 eth0, m 115, 120 eth0, n 114, 119 eth0, o 118 eth0, o, i 119 eth0, o, l 121 eth0, o, n 119 eth0, r 114, 120 eth0, s 113, 119 eth0, up 121 eth1 115 eth1, down 116 eth1, g 115 eth1, i 115 eth1, l 116 eth1, s 116 eth1, up 116 ethx 122 ethx, c 123 ethx, down 124 ethx, g 122 ethx, i 122 ethx, s 123 ethx, up 124 ethx, v 123 ethx, ve 123 g 125 i 116, 121, 125 maxv, disabled 124 maxv, enabled 124
101
ifconfig (continued) options (continued) pip 125 pm, disabled 126 pm, enabled 126 s 126 v 124 ifconfig command errors 289 ifconfig commands 113, 118 example 116, 126 import 216, 217 import certificate file SSL CSR 215 SSL self-signed certificate 215 info 128 options reload -fw 130 reload -hw 130 optionsall reload 130 optionsmac reload 130 optionswwn reload 130 info command 128 info command errors 292 info commands example 130 information about components and reloading components 128 information display, blade server power (overview) 99 information display, blower power 99 information display, component 128 information display, I/O module power 99 information display, power domain (detailed) 96, 100 information display, power domain (overview) 96, 99 information LED turn off 143 information reload, all 130 information reload, firmware 130 information reload, hardware 130 information reload, MAC addresses 130 information reload, WWN 130 informational alerts disable monitoring for all 151 disable monitoring for blade device 151 disable monitoring for chassis 152 disable monitoring for cooling device 153 disable monitoring for event log 152 disable monitoring for I/O module 151 disable monitoring for inventory change 152 disable monitoring for network change 152 disable monitoring for power module 153 disable monitoring for power state 152 disable monitoring for storage module 152 disable monitoring for system management 152 disable monitoring for user activity 152 enable monitoring for all 151 enable monitoring for blade device 151 enable monitoring for chassis 152 enable monitoring for cooling device 153
346
informational alerts (continued) enable monitoring for event log 152 enable monitoring for I/O module 151 enable monitoring for inventory change 152 enable monitoring for network change 152 enable monitoring for power module 153 enable monitoring for power state 152 enable monitoring for storage module 152 enable monitoring for system management 152 enable monitoring for user activity 152 integrated system management processor command target 91 iocomp 132 iocomp command errors 293 iocomp commands 132 example 132 IP address display BladeCenter units on network filtered by 187 display starting for blade servers 121 set for blade server 122 set for I/O module 125 set for management module 113, 118 set for standby management module 119 set starting for blade servers 116, 121, 124 IP address (BSMP) set starting for BladeCenter unit 124 IP address configuration keep new after reset 125 revert to old after reset 125 IP address, default 16 ISMP reset 190
L
LDAP client generate CSR 214 generate self-signed certificate 213 LDAP client distinguished name set for management module 139 LDAP client distinguished name password set for management module 139 LDAP client distinguished name password (confirm) set for management module 140 LDAP group filter set for management module 140 LDAP group search attribute set for management module 140 LDAP login permission attribute set for management module 141 LDAP name set for management module 136 LDAP root distinguished name set for management module 138 LDAP security version set for management module 136 LDAP server (first) host name set for management module 137 LDAP server (first) IP address set for management module 137 LDAP server (first) port number set for management module 138 LDAP server (second) host name set for management module 137 LDAP server (second) IP address set for management module 137 LDAP server (second) port number set for management module 138 LDAP server (third) host name set for management module 138 LDAP server (third) IP address set for management module 138 LDAP server (third) port number set for management module 138 LDAP server binding method set for management module 139 LDAP server discovery method set for management module 136 LDAP server domain source set for management module 137 LDAP server search domain set for management module 137 LDAP server service name set for management module 137 LDAP settings display for management module 136 LDAP UID search attribute set for management module 139 ldapcfg 136 options bm 139 cd 139 cp 140 ds 137 gf 140
Index
J
JS20 blade server commands reset (clear NVRAM) 192 reset (run diagnostics with boot sequence) reset (run diagnostics) 192 reset (with NMI) 191 192
K
keep new IP address configuration after reset I/O module 125 kvm 134 options b 134 local 134 KVM display owner 134 set owner 134 kvm command errors 293 kvm commands 134 example 134 KVM port set state for management module 177 KVM port number set for management module 174
347
ldapcfg (continued) options (continued) gsa 140 i1 137 i2 137 i3 138 lpa 141 p 139 p1 138 p2 138 p3 138 rd 138 sd 137 server 136 sn 137 t 136 usa 139 v 136 ldapcfg command 136 example 141 ldapcfg command errors 293 led 142 options e 143 info 142 info off 143 l 142, 143 loc 142, 144 loc, d 144 r 143 LED (information) turn off 143 LED (location), control 112 led command 142 led command errors 294 led commands example 144 LED commands 27 LED state display (blade server front panel) 142 display (external port link status) 142 display (fault) 143 display (for blade server and all subcomponents) 143 display (safe-to-remove) 143 display (state for blower fault LED) 142 display (state for fanpack fault LED) 142 display various LED states 142 legacy alert state display all 154 legacy alerts display all states 154 light location LED 112, 144 time period 144 light location LED (BladeCenter unit) time period 112 list 146 options l 146 list command example 146
list command errors 295 local KVM switching disable globally 134 enable globally 134 local media tray switching disable globally 159 enable globally 159 local power control disable for blade server 183 disable globally 182 enable for blade server 182 enable globally 182 location display for management module 77 set for management module 77 location LED blink 112, 144 display state 112 flash 112, 144 light 112, 144 time period 144 light (BladeCenter unit) time period 112 turn off 112, 144 location LED control 112 logging disable for logging of login events from same IP address 32 enable for logging of login events from same IP address 32 login permission attribute LDAP 141
M
MAC address set for channel 0 of management module 115, 120 set for channel 0 of standby management module 121 set for channel 1 of management module 116 manage alert recipients 46 management card command target 91 management module 65, 66 account security commands 29, 54 accseccfg 29 accseccfg commands 29, 35 add SSH public key 256 add SSH public key (specific) 257 advfailover command 36, 37 example 37 bofm 54, 55, 56 bofm commands 54, 56 cabling 13 change user password 251 cin commands 64 cinstatus commands 68 clear CIN configuration entries 64 clear event log 72 clear event log commands example 72
348
management module (continued) command target 90 command-line session configuration 224 command-line session timeout 224 command-line timeout 224 comment SSH public key 260 config command 77, 78 example 78 configuring 20 connect to SSH public key 259 create alert recipient 47, 48 create user 239, 240, 249 default IP address 16 delete alert recipient 46 delete CIN configuration 64 delete file 95 delete user 238, 248 DHCP settings commands example 80 dhcpinfo commands 80 direct connection 14 disable automatic configuration 186 disable CIN configuration entry 65 disable CLI SSH server 210 disable command-line interface 228 disable complex password 32 disable default administration password expiration 32 disable DNS 87 disable Ethernet channel 0 121 disable Ethernet channel 1 116 disable FTP 177 disable HTTPS port 177 disable monitoring of event log state 83 disable network interface for redundant 36 disable NTP 164, 177 disable password change at first login 33 disable password required 34 disable physical uplink failover 233 disable secure SMASH over SSH 177 disable SMASH over Telnet 177 disable SMASH SSH server 210 disable SNMP agent (SNMPv1) 200 disable SNMP agent (SNMPv3) 200 disable SNMP traps 178, 200 disable SNMPv1 228 disable SNMPv1 agent 178 disable SNMPv3 228 disable SNMPv3 agent 178 disable SSH port 178 disable TCP command mode 178, 228 disable technician debug 196 disable Telnet port 179 disable TFTP 179 disable trespass feature 226 disable V3 authentication for NTP 165 disable Web interface 228 display (reset counter) event log 81 display account security settings 29 display active users 247 display advanced failover settings 36
management module (continued) display alert properties (all recipients) 46 display alert properties (single recipient) 46 display all event log entries 81 display all event log filters 81 display all users 238, 247 display automatic configuration setting 185 display CIN configuration table 64 display clock settings 73 display contact name 77 display date 73 display daylight-savings time setting 73 display DNS configuration 87 display DSA host key information 210 display entries of CIN status table 68 display Ethernet channel 0 configuration 113 display Ethernet channel 0 DHCP configuration 80 display Ethernet channel 1 configuration 115 display event log 81 display event log commands example 83 display event log entries filtered by date 81 display event log entries filtered by severity level 82 display event log entries filtered by source 82 display file list 95 display free space 95 display global remote alert settings 44 display GMT offset 73 display LDAP settings 136 display location 77 display monitoring of event log state 83 display name 77 display network port settings 172 display NTP configuration 164 display open ports 172 display RSA host key information 210 display serial port configuration 170 display service setting 196 display single user 238, 247 display SLP settings 198 display SMTP server host name 199 display SMTP server IP address 199 display SNMP configuration 200 display SSH public key 256 display SSH status 210 display state of -lse option 81 display status 85 Display status of first five CIN entries 68 display syslog configuration 218 display temperature 225 display time 73 display trespass feature status 226 display user interface settings 228 display voltage 262 dns commands 87, 88 example 88 download SSH public key 259 enable automatic configuration 186 enable CIN configuration entry 65 enable CLI SSH server 210 enable command-line interface 228
Index
349
management module (continued) enable complex password 32 enable data encryption 195 enable default administration password expiration 32 enable DNS 87 enable Ethernet channel 0 121 enable Ethernet channel 1 116 enable FTP 176 enable HTTPS port 177 enable monitoring of event log state 82 enable network interface for redundant and allow IP swap 36 enable network interface for redundant and prevent IP swap 36 enable NTP 164, 177 enable password change at first login 33 enable password required 34 enable physical uplink failover 233 enable secure SMASH over SSH 177 enable security 195 enable SMASH over Telnet 177 enable SMASH SSH server 210 enable SNMP agent (SNMPv1) 200 enable SNMP agent (SNMPv3) 200 enable SNMP traps 178, 200 enable SNMPv1 228 enable SNMPv1 agent 178 enable SNMPv3 228 enable SNMPv3 agent 178 enable SSH port 178 enable TCP command mode 178, 228 enable technician debug 196 enable Telnet port 179 enable TFTP 179 enable trespass feature 226 enable V3 authentication for NTP 164 enable Web interface 228 Ethernet network settings commands example 116, 126 failover configuration 233, 235 filter alert type 49 generate host key 210 IBM Director communication 220, 222 ifconfig commands 113, 116, 118, 126 kvm commands 134 ldapcfg command 136, 141 example 141 mt commands 159, 160 network connection 14 physical uplink failover delay 233 portcfg commands 170 ports command 172, 180 example 180 read command 185, 186 example 186 read status table entries CIN read status table entries 68 remotechassis command 187, 188 example 188 remove SSH public key 257
management module (continued) replace SSH public key 258 reset (failover) 190 reset (force failover) 191 reset (primary) 190 reset (standby) 190 reset configuration 69 reset configuration (keep logs) 71 reset network port settings 173 restore configuration from file (encryption) 185 restore configuration from file (no encryption) 185 restore configuration from midplane 185 save configuration to chassis 263 save configuration to file 264 save configuration to file (encryption) 263 save configuration to file (no encryption) 263 save event log to TFTP server 83 security commands 29, 195 serial connection 15, 16 serial port settings commands example 170 service command example 196 service commands 196 set account inactivity alert time 32 set account inactivity disable time 33 set account lockout period 33 set account security default to high 31 set account security default to legacy 30 set alert notification method 49 set alert recipient email address 49 set alert recipient name 48 set alert recipient status 48 set alert type 49 set authentication logging timeout 31 set CIN state for global enable or disable 64 set CLI inactivity timeout 32 set contact name 78 set date 73 set daylight-savings time mode 75 set DNS first IP address 87 set DNS second IP address 87 set DNS third IP address 87 set Ethernet channel 0 configuration method 114, 120 set Ethernet channel 0 data rate 114, 120 set Ethernet channel 0 duplex mode 114, 120 set Ethernet channel 0 gateway IP address 113, 119 set Ethernet channel 0 hostname 114, 119 set Ethernet channel 0 MAC address 115, 120 set Ethernet channel 0 MTU 115, 120 set Ethernet channel 0 static IP address 113, 118 set Ethernet channel 0 subnet mask 113, 119 set Ethernet channel 1 gateway IP address 115 set Ethernet channel 1 MAC address 116 set Ethernet channel 1 static IP address 115 set Ethernet channel 1 subnet mask 116 set first LDAP server host name 137 set first LDAP server IP address 137 set first LDAP server port number 138
350
management module (continued) set FTP data port number 173 set FTP port number 173 set FTP timeout 179 set GMT offset 74 set hostname for alerts 50 set HTTP port number 173 set HTTPS port number 174 set IP address 113, 118 set IP address for alerts 50 set KVM port number 174 set LDAP client distinguished name 139 set LDAP client distinguished name password 139 set LDAP client distinguished name password (confirm) 140 set LDAP group filter 140 set LDAP group search attribute 140 set LDAP login permission attribute 141 set LDAP name 136 set LDAP root distinguished name 138 set LDAP security version 136 set LDAP server binding method 139 set LDAP server discovery method 136 set LDAP server domain source 137 set LDAP server search domain 137 set LDAP server service name 137 set LDAP UID search attribute 139 set location 77 set maximum LDAP sessions for user 33 set maximum number of login failures 33 set maximum number of simultaneous sessions for user 254 set minimum number of different characters for password 32 set name 77 set NTP server hostname 164 set NTP server IP address 164 set NTP server key 165 set NTP update frequency 164 set password expiration time 33 set password minimum change interval 34 set password reuse cycle 34 set privacy password (SNMPv3) 244, 255 set remote disk on card port number 174 set remote disk port number 174 set SDSP port number 175 set second LDAP server host name 137 set second LDAP server IP address 137 set second LDAP server port number 138 set serial port baud rate 170 set serial port communication rate 170 set serial port parity 170 set serial port stop bits 170 set server host name 199 set server IP address 199 set SLP address type 198 set SLP multicast address 198 set SLP port number 175 set SMASH Telnet port number 175 set SNMP agent port number 175 set SNMP community 1 first host name 201
management module (continued) set SNMP community 1 first host name - get 201 set SNMP community 1 first host name to set 201 set SNMP community 1 IP address (first host) 201 set SNMP community 1 IP address (first host) to get 201 set SNMP community 1 IP address (first host) to set 201 set SNMP community 1 IP address (second host) 201 set SNMP community 1 IP address (third host) 201 set SNMP community 1 name 200 set SNMP community 1 second host name 201 set SNMP community 1 third host name 201 set SNMP community 1 view type (SNMPv3) 202 set SNMP community 2 first host name 202 set SNMP community 2 IP address (first host) 202 set SNMP community 2 IP address (second host) 202 set SNMP community 2 IP address (third host) 202 set SNMP community 2 name 202 set SNMP community 2 second host name 202 set SNMP community 2 third host name 202 set SNMP community 2 view type (SNMPv3) 202 set SNMP community 3 first host name 203 set SNMP community 3 IP address (first host) 203 set SNMP community 3 IP address (second host) 203 set SNMP community 3 IP address (third host) 203 set SNMP community 3 name 203 set SNMP community 3 second host name 203 set SNMP community 3 third host name 203 set SNMP community 3 view type (SNMPv3) 203 set SNMP contact name 203 set SNMP location 203 set SNMP traps port number 175 set SSH port number 176 set state for KVM port 177 set syslog event log collector 1 IP address 218 set syslog event log collector 1 port number 219 set syslog event log collector 2 IP address 219 set syslog event log collector 2 port number 219 set syslog filter level 218 set TCP command mode port number 176 set TCP command-mode timeout 179 set Telnet port number 176 set Telnet port timeout 180 set TFTP port number 176 set third LDAP server host name 138 set third LDAP server IP address 138 set third LDAP server port number 138 set time 73 set trespass feature message 226 set tsyslog event log collector 1 host name 218 set tsyslog event log collector 2 host name 219 set user access type (SNMPv3) 245, 255 set user authentication method 31 set user authentication protocol (SNMPv3) 244, 254 set user authority level 242, 243, 252, 253 set user context name (SNMPv3) 243, 254 set user hostname (SNMPv3 traps) 245, 256
Index
351
management module (continued) set user IP address (SNMPv3 traps) 245, 256 set user name 241, 250 set user password 241, 250 set user privacy protocol (SNMPv3) 244, 255 set Web interface inactivity timeout 34 slp command 198 example 198 smtp commands 199 SMTP settings commands example 199 snmp commands 200, 204 SNMP settings commands example 204 SSH connection 17 sshcfg command 210, 211 example 211 SSL certificate status 212 SSL status 212 synchronize with NTP server 165 telnet configuration 224 telnet timeout 224 terminate user session 247 trespass command 226 example 226 turn TCP command mode on or off 179 uplink configuration 233, 235 upload SSH public key 258 view configuration 146 view power management policy 168 write command 263, 264 example 264 management module (advanced) disable logical uplink failover 236 disable physical uplink failover 235 enable logical uplink failover 236 enable physical uplink failover 235 logical uplink failover delay 236 logical uplink failover IP address 236 physical uplink failover delay 235 management module (primary) display Ethernet channel 0 configuration 118 reset 190 management module (standby) display Ethernet channel 0 configuration 118 reset 190 set Ethernet channel 0 hostname 119 set Ethernet channel 0 MAC address 121 set Ethernet channel 0 static IP address 119 set IP address 119 management module event log commands 27 management module failover commands 233, 235 management module telnet configuration commands example 224 management module uplink failover commands example 233, 236 management module Web server generate CSR 214 generate self-signed certificate 213 management module, user accounts 238, 247 management-module firmware 2
maximum LDAP sessions for user set for management module 33 maximum number of login failures set for management module 33 media tray command target 92 display owner 159 display temperature 225 set owner 159 media tray temperature display 100 media tray, display power trending 101 memory commands 27 microprocessor command target 91 minimum number of different characters for password set for management module 32 modactlog 148 modactlog command errors 295 modactlog commands 148 example 148 module (blade server) display activity 148 display information 148 monalerts 149 options ca 149 cb 149 ccd 150 ccsm 150 ciom 149, 150, 152 cpm 150 ec 149 ia 151 ib 151 icd 153 icsm 152 iel 152 iinv 152 iiom 151 inc 152 ipm 153 ipon 152 iua 152 wa 150 wb 150 wcd 151 wcsm 151 wel 151 wiom 150 wpm 151 monalerts command errors 295 monalerts commands 149 example 153 monalertsleg 154 options bt 157 ca 154 ct 155 cv 155 ec 154 el 157
352
monalertsleg (continued) options (continued) elf 156 hdd 154 ic 155 inv 157 kmsf 156 mccdf 154 miomf 154 nc 157 pf 155 pfa 157 pm 157 poff 157 pon 156 rl 158 rmf 156 sa 156 sccdf 155 vf 155 wa 155 wt 156 wv 156 monalertsleg command errors 295 monalertsleg commands 154 example 158 monitoring disable for all critical alerts 149 disable for all critical legacy alerts 154 disable for all informational alerts 151 disable for all system legacy alerts 156 disable for all warning alerts 150 disable for all warning legacy alerts 155 disable for blade device critical alerts 149 disable for blade device informational alerts 151 disable for blade device warning alerts 150 disable for blade server throttled system legacy alerts 157 disable for chassis critical alerts 150 disable for chassis informational alerts 152 disable for chassis warning alerts 151 disable for cooling device critical alerts 150 disable for cooling device informational alerts 153 disable for cooling device warning alerts 151 disable for critical temperature legacy alerts 155 disable for critical voltage legacy alerts 155 disable for event log full system legacy alerts 157 disable for event log full warning legacy alerts 156 disable for event log informational alerts 152 disable for event log warning alerts 151 disable for hard disk drive critical legacy alerts 154 disable for I/O module critical alerts 149 disable for I/O module informational alerts 151 disable for I/O module warning alerts 150 disable for invalid configuration critical legacy alerts 155 disable for inventory change informational alerts 152 disable for inventory system legacy alerts 157 disable for KVM/media tray switching failure warning legacy alerts 156
monitoring (continued) disable for multiple chassis cooling device critical legacy alerts 154 disable for multiple I/O-module failure critical legacy alerts 154 disable for network change informational alerts 152 disable for network change system legacy alerts 157 disable for power failure critical legacy alerts 155 disable for power management system legacy alerts 157 disable for power module critical alerts 150 disable for power module informational alerts 153 disable for power module warning alerts 151 disable for power off system legacy alerts 157 disable for power on system legacy alerts 156 disable for power state informational alerts 152 disable for predictive failure analysis system legacy alerts 157 disable for redundant module failure warning legacy alerts 156 disable for remote login system legacy alerts 158 disable for single chassis cooling device warning legacy alerts 155 disable for storage module critical alerts 149 disable for storage module informational alerts 152 disable for storage module warning alerts 150 disable for system management critical alerts 150 disable for system management informational alerts 152 disable for system management warning alerts 151 disable for user activity informational alerts 152 disable for VRM failure critical legacy alerts 155 disable for warning temperature legacy alerts 156 disable for warning voltage legacy alerts 156 enable for all critical alerts 149 enable for all critical legacy alerts 154 enable for all informational alerts 151 enable for all system legacy alerts 156 enable for all warning alerts 150 enable for all warning legacy alerts 155 enable for blade device critical alerts 149 enable for blade device informational alerts 151 enable for blade device warning alerts 150 enable for blade server throttled system legacy alerts 157 enable for chassis critical alerts 150 enable for chassis informational alerts 152 enable for chassis warning alerts 151 enable for cooling device critical alerts 150 enable for cooling device informational alerts 153 enable for cooling device warning alerts 151 enable for critical temperature legacy alerts 155 enable for critical voltage legacy alerts 155 enable for event log full system legacy alerts 157 enable for event log full warning legacy alerts 156 enable for event log informational alerts 152 enable for event log warning alerts 151 enable for hard disk drive critical legacy alerts 154 enable for I/O module critical alerts 149 enable for I/O module informational alerts 151
Index
353
monitoring (continued) enable for I/O module warning alerts 150 enable for invalid configuration critical legacy alerts 155 enable for inventory change informational alerts 152 enable for inventory system legacy alerts 157 enable for KVM/media tray switching failure warning legacy alerts 156 enable for multiple chassis cooling device critical legacy alerts 154 enable for multiple I/O-module failure critical legacy alerts 154 enable for network change informational alerts 152 enable for network change system legacy alerts 157 enable for power failure critical legacy alerts 155 enable for power management system legacy alerts 157 enable for power module critical alerts 150 enable for power module informational alerts 153 enable for power module warning alerts 151 enable for power off system legacy alerts 157 enable for power on system legacy alerts 156 enable for power state informational alerts 152 enable for predictive failure analysis system legacy alerts 157 enable for redundant module failure warning legacy alerts 156 enable for remote login system legacy alerts 158 enable for single chassis cooling device warning legacy alerts 155 enable for storage module critical alerts 149 enable for storage module informational alerts 152 enable for storage module warning alerts 150 enable for system management critical alerts 150 enable for system management informational alerts 152 enable for system management warning alerts 151 enable for user activity informational alerts 152 enable for VRM failure critical legacy alerts 155 enable for warning temperature legacy alerts 156 enable for warning voltage legacy alerts 156 mt 159 options b 159 local 159 remote 159 mt command errors 296 mt commands 159 example 160 MTU set for channel 0 of management module 115, 120 multiple video sessions disable for blade server 124 enable for blade servers 124 multiplexer expansion module command target 93 reset (failover) 190
N
name display BladeCenter units on network filtered by 188 display for blade server 77 display for management module 77 set for blade server 77 set for management module 77 name (contact) set for management module 78 nat 161 options activate 161 en 162 ep 162 ip 162 pi 162 pn 161 reset 161 nat command 161 example 163 nat command errors 296 NAT external port number set for I/O module 162 NAT internal port number set for I/O module 162 NAT protocol ID set for I/O module 162 NAT protocol name set for I/O module 161 NAT table disable for I/O module 162 enable for I/O module 162 network card display configuration information 122 network clock module command target 93 power off 181 power on 181 turn off 181 turn on 181 network configuration status display for blade server 122 network interface disable for redundant management module 36 enable for redundant management module and allow IP swap during failover 36 enable for redundant management module and prevent IP swap during failover 36 network port settings display for management module 172 reset for management module 173 network protocol settings activate for I/O module 161 display for I/O module 161 reset for I/O module 161 network settings display for BladeCenter unit 124 display for I/O module 125 notes, important 324 notices 323
354
notification method, set for alerts 49 ntp 164 options en, disabled 164 en, enabled 164 f 164 i 164 synch 165 v3 165 v3en, disabled 165 v3en, enabled 164 NTP disable for management module 164, 177 enable for management module 164, 177 ntp command 164 example 165 ntp command errors 296 NTP configuration display for management module 164 NTP server synchronize management module clock 165 NTP server hostname set for management module 164 NTP server IP address set for management module 164 NTP server key set for management module 165 NTP update frequency set for management module 164
O
online documentation 1 open ports display for management module 172 options a 68 f 68 out-of-band communication, IBM Director 220, 222 override persistent command environment 5
P
parity set for serial port of management module password change for user 251 LDAP distinguished name 139 password (confirm) LDAP distinguished name 140 password expiration time set for management module 33 password minimum change interval set for management module 34 password reuse cycle set for management module 34 persistent command environment override 5 persistent command target 4 ping 166 I/O module 166 170
ping command errors 297 ping commands 166 example 166 pmpolicy 167 options -pm 167, 168 acred 167 acredov 167 nonred 168 pd 167 pdx 167 redwoperf 168 redwperf 168 view for management module 168 pmpolicy command example 168 pmpolicy command errors 297 polling interval, set for power trending 101 portcfg options com1 170 com1, b 170 com1, p 170 com1, s 170 portcfg command errors 297 portcfg commands 170 example 170 ports 172 options -kvme, state 177 ftpdp 173 ftpe, off 177 ftpe, on 176 ftpp 173 ftpt 179 httpp 173 httpse, off 177 httpse, on 177 httpsp 174 kvmp 174 ntpe, off 177 ntpe, on 177 open 172 rdocp 174 rdp 174 reset 173 slpp 175 smashse, off 177 smashse, on 177 smashsp 175 smashte, off 177 smashte, on 177 smashtp 175 snmp1ae, off 178 snmp1ae, on 178 snmp3ae, off 178 snmp3ae, on 178 snmpap 175 snmpte, off 178 snmpte, on 178 snmptp 175
Index
355
ports (continued) options (continued) sshe, off 178 sshe, on 178 sshp 176 tcme, off 178 tcme, on 178 tcme, port mode 179 tcmp 176 tcmt 179 telnete, off 179 telnete, on 179 telnetp 176 telnett 180 tftpe, off 179 tftpe, on 179 tftpp 176 ports (open) display for management module 172 ports command 172 example 180 ports command errors 297 POST status display for I/O module 183 display for switch module 183 power options cycle 182 cycle, c 182 fp 183 local 182, 183 off 181 on 181 on, c 181 softoff 181 state 182 state, post 183 wol 182 power capping, enable for blade server 102 power capping, set for blade server 102 power command errors 298 power commands 181 example 184 power control commands 28 power domain disable acoustic mode 102 disable quiet mode 97 enable acoustic mode 102 enable quiet mode 97 power domain information display (detailed) 96, 100 power domain information display (overview) 96, 99 power domain redundancy loss policy, set 96, 100 power domain, display power trending 101 power management commands 28 power management, enable for blade server 102, 103 power module command target 92 power off alarm panel module 181 blade server 181, 182 I/O module 181
power off (continued) network clock module 181 switch module 181, 182 power on alarm panel module 181 blade server 181, 182 I/O module 181, 182 network clock module 181 switch module 181, 182 power on (to console) blade server 181, 182 power polling interval, set 101 power saver mode, enable for blade server 103 power state display for blade server 182 display for I/O module 182 display for switch module 182 power trending, display (blade server) 101 power trending, display (blower) 101 power trending, display (I/O module) 101 power trending, display (power domain) 101 power trending, display (system) 101 primary management module 5 protected mode disable for I/O module 126 enable for I/O module 126
Q
quiet mode, disable 97 quiet mode, enable 97
R
read 185 options config 185 config, auto, off 186 config, auto, on 186 config, l , i 185 config, l , i, p 185 read CIN configuration status table entries management module 68 read CIN status table entries for management module 68 read command 185 example 186 read command errors 299 redirect command 23, 89 redundancy loss policy, power domain (set) 96, 100 redundant management modules 5 reload all information 130 reload firmware information 130 reload hardware information 130 reload MAC address information 130 reload MAC addresses information 130 reload WNN information 130 remote alert set retry interval 44 set retry limit 44
356
remote disk on card port number set for management module 174 remote disk port number set for management module 174 remote media tray switching disable globally 159 enable globally 159 remotechassis 187 options clear 188 health 187 ip 187 name 188 remotechassis command 187 example 188 remotechassis command errors 300 remove 216, 217 remove SSH public key 257 replace SSH public key 258 required, firmware 2 required, hardware 2 reset 190 blade server 58, 190 I/O module 190 ISMP 190 management module (primary) 190 management module (standby) 190 options c 190 clr 192 ddg 192 dg 192 exd 191 f 190 force 191 full 191 sft 191 standby 190 std 191 service processor 190 switch module 190 reset (clear NVRAM) blade server 192 reset (extended diagnostics) I/O module 191 switch module 191 reset (failover) management module 190 multiplexer expansion module 190 reset (force failover) management module 191 reset (full diagnostics) I/O module 191 switch module 191 reset (run diagnostics with boot sequence) blade server 192 reset (run diagnostics) blade server 192 reset (standard diagnostics) I/O module 191 switch module 191
reset (to console) blade server 58, 190 reset (with NMI) blade server 191 reset blase server key sequence set for SOL 208 reset command 28 reset command errors 300 reset commands 190 example 193 reset configuration I/O module 69, 71 management module 69 switch module 69, 71 reset configuration (keep logs) management module 71 reset default configuration 69, 71 reset network port settings management module 173 reset network protocol settings I/O module 161 responding to thermal events 97, 102 restore configuration management module (from file with encryption) 185 management module (from file with no encryption) 185 management module (from midplane) 185 restore configuration commands 28 restore management module configuration command example 186 retry count set for SOL 206 retry interval set for remote alerts 44 set for SOL 206 retry limit set for remote alerts 44 revert to old IP address configuration after reset I/O module 125 RSA host key information display for management module 210
S
SAS zone activate for I/O module 265 SAS zone information display for I/O module 265 SAS zone list display for I/O module 265 save configuration commands 28 save configuration to chassis management module 263 save configuration to file management module 264 save configuration to file (encryption) management module 263 save configuration to file (no encryption) management module 263 save event log to TFTP server management module 83
Index
357
save management module configuration command example 264 save service information save to TFTP server 85 sddump options init 194 sddump command errors 301 sddump commands 194 example 194 SDSP port number set for management module 175 secure command-line interface 15 Secure Shell connection clients 15 secure shell server disabling 18 Secure Shell server exit codes (CLI) 19 using 17 secure SMASH enabling 18 secure SMASH over SSH disable for management module 177 enable for management module 177 security 15, 195 disable complex password for management module user authentication 32 disable default administration password expiration for management module 32 disable password change at first login to management module 33 disable password required for management module 34 display management module account settings 29 display management module setting 195 enable complex password for management module user authentication 32 enable default administration password expiration for management module 32 enable for management module 195 enable password change at first login to management module 33 enable password required for management module 34 options e 195 set management module account default to high 31 set management module account default to legacy 30 set management module account inactivity alert time 32 set management module account inactivity disable time 33 set management module account lockout period 33 set management module authentication logging timeout 31 set management module CLI inactivity timeout 32 set management module maximum LDAP sessions for user 33 set management module maximum number of login failures 33
security (continued) set management module minimum number of different characters for password 32 set management module password expiration time 33 set management module password minimum change interval 34 set management module password reuse cycle 34 set management module user authentication method 31 set management module Web interface inactivity timeout 34 security command errors 301 security commands 195 account security 29 example 195 selecting command environment 4 selecting command target 4 self-signed certificate generate for LDAP client 213 generate for management module Web server 213 self-signed certificate (SSL) download certificate file 215 import certificate file 215 upload certificate file 215 send threshold set for SOL 206 Serial Over LAN 21 Serial Over LAN commands 205 example 209 serial port baud rate set for management module 170 serial port communication rate set for management module 170 serial port configuration display for management module 170 serial port parity set for management module 170 serial port settings for management module commands example 170 serial port stop bits set for management module 170 server host name set for management module 199 server IP address set for management module 199 service 196 options disable 196 enable 196 service command example 196 service command errors 301 service commands 196 service data display command 85 dump from blade server 194 service information capture 85 display 85 save to TFTP server 85
358
service processor command target 91 reset 190 service setting display for management module 196 session command 28 set date, management module 73 daylight-savings time mode, management module 75 GMT offset, management module 74 TCP command-mode session timeout 220, 222 time, management module 73 set accumulate timeout SOL 206 set alarm 42 set alert notification method 49 set alert recipient email address 49 set alert recipient name 48 set alert recipient status 48 set alert type 49 set boot mode blade server 59 set CIN state for enable management module 64 set CIN state for disable management module 64 set CLI key sequence SOL 208 set command-line timeout management module 224 set contact name management module 78 set DNS first IP address management module 87 set DNS second IP address management module 87 set DNS third IP address management module 87 set Ethernet channel 0 configuration method management module 114, 120 set Ethernet channel 0 data rate management module 114, 120 set Ethernet channel 0 duplex mode management module 114, 120 set Ethernet channel 0 gateway IP address management module 113, 119 set Ethernet channel 0 hostname management module 114, 119 standby management module 119 set Ethernet channel 0 MAC address management module 115, 120 standby management module 121 set Ethernet channel 0 MTU management module 115, 120 set Ethernet channel 0 static IP address management module 113, 118 standby management module 119 set Ethernet channel 0 subnet mask management module 113, 119
set Ethernet channel 1 gateway IP address management module 115 set Ethernet channel 1 MAC address management module 116 set Ethernet channel 1 static IP address management module 115 set Ethernet channel 1 subnet mask management module 116 set Ethernet channel configuration method blade server 123 set Ethernet channel gateway IP address blade server 122 set Ethernet channel static IP address blade server 122 set Ethernet channel subnet mask blade server 123 set Ethernet channel VLAN ID blade server 123 set first LDAP server host name management module 137 set first LDAP server IP address management module 137 set first LDAP server port number management module 138 set FTP data port number management module 173 set FTP port number management module 173 set FTP timeout management module 179 set gateway IP address I/O module 125 set hostname for alerts 50 set HTTP port number management module 173 set HTTPS port number management module 174 set IP address blade server 122 I/O module 125 management module 113, 118 standby management module 119 set IP address for alerts 50 set KVM owner 134 set KVM port number management module 174 set LDAP client distinguished name management module 139 set LDAP client distinguished name password management module 139 set LDAP client distinguished name password (confirm) management module 140 set LDAP group filter management module 140 set LDAP group search attribute management module 140 set LDAP login permission attribute management module 141 set LDAP name management module 136
Index
359
set LDAP security version management module 136 set LDAP server binding method management module 139 set LDAP server discovery method management module 136 set LDAP server domain source management module 137 set LDAP server root distinguished name management module 138 set LDAP server search domain management module 137 set LDAP server service name management module 137 set LDAP UID search attribute management module 139 set location management module 77 set logical uplink failover delay advanced management module 236 management module (advanced) 236 set logical uplink failover IP address advanced management module 236 management module (advanced) 236 set management module account inactivity alert time 32 set management module account inactivity disable time 33 set management module account lockout period 33 set management module account security default high 31 legacy 30 set management module authentication logging timeout 31 set management module CLI inactivity timeout 32 set management module maximum LDAP sessions for user 33 set management module maximum number of login failures 33 set management module minimum number of different characters for password 32 set management module password expiration time 33 set management module password minimum change interval 34 set management module password reuse cycle 34 set management module user authentication method 31 set management module Web interface inactivity timeout 34 set maximum number of simultaneous sessions for user 254 set media tray owner 159 set name blade server 77 management module 77 set NAT external port number I/O module 162 set NAT internal port number I/O module 162 set NAT protocol ID I/O module 162
set NAT protocol name I/O module 161 set NTP server hostname management module 164 set NTP server IP address management module 164 set NTP server key management module 165 set NTP update frequency management module 164 set number of sessions TCP command mode 222 set physical uplink failover delay advanced management module 235 management module 233 management module (advanced) 235 set power capping for blade server 102 set power domain redundancy loss policy 96, 100 set power polling interval 101 set privacy password (SNMPv3) 244, 255 set remote disk on card port number management module 174 set remote disk port number management module 174 set reset blase server key sequence SOL 208 set retry count SOL 206 set retry interval remote alerts 44 SOL 206 set retry limit remote alerts 44 set SDSP port number management module 175 set second LDAP server host name management module 137 set second LDAP server IP address management module 137 set second LDAP server port number management module 138 set send threshold SOL 206 set serial port baud rate management module 170 set serial port communication rate management module 170 set serial port parity management module 170 set serial port stop bits management module 170 set server host name management module 199 set server IP address management module 199 set SLP address type management module 198 set SLP multicast address management module 198 set SLP port number management module 175
360
set SMASH Telnet port number management module 175 set SNMP agent port number management module 175 set SNMP community 1 first host name management module 201 set SNMP community 1 first host name -get management module 201 set SNMP community 1 first host name to set management module 201 set SNMP community 1 IP address (first host) management module 201 set SNMP community 1 IP address (first host) to get management module 201 set SNMP community 1 IP address (first host) to set management module 201 set SNMP community 1 IP address (second host) management module 201 set SNMP community 1 IP address (third host) management module 201 set SNMP community 1 name management module 200 set SNMP community 1 second host name management module 201 set SNMP community 1 third host name management module 201 set SNMP community 1 view type (SNMPv3) management module 202 set SNMP community 2 first host name management module 202 set SNMP community 2 IP address (first host) management module 202 set SNMP community 2 IP address (second host) management module 202 set SNMP community 2 IP address (third host) management module 202 set SNMP community 2 name management module 202 set SNMP community 2 second host name management module 202 set SNMP community 2 third host name management module 202 set SNMP community 2 view type (SNMPv3) management module 202 set SNMP community 3 first host name management module 203 set SNMP community 3 IP address (first host) management module 203 set SNMP community 3 IP address (second host) management module 203 set SNMP community 3 IP address (third host) management module 203 set SNMP community 3 name management module 203 set SNMP community 3 second host name management module 203 set SNMP community 3 third host name management module 203 set SNMP community 3 view type (SNMPv3) management module 203
set SNMP contact name management module 203 set SNMP location management module 203 set SNMP traps port number management module 175 set SSH port number management module 176 set starting BSMP IP address BladeCenter unit 124 set starting IP address blade servers 116, 121, 124 set state for KVM port management module 177 set subnet mask I/O module 126 set syslog event log collector 1 host name management module 218 set syslog event log collector 1 IP address management module 218 set syslog event log collector 1 port number management module 219 set syslog event log collector 2 host name management module 219 set syslog event log collector 2 IP address management module 219 set syslog event log collector 2 port number management module 219 set syslog filter level management module 218 set TCP command mode port number management module 176 set TCP command-mode timeout management module 179 set Telnet port number management module 176 set Telnet port timeout management module 180 set telnet timeout management module 224 set TFTP port number management module 176 set third LDAP server host name management module 138 set third LDAP server IP address management module 138 set third LDAP server port number management module 138 set trespass feature message management module 226 set user access type (SNMPv3) 245, 255 set user authentication protocol (SNMPv3) 244, 254 set user authority level 242, 243, 252, 253 set user context name (SNMPv3) 243, 254 set user hostname (SNMPv3 traps) 245, 256 set user IP address (SNMPv3 traps) 245, 256 set user name 241, 250 set user password 241, 250 set user privacy protocol (SNMPv3) 244, 255 set VLAN ID BladeCenter unit 124
Index
361
set VLAN ID (continued) SOL 207 shutdown blade server 181, 197 options f 197 shutdown command errors 302 shutdown commands 197 example 197 simultaneous sessions set maximum number for user 254 single video session enable for blade server 124 slp 198 options i 198 t 198 SLP address type set for management module 198 slp command 198 example 198 slp command errors 302 SLP multicast address set for management module 198 SLP port number set for management module 175 SLP settings display for management module 198 SMASH (secure) over SSH disable for management module 177 enable for management module 177 SMASH CLP enabling 18 SMASH over Telnet disable for management module 177 enable for management module 177 SMASH SSH server disable for management module 210 enable for management module 210 SMASH Telnet port number set for management module 175 smtp 199 options s 199 smtp command errors 302 smtp commands 199 example 199 SMTP server host name display for management module 199 SMTP server IP address display for management module 199 SMTP settings for management module commands example 199 snmp 200 options -ca1 get -c1i1 0.0.0.0 201 -ca1 set -c1i1 0.0.0.0 201 a, off 200 a, on 200 a3, off 200 a3, on 200
snmp (continued) options (continued) c1 200 c1i1 201 c1i2 201 c1i3 201 c2 202 c2i1 202 c2i2 202 c2i3 202 c3 203 c3i1 203 c3i2 203 c3i3 203 ca1 202 ca2 202 ca3 203 cn 203 l 203 t, off 200 t, on 200 SNMP agent disable for management module (SNMPv1) SNMPv1 200 disable for management module (SNMPv3) SNMPv3 200 enable for management module (SNMPv1) SNMPv1 200 enable for management module (SNMPv3) SNMPv3 200 SNMP agent port number set for management module 175 snmp command errors 303 snmp commands 200 example 204 SNMP community 1 first host name set for management module 201 set to get for management module 201 SNMP community 1 first host name to set set for management module 201 SNMP community 1 IP address (first host) set for management module 201 SNMP community 1 IP address (first host) to get set to get for management module 201 SNMP community 1 IP address (first host) to set set for management module 201 SNMP community 1 IP address (second host) set for management module 201 SNMP community 1 IP address (third host) set for management module 201 SNMP community 1 name set for management module 200 SNMP community 1 second host name set for management module 201 SNMP community 1 third host name set for management module 201 SNMP community 1 view type set for management module (SNMPv3) 202 SNMP community 2 first host name set for management module 202
362
SNMP community 2 IP address (first host) set for management module 202 SNMP community 2 IP address (second host) set for management module 202 SNMP community 2 IP address (third host) set for management module 202 SNMP community 2 name set for management module 202 SNMP community 2 second host name set for management module 202 SNMP community 2 third host name set for management module 202 SNMP community 2 view type set for management module (SNMPv3) 202 SNMP community 3 first host name set for management module 203 SNMP community 3 IP address (first host) set for management module 203 SNMP community 3 IP address (second host) set for management module 203 SNMP community 3 IP address (third host) set for management module 203 SNMP community 3 name set for management module 203 SNMP community 3 second host name set for management module 203 SNMP community 3 third host name set for management module 203 SNMP community 3 view type set for management module (SNMPv3) 203 SNMP configuration display for management module 200 SNMP contact name set for management module 203 SNMP location set for management module 203 SNMP settings for management module commands example 204 SNMP traps disable for management module 178, 200 enable for management module 178, 200 SNMP traps port number set for management module 175 SNMPv1 disable for management module 228 enable for management module 228 SNMPv1 agent disable for management module 178 enable for management module 178 SNMPv3 community 1 view type 202 community 2 view type 202 community 3 view type 203 disable for management module 228 enable for management module 228 privacy password 244, 255 trap receiver IP address or hostname 245, 256 user access type 245, 255 user authentication protocol 244, 254 user context name 243, 254 user privacy protocol 244, 255
SNMPv3 agent disable for management module 178 enable for management module 178 software service and support 322 sol 205 options c 206 e 208 i 206 r 208 s 206 status 206, 207 t 206 v 207 SOL 21, 22, 79 global disable 207 global enable 206, 207 set accumulate timeout 206 set CLI key sequence 208 set reset blase server key sequence 208 set retry count 206 set retry interval 206 set send threshold 206 set VLAN ID 207 status 205 sol command errors 304 sol commands example 209 SOL commands 205 SOL session ending 22, 79 starting 21 Specify ID CIN configuration 66 Specify IP CIN configuration entry 65 SRC record display specific for blade server 85 SRC records display all for blade server 85 SSH disabling 18 SSH clients 15 SSH connection 17 SSH port disable for management module 178 enable for management module 178 SSH port number set for management module 176 SSH public key add 256 SSH public key add (specific) 257 SSH public key comment 260 SSH public key connection 259 SSH public key display 256 SSH public key download 259 SSH public key remove 257 SSH public key replace 258 SSH public key upload 258 SSH status display for management module 210 sshcfg 210
Index
363
sshcfg (continued) options cstatus 210 hk, dsa 210 hk, gen 210 hk, rsa 210 sstatus 210 sshcfg command 210 example 211 sshcfg command errors 305 SSL disable for LDAP client 212 enable for LDAP client 212 SSL certificate (additional) disable for standby management module 212 enable for standby management module 212 SSL certificate status management module 212 SSL CSR download certificate file 215 import certificate file 215 upload certificate file 215 SSL for LDAP client disable 212 enable 212 SSL for management module Web server disable 212 enable 212 SSL for Web server disable for management module 212 enable for management module 212 SSL self-signed certificate download certificate file 215 import certificate file 215 upload certificate file 215 SSL status management module 212 SSL trusted certificate 1 216 download 216 import 216 remove 216 upload 216 SSL trusted certificate 2 216 download 216 import 216 remove 216 upload 216 SSL trusted certificate 3 217 download 217 import 217 remove 217 upload 217 sslcfg 212 options ac 212 c 213, 214 cert 213 cl 213, 214 client 212 cp 213, 214 cpwd 214
sslcfg (continued) options (continued) csr 214 dnld 215 dq 213, 214 ea 213, 214 gn 213, 214 hn 213, 214 i 215, 216, 217 in 213, 214 l 215, 216, 217 on 213, 214 ou 213, 214 s 213, 214 server 212 sp 213, 214 tc1 216 tc2 216 tc3 217 un 214 upld 215 sslcfg command errors 306 sslcfg commands 212 example 217 standby management module disable additional SSL certificate 212 enable additional SSL certificate 212 set Ethernet channel 0 hostname 119 set Ethernet channel 0 MAC address 121 set Ethernet channel 0 static IP address 119 set IP address 119 starting a session using SSH 17 starting a session using Telnet 16 starting an SOL session 21 starting command-line interface 15 static IP address set for channel 0 of management module 113, 118 set for channel 0 of standby management module 119 set for channel 1 of management module 115 set for channel of blade server 122 status display for management module 85 SOL 205 stop bits set for serial port of management module 170 storage expansion unit command target 91 subnet mask set for channel 0 of management module 113, 119 set for channel 1 of management module 116 set for channel of blade server 123 set for I/O module 126 support, web site 321 switch module command target 92 cycle power 182 display POST status 183 display power state 182 power off 181, 182 power on 181, 182
364
switch module (continued) reset 190 reset (extended diagnostics) 191 reset (full diagnostics) 191 reset (standard diagnostics) 191 reset configuration 69, 71 turn off 181, 182 turn on 181, 182 synchronize clock with NTP server management module 165 syntax help 109 syntax help commands example 109 syslog 218 options coll1 218 coll2 218 i1 218 i2 219 p1 219 p2 219 sev 218 syslog command errors 308 syslog commands 218 example 219 syslog configuration display for management module 218 syslog event log collector 1 host name set for management module 218 syslog event log collector 1 IP address set for management module 218 syslog event log collector 1 port number set for management module 219 syslog event log collector 2 host name set for management module 219 syslog event log collector 2 IP address set for management module 219 syslog event log collector 2 port number set for management module 219 syslog event log transmission for collector 1 disable 218 disable for management module 218 enable 218 enable for management module 218 syslog event log transmission for collector 2 disable 218 disable for management module 218 enable 218 enable for management module 218 syslog filter level set for management module 218 system view configuration tree 146 system legacy alerts disable monitoring for all 156 disable monitoring for blade server throttled 157 disable monitoring for event log full 157 disable monitoring for inventory 157 disable monitoring for network change 157 disable monitoring for power management 157 disable monitoring for power off 157
system legacy alerts (continued) disable monitoring for power on 156 disable monitoring for predictive failure analysis 157 disable monitoring for remote login 158 enable monitoring for all 156 enable monitoring for blade server throttled 157 enable monitoring for event log full 157 enable monitoring for inventory 157 enable monitoring for network change 157 enable monitoring for power management 157 enable monitoring for power off 157 enable monitoring for power on 156 enable monitoring for predictive failure analysis 157 enable monitoring for remote login 158 system management command 28 system physical configuration command 146 system power management policy command 167 system, display power trending 101
T
target 23, 89 TCP command mode disable 220, 222 disable for management module 178, 228 enable 220, 222 enable for management module 178, 228 set number of sessions 222 turn TCP command mode on or off for the management module 179 TCP command mode port number set for management module 176 TCP command-mode session status display 220, 222 TCP command-mode session timeout display 220, 222 set 220, 222 TCP command-mode timeout set for management module 179 tcpcmdmode 220, 222 options status, 0 222 status, 1 to 20 222 status, off 220 status, on 220 t 220, 222 tcpcmdmode command errors 308 tcpcmdmode commands 220, 222 example 220, 223 technician debug disable for management module 196 enable for management module 196 telephone numbers 322 telnet configuration display for management module 224 telnet configuration commands 224 Telnet connection 15, 16 Telnet port disable for management module 179 enable for management module 179
Index
365
Telnet port number set for management module 176 Telnet port timeout set for management module 180 telnet timeout display for management module 224 set for management module 224 telnetcfg 224 options t 224 telnetcfg command errors 309 telnetcfg commands 224 example 224 temperature display for blade server 225 display for management module 225 display for media tray 225 temperature display, blower 99 temperature display, media tray 100 temporary command target 5 temps 225 temps command errors 309 temps commands 225 example 225 terminate 247 terminate session 94 terminate user session management module 247 test alert generate 50 test communication I/O module 166 TFTP disable for management module 179 enable for management module 179 TFTP port number set for management module 176 thermal event response 97, 102 thermal trending, display (blower) 101 thermal trending, display (media tray) 101 thres command errors 310 time display for management module 73 set for management module 73 trademarks 323 trespass 226 options tw 226 twe 226 trespass command 226 example 226 trespass command errors 310 trespass feature disable for management module 226 enable for management module 226 trespass feature message set for management module 226 trespass feature status display for management module 226 trusted certificate 1 (SSL) download 216
trusted certificate 1 (SSL) (continued) import 216 remove 216 upload 216 trusted certificate 2 (SSL) download 216 import 216 remove 216 upload 216 trusted certificate 3 (SSL) download 217 import 217 remove 217 upload 217 turn index entries on or off CIN 64 turn index entries on or off for CIN 64 turn off alarm panel module 181 blade server 181, 182 I/O module 181 network clock module 181 switch module 181, 182 turn off LED information 143 turn off location LED 112, 144 turn on alarm panel module 181 blade server 181, 182 I/O module 181, 182 network clock module 181 switch module 181, 182 turn on (to console) blade server 181, 182 turn TCP command mode on or off management module 179
U
uicfg 228 options cli, disabled 228 cli, enabled 228 snmp, disabled 228 snmp, enabled 228 tcm, disabled 228 tcm, enabled 228 web, disabled 228 web, enabled 228 uicfg command errors 310 uicfg commands 228 example 229 update 230 options a 230 i, n 230, 231 update command 230 update command errors 311 update command help 230 update commands example 231
366
update firmware 230 update firmware (verbose) 231 uplink 233, 235 options del 233 dls 236 dps 235 el, disabled 236 el, enabled 236 ep, disabled 235 ep, enabled 235 ip 236 off 233 on 233 uplink command errors 313 uplink commands 233, 235 example 233, 236 uplink configuration display for management module 233, 235 uplink failover (logical) disable for advanced management module 236 disable for management module (advanced) 236 enable for advanced management module 236 enable for management module (advanced) 236 uplink failover (physical) disable for advanced management module 235 disable for management module 233 disable for management module (advanced) 235 enable for advanced management module 235 enable for management module 233 enable for management module (advanced) 235 uplink failover delay (logical) set for advanced management module 236 set for management module (advanced) 236 uplink failover delay (physical) set for advanced management module 235 set for management module 233 set for management module (advanced) 235 uplink failover IP address (logical) set for advanced management module 236 set for management module (advanced) 236 upload 216, 217 upload certificate file SSL CSR 215 SSL self-signed certificate 215 upload SSH public key 258 user authentication method disable complex password 32 enable complex password 32 set for management module 31 user interface configuration 228 example 229 user interface settings display for management module 228 user session 247 users 238, 247 options 1 through 12 238, 247 a 242, 252 ap 244, 254 at 245, 255
users (continued) options (continued) clear 238, 248 cn 243, 254 create (n, p, a, cn, ap, pp, ppw, at, i) 239, 249 curr 247 i 245, 256 ms 254 n 241, 250 op 251 p 241, 250 pk, add 256, 257 pk, af 259 pk, cm 260 pk, dnld 259 pk, e 256 pk, remove 257 pk, upld 258 pp 244, 255 ppw 244, 255 ts 247 users command 238, 247 users command errors 313 users commands example 245, 260 users, change password 251 users, create 239, 240, 249 users, delete 238, 248 users, display (active) 247 users, display (all) 238, 247 users, display (single) 238, 247 users, management module 238, 247 users, set access type (SNMPv3) 245, 255 users, set authentication protocol (SNMPv3) 244, 254 users, set authority level 242, 243, 252, 253 users, set context name (SNMPv3) 243, 254 users, set hostname (SNMPv3 traps) 245, 256 users, set IP address (SNMPv3 traps) 245, 256 users, set maximum number of simultaneous sessions 254 users, set name 241, 250 users, set password 241, 250 users, set privacy password (SNMPv3) 244, 255 users, set privacy protocol (SNMPv3) 244, 255 using Secure Shell server 17 using the command-line interface 3
V
V3 authentication for NTP disable for management module 165 enable for management module 164 view command target 146 VLAN ID disable for blade server Ethernet channel 123 enable for blade server Ethernet channel 123 set for BladeCenter unit 124 set for channel of blade server 123 set for SOL 207
Index
367
voltage display for blade server 262 display for management module volts 262 volts command errors 318 volts commands 262 example 262
262
W
Wake on LAN disable for blade server 182 disable globally 182 enable for blade server 182 enable globally 182 warning alerts disable monitoring for all 150 disable monitoring for blade device 150 disable monitoring for chassis 151 disable monitoring for cooling device 151 disable monitoring for event log 151 disable monitoring for I/O module 150 disable monitoring for power module 151 disable monitoring for single chassis cooling device 155 disable monitoring for storage module 150 disable monitoring for system management 151 enable monitoring for all 150 enable monitoring for blade device 150 enable monitoring for chassis 151 enable monitoring for cooling device 151 enable monitoring for event log 151 enable monitoring for I/O module 150 enable monitoring for power module 151 enable monitoring for storage module 150 enable monitoring for system management 151 warning legacy alerts disable monitoring for all 155 disable monitoring for event log full 156 disable monitoring for KVM/media tray switching failure 156 disable monitoring for redundant module failure 156 disable monitoring for temperature 156 disable monitoring for voltage 156 enable monitoring for all 155 enable monitoring for event log full 156 enable monitoring for KVM/media tray switching failure 156 enable monitoring for redundant module failure 156 enable monitoring for single chassis cooling device 155 enable monitoring for temperature 156 enable monitoring for voltage 156 Web interface disable for management module 228 enable for management module 228 Web interface inactivity timeout set for management module 34 web site publication ordering 321 support 321
web site (continued) support line, telephone numbers WNN information reload 130 write options config 263 config, l ,i 263, 264 write command 263 example 264 write command errors 318
322
Z
zonecfg 265 options activate 265 view 265 zonecfg command errors 319 zonecfg commands 265 example 265
368
Part Number: 44R5231
Printed in USA
(1P) P/N: 44R5231

44 R 5231

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

44 R 5231

Transféré par

Droits d'auteur :

Formats disponibles

IBM BladeCenter Management Module BladeCenter T Management Module Advanced Management Module BladeCenter T Advanced Management Module

Command-Line Interface Reference Guide

Command-Line Interface Reference Guide

Copyright IBM Corp. 2007

IBM BladeCenter: Management Module Command-Line Interface Reference Guide

IBM BladeCenter: Management Module Command-Line Interface Reference Guide

Copyright IBM Corp. 2007

Before you begin

IBM BladeCenter: Management Module Command-Line Interface Reference Guide

Chapter 2. Using the command-line interface

Command-line interface guidelines

Copyright IBM Corp. 2007

Selecting the command target

IBM BladeCenter: Management Module Command-Line Interface Reference Guide

Command targets are specified hierarchically, as shown in the following illustration.

mm[x] switch[x] where x = 1 to 2 where x = 1 to n

Integrated system management processor (service processor) sp

I/O expansion card

Storage expansion unit

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

High-speed expansion card

Concurrent KVM feature card

Double-width blade server mezzanine sb (AMM only)

Management card mgmtcrd (AMM only)

be [x] hsec (AMM only) ckvm (AMM only) where x = 1 to n

Chapter 2. Using the command-line interface

Commands and user authority

IBM BladeCenter: Management Module Command-Line Interface Reference Guide

Table 1. Command authority relationships Authority Chassis Account Management

I/O Module Administration

Chassis Log Management

I/O Module Configuration

Blade Remote Presence

Chapter 2. Using the command-line interface

Table 1. Command authority relationships (continued) Authority Chassis Account Management

I/O Module Administration

Chassis Log Management

IBM BladeCenter: Management Module Command-Line Interface Reference Guide

I/O Module Configuration

Blade Remote Presence

Table 1. Command authority relationships (continued) Authority Chassis Account Management

I/O Module Administration

Chassis Log Management

I/O Module Configuration

Blade Remote Presence

Chapter 2. Using the command-line interface

Table 1. Command authority relationships (continued) Authority Chassis Account Management

I/O Module Administration

Chassis Log Management

IBM BladeCenter: Management Module Command-Line Interface Reference Guide

I/O Module Configuration

Blade Remote Presence

Table 1. Command authority relationships (continued) Authority Chassis Account Management

I/O Module Administration

Chassis Log Management

Command power -on, -off, -softoff, -cycle

I/O Module Configuration

Blade Remote Presence

Chapter 2. Using the command-line interface

Table 1. Command authority relationships (continued) Authority Chassis Account Management

I/O Module Administration

Chassis Log Management