
ERserver
BladeCenter Management Module
User’s Guide

ER s e r v e r
BladeCenter Management Module
User’s Guide

©
US
Note: Before using this information and the product it supports, read the general information in
Appendix B, “Notices,” on page 59.
Fourth Edition (February 2004)
Copyright International Business Machines Corporation 2004. All rights reserved.
Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.

On
MM
©
Contents
Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . .v
Chapter 1. Introducing the BladeCenter management module . . . . . . .1
Management module controls and indicators . . . . . . . . . . . . . .2
Management module input/output connectors . . . . . . . . . . . . . .3
Video connector . . . . . . . . . . . . . . . . . . . . . . . .3
Keyboard connector . . . . . . . . . . . . . . . . . . . . . .4
Mouse connector . . . . . . . . . . . . . . . . . . . . . . .4
Remote management and console Ethernet connector . . . . . . . . . .4
Chapter 2. Configuring the management module and BladeCenter unit . . .5
Setting up the remote connection . . . . . . . . . . . . . . . . . .7
Cabling the Ethernet port . . . . . . . . . . . . . . . . . . . .7
Configuring the management module for remote access . . . . . . . . .8
Communicating with the IBM Director software . . . . . . . . . . . .9
Chapter 3. Using the management-module Web interface . . . . . . . .11
User authority . . . . . . . . . . . . . . . . . . . . . . . . .11
Starting the management-module Web interface . . . . . . . . . . . .12
Management-module Web interface options . . . . . . . . . . . . . .14
Monitors . . . . . . . . . . . . . . . . . . . . . . . . . .14
System Status . . . . . . . . . . . . . . . . . . . . . . .14
Event Log . . . . . . . . . . . . . . . . . . . . . . . . .16
LEDs . . . . . . . . . . . . . . . . . . . . . . . . . .17
Hardware VPD . . . . . . . . . . . . . . . . . . . . . . .18
Firmware VPD . . . . . . . . . . . . . . . . . . . . . . .18
Blade Tasks . . . . . . . . . . . . . . . . . . . . . . . . .19
Power/Restart . . . . . . . . . . . . . . . . . . . . . . .19
Demand . . . . . . . . . . . . . . . . . . . . . . . .20
Remote Control . . . . . . . . . . . . . . . . . . . . . . .20
Firmware Update . . . . . . . . . . . . . . . . . . . . . .22
Configuration . . . . . . . . . . . . . . . . . . . . . . .23
Serial Over LAN . . . . . . . . . . . . . . . . . . . . . .24
I/O Module Tasks . . . . . . . . . . . . . . . . . . . . . . .25
Power/Restart . . . . . . . . . . . . . . . . . . . . . . .25
Management . . . . . . . . . . . . . . . . . . . . . . . .25
Firmware Update . . . . . . . . . . . . . . . . . . . . . .26
Control . . . . . . . . . . . . . . . . . . . . . . . . .26
General Settings . . . . . . . . . . . . . . . . . . . . . .27
Login Profiles . . . . . . . . . . . . . . . . . . . . . . .27
Alerts . . . . . . . . . . . . . . . . . . . . . . . . . .29
Port Assignments . . . . . . . . . . . . . . . . . . . . . .29
Network Interfaces . . . . . . . . . . . . . . . . . . . . .30
Network Protocols . . . . . . . . . . . . . . . . . . . . . .32
Security . . . . . . . . . . . . . . . . . . . . . . . . .33
Configuration File . . . . . . . . . . . . . . . . . . . . . .34
Firmware Update . . . . . . . . . . . . . . . . . . . . . .34
Restore Defaults . . . . . . . . . . . . . . . . . . . . . .34
Restart MM . . . . . . . . . . . . . . . . . . . . . . . .35
Network and security configuration . . . . . . . . . . . . . . . . .35
Configuring SNMP . . . . . . . . . . . . . . . . . . . . . .35
Configuring SMTP . . . . . . . . . . . . . . . . . . . . . . .37
Configuring LDAP . . . . . . . . . . . . . . . . . . . . . . .38
Copyright IBM Corp. 2004
iii

iv
Setting up a client to use the LDAP server . . . . . . . . . . . . .38
Configuring the LDAP client authentication . . . . . . . . . . . . .40
Configuring the LDAP search attributes . . . . . . . . . . . . . .40
Secure Web server and secure LDAP . . . . . . . . . . . . . . .42
Configuring security . . . . . . . . . . . . . . . . . . . . .43
SSL certificate overview . . . . . . . . . . . . . . . . . . .44
SSL server certificate management . . . . . . . . . . . . . . .44
Enabling SSL for the secure Web server . . . . . . . . . . . . .50
SSL client certificate management . . . . . . . . . . . . . . . .50
SSL client trusted certificate management . . . . . . . . . . . . .50
Enabling SSL for the LDAP client . . . . . . . . . . . . . . . .52
Configuring the secure shell server . . . . . . . . . . . . . . . .52
Generating a secure shell server key . . . . . . . . . . . . . . .52
Enabling the secure shell server . . . . . . . . . . . . . . . .53
Using the secure shell server . . . . . . . . . . . . . . . . .54
Using the configuration file . . . . . . . . . . . . . . . . . . . .54
Backing up your current configuration . . . . . . . . . . . . . . .54
Restoring and modifying your ASM configuration . . . . . . . . . . .55
Appendix A. Getting help and technical assistance . . . . . . . . . .57
Before you call . . . . . . . . . . . . . . . . . . . . . . . . .57
Using the documentation . . . . . . . . . . . . . . . . . . . . .57
Getting help and information from the World Wide Web . . . . . . . . . .58
Software service and support . . . . . . . . . . . . . . . . . . .58
Hardware service and support . . . . . . . . . . . . . . . . . . .58
Appendix B. Notices . . . . . . . . . . . . . . . . . . . . . .59
Edition notice . . . . . . . . . . . . . . . . . . . . . . . . .59
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . .60
Important notes . . . . . . . . . . . . . . . . . . . . . . . . .60
Product recycling and disposal . . . . . . . . . . . . . . . . . . .61
Electronic emission notices . . . . . . . . . . . . . . . . . . . .61
Federal Communications Commission (FCC) statement . . . . . . . . .61
Industry Canada Class A emission compliance statement . . . . . . . .62
Australia and New Zealand Class A statement . . . . . . . . . . . .62
United Kingdom telecommunications safety requirement . . . . . . . . .62
European Union EMC Directive conformance statement . . . . . . . . .62
Taiwanese Class A warning statement . . . . . . . . . . . . . . .62
Chinese Class A warning statement . . . . . . . . . . . . . . . .63
Japanese Voluntary Control Council for Interference (VCCI) statement . . .63
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
BladeCenter Management Module: User’s Guide

©
Safety
Before installing this product, read the Safety Information.
Antes de instalar este produto, leia as Informações de Segurança.
Pred instalací tohoto produktu si prectete prírucku bezpecnostních instrukcí.
Læs sikkerhedsforskrifterne, før du installerer dette produkt.
Lees voordat u dit product installeert eerst de veiligheidsvoorschriften.
Ennen kuin asennat tämän tuotteen, lue turvaohjeet kohdasta Safety Information.
Avant d’installer ce produit, lisez les consignes de sécurité.
Vor der Installation dieses Produkts die Sicherheitshinweise lesen.
Prima di installare questo prodotto, leggere le Informazioni sulla Sicurezza.
Copyright IBM Corp. 2004
Les sikkerhetsinformasjonen (Safety Information) før du installerer dette produktet.
Antes de instalar este produto, leia as Informações sobre Segurança.
v

To
v Do
v
v
v
v
v
v
To
To
1.
2.
3.
4.
5.
1.
2.
3.
4.
vi
Antes de instalar este producto, lea la información de seguridad.
Läs säkerhetsinformationen innan du installerar den här produkten.
Statement 1:
DANGER
Electrical
current from power, telephone, and communication cables is
hazardous.
avoid a shock hazard:
not connect or disconnect any cables or perform installation,
maintenance, or reconfiguration of this product during an electrical
storm.
Connect all power cords to a properly wired and grounded electrical
outlet.
Connect to properly wired outlets any equipment that will be attached to
this product.
When possible, use one hand only to connect or disconnect signal
cables.
Never turn on any equipment when there is evidence of fire, water, or
structural damage.
Disconnect the attached power cords, telecommunications systems,
networks, and modems before you open the device covers, unless
instructed otherwise in the installation and configuration procedures.
Connect and disconnect cables as described in the following table when
installing, moving, or opening covers on this product or attached
devices.
Connect:
Turn everything OFF.
First, attach all cables to devices.
Attach signal cables to connectors.
Attach power cords to outlet.
Turn device ON.
BladeCenter Management Module: User’s Guide
Disconnect:
Turn everything OFF.
First, remove power cords from outlet.
Remove signal cables from connectors.
Remove all cables from devices.

a
Statement 8:
CAUTION:
Never remove the cover on a power supply or any part that has the following
label attached.
Hazardous voltage, current, and energy levels are present inside any
component that has this label attached. There are no serviceable parts inside
these components. If you suspect a problem with one of these parts, contact
service technician.
WARNING: Handling the cord on this product or cords associated with accessories
sold with this product, will expose you to lead, a chemical known to the State of
California to cause cancer, and birth defects or other reproductive harm. Wash
hands after handling.
ADVERTENCIA: El contacto con el cable de este producto o con cables de
accesorios que se venden junto con este producto, pueden exponerle al plomo, un
elemento químico que en el estado de California de los Estados Unidos está
considerado como un causante de cancer y de defectos congénitos, además de
otros riesgos reproductivos. Lávese las manos después de usar el producto.
Safety
vii

viii
BladeCenter Management Module: User’s Guide

at
at
©
Chapter 1. Introducing the BladeCenter management module
This Management Module User’s Guide contains information about configuring the
management module and managing components installed in the IBM
BladeCenter
™
unit.
®
ERserver
Your BladeCenter unit comes with one hot-swap management module in
management-module bay 1. You can add an additional management module in
management-module bay 2. Only one of these management modules can be active
one time, functioning as the primary management module; a second
management module, if present, provides redundancy. The secondary management
module remains inactive until it is switched to act as primary.
When two management modules are installed in the BladeCenter unit, both
management modules must always have the same level of firmware, at a level that
supports redundant management module function. This helps ensure a smooth
changeover of control from the active management module to the redundant
management module. The latest level of management-module firmware is available
the IBM Support Web site at http://www.ibm.com/pc/support/.
The management module functions as a service processor and a
keyboard/video/mouse (KVM) multiplexor for all of the blade servers installed in the
BladeCenter unit. It provides the following external connections: keyboard, mouse,
and video, for use by a local console, and one RJ-45 connector for a 10/100 Mbps
Ethernet remote management connection.
The service processor in the management module communicates with the service
processor in each blade server to support features such as: blade server power-on
requests, error and event reporting, KVM requests, and requests to use the
BladeCenter shared media tray (diskette drive, CD-ROM drive, and USB port).
You configure BladeCenter components using the management module, setting
information such as IP addresses. The management module communicates with all
components installed in the BladeCenter unit, detecting their presence or absence,
reporting their status, and sending alerts for error conditions when required.
Copyright IBM Corp. 2004
1

v
v
v
v
v
to
v
2
Management module controls and indicators
Active LED
Power-on LED
Management
module error LED
OK
LINK
TX/RX
Ethernet link
LED
Ethernet activity
LED
IP reset button
IP
Management module LEDs: These LEDs provide status information about the
management module and remote management connection. For additional
information, see the “Light path diagnostics” section in the Hardware Maintenance
Manual and Troubleshooting Guide on the IBM BladeCenter Documentation CD.
Power-on: When this green LED is lit, the management module has power.
Active: When this green LED is lit, it indicates that this management module is
actively controlling the BladeCenter unit.
Note: Only one management module actively controls the BladeCenter unit. If
there are two management modules installed in the BladeCenter unit, this
LED is lit on only one.
Management module error: When this amber LED is lit, it indicates that an
error has been detected somewhere on this management module. When this
indicator is lit, the system error LED on each of the BladeCenter system LED
panels is also lit.
Ethernet link: When this green LED is lit, there is an active connection through
the port to the network.
Ethernet activity: When this green LED is flashing, it indicates that there is
activity through the port over the network link.
Management
module IP reset button: Do not press this button unless you intend
erase your configured IP addresses for the management module and lose
connection with the remote management station, the I/O modules, and the blade
servers. If you press this button, you will need to reconfigure the management
module settings (see the information beginning with “Setting up the remote
connection” on page 7 for instructions). Use a straightened paper clip to press the
recessed button in one of the following sequences to reset management-module
settings:
Press the IP reset button for 3 seconds or less; then, restart the management
module to reset the IP configuration of the management module network
interfaces (Ethernet 1, Ethernet 2, gateway address, and so forth) to the factory
defaults.
BladeCenter Management Module: User’s Guide

v
v
v
v
v
Press the IP reset button for 5 seconds, release it for 5 seconds; then; press it
again for 10 seconds and restart the management module to reset all of the
management-module configuration fields to the factory defaults.
Management module input/output connectors
The management module has the following I/O connectors:
One video
One PS/2
One PS/2 mouse
One 10/100 Mbps Ethernet for remote management and console
The following illustration shows the I/O connectors on the management module.
Remote management
and console (Ethernet)
®
keyboard
OK
LINK
TX/RX
Note: There is no internal connections between the input/output connectors on the
Video connector
Your BladeCenter management module contains one standard video connector. Use
this connector to connect a compatible SVGA or VGA video monitor to the
BladeCenter unit. Blade server integrated video controllers share the
management-module video connector through the BladeCenter KVM interface.
Video
Mouse
Keyboard
management modules when two are installed in the BladeCenter unit. See
the IBM BladeCenter Management Module Installation Guide for information
about how to cable two management modules to support the redundant
management module interface requirements of your installation.
5
1
1115
Chapter 1. Introducing the BladeCenter management module
3

4
Keyboard connector
Your BladeCenter management module contains one PS/2-style keyboard
connector. Use this connector to connect a PS/2 keyboard to the BladeCenter unit.
Blade servers share the management-module keyboard connector through the
BladeCenter KVM interface.
6
4
2
5
3
1
Mouse connector
Your BladeCenter management module contains one PS/2-style mouse connector.
Use this connector to connect a PS/2 mouse to the BladeCenter unit. Blade servers
share the management-module mouse connector through the BladeCenter KVM
interface.
6
4
2
5
3
1
Remote management and console Ethernet connector
Your BladeCenter management module contains one 10/100 Mb Ethernet connector
that provides the remote connection to the network management station on the
network. Use this port to establish connections with the remote management and
remote console features of the BladeCenter unit.
The network management station, through this port, can access control functions
running in the service processor on each blade server or within other components
installed in the BladeCenter unit. The network management station cannot use this
port to communicate with application programs running in the blade servers. The
network management station must direct all application related communications
through a network connected to the external ports of the I/O modules installed in
the BladeCenter unit, which then interface with the blade servers and their
application programs.
The following illustration shows the Ethernet connector that is on the management
module.
8
1
BladeCenter Management Module: User’s Guide

v
v
v
v
©
Chapter 2. Configuring the management module and
BladeCenter unit
Important: You configure only the primary (active) management module. The
secondary management module receives the configuration and status
information automatically from the primary management module when
necessary. The configuration information in this chapter applies to the
primary management module, which might be the only management
module installed in the BladeCenter unit.
When the BladeCenter unit is started initially, it automatically configures the remote
management port on the active (primary) management module, so that you can
configure and manage BladeCenter components. You configure and manage
BladeCenter components remotely using the management-module Web interface or
the management-module command-line interface.
Note: You can also configure the I/O modules directly through an external I/O
module port, using a Telnet interface or a Web browser. See the
documentation that comes with each I/O module for information.
For the management module to communicate with the I/O modules in the
BladeCenter unit, you will need to configure the IP addresses for the following
internal and external ports:
The IP address for the external Ethernet (remote management) port on the
management module (see the information beginning on page 30 for instructions).
The initial automatic configuration of the management module enables the
network management station to connect to the management module to configure
the port completely and to configure the rest of the BladeCenter unit.
The IP address for the internal Ethernet port on the management module (see
the information beginning on page 30 for instructions) to support communication
with the I/O modules.
The IP address for the management port on each I/O module (see the
information beginning on page 25 for instructions) for communication with the
management module. You configure this port by configuring the IP address for
the I/O module.
Note: Some types of I/O modules, such as a pass-thru module, have no
management port.
communicate with the blade servers for functions such as deploying an operating
To
system or application program, you also will need to configure at least one external
(in-band) port on an Ethernet I/O module installed in I/O module bay 1 or 2. See the
Installation and User’s Guide for your BladeCenter unit for general information
about configuring the external ports on Ethernet I/O modules.
Copyright IBM Corp. 2004
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.
The management module supports the following Web browsers for remote access.
The Web browser that you use must be Java™-enabled, must support JavaScript
1.2 or later, and must have the Java 1.4.1 Plug-In installed.
Microsoft
®
Internet Explorer 5.5 (with latest Service Pack installed), or later
™
5

v
1.
to
2.
v
v
v
v
v
v
v
v
v
v
v
6
v
Netscape Navigator 4.72, or later (version 6.x is not supported)
Mozilla version 1.3, or later
Notes:
For best results when using the Web browser, set the resolution on your monitor
800 x 600 pixels or higher and 256 colors.
The Web interface does not support the double-byte character set (DBCS)
languages.
The Web-based user interface communicates with the management-module Web
interface and management-module command-line interface, that are part of the
firmware that comes with the management module, to perform tasks such as:
Defining the login IDs and passwords
Selecting recipients for alert notification of specific events
Monitoring the status of BladeCenter components
Controlling BladeCenter components, including the blade servers
Accessing the I/O modules to configure them
Changing the drive startup sequence for a blade server
Setting the date and time
Using a remote console for the blade servers
Changing ownership of the keyboard, video, and mouse
Changing ownership of the CD-ROM drive, diskette drive, and USB port
Activating On Demand blade servers
Note:
The IBM Director program is a system-management product that comes with
the BladeCenter unit. To configure the remote alert recipients for IBM
Director over LAN, the remote alert recipient must be an IBM
Director-enabled server.
You also can use the management-module Web interface and management-module
command-line interface to view some of the blade server configuration settings. See
Chapter 3, “Using the management-module Web interface,” on page 11 and the IBM
Eserver BladeCenter Management-Module Command-Line Interface Reference
Guide for more information.
BladeCenter Management Module: User’s Guide

To
1.
2.
v
v
Setting up the remote connection
configure and manage BladeCenter components, you must first set up the
remote connection through the external Ethernet port on the management module.
Cabling the Ethernet port
Complete the following steps to connect the Ethernet cable to the management
module:
Connect one end of a Category 5 or higher Ethernet cable to the remote
management and console (Ethernet) connector on the management module.
Connect the other end of the Ethernet cable to the network.
Check the Ethernet LEDs to ensure that the network connection is working.
When the green Ethernet link LED is lit, there is an active connection through
the port to the network.
When the green Ethernet activity LED is flashing, it indicates that there is
activity through the port over the network link.
following illustration shows the locations of the Ethernet LEDs.
The
OK
Ethernet link
LINK
TX/RX
Ethernet activity
IP
Chapter 2. Configuring the management module and BladeCenter unit
7

v If
v If
of
v If
v
8
Configuring the management module for remote access
After you connect the active management module to the network, the Ethernet port
connection is configured in one of the following ways:
you have an accessible, active, and configured dynamic host configuration
protocol (DHCP) server on the network, the host name, IP address, gateway
address, subnet mask, and DNS server IP address are set automatically.
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.
Either
these actions enables the Ethernet connection on the active management
module.
Make sure your computer is on the same subnet as the management module; then,
use your Web browser to connect to the management module (see “Starting the
management-module Web interface” on page 12 for more information). In the
browser Address field, specify the IP address the management module is using:
the IP address was assigned through a DHCP server, get the IP address from
your network administrator.
The factory-defined static IP address is 192.168.70.125, the default subnet
address is 255.255.255.0, and the default host name is MMxxxxxxxxxxxx, where
xxxxxxxxxxxx is the burned-in medium access control (MAC) address. The MAC
address is on a label on the management module, below the IP reset button.
OK
LINK
TX/RX
IP
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 and host name are assigned.
BladeCenter Management Module: User’s Guide
MAC address

To
If
1.
a
2.
on
Communicating with the IBM Director software
The IBM Director program is a system-management product that comes with the
BladeCenter unit. The IBM Director software communicates with the BladeCenter
unit through the Ethernet port on the active management module.
Note: See the IBM Support Web site at http://www.ibm.com/pc/support/ for the
version of IBM Director software that you can use to manage redundant
management modules.
communicate with the BladeCenter unit, the IBM Director software needs a
managed object (in the Group Contents pane of the IBM Director Management
Console main window) that represents the BladeCenter unit. If the BladeCenter
management module IP address is known, the network administrator can create an
IBM Director managed object for the unit. If the IP address is not known, the IBM
Director software can automatically discover the BladeCenter unit (out-of-band,
using the Ethernet port on the BladeCenter management module) and create a
managed object for the unit.
For the IBM Director software to discover the BladeCenter unit, your network must
initially provide connectivity from the IBM Director server to the BladeCenter
management-module Ethernet port. To establish connectivity, the management
module attempts to use DHCP to acquire its initial IP address for the Ethernet port.
the DHCP request fails, the management module uses the static IP address
assigned to it. Therefore, the DHCP server (if used) must be on the management
LAN for your BladeCenter unit.
Notes:
All management modules are preconfigured with the same static IP address.
You can use the management module Web interface to assign a new static IP
address for each BladeCenter unit. If DHCP is not used and you do not assign
new static IP address for each BladeCenter unit before attempting to
communicate with the IBM Director software, only one BladeCenter unit at a
time can be added onto the network for discovery. Adding multiple units to the
network without a unique IP address assignment for each BladeCenter unit
results in IP address conflicts.
For I/O module communication with 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
the same subnet.
Chapter 2. Configuring the management module and BladeCenter unit
9

10
BladeCenter Management Module: User’s Guide

in
v
v
v
v
v
a
or
→
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 v v v
v v v v v v v v v ©
Chapter 3. Using the management-module Web interface
This section provides instructions for using the management-module Web interface
the active (primary) management module. It has sections that describe:
Features of the management-module Web interface that can be accessed by
users, based on their authority level (see “User authority”).
“Starting the management-module Web interface” on page 12.
Descriptions of the management-module Web interface screens (see
“Management-module Web interface options” on page 14).
“Network and security configuration” on page 35.
Backup and restore of the management-module configuration (see “Using the
configuration file” on page 54).
User authority
Some fields and selections in the management-module Web interface screens can
only be changed or executed by users that are assigned a required level of
authority for that window. Viewing information does not require any special
command authority. Users with “Supervisor” command authority can change
information and execute tasks in all windows.
The following table lists the management-module Web interface windows and the
authority levels that are required to change information in these windows. The
windows and authorities listed in this table only apply to changing the information in
window or executing a task specified in a window: viewing the information in a
window does not require any special command authority. In the table, each row
indicates the valid user command authorities that let a user change the information
execute a task in that window. For example, executing tasks in the Blade Tasks
Power/Restart window is available to users with the “Supervisor” authority or to
users with the “Blade and I/O Module Power/Restart Access” authority.
Table 1. User authority relationships
Window
System Status
Event Log (view)
Event Log (clear)
LEDs
Monitors
Hardware VPD
Firmware VPD
Authority required to change information or execute tasks
Supervisor
Blade Server Remote
Console Access
Blade Server Remote Console
and Virtual Media Access
Blade and I/O Module
Power/Restart Access
Ability to Clear Event Logs
Basic Configuration
(MM, I/O Modules, Blades)
Network and Security
Configuration
Advanced Configuration
(MM, I/O Modules, Blades)
User Account Management
Copyright IBM Corp. 2004
11

v v On
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 v v
v v v
v v v
v v
v v
v v
v v
1.
12
Table 1. User authority relationships (continued)
Authority required to change information or execute tasks
Window
Blade Tasks
Tasks
I/O Module
MM Control
Power/Restart
Demand
Remote Control
(remote console)
Remote Control
(virtual media)
Firmware Update
Configuration
Serial over LAN
Power/Restart
Management
Firmware Update
General Settings
Login Profiles
Alerts
Port Assignments
Network Interfaces
Network Protocols
Security
Configuration File
Firmware Update
Restore Defaults
Restart MM
Supervisor
Blade Server Remote
Console Access
Blade Server Remote Console
and Virtual Media Access
Blade and I/O Module
Power/Restart Access
Ability to Clear Event Logs
Basic Configuration
(MM, I/O Modules, Blades)
Network and Security
Configuration
Advanced Configuration
(MM, I/O Modules, Blades)
User Account Management
Starting the management-module Web interface
Complete the following steps to start the management-module Web interface
program:
Open a Web browser. In the address or URL field, type the IP address or host
name assigned for the management-module remote connection (see
“Configuring the management module for remote access” on page 8 for more
details).
BladeCenter Management Module: User’s Guide

2.
v
v
In
The Enter Network Password window opens.
Type your user name and password. If you are logging in to the management
module for the first time, you can obtain your user name and password from
your system administrator. All login attempts are documented in the event log.
Note: The initial factory-defined user ID and password for the management
module are:
User ID: USERID (all capital letters)
Password: PASSW0RD (note the zero, not O, in PASSW0RD)
Follow the instructions that appear on the screen. Be sure to set the timeout
3.
value you want for your Web session.
BladeCenter management-module Web interface window opens.
The
Note: The upper left corner of the management-module Web interface window
shows the location and identity of the active (primary) management module.
the following example, the primary management module is identified as
“SN#” and is installed in management-module bay1.
Chapter 3. Using the management-module Web interface
13

of
? )
of
v
14
Management-module Web interface options
From the management-module Web interface is a management and configuration
program that lets you select the BladeCenter settings that you want to view or
change.
The navigation pane (on the left side of the management-module Web interface
window) contains navigational links that you use to manage your BladeCenter unit
and check the status of the components (modules and blade servers). Descriptions
the links that are in the navigation pane are described in the sections that follow.
Online help is provided for the management-module Web interface. Click the help (
icon next to a section or choice to display additional information about this item.
Monitors
Use the choices in the Monitors section to view the status, settings, and other
information for components in the BladeCenter unit.
System Status
Select the System Status choice to view the overall system status, a list of
outstanding events that require immediate attention, and the overall status of each
the blade servers and other components installed in your BladeCenter unit.
Blade Servers:
Bay - The lowest-number bay the blade server occupies.
BladeCenter Management Module: User’s Guide