HP Smart Update Manager User Guide

HP Smart Update Manager User Guide
Abstract
This document describes how to use HP SUM to apply firmware updates to HP ProLiant and HP Integrity servers, and apply
software updates to HP ProLiant servers. This document is intended for individuals who understand the configuration and
operations of Microsoft Windows, Windows Server, Linux, smart components, and the risk of data loss from performing updates.
HP Part Number: 613175-009

Published: May 2013
Edition: 10a
© Copyright 2009, 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.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial
Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under
vendor’s standard commercial license.
Acknowledgments
Microsoft®, Windows®, Windows Vista®, and Windows Server® are U.S. registered trademarks of Microsoft Corporation.
Contents
1 Introduction...............................................................................................6
HP SUM overview.....................................................................................................................6
Deploying HP SUM...................................................................................................................7
Running HP SUM.................................................................................................................7
Deploying firmware for HP ProLiant servers using the HP Service Pack for ProLiant.........................9
HP SUM supported firmware for HP ProLiant servers...........................................................10
Deploying HP Integrity Smart Update Firmware bundles with HP SUM......................................10
HP SUM supported firmware for Integrity servers...............................................................11
Deployment modes............................................................................................................11
Deployment scenarios.........................................................................................................12
Choosing HP SUM or HP SIM..................................................................................................13
Disabling BitLocker to permit firmware updates...........................................................................13
HP SUM status icons...............................................................................................................15
2 Using the HP SUM GUI.............................................................................16
Keyboard support...................................................................................................................16
Source selections....................................................................................................................16
Setting Proxy Server options................................................................................................17
Using multiple repositories..................................................................................................18
Adding the repository.........................................................................................................18
Editing the repository.........................................................................................................19
Removing the repository......................................................................................................19
Configuring the components................................................................................................19
Downloading components for target discovery.......................................................................20
Setting a schedule to download updates from the web............................................................20
Creating a custom baseline in HP SUM.................................................................................20
Filtering a custom baseline.............................................................................................21
Saving a custom baseline...............................................................................................21
Updating mixed HP ProLiant and HP Integrity environments.....................................................21
Selecting the targets................................................................................................................22
Inter-target dependency......................................................................................................23
Dependency checking........................................................................................................23
Target types......................................................................................................................23
Finding and discovering targets...........................................................................................23
Adding a single target........................................................................................................24
Updating VMware firmware................................................................................................24
Entering target credentials...................................................................................................25
Editing a target..................................................................................................................25
Removing a target..............................................................................................................25
Managing groups..............................................................................................................25
Pending firmware updates for iLO (HP Integrity servers only)....................................................26
Reviewing and installing updates..............................................................................................27
Installing updates...............................................................................................................28
Aborting an installation......................................................................................................28
Viewing failed dependencies...............................................................................................28
Selecting bundles...............................................................................................................28
Selecting components.........................................................................................................29
Selecting devices...............................................................................................................30
Viewing firmware details.....................................................................................................30
Viewing firmware mismatch details (HP Integrity servers only)...................................................31
Installation options.............................................................................................................31
Reboot options..................................................................................................................32
Contents 3
Scheduling updates................................................................................................................32
Generating and viewing reports...............................................................................................32
Generating a Report..........................................................................................................32
Viewing a report................................................................................................................33
3 Using scripts to deploy updates..................................................................34
Command-line interface...........................................................................................................34
Command-line syntax.........................................................................................................34
Using Linux root credentials............................................................................................34
Prerequisites for using Linux root credentials.................................................................35
Switch update commands...............................................................................................35
Command-line arguments...................................................................................................36
Component configuration for Windows components only........................................................44
Command-line examples.....................................................................................................44
Return codes.....................................................................................................................46
Windows smart-component return codes...............................................................................46
Linux smart-component return codes.....................................................................................46
Linux RPM return codes.......................................................................................................47
VMware ESXi smart-component return codes.........................................................................47
Input files...............................................................................................................................48
Input file format and rules....................................................................................................48
File encoding....................................................................................................................49
Error reporting...................................................................................................................49
Input file parameters...........................................................................................................50
Reports..................................................................................................................................60
Downloading HP SUM and components from the SDR.................................................................61
4 Advanced topics......................................................................................62
Configuring IPv6 networks.......................................................................................................62
Configuring IPv6 for Windows Server 2003..........................................................................62
Configuring IPv6 for Windows Server 2008..........................................................................63
Configuring IPv6 for Linux...................................................................................................63
Network ports used by HP SUM...............................................................................................64
5 Troubleshooting........................................................................................66
Installation issues....................................................................................................................66
Components do not appear on the Select Items to Install screen or do not deploy from the silent
console mode....................................................................................................................66
Collecting trace directories.............................................................................................66
The Update returned an error message appears.....................................................................68
Installation failed when installing Linux RPMs.........................................................................68
Discovery and connection issues...............................................................................................68
The connection error or Discovery Failed message appears.....................................................68
Troubleshooting connection errors....................................................................................68
HP SUM stalls during discovery...........................................................................................69
The Unable to Access Host message appears........................................................................69
Configuring firewall settings............................................................................................69
A Microsoft Windows Security Alert appears.........................................................................69
Configuring Windows firewall settings.............................................................................69
HP SUM fails on Windows hosts due to McAfee firewalls........................................................70
IPv6 network issues.................................................................................................................72
Troubleshooting HP SUM in IPv6 Windows Server 2003 environment.......................................72
Troubleshooting HP SUM in IPv6 Windows Server 2008 environment.......................................73
Troubleshooting HP SUM in IPv6 Red Hat and Novell SUSE-based Linux environments.................73
Operation issues....................................................................................................................74
HP SUM stalls during boot..................................................................................................74
4 Contents
HP SUM connection is lost during iLO or NIC firmware update................................................74
The user-specified reboot message does not appear when using a Japanese character set on a
Linux operating system........................................................................................................74
Automatic reboot does not occur when using the user-specified reboot message with a Japanese
character set on Windows...................................................................................................74
HP SUM stalls when run in a directory path that contains multi-bye characters............................74
Microsoft Windows displays a Found new hardware message.................................................75
Non-matching systems error reported when building source Linux RPMs or installing Linux RPMs
built from source................................................................................................................75
Linux component version discrepancy for source RPMs............................................................75
No components found in the selected repositories message appears.........................................75
HP SUM prevents an upgrade of Virtual Connect firmware if the VC health is invalid or bad health
state.................................................................................................................................75
HP ProLiant G6 Server ROM downgrade from 2010.03.30 or later to 2010.03.01 or earlier
with HP SUM is not supported.............................................................................................76
For HP ProLiant G2, G5, and G6 servers, after upgrading to the May 2011 (or later) revision of
the system ROM, perform special steps if downgrading the system ROM to revisions earlier than
May 2011 is required.........................................................................................................76
6 Support and other resources......................................................................77
Information to collect before contacting HP.................................................................................77
How to contact HP..................................................................................................................77
Subscription service................................................................................................................77
Related information.................................................................................................................78
Typographic conventions.........................................................................................................79
HP Insight Remote Support software..........................................................................................79
HP Insight Online...................................................................................................................80
7 Documentation feedback...........................................................................81
Acronyms and abbreviations.........................................................................82
Index.........................................................................................................83
Contents 5
1 Introduction
HP SUM overview
HP SUM is a technology included in many HP products for installing and updating firmware and
software on HP ProLiant servers, and firmware on HP Integrity servers.
HP SUM provides a GUI and a command-line scriptable interface for:
• Deployment of firmware for single or one-to-many HP ProLiant and HP Integrity servers and
network-based targets such as iLO, OA, and VC Ethernet and Fibre Channel modules.
• Deployment of software for single or one-to-many HP ProLiant servers (supported in Windows
and Linux environments).
HP SUM has an integrated hardware and software discovery engine that finds the installed hardware
and current versions of firmware and software in use on target servers. This capability prevents
extraneous network traffic by sending only the required components to a target host. HP SUM
installs updates in the correct order and ensures that all dependencies are met before deploying
an update. HP SUM prevents an installation if there are version-based dependencies that it cannot
resolve.
HP SUM does not require an agent for remote installations, because it copies a small, secure SOAP
server to the target for the duration of the installation. 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.
Key features of HP SUM include:
• Dependency checking, which ensures appropriate installation order and dependency checking
between components
• Intelligent deployment of only required updates
• Simultaneous firmware and software deployment for multiple remote targets in both GUI and
CLI modes
• Improved deployment performance
• Local online deployment of HP ProLiant servers and enclosures
• Remote (one-to-many) online deployment of HP ProLiant and HP Integrity servers and enclosures
• Local offline firmware deployments with HP Support Pack for ProLiant deliverables
• Remote offline deployment when used with the SmartStart Scripting Toolkit (HP ProLiant G7
and earlier servers), Scripting Toolkit (HP ProLiant Gen8 and later), iLO Virtual Media, or PXE
booted media
• GUI or CLI scripts with extensive logging
• Remote command-line deployment
• Support for updating firmware on network-based targets such as the OA, iLO through the
Network Management Port, VC Ethernet and Fibre Channel modules, and 3Gb/6Gb SAS BL
Switch interconnects on HP ProLiant servers
• Support for deploying firmware updates to supported Integrity servers and Superdome 2
enclosures
• Support for updating VC modules on Integrity servers
6 Introduction
NOTE: HP SUM does not support third-party controllers. This includes flashing hard drives
behind these controllers.
• Remote online deployment of I/O Card firmware on HP ProLiant and HP Integrity targets
running HP-UX
Deploying HP SUM
The following sections discuss deployment from HP SUM. For more information on planning an
update, see the HP ProLiant Firmware Management Best Practices Overview, HP ProLiant Firmware
Management Best Practices Planning Guide, or HP BladeSystem ProLiant Firmware Management
Best Practices Implementer Guide, available on the HP SUM documentation website at http://
www.hp.com/go/hpsum/documentation.
NOTE: HP SUM stores host and group information from session to session. However, user names,
passwords, and existing credentials are not stored in a session or from session to session.
Running HP SUM
HP SUM provides three ways of running for users:
• GUI—For firmware and software deployments
• Express—For software deployments only (local host only)
• Scripted—For silent firmware and software deployments
HP SUM supports local and remote deployments. HP SUM runs in Windows and Linux in online
and offline mode. For more information about deployment modes, see “Deployment modes” (page
11).
NOTE: You cannot use Windows Hyper-V systems to run HP SUM and deploy updates. You can
select Hyper-V systems as a target from HP SUM.
Use the following table to determine the correct execution mode for the server use case.
NOTE: Before deploying software updates to a target server, be sure that a recent backup of
the target server is available in the event the deployment procedure fails.
Deploying HP SUM 7
Scenario Description HP SUM command HP deliverable
Interactive, graphical Use this scenario when you: • Windows: • Online:

deployment on a local host • Are not familiar with hpsum
Run HP SUM on the server command line tools ◦ HP Service Pack for
being updated. • Linux: ProLiant (SPP)
• Are deploying
components on a local, ./hpsum • Offline:
single host
• Do not require scripting
◦ HP SPP
• Want to select the

components to be
installed
Scripted deployment on a Use this scenario when you: • Windows: • Online:

local host • Are familiar with hpsum -s
Run HP SUM from a network command line tools ◦ HP SPP
share on a local server. • Linux:
• Are deploying • Offline:
components on a local, ./hpsum -s
None
single host
• Must perform a
customized, scripted
deployment
• Are unable to unlock the
required HP SUM
network ports for remote
deployment
Interactive, graphical Use this scenario when you: • Windows: • Online:

deployment to a remote host • Are not familiar with
hpsum
Run HP SUM from a command line tools ◦ HP SPP
workstation and update • Linux:
• Do not require scripting ◦ HP Integrity Smart
remote hosts over the ./hpsum
network using the GUI. • Want to select the Update Firmware
components to be Targets can be bundles
installed Windows, Linux,
VMware ESXi 5.0, • Offline:
• Need to update multiple VMware ESXi 5.1 or None
targets including OA, later, HP-UX 11.31 or
VC, and server-based later servers, OA, iLO, or
firmware
8 Introduction
Scenario Description HP SUM command HP deliverable
• Need to select individual VC IP address or DNS

firmware to update name.
• Need to select individual

hardware devices to be
updated
• Need to target VMware
host servers
Scripted deployment to a Use this scenario when you: • Windows: • Online:

remote host • Are familiar with hpsum -s -target
Run HP SUM from a command line tools Target1 -target
◦ HP SPP
workstation and update a
• Must perform a Target2 -username
◦ HP Integrity Smart
remote host over the network User1 -password
customized, scripted Update Firmware
using scripts. PW1
deployment bundles
• Need to update multiple • Linux:
• Offline:
targets, including HP-UX
./hpsum -s -target
11.31 or later, and OA,
VC, and server-based Target1 -target ◦ SmartStart Scripting
Target2 -username Toolkit (G7 and older)
firmware
User1 -password
• Need to update all PW1 ◦ Scripting Toolkit
enclosure firmware (Gen8 and older)
• Need to target VMware
host servers
Automatic deployment to Use this scenario when you: The HP SPP manages this • Online:
one or more servers in a HP • Do not have an operating automatically
BladeSystem enclosure None
system installed on a
Use the HP SPP with server blade • Offline:
embedded HP SUM to
• Want an automatic way ◦ HP SPP
deploy firmware updates to
to deploy firmware
one or more blades
updates
automatically.
• Do not require log files
or user interaction with
the installation process
• Want to update multiple
blades in an enclosure in
a single operation
Update an existing enclosure The same scenario as shown • Windows: • Online:

manually in the “Interactive, graphical
hpsum
deployment to a remote ◦ HP SPP
host” or “Scripted • Linux:
deployment to a remote • Offline:
host” scenarios discussed ./hpsum
previously in this table ◦ HP SPP
Deploying firmware for HP ProLiant servers using the HP Service Pack for ProLiant
The SPP is a re-packaging of HP ProLiant system software and firmware for HP ProLiant BL/ML/DL/SL
servers and their options, and BladeSystem enclosures including OA,VC, and 3 Gb SAS switches
running supported Windows, Linux, and VMware operating systems. The single SPP image contains
a comprehensive collection of firmware and system software components including drivers, agents,
tools, utilities, and firmware that is tested, managed, and deployed together as a single solution.
The SPP includes HP SUM for deployment of the SPP components.
For a complete list of HP ProLiant systems and software supported by SPP, see the HP Service Pack
for ProLiant Release Notes on the HP website:
http://www.hp.com/go/spp/documentation
Deploying HP SUM 9
For information on the minimum requirements to run HP SUM, see the HP Smart Update Manager
Release Notes on the HP website:
http://www.hp.com/go/hpsum/documentation
HP SUM supported firmware for HP ProLiant servers
Component Supported
System ROM Yes
iLO firmware Yes, both server-based and directly to the iLO Management
NIC port
Broadcom NIC firmware Yes
Intel NIC firmware Yes
NetXen NIC firmware Yes, online
QLogic NIC firmware Yes
PowerPIC firmware Yes
Smart Array controller firmware Yes
SAS and SATA hard drive firmware behind HP Smart Array Yes, some older SATA hard drives require offline mode
controllers
SAS and SATA hard drive firmware behind non-Smart No

Array controllers
Emulex, QLogic, and Brocade Fibre Channel HBA firmware Yes
FC switch firmware Yes, online only

For more information on supported FC switches, see the
HP Smart Update Manager Release Notes, on the HP Smart
Update Manager Information Library at http://
Tape Blade firmware Yes
OA firmware Yes, online only
VC firmware Yes, online only
CPLD firmware Yes
HP StorageWorks MDS 600 enclosure firmware Yes
MSA 2000 firmware (P2x00 firmware) No
D2600/D2700 firmware Yes, when attached through a Smart Array controller
3Gb/s and 6 Gb/s SAS BL switches Yes, online only
FCoE/CNAs Yes
SES firmware Yes
Deploying HP Integrity Smart Update Firmware bundles with HP SUM

You can use HP SUM to deploy components delivered with the HP Integrity Smart Update Firmware
bundles, or use HP SUM to pull updates from the web.
10 Introduction
Deploying firmware to the HP Integrity servers is done remotely and is the same as deploying other
firmware, such as OA, with the following exceptions:
• Specify the IP address of the monarch (primary) OA on Suppertime 2 enclosures, or the
Monarch iLO 3 management processor on multi-blade servers.
• On the Select Components screen, click Configure Now, and then select whether you want to
Upload and Activate or Upload but Do Not Activate. The Upload and Activate option
automatically powers down and reboots the server after the update finishes, which activates
the firmware. If you select the Upload but Do Not Activate option, the system firmware will be
pending activation until the server is manually powered off. By default, HP SUM selects Upload
but Do Not Activate.
• Specify the IP address as the target to update I/O firmware updates on HP-UX servers. You
can only update remote HP-UX targets.
For more information on HP Integrity Smart Update Bundles, see the Manage HP Integrity Servers
Firmware Updates website at http://www.hp.com/go/smartupdate/integrity.
For information on the minimum requirements to run HP SUM, see the HP Smart Update Manager
Release Notes on the HP website:
http://www.hp.com/go/hpsum/documentation
HP SUM supported firmware for Integrity servers
Component Supported
System ROM firmware Yes
FPGA firmware Yes
iLO-3 MP firmware Yes
Power Monitor firmware Yes
Superdome 2 Complex and nPartition firmware Yes
OA firmware Yes
VC firmware Yes
I/O Card firmware Yes (Integrity servers running HP-UX)
FC switch firmware Yes, online only

For more information on supported FC switches, see the
HP Smart Update Manager Release Notes, on the HP Smart
Update Manager Information Library at http://
Deployment modes
The following key terms apply when using HP SUM to deploy updates:
Term Definition
Local The installation runs on the physical hardware you are

updating. For example, running a utility on a server to
update the server's system ROM.
Remote The installation runs on one system, but updates other

physical targets. For example, updating the OA or HP
Integrity server firmware across a network.
Online The installation occurs while the host processor is running

in the normal server environment. For example, if the server
Deploying HP SUM 11
Term Definition
runs Microsoft Windows Server 2008, the update occurs

under this environment. The update does not require you
to boot to a special environment to update the firmware.
You might need to reboot the target to activate the
firmware.
Offline In offline mode, the HP SUM boots a small Linux kernel

and enables updates to occur on a single server.
• Only updates the local system
• Only uses a single repository
NOTE: Some features of HP SUM that require the
regular local host operating systems are not supported
in offline mode.
These terms can be used in combination to designate the type of environment required for updates
to occur, such as local-online or remote-online.
Offline mode does not support the following functions:
• Proxy Server details
• Configure components
• Creating custom baselines
• Filter repository contents
• Use multiple repositories
• Add repository
• Edit repository
• Remove repository
• Configure components
• Abort installation
• Last updated field
• Associated targets
• Updating remote targets
• Scheduling updates
Deployment scenarios
HP SUM deploys updates from a local host or one or more remote hosts. If the host running HP
SUM is using Windows, you can update Windows, Linux, VMware, or HP–UX targets. You can
also update remote HP ProLiant or HP Integrity iLO, OA, and VC targets.
12 Introduction
The following table describes when typical HP SUM deployment scenarios are used.
Scenario Used when
Graphical deployment on a local host • You are not familiar with command line tools.
• You are deploying components on a local, single host.
• Updates do not require scripting.
Scripted deployment on a local host • You are familiar with command line tools.
• You are deploying components on a local, single host.
• Updates require a customized, scripted deployment.
Graphical deployment to a remote host • You are not familiar with command line tools.
• You are deploying components on one or more remote
hosts.
• Updates do not require scripting.
Scripted deployment to a remote host • You are familiar with command line tools.
• You are deploying components on one or more hosts.
• Updates require a customized, scripted deployment to
one or more host systems.
Choosing HP SUM or HP SIM

Use HP SUM to update 1–100 servers concurrently. You can use HP SIM to update more than 10
servers concurrently.
HP SIM versions 7.0 and later include the functionality of HP SUM. This allows you to use HP SIM
to update firmware, software, and drivers in the same session. You do not need to update these
items separately.
Disabling BitLocker to permit firmware updates

The TPM, when used with BitLocker, measures a system state. Upon detection of a changed ROM
image, it restricts access to the Windows file system if the user cannot provide the recovery key.
HP SUM detects if a TPM is enabled in your system. For some newer models of HP ProLiant servers,
if a TPM is detected in your system or with any remote server selected as a target, HP SUM utilities
for HP iLO, Smart Array, NIC, and BIOS warn users prior to a flash. If the user does not temporarily
disable BitLocker and does not cancel the flash, the BitLocker recovery key is needed to access the
user data upon reboot.
A recovery event is triggered in the following situations:
• You do not temporarily disable BitLocker before flashing the system BIOS when using the
Microsoft BitLocker Drive Encryption.
• You have optionally selected to measure HP iLO, Smart Array, and NIC firmware.
If HP SUM detects a TPM, a warning message appears.
Choosing HP SUM or HP SIM 13

To enable firmware updates without the need 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 have been completed,
the BitLocker Drive Encryption can be re-enabled. Once the BitLocker Drive Encryption has been
re-enabled, the plain text key is removed and BitLocker secures the drive again.
CAUTION: Temporarily disabling BitLocker Drive Encryption can compromise drive security and
should only be attempted in a secure environment. If you are unable to provide a secure
environment, HP recommends providing the boot password and leaving BitLocker Drive Encryption
enabled throughout the firmware update process. This requires setting the /tpmbypass parameter
for HP SUM or the firmware update is blocked.
To temporarily disable BitLocker support to allow firmware updates:
1. Click Start, and then search for gpedit.msc in the Search Text box.
2. When the Local Group Policy Editor starts, click Local Computer Policy.
3. Click Computer Configuration→Administrative Templates→Windows Components→BitLocker
Drive Encryption.
4. When the BitLocker settings are displayed, double-click Control Panel Setup: Enable Advanced
startup options.
5. When the dialog box appears, click Disable.
6. Close all windows, and then start the firmware update.
To enable advanced startup options:
1. Enter cscript manage-bde.wsf -protectors -disable c:
2. When the firmware update process is completed, the BitLocker Drive Encryption support can
be re-enabled by following steps 1 through 4 but clicking Enabled in step 5 instead. The
following command can be used to re-enable BitLocker Drive Encryption after firmware
deployment has completed.
3. Enter cscript manage-bde.wsf -protectors -enable c:
The following table describes TPM detection scenarios that you might encounter.
Scenario Result
If TPM is detected and enabled, the installation is not silent, A warning message appears. Select OK to continue. The
and a system ROM must be updated. installation is not canceled.
If TPM is detected and enabled, the installation is silent, No warning appears. A new log file is generated
the /tpmbypass switch is not given, and any firmware (%systemdrive%\cpqsystem\log\cpqstub.log).
updated must be applied to the server. Because the installation is silent, the installation is
terminated and cannot continue.
If TPM is detected and enabled with Option ROM A warning message appears. After selecting OK, you can
Measuring, the installation is not silent, and a system ROM continue. The installation is not canceled.
must be updated.
If TPM is detected and enabled with Option ROM No warning appears. A new log file is generated
Measuring, the installation is silent, the /tpmbypass (%systemdrive%\cpqsystem\log\cpqstub.log).
switch is not given, and any firmware updated must be Because the installation is silent, the installation is
applied to the server. terminated and cannot continue.
If TPM is detected and enabled, the installation is silent, The installation occurs.
the installation occurs, and the /tpmbypass switch is
supplied.
14 Introduction
HP SUM status icons
HP SUM uses the following status icons:
Icon Description
This icon indicates there is an error you need to resolve before continuing.
This icon indicates a recommended update.
This icon indicates that the component or bundle are ready for installation, or that HP
SUM added a repository successfully.
This icon indicates that there are no supported devices or updates available.
HP SUM status icons 15

2 Using the HP SUM GUI
Keyboard support
The HP SUM GUI has accelerator keys that enable you to manage and control common tasks
quickly. To ensure proper navigation, the following are a few reminders.
• Press ALT to see the task corresponding to the underlined letter.
• The accelerator keys work by pressing ALT + the underlined letter.
• Press Space to select items such as hosts or groups.
• Press Tab to select from a list, and then press the arrow keys to toggle radio buttons.
Source selections
Repositories are the directories that contain the SPP, bundles, and individual smart components
HP SUM uses to update targets. Bundles are groups of firmware and software components that HP
releases. HP SUM allows you to choose one or more repositories and check the HP FTP site for the
latest versions of the components.
NOTE: If more than one repository contains the same component, HP SUM uses the component
located in the repository closest to the top of the Current Repositories table.
Current Repositories table

The Current Repositories table displays:
• Name—This field displays the repository name. Select the repositories you want to use by
clicking the checkbox next to the repository name. If you want to edit a repository, highlight
the entire line to activate the Edit and Remove buttons.
◦ HP SUM automatically creates a repository named Default and scans it for updates. This
repository is the folder that holds the HP SUM application.
◦ The HP FTP site (ftp://ftp.hp.com) contains the latest versions of the firmware and software
components available from HP. The components are available for selection on the
Review/Install Updates screen. When using this method, both firmware and software
components are available for selection. The components are not downloaded from
ftp.hp.com to a target until the Install button is clicked unless the component is needed
to discover supported devices. If components are needed for discovery, you are prompted
to allow this action. The ftp.hp.com check box is cleared by default. To pull updates from
the web, click the ftp.hp.com check box. If HP SUM has downloaded a component, HP
SUM does not download it again. This repository cannot be edited except to set the
repository filter.
Click Settings in this field to select a directory to save downloads, change proxy settings
(if necessary) to access ftp.hp.com, and schedule automatic downloads. For more
information on changing proxy settings, see “Setting Proxy Server options” (page 17).
For information on scheduling automatic downloads, see “Setting a schedule to download
updates from the web” (page 20).
◦ Use the last downloaded repository from the HP FTP site—This option includes the
components that have been previously downloaded from the ftp.hp.com site. To use
components downloaded from the HP website, select this check box. The repository cannot
be edited.
• Location—This field displays the location of the repository.
• Addition Information—This field provides more information about the repository.
• Status—This field displays the repository's contents, and if you need to configure any
components in the repository.
◦ Click Repository Contents to view the contents of the chosen repository. Click the version
link to view the description, installation notes, enhancements and fixes, and version history
of the component or bundle.
◦ Click Configure Components to select components to configure. This option is available
only for a local repository with components that require configuration.
NOTE: HP SUM does not display Configure Components if HP SUM and the components
are on read-only media.
NOTE: The check box by the repository name selects whether the updates are used during an
update; it does not select the row for editing or removal.
Setting Proxy Server options

Proxy server information may be needed to allow HP SUM to access ftp.hp.com to determine if
updates are available and needed.
1. On the Source Selections screen, click Settings in the Current Repositories table. The link is in
the “Repository Name” field of the “Check for Latest Updates from ftp.hp.com” row in the
table.
2. In the Enter the Proxy Details dialog box, check Use Proxy server details.
3. Select Server or Script.
• If you chose Server, enter the server IP Address and Port information.
• If you chose Script, enter the script location in one of the following ways:
◦ Click Detect Proxy to automatically add the default location of the configuration
script.
◦ Manually enter the address.
4. Enter the User ID and Password (if necessary).
5. Click OK.
Source selections 17
Using multiple repositories
HP SUM allows you to select one or more repositories when selecting components to be installed.
You can have a different filter set for each repository. Be aware of the following items:
• HP SUM uses the highest version of a bundle or component it finds in any of the selected
repositories. If the same highest bundle or component version is found in multiple repositories,
HP SUM uses the version listed highest on the Current Repositories table.
• If a component is located in both a local repository and it is also on ftp.hp.com, HP SUM uses
the local version.
Adding the repository
If the default repositories do not include the component or bundle updates:

1. Click Add Repository, and then choose Firmware Only, Software Only, or Both.
You can choose the updates to use when you add or edit a repository. By default, HP SUM
displays firmware and software updates. If you want to view which updates are being used
in an existing repository, select the repository in the Current Repositories table, and then click
Edit Repository.
• Both - HP SUM displays component firmware and software updates that are ready.
• Firmware only - HP SUM only displays component firmware updates that are ready.
• Software only - HP SUM only displays software updates that are ready.
NOTE: If you select firmware or software only, you might not have any updates to apply
to a device on the Select Bundles or Select Components screens.
2. Enter an optional name for the repository in Repository Name.

3. Click Browse to open a navigation window, or enter the path to the directory that holds the
updates in Repository location directory or UNC path. Use the following examples to enter the
path:
• Drive share format: drive:path or /path or \path
• UNC format: \\fileserver\share
4. Click OK.

Editing the repository
You can edit a repository to change its name or location, or to filter the repository’s updates.
1. If you want to change the name of a repository, select the line of the repository you want to
edit, and then click Edit Repository.
NOTE: The check box by the repository name controls whether a repository is used in
updates; it does not select the row for editing or removal.
2. Edit the Repository Name.

3. Select Firmware Only, Software Only, or Both.
You can choose the updates to use when you add or edit a repository. By default, HP SUM
displays firmware and software updates. If you want to view which updates are being used
in an existing repository, select the repository in the Current Repositories table, and then click
Edit Repository.
• Both - HP SUM displays component firmware and software updates that are ready.
• Firmware Only - HP SUM only displays component firmware updates that are ready.
• Software Only - HP SUM only displays software updates that are ready.
NOTE: If you select firmware or software only, you might not have any updates to
apply to a device on the Select Bundles or Select Components screens.
Removing the repository

1. Select the repository you want to remove by clicking its row in the table to highlight it.
NOTE: The check box by the repository name controls whether a repository is used in
updates; it does not select the row for editing or removal.
2. When the correct row is highlighted, click Remove Repository.

3. Click Yes if you want to remove the repository, click No to cancel.
Configuring the components

Some components might have required or optional configuration settings. Configuration parameters
can include information necessary to set up the component correctly or passwords required for
software installed by the component. The configuration is stored within the component and is
propagated to all targets. If the optional configuration data of a component is not provided and
the component has not been installed previously, the default values for that configuration data are
used. If the component has been previously installed and configured and no changes are made
to the configuration data, the existing configuration information is preserved. Component
configuration requires that Smart Components are in a write-accessible location. A CD, DVD, or
read-only network share is not supported.
Components you can configure are indicated in the Status column on the Select Sources screen.
1. Click Configure Components, select the component you want to configure, and then click
Configure.
2. Follow the instructions when the Item Configuration screen appears.
3. When you finish configuring all the components, click OK to return to the Source Selections
screen.
NOTE: If more than one repository contains the same component, HP SUM only uses the
component located in the repository closest to the top of the Current Repositories table.
Downloading components for target discovery
If you select to pull updates from the web, when you click Next on the Source Selections screen
you see the Download Permissions screen. This list includes both Linux and Windows components
used for target discovery. If your environment does not include targets running Linux or Windows,
you can remove these components from the list to reduce the number of components that HP SUM
downloads to your system.
Setting a schedule to download updates from the web

HP SUM allows you to download updates from the HP FTP site at times that you schedule. Scheduling
your downloads allows you to:
• Minimize the impact on your network traffic.
• Schedule downloads to occur before you begin an update.
• Create a repeating download schedule can minimize download sizes.
• Download the latest updates before the update begins.
1. On the Select Repositories screen, click Settings underneath the Check for Latest Updates from
ftp.hp.com table cell.
2. Enter the repository where you want to store the downloaded updates.
3. Click the Enable Schedule check box.
4. Select whether to perform downloads Daily, Weekly, Monthly, or One Time Only.
5. Select the date and time to begin the scheduled downloads.
6. Click OK.
NOTE: To exit HP SUM, click Exit, and HP SUM will still download the updates at the time
you scheduled.
Creating a custom baseline in HP SUM

You can create a custom baseline by selecting specific components from multiple repositories. After
you create the custom baseline, you can copy the files to a DVD or USB key.
1. Download a set of updates, for example HP SPP or HP Integrity Smart Update Bundle.
NOTE: You cannot use components from the web. The components must be downloaded to
a repository listed in HP SUM.
2. Select the check box for the repositories that contain the updates you want to choose.
3. Click Custom Baseline.
4. Under Select the Criticality, click the updates you want to choose: Critical Updates,
Recommended Updates, or Optional Updates.
5. Under Type of Updates to Use, click the updates you want to choose: Firmware only, Software
only, or Both.
6. Under Select the Filter Options:
• Choose the OS from the Select OS Type list.
• Choose the type of devices from the Select Device Type list.
7. Select the check box for the updates you want to use from the Baseline Repositories list.
8. Click Save and Continue to save your baseline. For more information, see “Saving a custom
baseline” (page 21).
9. If you want to create more baselines, change the filter settings or select components. Click
Save and Continue to save the new baselines.
10. Click Done when you finish creating baselines.

Filtering a custom baseline
You can override the global settings for a bundle.
1. Click Filter Options for the bundle.
2. Click the criticality level of the updates you want to choose: Critical Updates, Recommended
Updates, or Optional Updates.
3. Under Type of Updates to Use, click the updates you want to choose: Firmware only, Software
only, or Both.
4. Under Select the Filter Options:
• Choose the OS from the Select OS Type list.
• Choose the type of devices from the Select Device Type list.
5. Click Apply.
Saving a custom baseline

1. Enter the name of the baseline in New Baseline Name.
2. Enter a description of the baseline in Description.
3. Create a version number using the drop down lists.
4. Enter a directory path, or click Browse to open a navigation window to select the directory
where you want the baseline stored.
5. Click Save to save the baseline. When HP SUM finishes saving the baseline, the window
closes.
Updating mixed HP ProLiant and HP Integrity environments

To update an environment with both HP ProLiant and HP Integrity servers:
1. Review the support matrix. Be sure to use OA and VC versions supported by both HP ProLiant
and HP Integrity servers. For more information, see the HP BladeSystem Release Sets for Mixed
ProLiant and Integrity website at http://h18004.www1.hp.com/products/servers/firmware/
mixed-release-sets.html.
2. Download the latest SPP version and HP Integrity Smart Update Firmware bundles.
NOTE: You can also use the Check for Latest Updates from ftp.hp.com function in HP SUM.
3. Unzip the SPP and HP Integrity Smart Update Firmware bundles to separate directories.
4. Launch HP SUM from one of the directories, and add the other directory on the Source
Selections screen as a component repository.
NOTE: Use the latest version of HP SUM that was included in the SPP or HP Integrity Smart
Update Firmware bundle you downloaded. You must use HP SUM version 5.0.0 or later.
5. Perform your updates. Be sure you do not update the OA or VC to a version not listed in the
support matrix.
Selecting the targets
The Select Targets screen automatically detects the local system running HP SUM and adds it to
the targets list. To find new targets, click Find Targets or Add Single Target. For more information,
see “Finding and discovering targets” (page 23) or “Adding a single target” (page 24).
If you have an enclosure that has different target types that share credentials and need to be
updated at the same time, create a group to manage them. For more information on creating and
editing groups, see “Managing groups” (page 25).
The table displays the following target information:
• Check box—Targets with selected check boxes are updated. Click the check box to select or
clear a target for update.
• Target Name—This field displays the IP address of the target or group.
• Status—This field displays a message indicating whether or not the target is ready to be
updated. Enter the credentials for each target you are updating. For more information, see
“Entering target credentials” (page 25).
NOTE: The target status Ready means that HP SUM can detect the target, and is able to
take inventory of the target. No analysis occurs until you click Next.
• Last Updated—This field displays the last time the target was updated. If HP SUM can find
the log from the last update, HP SUM shows a link to open a log file.
• Associated Targets—This field displays the associated devices of the target.
• Description—This field displays the description of the target.
• Type—This field displays the type of target (for example, iLO or Onboard Administrator).
NOTE: For HP SUM to discover a Broadcom NIC during an online update, you must bring the
NIC up in Linux. From a command line, enter # ifup ethx or # ifconfig ethx up.

Inter-target dependency
HP SUM finds potential targets by checking the OA host server list for all targets you add. HP SUM
asks you if you want to add the potential targets it found, and does dependency checking for these
servers.
Dependency checking
Dependency checking is an integral function of creating a supported configuration before HP SUM
deployment. During this process, HP SUM ensures that the requirements for a component or target
update are met. These include system requirements (for example, libraries and services) for the
component, target, or associated devices of the target have compatible software and firmware
revisions. This process is initiated automatically and silently after the HP SUM discovery process
and it involves:
1. Checking the dependencies of component /target/ or devices associated with targets. Examples
of dependency checking include:
• Health component requirement for installation of the SNMP Agents
• Required operating system libraries
• Compatibility of OA, VC, and iLO firmware versions
2. Indicating if there is a dependency failure. Failures are displayed in the HP SUM GUI, and
also saved in a log file.
To resolve any dependencies that were indicated during this process, review the logs and correct
the failures. After resolving the dependencies, restart the HP SUM application.
NOTE: For Superdome 2 servers that do not support online firmware updates, power down all
Superdome 2 partitions in the complex. If you do not power down all the partitions, a Failed
Dependencies error appears. On the Select Devices screen, click Ignore Warnings, and HP SUM
powers down the partitions for you after you begin the installation process.
Target types
Supported target types include:
• Server–a local host or a remote server. For example, Server — Windows, Server — Linux,
Server — UX.
• iLO
• Onboard Administrator
• Virtual Connect
• Superdome 2 Onboard Administrator
• VMware Host
NOTE: Only supported for remote installation and requires the HP Insight Management
WBEM Providers. For more information, see “Updating VMware firmware” (page 24).
• HP SAS B/L Interconnect Switch
Finding and discovering targets

1. Click Find Targets.
Selecting the targets 23

2. Select IP Address Range, Port Address, or LDAP Scan for Remote Targets, and then click OK.
• IP Address–Enables you to search a range of IP addresses in IPv4 or IPv6 format. Enter
the required address range information, click Search, select the target, and then click
Add to List.
NOTE: HP SUM searches only c-class blocks of IP addresses, and a maximum of 255
targets. For example, you can search for IP address 192.168.1.1 through 192.168.1.255,
but HP SUM does not support searching IP addresses 192.168.1.1 through
192.168.3.255.
• Port Address–Enables you to search in a range of IP addresses and specific port address.
• LDAP Scan for Remote Targets–Enables you to search for targets using an LDAP query.
NOTE: HP SUM will prompt whether or not to continue at the end of the discovery process if a
Linux server belongs to a Serviceguard cluster and the target is active. Click Yes or No. If you
continue and perform the update, you must reboot the target to activate the update.
Adding a single target

1. Click Add Single Target.
2. Type the IP or DNS address of the target.
3. Select the type of target from the dropdown list (optional). If you leave this field as the default
setting, HP SUM detects the type of target during the discovery process. If you select the correct
target type, the discovery process is faster.
4. Type a brief description of the target (optional).
5. Enter the username and password.
If you are using a Linux system and want to use a non-root user, click Use different user for
execution of components. Enter the user and password.
NOTE: The user must be part of the root group.
6. Select the checkbox if you want to validate the credentials and start the target discovery
process when you create the target.
7. If HP SUM finds an update already running on the target, select whether to continue the update
or cancel the update and use update planned in the current HP SUM session.
8. Click OK. This begins the discovery process of the target that is added.
Updating VMware firmware

The following must be true to update a VMware ESXi 5.0 target:
• The target must be running VMware ESXi 5.0 or later.
• The target must be active on the network so HP SUM can detect it.
• You are not attempting to run HP SUM on the VMware ESXi 5.0 or later target. You cannot
execute HP SUM locally to update a VMware ESXi 5.0 target.
• You are executing HP SUM on a Windows or Linux host computer.
• The VMware server must be running hp-smx-provider-500.03.01.2–434156 or later. You can
get the bundle from one of the following locations:
◦ Version 1.3.5 or later of the HP Insight Management WBEM Provider offline bundle. You
can download the bundle from the HP Online Depot at http://vibsdepot.hp.com.
◦ The provider is included in version 5.25 of the HP Custom Image. You can download
the HP Custom Image ISO from the Custom VMware ESXi Image for HP ProLiant Servers
website at http://www.hp.com/go/esxidownload.
Entering target credentials
You must enter credentials in the root group for all targets, including the local host if you are
updating it. To enter target credentials:
1. In the Select Targets screen table, select one or more targets by clicking to highlight the rows.
2. Click Enter Credentials.
3. In the Enter Credentials for the Target(s) dialog box, select one or more targets. The credentials
you enter are applied to all selected targets. The Select All button selects all targets in the list.
4. Click Add Credentials.
5. In the Enter Credentials for Target dialog box:
a. Enter a user name and password with root or administrator rights.
If you are using a Linux system and want to use a non-root user, click Use different user
for execution of components. Enter the user and password.
b. Select what HP SUM should do if it detects an update already running.
6. Click OK to save and close the dialog box.
7. Click Done.
8. In the Select Targets screen table, the Status field displays progress messages as HP SUM
verifies the credentials you entered.
NOTE: HP Integrity servers only: If an iLO is part of a domain, HP recommends managing

the entire domain, not just the iLO. During the discovery process, if HP SUM detects that an
iLO is part of a target domain, HP SUM asks you if you want to manage the entire domain,
or if you want to continue to update just the iLO. To add the OA and manage the entire
domain, click Enter OA Credentials.
Editing a target
1. Highlight a target, and then click Edit Target.
2. Type a brief description of the target (optional).
3. Enter the username and password.
If you are using a Linux system and want to use a non-root user, click Use different user for
execution of components. Enter the user and password.
NOTE: The user must be part of the root group.
4. Select the checkbox if you want to validate the credentials and start the target discovery
process when you create the target.
5. If HP SUM finds an update already running on the target, select whether to continue the update
or cancel the update and use update planned in the current HP SUM session.
6. Click OK after entering the information to exit this page.
Removing a target
Select a target, highlighting the entire line, and then click Remove Target.
If you remove a target, HP SUM removes the target from any groups and any scheduled updates.
Managing groups
To add a new group:
1. Enter a Group Name.
2. Enter a Description (optional).
3. From the Available Targets list, select the targets to add to the group.
4. Click Add.
Selecting the targets 25

5. When you are finished, click OK.
To edit an existing group:
1. Select targets in the Available Targets list and then click Add to add one or more targets to
the group.
2. Select the targets in the Targets in Group list, and then click Remove to remove one or more
targets from the group.
3. Enter a Description (optional).
4. Click OK.
Pending firmware updates for iLO (HP Integrity servers only)

If you update a previously updated Integrity server via iLO but did not power down and reboot to
activate the system firmware change, HP SUM asks you what to do with the pending update. You
can choose to:
• Leave the system for manual reboot to activate.
This disables the target in HP SUM and you will need to manually power down and reboot
the system to activate the pending update. After the reboot, you can open HP SUM and
proceed with the firmware update.
• Let HP SUM power down the system and reboot the operating system to let the activation
happen.
HP SUM sends a graceful shutdown request to the operating system and then powers down
the server to let the activation occur. Then HP SUM powers back up the server. After the system
restarts, you can continue with new updates.
• Let HP SUM cancel the pending update.
This option will cancel the staged update. After the HP SUM finishes the cancellation, HP SUM
will rediscover the target and you can continue with the new updates.
Before you cancel a pending update, make sure it is not a critical fix that prevents you from applying
current updates.
If you are updating an HP Integrity BL8x0c i2/i4 or rx2800 i2/i4 server, the firmware activation
will occur during the next power down. To manually check the firmware activation while the system
is powered down, run the iLO3 Management Processor Command Menu command, fw.
NOTE: Cancelling an update and not performing new updates might leave the server in a state
where you cannot boot it. The iLO and system firmware might be mixed and incompatible. If you
cancel a pending update, make sure you perform a new full firmware update.

Reviewing and installing updates
This screen appears after HP SUM completes the dependency checks for each target. The status
column notifies you whether each target has updates available, is ready to update, or if there are
dependencies you need to resolve.
On the Select Bundles or Select Components screen, you can select the devices on each target that
you want to update. Click Select Bundles to use a collection of components that have been tested
together for the target. The Select Bundles screen also allows you to install unbundled components
in addition to the bundles available for the target. Click Select Components to apply individual
components to devices. For more information on selecting bundles or components, see “Selecting
bundles” (page 28) or “Selecting components” (page 29).
The Selection area of the screen displays the following information:
• Target Name—This field displays the name of the target selected for update.
• Status—This field displays the status of the target. The status message “Ready to update”
indicates that at least one update is selected for installation. Status messages about failed
dependencies also appear in this field. To select updates, resolve failed dependencies, or
view device selection problems, click Select Bundles or Select Components. Both links display
a list of all available updates for your targets.
◦ The Select Bundles screen lists updates bundled in release sets first, by bundle, followed
by unbundled updates components. If a bundle is checked, at least one part of that bundle
is selected. Expand the items to view and select or clear the disk controllers and disk
drives available for update.
◦ The Select Components screen lists all available updates separately, whether or not they
are included in bundles. The list has two parts. Updates that are selected to be installed
are listed at the top, followed by any updates that are not selected. You can select or
clear updates in this view, as well as in the Select Bundles view. If a component is part
of multiple bundles, it is only shown once. If there are multiple versions of a component,
Reviewing and installing updates 27

HP SUM adds an expansion box next to the most recent version of the component. To
install an older version of the component, expand the list, and then select the older
component version.
NOTE: If you select individual components from the Select Unbundled Components list
on the Select Bundles screen, these selections are also applied to the Select Components
screen.
• Last Updated—This field displays the last time this target was updated by HP SUM from the
current host running HP SUM.
• Associated Target—This field displays the IP address of the target, if the target is listed on
another server's OA host servers list.
• Description—This field displays a brief description of the target.
Installing updates
Select all targets you want to update, and then click Install to begin installing the updates after
you have resolved all dependency issues. For more information, see “Selecting devices” (page
30).
Aborting an installation
Click Abort Installation once to complete the installation of the current component and abort the
installation of the remaining components.
NOTE: Aborting an installation is only available in online mode.
Viewing failed dependencies

If a failed dependency occurs, you must resolve it by ensuring the prerequisite libraries or the
appropriate software or firmware components are available before proceeding with the installation.
Click Failed Dependencies to see what changes you need to make.
Selecting bundles
The Bundle Components Selections screen displays the following information for a selected target:
• Select Devices—Displays all bundled and unbundled updates you can install on the target.
• Status—Displays whether the target is ready to be updated, or if there are dependencies that
need to be resolved before beginning the update.
• Installed Version—Displays the bundle or component version installed on the target.
• Active Version—Displays the version of the bundle or component that is currently active. This
might differ from the installed version if the bundle or component required a restart, and the
restart has not happened yet.

• Available Version—Displays the newest version available, if it is not active. Some updates
require rebooting the target. If the target has not been rebooted, the new version is installed,
but not yet active.
• Optional—Displays links to actions you can perform to for the target.
◦ Select Devices—Selects devices associated with this target. You can select the bundles
that you want to apply, and view any errors or warnings that might be associated with
the bundle or component.
◦ Installation Options—Open the Install Options screen. For more information about
installation options, see “Installation options” (page 31)
◦ Re-analyze—Can display an error or warning before applying the update. If you see the
same error or warning after correcting the problem, click Re-analyze to run the discovery
process again.
HP SUM automatically chooses and analyzes the newest bundle or component. If you
want to use a different bundle or component, check the bundle or component version you
want to apply, de-select the version you do not want to apply, and then click Re-analyze
to perform discovery and look for any errors or warnings that might affect the installation.
NOTE: If HP SUM shows no devices you can update, you might need to change the types of
updates to use on the Edit Repository screen. For more information, see “Editing the repository”
(page 19).
To select the bundles to update the selected target:
1. Click Select Bundles on the Review/Install Updates screen.
2. Check the bundle that you want to apply to the target.
To update individual components that are not part of a bundle:
1. Click Select Bundles on the Review/Install Updates screen.
2. Click the arrow next to Unbundled Components to expand the list.
3. Check each component that you want to update on the selected target. If there is a dependency
failure, click Failed Dependency to see potential solutions for the component.
NOTE: If you select individual components from the Select Unbundled Components list on
the Select Bundles screen, these selections are also applied to the Select Components screen.
Selecting components
Use this screen to install individual smart components that are not contained in a bundle. You can
choose the devices to update, and choose whether to activate the updates immediately, or wait
until the next scheduled target maintenance.
NOTE: If HP SUM shows no devices you can update, you might need to change the types of
updates to use on the Edit Repository screen. For more information, see “Editing the repository”
(page 19).
1. In the Review/Install Updates screen, click Select Components for a target. The Select
Components screen shows applicable components.
2. HP SUM selects the recommended updates automatically.
3. HP Integrity servers only:
Click Configure Now and then select Upload and Activate to have HP SUM power down the
server to activate the update. To wait until the next scheduled maintenance to activate the
update, select Upload and Do not Activate. This function is supported by HP Integrity servers
only.

4. Check each component that you want to update on the selected target. If there is a dependency
failure, click Failed Dependency to see potential solutions for the component.
NOTE: HP Integrity servers only: If you see an error that reads, "Mismatch Found" or
"Mismatch Found Update Required", click the message to view the Firmware Details or Select
Devices screen. For more information on this error, see “Viewing firmware mismatch details
(HP Integrity servers only)” (page 31).
5. Click OK.
Selecting devices
On the Select Devices screen, select the devices on the target that you want to update. You can
also review any dependency problems that need to be resolved before HP SUM begins the update
installation.
NOTE: HP Integrity servers only: Some targets that are part of a domain allow you to update the
entire domain at the same time. If you do not want to update the entire domain at once, select the
check box next to the partitions you want to update.
To select devices:
1. To reach the Select Devices screen, click Select Devices on the Select Bundles or Select
Components screen.
2. Select the check box for the device that you want to update. The Status field displays messages
about the selected device. If you cannot update a device, the Status field displays a brief
explanation.
NOTE: HP Integrity servers only: If a multi-blade server displays a Mismatch Firmware

or Mismatch Firmware Update Required error, HP SUM resolves the mismatch as part
of the update when you click Install. For more information on a firmware mismatch, see
“Viewing firmware mismatch details (HP Integrity servers only)” (page 31).
3. View any errors or warnings displayed at the bottom of the screen. Correct errors before
continuing. HP SUM cannot proceed with updates until you resolve the errors. Warnings do
not prevent the installation, but continuing an installation without correcting the problem that
caused the warning might cause more serious problems. To continue without resolving the
warnings, select Ignore Warnings.
4. After you have selected the devices, click OK to exit this screen.
Viewing firmware details

You can view the firmware detail screen from these screens:
• Review/Install Updates
• Select Bundles
• Select Components
To open the view firmware details, do one of the following:
• Click Installed Version on the Select Bundles or Select Components screen.
• HP Integrity servers only: Click Mismatch Found on the Review/Install Updates screen, if
displayed.
The View Firmware Details screen provides information about:

Table 1 View Firmware Details screen
HP ProLiant servers HP Integrity servers
SPP version Bundle version
NIC version iLO version (NIC version on HP–UX servers)
Firmware version Power Monitor firmware version
Component versions System firmware version
Bundle version FPGA firmware version
• Bundle version
NOTE: The bundle version is only displayed if all four firmware versions match a known
bundle. If there is no known bundle, HP SUM will display Unknown.
• iLO firmware version

• Power Monitor firmware version
• System firmware version
• FPGA firmware version
Viewing firmware mismatch details (HP Integrity servers only)

If you have a multi-blade server, you might encounter a situation where you have blades or partitions
that are running different firmware versions. As part of the update procedures, HP SUM will notify
you that there is a firmware mismatch by displaying either Mismatch Found or Mismatch
Found Update Required. Click the message to go to the View Firmware Details screen, where
you can view the mismatch details. HP SUM will resolve the firmware mismatch when it installs the
new updates.
Installation options
CAUTION: The ability to force the installation of components is generally unnecessary and is not
recommended. Incorrect use could result in data loss or system failure or both.
If you set the installation options from the Review/Install Updates screen, you set these options for
all the targets. If you want to set installation options for specific targets, click Select Bundles or
Select Components for the target, and then click Installation Options for the target.
1. Click Installation Options.
2. Click Check here to enable force options.
3. Do one of the following:
• Click Downgrade or Rewrite, depending on whether you want to downgrade the firmware
version, or overwrite the current firmware version.
• Force upgrade bundles, firmware, or software.
◦ Bundles—Selects older firmware bundles.
◦ Firmware—Selects older firmware components.
◦ Software—Selects older software bundles.
NOTE: You cannot use HP SUM to downgrade a Virtual Connect, Ethernet, or Fibre
Channel module

Reboot options
If you set the reboot options on the Review/Install Updates screen, they are set for all the targets.
If you want to set the reboot options for only specific targets, click Select Bundles or Select
Components for the target, and then click Reboot Options for the target.
NOTE: For Superdome 2 servers, the reboot options are set for each partition on the Select
Devices screen. HP SUM does not support global reboot options for Superdome 2 servers.
To set the reboot options:
1. Click Reboot Options.
2. Check Reboot System After Installation to set the reboot.
3. Check If Needed or Always.
4. Click OK.
NOTE: Reboot Delay and Reboot Message do not apply for HP Integrity iLO or HP
Superdomes 2 servers.
Scheduling updates
Usethese steps to schedule a time to run the updates.
1. Click Schedule Update.
2. Click Create Schedule, type a schedule name, and then click OK.
3. Select the targets or groups from the Unscheduled Targets list, and then click Add.
4. Select a date and time to start the updates. Check UTC if you want to use Coordinated Universal
Time, and not the time zone listed in the Time Zone field.
5. Click Save and Continue, click Done, and then click OK. If you click the X to close the window
will not save the schedule.
6. The schedule details are updated in the Target Status.
7. The schedule is completed when you click Install on the Review/Install Updates screen.
NOTE: If the Install button is grayed out, make sure you enter all required information on
the Review/Install Updates screen. For more information, see “Reviewing and installing
updates” (page 27).
NOTE: Schedule settings might be lost if the HP SUM session is closed. HP recommends
not to exit from an HP SUM session if a scheduled update has been set.
Generating and viewing reports

You can generate a report file in HTML, XML, or CSV format that details the repository contents,
target firmware, target installable details, failed dependencies, and installed items details. You
can view HTML and XML files in a web browser, such as Microsoft Internet Explorer. The reports
support JavaScript-enabled web browsers Internet Explorer 6.0 or Mozilla Firefox 3.5 and later.
The XML reports also allow you to write programs to pull the report information and display it in
other locations. You can view CSV reports in any application that supports the CSV format.
NOTE: Not all reports are available on all screens. If a report is not available, HP SUM grays
out the report.
Generating a Report
1. Click Generate Report.
2. Click the Browse button and then select the directory where you want to save the report.

3. Choose the topic you want to view in the report. Topics that are not valid are grayed out. The
Report name will be displayed next to the report selected once it is checked.
• Inventory selections–Provides details of the contents in all selected repositories.
• Target Firmware details–Provides firmware versions for the selected targets. You can
generate this report after you have entered the target credentials and HP SUM completes
the discovery process on the Select Targets screen.
• Target Installables details–Provides a list of updates available for the selected targets or
devices. HP SUM will collect all the information available for this report on the
Review/Install Update screen.
• Failed Dependency details–Provides details on any failed dependencies that will prevent
an update from succeeding.
NOTE: The Failed Dependencies Report is automatically generated when you generate
a Target Firmware details or Target Installable details report.
• Installed details–Provides details on the updates that HP SUM installed in this session.
4. Choose the type of report to generate:
• HTML
• XML
• CSV
5. HP SUM selects the View generated report box by default. If you do not want to view the
report immediately, clear this box.
6. Click Generate.
NOTE: HP SUM requires AMS to detect server IP addresses.
Viewing a report
1. Click View Report.
2. Click the Browse button and then select the report you want to view, and then click View.
Generating and viewing reports 33

3 Using scripts to deploy updates
Command-line interface
You can use the HP SUM command-line interface to script custom installations.
Command-line syntax
The general command-line syntax for HP SUM is as follows:
hpsum [/h[elp]] [/?] [/f[orce]] [/f[orce]:bundle] [/f[orce]:rom]
[/f[orce]:software] [/f[orce]:all ] [/g (/downgrade)] [/e (/rewrite)
[/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] [/nomgmt]
[/use_snmp] [/use_wmi] [/use_ams][/romonly] [/softwareonly] [/dryrun]
[/continue_on_error <error>] [/override_existing_connection]
[/express_install] [/user <username> or /username <username>] [/passwd
<password>] [/current_credential] [/target "netAddress"] [/targettype
“type of target” ] [/logdir "path"] [/v[erbose]] [/veryv[erbose]]
[/report][/inventory_report] [/firmware_report]
[/On_failed_dependency:<parameter>] [/oa_username <username>]
[/oa_password <password>] [/use_proxy <proxy server>] [/proxy_script
<proxy script>] [/proxy_user <username>] [/proxy_passwd
<password>][/inputfile "filename"] [/c[omponent]
<component_to_install>][<component1_to_install> <component2_to_install>
...][<bundle1_to_install> <bundle2_to_install>...] [/su_username]
[/su_password] [/use_sudo] [/auth_key]
The following commands are supported only by Superdome 2 servers:
[/update_type <type>] [/device_list <device[,device]…>] [/reboot_list
<npar[,npar]…>]
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 parameters and information enclosed in brackets are optional. The parameters may
be prefixed with either a hyphen (-) or slash (/) character. These examples show only the slash.
On Windows, use a slash before each argument. On Linux, use a hyphen before each argument.
If the /s[ilent] argument is not included on the command line, the HP SUM GUI appears.
NOTE: Command-line syntax does not support double-byte character sets. Any messages entered
through the command line via a double-byte character set will not be displayed correctly.
NOTE: /targettype is an optional command line argument. Use /targettype and /target
together.
Using Linux root credentials

If you run HP SUM from a Linux system where you have not logged in to the system as a root user,
you can still update targets from the CLI if you use Linux root credentials.

Prerequisites for using Linux root credentials
• If you have run HP SUM as a root user, remove the temp directory created by HP SUM.
• Make sure you have read/write access permissions to the /tmp and /var directories.
• If you create a sudo user, make sure that you add that user to the /ect/sudousers file. The
following table shows the privileges and specifications for users.
User Privilege Specification
Root ALL= (ALL) ALL
Sudo_user ALL= (ALL) ALL
Switch update commands

G7 and earlier servers do not support AMS agents. The following tables show what updates occur
when you use the switch agent commands.
NOTE: To find out if you have any switches installed, use HP SUM to create the Target Firmware
Details Report.
The following table shows what updates occur if no switches are currently installed.
Command G7 and earlier servers Gen8 servers
no switches SNMP AMS
/no_mgmt Nothing Nothing
/use_ams Nothing AMS
/use_snmp SNMP SNMP
/use_wmi WBEM WBEM
/use_ams /use_snmp SNMP AMS and SNMP
/use_ams /use_wmi WBEM AMS and WBEM
/use_wmi /use_snmp WBEM and SNMP WBEM and SNMP
/use_ams /use_wmi /use_snmp WBEM and SNMP AMS, SNMP, and WBEM
The following table shows what updates occur if SNMP switches are currently installed.
no switches SNMP SNMP
/use_ams SNMP SNMP and AMS
/use_snmp SNMP SNMP
/use_wmi WBEM and SNMP WBEM and SNMP
/use_ams /use_snmp SNMP AMS and SNMP
/use_ams /use_wmi WBEM and SNMP AMS, SNMP, and WBEM
Command-line interface 35
The following table shows what updates occur if WBEM switches are currently installed.
no switches WBEM WBEM
/use_ams WBEM WBEM and AMS
/use_snmp WBEM and SNMP WBEM and SNMP
/use_wmi WBEM WBEM
/use_ams /use_snmp WBEM and SNMP AMS, SNMP, and WBEM
/use_ams /use_wmi WBEM WBEM and AMS
The following table shows what updates occur if AMS switches are currently installed.
no switches N/A AMS
/use_ams N/A AMS
/use_snmp N/A AMS and SNMP
/use_wmi N/A AMS and WBEM
/use_ams /use_snmp N/A AMS and SNMP
/use_ams /use_wmi N/A AMS and WBEM
/use_wmi /use_snmp N/A AMS, SNMP, and WBEM
/use_ams /use_wmi /use_snmp N/A AMS, SNMP, and WBEM
NOTE: G7 and earlier servers do not support AMS.
Command-line arguments
HP SUM recognizes the following command-line arguments, which you can use to pre-populate
the GUI on the Source Selection and Review/Install Updates screens. If you specify the target and
credentials, use the /s[ilent] parameter to proceed with the installation.
You cannot use some arguments, such as /romonly and /softwareonly, together.
Help Description
/h[elp] or /? Displays command line help information.
Installation options Description
/f[orce] Overrides or downgrades an existing component

installation. This produces the same results as
/f:software.
/f[orce]:bundle Overrides or downgrades the existing installation of

components in the selected bundle.
/f[orce]:rom Overrides or downgrades the existing installation of the

selected firmware components (applies to firmware only).

/f[orce]:software Overrides or downgrades the existing installation of the

selected software components.
/f[orce]:all Overrides or downgrades the existing installation of the

selected software components, firmware components, and
bundles.
/g or /downgrade Downgrades to an earlier version of firmware for

multi-target devices such as hard drives and array
controllers (applies to firmware only).
/e or /rewrite Rewrites the current version of firmware for multi-target

devices such as hard drives and array controllers (applies
to firmware only).
/s[ilent] 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), the
component installation fails, and an error message writes
to the log file.
Failed dependencies are not reported to the user when you
are using the /s[ilent] argument. To check for failed
dependencies, remove the /s[ilent] argument and
reissue the command line. The HP SUM GUI appears.
/c[omponent]<component_to_install> or Specifies which components to install. Components to install

<component1_to_install> can be specified with or without the /c[omponent]
<component2_to_install> argument.
• If you are using the /c[omponent] argument, then
only one component can specified with the argument.
However, multiple /c arguments and components can
be specified on the same line.
• If you do not use the /c[omponent] argument, 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 you are mixing
components and bundles on the command line, the filter
switches control what components and bundles are
installed.
• HP SUM only uses the component name. If you type the
entire directory path, HP SUM will ignore the path. If
you use /use_location and /c, HP SUM checks
both the default repository and the directory provided.
/group "group_name" This argument specifies an already defined group name

in the HP SUM GUI.
/b[undle] <bundle_to_install> or This argument specifies bundles to install. Bundles to install

<bundle1_to_install> can be specified with or without the /b[undle] argument.
<bu/use_latestndle2_to_install> • If you are using the /b[undle] argument, only one
bundle can specified with the argument. However,
multiple /b arguments and bundles can be specified

on the same line.
• If you do not use the /b[undle] argument, multiple
bundles can be specified at the same time, but the
bundles must be separated by a blank and listed after
all the arguments on the command line.
/allow_update_to_bundle This argument is a filter switch. It enables you to install

newer versions of components defined in a PSP, ISP, or
firmware bundle.
This argument enables these components to replace the
older versions of the same component that might have
shipped with the bundles.
/allow_non_bundle_components This argument is a filter switch. It enables you to install

components that are 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 the latest version of the bundle to be
used 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 that has the latest version for installation.
/use_location "file_share" Specifies a directory or file share that contains the SPP, HP
Integrity Smart Update Firmware Bundles, and components
for use with HP SUM. The file_share format must be a
mapped file share or UNC format. If this argument is not
specified, the directory that contains hpsum.exe or HP
SUM is used by default.
The logged-in account must have access to this location.
The /user and /passwd arguments do not have any
effect when you are attempting to access the file share.
Use those arguments only when you are connecting to a
target system.
/use_web Specifies that the check box for Check ftp.hp.com on the
Source Selection screen is selected. This enables
components to be retrieved from ftp.hp.com and used in
the list of possible updates.
/use_proxy <Proxy server> Enables the inclusion of a proxy server (and port number)
to access ftp.hp.com. This parameter must be used with
/use_web. For example, /use_web /use_proxy
<1.22.33.44:80>.
/proxy_script <Proxy script> Enables the inclusion of a proxy script to access ftp.hp.com.
This parameter must be used with /use_web. For example,
/use_web /proxy_script <autoproxy.com>.
/proxy_password <password> Sets the password to be used for an authenticating proxy

server.
/use_d[ownloaded] Specifies that the check box for Use last downloaded
repository from ftp.hp.com on the Source Selection screen
in the GUI is selected. This enables the previously
downloaded components to be included in the list of
possible updates.
/no_mgmt Specifies that AMS, SNMP, and WBEM Providers

management components are optional on the Components
Selection screen. In silent mode, HP SUM will not update
any management components.

/use_snmp Specifies that components that use SNMP protocol and the
AMS components are available for installation by default.
When the /use_snmp argument is used, the AMS
components are required, but the WMI components are
optional.
/use_wmi Specifies that components that use the WMI protocol are
available for installation. These components are optional
and are not installed unless this argument is used. When
the /use_wmi argument is used, and the /use_snmp &
/use_ams arguments are not, the SNMP and AMS
components are optional. This argument does not apply
to HP Integrity servers.
/use_ams Specifies which AMS components can be installed along

with SNMP components. The AMS and SNMP components
are available to select by default. When the /use_ams
argument is used, the SNMP components are required,
and the WMI components are optional.
/romonly This filter switch allows you to see only the firmware
components needed for installation. When you are using
this filter switch, you must exit and restart HP SUM if you
want to return to an unfiltered state.
Do not use the /romonly argument with the
/softwareonly argument. (Applies to firmware only.)
/softwareonly This filter switch allows you to see only the software
components needed for installation. When you are using
this filter switch, you must exit and restart HP SUM if you
want to return to an unfiltered state.
Do not use the /softwareonly argument with the
/romonly argument.
/express_install Starts an express installation for the local host only. HP

SUM performs discovery, installation, and exits without
user interaction. You can cancel or terminate HP SUM.
Overriding errors Description
/tpmbypass or /ignore_tpm Specifies that if a TPM is enabled, the warning message

should be ignored and component installation can continue.
For more information about TPM, see “Disabling BitLocker
to permit firmware updates” (page 13).
/ignore_warnings Allows the installation to proceed on a Superdome 2 target

even when warnings are returned during analysis.
/continue_on_error <error> Causes the installation to continue and ignore errors. Valid
values are as follows:
* <error>=ServerNotFound and
* <error>=BadPassword.
* <error>=FailedDependencies
You can use the ServerNotFound option to bypass
inactive or unavailable remote hosts when you are
deploying firmware or software to multiple remote hosts at
the same time.
/override_existing_connection Defines the behavior when a remote target has an existing

HP SUM session in progress. It overrides the session in
progress and re-initializes the installation framework on
the remote host.
Overriding errors Description
/On_failed_dependency: <parameter> Provides HP SUM <parameter> the information on how to

proceed when a component has a failed dependency. The
supported parameters for this argument are Omit_Host
(default), Omit_Component , and Force. Omit_Host
causes the host to be put into a failure state, and no
installation is attempted. Omit_Component deselects the
affected components and proceeds with any updates that
do not have dependency failures. Force attempts all
updates, even if they have dependency failures.
/partition_only Use this argument to select a partition to update.

This command is for HP Integrity servers only.
/oa_name and /oa_password Use these arguments if you do not use the
/partition_only argument. If you do not enter the
selections, then the update will display and error and exit.
This command is for HP Integrity servers only.
Reboot options Description
/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
installed.
• At least one of the installed components requires a
reboot to complete its installation.
/reboot_message "reboot message" Displays the specified reboot message on remote consoles
connected to the server that you want to reboot. You must
use this argument with the /reboot option, or the
argument is ignored.
/reboot_delay timeout_in_secs Delays the reboot of the server for the length of time that
the timeout_in_seconds variable specifies. You must
use this argument with the /reboot option, or the
argument is ignored. Acceptable values are between 15
and 3600.
• The default timeout value is 15 seconds for Microsoft
Windows operating systems and 60 seconds for Linux.
• For Linux, the reboot delay time is converted from
seconds to minutes, and any value under a full minute
(59 seconds or less) rounds to the next minute.
/reboot_always If the following conditions are met, 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.
Simulating HP SUM Description
/dryrun Simulates the installation for a test run. Nothing is installed.

Targets Description
/user<username> or /username <username> Use this argument to log in to the remote targets by using
the user ID. For the OA target, use the /oa_username
argument.
The user name needs to belong to the root or administrator
group.
/psswd <password> Use this argument to use this password for the user ID
specified in the /user parameter (except for the OA
target). The password is used to log in to remote targets.
For the OA target, use the /oa_password argument.
/su_username Use root (super user) or sudo credentials username to start

a session, and discover and update components when the
credentials specified in /username and /passwd do not
have root privileges to update components. When you
specify /use_sudo, /su_username is considered as a
sudo username.
When you do not specify /use_sudo, /su_username
is considered a root (super user) username.
NOTE: To use the Linux root credential functionality, you
must pass the target type /TARGETTYPE =Linux.
/su_password Use root (super user) or sudo credentials password to start

a session, and discover and update components when
credentials specified in /username and /passwd do not
have root privileges to update components. When you
specify /use_sudo, /su_passwd is considered as sudo
password.
When you do not specify /use_sudo, /su_username
is considered a root (super user) username.
must use the target type /TARGETTYPE =Linux.
/use_sudo Specifies that /su_username and /su_passwd are sudo

/auth_key or root (super user) credentials.
When you specify /use_sudo in the CLI along with
/su_username and /su_passwd, then /su_username
and /su_passwd are considered as sudo credentials.
When you do not specify /use_sudo in the CLI,
/su_usename and /su_passwd are considered as root
credentials.
When you specify /use_sudo in the CLI, and
/su_username and /su_passwd are not specified, then
/username and /passwd are considered as sudo
credentials.
Accepts the private keys.pem to authenticate as ssh.
Regular user enter in the target details the location where
the key.pem to hold that value for the authentication.
/target “netAddress” This is the IP address or the DNS name of a remote host,
which can be a remote server, remote iLO NIC port, Virtual
Connect Ethernet or Fibre Channel Module for c-Class
BladeSystem, or BladeSystem OA.
Targets Description
When two OAs are in an enclosure, this argument should

be the active OA. When specifying the IP address, use
either the IPv4 or IPv6 format.
/targettype Reduces discovery time for scripted deployments. This is

an optional command line argument.
The following are valid target types:
• Server
• Windows
• Linux
• HPUX
• EVA or Command View for EVA
• FC Switch or Fibre Channel Switch
• OA or Onboard Administrator
• SUPERDOME 2 or SUPERDOME2 or Superdome 2
Onboard Administrator
• iLO
• VC or Virtual Connect
• HP SAS or HP SAS B/L Interconnect Switch
• VMware or VMware Host
• iPDU or Intelligent Power Distribution
Unit (iPDU)
Use /targettype with /target parameter. You can
interchange the sequence of /targettype and /target.
If the target name includes spaces, make sure you enclose
the name in quotation marks, “ “.
/current_credential Enables the credential of the local host to be used as the

credential to access the targets instead of providing the
user name and password explicitly for each target. The
assumption is that the current credential is valid for the
targets being accessed. (Applies to Windows only)
/oa_username This argument provides the user name credential for OA

associated with VC specified with the target
command-line parameter. Only one set of OA credentials
can be specified with command-line parameters. You can
add multiple VC targets to command-line parameters with
the target parameter only if the credentials of OAs
associated with specified VCs are the same. The argument
oa_username is not required if VC has the same
credentials as the associated OA. You do not need to
provide an OA network address associated with VC. HP
SUM queries it from a specified VC target.
To update multiple VCs with different user names and
passwords, or VCs with OAs that have different credentials,
use the corresponding input files OAUID and OAPWD.
/oa_password Provides the password credential for OA associated with

VC specified with the "target" command-line parameter.
Only one set of OA credentials can be specified with
command-line parameters. You can add multiple VC targets
to command-line parameters with the "target" parameter
only if the credentials of OAs associated with specified
VCs are the same. The argument oa_password is not
required if VC has the same credentials as the associated
OA. You do not need to provide an OA network address

Targets Description
associated with VC. HP SUM queries it from a specified

VC target.
To update multiple VCs with different user names and
passwords, or VCs with OAs that have different credentials,
use the corresponding input files OAUID and OAPWD .
Log files Description
/logdir “path" Redirects 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[erbose] Sets the verbosity level for the HP SUM execution log file,
hpsum_execution_log_<date>_<time>.log. It
increases the level of detail that is retained in the log file.
The default value is normal verbosity.
Generating reports Description
/report Generates a report listing of the target summary and

describes how the components in the repository affect the
target; for example, whether each component applies to
the target. The report is generated in HTML and XML with
file name formats of
HPSUM_Report_<date>_<time>.html and
HPSUM_Report_<date>_<time>.xml.
By default, the files are located in the present working
directory where HP SUM is initiated. If that location is
write-protected, you can find the files in the same directory
as the HP SUM log files.
/inventory_report Generates a report listing of the components in the

specified repository. The report is generated in HTML and
XML with file name formats of
HPSUM_Inventory_Report_<date>_<time>.html
and
HPSUM_Inventory_Report_<date>_<time>.xml.
By default, the report is located in the present working
write-protected, you can find the report in the same
directory as the HP SUM log files.
/firmware_report Generates a report listing of the firmware installed and

details of the target. The report is generated in HTML and
XML with file names of HPSUM_Firmware_Report.html
and fwreport.xml in the directory named
HPSUM_Firmware_Report_<date>_<time>.
By default, the report is located in the present working
write-protected, you can find the report in the same
directory as the HP SUM log files.
:
HP SUM does not install any updates when you generate a report.
Using input files Description
/inputfile “filename” Enables you to script the deployment of firmware and

software to multiple remote systems at one time. For more
information, see “Input files” (page 48).
/deleteinputfile Enables you to instruct HP SUM to delete the input file after
it has been read.
Superdome 2 server commands Description
/update_type <type> Determines which Superdome 2 firmware is updated. You

can choose ALL, COMPLEX, or PARTITIONS. The default
selection is ALL.
Example: /update_type PARTITIONS
/device_list <device[,device]…> Use this argument when the /update_type argument is

PARTITIONS. This argument specifies the subset of
partitions or blades to update when you do not want to
update all partitions or blades. Valid devices are:
npar(number) and blade(enc)/(bay). Do not put
any spaces between the parameters.
Example: /device_list
npar1,npar2,blade1/1,blade1/2
/reboot_list <npar[,npar]…> Use this argument when the /update_type is ALL or

PARTITIONS. This argument specifies specific partitions
to reboot after the partition firmware has been updated.
Valid npar values are npar(number). Do not put any
spaces between parameters.
Example: /reboot_list npar1,npar2
Component configuration for Windows components only

To configure components without using the HP SUM GUI, issue the command
hpsum_config<component_to_configure>. This command presents the same configuration
screens that appear in the HP SUM GUI. Run this command from a writeable media source.
Configuration for a given component must be executed only one time. The configuration is stored
within the component and is propagated to all target servers when it is deployed through the HP
SUM GUI or a command line. To change the configuration, rerun hpsum_config against the
component. If a component does not need configuration, the hpsum_config command returns
to the console.
To configure components to be deployed on all editions of Windows Server 2008 with the Server
Core option, you must access the system as a remote host by using HP SUM running on a system
with a supported Windows operating system, and then configure the components before deployment.
Command-line examples
The following command-line parameter examples can be executed within these environments:
• Firmware:
◦ System ROM
◦ Smart Array controller

◦ Hard drives
◦ iLO
• Software—later version of:
◦ HP Insight Diagnostics Online Edition for Windows Server 2003 (cp008097.exe)
◦ HP System Management Homepage (HP SMH) for Windows (cp008257.exe)

• HP SUM
◦ Defined groups: Management Servers—three servers (Management Server1, Management
Server2, Management Server3)
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 and firmware components from the update bundle, which HP
SUM determined must be installed, were installed.
Example 2:
Either of the following command-line inputs can deploy the previous version of the PSP only and
force all the components to be installed:
• hpsum /f:bundle /softwareonly BP000315.xml
• hpsum /b BP000315.xml /f:bundle /softwareonly
Results: All software components and firmware components from the update bundle, which HP
SUM determined must be installed, were installed. No firmware was installed.
Example 3:
This command-line input deploys firmware:
hpsum /romonly
Results: All firmware components that must be installed, were installed. No software was installed.
Example 4:
Either of the following command-line inputs can deploy two software components:
• hpsum /f:software cp008097.exe cp008257.exe
• hpsum /c cp008097.exe /c cp008257.exe /f:software
Results: The two components were installed. No firmware or other software was installed.
Example 5:
Either of the following command-line inputs can deploy the latest PSP, later versions of components
in the bundle, and firmware to three remote hosts and force all components to be installed:
• hpsum /group "Management Servers" /current_credential /use_latest
/allow_update_to_bundle /allow_non_bundle_components /force:all
/override_existing_connection /continue_on_error ServerNotFound
/silent /logdir "Management_Server_Files"
• hpsum /target "Management Server1" /target "Management Server2"
/target "Management Server3" /user administrator /passwd letmein
/use_latest /allow_update_to_bundle /allow_non_bundle_components
/force:all /override_existing_connection /continue_on_error
ServerNotFound /silent /logdir "Management_Server_Files"
Results: All software components and firmware components from the update bundle,
cp008097.exe, and cp008257.exe were installed on Management Server1, Management
Server2, and Management Server3.
Return codes
HP SUM has consolidated return codes from Linux and Windows smart components into a new,
enhanced return-code mapping. These return codes determine the status of the component
installation. You can also use return codes in a script to control the execution of the script and
determine any required branching.
In Linux, the negative return codes are reported. These return codes are determined by subtracting
the negative value from 256.
Return code Value Linux VMware Windows Text

ESXi 5.0
or later
SUCCESS_NO_REBOOT 0 0 0 0 The installation was successful.
SUCCESS_REBOOT 1 1 1 1 The installation was successful,

but a reboot is required.
SUCCESS_NOT_REQUIRED 3 3 3 3 The component was current or

not required.
FAILURE_GENERAL -1 255 255 255 A general failure occurred. For

details, see the error log.
FAILURE_BAD_PARM -2 254 254 254 A bad input parameter was

encountered.
FAILURE_COMPONENT_FAILED -3 253 253 253 The installation of the

component failed.
Windows smart-component return codes
Error level Meaning
0 The smart component was not installed. For more

information, see the log file.
1 The smart component was installed successfully.
2 The smart component was installed successfully, but the

system must be restarted.
3 The installation was not attempted because the required

hardware is not present, the software is current, or there
is nothing to install.
Linux smart-component return codes

Single-target servers:
Error level Meaning
0 The smart component was installed successfully.
1 The smart component was installed successfully, but the

system must be restarted.

Error level Meaning
2 The installation was not attempted because the required

hardware is not present, the software is current, or there
is nothing to install.
3 The smart component was not installed. For more

information, see the log file.
Multi-target servers:
Error level Meaning
0 The installation of the deliverable was successful. No reboot

is required.
1 The installation of the deliverable was successful. Reboot

is required for the deliverable to be enabled.
2 The installation was not attempted because the version to

be installed matches the version already installed.
3 The installation was not attempted because of one of the

following:
• The version to be installed is older than the version
already installed.
• The supported hardware is not present, not enabled,
or in a state that an installation could not be attempted.
• The smart component does not support the environment.
• There is nothing for the component to accomplish.
4 If the component is being installed to a remote target, such

as an OA or other network-based deployment, this return
code indicates that the target cannot be found.
5 A user canceled the installation before anything could be

installed.
6 The installer cannot run because of an un-met dependency

or installation tool failure.
7 The actual installation operation (not the installation tool)

failed.
Linux RPM return codes
Error level Meaning
0 The Linux RPM installation was successful.
1 The Linux RPM installation failed.
VMware ESXi smart-component return codes
Error level Meaning
0 The installation of the deliverable was successful. No reboot

is required.
1 The installation of the deliverable was successful. Reboot

is required for the deliverable to be enabled.
2 The installation was not attempted because the version to

be installed matches the version already installed.
Error level Meaning
3 The installation was not attempted because of one of the

following:
• The version to be installed is older than the version
already installed.
• The supported hardware is not present, not enabled,
or in a state that an installation could not be attempted.
• The smart component does not support the environment.
• There is nothing for the component to accomplish.
4 If the component is being installed to a remote target, such

as an OA or other network-based deployment, this return
code indicates that the target cannot be found.
5 A user canceled the installation before anything could be

installed.
6 The installer cannot run because of an un-met dependency

or installation tool failure.
7 The actual installation operation (not the installation tool)

failed.
Input files
HP SUM provides the ability to script the update of multiple, individual targets or groups of targets
(HP ProLiant and Integrity servers and options) within a single operation through the input file
functionality. To protect your credentials, use a secure server or a management console.
To create an input file, use a text editor. All section headers and trailers must match. Failure to use
the SILENT=YES option causes the GUI mode to be used, but the information provided enables
you to skip screens where information has already been provided. You can use the DRYRUN=YES
option to perform dry runs of installations to ensure the scripts are working without deploying the
firmware updates that might be required on each target. Remove the DRYRUN=YES option to
perform the updates.
For parameters that can take list values, list separators can be commas, semicolons, or spaces.
NOTE: The credentials can be omitted from the file for greater security and passed on the
command line to HP SUM. The only limitation that the user ID and credentials must be the same
on all.
When the file has been created, to use it with HP SUM, add it as the inputfile <filename>
parameter to a HP SUM command line. For example, if the name of the input file is hpsum.in,
the command-line syntax is hpsum -inputfile hpsum.in. Full paths can be added to the
input file location if the file is not stored in the same location as the HP SUM executable files. The
<filename> field can be enclosed in double quotes to enable paths with spaces. Also, the input
file itself might contain the same options on the command line. The usual command-line options
can still be used with the -inputfile option and they take precedence over any given input file.
Input file format and rules

The input file is divided into two sections:
• Configuration
The configuration section starts from the beginning of the file and proceeds until the first target
section is encountered. This section consists of a number of settings and their values. Each
configuration setting must appear on a fresh line in the file, along with its value. Comments

start with a pound (#) character at the beginning of the line. Only one pound character is
allowed on any line.
• Target
You can provide remote host targets to HP SUM. This section can repeat any number of times
in the input file, providing a way to organize targets in related sets.
The section starts with the following special header enclosed in brackets:
[TARGETS]
The section ends with the following special string enclosed brackets:
[END]
The keyword TARGETS can be suffixed with an optional arbitrary string. This string enables
you to tag the purpose of the TARGETS section. Other than the visible difference in the header,
the contents of such a section are not treated any differently. For example:
[TARGETS_WIN2003]
...
[END]
◦ Credentials: The TARGETS section allows the targets to be grouped according to the
credentials needed for logging in remotely. Each TARGETS section must have a set of
login credentials, which applies to all targets in that section. If you want to use the current
host's login credentials to log in to one or more remote targets, you can do so by setting
the variable USECURRENTCREDENTIAL to YES. You can supply login credentials for
one or more hosts by using the variables UID and PWD. If you want to provide the variables
at the beginning of a TARGETS section, use both of them. If you want to provide the
variables in the middle of a TARGETS section, use one or the other to override the selected
variable and continue using the active value for the remaining variable.
◦ Remote target: You can specify a remote target by using the variable HOST. Possible
values are a DNS name or an IP address.
File encoding
To allow for the inclusion of double-byte characters, the input file is in UTF-8 format.
Error reporting
If errors occur in the input file, HP SUM exits with a return value of –2 (bad parameter). The details
of the location and nature of the error are recorded in
hpsum_execution_log_<date>_<time>.raw.
Input files 49
Input file parameters
Parameter Description Possible values
SILENT This parameter causes the installation YES, NO

to run silently without GUI or console
output. All data is written 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), the component
installation fails (unless the
IGNOREERRORS =
"FailedDependencies" parameter is
supplied), and an error message is
written to the log file.
TARGETTYPE This parameter specifies the target /targettype vc

type and can shorten the discovery The following are valid target
process. types:
• Server
• Windows
• Linux
• HPUX
• EVA or Command View for
EVA
• FC Switch or Fibre
Channel Switch
• OA or Onboard
Administrator
• SUPERDOME 2 or
SUPERDOME2 or Superdome
2 Onboard Administrator
• iLO
• VC or Virtual Connect
• HP SAS or HP SAS B/L
Interconnect Switch
• VMware or VMware Host
• iPDU or Intelligent
Power Distribution Unit
(iPDU)
If you use the command with a
group, the HP SUM assumes all
targets in the group are the same
target type.
FORCEALL Forces updates to both firmware and YES, NO

software components.
FORCEROM Forces updates to firmware YES, NO

components.
FORCESOFTWARE Forces updates to software YES, NO

components.
FORCEBUNDLE Enables you to override or downgrade YES, NO

an existing installation of components
in the selected bundle.

DOWNGRADE Downgrade to an earlier version of YES, NO

firmware for multi-target devices such
as hard drives and array controllers.
(Applies to firmware only.)
REWRITE Rewrite the same version of firmware YES, NO

only for multi-target devices such as
hard drives and array controllers.
(Applies to firmware only.)
REBOOTALLOWED Enables you to reboot, if required. YES, NO
REBOOTMESSAGE Create a message to be displayed Any string (not exceeding 256

prior to rebooting. characters)
REBOOTDELAY Delay before rebooting. Time in seconds
COMPONENTSLIST Limit the list of components to be Component names with file

updated. extensions (.exe, .rpm, or .scexe)
BUNDLESLIST Limit the list of bundle xml files to be Bundle file names
filtered.
ALLOWUPDATEBUNDLE This is a filter switch and enables you YES, NO

to install newer versions of
components defined in a PSP, ISP, or
bundle.
This parameter enables these
components to replace the older
versions of the same component that
might have shipped with the bundles.
SKIPTARGET Defines the behavior when a remote YES, NO

target has an existing HP SUM session
in progress.
Use this parameter to skip the host if
an existing HP SUM session already
exists. A value of NO overrides the
session in progress and reinitializes
the installation framework on the
remote host.
IGNOREERRORS Causes the installation to continue and ServerNotFound, BadPassword,

ignore errors. FailedDependencies
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.
Use FailedDependencies to
ignore any failed dependencies and
proceed with the ones that are ready
to be installed.
SOURCEPATH Provide a single local repository path. Directory path

This action creates an inventory from
the given path instead of the local or
default repository.
USELATEST This is a filter switch for use with YES, NO

bundles. The parameter enables you
to use the latest version of the bundle
when multiple versions of bundles are
listed on the command line.
Input files 51
If no bundles are specified on the

command line, and multiple bundles
are in the directory, this parameter
enables HP SUM to use the bundle
that has the latest version for
installation.
DRYRUN Simulates the installation for a test run. YES, NO

Nothing is installed.
OPTIONS Specify the HP SUM CLI options inside One or more CLI switch
the input file, which overrides the
configuration settings. Parameters can
be separated by a semi-colon, comma,
or a space.
This parameter replaces the
LSPOPTIONS parameter that was
previously supported with LDU.
NOMGMT Specifies that components that use Yes

SNMP, AMS, and WBEM Providers No
listed as optional updates on the
Components Selection screen.
In silent mode, HP SUM does not
update SNMP, AMS, or WBEM
Providers.
USESNMP Specifies that components that use YES, NO

SNMP protocol, are available to be
selected for installation.
These components are available for
selection by default. When the
/usesnmp parameter is used, and the
/usewmi parameter is not used, the
WMI components are optional. This
parameter does not apply to HP
Integrity servers.
USEWMI Specifies that components that use YES, NO

WMI protocol are available to be
selected for installation.
These components are optional by
default and are not installed unless this
parameter is used. When the
/usewmi parameter is used, and the
/usesnmp parameter is not used, the
SNMP components are optional. This
parameter does not apply to HP
Integrity servers.
ROMONLY This is a filter switch that allows you YES, NO

to view only the firmware components
required for installation.
Do not use the /romonly parameter
with the /softwareonly parameter.
SOFTWAREONLY This is a filter switch that allows you YES, NO

to view only the software components
required for installation.
Do not use the /softwareonly
parameter with the /romonly
parameter.

USECURRENTCREDENTIAL Enables the credentials of the local YES, NO

host to be used as the credentials to
access the targets instead of providing
the user name and password explicitly
for each target.
The assumption is that the current
credentials are valid for the targets
that are being accessed. (Applies to
Windows only.)
WEBUPDATENEEDED Instructs HP SUM to include the YES, NO

components from the HP FTP site
(ftp://ftp.hp.com) in the list of possible
updates.
USEPROXYSERVER Use a proxy server (and port number) String value

to access the HP FTP site (ftp:// For example, 11.22.33.44:80
ftp.hp.com).
USEPROXYSCRIPT Include a proxy script to access the Web URL (for example,
HP FTP site (ftp://ftp.hp.com). autoproxy.com)
DELETEINPUTFILE Instructs HP SUM to delete the input YES, NO (default)

file after it has been read.
ONFAILEDDEPENDENCY This parameter instructs HP SUM how OmitHost (default),

to proceed when a component has a OmitComponent, Force
failed dependency.
The default of OmitHost causes the
host to be put in a failure state, and
no installation is attempted on it.
OmitComponent clears the affected
components and proceeds with any
updates that do not have dependency
failures. Force attempts all updates,
even if they have dependency failures.
HOST This parameter is the IP address or the IP address, DNS name

DNS name of a remote server, remote
iLO NIC port, Virtual Connect Ethernet
or Fibre Channel Module for c-Class
BladeSystem, or BladeSystem OA.
When two OAs are in an enclosure,
this parameter is the active OA. When
specifying the IP address, you can use
either the IPv4 or IPv6 format.
This parameter specifies an already
defined group name in the HP SUM
GUI.
UID Logs in to the target hosts with your <username>

user ID.
PWD Uses the password for the user ID <password>

specified in the UID.
The password is used to log in to
target hosts.
LOGFILENAME = "path" Redirects the output from HP SUM or Log file name
the HP BladeSystem c-Class OA flash
utility to a different directory than the
default location.
Input files 53
* 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>.
CMALOCALHOSTRWCOMMSTR Specifies an SNMP read/write SNMP read/write community

community string for local host access. string
(Applies to Linux PSP only.)
CMALOCALHOSTROCOMMSTR Specifies an SNMP read-only SNMP read-only community string

community string for local host access.
CMAMGMTSTATIONRWIPORDNS Specifies the IP address or DNS host IP address, DNS name

name of a system with read/write
access to serve as a management
station. You can specify multiple
locations separated by a space.
CMAMGMTSTATIONRWCOMMSTR Specifies an SNMP read/write SNMP read/write community

community string for a system with string
read/write access that serves as a
management station. You can specify
multiple strings separated by a space.
CMAMGMTSTATIONROIPORDNS Specifies the IP address or DNS host IP address, DNS name

name of a system with read-only
access to serve as a management
station. You can specify multiple
locations separated by a space.
CMAMGMTSTATIONROCOMMSTR Specifies an SNMP read/write SNMP read/write community

community string for a system with string
read-only access that serves as a
management station. You can specify
multiple strings separated by a space.
CMADEFTRAPCOMMSTR Sets a default SNMP community string SNMP community string

for traps. (Applies to Linux PSP only.)
CMATRAPDESTINATIONCOMMSTR Specifies the SNMP destination trap SNMP trap destination

community string. (Applies to Linux
PSP only.)
CMATRAPDESTINATIONIPORDNS Specifies the IP address or DNS host IP address, DNS name

name of a server as a destination for
SNMP traps, such as Systems Insight
Manager. (Applies to Linux PSP only.)
CMASYSCONTACT Specifies a person or phone number String value

for administration of this system.
CMASYSLOCATION Designates the location of this system. String value


CMASTARTWEBAGENT Determines whether the HP Systems • YES (start the web agent)
Insight Manager Web Agent is started
when the health application loads. • NO (do not start the web agent)
CMASTARTSTORAGEAGENT Determines whether the HP Systems • YES (start the storage agent)
Insight Manager Storage Agent is
started when the health application • NO (do not start the storage
loads. (Applies to Linux PSP only.) agent)
CMASTARTNICAGENT Determines whether the HP Systems • YES (start the web agent)
Insight Manager NIC agent is started.
(Applies to Linux PSP only). • NO (do not start the web agent)
CMANOTAINTEDKERNEL Determines whether the HP Lights-Out • YES (start the HP Lights-Out

management driver is started when management driver)
the health application loads. (Applies
to Linux PSP only.) • NO (do not start the HP
Lights-Out management driver)
HPVCAVCRMSERVER Informs the VCA of the name of the VCRM name

VCRM to use as a software distribution
repository. (Applies to Linux PSP only.)
HPVCAVCRMLOGINID This parameter is the login ID that the VCA login ID

VCA uses to communicate with the
VCRM. (Applies to Linux PSP only.)
HPVCAVCRMLOGINPASSWD This parameter is the password for the VCA login password
login ID specified in the
HPVCAVCRMLOGIN parameter.
FORCE-OVERWRITE HP Systems Management Homepage YES, NO (default)

(hpsmh) uses this parameter to force
overwrite the SMH settings of an
existing configuration file.
ADMIN-GROUP HP Systems Management Homepage Up to five Linux groups, separated

(hpsmh) uses this parameter to set up by spaces or semicolons, to enable
security for the web server. (Applies administrative access to the web
to Linux PSP only.) services.
USER-GROUP HP Systems Management Homepage Up to five Linux groups, separated

uses this parameter to set up security by spaces or semicolons, to enable
for the web server. (Applies to Linux user-level access to the web
PSP only.) servers.
OPERATOR-GROUP HP Systems Management Homepage Up to five Linux groups, separated

uses this parameter to set up security by spaces or semicolons, to enable
for the web server. (Applies to Linux operator-level access to the web
PSP only.) servers.
ANONYMOUS-ACCESS Determines whether an anonymous YES, NO (default)

user can access HP Systems
Management Homepage. (Applies to
Linux PSP only.)
IP-BINDING HP Systems Management Homepage YES, NO (default)

uses this parameter to determine
whether HP SMH can use all available
NICs and detect subnets for its web
services. (Applies to Linux PSP only.)
Input files 55
IP-BINDING-LIST HP Systems Management Homepage IP address pairs separated by

uses this parameter to restrict the NICs semicolons (for example,
and subnets to use for its web servers. 10.1.1.1/255.255.255.0;
The IP-BINDING parameter must be 10.2.2.2/255.255.255.0)
set to yes for this parameter to be
used during installation. (Applies to
Linux PSP only.)
IP-RESTRICTED-LOGINS HP Systems Management Homepage YES, NO (default)

uses this parameter to restrict login To enable restrictions on who can
access. (Applies to Linux PSP only.) log in to the web server, this
parameter must be set to yes, and
values must be provided to the
IP-RESTRICTED-EXCLUDE or
IP-RESTRICTED-INCLUDE
parameters.
IP-RESTRICTED-EXCLUDE HP Systems Management Homepage List of IP address ranges separated

uses this parameter to exclude specific by semicolons (for example,
IP address/netmask pairs from logging 10.1.1.1-10.1.1.10;
into the web services. (Applies to Linux 10.2.2.2-10.2.2.10)
PSP only.)
This parameter is ignored unless the
IP-RESTRICTED-LOGINS parameter
is set to yes.
IP-RESTRICTED-INCLUDE HP Systems Management Homepage List of IP address ranges separated

uses this parameter to enable login by semicolons (for example,
only from the IP address/netmask 10.1.1.1-10.1.1.10;
pairs specified. (Applies to Linux PSP 10.2.2.2-10.2.2.10)
only.)
This parameter is ignored unless the
IP-RESTRICTED-LOGINS parameter
is set to yes.
LOCALACCESS-ENABLED HP Systems Management Homepage • YES (default to include

uses this parameter to determine anonymous access)
whether to enable local anonymous
access to the web services. (Applies • NO
to Linux PSP only.)
LOCALACCESS-TYPE HP Systems Management Homepage • Anonymous (default)

uses this parameter to determine the
type of access granted to local users. • Administrator
(Applies to Linux PSP only.) CAUTION: Selecting local
access with administrator
privileges as the login provides
full access to any user who has
access to the local console,
without prompting for a user
name or password.
TRUSTMODE HP Systems Management Homepage • TrustByCert—If you use this

uses this parameter to set up the trust value, you must define the

relationship mode. (Applies to Linux CERTLIST parameter to

PSP only.) enable access to the server.
• TrustByName—If you use this
value, you must define the
XENAMELIST.
• TrustByAll—HP does not
recommend using this value
because of possible negative
security consequences.
CAUTION: The accepted
values are case-sensitive and
must be capitalized as shown.
Failure to do so prevents the
trust relationship from being set
up properly during installation
and might affect access to the
web server.
CERTLIST Enables you to provide a list of Certificate file name or Server

certificate files or servers where DNS name
certificates can be obtained for trust
relationships for the HP Systems
Linux PSP only.)
XENAMELIST Enables you to provide a list of Server DNS name

servers, separated by semicolons, for
trust relationships for the HP Systems
Linux PSP only.)
This parameter is valid only if the
TRUSTMODE parameter is set to
TrustByName. (Applies to Linux PSP
only.)
HPQLA2X00FO The hp_qla2x00 QLogic Fibre • SinglePath

Channel Driver uses this parameter to
determine the failover mode to use. • SecurePath
(Applies to Linux PSP only.) • QLogicFailure
NOTE: No default value
HPQLA2X00FORCE The hp_qla2x00 QLogic Fibre Y, N (default)

Channel Driver uses this parameter to
determine whether to skip detection of
third-party storage. (Applies to Linux
PSP only.)
OAUID Provides the user name credentials for User can define the OAUID
the OA associated with VC. You must variable multiple times before each
define a value of these variables HOST variable.
before the HOST variable in the
[TARGETS] section. This parameter
applies only for VC firmware.
You can also use OAUSER or
OAUSERNAME.
OAPWD Provides the password credentials for User can define OAPWD variable
the OA associated with VC. You must multiple times before each HOST
define a value of these variables variable.
before the HOST variable in the
[TARGETS] section. This parameter
applies only for VC firmware.
Input files 57
You can also use OAPASSWORD.
IGNOREWARNINGS Allows the installation to proceed on YES, NO

a Superdome 2 target even when Superdome 2 servers only
warnings are returned during analysis.
UPDATETYPE This argument determines which ALL, COMPLEX, PARTITIONS

Superdome 2 firmware is updated. Superdome 2 servers only
DEVICELIST Use this argument when the For example: DEVICELIST =

UPDATETYPE=PARTITIONS. This npar1, blade1/1
argument specifies the subset of Superdome 2 servers only
partitions or blades to update when
you do not want to update all
partitions. Valid devices are:
npar(number) and
blade(enc)/(bay).
REBOOTLIST Use this argument when the For example: REBOOTLIST =

UPDATETYPE= ALL or npar1, npar2
UPDATETYPE= PARTITIONS. This Superdome 2 servers only
argument specifies specific partitions
to reboot after the partition firmware
has been updated. Valid npar values
are npar(number).
Examples of the HP SUM input file include the following:

REBOOTALLOWED = YES
REBOOTREQUIRED = NO
REBOOTMESSAGE = "Server is going down for a reboot"
REBOOTDELAY = 15
COMPONENTSLIST = cp001234.exe, cp001235.exe
BUNDLESLIST = bp001234.xml
ALLOWUPDATEBUNDLE = YES
SKIPTARGET = NO
IGNOREERRORS = ServerNotFound, FailedDependencies
SOURCEPATH = c:\pkgsource1
USELATEST = YES
SILENT = YES
OPTIONS = /f:rom
[TARGETS]
HOST = schinta1
HOST = schinta2
UID = root
PWD = root123
HOST = 234.567.765.432
[END]
USAGE: hpsum /inputfile <path:\inputfile.txt>
Examples of inputfile.txt file:

Example: The two targets are passed to be updated. The targets do not necessarily have to be
OAs. They can be any target that HP SUM supports.
DRYRUN = YES
SILENT = YES
[TARGETS]
HOST = BL465C-01
HOST = 192.168.1.2
[END]
Example A host DNS is passed along with the user ID and password to use for the hosts in the
group.
DRYRUN = YES
SILENT = YES
[TARGETS]
HOST = BL685cG6
UID = Bigboss2
PWD = password
[END]
Example
SILENT = YES
IGNOREERRORS = ServerNotFound,BadPassword, FailedDepedencies
SKIPTARGET = NO
SOURCEPATH = C:\fwcd\firmware-8.70-0\hp\swpackages
[GROUPS]
HOST=winserver
UID=Userid
PWD=password
[END]
Example
SILENT = YES
IGNOREERRORS = ServerNotFound,BadPassword, FailedDepedencies
SKIPTARGET = NO
SOURCEPATH = C:\ fwcd\firmware-8.70-0\hp\swpackages
FORCEALL = YES
REBOOTALLOWED = YES
REBOOTDELAY = 30
REBOOTMESSAGE = “Install complete, server will reboot in 30 seconds”
[TARGETS]
HOST=16.83.62.141
UID=Userid
PWD=password
[END]
[TARGETS]
Input files 59
HOST=16.83.61.48
UID=Userid
PWD=password
[END]
[TARGETS]
HOST=16.83.62.196
UID=Userid
PWD=password
[END]
[TARGETS]
HOST=16.83.61.24
UID=Userid
PWD=password
[END]
Example: Superdome 2 input files:
IGNOREWARNINGS = TRUE
[TARGET] HOST = 10.0.0.206
UID = Userid
PWD = password
UPDATETYPE = PARTITIONS
DEVICELIST = npar1, npar2, blade1/4, blade 1/5
REBOOTLIST = npar1, npar2
[END]
Reports
HP SUM generates three types of reports about the specified system or repository. HP SUM generates
these reports by using the command-line arguments. If no additional arguments are specified on
the command line, HP SUM uses the local host and default repository locations (the directory where
HP SUM was initiated). You can specify a target if you provide the appropriate credentials. You
can specific a repository by using other command-line parameters to generate reports. For specific
commands, see “Command-line interface” (page 34).
Report type Description Report file information*
/report This argument generates a report The following report files are generated:
listing, a target summary, and • hpsum_Report_<date>.html
description of how the
components in the repository • hpsum_Report_<date>.xml
affect the target. For example, • hpsum_Report_<date>.csv
whether each component applies
to the target.
Usage: hpsum /report
/inventory_report This argument generates a report The following report files are generated:
listing of the components in the • hpsum_Inventory_Report_<date>.html
specified repository.
• hpsum_Inventory_Report_<date>.xml
Usage: hpsum
/inventory_report • hpsum_Inventory_Report_<date>.csv

Report type Description Report file information*
/firmware_report This argument generates a report The following report files are generated:
listing of the firmware in the • HPSUM_Firmware_Report_<date>
specified repository.
• fwreport.xml is placed in a folder named
Usage: hpsum
HPSUM_Firmware_Report_<date>
/firmware_report
/dependency_report This argument generates a report The following report file is generated:
that lists failed dependencies for HPSUM_FailedDependency_Reports_<datatime>.xml,
all targets. .html, or .csv.
/installed_report This argument generates a report The following report file is generated:
that lists all installed firmware, HPSUM_Installed_Report_<datatime>.xml ,
software, and driver versions .html, or .csv.
installed on targets.
HP SUM generates the reports as XML or HTML files that you can view in a JavaScript-enabled
web browser. The supported browsers for viewing the report files are Microsoft Internet Explorer
6.0 and Mozilla Firefox 3.5 and later. By default, the reports are located in the current working
directory from where HP SUM was initiated. If that current location is write-protected, the reports
are located in the same directory as the HP SUM log files.
HP SUM generates reports in CSV format that you can open in any application that supports CSV
format.
The HP SUM log files are located in these folders:
• On Windows operating systems: C:\cpqsystem\hp\log
• On Linux: /var/hp/log
When HP SUM generates the report, the HP SUM GUI does not appear. When the report is
generated, HP SUM displays the report file location.
Downloading HP SUM and components from the SDR

If you are using a Linux system, you can download HP SUM as an RPM from the HP SDR. This
allows you to download and install HP SUM and components from the SDR using common YUM
commands. For more information about downloading and installing HP SUM as an RPM, see the
document Linux best practices using HP Service Pack for ProLiant (SPP) and Software Delivery
Repository (SDR) at http://h20000.www2.hp.com/bc/docs/support/SupportManual/c03479393/
c03479393.pdf.
For information on using the SDR, go to http://www.hp.com/go/sdr.
Downloading HP SUM and components from the SDR 61

4 Advanced topics
Configuring IPv6 networks
You can deploy to remote targets in IPv6-based networks for Windows and Linux target servers.
Using HP SUM with IPv6 networks presents challenges for IT administrators.
For Windows-based servers, to communicate with remote target servers, HP SUM uses either
existing credentials or the user-provided user name and password to connect to the admin$ share.
This share is an automatic share provided by Windows Server. After HP SUM connects to the
admin$ share, it copies a small service to the target server for the duration of the installation. After
this service starts, HP SUM uses this service to communicate between the local and remote target
server. During this process, HP SUM opens ports in the Windows firewall to enable HP SUM to
use SOAP calls over SSL to pass data among local and remote systems. For more information
about the ports used, see “Network ports used by HP SUM” (page 64). After the installation is
completed or canceled, HP SUM stops the remote service, removes it from the target server, closes
the port on the Windows firewall, and then releases the share to the target server admin$ share.
For Linux-based servers, to communicate to remote target servers, HP SUM starts by using the
user-provided user name and password to create a SSH connection to the target server. After it
connects, HP SUM copies a small service to the target server for the duration of the installation.
After this service starts, HP SUM uses this service to communicate between the local and remote
target server. During this process, HP SUM opens ports in the iptables firewall to enable HP SUM
to use SOAP calls over SSL to pass data between the local and remote systems. For more information
about the ports used, see “Network ports used by HP SUM” (page 64). When the installation is
completed or canceled, HP SUM stops the remote service, removes it from the target server, closes
the port in the iptables firewall, and then closes the SSH connection to the target server.
NOTE: Windows XP clients are not supported in IPv6 networks for HP SUM deployment.
Configuring IPv6 for Windows Server 2003

For information on setting up a Windows Server 2003 operating system within an IPv6 network,
see the online Microsoft TechNet article Step-by-Step Guide for Setting Up IPv6 in a Test Lab.
Windows Server 2003 requires site-local addresses to provide the necessary file-sharing capabilities
needed by HP SUM. Link-local and global IPv6 addresses are not supported as remote targets with
HP SUM.
Before using HP SUM to deploy software and firmware updates to remote Windows Server 2003
servers, you must add a registry entry to enable file sharing connections over IPv6 networks.
To edit the registry:
1. Open the Registry Editor (Regedit32.exe).
2. Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
3. On the Edit menu, click Add Value.
4. Add the following registry value:
Value name: DisableStrictNameChecking
Data type: REG_DWORD
Radix: Decimal
Value: 1
5. Close the Registry Editor.
For more information about these steps, see the Microsoft Knowledge Base Item 281308 on the
Microsoft website.
62 Advanced topics
IPv6 addresses can be passed to HP SUM in command line arguments or using the HP SUM user
interface. In the HP SUM user interface, you can add a remote host on an IPv6 network by either
entering the DNS name of the IPv6 target server or by selecting the IPv6 address button and entering
the IPv6 address. HP SUM supports both the short-name and full IPv6 notation. You do not need
to add the optional interface number when you enter the address.
If you cannot connect to the target server or receive a Discovery failed message when executing
HP SUM in an IPv6 environment, see “Troubleshooting” (page 66).
After you connect to the target server, all other HP SUM functions work identically. Log files for
IPv6 hosts are stored with all other HP SUM files in the \CPQSYSTEM\hp\log\<ip_address>
directory.
Configuring IPv6 for Windows Server 2008

HP SUM provides the most robust support for remote deployment when using Windows Vista as
a client to Windows Server 2008-based servers. Using HP SUM in this environment enables you
to use all the capabilities of IPv6 including link-local, site-local, and global IP addresses for both
local and remote node servers. Windows Vista, when used as a client to run HP SUM to remote
Windows Server 2008 operating systems or as a node operating system on HP Workstation server
blades, provides the infrastructure that supports full IPv6 deployment of software and firmware
updates from HP SUM.
interface. In the HP SUM user interface, you can add a remote host on an IPv6 network by either
entering the DNS name of the IPv6 node server or by selecting the IPv6 address button and entering
the IPv6 address. HP SUM supports both the short-name and full IPv6 notation. You do not need
to add the optional interface number when you enter the address.
If you cannot connect to the node server or receive a Inventory failed message when executing HP
SUM in an IPv6 environment, see “Troubleshooting” (page 66).
After you connect to the node server, all other HP SUM functions work identically. Log files for IPv6
hosts are stored with all other HP SUM files in the \CPQSYSTEM\hp\log\<ip_address>
directory.
NOTE: Windows XP clients are not supported in IPv6 networks for HP SUM deployment.
Configuring IPv6 for Linux

HP SUM leverages the IPv6 capabilities of Linux as provided by the Red Hat Enterprise Linux and
Novell SUSE Linux Enterprise Server products. Using HP SUM in this environment enables you to
use all the capabilities of IPv6 including link-local, site-local, and global IP addresses for both local
and remote node servers. Remote node servers must have the iptables-ipv6 RPM installed before
targeting them from HP SUM. Failure to install the iptables-ipv6 RPM prevents HP SUM from opening
the communications port needed to send data to the initiating Linux workstation. You can disable
the Linux firewall to allow HP SUM to work, but the Linux server becomes vulnerable to attack.
For information on how to setup IPv6 in a Linux environment, please see the Linux IPv6 How To
website at Linux IPv6 How-To.
interface. In the HP SUM GUI, HP SUM automatically detects whether to use IPv4 or IPv6 on the
Add Node screen.
If you cannot connect to the node server or receive an inventory failed message when executing
HP SUM in an IPv6 environment, see “Troubleshooting” (page 66).
After you connect to the node server, all other HP SUM functions work identically. Log files for IPv6
hosts are stored with all other HP SUM files in the /var/hp/log/<ip_address> directories.
The only current limitation of HP SUM in a Linux IPv6 environment is that all remote node Linux-based
servers must have the iptables-ipv6 RPM file installed. You can find the file on the distribution media
Configuring IPv6 networks 63

for both Red Hat Enterprise Linux and Novell SUSE Linux Enterprise Server operating systems. HP
SUM uses this file to open a port in the IPv6 firewall to communicate with the Linux system that
runs HP SUM. Failure to install iptables-ipv6 results in HP SUM reporting an inventory failure unless
you disable the firewall.
Network ports used by HP SUM

HP SUM requires that certain network ports are available for proper operation. If you lock down
network ports, make sure that the ports listed in the network port tables are open so that HP SUM
works correctly when connecting to remote node 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 modules, through their web interfaces.
Table 2 HP SUM Windows network ports
Ports Description
Port 443 A secure data port used to transfer information.
Ports 445 and 137/138/139 (Port Connects to the remote ADMIN$ share on node servers. These are the standard
137 is used only if you are using ports Windows servers use to connect to the remote file shares. If you can
NetBIOS naming service.) connect remotely to a remote Windows file share on the node server, you
have the correct ports open.
Port 62286 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.
Ports 63001–63002 Updates are passed to the node and retrieved through an internal secure web
server that uses the first available port in the range of 63001-63002. This
allows iLO and VC firmware updates without having 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.
Remote HP Integrity iLO and Superdome 2 updates require these ports to be
open on systems for network traffic in both directions to transfer firmware files.
Ports 21 or 63006–63010 You can use these FTP ports to perform switch updates.
Table 3 HP SUM Linux network ports

Ports Description
Port 22 Establishes a connection to the remote Linux server via SSH. For Integrity servers,
HP SUM uses this port to discover node settings.
Port 443 A secure data port used to transfer information.
Port 62286 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.
Ports 63001–63002 Updates are passed to the node and retrieved through an internal secure web
server that uses the first available port in the range of 63001-63002. 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.
Remote HP Integrity iLO and Superdome 2 updates require these ports to be open
on systems for network traffic in both directions to transfer firmware files.
Ports 21 or 63006–63010 You can use these FTP ports to perform switch updates.
Special network configuration notes for HP Integrity servers

• HP Integrity servers have management network and production interfaces. These are usually
kept on separate subnets in an installation. To perform full remote administration of the server,
64 Advanced topics
access is required for both networks. If you keep both networks isolated, you need to perform
management and operating systems tasks separately.
• Updates for HP Integrity iLO and Superdome 2 nodes require network traffic in both directions
between the server running HP SUM and the node. The server running HP SUM creates a
local HTTP server, which is used to server firmware binaries to the node. The node issues an
HTTP request to the server running HP SUM to retries the firmware binaries during the update
process.
Network ports used by HP SUM 65

5 Troubleshooting
Installation issues
Components do not appear on the Select Items to Install screen or do not deploy from
the silent console mode
Solution: Components were not included in the installation set. Check the OpMan.trace file to
see which components were not included. For the location and more information about trace files,
see “Collecting trace directories” (page 66).
Use the following checklist to determine the reason and solution for this error:
Components are winnowed for the following reasons:
• The components do not support installation on the given operating system
• HP SUM does not discover the component's supported hardware on the targets.
• The component is not for the type of target selected
• HP SUM cannot deploy the component to the target.
• The component cannot be deployed in either the online or offline environment
Example: The following is an example of an output trace from the OpMan.trace file. In the
example, the binary image files 0.bin and 1.bin (which are iLO firmware files), components
cp011301.exe and cp011500.exe, and the HP SPP represented by bundle file bp000648.xml
were added to the installation set. All the other components were removed.
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[212]: Winnow--Adding FileName cp011500.exe
InstallSet.cpp[242]: Target 0: Added Bundle bp000648.xml
Collecting trace directories

HP SUM generates a set of debug trace logs located in the %TEMP%\HPSUM directory on Windows
systems. These files contain internal process and debug information which can be useful in
determining HP SUM failures.
The debug trace files are located under %temp%\hp_sum for Windows. The log files are located
under C:\cpqsystem\hp\log. These files provide the following information and are appended
in each HP SUM session.
HP SUM 5.0.0 and later includes a utility named GatherLogs.bat (Windows) or
Gatherlogs.sh (Linux) to create a compressed .zip (Windows) or tar.Z (Linux) file with all the
logs. If you need to review the log files, you can run this utility to gather all the logs in one file.
66 Troubleshooting
NOTE: Exit HP SUM before running the GatherLogs utility.
Debug Trace Files Function
InventoryResults.xml Contains details of the component inventory from the

repositories.
Settings.xml Includes general settings information of HP SUM such as

Force downgrade or upgrade.
SourceClient.trace Includes trace data of repository manager and general

errors if any.
Hpsumiserver\Hpsumiserver.log Contains trace data for HP SUM SOAP server sessions.
Hpsumiserver\HpsumserverW32.log Contains remote trace data for HP SUM SOAP server

sessions.
Hpsumiserver\localhpsumsoapserver.log Contains information of the HP SUM SOAP server.
Sesssion.log Contains the data and time for each session has started.
This file is saved in separate directory named with the date.
RepositoryManager Provides the repository and component information This

directory can be excluded in the trace data when collecting
the trace files.
<target>\Discoverymanager.log Provides the details of interaction between the Operations

Manager and the remote discovery client. If a discovery
tool fails, it is reported to this trace file and surfaced as a
Discovery Failed message. This log is target specific.
<target>\Installmanager.log Provides the interaction between the Operations Manager

and the remote discovery client. If a discovery tool fails, it
is reported to this trace file and surfaced as a Discovery
Failed message. This log is target specific.
<target>\<target name>_log.txt Provides the trace data from operations manager for
specific target.
<target> is the name of the target in the source selections
screen.
<target>\Settings.xml Provides general settings information of HP SUM such as

Force downgrade or upgrade for specific target.
Log Files Function
<target>\hpsum_log.txt Contains information of HP SUM discovery, installation

status and errors if any.
<target> is the name of the target in the source selections
screen.
Hpsum_detail_log.txt Contains the log data of the components.
hpsum.ini Stores persistent data on the user's system.
If you are running HP SUM in offline mode, use the following instructions to collect trace directories
and logs.
1. Launch HP SUM in offline mode.
2. Launch the command prompt from the HP SUM GUI by pressing CTRL-ALT-D-B-X.
NOTE: After approximately 30 seconds, the command prompt will appear over the HP SUM
GUI window.
Installation issues 67
3. Change the directory to the directory running HP SUM. For example, cd
/mnt/bootdevice/SPP2012060B/hp/swpackages.
4. Type ./GatherLogs.sh to collect the HP SUM logs. All logs are collected in a .tar.gz
file in the directory where you placed HP SUM. The log file is named
HPSUM_Logs_$(datetime).tar.
5. Place the logs on a removable media if you want to view them on another computer.
The Update returned an error message appears

When installing any component, if the installation fails, HP SUM displays the Update returned
an error message.
Solution: To determine the installation failure, review the associated component log.
Installation failed when installing Linux RPMs

When you install a Linux RPM, the installation fails and you receive the Update returned an
error message.
Solution: Ensure that you select the bundle for the operating system distribution on the Select Bundle
screen for installation or remove the RPMs from the directory that are not applicable to the Linux
distribution you are using.
This error can appear when the RPMs for more than one Linux distribution are present in a single
repository and a SPP bundle from the Select Bundle screen is not selected.
When multiple versions of source RPMs exist, the RPMs that are not the latest are not installed, and
Update not needed or Not Updated-already current messages appear. HP SUM
cannot determine which source RPMs go with which distribution because the RPMs do not contain
operating system information.
Discovery and connection issues

The connection error or Discovery Failed message appears
Solution: Use the following checklist to find a solution.
Troubleshooting connection errors

Use these tips to troubleshoot HP SUM connection errors:
• 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’s share
because Windows only allows one connection from a client to a server’s share. This can be
verified by entering net use at a command prompt. If a share to the target IP address
\admin$ share exists, delete it, and then attempt the installation again.
• Ensure that the target IP address server’s admin$ share is accessible. 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. When the connection is validated, ensure that
it is deleted by entering net use x: /d at the command prompt.
• Ensure the user ID being used to connect to the target IP address server is part of the
administrator’s or Linux root equivalent group. If it is not, HP SUM blocks installation to the
target.
• Ensure WMI is enabled and running on all Windows target servers.
• For Windows target servers, enter the user name in DOMAIN\USER format, where <user>
is the administrative user name, and <domain> is either the NETBIOS computer name or the
Active Directory domain name for this user account.
• For Linux, ensure the SSH port is not blocked by a firewall.
68 Troubleshooting
• For Linux, ensure that 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 are open on any routers in the network. For more information, see
“Network ports used by HP SUM” (page 64).
• The Symantec Endpoint Protection product blocks HP SUM ability to communicate with remote
targets if the Network Threat Analysis feature is enabled. Disable this feature while HP SUM
is in use on the workstation.
• Examine the trace directories for connection problems. For more information, see “Collecting
trace directories” (page 66).
• Ensure the server has a valid serial number.
HP SUM stalls during discovery

Solution: If the system is connected to external storage, try disconnecting the external storage.
If discovering a VMware ESXi 5.0 or later server, make sure you have installed the HP Management
WBEM Providers. You can download the HP Management WBEM Providers in the HP ESXi Offline
Bundle at http://h18000.www1.hp.com/products/servers/software/vmware-esxi/
offline_bundle.html or from the HP Online Depot at http://vibsdepot.hp.com. The HP Management
WBEM Providers are included in the HP Custom Image.
The Unable to Access Host message appears

Solution: Reconfigure the firewall settings on the host to recover Linux remote functionality.
Configuring firewall settings

By default, the target firewall is enabled in Linux.
To enable remote Linux functionality, the target and host firewall must be disabled or reconfigured
to allow IP traffic through the ports needed by HP SUM to deploy firmware. For more information
about ports, see “Network ports used by HP SUM” (page 64).
A Microsoft Windows Security Alert appears

Solution: Reconfigure the Windows firewall settings.
Configuring Windows firewall settings

The Windows Security Alert dialog box appears when a program is blocked from accepting
connections from the Internet or a network.
Discovery and connection issues 69

To set the rules for the Windows Firewall and Security Policy, click Unblock, and then set your
firewall settings to the following:
1. Click Start→Control Panel→Administrative Tools→Windows Firewall with Advanced
Security→Inbound Rules→Remote Administration (NP-IN).
2. Select Enabled, and then select Allow the connections.
For Direct to iLO support, you must enable ping.
HP SUM fails on Windows hosts due to McAfee firewalls

McAfee firewalls block HP SUM traffic.
Solution: Enable the port traffic associated with the HP SUM application:
1. From the system tray, click the McAfee icon.
2. Select Manage Features.
3. Select McAfee Host Intrusion Prevention.
4. Select the Activity Log tab.
As displayed in the following image, in the Message column, notice the entry similar to the
following: Blocked Incoming TCP from the HOST (15.255.101.110) during
execution of HP SUM.
70 Troubleshooting
5. From the menu, select Task→Unlock Interface.
6. Enter the password of the McAfee user interface.
7. Select the Firewall Policy tab.
8. On the bottom of the screen, click Add (Add new rule).
9. From the screen image, use the following settings for the new firewall rules on your system.
10. Click OK to ensure new firewall rules have been implemented.
Discovery and connection issues 71

11. Restart HP SUM.
Performing these steps allows HP SUM to function, although after a period of time (ranging
from minutes to hours), McAfee disables HP SUM access.
IPv6 network issues

If HP SUM cannot connect to the remote server, you might receive a Discovery Failed error. Discovery
failures can be caused by third-party storage, failure to access the remote target server, and an
inability to access system resources. For IPv6 networks, host discovery failures can be caused by
the incorrect configuration of the IPv6 network.
Solution: Follow the steps for your environment to correctly configure the IPv6 network.
Troubleshooting HP SUM in IPv6 Windows Server 2003 environment

To validate that the IPv6 network is configured correctly for HP SUM support, you must verify the
following based on your operating system version.
• Validate that the addresses are site-local. Site-local addresses normally start with "FEC0:".
Global and link-local IPv6 addresses are not supported when the remote target is Windows
Server 2003.
• Validate that you can ping the remote target server. With computers running Windows, you
can still use the ping command to ping IPv6 addresses:
ping <ipv6 address>.
• Ensure you can ping the IPv6 loopback address:
ping ::1
• Use the DNS hostname instead of IPv6 address to ensure the address is correct.
• Ensure you have installed the IPv6 protocol. It is not installed by default in Windows Server
2003. Be sure to reboot the server after installing the protocol to ensure addresses are properly
obtained.
• Verify that you can connect to the admin$ share using the credentials within HP SUM by
issuing the following command at a console prompt:
net use * \\<ipv6-address>.ipv6-literal.net\admin$ /user:<username>
net use * \\fec0::2.ipv6-literal.net\admin$ /user:administrator
72 Troubleshooting
You might need to provide the password if you are using a user name that is not the same as
you used to log in to the local system. All network shares require the use of the .ipv6-literal.net
name string to be properly configured by Windows.
NOTE: You do not need to use the .ipv6-literal.net suffix when entering IPv6 address into
the HP SUM user interface or when passing IPv6 address using command line parameters to
HP SUM.
After you validate that you can access the admin$ share on the remote target server, HP SUM
works unless other network or hardware issues exist.
• Ensure you have made the registry change on remote target servers. For more information,
see “Configuring IPv6 for Windows Server 2003” (page 62).
• Move back to an IPv4 network address to ensure HP SUM properly finds the remote target
server without any issues.
You can always copy HP SUM to the target servers and execute using the local installation method.
Troubleshooting HP SUM in IPv6 Windows Server 2008 environment

To validate that the IPv6 network is configured correctly for HP SUM support, you must verify the
following based on your operating system version.
• Validate that you can ping the remote target server. With computers running Windows, you
can still use the ping command to ping IPv6 addresses:
ping <ipv6 address>
ping ::1
• Verify that you can connect to the admin$ share using the credentials within HP SUM by
issuing the following command at a console prompt:
net use * \\<ipv6-address>.ipv6-literal.net\admin$ /user:<username>
net use * \\fec0::2.ipv6-literal.net\admin$ /user:administrator
You might need to provide the password if you use a user name that is different from the one
you used to log in to the local system. All network shares require the use of the .ipv6-literal.net
name string to be properly configured by Windows.
After you validate you can access the admin$ share on the remote target server, HP SUM
works unless there are other network or hardware issues.
Troubleshooting HP SUM in IPv6 Red Hat and Novell SUSE-based Linux environments
• Verify that you can establish an SSH connection to the remote target server using the credentials
within HP SUM by issuing the following command at a console prompt:
ssh <ipv6 address>
ssh 2101:db8:0:1::9
You must enter the root password for the target Linux server at the console to complete the
IPv6 connection.
• Validate that you can ping the remote target server. In Linux, you need to use the ping6
command to ping IPv6 addresses:
ping6 <ipv6 address>
IPv6 network issues 73

ping6 ::1
• Use ipconfig to validate you have IPv6 addresses assigned to your NICs.
• Use an IPv4 network address to ensure HP SUM can properly find the remote target server.
• HP SUM can always be copied to the target servers and executed using the local installation
method. For more information, see “Deployment modes” (page 11).
Operation issues
HP SUM stalls during boot
Solution: Check that the IP address 192.168.0.1 is not being used on your network. HP SPP uses
this IP address to deploy offline updates.
If this IP address is being used on the network, you might have to disconnect the server from the
network to perform updates.
For more information on how this IP address is used by HP SPP to deploy updates, see:
http://h20564.www2.hp.com/portal/site/hpsc/public/kb/docDisplay/?
docId=emr_na-c02959269
HP SUM connection is lost during iLO or NIC firmware update

Solution: None.
When either iLO or NIC firmware are updated, the HP SUM connection might be lost. If this
happens, it prevents the installation of components from continuing.
You cannot boot into Offline Interactive mode while using the iLO Virtual Media. When you update
the firmware, the connection to the iLO Virtual Media will be disconnected.
The user-specified reboot message does not appear when using a Japanese character
set on a Linux operating system
Solution: None.
You can specify a message to appear before the system shuts down during a reboot operation. If
you are using a Japanese character set and running on a Japanese version of a Linux operating
system, the message does not appear properly.
Automatic reboot does not occur when using the user-specified reboot message with
a Japanese character set on Windows
You can specify a message to appear before the system shuts down during a reboot operation.
When using a Japanese character set and running on a Japanese version of Windows, the message
causes the reboot not to occur automatically.
Solution: For a successful reboot, you must click Exit. When the message is entered using CLI, the
reboot message looks corrupted because the Japanese character set is not supported in CLI.
HP SUM stalls when run in a directory path that contains multi-bye characters
Solution: Do not run HP SUM in directories containing multi-byte characters in the path name.
74 Troubleshooting
Microsoft Windows displays a Found new hardware message
During the discovery progress, HP SUM might display the following message: Found New
Hardware. This message appears because one of the self-discovery components is loading a
new driver and Windows discovers it as a new piece of hardware.
Solution: Ignore the message and continue.
Non-matching systems error reported when building source Linux RPMs or installing
Linux RPMs built from source
If HP SUM reports non-matching systems errors when trying to build source Linux RPMs or installing
Linux RPMs built from source, the operating system on the target server does not match the operating
system from which you are running HP SUM in one of the following ways:
• The distribution of the operating system does not match. For example, RHEL 6.0 and RHEL
6.1 would be a mismatch.
• The architecture of the two operating systems does not match. For example, one server might
be running an operating system with x86 architecture and the other with x86_64 architecture.
• The kernel version running on the two systems does not match.
Solution: Use one of the following options:
• Run HP SUM on the target server itself instead of remotely deploying HP SUM.
• Build the driver RPM locally and take the resulting RPM file from the standard location (for
example, /usr/src/redhat/RPMS/i686/<driver>.rpm) and then copy it back into the HP SUM
repository. HP SUM will pick up the pre-built RPM and enable you to deploy it anywhere you
choose.
Linux component version discrepancy for source RPMs

You might observe differences in the RPM component name that might appear to be a version
mismatch for the component on the Select Item to be Installed and Installation Results screens. This
is caused by the RPM build phase. The resulting component is actually the same version. The RPM
build adds information, so it is technically the same component.
For example, if you select the component HP NC Series Mellanox 10GBE Driver for
Linux on the Select Items to be Installed screen, it appears as
hp-minx-en-1.4.3.1-1.src.rpm and on the Installation Results screen, it appears as
hp-minx-en-kmp-default-1.4.3.1_2.6.27.19_5-1.x86_64.rpm.
Solution: None.
No components found in the selected repositories message appears

The No components found in the selected repository(ies)error appears when at
least one space is in the path name of the repository containing the components to be installed.
Solution: Ensure that no spaces are in the path name.
HP SUM prevents an upgrade of Virtual Connect firmware if the VC health is invalid

or bad health state.
Virtual Connect firmware can be upgraded using HP SUM only if the health state of the VC is in
a good state. If the health state is invalid or bad, HP SUM does not upgrade the VC firmware.
Solution: Use VCSU to upgrade the firmware if the VC health is in one of the following states:
• Unhealthy
• Non-redundant
• Not part of a domain
Operation issues 75
• The user wants to select the order of deployment
• The user wants to back-up the configuration before flashing the VC firmware
HP ProLiant G6 Server ROM downgrade from 2010.03.30 or later to 2010.03.01

or earlier with HP SUM is not supported
Solution: This behavior is by design, and HP recommends that you do not copy the ROM components
containing the unsupported versions in the HP SUM repository.
When HP SUM is launched, all the available versions of ROM components in the repository are
listed under the Updates to be installed section of the Select Items to be Installed screen.
If a ROM downgrade is attempted from 2010.03.30 or later to 2010.03.01 or earlier with HP
SUM on ProLiant G6 servers, the ROM components with the unsupported version are automatically
removed from the updates to be installed. ROM components do not have the ability to block
downgrades.
For HP ProLiant G2, G5, and G6 servers, after upgrading to the May 2011 (or later)
revision of the system ROM, perform special steps if downgrading the system ROM
to revisions earlier than May 2011 is required
The May 2011 (and later) revisions of the system ROM for the HP ProLiant G2, G5, and G6-series
servers listed in the support document (see hyperlink below) include enhancements to the system
ROM flash update process. These enhancements improve the reliability and security of System
ROM updates by reducing the possibility of unexpected corruption of the flash part.
Because these enhancements require modifications to both the System ROM and the flash update
utility, the May 2011 (or later) System ROM cannot be downgraded using the flash components
available on the HP Support site that are dated earlier than May 2011.
Solution: The system ROM can be downgraded by creating a new flash component using an older
system ROM revision. For more information on how to downgrade the system ROM, see the HP
support website at http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?
objectID=c02838375.
76 Troubleshooting
6 Support and other resources
Information to collect before contacting HP
Be sure to have the following information available before you contact HP:
• Active Health System log (HP ProLiant Gen8 servers only)
Download and have available an Active Health System log for 3 days before the failure was
detected. For more information, see the HP iLO 4 User Guide or HP Intelligent Provisioning
User Guide on the HP website:
http://www.hp.com/go/ilo/docs
• OA SHOW ALL report (for HP BladeSystem products only)

For information on obtaining the OA SHOW ALL report, see:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?
objectID=c02843807
• Technical support registration number (if applicable)

• Product serial number
• Product model name and number
• Product identification number
• Applicable error messages
• Add-on boards or hardware
• Third-party hardware or software
• Operating system type and revision level
How to contact HP
Use the following methods to contact HP technical support:
• See the Contact HP worldwide website:
http://www.hp.com/go/assistance
• Use the Contact HP link on the HP Support Center website:

http://www.hp.com/go/hpsc
• In the United States, call +1 800 334 5144 to contact HP by telephone. This service is available
24 hours a day, 7 days a week. For continuous quality improvement, conversations might be
recorded or monitored.
Subscription service
HP recommends that you register your product at the Subscriber's Choice for Business website:
http://www.hp.com/country/us/en/contact_us.html
After registering, you will receive email notification of product enhancements, new driver versions,
firmware updates, and other product resources.
Information to collect before contacting HP 77

Related information
Documents
You can find these documents on the SPP documentation page:
http://www.hp.com/go/spp/documentation
• HP Smart Update Manager Release Notes

• HP Service Pack for ProLiant Release Notes
• HP Service Pack for ProLiant Server Support Guide
• HP ProLiant and Integrity Firmware Management Best Practices Overview
• HP ProLiant and Integrity Firmware Management Best Practices Planning Guide
• HP ProLiant and Integrity Firmware Management Best Practices Implementer Guide
The following document is available for HP Integrity firmware update best practices:
• Using HP Smart Update Manager with Integrity Servers
http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c03572337/
c03572337.pdf
Websites
For more information about SPP, see the SPP website:
http://www.hp.com/go/spp
To download the latest SPP and available hot fixes, see the SPP download page:
http://www.hp.com/go/spp/download
For information about HP Subscriber's Choice, see the Subscriber's Choice website:
http://www.hp.com/go/subscriberschoice
For information on the HP Systems Insight Manager, see the following documents on the HP Systems
Insight Manager website:
http://www.hp.com/go/insightmanagement/sim/docs
• HP Systems Insight Manager Installation and Configuration Guide for MS Windows

• HP Systems Insight Manager User Guide
For more information about HP ProLiant Gen8 servers and software see the HP website:
http://www.hp.com/go/proliantgen8/docs
For information about HP Insight Control Management Software, see the HP website:
http://www.hp.com/servers/rdp
For information about operating systems supported by HP ProLiant servers, see the operating system
support matrices:
http://www.hp.com/go/supportos
For information about support for updating SATA hard drives in a Modular Smart Array
20/50/60/70 storage enclosure connected to an HP ProLiant server using a Smart Array controller,
see the support matrix on the HP StorageWorks Modular Smart Arrays website:
http://www.hp.com/go/msa

Typographic conventions
Table 4 Document conventions
Convention Element
Blue text: Table 4 (page 79) Cross-reference links and e-mail addresses
Blue, underlined text: http://www.hp.com Website addresses
Bold text • Keys that are pressed

• Text typed into a GUI element, such as a box
• GUI elements that are clicked or selected, such as menu
and list items, buttons, tabs, and check boxes
Italic text Text emphasis
Monospace text • File and directory names

• System output
• Code
• Commands, their arguments, and argument values
Monospace, italic text • Code variables

• Command variables
Monospace, bold text Emphasized monospace text
CAUTION: Indicates that failure to follow directions could result in damage to equipment or data.
IMPORTANT: Provides clarifying information or specific instructions.
NOTE: Provides additional information.
TIP: Provides helpful hints and shortcuts.
HP Insight Remote Support software

HP strongly recommends that you install HP Insight Remote Support software to complete the
installation or upgrade of your product and to enable enhanced delivery of your HP Warranty,
HP Care Pack Service, or HP contractual support agreement. HP Insight Remote Support supplements
your monitoring continuously to ensure maximum system availability by providing intelligent event
diagnosis, and automatic, secure submission of hardware event notifications to HP, which will
initiate a fast and accurate resolution, based on your product’s service level. Notifications may be
sent to your authorized HP Channel Partner for onsite service, if configured and available in your
country.
HP Insight Remote Support software extends the HP enterprise remote support portfolio for customers
with small and medium-sized IT environments. The software is available in two variants:
• HP Insight Remote Support 7.x software is optimized to support up to 500 devices and can
be installed on a Windows ProLiant hosting device or a Windows ESXi Virtual Machine. It
can be easily integrated to work with a supported version of HP Systems Insight Manager.
HP Insight Remote Support 7.x provides anytime, anywhere personalized access to your IT
environment through HP Insight Online, and is also the recommended version for HP Proactive
Care Service.
• HP Insight Remote Support Advanced supports medium-sized to large environments with up
to 3,500 devices. It can be installed on a Windows ProLiant hosting device or a Windows
Typographic conventions 79
ESXi Virtual Machine and requires HP Systems Insight Manager. Optionally, customers using
HP Operations Manager or SAP Solution Manager to manage their environment can easily
integrate these platforms to create a single view. This software is also optimized to deliver
Mission Critical Services through additional features.
For more information, see the HP website at http://www.hp.com/go/insightremotesupport. The
HP Insight Remote Support Release Notes detail the prerequisites, supported hardware, and
associated operating systems. The release notes are available on the HP website at http://
www.hp.com/go/insightremotesupport/docs. HP Insight Remote Support is included as part of
HP Warranty, HP Care Pack Service, or HP contractual support agreement.
HP Insight Online
HP Insight Online is a new capability of the HP Support Center portal. Combined with HP Insight
Remote Support 7.x, it automatically aggregates device health, asset, and support information
from iLO Management Engine with contract and warranty information, and then secures it in a
single, personalized dashboard that is viewable from anywhere at any time. The dashboard
organizes your IT and service data to help you understand and respond to that information more
quickly. With specific authorization from you, an authorized HP Channel Partner can also remotely
view your IT environment at HP Insight Online.
• For more information about using HP Insight Online, see the HP Insight Online Getting Started
Guide at http://www.hp.com/go/proliantgen8/docs.
• To install HP Insight Remote Support and enable HP Insight Online, see the HP Insight Online
Integrated Solution and Management Setup Guide at http://www.hp.com/go/proliantgen8/
docs.

7 Documentation feedback
HP is committed to providing documentation that meets your needs. To help us improve the
documentation, send any errors, suggestions, or comments to Documentation Feedback
(docsfeedback@hp.com). Include the document title and part number, version number, or the URL
when submitting your feedback.
81
Acronyms and abbreviations
AMS Agentless Management Service
CPLD complex programmable logic device
DNS domain name system
FPGA Field Programmable Gate Array
HP SUM HP Smart Update Manager
iLO Integrated Lights-Out
IPDU intelligent power distribution unit
ISP Integrity Support Pack
OA Onboard Administrator
POST Power-On Self Test
PSP HP ProLiant Support Pack
RBSU HP ROM-Based Setup Utility
RILOE II Remote Insight Lights-Out Edition II
SDR Software Delivery Repository
SEP Symantec Endpoint Protection
SES Shared Engineering Services
SOAP Simple Object Access Protocol
SPP HP Service Pack for ProLiant
SSH Secure Shell
SSL Secure Sockets Layer
TPM Trusted Platform Module
UNC Universal Naming Convention
VC Virtual Connect
WBEM Web-Based Enterprise Management
WMI Windows Management Instrumentation
82 Acronyms and abbreviations

Index
download updates, 20
A
advanced topics, 62 E
arguments, 36 editing hosts, 19
errors
B Discovery failure, 68
baseline Installation of components failed with 'Update returned
creating, 20 an error' when installing Linux RPMs, 68
blocked HP SUM, recovering from, 69 Non-matching systems error reported when building
bundle filter options source Linux RPMs or installing Linux RPMs built from
Add Repository, 18 source, 75
Edit Repository, 19 execution, first time, 7
Select bundles, 28
F
C failed dependencies, 28
CLI (Command Line Interface) files, creating input
Command-line arguments, 36 Input file format and rules, 48
Command-line examples, 44 Input files, 48
Command-line interface, 34 firewall settings, configuring
Command-line syntax, 34 Configuring firewall settings, 69
command line arguments, 36 Configuring Windows firewall settings, 69
command line examples, 44 HP SUM fails on Windows due to McAfee firewalls, 70
command line interface, using, 34 firmware
command line syntax, 34 details, 30
component configuration, 19 HP SUM supported firmware for HP Integrity servers,
components 11
Installation of components failed with 'Update returned HP SUM supported firmware for HP ProLiant servers,
an error' when installing Linux RPMs, 68 10
Select components, 29 VMware, 24
configuring components, 19 firmware details
configuring firewall settings view, 30
Configuring firewall settings, 69
Configuring Windows firewall settings, 69 G
contacting HP, 77 groups, 25
conventions GUI, 16
document, 79
creating input files, 48 H
credentials, 25 hardware, found new, 75
help
D obtaining, 77
deployment methods, 12 hosts, 30
deployment overview, 7 HP
deployment scenarios, 12, 13 technical support, 77
deployment, scripted, 34 HP Insight Online, 80
discovery issues, troubleshooting, 69 HP ProLiant Servers, 10
Discovery Process screen, 20
document I
conventions, 79 iLO
related documentation, 78 pending updates, 26
documentation iLO (Integrated Lights-Out), 74
HP website, 78 input file parameters
providing feedback on, 81 Input file format and rules, 48
double-byte characters Input file parameters, 50
File encoding, 49 installation, 27
Running in a directory path containing multi-byte installation issues
characters, 74 installation failure, 66
83
Installation of components failed with 'Update returned reboot settings, 74
an error' when installing Linux RPMs, 68 reboot, troubleshooting, 74
installation options, 30 recovering from a failed system ROM upgrade
introduction, 6 Recovering from an installation failure, 66
IPv6 network configurations related documentation, 78
Configuring IPv6 for Windows Server 2008, 63 remote functionality, recovering, 69
Configuring IPv6 networks with HP SUM, 62 reports
IPv6, troubleshooting Generate and View Reports, 32
Troubleshooting HP SUM in IPv6 networks, 72 Reports, 60
Troubleshooting HP SUM in IPv6 Red Hat and Novell reports, creating
SUSE-based Linux environments, 73 Generate a Report, 32
Troubleshooting HP SUM in IPv6 Windows Server 2003 Reports, 60
environment, 72 repository
Troubleshooting HP SUM in IPv6 Windows Server 2008 Add Repository, 18
environment, 73 Configure Components, 19
Edit Repository, 19
K HP SUM displays No components found in the selected
keyboard support, 16 repository(ies) message, 75
Remove Repository, 19
L Using multiple repositories, 18
Linux component version discrepancy, 75 return codes
Linux IPv6 environment, 63 Linux RPM return codes, 47
Linux remote functionality, recovering, 69 Return codes, 46
Linux RPM return codes, 47 VMware ESXi return codes, 47
Linux smart components, return codes, 46 return codes, Linux smart components, 46
return codes, VMware ESXi, 47
M return codes, Windows smart components, 46
mounting virtual media, 74 RPM return codes, Linux, 47
N S
non-matching system error, 75 scripted deployment, 34
selecting bundles to filter, first time, 28
O selecting components to install, 29
operating system problems source selections, 16
Displaying the user-specified reboot message using a
Japanese character set when running on a Linux T
operating system, 74 target interfaces
Rebooting with the user-specified reboot message using `Select targets, 22
a Japanese character set when running on a Windows Add single target, 24
operating system, 74 Dependency checking, 23
operating systems Edit Target, 25
Displaying the user-specified reboot message using a Find and discover targets, 23
Japanese character set when running on a Linux Inter-target dependency, 23
operating system, 74 Select devices, 30
Rebooting with the user-specified reboot message using Target types, 23
a Japanese character set when running on a Windows technical support
operating system, 74 HP, 77
overview, HP SUM, 6 TPM (Trusted Platform Module)
Trusted Platform Module, 14
P troubleshooting
parameters HP Smart Update Firmware DVD mounted using iLO
Error reporting, 49 virtual media, 74
Input file parameters, 50 HP SUM hangs during discovery, 69
pending Troubleshooting, 66
iLO updates, 26 troubleshooting, Linux component discrepancy issue, 75
proxy settings, 17 troubleshooting, non-matching system error, 75
troubleshooting, reboot, 74
R troubleshooting, repository, 75
Reboot Options, 32 Trusted Platform Module, 13
84 Index
Trusted Platform Module (TPM)
Trusted Platform Module, 14
typographic conventions, 79
V
version discrepancy issue, 75
virtual media access, 74
VMware
updates, 24
VMware ESXi return codes, 47
W
websites
product manuals, 78
Windows smart components, return codes, 46
85

HP Smart Update Manager User Guide

Uploaded by

Copyright:

Available Formats

You might also like

HP Smart Update Manager User Guide

Uploaded by

Document Information

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

HP Smart Update Manager User Guide

Uploaded by

Copyright:

Available Formats

HP Smart Update Manager User Guide

HP Part Number: 613175-009

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

• Want to select the

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

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

• Need to select individual VC IP address or DNS

• Need to select individual

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

Update an existing enclosure The same scenario as shown • Windows: • Online:

HP SUM supported firmware for HP ProLiant servers

System ROM Yes

Broadcom NIC firmware Yes

Intel NIC firmware Yes

NetXen NIC firmware Yes, online

QLogic NIC firmware Yes

PowerPIC firmware Yes

Smart Array controller firmware Yes

SAS and SATA hard drive firmware behind non-Smart No

Emulex, QLogic, and Brocade Fibre Channel HBA firmware Yes

FC switch firmware Yes, online only

Tape Blade firmware Yes

OA firmware Yes, online only

VC firmware Yes, online only

CPLD firmware Yes

HP StorageWorks MDS 600 enclosure firmware Yes

MSA 2000 firmware (P2x00 firmware) No

D2600/D2700 firmware Yes, when attached through a Smart Array controller

3Gb/s and 6 Gb/s SAS BL switches Yes, online only

SES firmware Yes

Deploying HP Integrity Smart Update Firmware bundles with HP SUM

HP SUM supported firmware for Integrity servers

System ROM firmware Yes

FPGA firmware Yes

iLO-3 MP firmware Yes

Power Monitor firmware Yes

Superdome 2 Complex and nPartition firmware Yes

I/O Card firmware Yes (Integrity servers running HP-UX)

FC switch firmware Yes, online only

Local The installation runs on the physical hardware you are

Remote The installation runs on one system, but updates other

Online The installation occurs while the host processor is running

runs Microsoft Windows Server 2008, the update occurs

Offline In offline mode, the HP SUM boots a small Linux kernel

Scenario Used when

Choosing HP SUM or HP SIM

Disabling BitLocker to permit firmware updates

Choosing HP SUM or HP SIM 13

This icon indicates a recommended update.

HP SUM status icons 15

Current Repositories table

Setting Proxy Server options

Adding the repository

If the default repositories do not include the component or bundle updates:

2. Enter an optional name for the repository in Repository Name.

18 Using the HP SUM GUI

2. Edit the Repository Name.

Removing the repository

2. When the correct row is highlighted, click Remove Repository.