IBM 26R0881 User manual

IBM Systems
IBM BladeCenter Open Fabric Manager
Installation and User's Guide
Version 2.1


IBM Systems
IBM BladeCenter Open Fabric Manager
Installation and User's Guide
Version 2.1


Note
Before using this information and the product it supports, read the information in “Notices &
Trademarks” on page 55.
This edition applies to version 2.1 of IBM BladeCenter Open Fabric Manager and to all subsequent releases and
modifications until otherwise indicated in new editions.
©Copyright International Business Machines Corporation 2007, 2008. All rights reserved.
US Government Users Restricted Rights –Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.

Contents
Tables ...............v
Who should read this user’s guide .. vii
Conventions and terminology .....ix
Chapter 1. IBM BladeCenter Open Fabric
Manager ..............1
Chapter 2. Planning for BladeCenter
Open Fabric Manager .........3
Hardware and software requirements ......3
Supported hardware ...........3
Supported software ...........5
Preparing for OFM ............6
Upgrading firmware...........6
Setting up boot from SAN ........10
Chapter 3. Installing BladeCenter Open
Fabric Manager ...........11
Installing OFM .............11
Installing OFM-Advanced upgrade ......11
Installing the IBM Director extension version of
OFM-Advanced upgrade for Windows ....11
Installing the OFM-Advanced upgrade
standalone version for Windows ......12
Installing the IBM Director extension version of
OFM-Advanced upgrade for Linux .....12
Installing the OFM-Advanced upgrade
standalone version for Linux .......12
Chapter 4. Configuring BladeCenter
Open Fabric Manager ........15
Creating aconfiguration file automatically ....15
Selecting domains ...........17
Avoiding address duplication .......18
Creating arequirements report ........19
Creating arequirements report from ″The
Configuration File Has Been Created″page in the
AMM Web interface ..........19
Creating arequirements report from the main
Open Fabric Manager Configuration
Management page on the AMM Web interface..19
Editing the configuration file manually .....19
Applying anew configuration ........20
Viewing the configuration in alocal chassis ...20
Retrieving the current configuration ......21
Chapter 5. Using OFM and
OFM-Advanced upgrade .......23
Using OFM ..............23
Initial deployment ...........23
Adding anew chassis to the domain .....23
Replacing ablade in the same slot......23
Swapping addresses between blades .....24
Replacing AMM IP addresses .......24
Replacing the AMM in asingle AMM
environment .............24
Using OFM-Advanced upgrade........25
Discovering achassis ..........25
Creating ablade address profile ......26
Applying ablade address profile ......28
Creating astandby blade pool profile.....28
Applying afailover configuration profile
manually ..............29
Comparing the configuration file with the actual
configuration .............29
Creating an event action plan .......30
Chapter 6. Troubleshooting and
support ..............31
Problems when you create or apply astandby blade
pool .................31
Incorrect OFM address usage ........32
Configuration failure scenarios ........32
Error messages .............34
Getting help and support..........36
Finding information about IBM Director
Problems ..............37
Information to provide to the IBM Technical
Support Center or IBM Director customer forum .39
Getting fixes .............41
Software service and support .......41
Chapter 7. Reference ........43
BladeCenter Open Fabric Manager components ..43
Configuration file ...........43
AMM Web interface ..........49
Accessibility ..............49
Session and credentials ..........50
Standby AMM .............50
CLI command .............51
Events ................51
Chapter 8. Related information ....53
Notices &Trademarks ........55
Notices ................55
Trademarks .............56
Glossary ..............59
Terms ................59
Index ...............61
©Copyright IBM Corp. 2007, 2008 iii

iv IBM BladeCenter Open Fabric Manager Installation and User's Guide

Tables
1. Expansion cards that support OFM .....3
2. BladeCenter chassis’ that support OFM ...3
3. BladeCenter servers that support OFM ....4
4. Fibre channels switches that support OFM 4
5. Ethernet switches that support OFM ....4
6. Pass-thru modules and switches that support
OFM ...............5
7. Supported software -OFM-Advanced upgrade 6
8. BladeScanner and ChassisUpdate log file
locations ..............8
9. Blade address configuration creation and
application problems .........31
10. Standby blade pool creation and application
problems .............31
11. Parsing errors ............35
12. ................48
©Copyright IBM Corp. 2007, 2008 v

vi IBM BladeCenter Open Fabric Manager Installation and User's Guide

Who should read this user’s guide
This user’s guide is for system administrators and operators using OFM™from
IBM®Director or the Advanced Management Module (AMM) to replace and
recover blades in their environment.
©Copyright IBM Corp. 2007, 2008 vii

viii IBM BladeCenter Open Fabric Manager Installation and User's Guide

Conventions and terminology
These notices are designed to highlight key information:
Note: These notices provide important tips, guidance or advice.
Important: These notices provide information or advice that might help you avoid
inconvenient or difficult situations.
CAUTION:
These notices indicate possible damage to programs, devices or data. An
attention notice appears before the instruction or situation in which damage can
occur.
©Copyright IBM Corp. 2007, 2008 ix

xIBM BladeCenter Open Fabric Manager Installation and User's Guide

Chapter 1. IBM BladeCenter Open Fabric Manager
IBM BladeCenter®Open Fabric Manager (OFM) is asolution that enables you to
quickly replace and recover blades in your environment.
It does this by assigning Ethernet MAC and Fibre Channel WWN addresses to the
BladeCenter slots in such away that any blades plugged into those slots will take
on the assigned addresses. This enables the Ethernet and Fibre Channel
infrastructure to be configured once and before any blades are connected to the
BladeCenter chassis. BladeCenter Open Fabric Manager-Advanced upgrade adds
capabilities to monitor blades for failure events and to take automatic action to
failover from afaulty blade to acold standby blade. The Ethernet MAC and Fibre
Channel WWN addresses are moved from the faulty blade’s slot to the standby
blade’s slot and the standby blade is automatically powered on. In aboot from
SAN environment, the operating system and software that was once running on
the faulty blade is now running on the standby blade.
There are two separate offerings of BladeCenter Open Fabric Manager. The main
BladeCenter Open Fabric Manager function is provided in the OFM offering.
Additional capabilities are available with the OFM-Advanced upgrade offering.
OFM
With BladeCenter Open Fabric Manager, you can pre-assign MAC and WWN
addresses, as well as storage boot targets, for up to 100 chassis or 1400 blade
servers. Using the management module Web interface, you can create addresses for
blade servers, save the addresses to aconfiguration file, deploy the addresses to
the blade slots in the same chassis or in up to 100 different chassis. This can be
done without any blade servers installed in the chassis.
OFM-Advanced upgrade
With BladeCenter Open Fabric Manager-Advanced upgrade, you can monitor the
health of blade servers and automatically -without user intervention -replace a
failed blade from adesignated pool of spare blades. After receiving afailure alert,
OFM-Advanced upgrade attempts to power off the failing blade, read the
BladeCenter Open Fabric Manager virtualized addresses and boot target
parameters, apply these parameters to the next blade in the standby blade pool,
and power on the standby blade.
You can also pre-assign MAC and WWN addresses, as well as storage boot targets,
for up to 100 chassis or 1400 blade servers with BladeCenter Open Fabric
Manager-Advanced upgrade. Using an enhanced graphical user interface, you can
create addresses for blade servers, save the addresses profiles; deploy the addresses
to the blade slots in the same chassis or in up to 100 different chassis. This can be
done without any blade servers installed in the chassis. Additionally, you can
create profiles for chassis that have not been installed in the environment by
simply associating an IP address to the future chassis.
BladeCenter Open Fabric Manager-Advanced upgrade is available as astandalone
offering or as an extension to IBM Director. The standalone version includes an
embedded version of IBM Director.
©Copyright IBM Corp. 2007, 2008 1

Important: OFM is aprerequisite of OFM-Advanced upgrade
2IBM BladeCenter Open Fabric Manager Installation and User's Guide

Chapter 2. Planning for BladeCenter Open Fabric Manager
Planning involves understanding the hardware and software requirements for
OFM and OFM-Advanced upgrade and preparing for OFM.
Hardware and software requirements
There are minimum hardware and software requirements the system must meet
before you can install or use OFM and OFM-Advanced upgrade.
Supported hardware
The following hardware supports OFM and OFM-Advanced upgrade.
Expansion cards
Table 1. Expansion cards that support OFM
Expansion card Firmware version
HS/LS blades JS blades
QLogic 4Gb SFF Fibre Channel
Expansion Card (26R0890)
Muti-boot v1.43 or later Muti-boot v1.46 or later
QLogic 4Gb Fibre Channel
Expansion Card (CFFv) for IBM
BladeCenter (41Y8527)
1.43 or later v1.46 or later
QLogic Ethernet and 4Gb Fibre
Channel Expansion Card (CFFh)
for IBM BladeCenter (39Y9306)
1.43 or later v1.46 or later
Emulex 4Gb SFF Fibre Channel
Expansion Card (39Y9186)
6.02a2 or later 6.02a7 or later
Emulex 4Gb Fibre Channel
Expansion Card (CFFv) for IBM
BladeCenter (43W6859)
6.02a2 or later 6.02a7 or later
IBM SFF Gb Ethernet Expansion
Card (39R8624)
Any version Any version
Ethernet Expansion Card (CFFv)
for IBM BladeCenter (39Y9310)
Any version Any version
NetXen 10 Gb Ethernet
Expansion Card for IBM
BladeCenter (39Y9271)
3.4.223 3.4.223
Note: JS22 cannot host NetXen 10 Gb Ethernet Expansion Card for IBM
BladeCenter (39Y9271).
BladeCenter chassis’
Table 2. BladeCenter chassis’ that support OFM
BladeCenter chassis Firmware version
HS/LS blades JS blades
BladeCenter E(8677) AMM 4.0 (BPET42C) or later AMM 4.0 (BPET42D) or later
BladeCenter E(8677) AMM 4.0 (BPET42C) or later AMM 4.0 (BPET42D) or later
BladeCenter HT (8740/8750) AMM 4.0 (BPET42C) or later AMM 4.0 (BPET42D) or later
BladeCenter S(8886) AMM 4.0 (BPET42C) or later AMM 4.0 (BPET42D) or later
©Copyright IBM Corp. 2007, 2008 3

BladeCenter servers
Table 3. BladeCenter servers that support OFM
BladeCenter server BIOS version BMC version NIC version
IBM BladeCenter HS21
(8853)
BCE128A or later BCBT42BUS or later See “Expansion cards”
on page 3.
IBM BladeCenter HS21
XM (7995)
MJE119A or later MJBT18AUS or later See “Expansion cards”
on page 3.
IBM BladeCenter LS21
(7971)
BAE139AUS or later BABT42AUS or later See “Expansion cards”
on page 3.
IBM BladeCenter LS41
(7972)
BAE139AUS or later BABT42AUS or later See “Expansion cards”
on page 3.
IBM BladeCenter
JS22/JS12 (7998)
eFW 3.3 or later eFW 3.3 or later See “Expansion cards”
on page 3.
IBM BladeCenter HS12
(8014)
N1E125A N1BT07AUS See “Expansion cards”
on page 3.
IBM BladeCenter HS12
(8028)
N1E125A N1BT07AUS See “Expansion cards”
on page 3.
Fibre channels
Table 4. Fibre channels switches that support OFM
Fibre channel switch Firmware version
Brocade Entry SAN Switch Module for IBM
BladeCenter (26K5601)
Any version
Brocade Enterprise SAN Switch Module for IBM
BladeCenter (90P0165)
Any version
Brocade 10-port SAN Switch Module for IBM
eServer™BladeCenter (32R1813)
Any version
Brocade 20-port SAN Switch Module for IBM
eServer BladeCenter (32R1812)
Any version
Qlogic 6pt Fibre Channel Switch Module
(26K6477)
Any version
QLogic 10-port Fibre Channel Switch Module for
IBM eServer BladeCenter (32R1904)
Any version
QLogic 20-port Fibre Channel Switch Module for
IBM eServer BladeCenter (26R0881)
Any version
QLogic 4Gb FC 10-port Full Fabric Switch
(43W6724)
Any version
QLogic 4Gb FC 20-port Full Fabric Switch
(43W6725)
Any version
QLogic 4Gb FC 20-port Pass-thru Switch
(43W6723)
Any version
Cisco Systems 4Gb 10 port Fibre Channel Switch
Module for IBM BladeCenter (39Y9284)
Any version
Cisco Systems 4Gb 20 port Fibre Channel Switch
Module for IBM BladeCenter (39Y9280)
Any version
Ethernet switches
Table 5. Ethernet switches that support OFM
Network Firmware version
Cisco Catalyst Switch Module 3012 for IBM
BladeCenter (43W4395)
Any version
4IBM BladeCenter Open Fabric Manager Installation and User's Guide

Table 5. Ethernet switches that support OFM (continued)
Network Firmware version
Cisco Catalyst Switch Module 3110G and 3110X
for IBM BladeCenter (41Y8523 &41Y8522)
Any version
Cisco Systems Gigabit Ethernet Switch Module for
eServer BladeCenter (13N2281)
Any version
Cisco Systems Intelligent Gigabit Fiber Ethernet
Switch Module for IBM eServer BladeCenter
(26K6547)
Any version
Cisco Systems Intelligent Gigabit Ethernet Switch
Module for IBM BladeCenter (32R1892)
Any version
Cisco Systems Fiber Intelligent Gigabit Ethernet
Switch Module for IBM BladeCenter (32R1888)
Any version
Nortel Networks L2/L3 Copper Gigabit Ethernet
Switch Module for IBM eServer BladeCenter
(26K6530)
Any version
Nortel Networks L2/L3 Fiber Gigabit Ethernet
Switch Module for IBM eServer BladeCenter
(26K6531)
Any version
Nortel Layer 2/3 Copper Ethernet Switch Module
for IBM BladeCenter (32R1860)
Any version
Nortel Layer 2/3 Fiber Ethernet Switch Module
for IBM BladeCenter (32R1861)
Any version
Nortel Layer 2-7 Gigabit Ethernet Switch Module
for IBM BladeCenter (32R1859)
Any version
Nortel Networks (TM) Layer 2-7Gigabit
Ethernet Switch Module for IBM eServer
BladeCenter (73P9057)
Any version
Nortel 10 Gb Ethernet Switch Module for IBM
eServer BladeCenter (32R1783)
Any version
IBM Server Switch Module (39Y9324) Any version
Pass-thru modules and switches
Table 6. Pass-thru modules and switches that support OFM
Passthru Firmware version
IBM BladeCenter Optical Pass-thru Module
(02R9080)
Any version
IBM BladeCenter Optical Pass-thru Module
(39Y9316)
Any version
Copper Pass-thru Module Option (39Y9320) Any version
Copper Pass-thru Module Option (73P6100) Any version
InfiniBand Passa-thru Module for IBM
BladeCenter (43W4419)
Any version
Intelligent Copper Pass-Thru Module for IBM
BladeCenter (44W4483)
Any version
QLogic 4Gb FC 20-port Pass-thru Switch
(43W6723)
Any version
Supported software
OFM-Advanced upgrade is supported on selected Microsoft®Windows®and
Linux®operating systems on x86 architecture. OFM is supported on any operating
system supported by the blade.
Chapter 2. Planning 5

Table 7. Supported software -OFM-Advanced upgrade
Operating System
Microsoft Virtual Server 2005
Microsoft Windows 2003 (SP1, SP2, R2)
Microsoft Windows 2000 (Up to SP4)
RHEL 3(32-bit only; up to SP9)
RHEL 4(up to SP6)
RHEL 5with Xen 3.0 (up to SP1)
SLES 9(up to SP4)
SLES 10 with Xen 3.0 (up to SP1)
Preparing for OFM
In order to prepare your environment for OFM, you will need to upgrade the
firmware of the AMMs and blades, including the BMC, BIOS, and additional
expansion cards in your environment. In addition, optimum use of OFM requires
that you setup your blade environment to boot from SAN.
Important: UXSPs simplify the updating of all of your firmware. However, before
you can upgrade your firmware on Emulex and Qlogic drivers, you
must ensure that these fiber channel cards are already installed and
operating properly. If you are not using UXSPs, follow the instructions
in “Steps to update firmware without an OS” on page 8.
Upgrading firmware
Before you can use OFM, you must first update the firmware of the BladeCenter
and blades, including BMC, BIOS, and additional expansion cards in your
environment.
For alist of the latest firmware ,see: Software and device drivers -IBM
BladeCenter
Steps to update AMM firmware using the AMM Web interface
1. Login to the AMM Web interface and select Firmware Update on the left pane,
under MM Control.The Update MM Firmware page will open in the right
pane.
2. On the Update MM Firmware page, click Browse to find the AMM flash file.
3. Aseparate Choose file window will open. Select the AMM flash file and click
Open.The AMM flash file will appear in the field next to the Browse button
on the Update MM Firmware page.
4. Click Update button on the Update MM Firmware page and wait for the
firmware to be uploaded to the AMM. If there is astandby MM installed, the
firmware on the standby MM will automatically update to the same level.
5. Click Continue to actually perform the flash.
6. Once the flashing is complete, you must reboot the AMM.
On reboot, the new firmware will be active and the standby AMM firmware will
be automatically updated.
6IBM BladeCenter Open Fabric Manager Installation and User's Guide

Steps to update AMM firmware using UpdateXpress for
BladeCenter (UXBC)
1. Download Python interpreter, version 2.3 or later at http://www.python.org.
The UXBC uses the Python update scripts to update the firmware of the
applicable systems. To run the Python scripts, you must install Python
interpreter on the administrative system.
Note: Python also comes with most Linux distributions.
2. Download the latest UpdateXpress CD2 at IBM System xSupport Web site
(www.ibm.com/servers/eserver/support/xseries/index.html).
3. Go to the Software and device drivers -IBM BladeCenter Web site
(http://www-304.ibm.com/jct01004c/systems/support/supportsite.wss/
docdisplay?lndocid=MIGR-63017&brandind=5000020) (www.ibm.com/servers/
eserver/support/xseries/index.html). Select your blade type from the list. This
action directs you to apage for your blade type. Click Mangement Module,
which takes you to the Management Module section of the page. You can then
select from alist of available AMM firmware updates. After you download the
package, you must unzip the package and save it to the applicable server or
network location for distribution to target systems.
4. To save the firmware updates for aBladeCenter management module, complete
the following steps:
a. Copy the firmware update package to anetwork directory that you can
access from the administrative console.
Note: Do not unzip the firmware update package in the
\BladeCenterUpdates directory. Each firmware update package
includes areadme file. If you unzip the package in the
\BladeCenterUpdates directory, the UXBC readme file is replaced
with the update package readme file.
b. Make anote of the directory path. This information is used to create the
response file when BladeScanner is run.
Steps to update AMM firmware using BladeScanner and ChassisUpdate:
1. Use Bladescanner to create aresponse file.
Note: Running ChassisUpdate with the -s (scan) switch (with valid
Management Module login credentials) will also create adefault
response file.
2. Make sure that you have the file name and directory location of the response
file that you want to use.
3. In the MM section of the response file, set the paths of the AMM firmware
updates and make sure mmdisable is set to false.
### MANDATORY Fields ###
#These fields must be specified.
#This is amandatory field that specifies the dotted IP
#address of the BladeCenter Management Module.
mmipaddr=192.168.70.125
#### OPTIONAL Fields ###
#These fields may be necessary depending on the BladeCenter configuration.
#This is amandatory field that specifies the username for the
#BladeCenter Management Module.
mmuser=UX2
#This is an optional field that contains the password of the specified
#username for the BladeCenter Management Module. If not specified, an
#empty password will be supplied to the Management Module.
mmpass=nIKH7P!,
Chapter 2. Planning 7

#This field is mandatory if you intend to update the Management Module. If
#not overridden, the default paths are used.
mmFilename1=\\server\share\AMMFirmware\BPETXXX.TKT
#mmFilename2=FILE2
#mmFilename3=FILE3
#This is an optional field that disables the update of the BladeCenter
#Management Module. If not specified, or specified as FALSE, the
#Management Module is updated.
mmdisable=FALSE
#This is an optional field that is used for informational purposes by
#BladeScanner. BladeScanner in scan mode detects the firmware revision of
#the MM and stores it in this field. BladeScanner in edit mode reads the MM
#firmware revision from this field and displays it on the UI.
#The update scripts ignore this field.
mmMainAppFirmwareRevision=BRET86L
mmMainAppRevisionNum=16
#mmBootRomFirmwareRevision=
#mmBootRomRevisionNum=
#mmRemoteControlFirmwareRevision=
#mmRemoteRevisionNum=
mmPS2toUSBFirmwareRevision=BREZ15
mmMMtoUSBFirmwareRevision=BRPI33
mmName=MM00096BCA2328
4. From acommand-line prompt, change to the disk drive that contains the
UpdateXpress for BladeCenter utilities.
5. Type the following command to run the ChassisUpdate utility:
chassisupdate.py -r file
where, file is the fully qualified file name of the response file that you want to
use. The ChassisUpdate utility reads the parameter from the response file and
updates the applicable systems.
BladeScanner and ChassisUpdate record the transactions that they perform in a
single log file. The log file is created in the following directories:
Table 8. BladeScanner and ChassisUpdate log file locations
Windows Linux
%TEMP%\uxbc.log
where %TEMP% is the temporary directory
for the Windows operating system.
$HOME/uxbc.log
Information is appended to the uxbc.log file each time you run BladeScanner or
ChassisUpdate. As abest practice, you should periodically delete this file.
Steps to update firmware without an OS
The use of UXSPs requires that you have an OS running on the blade. If you do
not have an OS on your blade, you can follow these steps to upgrade your
firmware.
Steps to update blade BMC firmware:
1. Download the boot image (BMC update diskette) of the latest version of the
BMC firmware for your system from the Software and device drivers -IBM
BladeCenter Web site (http://www-304.ibm.com/jct01004c/systems/support/
supportsite.wss/docdisplay?lndocid=MIGR-63017&brandind=5000020). Select
your blade type from the list. This action directs you to apage for your blade
type. Click Baseboard Management Controller,which takes you to the
Baseboard Management Controller section of the page. You can then select from
alist of available boot images. The boot image (BMC update diskette) will have
afile extension of img.
8IBM BladeCenter Open Fabric Manager Installation and User's Guide