Transitioning To UEFI and IBM

Whitepaper
Life Without DOS

Transitioning to UEFI and IMM
Written By: System x

Version: 1.0
Last Revised: 03/17/09
System x Transitioning to UEFI and IMM
Page 2 of 50 Whitepaper
Table of Contents
1 INTRODUCTION......................................................................................................................................................3
1.1 WHAT IS CHANGING?.................................................................................................................................................3
1.2 DOCUMENT OVERVIEW..............................................................................................................................................3
1.3 DOCUMENT CONTRIBUTORS........................................................................................................................................5
2 DEFINITIONS AND ABBREVIATIONS................................................................................................................6
3 SUPPORTED SYSTEMS AND COMPATIBILITY...............................................................................................8
3.1 UEFI AWARE OPERATING SYSTEMS............................................................................................................................8
3.2 IBM UEFI AND IMM BLADES AND SERVERS............................................................................................................8
4 DOS BASED TOOLS OVERVIEW.........................................................................................................................9
4.1 CONFIGURATION........................................................................................................................................................9
4.2 DEPLOYMENT.........................................................................................................................................................11
4.3 UPDATES...............................................................................................................................................................11
4.4 MANAGEMENT........................................................................................................................................................12
5 CONFIGURATION.................................................................................................................................................14
5.1 CONFIGURING BIOS/UEFI SETTINGS......................................................................................................................14
5.2 CONFIGURING BMC/IMM BMC SETTINGS.............................................................................................................18
5.3 CONFIGURING RSA II/IMM SP SETTINGS................................................................................................................20
5.4 CONFIGURING STORAGE SUBSYSTEM..........................................................................................................................22
5.5 CONFIGURING SYSTEM VIA PXE BOOTING.................................................................................................................25
6 DEPLOYMENT.......................................................................................................................................................29
6.1 DEPLOYING AN OS USING SERVERGUIDE SCRIPTING TOOLKITS....................................................................................29
7 UPDATES.................................................................................................................................................................32
7.1 BOOTABLE MEDIA..................................................................................................................................................32
7.2 INDIVIDUAL UPDATES..............................................................................................................................................35
7.3 REMOTE BOOTING..................................................................................................................................................38
8 MANAGEMENT.....................................................................................................................................................40
8.1 BMC AND RSA II................................................................................................................................................40
8.2 IMM...................................................................................................................................................................42
1 Introduction
1.1 What is changing?
The Unified Extensible Firmware Interface (UEFI) replacing legacy BIOS is System x’s new
interface between operating systems and platform firmware. UEFI provides a modern, well
defined environment for booting an operating system and running pre-boot applications.
Unified Extensible Firmware Interface improvements over legacy BIOS:
•Advanced Settings Utility (ASU) will now have more complete coverage of system settings.
•On rack mount servers, UEFI Settings can be accessed Out of Band via ASU and the
Integrated Management Module (not available on Blades).
•Adapter configuration can move into F1 Setup, for example iSCSI Configuration is now in
F1 Setup and consolidated in to ASU
•Elimination of Beep Codes – All Errors covered by Lightpath
•DOS tools are no longer required or officially supported
The Integrated Management Module (IMM) service processor provides competitive, standards
based systems management enabling upward integration into wide variety of enterprise
management environments "out of the box".
Integrated Management Module provides RSA II functionality and Remote Presence in addition to the
following new functions:
• Standard CIM and WS-Man interfaces
• OS drivers included in Windows and Linux, no additional device drivers needed
• Single firmware image for IMM across the product set
• Choice of dedicated or shared Ethernet connections
1.2 Document Overview

The main purpose of this document is to introduce our new toolset and help our clients transition
away from using DOS based processes. Our new toolset offers a simplified, consolidated set of
tools which eliminate the need for DOS-based utilities. The new tools support configuration and
updates from Windows, Linux and VMware ESX operating systems, and support deployment
using Linux or WinPE preboot environments. The tools can either be used online (under a
running OS) or in an offline, bootable environment.
Diagnostics Updates Deployment Configuration

Dynamic System UpdateXpress ServerGuide, ASU, BladeCenter
Analysis (DSA) System Packs Scripting Toolkits Start Now Asst
Bootable Media Creator Online, runnable
This document identifies the current DOS based tools that IBM has provided for existing Intel
Architecture servers, what they are used for, and what tools will be used to replace them. As you
read this document, you will see that IBM is not taking this transition lightly and we are
providing new tools as well as enhancing existing tools to make sure that everything that could
be done previously from DOS can be done on our new systems that no longer support DOS. In
addition, you will find that, for many tasks and environments, the transition should be seamless.
Hence this document is targeted at customers using such tools, typically for the the following
task categories: Updates, Configuration, Deployment and Management. As such this document
considers these tasks and customers should use this document to evaluate their processes and
decide whether or not they need to plan for and/or make changes.
In order to keep the document short and to the point, we purposely do not go into detailed usage
of the tools in this document. Instead we have focused on typical usage scenarios and providing
sample commands and steps for accomplishing those tasks. Items such as configuring a PXE
server, creating a DOS bootable diskette, creating a WinPE environment, installing the tools (if
required), etc. are beyond the scope of this document. For documentation of and links for our
tools, please visit the ToolsCenter Web site either by clicking this link or using the URL:
https://www.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=TOOL-
CENTER&brandind=5000016.
It is also worth noting that most of the tools we are providing for this transition are backwards
compatible meaning that they will function on our previous systems as well as our new systems.
This will allow our customers to use the same set of tools regardless of what IBM system they
need to manage.
While the main focus of this document is migrating away from DOS tools, we will also cover
additional items such as how managing our new IMM based systems will be different in a good
way. For example, with our previous systems, a USB daemon was required to access the RSA II
from under the operating system. With our new IMM based systems, the USB and IPMI device
drivers are included in the distros.
1.3 Document Contributors

• Carlos Santana
• Chuck Weber
• Fabiano Matassa
• Gregory Pruett
• Jason Brunson
• Josh Blumert
• Khalid Ansari
• Mike Nolterieke
• Rick Luciano
• Saleem Akhtar
2 Definitions and Abbreviations

Name and Abbreviation Definition
AMM (Advanced Management Follow-on product and replacement for Management
Module) Module, or MM1, in a Blade Chassis
ASU (Advanced Settings Utility) Utility used to configure BIOS, BMC, and RSA II settings
BIOS (Basic Input/Output The low level I/O interface that supports the system during
System) system initialization and startup and provides access to I/O
devices
BMC (Baseboard Management A hardware device in a system that provides hardware
Controller) management both in-band and out-of-band
ITBoMC (IBM ToolsCenter Utility used to create bootable media that contains IBM tools
Bootable Media Creator)
CIM (Common Information An open standard that defines how managed elements are
Model) represented as a common set of objects
CLI (Command Line Interface) A text-only interface that requires keyboard inputs
cKVM (Concurrent Keyboard, Adapter or functionality that provides concurrent access to
Video, Mouse) remote Keyboard, Video, and Mouse
DOS (Disk Operating System) Single-user, single-task operating system
DSA (Dynamic System Analysis) IBM’s diagnostic and information gathering tool
IMM (Integrated Management The next generation of BMC that integrates BMC and RSA
Module) II functionality on the same chip
In-Band The path of execution on system processor running a
functional operating system
OS (Operating System) or NOS Software that runs on a system that serves as the interface
(Network Operating System) between the hardware and applications providing access to
hardware resources such as the CPU, Memory, and I/O
Devices
Out-of-Band (OOB) The path of server execution running asynchronously to the
system processor and functional operating system
PXE (Preboot Execution An industry standard environment that supports booting the
Environment) system over the network for the purposes of maintenance
and/or system deployment
RDM (Remote Deployment An IBM Director plug-in used to deploy remote systems
Manager)
RSA II (Remote Supervisor The second generation option card for servers that provide
Adapter) advanced remote management such as remote presence and
virtual media functionality
SAN (Storage Area Network) Architecture to attach remote computer storage devices to
servers
SGTK (ServerGuide Scripting A collection of tools used to configure and deploy servers
Toolkit)
SLP (Service Location Protocol) A service discovery protocol that allows computers and other
devices to find services in a local area network without prior
configuration
SP (Service Processor) An embedded processor for advanced functions above those
provided by the BMC such as a Web interface, remote KVM,
and virtual media
TPMfOSD (Tivoli Provisioning RDM follow-on
Manager for OS Deployment)
UEFI (Universal Extensible A specification that defines a software interface between an
Firmware Interface) operating system and platform firmware
UX (UpdateXpress) A physical DOS based CD used to update firmware and
device drivers
UXSP (UpdateXpress System A bundle of Firmware and Device Driver updates packaged
Packs) together per system type and per operating system version
that are known to all work together
UXSPI (UpdateXpress System The tool used to acquire and install UXSPs
Pack Installer)
WinPE (Windows Preinstallation A lightweight version of Windows XP, Windows
Environment) Server 2003 or Windows Vista that is used for
the deployment of workstations and servers
3 Supported Systems and Compatibility

3.1 UEFI Aware Operating Systems
Not all operating systems are UEFI aware, meaning they do not have support for UEFI and
therefore cannot take advantage of UEFI interfaces such as runtime services.
3.1.1 Windows
At the writing of this document, Windows 2008 x64 is the only released operating
system that is UEFI aware.
3.1.2 Linux
At the writing of this document, there are no released Linux operating systems that
are UEFI aware. RedHat and SUSE UEFI aware operating systems are expected later
in 2009.
3.2 IBM UEFI and IMM Blades and Servers

IBM will start releasing Blades and Servers in early 2009 that have UEFI and IMM. Below is
the list of these systems as of the writing of this document, however, this document applies to
any other systems that IBM releases in the future that have UEFI and IMM.
 HS22 7870 Blade Server

The new HS22 combines unprecedented x86 performance, pay as you grow scalability,
and enhanced mission-critical availability to deliver the industry’s leading 64-bit solution
from enterprise workloads, web serving, to server virtualization, all in a 30mm design.
 x3650 M2 7947 2U Rack Mount Server

The IBM x3650 M2 server is a superior 2U, 2P business critical application server
delivering exceptional power-optimized performance, leadership virtualization and a “no
compromise” feature list for commercial and virtualized workloads.
 x3550 M2 7946 1U Rack Mount Server

The IBM x3550 M2 server is an exceptional 1U rack dense, dual socket business critical
application server delivering power-optimized performance and balanced functionality
for mid-tier and LE commercial and virtualized workloads.
4 DOS Based Tools Overview

This section gives an overview of our current DOS based tools, the function they perform, the
supported Operating Systems for the tool, and whether or not the tool will work on the new
UEFI/IMM based systems. Note that some DOS based tools specific to older systems are not
included.
The actual usage of the tools and their replacements are described in the remaining sections.
Note that not all the tools described in this section are used in the remaining sections. They are
listed here only for completeness.
4.1 Configuration
4.1.1 ACU/ACUSAS/ACUICHSV/ACUACHI/RAIDSEL
Description: Configures ServeRAID controllers
Supported OS’: DOS only
Works on UEFI/IMM Systems: N/A – controller not used on newer systems
Replacement Tool(s): ServerGuide Scripting Toolkit, WinPE and Linux editions
(contain pRAID which packages all individual RAID
configuration tools, including ARCCONF, HRCONF)
4.1.2 ASU (Advanced Settings Utility)

Description: Configures BIOS, BMC, and RSA II settings
Supported OS’: DOS (BIOS only), Windows, Linux
Works on UEFI/IMM Systems: Yes – non-DOS versions
Replacement Tool(s): ServerGuide Scripting Toolkit includes the new ASU 3.0.0,
(which is supported on Windows, WinPE, Linux, and VMware
ESX)
4.1.3 BMC_CFG
Description: Configures BMC settings, providing raw access to IPMI commands
Supported OS’: DOS only
Works on UEFI/IMM Systems: No
Replacement Tool(s): ServerGuide ServerGuide Scripting Toolkit, WinPE and Linux
editions (contain ASU 3.0.0), Open Source ipmitool (included in
Linux distributions)
4.1.4 CFG1030
Description: Configures LSI SCSI controllers
Supported OS’: DOS, Windows, Linux
Replacement Tool(s): N/A – controller not used on newer systems
4.1.5 CFGGEN
Description: Configures IBM and LSI Integrated controllers
configuration tools, including CFGGEN)
4.1.6 CMOSUTIL
Description: Saves and restores the entire BIOS configuration
Supported OS’: DOS
(contain ASU 3.0.0)
4.1.7 DOSLPCFG
Description: Configures Emulex adapters
Replacement Tool(s): WINLPCFG for Windows, LINLPCFG for Linux
4.1.8 FASUTIL
Description: Configures QLogic adapters
Replacement Tool(s): sCLI – Also included in ServerGuide Scripting Toolkit, WinPE
and Linux editions
4.1.9 IPSSEND
Description: Configures ServeRAID controllers prior to version 8 (ServeRAID 6m, 7k,
etc.)
configuration tools, including ipssend)
4.1.10MegaCLI
Description: Configures SAS/SATA LSI MegaRAID controllers (ServeRAID 10)

configuration tools, including MegaCLI)
4.2 Deployment
4.2.1 Altiris DS
Description: Altiris Deployment Solution is a 3rd party product for remotely deploying
systems via PXE
Supported Preboot Environments: DOS, WinPE, Linux
Works on UEFI/IMM Systems: Yes – via ServerGuide WinPE and Linux Scripting
Toolkits
Replacement Tool(s): Altiris DS 6.9 with ServerGuide Scripting Toolkit (WinPE and
Linux Editions) preboot environments.
4.2.2 Remote Deployment Manager

Description: IBM Director plug-in for remotely deploying operating systems via PXE.
RDM can also be used for configuration tasks.
Supported Preboot Environments: DOS
Works on UEFI/IMM Systems: No, product is end-of-life, support will not be
extended to these new systems.
Replacement Tool(s): Tivoli Provisioning Manager for OS Deployment (TPMfOSD),
ServerGuide Scripting Toolkits for WinPE, Linux, SGTK
integration with Altiris DS, Microsoft SCCM OS Deployment
(OSD) Pack
4.2.3 ServerGuide Scripting Toolkit for DOS (SGTK)

Description: Collection of DOS based tools and sample scripts to deploy systems.
SGTK can also be used for configuration tasks. Selected WinPE and
Linux utilities were also included.
Supported Preboot Environments: DOS only in general (selected WinPE & Linux
utilities included)
4.3 Updates
4.3.1 DOS Based Diskette Images

Description: Individual diskette and ISO images used to flash firmware such as BIOS,
BMC, and Diagnostics
Supported OS’: DOS Only
Supported on UEFI/IMM Systems: No
Replacement Tool(s): UpdateXpress System Packs (UXSPs), individual on-line update
packages, bootable media created by ITBoMC
4.3.2 DOSLPCFG
Description: Updates Emulex adapters
packages, bootable media created by BoMC
4.3.3 MegaCLI
Description: Flashes firmware of IBM and LSI MegaRAID controllers
4.3.4 SASFlash
Description: Flashes firmware of IBM and LSI Integrated SAS controllers
Supported on UEFI/IMM Systems: Yes – non-DOS versions
4.3.5 UpdateXpress CD
Description: Bootable DOS based CD that updates all of the firmware in the systems
Supported on UEFI/IMM Systems: No, product is end-of-life. Support will not be
extended to these new systems.
Replacement Tool(s): Bootable media created by UXSPI or ITBoMC
4.4 Management
4.4.1 PC Doctor
Description: Bootable DOS based CD that runs system diagnostics
Supported on UEFI/IMM Systems: No
Replacement Tool(s): Preboot Dynamic Systems Analysis (pDSA), embedded in
firmware on new systems and bootable via pressing F2 during
POST; online DSA, bootable media created by ITBoMC.
5 Configuration
In this section we describe and walk through some typical scenarios used to configure the system
in preparation for operating system deployment. We will cover how those tasks are commonly
performed today with DOS based tools and how the same tasks will be performed on our new
UEFI/IMM based systems.
5.1 Configuring BIOS/UEFI Settings

5.1.1 DOS Methods (Replaced by ServerGuide Scripting Toolkit, WinPE
and Linux Editions)
5.1.1.1 DOS ASU

IBM provided a DOS version of ASU to configure systems with legacy BIOS.
To accomplish this, you would create a bootable diskette that contains PC-DOS
7.0 and the DOS version of ASU. You would then boot that diskette on the
system and run ASU commands individually or create a batch file that runs
several commands in succession. Below are sample ASU commands used for
some of the most common configuration tasks.
Device Configuration Commands:

• asu set CMOS_NumLock “Off”
• asu set CMOS_FloppyRequired “Enabled”
• asu set CMOS_DisketteController “Enabled”
Error Handling Configuration:

• asu set CMOS_StopOnError “Enabled”
• asu set CMOS_PostBootFailRequired “Enabled”
SOL (Serial Over LAN) Configuration:

• asu set CMOS_SerialB “Auto-configuration”
• asu set CMOS_SerialA “Auto-configuration”
• asu set CMOS_RemoteConsoleEnable “Enabled”
• asu set CMOS_RemoteConsoleComPort “COM 1”
• asu set CMOS_RemoteConsoleBaud “19200”
• asu set CMOS_RemoteConsoleDataBits “8”
• asu set CMOS_RemoteConsoleParity “None”
• asu set CMOS_RemoteConsoleStopBits “1”
• asu set CMOS_RemoteConsoleEmulation “ANSI”
• asu set CMOS_RemoteConsoleKybdEmul “ANSI”
• asu set CMOS_RemoteConsoleBootEnable “enabled”

• asu set CMOS_RemoteConsoleFlowCtrl “Hardware”
• asu set CMOS_BMCSerialConfig “Dedicated”
• asu set CMOS_BMCSerialShareConfig “Enabled”
Boot Sequence Configuration:

• asu set CMOS_PrimaryBootDevice1 “Diskette Drive 0”
• asu set CMOS_PrimaryBootDevice2 “CD Rom”
• asu set CMOS_PrimaryBootDevice3 “Hard Disk 0”
• asu set CMOS_PrimaryBootDevice4 “Network”
Configuring Booting From SAN:

• asu set CMOS_ENET_PXE_ENABLE “Planar Ethernet 1”
• asu set CMOS_AlternateBootDevice1 “Network”
• asu set CMOS_AlternateBootDevice2 “Hard Disk 0”
• asu set CMOS_AlternateBootDevice3 “CD ROM”
• asu set CMOS_AlternateBootDevice4 “Diskette Drive 0”
• asu set CMOS_PCIBootPriority “Daughter Card Slot 1”
5.1.1.2 CMOSUTIL
IBM provided a DOS utility called CMOSUTIL on every BIOS flash diskette.
This utility was used to save, restore, or clone the entire BIOS configuration on
systems of the same type. To use this utility, you would create a bootable
diskette that contains PC-DOS 7.0 and the CMOSUTIL utility. You would then
boot that diskette on the system and run one of the following commands.
Saving the BIOS Configuration:

• cmosutil /s {filename}
Restoring the BIOS Configuration:

• cmosutil /r {filename}
5.1.2 New Method
5.1.2.1 ASU 3.0.0

ASU 3.0.0 has versions which run under other operating systems such as
WinPE, Windows, RedHat, SuSE, and VMware ESX Service Console that are
used to perform the same tasks as described above in sections 5.1.1.1 and
5.1.1.2. On UEFI based systems, however, you will need ASU version 3.00 or
higher.
On our previous systems, the BIOS configuration was stored directly on the
CMOS chip. ASU would access a definition file that was embedded in the
BIOS that contained the CMOS map for the system and that specific version of
BIOS. ASU would use that definition file to determine which bits in CMOS to
either read or write based on what the user wanted to do. Because of this, ASU
could only be used on the local system. Additionally because space was very
limited only a small subset of the settings was in the definition file. On our new
UEFI/IMM systems, almost all of the UEFI settings are stored on the IMM file
system. This means that ASU does not need to access UEFI. It only needs to
access the IMM in order to view or modify both UEFI and IMM settings. Since
the IMM is a network device, ASU can now also be used remotely as well as
locally to view or modify the UEFI settings.
Device Configuration Commands Using ASU Locally:

• asu set uEFI.TurboModeEnable “Enable”
• asu set uEFI.RebootOnNMI “Enable”
Device Configuration Commands Using ASU Remotely:

Note that the password contains a zero not a capital O
• asu set uEFI.TurboModeEnable “Enable” --host 192.168.72.125 --user
USERID --password PASSW0RD
• asu set uEFI.RebootOnNMI “Enable” --host 192.168.72.125 --user
SOL (Serial Over LAN) and SP Redirection Configuration:

Notes: SP Redirection is not available on Blades
The legacy options ROMs can only be displayed over one COM port.
The LegacyOptionRomPort option is used to specify which COM port is
used.
• asu set uEFI.SerialCOMPort1 “Enable”
• asu set uEFI.SerialCOMPort2 “Enable”
• asu set uEFI.RemoteConsoleRedirection “Enable”
• asu set uEFI.SerialPortSharing “Enable”
• asu set uEFI.SerialPortAccessMode “Dedicated”
• asu set uEFI.SPRedirection “Enable”
• asu set uEFI.LegacyOptionRomPort “COM Port 1”
• asu set uEFI.Com1BaudRate “115200”
• asu set uEFI.Com1DataBits “8”
• asu set uEFI.Com1Parity “None”
• asu set uEFI.Com1StopBits “1”
• asu set uEFI.Com1TextEmul “VT100”

• asu set uEFI.Com1ActiveAfterBoot “Enable”
• asu set uEFI.Com1FlowControl “Hardware”
• asu set uEFI.Com2BaudRate “115200”
• asu set uEFI.Com2DataBits “8”
• asu set uEFI.Com2Parity “None”
• asu set uEFI.Com2StopBits “1”
• asu set uEFI.Com2TextEmul “VT100”
• asu set uEFI.Com2ActiveAfterBoot “Enable”
• asu set uEFI.Com2FlowControl “Hardware”
Boot Sequence Configuration:

• asu set BootOrder.BootOrder "Floppy Disk=CD/DVD ROM=Hard Disk
0=PXE Network"
Configuring Booting From SAN:

• asu set uEFI.EnableLegacyPxe “Enable”
• asu set BootOrder.WolBootOrder "PXE Network=Floppy
Disk=CD/DVD ROM=Hard Disk 0"
ASU also has the ability to save, restore, and replicate the UEFI settings
providing functionality similar to the DOS cmosutil:
Saving the UEFI Configuration:

• asu save UEFISettings.asu –group uEFI
Saving the Entire Configuration:

• asu save ALLSettings.asu
Restoring the UEFI Configuration to the Same System it was Saved from:
• asu restore UEFISettings.asu
Replicating the UEFI Configuration to Multiple Systems:

• asu replicate UEFISettings.asu
5.2 Configuring BMC/IMM BMC Settings

5.2.1 DOS Method (Replaced by ASU and IPMITool)
5.2.1.1 BMC_CFG
ASU does not provide support for configuring the BMC under DOS. The only
method IBM provides for configuring the BMC in a DOS environment is using
the utility called BMC_CFG that is provided on every BMC flash diskette. This
is not a very user friendly utility as it requires using IPMI commands in hex
format so we do not encourage customers to use it. The instructions for using it
are included here only for completeness.
To use this utility, you would create a bootable diskette that contains PC-DOS
7.0, the BMC_CFG utility, and a text file that has the commands to pass to the
utility.
Creating the Text File:

To create this file, you would open your favorite text editor, add the following
lines, and then save it as something like BMC_CFG.DAT. Note that the #
character signifies a comment. Lines that start with the # character as well as
blank lines are not processed by the utility.
# Enable Serial Port Sharing

0c 10 20 00 04 02 08 06 0a
# Set BMC Serial Port to Dedicated Mode

0c 12 20 00 02 02 04
# Set BMC Serial Port to Terminal Mode
0c 10 20 00 03 02 03 84
# Disable Serial Keep Alive Messages

0c 10 20 00 04 02 08 06 08
# Set BMC IP address to 10.1.1.10

0c 01 20 00 06 01 03 0a 01 01 0a
# Set BMC Submask to 255.255.255.0
0c 01 20 00 06 01 06 ff ff ff 00
# Set BMC Default Gateway to 10.1.1.1

0c 01 20 00 06 01 0c 0a 01 01 01
Changing the Configuration:

After you have created the text file as described above, you would pass that text
file to the utility to change the configuration using the following command.
bmc_cfg –f BMC_CFG.DAT –c -noreport
5.2.2 New Method
5.2.2.1 ServerGuide Scripting Toolkit -- ASU

IBM’s recommended method for configuring the BMC settings is to use the
ASU 3.0.0 tool included in the ServerGuide Scripting Toolkit, WinPE and Linux
Editions. ASU provides access to most of the IMM settings, including the
IPMI-specific settings. Note that the SOL (Serial Over LAN) settings are
configurable via ASU -- those settings are marked as UEFI settings and are
included in the steps for configuring SOL in section 5.1.2.1.
On IMM systems, ASU accesses all settings using the IMM. To access the
IMM, ASU either requires an IPMI driver or a LAN-over-USB driver. When
using the IPMI driver, ASU can access settings in-band without requiring a
userid/password be specified. If accessing IMM settings remotely or without an
IPMI driver, ASU requires that an valid IMM userid and password be specified
on the command line. ASU is compatible with the following device drivers:
Operating System Driver Included in OS?

IPMI drivers:
Windows Server 2000/2003 OSA IPMI No, available from IBM
Windows Server 2003 R2 Microsoft IPMI Yes (must be installed)
Windows Server 2008 Microsoft IPMI Yes (installed by default)
RHEL3,4,5, SLES9,10,11 OpenIPMI Yes
VMware ESX 3.02, 3.5, 4.0 OpenIPMI Yes
LAN-over-USB drivers: (see details in 8.2.1)

Windows 2000/2003/2008 rndis Yes
RHEL4,5, SLES9,10,11 usbnet / cdc-ether Yes
VMware ESX 3.5u4, 4.0 CDCEther / cdc- Yes
ether
5.2.2.2 IPMITool
The open source IPMITool utility can be used on any IBM IPMI based system
including our new systems with IMM. There are versions of this utility that run
under both Windows and Linux environments in local and remote fashions that
can be used to view or modify all of the IPMI 2.0 settings and initiate SoL
sessions. IPMITool provides full access to any of the capabilities that were
previously available thru bmc_cfg.. We will not go into detail on the usage of
IPMITool in this document. For additional information, visit the SourceForge
IPMITool web site.
In order to use IPMITool locally (in-band) you must have an IPMI driver such
as OpenIPMI installed and functioning. As you will in the following sections,
this is not required when using ASU.
5.3 Configuring RSA II/IMM SP Settings

5.3.1 DOS Method
IBM does not provide any utilities to configure the RSA II in a DOS environment.
This is because the RSA II is a USB device and there are no generally available USB
drivers for DOS.
5.3.2 New Method
5.3.2.1 Non-DOS ASU

As previously stated, ASU also has versions of the tool that run under other
operating systems such as WinPE, Windows, RedHat, SuSE, and VMware ESX.
You will be able to use these versions to configure the SP portion of the IMM,
however, you will need ASU version 3.00 or higher. To access settings in the
IMM, ASU requires either an IPMI driver or a LAN-over-USB driver be
installed, as described above.
For backward compatibility, ASU 3.0.0 also supports configuring settings on

IBM RSA II. To view or modify the RSA II settings locally (in-band), the IBM
RSA Server Software daemon is required to be installed first..
All of the IMM settings are stored on the IMM file system and are directly
accessible by ASU. This means that most of the settings supported by the IMM
Web interface are also supported by ASU. Since the IMM is a network device,
ASU can now also be used remotely as well as locally to view or modify the
IMM settings. As discussed in section 8, the IMM supports a new LAN over
USB interface for local in-band access. ASU uses this interface by default to
access the IMM locally and therefore does not require any additional device
drivers or daemons to be installed. Refer to section 8.2.1 for details on
configuring the LAN over USB interface under Windows and Linux. However,
if you would rather not configure the LAN over USB channel and use IPMI
instead, ASU supports that as well if you will have to have the IPMI drivers
already installed. Below are examples for configuring some of the IMM
settings.
Note that viewing or modifying IMM settings via ASU is not currently
supported on IBM Blade servers.
IMM Information Configuration Using ASU Locally:

• asu set IMM.IMMInfo_Name “My iBMC”
• asu set IMM.IMMInfo_Contact “My name”
• asu set IMM.IMMInfo_Location “My location”
IMM Information Configuration Using ASU Remotely:

Note that the password contains a zero not a capital O
• asu set IMM.IMMInfo_Name “My iBMC” --host 192.168.72.125 --user
• asu set IMM.IMMInfo_Contact “My name” --host 192.168.72.125 --
user USERID --password PASSW0RD
• asu set IMM.IMMInfo_Location “My location” --host 192.168.72.125 --
user USERID --password PASSW0RD
Configuring the IMM for SP Serial Redirection:

• asu set IMM. SerialRedirectionCLIMode1 “CLI with user defined
keystroke sequences”
• asu set IMM. SerialExitCLIKeySequence “^[Q”
• asu set IMM. SerialBaudRate “115200”
ASU also has the ability to save, restore, and replicate the IMM settings as
follows:
Saving the IMM Configuration:

• asu save IMMSettings.asu IMM
Restoring the IMM Configuration to the Same System it was Saved from:
• asu restore IMMSettings.asu
Replicating the IMM Configuration to Multiple Systems:

• asu replicate IMMSettings.asu
5.4 Configuring Storage Subsystem

5.4.1 DOS Method (Replaced by ServerGuide Scripting Toolkit)
The recommended method for configuring the storage subsystems is to use the
ServerGuide Scripting Toolkit. There are DOS, Windows, and Linux versions of the
Toolkit available. All of these versions come with a tool called PRAID which is a
policy based RAID configuration utility. This utility automatically detects which
storage subsystem is present in the system and based on the policies that are
available, automatically configures the subsystem. Additional information on the
ServerGuide Scripting Toolkit and the PRAID utility can be found via the
ServerGuide Scripting Toolkit matrix:
https://www-
304.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=SERV-
TOOLKIT&brandind=5000008
We also provide individual command line utilities and other tools for configuring the
storage subsystem as dicussed in the following sections.
5.4.1.1 DOS CFGGEN

The individual utility provided to configure the integrated RAID controller, also
known as IR, is named CFGGEN. Below are some examples for configuring
the IR controller.,
Create a new mirrored logical drive of 52 GB on channel 0 and SCSI ID 1

and on channel 0 and SCSI ID2 on controller 1, using quick
synchronization
• cfggen 1 create logicaldrive NEWARRAY 52071 1 0 1 0 2 qsync
Creates a logical drive on controller 1, using all available space on the

drive, sets RAID1 for channel 0 and SCSI ID 1; then, sets the state to hot
spare
• cfggen 1 create logicaldrive NEWARRAY MAX 1 0 1 cfggen setstate 1
0 1 HSP
5.4.1.2 DOS MegaCLI

The individual utility provided to configure the optional MegaRAID adapters,
also known as MR, is named MegaCLI. This is a very powerful utility that has
many options. In order to keep this document as brief as possible, we will only
show examples of a couple simple commands. Refer to the ServerRAID-MR
Software guide for more information..
Display the Properties of all Adapters in the System

• MegaCli -AdpAllinfo -aALL
Enable Automatic Rebuild on all of the Adapters in the System

• MegaCli –AdpAutoRbld –Enbl -aALL
5.4.2 New Method

As previously mentioned, the recommended method for configuring the storage
subsystems is to use the ServerGuide Scripting Toolkit. There are Windows and
Linux versions of the Toolkit available. Both of these versions come with a tool
called PRAID which is a policy based RAID configuration utility. This utility
automatically detects which storage subsystem is present in the system and based on
the policies that are available, automatically configures the subsystem. Additional
information on the ServerGuide Scripting Toolkit and the PRAID utility can be found
via the ServerGuide Scripting Toolkit matrix:
https://www-
304.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=SERV-
TOOLKIT&brandind=5000008
ServerGuide Scripting Toolkit provides all of the individual command line utilities
and other tools for configuring the storage subsystem as dicussed in the following
sections.
5.4.2.1 Non-DOS CFGGEN

CFGGEN already has versions of the tool that run under other operating
systems such as Windows and Linux. The steps for using CFGGEN under these
OS’ are the same as those used in section 5.4.1.1.
5.4.2.2 Non-DOS MegaCLI

MegaCLI already has versions of the tool that run under other operating systems
such as Windows and Linux. The steps for using MegaCLI under these OS’ are
the same as those used in section 5.4.1.2.
5.4.2.3 WinPE ServerGuide Scripting Toolkit

For more information and the setup steps required to enable
the scenarios below, see the Standalone User’s Reference
(ibm_sw_sgtkw_2_1_01_anyos_anycpu.pdf)
and the Altiris Deployment Solution User’s reference
(ibm_sw_sgtkw_2_1_01_anyos_anycpu_altiris.pdf).
Links to these documents can be found on the Scripting Toolkit’s main page:
https://www-
304.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=
MIGR-5073727&brandind=5000008
Standalone:
1. Change directory to \sgshare\sgdeploy\SGTKWinPE
2. Run the following command from a command prompt:
3. SGTKWinPE.cmd ScenarioINIs\Local\Raid_config_Only.ini
This command creates an ISO image WinPE_x86.iso in
..\WinPE_ScenatioOutput\Local_Raid_Config_Only\
4. Burn the CD from iso image and then boot the target server with this CD
and follow the on line instruction to complete the task
Altiris Raid Configuration:

1. Navigate to IBM Scripting Toolkit, Windows Edition 2.1 -> Modular
Deployment Tools -> Step 1 – Preinstallation Hardware Configuration ->
RAID Configuration folder
2. Run the appropriate Job against the target system to create the RAID
configuration
Altiris Raid Replication:

RAID Replication folder
2. Run the Capture RAID configuration job against the target system to capture
and existing RAID configuration
3. The job will create RAID configuration file ‘RAID_Configuration.ini’.
5. Run the deploy RAID configuration job against the target system. This job
will use the same configuration file as in step 3
5.4.2.4 Linux ServerGuide Scripting Toolkit

(ibm_utl_sgtklnx_1.00_anyos_anycpu.pdf)
(ibm_utl_sgtklnx_1.00_anyos_anycpu_altiris.pdf).
https://www-
Standalone:
1. Launch the Linux Toolkit Console by running sgtklinux.sh
2. Define a workflow that includes the RAID Task
3. Create the Boot Media type ISO, USB Key, or PXE
4. Boot the media on the server and the workflow will run automatically.
Altiris Raid Configuration:

1. Navigate to IBM Scripting Toolkit, Linux Edition 1.00 -> Modular
RAID Configuration folder
2. Run the appropriate Job against the target system to create the RAID
configuration
Altiris Raid Replication:

2. Run the Capture RAID configuration job against the target system to capture
and existing RAID configuration
3. The job will create RAID configuration file ‘raid_capture.ini’.
5. Run the deploy RAID configuration job against the target system. This job
will use the same configuration file as in step 3
5.5 Configuring System via PXE Booting

5.5.1 DOS Method
5.5.1.1 DOS Based HDD Image

There are a number of methods that can be used to create a bootable DOS HDD
image:
1. Use DOS HDD image from xCAT 1.2
2. Install DOS to HDD image via virtual machine software (VMware,
Virtualbox, Xen, KVM, etc.
3. Create DOS bootable USB key and copy key as image.
4. Reference IBM techdocs for creating DOS bootable image
“Updating System Firmware using the PXE boot Method of Remote
Deployment”. This document describes how to create a DOS bootable disk
image and can be found at the following link:
http://www-03.ibm.com/support/techdocs/atsmastr.nsf/Web/Techdocs
Once an image is created, the DOS based configuration utilities referenced in

previous sections can be added to the image (copy to root of image) and scripted
via DOS batch files. These scripts can be auto run via the autoexec.bat file.
You can create a script file for each configuration utility and then create a
master configuration script to execute each. Use autoexec.bat to call the master
script.
For example create a script raid.bat to configure the arrays, and cmos.bat to set
BIOS settings
Sample RAID configuration script:

NOTE: You must copy the DOS version of CFGGEN to the HDD image.
ECHO configure raid set

CALL CFGGEN 0 delete
CALL CFGGEN 0 CREATE IM MAX 1 4 noprompt
Sample BIOS Settings script:

NOTE: You must copy the DOS version of ASU to the HDD image.
ECHO enable serial console:

ECHO configure Serial ports
CALL asu set CMOS_SerialB “Auto-configure”
CALL asu set CMOS_SerialA “Auto-configure”
ECHO configure text console

CALL asu set CMOS_RemoteConsoleEnable “Enabled”
CALL asu set CMOS_RemoteConsoleComPort “COM 2”
CALL asu set CMOS_RemoteConsoleBaud “19200”
CALL asu set CMOS_RemoteConsoleDataBits “8”
CALL asu set CMOS_RemoteConsoleParity “None”
CALL asu set CMOS_RemoteConsoleStopBits “1”
CALL asu set CMOS_RemoteConsoleEmulation “ANSI”
CALL asu set CMOS_RemoteConsoleKybdEmul “ANSI”
CALL asu set CMOS_RemoteConsoleBootEnable “Enabled”
CALL asu set CMOS_RemoteConsoleFlowCtrl “Hardware”
Sample autoexec.bat:
ECHO Configure system settings
CALL RAID.BAT
CALL CMOS.BAT
5.5.2 New Method
5.5.2.1 Bootable Media Creator Image

There are multiple ways to create a bootable media environment that can be
delivered via PXE (network boot).
1. The IBM ToolsCenter Bootable Media Creator will create a bootable which
can be delivered via PXE
2. The SystemRescueCD project: http://www.sysresccd.org can be use to
create a bootable environment as well. It uses a very recent version of 2.6
linux kernel, which most system can boot and contains most of the drivers
and utilities needed.
3. Boot the RedHat and SuSE installers contain a rescue environment that can
be PXE booted and used for system configuration.
In each of these methods a Linux kernel image (vmlinuz) and corresponding

initial ramdisk image (initrd) are booted via PXE. The initrd will need to
contain the necessary drivers and utilities for system configuration. This will
usually include the drivers for the RAID controller and the matching Linux
command line utility:
AACRAID.KO and ARCCONF

MEGARAID_SAS and MegaCLI
The Bootable Media Creator and UpdateXpress Installer both will download a
zip’ed image that contains the bootable Linux environment. There is a startup.sh
script that can be edited to contain the necessary scripts to configure the server.
Also both tools create a working directory that the tools are copied from, so the
necessary tools can be copied to this working directory. A modified copy of the
startup.sh should also be placed in this directory. Any files in this working
directory will be part of the bootable image.
5.5.3 PXE Booting Hard Drive Images

From a Linux System:
1. Install syslinux
2. Install TFTP and DHCP servers
3. Create static reservations for each server or a dynamic range in
/etc/dhcpd.conf
4. Setup /TFTPBOOT directory
copy pxelinux.0 and memdisk to /tftpboot
create /tftpboot/pxelinux.cfg subdirectory
5. Copy DOS image to /tftpboot (i.e. hd.img)
6. Create pxeboot file “default” in /tftpboot/pxelinux.cfg:
Default PXE file contents:

DEFAULT dos
LABEL dos
KERNEL memdisk
APPEND initrd=hd.img
Note: If “default” is used for the filename, any server that PXE boots will get
this file. The default file can be set to boot the local hard drive. Server specific
files can be also used. These files can be named via the MAC address of the
server or the HEX encoded IP address the server is using.
6 Deployment
In this section we describe and walk through some typical scenarios used to deploy the operating
system. We will cover how those tasks are commonly performed today with DOS based tools
and how the same tasks will be performed on our new UEFI/IMM based systems.
6.1 Deploying an OS Using ServerGuide Scripting Toolkits

6.1.1 DOS Method
6.1.1.1 DOS ServerGuide Scripting Toolkit

The User’s reference is ibm_sw_sgtk_1_3_07_anyos_anycpu.pdf which can be
found on the Scripting Toolkit for DOS main page:
https://www-
304.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=MIGR-
53564&brandind=5000008
See the “Using a DOS-startable CD-ROM or DOS-startable diskette and data

CD-ROM” and “Using a DOS-startable diskette and network share” sections in
“Chapter 5, Deploying Microsoft windows operating systems” for examples of
deployment scenarios similar to the ones below for the WinPE Toolkit.
6.1.2 New Methods

https://www-
5073727&brandind=5000008
Standalone:
2. Acquire UXSP for Systems and OS to be deploy
3. Create OS Task
4. Define a workflow that includes the OS Task
Altiris:
Cloning Installation:
1. Navigate to IBM ServerGuide Toolkit, Linux Edition 1.00 -> Modular
Deployment Tools -> Step 2 –Operating System Installation -> Operating
System Imaging folder
2. Open the Capture Linux Image Job
3. Select Create Disk Image and click Modify
4. Change the file name and path for the captured image and click Finish
5. Run the Capture Linux Image against the donor system
6. Open the Deploy Linux Image job
7. Select the Distribute Disk Image task and click Modify
8. Change the path and filename to match as in step 4 and click Finish
9. Run the Deploy Linux Image job against the target server
Scripted Installation:
1. Navigate to IBM Scripting Toolkit, Linux Edition 1.00, Modular
Deployment Tools -> Step 2 – Operating System Installation -> Scripted
Operating System Installation folder
2. Select the job that corresponds to the Linux or VMware you want to install
6.1.2.2 WinPE ServerGuide Scripting Toolkit

(ibm_sw_sgtkw_2.1.02_anyos_anycpu.pdf)
(ibm_sw_sgtkw_2.1.02_anyos_anycpu_altiris.pdf).
https://www-
5073727&brandind=5000008
Standalone:
Windows Local Deployment:
SGTKWinPE.cmd ScenarioINIs\Local\Win2003_x86_EE.ini
..\WinPE_ScenatioOutput\Local_Win2003_x86_EE\
Windows Network Deployment:

SGTKWinPE.cmd ScenarioINIs\Network\Win2003_x86_EE.ini
..\WinPE_ScenatioOutput\Netwrk_Win2003_x86_EE\
Altiris:
Cloning Installation:
1. Navigate to IBM ServerGuide Toolkit, Windows Edition 2.1 -> Modular
Deployment Tools -> Step 2 –Operating System Installation -> Operating
System Imaging folder
2. Open the Capture Windows Image
3. Select Create Disk Image and click Modify
4. Change the file name and path for the captured image and click Finish
5. Open the Deploy Windows Image job
6. Select the Distribute Disk Image task and click Modify
7. Change the path and filename to match as in step 4 and click Finish
8. Run the Capture Windows Image against the donor system
9. When it completes. Run the Deploy Windows Image job against the target
server
Scripted Installation:
1. Navigate to IBM Scripting Toolkit, windows Edition 2.1, Modular
Deployment Tools -> Step 2 – Operating System Installation -> Scripted
Operating System Installation folder
2. Select the job that corresponds to the Windows operating system you want
to install
7 Updates
In this section we describe and walk through some typical scenarios used to perform firmware
updates. We will cover how those tasks are commonly performed today with DOS based tools
and how the same tasks will be performed on our new UEFI/IMM based systems.
7.1 Bootable Media

7.1.1 DOS Methods
7.1.1.1 DOS ServerGuide Scripting Toolkit

The User’s Reference is ibm_sw_sgtk_1_3_07_anyos_anycpu.pdf which can be
found on the DOS Toolkit main page:
https://www-
53564&brandind=5000008
Instructions to populate the Toolkit source server with the desired updates are in
section “Including BIOS code and firmware updates in a deployment scenario”
in Appendix B “Enhancing deployment scenarios”.
The corresponding variables for the desired scenario then need to be updated
accordingly. See the “BIOS code and firmware code update variables” portion
of the table on printed page number 47 in the User’s Reference. This is located
within the “Modifying USRVARS.BAT” section in Chapter 3 “Customizing
Toolkit scenarios”.
7.1.1.2 UpdateXpress CD
IBM provided a product called UpdateXpress CD used to perform firmware and
devices driver updates. The method to perform the firmware update portion was
booting the CD. The CD booted PC-DOS and then executed the DOS based
firmware update packages.
Users could boot the CD using the systems local CD-ROM and could also use
the virtual media functionality of RSA II and the Advanced Management
Module to mount the ISO image and have the system boot it remotely as
detailed below in sections 7.3.1 and 7.3.2.
7.1.2 New Methods
7.1.2.1 Bootable Media Created with UXSPI

One of the main UpdateXpress CD replacement tools IBM provides is called the
UXSP Installer (UXSPI). The main function of this tools is to install our
UXSPs but this tool also provides the ability to create bootable media that
contains the latest UXSP for any given system using either a CLI (under
Windows or Linux) or using a GUI (under Windows only). This tool solves two
of the main issues customers had with the UpdateXpress CD which were that
the content was stale and updating the content of the CD was a tedious task.
Below are the steps used to…

• Acquire the current UXSP for the system, 7979 in this case
• Acquire the bootable media environment
• Create a bootable ISO image
Notes:
• The instructions below use the Windows version of UXSPI. There are
also versions available for RedHat and SuSE.
• The instructions below are executed from a Windows command prompt
• The examples in this document use UXSPI version 2.01. The ability to
create bootable media directly from UXSPI will be removed in version
3.00. Instead, users will use our new IBM ToolsCenter Bootable Media
Creation (ITBoMC) tool which is described below in section 7.1.2.2.
• As noted above, UXSPI 3.00 will not directly create the bootable media,
however, UXSPI 3.00 will still accept the ‘bootable’ command listed
below and pass it and the additional arguments to the ITBoMC utility.
• UXSPI 2.01 will not be able to detect the current firmware levels of the
new systems. You will need UXSPI version 3.00 or higher for this.
• These examples are for creating a bootable ISO image. UXSPI also
provides the ability to create bootable USB devices. Please refer to the
UXSPI users guide on our ToolsCenter InfoCenter for additional details
and functionality.
• UXSPI 2.01 does not provide the ability to create hard drive images that
can be booted via PXE. That functionality may be provided in our new
ITBoMC tool.
Creating Bootable ISO Image for a 7979 Server:

1. Create a working directory
 md c:\UXSPI2.01
2. Change to the working directory
 c:
 cd \UXSPI2.01
3. Download the Windows version of UXSPI 2.01 (setup201.exe) to the
directory created above (c:\UXSPI2.01)
4. Acquire the latest UXSP for the 7979 server
 setup201 acquire –m 7979 –o sles10
Note that the bootable media requires the SLES 10 packages, not the
Windows packages
5. Acquire the bootable media environment
 setup201 acquire -b
6. Create the bootable ISO image
 setup201 bootable –i 7979Firmware.iso
7.1.2.2 Bootable Media Created with ITBoMC

As noted in the above section, creating bootable media with UXSPI will be
replaced with our new Bootable Media Creator (ITBoMC) tool. To make the
transition as easy as possible, ITBoMC 1.0 and UXSPI 3.0.0 will both support
the same command line arguments meaning that UXSPI version 3.0.0 will
accept the commands to create the bootable media and pass them to ITBoMC.
ITBoMC offers significantly more functionality than was available with UXSPI
such as adding other IBM tools like DSA to the bootable image. Another
difference in ITBoMC from UXSPI is that you do not have to manually
download the bootable environment. ITBoMC will automatically check for the
existence of the bootable environment and if it does not find it, it will
automatically download it. If it does find it, it will check and make sure it is the
latest version and if not, automatically download the latest. Finally, with
UXSPI you had to run separate commands to aquire the bootable environment,
then acquire the updates, and then create the media. With ITBoMC, all of this is
done with one simple command line.
Creating Bootable ISO Image for a 7979 Server:

1. Create a working directory
 md c:\ITBoMC1.0
2. Change to the working directory
 c:
 cd \ ITBoMC1.0
3. Download the Windows version of ITBoMC 1.0
(ibm_utl_itbomc_1.00_windows_i386.exe) to the directory created
above (c:\ ITBoMC1.0)
4. Create the ISO image
 ibm_utl_itbomc_1.00_windows_i386.exe --iso=7979Firmware.iso --
function uxspi --bootenv=linux –m 7979

https://www-
Standalone:
2. Define a workflow that includes the Firmware Update Task
Altiris Firmware Updates:

Update Firmware (UXSP) folder
2. Run Update System Firmware Job against the target system to update the
system
7.2 Individual Updates

7.2.1 DOS Method
7.2.1.1 Individual Diskette and CD-ROM Images
IBM provided individual DOS based diskette (.img) and/or CD-ROM (.iso)
images for updating the system firmware.
Users could create physical diskettes or CD-ROMs and boot them using the
systems local diskette or CD-ROM drive and could also use the virtual media
functionality of RSA II and the Advanced Management Module to
mount/upload the images and have the system boot them remotely as detailed
below in sections 7.3.1 and 7.3.2.
Note that all of the DOS based updates run in attended mode by default,
meaning that the utilities will stop and wait for user interaction. Most of these
updates also provide metods to run the updates in unattended mode however,
this is beyond the scope of this document. Consult the ReadMe provided with
the update for instructions of how to execute the updates in unattended mode.
7.2.2 New Methods
7.2.2.1 Individual Updates

Most of our updates are now on-line meaning that they can be executed under
the running operating system such as Windows and Linux and do not require a
reboot in order to perform the actual flash. Some of the updates such as BIOS,
UEFI, and the storage controllers require a reboot to activate the new firmware
but the firmware is actually flashed from under the operating system. For
systems that do not have an operating system installed, the recommended
method to perform updates is using the Bootable Media Creator (ITBoMC) as
described in section 7.1.2.2 which also uses on-line updates. ITBoMC can
create a bootable media with a individual update, with multiple updates, or with
all firmware updates.
Example for Creating Bootable Media that Contains a Single Update:

Follow the steps below to create a bootable ISO image or USB key using
ITBoMC that contains a single update for the HS21 Blade using the Windows
version of the tool.
Notes: The instructions below will vary slightly when using ITBoMC on Linux
operating systems.
When ITBoMC is executed, it will automatically acquire the required

UXSPI (UpdateXpress System Pack Installer) and bootable environment
files from the IBM web site. This operation requires an internet
connection.
1. Create a working directory, for example, C:\HS21BIOSUpdate

2. Download the Windows version of ITBoMC to the temporary directory.
For example:
a. ibm_utl_bomc_1.00_windows_i386.exe
3. Download the Linux version of the update and the corresponding XML
file to the temporary directory. For example, download the following
BIOS update files for the HS22:
a. ibm_fw_bios_bce140a_linux_i386.sh
b. ibm_fw_bios_bce140a_linux_i386.xml
4. Execute ITBoMC to create a bootable ISO image or USB key
a. ibm_utl_bomc_1.00_windows_i386.exe --
iso=HS21BIOSUpdate.iso
b. ibm_utl_bomc_1.00_windows_i386.exe --usbkey=E:
Example for Creating Bootable Media that Contains a UXSP:

Follow the steps below to create a bootable ISO image or USB key using
ITBoMC that contains the latest UXSP for the HS21 Blade using the Windows
version of the tool.
Notes: The instructions below will vary slightly when using ITBoMC on Linux
operating systems.
When ITBoMC is executed, it will automatically acquire the required

UXSPI (UpdateXpress System Pack Installer), bootable environment,
and UXSP files from the IBM web site. This operation requires an
internet connection.
1. Create a working directory, for example, C:\HS21UXSP

2. Download the Windows version of ITBoMC to the temporary directory.
For example:
a. ibm_utl_bomc_1.00_windows_i386.exe
3. Execute ITBoMC to create a bootable ISO image or USB key
a. ibm_utl_bomc_1.00_windows_i386.exe --
iso=HS21BIOSUpdate.iso –m 8853
b. ibm_utl_bomc_1.00_windows_i386.exe --usbkey=E: -m 8853
On our new systems, the UEFI, Diagnostic, and IMM firmware updates are all
performed by the IMM. The updates are delivered to the IMM using the LAN
over USB interface, described in section 8.2.1, or out-of-band using the external
IP address of the IMM. We will focus on using the LAN over USB interface for
in-band updates in this section. The other individual firmware updates perform
the same way they do on our previous systems.
Because the updates are much larger on our new systems, using a device driver
or a slow bus is not efficient enough. Therefore, the UEFI, Diagnostic, and
IMM updates all have an FTP client built in. When the update is executed, at a
high level, the following occurs:
1. The package extracts itself to a temporary directory

2. The update utility attempts to connect to the IMM using the default
IMM LAN Over USB address – 169.254.95.118
3. If the update utility cannot connect to the IMM using the default address,
it will:
a. Check to see if the LAN Over USB interface is up and configured
properly
i. If the interface is not up or configured properly, the update utility
will attempt to automatically bring it up and/or configure it
b. Attempt to discover the IMM using an SLP multicast only on the

LAN Over USB interface
4. The update utility contacts the IMM via the LAN over USB interface
using either the default address or the IP address discovered by SLP and
tells it to start an embedded FTP server
5. The update utility sends the update to the IMM via FTP
6. The update utility obtains status updates from the IMM as the update is
downloaded
7. The update utility tells the IMM to shut down the FTP server
8. The update utility tells the IMM to perform the update
9. The update utility obtains status updates from the IMM as the update
performed
10. Upon a successful update, if the update was for the IMM, the update
utility automatically reboots the IMM
7.2.2.2 UXSPs
IBM’s recommend method for performing device driver and firmware updates
is using our UpdateXpress System Packs (UXSPs). These are a tested bundle of
updates that run under the operating system. Our bootable media creation tools
also use UXSPs to create a bootable media containing all necessary firmware
updates. The UXSPs can be downloaded as a complete set from the IBM web
site or aquired by the UpdateXpress System Pack Installer (UXSPI) and/or the
Bootable Media Creator (ITBoMC). Please refer to the ToolsCenter Web site
for additional information on our UXSPs.
7.3 Remote Booting

Note that the methods detailed in this section can be used to remotely boot the updates
whether they are DOS or non-DOS based unless otherwise stated.
7.3.1 Using RSA II Virtual Media

To use the virtual media functionality of the RSA II, launch the remote control applet
via the Web interface under the Remote Control link and clicking on either the ‘Start
Remote Control in Single User Mode’ or ‘Start Remote Control in Multi-user Mode’.
Once the applet has started, you would…
• Left click on ‘Select File’
• Press the >> button
• Select the diskette or ISO image from the file brower and click Open
• Click on the Mount Drive button
• Boot or reboot the server
Note that in order to boot the diskette or ISO image you have to have diskette or CD-
ROM in your boot order before the local hard drive or network boot if you used PXE
booting.
7.3.2 Using AMM Virtual Media

Note that these instructions were written using AMM firmware version BPET48C. If
using AMM firmware versions prior to the one used above, you would skip the first
step below.
To use the virtual media functionality of the AMM, launch the remote control applet
via the Web interface under the Remote Control link and clicking on Start Remote
Control button. Once the applet has started, you would…
• Click on the ‘Remote Drive’ buton
• Left click on ‘Select Image’
• Press the Add -> button
• Select the diskette or ISO image from the file brower and click Open
• Click on the Mount All button
• Boot or reboot the server
Note that in order to boot the diskette or ISO image you have to have diskette or CD-
ROM in your boot order before the local hard drive or network boot if you used PXE
booting.
Additionally with the AMM, if the image is small enough, you can upload the entire
image to the memory of the AMM. The amount of free space available is shown in
parenthesis next to the ‘Upload Image AMM…’ option.
To upload the image to the AMM, you would follow the instuctions above but replace
the second step (Left click on ‘Select Image’) with ‘Left click on ‘Upload Image to
AMM…’.
8 Management
As previously stated, while the main focus of this document is migrating away from DOS tools,
in this section we will cover some additional items such as how managing our new IMM based
systems will be different in a good way.
8.1 BMC and RSA II

There are several methods you can use to manage the BMC and RSA II devices in our
systems. There are In-Band paths meaning that you communicate with the device from the
operating system running on the system and Out-Of-Band paths meaning that you
communicate with the device over the Ethernet network.
The IBM Director agents, ASU, and our On-Line flash utilities, for example, use the In-Band
path while the IBM Director server uses the Out-Of-Band path.
Notes:
• The In-Band is available for all systems
• The Out-Of-Band path is not available for Blades
• The RSA II is not supported on Blades
8.1.1 BMC Device Drivers

In order to communicate with the BMC In-Band, you must have an IPMI device
driver installed. Our tools support two IPMI device drivers:
8.1.1.1 OSA IPMI Device Driver and Mapping Layer

When we originally shipped our BMC products, we also released an IPMI
device driver written by OSA. This device driver also required the installation
of a Mapping Layer for the utilities such as SMBridge to function properly.
Both the OSA IPMI device driver and Mapping Layer can be downloaded from
the IBM support site.
8.1.1.2 OpenIPMI Device Driver

We later transitioned our tools to support using the Open Source OpenIPMI
device driver. This device driver does not require a Mapping Layer to function
properly. The OpenIPMI device driver comes with most major Linux operating
systems and and VMware ESX. Windows operating systems also include an
IPMI driver starting with Windows Server 2003 R2.
8.1.2 RSA II USB Daemon

A device driver is not required to communicate with the RSA II In-Band however, a
USB daemon is. As the name states, this is not a device driver. This is a daemon that
creates a USB connection from the operating system to the RSA II. There are
versions of this daemon available for both Windows and Linux operating systems.
8.1.3 In-Band Tools

Once you have the device driver and/or deamon installed, you can use the following
tools to manage the BMC and/or RSA II in-Band. Note that this is not a complete list
of tools.
8.1.3.1 SMBridge
As mentioned above, we initially released a tool named SMBridge (System
Management Bridge) used to manage and configure the BMC on our systems.
The documentation for this tool can be found on our ToolsCenter Information
Center.
8.1.3.2 IPMITool
Also as mentioned above, we now support using the Open Source tool
IPMITool to manage and configure the BMC on our systems. Please visit the
SourceForge web site for documentation on using IPMITool.
8.1.3.3 ASU Version 2.x and Earlier

As mentioned in previous sections, ASU can be used to configure the BMC and
RSA II settings. Versions 2.x and Earlier can only be used In-Band.
8.1.3.4 Flash Utilities

Also as mentioned previous sections, we have flash utilities that run In-Band to
update the BMC and RSA II firmware. The flash utilities for these devices can
only be used In-Band.
8.1.4 Out-Of-Band Tools

You can use the following tools to manage the BMC and/or RSA II Out-Of-Band.
Note that this is not a complete list of tools.
8.1.4.1 SMBridge
SMBridge can also be used to manage and configure the BMC on our systems
Out-Of-Band. Again, the documentation for this tool can be found on our
ToolsCenter Information Center.
8.1.4.2 IPMITool
IPMITool can also be used to manage and configure the BMC on our systems
Out-Of-Band. Again, please visit the SourceForge web site for documentation
on using IPMITool.
8.1.4.3 Other RSA II Interfaces

There are several other interfaces as listed below that can be used to manage the
RSA II Out-Of-Band but we will not go into detail for these interfaces:
• Web
• SNMP
• Telnet CLI
• SSH CLI
8.2 IMM
Similar to the BMC and RSA II, there are several methods you can use to manage the IMM.
There are both In-Band and Out-Of-Band paths, however, there are no device drivers or deamons
required for In-Band management although as you will see you can use the OpenIPMI drivers if
you so choose.
8.2.1 LAN over USB

As mentioned above, we no longer require IPMI device drivers or USB daemons to
communicate with the IMM In-Band. We can now use a LAN over USB interface.
This means that we expose an Ethernet NIC from the IMM to the operating system.
Typically, the IMM IP address for the LAN over USB interface is set to a static
address of 169.254.95.118 with a subnet mask of 255.255.0.0. In the event of an IP
address collision on the network, the IMM may obtain a different IP address within
the 169.254 range. The IMM will first try to use the same address that is currently
being used as the static address, 169.254.95.118. If that address is in use, it will
randomly obtain an address and try it until it finds one that is not in use.
Since the IMM could possibily obtain a random IP address for the LAN over USB
interface, ASU, the IMM, UEFI, and Diagnostic flash utilities, DSA, ITBoMC, and
the IBM Director agent will use SLP (Service Location Protocol) to discover the
IMMs IP address. At a high level, these tools will perform an SLP multicast
discovery on the LAN over USB interface and when they recive the response from
the IMM, they will obtain the attributes that contains the IP address the IMM is using
for the LAN over USB interface.
Additionally, all of the tools mentioned above will automatically detect if the LAN
over USB interface is not already configured or misconfigured and automatically
configure it. The sections below describe how to configure the interface on the
various operating systems if you so choose to configure it yourself.
8.2.1.1 Configuring the LAN over USB Interface on Windows

When you install Windows on these systems, there will be an unknown RNDIS
device in the device manager. IBM provides a Windows INF that identifies this
device. The signed version of the INF is included in all of the Windows
versions of the IMM, UEFI, and DSA update packages. To obtain the INF,
extract the contents of the package via the GUI (execute the package with no
parameters) or the –x command line parameter.
Installing the Windows INF file:
Note: These instuctions are for Windows 2003
• Obtain the INF as instructed above and note the location
• Open the Windows device manager
o Right click on ‘My Computer’ and select ‘Manage’
o Left click on ‘Device Manager’
• Locate the unknown ‘RNDIS/CDC ETHER’ device located under ‘Other
devices’
• Right click on the device and select Update Driver
• Follow the prompts and select the INF file
• Using the Hardware Update Wizard
o Select ‘Install from a list or specific location (Advanced)’
o Click on ‘Next’
o Deselect ‘Search removeable media (floppy, CD-ROM…)’
o Click on the ‘Browse’ button
o Select the location of the INF file and press ‘OK’
o Click ‘Next’
o For now, the INF is not signed so you will have to press
‘Continue Anyway’
o Click ‘Finish’
o Close the ‘Computer Management’ window
By default when Windows installs the device, it will set it to try and obtain an IP
address via DHCP. This will not work so you will have to reconfigure the
interface with a static IP address.
To configure a static IP address:

Note: These instuctions are for Windows 2003
• Right click on ‘My Network Places’ and select ‘Properties’
• Select the device listed as ‘IBM USB Remote NDIS Network Device’
• Right click on the device and select ‘Properties’
• Select ‘Internet Protocol (TCP/IP)’
• Click on ‘Properties’
• Select ‘Use the following IP address:’
• Enter 169.254.95.130 in the ‘IP address:’ field

• Enter 255.255.0.0 in the ‘Subnet Mask:’ field
• Click ‘OK’
• Click ‘Close’
• Close the ‘Network Connections’ window
8.2.1.2 Configuring the LAN over USB Interface on Linux
8.2.1.2.1 Current Versions

The current versions of Linux such as RHEL5 Update 2 and SLES10
Service Pack 2 support the LAN over USB interface by default. This
interface will be detected and displayed during the installation of these
operating systems. Remember when configuring the device to use a static
IP address of 169.254.95.130 with a subnet mask of 255.255.0.0.
Once setup of the device is complete, ensure that communication to the

IMM is successful by pinging 169.254.95.118. If no ping response is
received ensure that your routing table is correct for this device. A single
route entry of 169.254.0.0 should exist for usb0, if any other 169.254.0.0
route entry exist it must be removed from the table to ensure
communication to the IMM.
8.2.1.2.2 Previous Versions
8.2.1.2.2.1 RHEL4 U7
The previous version of RedHat, RHEL4 U7, does not
automatically detect this interface so you must manually configure
it as follows.
Configuring the LAN over USB interface on RHEL4 U7:

Note: These instructions are for using the GNOME desktop
• Edit the ‘/etc/modprobe.conf’ file
o Open the file in your favorite text editor
o Add the following line to the bottom of the file
 alias usb0 usbnet
• At a console prompt, type ‘modprobe usb0’
• Verify the drivers are loaded
o At a console prompt, type ‘lsmod | grep usb’
o You should see ‘usbnet’ and ‘mii’ listed
• Left click on ‘Applications’ -> ‘System Settings’ -> ‘Network’
• In the ‘Network Configuration’ GUI:
o Left click on ‘New’
o Select ‘Ethernet connection’ and click the ‘Forward’ button

o Select ‘USB CDC Ethernet driver (usb0)’ and click the
‘Forward’ button
o Configure the IP address:
 Select ‘Statically set IP address’
 Enter 169.254.95.130 in the ‘Address:’ field
 Enter 255.255.0.0 in the ‘Subnet mask:’ field
o Click on ‘Forward’
o Click on ‘Apply’
o Click on ‘File’ -> ‘Save’
o Click on ‘OK’
o Highlight the new Inactive usb0 device
o Click on ‘Activate’
 The interface should now be ‘Active’
o Close the ‘Network Configuration’ GUI
• Verify you can ping the IMM
o At a console prompt, type ‘ping –c 4 169.254.95.118’
o You should see 4 successful pings
8.2.1.2.2.2 SLES9 SP4

The previous version of SuSE, SLES9 SP4, automatically detects
this interface during the install however it detects it is a modem not
a network interface. Due to this, you cannot configure it during the
install and must manually configure it after the install as follows.
Configuring the LAN over USB interface on SLES9 SP4:

o Manually create an ifcfg-usb0 file in the
/etc/sysconfig/network directory
 cd /etc/sysconfig/network
 vi ifcfg-usb0 and add the following lines
• IPADDR=169.254.95.130
• NETMASK=255.255.0.0
• STARTMODE=onboot
 Save the file
o Add an alias to usb0 in the file /etc/modprobe.conf.local
 vi /etc/modprobe.conf.local
• alias usb0 usbnet
 Save the file
o Bring the interface up
 ifup usb0
8.2.1.2.3 Known Issue with SuSE and VMWare Routing Tables

There is a known issue with SuSE and VMWare where by default the
routing tables may contain a network route for eth0 that prevents
communications with the IMM via the LAN over USB interface. To
delete the route, type the following at the command line. Note that if you
reboot, this route will appear again. To prevent this, add this command to
one of the init scripts that is run after the network devices are configured.
• route del -net 169.254.0.0 netmask 255.255.0.0 dev eth0
8.2.1.2.4 Known Limitation with RHEL5 U2 and Earlier and the LAN over
USB Interface
There is a known limitation with RHEL5 U2 where network installations
will fail if this interface is enabled. This is a RedHat issue that resides in
the installation code so cannot be fixed in that version. RedHat has
identified and fixed this issue. The fix will be included in RHEL5 U3.
In order to network install RHEL5 U2 and earlier versions, you must

disable the LAN over USB interface. Once the operating system has been
installed, you can reenable the device. Note that if you do not reenable the
device, you will not be able to perform updates from under the operating
system.
The interface can be enabled or disabled via an IPMI command, the IMM
web interface, the AMM web interface, or via ASU. The IPMITool
command is listed below for convenience.
Disabling the LAN over USB interface using IPMITool:

Note: If executing IPMITool inband, which is required for Blades, you
must have the IPMI device drivers loaded. Additionaly, if
executing IPMITool inband, you would omit the –I, -C, -U, -P and
–H parameters in the command below
• ipmitool –I lanplus –C 1 –U {user ID} –P {password} –H {IMM
IP address} raw 0xC 0x1 0x1 0xC1 0x0
Enabling the LAN over USB interface using IPMITool:

Note: If executing IPMITool inband, which is required for Blades, you
must have the IPMI device drivers loaded. Additionaly, if
executing IPMITool inband, you would omit the –I, -C, -U, -P and
–H parameters in the command below
• ipmitool –I lanplus –C 1 –U {user ID} –P {password} –H {IMM
IP address} raw 0xC 0x1 0x1 0xC1 0x1
8.2.1.2.5 Potential LAN over USB Interface Conflicts

There are cases where the LAN Over USB interface can conflict with
certain network configurations and/or applications. An example is
OpenMPI which attempts to use all available network interfaces.
OpenMPI will see this interface and attempt to use it to communicate with
other systems in a clustered environment. Since this interface is an
internal only interface, this will not work.
There are a few alternatives to workaround these types of issues such as:
 You can take the interface down (ifdown under Linux)
 You can completely remove the driver (rmmod under Linux)
 You can disable the interface on the IMM as described in the above
section
 Specifically for OpenMPI, you can configure it to not attempt to
use this interface
There are additional considerations to take into account before selecting

which action to take.
1. The OS loader watchdog depends on the LAN Over USB interface

to be active. If you take it down or disable the interface, the
watchdog could erroneously trigger and reboot the system. There
fore, if this interface is not active, you must also disable the OS
watchdog.
2. As mentioned in previous sections, our online IMM, UEFI, and
Diagnostic updates require this interface to send the update to the
IMM. If you take down or remove the interface, our update
utilities will automatically attempt to bring it back up. If you
disable the interface from the IMM, the online utilities will not
work at all.
It is therefore recommended that you do not take down, remove, or disable

the interface if it can be avoided.
8.2.2 In-Band Tools

As previously mentioned, there is no need to install device drivers to use our tools to
manage the IMM In-Band, however, if you choose to use certain tools such as
IPMITool In-Band, you will need the OpenIPMI drivers. Below are the tools you can
use In-Band to manage the IMM.
8.2.2.1 IPMITool
Using IPMITool In-Band on IMM is the same as using it on BMC. Please visit
the SourceForge web site for documentation on using IPMITool.
8.2.2.2 ASU Version 3.00 and Higher

As mentioned in previous sections, ASU 3.00 is used to configure the UEFI and
IMM settings.

Also as mentioned previous sections, we have flash utilities that run In-Band to
update the UEFI, IMM, and Diagnostic firmware.
8.2.3 Out-Of-Band Tools
You can use the following tools to manage the IMM Out-Of-Band.
8.2.3.1 IPMITool
IPMITool can also be used to manage and configure the IMM on our systems
Out-Of-Band. Again, please visit the SourceForge web site for documentation
on using IPMITool.
8.2.3.2 ASU Version 3.00 and Higher

As mentioned in previous sections, ASU 3.00 can be used to manage the IMM
Out-Of-Band to configure the UEFI and IMM settings.

Also as mentioned previous sections, the flash utilities for the UEFI, IMM, and
Diagnostic firmware can be used Out-Of-Band.
8.2.3.4 Other IMM Interfaces

There are several other interfaces as listed below that can be used to manage the
IMM Out-Of-Band but we will not go into detail for these interfaces:
• Web
• SNMP v1
• SNMP v3
• Telnet CLI
• SSH CLI
• CIM/XML via HTTP
• CIM/XML via HTTPS

• WS-MAN via HTTP
• WS-MAN cia HTTPS
This is the last page of the document!!
End of Document

Transitioning To UEFI and IBM

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Transitioning To UEFI and IBM

Uploaded by

Copyright:

Available Formats

Whitepaper

Life Without DOS

Written By: System x

Unified Extensible Firmware Interface improvements over legacy BIOS:

1.2 Document Overview

Diagnostics Updates Deployment Configuration

Bootable Media Creator Online, runnable

1.3 Document Contributors

2 Definitions and Abbreviations

3 Supported Systems and Compatibility

3.2 IBM UEFI and IMM Blades and Servers

 HS22 7870 Blade Server

 x3650 M2 7947 2U Rack Mount Server

 x3550 M2 7946 1U Rack Mount Server

4 DOS Based Tools Overview

4.1.2 ASU (Advanced Settings Utility)

Description: Configures SAS/SATA LSI MegaRAID controllers (ServeRAID 10)

4.2.2 Remote Deployment Manager

4.2.3 ServerGuide Scripting Toolkit for DOS (SGTK)

4.3.1 DOS Based Diskette Images

5.1 Configuring BIOS/UEFI Settings

5.1.1.1 DOS ASU

Device Configuration Commands:

Error Handling Configuration:

SOL (Serial Over LAN) Configuration:

• asu set CMOS_RemoteConsoleBootEnable “enabled”

Boot Sequence Configuration:

Configuring Booting From SAN:

Saving the BIOS Configuration:

Restoring the BIOS Configuration:

5.1.2 New Method

5.1.2.1 ASU 3.0.0

Device Configuration Commands Using ASU Locally:

Device Configuration Commands Using ASU Remotely:

SOL (Serial Over LAN) and SP Redirection Configuration:

• asu set uEFI.Com1TextEmul “VT100”

Boot Sequence Configuration:

Configuring Booting From SAN:

Saving the UEFI Configuration:

Saving the Entire Configuration:

Replicating the UEFI Configuration to Multiple Systems:

5.2 Configuring BMC/IMM BMC Settings

Creating the Text File:

# Enable Serial Port Sharing

# Set BMC Serial Port to Dedicated Mode

# Disable Serial Keep Alive Messages

# Set BMC IP address to 10.1.1.10

# Set BMC Default Gateway to 10.1.1.1

Changing the Configuration:

5.2.2 New Method

5.2.2.1 ServerGuide Scripting Toolkit -- ASU

Operating System Driver Included in OS?

LAN-over-USB drivers: (see details in 8.2.1)

5.3 Configuring RSA II/IMM SP Settings

5.3.2 New Method

5.3.2.1 Non-DOS ASU

For backward compatibility, ASU 3.0.0 also supports configuring settings on

IMM Information Configuration Using ASU Locally:

IMM Information Configuration Using ASU Remotely:

Configuring the IMM for SP Serial Redirection:

Saving the IMM Configuration:

Replicating the IMM Configuration to Multiple Systems:

5.4 Configuring Storage Subsystem