Using HP Smart Update Manager With HP Integrity Servers: Capabilities, Best Practices, and Troubleshooting

Technical white paper
Using HP Smart Update Manager with HP

Integrity Servers
Capabilities, Best Practices, and Troubleshooting
Table of contents
Overview
High-level Summary
Overall Firmware Update Flow
3
3
3
Update Capabilities
HP Integrity Servers Running HP-UX
HP Integrity Servers Running
OpenVMS or NonStop
Mixed HP ProLiant and Integrity
Environments
4
5
5
5
Best Practices
Network Connectivity
Enclosure Level Updates
Server Level Updates
Enterprise Level Updates / HP
Systems Insight Manager
Activating Firmware Updates
6
6
8
15
Conclusion
21
For more information
21
Call to action
21
Glossary
21
New terms in HP SUM 6.0.0 and later
22
Appendix A: Troubleshooting
Failed to Download Component /
HTTP Access Issue
Pending System Firmware Update
Driver Version Dependency Failure
23
19
20
23
24
29
Appendix B: Understanding the

Firmware Download Pages
Finding the Correct Firmware to
Download
c-Class Blades
Rack-mount Servers
Superdome 2 Servers
Files to Download
30
30
31
32
32
33
Overview
HP Smart Update Manager (HP SUM) is a versatile tool that allows you to update one or more systems and
the devices within those systems at a single time. This paper describes the many choices available using this
flexible tool by providing a list of update capabilities and best practices for different situations, with a focus
on HP Integrity servers.
Disclaimer: The suggested best practices in this document are for common configurations. HP support and
customers may work together with specific installation details to provide different advice that is better for
those situations.
This document references functionality provided in HP SUM 5.3.0 and later for HP Integrity i2 and later
systems. HP SUM does not support any updates on older HP Integrity servers. Basic HP SUM usage and
troubleshooting is similar for older HP SUM releases, but some functions might not be available or might act
slightly differently.
High-level Summary
Recent HP SUM enhancements allow you to update I/O card firmware on HP Integrity servers via HP-UX OS
installations.
HP SUM should be run from a system with full network connectivity to both management and OS networks.
Use HP Systems Insight Manager (HP SIM) to update more than 50 servers or devices in a single management session.
Overall Firmware Update Flow
Update Capabilities
HP SUM can help an administrator manage enclosure, platform and I/O card firmware on HP Integrity
servers. Updates are performed through management interfaces and the operating system. Because the
operating system is used for some updates, the specific HP SUM update capabilities might vary according to
the operating system running on the servers.
Rack-mount servers
c-Class enclosures
Superdome 2 enclosures
HP-UX
Platform FW (iLO, SFW) via iLO

I/O card FW via OS
Enclosure FW (OA, VC) via OA, VC

I/O card FW via OS
Enclosure FW (complex) via OA

Platform FW (nPar) via OA
I/O card FW via OS
OpenVMS or NonStop

Enclosure FW (OA, VC) via OA,
VC

n/a
HP Integrity Servers Running HP-UX

HP SUM can interact with both management interfaces and HP-UX to provide enclosure, platform and I/O
card firmware updates. To update all firmware in the same session, you must run HP SUM from a system
that has network access to both the management and OS interfaces.
HP Integrity Servers Running OpenVMS or NonStop

HP SUM can interact only with the management interface on HP Integrity systems running other OpenVMS or
NonStop operating systems. Therefore, it can only provide enclosure and platform firmware updates. I/O
card firmware must be manually updated using the traditional EFI packages method on these systems.
Mixed HP ProLiant and Integrity Environments
Both HP ProLiant and Integrity servers can be updated by the same version of HP SUM software, and can be done in the
same HP SUM session concurrently. There are extra steps to be aware of when the servers are in the same enclosure.
If you are updating an environment with both HP ProLiant and Integrity servers in the same enclosure, do the following:
Review the support matrix. Be sure to use OA and VC versions supported by both HP ProLiant and Integrity servers.
For more information, see the HP BladeSystem Release Sets for Mixed ProLiant and Integrity website at:
h18004.www1.hp.com/products/servers/firmware/mixed-release-sets.html
Download the latest HP Service Pack for ProLiant (SPP) and HP Integrity server bundles.
Unzip the HP SPP and Integrity bundles into separate directories.
Run HP SUM from the latest bundle. It must be HP SUM 5.0.0 or later to support both HP ProLiant and Integrity.
In HP SUM, add the separate directories as separate repositories on the Source Selections page (HP SUM 5.3.5) or add
the directories as baselines on the Baseline Library screen (HP SUM 6.0.0 and later)
Perform your updates.
Best Practices
More detailed documents on HP SUM best practices, including planning and implementing guides
encompassing HP Integrity and ProLiant servers, are provided in the HP SUM Information Library at
www.hp.com/go/hpsum/documentation.
This document includes additional details on HP Integrity specific issues.
Network Connectivity
HP Integrity servers have both management network and production interfaces. Usually these are kept on
separate subnets within an installation. To perform full remote administration of the server, access is
required to both networks.
There are three general scenarios to manage this connectivity issue:
1) Keep the networks completely isolated, and manage management and OS tasks separately.
2) Enable routing between the two networks by enabling a system on either network to access the
other and do simultaneous management and OS tasks.
3) Block routing between networks, but allow a third network, or possibly just specific servers, access
to route to both networks. This allows simultaneous management and OS tasks to be completed,
but from specific locations. This option provides network isolation, but also allows full remote
administration.
Management and production networks both reachable

You can use HP SUM in any of the scenarios listed previously, but the second two scenarios allow taking
advantage of the most functionality. When HP SUM can access and update both networks at once, it can do
dependency checking between OS and management revisions on the same server. HP SUM can also usually
be used to require only a single reboot to activate both types of updates, which reduces overall downtime.
Note: Two steps are still recommended when updating an entire c-Class enclosure including the OA. In those
cases, OA, VC and iLO firmware updates should be done in one step, and then HP-UX I/O firmware updates
should be done.
Management and production networks isolated

If the networks are isolated, you must run HP SUM twice, once from a system on the management network
and again from a system connected to the OS network. It is important for you to manually check any
dependencies and reboot requirements between the two installations.
Enclosure Level Updates

When an entire enclosure is available for updates, HP SUM can be used to update the entire enclosure,
platform and I/O card firmware. It is recommended to update Superdome 2, OA, VC and iLO firmware in one
HP SUM step and then update I/O card firmware next.
Superdome 2 Enclosure Update Procedure

HP SUM 5.3.5 Instructions
1) Start with partitions powered on and running HP-UX.
2) Select the correct repositories from which to pull updates.
o
This could be a single HP Integrity bundle, multiple bundles for different server types in
different directories or from Check for latest updates from hp.com.
3) Enter IP addresses and root credentials for all HP-UX OS instances.

o
The associated OA targets will be found.
4) Enter OA IP addresses (if needed) and credentials.

o
All partitions are discovered, although this is not visible until the Review/Install screen.
Partitions are managed as part of the single enclosure target.
5) Continue to the Review/Install Updates screen.

6) Clear any selected targets if you are updating only some of the enclosures.
7) Run the Updates to be Installed report and review.
o
This report provides a full view of all the recommended updates that HP SUM would apply
to the selected servers when you continue. Select/clear selected targets, force
downgrades or rewrites, if needed, and re-run the report to see the changes.
8) Set reboot options.

o
Superdome 2 nPartition reboots must be enabled by choosing the Select Components

and then Select Devices links.
Allowing HP SUM to sequence the reboot will help minimize the downtime by immediately
issuing shutdown and power on when needed. Generally HP SUM can coordinate all the
updates such that only a single reboot is required.
9) Start or schedule the update.

o
The updates can be set to be performed at a later time using the Schedule Update
button. After setting the schedule, click the Install button and leave the HP SUM
application running.
10) After HP SUM completes and systems have finished rebooting, you can continue with other updates
not controlled by HP SUM.
o
On non-HPUX systems, EFI packages can be used for updating I/O cards.
HP-UX software and driver patches can be installed.
HP SUM 6.0.0 and later Instructions

1) Start with partitions powered on and running HP-UX.
2) Start HP SUM from the Superdome 2 bundle location.
o
The current directory will be added as a baseline automatically.
3) Go to the Nodes page and select Add Node.

o
Enter the IP address and administrator credentials for the active OA.
4) After the node completes validating the system type, select Inventory from the Action menu.
o
Select the current directory as the Baseline to apply to the node.
All partitions and FW versions within the enclosure will be discovered and displayed on the
node page.
5) After Inventory completes, select Reports from the Action menu and run the Installable Details
report and review.
o
to the selected node when you continue.
6) After confirming the updates to be performed, select Deploy from the Action menu.
o
If you will be also updating I/O firmware online, leave the npartition reboot turned off. A
single reboot can be done after I/O firmware update to activate both updates.
If you will not be updating any I/O firmware online, enable reboot for each npartition so
that the firmware update can be fully activated.
If you want to update only a subset of the enclosure, such as only one npartition, you can
make those changes and then click the Analyze button to have HP SUM validate the
selection.
Once any changes are made, click the Deploy button to start the update process.
Note: Superdome 2 enclosure updates may take up to 90 minutes or more depending on

the configuration and the update.
7) While the OA update is in progress, you can add each of the HP-UX nodes using Add Node.
o
Enter the IP address or DNS name and root credentials for each HP-UX instance.
8) Run Inventory on each HP-UX node

o
Select the current directory for the Baseline to be applied to the node.
report on the HP-UX nodes and review.
o
10
10) After HP SUM finishes the OA node update, start Deploy on each HP-UX node.
o
Be sure to set the Reboot option to Always in order to also activate the npartition updates
as well as any I/O FW updates that may require a reboot.
11) After HP SUM completes updates on each node and the systems have finished rebooting, you can
continue with other updates not controlled by HP SUM.
o
On non-HP-UX systems, EFI packages can be used for updating I/O cards.
c-Class Enclosure Update Procedure

o
This could be a single HP Integrity bundle, multiple bundles for different server types in
different directories or from Check for latest updates from hp.com.
If this is a mixed HP Integrity and ProLiant enclosure, you can also add HP ProLiant server
firmware and software by adding an HP SPP as an additional repository. HP ProLiant
updates will also be found if you choose Check for latest updates from hp.com.
2) Enter the Active OA IP address and credentials for each enclosure.

o
All installed blades and Virtual Connect are discovered as associated targets.
3) Enter credentials for Virtual Connect, if installed.

o
Even if the Virtual Connect firmware is not going to be updated, HP SUM can discover the
VC firmware version and use that information for dependency checking purposes. The VC
target can be deselected after discovery and the information will still be used.

o

o
Reboot options for targets can be set using the global Reboot Options button, or
individually per target on the Select Components screen.
issuing shutdown and power on when needed.
11
9) After HP SUM completes, exit HP SUM and verify all systems have finished rebooting and HP-UX is
running.
10) Start HP SUM again and enter the IP address and root credentials for each HP-UX instance.
o

o
Reboot options for targets can be set using the global Reboot Options button, or
individually per target on the Select Components screen.
issuing shutdown and power on when needed.

o
16) After HP SUM completes and systems have finished rebooting, you can continue with other updates
not controlled by HP SUM.
12

1) Start with systems powered on and running HP-UX.
2) Start HP SUM from the Integrity platform bundle location.
o
If you have a mix of i2 and i4 blades, start HP SUM from one Integrity bundle location and
then choose Add Baseline to add the other directory location.

o
Enter IP address and administrator credentials for the active OA.
o
Keep the default checkbox to find associated nodes. This will automatically find and add VC
and iLO nodes in the enclosure.
5) After inventory completes on the OA, each iLO node will be added and inventory will continue on
those nodes as well.
o
If you have multiple blade types, go to the iLO nodes and set the correct Baseline for each
node type.
6) If you have VC installed, it will be waiting for credentials before it can start Inventory.
o
Go to the VC node screen and click Edit to enter the VC credentials.
Then start Inventory on the node.
7) After Inventory completes on all the nodes, select Reports from the Action menu and run the
Installable Details report and review.
o
You can select multiple nodes to run the report on at once using ctrl-click on the node
names in the list on the left of the nodes page and then using the Generate Report button.
8) Set Reboot options on iLO nodes

o
Note: in HP SUM 6.0.0 and later the reboot options for each iLO node must be set
individually
On each iLO node page, select Deploy, then enable the reboot to activate using the drop
down box and click Analyze to save the setting.
Then click Cancel. (HP SUM begins deployment from the OA, which will then sequence
updates automatically.)
13
9) After confirming the updates to be performed, select Deploy from the Action menu on the OA
node.
o
Associated nodes will be listed to also be updated. Uncheck any that you do not want to
update at this time.
Note: Updates on nodes will be sequenced. The OA node will update first and then VC and
iLO nodes.
If any changes are made, click the Analyze button to have HP SUM confirm the changes.
Click the Deploy button to start the update process.
10) After OA, VC and iLO nodes have finished updating, add each of the HP-UX nodes using Add Node.
o
Enter the IP address or DNS name and root credentials for each HP-UX instance.
11) Run Inventory on each HP-UX node

o
report on the HP-UX nodes and review.
o
13) Start Deploy on each HP-UX node.

o
Be sure to set the Reboot option to If Needed or Always in order to fully activate the I/O
FW updates that may require a reboot.
14) After HP SUM completes updates on each node and the systems have finished rebooting, you can
continue with other updates not controlled by HP SUM.
14
Server Level Updates

When a single server is being updated, you can use HP SUM to update platform and I/O card firmware.
For rack-mount server or c-Class blade
1) Start with server powered on and running HP-UX.
o
In this case, it will usually be the current default directory with the server firmware bundle
where HP SUM is running from, but you can also choose to get updates from another
directory or from Check for latest updates from hp.com.
3) Enter the IP address and root credentials for the HP-UX OS instance.
o
The associated iLO target (and OA if it is a blade) targets will be found.
4) Enter credentials for the associated iLO target.

o
to the selected servers once you continue. Select/clear selected targets, force

o
If reboot is enabled, HP SUM will coordinate reboot between the iLO and OS installations so
only one reboot is necessary. The global Reboot Options button can be used to set both at
once.

o
The update can be set to be performed at a later time using the Schedule Update button.
After setting the schedule, click the Install button and leave the HP SUM application
running.
9) After HP SUM completes and the system has finished rebooting you can continue with other
updates not controlled by HP SUM.
o
15

1) Start with systems powered on and running HP-UX.
2) Start HP SUM from the Integrity platform bundle location.
o

o
Enter IP address and administrator credentials for the system iLO.
o
5) After Inventory completes on all the nodes, select Reports from the Action menu and run the
Installable Details report and review.
o
6) After confirming the updates to be performed, select Deploy from the Action menu on the iLO
node.
o
Set Reboot option to If Needed or Always using the drop down menu.
Click the Analyze button to have HP SUM confirm the changes.
Click the Deploy button to start the update process.
7) After the iLO node finishes updating add the HP-UX node using Add Node.
o
Enter the IP address or DNS name and root credentials for the HP-UX instance.
8) Run Inventory on the HP-UX node

o
9) After Inventory completes, select Reports from the Action menu and run the Updates to be
Installed report on the HP-UX nodes and review.
o
10) Start Deploy on the HP-UX node.

o
Be sure to set the Reboot option to If Needed or Always in order to fully activate any I/O
FW updates that may require a reboot.
11) After HP SUM completes updates on the HP-UX node and the systems have finished rebooting, you
can continue with other updates not controlled by HP SUM.
o
16
For single Superdome 2 nPartition

You can update one or more nPartitions or unassigned blades in a Superdome enclosure at a time by HP
SUM. HP SUM defaults to updating the entire enclosure, but you can manually select which subset to update.
For example, you can use this procedure for configurations with two nPartitions providing redundant
functionality and only one can be updated at a time.
1) Start with the nPartition powered on and running HP-UX.
o
In this case, it will usually be the current default directory with the Superdome 2 server
firmware bundle where HP SUM is running from, but you can also choose to get updates
from another directory or from Check for latest updates from hp.com.
3) Enter the IP address and root credentials for the HP-UX OS instance.
o
The associated OA target will be found.
4) Enter credentials for the associated OA target.

o
nPartition platform firmware update is controlled through the Superdome 2 OA. HP SUM
will discover all of the partitions, but HP SUM allows selecting only a single nPartition for
update if you want.

6) On the Superdome 2 target, select only the single nPartition for update and set reboot options.
o
Choose the Select Components, and then View Devices links. An inventory of the
Superdome 2 system will be visible, with all nPartitions, blades and complex visible. Clear
the All check box and select only the one check box next to the nPartition you want to
update.
On the same screen, choose whether to have HP SUM reboot the nPartition after update by
selecting the Reboot to Activate check box next to the nPartition.
Click the OK button and HP SUM will re-validate the choices made. If there are any
warnings or errors that would occur due to this update, they will be displayed as
dependency failures and the details will be available on this screen.

o
to the selected servers once you continue. Select/clear selected targets, force
17

o
The update can be set to be performed at a later time using the Schedule Update button.
After setting the schedule, click the Install button and leave the HP SUM application
running.
9) After HP SUM completes and the nPartition has finished rebooting you can continue with other
updates not controlled by HP SUM.
o

Follow the Superdome 2 instructions above, but at step 6 during Deploy, open the Select Devices section of
the Deploy page and choose an Partition/Blades from the Update Type menu. Then select the individual
partition(s) that you want to update. Click Analysis to save the settings and then continue with Deploy.
18
Updates Without Network Access

If no remote network access to run HP SUM is available in a specific situation then I/O firmware updates can
still be applied to HP-UX systems manually using the components in HP SUM Integrity server bundles. The
firmware smart components can be copied to the HP-UX system and individually executed.
1) Download the HP SUM Integrity bundle for Linux HP SUM to the HP-UX server
2) Unzip and untar the HP SUM bundle
3) Execute the smart components, which are named CPnnnnnn.scexe individually.
Note: Use the h option to list additional execution options.
Enterprise Level Updates / HP Systems Insight Manager
The number of systems that HP SUM can update at a time on its own depends on the server configuration
that HP SUM is running on. Processor power, memory and network bandwidth can contribute to the
limitation. A general rule of thumb would be to start testing with a couple enclosures or about 30 40
targets and increase the number of targets if performance was acceptable.
When a larger number of systems need to be updated, HP SIM 7.0 and later can help coordinate the updates.
HP SIM uses the embedded version of HP SUM to sequence through groups of servers, calling HP SUM
multiple times to perform the updates. This allows you to have one point of control, instead of running HP
SUM individually multiple times.
19
Activating Firmware Updates

Some updates take effect immediately, some require an OS reset to activate and some require a server
power cycle to activate. HP SUM understands the requirements of each update and can include the
appropriate commands in the update sequence if enabled. Enabling HP SUM to perform the necessary
commands will result in them being sequenced as close as possible to the updates, reducing overall
downtime. Therefore, it is recommended that when performing an update, you schedule the system to
expect a reboot at the end of the firmware update process. In some cases, leaving a system with nonactivated firmware can lead to the inability to reboot until the firmware is activated.
Firmware Type
Activation Required
Notes
None effective
immediately
iLO automatically resets itself at the end of

the update without affecting server
operation.
Onboard Administrator
(OA)
None effective
immediately
Virtual Connect (VC)
None effective
immediately
In redundant OA configurations, the standby

OA is programmed and reset, and then it
takes over as Active. Then the other OA is
programmed and reset, and resumes the
Active roll. In single OA configurations, the
OA is programmed and resets. These updates
do not affect server operations.
Integrated Lights Out

(iLO)
System FW (SFW)
Superdome 2 Complex FW
Superdome 2 nPartition
FW
I/O card FW
Power cycle (DC)
None effective
immediately
OS reboot
Varies per vendor/card

OS reboot
None effective
immediately
20
Firmware is staged in iLO memory as

Pending until system power is turned off.
Then programming occurs and takes
approximately 6 minutes, during which time
power cannot be turned back on. Leaving
SFW in Pending might prevent system reset
or boot, so its recommended to activate as
soon as possible.
Virtual connect firmware is downloaded to

all interconnect modules at once and then
each module is reset in sequence.
Complex FW, which includes OA FW, is

programmed and the affected devices reset
to activate if needed without affecting server
operation.
nPartition FW is programmed during the
update process, but the new version is not
read and used by the OS until the next OS
reboot.
Some I/O cards support immediate

activation of new firmware; some cards
program the new firmware, but do not read
and use it until the next OS reboot; and some
cards actually have firmware programmed
during the next reboot.
Conclusion
HP SUM is a versatile and flexible tool that can manage enclosure, platform and I/O card firmware on HP
Integrity servers. Updating single servers, enclosures or multiple enclosures is possible in a single HP SUM
session. Using HP SUM in the correct manner can help reduce downtime due to firmware upgrades, and
automate the process of upgrading firmware, therefore reducing the complexity of this critical task.
For more information
To read more about HP SUM, go to: hp.com/go/hpsum
Call to action
For detailed support for maintaining firmware on your HP Integrity or other HP servers, please contact your
HP representative or visit: hp.com/go/Integrity or hp.com/go/support.
Glossary
Term
Definition
EFI
Extensible Firmware Interface

A pre-boot environment
Enclosure FW
Firmware for enclosure wide resources, management or I/O

Onboard Administrator FW and Virtual Connect FW for c-Class enclosures
Complex FW for Superdome 2 enclosures
HP SIM
HP Systems Insight Manager
HP SUM
HP Smart Update Manager
I/O Card FW
Firmware for add in and embedded I/O cards
iLO
Integrated Lights Out
OA
Onboard Administrator
OS
Operating System
Platform FW
Firmware for the base compute system and embedded management interface:
System FW and iLO on rx2800 i2/i4 and BL8x0c i2/i4
nPartition FW on Superdome 2
SFW
System Firmware
SPP
Service Pack for ProLiant
VC
Virtual Connect
21
New terms in HP SUM 6.0.0 and later

HP SUM 5.x
Repository
HP SUM 6.x
Baseline
Target
Discovery
Node
Scouting
Discovery
Inventory
N/A
N/A
N/A
N/A
Location
Guided
Update
Mode
Analyze
Install
Deploy
22
Description
A collection of components for use in updating a node. For example, HP
SPP or a custom baseline.
Hardware you want to update.
The process where HP SUM determines the contents of a node or
baseline.
The process where HP SUM determines the contents of a node or
baseline.
Network directory for baseline updates.
An automated or wizard-style method to update the local node.
You can run HP SUM in either interactive or non-interactive mode.
The process where HP SUM verifies all dependencies are met before
beginning deployment.
The process where HP SUM begins the update process.
Appendix A: Troubleshooting
Failed to Download Component / HTTP Access Issue
HP SUM requires a bi-directional link to the target to complete the firmware update process. HP SUM may be
able to perform discovery of the target by direct queries, but most installations require that the target
request the firmware binaries for update. HP SUM launches a local HTTP server on the system running HP
SUM to provide that firmware retrieval capability. This incoming HTTP request to the server running HP SUM
might be blocked by firewall software on the server running HP SUM or by firewalls in the network. When
blocked by a firewall, HP SUM will generally start the firmware update, but then fail. Usually the log will
indicate some issue with HTTP retrieval of the firmware binary.
If this type of failure occurs, either temporarily disable the firewall or add a rule to allow incoming HTTP.
Many firewall software vendors have a learning mode that can be used to help enable this rule by letting
the software know that this is expected and allowed behavior. See the HP SUM Release Notes
(www.hp.com/support/HP_SUM_RN_en) for specific methods for some vendors.
Example screen with error from HP SUM 6.0.0 and later:
23
Pending System Firmware Update

On HP Integrity rack-mount and c-Class systems, System Firmware (SFW) is part of the platform firmware
that is updated via the iLO management interface. If the system is powered on at the time of the update,
SFW cannot be immediately programmed into flash because it is in use. iLO stages the SFW image and will
perform the programming once the system is powered down. At that time, the update will take about 6
minutes and then the system can be powered back up again.
Example screen with reboot option enabled in HP SUM 6.0.0 and later:
24
When HP SUM performs a system update that includes SFW, it provides the option of allowing HP SUM to
sequence through this sequence. HP SUM will issue a graceful OS shutdown request, monitor the SFW
programming, and then issue a power on request once it is done. If the HP SUM install is done without
selecting this option, and you do not immediately perform the power cycle manually, the SFW is said to be in
a pending state. iLO will not allow another update to proceed until that existing pending SFW update is
either activated or cancelled.
Example screen with pending firmware from HP SUM 6.0.0 and later:
25
If a subsequent HP SUM session is started against the same server, HP SUM will detect that there is a
pending SFW update on the system and will provide options for handling the situation.
HP SUM can leave the system to be manually powered down at a future date. That target will not be able
to continue with any platform level updates by HP SUM.
HP SUM can activate the pending SFW. If selected, HP SUM will walk through the sequence of powering
down the system and making sure the SFW update completes successfully. The target will then be
available to continue with any new platform level updates in the same HP SUM session.
HP SUM can cancel the pending SFW. If selected, HP SUM will issue a reset command to iLO, which will
cancel the pending SFW, while keeping the OS still booted. The target will then be available to continue
with any new platform level updates in the same HP SUM session.
Note: Because iLO and SFW are meant to be installed in pairs, cancelling just the SFW update might leave
the system in an unstable state at the next boot time. The cancel option is not recommended unless you
are about to perform a new full platform firmware install and update iLO and SFW to a new recipe.
Note: On Superdome 2 nPartitions, it is possible to install but not activate partition firmware, but this is not
the same issue. On Superdome 2, additional updates can be applied even when partition firmware is pending
activation.
26
Manually Managing Pending System Firmware

To manually check for pending SFW, use the iLO GUI or CLI.
From the iLO GUI, select the Status Summary menu, and then the FW Revisions tab:
From the iLO CLI command menu, issue the sr command. Any pending SFW will be shown.
27
A pending SFW state may be activated by powering down the server. This does not mean removing A/C
power, but instead, it means removing main DC power to the main server, while the standby power to iLO
remains on. This can be done in several ways:
From iLO CLI command menu
pc off
From iLO GUI, power management

tab
From HP-UX
shutdown h
Note: shutdown r and reboot do NOT
power down the server. These commands
might only result in HP-UX stopping, but the
firmware will not be activated. The systems
may not reboot until power is shutdown via
the iLO at that point.
If you must to manually cancel the pending SFW update, cancel the update via the iLO CLI command menu
using the fw cancel command. Note: This should only be done under extenuating circumstances because it
might leave the system with incompatible iLO and SFW images. A full platform firmware update should be
immediately performed.
28
Driver Version Dependency Failure

To install I/O card firmware on HP-UX, the firmware components require a minimum driver version. If the
driver is not at the correct minimum, a dependency failure error message will appear in the target status
area. Clicking the dependency failure link will bring up a description of the error including what the expected
minimum version is. HP SUM cannot continue to update I/O cards supported by that smart component until
the driver is updated manually. HP SUM cannot automatically update drivers to meet the minimum
requirements.
29
Appendix B: Understanding the Firmware Download Pages

Finding the Correct Firmware to Download
HP SUM Integrity bundles are released to hp.com for each server family. To find the correct page with
available firmware bundles for a server:
1) Start at: www.hp.com.
2) Click: Support and Drivers.
3) Click: Drivers and Software.
4) A search box appears that allows you to enter the server model number, similar to the screen shot
below.
5) After entering the model number and clicking Search you are either taken directly to the server
page, or presented with a list of possible matches or variations on the server model.
6) If you are presented a list of options, click the one that matches your server. In general, all of the
options for a server family will lead to the same firmware bundle options.
7) The next page that is presented generally shows a list of operating systems. For firmware updates,
click Cross operating system (BIOS, Firmware, Diagnostics, etc).
8) A list of available downloads, including HP SUM firmware bundles appears. The list of available
options varies between server models. The specific bundle options are explained in sections below
under each general type of server.
Note: In all cases, each firmware bundle is listed once with files to run from a Windows management
system and once with files to run from a Linux management system. Both versions of the bundle will
include the same enclosure, platform and I/O firmware (as appropriate). Choose the one to download
that matches the server you will run HP SUM from. Either can be used to update the remote HP Integrity
servers in the same fashion.
30
c-Class Blades
There are 3 types of HP SUM firmware bundles provided for HP Integrity c-Class blades, under two different
headings:
Under Firmware Bundle
1) CloudSystem Matrix Firmware bundles
These bundles include firmware for enclosures: Onboard Administrator, Virtual
Connect and HP Integrity Blades with specific versions that match the CloudSystem
Matrix version. The bundles include filtering information so HP SUM can determine if
the target enclosure is set to the matching CloudSystem Matrix version.
2) General bundles with full enclosure

These bundles include firmware for enclosures: Onboard Administrator, Virtual Connect
and HP Integrity Blades. I/O card firmware for online HP-UX updates will be included in a
rolling fashion as new versions of firmware bundles are released. The firmware versions in
these bundles represent an approved and tested recipe.
Under Firmware System

3) HP Integrity server only bundles
These bundles include just the firmware for Integrity Blades and mezzanine I/O cards. They
do not include an additional enclosure firmware. These are made available to ease
deployment in some cases where special versions of enclosure firmware are needed that
are different from the recipe provided in the general bundles. These might be useful for a
mixed-environment with HP ProLiant blades, older CloudSystem Matrix revisions that do
not have a specific bundle, or other situations.
31
Rack-mount Servers
There is only one type of HP SUM firmware bundle provided for HP Integrity rack-mount servers, under the
Firmware System heading.
Bundles under this heading include firmware for just the server. Firmware for HP I/O cards that are
approved for use in the server will be included in a rolling fashion as new versions of firmware bundles are
released.
Superdome 2 Servers
There is only one type of HP SUM firmware bundle provided for Superdome 2 servers, under the Firmware
Bundle heading.
Bundles under this heading include firmware for just the server. Firmware for HP I/O cards that are
approved for use in Superdome 2 IO expansion cabinets will be included in a rolling fashion as new versions
of firmware bundles are released.
32
Files to Download
Underneath each bundle, there might be two or three files listed.
1) The main firmware bundle.
This will be the .exe or .tar.gz file, which is the main firmware bundle.
This is the only file that is required to be downloaded.
Once downloaded and optionally verified:
On Windows: execute the .exe file as you would any program and you will be
presented with an option to extract the files to a directory.
On Linux: extract the tar.gz file using tar xvf <filename> or a Linux graphical archive
management utility.
2) The MD5 checksum file
This file can be used to validate the integrity of the main downloaded bundle using an MD5
check program. It can be used by a MD5 checksum validation tool (such as md5sum on Linux) to
verify the downloaded firmware image is the one expected and there was no corruption during
the download.
3) [possibly] A bundle contents file
This file is not needed and is being removed from download pages as soon as possible.
33
Get connected
hp.com/go/getconnected
Current HP driver, support, and security alerts
delivered directly to your desktop
Copyright 2013 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.
Trademark acknowledgments, if needed.
718525-003, Edition 1, Created September 2013
34

Using HP Smart Update Manager With HP Integrity Servers: Capabilities, Best Practices, and Troubleshooting

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Using HP Smart Update Manager With HP Integrity Servers: Capabilities, Best Practices, and Troubleshooting

Uploaded by

Copyright:

Available Formats

Technical white paper

Using HP Smart Update Manager with HP

For more information

New terms in HP SUM 6.0.0 and later

Appendix B: Understanding the

Platform FW (iLO, SFW) via iLO

Enclosure FW (OA, VC) via OA, VC

Enclosure FW (complex) via OA

Platform FW (iLO, SFW) via iLO

Platform FW (iLO, SFW) via iLO

HP Integrity Servers Running HP-UX

HP Integrity Servers Running OpenVMS or NonStop

Perform your updates.

Management and production networks both reachable

Management and production networks isolated

Enclosure Level Updates

Superdome 2 Enclosure Update Procedure

3) Enter IP addresses and root credentials for all HP-UX OS instances.

The associated OA targets will be found.

4) Enter OA IP addresses (if needed) and credentials.

5) Continue to the Review/Install Updates screen.

8) Set reboot options.

Superdome 2 nPartition reboots must be enabled by choosing the Select Components

9) Start or schedule the update.

HP-UX software and driver patches can be installed.

HP SUM 6.0.0 and later Instructions

The current directory will be added as a baseline automatically.

3) Go to the Nodes page and select Add Node.

Select the current directory as the Baseline to apply to the node.

Note: Superdome 2 enclosure updates may take up to 90 minutes or more depending on

8) Run Inventory on each HP-UX node

HP-UX software and driver patches can be installed.

c-Class Enclosure Update Procedure

2) Enter the Active OA IP address and credentials for each enclosure.

3) Enter credentials for Virtual Connect, if installed.

4) Continue to the Review/Install Updates screen.

7) Set reboot options.

8) Start or schedule the update.

14) Set reboot options.

15) Start or schedule the update.

HP-UX software and driver patches can be installed.

HP SUM 6.0.0 and later Instructions

The current directory will be added as a baseline automatically.

3) Go to the Nodes page and select Add Node.

Enter IP address and administrator credentials for the active OA.

Select the current directory as the Baseline to apply to the node.

Go to the VC node screen and click Edit to enter the VC credentials.

Then start Inventory on the node.

8) Set Reboot options on iLO nodes

Click the Deploy button to start the update process.

11) Run Inventory on each HP-UX node

13) Start Deploy on each HP-UX node.

HP-UX software and driver patches can be installed.

Server Level Updates

The associated iLO target (and OA if it is a blade) targets will be found.

4) Enter credentials for the associated iLO target.

7) Set reboot options.

8) Start or schedule the update.

HP-UX software and driver patches can be installed.

HP SUM 6.0.0 and later Instructions

The current directory will be added as a baseline automatically.

3) Go to the Nodes page and select Add Node.

Enter IP address and administrator credentials for the system iLO.