HP BladeSystem ProLiant Firmware

Management Best Practices

Implementer Guide

Table of contents
Introduction ......................................................................................................................................... 5
Firmware updates ............................................................................................................................ 5
HP BladeSystem................................................................................................................................... 5
Overview ........................................................................................................................................ 5
Quickstart ........................................................................................................................................... 6
Generic BladeSystem firmware update installation order ................................................................... 7
Installation order .......................................................................................................................... 8
General best practices ...................................................................................................................... 9
Recommended firmware deployment strategies ..................................................................................... 10
HP BladeSystem and firmware ......................................................................................................... 10
Firmware management ....................................................................................................................... 11
Developing a firmware management strategy .................................................................................... 11
What options are available for firmware deployment? ....................................................................... 12
Firmware deployment overview ........................................................................................................... 13
Available tools to update HP BladeSystem firmware ............................................................................... 14
HP SUM ........................................................................................................................................ 14
HP SUM Minimum Requirements .................................................................................................. 16
HP SUM Execution Modes ........................................................................................................... 17
VCSU ........................................................................................................................................... 19
Single smart components ................................................................................................................ 21
HP SIM and Version Control Agent .................................................................................................. 22
Virtual SAS Manager...................................................................................................................... 25
Obtaining the latest available HP firmware update tools ......................................................................... 26
Choosing the deployment tool ............................................................................................................. 27
HP BladeSystem Firmware Update Bundles ....................................................................................... 29
HP BladeSystem FDT....................................................................................................................... 31
HP Firmware Maintenance CD ........................................................................................................ 33
Recommended methods to deploy individual firmware types ................................................................... 34
System ROM ................................................................................................................................. 35
iLO2 firmware ............................................................................................................................... 35
NIC firmware ................................................................................................................................ 37
PowerPIC or Power Management Controller firmware ........................................................................ 38
Smart Array Controller firmware ...................................................................................................... 41
SAS and SATA hard drive firmware ................................................................................................. 41
Emulex, QLogic, and Brocade Fibre Channel HBA firmware ............................................................... 43
Tape Blade firmware ...................................................................................................................... 43
 OA firmware ................................................................................................................................. 44
Installation order ........................................................................................................................ 45
VC firmware .................................................................................................................................. 45
Installation order ........................................................................................................................ 48
HP StorageWorks MDS600 firmware ............................................................................................... 48
HP StorageWorks 3Gb SAS BL Switch firmware ................................................................................ 49
Firmware deployment scenarios........................................................................................................... 49
Installation scenarios .......................................................................................................................... 52
Scenario 1A: Updating an individual server using the HP BladeSystem Firmware Update Bundles ........... 52
Scenario 1B: Updating a server using the HP BladeSystem FDT ........................................................... 54
Scenario 1C: Updating an individual server using the HP Firmware Maintenance CD ............................ 55
Online updates .......................................................................................................................... 56
*iLO Virtual Media ..................................................................................................................... 57
Offline updates .......................................................................................................................... 58
Scenario 2A: Updating the OA firmware using HP SUM..................................................................... 59
Scenario 2B: Updating the OA firmware using the OA browser interface from a workstation .................. 60
Scenario 2C: Updating the OA firmware using the OA CLI interface and a web server .......................... 60
Obtaining all necessary files ........................................................................................................ 61
Setting Up the Microsoft IIS web server ......................................................................................... 61
Setting up the Apache web server in Linux..................................................................................... 62
Configuring the SSH keys for scripted installations .......................................................................... 64
Uploading the SSH keys to the OAs ............................................................................................. 65
Updating the OA firmware once the web server successfully configures ............................................ 67
Scenario 3A: Updating the VC firmware using VCSU ......................................................................... 68
General requirements ................................................................................................................. 68
Before the upgrade begins .......................................................................................................... 69
Updating the VC firmware ........................................................................................................... 70
Scenario 3B: Updating the VC firmware using the HP SUM ................................................................ 71
General requirements ................................................................................................................. 71
Before the upgrade begins .......................................................................................................... 72
Updating the VC firmware ........................................................................................................... 72
Scenario 3C: Updating the VC firmware in a DMZ (special case using the OA virtual USB support) ........ 74
General requirements ................................................................................................................. 74
Before the upgrade begins .......................................................................................................... 74
Updating the VC firmware from a USB key in the OA ..................................................................... 75
Scenario 4: Updating an enclosure and blades with a previously installed OS ...................................... 76
Installation order ........................................................................................................................ 76
If VC Ethernet firmware is earlier than 1 .34: ................................................................................. 77
Scenario 5: Updating an enclosure and blades without an existing OS installed.................................... 78
Summary ................................................................................................................................... 79
Scenario 6: Scripted installation of firmware updates for multiple enclosures, including the OA, VC, and server
blades .......................................................................................................................................... 79
Obtaining all necessary files ........................................................................................................ 80
Setting up the Microsoft IIS web server .......................................................................................... 81
Setting up the Apache web server in Linux..................................................................................... 82
Configuring the SSH keys for scripted installations .......................................................................... 83
Uploading the SSH keys to the OAs ............................................................................................. 84
Populate the web servers and script directory with all necessary files ................................................ 85
Populating the script directory ...................................................................................................... 85
Populating the web server directory .............................................................................................. 86
Installing necessary RPMs in Linux ................................................................................................ 87
Obtaining a list of all iLO IP addresses by querying the OA for them ................................................ 87
Validating the iLO Advanced License is installed on each blade ....................................................... 88
Finding the version of iLO firmware on each blade ......................................................................... 89
Obtaining the current Virtual Media status for a blade .................................................................... 90
Setting Virtual Media to boot on a blade ....................................................................................... 91
Inserting the virtual media on a blade ........................................................................................... 92
Disconnecting the virtual media on a blade ................................................................................... 93

2
 Determining the power state on a blade ........................................................................................ 93
Turning the power off on a blade ................................................................................................. 94
Turning the Power On for a blade ................................................................................................ 95
Creating HP SUM Inputfiles ......................................................................................................... 96
Extracting the VCSU and VC binary firmware files from the VC component ....................................... 97
Putting it all together ................................................................................................................... 97
Update Blade firmware scripts ..................................................................................................... 98
Sample Windows Power Shell script to drive the FDT update process for an entire enclosure at once . 100
Sample L ................................................................................................................................. 108
Update OA firmware scripts ...................................................................................................... 116
Sample Windows Power Shell script to drive the OA firmware update process to a single OA at a time117
Sample Linux script to drive the OA firmware update process to a single OA at a time ..................... 118
Update VC firmware scripts ....................................................................................................... 119
Sample Windows Power Shell script to drive the VC firmware update process to a single VC at a time120
Sample Linux script to drive the VC firmware update process to all the VC modules in a single enclosure at a
time ........................................................................................................................................ 122
Scenario 7: Updating the HP StorageWorks MDS600 firmware ........................................................ 123
Using HP SUM in GUI mode ............................................................................................................. 125
Using the GUI for local host installations ......................................................................................... 125
Selecting the location to check for updates .................................................................................. 125
Directory ................................................................................................................................. 126
Proxy Details ............................................................................................................................ 127
Include components previously downloaded from www.hp.com. .................................................... 127
Download permission ............................................................................................................... 127
Selecting an installation host ...................................................................................................... 128
Selecting components to install ................................................................................................... 130
Multi-session installation ............................................................................................................ 133
Reboot section ......................................................................................................................... 133
Component selection pane ........................................................................................................ 134
Installation options .................................................................................................................... 135
Viewing the installation results.................................................................................................... 137
Using the GUI for multiple-host installations ..................................................................................... 140
Selecting remote hosts or groups .................................................................................................... 140
Managing hosts ....................................................................................................................... 141
Entering credentials for hosts ..................................................................................................... 144
Selecting components to install on multiple hosts .......................................................................... 147
Viewing the installation results for multiple hosts ........................................................................... 149
Using HP SUM in Scripted or Silent mode ........................................................................................... 150
Command line syntax ............................................................................................................... 150
Command line arguments .......................................................................................................... 151
HP SUM return codes ................................................................................................................ 154
Results ..................................................................................................................................... 156
HP SUM special considerations ......................................................................................................... 157
Network ports used by HP SUM..................................................................................................... 157
Trusted platform module support issues ........................................................................................... 159
TPM scenarios .......................................................................................................................... 161
VMware ESX firmware updates ......................................................................................................... 161
VMware ESX/ESXi environments.................................................................................................... 161
HP firmware management services .................................................................................................... 162
HP BladeSystem firmware and Driver Gap analysis .......................................................................... 162
HP BladeSystem firmware and Driver Update process review ............................................................ 163
FAQ ............................................................................................................................................... 163
Driver dependency considerations .............................................................................................. 163
What tools should I use to update the various firmware types? ....................................................... 166
Why must I always upgrade to the latest individual firmware and driver components? ...................... 166
HP SUM questions ........................................................................................................................ 166
 How does HP SUM work when applied to an entire chassis; for example, does it update each blade, iLO2,
and so on, sequentially or in parallel? ........................................................................................ 166
What are the advantages and drawbacks to using the HP BladeSystem Firmware Update Bundles versus the
HP BladeSystem FDT? ............................................................................................................... 166
Why is Version Control (included with SIM) not the tool of choice to manage firmware upgrades across the
HP BladeSystem portfolio? ......................................................................................................... 167
What about administrators who have invested time to understand HP SIM and specifically Version Control?
.............................................................................................................................................. 167
Where do I obtain theHP SUM user guide? ................................................................................. 167
How can I leverage the HP SUM pull-from-web functionality when my data center cannot be connected to
the Internet for security reasons? ................................................................................................. 167
It seems the HPSUM GUI interface cannot currently accept input (for example, groups of IP addresses) from
files, but I heard this feature is planned in a future version. Does the HPSUM CLI allow creation of a group
from a file with a list of IP addresses or DNS names when the file is presented to it as a file name that is
given as a CLI command-line parameter? .................................................................................... 167
What is the function of the additional drivers in the BladeSystem Firmware Update Bundle? .............. 168
When using the HP BladeSystem Online Firmware Bundles for Windows and Linux to upgrade an entire
c7000 Enclosure and all of its constituents, including the OAs, server blades, iLO2s, and switch modules:
.............................................................................................................................................. 168
Currently, the server BIOS must be updated prior to the iLO2 because of a potential issue with the Power
PIC. Will HP SUM reorder the installation set to avoid this issue? ................................................... 168
Miscellaneous BladeSystem firmware-related questions ..................................................................... 169
Can SIM use the HP BladeSystem firmware update bundles for Windows and Linux as a VCRM-custom base
line? ....................................................................................................................................... 169
What is the recommended tool for understanding the currently-deployed BladeSystem equipment firmware
revisions? ................................................................................................................................ 169
Can I update my Blades HBA firmware online? ............................................................................ 170
How do I manage my Blade interconnect switch updates? ............................................................. 170
Are there any guidelines for downgrading firmware? ................................................................... 170
Can you upgrade versions of HBA firmware without being concerned about going through an interim
version to facilitate the upgrade? ................................................................................................ 170
Can I roll-back the individual changes on a per-server or per chassis basis? .................................... 170
How often should we upgrade firmware? .................................................................................... 171
How does the firmware version affect our support status with HP? .................................................. 171
How do I add updated components to the HP BladeSystem FDT? ................................................... 171
How do I add updated components to the HP firmware maintenance CD? ...................................... 171
How do virtual environments affect the firmware update process? .................................................. 173
Installed firmware version data collection ........................................................................................... 173
Enclosure-level firmware information ............................................................................................... 173
Blade server-level firmware information ........................................................................................... 175
NIC firmware ........................................................................................................................... 175
Tape firmware ......................................................................................................................... 176
Smart Array controller firmware and SAS/SATA hard drive firmware versions ................................. 177
Troubleshooting ............................................................................................................................... 178
Troubleshooting HP SUM .............................................................................................................. 178
Troubleshooting HP BladeSystem FDT ............................................................................................. 181
Trouble shooting Log Files for individual smart components ............................................................... 182
Troubleshooting PowerPIC firmware update errors ........................................................................... 182
Troubleshooting failed iLO2 firmware updates ................................................................................. 183
For more information ........................................................................................................................ 185
Glossary ......................................................................................................................................... 187
Acronyms and abbreviations ......................................................................................................... 187

4
Introduction
Firmware updates
Updating firmware is crucial for maintaining server systems. Updating the existing firmware is less
expensive than replacing it. Consequently, firmware updates are as important to the OS as software
and driver updates. This document describes the best practices for updating HP c-Class BladeSystem
product firmware, including the following:
 Information to help identify a firmware maintenance strategy
 Determining which firmware to update
 Selecting the appropriate tools to perform firmware updates
 Considering the process dependencies
 Guiding you in performing firmware updates

HP BladeSystem
Overview
When updating HP BladeSystem c-Class enclosures, consider the following firmware:
 BladeSystem OA firmware
 BladeSystem VC firmware
 Blade Server System ROM
 Blade Server iLO 2 firmware
 Broadcom, Intel, and NetXen NIC firmware
 PowerPIC firmware
 Smart Array Controller firmware
 SAS and SATA hard drive firmware
 Emulex, QLogic, and Brocade Fibre Channel HBA firmware
 Tape blade firmware
 HP StorageWorks MDS600
 HP 3Gb SAS BL Switch Firmware

Note:
EVA firmware, MSA2000 firmware, and BladeSystem Interconnect
Switches are not covered in this document. To update the firmware for
these devices, see the specific product documentation.

5
 Quickstart
Table 1 provides a quick jumpstart in performing firmware updates.
The information in the Estimated time for deployment column indicates the time required to update the
firmware, not the time required to obtain the firmware, execute the deployment tools, or gather
information necessary for the firmware update process.
The information in the Does update effect normal server operations? column indicates whether or not
the update process causes a server downtime. Many types of firmware can be staged to the actual
hardware while the server is operating normally. You can update these firmware types and have them
staged for the next time the server is rebooted to activate the firmware.
Table 1. Required information for firmware update

Is firmware staged for next Estimated time for Does update affect
Firmware type Tool to use reboot or immediately deployment normal server
activated? operations?

System ROM HP SUM Staged 1 minute No

iLO2 firmware HP SUM Immediate 2 minutes No

Broadcom NIC firmware HP SUM Immediate, but requires a 5 minutes Yes

reboot

Intel NIC firmware HP SUM Immediate, but requires a 5 minutes Yes

reboot

NetXen NIC firmware HP SUM Immediate, but requires a 10 minutes Yes, must be
reboot updated offline

PowerPIC firmware HP SUM Immediate, but requires a 3 minutes No

reboot

Smart Array controller firmware HP SUM Staged 2 minutes No

SAS and SATA hard drive firmware HP SUM Staged 1 minute per drive No
behind Smart Array controllers

SAS and SATA hard drives behind non- No current support 1 minute per drive No
Smart Array controllers

Emulex, QLogic, and Brocade Fibre HP SUM Staged 3 minutes Yes, must be
Channel HBA firmware updated offline

Tape Blade firmware HP SUM Immediate 10 minutes No, unless tape

backups are
planned during the
firmware update
process

OA firmware HP SUM Immediate 10 minutes No

VC firmware VCSU Immediate 10-40 minutes If the VC firmware

is earlier than 1.34,
the VC must be in a
redundant
configuration or
updated to a later
version before
updating the OA

6
 Is firmware staged for next Estimated time for Does update affect
Firmware type Tool to use reboot or immediately deployment normal server
activated? operations?

firmware;
otherwise, a
network downtime
of up to 10 minutes
can occur.

HP StorageWorks MDS600 HP SUM Immediate 10 minutes Yes, must be

updated offline and
other blades
connected to the
MDS600 must be
powered off during
the update process

HP 3Gb SAS BL switch firmware VSM Immediate 10 minutes Yes, can cause a
temporary
downtime for any
storage being
updated

Important:
MDS600 firmware update requires HP SUM 3.6.0 or later and that ALL
blades in an enclosure that have Smart Array P700Mcontrollers except the
blade doing the update must be turned OFF before the firmware update
process is initiated. MDS600 firmware can only be updated using the
Firmware Maintenance CD in offline mode.

Important:
The HP 3Gb SAS BL switch firmware can only be updated by uploading a
bin file through the VSM product. This firmware is currently delivered as a
binary image file on the HP website and must be downloaded and
manually upgraded because it is not available on any other tool discussed
in this document.

Generic BladeSystem firmware update installation order

If the VC Ethernet firmware is 1.34 or later, or if you are not using VC in your blade enclosures, HP
recommends the following installation order, based on whether or not an OS is installed.
OS is installed
1. Update the blades and the OA by using the HP BladeSystem Online Firmware Bundles for
Windows and Linux.
Be sure to use a workstation connected to the same network as the OA.
2. Update any offline-only firmware with the HP BladeSystem FDT or HP Firmware Maintenance
CD tool.
3. Update the VC firmware with the VCSU from a workstation that is connected to the same
network(s) as the OA and VC Ethernet modules.
Be sure to update the firmware after all other updates are applied, after servers are rebooted,
and after all firmware is activated.

7
 OS is not installed
1. Update the OA first by using the HP BladeSystem Online Firmware Bundles for Windows and
Linux.
Use a workstation connected to the same network as the OA.
2. Update the VC firmware with the VCSU from a workstation connected to the same network(s)
as the OA and VC Ethernet modules.
Be sure to update the firmware after all other updates have been applied, after the servers are
rebooted, and after all firmware is activated.
3. Update all server-specific firmware with the HP BladeSystem FDT or HP Firmware Maintenance
CD.

If VC Ethernet firmware is earlier than 1.34

Follow these steps, regardless of whether or not an OS is installed.
1. Update the VC firmware by using the VCSU from a workstation connected to the same
network(s) as the OA and VC Ethernet modules.
2. Update the server blades and the OA by using the HP BladeSystem Online Firmware Bundles
for Windows and Linux from a workstation connected to the same network as the OA.
3. Update any offline-only firmware with the HP BladeSystem FDT or HP Firmware Maintenance
CD.
The HP SUM tool embedded in these tools correctly orders all firmware updates within the
blades and enclosures to be updated.

Use the following links to gain access to the latest versions of the quarterly release sets that contain
the firmware and tools described in the table.
 HP BladeSystem Online Firmware Update Bundles for Windows 1.70
 HP BladeSystem Online Firmware Update Bundles for Linux 1.70
 HP FDT for Offline Updates 1.70
 HP Firmware Maintenance CD 8.70

Installation order
Use the following installation order if you are using VC Ethernet firmware 1.34 or later, or if you are
not using VC in your blade enclosures.
Server OS is already installed
1. Update the blades and the OA first by using the HP BladeSystem Online Firmware Bundles for
Windows and Linux using a workstation connected to the same network as the OA.
2. Use the HP BladeSystem FDT or HP Firmware Maintenance CD to update any offline-only
firmware.
3. Use the VCSU from a workstation connected to the same network(s) as the OA and VC Ethernet
modules to update the VC firmware after all other updates are applied, servers are rebooted,
and all firmware is activated.

8
Server OS is not installed
1. Update the OA first by using the HP BladeSystem Online Firmware Bundles for Windows and
Linux by using a workstation connected to the same network as the OA.
2. Use the VCSU from a workstation connected to the same network(s) as the OA and VC Ethernet
modules to update the VC firmware after all other updates are applied, servers are rebooted,
and all firmware is activated.
3. Use the HP BladeSystem FDT or HP Firmware Maintenance CD to update all server-specific
firmware.

If the VC Ethernet firmware is earlier than 1.34, follow this installation order (whether or not a
Server OS is installed):
1. Update the VC firmware first by using the VCSU from a workstation connected to the same
network(s) as the OA and VC Ethernet modules.
2. Update the server blades and the OA next using the HP BladeSystem Online Firmware Bundles
for Windows and Linux from a workstation connected to the same network as the OA.
3. Use the HP BladeSystem FDT or HP Firmware Maintenance CD to update any offline-only
firmware.

General best practices

For bare-metal deployment (no server OS installed), use HP BladeSystem FDT—Offline for unattended
installation. Use HP Firmware Maintenance CD for attended installations.
Use the HP BladeSystem Online Firmware Bundles for Windows and Linux for updating existing
servers that are configured with an OS.
The HP BladeSystem Firmware Bundle—Online should use the HPSUM input file for scripted
installations in large environments to ease this potentially time consuming task.
When registering an issue with the HP post sales support team, make sure the firmware version of the
components that are included in the enclosure align with those listed in the HP BladeSystem Firmware
Compatibility chart.
You can deploy firmware and software together by using HPSUM:
 Test your representative setup and the updates desired in a lab environment, if available, before
updating production servers.
 If you do not have access to a test lab, update one server, and then run the updated server for a
few days. If the server operates normally, update the remaining servers, beginning with small
groups of similar servers.
 Make sure that you are using the most current version or the previous version of firmware. HP
ensures that if you are within the currently supported versions, you can obtain help without being
required to upgrade to the latest version of firmware. Occasionally, upgrading the firmware
might be the only solution.
 If you have a problem installing a smart component, visit the web site and the ITRC forums to find
out if there is a newer component available or if others are reporting the same problem.
 You can flash firmware for an entire enclosure at a time as long as you have performed the
appropriate unit testing in a lab environment.
 If you are installing a new server, update the firmware first before installing the OS. This ensures
that any firmware issues with OS installation are addressed.
 Always ensure you have a backup of the server in case the firmware update fails.

9
  HP does not recommend downgrading or rewriting firmware unless there is a specific reason to
do so. Downgrading firmware may cause incompatibilities between hardware devices if the
downgraded firmware is not compatible with other firmware.
 Always reboot the server after server-based driver or firmware upgrades.

Recommended firmware deployment strategies

HP BladeSystem and firmware
First, determine which firmware needs to be deployed and what are the supported versions of this
firmware. The HP BladeSystem Firmware Compatibility chart provides a list of which firmware and
software versions were tested together. This chart provides information about the current and previous
versions of firmware. HP recommends that the firmware in your enclosures be one of the previous two
versions to ensure proper operation of your enclosures. The chart is updated approximately every
three months.
HP is introducing a new release set concept that is represented as release column in the HP
BladeSystem Firmware Compatibility chart for a given release—such as 2010.01, which represents
the January 2010 release set. The quarterly release charts will show the current and two previous
versions of the HP BladeSystem Online Firmware Bundles for Windows and Linux and the HP
BladeSystem FDT. HP recommends that you select a quarterly release set as your standard, instead of
an individual firmware version. By doing so, your updates are based on a release set that has been
extensively tested as an integrated solutions stack.
HP will validate each quarterly release set to ensure it meets the high quality standards you expect. As
part of their standard verification of user environments, HP verifies that a server is running one of the
supported quarterly release sets (which includes the currently released version and the two previous
released versions). If necessary, HP will recommend individual firmware updates. However, by using
the supported versions, you can remain in a supported environment for up to nine months. If an
individual component is released out of cycle, it will be tested with the latest release set to ensure
quality for the out-of-cycle component. It will also be reflected as a smart component update to the
release set. If an out-of-cycle component is added to a released set, the server is still considered to be
in a supported environment.
You can obtain information about the individual firmware versions contained within each quarterly
release set by clicking the Download link on the HP BladeSystem Firmware Compatibility chart,
selecting the Installation Instructions tab and following the link to the contents document.

10
Table 2 is a partial example of the HP BladeSystem Firmware Compatibility chart.
For the latest revision of the HP BladeSystem Firmware Compatibility Chart, see
http://www.hp.com/go/bladesystemupdates/.
Table 2. Firmware compatibility

Compatibility
Description Version release date with OA File download
release

HP BladeSystem Online 1.60 Latest - Revision history

OA V2.52
Firmware Bundle for Windows and download links

HP BladeSystem Online 1.60 Latest - Revision history

OA V2.52
Firmware Bundle for Linux and download links

HP BladeSystem FDT 1.60 – Aug 10, 2009 N/A

HP BladeSystem FDT 1.50 – Mar 25, 2009 N/A

HP BladeSystem FDT 1.41 - Jan 26, 2009 N/A

Firmware management
Developing a firmware management strategy
Before updating any firmware, it is important to develop and document a firmware management
strategy. Consider the following criteria when developing your strategy.
 How frequently do I update the firmware?
Updating firmware continuously is not a good use of vital IT resources. HP recommends
standardizing to either a three-month or six-month maintenance window for updating firmware.
In the near future, HP will provide information about how critical each firmware release is. HP SUM
will be able to display this information to help you determine whether or not an update is required,
recommended, or optional.
By viewing these recommendations and considering available downtimes, you can determine the
best time to update your BladeSystem firmware. In some cases, staggering the updates across
multiple enclosures over several weeks is the best practice to follow.
 How do I manage critical updates?
Not every firmware update released by HP is critical to a server. Reviewing the available
documentation, such as release notes and customer advisories, can help you determine if a given
firmware release is critical or not. When a critical update is released, it is important to note which
options are available for updating that type of firmware. In some cases, you can update the
firmware, such as iLO firmware, with no downtime to the target servers. In other cases, you must
reboot the server into a special boot environment such as those provided by the offline Firmware
Maintenance CD and BladeSystem FDT ISO. Updates requiring these special boot environments
may have excessive downtime depending on the number of devices that must be updated. For
instance, updating an external array of 70 drives which take about 40 seconds per drive can
require almost an hour of downtime. The amount of downtime must be factored into the server
uptime requirements for daily operations. Analyzing the updates and categorizing them as reboot

11
 required, offline boot environment required, ability to be staged, and other consideration (such as
timeframes required) will help in outlining the firmware update strategy.
 When do I stage updates?
Because many firmware updates require rebooting, it is sometimes best to install these firmware
updates and wait for a window of downtime before rebooting the server and activating the
updates. Many types of firmware can be staged, such as System ROM, Storage Controller, and
hard drives. When an available downtime occurs for other reasons, such as updating Microsoft or
Linux fixes, application updates, or weekly server reboots, the downtime for the server can be
minimized or eliminated because the firmware has already been written to the hardware. This is
because most firmware loads itself from the hardware into memory when the server boots. When
the server boots, the firmware image on the hardware is not accessed again until the server is
rebooted to reload the image. There are also several infrastructure updates such as the OA, iLO,
and VC (if it is set up in redundant mode) where the firmware can be flashed without any
interruption in service on the servers in the enclosure.
Also consider that many network-based devices such as the OA, VC, and iLO can be updated
without affecting the server operations. In the case of VC, the VC configuration must be set up in
redundant mode to prevent a network downtime. Updating this firmware without affecting the
servers enables you to reduce the maintenance window because these devices are already up to
date. Now you can use the maintenance window for server-based updates that require a reboot
and not for infrastructure updates that extend the downtime.
 How can I take advantage of firmware that immediately updates?
Some server-based updates, such as iLOs and tape firmware, can be updated while the server is
still operational without requiring downtime.

What options are available for firmware deployment?

The HP ProLiant BladeSystem series of server blades were invented, designed, and created by the
same teams that designed the ProLiant DL rack-based and ML stand-alone servers and associated
management tools. This is mature technology, and this technology can be understood quickly because
the reliability and design confidences that have been built up over many years with both ProLiant and
Integrity products are present in HP BladeSystem server blades.
As HP BladeSystem server blades were adopted in many environments and subsequent feedback was
received, these teams developed additional tools specific to HP BladeSystem solutions. Figure 1 shows
how HP provides individual smart components to update individual firmware, how HP SUM and other
tools are provided to manage and deploy these updates, and how the components and tools are
integrated into HP customer tools.

12
Figure 1. HP Smart Update technology

With multiple tools comes flexibility, but also the potential for confusion. This section specifies the
recommended tools to use to upgrade firmware components within an HP BladeSystem solution,
and explains which tool is appropriate for which situation.

Firmware deployment overview

Four key terms are used when describing firmware update use case scenarios; local, remote, online,
and offline.
 A local installation means the installation tool runs on the physical hardware that is being
updated. An example is a utility that is executed on a server to update its System ROM.
 A remote installation means the installation tool runs on one system but updates other physical
targets. An example is where the OA firmware can be updated across the network by uploading
a firmware .bin file to OA through a web browser. The physical tool runs on a workstation, but
remotely updates the OA.
 An online installation means the installation takes place while the host processor is running in the
normal server environment. For instance, if the server runs Microsoft Windows Server 2003, the
update takes place under this environment and does not require you to boot to a special
environment to update the firmware. An online installation does not mean that a reboot may not
be necessary for the firmware to be activated.
 An offline installation means the installation takes place while the server is booted to a special
environment that prevents you from performing normal operations until the firmware update
operations are completed and the server is rebooted. An example is when a server boots to the
Firmware Maintenance CD to deploy Emulex, QLogic, and Brocade Fibre Channel HBA firmware

13
 updates. These updates require that no I/O operations are done through the adapters while they
are being updated, and the only way to ensure this is to boot to a special environment.

These terms can be used in combination to designate the type of environment required for firmware
updates to occur, such as local-online or remote-online.

Available tools to update HP BladeSystem firmware

The recommended tools to use for deployment of firmware are as follows:
 HP SUM
 VCSU for VC firmware
 Individual smart components

HP SUM
HP SUM, which is the deployment engine within the HP BladeSystem FDT, HP BladeSystem Online
Firmware Bundles for Windows and Linux, HP Firmware Maintenance CD and ProLiant Support Pack
for Windows, is the primary deployment tool that should be used to update firmware on HP
BladeSystem enclosures. HP SUM is designed for maximum flexibility and is shipped within the HP
ProLiant Support Pack for Windows, Firmware Maintenance CD, HP BladeSystem FDT, and HP
BladeSystem Online Firmware Update Bundles for Windows and Linux.
HP SUM provides a GUI and a command-line, scriptable interface for deployment of firmware for
single or one-to-many servers and network-based targets such as iLOs, OAs, and VC Ethernet and
Fibre Channel modules. HP SUM has an integrated hardware and software discovery engine that
discovers the installed hardware, current versions of firmware in use on a target, and software
versions on target servers. This prevents extraneous network traffic by only sending the required
components to a target host. HP SUM also has logic to install updates in the correct order and ensure
all dependencies are met before deployment of a firmware update. It also contains logic to prevent
version-based dependencies from destroying an installation and ensures firmware updates are
handled in a manner that reduces any downtime required for the firmware update process.
HP SUM does not require an agent for remote installations as it copies a small, secure SOAP server to
the target server for the duration of the installation and thus requires Administrative (Windows) and
root (Linux) level access. After the installation is complete, the SOAP server and all remote files
associated with the installation except installation log files are removed. HP SUM copies the log files
from the remote targets back to the system where HP SUM is executed.
The key features of HP SUM include the following:
 Dependency checking, which ensures appropriate install order and dependency checking
between components
 Hardware, Software and Services discovery
 Intelligent deployment deploys only required updates
 Simultaneous firmware and software deployment
 Improved deployment performance
 Local or remote (one-to-many) online deployment
 Local offline deployments with the HP FDT and Firmware Maintenance CD
 Remote offline deployment, when used with the SmartStart Scripting Toolkit or iLO Virtual Media
 GUI or CLI/scriptable with extensive logging
 Remote command-line deployment

14
  Support for updating firmware on network-based targets, such as the OA, iLO2 through its
Network Management Port, and VC Ethernet and Fibre Channel modules

 Reporting of repository content, discovered versions, and recommended installation set per target
as both html and xml

Table 3. HP SUM updates for firmware types

Firmware types Supported by HP SUM

System ROM Yes

Yes, both server-based and directly to the iLO Management

iLO2 firmware
port

Broadcom NIC firmware Yes

Intel NIC firmware Yes, after firmware is available

Yes, in offline mode only because of NetXen NIC firmware

NetXen NIC firmware
limitations

PowerPIC firmware Yes, beginning with version 3.5.1

Smart Array controller firmware Yes

Yes, some older SATA hard drives require offline mode

SAS and SATA hard drive firmware behind Smart Array controllers

SAS and SATA hard drive firmware behind non- Smart Array No
controllers

Emulex, QLogic, and Brocade Fibre Channel host bus adapter Yes, in offline mode only because of HBA firmware
firmware limitations

Tape Blade firmware Yes

OA firmware Yes, online only

VC firmware Yes, online only beginning with version 3.5.0

HP StorageWorks MDS600 Yes, offline only beginning with version 3.6.0

HP 3Gb SAS BL switch firmware No

Important:
MDS600 firmware update requires HPSUM 3.6.0 or later and that ALL
blades in an enclosure that have Smart Array P700M controllers except the
blade doing the update must be turned OFF before the firmware update
process is initiated. MDS600 firmware can only be updated using the
Firmware Maintenance CD in offline mode.

Note:
The long-term goal is for HP SUM to address all of the firmware
components included in an enclosure including partner switches.

15
 The latest HP SUM User Guide is included in the Firmware Maintenance CD User’s Guide. To obtain
a copy of this PDF file, see ftp://ftp.hp.com/pub/c-products/servers/management/smartstart/ and
select the latest version of the FWCDUsersGuidex.xx.pdf.
HP SUM Minimum Requirements
To successfully deploy HP SUM on target systems based on a Microsoft Windows OS, the following
items must be available:
 A local administrative system with 512 MB of memory, running a supported Windows OS
 Sufficient hard-drive space of at least twice the file size of the components to be deployed
 WMI enabled

Note:
When attempting to use the remote deployment functionality of HP
SUM on any edition of Windows Server 2008, you must ensure that the
File and Print Services feature is enabled and that the File and Print
Services exception is enabled in the Windows firewall. Failure to do so
prevents HP SUM from deploying remote Windows target servers.

Note:
HP SUM requires a true administrator login (not an elevated RUN AS
administrator). If you are unable to perform the net use *
\\server\ADMIN$ for Windows target servers, you do not have sufficient
privileges to run HP SUM.

To successfully deploy HP SUM on target systems based on a Linux OS, the following items must be
available:
 A local administrative system with 512 MB of memory, running a supported Linux OS
 glibc 2.2.4-26 or later
 gawk 3.1.0-3 or later
 sed 3.02-10 or later
 pciutils-2.1 .8-25.i386.rpm or later

To successfully update HP SUM on remote target systems based on a Linux OS, the following items
must be available:
 tcl-8.x package
 tcl-5.x package
 expect-5.x package

To successfully execute HP SUM on any local or remote target systems running a SUSE Enterprise
Linux 11 OS on x86 or x64 architectures, the following library must be available:
 compat-libstdc++-296-2.96-1 32.7.2.i386.rpm or another compatibility library that provides the
/usr/lib/libstdc++-libc6.2-2.so.3 file

Without this library, HP SUM does not complete discovery and returns Discovery Failed messages.

16
Note:
Beginning with the Firmware Maintenance CD v8.50, HP SUM no longer
runs on SUSE Enterprise Linux 9.

Note:
To perform remote Linux deployments, a root equivalent user account must
be used.

Note:
SSH support must be enabled and the firewall opened to allow SSH
communications on remote Linux servers or HPSUM cannot deploy updates.
By default, SUSE LINUX Enterprise Server 10 and 11-block SSH support
through the firewall. To enable SSH support if it has been disabled in the
firewall, use the yast2 command to open the necessary ports in the Linux
firewall.

Important:
The HP SUM does not support cross-platform deployments (for example,
deployments from Linux systems to Windows systems).

HP SUM Execution Modes

HP SUM provides three modes of execution for users: GUI, express, and silent. The express mode is
for software (drivers, agents and tools)deployments only. This means that there are two HPSUM
modes available for firmware deployment: GUI and silent. HP SUM provides scripted deployments in
silent mode. HP SUM also enables you to use either mode to handle both local and remote
deployments. HP SUM can run in both standard Windows and Linux OSs in online mode and in
offline mode via special boot environments based on Linux boot kernels and WinPE as long as all the
prerequisites are met as stated above.
Use Table 4 to help determine the correct execution mode for the server use case.
Table 4. Server execution mode
Scenario Description HP SUM command to HP tool to use
use*

Interactive, graphical Use this scenario when you: Windows: Online:

deployment on a local host Are not familiar with command hpsum HP BladeSystem Online
(run HPSUM on the server line tools Firmware Bundles for
being updated) Linux: Windows and Linux
Are deploying components on a
local, single host ./hpsum or
Do not require scripting HP Firmware Maintenance
CD
Want to choose the components
to be installed Offline:
HP Firmware Maintenance
CD

Scripted deployment on a Use this scenario when you: Windows: Online:

local host (run HPSUM from a Are familiar with command line hpsum -s HP BladeSystem Online
network share on a local tools Firmware Bundles for
server) Windows and Linux or
Are deploying components on a Linux:
local, single host ./hpsum –s HP Firmware Maintenance
Must perform a customized, CD
scripted deployment Offline:
Are unable to unlock the None
required HP SUM network ports
for remote deployment

17
 Scenario Description HP SUM command to HP tool to use
use*

Interactive, graphical Use this scenario when you: Windows: Online:

deployment to a remote host Are not familiar with command hpsum -target Target1 - HP BladeSystem Online
(run HPSUM from a line tools target Target2 -username Firmware Bundles for
workstation and update a User1 -password PW1 Windows and Linux or HP
Do not require scripting
remote host over the network Firmware Maintenance CD
Want to choose the components Linux:
via the GUI)
to be installed ./hpsum -target Target1 - Offline:

Need to update multiple targets target Target2 -username None

including OA, VC and Server- User1 -password PW1
based firmware
Note:
Need to select individual
firmware to update Targets can be a server,
OA, iLO, or VC IP
Need to select individual
address or DNS name.
hardware devices to be
updated

Scripted deployment to a Use this scenario when you: Windows: Online:

remote host Are familiar with command line hpsum -s -target Target1 - HP BladeSystem Online
(run HPSUM from a tools target Target2 -username Firmware Bundles for
workstation and update a Must perform a customized, User1 -password PW1 Windows and Linux or HP
remote host over the network scripted deployment Linux: Firmware Maintenance CD
via scripts) Offline:
Need to update multiple targets ./hpsum -s -target Target1
including OA, VC and Server- -target Target2 -username None*
based firmware User1 -password PW1
Need to update an entire *The HP BladeSystem FDT
enclosure’s firmware can be scripted to provide
remote, offline deployment
capabilities, but the FDT is
not scriptable within
HPSUM.

Automatic Deployment to one Use this scenario when you: The HP BladeSystem FDT Online:
or more servers in a HP Do not have an OS installed on takes care of this None
BladeSystem enclosure a server blade automatically
Offline:
(use the HP BladeSystem FDT Want an automatic way to HP BladeSystem FDT
with embedded HPSUM to deploy firmware updates
deploy firmware updates to
Do not require log files or user
one or more blades)
interaction with the installation
process
Want to update multiple blades
in an enclosure in a single
operation

Update an existing enclosure This is the same scenario as Windows: Online:

manually shown in the Interactive, hpsum HP BladeSystem Online
graphical deployment to a Linux: Firmware Bundles for
remote host or Scripted ./hpsum Windows and Linux or
deployment to a remote host HP Firmware Maintenance
scenarios discussed above CD
Offline:
HP BladeSystem FDT
* For details on specific HP SUM command-line options and their usage, see Using HP SUM in Scripted or Silent mode.

For more information about each of these scenarios, other HP SUM command-line parameters, and
HP SUM return codes, see Using HP SUM in GUI mode or Using HP SUM in scripted or silent mode
or review the Firmware CD User’s Guide at ftp://ftp.hp.com/pub/c-
products/servers/management/smartstart/.

18
Note:
For information on updating the 3 Gb SAS BL switch firmware, see Virtual
SAS Manager.

VCSU
HP BladeSystem c-Class VCSU enables you to perform the following tasks.
 Upgrade VC Ethernet and VC-FC firmware modules
 Perform other maintenance tasks remotely on VC Ethernet and Fibre Channel modules installed in
both the HP BladeSystem c-Class c7000 and c3000 enclosures using a standalone Windows or
Linux-based command-line utility

When the utility initiates a firmware upgrade process, all modules can be updated at the same time,
or the updates can be alternated between left and right modules so that network and SAN
connectivity is not disrupted during the upgrades. The utility displays a progress message indicating
that an update is in progress and the percentage completed. After the module firmware updates are
complete, the utility activates all modules. The VCSU also minimizes any downtime time in the network
fabric and might eliminate it altogether if the VC modules are installed in redundant pairs.

Note:
Currently, the VCSU can only update VC Ethernet and Fibre Channel
modules. The VCSU cannot update other types of firmware in an enclosure.

Follow these steps to locate the latest version of VCSU.

1. Go to www.hp.com.
2. Click Support and Drivers.
3. Press the Download drivers and software (and firmware) button.
4. Enter HP BladeSystem c-Class VCSU in the blank space, and then press Enter.
5. Select the VC module type.
6. Select the OS for updating the VC.

The latest VCSU utility is located in the Utility Tools section.

Follow these steps to locate the latest VC firmware.
1. Go to www.hp.com.
2. Click Support and Drivers.
3. Press the Download drivers and software (and firmware) button.
4. Type HP BladeSystem c-Class VCSU in the blank space, and then press Enter.
5. Select the VC module type.
6. Select a Server OS (not XP or Vista).

The latest VC firmware components and binary files for use with VCSU are available in the
Firmware—Blade Infrastructure section on the www.hp.com website.

19
 Table 5. Supported modes for updating VC Ethernet or Fibre Channel module
VC Update Scenario Description Update Tool to Use HP Tool to Use

Interactive, graphical Use this scenario when you: HP SUM* HP BladeSystem Online
deployment to VC modules in Are not familiar with command Firmware Bundles for
a single enclosure line tools Windows and Linux

Are deploying components on a

local, single host
Do not require scripting

Scripted deployment to VC Use this scenario when you: VCSU HP BladeSystem Online
modules in a single enclosure Are familiar with command line Firmware Bundles for
tools Windows and Linux

Are deploying components to a --------------------------------------------------------

single enclosure Note:
Must perform a customized, VCSU can also be found
scripted deployment by extracting the VC
Are unable to unlock the firmware component
required HP SUM network ports contained within the above
for remote deployment bundles.
--------------------------------------------------------

Interactive, graphical Use this scenario when you: HP SUM HP BladeSystem Online
deployment to VC modules in Are not familiar with command Firmware Bundles for
multiple enclosures line tools Windows and Linux

Do not require scripting

Want to choose the version to
be installed
Need to select individual
firmware to update

Scripted deployment to VC Use this scenario when you: VCSU can update HP BladeSystem Online
modules in multiple Are familiar with command line multiple VCs one-at-a-time Firmware Bundles for
enclosures tools via standard scripting Windows and Linux

Must perform a customized, --------------------------------------------------------

HP SUM* can update
scripted deployment Note:
multiple VCs in parallel
Need to update multiple VCs in VCSU can be found by
multiple enclosures extracting the VC firmware
component contained
within the above bundles.
--------------------------------------------------------
*HP SUM can only be used to update VC firmware from 1.20 or later to 2.10 or later. HP SUM cannot downgrade or rewrite VC firmware. The
VCSU must be used to install an earlier version of VC firmware.

Note:
If updating to a version of VC firmware earlier than version 2.10, VCSU
must be used in all circumstances.

Note:
HP SUM 3.5.0 or later is required to support VC firmware updates.

Note:
HP SUM 3.6.2 or later is required to support upgrades to VC firmware
2.12 and later.

For information on how to deploy VC firmware by using VCSU or HP SUM, click the highlighted tool
name or go to Scenario 3A: Updating the VC firmware using VCSU or Scenario 3B: Updating the VC
firmware using the HP SUM.

20
Single smart components
HP provides almost all firmware updates as individual smart components. In most cases, individual
smart components are available for both Windows and Linux environments. Individual smart
components, except VC firmware, have an embedded installer that checks basic dependencies
including supported OS, presence of required hardware, and enforcement of limited advanced
dependencies known for the individual component.
The smart components for VC firmware update must use HP SUM. Individual smart components can
be used in almost any deployment scenario. However, certain limitations exist, such as some firmware
updates needing to be managed offline, and can limit effectiveness. Most smart components support
only local deployment but can be integrated with other deployment tools to support deployment on
remote servers.
Table 6. Firmware smart component capabilities
Firmware types Online Offline Local Remote Is firmware staged for
next reboot or to activate
immediately?

System ROM X X X Staged

iLO2 firmware X X X X (Can be deployed to Immediate

iLO 2 when using
HP SUM to deploy this
firmware)

Broadcom NIC firmware X X X Staged

Intel NIC firmware X X X Staged

NetXen NIC firmware X X Staged

PowerPIC firmware X X X Staged

Smart Array controller X X X Staged

firmware

SAS and SATA hard drive X(Some older X X Staged

firmware behind Smart SATA drives may
Array controllers be offline only)

Not currently supported

SAS and SATA hard drive
firmware behind non-
Smart Array controllers

Emulex, QLogic, and X X Staged

Brocade Fibre Channel
host bus adapter firmware

Tape Blade firmware X X X Immediate

21
 Firmware types Online Offline Local Remote Is firmware staged for
next reboot or to activate
immediately?

OA firmware X X (Can be updated stand- Immediate

alone or by HP SUM)

VC firmware X X (Can be updated by Immediate

VCSU, HP SUM, or
through web browser)

HP StorageWorks MDS600 X X Immediate

HP 3Gb SAS BL Switch X X (Must be updated by Immediate

firmware using Virtual SAS
Manager [VSM])

*Individual components normally require another application like VCSU or HP SUM to deploy them to remote target servers and hosts. In
some instances, components have embedded support to deploy themselves remotely.

Important:
MDS600 firmware update requires HPSUM 3.6.0 or later and that ALL
blades in an enclosure that have Smart Array P700Mcontrollers except the
blade doing the update must be turned OFF before the firmware update
process is initiated. MDS600 firmware can only be updated using the
Firmware Maintenance CD in offline mode.

Note:
Staged firmware means the firmware is written to the chipset, but not
activated until the next reboot. Any firmware that is staged can be
installed together and activated at a later time.

It is not a best practice to use individual components to upgrade HP BladeSystem enclosure firmware.
Use installation tools such as HP SUM and VCSU to deploy components because these tools
understand the dependencies between components and installation limitations. These limitations and
dependencies can include certain components supporting only offline deployment, validating that the
correct driver is installed, ordering VC module updates to minimize any network outages.

HP SIM and Version Control Agent

HP provides a free CMS named HP SIM and one of its key features is the ability to version control
software and firmware on multiple target servers. HP SIM enables you to quickly determine whether or
not a server is in alignment with a given baseline. With the SIM built-in report generation capabilities,
you can quickly generate reports that show which servers are out of date.

22
Currently, SIM uses VCRM and VCA to handle version control in the SIM 5.x and earlier versions. The
VCRM must be installed on a server running Microsoft Windows Server 2003/2008 and must have
internet access to be able to automatically download the latest bundles and PSPs. The VCA must be
running on each target server that is to be managed by SIM. The VCA is available in both Windows
and Linux versions. Using the current version control infrastructure, SIM is able to deploy firmware
updates for a limited number of firmware types as listed in Table 7.
Table 7. Available firmware updates

Firmware types Online Offline

SIM 5.x SIM 5.x

System ROM X

iLO2 firmware X

Broadcom NIC firmware

Intel NIC firmware

NetXen NIC firmware

PowerPIC firmware

Smart Array Controller firmware X

SAS and SATA hard drive firmware behind Smart Array controllers X

SAS and SATA hard drives behind non-Smart Array Controllers

(supported by HP SUM in 1Q10)

Emulex, QLogic and Brocade Fibre Channel host bus adapter

firmware

OA firmware

Tape Blade firmware

VC firmware

HP StorageWorks MDS600

HP 3Gb SAS BL switch firmware

Note:
SIM 5.x cannot be used to update firmware on network based targets such
as the OA, ILO, or VC.

Important:
600 firmware update requires HPSUM 3.6.0 or later and that ALL blades
in an enclosure that have Smart Array P700M controllers except the blade
doing the update must be turned OFF before the firmware update process is
initiated. MDS600 firmware can only be updated using the Firmware
Maintenance CD in offline mode.

23
 Because of the reduced coverage of the current SIM 5.x version control firmware update, SIM is not
recommended for maintaining BladeSystem firmware today.
When it becomes available, SIM 6.0 will have significantly improved firmware update capabilities,
including the ability to update network-based targets such as the OA and iLO. SIM is providing this
capability by building on top of the HP Smart Update Technology, specifically HP SUM. Over the next
several releases, additional functionality will be added to HP SIM and HP SUM that will enable
updates to be pulled dynamically from the web, baselines to be set for non-server based targets such
as OAs, iLOs, and VCs, the ability to set maintenance windows, and the ability to mass deploy
updates in enterprise environments.
The SIM 6.0 release also removes the requirement for the VCRM and VCA because SIM will be able
to leverage HP SUM directly without requiring additional infrastructure. While the current version
control architecture will be supported for several more years, the version control architecture will be
transitioned to SIM leveraging HP SUM instead of the VCRM and VCA. With the improved firmware
update capabilities this provides SIM 6.0, SIM can now be recommended as a possible option for
updating and managing firmware for enterprise environments. As Table 8 describes, SIM 6.0 will
have much better firmware coverage than the current SIM 5.x product.
Table 8. SIM 6.0 online/offline firmware updates

Firmware Types Online Offline

SIM 6.0 SIM 6.0

System ROM X

iLO2 firmware X

Broadcom NIC firmware X

Intel NIC firmware X

NetXen NIC firmware

PowerPIC firmware X

Smart Array Controller firmware X

SAS and SATA hard drive firmware behind Smart Array controllers X

SAS and SATA hard drives behind non-Smart Array Controllers

(supported by HPSUM in 1Q10)

Emulex, QLogic and Brocade Fibre Channel HBA firmware

OA firmware X

Tape Blade firmware X

VC firmware

HP StorageWorks MDS600

HP 3Gb SAS BL switch firmware

With the updated firmware capabilities of SIM 6.0, all BladeSystem firmware that HP SUM is capable
of updating online will be available for deployment in SIM.

24
Important:
MDS600 firmware update requires HPSUM 3.6.0 or later and that ALL
blades in an enclosure that have Smart Array P700Mcontrollers except the
blade doing the update must be turned OFF before the firmware update
process is initiated. MDS600 firmware can only be updated by using the
Firmware Maintenance CD in offline mode.

Virtual SAS Manager

The VSM is used to update the firmware on the HP StorageWorks 3Gb SAS BL Switch for HP
BladeSystem c-Class enclosures. The HP StorageWorks 3Gb SAS BL Switch for HP BladeSystem c-
Class enclosures is an integral part of an HP direct connect SAS storage solution, providing a straight
forward architecture for external zoned direct attach as well as shared SAS storage. BladeSystem
server administrators now have a simple in-rack SAS storage solution that’s ideal for growing
capacity requirements—without the need to coordinate storage requirements with SAN administrators.
The SAS architecture combines a P700m Smart Array in each server, and 3 Gb SAS BL switches
connected to HP StorageWorks MDS600 or MSA2000sa SAS storage devices. The simplicity of SAS
results in a very low cost per GB, enabling low cost zoned or shared SAS storage.

Note:
When updating the firmware for the HP StorageWorks 3GB SAS BL Switch,
you must use VSM. Neither HP SUM nor VCSU is capable of updating this
firmware.

The firmware is updated by browsing to OA, opening VSM, uploading a binary image file and
selecting to update the firmware.

Important:
When using the VSM along with full-height blade servers residing in the HP
BladeSystem c3000 Enclosure, the Smart Array P700m must be installed in
mezz position 2. Installing the P700m controller in mezz position 3 of full
height blade servers in the c3000 enclosure is not supported at this time.
This issue will be corrected in a future release of the VSM software.

Important:
When two 3 Gb SAS BL switches are installed in the same row of an
enclosure, make sure that they are running the same firmware version.

Table 9. Deployment tools for online/offline modes

Deployment tool to use Online mode Offline mode

Interactive mode Upload bin file through the VSM Not supported
is currently the only method to
upgrade this firmware

Scripted or automated mode Not supported Not supported

25
 Follow these steps to update the firmware for the 3G SAS BL switch.
1. Download the firmware image for the 3G SAS BL switch to a workstation with network access
to the c-Class enclosure OA.
Locate the latest firmware image by browsing to www.hp.com and searching for 3G SAS BL
Switch firmware (Image File).

Note:
Firmware versions less than 2.0.0.0 only provide single open
zone support. By default, all blade servers have access to all
storage connected to the switch. This configuration is pre-
configured and cannot be altered. To restrict access to the
storage, use features included in your storage management
software.

Note:
Firmware versions 2.0.0.0 and higher support multi-zone
support. By default, for servers to access storage, switch-port or
drive-bay zone groups must be created. Zone groups provide
user-defined isolation within the switch.

2. Schedule a maintenance window to perform the firmware update, stop all traffic passing
through the switch, and turn off all servers and storage enclosures that connect to the switch.
3. Log in to OA as an administrator, and open the VSM for the 3G SAS BL Switch.
4. In the VSM Systems and Devices tree, choose the SAS switch to update, and then select Update
Firmware from the Available Tasks list.
5. Provide the path to the firmware image file, or press the Browse button to locate the firmware
image on the local machine, a mapped drive, or a network share, and then click OK to begin
the firmware update process.
6. When the firmware update is complete, select Reset Blade Switch under Available Tasks, and
then select Reset Now.
7. For configurations containing more than one 3G SAS BL Switch, repeat the firmware update
process to update the firmware on the other switch modules.

Note:
After updating the firmware, you must delete any temporary
internet files from the browser cache before logging back into OA
or VSM.

Obtaining the latest available HP firmware update tools

HP has introduced the concept of firmware release sets so that administrators can be aware
of what HP has tested together as an integrated solution set. Previously, firmware updates had been
released as required by the various product teams. However, because of the complexity of
integrating the various firmware updates, bundles are now the recommended method to update
HP BladeSystem firmware. The firmware release sets are based on the HP BladeSystem Firmware
Compatibility chart (http://www.hp.com/go/bladesystemupdates) and are updated
approximately once a quarter.

26
To obtain firmware updates based on these release sets for HP BladeSystem products, use the
following tools that contain the same release set versions:
 HP BladeSystem Firmware Update Bundles
 HP BladeSystem FDT
 HP Firmware Maintenance CD

Note:
Individual smart components might still be released when critical updates
are required and will be integrated into the next release of the Firmware
Update Bundles, FDT, and Firmware Maintenance CD.

Choosing the deployment tool

Table 10 lists the recommended deployment type for online/offline support.
Table 10. Deployment types
Deployment type Online support Offline support

Local Firmware Maintenance CD Firmware Maintenance CD

BladeSystem Firmware Update BladeSystem FDT
Bundles

Remote Firmware Maintenance CD BladeSystem FDT

BladeSystem Firmware Update
Bundles

Bare-metal (no Not applicable Firmware Maintenance CD

OS installed on server) BladeSystem FDT

Single server Firmware Maintenance CD Firmware Maintenance CD

BladeSystem Firmware Update BladeSystem FDT
Bundles

1-to-many Firmware Maintenance CD

BladeSystem FDT (using iLO Virtual
BladeSystem Firmware Update Media or c3000 DVD drive)
Bundles

Network-based targets (OA, VC) Firmware Maintenance CD None

BladeSystem Firmware Update
Bundles

From another perspective, Table 11 identifies the correct tool to use depending on the update
scenario. Table 11 also describes the limitations of each scenario.
Table 11. Tool based on scenario
Scenario Description Limitations

I want to automatically update the Recommended deployment tool to use: Using this method updates all
server firmware offline  HP BladeSystem FDT firmware in an enclosure with
the exception of OA and VC
Ethernet and Fibre Channel
Use this scenario when you: modules.
 Want an automated way to update a blade
 Do not need to update infrastructure Using the HP SUM pull-from-
firmware at the same time web feature to pull the latest
 Want to leverage the BladeSystem enclosure updates is not supported in

27
 Scenario Description Limitations
ability to load an ISO image to multiple offline environments.
server concurrently
 Do not need feedback during the update
process
 Do not need log files at the conclusion of the
installation for archival or debug purposes
 Need to support devices that are only
updateable off line
 Need to simultaneously update firmware on
multiple server blades

I want to update the server firmware Recommended deployment tool to use: Using this method updates all
offline but prefer a graphical  HP Firmware Maintenance CD (FWCD) firmware in an enclosure with
installation or manual method the exception of OA and VC
Ethernet and Fibre Channel
Use this scenario when you: modules.
 Want to manually update server blade
firmware
Using the HP SUM pull-from-
 Do not want to do this under your normal web feature is not supported in
operating environment offline environments.
 Need to flash firmware for devices that are
only updateable offline
 Do not need to update infrastructure
firmware at the same time
 Are not familiar with the OA web
interface
 Only need to update a single blade server
within an enclosure
 Only need to update firmware for a single
device

I want to update the server firmware Recommend deployment tool to use: Using this method, all firmware
online to a single server network-  HP BladeSystem bundle for Windows except the following can be
based host, such as the OA, iLO2 and updated:
 HP B lad e Syst em B und le fo r Li nux
VC Ethernet and Fibre Channel NetXen NIC
Modules  HP Firmware Maintenance CD (FWCD)
Emulex FC HBA
QLogic FC HBA
Use this scenario when you:
Brocade FC HBA
 Want to manually update server blade
firmware These types of firmware must
be updated offline using either
 Do not want to do this under your normal
the BladeSystem FDT or the HP
operating environment
Firmware Maintenance CD.
 Need to flash firmware for devices that are
only updateable offline
 Do not need to update infrastructure
firmware at the same time
 Are not familiar with t he OA web
interface
 Only need to update a single blade
server within an enclosure

I want to update the server firmware Recommend deployment tool to use: Using this method, all firmware
online to multiple servers and network-  HP BladeSystem Bundle for Windows except the following can be
based host such as OA and iLO 2. updated:
 HP BladeSystem Bundle for Linux
 NetXen NIC
 HP Firmware Maintenance CD (FWCD)
 Emulex FC HBA
 QLogic FC HBA
Use this scenario when you:
 Brocade FC HBA
 Want to manually update server tabs, OA,

28
Scenario Description Limitations
or iL0 2 firmware
 Want the option to script updates to a single These types of firmware must
or to multiple servers and enclosures be updated offline using either
 Need to update infrastructure firmware the BladeSystem FDT or the HP
Firmware Maintenance CD.
 Are not familiar with the OA web interface
 Need to minimize downtime across the
enclosure
 Want to stage updates so blades can be
rebooted at a later time to activate the new
firmware
 Need to update many servers simultaneously

I want to update the VC firmware Recommended deployment tools to use: If updating from VC firmware
 (VCSU versions before 1.34, the VC
firmware must be updated
 HP BladeSystem Bundle for Windows
before the OA firmware.
 HP BladeSystem Bundle for Linux

For VC firmware versions 1.34

Use this scenario when you: and later, the update order
 Want to manually update VC Ethernet and between the OA and VC is not
Fibre Channel Module firmware important
 Want to update a single VCSU
 Want to update multiple VC domains
simultaneously (HP BladeSystem Bundles)

HP BladeSystem Firmware Update Bundles

The HP BladeSystem Online Firmware Bundles for Windows and Linux are a collection of HP SUM,
firmware smart components and the latest available driver smart components from the Windows and
Linux PSPs that have been tested together to ensure compatibility. The driver smart components are
provided as a convenience for those who might not want to deploy a full PSP but need the drivers to
perform firmware update operations. BladeSystem Firmware Update Bundles are for use by those who
already have an installed OS on a server and just want to update the firmware to the latest available
level. These BladeSystem Firmware Update Bundles require an OS installed on each target server.
These bundles are for online deployment in either a local or remote scenario using HP SUM to deploy
the updates, enforce limitations, and move the components to remote targets.
For deployment details, see the Firmware deployment scenarios and Installation scenarios.
The BladeSystem Firmware Update Bundles are intended to be deployed from a Windows or Linux
workstation, PC, or server to servers running a supported version of the same OS. Deployment from a
Windows workstation to a Linux server or from a Linux server to a Windows workstation is not
supported.
For workgroup-level deployments of up to 29 servers or network-based devices such as OA and iLO2,
HP SUM should be used to update firmware. For enterprise-level deployment scenarios requiring
deployment to more than 29 servers concurrently, these BladeSystem Firmware Update Bundles can
be integrated with the version control software provided by HP SIM. However, additional limitations
exist when including these bundles with HP SIM version control infrastructure beyond what is listed in
the following table. These limitations include the inability to deploy OA and VC firmware updates and
the inability to deploy iLO2 firmware through the iLO management port. The HP SIM team is
addressing these limitations and plans to resolve them by integrating HP SUM into their version
control infrastructure.

29
 Note:
HP supports the current and two previous versions of the BladeSystem
Firmware Update Bundles as indicated in the HP BladeSystem Firmware
Compatibility chart.

These BladeSystem Firmware Update Bundles allow you to update the BladeSystem firmware that is
listed in Table 12.
Table 12. BladeSystem firmware update bundles
Firmware types Supported by HP BladeSystem Firmware Update Bundle (Online only,
supports both local and remote deployment)

System ROM Yes

iLO 2 firmware Yes, both server-based and directly to the iLO Management port

Broadcom NIC firmware Yes

Intel NIC firmware Yes, when the firmware becomes available

NetXen NIC firmware No

PowerPIC firmware Yes, beginning with bundle 1.60 released in July 2009

Smart Array controller firmware Yes

SAS and SATA hard drive firmware behind Yes, some older SATA drives might not be supported if they are for
Smart Array controllers offline only deployment

SAS and SATA hard drive firmware behind non- No

Smart Array controllers

Emulex, QLogic, and Brocade Fibre Channel No

host bus adapter firmware

Tape blade firmware Yes

OA firmware Yes

VC firmware Yes, beginning with bundle 1 .60

HP StorageWorks MDS600 No

HP 3Gb SAS BL switch firmware

No

Important:
MDS600 firmware update requires HPSUM 3.6.0 or later and that ALL
blades in an enclosure that have Smart Array P700Mcontrollers except the
blade doing the update must be turned OFF before the firmware update
process is initiated. MDS600 firmware can only be updated using the
Firmware Maintenance CD in offline mode.

Important:
The HP 3Gb SAS BL switch firmware can only be updated by uploading a
bin file through the Virtual S AS Manager (VSM) product. This
firmware is currently delivered as a binary image file on the HP website
and must be downloaded and manually upgraded as it is not available on
any other tools discussed in this document.

30
Note:
Because HP BladeSystem Firmware Update Bundles do not provide the
ability to update all possible firmware types, additional deployment tools
must be used to ensure all firmware is updated within a BladeSystem
enclosure and to align with the HP BladeSystem Compatibility Chart. To
update the firmware that cannot be updated by HP BladeSystem Firmware
Update Bundles, use the BladeSystem FDT or the HP Firmware Maintenance
CD. The latest version can be obtained from
http://www.hp.com/go/bladesystemupdates/.

HP BladeSystem FDT
The HP BladeSystem FDT is an offline-only ISO image containing a collection of HP SUM and
firmware smart components that have been tested together to ensure compatibility. The FDT has been
designed for those servers that do not have an installed OS yet or that want an unattended
method of deploying firmware in an offline environment. As presented in Scenario 6, the FDT
can be scripted for remote deployment to multiple servers using the iLO Advanced Lic ense feature
for scripted virtual media.
Because the FDT requires you to boot to it, the server must be taken offline for the period of time
required to complete the firmware update.
When you boot to the FDT, all feedback is provided through the UID lights. While the update process
is running, the UID light blinks. Upon completion, the UID light is set to one of two states:
 If the UID light is off, the update process has completed and the server OS can be installed or the
server restarted to its previous OS.
 If the UID light is solid, a firmware update failure has occurred requiring user attention. The user
should either plug in the KVM dongle or use iLO Remote Console support to browse into the
affected server to determine the cause of the failure. The FDT loads the error log into a vi edit for
review.

HP highly recommends that the issue causing the failure be resolved before installing or restarting the
OS to prevent issues that could affect server operation. For more information on how to handle
various firmware update failure scenarios, see Troubleshooting HP BladeSystem FDT.
The FDT was designed with limited user intervention and feedback in mind. To log files or feedback
beyond the UID lights, use other firmware update tools such as the HP Firmware Maintenance CD.

Important:
Prior to iLO firmware version 1.79, using the iLO Remote Console while the
iLO firmware was being updated could corrupt the iLO firmware image
and prevent the server from rebooting after a firmware update operation. It
is strongly recommended that if the iLO Remote Console not be used to
browse into a blade updating firmware if the UID light is blinking to prevent
this condition from occurring.

Note:
Use OA version 2.51 or later to get a list of all major firmware versions
deployed in your enclosure by using the Rack Firmware link on the main
OA web page.

31
 Note:
HP supports the current and two previous versions of the BladeSystem FDT.

Table 13 lists the HP BladeSystem FDT used to update the BladeSystem firmware.

Table 13. Supported firmware types

Firmware types Supported by HP BladeSystem FDT

System ROM Yes

iLO 2 firmware Yes

Broadcom NIC firmware Yes

Intel NIC firmware Yes, beginning with 1 .70

NetXen NIC firmware Yes, beginning with 1 .70

PowerPIC firmware Yes, beginning with 1 .70

Smart Array controller firmware Yes

SAS and SATA hard drive firmware behind Smart Array controllers Yes

SAS and SATA hard drive firmware behind non-Smart Array controllers No

Emulex, QLogic, and Brocade Fibre Channel host bus adapter firmware Yes

Tape blade firmware Yes

OA firmware No

VC firmware No

HP StorageWorks MDS600 No

HP 3Gb SAS BL switch firmware No

The latest version can be obtained from http://www.hp.com/go/bladesystemupdates.

Important:
MDS600 firmware update requires HPSUM 3.6.0 or later and that ALL
blades in an enclosure that have Smart Array P700Mcontrollers except the
blade doing the update must be turned OFF before the firmware update
process is initiated. MDS600 firmware can only be updated using the
Firmware Maintenance CD in offline mode.

Important:
The HP 3Gb SAS BL switch firmware can only be updated by uploading a
bin file through the Virtual SAS Manager (VSM) product. This firmware is
currently delivered as a binary image file on the HP website and must be
downloaded and manually upgraded as it is not available on any other
tools discussed in this document.

32
HP Firmware Maintenance CD
The HP ProLiant Firmware Maintenance CD provides a collection of HP SUM and firmware in an ISO
image that can be used either in an offline, interactive mode, or online in either a scripted or
interactive mode. The Firmware Maintenance CD provides firmware for supported HP servers and
options. The Firmware CD contains all the firmware for the BladeSystem enclosures with the exception
of the VC firmware. The VC firmware is not available on the Firmware Maintenance CD because of
its size and limited space on the CD.
In offline mode, the Firmware Maintenance CD boots a small Linux kernel and enables firmware
updates to take place on a single server using the embedded HP SUM software. Because of the
special boot environment, support for remote servers and hosts is not available.
In online mode, you can leverage the autorun utility to launch HP SUM or browse the CD to the
\compaq\swpackages directory and execute it directly.

All firmware smart components are placed in the \compaq\swpackages directory for use by HP SUM.
If you require additional firmware smart components, copy the Firmware Maintenance CD to a USB
key, and then add these additional components to the \compaq\swpackages directory. If HP SUM
supports the type of firmware added, it is automatically picked up the next time HP SUM is executed.
For more information on the firmware update process using the HP Firmware Maintenance CD and
HP SUM, see the Firmware CD User Guide. The latest HP SUM User Guide is included in the
Firmware CD User’s Guide. To obtain a copy of this PDF file, see ftp://ftp.hp.com/pub/c-
products/servers/management/smartstart/ and select the latest version of the
FWCDUsersGuidex.xx.pdf.

Note:
Use OA 2.51 or later to get a list of all major firmware versions deployed
in your enclosure using the Rack Firmware link on the main OA web page.

Note:
HP supports the current and two previous versions of the Firmware
Maintenance CD.

The Firmware Maintenance CD provides the means to update the following BladeSystem firmware.
Table 14 lists the firmware types that are supported by the HP Firmware Maintenance CD.
Table 14. Firmware support
Firmware types Supported by HP Firmware Maintenance CD

System ROM Yes

iLO 2 firmware Yes, local and remote

Broadcom NIC firmware Yes

Intel NIC firmware No

NetXen NIC firmware No

PowerPIC firmware Yes, beginning with Firmware Maintenance CD 8.60

Smart Array controller firmware Yes

SAS and SATA hard drive firmware behind Smart Yes

Array controllers

SAS and SATA hard drive firmware behind non- No

Smart Array controllers

33
 Firmware types Supported by HP Firmware Maintenance CD

Emulex, QLogic, and Brocade Fibre Channel HBA Yes, offline only
firmware

Tape blade firmware Yes

OA firmware Yes, online only

VC firmware Yes, online only and components must be downloaded from the web and
added to the CD
HP StorageWorks MDS600 Yes, offline only (see important note below for more details of special
requirements to update this firmware type)
HP 3Gb SAS BL switch firmware
No

Important:
MDS600 firmware update requires HPSUM 3.6.0 or later and that ALL
blades in an enclosure that have Smart Array P700Mcontrollers except the
blade doing the update must be turned OFF before the firmware update
process is initiated. MDS600 firmware can only be updated using the
Firmware Maintenance CD in offline mode.

Important:
The HP 3Gb SAS BL switch firmware can only be updated by uploading a
bin file through the Virtual SAS Manager (VSM) product. This firmware is
currently delivered as a binary image file on the HP website and must be
downloaded and manually upgraded as it is not available on any other
tools discussed in this document.

Note:
Because firmware might be able to update only in online or offline mode
for some components, you might need to execute the HP Firmware
Maintenance CD both online and offline to update all the firmware in an
enclosure.

Note:
VC firmware components are not shipped on the HP Firmware
Maintenance CD because of their size (approximately 50 MB per
component). However, if the VC firmware components are downloaded
from www.hp.com, they can be added to the Firmware Maintenance CD
by creating a USB key using the USB Key Utility. The latest version can be
obtained from http://www.hp.com/go/bladesystemupdates.

Recommended methods to deploy individual firmware types

While the deployment tools such as HP SUM remove much of the complexity of the actual firmware
update process, there are times when it is necessary to understand the underlying process required to
update individual firmware components. The best practice is still to use the deployment tools to update
individual firmware components. The following section provides the recommended methods for
deploying individual firmware types. The section also includes information about specific issues that
you might encounter while updating the different types of firmware. Recommended deployment tools

34
are indicated as a cross-reference to use when planning updates for these individual firmware types
for the various operational modes.

System ROM
System ROM firmware is staged and not immediately activated upon update. This means that the
firmware image is written to the physical ROM chip in the server but will not be activated until the
server is rebooted. While it is recommended that a reboot occur as soon as possible to activate new
firmware, there is no harm in leaving the System ROM image deployed and rebooting the server
during a later maintenance window.
System ROM Firmware can be updated using the version of HP SUM provided in the HP BladeSystem
Firmware Update Bundles for Windows or Linux if an OS has already been installed on the blade.
If an OS has not yet been installed and you want an automated method of installation, use the HP
BladeSystem FDT. HP SUM is embedded within the tool and updates the System ROM if an update is
required during the silent, automated firmware update process provided by the FDT.
If an OS has not been installed and you want an interactive, offline method of installation, use the HP
Firmware Maintenance CD deployment tool. HP SUM is embedded within the tool and enables the
System ROM to be updated interactively.
Table 15. Deployment tools for online/offline modes
Deployment tools to use Online mode Offline mode

Interactive Mode HP BladeSystem Online Firmware HP Firmware Maintenance CD

Bundles for Windows and Linux in
GUI mode
HP Firmware Maintenance CD

Scripted or Automated Mode HP BladeSystem Online Firmware HP BladeSystem FDT

Bundles for Windows and Linux in
silent mode

Note:
While individual smart components are made available for System ROM
firmware updates, they are not recommended for update scenarios unless
absolutely necessary. If new smart components are released to resolve
critical issues, the components can be added to any of the tools above and
picked up by HP SUM automatically.

Note:
For information on how to add components to an existing tool, see How do
I add updated components to the HP BladeSystem FDT? or How do I add
updated components to the HP Firmware Maintenance CD?

iLO2 firmware
iLO2 firmware is activated immediately upon update of the iLO2 by resetting the iLO2. This reset
disconnects any virtual media devices and remote consoles through the iLO2. This reset normally
takes less than a minute to occur and does not affect the OS or any running applications. The server
does not need to be rebooted to activate the iLO2 firmware.

35
 Note:
HP does not recommend that you update the iLO2 firmware with the
Firmware Maintenance CD by using Virtual Media. The reset of the Virtual
Media is similar to pulling the media out of a drive and will result in the
Firmware Maintenance CD installation hanging because the media is no
longer available.

It is possible to use the BladeSystem FDT to update iLO2 firmware as it

creates a RAM drive and copies the files from the media into the RAM drive
before initiating the firmware update process. It is also possible to update
all other firmware except the iLO2 firmware by using the Firmware CD
through Virtual Media. This can be accomplished by deselecting the iLO
Firmware component on the HP SUM Select Items to Install screen.

iLO2 firmware can be updated by using the HP BladeSystem Firmware Update Bundles for Windows
or Linux in one of two ways.
 If the OS-specific iLO2 driver is installed, update the iLO2 firmware on a server with a running OS.
To deploy iLO2 firmware by this method, first install the OS-specific iLO2 driver using HP SUM and
the driver provided by the HP BladeSystem Firmware Update Bundles for Windows or Linux, or
from the HP (PSP. Then use HP SUM as provided in the BladeSystem Firmware Update Bundles to
update the firmware.
 When a workstation or server is connected to the same network as the iLO2 NIC Management Port,
update the firmware directly to the iLO2 NIC Management Port. To deploy iLO2 firmware by this
method, use the HP SUM to add the iLO2 Management Port as a target host and provide the iLO2
credentials when prompted. The iLO firmware update can also be scripted by passing the iLO IP
address or DNS name along with the iLO userid and password on the HP SUM command-line. HP
SUM must be in the -s or --silent mode to work in scriptable mode.

If an OS has not yet been installed and you want an automated method of installation, use the HP
BladeSystem FDT. HP SUM is embedded within the tool and updates the iLO2 firmware if an update
is required during the silent, automated firmware update process provided by the FDT.
If an OS has not been installed and you want an interactive, offline method of installation, use the HP
Firmware Maintenance CD deployment tool. HP SUM is embedded within the tool and enables the
iLO2 firmware to be updated interactively.
Table 16. Deployment tools for online/offline modes
Deployment tool to use Online mode Offline mode

Interactive Mode  HP BladeSystem Online Firmware HP Firmware Maintenance CD

Bundles for Windows and Linux in
GUI mode
 HP Firmware Maintenance CD

Scripted or Automated Mode HP BladeSystem Online Firmware HP BladeSystem FDT

Bundles for Windows and Linux in
silent mode

Note:
While individual smart components are made available for iLO2 firmware
upgrades, they are not recommended for upgrade scenarios unless
absolutely necessary. If new smart components are released to resolve
critical issues, the components can be added to any of the tools above and
picked up by HP SUM automatically.

36
Note:
HP SUM cannot update the iLO firmware from the web if the iLO driver is
not already loaded before starting the firmware update process. The iLO
driver must be present and running for HP SUM to detect the installed
version of iLO firmware. Failure to install the iLO driver before starting HP
SUM results in the iLO firmware component being placed in the No Device
Driver Found section and the need to run the HP SUM update again once
the iLO driver has been installed to properly update the iLO firmware.

Note:
New versions of the iLO firmware can be dropped into the
\compaq\swpackages directory and picked up by HP SUM
automatically. In Linux, you must leave the old version of the iLO firmware
in the directory for HP SUM to correctly detect the iLO firmware version.
While the latest iLO firmware component is installed, HP SUM needs the
older component to handle the version detection. Removal of the older
driver in Linux could cause HP SUM to be unable to detect the installed
version of iLO firmware and report that the iLO driver is not loaded. The
older iLO firmware component can be removed in Windows without any
issues.

Note:
For information on how to add components to an existing tool, see How do
I add updated components to the HP BladeSystem FDT? or How do I add
updated components to the HP Firmware Maintenance CD?

NIC firmware
Currently, the Broadcom NIC firmware is the only type of NIC firmware supported by HP. As
firmware for new NIC options is released, HP will also provide additional mechanisms for updating
the Intel and NetXen NIC firmware.
Broadcom and Intel NIC firmware can be updated using the HP BladeSystem Firmware Update
Bundles for Windows or Linux. However, the corresponding OS-specific NIC driver must be
previously installed. You can obtain a NIC driver by using the one available in the HP BladeSystem
Firmware Update Bundles for Windows or Linux or from the HP ProLiant Support Pack (PSP and then
use the HP BladeSystem Firmware Update Bundles to update the firmware.
If an OS has not yet been installed and you want an automated method of installation, use the HP
BladeSystem FDT regardless of the type of NIC firmware being updated. HP SUM is embedded within
the tool and updates the NIC firmware if an update is required during the silent, automated firmware
update process provided by the FDT.
If an OS has not been installed and you want an interactive, offline method of installation, use the HP
Firmware Maintenance CD deployment tool. HP SUM is embedded within the tool and enables the
NIC firmware to be updated interactively.
Table 17. Deployment tools for online/offline modes
Deployment tool to use—Broadcom Online mode Offline mode
and Intel NIC

Interactive Mode HP BladeSystem Online HP Firmware Maintenance CD

Firmware Bundles for Windows
and Linux in GUI mode
HP Firmware Maintenance CD

Scripted or Automated Mode HP BladeSystem Online HP BladeSystem FDT

Firmware Bundles for Windows
and Linux in silent mode

37
 In addition, for the Broadcom NICs, there are some special cases where depending on the
functionality of the adapter, different firmware may be preloaded on the adapter. An example of this
is the HP NC373i Multifunction Gigabit Sever Adapter and the HP NC373m Multifunction Gigabit
Server Adapter. The adapter is released in two forms. One form includes iSCSI support and is
versioned in the 1.x.x range. The same adapter is also available without iSCSI support and has
firmware versioned in the 4.x.x range. The NIC firmware component is intelligent enough to only load
the appropriate firmware on the adapter. Because of the different functionality the different types of
firmware enable, it is important to use the NIC firmware components and HP SUM to deploy the NIC
firmware and not attempt to update the firmware directly to prevent loss of functionality.
For the NetXen NIC firmware, the HP BladeSystem FDT or the HP Firmware Maintenance CD must be
used to update the firmware as the NetXen NIC firmware can only be updated in an offline manner.
Table 18. Deployment tools for online/offline modes
Deployment tool to use—NetXen NIC Online mode Offline mode

Interactive Mode Not Supported HP Firmware Maintenance CD

Scripted or Automated Mode Not Supported HP BladeSystem FDT

Note:
While individual smart components are made available for NIC firmware
updates, HP does not recommend them for update scenarios unless
absolutely necessary. If new smart components are released to resolve
critical issues, the components can be added to any of the tools above and
picked up by HP SUM automatically.

Note:
When downgrading or rewriting NIC firmware, use the GUI method or the
NIC firmware is not updated. This is because the HP SUM downgrade and
rewrite options require that the individual NIC adapters be selected even
after the force option has been enabled. This prevents downgrading
firmware on all adapters by default because some adapters can be de-
featured if their firmware is downgraded to a version that does not support
a given feature.

Note:
For information on how to add components to an existing tool, see How do
I add updated components to the HP BladeSystem FDT? or How do I add
updated components to the HP Firmware Maintenance CD?

PowerPIC or Power Management Controller firmware

PowerPIC or Power Management Controller firmware controls the power subsystem of the HP
BladeSystem enclosure and server blades. This firmware has a number of dependencies that must be
met before an upgrade can take place.
 Existing Power Management Controller firmware must be 0.7 or later. Version 0.5 does not need to
be flashed and cannot be flashed using any existing smart components or tools. Many older
BL460c G1, BL465c G1, BL480c G1 and BL685c G1 servers might be at version 0.5 and do not
need to be updated. Be aware that the only difference between PowerPIC firmware 0.5 and 3.4 is
the response time to power capping commands. Version 0.5 typically responds to power
adjustment commands within a couple of seconds. Version 3.4 typically responds within
milliseconds. This does not affect the operation of the servers or the overall power requirements of a
given blade.
 The stepping level of the processors on some BL460c G1 and BL480c G1 servers must be G or
later.
38
 iLO2 firmware 1.78 or later must be installed before the PowerPIC firmware can be updated.
 An iLO2 driver must be loaded.
 System ROM must have dynamic power capping support. All ROMs released in 2009 or later meet
this requirement.
 OA firmware must be at level 2.41or later for dynamic power capping to function properly.
 All versions prior to Power Management Controller firmware 3.4 have known issues. HP strongly
recommends that you update to 3.4 or later.

Note:
PowerPIC firmware 3.4(C) is required to interface with HP SUM.

Note:
While iLO2 firmware1.70 attempts to update the PowerPIC firmware,
issues occur when the PowerPIC is updated because the iLO2 resets during
its own firmware update. Because of this issue, HP recommends that you do
not use iLO2 firmware 1.70 on any blade server.

Note:
For details on how to troubleshoot PowerPIC firmware, see Troubleshooting
PowerPIC firmware update errors.

Update PowerPIC firmware by using the HP BladeSystem Firmware Update Bundles for Windows or
Linux starting with version 1.0. Make sure that you meet the dependencies listed previously, including
installation of the iLO2 driver. The HP BladeSystem Firmware Update Bundles contain a supported
version of the iLO2 drivers for Windows and Linux. If a driver is not currently installed, you must
install the driver first by using HP SUM. The HP BladeSystem Firmware Update Bundles that are
deployed during this installation ensure that the PowerPIC firmware update succeeds.
If an OS has not yet been installed and you want an automated method of installation, HP
recommends that you use the HP BladeSystem FDT 1.60 or later deployment tool for PowerPIC
firmware updates.
If an OS has not been installed and you want an interactive, offline method of installation, HP
recommends that you use the HP Firmware Maintenance CD 8.60 or later deployment tool. HP SUM
is embedded within the tool and enables the PowerPIC firmware to be updated interactively.
Table 19. Deployment tools for online/offline modes
Deployment tool to use Online mode Offline mode

Interactive Mode HP BladeSystem Online Firmware HP Firmware Maintenance CD

Bundles for Windows and Linux in GUI
mode
HP Firmware Maintenance CD

Scripted or Automated Mode HP BladeSystem Online Firmware HP BladeSystem FDT

Bundles for Windows and Linux in silent
mode

Note:
While individual smart components are made available for PowerPIC
firmware updates, HP does not recommend them for update scenarios
unless absolutely necessary.

39
 Note:
A workaround is required for HP SUM included in the HP Firmware
Maintenance CD 8.60 to correctly install the PowerPIC firmware in offline
mode.

Follow these steps to correctly install the PowerPIC firmware in offline mode:
1. Create a USB key by using the HP USB Key Creator Utility.
2. Edit the master_dependencies.xml file by using Notepad or vi.
3. Change the PowerPIC-Iris Blades.
<component name="PowerPIC-Iris-Blades" type="firmware:QLOGIC" >
<hpsum_prerequisites version="1" >
<is_staged_updated value="No" />
<installation_mode value="both" />
<blade value="n/a" />
<enforce_supported_operating_systems value="no" />
<configuration type="None" >
<filename />
</configuration>
<prerequisite_list relation="AND" >
<prerequisite>
<mode>both</mode>
<product type="firmware:ilo2" id="ILO2" />
<version value="1.78" />
<path></path>
<condition>InstalledBefore</condition>
<compare_type>GTE</compare_type>
<compare_time>Install</compare_time>
<description lang="en">Online ROM Flash Component - HP
Integrated Lights-Out 2</description>
<description lang="ja">Online ROM Flash Component - HP
Integrated Lights-Out 2</description>
</prerequisite>
</prerequisite_list>
<supported_devices>
<supported_devices_remove>
<id value="0E11.B204.103C.3304" />
<id value="0E11.B204.103C.3305" />
</supported_devices_remove>
</supported_devices>
<discovery_prerequisite_list />
<uninstalled_products_list />
<install_instructions />
</hpsum_prerequisites>
</component>

4. Once the file has edited, save it, and then use the Firmware Maintenance CD as normal.

This issue is resolved in the Firmware Maintenance CD 1.70 release.

Note:
HP SUM provides the capability to update the PowerPIC firmware by
allowing you to retrieve the latest updates from the HP website. For this
functionality to work correctly when using PowerPIC firmware, you must
install the iLO driver before starting the firmware update process. If you do
not install the iLO driver before starting HP SUM, the PowerPIC firmware
component is placed in the No Device Driver Found section. You are
required to run the HP SUM update again when the iLO driver is installed
to correctly update the PowerPIC firmware.

40
Note:
For information on how to add components to an existing tool, see How do
I add updated components to the HP BladeSystem FDT? or How do I add
updated components to the HP Firmware Maintenance CD?

Smart Array Controller firmware

Update Smart Array Controller firmware by using the version of HP SUM provided in the HP
BladeSystem Firmware Update Bundles for Windows or Linux if an OS is already installed on the
blade.
If the event an OS has not yet been installed and you want an automated method of installation, use
the HP BladeSystem FDT. HP SUM is embedded within the tool and updates the Smart Array
Controller firmware if an update is required during the silent, automated firmware update process
provided by the FDT.
If an OS has not been installed and you want an interactive, offline method of installation, use the HP
Firmware Maintenance CD deployment tool. HP SUM is embedded within the tool and enables the
Smart Array Controller firmware to be updated interactively.
Table 20. Deployment tools for online/offline modes
Deployment tool to use Online mode Offline mode

Interactive Mode HP BladeSystem Online Firmware HP Firmware Maintenance CD

Bundles for Windows and Linux in
GUI mode
HP Firmware Maintenance CD

Scripted or Automated Mode HP BladeSystem Online Firmware HP BladeSystem FDT

Bundles for Windows and Linux in
silent mode

Note:
The Smart Array Controller driver must be installed in order for the Smart
Array Controller firmware to be updated.

Note:
While individual smart components are made available for Smart Array
Controller firmware updates, they are not recommended for update
scenarios unless absolutely necessary. If new smart components are
released to resolve critical issues, the components can be added to any of
the tools above and picked up by HP SUM automatically.

Note:
For information on how to add components to an existing tool, see How do
I add updated components to the HP BladeSystem FDT? or How do I add
updated components to the HP Firmware Maintenance CD?

SAS and SATA hard drive firmware

SAS and SATA hard drive firmware have dependencies that must be met before installation can
proceed. You must install the Smart Array controller driver. The version is not important because any
Smart Array controller driver available since early 2006 is sufficient. The hard drives must be behind
a Smart Array controller.

41
 Note:
None of the current installation tools can update SAS or SATA hard drive
firmware behind non-Smart Array Controllers.

Update SAS and most SATA Hard Drive Firmware by using the version of HP SUM provided in the HP
BladeSystem Firmware Update Bundles for Windows or Linux if an OS is already installed on the
blade.
If an OS has not yet been installed and you want an automated method of installation, use the HP
BladeSystem FDT. HP SUM is embedded within the tool and updates the SAS and SATA hard drive
firmware if an update is required during the silent, automated firmware update process provided by
the FDT.
If an OS has not been installed and you want an interactive, offline method of installation, use the HP
Firmware Maintenance CD deployment tool. HP SUM is embedded within the tool and enables the
SAS and SATA hard drive firmware to be updated interactively.
Table 21. Deployment tools for online/offline modes
Deployment tool to use Online mode Offline mode

Interactive Mode HP BladeSystem Online Firmware HP Firmware Maintenance CD

Bundles for Windows and Linux in GUI
mode
HP Firmware Maintenance CD

Scripted or Automated Mode HP BladeSystem Online Firmware HP BladeSystem FDT

Bundles for Windows and Linux in silent
mode

Note:
Some older SATA hard drives might require offline mode because they do
not have an online equivalent.

Note:
Currently, HPSUM does not support firmware updates for SAS or SATA
hard drives located behind non-Smart Array controllers. See the web pages
for the individual SAS and SATA hard drive firmware releases for the steps
on how to update these drives.

Note:
The Smart Array Controller driver must be installed to update SAS and
SATA hard drive firmware.

Note:
To update some older SATA drives, make sure that they do not have active
I/O operations. You can only update these older SATA drives by using
either the Firmware Maintenance CD or the FDT ISO.

Note:
While individual smart components are made available for SAS and SATA
hard drive firmware updates, they are not recommended for update
scenarios unless absolutely necessary. If new smart components are
released to resolve critical issues, the components can be added to any of
the tools above and picked up by HP SUM automatically.

Note:
For information on how to add components to an existing tool, see How do
I add updated components to the HP BladeSystem FDT? or How do I add
updated components to the HP Firmware Maintenance CD?

42
Emulex, QLogic, and Brocade Fibre Channel HBA firmware
Emulex, QLogic and Brocade Fibre Channel HBA firmware have dependencies that must be met
before installation. Install the appropriate Emulex, QLogic and Brocade Fibre Channel HBA controller
driver. You must update the HBA firmware while the HBAs are not processing I/O. Because of the
nature of HBA firmware updates, this dependency requires you to update the HBA firmware offline.
If you want an automated method of installation, use the HP BladeSystem FDT. HP SUM is embedded
within the tool and updates the QLogic, Brocade and Emulex HBA firmware if an update is required
during the silent, automated firmware update process provided by the FDT.
For an interactive method of installation, use the HP Firmware Maintenance CD deployment tool. HP
SUM is embedded within the tool and enables the Emulex and QLogic HBA firmware to be updated
interactively. For some HBAs, there are multiple firmware types such as Boot Block and BIOS that must
both be updated.
Table 22. Deployment tools for online/offline modes
Deployment tool to use Online mode Offline mode

Interactive Mode Not Supported HP Firmware Maintenance CD

Scripted or Automated Mode Not Supported HP BladeSystem FDT

Note:
The BladeSystem Firmware Update Bundles cannot be used to update HBA
firmware.

Note:
While individual smart components are made available for QLogic and
Emulex HBA firmware updates, they must be used with HP SUM in an
offline environment with the appropriate driver already loaded as part of
the boot process. HP does not recommend using the smart components
individually unless absolutely necessary. If new smart components are
released to resolve critical issues, the components can be added to any of
the tools above and picked up by HP SUM automatically.

Note:
For information on how to add components to an existing tool, see How do
I add updated components to the HP BladeSystem FDT? or How do I add
updated components to the HP Firmware Maintenance CD?

Tape Blade firmware

Tape Blade firmware has dependencies that must be met before installation. Load an appropriate
driver for the controller the Tape Blade is attached to. Typically, this will be a Smart Array P700M or
similar controller. Loading the Smart Array Controller driver fulfills this dependency. Also, the tape
drive must have a tape in it. As part of the firmware update process, the tape is ejected. Failure to
have a tape in the drive could cause the firmware update to fail.
Update the Tape Blade firmware by using the version of HP SUM provided in the HP BladeSystem
Firmware Update Bundles for Windows or Linux if an OS has already been installed on the blade.
If an OS has not yet been installed and you want an automated method of installation, use the HP
BladeSystem FDT. HP SUM is embedded within the tool and updates the Tape Blade firmware if an
update is required during the silent, automated firmware update process provided by the FDT.
If an OS has not been installed and you want an interactive, offline method of installation, use the HP
Firmware Maintenance CD deployment tool. HP SUM is embedded within the tool and will allow the
Tape Blade Firmware ROM to be updated in an interactive manner.
43
 Table 23. Deployment tools for online/offline modes
Deployment tool to use Online mode Offline mode

Interactive Mode HP BladeSystem Online Firmware Bundles HP Firmware Maintenance CD

for Windows and Linux in GUI mode
HP Firmware Maintenance CD

Scripted or Automated Mode HP BladeSystem Online Firmware Bundles HP BladeSystem FDT

for Windows and Linux in silent mode

Note:
While individual smart components are made available for Tape Blade
firmware updates, they are not recommended for update scenarios unless
absolutely necessary. If new smart components are released to resolve
critical issues, the components can be added to any of the tools above and
picked up by HP SUM automatically.

OA firmware
There are many methods to update OA firmware. Many of these methods require knowledge of the
OA Command-Line Interface and various utilities. Because these methods only allow the OA firmware
to be updated and do not take into account the total release set of OA, iLO, System ROM and other
firmware, HP recommends that you do not use these methods. Instead, use the version of HP SUM
provided in the HP BladeSystem Firmware Update Bundles for Windows or Linux.
There are a few requirements for updating OA firmware. You must connect a workstation to the same
network as the OA network port. Also, you must have OA administrator credentials. Other types of
OA credentials do not allow firmware updates. Finally, the OA firmware can only be updated online.
You cannot use tools such as the HP BladeSystem FDT and you cannot boot to the HP Firmware
Maintenance CD.
Execute HP SUM from a workstation or server running any supported version of a Windows or Linux
OS. You can execute HP SUM, select remote installation, add the IP address or DNS name of the OA
network port as a remote host and HP SUM will automatically detect the target is an OA and only
allow the OA firmware to be selectable.
An alternative method of updating the OA firmware is to use the HP Firmware Maintenance CD in
online mode. This requires you to run HP SUM from a workstation or server running a supported
version of Windows or Linux, just like when using the HP BladeSystem Firmware Update Bundles.
Table 24. Deployment tools for online/offline modes
Deployment tool to use Online mode Offline mode

Interactive Mode HP BladeSystem Online Firmware Bundles for Not Supported

Windows and Linux in GUI mode
HP Firmware Maintenance CD

Scripted or Automated Mode HP BladeSystem Online Firmware Bundles for Not Supported
Windows and Linux in silent mode

Note:
Using the HP BladeSystem FDT or the HP Firmware Maintenance CD in
offline mode (booting to the ISO or media) is not supported for updating
OA firmware.

44
Note:
While individual smart components are made available for OA firmware
updates, they are not recommended for update scenarios unless absolutely
necessary. If new smart components are released to resolve critical issues,
the components can be added to any of the tools above and picked up by
HP SUM automatically.

Note:
For information on how to add components to an existing tool, see How do
I add updated components to the HP Firmware Maintenance CD?

Note:
If using VC Ethernet or Fibre Channel modules and the firmware version is
earlier than version 1.34, network outages might occur. HP recommends
that you update the VC firmware to version 1.34 or greater to prevent this
network downtime from occurring when the OA firmware is updated.

Installation order
If the VC Ethernet firmware is version 1.34 or later, or you are not using VC in your blade enclosures,
the following is the recommended installation order.
If an OS has already been installed:
1. Update the blades and the OA first using the HP BladeSystem Online Firmware Bundles for
Windows and Linux using a workstation connected to the same network as the OA.
2. Use the HP BladeSystem FDT or HP Firmware Maintenance CD to update any offline only
firmware.
3. Use the VCSU from a workstation connected to the same network(s) as the OA and VC Ethernet
modules to update the VC firmware after all other updates are applied, servers are rebooted,
and all firmware is activated.

If an operating has not yet been installed:

1. Update the OA first using the HP BladeSystem Online Firmware Bundles for Windows and
Linux using a workstation connected to the same network as the OA.
2. Use the VCSU from a workstation connected to the same network(s) as the OA and VC
Ethernet modules to update the VC firmware after all other updates are applied, servers are
rebooted, and all firmware is activated.
3. Use the HP BladeSystem FDT or HP Firmware Maintenance CD to update all server-specific
firmware.

If VC Ethernet firmware is earlier than version 1.34:

1. Update the VC firmware first by using the VCSU from a workstation connected to the
same network(s) as the OA and VC Ethernet modules.
2. Update the server blades and the OA next using the HP BladeSystem Online Firmware
Bundles for Windows and Linux from a workstation connected to the same network as
the OA.
3. Use the HP BladeSystem FDT or HP Firmware Maintenance CD to update any offline-only
firmware.

VC firmware
As with the OA firmware, there are many methods to update VC firmware. Many of these methods
require knowledge of the VCM CLI or web browser or require the installation of the VCEM and

45
 various other utilities. HP recommends the use of VCSU to update VC firmware as the most direct
path.
VC firmware is provided as .bin files until version 2.10. As of version 2.10, smart components that
contain .bin files and the VCSU have been made available. Currently, there are two smart
components. One of the smart components contains the Ethernet module firmware and 4 GB Fibre
Channel Module firmware updates. The second smart component contains the same Ethernet module
firmware and the 8GB Fibre Channel Module firmware updates. Initially, this was done because of
the size of the firmware images (about 50MB each) that prevented them from being uploaded
completely into the VC. With planned enhancements in the VCSU, eventually, all three modules are
combined into a single component containing the VCSU.
There are a few dependencies for updating VC firmware. You must connect a workstation to the same
network as the VC management port. Also, you must have both the OA and VC administrator
credentials. Because the VCSU uses information from the OA in updating the VC firmware, it requires
both sets of credentials. Finally, the VC firmware can only be updated online. You cannot use tools
such as the HP BladeSystem FDT and you cannot boot to the HP Firmware Maintenance CD.
The VCSU provides a command-line scriptable method to update the VC firmware. It also contains
logic that minimizes any network and fabric outages caused by the update process under certain VC
configurations. In some cases, the VCSU can eliminate all outages during the firmware update
process if correct redundancy has been installed. VCSU must be executed from a Windows or Linux
(requires version 1.40 or later of VCSU) workstation or server.
An alternative method of updating VC firmware is to use the HP BladeSystem Online Firmware
Bundles for Windows and Linux. VC firmware update support was added to the HP SUM beginning
with version 3.5.0. HP SUM can deploy the VC smart components using the VCM interface. The VCM
interface is being deprecated in the VC firmware 3.0.0 release, and HP SUM will be enhanced to use
the VCSU embedded in the smart components to support VC firmware updates. The HP BladeSystem
Online Firmware Bundles for Windows and Linux provide the necessary support starting with version
1.60 and later.
Table 25. Deployment tools for online/offline modes
Deployment tool to use Online mode Offline mode

Interactive Mode HP BladeSystem Online Firmware Bundles for Not supported

Windows and Linux in GUI mode

Scripted or Automated Mode HP BladeSystem Online Firmware Bundles for Not supported
Windows and Linux in silent mode

46
Note:
While the HP Firmware Maintenance CD can be used in online mode to
update VC firmware, there are many manual steps involved. Because of
their size, the VC firmware smart components must be downloaded from
the HP website because they will not fit on the HP Firmware Maintenance
CD ISO. When they are downloaded, the HP Firmware Maintenance CD
must be copied to read-write media and the VC firmware smart components
copied to the \compaq\swpackages directory. When this is finished, HP
SUM can be executed to deploy the VC firmware components. Because the
VC firmware is not shipped on the HP Firmware Maintenance CD, HP does
not recommend this method because it is possible to download VC
firmware that would not be compatible with the HP SUM version on the HP
Firmware Maintenance CD.

Note:
Using the HP BladeSystem FDT or the HP Firmware Maintenance CD in
offline mode (booting to the ISO or media) is not supported for updating
VC firmware.

Note:
While individual smart components are made available for VC firmware
updates, they are not recommended for update scenarios unless absolutely
necessary. If new smart components are released to resolve critical issues,
the components can be added to any of the tools above and picked up by
HP SUM automatically.

Note:
HP SUM 3.5.0 can update VC firmware to version 2.10 only. To update to
VC firmware versions greater than 2.10, HP SUM 3.6.2 or later must be
used.

Important:
If you are using the VCEM software, the VC domains must be placed in
maintenance mode before firmware updates are allowed.

Note:
Versions of HP SUM earlier than 3.6.2 have a known issue if the VC log
contains more than 650 entries. The issue will be seen as a Discovery
Failed message in HP SUM when attempting to update the VC firmware on
those VCs in this condition. Moving to HP SUM 3.6.2 or later or clearing
the VC System Log allows the firmware update to proceed.

Note:
For information on how to add components to an existing tool, see the How
do I add updated components to the HP Firmware Maintenance CD?

Important:
If the VC configuration is not redundant or if the VC firmware version is
earlier than version 1.34, a network fabric downtime of up to 10 minutes
can occur while the firmware is being activated. This affects all servers in
the enclosure and prevents network access until the VC firmware is
activated.

47
 Note:
Because of the possibility of NIC fabric downtime during a VC firmware
installation, HP strongly recommends that the VC be updated from a
workstation outside the enclosure to ensure continuous network access to
the firmware update utilities.

Installation order
If the VC Ethernet firmware is version 1.34 or later, or you are not using VC in your blade
enclosures, the following is the recommended installation order.
If an OS has already been installed:
1. Update the blades and the OA first using the HP BladeSystem Online Firmware Bundles for
Windows and Linux using a workstation connected to the same network as the OA.
2. Use the HP BladeSystem FDT or HP Firmware Maintenance CD to update any offline only
firmware.
3. If needing to update VC Ethernet firmware, use the VCSU from a workstation connected to the
same network(s) as the OA and VC Ethernet modules to update the VC firmware after all other
updates are applied, servers are rebooted, and all firmware is activated.
If an operating has not yet been installed:
1. Update the OA first using the HP BladeSystem Online Firmware Bundles for Windows and
Linux using a workstation connected to the same network as the OA.
2. Use the VCSU from a workstation connected to the same network(s) as the OA and VC Ethernet
modules to update the VC firmware after all other updates are applied, servers are rebooted,
and all firmware is activated.
3. Use the HP BladeSystem FDT or HP Firmware Maintenance CD to update all server-specific
firmware.

If VC Ethernet firmware is earlier than version 1 .34:

1. Update the VC firmware first using the VCSU from a workstation connected to the same
network(s) as the OA and VC Ethernet modules.
2. Update the server blades and the OA next using the HP BladeSystem Online Firmware Bundles
for Windows and Linux from a workstation connected to the same network as the OA.
3. Use the HP BladeSystem FDT or HP Firmware Maintenance CD to update any offline-only
firmware.

HP StorageWorks MDS600 firmware

With the release of the MDS600, new firmware update support was required. . The MDS600 is
normally deployed as part of a straight-forward in-rack 3 Gb/s SAS implementation that delivers high-
density, low-cost external zoned direct attach storage for HP BladeSystem servers. Up to six MDS600
storage devices can be supported off a single BladeSystem enclosure for up to 420 TB of capacity.
End-to-end 3 Gb/s SAS connectivity enables a high performance storage solution using an HP Smart
Array P700m controller, 3Gb SAS BL switches, and the MDS600.
The MDS600 has very special requirements for firmware updates that will necessitate powering down
all blades in an enclosure that are using the HP Smart Array P700m controller and that are attached
to the MDS600 storage enclosures. This requirement is in place because the enclosure cannot process
any I/O while the firmware is being updated. Also, because OSs periodically scan external storage,

48
only the offline mode of the Firmware Maintenance CD can be used to update the firmware for the
MDS600 storage enclosure.
The current version of MDS600 firmware is 2.54(B) as of the writing of this document. Most MDS600
storage enclosures should be at that level when shipped from the factory. Until new firmware updates
are made available, administrators do not need to include the MDS600 storage enclosure support in
their firmware update plans.
To update the MDS600 firmware, first power off all blades except the blade that will run the update.
Once the blades are powered off, the Firmware Maintenance CD must be booted offline on one of
the blades within the enclosure. There are a number of ways to boot the Firmware Maintenance CD
offline. To determine the best one to use in your environment, review Scenario 1C: Updating an
individual server using the HP Firmware Maintenance CD for the steps needed to perform the
firmware update.
Table 26. Deployment tools for online/offline modes

Deployment tool to use Online mode Offline mode

Interactive Mode Not supported HP Firmware Maintenance CD

Scripted or Automated Mode Not supported Not supported

Note:
The BladeSystem FDT cannot be used to update the MDS600 storage
enclosure firmware. Because the FDT is a single server firmware-update
tool, there is no way to guarantee any given server executing it is the right
one to update the MDS600. Because there is no guarantee, the Firmware
Maintenance CD must be used in offline mode.

Note:
Because the Firmware Maintenance CD must be used to update the
MDS600 storage enclosure and because the Firmware CD cannot be
executed using iLO Virtual Media if the iLO needs to be updated, the iLO
firmware update component must be deselected if it shows an update is
needed before flashing the MDS600 storage enclosure firmware.

Note:
For information on how to add components to an existing tool, see How do
I add updated components to the HP Firmware Maintenance CD?

HP StorageWorks 3Gb SAS BL Switch firmware

For information on how to update the firmware on the HP StorageWorks 3Gb SAS BL Switch, see
Virtual SAS Manager (VSM).

Firmware deployment scenarios

Over the past several years, there has been a lot of confusion as to the recommended update best
practices and prerequisites for updating enclosure-based firmware. This section provides several
recommended deployment scenarios including step-by-step description and examples for deploying
firmware updates based on various customer environments.
Observe the following dependencies while updating BladeSystem enclosure firmware.
 Upgrade the OA from version 1 .x to 2.x, which requires an intermediate step.
 Be aware that the PowerPIC firmware 3.4(C) requires iLO 2 firmware 1 .78 or later.

49
  If the VC firmware version is earlier than version 1.34, update VC firmware before the OA
firmware to prevent a network disconnection.
 Starting with VC firmware version 1.34 and later, the VC firmware should be updated after the OA
firmware.
The recommended firmware update strategies as documented in the following sections are intended to
minimize downtime and provide the least intrusive method of updating the OA, VC Ethernet, Fibre
Channel Modules, and servers in a given enclosure(s) that have been daisy-chained together.
Depending on the deployment tool, some of these will scale better to larger environments than others.
In each scenario, at least two options are provided. For more information, see Choosing the
deployment tool.
Table 27 lists the step-by-step instructions for each scenario.
Table 27. Installation scenarios
Scenario Description

1. Updating an Recommended deployment tool:

individual server HP BladeSystem Firmware Update Bundles for Windows or Linux
using:
 - HP BladeSystem
Firmware Update Note:
Bundles (online) Because HP BladeSystem Firmware Update Bundles do not provide
 HP BladeSystem FDT the ability to update all possible firmware types, additional
offline) deployment tools must be used to ensure that all firmware is updated
 HP Firmware within a BladeSystem enclosure and to align with the HP
Maintenance CD BladeSystem Compatibility Chart. To update the firmware that
cannot be updated by HP BladeSystem Firmware Update Bundles,
use the BladeSystem FDT or the HP Firmware Maintenance CD. The
latest version can be obtained from
http://www.hp.com/go/bladesystemupdates

2. HP BladeSystem FDT
Updating the OA Recommended deployment tool:
firmware using  H P F i r m w a r e M a i n t e n a n c e C D
 HP BladeSystem Firmware Update Bundles for Windows or Linux
 Updating the OA
 Use the OA web interface
firmware using HP
SUM
 Updating the OA
firmware using the
OA browser
interface from a
workstation
 Scenario 2C:
Updating the OA
firmware using the
OA CLI interface and
a web server

50
Scenario Description
3. Updating Recommended deployment tool:
the VC  VCSU
firmware
 HP BladeSystem Firmware Update Bundles for Windows or Linux
o using VCSU
o using the HP
SUM
o in a DMZ

4. Updating an Recommended deployment tool:

enclosure and
 HP BladeSystem Firmware Update Bundles for Windows or Linux
blades with an
OS already  HP Firmware Maintenance CD

5. Updating an Recommended deployment tool:

enclosure and
blades without
an existing OS Note:
installed Because HP BladeSystem Firmware Update Bundles do not provide
the ability to update all possible firmware types, additional
deployment tools must be used to ensure that all firmware is
updated within a BladeSystem enclosure and to align with the
HP BladeSystem Compatibility Chart. To update the firmware
that cannot be updated by HP BladeSystem Firmware
Update Bundles, use the BladeSystem FDT or the HP Firmware
Maintenance CD. The latest version can be obtained from
http://www.hp.com/go/bladesystemupdates/.

 HP BladeSystem FDT
 HP Firmware Maintenance CD
 HP BladeSystem Firmware update Bundles for Windows and Linux
 VCSU

51
 Scenario Description

6. Scripted Recommended deployment tool:

Installation of
Firmware
Updates for Note:
Multiple The HP BladeSystem Firmware Update Bundles can update all online
Enclosures firmware. However, there are some firmware types that cannot be
including the do not provide the ability to update all possible firmware
OA, VC and types, additional deployment tools must be used to ensure all
server blades firmware is updated within a BladeSystem enclosure and to
align with the HP BladeSystem Compatibility Chart. To update
the firmware that cannot be updated by HP BladeSystem
Firmware Update Bundles, use the BladeSystem FDT or the
HP Firmware Maintenance CD. The latest version can be
obtained from http://www.hp.com/go/bladesystemupdates/.

 HP BladeSystem FDT
 HP BladeSystem Firmware Update Bundles for Windows or Linux

7. Scenario 7: HP Firmware Maintenance CD

Updating the HP
StorageWorks
The HP Firmware Maintenance CD in offline mode is the only way to update this firmware. The
MDS600
component must be downloaded from the HP website and placed on a USB containing the HP
firmware
Firmware Maintenance CD in the \compaq\swpackages directory to be picked up and deployed
by HP SUM in this offline mode.

8. I want to update The only method available for updating this firmware is to download the binary firmware image
my HP 3 Gb SAS from the HP website and use the HP Virtual SAS Manager (VSM) to upload the firmware to the
BL Switch switch.
firmware

For information on how to update this firmware, see the Virtual SAS Manager (VSM) .

Installation scenarios
Scenario 1A: Updating an individual server using the HP BladeSystem
Firmware Update Bundles

Note:
To update any firmware that requires an offline environment, the HP
BladeSystem Firmware Update Bundles cannot be used to update that
firmware. In the case of the Emulex and QLogic HBA firmware updates, the
HP BladeSystem Firmware Update Bundles must be used in conjunction with
the HP Firmware Maintenance CD or the FDT ISO to fully update all
available firmware on an individual server.

52
The following instructions can be used to update the firmware on an individual server using the HP
BladeSystem Firmware Update Bundles for Windows or Linux.
1. Download the HP BladeSystem Firmware Update Bundles from the hp website. Links to the
latest versions are posted on the BladeSystem Compatibility Chart web pages and can be
accessed through the http://www.hp.com/go/bladesystemupdates URL. The files are
called:
hpblade_fw_bndl-<version>.w2k3.i386.exe for Windows and
hp_blade_fw_bundle-<version>.linux.tar.gz for Linux.
2. To extract the Windows bundles, execute the downloaded file and select a directory for
the extracted files to be placed. In Linux, simply untar/unzip the downloaded file as
follows:
tar zxvf hp_blade_fw_bundle-<version>.linux.tar.gz.
3. Before deploying firmware on a server, perform the following best practices to ensure the
firmware updates are successful.
 Test your setup in a lab environment before updating production servers.
 For those administrators who do not have access to a test lab, pick one server and
update it. Let the updated server run for a few days, and if everything continues to
work properly, update other servers starting with small groups of similar servers.
 Make sure you are within the support window of current or two previous releases. If
problems occur, it is best to be working on the most current release with support.
 If you have a problem with a component installing, check the web and the ITRC
forums to see if there is a new component available or if other users are reporting the
same problem.
 If you are installing a new server, update the firmware first before installing the OS.
This ensures that any firmware issues with OS installation have been addressed.
 Always ensure you have a backup of the server in case the firmware update fails
 Always reboot the server after server-based driver or firmware upgrades. Doing so
allows everything to be flushed out, memory cleared, and so on so the new
firmware/driver starts out fresh.

Note:
For more information and enhanced details of each of the HP
SUM screens, see the help support provided within HP SUM that
can be accessed using the ? icon at the top right of all screens
that support user input.

4. Follow the steps shown in Using HP SUM in GUI mode or HP SUM in scriptable or silent
mode.

Note:
Reboot the server once the firmware updates have completed
successfully to activate all the firmware.

53
 Scenario 1B: Updating a server using the HP BladeSystem FDT
The following instructions can be used to update the firmware on a server using the HP BladeSystem
FDT.
1. Download the HP BladeSystem FDT from the HP website.
Links to the latest versions are posted on the BladeSystem Compatibility Chart web pages and
can be accessed at http://www.hp.com/go/bladesystemupdates. The file is called:
bb-<version>.iso.
2. Copy the ISO image file to a USB key, and then insert it into the USB port on the front of the
C3000 Enclosure or on the rear of the C7000 Enclosure.
This is the easiest way to update a server blade is to use the HP BladeSystem FDT ISO.
3. Browse to the HP BladeSystem OA web interface, and log in by using the OA administrator
credentials.
4. Click on Device Bays to pull up a summary of all blades in the enclosure.
5. Check the box beside each blade selected to update.
6. Click the DVD tab, and select the Connect to bb*.iso option in the pull-down menu.
In this option, the * signifies the version, date, and pass number of the HP BladeSystem FDT
ISO file that was extracted in Step 2.
7. Check the box beside each blade that needs to be updated again as it will be deselected
during the DVD connection step.
8. Select the Virtual Power tab, and then select the Momentary Press option.
After confirming the popup for power change on the blade(s), the blades should power down if
they were already powered on. They will power on if they had already been powered off. In
the event they are powered off by Step 9, repeat this step again to power on the blade(s).

Note:
The Momentary Press option brings down any OS that is
running on the blade, as long as ACPI support has not been
disabled in the OS.

9. When you boot to the FDT, all feedback is provided through the UID lights. While the
update process is running, the UID light blinks. Upon completion, the UID light is set to one of
two states:
 If the UID light is off, the update process is complete, and the server OS can be installed or
the server can be restarted to its previous OS.
 If the UID light is solid, a firmware update failure has occurred requiring attention. You can
either plug in the KVM dongle or use iLO Remote Console support to browse into the
affected server to determine the cause of the failure. The FDT loads the error log into a
vi editor window for review.

HP strongly recommends that you resolve the issue causing the failure before installing or restarting
the OS to prevent issues that could affect server operation. For more information on how to
handle various firmware update failure scenarios, see Troubleshooting HP BladeSystem FDT.

Note:
For more information on how to handle various firmware update failure
scenarios, see Troubleshooting HP BladeSystem FDT.

54
Note:
The server automatically reboots after the FDT completes.

Note:
In some rare instances, the HP BladeSystem FDT may not boot with some
third-party external Fibre Channel storage attached. In this event, it may be
necessary to disconnect the external storage for the duration of the update
process and reconnect it afterwards.

Note:
As an alternative, the HP FDT ISO can be burned to a physical CD and
placed in an external CD/DVD drive connected to the KVM dongle for the
individual blade that must be updated.

Note:
If more than 64 GB of memory is included in a blade, FDT 1.60 and earlier
ISOs hang at a blank screen shortly after the FDT starts to boot. To resolve
this issue, use an FDT version later than 1.60, or issue the following
command at the Boot: prompt: . Another workaround is to
remove the extra memory until there is less than 64 GB in the server. The
additional memory can be added back to the server after the FDT
completes updating the firmware.

Note:
For information on how to script updates of the FDT, see Scenario 6: I want
to automate and script the update of multiple enclosures including the OA,
VC, and server blades.

Scenario 1C: Updating an individual server using the HP Firmware

Maintenance CD

Note:
For information on how to add components to an existing tool, see How do
I add updated components to the HP Firmware Maintenance CD?

The HP Firmware Maintenance CD supports both online and offline

installations. Because of the limitations of some types of firmware, it may be
necessary to update firmware in both the online and offline environments to
ensure all relevant firmware has been updated correctly.

Note:
If you need to update VC firmware, the firmware smart components must be
downloaded off the web and added to contents of the HP Firmware
Maintenance CD. For steps on how to do this, see How do I add updated
components to the HP Firmware Maintenance CD.
Note:
OA and VC firmware components can only be updated online.

Note:
Updating Emulex, QLogic, or Brocade HBA Firmware or earlier SATA hard
drive firmware requires the use of the Offline Updates method for the HP
Firmware Maintenance CD.

55
 Online updates
For the online method of firmware updates, there are multiple ways to use the HP Firmware
Maintenance CD.
 Place the Firmware CD ISO image file onto a USB key, and insert the USB key into the OA USB
ports on the c3000 Enclosure and c7000 Enclosure.
 Insert a USB key containing the Firmware CD ISO image created by using the HP USB Key Creator
for Windows utility into the SUV (Serial-USB-Video) cable attached to the physical blade that you
want to update, if the blade server supports the SUV cable connection.
 For Windows, the HP USB Key Creator for Windows utility must be downloaded from the HP
website and installed on a workstation. Once installed, the utility places a shortcut in the HP System
Tools in the Programs start menu folder.
Follow the instructions provided with the USB Creator utility.

Note:
The HP USB Key Creator formats the USB key so any files on the key are
lost. Be sure to use a USB key that is at least 1 GB and does not contain
any valuable files.

For Linux, follow these steps to manually create the USB key:
1. Obtain SYSLINUX 3.2 or higher from http://freshmeat.net or http://syslinux.zytor.com and
download to a Linux workstation.
2. Install the SYSLINUX RPM obtained in Step 1.
3. Create a directory for the USB key mountpoint if one does not already exist. (For example,
mkdir /usbkey.)
4. Insert the USB key, and mount it (mount /dev/sda1 /usbkey).

Note:
The device mountpoint can vary depending on whether other
SCSI drives are also installed on the server. Thus, the device
mountpoint can be sdb1, sdc1, and so on).

5. Issue the ./syslinux /usbkey at the command to prompt SYSLINUX write out the boot
partition to the USB key.

Note:
Failure to follow this step could lead to a key that will not boot
the Firmware CD until the SYSLINUX command is successful.

6. Create a directory to mount the CD image.

mkdir /cd_mount_point
7. Insert the Firmware CD or mount the Firmware CD ISO via a loopback
mount /dev/cdrom /cd_mount_point
or
mount -t iso9660 firmware-<version>.iso /cd_mount_point -o loop
8. Change to the /USB directory on the CD.

56
 cd /cd_mount_point/usb
9. Execute the usbcreator.sh shell script passing in the CD mount point and the USB mount point
to move the Firmware CD files to the USB key.
./usbcreator.sh /cd_mount_point /usbkey
10. Unmount the CD and the USB key.
umount /dev/cdrom
umount /dev/sda1

Note:
This must match the initial mount point in Step 4.

11. Remove the USB key and CD from the workstation used to create the USB key.
12. Insert the physical Firmware CD burned from the Firmware CD ISO image into an external
CD/DVD drive attached to the SUV (Serial-USB-Video) cable for the blade that needs to be
updated if the blade server supports the SUV cable.

*iLO Virtual Media

The iLO Virtual Media can be connected through the OA interface to a given server, through the iLO
Virtual Media applet, or remotely through RIBCL scripts.
Under Windows, the ILO Virtual Media shows up as the next available drive letter. In Linux, the iLO
Virtual Media must be mounted as follows:
 mount /dev/sda /mnt/floppy -t vfat to mount a virtual floppy
 mount /dev/sda1 /mnt/keydrive to mount a virtual USB key drive
 mount /dev/cdrom1 /mnt/cdrom to mount a virtual CD-ROM on a Red Hat System
(Use /dev/cdrom if the server does not have a locally attached CD-ROM drive)
 mount /dev/scd0 /mnt/cdrom to mount a virtual CD-ROM on a SUSE system

Note:
When using the Firmware CD through iLO Virtual Media, it is strongly
recommended that all files be copied locally even when leveraging the iLO
Virtual Media under OS control. Otherwise, when the iLO firmware is
updated if needed, the connection to the iLO Virtual Media will be reset
and connection to the file system will be lost. If this happens during a
deployment scenario, HP SUM could hang after updating the iLO
Firmware.

Note:
HP recommends that you copy the files locally if NIC firmware is to be
updated even if files are being accessed through a Windows network file
share or Linux NFS mountpoint. Failure to copy the files locally can cause
all firmware updates after the NIC firmware update to fail because of loss
of network connectivity related to the update of the NIC firmware.

Once the files are available locally on the server selected to update, change to the
\compaq\swpackages directory or the file share location and follow the steps shown in Using HP
SUM in GUI mode or Using HP SUM in Scripted or Silent mode.

57
 Offline updates
The following instructions can be used to update the firmware on an individual server using the HP
Firmware Maintenance CD.
1. Download the HP Firmware Maintenance CD from the HP website. Links to the latest versions
are posted on the BladeSystem Compatibility Chart web pages and can be accessed at
http://www.hp.com/go/bladesystemupdates. The file is called firmware-<version>.zip.
2. To extract the ISO image, open Windows Explorer, double-click on the ZIP file, and then copy
the ISO image to a directory on a USB key or network hard drive.
For Linux users, simply unzip the ZIP file by using the unzip firmware-<version>.zip
command.
3. Update a server blade with the HP Firmware Maintenance CD ISO image by placing it on a
USB key, and then inserting it into the USB port on the front of the C3000 Enclosure or on the
rear of the C7000 Enclosure.
4. Browse to the HP BladeSystem OA web interface, and log in with the OA administrator
credentials.
5. Click Device Bays to pull up a summary of all blades in the enclosure.
6. Check the box beside each blade that you want to update.
7. Click the DVD tab, and select the Connect to FW*.iso option in the pull-down menu where the *
signifies the version, date, and pass number of the HP Firmware Maintenance CD ISO file that
was extracted in Step 2.
8. Check the box beside each blade that you want to update again if the boxes are deselected
during the DVD connection step.
9. Select the Virtual Power tab, and then select the Momentary Press option.
After confirming the popup for power change on the blade(s), the blades should power down if
they are already powered on or power on if they are already powered off. In the event they
are powered off by Step 9, repeat this step again to power on the blade(s).
10. Use the remote console to browse into each blade, and drive the installation process by
following the steps outlined in Using HP SUM in GUI mode.
Some screens, such as the Source Selection and Select Installation Hosts, are displayed in
offline mode.

Note:
The iLO firmware must be deselected if the Firmware CD is
executed in offline mode to prevent errors that might occur when
the iLO Firmware is updated and the iLO virtual media and
remote console is reset. Update the iLO firmware online first by
using the HP BladeSystem Firmware Update Bundles, and then
use the HP Firmware Maintenance CD in offline mode to flash
offline-only firmware, such as the QLogic, Brocade, and Emulex
FC HBA firmware.

Note:
Use the HP BladeSystem FDT for an automated way to perform
these steps. The HP BladeSystem FDT also does not have the
issue with iLO Firmware updates disconnecting the media,
because the FDT copies all of the files from the iLO Virtual Media
to a RAM drive on each server before initiating the firmware
update process.

Note:
Reboot the server once the firmware updates have completed
successfully to activate all software.

58
 Note:
In some rare instances, the Firmware Maintenance CD may not
boot with some third-party external Fibre Channel storage
attached. In the event this occurs, it may be necessary to
disconnect the external storage for the duration of the update
process and reconnect it afterwards.

Note:
As an alternative, you can burn the HP Firmware Maintenance
CD to a physical CD and placed in an external CD/DVD drive
connected to the SUV (Serial-USB-Video) cable for the individual
blade that must be updated.

Scenario 2A: Updating the OA firmware using HP SUM

The following instructions can be used to update the OA firmware on an individual enclosure by using
the HP BladeSystem Firmware Update Bundles for Windows or Linux.
1. Download the HP BladeSystem Firmware Update Bundles from the hp website.
Links to the latest versions are posted on the BladeSystem Compatibility Chart web pages and
can be accessed at http://www.hp.com/go/bladesystemupdates. The files are called:
hpblade_fw_bndl-<version>.w2k3.i386.exe for Windows and hp_blade_fw_bundle-
<version>.linux.tar.gz for Linux.
2. To extract the Windows bundles, execute the downloaded file, and select a directory to place
the extracted files.
In Linux, simply untar/unzip the downloaded file as follows:
tar zxvf hp_blade_fw_bundle-<version>.linux.tar.gz.
3. Follow the steps shown in Using HP SUM in GUI mode or Using HP SUM in Scripted or Silent
mode.
Ensure the target device IP address or DNS name is in the information for the Active OA
management NIC port. During the OA firmware update process, the Standby OA firmware is
updated first, and then the active OA firmware. After the firmware is updated, the OA
experiences a brief downtime as the firmware is activated. This downtime does not affect any
server blades or traffic through any VC modules, as long as the VC configuration is at least
1.34 or later. If the VC firmware version is earlier than 1.34, a network fabric downtime of up
to 10 minutes can occur while the firmware is being activated.

Note:
The firmware update process for both OAs should take between
6-8 minutes. An individual OA firmware update should take
approximately 4-6 minutes.

Note:
If the OA firmware is updated independent of other components
of the OA firmware version being deployed, make sure it aligns
with the currently supported release sets on the BladeSystem
Firmware Compatibility Chart.

Note:
Multiple OA can be updated simultaneously to speed up the
process.

59
 Scenario 2B: Updating the OA firmware using the OA browser interface
from a workstation
The OA firmware can also be updated by using the OA browser interface if the HP BladeSystem
Firmware Update Bundles for Windows or Linux cannot be used. Follow these steps to use this
installation approach.
1. Download the HP BladeSystem Firmware Update Bundles from the ―Download and Support‖
section on the HP website at: http://hp.com.
Links to the latest versions are posted on the BladeSystem Compatibility Chart located at
http://www.hp.com/go/bladesystemupdates. The files are named:
hpblade_fw_bndl-<version>.w2k3.i386.exe for Windows and hp_blade_fw_bundle-
<version>.linux.tar.gz for Linux.
2. To extract the Windows bundles, execute the downloaded file, and then select a directory
location to place the extracted files.
In Linux, simply untar/unzip the downloaded file as follows: tar zxvf hp_blade_fw_bundle-
<version>.linux.tar.gz.
3. Find the bp00xxxx.txt file that is extracted from the bundle, and determine the component
number for the OA firmware component.
4. Execute the OA firmware component to extract the firmware .bin file by using the following
commands:
Windows: CP01xxxx.exe (Choose Extract option and select a directory)
Linux: ./CP01xxxx.scexe --unpack=<dir_path> (unpack it to dir_path)

5. Log in to the OA management interface with the OA administrator credentials.

6. From the Systems and Devices pane, select Enclosure Information > Active Onboard
Administrator > Firmware Update.
7. Press the Browse button to locate the .bin file previously extracted in Step 4.
8. Choose Upload to begin the installation.

Scenario 2C: Updating the OA firmware using the OA CLI interface and
a web server
The OA firmware can also be updated by using the OA CLI interface and placing the OA firmware
binary image file on a web server. This is useful if the HP BladeSystem Firmware Update Bundles for
Windows or Linux cannot be used. This method requires setting up a web server to host the firmware
binary image file that is extracted from the OA component. While setting up a web server can be a
complex operation, we describe the basics of how to set up both Microsoft Windows IIS and Apache
web servers. This information will help you stage image files for update through the OA browser
interface without the need for physical media. For more complete information about security and
maintenance, see the HP BladeSystem Onboard Administrator Command Line Interface User Guide.
There are multiple sections that must be completed for this support to work. Follow these steps to
ensure the configuration is set up correctly to allow this type of deployment.

60
Obtaining all necessary files
The following files must be obtained to complete this scenario:
 OpenSSH for Windows located at:
http://softlayer.dl.sourceforge.net/project/sshwindows/OpenSSH%20for%20Windows%20-
%20Release/3.8p1-1%2020040709%20Build/setupssh381-20040709.zip
 A web server for Microsoft Windows Internet Information Server
Obtained from Windows Server 2003/2008 installation CDs
 Apache web server located at:
http://www.ecoficial.com/apachemirror/httpd/binaries/win32/apache_2.2.13-win32-x86-
openssl-0.9.8k.msi
 HP BladeSystem Firmware Update Bundles for Windows or Linux
o Windows located at:
ftp://ftp.hp.com/pub/softlib2/software1/supportpack-windows/p1116845569\
(Choose highest numbered directory for the latest version)
o Linux located at:
ftp://ftp.hp.com/pub/softlib2/software1/supportpack-linux/p1418640128
(Choose highest numbered directory for the latest version)
After the files are obtained, a web server must be set up. The following sections describe the
fundamentals for installing and setting up a basic Microsoft IIS and Apache web server for Linux.

Setting Up the Microsoft IIS web server

The web server is a system that, when configured, houses the files and serves them for the OA and
other devices. The web server setup is a one-time operation. After it has been set up, files can be
added to the web server so that updates are easily handled when new versions of the various
deployment tools are released.
To install Microsoft IIS, follow these steps:
1. Use the Add or Remove Programs Option in Control Panel (Windows Server 2003) or add the
role of web server (IIS) (Windows Server 2008) to install IIS.
2. Visit the Microsoft Update site to ensure all fixes are installed prior to enabling IIS to prevent
possible security breaches.
3. Once the web server is set up, locate and click the Internet Information Services (IIS) Manager
option in the Start menu to launch the web configuration manager.
4. Click Web Sites, click Default Web Sites, click Properties, and then click Home Directory to find
the web server file system root directory.
For IIS, this is normally c:\inetpub\wwwroot. Once you determine the home directory, ensure
the Write option is not checked to prevent unauthorized writing to the web server.
5. Click the HTTP Headers tab, and then click MIME Types.
6. In the MIME Types dialog, add three new MIME types as shown if they do not already exist.
Extension MIME Type

.img application/octet-stream
.iso application/octet-stream
.bin application/octet-stream

7. Click OK, click Apply, and then click Exit the IIS Manager.

61
 8. Download the HP BladeSystem Firmware Update Bundles from http://hp.com.
Links to the latest versions are posted on the BladeSystem Compatibility Chart web pages at
http://www.hp.com/go/bladesystemupdates. The file is called hpblade_fw_bndl-
<version>.w2k3.i386.exe for Windows.
9. To extract the Windows bundles, execute the downloaded file, and then select a directory
location to place the extracted files.
10. Find the bp00xxxx.txt file extracted from the bundle, and determine the component number
for the OA firmware component.
11. Execute the OA firmware component to extract the firmware .bin file contained within it by
using the following commands:
Windows: CP011352 (and then choose the Extract option and extract the
file to the c:\inetpub\wwwroot directory)

12. Create a simple HTML file in the web server root. For IIS, this is typically
c:\inetpub\wwwroot. Use this file to use to test the web server. Use the following example to
create this default file. The file is typically named index.html.
<html>
<head>
<title>OA Firmware</title>
</head>
<body>
<a name="top"></a>
<h1>OA Firmware Binaries</h1>
<h2>Contents</h2>
<p>
<a href="hpoa252.bin">OA Firmware 2.52</a>
<p>
</body>
</html>

13. Once the file is saved into the web server directory root, (c:\inetpub\wwwroot), go to
another workstation, open a browser, and try to load the web page just created on the web
server. (For instance, http://<workstation_IP_address/index.html).
Once the pages are loading, verify the download of the binary file to the workstation is
working properly. This is important because it simulates the same type of interface that the OA
uses to pull the newly created file from the web server.
14. If the file is successfully downloaded, skip Setting up the Apache web server in Linux, and
continue to Configuring the SSH keys for scripted installations.

Setting up the Apache web server in Linux

The web server is a system that, if configured, houses the files and serves them for the OA and other
devices. The web server setup is a one-time operation. After it has been set up, files can be added to
the web server so that updates can be easily handled when new versions of the various deployment
tools are released.
To install the Apache web server, follow these steps:
1. Download the Apache web server from the Apache mirror site or directly from the
http://httpd.apache.org/ Apache HTTP Server website.
2. Extract the files by using the tar zxvf httpd-<version>.tar.gz command
3. Change directory to the httpd-<version> directory.

62
4. Execute the configure command to configure Apache:
./configure --prefix=/usr/local/apache2

The --prefix directory becomes the web server root location. The Apache default location is
/usr/local/apache2 in Linux.

5. Once Apache is configured, run the make command to build the product.
6. After the make is complete, enter the make install command to install Apache.
7. After Apache is installed, modify the httpd.conf file located in the PREFIX/conf directory, in
which PREFIX is normally /usr/local/apache2. The following are the changes that must be
made.
 ServerAdmin you@example must be changed to your email address.
 ServerName must be set to Port 80, plus the DNS name, or the IP address of this new web
server. For example, a ServerName could be 10.7.78.144:80.
 DefaultType text/plain must be modified to be DefaultType application/octet-
stream.

Note:
This is the minimum set of changes needed to enable the basic
web server functionality. HP recommends that you see to the
Apache documentation for full details regarding server
configuration.

8. Next, start the Apache server. The command to start the server is:
PREFIX/bin/apachectl -k start
PREFIX/bin/apachectl -k stop

Note:
If updating an existing Apache server after changing the
httpd.conf file, be sure to stop and restart the web server
first

9. Download the HP BladeSystem Firmware Update Bundles from http://hp.com. Links to the
latest versions are posted on the BladeSystem Compatibility Chart web pages at
http://www.hp.com/go/bladesystemupdates . The file is named:
hp_blade_fw_bundle-<version>.linux.tar.gz for Linux.
10. To extract the Linux bundles, untar/unzip the downloaded file as follows:
tar zxvf hp_blade_fw_bundle-<version>.linux.tar.gz.
Find the bp00xxxx.txt file extracted from the bundle, and determine the OA firmware
component.
11. Execute the OA firmware component to extract the firmware .bin file contained within it by
using the following commands:
Linux ./CP01xxxx --unpack=<dir_path>
(dir_path is the location of the Apache web server files which default to
/usr/local/apache2/htdocs)

63
 12. Create a simple HTML file in the web server root. For Apache, this is typically
/usr/local/apache2/htdocs, which is used to test the web server. Use the following
example to create the default file. The file is typically named index.html.
<html>
<head>
<title>OA Firmware</title>
</head>
<body>
<a name="top"></a>
<h1>OA Firmware Binaries</h1>
<h2>Contents</h2>
<p>
<a href="hpoa252.bin">OA Firmware 2.52</a>
<p>
</body>
</html>

13. Once the file is saved into the web server root directory (/usr/.local/apache2/htdocs), go
to another workstation, open a browser, and try to load the newly created web page for
example, http://<workstation_IP_address/index.html). Once the page is loading, verify the
download of the binary file to the workstation works. This simulates the same type of interface
the OA uses to pull the newly created file from the web server.
14. If the file is successfully downloaded, go to the Configuring the SSH keys for scripted
installations.

Configuring the SSH keys for scripted installations

To script deployments by using the OA command-line interface and not having to supply the OA
administrator password when each script is executed, you must generate public key pairs and upload
them to the OA from the system locations where updates occur.
For Windows, download the OpenSSH software as discussed in Obtaining all necessary files. Once
the OpenSSH zip file is downloaded, unzip it, and install the previously prepared setupssh
executable on the web server.
For Linux, ensure the SSH RPM is installed.
Once SSH support is installed, you must generate the SSH keys by using the ssh-keygen executable.
To generate a key, use the following commands.
Windows:
C:\Program Files\OpenSSH\bin\ssh-keygen -t dsa -C
Administrator -f id_dsa
Linux:
ssh-keygen -t dsa -C Administrator

Note:
The parameter after the -C must be an OA administrator ID and is case-
sensitive. If you are using an OA administrator ID other than Administrator,
substitute it here.

Note:
You can generate an RSA-based key in place of the DSA-based key by
changing out the dsa parameter with rsa. For more details on selecting
the appropriate key for a deployment environment, consult the ssh-
keygen documentation.

64
Note:
If prompted for a pass-phrase, the phrase must be left empty by pressing
Enter. If any pass-phrase is entered, the automated script process will fail as
the pass-phrase will be prompted for when the script is initiated.

The resulting keys are placed in the following file locations:

Windows:
Private key: C:\Program Files\OpenSSH\bin\id_dsa
Public key: C:\Program Files\OpenSSH\bin\id_dsa.pub

Note:
The files will default to the current directory or the directory indicated in the
-f parameter.

Linux:
Private key: /root/.ssh/id_dsa
Public Key: /root/.ssh/id_dsa.pub

Important:
To maintain security, the private key must be on the system where it was
generated and protected. The public key can be sent to other computers
and devices such as the OA without worry of compromising security.

Once the public key is generated, copy it to the web server root directory (c:\inetpub\wwwroot for
IIS and /usr/local/apache2/htdocs for Apache) so you can pull it with the OAs that are
configured to support the automated scripting as described in Uploading the SSH Keys to the OAs.
Uploading the SSH keys to the OAs
The SSH key can be uploaded into the OA so scripts can be executed from the workstation location
where the SSH public keys are generated without the need to enter a password for each script.
Figure 2 shows the OA screen where the SSH keys are uploaded.

65
 Figure 2. SSH Administration OA screen

The steps to upload the SSH keys follow.

1. Browse to the OA web interface, and log in with administrator credentials.
2. Click Users/Administration under Systems and Devices on the left panel.
3. Click SSH Administrator to open the SSH administrator panel.
4. To upload the key, perform the following options:
(a) Open the id_dsa.pub file in Notepad, copy the entire key, and then paste it into the
Authorized SSH Keys panel at the top of the web page.
(b) Enter the URL to the web server file (http://<web_server_ip_address/id_dsa.pub) if
the file was copied into the web server root directory.
5. Press the Apply button to upload the key from the web server, or accept the pasting of the
contents.
6. Once the SSH keys have been uploaded, update the OA firmware.

66
Updating the OA firmware once the web server successfully configures
To update the OA from its CLI interface once the web server is properly configured, follow these
steps.
1. Create a script with the following command in it:
Windows:
C:\Program Files\OpenSSh\bin\ssh [email protected] update image
http://16.89.1.88/hpoa252.bin

where:
“Administrator” is the OA administrator account to be used
“16.89.1.3” is the Active OA IP address
“http://<web_server_address/<file_to_download>” should match the web server and file
created above.

Linux:
ssh [email protected] update image http://16.89.1.88/hpoa252.bin

where:
“Administrator” is the OA administrator account to be used
“16.89.1.3” is the Active OA IP address
“http://<web_server_address/<file_to_download>” should match the web server and file
created above.

2. During the process, the SSH command reports the link is terminated because the firmware
process is initiated. Wait for 3-5 minutes before attempting to reconnect to the OA to allow
time for the firmware update process to complete. Once the SSH interface is re-enabled by the
OA after the firmware update is complete, issue the following command to pull the System Log
from the OA.
Windows:
C:\Program Files\OpenSSh\bin\ssh [email protected] show
syslog enclosure

Linux:
ssh [email protected] show syslog enclosure

The returned data contains output, such as the following example Search for entries similar to this
output to validate that the firmware update is successful.
Sep 17 11:07:13 OA: Administrator logged out of the Onboard Administrator
Sep 17 11:07:22 OA: Administrator logged out of the Onboard Administrator
Sep 17 11:10:05 OA_Flash: Firmware image flashed from 2.51 to 2.52
Sep 17 11:10:11 OA: Onboard Administrator is rebooting
Sep 17 11:10:58 Kernel: Network link is up at 100Mbps - Half Duplex
Sep 17 11:10:59 OA: Got IP address = 16.89.1.3
Sep 17 11:10:59 OA: Time zone changed to CDT+5
Sep 17 11:11:03 OA: LCD Status is: OK.
Sep 17 11:11:03 OA: A USB Key was inserted into the Onboard Administrator.
Sep 17 11:11:05 Enclosure-Link: Service started
Sep 17 11:11:06 OA: Onboard Administrator booted successfully

Note:
For details on any error messages returned by a failed update operation
and the steps to recover, see the HP BladeSystem Onboard Administrator
User Guide.

67
 Scenario 3A: Updating the VC firmware using VCSU
General requirements
There are a number of general requirements that must be met to update VC firmware.
 Install Microsoft Windows XP (Service Pack 1 or 2), Windows Server 2003, Windows Server
2008, or Windows Vista OSs on the client.
 Upload Administrative or Power User privileges on the client system to install and run the utility
when upgrading from VC 4 Gb FC module 1.31 or earlier.
 Install a valid HP VC firmware package. Download the firmware from the HP website
(http://www.hp.com). Click Software and Driver Downloads, and then search for VC Firmware.
 Do not close the console application when a firmware update is in progress. If the application is
closed before the update completes, the module firmware might not update properly, causing the
module firmware to be inoperative.
 Have an OA user account with Administrative privileges and access to all OAs and interconnect
bays available for use. If the enclosure is imported into a VC domain, a VC user account with
domain privileges is also required.
 Ensure Ethernet network connectivity between the client system and the enclosure OA. To validate
this connectivity, open a web browser to the enclosure OA before running the utility.
 Ensure Ethernet network connectivity between the client system and the interconnect modules in the
enclosure.
 Add the VCSU application to the list of exceptions for any host-based firewall on the client.
 Know that no firewalls can exist between the client system and the remote enclosure OA. If a
firewall exists, and it is blocking ports, the utility cannot open a connection with the remote modules
to perform the update.
 Install OA firmware 1.30 or later on the target enclosure. HP recommends OA firmware 2.25 and
later.
 Run only one instance of the VCSU to access a single enclosure on one single client at one time.
 Know that during firmware update operations, the modules are unavailable for use. Any attempt to
reset or remove the modules during the update process could result in a corrupted firmware image.
In addition, do not reset the OA of the target enclosure or update its firmware while VC modules
are being updated. Doing so can interfere with the firmware update process and cause it to fail.
During the firmware update process, connectivity through the modules, which might be hosted to
servers in the enclosure, can be temporarily interrupted.
 Use a single client to update modules in a specific remote enclosure during a firmware update
session. Using multiple clients to interface remotely with the same enclosure can interrupt the
firmware update process and prevent it from completing successfully.
 Reset the affected module and restart the firmware update process if the firmware update client is
interrupted or loses network connectivity during the update.
 Know that if you use VCEM, the VC domains must be placed in Maintenance Mode, or the
firmware updates are blocked.

68
Before the upgrade begins
Before using VCSU to update VC firmware, perform the following pre-installation checks to ensure the
health of the VC domains.
1. Back up the current VC configuration as follows:
o Log in to VCM through a supported browser by browsing to the IP address or
DNS name of the VCM and providing administrator credentials.
o Select Tools/Backup Restore Domain Configuration from top menu.
o Select Backup Configuration, and then click OK.
o Save the file to your system in case it is needed for recovery at a later time.
o Log out of VCM, and close your browser.
2. Run a health check by using the VCSU on the VC domain.

Item Description

Syntax vcutil -a healthcheck -i <IP> -u <USER> -p <PWD>

Parameters

IP IP address of the active OA in the enclosure1

USER Name of the OA user with privileges to access all enclosure interconnect bays

PWD Password of the OA user

Note:
In a multi-enclosure environment or when redundant OA modules are
present, this must be the IP address of the active OA in the primary
enclosure.

Example
List the state of modules in an enclosure:
vcutil -a healthcheck -i 192.168.0.100 -u Administrator -p password

After these checks have been performed and completed successfully, you can use VCSU to upgrade
the firmware.

Important:
If you are using the VCEM to manage your VC domains, you must place
them in Maintenance mode before using the VCSU utility.

To update VC firmware by using VCSU, the VC firmware component must be downloaded from the
web by following the steps above.
1. Download the HP BladeSystem Firmware Update Bundles from the hp website. Links to the
latest versions are posted on the BladeSystem Compatibility Chart web pages located at
http://www.hp.com/go/bladesystemupdates. The file is named hpblade_fw_bndl-
<version>.w2k3.i386.exe for Windows.
2. To extract the Windows bundles, execute the downloaded file, and select a location directory
to place the extracted files.

69
 3. Find the bp00xxxx.txt file that is extracted from the bundle, and determine the VC firmware
component numbers.

4. Execute the VC firmware components to extract the firmware .bin file by using the following
commands:

Windows: CP01xxxx (and then choose the Extract option and a directory to
unpack it to

Linux: ./CP01xxxx --unpack=<dir_path> (dir_path is where to unpack it to)

Once the firmware is downloaded and extracted, use the VCSU and the firmware identified for
update to execute from either a local Windows or Linux (requires VCSU 1.40 or later) workstation.
Because of the way VCSU works, the OA and VC credentials are required for the update process.
The OA credentials must administrator equivalent credentials so the VC can access specific data in
the OA to perform the VC firmware upgrade.
Updating the VC firmware
To update the VC firmware, use these steps:
1. Issue the following command from a console or MS-DOS Command prompt.
vcutil -a update -i <Primary OA IP> -u <OA Admin account> -p <OA
password>
-l <path to firmware image>

2. When prompted, enter the VC Domain Level credentials.

3. Verify the report of discovered VC modules before continuing to ensure all modules in the
enclosure are updated.
If the report does not reflect the correct modules, browse to the OA web browser interface,
click on the Virtual Connect Manager link, and verify the configuration is valid and the health
check is successful again.
4. Enter YES when ready to update the VC firmware.

Note:
VC firmware updates can take from approximately 10 minutes to
as long as one hour, depending on the number and type of
modules in the enclosure. Do not restart modules or close the
window while the update process is in progress, or the firmware
update will fail.

5. After the VC firmware update process is complete, validate that all VC modules are successfully
updated.

Note:
To recover from a failed VC firmware update process, start over
with the pre-installation steps, and then restart the VC firmware
update process. If it fails a second time, contact HP Support.

70
 Important:
If the VC configuration is not redundant or if the VC firmware
version is earlier than version 1.34, a network fabric downtime
of up to 10 minutes can occur while the firmware is being
activated. This affects all servers in the enclosure and prevents
network access until the VC firmware is activated.

Note:
Because of the possibility of NIC fabric downtime during a VC
firmware installation, HP strongly recommends that you update
the VC from a workstation outside the enclosure to ensure
continuous network access to the firmware update utilities.

Scenario 3B: Updating the VC firmware using the HP SUM

Before using the HP BladeSystem Firmware Update Bundles and the embedded HP SUM to update
VC firmware, perform the following checks to ensure the health of the VC domains.
General requirements
There are a number of general requirements that need to be met to update VC firmware.
 Ensure that Microsoft Windows XP (Service Pack 1 or 2), Windows Server 2003, Windows Server
2008, or Windows Vista OSs is installed on the client.
 Make sure when upgrading from VC 4 Gb FC module version 1.31 or earlier, you have
Administrative or Power User privileges on the client system to install and run the utility.
 Make sure that valid HP VC firmware package is available to install. Download the firmware from
the HP website (http://www.hp.com). Click Software and Driver Downloads, and then search for
Virtual Connect Firmware.
 Ensure you have an OA user account with Administrative privileges and access to all OAs and
interconnect bays are available for use. If the enclosure is imported into a VC domain, you must
also have a VC user account with domain privileges.
 The user must have Ethernet network connectivity between the client system and the enclosure OA.
To validate this connectivity, open a web browser to the enclosure OA before running the utility.
 Ensure you have Ethernet network connectivity between the client system and the interconnect
modules in the enclosure.
 Confirm that you have OA firmware 1.30 or later as it is required on the target enclosure. HP
recommends OA firmware version 2.25 or higher.
 Know that during firmware update operations, the modules are unavailable for use. Any attempt to
reset or remove the modules during the update process could result in a corrupted firmware image.
In addition, do not reset the OA of the target enclosure or update its firmware while VC modules
are being updated. Doing so can interfere with the firmware update process and cause it to fail.
During the firmware update process, connectivity through the modules, which might be hosted to
servers in the enclosure, can be interrupted temporarily.
 Use only one single client to update modules in a specific remote enclosure during a firmware
update session. Using multiple clients to interface remotely with the same enclosure can interrupt the
firmware update process and prevent it from successfully completing.
 Reset the affected module and restart the firmware update process if the firmware update client is
interrupted or loses network connectivity during the update.

71
 Before the upgrade begins
Before using HP SUM to update VC firmware, perform the following checks to ensure the health of the
VC domains.
The first check is to back up the current VC configuration. To back up the current VC configuration,
use the following steps:
1. Log in to VCM through a supported browser by browsing to the IP address or DNS name of the
VCM and providing administrator credentials.
2. Select Tools/Backup Restore Domain Configuration from top menu.
3. Select Backup Configuration, and then click OK.
4. Save the file to your system in case it is needed for recovery at a later time.
5. Log out of VCM, and close your browser.

Another pre-installation check is to run a health check with the VCSU on the VC domain.

Item Description

Syntax vcutil -a healthcheck -i <IP> -u <USER> -p <PWD>

Parameters

IP IP address of the active OA in the enclosure1

USER Name of the OA user with privileges to access all enclosure interconnect bays

PWD Password of the OA user

1
In a multi-enclosure environment or when redundant OA modules are present, this must be the IP address of the active OA in the primary
enclosure.

Example
List the state of modules in an enclosure:
vcutil -a healthcheck -i 192.168.0.100 -u Administrator -p password

The last pre-installation check is for VCEM to set all VC domains into maintenance mode. Failure to do
this prevents the firmware update process from occurring.
Updating the VC firmware
Once these prerequisites have been completed, you can use the following instructions to update the
VC firmware on an individual or multiple enclosures by using the HP BladeSystem Firmware Update
Bundles for Windows or Linux.
1. Download the HP BladeSystem Firmware Update Bundles from http://hp.com.
Links to the latest versions are posted on the BladeSystem Compatibility Chart web pages
located at http://www.hp.com/go/bladesystemupdates. The files are names
hpblade_fw_bndl-<version>.w2k3.i386.exe for Windows and hp_blade_fw_bundle-
<version>.linux.tar.gz for Linux
2. To extract the Windows bundles, execute the downloaded file, and then select a directory for
the extracted files to be placed.
In Linux, simply untar/unzip the downloaded file as follows: tar zxvf hp_blade_fw_bundle-
<version>.linux.tar.gz.

Follow the steps described in Using HP SUM in GUI mode or Using HP SUM in Scripted or Silent
mode. Ensure the target device IP address or DNS name is the information for the active VCM
Interface NIC port. During the VC firmware update process, all VC modules including the Ethernet, 4
GB Fibre Channel and 8 GB Fibre Channel modules are updated. After the firmware is updated,
users may experience a brief network downtime as the VC resets the Ethernet modules. If the VC is set
72
up in a redundant fashion, there is no network downtime unless the VC firmware version is later than
1.34. If the VC firmware version is later than 1.34 or the VC is not configured redundantly, a network
fabric downtime of up to 10 minutes can occur. However, in most cases, the network is back up in
about one minute.

Note:
Because of the potential network downtime, updating the VC should only
be done when a maintenance window is available that allows for this
downtime.

Note:
Using the standby VC IP address instead of the active IP VC address causes
HP SUM to fail discovery for that target VC.

Note:
The firmware update process for all VC modules can take up to one hour,
and although the network downtime only occurs once, all firmware images
are uploaded to the VC modules. Older modules usually take longer to
flash than newer modules.

Important:
If the VC configuration is not redundant or if the VC firmware version is
later than 1.34, a network fabric downtime of up to 10 minutes can occur
while the firmware is activated. This affects all servers in the enclosure and
prevents network access until the VC firmware is activated.

Note:
Because of the possibility of NIC fabric downtime during a VC firmware
installation, HP strongly recommends that the VC be updated from a
workstation outside the enclosure to ensure continuous network access to
the firmware update utilities.

Note:
If HP SUM determines that only the VC Ethernet firmware must be updated,
HP SUM may select the component with Fibre Channel firmware that does
not match the installed configuration. This is caused by the way the VC
smart components are packaged.

Today, there are two smart components for VC firmware updates. The first
component contains the VC-Ethernet firmware and the 4-GB VC-FC
firmware. The second component contains the same VC-Ethernet firmware
and the 8-GB VC-FC firmware. Because HP SUM can use the VC-Ethernet
firmware from either component to update the VC Ethernet modules, it may
at times pick one that contains the other type of VC-FC firmware. This is not
an error as only the correct firmware is updated.

In the future, HP SUM will be updated to leverage VCSU within the

component and will be able to support a common component with all
firmware in it. At that time, the separate components are combined and the
problem no longer occurs.

73
 Scenario 3C: Updating the VC firmware in a DMZ (special case using
the OA virtual USB support)
This section contains information on how to update the VC firmware in the case when the VC module
may be hooked into the Internet and the user does not want to risk exposure of their internal network
with the external. In this section, the general requirements and prerequisites for installation should still
be validated. Once these are done, the binary firmware files for VC can be copied to a USB key and
inserted in the OA USB ports. From there, it is possible to update the VC firmware without exposing
the firmware image to the Internet.
General requirements
There are a number of general requirements that must be met to update VC firmware.
1. Have a valid HP VC firmware package must be available to install. Download the firmware
from the HP website (http://www.hp.com). Click Software and Driver Downloads, and then
search for Virtual Connect Firmware.
2. Have an OA user account with Administrative privileges and access to all OAs and
interconnect bays. If the enclosure is imported into a VC domain, you must also have a VC user
account with domain privileges.
3. Make sure you have Ethernet network connectivity between a client system and the active OA.
4. Ensure you have OA firmware 2.4x or higher because it is required on the target enclosure.
5. Know that during firmware update operations, the modules are unavailable for use. Any
attempt to reset or remove the modules during the update process could result in a corrupted
firmware image. In addition, do not reset the OA of the target enclosure or update its firmware
while VC modules are being updated. Doing so can interfere with the firmware update process
and cause it to fail. During the firmware update process, connectivity through the modules,
which might be hosted to servers in the enclosure, can be temporarily interrupted.

Before the upgrade begins

Before updating the VC firmware, perform these checks to ensure the health of the VC domains.
The first check is to back up the current VC configuration. To back up the current VC configuration,
follow these steps:
1. Log in to VCM through a supported browser by browsing to the IP address or DNS name of the
VCM and providing administrator credentials.
2. Select Tools/Backup Restore Domain Configuration from top menu.
3. Select Backup Configuration and click OK.
4. Save the file to your system in case it is needed for recovery at a later time.
5. Logout of VCM and close your browser.
The next check is to run a health check by using the VCSU on the VC domain.

Item Description

Syntax vcutil -a healthcheck -i <IP> -u <USER> -p <PWD>

Parameters

IP IP address of the active OA in the enclosure 1

USER Name of the OA user with privileges to access all enclosure interconnect bays

PWD Password of the OA user

1
In a multi-enclosure environment or when redundant OA modules are present, this must be the IP address of the active OA in the primary
enclosure.

74
Example
List the state of modules in an enclosure:
vcutil -a healthcheck -i 192.168.0.100 -u Administrator -p password

Note:
If you are using the VCEM to manage your VC domains, you must place
them in Maintenance mode before attempting to update the VC firmware.

Updating the VC firmware from a USB key in the OA

The following steps describe how to update the VC firmware using the OA port.
Once these prerequisites are complete, follow these instructions to update the VC firmware on an
individual or multiple enclosures by using the HP BladeSystem Firmware Update Bundles for Windows
or Linux.
1. Download the HP BladeSystem Firmware Update Bundles from the HP website.
Links to the latest versions are posted on the BladeSystem Compatibility Chart web pages
located at http://www.hp.com/go/bladesystemupdates. The files are named
hpblade_fw_bndl-<version>.w2k3.i386.exe for Windows and hp_blade_fw_bundle-
<version>.linux.tar.gz for Linux.
2. To extract the Windows bundles, execute the downloaded file, and then select a directory
location to place the extracted files.
In Linux, simply untar/unzip the downloaded file as follows:
tar zxvf hp_blade_fw_bundle-<version>.linux.tar.gz.
3. Locate the bp00xxxx.txt file that is extracted from the bundle and determine the VC firmware
component numbers.
4. Execute the VC firmware components to extract out the firmware .bin file by using the
following commands:
Windows: CP01xxxx (and then choose the Extract option and a directory
to unpack it to

Linux ./CP01xxxx --unpack=<dir_path> (dir_path is where to unpack

it to)
5. Copy the VC firmware update binary image file to the USB key. Place the file on the root of the
key so that OA can identify it.
6. Plug the USB key into the active OA in the enclosure.
7. Use SSH to log in to the OA Command-Line Interface, and then issue the show usbkey
command.
ssh -l Administrator 16.89.1.3 show usbkey

This example provides a list of ISOs, bins, and configuration files and their paths available on the
USB key.
Example:
Firmware Image Files Image Version
--------------------------------------- -------------
usb://d1/hpoa252.bin 2.52
usb://d1/vcfw212.bin 2.12

75
 Note:
If the c3000 with the KVM option module or the c7000 OA with
KVM support is used, it is possible to select the OA CLI from the
Enclosure KVM menu.

8. Identify the path to the image file that is needed to update the VC firmware.
9. Log into the VCM either through the OA browser interface or through the OA CLI on the KVM
console by using connect interconnect 1 or 2, based on which module is running VCM.
10. Use the VCM GUI or CLI to perform the VC firmware update from the web URL discovered in
Step 7 and concatenated with the OA IP address as follows.
http://,active-oa-ip-address>media/usbkey/d1/<VI-filename>
11. After the firmware update is complete, remove the USB key from the OA USB port.

Important:
If the VC configuration is not redundant or if the VC firmware
version is earlier than 1.34, a network fabric downtime of up to
10 minutes can occur while the firmware is activated. This affects
all servers in the enclosure and prevents network access until the
VC firmware is activated.

Note:
Because of the possibility of NIC fabric downtime during a VC
firmware installation, HP strongly recommends that the VC be
updated from a workstation outside the enclosure to ensure
continuous network access to the firmware update utilities.

Scenario 4: Updating an enclosure and blades with a previously

installed OS
The scenarios involving the HP BladeSystem Firmware Update Bundles and the HP Firmware
Maintenance CD are combined because updating an enclosure and blades when an OS is already
installed requires a systematic approach to ensure the firmware updates are installed and the
enclosure downtime is minimized. Even with all the tools available, there is no current single tool that
can update the firmware for blades, all options and network-based devices such as the OA and VC
without requiring the user to execute it multiple times. Currently, HP SUM can update almost all
enclosure and blade infrastructure, but may need to be booted into an offline mode by using either
the HP BladeSystem FDT or HP Firmware Maintenance CD to update Emulex, Brocade and QLogic FC
HBA or NetXen NIC firmware. This section provides a list of the steps to use to minimize the
downtime and ensure the firmware is updated in tandem between the various devices and hardware
in an enclosure.
The strategy for updating an enclosure should start with the server blades first, except when the VC
firmware is earlier than version 1.34.
Installation order
If the VC Ethernet firmware is 1.34 or later, or you are not using VC in your blade enclosures, HP
recommends the following is the recommended installation order based on whether or not an
OS is installed.

76
If an OS is already installed, follow these steps.
1. Update the blades and the OA by using the HP BladeSystem Online Firmware Bundles for
Windows and Linux from a workstation connected to the same network as the OA.
2. Use the HP BladeSystem FDT or HP Firmware Maintenance CD to update any offline only
firmware.
3. Use the VCSU from a workstation connected to the same networks as the OA and VC Ethernet
modules to update the VC firmware after all other updates have been applied, servers
rebooted, and all firmware activated.

If VC Ethernet firmware is earlier than 1 .34:

If the VC Ethernet firmware is earlier than version 1 .34, the following is the recommended
installation order regardless of whether an OS has been installed or not.
1. Update the VC firmware by using the VCSU from a workstation connected to the same
networks as the OA and VC Ethernet modules.
2. Update the server blades and the OA by using the HP BladeSystem Online Firmware Bundles
for Windows and Linux from a workstation connected to the same network as the OA.
3. Use the HP BladeSystem FDT or HP Firmware Maintenance CD to update any offline only
firmware.

Note:
The assumption in this scenario is that an OS has already been installed on
the blades. For information on how to install firmware on blades without an
OS, see Scenario 5: Updating an enclosure and blades without an existing
OS installed.

In almost all cases, the HP BladeSystem Firmware Update Bundles can be used to update firmware on
the blades using HP SUM. With the exception of NIC firmware updates, all other online server-based
firmware can be updated without interfering with normal server operations. A reboot is required after
all updates have been installed on a server. This stages all the firmware that updates the underlying
hardware but does not activate it until the server is rebooted. This reboot can occur in later
maintenance windows after the firmware has been staged to complete the firmware update process.
The OA and iLO firmware can also be updated without affecting the operation of the servers
themselves. Depending on how VC modules are configured and the version of VC firmware in use,
the VC firmware update may also be possible without affecting any servers in the enclosure.
If a blade contains hardware requiring offline mode firmware updates, such as Emulex, Brocade, or
QLogic adapters or NetXen NICs, the server must be taken offline and updated by using either the HP
BladeSystem FDT (preferred) or the HP Firmware Maintenance CD.
These deployment tools should be the second step in updating enclosure firmware after the HP
BladeSystem Firmware Update Bundles have updated the majority of firmware online. There are a
couple of reasons for the order of these steps.
The primary reason is to minimize the amount of downtime required to perform firmware updates. The
fewer updates that need to be performed offline, the quicker the server can return to its normal
production mode.
The second reason is that it prevents some situations where the firmware cannot be updated in the
offline environment. Examples of this include the restriction from updating iLO firmware if the iLO
Virtual Media is in use as it is when using the HP Firmware Maintenance CD and for updating
firmware that takes significant time to update such as the VC and OA firmware.

77
 If possible, the OA and blades should be updated together. If this is not possible, update the blades
first, and then focus on the OA firmware. It is possible to update the OA firmware concurrently with
the server blades in an online mode without any interruption to the network or server usage. HP
recommends updating the OA firmware with the server blades to minimize the time it takes to update
firmware in the enclosure and to ensure when the blades are rebooted, the OA firmware is quickly
updated to match the requirements of the HP BladeSystem Compatibility Chart. Using HP SUM as
provided in the HP BladeSystem Firmware Update Bundles to deploy the OA firmware allows any
dependencies between the OA firmware and other components to be comprehended during the
installation process.
Finally, the VC and other networking infrastructure should be updated. These devices take large
amounts of time to update and can cause networking and server outages so planning must be done to
accommodate large update windows (approximately 1-2 hours for all updates).
The following points summarize the important findings.
 If the VC Ethernet firmware is 1.34 or later, these are the recommended steps to update the
firmware in the enclosure.
1. Update the blades and the OA by using the HP BladeSystem Online Firmware Bundles for
Windows and Linux by using the instructions in Scenarios 1A and 2A.
2. Use the HP BladeSystem FDT or HP Firmware Maintenance CD to update any offline only
firmware by using the instructions in Scenarios 1B and 1C:
3. Use the VCSU to update the VC firmware after all other updates have been applied, servers
rebooted, and all firmware is activated by using the instructions in Scenario 3A.

 If the VC Ethernet firmware is earlier than 1.34, these are the recommended steps to update the
firmware in the enclosure.
1. Use the VCSU to update the VC firmware as described in Scenario 3A.
2. Update the blades and the OA first using the HP BladeSystem Online Firmware Bundles for
Windows and Linux by using the instructions in Scenarios 1A and 2A.
3. Use the HP BladeSystem FDT or HP Firmware Maintenance CD to update any offline only
firmware by using the instructions in Scenarios 1B and 1C.

Scenario 5: Updating an enclosure and blades without an existing OS

installed
The scenarios involving the HP BladeSystem Firmware Update Bundles and the HP Firmware
Maintenance CD are combined, because updating an enclosure and blades when an OS is not
installed (called bare metal or offline deployment) is usually only executed one-time when a blade first
arrives from the factory and is ready for deployment into an enterprise environment.
There are two deployment tools that you can use to install firmware updates when there is no OS
present. Each provides updates to the blade servers, but neither takes into account the enclosure-
based firmware. In these scenarios, HP still recommends a two-phased approach to leverage the HP
BladeSystem Firmware Update Bundles, along with either the HP BladeSystem FDT or HP Firmware
Maintenance CD to use together to deploy firmware updates to fresh enclosures.

Note:
You can use the BladeSystem Firmware Update Bundles to allow the VC,
iLO, and OA firmware to update remotely when using these bundles from a
Windows or Linux workstation.

78
Because an enclosure may not have a supported level of firmware on the OA, VC, and blades,
especially if they have sat on a shelf for a while before deployment, HP typically recommends the OA
firmware be updated first. These recommendations are being made because out-of-date OA and VC
firmware can cause issues that prevent blade servers from even powering on. Thus, using the
BladeSystem Firmware Update Bundles to update the OA firmware should be the first step in updating
the enclosure firmware. The second step should be to update the VC firmware in the firmware update
strategy for enclosures without an existing OS installed. HP strongly recommends that the VC firmware
be updated if it is earlier than version 1.34 to prevent network outages when the OA firmware is later
updated.
The next step in the strategy is to update the blade servers by using the HP BladeSystem FDT or the HP
Firmware Maintenance CD.

Note:
HP recommends updating the OA and VC firmware first, which is directly
opposite the recommendation for enclosures when an OS is already
installed on the blades. Because the recommendations are inverted, there
has been a lot of confusion in the field as to the installation order
recommended by BladeSystem development.

Summary
If the VC Ethernet firmware is 1.34 or later, HP recommends the following steps to update the
firmware in the enclosure.
1. Update the OA by using the HP BladeSystem Online Firmware Bundles for Windows and Linux
by using the instructions in Scenario 2A.
2. Use the VCSU to update the VC firmware after all other updates have been applied, servers
rebooted, and all firmware activated by using the instructions in Scenario 3A.
3. Use the HP BladeSystem Firmware FDT or HP Firmware Maintenance CD to update all server-
specific firmware by using the instructions in Scenarios 1B and 1C.

If the VC Ethernet firmware is earlier than 1.34, HP recommends the following steps be taken to
update the firmware in the enclosure.
1. Use the VCSU to update the VC firmware by using the instructions in Scenario 3A.
2. Update the OA by using the HP BladeSystem Online Firmware Bundles for Windows and Linux
by using the instructions in Scenario 2A.
3. Use the HP BladeSystem FDT or HP Firmware Maintenance CD to update all server-specific
firmware by using the instructions in Scenarios 1B and 1C.

Scenario 6: Scripted installation of firmware updates for multiple

enclosures, including the OA, VC, and server blades
Automation and scripting are the most complicated and the most rewarding items to implement for
enterprise administrator use. While there are many different processes that can be used to script
firmware deployments, this scenario focuses on leveraging existing tools for this functionality. This
scenario scripts the use of the BladeSystem Firmware Update Bundles through HP SUM to update the
OA firmware, the VCSU to update the VC firmware, and the HP BladeSystem FDT to update all server
blade firmware. Because the HP Firmware Maintenance CD does not have an automated option, it is
not considered for this automation process.
Before beginning, we will review the HP-recommended installation order to understand the process.

79
 If the VC Ethernet firmware is 1.34 or later, HP recommends the following steps to update the
firmware in multiple enclosures.
1. Use the BladeSystem Firmware Update Bundles and the included HPSUM tool to update the
OA firmware using the inputfile method.
2. Use the HP BladeSystem Firmware Deployment.
3. Use the VCSU to update the VC firmware Tool ISO image to update all server-specific
firmware.

If the VC Ethernet firmware is earlier than 1.34, HP recommends these steps to update the firmware in
multiple enclosures.
1. Use the VCSU to update the VC firmware.
2. Use the BladeSystem Firmware Update Bundles and the HPSUM tool to update the OA
firmware by using the inputfile method.
3. Use the HP BladeSystem FDT ISO image to update all server-specific firmware.

Note:
The following instructions focus on the effort needed to update, assuming
the VC firmware is at least at 1.34 or later. If the VC firmware is earlier
than 1.34, the setup is still the same but in the installation sequence, the
steps for the VC firmware update and the OA firmware update should be
reversed.

Because there is not a single tool available for updating all firmware in the BladeSystem infrastructure
at once, this must be handled as a multi-step process. A summary of the process involved follows.
1. Obtain all necessary files.
2. Set up either Microsoft IIS or Apache web servers.
3. Install OpenSSH (Windows only), and generate the SSH keys needed to automate the OA
communications process without the constant need to re-enter passwords.
4. Populate the web server and script directory with all necessary files.
5. Validate the iLO Advanced License is installed on each blade.
6. Update the iLO license for multiple servers to the iLO Advanced License if needed.
7. Obtain the iLO firmware version to confirm iLO firmware is at least at 1.50 or later, which is
necessary to support the automation process.
8. Script the deployment of the OA firmware update process by using the BladeSystem Firmware
Update Bundles and HP SUM.
9. Script the deployment of the VC firmware update process by using the BladeSystem Firmware
Update Bundles and VCSU.
10. Script the deployment of the HP FDT ISO image through the iLO Virtual Media support.

Obtaining all necessary files

The following files must be obtained to complete this scenario:
 OpenSSH for Windows (The SSH RPM must be installed for Linux)
http://softlayer.dl.sourceforge.net/project/sshwindows/OpenSSH%20for%20Windows%20-
%20Release/3.8p1-1%2020040709%20Build/setupssh381-20040709.zip
 A web server

80
 o Microsoft Windows Internet Information Server (obtained from Windows Server 2003/2008
installation CDs)
or
o Apache web server located at:
http://www.ecoficial.com/apachemirror/httpd/binaries/win32/apache_2.2.13-win32-x86-
openssl-0.9.8k.msi
 HP BladeSystem Firmware Update Bundles for Windows or Linux
o Windows located (choose highest numbered directory for the latest version) located at
ftp://ftp.hp.com/pub/softlib2/software1/supportpack-windows/p1116845569\
o Linux located (choose highest numbered directory for the latest version) located at
ftp://ftp.hp.com/pub/softlib2/software1/supportpack-linux/p1418640128
 HP BladeSystem FDT ISO (choose highest numbered directory for the latest version) located at
ftp://ftp.hp.com/pub/softlib2/software1/cd/p1255591055
 Perl RPM for Linux only
For more information, see the Linux distribution CD/DVDs to obtain the Perl RPM. Perl is required
for the Linux RIBCL scripts to work.
 Perl-IO-Socket-SSL RPM for Linux only
See the Linux distribution CD/DVDs to obtain this RPM. The Perl SSL socket support is required for
the Linux RIBCL scripts to work.
 Perl-Net-SSLeay RPM for Linux only
See the Linux distribution CD/DVDs to obtain this RPM. The Perl network interface with SSL is
required for the Linux RIBCL scripts to work.
 Expect RPM for Linux only
See the Linux distribution CD/DVDs to obtain the expect RPM. Expect is required for HPSUM to be
able to remotely deploy the OA and VC firmware in Linux
After the files have been obtained, you must set up a web server. The basics for installing and setting
up a basic Microsoft IIS and Apache web server for Linux follow.
Setting up the Microsoft IIS web server
The web server should be a system that houses the files and serves them for the OA and other
devices, if configured. The web server setup is a one-time operation. After it has been set up, files can
be added to the web server so that updates can be easily handled when new versions of the various
deployment tools are released.
To install Microsoft IIS, follow these steps:
1. Use the Add or Remove Programs Option in Control Panel (Windows Server 2003) or add the
role of web server (IIS) (Windows Server 2008) to install IIS.
2. Visit the Microsoft Update site to ensure all fixes are installed prior to enabling IIS to prevent
possible security breaches.
3. Once the web server is setup, locate and click the Internet Information Services (IIS) Manager
option in the Start menu to launch the web configuration manager.
4. Click Web Sites, click Default Web Sites, click Properties, and then click Home Directory to
locate the web server root file system.
For IIS, this is typically c:\inetpub\wwwroot. Once the home directory is determined, ensure
the Write option is not checked to prevent unauthorized writing to the web server.
5. Next, click the HTTP Headers tab, and then click MIME Types.
6. In the MIME Types dialog, add three new MIME types as shown if they do not already exist.

81
 Extension MIME Type

.img application/octet-stream
.iso application/octet-stream
.bin application/octet-stream

7. Click OK, click Apply, and then click Exit to exit the IIS Manager.
8. Skip the next section about setting up an Apache server and continue with the Configuring the
SSH keys for scripted installations section that follows.

Setting up the Apache web server in Linux

The web server should be a system that houses the files and serve them for the OA and other devices,
if configured. The web server setup is a one-time operation. After it has been set up, files can be
added to the web server so that updates are easily handled when new versions of the various
deployment tools are released.
To install the Apache web server, follow these steps:
1. Download the Apache web server from the Apache mirror site or directly from the Apache
HTTP Server website at http://httpd.apache.org/.
2. Extract the files by using the tar zxvf httpd-<version>.tar.gz command.
3. Change directory to the httpd-<version> directory.
4. Execute the configure command to configure Apache:
./configure --prefix=/usr/local/apache2

The --prefix directory becomes the web server root location. The default location for Apache is
/usr/local/apache2 in Linux.

1. Once Apache is configured, run the make command to build the product.
2. After the make is complete, use the make install command to install Apache.
3. After Apache is installed, you have to modify the httpd.conf file located in the PREFIX/conf
directory, when PREFIX is typically /usr/local/apache2. The changes that need to be made
are as follows:
 ServerAdmin you@example must be changed to your email address
 ServerName must be set to Port 80 plus the DNS name or the IP address of this new web
server. For example, a ServerName could be 10.7.78.144:80
 DefaultType text/plain must be modified to DefaultType application/octet-
stream.

Note:
This is a minimum set of changes to enable the basic web server
functionality. It is recommended that the user see the Apache
documentation for full details regarding server configuration.

82
 4. Next, the Apache server needs to be started. The command to start the server is:
PREFIX/bin/apachectl -k start
PREFIX/bin/apachectl -k stop

Note:
If updating an existing Apache server after changing the
httpd.conf file, be sure to stop and restart the web server first.

5. Continue to the next section to configure the SSH keys needed for scripted installation.

Configuring the SSH keys for scripted installations

To script deployments by using the OA command-line interface and not have to enter the OA
administrator password when each script is executed, it is necessary to generate public key pairs and
upload them to the location where the OA systems updates occur.
For Windows, download the OpenSSH software as shown in Obtaining necessary files. Once the
OpenSSH zip file has been downloaded, unzip it, and install the setupssh executable on the web
server that was previously prepared.
For Linux, ensure the SSH RPM is installed.
Once SSH support is installed, it is necessary to generate the SSH keys by using the ssh-keygen
executable. To generate a key, use the following commands.
1. Windows:
C:\Program Files\OpenSSH\bin\ssh-keygen -t dsa -C Administrator -f id_dsa

Note:
If the Windows system is an x64-based version, the directory location will
be C:\Program Files (x86)\OpenSSH\bin.

2. Linux:
ssh-keygen -t dsa -C Administrator

Note:
The parameter after the -C must be an OA administrator ID and is case-
sensitive. If you are using an OA administrator ID other than Administrator,
it must be substituted here.

Note:
An RSA-based key can be generated in place of the DSA-based key above
by changing out the dsa parameter with rsa. Consult the ssh-keygen
documentation for more details on which key is appropriate to the
environment in which it is being deployed.

Note:
If prompted for a pass-phrase, the phrase must be left empty by pressing
Enter. If any pass-phrase is entered, the automated script process fails as
the pass-phrase is prompted for when the script is initiated.

83
 The resulting keys are placed in the following file locations:
3. Windows:
Private key: C:\Program Files\OpenSSH\bin\id_dsa
Public key: C:\Program Files\OpenSSH\bin\id_dsa.pub

Note:
If the Windows system is an x64-based version, the directory location will
be C:\Program Files (x86)\OpenSSH\bin.

Note:
The files will default to the current directory or the directory indicated in the
-f parameter.

4. Linux:
Private key: /root/.ssh/id_dsa
Public Key: /root/.ssh/id_dsa.pub

Important:
To maintain security, the private key must be on the system where it was
generated and protected. The public key can be sent to other computers
and devices such as the OA without worry of compromising security.

Once the public key has been generated, it can be copied to the root directory of the web server
(c:\inetpub\wwwroot for IIS and /usr/local/apache2/htdocs for Apache) so it can be
pulled by the OAs that are configured to support the automated scripting.
Uploading the SSH keys to the OAs
The following describes how to upload the SSH key into the OA so scripts can be executed from the
workstation where the SSH public keys were generated without the need to enter a password for each
script. Figure 3 shows the OA screen where the SSH keys are uploaded.

84
Figure 3. OA screen where the SSH keys are uploaded

The steps to upload the SSH keys follow.

1. Browse to the OA web interface, and log in with administrator credentials.
2. Click Users/Administration under Systems and Devices on the left panel.
3. Click SSH Administrator to open the SSH administrator panel.

To upload the key, perform on the following options:

1. Open the id_dsa.pub file in Notepad, copy the entire key, and paste it into the Authorized
SSH Keys panel at the top of the web page.
2. Provide the URL to the web server file (http://<web_server_ip_address/id_dsa.pub) if the
file was copied into the root of the web server as discussed above.
3. Click the Apply button to upload the key from the web server or accept the pasting of the
contents.
4. Once the SSH keys are uploaded, continue to the next section.

Populate the web servers and script directory with all necessary files
Once the web servers and SSH configuration is properly configured, it is now time to populate the
web server and local script directories necessary to execute the scripts with all files needed to update
the servers.
Populating the script directory
The script directory must be populated with all sample scripts you will use, plus HP SUM, VCSU, and
the VC, and OA firmware components files from the HP BladeSystem Firmware Update Bundles. The
following steps show how to put all of these files into a location on the workstation that you will use to

85
 update the servers. The script directory in this scenario is named c:\scripts in Windows and
/scripts in Linux.

1. Download the HP BladeSystem Firmware Update Bundles from http://hp.com.

Links to the latest versions are posted on the BladeSystem Compatibility Chart web pages and
can be accessed at http://www.hp.com/go/bladesystemupdates. The files are named
hpblade_fw_bndl-<version>.w2k3.i386.exe for Windows and hp_blade_fw_bundle-
<version>.linux.tar.gz for Linux.
2. To extract the Windows bundles, execute the downloaded file and select the c:\scripts
directory location to place the extracted files.
In Linux, copy the file to the /scripts directory and untar/unzip the downloaded file as follows:
tar zxvf hp_blade_fw_bundle-<version>.linux.tar.gz.
3. Find the bp00xxxx.txt file that is extracted from the bundle, and determine the component
numbers for the VC firmware components.
Record these values for use later in the scripts.
4. Download the HP BladeSystem FDT from http://hp.com.
Links to the latest versions are posted on the BladeSystem Compatibility Chart web pages
located at http://www.hp.com/go/bladesystemupdates.
5. Extract the FDT file from the downloaded zip file.
There are a number of files to unzip/unpack, including the default scripts that are provided
with the FDT. HP will modify these scripts later to ensure they are unzipped/unpacked into the
c:\scripts or /scripts directory.

Populating the web server directory

1. Once all of the files have been positioned correctly in the c:\scripts or /scripts
directories, you must copy the FDT ISO file to the c:\inetpub\wwwroot or
/usr/local/apache2/htdocs directories so the web server can serve this file. The name of
the FDT ISO is of the format BB<version>.<Year>.<Date>.<Build_Number>.iso. In the
previous example the file name to copy is BB160.2009_0726.26.iso.
2. Once the FDT ISO is copied, you must verify that the web server is set up correctly.
Do this by creating a simple HTML file in the root of the web server (for IIS, this is normally
c:\inetpub\wwwroot) to use to test out the web server. The following example can be used to
create this default file. The file is normally named index.html.
<html>
<head>
<title>Firmware Deployment Tool Download
Page</title>
</head>
<body>
<a name="top"></a>
<h1>Firmware Deployment Tool</h1>
<h2>Contents</h2>
<p>
<a href="BB160.2009_0726.26.iso">FDT
1.60</a>
<p>
</body>
</html>

86
 3. Go to another workstation, open a browser, and try to load the web page that was just created
on the web server, (for example, http://<workstation_IP_address/index.html). Once
the page is loading, verify the download of the binary file to the workstation works. This is
important as this is simulating the same type of interface the OA uses to pull the file from the
newly created web server.

Now that the file system has been populated and the web server verified, write a few RIBCL XML files
and SSH scripts. The following sections show the RIBCL XML files and an SSH script to obtain all the
iLO addresses based off just the OA IP address and userid. All SSH commands are based on having
the SSH key support as previously noted.

Important:
All RIBCL scripts require a LOGIN element. However, the data placed in
this field, as long as it is not invalid XML data, is not used for the
installation. These elements are overridden by the external scripts that HP
writes around these functions.

Installing necessary RPMs in Linux

At this point, it is necessary to install the perl perl-IO-Socket-SSL, perl-Net-SSLeay, and
expect RPMs from the distribution CDs for the version of Linux being used on the workstation. Without
these RPMs installed, the RIBCL commands used by the UpdateBladeFirmware.sh script and the HP
SUM commands to update OA and VC firmware will fail.
Obtaining a list of all iLO IP addresses by querying the OA for them
The first command we will look at is the SSH command to return a list of iLO IP addresses in a given
enclosure with just the IP address for the OA and the OA Administrator ID used when we created the
SSH keys previously. The show server list command takes a single SSH command and returns
data allowing us to confirm the OA firmware version, OA role, and a list of all blades and their iLO
IP addresses. This command can be executed against a number of enclosures to obtain all the iLO IP
addresses, aggregate these addresses and allow different operations to be performed in batch mode.
The command is:
ssh -l Administrator 16.89.1.3 show server list

A sample of the output from this command follows:

87
 C:\scripts>ssh -l Administrator 16.89.1.3 show server list

-----------------------------------------------------------------------------
WARNING: This is a private system. Do not attempt to login unless you are an
authorized user. Any authorized or unauthorized access and use may be moni-
tored and can result in criminal or civil prosecution under applicable law.
-----------------------------------------------------------------------------
Firmware Version: 2.52
Built: 07/13/2009 @ 14:01
OA Bay Number: 1
OA Role: Active

HP BladeSystem Onboard Administrator

(C) Copyright 2006-2009 Hewlett-Packard Development Company, L.P.

OA-0018FE2737AD [SCRIPT MODE]> show server list

Bay iLO Name iLO IP Address Status Power UID Partner

--- ----------------------------- --------------- -------- ------- --- -------
1 ILO2UX91700UU 16.89.2.173 OK Off Off
2A BladeILO 16.89.1.79 OK Off Off
2B ILOTWT750009P 16.89.1.78 OK Off Off
3A ILOTWT742005A 16.89.1.58 OK On Off
3B ILOTWT742001C 16.89.2.172 OK On Off
4 ILOMXQ91600J2 16.89.1.49 OK Off Off

Validating the iLO Advanced License is installed on each blade

Now that we have a way to obtain a list of iLO IP addresses as shown above, we need to write
several RIBCL XML files that is used later to build our scripts. The XML files contain the same format
and data regardless of whether or not we plan to execute the m from a Windows or Linux system.

Note:
The login name and password within the RIBCL XML file is not used. It is
there because iLO requires an entry in this field. Set the Password field to
DoesNotMatter to show it doesn’t matter what you put in these fields, as
long as it is valid XML data.

The XML file below is named Get_ILO_Firmware_Version.xml in the scripts created later. It is the
same as the command to retrieve the iLO firmware version information below, but for clarity purposes,
a separate XML file is created.
<!-- FDT RIBCL Sample Script for HP Lights-Out Products -->
<!-- Copyright (c) 2009 Hewlett-Packard Development Company, L.P. -->

<!-- Description: This is a sample XML script to insert a virtual -->

<!-- media image -->

<RIBCL VERSION="2.0">
<LOGIN USER_LOGIN="Administrator" PASSWORD="DoesNotMatter">
<RIB_INFO MODE="read">
<GET_FW_VERSION/>
</RIB_INFO>
</LOGIN>
</RIBCL>

88
When we create a script later, the output from issuing this XML file against the iLO is similar to the
output example follows.
<?xml version="1.0"?>
<RIBCL VERSION="2.22">
<RESPONSE
STATUS="0x0000"
MESSAGE='No error'
/>
<GET_FW_VERSION
FIRMWARE_VERSION = "1.78"
FIRMWARE_DATE = "Jun 10 2009"
MANAGEMENT_PROCESSOR = "iLO2"
LICENSE_TYPE = "iLO 2 Standard Blade Edition"
/>
</RIBCL>

This output means the blade does not have an iLO Advanced license. Because of this, the blade is
unable to support scriptable virtual media and must use the OA GUI (as described in Scenario 1B:
Updating a server using the HP BladeSystem FDT.) to update an enclosure through the OA Virtual
Media pass-through feature. Output similar to the following example means the blade is supported for
scriptable virtual media.
<?xml version="1.0"?>
<RIBCL VERSION="2.22">
<RESPONSE
STATUS="0x0000"
MESSAGE='No error'
/>
<GET_FW_VERSION
FIRMWARE_VERSION = "1.79"
FIRMWARE_DATE = "Aug 26 2009"
MANAGEMENT_PROCESSOR = "iLO2"
LICENSE_TYPE = "iLO 2 Advanced"
/>
</RIBCL>

Finding the version of iLO firmware on each blade

The next RIBCL XML file allows us to verify the version of iLO firmware is at least 1.50. This is required
for us to execute all scripts without any problems. The XML files contain the same format and data
regardless of whether or not we plan to execute them from a Windows or Linux system.

Note:
The login name and password within the RIBCL XML file is not used. It is
there because iLO requires an entry in this field. Set the Password field to
DoesNotMatter to show it doesn’t matter what you put in these fields, as
long as it is valid XML data.

The XML file that follows is named Get_ILO_Firmware_Version.xml in the scripts created later. It is
the same command to retrieve the iLO license version information, but for clarity purposes, a separate
XML file is created.
<!-- FDT RIBCL Sample Script for HP Lights-Out Products -->
<!-- Copyright (c) 2009 Hewlett-Packard Development Company, L.P. -->

<!-- Description: This is a sample XML script to insert a virtual -->

<!-- media image -->

89
 <RIBCL VERSION="2.0">
<LOGIN USER_LOGIN="Administrator" PASSWORD="DoesNotMatter">
<RIB_INFO MODE="read">
<GET_FW_VERSION/>
</RIB_INFO>
</LOGIN>
</RIBCL>

The output from this command is similar to the following example.

<?xml version="1.0"?>
<RIBCL VERSION="2.22">
<RESPONSE
STATUS="0x0000"
MESSAGE='No error'
/>
<GET_FW_VERSION
FIRMWARE_VERSION = "1.78"
FIRMWARE_DATE = "Jun 10 2009"
MANAGEMENT_PROCESSOR = "iLO2"
LICENSE_TYPE = "iLO 2 Standard Blade Edition"
/>
</RIBCL>

The iLO firmware version is returned in the FIRMWARE_VERSION tag in the output.
Obtaining the current Virtual Media status for a blade
The GET_VM_STATUS RIBCL command returns the Virtual Media drive status. This command must
display within a RIB_INFO element as shown.

Note:
The login name and password within the RIBCL XML file is not used. It is
there because iLO requires an entry in this field. Set the Password field to
DoesNotMatter to show it doesn’t matter what you put in these fields, as
long as it is valid XML data.

The following XML file is named Get_VM_Status.xml in the scripts created later.
<!-- FDT RIBCL Sample Script for HP Lights-Out Products -->
<!-- Copyright (c) 2009 Hewlett-Packard Development Company, L.P. -->

<!-- Description: This is a sample XML script to obtain the virtual -->
<!-- media status -->
<RIBCL VERSION="2.0">
<LOGIN USER_LOGIN="Administrator" PASSWORD="DoesNotMatter">
<RIB_INFO MODE="read">
<GET_VM_STATUS DEVICE="CDROM"/>
</RIB_INFO>
</LOGIN>
</RIBCL>

The returned information from this command shows something similar to the following:

<?xml version="1.0"?>
<RIBCL VERSION="2.22">
<RESPONSE
STATUS="0x0000"
MESSAGE='No error'
/>
<GET_VM_STATUS>

90
 VM_APPLET="DISCONNECTED"
DEVICE="CDROM"
BOOT_OPTION="BOOT_ALWAYS"
WRITE_PROTECT="YES"
IMAGE_INSERTED="YES"
IMAGE_URL=http://192.168.1.77/BB160.2009_0726.26.iso
/>
</RIBCL>

Note:
Even though the VM_APPLET entry reads DISCONNECTED, this references
what the Virtual Media applet reflects when viewed through the iLO web
browser.

As can be seen from the previous results, the IMAGE_INSERTED should read YES and should also
point to the expected web server URL Address:
IMAGE_URL=http://192.168.1.77/BB160FDT.iso

Another point to observe is the BOOT_OPTION=BOOT_ALWAYS option. This ensures that despite any
customization of the Boot order in the Rom Based Setup Utility (RBSU), the server boots to the CDROM
drive first upon the next reboot, and then returns to the defaults as set in the RBSU settings. For the
FDT, the BOOT_OPTION should always be set to BOOT_ALWAYS instead of BOOT_ONCE as the BOOT_ONCE
option did not work in several versions of iLO2 firmware. Because the FDT ejects the ISO image once
it has completed the firmware update process, the BOOT_OPTION will be ignored on subsequent boots
because the image is no longer available to the server during boot.
Setting Virtual Media to boot on a blade
This RIBCL XML file allows you to set the virtual media that has been inserted to be the boot option for
the given server the next time the server is powered on. One thing to note is the
―BOOT_OPTION="BOOT_ALWAYS" option. This ensures that despite any customization of the Boot order
in the Rom Based Setup Utility (RBSU), the server boots to the CDROM drive first upon the next reboot,
and then returns to the defaults as set in the RBSU settings. For the FDT, the BOOT_OPTION should
always be set to BOOT_ALWAYS instead of BOOT_ONCE as the BOOT_ONCE option did not work in
several versions of iLO2 firmware. Because the FDT ejects the ISO image once it has completed the
firmware update process, the BOOT_OPTION is ignored on subsequent boots because the image is no
longer available to the server during boot.
The XML files contain the same format and data, regardless of whether or not you plan to execute
them from a Windows or Linux system.

Note:
The login name and password within the RIBCL XML file is not used. It is
there because iLO requires an entry in this field. Set the Password field to
DoesNotMatter to show it doesn’t matter what you put in these fields, as
long as it is valid XML data.

The following XML file is named Set_Virtual_Media_Status.xml in the scripts created later.
<!-- FDT RIBCL Sample Script for HP Lights-Out Products -->
<!-- Copyright (c) 2009 Hewlett-Packard Development Company, L.P. -->

<!-- Description: This is a sample XML script to set the boot option for a
virtual -->
<!-- media image on a given server -->

91
 <RIBCL VERSION="2.0">
<LOGIN USER_LOGIN="Administrator" PASSWORD="DoesNotMatter">
<RIB_INFO MODE="write">
<SET_VM_STATUS DEVICE="CDROM">
<VM_BOOT_OPTION value="BOOT_ALWAYS"/>
<VM_WRITE_PROTECT value="Y"/>
</SET_VM_STATUS>
</RIB_INFO>
</LOGIN>
</RIBCL>

The output from this command is similar to the following example.

<?xml version="1.0"?>
<RIBCL VERSION="2.22">
<RESPONSE
STATUS="0x0000"
MESSAGE='No error'
/>
</RIBCL>

The return status that no error occurred indicates the blade has successfully shut down and rebooted.
Inserting the virtual media on a blade
This RIBCL XML file allows us to insert virtual media for a given iLO. This allows the mounting of the
BladeSystem FDT ISO from the web server that was previously created. This is required for launching
the ISO image when the server is rebooted later in the scripts. The XML files contain the same format
and data, regardless of whether or not you plan to execute them from a Windows or Linux system.
In this command, it is important that the IMAGE_URL be the same as the URL created on the web server
and validated with the index.html file. This allows the iLO to mount the ISO image of the FDT from the
web server and boot it in the scripts later.

Note:
The login name and password within the RIBCL XML file is not used. It is
there because iLO requires an entry in this field. Set the Password field to
DoesNotMatter to show it doesn’t matter what you put in these fields, as
long as it is valid XML data.

The following XML file is named Insert_Virtual_Media.xml in the scripts created later.
<!-- FDT RIBCL Sample Script for HP Lights-Out Products -->
<!-- Copyright (c) 2009 Hewlett-Packard Development Company, L.P. -->

<!-- Description: This is a sample XML script to insert a virtual -->

<!-- media image -->

<RIBCL VERSION="2.0">
<LOGIN USER_LOGIN="Administrator" PASSWORD="DoesNotMatter">
<RIB_INFO MODE="write">
<INSERT_VIRTUAL_MEDIA DEVICE="CDROM" IMAGE_URL=""/>
</RIB_INFO>
</LOGIN>
</RIBCL>

92
If this script is used independent of the script provided later in this scenario, the IMAGE_URL=”” should
be set to a valid URL. An example of a valid IMAGE_URL value is:
IMAGE_URL="http://16.89.2.132/BB161.2009_0903.14.iso"

The output from this command is similar to the following example. The status of 0x0000 indicates the
virtual media was successfully inserted.
<<?xml version="1.0"?>
<RIBCL VERSION="2.22">
<RESPONSE
STATUS="0x0000"
MESSAGE='No error'
/>
</RIBCL>

Disconnecting the virtual media on a blade

This RIBCL XML file allows you to eject the virtual media for a given iLO. This allows the eject the
BladeSystem FDT ISO from the iLO once you have completed the update process. The XML files
contain the same format and data, regardless of whether or not you plan to execute them from a
Windows or Linux system.

Note:
The login name and password within the RIBCL XML file is not used. It is
there because iLO requires an entry in this field. Set the Password field to
DoesNotMatter to show it doesn’t matter what you put in these fields, as
long as it is valid XML data.

The following XML file is named Eject_Virtual_Media.xml in the scripts created later.
<!-- FDT RIBCL Sample Script for HP Lights-Out Products -->
<!-- Copyright (c) 2009 Hewlett-Packard Development Company, L.P. -->

<!-- Description: This is a sample XML script to eject virtual -->

<!-- media -->

<RIBCL VERSION="2.0">
<LOGIN USER_LOGIN="Administrator" PASSWORD="DoesNotMatter">
<RIB_INFO MODE="write">
<EJECT_VIRTUAL_MEDIA DEVICE="CDROM"/>
</RIB_INFO>
</LOGIN>
</RIBCL>

The output from this command is similar to the following example.

<?xml version="1.0"?>
<RIBCL VERSION="2.22">
<RESPONSE
STATUS="0x0000"
MESSAGE='No error'
/>
</RIBCL>

Determining the power state on a blade

This RIBCL XML file allows us to determine the current power state of a given server through the iLO.
This allows you to identify which power script to call when putting everything together. The XML files
contain the same format and data, regardless of whether or not you plan to execute them from a
Windows or Linux system.
93
 Note:
The login name and password within the RIBCL XML file is not used. It is
there because iLO requires an entry in this field. Set the Password field to
DoesNotMatter to show it doesn’t matter what you put in these fields, as
long as it is valid XML data.

The following XML file is named Get_Host_Power_Status.xml in the scripts created later.
<!-- FDT RIBCL Sample Script for HP Lights-Out Products -->
<!-- Copyright (c) 2009 Hewlett-Packard Development Company, L.P. -->

<!-- Description: This is a sample XML script to determine power -->

<!-- state on the host server
-->
<!-- This script will use the ACPI Power Button function to -->
<!-- attempt to gracefully shutdown the host operating system -->
<!-- (if your OS supports and is configured for graceful -->
<!-- shutdown) before it powers off the server. -->
<RIBCL VERSION="2.0">
<LOGIN USER_LOGIN="Administrator" PASSWORD="DoesNotMatter">
<SERVER_INFO MODE="write">
<GET_HOST_POWER_STATUS/>
</SERVER_INFO>
</LOGIN>
</RIBCL>

The output from this command is similar to the following example.

<?xml version="1.0"?>
<RIBCL VERSION="2.22">
<RESPONSE
STATUS="0x0000"
MESSAGE='No error'
/>
<GET_HOST_POWER
HOST_POWER="OFF"
/>
</RIBCL>

This example returns the status that the host power as OFF. The only difference between the previous
status and what would be returned if the power was on is the HOST_POWER would be set to ON.
Turning the power off on a blade
This RIBCL XML file allows you to turn off the power on a given server through the iLO. This is
equivalent to a Momentary Press when the server is notified that the OS must shut down gracefully.
This command only turns the power off. A second command must be issued to turn the power on after
the successful completion of this command. The XML files contain the same format and data
regardless of whether or not you plan to execute them from a Windows or Linux system.

Note:
The login name and password within the RIBCL XML file is not used. It is
there because iLO requires an entry in this field. Set the Password field to
DoesNotMatter to show it doesn’t matter what you put in these fields, as
long as it is valid XML data.

94
The following XML file is named Power_Off_Server.xml in the scripts created later.
<!-- FDT RIBCL Sample Script for HP Lights-Out Products -->
<!-- Copyright (c) 2009 Hewlett-Packard Development Company, L.P. -->

<!-- Description: This is a sample XML script to turn off the power -->
<!-- on the host server
-->
<!-- This script will use the ACPI Power Button function to -->
<!-- attempt to gracefully shutdown the host operating system -->
<!-- (if your OS supports and is configured for graceful -->
<!-- shutdown) before it powers off the server. -->

<RIBCL VERSION="2.0">
<LOGIN USER_LOGIN="Administrator" PASSWORD="DoesNotMatter">
<SERVER_INFO MODE="write">
<SET_HOST_POWER HOST_POWER="No"/>
</SERVER_INFO>
</LOGIN>
</RIBCL>

The output from this command is similar to the following example.

<?xml version="1.0"?>
<RIBCL VERSION="2.22">
<RESPONSE
STATUS="0x0000"
MESSAGE='No error'
/>
</RIBCL>

The return status that no error occurred indicates the power is now off on the blade the command was
issued against.
Turning the Power On for a blade
This RIBCL XML file allows us to turn on the power on a given server through the iLO. This command
only turns the power on. The server power must be off for this command to do anything. Issuing this
command against a server that is already on has no effect. The XML files contain the same format and
data, regardless of whether we plan to execute them from a Windows or Linux system.

Note:
The login name and password within the RIBCL XML file is not used. It is
there because iLO requires an entry in this field. Set the Password field to
DoesNotMatter to show it doesn’t matter what you put in these fields, as
long as it is valid XML data.

The following XML file is named Power_On_Server.xml in the scripts created later.
<!-- FDT RIBCL Sample Script for HP Lights-Out Products -->
<!-- Copyright (c) 2009 Hewlett-Packard Development Company, L.P. -->

<!-- Description: This is an XML script to turn on the power -->

<!-- on the host server -->
<RIBCL VERSION="2.0">
<LOGIN USER_LOGIN="Administrator" PASSWORD="DoesNotMatter">
<SERVER_INFO MODE="write">
<SET_HOST_POWER HOST_POWER="Yes"/>
</SERVER_INFO>
</LOGIN>
</RIBCL>

95
 The output from this command is similar to the following example.
<?xml version="1.0"?>
<RIBCL VERSION="2.22">
<RESPONSE
STATUS="0x0000"
MESSAGE='No error'
/>
</RIBCL>

The return status that no error occurred indicates the power is now on for the blade the command was
issued against.
Creating HP SUM Inputfiles
To update the OA firmware, HP recommends that HPSUM inputfiles be created. This new inputfile
mode is in beta format within HP SUM today and will be officially supported in the HPSUM 3.7.0
release. This ability allows network administrators to leverage the capability within HP SUM to script
multiple targets or groups within a single operation. Currently, there is a limit of 29 total targets for an
installation with HP SUM, although this number will soon be increased. The inputfile functionality can
be leveraged to streamline even further the updates for workgroup-sized groups of servers and
targets. The input file for the script can exist on a secure server or even a personal computer as long
as HP SUM is executed from this chosen platform. Using a secure server or a management console to
protect the credentials is essential to ensure administrator and root passwords are not exposed.
To create an inputfile, use Notepad or vi and the following file format.

Note:
All sections headers and trailers [END] must match.

Note:
Failure to use the SILENT=YES option causes the GUI mode to be used, but
the information provided allows a user to skip screens when information
has already been provided. The DRYRUN=YES option can be used to do
dry runs of installations to ensure the scripts are working without actually
deploying the firmware updates that may be needed on each target.

Note:
Remove the DRYRUN=YES option to actually perform the updates.

Examples of the HP SUM inputfile:

Example 1:
DRYRUN = YES
SILENT = YES

[TARGETS]
HOST = BL465C-01
HOST = 192.168.1.2
[END]

Example 2:
DRYRUN = YES
SILENT = YES

[TARGETS]
HOST=BL685cG6
UID = Bigboss2
PWD = password
[END]

96
In Example 1, two targets are passed for update. The targets do not necessarily have to be OAs as
they can be any target supported by HP SUM. In the second example, a host is passed along with the
userid and password to use for the hosts in the SCRIPSUM2 group.

Important:
The credentials can be left out of the file for greater security and passed on
the command-line to HPSUM. The only limitation of this is that the userid
and credentials must be the same on all

Once the file has been created, to use it with HP SUM simply add it as the --inputfile
<filename> parameter to a normal HP SUM command-line. For instance, if the name of the inputfile
is hpsum.in, the command-line syntax is hpsum --inputfile hpsum.in. Full paths can be added to
the inputfile location in the event it is not stored in the same location as the HP SUM executables.
At this point, if more than five enclosures are updated, HP recommends that the OAs IP addresses or
DNS names be added to an inputfile. This allows greater scripting flexibility and reuse of the inputfile
in future updates. If five or fewer enclosures are to be updated, the OA IP addresses can be passed
on the HPSUM command-line. Passing multiple target OAs to HPSUM allow for HPSUM to update the
OA firmware in parallel.
Extracting the VCSU and VC binary firmware files from the VC component
As discussed in Populate the web servers and script directory with all necessary files in Step 3, the VC
firmware component numbers are documented. In this step, extract these components to obtain the
VCSU and the binary firmware files needed by the VCSU to update the VC firmware.
To extract these components, use the following commands, substituting the virtual connect firmware
component numbers in each command. The commands must be executed twice to extract both
firmware components if needed. If the virtual connect enclosure either does not use or has only has
one type of VC Fiber Channel modules, only the component that provides the given type of VC Fiber
Channel module firmware needs to be extracted.
Execute the VC firmware components to extract out the firmware .bin file contained within it by using
the following commands:
4. Windows: CP01xxxx (and then choose the Extract option and a directory to unpack it to
5. Linux: ./CP01xxxx --unpack=<dir_path> (dir_path is where to unpack it to)
For the purposes of our scripts, the dir_path should be c:\scripts or /scripts.
Once the files have been extracted, it’s time to put everything together.

Putting it all together

Now that the environment, RIBCL scripts, HP BladeSystem bundles, and other configuration details are
complete, the next step is to put everything together.
As stated earlier, there are several steps that must be completed before everything can be put
together. To summarize, these steps include the following:
1. Obtain all necessary files.
2. Set up either Microsoft IIS or Apache web servers.
3. Install OpenSSH (Windows only), and generate the SSH keys needed to automate the OA
communications process without constant need to re-enter passwords.
4. Populate the web server and script directory with all necessary files.
5. Validate that the iLO Advanced License is installed on each blade.
6. Update the iLO license for multiple servers to the iLO Advanced License if needed.
97
 7. Obtain the iLO firmware version to confirm iLO firmware is at least 1.50 or later, which is
needed to support this automation process.
8. Script the deployment of the OA firmware update process by using the BladeSystem Firmware
Update Bundles and HP SUM.
9. Script the deployment of the VC firmware update process by using the BladeSystem Firmware
Update Bundles and VCSU.
10. Script deployment of the HP FDT ISO image through the iLO Virtual Media support.

To help with these steps a set of scripts are being provided starting with the 1.70 version of the FDT to
support this functionality. Before presenting the scripts, a brief understanding of the requirements and
process must be discussed.
The following scripts are working samples by using the configuration that has been FDT to an
enclosure of blades simultaneously using the SSH interface of the OA to return the list of iLO2 IP
addresses to attach the FDT ISO image via iLO2 Virtual Media feature. Because the iLO2 Virtual
Media feature can only be scripted when the iLO Advanced License is installed, this is a firm
requirement for this process. In addition, these scripts were only tested with the latest BladeSystem
Compatibility Chart versions. Though they should work with earlier versions of iLO firmware, there is
a chance, especially if the iLO firmware is earlier than version 1.60 that these scripts may not work.
A check is in the script to validate the iLO firmware is at least at 1.60 or later.
Update Blade firmware scripts
For the Update Blade Firmware scripts, the initial assumption is the blades that are being updated
have been powered off and may not have an OS installed. Because this isn’t always the case, the
script attempts to issue a gentle shutdown by simulating a power button press to any running OS.
Because of the security policies for Microsoft Windows and SUSE Linux Enterprise Server, either a
user must be logged into the server or the security settings must be changed to allow for a server to be
powered off without needing to provide the administrator or root-equivalent password.
The following steps show how to change the setting to allow the server to be powered down remotely.
In some instances, administrators may not want to implement these changes because of security
concerns, since these changes will allow anyone with access to the iLO credentials to power off a
server. For those administrators who choose not to implement these changes, the scripts will notify
them of any servers that are still powered on. These servers must then be manually powered down
before the FDT can be used to upgrade the firmware.
For those administrators who want to change the default settings and allow a remote user with iLO
credentials to gracefully power down a server, the following changes must be made.

Note:
In a default installation, Red Hat Enterprise Linux server does not require a
user to enter the root-equivalent password to shutdown the server. If the
default configuration is altered, the following steps in the Linux section must
be followed to re-enable the ability to remotely shutdown the server through
iLO.

Windows
To allow a Microsoft Windows-based system to be shutdown without having to logon, follow these
steps.
1. Click Start, and then select Administrative Tools.
2. Double click Local Security Policy.
3. Under the Local Policies option in the left window pane, click Security Options.

98
 4. In the right window pane, scroll down and double-click the option Shutdown: Allow system to
be shut down without having to log on.
5. In the dialog box that opens, change Disabled to Enabled, click Apply, and then click OK.

Linux
To allow a Linux based server with ACPI configured (which is normally the default), an event must be
registered in the /etc/acpi/events directory. In this directory, a file must be created, which we will
call power_off.conf. A sample power_off.conf script is shown.
event=button/power.*
action=/sbin/poweroff

If there are any additional scripts in the /etc/acpi/events directory, they must be renamed so they
do not end in the .conf extension.

Note:
The Linux server must be rebooted so the ACPI daemon will find and
register the event as specified in the above file. The Microsoft Windows
changes do not require a server reboot to take effect.

Note:
The UpdateBladeFirmware scripts should not be executed from a server
within the enclosure being updated as the servers will be powered off so
the FDT can be executed.

Follow these steps so that the scripts will perform the following operations.
1. Obtain the list of iLO2 IP addresses from the OA for the servers in the targeted enclosure.
2. Verify each iLO2 has iLO firmware 1.60 or later, and that an Advanced License is installed
3. Disconnect any iLO Virtual Media that may still be attached.
4. Attach the ISO image from the web site created in the previous steps and defined in the
WEB_URL parameter at the top of the script.
5. Set the iLO2 to BOOT_ALWAYS from the ISO image.
6. Issue a power down command to attempt to gracefully shutdown any OS that may be running
on a blade.
7. Once all blades are powered down, the scripts will power up each blade and exit.

The FDT will boot on each blade, update any firmware, eject the ISO image from the iLO virtual
media and reboot the server unless an error occurs during the firmware update process. The UID
lights can be used as discussed in the single server FDT scenario described in Scenario 1B: Updating
a server using the HP BladeSystem FDT.
To execute these scripts, use the following commands.
Windows
 UpdateBladeFirmware.cmd <OA_IP_Address> <ILO_ADMIN_ID> <ILO_PASSWORD>
 Ex. UpdateBladeFirmware.cmd 16.89.1.3 Administrator AdminPassword
Linux
 ./UpdateBladeFirmware.sh <OA_IP_Address> <ILO_ADMIN_ID> <ILO_PASSWORD>
 Ex. ./UpdateBladeFirmware.sh 16.89.1.3 Administrator AdminPassword

99
 Sample Windows Power Shell script to drive the FDT update process for an entire enclosure at once
UpdateBladeFirmware.ps1
##################################################################
#
# FDT Sample Script for Updating HP BladeSystem firmware
#
# Copyright(c) 2009 Hewlett-Packard Development Company, L.P.
#
##################################################################

#Change the WEB_URL to be the URL of the ISO image on the web server
#Please see the Firmware Best Practices Implementer's Guide for
#more information on how to configure the Firmware Update environment

$WEB_URL='"http://16.89.2.132/BB161.2009_0903.14.iso"'
$OAIP=$1
$USERNAME=$2
$PASSWORD= $3
$IPSTOUSE="ipaddrs.txt"
$TMPOA="tmpoa.txt"
$TMP="tmp.txt"
$OUTPUT="output.txt"
$ERR="error.txt"
$TMPRIBCL="ribcl.xml"

#Custom alias command for color-coded statements

#Will have to define foreground color in the statements
Set-Alias print Write-Host

function AttachVirtualMedia
{
$opts=$i
$IP=$i
$RC=0

print -foreground yellow "Now connecting virtual media to ILO2 IP address"

$IP
DetachVirtualMedia $IP
$RC=$?
if($RC -ne $true){
return $RC
}

ConnectVirtualMedia $IP
$RC=$?
if($RC -ne $true) {
print -foreground red "ERROR: Unable to connect virtual media on ILO2 IP
Address" $IP.
return $RC
}

CheckVirtualMediaState $IP
$RC = $?
if($RC -eq $true){
print -foreground green "Virtual media successfully connected on ILO2 IP
Address" $IP.
}
else{
print -foreground red "ERROR: Unable to connect virtual media on ILO2 IP
Address" $IP.
}
return $RC
}

function CheckILOReturnCodes
{
$ILORC=0
100
 cat $OUTPUT | select-string "STATUS" -context 0, 1 >$ERR
$var=cat error.txt
for($j=1; $j -le $var.length; $j++)
{ if($var[$j].length -gt 0)
{
if(($var[$j].Contains("STATUS") -eq $true) -and
($var[$j].Contains("0x0000") -ne $true))
{
print -foreground red "ILO Returned error Status:"$var[$j]
"Message:"$var[$j+1]
$j=$j+1
}
else{
print -foreground green "ILO did not returned any error"
}
}
}
del $ERR >$null 2>&1
return $ILORC
}

function CheckVirtualMediaState
{
$opts=$i
$IP=$i
$RC=0

print -foreground yellow "Now checking virtual media status on ILO2 IP

address" $IP
cat Get_VM_Status.xml | %{$_ -replace "Administrator","USERNAME"} | %{$_ -
replace "DoesNotMatter","PASSWORD"} | out-file -encoding ASCII $TMPRIBCL
.\cpqlocfg.exe -l $OUTPUT -s $IP -f $TMPRIBCL

CheckILOReturnCodes $IP
$RC=$?
if($RC -ne $true)
{
print -foreground red "ILO IP address" $IP "returned an error and cannot
continue."
return $RC
}
elseif((cat $OUTPUT | select-string 'image_inserted="yes"') -and (cat $OUTPUT
| select-string 'VM_APPLET="CONNECTED"'))
{
print -foreground yellow "A CD ISO image is inserted"
$VMRC=1
}
else{
print -foreground yellow "A CD ISO image is not inserted"
$VMRC=0
}

del $OUTPUT >$null 2>&1

return $VMRC
}

function ConnectVirtualMedia
{
$opts=$i
$IP=$i
$CONNECTRC=0

cat Insert_Virtual_Media.xml | %{$_ -replace "Administrator","USERNAME"} |

%{$_ -replace "DoesNotMatter","PASSWORD"} | %{$_ -replace
"IMAGE_URL=""","IMAGE_URL=$WEB_URL"} | out-file -encoding ASCII $TMPRIBCL
.\cpqlocfg.exe -l $OUTPUT -s $IP -f $TMPRIBCL

CheckILOReturnCodes $IP
101
 $CONNECTRC=$?

if($CONNECTRC -ne $true){

print -foreground red "ERROR ILO IP address" $IP "returned an error while
connecting virtual media"
print -foreground red "and cannot continue."
return $CONNECTRC
}

del $OUTPUT >$null 2>&1

return $CONNECTRC
}

function DetachVirtualMedia
{
$opts=$i
$IP=$i
$RC=0

print -foreground yellow "Now disconnecting any existing virtual media from
ILO2 IP address" $IP

CheckVirtualMediaState $IP
$RC=$?
if($RC -eq $true)
{
print "Ejecting virtual media connection."

EjectVirtualMediaConnection $IP
$RC=$?
if($RC -ne $true)
{
print -foreground red "ERROR: Unable to eject virtual media on ILO2 IP
Address" $IP
return $RC
}
else{
print -foreground green "ILO virtual media successfully ejected for ILO2
IP Address" $IP
}
}
else{
print -foreground yellow "No ILO virtual media available to eject for ILO2
IP Address" $IP
}
return $RC
}

function EjectVirtualMediaConnection
{
$opts=$i
$IP=$i
$RC=0

print -foreground yellow "Ejecting Virtual Media currently connected to ILO2

IP address" $IP

cat Eject_Virtual_Media.xml | %{$_ -replace "Administrator","USERNAME"} |

%{$_ -replace "DoesNotMatter","PASSWORD"} | out-file -encoding ASCII $TMPRIBCL
.\cpqlocfg.exe -l $OUTPUT -s $IP -f $TMPRIBCL

CheckILOReturnCodes $IP
$RC=$?
return $RC
}

function GetServerILOList
{
102
 del $TMPOA >$null 2>&1
del $IPSTOUSE >$null 2>&1

ssh -l $USERNAME $OAIP show server list >$TMPOA

$RC=$?
if($RC -eq $true)
{
$value=cat $TMPOA
$regex=[regex]"\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}"
$regex.Matches($value) | select-object -unique -property "value" | select-
string "16" | %{$_ -replace "@", ""} | %{$_ -replace "{", ""} | %{$_ -replace
"Value", ""} | %{$_ -replace "=", ""} | %{$_ -replace "}", ""} | %{$_ -replace "
", ""} > $TMP
}
else{
print -foreground red "ERROR: Error" $RC "attempting to connect to OA at
adress" $IP. "Installation aborted."
}
return $RC
}

function GetServerPowerState
{
$opts=$i
$IP=$i
$RC=0

print -foreground yellow "Now detecting power state for server with ILO2 IP
address" $IP

cat Get_Host_Power_Status.xml |%{$_ -replace "Administrator","USERNAME"} |

%{$_ -replace "DoesNotMatter","PASSWORD"} | out-file -encoding ASCII $TMPRIBCL
.\cpqlocfg.exe -l $OUTPUT -s $IP -f $TMPRIBCL

CheckILOReturnCodes $IP
$RC=$?
if($RC -ne $true){
print -foreground red "ERROR: Unable to detect current power state of
server with ILO2 IP Address" $IP
return $RC
}

if(cat $OUTPUT | where{$_ -match 'HOST_POWER="OFF"'})

{
$POWER=0
}
else{
$POWER=1
}
if ($POWER -eq 1){
print -foreground red "Server power is ON for server with ILO2 IP address"
$IP.
}
del $OUTPUT >$null 2>&1
del $TMP >$null 2>&1
return $POWER
}

function PowerOffServer
{
$opts=$i
$IP=$i
$RC=0

print -foreground yellow "Rebooting server with ILO IP address" $IP

cat Power_Off_Server.xml | %{$_ -replace "Administrator","USERNAME"} | %{$_ -

replace "DoesNotMatter","PASSWORD"} | out-file -encoding ASCII $TMPRIBCL
103
 .\cpqlocfg.exe -l $OUTPUT -s $IP -f $TMPRIBCL

CheckILOReturnCodes $IP
$RC=$?
if($RC -ne $true){
print -foreground red "ERROR: Server cannot be rebooted because an error
was returned."
}
else{
print -foreground green "Server was successfully rebooted."
}
return $RC
}

function PowerOnServer
{
$opts=$i
$IP=$i
$RC=0

print -foreground yellow "Powering on server with ILO IP address" $IP

cat Power_On_Server.xml | %{$_ -replace "Administrator","USERNAME"} | %{$_ -

replace "DoesNotMatter","PASSWORD"} | out-file -encoding ASCII $TMPRIBCL
.\cpqlocfg.exe -l $OUTPUT -s $IP -f $TMPRIBCL

CheckILOReturnCodes $IP
$RC=$?
if($RC -ne $true){
print -foreground red "ERROR: Server cannot be powered on because an
error was returned."
}
else{
print -foreground green "Server was successfully powered on."
}
return $RC
}

function SetVirtualMediaToBootOnce
{
$opts=$i
$IP=$i
$RC=0

print -foreground yellow "Now setting iLO to boot to Virtual Media for ILO2
IP address" $IP

cat Set_Virtual_Media_Status.xml | %{$_ -replace "Administrator","USERNAME"}

| %{$_ -replace "DoesNotMatter","PASSWORD"} | out-file -encoding ASCII $TMPRIBCL
.\cpqlocfg.exe -l $OUTPUT -s $IP -f $TMPRIBCL

CheckILOReturnCodes $IP
$RC=$?
if($RC -ne $true){
print -foreground red "ERROR: Unable to set boot once parameter for ILO2
IP Address" $IP.
}
else{
print -foreground green "iLO at IP address '$IP' has successfully been
set to boot virtual media."
}
return $RC
}

function usage
{
print ".\UpdateBladeFirmware.ps1 <OA ipaddress> <iLO username> <iLO
password>"
104
 return 0
}

function ValidateAdvancedLicense
{
$opts=$i
$IP=$i
$RC=0

print -foreground yellow "Now validating ILO2 IP address" $IP

cat Get_ILO_Firmware_Version.xml | %{$_ -replace "Administrator","USERNAME"}

| %{$_ -replace "DoesNotMatter","PASSWORD"} | out-file -encoding ASCII $TMPRIBCL
.\cpqlocfg.exe -l $OUTPUT -s $IP -f $TMPRIBCL

CheckILOReturnCodes $IP
$RC=$?
if($RC -ne $true){
print -foreground red "ERROR: Server cannot be used because an error was
returned."
return $RC
}
$VERSION= cat $OUTPUT | where{$_ -match "FIRMWARE_VERSION"} |
%{$_.Split("=")[1];} | %{$_ -replace '"',"$s"}
$INTVERSION= $VERSION / 0.01
if($INTVERSION -gt 159)
{
print -foreground green "Supported version of iLO2 Firmware found."
if(cat $OUTPUT | where{$_ -match "iLO 2 Advanced"})
{
print -foreground green "iLO2 Advanced License has been detected."
$IP >> $IPSTOUSE
}
else{
print -foreground red "ERROR: iLO2 Base License has been detected."
print -foreground red "Server cannot be used to script FDT deployment."
}
}
else{
print -foreground red "ERROR: Version of iLO2 firmware installed
(Version'$VERSION'<1.60) is too old and must be updated."
print -foreground red "Server cannot be used to script FDT deployment."
}

del $TMPRIBCL >$null 2>&1

del $VERSION >$null 2>&1
return $RC
}

#Main function
#Check to make sure three parameters are passed
# $1 = OA IP address
# $2 = ILO Username
# $3 = ILO Password

$args
if($args.count -ne 3)
{
usage
return 0
}

$OAIP=$args[0]
$USERNAME=$args[1]
$PASSWORD=$args[2]

$FINALRC=0

105
 #Obtain the list of ILOs from the OA
GetServerILOList

#Validate we were able to obtain the list from the OA

if($RC -eq $true)
{
continue
}

#Validate the provided credentials are good and

#ensure each blade has an iLO Advanced License
#and has iLO Firmware version 1.60 or later

print ""
print -foreground cyan "Validating iLO2 firmware version and Advance License for
IP address" $IP
print ""

$i=0
$temp=cat tmp.txt
foreach($i in $temp)
{
ValidateAdvancedLicense $IP
if($RC -ne $true)
{
$FINALRC=-1
}
del $TMP >$null 2>&1
del $temp >$null 2>&1
print ""
print ""
}

#Check the Virtual Media State and disconnect

#any existing virtual media connections and
#establish connection to the web server URL
#stored in the WEB_URL variable

print ""
print -foreground cyan "Connecting to the HP Firmware Deployment Tool (FDT) ISO
image"
print -foreground cyan "and setting the iLO VM Status to boot from it"
print ""
print ""

$i=0
$iptouse=cat ipaddrs.txt
foreach($i in $iptouse)
{
AttachVirtualMedia $IP
if($RC -ne $true)
{
$FINALRC=-1
}
SetVirtualMediaToBootOnce $IP
if($RC -ne $true)
{
$FINALRC=-1
}
print ""
print ""
}

#Get the Power State of the target servers and shutdown running ones.
print ""
print -foreground cyan "Verifying the servers are powered off. If they are not,"
print -foreground cyan "send a gentle power down command"
106
print ""

$i=0
foreach($i in $iptouse)
{
PowerOffServer
print ""
}

#Wait for all servers to power off

print ""
print -foreground cyan "Waiting for all servers to power down."
print ""
$ANYSERVERSON=1
$ITERATIONS=0
$LOOP=0
$i=0
while($ANYSERVERSON -ne 0)
{
$ANYSERVERSON=0
foreach($i in $iptouse)
{ GetServerPowerState $IP
$POWER=$?
if($POWER -eq $true)
{
$POWER=0
}
else
{
$POWER=1
}
$ANYSERVERSON=$ANYSERVERSON+$POWER
if(($ITERATIONS -eq 5) -and ($POWER -eq 1))
{
PowerOffServer $IP
print "Sent poweroff"
}
}
$TOTAL=$LOOP*5+$ITERATIONS
print -foreground cyan "Power check has completed" $TOTAL "iterations"
print ""
if($ITERATIONS -eq 5)
{
$ITERATIONS=0
$LOOP=$LOOP+1
if($LOOP -eq 5)
{
print -foreground red "ERROR: Unable to power off one or more servers.
Please go to"
print -foreground red "the OA browser interface or iLO Remote Console to
determine why"
print -foreground red "the server will not power off. Once the servers
have all"
print -foreground red "been powered off, please execute this script to
continue"
print -foreground red "the firmware update process."
$FINALRC=2
$i=0
foreach($i in $iptouse)
{
print ""
print -foreground cyan "Detaching virtual media and terminating the
script."
print ""
DetachVirtualMedia $IP
print ""
print ""
}
107
 del $IPSTOUSE >$null 2>&1
del $TMPOA >$null 2>&1
del $TMP >$null 2>&1
del $OUTPUT >$null 2>&1
del $ERR >$null 2>&1
del $TMPRIBCL >$null 2>&1
return $FINALRC >$null 2>&1
}
}
$ITERATIONS=$ITERATIONS+1
print ""
#Wait 5 seconds between iterations to give servers time to shutdown
sleep 5
}

#Power the servers on to start the FDT update

if($FINALRC -ne 2)
{
$i=0
$ip=cat ipaddrs.txt
foreach($i in $ip)
{
PowerOnServer $IP
print -foreground cyan "Waiting 30 seconds before powering on next server
to ensure"
print -foreground cyan "enclosure Virtual Media is not overloaded"
sleep 30
}
}

print -foreground green "Blade firmware update script has successfully launched
the HP "
print -foreground green "Firmware Deployment Tool (FDT) on all supported HP
blade servers"
print -foreground green "The FDT will execute, eject the virtual media ISO image
and"
print -foreground green "reboot once all firmware is updated."

$TMPOA="tmpoa.txt"
$TMP="tmp.txt"
$OUTPUT="output.txt"
$ERR="error.txt"
$TMPRIBCL="ribcl.xml"
del $IPSTOUSE >$null 2>&1
del $TMPOA >$null 2>&1
del $TMP >$null 2>&1
del $OUTPUT >$null 2>&1
del $ERR >$null 2>&1
del $TMPRIBCL >$null 2>&1
return $FINALRC

Sample Linux script to drive the FDT update process for an entire enclosure at once
UpdateBladeFirmware.sh
#!/bin/bash
#
# FDT Sample Script for Updating HP BladeSystem firmware
# Copyright (c) 2009 Hewlett-Packard Development Company, L.P.
#

#Change the WEB_URL to be the URL of the ISO image on the web server
#Please see the Firmware Best Practices Implementer's Guide for
#more information on how to configure the Firmware Update environment

WEB_URL="http://16.89.2.132/BB160.2009_0726.26.iso"
OAIP=$1
USERNAME=$2

108
PASSWORD=$3
IPSTOUSE=./ipaddrs.txt
TMPOA=./tmpoa.txt
TMP=./tmp.txt
OUTPUT=./output.txt
ERROR=./error.txt
TMPRIBCL=./ribcl.xml

# Color definitions.
GREEN="_[1;32m"
BLUE="_[1;34m"
RED="_[1;31m"
HILITE="_[1;39m"
NORMAL="_[0;39m"

function AttachVirtualMedia ()
{
opts=$1
IP=$1
RC=0
rm -f ${IP}.log 1>/dev/null 2>&1
echo "${HILITE}Now connecting virtual media to ILO2 IP address ${IP}${NORMAL}"
DetachVirtualMedia $IP
RC=$?
if [ ! $RC -eq 0 ]
then
return $RC
fi
ConnectVirtualMedia $IP
RC=$?
if [ ! $RC -eq 0 ]
then
echo " ${RED}ERROR: Unable to connect virtual media on ILO2 IP Address
${IP}.${NORMAL}"
return $RC
fi
CheckVirtualMediaState $IP
RC=$?
if [ $RC -eq 1 ]
then
echo " ${GREEN}Virtual media successfully connected on ILO2 IP Address
${IP}.${NORMAL}"
RC=0
else
echo " ${RED}ERROR: Unable to connect virtual media on ILO2 IP Address
${IP}.${NORMAL}"
RC=1
fi
return $RC
}

function CheckILOReturnCodes ()
{
ILORC=0
grep -A 1 "STATUS=" ${OUTPUT} | grep -v "^\-\-$" > $ERROR
while read STATUS REST
do
OLDIFS=$IFS
IFS=$(echo -en "\n\b")
read MESSAGE REST
if [ $STATUS != "STATUS=\"0x0000\"" ]
then
echo " ${RED}ERROR: ILO returned an error: '$STATUS' :
'$MESSAGE'${NORMAL}"
ILORC=1
IFS=$OLDIFS
return $ILORC
fi
109
 IFS=$OLDIFS
done < $ERROR
rm -f $ERROR 1>/dev/null 2>&1
return $ILORC
}

function CheckVirtualMediaState()
{
opts=$1
IP=$1
RC=0
echo "${HILITE}Now checking virtual media status on ILO2 IP address
${IP}${NORMAL}"
sed "/<LOGIN/s/Administrator/${USERNAME}/" Get_VM_Status.xml | sed
"s/DoesNotMatter/${PASSWORD}/" > ${TMPRIBCL}
/usr/bin/perl locfg.pl -l ${OUTPUT} -s ${IP} -f ${TMPRIBCL}
CheckILOReturnCodes
RC=$?
if [ ! $RC -eq 0 ]
then
echo " ${RED}ERROR: ILO IP address $IP returned an error and cannot
continue.${NORMAL}"
return $RC
fi
if [ `grep -ic "image_inserted=\"yes\"" ${OUTPUT}` -eq 1 -o `grep -ic
"VM_APPLET=\"CONNECTED\"" ${OUTPUT}` -eq 1 ]
then
echo " A CD ISO image is inserted"
VMRC=1
else
echo " A CD ISO Image is not inserted."
VMRC=0
fi
rm -f ${OUTPUT} 1>/dev/null 2>&1
return $VMRC
}

function ConnectVirtualMedia ()
{
opts=$1
IP=$1
CONNECTRC=0
sed "/<LOGIN/s/Administrator/${USERNAME}/" Insert_Virtual_Media.xml | sed
"s/DoesNotMatter/${PASSWORD}/" | sed "s,IMAGE_URL=\"\",IMAGE_URL=\"${WEB_URL}\","
> ${TMPRIBCL}
/usr/bin/perl locfg.pl -l ${OUTPUT} -s ${IP} -f ${TMPRIBCL}
CheckILOReturnCodes
CONNECTRC=$?
if [ ! $CONNECTRC -eq 0 ]
then
echo " ${RED}ERROR: ILO IP address $IP returned an error while connecting
virtual media\n and cannot continue.${NORMAL}"
return $CONNECTRC
fi
rm -f ${OUTPUT} 1>/dev/null 2>&1
return $CONNECTRC
}

function DetachVirtualMedia ()
{
opts=$1
IP=$1
RC=0
rm -f ${IP}.log 1>/dev/null 2>&1
echo "${HILITE}Now disconnecting any existing virtual media from ILO2 IP
address ${IP}${NORMAL}"
110
 CheckVirtualMediaState $IP
RC=$?
if [ $RC -eq 1 ]
then
echo " Ejecting virtual media connection."
EjectVirtualMediaConnection $IP
RC=$?
if [ ! $RC -eq 0 ]
then
echo " ${RED}ERROR: Unable to eject virtual media on ILO2 IP Address
${IP}.${NORMAL}"
return $RC
else
echo " ${GREEN}ILO virtual media successfully ejected for ILO2 IP address
${IP}.${NORMAL}"
fi
else
echo " No iLO virtual media available to eject for ILO2 IP address ${IP}."
fi
return $RC
}

function EjectVirtualMediaConnection ()
{
opts=$1
IP=$1
RC=0
echo "${HILITE}Ejecting Virtual Media currently connected to ILO2 IP address
${IP}${NORMAL}"
sed "/<LOGIN/s/Administrator/${USERNAME}/" Eject_Virtual_Media.xml | sed
"s/DoesNotMatter/${PASSWORD}/" > ${TMPRIBCL}
/usr/bin/perl locfg.pl -l ./${OUTPUT} -s ${IP} -f ${TMPRIBCL}
CheckILOReturnCodes
RC=$?
return $RC
}

function GetServerILOList()
{
rm -f ${TMPOA} 1>/dev/null 2>&1
rm -f ${IPSTOUSE} 1>/dev/null 2>&1
ssh -l $USERNAME ${OAIP} show server list 1> ${TMPOA} 2>/dev/null
RC=$?
if [ $RC == 0 ]
then
grep -P '[0-9]{1,3}(\.[0-9]{1,3}){3}' ${TMPOA} | awk '{ print $3 }' >
${OUTPUT}
grep -v "^$" ${OUTPUT} > ${TMP}
rm -f ${OUTPUT} 1>/dev/null 2>&1
else
echo " ${RED}ERROR: Error $RC attempting to connect to OA at address $IP.
Installation aborted.${NORMAL}"
return $RC
fi
}

function GetServerPowerState ()
{
opts=$1
IP=$1
RC=0
rm -f ${IP}.log 1>/dev/null 2>&1
echo "${HILITE}Now detecting power state for server with ILO2 IP address
${IP}${NORMAL}"
sed "/<LOGIN/s/Administrator/${USERNAME}/" Get_Host_Power_Status.xml | sed
"s/DoesNotMatter/${PASSWORD}/" > ${TMPRIBCL}
/usr/bin/perl locfg.pl -l ./${OUTPUT} -s ${IP} -f ${TMPRIBCL}
111
 CheckILOReturnCodes
RC=$?
if [ ! $RC -eq 0 ]
then
echo " ${RED}ERROR: Unable to detect current power state of server with ILO2
IP Address ${IP}.${NORMAL}"
return $RC
fi
POWER=1
if [ `grep -ic "HOST_POWER=\"OFF\"" ${OUTPUT}` -eq 1 ]
then
POWER=0
fi
if [ $POWER -eq 1 ]
then
echo " ${RED}Server power is ON for server with ILO2 IP address
${IP}.${NORMAL}"
fi
rm -f ${OUTPUT} 1>/dev/null 2>&1
rm -f ${TMP} 1>/dev/null 2>&1
return $POWER
}

function PowerOffServer()
{
opts=$1
IP=$1
RC=0
echo "${HILITE}Rebooting server with ILO IP address ${IP}${NORMAL}"
sed "/<LOGIN/s/Administrator/${USERNAME}/" Power_Off_Server.xml | sed
"s/DoesNotMatter/${PASSWORD}/" > ${TMPRIBCL}
/usr/bin/perl locfg.pl -l ./${OUTPUT} -s ${IP} -f ${TMPRIBCL}
CheckILOReturnCodes
RC=$?
if [ ! $RC -eq 0 ]
then
echo " ${RED}ERROR: Server cannot be rebooted because an error was
returned.${NORMAL}"
else
echo " ${GREEN}Server was successfully rebooted.${NORMAL}"
fi
return $RC
}

function PowerOnServer ()
{
opts=$1
IP=$1
RC=0
echo "${HILITE}Powering on server with ILO IP address ${IP}${NORMAL}"
sed "/<LOGIN/s/Administrator/${USERNAME}/" Power_On_Server.xml | sed
"s/DoesNotMatter/${PASSWORD}/" > ${TMPRIBCL}
/usr/bin/perl locfg.pl -l ./${OUTPUT} -s ${IP} -f ${TMPRIBCL}
CheckILOReturnCodes
RC=$?
if [ ! $RC -eq 0 ]
then
echo " ${RED}ERROR: Server cannot be powered on because an error was
returned.${NORMAL}"
else
echo " ${GREEN}Server was successfully powered on.${NORMAL}"
fi
return $RC
}

function SetVirtualMediaToBootOnce ()
{
opts=$1
112
 IP=$1
RC=0
rm -f ${IP}.log 1>/dev/null 2>&1
echo "${HILITE}Now setting iLO to boot to Virtual Media for ILO2 IP address
${IP}${NORMAL}"
sed "/<LOGIN/s/Administrator/${USERNAME}/" Set_Virtual_Media_Status.xml | sed
"s/DoesNotMatter/${PASSWORD}/" > ${TMPRIBCL}
/usr/bin/perl locfg.pl -l ./${OUTPUT} -s ${IP} -f ${TMPRIBCL}
CheckILOReturnCodes
RC=$?
if [ ! $RC -eq 0 ]
then
echo " ${RED}ERROR: Unable to set boot once parameter for ILO2 IP Address
${IP}.${NORMAL}"
else
echo " ${GREEN}iLO at IP address ${IP} has successfully been set to boot
virtual media.${NORMAL}"
fi
return $RC
}

function usage()
{
echo "${HILITE}Usage: ./UpdateBladeFirmware1.sh <OA ipaddress> <iLO username>
<iLO password>${NORMAL}"
exit 0
}

function ValidateAdvancedLicense()
{
opts=$1
IP=$1
RC=0
rm -f ${IP}.log 1>/dev/null 2>&1
echo "${HILITE}Now validating ILO2 IP address ${IP}${NORMAL}"
sed "/<LOGIN/s/Administrator/${USERNAME}/" License.xml | sed
"s/DoesNotMatter/${PASSWORD}/" > ${TMPRIBCL}
/usr/bin/perl locfg.pl -l ./${OUTPUT} -s ${IP} -f ${TMPRIBCL}
CheckILOReturnCodes
RC=$?
if [ ! $RC -eq 0 ]
then
echo " ${RED}ERROR: Server cannot be used because an error was
returned.${NORMAL}"
return $RC
fi
VERSION=`grep "FIRMWARE_VERSION" $OUTPUT | awk -F= '{ print $2 }' | sed
's/"//g' | sed 's/ //g'`
INTVERSION=`echo $VERSION '*100' | bc -l | awk -F'.' '{ print $1 }'`
if [ $INTVERSION -gt 159 ]
then
echo " ${GREEN}Supported version of iLO2 Firmware found.${NORMAL}"
if [ `grep -ic "LICENSE_TYPE = \"iLO 2 Advanced\"" ${OUTPUT}` -eq 1 ]
then
echo " ${GREEN}iLO2 Advanced License has been detected.${NORMAL}"
echo ${IP} >> ${IPSTOUSE}
else
echo " ${RED}ERROR: iLO2 Base License has been detected."
echo " Server cannot be used to script FDT deployment. ${NORMAL}"
RC=1
fi
else
echo " ${RED}ERROR: Version of iLO2 firmware installed (Version $VERSION <
1.60) is too old and must be updated."
echo " Server cannot be used to script FDT deployment.${NORMAL}"
RC=1
fi
113
 rm -f ${IP}.log 1>/dev/null 2>&1
rm -f ${TMPRIBCL} 1>/dev/null 2>&1
rm -f ${OUTPUT} 1>/dev/null 2>&1
rm -f ${VERSION}
return $RC
}

#Main function
#Check to make sure three parameters are passed
# $1 = OA IP address
# $2 = ILO Username
# $3 = ILO Password

if [ "$3" == "" ]
then
usage
exit 0
fi

FINALRC=0

#Obtain the list of ILOs from the OA

GetServerILOList

#Validate we were able to obtain the list from the OA

if [ $RC != 0 ]
then
exit $RC
fi

#Validate the provided credentials are good and

#ensure each blade has an iLO Advanced License
#and has iLO Firmware version 1.60 or later
echo ""
echo "${BLUE}Validating iLO2 firmware version and Advanced License for IP
address ${IPADDRESS}${NORMAL}"
echo ""
while read IPADDRESS REST
do
ValidateAdvancedLicense $IPADDRESS
if [ ! $RC -eq 0 ]
then
FINALRC=-1
fi
done < ${TMP}
rm -f ${TMP} 1>/dev/null 2>&1
echo ""
echo ""

#Check the Virtual Media State and disconnect

#any existing virtual media connections and
#establish connection to the web server URL
#stored in the WEB_URL variable

echo ""
echo "${BLUE}Connecting to the HP Firmware Deployment Tool (FDT) ISO image"
echo " and setting the iLO VM Status to boot from it${NORMAL}"
echo ""
echo ""
while read IPADDRESS REST
do
AttachVirtualMedia $IPADDRESS
if [ ! $RC -eq 0 ]
then
FINALRC=-1
fi
SetVirtualMediaToBootOnce $IPADDRESS
if [ ! $RC -eq 0 ]
114
 then
FINALRC=-1
fi
echo ""
echo ""
done < ${IPSTOUSE}

#Get the Power State of the target servers and shutdown running ones.

echo ""
echo "${BLUE}Verifying the servers are powered off. If they are not, send a
\"gentle\""
echo " power down command${NORMAL}"
echo ""
while read IPADDRESS REST
do
PowerOffServer $IPADDRESS
echo ""
done < ${IPSTOUSE}

#Wait for all servers to power off

echo ""
echo "${BLUE}Waiting for all servers to power down.${NORMAL}"
echo ""
ANYSERVERSON=1
ITERATIONS=0
LOOP=0
while [ ! ${ANYSERVERSON} -eq 0 ]
do
ANYSERVERSON=0
while read IPADDRESS REST
do
GetServerPowerState $IPADDRESS
POWER=$?
ANYSERVERSON=`expr $ANYSERVERSON + $POWER`
if [ $ITERATIONS -eq 5 -a $POWER -eq 1 ]
then
PowerOffServer $IPADDRESS
fi
done < ${IPSTOUSE}
ITERATIONS=`expr $ITERATIONS + 1`
echo ""
TOTAL=`expr $LOOP \* 5 + $ITERATIONS`
echo "${BLUE}Power check has completed ${TOTAL} iterations.${NORMAL}"
echo ""
if [ $ITERATIONS -eq 5 ]
then
ITERATIONS=0
LOOP=`expr $LOOP + 1`
if [ $LOOP -eq 5 ]
then
echo "${RED}ERROR: Unable to power off one or more servers. Please go
to the"
echo " OA browser interface or iLO Remote Console to determine
why"
echo " the server will not power off. Once the servers have all"
echo " been powered off, please execute this script to continue"
echo " the firmware update process.${NORMAL}"
FINALRC=2
while read IPADDRESS REST
do
echo ""
echo "${BLUE}Detaching virtual media and terminating the
script.${NORMAL}"
echo ""
DetachVirtualMedia $IPADDRESS
echo ""
echo ""
115
 done < ${IPSTOUSE}
rm -f ${IPSTOUSE} 1>/dev/null 2>&1
rm -f ${TMPOA} 1>/dev/null 2>&1
rm -f ${TMP} 1>/dev/null 2>&1
rm -f ${OUTPUT} 1>/dev/null 2>&1
rm -f ${ERROR} 1>/dev/null 2>&1
rm -f ${TMPRIBCL} 1>/dev/null 2>&1
exit $FINALRC
break
fi
fi
#Wait 5 seconds between iterations to give servers time to shutdown
sleep 5
done

#Power the servers on to start the FDT update

if [ ! $FINALRC -eq 2 ]
then
while read IPADDRESS REST
do
PowerOnServer $IPADDRESS
echo "${BLUE}Waiting 30 seconds before powering on next server to ensure "
echo " enclosure Virtual Media is not overloaded.${NORMAL}"
sleep 30
done < ${IPSTOUSE}
fi

echo "${GREEN}Blade firmware update script has successfully launched the HP "
echo " Firmware Deployment Tool (FDT) on all supported HP blade servers"
echo " The FDT will execute, eject the virtual media ISO image and"
echo " reboot once all firmware is updated.${NORMAL}"

TMPOA=./tmpoa.txt
TMP=./tmp.txt
OUTPUT=./output.txt
ERROR=./error.txt
TMPRIBCL=./ribcl.xml
rm -f ${IPSTOUSE} 1>/dev/null 2>&1
rm -f ${TMPOA} 1>/dev/null 2>&1
rm -f ${TMP} 1>/dev/null 2>&1
rm -f ${OUTPUT} 1>/dev/null 2>&1
rm -f ${ERROR} 1>/dev/null 2>&1
rm -f ${TMPRIBCL} 1>/dev/null 2>&1
exit $FINALRC

Update OA firmware scripts

For the UpdateOAFirmware scripts, the expectation is the script will run from a workstation connected
to the same network as the OA. The script does a couple of checks to ensure the dependencies have
been installed. For Windows, the only dependency is that the HP BladeSystem Firmware Update
Bundles for Windows and specifically HP SUM and the OA firmware component contained in the
Firmware Update Bundles are available in the directory where the script is executed.
For Linux, the requirements include the HP BladeSystem Firmware Update Bundles for Linux and
specifically HP SUM and the OA firmware component included in the Firmware Update bundles are
in the directory where the script is executed AND the ―expect‖ RPM has been installed on that
workstation.

116
To execute the scripts below, use the following commands.
Windows
 UpdateOAFirmware.cmd <OA_IP_Address> <OA_ADMIN_ID> <OA_PASSWORD>
 Ex. UpdateOAFirmware.cmd 16.89.1.3 Administrator AdminPassword
Linux
 ./UpdateOAFirmware.sh <OA_IP_Address> <OA_ADMIN_ID> <OA_PASSWORD>
 Ex. ./UpdateOAFirmware.sh 16.89.1.3 Administrator AdminPassword

Sample Windows Power Shell script to drive the OA firmware update process to a single OA at a time
UpdateOAFirmware.ps1
##################################################################
#
#FDT Sample Scripts for Updating HP Onboard Administrator firmware
#
#Copyright(c)2009 Hewlett-Packard Development Company, L.P.
#
##################################################################

#Custom alias command for color-coded statements

#Need to define foreground color in the statements
Set-Alias print Write-Host

#variable to get the correct path to hpsum.exe

$dir = gci "C:\scripts\hpsum.exe"

function usage
{
print "Usage:.\UpdateOAFirmware.ps1 <OA ipaddress> <OA username> <OA password>"
return 0
}

#Main Function
#Check to make sure three parameters are passed
#$1 = OA IP adress
#$2 = OA Username
#$3 = OA Password

$args
if($args.count -ne 3){
usage
}

$1=$args[0]
$2=$args[1]
$3=$args[2]

if($dir -notmatch 'hpsum.exe')

{
print -foreground red "The HPSUM executable has not been found in the current
directory. Please"
print -foreground red "download the HP Bladesystem Firmware Update Bundles for
Linux from the"
print -foreground red "www.hp.com/go/bladesystemupdates web page and extract
the contents"
print -foreground red "into the directory to update the Onboard Administrator
firmware"
return -5
}

else
{

117
 print " Firmware Update for OA at is now starting and will take"
print " approximately 4 to 8 minutes to complete. No output will"
print " be provided until the firmware update process is completed"
.\hpsum -s -target $1 -user $2 -passwd $3 -f:rom
}

$RC=$?

switch ($RC) {
-3 { print -foreground red "The installation of the OA firmware component
returned an error. Please"
print -foreground red "see the C:\cpqsystem\hp\log\'IP' directory for
details of the"
print -foreground red "returned error." }

-2 { print -foreground red "Bad parameter passed to the UpdateOAFirmware

script. Please check your"
print -foreground red "parameters and attempt the OA Firmware update
again." }

-1 { print -foreground red "An HPSUM error occured. Please review the logs in
the C:\cpqsystem\hp\log\'IP'"
print -foreground red "directory for more details on the cause of the
error." }

(0 -or 1) { print -foreground green "The OA firmware was successfully

installed."}

3 { print -foreground blue "The OA firmware is already up to date and does

not need to be updated."}

* { print -foreground red "An HPSUM error occurred. Please review the logs in
the C:\cpqsystem\hp\log\'IP'"
print -foreground red "directory for more details on the cause of the
error." }
}

Sample Linux script to drive the OA firmware update process to a single OA at a time
UpdateOAFirmware.sh
#!/bin/bash
#
# FDT Sample Script for Updating HP Onboard Administrator firmware
# Copyright (c) 2009 Hewlett-Packard Development Company, L.P.
#

# Color definitions.
GREEN="_[1;32m"
BLUE="_[1;34m"
RED="_[1;31m"
HILITE="_[1;39m"
NORMAL="_[0;39m"

function usage()
{
echo "${HILITE}Usage: ./UpdateOAFirmware.sh <OA ipaddress> <OA username> <OA
password>${NORMAL}"
exit 0
}

#Main function
#Check to make sure three parameters are passed
# $1 = OA IP address
# $2 = OA Username

118
# $3 = OA Password

if [ "$3" == "" ]
then
usage
exit 0
fi

if [ `rpm -qa | grep -c 'expect'` -eq 0 ]

then
echo "${RED}The \"expect\" RPM must be installed before attempting to update
the OA firmware."
echo " HPSUM requires this RPM in order to deploy firmware remotely."
echo " The update of the OA firmware cannot proceed and will exit.${NORMAL}"
exit -4
fi
if [ ! `find * -print | grep -c -x 'hpsum'` -eq 1 ]
then
echo "${RED}The HPSUM executable has not been found in the current directory.
Please"
echo " download the HP BladeSystem Firmware Update Bundles for Linux from
the"
echo " www.hp.com/go/bladesystemupdates web page and extract the contents"
echo " into the current directory to update the Onboard Administrator
firmware${NORMAL}"
exit -5
fi

echo "${HILITE}Firmware Update for OA at ${IP} is now starting and will take"
echo " approximately 4 to 8 minutes to complete. No output will be provided"
echo " until the firmware update process is completed.${NORMAL}"
./hpsum -s -target $1 -user $2 -passwd $3 -f:rom
RC=$?
case $RC in
-3) echo "${RED}The installation of the OA firmware component returned an
error. Please see the "
echo " /var/hp/log/${IP}/hpsum_details.txt directory for details of the
returned error.${NORMAL}"
;;
-2) echo "${RED}Bad parameter passed to the UpdateOAFirmware script. Please
check your parameters and attempt"
echo " the OA firmware update again.${NORMAL}"
;;
-1) echo "${RED}An HPSUM error occurred. Please review the logs in the
/var/hp/log/${IP}"
echo " directory for more details on the cause of the error.${NORMAL}"
;;
0|1) echo "${GREEN}The OA firmware was successfully installed.${NORMAL}"
;;
3) echo "${BLUE}The OA firmware is already up to date and does not need to be
updated.${NORMAL}"
;;
*) echo "${RED}An HPSUM error occurred. Please review the logs in the
/var/hp/log/${IP}"
echo " directory for more details on the cause of the error.${NORMAL}"
;;
esac

exit $RC

Update VC firmware scripts

For the UpdateVCFirmware scripts, the expectation is the script will run from a workstation connected
to the same network as the OA. The script does a couple of checks to ensure the dependencies have
been installed. For Windows, the only dependency is that the HP BladeSystem Firmware Update

119
 Bundles for Windows and specifically the VCSU and the VC firmware binaries included in the VC
firmware component contained in the Firmware Update Bundles are available in the directory where
the script is executed.
For Linux, the script is written to leverage HPSUM. The requirements for deploying the VC firmware
update in Linux include the HP BladeSystem Firmware Update Bundles for Linux and specifically HP
SUM and the VC firmware component included in the Firmware Update bundles are in the directory
where the script is executed. In addition, the ―expect‖ RPM must be installed on the workstation
running the script for HP SUM to be able to perform remote deployments in Linux.
To execute the scripts below, use the following commands.
Windows
 UpdateVCFirmware.cmd <OA_IP_Address> <OA_ADMIN_ID> <OA_PASSWORD>
 Ex. UpdateVCFirmware.cmd 16.89.1.3 Administrator AdminPassword
Linux
 ./UpdateVCFirmware.sh <VC_IP_Address> <VC_ADMIN_ID> <VC_PASSWORD>
 Ex. ./UpdateVCFirmware.sh 16.89.1.3 Administrator AdminPassword

Important:
The VC modules must be updated through the primary OA connection for
Windows. For Linux, the IP address must be to the Active VC Ethernet
module as reported by the VCM link in the OA web browser interface.

Sample Windows Power Shell script to drive the VC firmware update process to a single VC at a time
UpdateVCFirmware.ps1
####################################################################
#
# FDT Sample Script for updating HP Virtual Connect firmware
# Copyright (c) 2009 Hewlett-Packard Development Company, L.P.
#
####################################################################

# Alias for print statement

Set-Alias print Write-Host

#variable to get the correct path to hpsum.exe

$dir = gci "C:\scripts\hpsum.exe"

function usage
{
print "Usage: .\UpdateVCFirmware.sh <VC ipaddress> <VC username> <VC
password>"
return 0
}

#Main function
#Check to make sure three parameters are passed
# $1 = VC IP address
# $2 = VC Username
# $3 = VC Password

$args
if($args.count -ne 3){
usage
}

$1=$args[0]
$2=$args[1]

120
$3=$args[2]
if($args.count -ne 3)
{
usage
}

if($dir -notmatch 'hpsum.exe')

{
print -foreground red "The HPSUM executable has not been found in the current
directory. Please"
print -foreground red "download the HP BladeSystem Firmware Update Bundles for
Linux from the"
print -foreground red "www.hp.com/go/bladesystemupdates web page and extract
the contents"
print -foreground red "into the current directory to update the HP Virtual
Connect firmware"
return -5
}

else
{
print -foreground green "Firmware update for Virtual Connect at $IP is now
starting and will"
print -foreground green "take approximately 10 to 60 minutes to complete. No
output will be"
print -foreground green "provided until the firmware update process is
completed"
.\hpsum -s target $1 -user $2 -passwd $3 -f:rom
}

$RC=$?

switch ($RC) {
-3 { print -foreground red "The installation of the Virtual Connect firmware
component returned an error. Please"
print -foreground red "see the C:\cpqsystem\hp\log\'IP' directory for
details of the"
print -foreground red "returned error." }

-2 { print -foreground red "Bad parameter passed to the UpdateVCFirmware

script. Please check your"
print -foreground red "parameters and attempt the OA Firmware update
again." }

-1 { print -foreground red "An HPSUM error occured. Please review the logs in
the C:\cpqsystem\hp\log\'IP'"
print -foreground red "directory for more details on the cause of the
error." }

(0 -or 1) { print -foreground green "The VC firmware was successfully

installed."}

3 { print -foreground blue "The VC firmware is already up to date and does not
need to be updated."}

* { print -foreground red "An HPSUM error occurred. Please review the logs in
the C:\cpqsystem\hp\log\'IP'"
print -foreground red "directory for more details on the cause of the
error." }

}
Script to be added later

121
 Sample Linux script to drive the VC firmware update process to all the VC modules in a single
enclosure at a time
UpdateVCFirmware.sh
#!/bin/bash
#
# FDT Sample Script for updating HP Virtual Connect firmware
# Copyright (c) 2009 Hewlett-Packard Development Company, L.P.
#

# Color definitions.
GREEN="_[1;32m"
BLUE="_[1;34m"
RED="_[1;31m"
HILITE="_[1;39m"
NORMAL="_[0;39m"

function usage()
{
echo "${HILITE}Usage: ./UpdateVCFirmware.sh <VC ipaddress> <VC username> <VC
password>${NORMAL}"
exit 0
}

#Main function
#Check to make sure three parameters are passed
# $1 = VC IP address
# $2 = VC Username
# $3 = VC Password

if [ "$3" == "" ]
then
usage
exit 0
fi

if [ `rpm -qa | grep -c 'expect'` -eq 0 ]

then
echo "${RED}The \"expect\" RPM must be installed before attempting to update
the OA firmware."
echo " HPSUM requires this RPM in order to deploy firmware remotely."
echo " The update of the VC firmware cannot proceed and will exit.${NORMAL}"
exit -4
fi
if [ ! `find * -print | grep -c -x 'hpsum'` -eq 1 ]
then
echo "${RED}The HPSUM executable has not been found in the current directory.
Please"
echo " download the HP BladeSystem Firmware Update Bundles for Linux from
the"
echo " www.hp.com/go/bladesystemupdates web page and extract the contents"
echo " into the current directory to update the HP Virtual Connect
firmware${NORMAL}"
exit -5
fi

echo "${HILITE}Firmware Update for Virtual Connect at ${IP} is now starting and
will take"
echo " approximately 10 to 60 minutes to complete. No output will be
provided"
echo " until the firmware update process is completed.${NORMAL}"
./hpsum -s -target $1 -user $2 -passwd $3 -f:rom
RC=$?
case $RC in
-3) echo "${RED}The installation of the Virtual Connect firmware component
returned an error. Please see the "

122
 echo " /var/hp/log/${IP}/hpsum_details.txt directory for details of the
returned error.${NORMAL}"
;;
-2) echo "${RED}Bad parameter passed to the UpdateVCFirmware script. Please
check your parameters and attempt"
echo " the OA firmware update again.${NORMAL}"
;;
-1) echo "${RED}An HPSUM error occurred. Please review the logs in the
/var/hp/log/${IP}"
echo " directory for more details on the cause of the error.${NORMAL}"
;;
0|1) echo "${GREEN}The VC firmware was successfully installed.${NORMAL}"
;;
3) echo "${BLUE}The VC firmware is already up to date and does not need to be
updated.${NORMAL}"
;;
*) echo "${RED}An HPSUM error occurred. Please review the logs in the
/var/hp/log/${IP}"
echo " directory for more details on the cause of the error.${NORMAL}"
;;
esac

exit $RC

Scenario 7: Updating the HP StorageWorks MDS600 firmware

The MDS600 firmware update process requires slight modifications to the standard HP Firmware
Maintenance CD installation support described in Section 1C. The process involves the following
items.
1. Downloading the HP Firmware Maintenance CD and the MDS600 firmware component from
the HP website.
2. Creating a USB key with the contents of the Firmware Maintenance CD and adding the
MDS600 component.
3. Shutting down all servers in the enclosure with Smart Array P700m controllers that are
connected to the MDS600 being updated except the one used to perform the update.
4. Booting the USB key and updating the MDS600 firmware from one of the server blades that
contains a Smart Array P700m controller.
5. Rebooting the blade executing the update.
6. Restarting all the blades that were previously shut down.

Use the following instructions to update the MDS600 firmware on an individual server using the HP
Firmware Maintenance CD
1. Download the HP Firmware Maintenance CD from the HP website.
Links to the latest versions are posted on the BladeSystem Compatibility Chart web pages are
located at http://www.hp.com/go/bladesystemupdates. The file is named firmware-
<version>.zip.
2. To extract the ISO image, open Windows Explorer and double-click on the ZIP file, and copy
the ISO image to a directory on a USB key or network hard drive.
For Linux users, simply unzip the ZIP file using the unzip firmware-<version>.zip
command.
3. Download the MDS600 firmware from the HP website.
The latest version can be found by issuing a search for MDS600 on the www.hp.com website.
4. The next step is to create a USB key from the contents of the Firmware CD ISO.

123
 5. For Windows, the HP USB Key Creator for Windows utility must be downloaded from the HP
website and installed on a workstation. Once installed, the utility will place a shortcut in 'HP
System Tools' in the Programs start menu folder.

To make your drive key bootable and copy the contents of the CD:
1. Place your HP USB drive key in an available USB port.
2. Select the HP USB Key Utility shortcut in the HP System Tools folder.
3. Complete each step presented by the application.

Note:
The HP USB Key Creator formats the USB key so any files on the
key are lost. Be sure to use a USB key that is at least 1 GB in
size and does not contain any valuable files.

For Linux, the USB key can be created manually using the following steps:
1. Obtain SYSLINUX 3.2 or higher from http://freshmeat.com or http://syslinux.zytor.com and
download to a Linux workstation.
2. Install the SYSLINUX RPM obtained in Step 1.
3. Make a directory for the USB key mountpoint if one does not already exist. (For example,
mkdir /usbkey).
4. Insert the USB key and mount it (mount /dev/sda1 /usbkey).

Note:
The device mountpoint can vary depending on whether or not
other SCSI drives are also installed on the server. Thus, the
device mountpoint can be sdb1, sdc1, and so on).

5. Issue the command ./syslinux /usbkey to have SYSLINUX write out the boot partition to the
USB key.

Caution:
Failure to follow this step could lead to a key that will not boot
the Firmware CD until the SYSLINUX command is successful.

6. Create a directory to mount the CD image.

mkdir /cd_mount_point
7. Insert the Firmware CD or mount the Firmware CD ISO via a loopback.
mount /dev/cdrom /cd_mount_point

or

mount -t iso9660 firmware-<version>.iso /cd_mount_point -o loop

8. Change to the /usb directory on the CD.

cd /cd_mount_point/usb
9. Execute the usbcreator.sh shell script passing in the CD mount point and the USB mount
point to move the Firmware CD files to the USB key.
./usbcreator.sh /cd_mount_point /usbkey

124
 10. Unmount the CD and the USB key.
umount /dev/cdrom
umount /dev/sda1

Note:
This must match the initial mount point in Step 4.

11. Remove the USB key and CD from the workstation used to create the USB key.

Follow these steps to remove the USB key and CD from the workstation.
1. Copy the CP01xxxx.scexe file downloaded in Step 3 to the \compaq\swpackages directory
on the USB key.
2. Power off all servers with Smart Array P700m controllers connected to the MDS600s that will
be updated.
3. Insert the USB key into the SUV (Serial-USB-Video) cable and boot the server to be used to
perform the update.
4. Once the HP Firmware Maintenance CD boots, choose the appropriate keyboard language
and screen language to use and accept the End User License Agreement (EULA) to proceed.
5. Click the Firmware Update tab, then the Install Firmware link to launch HP SUM.
6. On the HP SUM Select Items to Install screen, deselect all other firmware updates besides the
MDS600.
7. Click Install for the firmware update process to start.
HP SUM shows the relative progress during installation and the Installation Results once the
installation has completed for review.
8. Click Exit, and then click Yes to exit HP SUM.
9. Click Exit and Yes to reboot the server after successful installation of the MDS600 firmware.
10. Remove the USB key from the server and power back on all blades that were powered off.

Using HP SUM in GUI mode

Using the GUI for local host installations
HP SUM can deploy smart components on a local host or on one or more remote hosts. You can
deploy components on a local host by using the HP SUM GUI.
Selecting the location to check for updates
As Figure 4 shows, the Source Selections screen enables you to select components from a directory
and the HP FTP site (ftp://ftp.hp.com) as a location for obtaining updates to your systems. You
can also select components that have already been downloaded. You can use up to all three of the
following methods simultaneously.

Note:
For offline deployments, the Source Selections screen does not appear.

125
 Figure 4. HP SUM Source Selections screen

The Source Selections screen allows you to specify where to get components for updating the targets
by using one or more of the following methods:
Directory
This option allows you to select the directory where the components you want to deploy are
located. It can be located on a locally accessible file system. The default location is the directory from
where HP SUM is executed.
1. To change the directory value, click the Browse button to launch a select-directory menu.
2. To set the field back to its initial value, click the Default button.
3. Check ftp.hp.com.

This option allows you to get firmware and software components located on the HP FTP site
(ftp://ftp.hp.com). The HP FTP site contains the latest versions of the firmware and software
components available from HP. The components, which are applicable (denoted with an HP.com
icon) are available for selection on the Select Items to be Installed screen. When using this method,
both firmware and software components are available for selection depending on the options set on
the Set Bundle Filter screen when ProLiant Support Packs are included in the components to be
deployed.
To limit the appearance of available firmware components, use the /romonly command line
argument; for software components, use the /softwareonly command line argument. The
components are not downloaded from the HP FTP site to a target until the Install button is actually
selected unless the component is needed to discover supported devices. If components are needed for
discovery, you are prompted to allow this action. If components are already up-to-date, the
components are not seen.

126
The Check ftp.hp.com checkbox is cleared by default.
1. Select the Check ftp.hp.com checkbox to pull updates from the web.
2. Select the Use Proxy Server checkbox to use a proxy server and enable the proxy details
group box.

Proxy Details
1. Enter the proxy information in the Proxy Details group box to be used to access the HP FTP site.
2. Click the Detect Proxy button to auto-detect the proxy information.
If you use a proxy server in accessing the HP FTP site, the proxy information is saved and pre-
populated on the next deployment.

Note:
HP SUM does not support FTP over HTTP proxy. FTP
downloaded from HTTP proxy fails. Components from the HP
FTP site is only presented for selection on the Select Items to
Install screen if their versions are newer than what is already
on the system. If a system has all of the latest versions of
firmware and software, no components from www.hp.com
presented on the Select Items to be Installed screen.

Include components previously downloaded from www.hp.com.

This option includes the components that have been previously downloaded from the HP ftp site. You
can select the available components from the Select Items to be Installed screen.
The default location for the previously downloaded components is:
%TEMP%\hp_sum\RepositoryManager\Repxx\<component_nu mber> directory

To use previously downloaded components from www.hp.com, follow these steps:

1. Select the www.hp.com checkbox.
2. Click Start Inventory to begin the inventory process.
The Inventory Progress screen appears while the HP SUM builds an inventory of available
updates.
Download permission
Before starting any discovery, HP SUM searches the web digest for self-discovery components that
need to be downloaded for the discovery process. Self-discovered components are components
including but not limited to NIC firmware and tape firmware that HP SUM uses to discover the
hardware in the system. The Download Permission screen appears, as shown in Figure 5.

127
 Figure 5. Download Permission screen

The Download Permission screen lists the available updates found on the HP FTP site. You can select
or clear the updates you are allowing to download.
The Download Permission screen includes the following buttons:

Button Function

Select All Selects all available components for download

Clear All Clears all components selected for download

Cancel Exits the Download Permission screen and returns to the source Selections screen

OK Downloads all selected components

Note:
Emulex HBAs, QLogic HBAs, and offline-only components cannot be
retrieved from the HP website and can only be installed offline. These
components do not appear on the web components list.

Selecting an installation host

The Select Installation Host(s) screen appears (see Figure 6) when you have selected the location to
obtain your updates from.

128
Figure 6. Select Installation Host(s) screen

The Select Installation Host(s) screen enables you to choose a host for component installation. By
default, the first time you run HP SUM on a particular system, the only host available is the
local host. However, you can also select remote hosts as your targets. For more information
about using the graphical interface for multiple remote deployments, see Using the GUI for
multiple-host installations.
The following columns are included in the Select Installation Host(s) screen:

Column Function

Host Name Displays the host PI address or DNS name

Last Used Categorizes the system as a host or group

Last Used Enables you to sort the list by the most recently used hosts

Description Displays the user –defined description given to a host

When the Remote Host or Group option in the Select Installation Host(s) screen is selected, you can
sort your view of the host list by selecting Only Hosts, Only Groups, or Both.

129
 The Select Installation Host(s) screen also includes the following buttons:

Button Function

Manage Hosts Enables you to add, edit, and delete hosts

Manage Groups Enables you to add, edit, and delete groups

Edit Enables you to edit the selected host

Next Proceeds to the next step in the installation process. The local or remote system then checks for
items that are already installed.

Exit Exits HP SUM

Click Next to continue selecting an installation host. For multiple remote deployments, enter the
credentials for the host. When the credentials are successfully entered, the discovery process occurs.
Selecting components to install
When the discovery process is complete, the Select Items to be Installed screen appears (see
Figure 7). The Select Items to be Installed screen displays information about which components are
available for installation on your system and enables you to select or deselect components to
install.

Figure 7. Select Items to be Installed window

130
The Select Items to be Installed screen includes the following sections:

Sections Function

Product Lists the system on which the selected items are installed

Status Indicates if the installation is ready

Optional Actions Indicates whether or not the component configuration is optional or required but has already
been updated

Reboot section Enables you to specify reboot settings and determine when reboots occur

Component selection Enables you to specify the components to install

pane

When updating installation for some NIC components, select the devices to be updated in the
window that appears. If the NIC firmware listed for the device does not have a version, you
cannot add that firmware to the device using HP SUM.
When multiple hardware devices such as hard drives or array controllers exist in a single
server, HP SUM lists each device only once. If the devices have different firmware versions, then the
versions are listed from earliest to latest in a range. When multiple instances of the firmware
are available for installation, the instances are listed from latest to earliest. If necessary, all
hardware device firmware is flashed to the selected version.
The Select Items to be Installed screen also includes the following buttons:

Button Function

Select All Selects all available components for installation

Deselect All Clears all components selected for installation

Default Restores the selections in the production installation pane to the default view, which is
based on the existing configuration of the local system

Exit Exits HP SUM

Install Installs all selected components

Add Supplemental Enables you to deploy additional components from a removable device. The additional
components must be located on the device root. This button is available only for offline
deployments.

The component selection pane in the Select Items to be Installed screen is divided into sections, which
might vary depending upon your system. The Select Items to be Installed screen sections include
the following headings:
User
This function allows you to deselect the components in this section. The components that are checked
as Deselected By User are not installed.

131
 Installation not needed
The components in this section do not need to be updated, although they can be. To update the
components, select the components, and then click Installation Options.

Excluded by filtering
The components in this section are excluded through the filtering options. You can use the Select
Bundle Filter option or one of the command line arguments, such as /romonly o r /softwareonly,
to change the exclusion on a single target. For multiple targets, you must repeat the command for
each additional target. The Select Bundle Filter option screen is only available when there are
bundles, such as ProLiant Support Packs, included in the same location as the components
selected for download.

Updates to be installed
The components in this section can be installed on your system.

Optional updates
The components in this section are not selected for installation by default, even if the product is
not already installed or is installed but not up-to-date. To include the component in the installation set,
you must select the component.

No device driver installed

The devices supported by the components in this section are detected on the system, but HP SUM
requires a device driver before the component can be made available for installation. Install the
device driver.

132
Multi-session installation
Multi-session installation appears on the Source Selections screen under certain dependency
combinations between components selected for installation. The following criteria must be met
for the multi-session installation to be successful.
1. To install Component B, the product must already be installed and active. Component B
depends on the product in Component A.
2. To become active, Component A must reboot after the installation.
3. To succeed with installation, there must not be an already-installed version of the product in
component A, or at least not one of the correct versions to satisfy the dependency.
HP SUM detects when all of the conditions are met, and a notification to reboot appears to continue
the installation. All installable components appear in the original update list. However, only the
components shown before the notification appears are installed. You must reboot to complete the
installation, and then restart HP SUM to continue the installation process.

The Status field of the Select Items to be Installed screen displays information about whether or not the
installation is ready to proceed.

Icon Text Description

Ready All selected components are ready to be installed.

Already up-to- No component installation is required.

date

None Selected No components are selected for installation.

X components are not ready for installation due to failed dependencies ( x is the
x Critical Action number of components). The installation cannot proceed until the dependencies are met
or until the component is deselected for installation.

Reboot section
The reboot section of the Select Items to be Installed screen allows you to specify the preferred reboot
behavior.

To instruct the system to reboot after updates are installed:

1. Click Reboot System After Installation.
2. Click Always or If Needed.

If Always is selected, the system is always rebooted, unless there is a component installation failure.
When If Needed is selected, the system is rebooted if needed by at least one componen t, unless
there is a component installation failure.

133
 Follow these steps to change the delay before reboot or the reboot message.
1. Press Reboot Options. The Set Reboot Options screen appears.
2. Make any changes, and click OK.

Note:
In Linux, the Reboot Delay time is automatically converted from seconds to
minutes. For Linux, any value under a full minute (59 seconds or less) is
rounded to the next minute.

Component selection pane

The component selection pane of the Select Items to be Installed screen displays all components
available for installation, based on your server and hardware options. The Select Items to be
Installed screen lists by component number order, unless a dependency causes the installation
order to change. The HP SUM checks each component for dependencies and determines if the
component is already installed on the system, or if it requires a reboot after installation. Items
available for installation are selected by default. You can deselect any of the components that
you do not want to install.
The component selection pane is divided into the following columns:

Column Function

Product Specifies the name of the component, version number, and new component version number. To
view the component version history, click the New version number

Status Displays the status of a component

Optional Actions Reserved for future use

Additional Contains the installation options and additional component information

The following is a list of the Component Selection panel icons and icon descriptions.

Icon Text Description

Ready for installation The component is ready for installation.

The component has not been selected for installation.

Not selected for installation

Already up-to-date The component is already up-to-date. To downgrade or rewrite a

component, click Installation Options.

No device driver installed The firmware devices supported by the components in this section are
detected on the system but require a device driver. Install the device
driver.

Deselected by user The component has not been selected for installation.

Failed dependencies
The component has a dependency that has not been met. To
determine the nature of the failed dependency, click View Failed
Dependencies.

If a failed dependency occurs, you must resolve it before proceeding with the installation. Depending
on the issue, you must locate software or firmware components in the Firmware Maintenance
CD or HP website at www.hp.com. Figure 8 shows the Failed Dependencies screen.

134
Figure 8. Failed Dependencies screen

Installation options
You can specify firmware upgrade behavior for installable components by selecting one or more
options from the Additional Options field. Depending on the component type, one of the
following screens appears.

135
 Caution:
Updating the firmware while a shared device is in use can lead to data
loss. Before enabling the Allow Shared Devices option, be sure any other
servers sharing the selected devices are offline.

Choose one of these options to downgrade or overwrite the current firmware.

1. Select Allow Downgrades to downgrade the current firmware to an earlier version.
2. Select Allow Rewrites to enable HP SUM to overwrite the current firmware version with the
same version.

136
Note:
HP SUM does not support Allow Downgrades or Allow Rewrites for
the HP VC Ethernet and Fibre Channel Modules for c-Class BladeSystem
firmware component.

Changing the options for firmware upgrade behavior can change the firmware upgrade results. In
this example, the array controller is an HP Smart Array 6402 controller.
If the existing array controller has firmware version 3.00 installed, updating the firmware produces
the results described in the following table.

Firmware version Default Allow downgrades Allow rewrites

Firmware upgrade 3.05 3.05 3.05 3.05

Firmware upgrade 3.10 3.10 3.10 3.10

If the existing array controller has firmware version 3.10 installed, updating the firmware produces
results as described in the following table.

Firmware version Default Allow Downgrades Allow rewrites

Firmware upgrade 3.05 No change 3.05 3.10

Firmware upgrade 3.10 No change No change 3.10

Note:
When updating installation for NIC components, select the devices to be
updated in the window that appears.

After you have selected all the components that you want to install, click Install to proceed with the
installation. The Installation Results screen appears.
Viewing the installation results
When the installation is complete, the Installation Results screen appears (see Figure 9).

137
 Figure 9. Installation Results screen

The Installation Results screen is divided into the following columns:

Column Function

Product Specifies the name of the installed component. To see the component version history, click
the Version number.

Status Specifies the installation status of the component

Additional Enables you to view the installation log for each component, and prompts a reboot if
needed

The following is a list of the Installation Results screen Status column icons.

Icon Text Description

Success The component is installed successfully.

Same/earlier version The existing component is successfully downgraded or re-flashed to the

successfully installed same or earlier version.

Update returned an error An update error has occurred. See the HP SUM log file for details.

Installation failed The component is not installed. To see additional details, click View
Installation Log.

138
Figure 10 shows the Installation Log results screen.

Figure 10. Installation Log results screen

The Installation Results screen includes the following buttons:

Button Function

Reboot Now Reboots the server (This button is available for local installations only.)

Exit Exists the HP SUM

Note:
After updating hard drives in external enclosures such as MSA20,
you must power cycle the external enclosures. The Reboot button in HP
SUM only reboots the server but never power cycles an external enclosure.

There are installation logs named hpsum_log.txt and hpsum_detail_log.txt that contain information
about the installation activity for each host being updated. The hpsum_log.txt log contains a

139
 brief summary of the installation activity. The hpsum_detail_log.txt log contains all of the
installation details, including errors, for each component installed.
The log files are found in the following locations:
 The Windows OS files are located in subdirectories named according to the IP address of each host
in the \CPQSYSTEM\hp\log subdirectory on the boot partition of the local host. However, the
directory containing the local host information is named local host instead of being named after
the IP address.
 The Linux OS files are located in subdirectories named according to the IP address of each host in
the /var/hp/log subdirectory of the local host. The directory containing the local host information is
named local host instead of being named after the IP address. A new file contains detailed
information on the execution of HP SUM.
o The file name for Windows OSs is
C:\cpqsystem\hp\log\hpsum_execution_log_<date>_<ti me>. log.
o The file name for Linux OSs is: /var/hp/log/hpsum_execution_log_<date>_<time>.log.

Using the GUI for multiple-host installations

HP SUM provides an easy-to-use graphical interface that allows you to deploy and maintain firmware
components. After you start HP SUM, the Source Selection screen appears which allows you to
specify the location of the components that you want to deploy. After selecting the location of the
components, the Inventory Progress screen appears while HP SUM builds an inventory of available
updates. When the inventory process is complete, the Select Installation Host(s) screen appears.

Selecting remote hosts or groups

The Select Installation Host(s) screen allows you to choose multiple hosts and groups for component
installation. A remote host can either be the IP address or the DNS name of the following components:
 Remote server
 Remote iLO NIC port
 VC Ethernet
 Fibre Channel Module for c-Class BladeSystem
 BladeSystem OA

Note:
Local hosts cannot be included in a list with remote hosts or in a group.
When selecting an iLO or iLO2 as a host, only the iLO firmware can be
updated. The server host must also be selected to update all other
firmware and software components on the same physical server. The
iLO firmware can be updated by either selecting the iLO or the server host.

Figure 11 shows the Select Installation Host(s) screen for Remote Host or Group options.

140
Figure 11. Select Installation Host(s) screen for Remote Host or Group options

1. To add hosts, press the Manage Hosts button.

2. To add groups, press the Manage Groups button.
3. To continue with the deployment process, follow these steps:
4. Select one or more hosts or groups.
5. Click Next to continue.
6. Enter the credentials for the host
7. Click OK to proceed
When the installation is complete, the Installations result for multiple hosts screen appears.

Managing hosts
To add, edit, or delete hosts, click the Manage Hosts button. The Manage Hosts screen appears.
Hosts include servers, OAs, iLO, and iLO 2.

141
 Note:
Local hosts cannot be included in a list with remote hosts or in a group.
When selecting an iLO or iLO2 as a host, only the iLO firmware can be
updated. The server host must be selected to update all other firmware and
software components. The iLO firmware can be updated by either selecting
the iLO or the server host.

Figure 12 shows the Manage Hosts screen.

Figure 12. Manage Hosts screen

142
Follow these steps to add a host.
1. Click Add Host. The New Host dialog box appears.

2. Select the method to add a host from the following:

o Method 1: Enter the DNS name of the host you want to add. Enter the IP address of the host
you want to add.
o Method 2: Enter the IP address range of the hosts you want to add. The starting and ending
IP addresses must both be on the same subnet. When using the IPv6 format, the last field
in the ending address is limited to 32 targets.

Note:
When adding hosts by using either IP address option, you can
select from the IP format options IPv4 or IPv6. The IPv4 format is
the default option because it is the current Internet protocol. The
IPv6 format is the next generation Internet protocol.

3. Enter an optional user-defined description given to the host you want to add.
4. Click OK.

The new host is added to the list on the Select Installation Host(s) screen.

143
 Follow these steps to edit an existing host.
1. On the Manage Hosts screen, click the Edit Host button.
The Edit Host dialog box appears.

2. Edit the Host Name and Description.

3. Click OK.

Follow these steps to delete a host.

1. On the Manage Hosts screen, click the Delete Host button.
2. When the confirmation screen appears, click Yes.

Entering credentials for hosts

When you select a single remote host, the Enter Credentials for Host screen appears (see Figure 13).
You must enter your user name and password as the credentials for the host.

144
Figure 13. Enter Credentials for Host screen

To enter the credentials for the host, choose one of the following:
1. Select Enter Username and Password, and then enter the username and password.
2. Select Use Current Credentials to use the currently logged-in user credentials.
If an active update process is detected on the remote host, you can select Skip host or Restart update.
Skip host causes the host to be ignored for the rest of the update process, and Restart update
causes any existing or in-progress installation to be terminated.
To continue, click OK.
When you select a group or multiple hosts, the Enter Credentials for Group screen appears as shown
in Figure 14.

145
 Figure 14. Enter Credentials for Group screen

The screen separates the remaining hosts that still require credentials from the completed hosts.
Each pane is divided into the following columns:

Column Function

Name Specifies the name of the host

Status Specifies the credentials status of the host

Description Displays the user-defined description given to the host.

The following is a list of the Enter Credentials for Group screen icons and icon descriptions.

Icon Text Description

Entered The credentials for the host have been entered.

Needs Credentials The credentials for the host have not been entered.

Credentials Failed The credentials entered for the host have failed.

Unable to access host The host cannot be accessed using the credentials
entered, or the host cannot be found on the network.

Host Skipped Due to The host is skipped due to an existing HP SUM

Existing HPSUM Session session. The skipped hosts can be accessed if the
appropriate CLI switch is used or if Restart Update is
selected on the Enter credentials for host screen.

146
Follow these steps to enter the credentials for the host:
1. In the left pane, select the host from the list of hosts requiring credentials.
2. If all credentials are the same, click Select All to select all the hosts on the list.
3. To enter the required credentials and move the selected host to the Completed Hosts pane,
press the Enter button.
4. To continue, click Next.

Note:
If a TPM is detected and enabled, an HP SUM pop-up warning
message appears after the Discovery Progress screen. You must
read the message and determine how to proceed.

Selecting components to install on multiple hosts

As shown in Figure 15, the Select Items to be Installed screen displays the server hosts and status
information.

Figure 15. Select Items to be Installed screen

The Select Items to be Installed screen includes the following buttons:

Button Function

View Host Enables you to view additional information about a host after you select it

Install Installs all selected components on all remote hosts. The Install button is grayed-out when a
dependency failure occurs

Exit Exits HP SUM

147
 The server host pane of the Select Items to be Installed screen displays the summary information for
each server host that is available for installation. The host pane also features a drilldown of
individual hosts.
The following is a list of the Server Host(s) pane columns.

Column Function

Host Specifies the name of the system, number of updates available, and the estimated time for the
installation

Status Specifies the status of the host

The following are the Server Host(s) pane icons and icon descriptions.

Icon Text Description

Ready The host is ready for installation.

Nothing to Install The host is already up-to-date.

Host Skipped Due to The host is skipped due to an existing HP SUM session.
Existing HPSUM Session

Action Required The host is not ready for installation. Click View Host for additional information.

Discovery Failed The host is not ready for installation. The detection of installed hardware,
software, and firmware has failed.

Note:
The default reboot behavior after updates are installed might also appear
in the Status column.

Follow these steps to zoom in to single host selections:

1. Click View Host on the Select Items to be Installed screen.
The Selections for Single Host screen appears.

148
 2. Click Install on the Select Items to be Installed screen to update all hosts.

Viewing the installation results for multiple hosts

When the installation is complete, the Installation Results screen appears.

The Installation Results screen is divided into the following columns:

Column Function

Host Specifies the IP address or DNS name of the host

Status Specifies the overall installation status of the components on the remote host

The following are the Installation Results screen icons and icon descriptions.

Icon Text Description

Success The host was updated successfully.

Nothing to install The host is already up-to-date.

Installation canceled by user The installation was canceled and cannot continue the process.

Installation failed One or more of the component installations have failed.

The Installation Results screen also includes the following buttons:

Button Function

View Host Enables you to view the installation results for the selected host

Exit Exits HP SUM

To view single-host installation results, double-click the host or select the host, and click View Host, as
shown in Figure 16.

149
 Figure 16. Zoom into Single Host screen

Using HP SUM in Scripted or Silent mode

HP SUM allows you to deploy firmware in scripted mode as well. Below are all the command-line
parameters, return codes, information on how to create an inputfile to allow for multiple targets to be
updated simultaneously and samples of how to execute HPSUM.
Command line syntax
The following output is the general command line syntax for HP SUM.
hpsum [/h[elp]] [/?] [/f[orce]] [ /f[ orce] :bundle] [ /f[ orce] :rom]
[/f[ orce] :software] [ /f[ orce] :all ] [/g (/downgrade)] [/e (/rewrite)] [/m[utual])]
[/r[eboot]] [ /reboot _message "reboot message"]
[/reboot _delay timeout_in_seconds] [ /reboot _always] [/s[ilent]] [/c[ omponent]
<component _to _install>] [/group "group _name"] [/b[ undle] <bundle _to _install>] [
/allow _update _to _bundle] [/allow _non _bundle _components] [ /use _latest] [ /use
_location
"file _share"] [ /use _web] [ /use _d[ ownloaded]] [ /tpmbypass] [ /ignore_tpm] [/use_snmp] [
/use_wmi] [ /romonly] [ /softwareonly] [ /dryrun]
[/continue _on _error <error>] [ /override _existing _connection]
[/express _install] [/user <username> or /username <username>] [ /passwd <password>] [
/current _credential] [/target "netAddress"] [ /logdir "path"] [ <component1
_to_install> <component2 _to _install> ...]
[<bundle1 _to _install> <bundle2 _to _install> ...] [/v[erbose]] [/veryv[ erbose]]

The HP SUM with OA requires a user ID and password to log in. The user ID must be an
administrator-equivalent ID and not an operator or user equivalent level ID.

Note:
All arguments and information enclosed in brackets are optional.

150
 On Windows OSs, use a slash (/) before each argument.
 On Linux OSs, use a hyphen (-) before each argument.

If no command line arguments are executed on the command line, the component GUI appears.
Command line arguments
HP SUM recognizes the command line arguments listed in Table 28. These arguments pre-
populate the GUI in the Select Items to be Installed screen. If you specify the host or group, the Select
Items to be Installed screen does not appear.
You cannot use some arguments together, such as /romonly and /softwareonly.
Table 28. Command line arguments

Command line argument Description

/h[ elp] or /? This argument displays command line Help information.

/f[ orce]
This argument enables you to override or downgrade an existing component
installation. This argument produces the same results as /f: software.
/f[ orce] :bundle
This argument enables you to override or downgrade the existing installation of
components in the selected bundle.
/f[ orce] : rom
This argument enables you to override or downgrade the existing installation of
the selected firmware components. (Applies to firmware only.)
/f[ orce] : software
This argument enables you to override or downgrade the existing installation of
the selected software components.
/f[ orce] :all
This argument enables you to override or downgrade the existing installation of
the selected software components, firmware components, and bundles.
/g or /downgrade
This argument enables you to downgrade to an earlier version of firmware for multi-
target devices such as hard drives and array controllers. (Applies to firmware
only.)
/e or /rewrite
This argument enables you to rewrite the same version of firmware only for multi-
target devices such as hard drives and array controllers. (Applies to firmware only.)

/m[utual]
If the device you want to flash is in a shared storage environment, then this
argument informs the firmware flash engine to flash the firmware. If the device to
be flashed is in a shared storage environment, and the /m option is not passed, then
the component installation fails. (Applies to firmware only.)
/r[eboot]
If the following conditions are met, this argument causes the server (or host server in a
remote installation) to reboot:
 The /reboot option is selected or given as a command line argument.
 All components selected for installation are successfully installe d.
 At least one of the installed components requires a reboot to complete its installation.

/reboot _message "reboot

message" This argument displays the specified reboot message on remote consoles
connected to the server you want to reboot. You must use this argument with the
/reboot option, or the argument is ignored.

151
 Command line argument Description
/reboot _delay This argument delays the reboot of the server for the length of time specified by the
timeout_in_secon timeout_i n_seconds variable. You must use this argument with the
ds
/reboot option, or the argument is ignored. Acceptable values are between 15
and 3,600. The default timeout value is 15 seconds for Microsoft Windows
and 60 seconds for Linux. In Linux, the Reboot Delay time is converted from
seconds to minutes. For Linux, any value under a full minute ( 59 seconds or less)
rounds to the next minute.

/reboot _always
If the following conditions are met, then this argument forces the server to reboot:
 The /reboot_always option is selected or given as a command line argument.
 All components selected for installation are successfully installed.

/s[ilent]
 This argument causes the installation to run silently with no GUI or console
output. All data writes to the log file. Any generated prompts use the default option
and continue the installation without user input. If a component requires input
before installation (such as configuration information), then the component
installation fails, and an error message writes to the log file. Failed dependencies are
not reported to the user when using the
 /s[ ilent] argument. To check for failed dependencies, remove the
 /s[ ilent] argument, reissue the command line, and then the HP SUM GUI
appears.
/c[ omponent]
 This argument specifies the components to install. Components to install can be
<component to install>
or specified with or without the /c[ omponent] argument. If using the /c[ omponent]
<component1_to_install> argument, only one component can be specified with the argument. However, multiple
<component2_to_install> /c arguments and components can be specified on the same line. If the /c[ omponent]
argument is not used, multiple components can be specified at the same time, but
the components must be separated by a blank and listed after all the arguments on the
command line. The components are installed in the order provided unless
dependencies between components require installation in a different order. If so,
the utility changes the installation order based on the component
dependencies to ensure the successful installation of as many components as
possible. Multiple components and bundles can be specified on the same
command line. When mixing components and bundles on the command line,
the filter switches control what components and bundles are installed.

/group "group_name"
 This argument specifies an already defined group name in the HP SUM GUI.

/b[ undle]
 This argument specifies the bundles to install. Bundles to install can be
<bundlename> or <bundle
1_to_install> specified with or without the /b[ undle] argument. If using the /b[ undle] argument,
<bundle2_to_install> only one bundle can be specified with the argument. However, multiple /b
arguments and bundles can be specified on the same line. If the /b[ undle]
argument is not used, multiple bundles can be specified at the same time, but the
bundles need to be separated by a blank and listed after all the arguments on the
command line. Multiple components and bundles can be specified on the same
command line. When mixing components and bundles on the command line, the
filter switches control what components and bundles are installed.

/allow_update_to_bun dle
 This argument is a filter switch and enables the user to install newer versions of
components defined in a PSP or firmware bundle. This argument enables these
components to replace the earlier versions of the same component that might
have shipped with the bundles.

152
Command line argument Description
/allow_non_bundle_co
 This argument is a filter switch and enables the user to install components that are
mponents
not included in the bundle but reside in the directory with the components in the
bundle.
/use_latest
 This argument is a filter switch for use with bundles. The argument enables you to
use the latest version of the bundle when multiple versions of bundles are listed on the
command line. If there are no bundles specified on the command line, and
multiple bundles are in the directory, the /use_latest argument allows HP SUM to
use the bundle with the latest version for installation.

/use_location
This argument specifies a directory or file share that contains the PSP and components
file_share
for use with HP SUM. The file_share format must be a mapped file share and not
in Universal Naming Convention (UNC) format. If you do not specify this argument, the
directory containing hpsum.exe or HP SUM is used by default. This populates the
Directory box on the Source Selection screen. The logged-in account must have
access to this location. The /user and /passwd arguments do not have any
effect when attempting to access the file share. You can use those arguments
only when connecting to a target system.

/use_web
This argument specifies that the check box for Check ftp.hp.com on the Source Selection
screen is to be selected. This allows components to be retrieved from hp.com and to be
used in the list of possible updates
/use_d[ownloaded]
This argument specifies that the check box for Include components previously
downloaded from hp.com on the Source Selection screen is to be selected. This
allows those previously downloaded components to be included in the list of
possible updates.
/tpmbypass or
These arguments specify that if a TPM is enabled, the warning message must be
/ignore_tpm
ignored and component installation is allowed to continue.
/use_snmp
This argument specifies that components, which use SNMP protocol, are
available to be selected for installation. These components are available for
selection by default. When the /use_snmp argument is used, and the
/use_wmi argument is not, the WMI components are optional.
/use_wmi
This argument specifies that components, which use WMI protocol, are
available to be selected for installation. These components are optional by
default and will not be installed unless this argument is used. When the
/use_wmi argument is used, and the /use_snmp argument is not, the SNMP
components are optional.

/romonly
This argument is a filter switch and allows the user to see only the firmware
components needed for installation. When using this filter switch, you must exit,
and then restart HP SUM to return to an unfiltered state. Do not use the /romonly
argument with the /softwareonly argument.
/softwareonly
This argument is a filter switch and allows the user to see only the software
components needed for installation. When using this filter switch, you must exit,
and then restart HP SUM to return to an unfiltered state. Do not use the
/softwareonly argument with the /romonly argument.

/dryrun
This argument simulates the installation for a test run. Nothing is installed.

/continue_on_error
This argument causes the installation to continue and ignore errors. Valid
<error>
values are <error>=ServerNotFound and <error>=BadPassword. The
ServerNotFound option can be used to bypass inactive or unavailable remote hosts
when deploying firmware or software to multiple remote hosts at the same time.

153
 Command line argument Description
/override_existing_c
This argument defines the behavior when a remote target has an existing HP SUM
onnection
session in progress. This argument overrides the session in progress and
reinitializes the installation framework on the remote host.

/express_install
This argument starts express install (for local host only). The HP SUM performs
discovery, install, or exit without user interaction. The user can cancel or terminate
HP SUM.
/user <username> or
This argument enables you to log in to HP BladeSystem c-Class OA with your user ID.
/username <username>

/passwd <password>
This argument enables you to use the password for the user ID specified in the /user
parameter. The password is used to log in to remote hosts and HP BladeSystem c-
Class OAs.
/current_credential
This argument enables the credentials of the local host to be used as the
credentials to access the targets instead of providing the username and password
explicitly for each target. The assumption is that the current credentials are valid
for the targets being accessed. (Applies to Windows OSs only.)

/target "netAddress"
This argument is the IP address or the DNS name of a HP BladeSystem c-Class OA
or remote host. When two OAs are in an enclosure, this argument should be
the active OA. When specifying the IP address, you can use either the IPv4 or
IPv6 format.

/logdir "path"
This argument enables you to redirect the output from HP SUM or the HP
BladeSystem c-Class OA flash utility to a different directory than the default
location. For Windows® components, the default location is
%SYSTEMDRIVE%\CPQSYSTEM \hp\log<netAddress> and the redirected
location is <path>\hp\log\<netAddress>. For Linux components, the
default location is /var/hp/log/<netAddress> and the redirected location
is <path>/hp/log/<netAddress>.

/v[ erbose] or /veryv[ e

These arguments enable you to set the verbosity level for the HP SUM execution log
rbos e]
file, hpsum_execution_log_<date>_<time>. log. Using one of these
arguments increases the level of detail that is retained in the log file. The default
value is normal verbosity.

HP SUM return codes

The HP SUM tool provides both silent and scriptable methods of deploying firmware. Both methods
can be used to deploy locally on a server or remotely to a group of servers. Use the /s or -s
command-line parameter to place HPSUM in scriptable or silent mode. . This parameter suppresses all
screen output. However, all output is still written to the HP SUM logs (see Troubleshooting HP SUM for
more information about the HP SUM logs files). HP SUM also indicates the success or failure of the
firmware update operations by returning one of the following return codes:

Return code Value Linux Windows Text

SUCCESS_NO_REBOOT
0 0 0 The installation was successful
and no reboot is required
SUCCESS_REBOOT
1 1 1 The installation was successful,
but reboot is required
SUCCESS_NOT_REQUIRED
3 3 3 The component was current or
not required.

154
 Return code Value Linux Windows Text

FAILURE_GENERAL
-1 255 255 A general failure occurred. See
error log for details
FAILURE_BAD_PARM
-2 254 254 A bad input parameter was
encountered
FAILURE_COMPONENT_FAILED
-3 253 253 The installation of the component
failed.

HP SUM allows targets, credentials and other information to drive the installation process through
various command-line parameters. Extensive work has been done to ensure HP SUM has command-
line equivalents for all GUI-based operations. With the exception of a few items around proxy
authentication for the pulling of updates from ftp.hp.com, this has been accomplished
HP SUM inputfile
In addition, you can use the new inputfile mode in beta format within HP SUM. Though not yet
officially supported, inputfile mode allows network administrators to leverage within HP SUM to script
multiple targets within a single operation. Currently, the limit for HP SUM is 29 total targets for an
installation, although this number will soon increase. The inputfile functionality is leveraged to further
streamline the updates for work groups of servers and targets. The script input file exists on a secure
server or even a personal computer, as long as HP SUM is executed from this chosen platform. Using
a secure server or a management console to protect the credentials is essential to ensure administrator
and root passwords are not exposed.
To create an inputfile, simply use Notepad or vi editor and the following file format.

Note:
All sections headers and trailers [END] must match.

Note:
Failure to use the SILENT=YES option triggers the use of the GUI mode,
which allows a user to skip screens when the information has already been
provided.

Note:
The DRYRUN=YES option performs dry run installations to ensure that the
scripts work without actually deploying the firmware updates that might be
needed on each target. Remove the DRYRUN=YES option to actually
perform the updates.

The following is an example of the FORMAT of an HP SUM inputfile.

DRYRUN = YES
SILENT = YES

[TARGETS]
HOST = BL465C-01
HOST = 192.168.1.2
UID = Bigboss1
PWD = password
[END]

[TARGETS]
HOST = 161.188.162.111
UID = Bigboss2
PWD = password
[END]

155
 Once the file has been created, use it with HP SUM by simply adding it as the -inputfile <filename>
parameter to a normal HP SUM command line. For instance, if the name of the inputfile is hpsum.in,
the command-line syntax is hpsum --inputfile hpsum.in.

Note:
Full paths can be added to the inputfile location if it is not stored in the
same location as the HP SUM executables.

Once HP SUM is executed in silent or scripted mode, it runs to completion. However, the HP SUM will
not run to completion if the credentials are bad for any server in the inputfile or on the command-line
through the /target option, or if any server in the installation set cannot be contacted. If any server
password is invalid, HP SUM stops the installation to prevent it from locking out the administrator
password. In addition, the return codes are consolidated so that if any server in the installation set
fails, an error code is returned.

Note:
HP SUM has a parameter that allows an installation to continue if there is a
bad password or a server is not responding. The
continue_on_error parameter allows the BadPassword and
ServerNotFound options to continue with the installation on the
available servers, and the password works. An error is logged in the
subdirectory for the failing servers. The final HP SUM return code still
reflects that an error occurred, but it allows a user to continue with the
installation for certain targets even when all targets are not available.

Example 1
This command line input deploys the latest PSP and firmware components:
hpsum /use_latest /allow_non_bundle_components /silent

Results
All software components from the current directory, including PSP and firmware components that the
HP SUM determines need to be installed, are installed.
Example 2
Either of the following command-line inputs can deploy the firmware components only from the
BladeSystem Firmware Update Bundle and force all components to be installed on a local system:
 hpsum /f:bundle /romonly BP000537.xml
 hpsum /b BP000537.xml /f:bundle /romonly /silent

Example 3
The following command line can deploy the firmware components only from the BladeSystem
Firmware Update Bundle to targets Target 1 and Server 1:
hpsum /f:bundle /romonly BP000537.xml /target Target1 /target Target2 /user
Administrator /passwd AdminPassword

156
The Target 1 and Server 1 can be any of the following components:
1. An OA
2. A VC Ethernet module
3. An iLO Management NIC port
4. A server that runs the same OS as the system that initiated HPSUM. Both of the targets have the
administrator user ID and the AdminPassword password.

HP SUM special considerations

This chapter describes the areas where special considerations must be made when designing the
firmware update strategy and when using HP SUM. HP SUM provides efficiencies in the firmware
update process, as long as the following details are understood and applied to a general firmware
update strategy.

Network ports used by HP SUM

HP SUM requires that certain network ports are available for proper operation. If you lock down
network ports, remember to ensure that the ports listed in Table 29 and Table 30 are open so that HP
SUM works correctly when connecting to remote target servers and hosts. If you are unable to unlock
these network ports, the only option is to run HP SUM locally and update network-based hosts, such
as the OA, iLO, and VC, through their web interfaces.
Table 29. Ports for Windows

Ports Description

Ports 445 and 137/138/139 These ports are needed to connect to the remote ADMIN$ share on target servers. These
(Port 137 is used only if you are are the standard ports Windows servers use to connect to the remote file shares. If you
using NetBIOS naming service.) can connect remotely to a remote Windows file share on the target server, then you have
the right ports open.

Ports 60000–60028 Random ports are used in this range to pass messages back and forth between the local
and remote systems through the SSL. These ports are used on the system that is running HP
SUM to send data to the target server.
Several internal processes within HP SUM automatically use the port from 60000 when
no other application uses it. If there is a port conflict, the manager uses the next available
port. There is no guarantee that the upper limit is 60028 because it depends on how
many target devices are selected for installation.

Ports 61000–61028 These ports are used from the target server back to the system that is running HP SUM.
The same mechanism is used by the remote access code as the 60000 ports, with the first
trial port as 61000. When a conflict occurs, there is no guarantee that the upper limit is
61028. For the case of ipv4-only and one NIC, the lowest available port is used by HP
SUM to pass information between processes on the local workstation and the location
where the HP SUM is executed. The next available port receives messages from remote
servers.

Port 62286 This port is the default for some internal communications. This port listens on the remote
side if there is no conflict. If a conflict occurs, the next available port is used.

157
 Ports Description

Ports 80 or 63000–63005 The logs are passed to the target and retrieved through an internal secure web server that
uses port 80 if it is available. If it is not available, the server uses a random port between
63000 and 63005. This support allows updates of the iLO and VC firmware without the
need to access the host server. It also allows the servers to run VMware or other
virtualization platforms to update the iLO firmware without requiring a server reboot or a
migration of the virtual machines to other servers.

Note:
HP SUM attempts to determine if a server running HP SUM
also hosts a web server. In some cases, HP SUM cannot
detect an existing web server and attempts to use port 80. If
this occurs, installations that are using HP SUM will fail. If
failure occurs, you can move HP SUM to another server or
workstation that is not already running a web server. You can
also disable the web server until HP SUM installations are
complete.

Table 30. Ports for Linux

Port Description

Port 22 This port is establishes a connection to the remote Linux server via SSH

Ports 60000–60028 Random ports in this range can pass messages back and forth between the local and
remote systems through SSL. These ports are used on the system running HP SUM to send
data to the target server.
Several internal processes within HP SUM automatically use the port from 60000 when
no other application uses it. If there is a port conflict, the manager uses the next available
one. There is no guarantee that the upper limit is 60028 as it is dependent on how many
target devices are selected for installation.

Ports 61000–61028 The target server and the system running the HP SUM both use these ports to pass
information. Both the remote access code and the 60000 ports use the same mechanism,
with the first trial port as 61000. There is no guarantee that the upper limit is 61028
when a conflict occurs. For the case of ipv4 and one NIC, HP SUM uses the lowest
available port to pass information between processes on the local workstation that
executes HP SUM. The next available port receives messages from remote servers.

Port 62286 This port is the default for some internal communications. It listens on the remote side if
there is no conflict. If a conflict occurs, the next available port is used.

Ports 80 or 63000–63005 The logs are passed to the target and retrieved through an internal secure web server that
uses port 80 if it is available or a random port between 63000 and 63005, if it is not.
This support allows iLO and VC firmware updates without having to access the host
server. It also allows servers running VMware or other virtualization platforms to update
their iLO without having to reboot their server or to migrate their virtual machines to other
servers.
Note:
HP SUM attempts to determine if a server running HP SUM
also hosts a web server.In some cases, HP SUM cannot
detect an existing web server and attempts to use port 80. If
this occurs, installations that use HP SUM will fail. If failure
occurs, move HP SUM to another server or workstation that is
not already running a web server. You can also disable the
web server until HP SUM installations are complete.

158
Trusted platform module support issues
When used with BitLocker, the Trusted Platform Module measures a system state and, upon detection
of a changed ROM image, restricts access to the Windows file system if you cannot provide the
recovery key. HP SUM detects a TPM that is enabled in your system. If a TPM is detected in your
system or with any remote server selected as a target, newer models of ProLiant, HP SUM utilities for
iLO, Smart Array, NIC, and BIOS warn users prior to a firmware update. If you do not temporarily
disable BitLocker and cancel the firmware update, you will need the BitLocker recovery key to access
the user data upon reboot.

Note:
Updating the iLO firmware across the network could trigger a TPM event on
the next server reboot, even if the iLO firmware was updated weeks before.
It is best to reboot the server immediately after updating the iLO firmware
when TPM is enabled to prevent a future issue from occurring.

A recovery event is triggered if one of the following items occurs:

 The user does not temporarily disable BitLocker before updating the System BIOS when using the
Microsoft BitLocker Drive Encryption.
 The user has optionally selected to measure iLO, Smart Array, and NIC firmware.

If HP SUM detects a TPM, a pop-up warning message appears.

To allow firmware updates without having to type in the TPM password on each server, the BitLocker
Drive Encryption must be temporarily disabled. Disabling the BitLocker Drive Encryption keeps the
hard drive data encrypted. However, BitLocker uses a plain text decryption key that is stored on the
hard drive to read the information. After the firmware updates are complete, you can re-enable the
BitLocker Drive Encryption Once the BitLocker Drive Encryption is re-enabled, the plain text key is
removed and BitLocker secures the drive again.

Important:
Temporarily disabling BitLocker Drive Encryption can compromise drive
security and should only be attempted in a totally secure environment. For
those administrators unable to provide a totally secure environment, HP
recommends you provide the boot password and leave BitLocker Drive
Encryption enabled throughout the firmware update process. Doing so
requires the /tpmbypass parameter for HP SUM or the firmware update
will be blocked.

159
 Follow these steps to temporarily disable BitLocker support to allow firmware updates.
1. Click Start, type gpedit.msc in the Search Text box, and press Enter.
2. Once the Local Group Policy Editor has started, click Local Computer Policy.
3. Click Computer Configuration.
4. Click Administrative Templates.
5. Click Windows Components.
6. Click BitLocker Drive Encryption.
7. When the BitLocker settings are displayed, double-click Control Panel Setup: Enable Advanced
startup options.
8. When the dialog box is displayed, click Disable.
9. Close all the windows, and start the firmware update.

You can also temporarily disable BitLocker in a script by using the following command:
cscript manage-bde.wsf -protectors -disable c:

Once the firmware update process is complete, you can re-enable the BitLocker Drive Encryption
support by following the previous Steps 1 through 7, then clicking Enabled in Step 8, and then closing
all of the windows. If you are scripting the installation, use the following command to re-enable
BitLocker Drive Encryption after completing the firmware deployment.
cscript manage-bde.wsf -protectors -enable c:

160
TPM scenarios

Scenario Result

If the TPM is detected and enabled, the A pop-up warning message appears. After selecting OK, is selected, you
installation is not silent, and a system ROM may continue. The installation is not cancelled by the detection.
must be updated.

If the TPM is detected and enabled, the No pop-up warning appears. A new log file is generated
installation is silent, the /tpmbypass switch is (%systemdrive%\cpqsystem\log\cpqstub.log). Because the
not given, and any firmware updated must be installation is silent, the installation is terminated and not allowed to
applied to the server. continue.

If the TPM is detected and enabled with Option A pop-up warning message appears. After selecting OK, you may continue.
ROM Measuring, the installation is not silent, The installation is not cancelled by the detection.
and a system ROM must be updated.

If the TPM is detected and enabled with Option No pop-up warning appears. A new log file is generated
ROM Measuring, the installation is silent; the (%systemdrive%\cpqsystem\log\cpqstub.log). Because the
/tpmbypass switch is not given, and any installation is silent, the installation is terminated and not allowed to
firmware updated must be applied to the continue.
server.

If the TPM is detected and enabled, the The installation is allowed as if TPM were not detected.
installation is silent, and the /tpmbypass
switch is supplied.

Note:
All other scenarios will not hinder the normal installation procedure.

VMware ESX firmware updates

VMware ESX/ESXi environments
Because of the lack of a console-based interface and the lockdown of SSH support that HP SUM
normally uses to connect to Linux-based servers, none of the online HP tools can currently update
firmware on blade servers that are running VMware ESX or ESXi. To update the firmware on a blade
server that is running VMware ESX or ESXi, HP recommends evacuating the virtual machine guests to
an alternate host or shutdown the VM’s. To update the firmware on these servers, use the HP
Firmware Maintenance CD or the HP BladeSystem FDT. Even though the firmware update process
involves offline updates, HP recommends the same installation order as that used for blades that
already have an installed OS. The recommended installation order follows.
If the VC Ethernet firmware version is 1.34 or later, HP recommends that you perform the following
tasks to update the enclosure firmware.
1. Update the OA first with the HP BladeSystem Online Firmware Bundles for Windows and Linux
by using the instructions in Scenario 2A: Updating the OA firmware using HP SUM.
2. Update the server-based firmware with the HP BladeSystem FDT or HP Firmware Maintenance
CD by using the instructions described in the following scenarios:
 Scenario 1B: Updating a server using the HP BladeSystem FDT
 Scenario 1C: Updating an individual server using the HP Firmware Maintenance CD

161
 3. Update the VC firmware with the VCSU after all other updates are applied, after the servers
are rebooted, and after all firmware is activated by using the instructions in Scenario 3A:
Updating the VC firmware using VCSU.
If the VC Ethernet firmware is later than version 1.34, HP recommends that you perform the
following tasks to update the enclosure firmware.
4. Update the VC firmware with VCSU as described in Scenario 3A: Updating the VC firmware
using VCSU.
5. Update the OA using the HP BladeSystem Online Firmware Bundles for Windows and Linux by
using the instructions in Scenario 2A: Updating the OA firmware using HP SUM.
6. Update all server-based firmware with the HP BladeSystem FDT or HP Firmware Maintenance
CD by using the instructions in Scenario 1B: Updating a server using the HP BladeSystem FDT
and Scenario 1C: Updating an individual server using the HP Firmware Maintenance CD.
7. Perform automated, scripted installations by moving the VMs to other servers outside the
enclosure selected for update and by using the information in Scenario 6: Scripted installation
of firmware updates for multiple enclosures, including the OA, VC, and server blades.

HP provides individual firmware smart components for online upgrading of the System ROM and iLO
firmware in VMware environments. These smart components apply critical fixes, but because online
smart components are not available for all firmware in VMware environments, HP recommends using
the HP BladeSystem FDT or HP Firmware Maintenance CD update firmware for VMware servers.

HP firmware management services

HP firmware management tools and the BladeSystem Compatibility Chart make it possible for network
and server administrators to apply firmware updates with minimal research or interaction. However in
many environments, administrators find it prudent to have a firmware strategy that takes into account
the significance of the systems and applications, the businesses preference for stability versus
innovation, and sensitivity to downtime. HP offers the following two services that help BladeSystem
administrators review the current firmware levels and to develop an appropriate firmware
management strategy:
 HP BladeSystem Firmware and Driver Gap Analysis
 HP BladeSystem Firmware and Driver Update Process Review

These services are designed for administrators who want to ensure their bladed environment has the
most appropriate firmware and driver levels and wish to develop an effective approach to firmware
and driver maintenance.

HP BladeSystem firmware and Driver Gap analysis

This service offers a thorough review of your BladeSystem current and recommended firmware and
drivers, including analysis of risks and interdependencies. It features: -
1. Working with you remotely and on-site to obtain detailed revision level information for your
BladeSystem firmware and related drivers. This includes all aspects of the enclosure, server
blades with Mezzanine cards, storage blades, power and cooling components, networking
and interconnects including VC.
2. Comparing your existing versions to HP’s current versions, and analyze where you are at risk
based on your environment, the specifics of each firmware item and firmware
interdependencies.

162
 3. Presenting a detailed report with a graphical view of where firmware gaps exist, tables
summarizing specific firmware and driver gaps that require your attention, and an action plan
with specific recommendations and best practices for your update procedure.

HP BladeSystem firmware and Driver Update process review

The Driver Update process review service provides a review of your BladeSystem firmware and driver
update strategy, including best practices and related use of management tools. The Driver Update
includes the following features:
1. An on-site workshop to review your current approach to firmware maintenance. This feature
includes analyzing your business needs, update processes, and use of management tools. This
feature provides a framework so that you can align business requirements with firmware
maintenance practices.
2. Based on input from the workshop, a tailored firmware strategy, which includes best practices
and appropriate use of update mechanisms and management tools such as HP SIM, Version
Control, and HP SUM.
3. A strategy and recommendations report and a discussion on how to fine tune these methods in
your environment.

These firmware management services are available as part of the HP Proactive Select portfolio of
services. For more information, see www.hp.com/services/proactiveselect.

FAQ
The following sections provide typical questions and answers about specific details regarding
firmware updates. Over time, some of the answers may change, so be sure to see the most recent
edition date of this document for the most current information regarding firmware deployment best
practices.
HP recommends the following firmware update processes as discussed in the answers.

Note:
Firmware updates for the HP StorageWorks MDS600 and the HP 3Gb SAS
BL Switch must be done independent of all other firmware updates. These
updates can be done either before or after the rest of the changes
previously listed in the installation order.

Note:
The MDS600 requires that all servers with Smart Array P700m controllers
be powered down, except for the one executing the firmware update. The
3 Gb SAS BL Switch must be updated with the Virtual SAS Manager (VSM)
web browser interface.

Driver dependency considerations

In most cases, server-based firmware updates (other than the System ROM) require that the device
driver be loaded for the device. The device driver provides the interface that the firmware update
tools need to access the physical device and update its firmware. Because the firmware interface is
intrinsic to the driver, the interface is normally not changed even when new hardware is released.
Thus, loading almost any version of the driver for a particular piece of hardware allows the firmware
to be updated. The following table lists the firmware types and known driver dependencies.

163
 Firmware types Known driver dependencies

System ROM None

iLO 2 firmware Windows:

iLO2 firmware 1.78 or later

CpqCiDrv.sys 1.9.3790.0 or later

Linux:

iLO2 firmware 1.78 or later

Any version of the hp_ilo RPM or hpilo driver*

*The hpilo driver is included in the kernel drivers for Red

Hat Enterprise Linux 5.3 and SUSE Linux Enterprise Server
11. The hp_ilo RPM must be used for Red Hat Enterprise
Linux 4.0 and all versions of Red Hat Enterprise Linux 5.0
earlier than 5.3. The hp_ilo RPM must also be used for
SUSE Linux Enterprise Server 10.

Linux:

iLO2 firmware 1.78 or later

Any version of the hp_ilo RPM or hpilo driver*

*The hpilo driver is included in the kernel drivers for Red

Hat Enterprise Linux 5.3 and SUSE Linux Enterprise Server
11. The hp_ilo RPM must be used for Red Hat Enterprise
Linux 4.0 and all versions of Red Hat Enterprise Linux 5.0
and earlier than 5.3. The hp_ilo RPM must also be used for
SUSE Linux Enterprise Server 10.

Broadcom NIC firmware Windows:

One of the following drivers must be installed and

running for Broadcom NIC firmware to be updated in
Windows.

Any version of one of the following Windows drivers.

q57xp32.sys
bxvbdx.sys
nxp2nic.sys
N3xn5x86.sys
q57nd60x.sys

Linux:

One of the following drivers must be installed and

running for Broadcom NIC firmware to be updated in Linux.

tg3 driver 3.58b or later

bnx2 driver 1.4.41 or later
bnx2x driver 1.45.19 or later
Power PIC firmware Windows:
iLO2 firmware 1.78 or later
CpqCiDrv.sys 1.9.3790.0 or later

164
Firmware types Known driver dependencies

Linux:
iLO2 firmware 1.78 or later
Any version of the hp_ilo RPM or hpilo driver*

*The hpilo driver is included in the kernel drivers for Red

Hat Enterprise Linux 5.3 and SUSE Linux Enterprise Server
11. The hp_ilo RPM must be used for Red Hat Enterprise
Linux 4.0 and all versions of Red Hat Enterprise Linux 5.0
earlier than 5.3. The hp_ilo RPM must also be used for
SUSE Linux Enterprise Server 10.
Windows:
Smart Array controller firmware
hpcisss2.sys driver 5.8.0.0 or later

Linux:
cpq_cciss RPM 2.4.48-12 or later

Note:
Later driver versions may be
required to support newer Smart
Array controllers. The version
listed is the minimum needed to
support firmware updates.

SAS and SATA hard drive firmware behind Smart Array Windows:
controllers hpcisss2.sys driver 5.8.0.0 or later

Linux:
cpq_cciss RPM 2.4.48-12 or later
Note:
Later driver versions may be
required to support newer Smart
Array controllers. The version
listed is the minimum needed to
support firmware updates.

Emulex, QLogic, and Brocade Fiber Channel HBA Linux:

firmware *The requirement is for a kernel driver for the appropriate
adapter that has been compiled to work with the boot
*Can only be updated offline kernel. Since all three of these adapter’s drivers are
shipped as source RPMs, the source must be compiled
through installation of the RPM and then the resulting driver
used in the boot environment. Since this is only available in
offline mode, the details about how to create and integrate
the appropriate kernel driver are left to the user.

Tape blade firmware For SCSI attached tape drives, the following drivers must be
loaded. For USB-attached tape drives, the support is
already in the OS.

Windows:
hpcisss2.sys driver 5.8.0.0 or later

Linux:
cpq_cciss RPM 2.4.48-12 or later

165
 Firmware types Known driver dependencies

Note:
Later driver versions may be
required to support newer Smart
Array controllers. The version
listed is the minimum needed to
support firmware updates.

OA firmware None

VC firmware None

HP StorageWorks MDS600 Linux:

cpq_cciss RPM 2.4.48-12 or later

*Can only be updated offline Note:

Later driver versions may be
required to support newer Smart
Array controllers. The version
listed is the minimum needed to
support firmware updates.

HP 3Gb SAS BL Switch Firmware None

What tools should I use to update the various firmware types?

The recommended tools for updating firmware are HP SUM tool and VCSU, as discussed previously
in this document. Firmware will be released as part of three different tools: the HP BladeSystem FDT;
the HP BladeSystem Online Firmware Bundles for Windows and Linux; and the Firmware
Maintenance CD. These three tools leverage the recommended tools to deploy firmware updates.
Why must I always upgrade to the latest individual firmware and driver components?
As discussed previously, instead of recommending that individual firmware be at a given level, HP
Support is directed to ensure an administrator is at a given Quarterly Release Set as shown by the HP
BladeSystem Compatibility Chart and enforced by the Firmware Maintenance CD, HP BladeSystem
FDT, and HP BladeSystem Bundles. Unless an individual smart component is released for a critical
update, administrators should not be directed to install individual smart components.

HP SUM questions
This section contains questions that are directly related to HP SUM and its use in the firmware
environment.
How does HP SUM work when applied to an entire chassis; for example, does it update each blade,
iLO2, and so on, sequentially or in parallel?
When HP SUM in executed, the updates are parallel across each target regardless of whether or not
the targets are blades, iLOs, OAs, or VC. However, it executes sequentially within a blade, iLO, VC,
or OA. In other words, all targets are updated in parallel, but only one piece of firmware is updated
at one time on each of the targets that HP SUM is updating.
What are the advantages and drawbacks to using the HP BladeSystem Firmware Update Bundles
versus the HP BladeSystem FDT?
The advantage to the FDT is that it can update firmware for the QLogic, Brocade, and Emulex FC
HBAs. The disadvantage is that it cannot update OA or VC firmware. The advantage of the
BladeSystem Firmware Update Bundles is that it can update the firmware on the OA, VC, and other
network-based targets that the FDT cannot update. Another advantage of the BladeSystem Firmware
Update Bundles is the ability to update multiple targets simultaneously up to the current HP SUM limit
of 29 concurrent targets.

166
 Why is Version Control (included with SIM) not the tool of choice to manage firmware upgrades
across the HP BladeSystem portfolio?
The current Version Control Agent (VCA) requires the target to be a server, and requires the
installation of the Version Control Agent on each server. In addition, Version Control only supports a
limited set of firmware updates on a server. Also, Version Control requires that a Windows-based
server host the Version Control Repository Manager (VCRM), which acts as a host for providing the
firmware updates to remote servers. In many Linux-only IT departments, this restriction prevents the use
of Version Control.
Another advantage to using HP SUM is that it can work with non-server-based targets, such as the OA
and VC, which the VCA cannot update. The SIM version control infrastructure is re-architected to
leverage HP SUM as the deployment mechanism to remove the requirement of an agent on each
target and allows SIM to support firmware deployment to network-based devices such as the OA and
VC. The first release of this new architecture is planned ith the SIM 6.0 release.
Currently, Version Control cannot update any offline firmware, which means the Emulex, QLogic, and
Brocade Fiber Channel HBA firmware, the NetXen NIC firmware, and the MDS600 firmware cannot
be updated by using SIM or the VCA.
What about administrators who have invested time to understand HP SIM and specifically Version
Control?
The HP SUM technology will be incorporated into SIM starting in the SIM 6.0 release as a new
method of deploying software and firmware. This will still allow administrators who have invested in
the VCRM to leverage that investment but will allow users to update firmware on non-server-based
target devices. The VCRM catalog will continue to be updated for at least one year after HP SUM
provides equivalent functionality compared to what is available today. Currently, the HP SUM-
equivalent functionality to all features of Version Control will not be completed for several releases.
Plenty of advance notice will be given to administrators to allow them to plan and implement any
changes needed to support the new SIM version control infrastructure. In most cases, the only change
needed will be to remove the Version Control Agent from the servers after validating the new SIM
version control infrastructure works in their environment. Version Control Repository Manager (VCRM)
servers can still be leveraged, but are not required to support this new version-control infrastructure.
Where do I obtain theHP SUM user guide?
The latest HP SUM User’s Guide is always provided in the Firmware CD User’s Guide. To obtain a
copy of this PDF file, visit the FTP site located at ftp://ftp.hp.com/pub/c-
products/servers/management/smartstart/, and choose the latest version of the
FWCDUsersGuidex.xx.pdf file.

How can I leverage the HP SUM pull-from-web functionality when my data center cannot be connected
to the Internet for security reasons?
In this case, the only way to leverage the functionality is to execute HP SUM from a workstation that is
dual-homed on a network with Internet access and to a management network. HP SUM can be
executed on a Windows XP, Vista, or Windows 7 workstation. The HP SUM remote deployment
capabilities can update remote servers, OAs, VC modules, and iLOs. When leveraging the
workstation, none of the servers are connected directly to the Internet. In this configuration, HP SUM
pulls updates through the network connected to the Internet and deploys them on the management
network.
It seems the HPSUM GUI interface cannot currently accept input (for example, groups of IP addresses)
from files, but I heard this feature is planned in a future version. Does the HPSUM CLI allow creation of
a group from a file with a list of IP addresses or DNS names when the file is presented to it as a file
name that is given as a CLI command-line parameter?
HP SUM can accept an input file for the IP addresses and user credentials. The use current
credentials option can be used with the CLI for Windows only (it’s not clear text across the

167
 network) as current credentials are not available for Linux users. For more information on how to use
this in your firmware deployments, see HP SUM special considerations.
What is the function of the additional drivers in the BladeSystem Firmware Update Bundle?
The additional drivers facilitate the application of the firmware updates. They are provided as a
convenience and can be deleted if needed Also, if you do not wish to upset the currently installed
software baselines, HP SUM provides an option either through the GUI or silent/scripted installation
that you can select so that the additional drivers are not used. On the Source Selection screen in the
GUI, simply select the Firmware Only option at the bottom of the screen. For silent/script installations,
you can provide the /rom_only command-line parameter when initiating HP SUM from the console
window. This feature is only available in HP SUM 3.6.0 and later.
What is the purpose of the dryrun scripting option?
Its primary purpose is to test scripts called from the CLI approach to HP SUM. The dryrun feature in HP
SUM is activated by using the /dryrun or --dryrun switch, which causes HP SUM to bypass the
actual calling of the firmware smart components during installation and return SUCCESS. This mode is
useful for validating when the targets are available, that credentials are valid, and that all of the
network interfaces and ports are available for a successful firmware deployment.
When using the HP BladeSystem Online Firmware Bundles for Windows and Linux to upgrade an
entire c7000 Enclosure and all of its constituents, including the OAs, server blades, iLO2s, and switch
modules:
 Can I simply give the HPSUM tool the OA IP address?
 Is the tool able to upgrade all of the components inside the chassis because the OA can
automatically identify the addresses of the iLO2 and modules?
 Do I have to manually add IP addresses of the blades, iLO2s, modules, and so on, into the HPSUM
GUI interface, thereby creating my own group, which is, in effect, the enclosure and all of its
contents?
 Must I always manually add the host OS IP address that upgrades the blade server BIOS because
the OA cannot identify what it is?
You need to provide the IP addresses/DNS names for all servers that you want updated, along with
the address/DNS name of the OA. On the servers, HPSUM updates the System ROM, iLO/iLO2
firmware, Smart Array Controllers, SAS/SATA hard drives, NICs, and any of the base drivers (iLO,
Smart Array, or NIC) from the HP BladeSystem Online Firmware Bundles for Windows and Linux. In
addition, HPSUM updates the OA firmware through the OA NIC interface. It can be somewhat time-
consuming the first time that you enter the data, but once entered, HP SUM remembers the data
between utility runs. While no passwords are saved, the targets and groups are saved for future
updates
Currently, the server BIOS must be updated prior to the iLO2 because of a potential issue with the
Power PIC. Will HP SUM reorder the installation set to avoid this issue?
There is not an issue with the installation order of the PowerPIC firmware and server BIOS updates.
This was an early concern when the PowerPIC firmware was first released. The current requirements
for updating the PowerPIC firmware including the following:
 The PMC firmware must be 0.7 or later. Version 0.5 does not need to be flashed and cannot be
flashed by using any existing smart components or tools. Many older BL460c G1, BL465c G1,
BL480c G1, and BL685c G1 servers are 0.5 and do not need to be updated. Be aware that the
only difference between the 0.5 and 3.4 versions of PowerPIC firmware is the response time to
power capping commands. Version 0.5 normally responds to power adjustment commands within
a couple of seconds. Version 3.4 normally responds within milliseconds. Response time does not
affect the operation of the servers or the overall power requirements of a given blade.

168
 The stepping level of the processors on some BL460c G1 and BL480c G1 servers must be G or
later.
 iLO2 firmware 1.78 or later must be installed before the PowerPIC firmware can be updated.
 An iLO2 driver must be loaded.
 System ROM must have dynamic power capping support. All ROMs released in 2009 or later meet
this requirement.
 OA firmware must be 2.41 or later for dynamic power capping to function properly.
 All versions prior to PMC firmware 3.4 have known issues, so HP strongly recommends that you
update to 3.4 or later.

Note:
You need PowerPIC firmware 3.4(C) to interface with HP SUM.

Miscellaneous BladeSystem firmware-related questions

This section contains questions directly related to blade firmware updates.
Can SIM use the HP BladeSystem firmware update bundles for Windows and Linux as a VCRM-custom
base line?
Yes, it can be used by dropping the downloaded and expanded bundle into the VCRM directory and
running a rescan on this directory from the HP Systems Management Homepage for the VCRM.
However, if SIM 5.x or earlier is used, only the System ROM, iLO, Smart Array controller, and NIC
firmware can be updated. Additional firmware can be updated, beginning with SIM 6.0. Even with
SIM 6.0, however, there is no support for offline updates, which is required for the Emulex, QLogic,
Brocade Fiber Channel HBA, NetXen NIC, and MDS600 firmware updates. For information on
additional support for the SIM 6.0 release, see HP SIM and Version Control Agent.
What is the recommended tool for understanding the currently-deployed BladeSystem equipment
firmware revisions?
Some HP SUM firmware versions are based on the selected programs that the agent installed on the
target systems HP SUM will have support for generating an HTML report of this functionality in a future
release.
What are the dependencies between the firmware and PSP drivers?
System software (for example, drivers and services) dependencies for firmware updates are very
generic in that a driver needs to be loaded so the device can be discovered, version checked, and so
on. The list of generic dependencies is addressed in a previous FAQ question. HP tests the current
firmware Quarterly Release Sets with the most current and two most recent early versions of the PSP
and its associated drivers. As long as the user stays within the combined support window of the PSP
and firmware Quarterly Release Sets, all firmware update dependencies should be met.

169
 Can we upgrade each component directly to the latest version or do we need intermediate revision
steps.
Almost all components can be upgraded to the latest firmware revision without issue. The only
component that requires an interim revision is for OA firmware updates from 1.x f/w revisions to 2.x
versions. For more information, see the following support documents:
 Customer Advisory: HP OA- Upgrading Firmware From Version 1.x to Version 2.25 (or Later) Will
Not Be Successful
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?locale=en_US&objectID=c0
1597033
 Link to earlier versions of the OA firmware:
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&
prodTypeId=3709945&prodSeriesId=3808910&swItem=MTX-
c1b90e546c3f476193c43cf0d9&prodNameId=3808911&swEnvOID=4006&swLang=13&taskId
=135&mode=5
Can I update my Blades HBA firmware online?
If you have QLogic, Brocade, or Emulex FC HBAs in your servers, you must boot offline (by using the
HP BladeSystem FDT or the Firmware Maintenance CD) to update the firmware. This is required
because these vendors have not yet provided online firmware flash tools. HP is working with the
individual firmware vendors and hopes to have online firmware updates for these Fiber Channel
HBAs in the future.
How do I manage my Blade interconnect switch updates?
You must use the vendor tools to update the blade switch interconnect modules. In the future, HP SUM
will be enhanced to support blade switch interconnects.
Are there any guidelines for downgrading firmware?
There are several limitations about downgrading firmware. If necessary, firmware downgrades should
only be attempted on a component-by-component basis. None of the current installation tools have the
necessary logic to preclude issues from occurring when downgrading firmware. Downgrades are
discouraged unless absolutely necessary.

Best Practice:
Do not downgrade more than one firmware version or risk incompatibilities
between the downgraded firmware and other hardware.

Can you upgrade versions of HBA firmware without being concerned about going through an interim
version to facilitate the upgrade?
There are no generational skipping requirements for Fibre Channel HBAs. You can upgrade from one
firmware and boot bios version to another without any intermediate steps.
Can I roll-back the individual changes on a per-server or per chassis basis?
There is no uninstall/reverse functionality, although it is possible to force older components to
overwrite newer ones if a reference set of the presently installed versions is created.

Note:
HP strongly discourages downgrading firmware unless absolutely
necessary.

170
How often should we upgrade firmware?
Normally, update cycles should be set at approximately 6-month intervals. HP strongly recommends
upgrading within the 9-month support window, which includes the currently released Quarterly
Release Set plus two earlier versions to ensure vital updates and enhancements are installed. The
result is optimal performance and availability of HP BladeSystem enclosures and servers.
How does the firmware version affect our support status with HP?
HP Support requires that when support is needed for a server, the serve must be aligned with one of
the columns on the BladeSystem Firmware Compatibility Chart; otherwise, an administrator is
requested to update the server before additional support is provided. Doing so ensures that all known
issues are addressed and possibly resolved and that the enclosure and blades are at a known support
state before HP Support attempts to resolve the problem.
How do I add updated components to the HP BladeSystem FDT?
Today, the only want to update the FDT is to use UltraISO or another ISO editing tool that supports
SLES10 SP2 (or in the SLES11) boot environments.
How do I add updated components to the HP firmware maintenance CD?
The following information will guide you in adding components to the HP Firmware Maintenance CD.
Using a USB Key
1. Insert a USB key containing the Firmware CD ISO image created.
If the blade server supports the SUV cable, use the HP USB Key Creator for Windows utility in
the SUV (Serial-USB-Video) cable attached to the blade that is selected for update.
2. For Windows, download the HP USB Key Creator for Windows utility from the HP website and
install it on a workstation.
Once installed, the utility places a shortcut in the Programs start menu folder of the HP System
Tools.
Follow these steps to make your drive key bootable and copy the contents of the CD.
1. Place your HP USB drive key in an available USB port.
2. Select the HP USB Key Utility shortcut in the HP System Tools folder.
3. Complete each step presented by the application.

Note:
The HP USB Key Creator formats the USB key so that any files on
the key are lost. Be sure to use a USB key that is at least 1 GB
and does not contain any valuable files.

For Linux, you can manually create the USB key by following these steps.
1. Obtain SYSLINUX 3.2 or higher from http://freshmeat.com or http://syslinux.zytor.com from
and download to a Linux workstation.
2. Install the SYSLINUX RPM obtained in Step 1.
3. Create a directory for the USB key mountpoint if one does not already exist. (For example,
mkdir /usbkey.)
4. Insert the USB key and mount it (mount /dev/sda1 /usbkey).

171
 Note:
The device mountpoint can vary depending on whether other
SCSI drives are also installed on the server. Thus, the device
mountpoint can be sdb1, sdc1, etc).

5. Issue the command ./syslinux /usbkey to have SYSLINUX write out the boot partition to the
USB key.

Caution:
Failure to follow this step could lead to a key that will not boot
the Firmware CD until the SYSLINUX command is successful.

6. Create a directory to mount the CD image.

mkdir /cd_mount_point

7. Insert the Firmware CD or mount the Firmware CD ISO via a loopback.

mount /dev/cdrom /cd_mount_point

or
mount -t iso9660 firmware-<version>.iso /cd_mount_point -o loop

8. Change to the /usb directory on the CD.

cd /cd_mount_point/usb

9. Execute the usbcreator.sh shell script passing in the CD mount point and the USB mount point
to move the Firmware CD files to the USB key.
./usbcreator.sh /cd_mount_point /usbkey

10. If additional components must be added to the USB, copy them into the /compaq/swpackages
(Linux) or the \compaq\swpackages (Windows) directory and HP SUM picks them up
automatically if the HP SUM version being used can support the type of components added.
11. .Unmount the CD and the USB key.
umount /dev/cdrom
umount /dev/sda1

Note:
This must match the initial mount point in Step 4.

12. Remove the USB key and CD from the workstation used to create the USB key.

Using a hard drive

1. Copy the contents of the \compaq\swpackages directory from the CD or ISO image to a
directory on the hard drive in the location where HP SUM will be executed.
2. Ensure execute privileges are available in Linux by using the chmod 700 * command. By
default, the files are copied off the CD in Linux as read-only with no execution privileges.
3. Copy any updated files into the same directory as where the files are copied in Step 1.
4. Execute HPSUM so that the new firmware components are recognized.

172
How do virtual environments affect the firmware update process?
Unfortunately, none of HP current firmware update tools work in virtualized environments. The
problem is the Virtual Machines abstract the physical hardware and firmware updates deal with
physical hardware. VM’s have limited ability to access underlying hardware through vendor-specific
APIs. Because of the physical hardware abstraction, it is necessary for the user to either shut down or
move all of the VMs to another server and reboot the server into another boot environment, such as
the ones provided by the HP BladeSystem FDT and the HP Firmware Maintenance CD. These boot
environments provide access to the physical hardware so the firmware can be updated. Once the
update process has been completed, the virtual machine environment can be restored to its initial
configuration by either restarting the VMs or moving them back to the recently updated server.

Installed firmware version data collection

Enclosure-level firmware information
Unfortunately, there is not a single tool to pull all firmware-version information for an enclosure.
However, by scripting the use of the available tools, it is possible to pull together a list of much of the
firmware in an enclosure.
Through a combination of SSH scripts and RIBCL commands, it is possible to pull the OA version, the
iLO firmware version, the System ROM version, PowerPIC, and the VC firmware version.
There are a number of possible ways to collect the firmware revision date of the current install base.
HP recommends using the HP SIM tool, especially when collecting information from a large IT
environment. This is because both standard and customized report can be derived from the tool that
enables viewing of the various firmware revisions that might be present.
Another way to collect firmware information is by using a CLI approach when connecting to the OA
with OpenSSH. Once SSH has been installed, OA CLI commands can be issued against the active
OA to obtain firmware information about the enclosure. The OA CLI commands are documented in
the HP BladeSystem Onboard Administrator Command Line Interface User Guide.
Use the ssh command to retrieve the OA firmware as follows:
ssh -l Administrator 16.89.1.3 show oa info

In this command, Administrator is the OA administrator account and 16.89.1.3 is the address of the
active OA module. The output from the command returns a similar output as the following example.
The highlighted element contains the version of OA firmware currently installed (2.52).
Onboard Administrator #1 information:
Product Name : BladeSystem c3000 Onboard Administrator
Part Number : 448589-B21
Spare Part No.: 441832-001
Serial Number : P3059X39VUE073
UUID : 18P3059X39VUE073
Manufacturer : HP
Firmware Ver. : 2.52 Jul 13 2009
Hw Board Type : 1
Hw Version : X3

The ssh command can be used to retrieve the installed versions of iLO, System ROM, and PowerPIC
firmware by using the OA show server info all command. The highlighted areas reflect the
System ROM version, the iLO firmware version and the PowerPIC firmware version in sequence.
ssh -l Administrator 16.89.1.3 show server info all

Server Blade #1 Information:

Type: Server Blade
Manufacturer: HP

173
 Product Name: ProLiant BL280c G6
Part Number: [Unknown]
System Board Spare Part Number: 531337-001
Serial Number: 2UX91700UU
UUID: 37373035-3738-5532-5839-313730305555
Server Name: WIN-P2L0THRBZYQ
Asset Tag: [Unknown]
ROM Version: I22 08/14/2009

CPU 1: Six-Core Intel Xeon 2400 MHz

CPU 2: Not present
Memory: 6144 MB

Embedded Ethernet
NIC 1 MAC Address: 00:24:81:D2:89:5A
NIC 2 MAC Address: 00:24:81:D2:89:5B

Management Processor Information:

Type: iLO2
Name: ILO2UX91700UU
Firmware Version: 1.79 Aug 26 2009
IP Address: 16.89.2.173
MAC Address: 00:24:81:D2:89:5E
Power Management Controller Version: 3.4

In some cases, the Power Management controller firmware version shows Not Available. This is
usually an indication that the Power Management controller is not functioning correctly. If this
happens, try powering off the blade, removing it from the enclosure, and re-inserting it. If the problem
still occurs, contact HP Technical Support to report the problem.
Management Processor Information:
Type: iLO2
Name: ILOTWT750009P
Firmware Version: 1.79 Aug 28 2009
IP Address: 16.89.1.78
MAC Address: 00:1E:0B:92:30:66
Power Management Controller Version: Not Available

To find the version of installed firmware for the VC, use the show firmware command by using
OpenSSH for Windows or the ssh RPM for Linux as shown in the example that follows. The password
must be provided, unless SSH credentials are established with the VCM.
C:\>ssh -l Administrator 16.83.61.67 show firmware
Password:
=============================================================================
ID Enclosure Bay Type Firmware Version Status
=============================================================================
enc0:1 HPSUMEnclosure 1 VC-ENET 2.12 2009-08-06T16:45:57Z OK
-----------------------------------------------------------------------------
enc0:2 HPSUMEnclosure 2 Unknown
Incompatible
-----------------------------------------------------------------------------
enc0:3 HPSUMEnclosure 3 VC-ENET 2.12 2009-08-06T16:45:57Z OK
-----------------------------------------------------------------------------
enc0:4 HPSUMEnclosure 4 Unknown OK
-----------------------------------------------------------------------------
enc0:5 HPSUMEnclosure 5 VC-FC 1.32 7.12.2.04
OK

In this example, the VC Ethernet modules in Bay 1 and Bay 3 are 2.12 of VC firmware, and the VC
Fiber Channel module in Bay 5 is 1.32.

174
Blade server-level firmware information
As with the Enclosure-Level firmware information, there is not a single tool that provides all firmware
version information within a blade. However, by leveraging data reported by the individual smart
components, most of the installed firmware versions can be obtained without too much effort. The only
exception is the installed firmware version for the Emulex, Brocade, and QLogic Fiber Channel HBAs.
Currently, the firmware version for the HBAs can only be obtained in Linux without the use of external
applications such as SANSurfer, CommandView, and others.
This section covers how to obtain the installed firmware versions for the following firmware types:
NIC firmware
To determine the versions of NIC firmware installed in a given server, the NIC firmware smart
component must be available. The NIC firmware component provides its own firmware version
information for each type of firmware available for each NIC found in the server. The component can
be executed in discovery mode and provides a file name to generate the special discovery output file.
The NIC firmware component can be executed in discovery mode by using the following command.
CP010605.scexe /d CP010605_nic.xml
Where:
 CP010605.scexe is the name of the NIC firmware component
 /d is the discovery option
 CP010605_nic.xml is the output file name to write the discovered firmware information

Note:
The /d option must be /d and must immediately be followed with a file
name. Otherwise, the firmware component launches the NIC firmware
installers instead of identifying the available NIC firmware.

The resulting output file shows the information in the following example. In this example, the output
has been pruned to show only necessary details.
…
<alt_name value="HP NC-Series Broadcom Online Firmware Upgrade Utility
for Linux" />
<version value="2.1.8" />
<takes_effect value="reboot" />
<devices>
<device>
<device_id value="eth0" />
…
<macaddress value="001A4BB28938" />
<product_id value="HP NC373i Multifunction Gigabit Server
Adapter" />
…
<fw_item>
<type value="Bootcode" />
…
<version value="1.9.6" />
<active_version value="1.9.6" />
…
</fw_item>
<fw_item>
<type value="PXE" />
…
<version value="n/a" />
<active_version value="n/a" />
…
</fw_item>
175
 <fw_item>
<type value="iSCSI" />
…
<version value="1.2.3" />
<active_version value="1.2.2" />
…
</fw_item>
</device>
</devices>
…
The first version field located near the top of the returned XML file (2.1.8 in the example) indicates the
version of the component being used and does not indicate the individual firmware types.
Each NIC has its own <device> entry. The entry also includes product name and MAC address of the
adapter that is being reported, plus multiple firmware items ( fw_item) entries that indicate the
installed firmware version for each type of firmware available on the NIC. For each type of firmware,
the <version> field indicates the version of firmware that is deployed if the firmware update is
initiated with this component. The <active_version> field indicates the currently installed version of
this firmware.
In the previous example, the Bootcode shows the installed version in the <active_version> field as
1.9.6 and the version available in the component as also being 1.9.6. In the PXE item, the n/a
indicates this NIC has PXE support disabled and, therefore, cannot be updated. In the last firmware
item for iSCSI support, the installed version of firmware is 1.2.2 and the component updates it to
1.2.3 if an update was attempted with the CP010605.scexe component used to generate the
discovered data.

Note:
The same discovery file format is also available using the Windows smart
components.

Tape firmware
To determine the version of tape firmware installed on a given tape drive, the tape firmware smart
component must be available. The tape firmware component provides its own firmware version
information for each tape drive found in a server. The component can be executed in discovery mode
and provides a file name to generate the special discovery output file. The tape firmware component
can be executed in discovery mode by using the following command.
CP010445.scexe -s -d CP010445_tape.xml

Where:
 CP010445.scexe is the name of the tape firmware component
 -s is the silent option
 -d is the discovery option
 CP010445_tape.xml is the output filename to write the discovered firmware information

The CP010445_tape.xml file option must be passed immediately after the -d option for this to work.
This file can then be parsed to obtain the drive type and firmware as highlighted in the following
sample tape firmware discovery output file called CP010445_tape.xml in our example.
<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
<hp_rom_discovery version="2.0.0.0">
<type value="TAPE"/>
<alt_name value="HP TAPE Firmware for Drive x, Drive y, and Drive z for
Windows"/>

176
 <version value="2.0.3"/>
<takes_effect value="immediate"/>
<devices>
<device>
<device_id value="0x80050300"/>
<product_id value="Ultrium 4-SCSI"/>
<busnumber value="0"/>
<devicenumber value="0"/>
<funcnumber value="0"/>
<fw_item>
<type value=""/>
<firmware_id value=""/>
<version value="11.825000"/>
<active_version value="11.825000"/>
<action value="upgrade"/>
<duration value="0"/>
<message value=""/>
<shared value="no"/>
</fw_item>
</device>
</devices>
</hp_rom_discovery>

In this example, the Ultrium 4 SCSI tape drive in the server is 11.825000 of the firmware that is
available for that type of drive.

Note:
The same discovery file format is also available by using the Windows
smart components.

Smart Array controller firmware and SAS/SATA hard drive firmware versions
The HP Array Configuration Utility Command-Line Interface program (hpacucli) can pull controller
and hard-drive firmware information. The latest version of the hpacucli utility is found in the latest HP
ProLiant Support Pack version. Once installed, the binary file and its support libraries are placed in
the C:\Program Files\Compaq\Hpacucli\Bin” or “C:\Program Files
(x86)\Compaq\Hpacucli\bin directory, depending on the architecture of the system on which it was
originally installed. The files in the directory can be scraped and added to a script that is executed on
each server. Doing so pulls out the installed firmware version for the Smart Array Controllers and hard
drives located behind these controllers in a given server. The following is an example of the command
to show the details for

C:\Program Files\Compaq\Hpacucli\Bin>hpacucli ctrl all show config detail

Smart Array P400 in Slot 1

…
Hardware Revision: Rev B
Firmware Version: 5.26
…
physicaldrive 2I:1:3
…
Drive Type: Data Drive
Interface Type: SAS
Size: 36 GB
Rotational Speed: 10000
Firmware Revision: HPD4
Serial Number: B0G2P5700KDH0527
Model: HP DG036A8B5B
…
physicaldrive 2I:1:4
…

177
 Drive Type: Data Drive
Interface Type: SAS
Size: 36 GB
Rotational Speed: 10000
Firmware Revision: HPD7
Serial Number: 3LC04GYB00007543CG6U
Model: HP DG036A8B53
…

In this example, which has been reduced to show only the relevant parts, the Smart Array firmware
5.26 and of the drives shown, one is HP model number DG036A8B5B and has firmware HPD4, and
the other is HP model number DG036A8B53 and has firmware HPD7 installed. Multiple controllers
and drives can be reported in a single call to hpacucli.

Note:
The same functionality also exists for Linux with the HP array configuration
utility command-line interface RPM provided in the ProLiant Support Packs
for Linux.

Troubleshooting
Troubleshooting HP SUM
When using HPSUM, the logs files are located at the following locations:
 Windows (for both firmware and drivers)
%SYSTEMDRIVE%\cpqsystem\hp\log\<ip_address>\hpsum_detail_log.txt

 Linux
/var/hp/log/<ip_address>/hpsum_detail_log.txt

Note:
Using the offline environments provided by the Firmware Maintenance CD
and the HP BladeSystem FDT result in the log files being written to the Linux
location.

HP SUM also creates trace logs of its installation that can be used to debug problems. These trace
files are located in the following places:
 Windows Server 2003/XP/Vista:
%TEMP%\hp_sum\

 Windows Server 2008:

%TEMP%\<number>\hp_sum normally the <number> is “1”

 Linux:
/tmp/hp_sum

HP SUM creates a separate trace log for each target server. These are captured in subdirectories
under the trace log directories noted in this example. The directories start with Target_0, Target_1,
and so on. These directories contain the target specific trace information. No passwords or sensitive
data is stored in this trace logs.
178
How to debug Discovery failures
If you receive an HPSUM Connection Error or Discovery Failed messages, there are several
troubleshooting tips.
1. Ensure your workstation does not have an existing connection to the ADMIN$ share on the
target IP address. If it does, it prevents HP SUM from connecting to the remote server share,
because Windows only allows one connection from a client to a server share. This can be
checked by entering net use‖ at a command prompt. If there is an existing share to the target
IP address \admin$ share, delete it and try the installation again.
2. Ensure the target IP address server admin$ share is accessible. To accomplish this, validate the
target server can be accessed by entering net use x:
\\<ip_address_or_dns_name>\admin$ for the target server IP address or DNS name. Once
the connection is validated, ensure it gets deleted by entering net use x: /d at a command
prompt.
3. Ensure that the user id for connecting to the target IP address server is part of the administrators
group. If it isn’t, HP SUM blocks installation to the target.
4. Ensure WMI is enabled and running on all Windows target servers
5. For Linux, ensure the SSH port is not blocked.
In some rare cases, external storage enclosures may cause HP SUM to hang or report discovery
failed. To resolve this problem, disconnect the external storage until the firmware updates are
complete.
For Linux, ensure the target server can be contacted through SSH and that the scp command is
available to securely send files to the target server.
Ensure the firewall ports on any routers in the network, as discussed in HP SUM Special
Considerations.
The Symantec End Point Protection product (SEP) blocks HP SUM ability to communicate with remote
targets if the Network Threat Analysis feature is enabled. The only workaround so far is to disable this
feature while HP SUM is in use on the workstation.
 Examine the OpMan.trace, IPScout.trace, OSScout.trace, discagent.trace, and
discmanager.trace files to determine the cause of the failure. These files provide the following
information.
HPSUM Trace files Function provided
OpMan.trace Provides operations trace of the overall installation process.
IPScout.trace
Provides the information on whether the remote target could be contacted
and the type of target found (iLO, server, VC, OA, etc.)
OSScout.trace
Provides the details on the connection setup plus is responsible for
cleaning up after an installation and initiating a reboot, if needed and
selected by the user, on the target system
discagent.trace
Provides the actual details of the execution of the discovery agent on
either the local system during a local installation or the remote target
server. If a discovery tool fails, it is normally reported here and surfaced
as a ―Discovery Failed‖ message.
discmanager.trace
Provides the interaction between the Operations Manager and the remote
discovery client. Any failure in network communications is normally
reported in this file and surfaced as a ―Discovery Failed‖ message.

 OpMan.trace—Provides operations trace of the overall installation process.

 IPScout.trace—Provides the information on whether the remote target could be contacted and
the type of target found (iLO, server, VC, OA, and so on).

179
 Installation failures
1. When remote installations fail, try running HP SUM locally on the failing server if possible. This
removes the network connectivity from the situation and allows more information to be seen
while the installation occurs.
2. The HPSUM remote session logs are saved on the target server. For Windows, these are
located in the C:\Windows\hpsum_<date_time_codex>\HPSumServerW32.log file. For Linux,
these files are located in the /tmp/hpsum_<date_time_codex>HPSumServer.log file.
3. Examine the OpMan.trace, IPScout.trace, OSScout.trace, InstallClient.log, and
InstallManager.log trace files to determine the cause of the failure. These files provide the
following information.
HPSUM Trace files Function provided
OpMan.trace
Provides operations trace of the overall installation process.
IPScout.trace
Provides the information on whether the remote target could be contacted
and the type of target found (iLO, server, VC, OA, etc.)
OSScout.trace
Provides the details on the connection setup plus is responsible for
cleaning up after an installation and initiating a reboot, if needed and
selected by the user, on the target system
InstallClient.log
Provides the actual details of the execution of the individual components
including the command line parameters used to launch the components
and the component return code before it is converted to HPSUM return
codes.
InstallManager.log
Provides the interaction between the Operations Manager and the remote
installation client. Any failure in network communications is normally
reported in this file and surfaced as a ―Installation Failed‖ message for the
affected component and potentially all components that follow the failing
component.

It is possible to look in the OpMan.trace file to see which component was winnowed from the
installation set and which ones were added. Normally, components are winnowed for the following
reasons:
 If they don’t support installation on the given OS
 If the hardware they are designed for is not discovered to be present in the server
 If the component is not for the type of target selected
 If the component does not report itself capable of being deployed to a given target
 If the component cannot be deployed in either the online or offline environment
 If HP SUM detects components that don’t match the online or offline mode
 If the component is for a particular class (p-class/c-class) of BladeSystem enclosure and the
component does not find that class of enclosure

A sample of the output trace in the OpMan.trace is provided in the following example that shows
how to determine if a component is prevented from being shown on the Select Items to Install screen
in HP SUM or is being deployed from the silent, console mode. In the example, the binary image files
0.bin and 1.bin (which represented iLO firmware files), components cp011301.exe and
cp011500.exe and the HP BladeSystem Firmware Update Bundle for Windows represented by
bundle file bp000648.xml are added to the installation set. All the other components are removed for
various reasons.

180
 InstallSet.cpp[212]: Winnow--Adding FileName 0.bin
InstallSet.cpp[212]: Winnow--Adding FileName 1.bin
InstallSet.cpp[222]: Winnow--Removing FileName 2.bin
InstallSet.cpp[212]: Winnow--Adding FileName cp011301.exe
InstallSet.cpp[222]: Winnow--Removing FileName cp011321.exe
InstallSet.cpp[222]: Winnow--Removing FileName cp011489.exe
InstallSet.cpp[222]: Winnow--Removing FileName cp011497.exe
InstallSet.cpp[212]: Winnow--Adding FileName cp011500.exe
InstallSet.cpp[222]: Winnow--Removing FileName cp011504.exe
InstallSet.cpp[222]: Winnow--Removing FileName cp011505.exe
InstallSet.cpp[222]: Winnow--Removing FileName cp011550.exe
InstallSet.cpp[222]: Winnow--Removing FileName cp011560.exe
InstallSet.cpp[242]: Target 0: Added Bundle bp000648.xml

Troubleshooting HP BladeSystem FDT

1. If a failure occurs, use the console keyword at the boot prompt to drop into a debug console.
From here, run ./hpsum –s to manually execute the Blade Blaster.
2. Before using the ISO, validate the MD5 checksum against the value on the download page to
ensure a good image has been downloaded correctly.
3. If more than 64 GB of memory is included in a blade FDT 1.60 and earlier ISOs hang at a
blank screen shortly after the FDT starts to boot. To resolve this issue, use a version of the FDT
later than 1.60, or issue the following command at the Boot: prompt: bdcd mem=16g. Another
workaround is to remove the extra memory until there is less than 64 GB in the server. The
additional memory can be added back to the server after the FDT has completed updating the
firmware.
To debug individual component installations on the FDT, perform the following operations.
1. When the system completes, power on self-test and start to boot the FDT.
A Boot: prompt is shown for approximately 5 seconds.
2. Press any key to stop the countdown.
3. Enter the word console at the prompt.
4. Press Enter.
5. When the FDT boots, copy all files to a RAM drive, and then drop the user at a console
prompt.
6. At the console prompt, manually install a component by entering the component number,
followed by the -s switch, which invokes the silent option as follows:
./CP011301.scexe -s

Some components, such as the Emulex, Brocade, QLogic HBAs, the Tape firmware, and Broadcom
NIC firmware components require additional parameters. Executing these components without the -s
option displays the additional parameters these components require to successfully install in the FDT
boot environment.
Once the component installation is complete, the echo $? command can be provided at the prompt
to find the final return status for the component. In addition, the /var/cpq/Component.log file can
be edited with vi to see the details written to the log during the component installation. Be aware that
the /var/cpq/Component.log file is overwritten each time a component is executed.
More advanced users can insert a USB key into the SUV (Serial, USB, and Video) cable connected to
the front of a given blade. If additional components are placed in the / directory on the USB key,
HPSUM can automatically pick these up. To execute HPSUM, use the ./hpsum -s option as
previously mentioned.

181
 Trouble shooting Log Files for individual smart components
When using an individual smart component to install firmware or software, the log file is written in the
following locations:
 Windows (both firmware and drivers)
%SYSTEMDRIVE%\cpqsystem\log\cpqsetup.log

 Linux:
o Drivers: /var/log/hppldu.log
o Firmware: /var/cpq/Component.log

Note:
All logs are cumulative for Windows (all) and Linux PSP software. Linux
firmware components overwrite the Component.log file each time.

Troubleshooting PowerPIC firmware update errors

The following information comes from the HP Support document ―Customer Advisory c01796365, HP
ProLiant Servers - Error Messages May Be Displayed When Updating the Power Management
Controller Firmware Using Online Flash Components,‖ which is located at
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c01796365.

Error Action

The software is not supported for installation on this system. The SMART component is corrupt.
Unable to load the FIRMWARE.INI file. No firmware is Download the component again from hp.com and reinstall.
found for this system.

This system does not have a Power Management Controller. The server does not support the Power Management
Controller. On certain servers, the Power Management
Controller is optional based on the specific Power Supply
solution that is being used.
Ensure the proper option kit is installed.

The software is installed and up-to-date. The installation The Power Microcontroller firmware is already up-to-date
process does not need to continue; however, you may still and no further update is required.
install the software.

Unable to communicate with the iLO management Ensure that Integrated Lights-Out 2 (iLO 2) is not being
processor! flashed or reset because of a recent firmware upgrade flash
process. Make sure the HP iLO Channel Interface driver is
installed and functioning properly.
You may be able to correct this problem by cycling power.
Unable to communicate with the Power Management
You must physically disconnect all power, not just press the
Controller.
power button. If this is a blade server, you must remove and
reinsert the blade.
You must install the iLO Channel Interface driver to use this
component.

The Power Management Controller on this system does not Certain versions of ProLiant BL460c and ProLiant BL480c
support firmware updates series servers do not support update of the Power
Microcontroller.

Unable to communicate with the Power Management You may be able to correct this problem by cycling power.
Controller. You must physically disconnect all power, not just press the

182
Error Action
The Power Management Controller requires disaster power button. If this is a blade server, you must remove and
recovery. reinsert the blade.
Could not unlock the Power Management Controller! 1. Remove auxiliary power from the system.
Unable to flash the Power Management Controller! On all ProLiant G5 series blades and certain ProLiant
BL460c and ProLiant BL480c series blade, this requires
physically removing the blade from the enclosure or
removing all power from the enclosure.
2. On a ProLiant G6 series blade, use the RESET SERVER
<BAY NUMBER> command from the OA.
Be aware that resetting a bay will reset all blades in the bay
including both servers in a dual server blade configuration.
It may be necessary to reseat and attempt the Power
Management Controller Firmware update process multiple
times before proceeding to the next step.

3. Attempt the Power Management Controller Firmware

update with the /DISASTER-RECOVERY command line
option.
This forces the flash tool to try and recover a Power
Management Controller that has corrupt firmware.

If the previous recovery attempts do not resolve the issue, contact HP Technical Support for further
assistance at http://www.hp.com/support.

Troubleshooting failed iLO2 firmware updates

Follow these steps to recover from a failed firmware update using the HP Drive Key Boot Utility.
1. Copy the iLO 2 offline flash component to your USB drive key.
2. Verify that the iLO 2 security override switch is set to disabled.
3. Boot the USB drive key containing the iLO 2 flash component.
4. To download the HP Drive Key Boot Utility and for information on how to create a boot USB
key, see the HP website at http://www.hp.com/go/support.
5. After the first screen displays, switch to text console by pressing the Ctrl+Alt+F1 keys.
6. Switch to the directory where the flash component is stored by entering cd.
7. Enter /mnt/usb/components/ at the # prompt.
8. Remove the loaded HP Lights-Out driver by entering the following commands:
o /etc/init.d/hp-snmp-agents stop
o /etc/init.d/hp-ilo stop
o /etc/init.d/hpasm stop

9. Run the component by using the --direct option. For example:

./CP00xxxx.scexe ––direct

10. Enter y at the Continue (y/N)? prompt.

11. After programming is successfully completed, set the security override switch to enabled, and
reboot the server.

In some instances, after an iLO or PowerPIC firmware update, a server shows a red X in the OA web
interface, and the server is unable to power on. There are several possible causes of this condition.
The following items list three possible ways to recover from this scenario once it has been confirmed
that all iLO, System ROM, OA, and Power Management Controller firmware is updated.

183
 When a blade is first inserted into an enclosure, the Power Management Controller calculates the
amount of power need to power on the server. This value is then requested from the OA. With Power
Management Controller 0.7 firmware, the value is incorrectly calculated, which causes the request to
the OA to be maxed out. This usually occurs at around 500 watts instead of the normal range of 100-
200 watts for a given blade server. When too many servers request the maxed-out value, the OA
becomes over-allocated and prevents some blades from powering on. Even after the power
management controller is updated, there are instances when the incorrect values in NVRAM for the
blade server persist.
Reset the blade
1. Remove the blade and re-insert it.
2. If this does not work, reset the NVRAM.

Clear the NVRAM

1. Power off blade.
2. Remove blade from enclosure.
3. Open blade cover, locate the Configuration Reset switch, and set it to On.
4. Re-insert blade into enclosure.
5. Allow blade to power up, and wait until it prompts you to reset Configuration Reset switch
to Off.
6. Power off blade again.
7. Remove blade from enclosure.
8. Open blade cover, locate the Configuration Reset switch, and reset it to Off.
9. Re-insert blade into enclosure.
Allow blade to power up and go through initial configuration. At this point, blade can now
be flashed to latest firmware version (and the fans will return to normal state, along with
power allocation to that blade).

Note:
Resetting the configuration causes any RBSU settings to be reset to defaults.
After following this set of instructions, it may be necessary to reset the RBSU
settings after updating the PowerPIC firmware to the latest version.

If clearing the NVRAM does not clear the problem, it may be necessary to reset the iLO.
Reset the iLO
1. Power off blade.
2. Remove blade from enclosure.
3. Open blade cover and put a jumper on the two pins (J102) close to the system maintenance
switch.
4. Re-insert blade into enclosure.
5. Allow blade to power up, and If system powers on and iLO2 is dead, turn power system back
off.
6. Remove blade from enclosure.
7. Open blade cover, and flip the System Maintenance Switch 1 to On.
8. Re-insert blade into enclosure.
9. Allow blade to power up, and start FDT to flash the iLO2 firmware.

184
 10. Power-off the blade after the firmware updates are complete.
11. Remove blade from enclosure.
12. Open blade cover, and flip the System Maintenance Switch 1 to Off.
13. Remove jumper from J102.
14. Re-insert blade into enclosure.
15. Allow blade to power up and go through normal boot process.

Note:
Resetting the iLO causes all iLO settings to reset to defaults. After following
this set of instructions, it is necessary to reset their iLO configuration
settings, after updating the iLO firmware to the latest version if the user has
changed the iLO default settings.

For more information

 Customer Advisory: HP OA—Upgrading Firmware from 1.x to 2.25 (or later) will not be successful.
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?locale=en_US&objectID=c0
1597033

 Link to earlier versions of the OA firmware.

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&
prodTypeId=3709945&prodSeriesId=3808910&swItem=MTX-
c1b90e546c3f476193c43cf0d9&prodNameId=3808911&swEnvOID=4006&swLang=13&taskId
=135&mode=5
 The latest HP SUM User Guide is included in the Firmware CD User’s Guide. To obtain a copy of
this PDF file, see ftp://ftp.hp.com/pub/c-products/servers/management/smartstart/ and
select the latest version of the FWCDUsersGuidex.xx.pdf.
 The OpenSSH for Windows files can be obtained from
http://softlayer.dl.sourceforge.net/project/sshwindows/OpenSSH%20for%20Windows%20-
%20Release/3.8p1-1%2020040709%20Build/setupssh381-20040709.zip
 A web server:
o Microsoft Windows Internet Information Server (obtained from Windows Server 2003/2008
installation CDs)
or
o Apache web server located at:
http://www.ecoficial.com/apachemirror/httpd/binaries/win32/apache_2.2.13-win32-x86-
openssl-0.9.8k.msi

o HP BladeSystem Firmware Update Bundles for Windows or Linux

o Windows:
ftp://ftp.hp.com/pub/softlib2/software1/supportpack-windows/p1116845569\
(Choose highest numbered directory for the latest version)

185
 o Linux:
ftp://ftp.hp.com/pub/softlib2/software1/supportpack-linux/p1418640128
(Choose highest numbered directory for the latest version)

 HP BladeSystem FDT ISO.

ftp://ftp.hp.com/pub/softlib2/software1/cd/p1255591055
Choose highest numbered directory for the latest version)

 The HP Integrated Lights-Out Management Processor Scripting and Command-Line Resource Guide
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00294268/c00294268.pdf

 The HP BladeSystem Onboard Administrator User’s Guide

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00705292/c00705292.pdf

 Customer Advisory: (Revision) ProLiant Servers - Servers with Equal to or Greater Than 64 GB of
Memory May Stop Responding While Booting SmartStart 8.25 (or Earlier), Firmware Maintenance
CD 8.50 (or Earlier), or HP BladeSystem FDT CD 1.60

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=
c01554945&jumpid=reg_R1002_USEN

 PowerPIC firmware errors

Customer Advisory c01796365, ―HP ProLiant Servers - Error Messages May Be Displayed When
Updating the Power Management Controller Firmware Using Online Flash Components‖ at:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c01796365
 About supported hardware, software, and firmware versions, see the HP BladeSystem Compatibility
Chart at:
http://www.hp.com/go/bladesystemupdates/

 About the latest management software and driver updates and known issues, see the HP
BladeSystem Chart Release Notes at:
http://h18004.www1.hp.com/products/blades/components/matrix/

 For best practices, see the HP BladeSystem Chart Getting Started Guide
 http://h18004.www1.hp.com/products/blades/components/matrix/

186
Glossary
Acronyms and abbreviations
Term Definition

CLI command-line interface

EVA Enterprise Virtual Array

FC Fibre Channel

FDT Firmware Deployment Tool

GUI graphical user interface

HBA host bus adapter

HPONCFG HP Lights-Out Online Configuration Utility

HP SIM HP Systems Insight Management

HP SUM HP Smart Update Manager

IIS Microsoft Internet Information Server

iLO 2 Integrated Lights Out 2

ISO International Organization for Standardization

KVM keyboard, video, and mouse

MDS600 HP StorageWorks 600 Modular Disk System

NIC network interface controller

OA Onboard Administrator

OS operating system

POST Power-On Self Test

PSP ProLiant Support Pack

RDP Remote Deployment Program

RIBCL Remote Insight Board Command Language

ROM read-only memory

SAS Serial attached SCSI

SATA Serial ATA

SOAP Simple Object Access Protocol

UID unit identification

USB universal serial bus

VC Virtual Connect

VCM Virtual Connect Manager

VCEM Virtual Connect Enterprise Manager

VCSU Virtual Connect Support Utility

VCRM Version Control Repository Manager

VM virtual machine

VSM Virtual SAS Manager

187
Technology for better business outcomes
© Copyright 2010 Hewlett-Packard Development Company, L.P. The information
contained herein is subject to change without notice. The only warranties for HP
products and services are set forth in the express warranty statements
accompanying such products and services. Nothing herein should be construed as
constituting an additional warranty. HP shall not be liable for technical or editorial
errors or omissions contained herein.

Microsoft, Microsoft Windows, Windows XP, and Windows Vista are U.S.
registered trademarks of Microsoft Corporation.

613178-001, March 2010