HP Smart Update Manager

User Guide

Abstract
This guide is intended for individuals familiar with the configuration and operation of Microsoft Windows, Windows Server 2003 and 2008, Linux,
smart components, and deployment of firmware and software. Because of the risk of data loss, only individuals experienced with using firmware and
software should implement the procedures.

Part Number: 613175-005

September 2011
Edition: 5
© Copyright 2011 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.
Microsoft®, Windows®, Windows Vista®, and Windows Server® are U.S. registered trademarks of Microsoft Corporation.
Contents

Introduction .................................................................................................................................. 6
HP SUM overview ........................................................................................................................................ 6
Using this guide ........................................................................................................................................... 7
New features of HP SUM .............................................................................................................................. 7
Minimum requirements .................................................................................................................................. 7
Minimum requirements for Windows servers ......................................................................................... 7
Minimum requirements for Linux x86 servers ......................................................................................... 8
Supported deliverables overview ................................................................................................................. 10
Support and limitations of HP SUM .................................................................................................... 10
Deployment from HP SUM ........................................................................................................................... 11
Executing HP SUM ........................................................................................................................... 11
Deploying firmware for ProLiant servers using the HP Smart Update Firmware DVD ................................ 13
Deploying Integrity firmware bundles with HP SUM ............................................................................. 15

HP SUM User Interface ................................................................................................................ 16

Deployment scenarios ................................................................................................................................. 16
Keyboard support ...................................................................................................................................... 16
Source selections ........................................................................................................................................ 17
Set Proxy Server options ................................................................................................................... 18
Using multiple repositories ................................................................................................................ 19
Add Repository ................................................................................................................................ 19
Edit Repository ................................................................................................................................. 20
Remove Repository ........................................................................................................................... 20
Configure Components ..................................................................................................................... 20
Download components for target discovery......................................................................................... 21
Select targets ............................................................................................................................................. 22
Inter-target dependency .................................................................................................................... 23
Dependency checking ...................................................................................................................... 23
Target types ..................................................................................................................................... 24
Find and discover targets .................................................................................................................. 24
Add Single Target ............................................................................................................................ 24
Enter Target Credentials .................................................................................................................... 24
Edit Target ....................................................................................................................................... 25
Remove Target ................................................................................................................................. 25
Manage Groups .............................................................................................................................. 25
Install updates ............................................................................................................................................ 25
Installing updates ............................................................................................................................. 26
Abort installation .............................................................................................................................. 27
View failed dependencies ................................................................................................................. 27
Select bundles .................................................................................................................................. 27
Select components............................................................................................................................ 28
View firmware mismatch details ......................................................................................................... 28
Select devices .................................................................................................................................. 28
Installation options ........................................................................................................................... 29
Reboot options ................................................................................................................................. 29
Schedule Updates ...................................................................................................................................... 29
Generate and View Reports ........................................................................................................................ 30

Contents 3
 Generate a Report............................................................................................................................ 30
View a Report .................................................................................................................................. 30

Scripted deployment ................................................................................................................... 31

Command-line interface .............................................................................................................................. 31
Command-line syntax ....................................................................................................................... 31
Command-line arguments .................................................................................................................. 32
Component configuration for Windows components only ..................................................................... 38
Command-line examples ................................................................................................................... 38
Return codes .................................................................................................................................... 40
Windows smart component return codes ............................................................................................ 40
Linux smart component return codes ................................................................................................... 40
Linux RPM return codes ..................................................................................................................... 41
Input files................................................................................................................................................... 41
Command-line usage of input file ....................................................................................................... 42
Input file format and rules .................................................................................................................. 42
File encoding ................................................................................................................................... 42
Error reporting ................................................................................................................................. 43
Input file parameters ......................................................................................................................... 43
Reports...................................................................................................................................................... 51

Advanced topics ......................................................................................................................... 56

Configuring IPv6 networks with HP Smart Update Manager............................................................................ 56
Configuring IPv6 for Windows Server 2003 ....................................................................................... 56
Configuring IPv6 for Windows Server 2008 ....................................................................................... 57
Limitations of IPv6 for Windows Server 2003 and Windows Server 2008 ............................................. 58
Configuring IPv6 for Linux ................................................................................................................. 58
Limitations of IPv6 for Linux ............................................................................................................... 60
Server virtualization detection and support.................................................................................................... 60

Troubleshooting .......................................................................................................................... 61
Recovering from a failed ROM upgrade ....................................................................................................... 61
Recovering from a failed system ROM upgrade ................................................................................... 61
Recovering from a failed option ROM upgrade ................................................................................... 62
Recovering from an installation failure .......................................................................................................... 63
Collecting trace directories ................................................................................................................ 63
Recovering from a discovery failure ............................................................................................................. 64
Troubleshooting connection errors ...................................................................................................... 64
HP SUM hangs during discovery........................................................................................................ 65
HP SUM hangs during boot ......................................................................................................................... 65
Recovering from a loss of Linux remote functionality ....................................................................................... 66
Configuring firewall settings .............................................................................................................. 66
Recovering from a blocked program on Microsoft Windows ........................................................................... 66
Configuring Windows firewall settings ............................................................................................... 66
Enabling ports in HP Smart Update Manager ...................................................................................... 67
Recovering from operating system limitations when using a Japanese character set ........................................... 69
Displaying the user-specified reboot message using a Japanese character set when running on a Linux
operating system .............................................................................................................................. 69
Rebooting with the user-specified reboot message using a Japanese character set when running on a Windows
operating system .............................................................................................................................. 69
Running in a directory path containing multi-byte characters ........................................................................... 69
Recovering a lost HP Smart Update Manager connection ............................................................................... 69
HP Smart Update Firmware DVD mounted using iLO virtual media ........................................................ 69
Troubleshooting HP Smart Update Manager in IPv6 networks ......................................................................... 70

Contents 4
 Troubleshooting HP Smart Update Manager in IPv6 Windows Server 2003 environment ........................ 70
Troubleshooting HP Smart Update Manager in IPv6 Windows Server 2008 environment ........................ 71
Troubleshooting HP Smart Update Manager in IPv6 Red Hat and Novell SUSE-based Linux environments . 71
HP SUM found new hardware message........................................................................................................ 72
Non-matching systems error reported when building source Linux RPMs or installing Linux RPMs built from source 72
Linux component version discrepancy for source RPMs ................................................................................... 72
HP SUM displays No components found in the selected repository(ies) message ............................................... 73
Additional/Optional Actions columns are grayed when HP SUM is maximized ................................................ 73
Installation of components failed with 'Update returned an error' when installing Linux RPMs ............................. 73
HP SUM fails on Windows Vista® due to McAfee firewalls ............................................................................ 73
Downgrade of ProLiant G6 Server ROM from 2010.03.30 or later to 2010.03.01 or earlier using HP SUM is not
supported .................................................................................................................................................. 76

Technical support ........................................................................................................................ 77

Reference documentation ............................................................................................................................ 77
Operating system information ...................................................................................................................... 77
HP contact information ................................................................................................................................ 78

Acronyms and abbreviations ........................................................................................................ 79

Index ......................................................................................................................................... 81

Contents 5
Introduction

HP SUM overview
HP SUM is a technology included in many HP products for installing and updating firmware and software
components on HP ProLiant and HP Integrity servers, enclosures, and options.
HP SUM provides a GUI and a command-line scriptable interface for:
• Deployment of firmware for single or one-to-many HP servers and network-based targets such as iLOs,
OAs, 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) and HP Integrity servers.

IMPORTANT: Throughout this document, references to the deployment of firmware apply only to
HP SUM when used with HP ProLiant servers. For HP Integrity servers, deploying firmware using
HP SUM only applies to BL8x0c i2, rx2800 i2 and Superdome 2 Servers.

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
version-based dependencies from destroying an installation, and ensures firmware updates are handled in a
manner that reduces any downtime required for the firmware update process.
HP SUM does not require an agent for remote installations, because it copies a small, secure SOAP server to
the target server 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 deploys only required updates
• Simultaneous firmware and software deployment for multiple remote targets in both GUI and CLI modes
(ProLiant servers and options only)
• Improved deployment performance
• Local or remote (one-to-many) online deployment
• Local offline firmware deployments with the earlier HP Firmware Maintenance CD or the HP Smart
Firmware Update DVD for ProLiant servers and options
• Remote offline deployment when used with the SmartStart Scripting Toolkit or iLO Virtual Media
• GUI- or CLI-scriptable with extensive logging
• Remote command-line deployment

Introduction 6
 • Support for updating firmware on network-based targets such as the OA, iLO 2/iLO 3 through Network
Management Port, and VC Ethernet and Fibre Channel modules on HP ProLiant servers

NOTE: HP SUM does not support third-party controllers. This includes flashing hard drives
behind these controllers.

Using this guide

HP SUM is included with many different deliverables. A deliverable is an HP product which contains HP SUM
and a set of firmware or software components, for example, the HP Smart Update Firmware DVD. Read your
deliverable’s overview section to verify specific HP SUM limitations, and then, review the SUM features
sections. For more information, see "Overview of supported deliverables ("Supported deliverables overview"
on page 10)."

New features of HP SUM

HP SUM 5.0.0 includes support for:
• New Graphical User Interface
• Ability to deploy firmware from Windows servers to Linux targets
• Support for Integrity BL8x0c i2, rx2800 i2, and Superdome 2 servers
• Automatic discovery of blades and interconnects when given the Onboard Administrator as the target

Minimum requirements
• Minimum requirements for Windows operating systems ("Minimum requirements for Windows servers"
on page 7)
• Minimum Requirements for Linux Servers ("Minimum requirements for Linux x86 servers" on page 8)
The minimum display settings for optimum performance are 1024 x 768 pixels resolution.

NOTE: For Windows operating systems, the respective device drivers for the embedded/add-on
devices in the target servers must be installed for HP SUM to discover the devices.

Minimum requirements for Windows servers

To successfully use HP SUM to deploy firmware and software to targets running a Windows® operating
system, the following must be available:
• A local administrative system with 1 GB of memory
• Sufficient hard-drive space of at least twice the file size of the components to be deployed
• WMI enabled
• All remote targets must be visible by the administrative system running HP SUM.
• An account with administrator privileges on each target server
HP recommends that the user name and password for the administrator account on each target server
be the same as those on the local administrative system. If administrator privileges are not set up in this

Introduction 7
 manner, you must have the user name and password available for each remote server available.
Alternatively, you can use a domain account on the local administrative system that has administrator
privileges on the target servers.
• The beginning and ending IP addresses entered for the range of targets must both be on the same
subnet.

NOTE: HP Smart Update Manager requires the user to be logged in using Administrator
credentials. A user account elevated to “Run as administrator” in most cases does not have
sufficient rights because access to protected system files and the Windows registry, which is
needed to deploy most firmware and driver updates, is restricted. If the logged in account is
unable to perform the net use *\\server\ADMIN$ for Microsoft Windows targets, you do not
have sufficient privileges to run HP SUM to remote targets. Deployment of some software updates
on a local server may still be possible in some instances, but is not recommended.

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

• Enable the network ports that HP SUM uses. For more information, see "Enabling ports in HP Smart
Update Manager (on page 67)."

Minimum requirements for Linux x86 servers

To successfully use HP SUM to discover perform dependency checks on targets running a Linux operating
system, the following must be available:
• A local administrative system with 1 GB of memory
• glibc 2.2.4-26 or later
• gawk 3.1.0-3 or later
• sed 3.02-10 or later
• pciutils-2.1.8-25.i386.rpm or later
Be sure that the following platform-specific compatibility libraries are also installed.
• For Red Hat Enterprise Linux 4x86 servers:
o libnl (required for QLogic and Emulex drivers)
• For Red Hat Enterprise Linux 4 AMD64/EM64T servers:
o libnl (required for QLogic and Emulex drivers)
• For Red Hat Enterprise Linux 5 x86 servers:
o libnl (required for QLogic and Emulex drivers)
• For Red Hat Enterprise Linux 5 AMD64/EM64T servers:
o libnl (required for QLogic and Emulex drivers)
• For SLES 10 x86 servers:
o libnl (required for QLogic and Emulex drivers)
• For SLES 10 AMD64/EM64T servers:
o libnl (required for QLogic and Emulex drivers)

Introduction 8
 o e2fsprogs-32bit
• For SLES 11 x86 servers:
o libstdc++33-3.3.3-11.9.i586 or later
o libnl (required for QLogic and Emulex drivers)
• For SLES 11 AMD64/EM64T servers:
o libstdc++33-32bit-3.3.3-11.9 or later
o libnl (required for QLogic and Emulex drivers)

Minimum requirements for Red Hat Enterprise Linux 6 servers

NOTE: The following versions listed are needed as a minimum. Later versions of these might be
used as well.

NOTE: Ensure that each NIC has an IP address assigned. To get the IP address assigned to a
NIC, enter the dhclient command in the console, which enables the NIC interfaces and
retrieves an IP address. If a NIC does not have an IP address, HP SUM appears to hang on start
up.

• RHEL6 console mode

NOTE: No X console in either x86 or x86_64 servers. To run HP SUM in silent mode, you must
install the base server with defaults and the following RPMs.

o lm_sensors-libs-3.1.1-10.el6.<arch>.rpm
o net-snmp-libs-5.5-27.el6.<arch>.rpm
o net-snmp-5.5.27.el6.<arch>.rpm
o kernel-headers-2.6.32-71.el6.<arch>.rpm
o redhat-rpm-config-9.0.3-25.el6.noarch.rpm
o kernel-devel-2.6.32-71.el6.<arch>.rpm
o rpm-build-4.8.0-12.el6.<arch>.rpm
o gcc-4.4.4-13.el6.<arch>.rpm
• RHEL6 graphical mode

NOTE: If the user elects to install the XWindows support, then the following steps apply to both
x86 and x86_64 servers.

NOTE: The following items must be the 32-bit version even under x86_64 architecture as HP
SUM and several of the RPMs require 32-bit libraries installed.

o libuuid-2.17.2-6.el6.i686.rpm
o freetype-2.3.11-5.el6.i686.rpm
o libSM-1.1.0-7.1.el6.i686.rpm
o libICE-1.0.6-1.el6.i686.rpm
o libXi-1.3-3.el6.i686.rpm
o libX11-1.3-2.el6.i686.rpm
o libXext-1.1-3.el6.i686.rpm

Introduction 9
 o libxcb-1.5-1.el6.i686.rpm
o libXau-1.0.5-1.el6.i686.rpm
o libXrender-0.9.5-1.el6.i686.rpm
o libXrandr-1.3.0-4.el6.i686.rpm
o libXfixes-4.0.4-1.el6.i686.rpm
o libXcursor-1.1.10-2.el6.i686.rpm
o fontconfig-2.8.0-3.el6.i686.rpm
o expat-2.0.1-9.1.el6.i686.rpm
o expect-5.44.1.15-2.el6.<arch>.rpm
o zlib-1.2.3-25.el6.i686.rpm
o libstdc++-4.4.4-13.el6.i686.rpm
o net-snmp-5.5-27.el6.<arch>.rpm

Supported deliverables overview

HP SUM support is specific to the deliverable in which it is delivered. Make sure you use the correct version
of HP SUM that is released along with the deliverable supporting the environment.

NOTE: Not all functionality is available in each version of HP SUM. Before using HP SUM that
comes with a deliverable, review the Support and limitations ("Support and limitations of HP
SUM" on page 10) of that version of HP SUM to determine if it has the features that you need.

Support and limitations of HP SUM

Before installing HP SUM, use the following table to verify that you are using the appropriate software
version.

HP SUM Delivered with Support and limitations

version
4.0.0 For ProLiant servers: No support for Integrity server firmware or support
• HP ProLiant Support Pack for Windows packs
8.40
• HP ProLiant Support Pack for Linux 8.40
• HP Smart Update Firmware DVD 9.0
For ProLiant Workstation Blades:
• HP Workstation Support Pack for
Windows for HP WS460c G6 Blade
• HP Smart Update Firmware DVD 9.0
(offline only)
4.0.0.64 • HP Integrity Support Pack for Windows • Support for Integrity Support Pack for Windows
on Itanium-based systems 7.00
• No support for Integrity server firmware
bundles
• No support to download the latest components
available from ftp.hp.com through the HP SUM
GUI and command line options
4.0.1 • HP ProLiant Support Pack for Windows No support for Integrity server firmware or support

Introduction 10
 HP SUM Delivered with Support and limitations
version
8.50 packs
• HP ProLiant Support Pack for Linux 8.50
4.0.2 • HP Smart Update Firmware DVD 9.10 No support for Integrity server firmware or support
packs
4.1.0 • HP ProLiant Support Pack for Windows No support for Integrity server firmware or support
8.60 packs
• HP ProLiant Support Pack for Linux 8.60
4.2.0 • HP ProLiant Support Pack for Linux 8.70 No support for Integrity server firmware or support
• HP ProLiant Support Pack for Windows® packs
8.70
4.2.1 • HP Smart Update Firmware DVD 9.30 No support for Integrity server firmware or support
packs
4.9.5 • HP Integrity Server Bundles • HP BL8x0c i2 server
• HP rx2800 i2 server
• HP c-Class Onboard Administrators
• No VC support
5.0.0 • HP Smart Update Firmware DVD • HP Superdome 2 server
• HP Integrity Server Bundles • VC support

Deployment from HP SUM

The following sections discuss deployment from HP SUM.

Executing HP SUM
HP SUM provides three modes of execution 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 standard Windows and Linux operating
systems in online and offline mode (available on HP Smart Update Firmware DVD) through special boot
environments based on Linux boot kernels when the prerequisites are met.
Use the following table to determine the correct execution mode for the server use case.

IMPORTANT: 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.

Scenario Description HP SUM command HP deliverable

Interactive, graphical Use this scenario when you: • Windows: • Online:
deployment on a local • Are not familiar with hpsum HP ProLiant Support Pack for
host (Run HP SUM on the command line tools • Linux: Windows and Linux
server being updated.) • Are deploying ./hpsum or
components on a local, Smart Update Firmware DVD
single host • Offline:

Introduction 11
Scenario Description HP SUM command HP deliverable
• Do not require scripting Smart Update Firmware DVD
• Want to select the
components to be
installed
Scripted deployment on a Use this scenario when you: • Windows: • Online:
local host (Run HP SUM • Are familiar with hpsum -s HP ProLiant Support Pack for
from a network share on a command line tools • Linux: Windows and Linux
local server.) • Are deploying ./hpsum -s or
components on a local, Smart Update Firmware DVD
single host or
• Must perform a HP Integrity Support Pack for
customized, scripted Windows
deployment • Offline:
• Are unable to unlock None
the required HP SUM
network ports for
remote deployment
Interactive, graphical Use this scenario when you: • Windows: • Online:
deployment to a remote • Are not familiar with hpsum HP ProLiant Support Pack for
host (Run HP SUM from a command line tools • Linux: Windows and Linux
workstation and update • Do not require scripting ./hpsum or
remote hosts over the • Want to select the Targets can be a Smart Update Firmware DVD
network using the GUI) components to be server, OA, iLO, or VC or
installed IP address or DNS HP Integrity Support Pack for
• Need to update name. Windows
multiple targets or
including OA, VC, and HP Integrity BL8x0c i2,
server-based firmware rx2800 i2 and Superdome 2
• Need to select Servers Bundles for Windows
individual firmware to and Linux
update • Offline:
• Need to select None
individual hardware
devices to be updated
Scripted deployment to a Use this scenario when you: • Windows: • Online:
remote host • Are familiar with hpsum -s -target HP ProLiant Support Pack for
(Run HP SUM from a command line tools Target1 -target
Windows and Linux
Target2
workstation and update a • Must perform a or
-username User1
remote host over the customized, scripted -password PW1 Smart Update Firmware DVD
network using scripts.) deployment or
• Linux:
• Need to update ./hpsum -s HP Integrity Support Pack for
multiple targets -target Target1 Windows
including OA, VC, and -target Target2 or
server-based firmware -username User1 HP Integrity BL8x0c i2,
• Need to update all -password PW1 rx2800 i2, and Superdome 2
enclosure firmware Servers Bundles for Windows
and Linux
• Offline:
None
Automatic Deployment to Use this scenario when you: The HP Smart Update • Online:
one or more servers in a • Do not have an Firmware DVD takes None
HP BladeSystem enclosure operating system care of this
• Offline:

Introduction 12
 Scenario Description HP SUM command HP deliverable
(use the HP Smart Update installed on a server automatically HP Smart Update Firmware
Firmware DVD with blade DVD
embedded HP SUM to • Want an automatic
deploy firmware updates way to deploy firmware
to one or more blades) updates
• 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 The same scenario as • Windows: • Online:
enclosure manually shown in the “Interactive,
hpsum HP BladeSystem Firmware
For more information, see graphical deployment to a
• Linux: Update Bundles for Windows
the HP website remote host” or “Scripted
and Linux
deployment to a remote ./hpsum
(http://www.hp.com/go or
/matrixcompatibility). host” scenarios discussed
HP Smart Update Firmware
previously in this table
DVD
• Offline:
HP Smart Update Firmware
DVD

Deploying firmware for ProLiant servers using the HP Smart

Update Firmware DVD
The HP Smart Update Firmware DVD provides a collection of firmware bundles containing HP SUM and
firmware for ProLiant servers in an ISO image that can be used either in offline (an automatic or interactive
mode), or online (a scripted or interactive mode) modes. The HP Smart Update Firmware DVD provides
firmware for supported HP ProLiant servers and options. The Firmware DVD contains all the firmware for the
supported HP ProLiant servers including BladeSystem enclosures and Virtual Connect firmware.
• In offline mode, the HP Smart Update Firmware DVD boots a small Linux kernel and enables firmware
updates to occur on a single server using the HP SUM software.
• In online mode, users can leverage the autorun utility to launch HP SUM or browse the DVD to the
\hp\swpackages directory and then execute it directly.
All firmware smart components are placed in the \hp\swpackages directory for use by HP SUM. If
additional firmware smart components are required, then the HP Smart Update Firmware DVD can be copied
to a USB key, and these additional components added to the \hp\swpackages directory. If HP SUM supports
the type of firmware added, then it is automatically added the next time HP SUM is executed.

CAUTION: The HP Smart Update Firmware DVD and its contents must be used only by
individuals who are experienced and knowledgeable with HP SUM. Before using HP SUM to
update firmware, back up the target server, and take all other necessary precautions so that
mission-critical systems are not disrupted if a failure occurs.

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

Introduction 13
 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.
If you use OA version 2.51 or later, click the Rack Firmware link on the main OA website for a list of all major
firmware versions deployed in your enclosure. HP supports the current and two previous versions of the HP
Smart Update Firmware DVD.

NOTE: The Onboard Administrator and Virtual Connect Ethernet and Fibre Channel Modules
are supported only in online deployments on HP ProLiant servers.

NOTE: You can add firmware components to the USB drive key in the /hp/swpackages
directory.

IMPORTANT: Before deploying firmware updates to a target server, be sure that a recent backup
of the target server is available in the event the deployment procedure fails.

For more information about deploying firmware on HP ProLiant servers, see the HP Smart Update Firmware
DVD User Guide on the HP website
(http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManu
al&lang=en&cc=us&docIndexId=64179&taskId=101&prodTypeId=18964&prodSeriesId=345557).

HP SUM supported firmware for HP ProLiant servers

The following table describes firmware types that are supported by HP SUM.
Firmware Types Supported by HP SUM

System ROM Yes

iLO firmware Yes, both server-based and directly to the iLO Management NIC port
Broadcom NIC Yes
firmware
Mellanox NIC firmware Yes
QLogic NIC firmware Yes
PowerPIC firmware Yes
Smart Array controller Yes
firmware
SAS and SATA hard Yes, some older SATA hard drives require offline mode
drive firmware behind
Smart Array controllers
SAS and SATA hard Yes
drive firmware behind
non-Smart Array
controllers
Emulex, QLogic, and Yes, in offline mode only because of HBA firmware limitations
Brocade Fibre Channel
HBA firmware
Tape Blade firmware Yes
OA firmware Yes, online only
VC firmware Yes, online only beginning with HP SUM 4.1.0.
HP SUM only updates a VC if the VC is in a good health state, the VC is part of a
domain, and if the VC is in a paired or redundant configuration.
CPLD firmware No

Introduction 14
 Firmware Types Supported by HP SUM

HP StorageWorks MDS Yes

600 enclosure firmware
MSA 2000 firmware No
(P2x00 firmware)
D2600/D2700 Yes when attached through a Smart Array controller
firmware
3Gb/s SAS BL switch Yes, online only
FCoE/CNAs Yes, in offline mode only because of FCoE/CNA firmware limitations

Deploying Integrity firmware bundles with HP SUM

You can use HP SUM to deploy components delivered with the Integrity Server Bundles, or use HP SUM to pull
updates from the web. For supported HP SUM versions, see "Support and Limitations of HP SUM (on page
10)."
Deploying firmware to the HP Integrity Servers, including BL8x0c i2, rx2800 i2 server, and Superdome 2
servers, is done remotely and is the same as deploying other firmware, such as OA, with the following
exceptions:
• You must specify the IP address of the Monarch (primary) iLO-3 MP on the server as the target to be
updated.
• On the Select Items to be Installed 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 server does not automatically reboot, so you must either
manually reboot or wait for the next regularly-scheduled maintenance reboot for the firmware to be
activated. The default behavior is Upload but Do Not Activate.

HP SUM supported firmware for HP Integrity servers

Component Supported
Online System ROM firmware Yes

FPGA firmware Yes

iLO-3 MP firmware Yes
Power Monitor firmware Yes
Superdome 2 firmware Yes

OA firmware Yes
VC firmware Yes

Introduction 15
HP SUM User Interface

Deployment scenarios
HP SUM deploys firmware and software on a local host or one or more remote hosts. Except for Integrity
servers, the remote hosts must be online and running the same operating system as the system running HP
SUM. For example, when the remote hosts are running Linux, HP SUM must also be running on a Linux
operating system. However, this is not true for Integrity servers. Integrity servers can be running HP-UX or
other operating systems, and the updates can be performed through iLO or the OA.
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.

Keyboard support
The HP Smart Update Manager graphical user interface has accelerator keys that enable you to manage and
control common tasks quickly. To ensure proper navigation, the following are a few reminders.
• Depending on the operating system, you must 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.

HP SUM User Interface 16

Source selections

Use the Source Selections screen to:

• Select repositories that contain updates
• Add repositories
• Edit repositories
• Configure repository components
• Select whether to pull updates from the HP FTP site
• Select whether to display firmware-only, software-only, or both types of updates in each repository
Repositories are the directories that contain the bundles, also called release sets, and individual smart
components HP SUM uses to update targets. Update bundles are groups of firmware and software
components that HP releases. HP SUM allows you to choose one or more repositories or check the HP FTP site
for the latest versions of the components.
To add a new repository, click Add New Repository. For more information about adding a new repository,
see "Add Repository (on page 19)."
The Current Repositories table displays the following information:

HP SUM User Interface 17

 • Name—This field displays the repository name. Select the repositories you want to use by checking the
box next to the repository name. If you want to edit a repository, highlight the entire line to activate the
Edit and Remove buttons.
o HP SUM automatically creates a repository named Default. This repository is the folder that holds the
HP SUM application.
o 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 site to a target until the Install
button is selected, unless the component is needed to discover supported devices. If components are
needed for discovery, then you are prompted to allow this action. The ftp.hp.com checkbox is
cleared by default. To pull updates from the web, select the ftp.hp.com checkbox. 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.
o Use the last downloaded repository from the HP FTP site (ftp://ftp.hp.com)—This option includes the
components that have been previously downloaded from the ftp.hp.com site. The location for the
previously downloaded components is the %TEMP%\hp_sum\ directory. To use components
downloaded from the HP website, select this checkbox. The repository cannot be edited.
• Location—This field displays the location of the repository. The repository path cannot be edited.
o Additional—This field displays more information, or links to functions. It is used for setting proxy
server settings to access ftp://ftp.hp.com.
• Addition Information—This field provides more information about the bundle. Click Proxy Options in
this field to change proxy settings for your network.
• Status—This field allows you to view the repository's contents, and displays whether you need to
configure any components in the repository.
o Click Repository Contents to view the contents of the chosen repository and their version number.
o Click Configure Components to select components to configure. This option is available only for a
local repository with components that require configuration.

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.

Set 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. To enter proxy server details:
1. On the Source Selections screen, click Proxy Options in the Current Repositories table. The link is in the
“Additional” 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. Choose Server or Script.
a. If you chose Server, enter the server IP Address and Port information.
b. 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.

HP SUM User Interface 18

 4. Enter the User ID (if necessary).
5. Enter the Password (if necessary).
6. Click OK.

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:
• If a component is located in more than one repository, HP SUM will use the version that is in the
repository that is listed highest on the Current Repositories table.
• If a component is located in a local repository and it is also on ftp.hp.com, HP SUM will use the local
version.

Add Repository

If the default repositories do not include the component or bundle updates, use the following steps to add a
new repository:
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.
o Both - HP SUM will display component firmware and software updates that are ready.
o Firmware only - HP SUM will only display component firmware updates that are ready.
o Software only - HP SUM will only display software firmware updates that are ready.

HP SUM User Interface 19

 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.
4. Click OK.

Edit Repository
You can edit a repository to change its name or location, or to filter the repository’s updates.
Follow these steps to edit a repository:
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.
2. Edit the Repository Name.
3. 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, select the repository in the Current
Repositories table, and then click Edit Repository.
o Both - HP SUM will display component firmware and software updates that are ready.
o Firmware Only - HP SUM will only display component firmware updates that are ready.
o Software Only - HP SUM will only display software firmware 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.

4. Click OK to save the changes.

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.

Remove Repository
Follow these steps to remove a repository
1. Select the repository you want to remove by clicking its row in the table to highlight it.
2. When the correct row is highlighted, click Remove Repository.
3. Click Yes if you want to remove the repository, click No to cancel.

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.

Configure 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

HP SUM User Interface 20

 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, then 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, then 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.
Configurable components are indicated in the Status column on the Select Sources screen.
Use these steps to configure a component.
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 will only use the
component located in the repository closest to the top of the Current Repositories table.

Download components for target discovery

If you choose to pull updates from the web, when you click Next on the Source Selections screen you will 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 the Linux or Windows® OS, you can remove
these components from the list to reduce the number of components that HP SUM downloads to your system.

HP SUM User Interface 21

Select targets

The Select Targets screen, allows you to do the following:

• Select targets (for example, servers or enclosures)
• Add targets
• Edit targets
• Remove targets
• Generate and view reports
• Manage groups
• Enter credentials for 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 "Find and
Discover Targets (on page 24)" or "Add Single Target (on 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
"Manage Groups (on page 25)."

HP SUM User Interface 22

 The table displays the following target information:
• Check box—Targets with selected checkboxes are updated. Click the checkbox 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 "Enter Target Credentials
(on page 24)."

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.
• 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).

Inter-target dependency
HP SUM will find potential targets by checking the OA host server list for all targets you add. HP SUM will ask
you if you want to add the potential targets it found, and will do 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/target update are
met. These include system requirements (for example, libraries and services) for the component or
target/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:
o Health component requirement for installation of the SNMP Agents
o Required Operating System libraries
o 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: HP recommends that you check for dependencies before starting HP SUM.

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.

HP SUM User Interface 23

Target types
Supported target types include:
• Server–a local host or a remote server.
• iLO
• Onboard Administrator
• Virtual Connect

Find and discover targets

To search for multiple targets on a network:
1. Click Find Targets.
2. Select IP Address Range, Port Address, or LDAP Scan for Remote Targets, and then click OK.
o IP Address–This option 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.
o Port Address–This option enables you to search in a range of IP addresses and specific port address.
o LDAP Scan for Remote Targets–This option enables you to search for targets using an LDAP query.

Add Single Target

Use the following steps to add 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 will detect 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 root or administrator Username and Password.
6. Click OK. This will begin the discovery process of the target that is added.

Enter Target Credentials

You must enter the credentials (administrator user name and password) for all targets, including the Local
Host, if you are updating it.
1. In the Select Targets screen table, select one or more targets by clicking to highlight the row(s).
2. Click Enter Credentials.
3. In the Enter Credentials for the Target(s) dialog box, select one or more targets. The credentials you
enter will be 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.
b. Select what HP SUM should do if it detects an update already running.

HP SUM User Interface 24

 6. Click OK to save and close the dialog box.
7. Click Done.
8. In the Select Targets screen table, the Status field will display progress messages as HP SUM verifies the
credentials you entered.

Edit Target
Use the following steps to edit a target:
1. Highlight a target, and then click Edit Target.
2. Type a brief description of the target (optional).
3. Enter the root or administrator username and password.
4. Click OK after entering the information to exit this page.

Remove 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.

Manage Groups
Use the following steps to add or edit groups:
1. Add a new group:
a. Enter a Group Name.
b. Enter a Description (optional).
c. From the Available Targets list, select the targets to add to the group.
d. Click Add.
e. When you are finished, click OK.
2. Edit an existing group:
a. To add one or more targets to the group, select targets in the Available Targets list, and then click
Add.
b. To remove one or more targets from the group, select the targets in the Targets in Group list, and
then click Remove.
3. Enter a Description (optional).
4. Click OK.

Install updates
The Review/Install Updates allows you to do the following:
• Review target information
• Address any dependency problems
• Select installation options
• Select reboot options

HP SUM User Interface 25

 • Schedule updates
• Select bundles to install on bundles and/or targets
• Select components to install to bundles and/or targets
• Generate and view reports
• Abort an installation
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 "Select Bundles (on page 27)" or "Select Components
(on page 28)."
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.
o The Select Bundles screen lists updates bundled in release sets first, by bundle, followed by
unbundled updates components. If a bundle is checked, then 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.
o 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, HP SUM adds an expansion box next to the most
recent version of the component. To install and 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.
• 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
Click Install to begin installing the updates after you have resolved all dependency issues. For more
information, see "Select Devices (on page 28)."

HP SUM User Interface 26

Abort installation
Click Abort Installation to complete the installation of the current component and then abort the installation of
the remaining components.

View failed dependencies

If a failed dependency occurs, then you must resolve it by ensuring the prerequisite libraries or the
appropriate software or firmware components are available before proceeding with the installation. Click on
the Failed Dependencies to see what changes you need to make.

Select bundles
The Bundle Components Selections screen displays the following information for a selected target:
• Select Devices—This field displays all bundled and unbundled updates you can install on the target.
• Status—This field 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—This field displays the bundle or component version installed on the target.
• Active Version—This field 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—This field displays the newest version available, if it is not active. Some updates
require rebooting the target. If the target has not been rebooted, then the new version is installed, but
not yet active.
• Optional—This field displays links to actions you can perform to for the target.
o Select Devices—Click this link to select 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.
o Installation Options—Click this link to open the Install Options screen. For more information about
installation options, see "Installation Options (on page 29)."
o Re-analyze—An error or warning might appear 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.
Use the re-analyze function when you have decided on a specific bundle or component version to
apply, but HP SUM has found a newer bundle or component version. 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.
To select the bundles to update on 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.

HP SUM User Interface 27

 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 failed dependency.

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.

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 "Edit Repository (on page
20)."

Select components
This screen allows you 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.
1. In the Review/Install window, click Select Components for a target. The Select Components screen
shows applicable components.
2. Select the components that you want to install.
3. Click Configure Now and then select Upload and Active to activate the update. To wait until the next
scheduled maintenance to activate the update, select Upload and Do not Activate.
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 to the failed dependency.

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 "Edit Repository (on page
20)."

5. Click OK.

View firmware mismatch details

If you have a multi-blade server, you might encounter an instance where the device bays are running different
versions of component firmware. Before you can update the server, you need to first correct the mismatch.
Use HP SUM to update the bays so that they are using the same firmware version. After you update the bay
firmware, close HP SUM. To perform the remaining updates, reopen HP SUM.

Select 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.
To select devices:
1. To reach the Select Devices screen, click Select Devices on the Select Bundles or Select Components
screen.
2. Select the checkbox 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.
3. View any errors or warnings displayed at the bottom of the screen. Correct errors before continuing.
Warnings do not prevent the installation, but continuing an installation without correcting the problem

HP SUM User Interface 28

 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.

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 and/or system failure.

If you have a problem with an update, you can use the Installation Options screen to rewrite or downgrade
the firmware and software. You need to download the bundle or component version that you want to
reinstall.
If you set the Installation Options from the Review/Install Updates screen, you set these options for all targets.
If you want to set installation options for specific targets:
1. Click Select Bundles or Select Components for the target.
2. Click Installation Options for the target.
3. Click Check here to enable force options.
a. Click Downgrade or Rewrite, depending on whether you want to downgrade the firmware version,
or overwrite the current firmware version.
b. Force upgrade bundles, firmware, or software.

— Bundles—Enables the selection of older PSP and firmware bundles.

— Firmware—Allows the selection of older firmware components.
— Software—Allows the selection of older PSP or software bundles.

Reboot options
If you set the Reboot Options from the Review/Install Updates screen, the reboot options are set for all the
targets. If you want to set reboot options for only specific targets, click Select Bundles or Select Components
for the target, and then click Reboot Options for the target.
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 Integrity servers.

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.

Schedule Updates
Use these steps to schedule a time to run the updates.

HP SUM User Interface 29

 1. Click Schedule Update.
2. Click Create Schedule, type a schedule description, 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 will be completed when you click Install on the Review/Install Updates screen.

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.

Generate and View Reports

You can generate either an HTML or XML report file. You can view both files in a web browser, such as
Internet Explorer. The supported browsers for viewing the report files are Microsoft® Internet Explorer 6.0
and Mozilla Firefox 3.5 and above. The XML reports also allow you to write programs to pull the report
information and display it in other locations.

Generate 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.
o Inventory Selections - This report provides the details of the contents in a repository.
o Target Firmware - This report provides the 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.
o Target Installable details - This report provides the selected targets or devices that require the
update. HP SUM will collect all the information available for this report on the Review/Install Update
screen.
4. Choose the type of report to generate:
o HTML
o XML
5. Check the View generated report box if you want to view the report immediately.
6. Click Generate.

View a Report
1. Click View Report.
2. Click the Browse button and then select the report you want to view, and then click View.

HP SUM User Interface 30

Scripted deployment

Command-line interface
The HP SUM command-line interface enables you to script custom installations.

Command-line syntax
The general command-line syntax for HP SUM is:
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] [/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"] [/logdir "path"]
[/v[erbose]] [/veryv[erbose]] [/report][/inventory_report]
[/firmware_report] [/On_failed_dependency:<parameter>] [/oa_username
<username>] [/oa_passwd <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>...]
The following commands are only supported by Superdome 2 servers:
[/update_type<type>] [/device_list <device[,device]…>] [/reboot_list
<npar[,npar]…>]
HP SUM with Onboard Administrator requires a user ID and password to log in. The user ID must be an
administrator equivalent ID and not an operator or user equivalent level ID.

NOTE: All arguments and information enclosed in brackets are optional. The arguments may be
prefixed with either a '-' or '/' character. These examples show only the '/'.

On Windows operating systems, use a slash (/) before each argument. On Linux operating systems, 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 using a double-byte character set will not be displayed
correctly.

Scripted deployment 31
Command-line arguments
HP SUM 5.0.0 recognizes the following command-line arguments. These arguments can be used to
pre-populate the GUI in the Source Selection and Review/Install Updates screens. If you specify the target
and credentials, then the /s[ilent] parameter is required to proceed with the installation.
You cannot use some arguments, such as /romonly and /softwareonly together.
Help Description
/h[elp] or /? This argument displays command line help information.

Installation options Description

/f[orce] This argument enables you to override or downgrade an existing component
installation. This argument produces the same results as /f:software.
/f[orce]:bundle This argument enables you to override or downgrade the existing installation of
components in the selected bundle.
/f[orce]:rom This argument enables you to override or downgrade the existing installation of the
selected firmware components (applies to firmware only).
/f[orce]:software This argument enables you to override or downgrade the existing installation of the
selected software components.
/f[orce]:all This argument enables you to override or downgrade the existing installation of the
selected software components, firmware components, and bundles.
/g or /downgrade This argument enables you to downgrade to an earlier version of firmware for
multi-target devices such as hard drives and array controllers (applies to firmware
only).
/e or /rewrite This argument enables you to downgrade to an earlier version of firmware for
multi-target devices such as hard drives and array controllers (applies to firmware
only).
/s[ilent] This argument causes the installation to run silently with no GUI or console output. All
data writes to the log file. Any generated prompts use the default option and continue
the installation without user input. If a component requires input before installation
(such as configuration information), then the component installation fails, and an error
message writes to the log file.
Failed dependencies are not reported to the user when using the /s[ilent]
argument. To check for failed dependencies, remove the /s[ilent] argument and
reissue the command line. The HP SUM GUI appears.
/c[omponent]<comp This argument specifies components to install.Components to install can be specified
onent_to_install> with or without the /c[omponent] argument.
or
<component1_to_in • If using the /c[omponent] argument, then only one component can specified with
stall> the argument. However, multiple /c arguments and components can be specified
<component2_to_in on the same line.
stall> • If the /c[omponent] argument is not used,then multiple components can be
specified at the same time, but the components must be separated by a blank and
listed after all the arguments on the command line.
• The components are installed in the order provided unless dependencies between
components require installation in a different order. If so, the utility changes the
installation order based on the component dependencies to ensure the successful
installation of as many components as possible.
• Multiple components and bundles can be specified on the same command line.
When mixing components and bundles on the command line, the filter switches
control what components and bundles are installed.
/group This argument specifies an already defined group name in the HP Smart Update

Scripted deployment 32
Installation options Description
"group_name" Manager graphical user interface.
/b[undle] This argument specifies bundles to install. Bundles to install can be specified with or
<bundle_to_instal without the /b[undle] argument.
l> or
<bundle1_to_insta • If using the /b[undle] argument, then only one bundle can specified with the
ll> argument. However, multiple /b arguments and bundles can be specified on the
<bu/use_latestndl same line.
e2_to_install> • If the /b[undle] argument is not used, multiple bundles can be specified at the same
time, but the bundles need to be separated by a blank and listed after all the
arguments on the command line.
This argument specifies bundles to install. Bundles to install can be specified with or
without the /b[undle] argument.
If using the /b[undle] argument, then only one bundle can specified with the argument.
However, multiple /b arguments and bundles can be specified on the same line.
If the /b[undle] argument is not used, multiple bundles can be specified at the same
time, but the bundles need to be separated by a blank and listed after all the arguments
on the command line.
/allow_update_to_ This argument is a filter switch and enables the user to install newer versions of
bundle 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 This argument is a filter switch and enables the user to install components which are not
_components 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 Smart Update
Manager to use the bundle with the latest version for installation.
/use_location This argument specifies a directory or file share that contains the PSP, ISP, and
"file_share" components for use with HP SUM. The file_share format must be a mapped file share
and not in Universal Naming Convention (UNC) format. If this argument is not
specified, the directory containing hpsum.exe or HP Smart Update Manager 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 attempting to access
the file share. Use those arguments only when connecting to a target system.
/use_web This argument specifies that the checkbox for Check ftp.hp.com on the Source Selection
screen is selected. This enables components to be retrieved from hp.com and used in
the list of possible updates.
/use_proxy <Proxy This argument enables the inclusion of a proxy server (and port number) to access
server> ftp.hp.com. This parameter must be used with /use_web. For example, /use_web
/use_proxy <1.22.33.44:80>.
/proxy_script This argument enables the inclusion of a proxy script to access ftp.hp.com. This
<Proxy script> parameter must be used with /use_web. For example, /use_web /proxy_script
<autoproxy.com>.
/proxy_password This argument sets the password to be used for an authenticating proxy server.
<password>
/use_d[ownloaded] This argument specifies that the checkbox 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.
/use_snmp This argument specifies that components that use SNMP protocol and the AMS
components are available for installation by default. When the /use_snmp argument is

Scripted deployment 33
Installation options Description
used, the AMS components are required, but the WMI components are optional.
/use_wmi This argument specifies that components that use 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 This argument specifies that components which Agentless Monitoring service (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 argument is a filter switch and allows the user to only see the firmware components
needed for installation. When using this filter switch, you must exit and restart HP Smart
Update Manager if you wish to return to an unfiltered state.
Do not use the /romonly argument with the /softwareonly argument.(Applies to
firmware only.)
/softwareonly This argument is a filter switch and allows the user to only see the software components
needed for installation. When using this filter switch, you must exit and restart HP Smart
Update Manager if you wish to return to an unfiltered state.
Do not use the /softwareonly argument with the /romonly argument.
/express_install This argument starts express install (for local host only). The HP Smart Update Manager
(HPSUM) performs discovery,install, or exit without user interaction. The user can
cancel or terminate HP Smart Update Manager.

Overriding errors Description

/tpmbypass or These arguments specifies that if a Trusted Platform Module (TPM) is enabled, the
/ignore_tpm warning message should be ignored and component installation will be allowed to
continue.
/ignore_warnings This argument allows the installation to proceed on a Superdome 2 target even when
warnings are returned during analysis.
/continue_on_erro This argument causes the installation to continue and ignore errors. Valid values are :
r <error> * <error>=ServerNotFound and
* <error>=BadPassword.
* <error>=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.
/override_existin This argument is used to define the behavior when a remote target has an existing HP
g_connection Smart Update Manager session in progress. It overrides the session in progress and
reinitializes the installation framework on the remote host.
/On_failed_depend This argument provides HP Smart Update Manager <parameter> the information of
ency: <parameter> 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 component(s) and proceeds with any updates
that do not have dependency failures. Force attempts all updates, even if they have
dependency failures.

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.

Scripted deployment 34
Reboot options Description
• All components selected for installation are successfully installed.
• At least one of the installed components requires a reboot to complete its
installation.
/reboot_message This argument displays the specified reboot message on remote consoles connected to
"reboot message" the server you want to reboot. You must use this argument with the /reboot option or the
argument is ignored.
/reboot_delay This argument delays the reboot of the server for the length of time specified by the
timeout_in_secs timeout_in_seconds variable.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 This argument simulates the installation for a test run. Nothing is installed.

Targets Description

/user <username> or This argument enables you to log in to the remote targets with the user ID. For the OA
/username target, see /oa_username argument.
<username>
/psswd <password> This argument enables you 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, see /oa_password argument.
/target This argument is the IP address or the DNS name of a remote host which can be remote
"netAddress" server, remote iLO NIC port, Virtual Connect Ethernet or Fibre Channel Module for
c-Class BladeSystem, or BladeSystem Onboard Administrator(OA).
When two Onboard Administrators are in an enclosure, this argument should be the
active Onboard Administrator.When specifying the IP address, use either the IPv4 or
IPv6 format.
/current_credenti This argument enables the credential of the local host to be used as the credential to
al access the targets instead of providing the username 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 username credential for OA associated with VC specified
with "target" command-line parameter. Only one set of OA credentials can be
specified with command-line parameters. You can only add multiple VC targets to
command-line parameters with "target" parameter 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 Virtual Connect. HP SUM queries it from a specified VC target.
To update multiple VCs with different username and password or VCs with OAs which
have different credentials, the corresponding input files OAUID and OAPWD must be
used.

Scripted deployment 35
Targets Description
/oa_password This argument provides the password credential for OA associated with VC specified
with "target" command-line parameter. Only one set of OA credentials can be
specified with command-line parameters. You can only add multiple VC targets to
command-line parameters with "target" parameter 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 associated with Virtual Connect. HP SUM queries it from a specified VC target.
To update multiple VCs with different username and password or VCs with OAs which
have different credentials, the corresponding input files OAUID and OAPWD must be
used.

Log files Description

/logdir "path" This argument enables you to redirect the output from HP SUM or the HP BladeSystem
c-Class Onboard Administrator 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 These arguments enable you to set the verbosity level for the HP SUM execution log file,
/veryv[erbose] hpsum_execution_log_<date>_<time>.log. Using one of these arguments increases the
level of detail that is retained in the log file. The default value is normal verbosity.

Generating reports Description

/report This argument generates a report listing of the target summary and how the
components in the repository affect the target. For example, whether each component
applies to the target or not. 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 Smart
Update Manager is initiated from. If that location is write-protected, the files can be
found in the same directory as the HP Smart Update Manager log files.
/inventory_report This argument 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 directory from where HP SUM is
initiated. If that location is write-protected, the report can be found in the same
directory as the HP SUM log files.
/firmware_report This argument 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 directory from where HP SUM is
initiated. If that location is write-protected, the report can be found in the same
directory as the HP SUM log files.

Scripted deployment 36
 Using input files Description
/inputfile This argument enables you to script the deployment of firmware and software to
“filename” multiple remote systems at one time. For details of the file format and commands, see
"Input files (on page 41)."

/deleteinputfile This argument enables you to instruct HP SUM to delete the input file after it has been
read in.

Superdome 2 server Description

commands
/update_type<type> This argument 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 Use this argument when the /update_type argument is "PARTITIONS." This argument
<device[,device]…> 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 Use this argument when the /update_type is "ALL" or "PARTITIONS."
<npar[,npar]…> 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

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.
The following table shows what updates if no switches are currently installed:
Command G7 and earlier
no switches SNMP

/use_ams Nothing
/use_snmp SNMP
/use_wmi WBEM
/use_ams/use_snmp SNMP
/use_ams/use_wmi WBEM
/use_wmi/use_snmp WBEM and SNMP
/use_ams/use_wmi/ WBEM and SNMP
use_snmp

The following table shows what updates if SNMP switches are currently installed:
Command G7 and earlier

no switches SNMP

/use_ams SNMP
/use_snmp SNMP
/use_wmi WBEM and SNMP
/use_ams/use_snmp SNMP

Scripted deployment 37
 Command G7 and earlier

/use_ams/use_wmi WBEM and SNMP

/use_wmi/use_snmp WBEM and SNMP

/use_ams/use_wmi/us WBEM and SNMP

e_snmp

The following table shows what updates if WBEM switches are currently installed:
Command G7 and earlier

no switches WBEM

/use_ams WBEM
/use_snmp WBEM and SNMP
/use_wmi WBEM
/use_ams/use_snmp WBEM and SNMP
/use_ams/use_wmi WBEM
/use_wmi/use_snmp WBEM and SNMP

/use_ams/use_wmi/us WBEM and SNMP

e_snmp

Component configuration for Windows components only

To configure components without using the HP Smart Update Manager GUI, issue the command,
hpsum_config <component_to_configure>. This command presents the same configuration screens seen
in the HP Smart Update Manager GUI. You must run this command from a CD or other read-only media, or
the component cannot be configured. Configuration for a given component only needs to be executed one
time. The configuration is stored within the component and is propagated to all target servers when deployed
through HP Smart Update Manager GUI or command line. To change the configuration, rerun
hpsum_config against the component and a new configuration writes out. 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 the Windows Server® 2008 with the Server Core
option, you must access the system as a remote host using HP Smart Update Manager 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:
o System ROM
o Smart Array controller
o Hard drives
o iLO
• Software—later version of:
o HP Insight Diagnostics Online Edition for Windows Server 2003 (cp008097.exe)

Scripted deployment 38
 o HP System Management Homepage for Windows (cp008257.exe)
• HP Smart Update Manager
o 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 from the 7.90 PSP and firmware components, which HP SUM determined
are required to 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 from the 7.80 PSP, which HP SUM determined are required to be installed,
were installed. No firmware was installed.
Example 3:
This command-line input deploys firmware:
hpsum /romonly
Results: All firmware components, which are required to 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 firmware components, software components from the 7.90 PSP, cp008097.exe, and
cp008257.exe were installed on Management Server1, Management Server2, and Management Server3.

Scripted deployment 39
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.
To view the installation log file locations, see "Viewing the installation results."

Return code Value Linux Windows® Text

SUCCESS_NO_REBOOT 0 0 0 The installation was successful.
SUCCESS_REBOOT 1 1 1 The installation was successful, but
a reboot is required.
SUCCESS_NOT_REQUIRED 3 3 3 The component was current or not
required.
FAILURE_GENERAL -1 255 255 A general failure occurred. For
details, see the error log.
FAILURE_BAD_PARM -2 254 254 A bad input parameter was
encountered.
FAILURE_COMPONENT_FAILED -3 253 253 The installation of the component
failed.

Windows smart component return codes

Error level Meaning
0 The smart component failed to install. For more details, see the log file.

1 The smart component installed successfully.

2 The smart component 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 installed successfully.

1 The smart component installed successfully, but the system must be restarted.

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 failed to install. For more details, see the log file.

Multi-target servers:
Error level Meaning
0 The installation of the deliverable is successful. No reboot is required.

Scripted deployment 40
 Error level Meaning
1 The installation of the deliverable is 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 installing to a remote target, such as Onboard Administrator or other
network-based deployment, this return code indicates that the target cannot be found.
5 The installation was canceled by a user before anything could be installed.

6 The installer cannot execute because of an unmet 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.

Input files
HP SUM provides the ability to script the update of multiple, individual targets or groups of targets (HP
ProLiant and Integrity server 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 [END] 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. The DRYRUN=YES option can be used 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 separator can be commas, semicolons, or spaces.

NOTE: The credentials can be left out of the file for greater security and passed on the command
line to HP Smart Update Manager. The only limitation of this is that the userID 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 normal 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 it is not stored
in the same location as the HP SUM executables. The <filename> field can be enclosed in double quotes to
enable paths with spaces. Also, the input file itself might contain the same flags on the command line. The
usual command-line flags can still be used with the -inputfile flag and takes precedence over any given
input file.

Scripted deployment 41
Command-line usage of input file
The form for the HP SUM command line using an input file is hpsum -inputfile <filename>. The input
file itself can contain the same flags on the command line. The usual command line flags can still be used with
the -inputfile flag, and takes precedence over any given input file. The <filename> field can be enclosed
in double quotes to enable paths with spaces.

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 parameters and their values. Each
configuration setting must appear on a fresh line in the file along with its value. Comments start with a
# character at the beginning of the line. Only one # is allowed on any line.
• Target
You can provide remote host targets to HP Smart Update Manager. 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 a special header "TARGETS" enclosed in a pair of square brackets:
[TARGETS]
Targets section ends with the special string "END" enclosed in a pair of brackets:
[END]
The keyword TARGETS can be suffixed with an optional arbitrary string. This 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]
o 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 into
one or more remote targets, you can do so by setting the variable USECURRENTCREDENTIAL to
YES. Login credentials for one or more hosts can be supplied using the variables UID and PWD. If
given at the beginning of a TARGETS section, both variables must be used. If given in the middle of
a TARGETS section, one or the other can be used to override the selected variable and continue
using the active value for the remaining variable.
o Remote Target: A remote target can be specified 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.

Scripted deployment 42
Error reporting
If errors are encountered in the input file, HP Smart Update Manager 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 file parameters

Parameter Description Possible values
SILENT This parameter causes the installation to run silently YES, NO
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), then the
component installation fails (unless the
IGNOREERRORS = "FailedDependencies"
parameter is supplied), and an error message is
written to the log file.
FORCEALL This parameter forces both firmware and software YES, NO
components.
FORCEROM This parameter forces updates to firmware YES, NO
components.
FORCESOFTWARE This parameter forces updates to software YES, NO
components.
FORCEBUNDLE This parameter enables you to override or YES, NO
downgrade an existing installation of components
in the selected bundle.
DOWNGRADE This parameter enables you to downgrade to an YES, NO
earlier version of firmware for multi-target devices
such as hard drives and array controllers. (Applies
to firmware only.)
REWRITE This parameter enables you to rewrite the same YES, NO
version of firmware only for multi-target devices
such as hard drives and array controllers. (Applies
to firmware only.)
REBOOTALLOWED This parameter enables you to reboot, if required. YES, NO
REBOOTMESSAGE This parameter enables you to create a message to Any string (not exceeding
be displayed prior to rebooting. 256 characters)
REBOOTDELAY This parameter enables you to delay before Time in seconds
rebooting.
COMPONENTSLIST This parameter enables you to limit the list of Component names with file
components to be updated. extensions (.exe, .rpm, or
.scexe)
BUNDLESLIST This parameter enables you to limit the list of bundle Bundle file names
xml files to be filtered.
ALLOWUPDATEBUNDLE This parameter is a filter switch and enables you to YES, NO
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.

Scripted deployment 43
Parameter Description Possible values
SKIPTARGET This parameter defines the behavior when a remote YES, NO
target has an existing HP SUM session in progress.
This parameter enables you to skip the host if an
existing HP SUM session already exists. A NO
overrides the session in progress and reinitializes
the installation framework on the remote host.
IGNOREERRORS This parameter causes the installation to continue ServerNotFound,
and ignore errors. BadPassword,
The ServerNotFound option can be used to bypass FailedDependencies
inactive or unavailable remote hosts when
deploying firmware or software to multiple remote
hosts at the same time.
FailedDependencies can be used to ignore any
failed dependencies and proceed with the ones
that are ready to be installed.
SOURCEPATH This parameter can be used to provide a single Directory path
local repository path. This creates an inventory
from the given path instead of the local or default
repository.
USELATEST This parameter 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.
If no bundles are specified on the command line,
and multiple bundles are in the directory, then this
parameter enables HP SUM to use the bundle with
the latest version for installation.
DRYRUN This parameter simulates the installation for a test YES, NO
run. Nothing is installed.
OPTIONS This parameter can be used to specify the HP SUM One or more CLI switch
CLI options inside 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.
USESNMP This parameter specifies that components, which YES, NO
use 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 This parameter specifies that components, which YES, NO
use 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 parameter is a filter switch and allows the user YES, NO
to view only the firmware components required for

Scripted deployment 44
Parameter Description Possible values
installation.
Do not use the /romonly parameter with the
/softwareonly parameter.
SOFTWAREONLY This parameter is a filter switch and allows the user YES, NO
to view only the software components required for
installation.
Do not use the /softwareonly parameter with
the /romonly parameter.
USECURRENTCREDENTIAL This parameter enables the credentials of the local YES, NO
host to be used as the credentials to access the
targets instead of providing the username and
password explicitly for each target.
The assumption is that the current credentials are
valid for the targets being accessed. (Applies to
Windows® operating systems only.)
WEBUPDATENEEDED This parameter enables you to instruct HP SUM to YES, NO
include the components from the HP FTP site
(ftp://ftp.hp.com) in the list of possible updates.
USEPROXYSERVER This parameter enables the inclusion of a proxy String value
server (and port number) to access the HP FTP site For example,
(ftp://ftp.hp.com). 11.22.33.44:80
USEPROXYSCRIPT This parameter enables the inclusion of a proxy Web URL (for example,
script to access the HP FTP site (ftp://ftp.hp.com). autoproxy.com)
DELETEINPUTFILE This parameter enables you to instruct HP SUM to YES, NO (default)
delete the input file after it has been read in.
ONFAILEDDEPENDENCY This parameter instructs HP SUM how to proceed OmitHost (default),
when a component has a failed dependency. OmitComponent, Force
The default of OmitHost causes the host to be put
in a failure state and no install 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 DNS name IP address, DNS name
of a remote server, remote iLO NIC port, Virtual
Connect Ethernet or Fibre Channel Module for
c-Class BladeSystem, or BladeSystem Onboard
Administrator.
When two Onboard Administrators are in an
enclosure, this parameter is the active Onboard
Administrator. 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 This parameter enables you to log in to the target <username>
hosts with your user ID.
PWD This parameter enables you to use the password for <password>
the user ID specified in the UID.
The password is used to log in to target hosts.
LOGFILENAME = "path" This argument enables you to redirect the output Log file name
from HP Smart Update Manager or the HP
BladeSystem c-Class Onboard Administrator flash
utility to a different directory than the default

Scripted deployment 45
Parameter Description Possible values
location.
* For Windows components, the default location is
%SYSTEMDRIVE%\CPQSYSTEM\hp\log<netAddr
ess> 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 This parameter enables you to specify an SNMP SNMP read/write
read/write community string for local host access. community string
(Applies to Linux PSP only.)
CMALOCALHOSTROCOMMSTR This parameter enables you to specify an SNMP SNMP read-only
read-only community string for local host access. community string
(Applies to Linux PSP only.)
CMAMGMTSTATIONRWIPORD This parameter enables you to specify the IP IP address, DNS name
NS address or DNS host name of a system with
read/write access to serve as a management
station. You can specify multiple locations
separated by a space. (Applies to Linux PSP only.)
CMAMGMTSTATIONRWCOMMS This parameter enables you to specify an SNMP SNMP read/write
TR read/write community string for a system with community string
read/write access that serves as a management
station. You can specify multiple strings separated
by a space. (Applies to Linux PSP only.)
CMAMGMTSTATIONROIPORD This parameter enables you to specify the IP IP address, DNS name
NS address or DNS host name of a system with
read-only access to serve as a management station.
You can specify multiple locations separated by a
space. (Applies to Linux PSP only.)
CMAMGMTSTATIONROCOMMS This parameter enables you to specify an SNMP SNMP read/write
TR read/write community string for a system with community string
read-only access that serves as a management
station. You can specify multiple strings separated
by a space. (Applies to Linux PSP only.)
CMADEFTRAPCOMMSTR This parameter enables you to set a default SNMP SNMP community string
community string for traps. (Applies to Linux PSP
only.)
CMATRAPDESTINATIONCOM This parameter enables you to specify the SNMP SNMP trap destination
MSTR destination trap community string. (Applies to Linux
PSP only.)
CMATRAPDESTINATIONIPO This parameter enables you to specify the IP IP address, DNS name
RDNS address or DNS host name of a server as a
destination for SNMP traps, such as Systems Insight
Manager. (Applies to Linux PSP only.)
CMASYSCONTACT This parameter enables you to specify a person or String value
phone number for administration of this system.
(Applies to Linux PSP only.)
CMASYSLOCATION This parameter enables you to designate the String value
location of this system. (Applies to Linux PSP only.)
CMASTARTWEBAGENT This parameter determines whether the HP Insight • YES (start the web
Systems Manager Web Agent is started when the agent)
health application loads. (Applies to Linux PSP • NO (do not start the
only.) web agent)

Scripted deployment 46
Parameter Description Possible values
CMASTARTSTORAGEAGENT This parameter determines whether the HP Insight • YES (start the storage
Systems Manager Storage Agent is started when agent)
the health application loads. (Applies to Linux PSP • NO (do not start the
only.) storage agent)
CMASTARTNICAGENT This parameter determines whether the HP Insight • YES (start the web
Systems Manager NIC agent is started. (Applies to agent)
Linux PSP only). • NO (do not start the
web agent)
CMANOTAINTEDKERNEL This parameter determines whether the HP • YES (start the HP
Lights-Out management driver is started when the Lights-Out management
health application loads. (Applies to Linux PSP driver)
only.) • NO (do not start the HP
Lights-Out management
driver)
HPVCAVCRMSERVER This parameter 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 uses to VCA login ID
communicate with the VCRM. (Applies to Linux PSP
only.)
HPVCAVCRMLOGINPASSWD This parameter is the password for the login ID VCA login password
specified in the HPVCAVCRMLOGIN parameter.
(Applies to Linux PSP only.)
FORCE-OVERWRITE This parameter is used by the HP Systems YES, NO (default)
Management Homepage (hpsmh) to force
overwrite the SMH settings of an existing
configuration file.
ADMIN-GROUP This parameter is used by the HP Systems Up to five Linux groups,
Management Homepage (hpsmh) to set up security separated by spaces or
for the web server. (Applies to Linux PSP only.) semicolons, to enable
administrative access to the
web services.
USER-GROUP This parameter is used by the HP Systems Up to five Linux groups,
Management Homepage to set up security for the separated by spaces or
web server. (Applies to Linux PSP only.) semicolons, to enable
user-level access to the web
servers.
OPERATOR-GROUP This parameter is used by the HP Systems Up to five Linux groups,
Management Homepage to set up security for the separated by spaces or
web server. (Applies to Linux PSP only.) semicolons, to enable
operator-level access to the
web servers.
ANONYMOUS-ACCESS This parameter determines whether an anonymous YES, NO (default)
user can access the HP Systems Management
Homepage. (Applies to Linux PSP only.)
IP-BINDING This parameter is used by the HP Systems YES, NO (default)
Management Homepage to determine whether
hpsmh can use all available NICs and detect
subnets for its web services. (Applies to Linux PSP
only.)
IP-BINDING-LIST This parameter is used by the HP Systems IP address/NetMask pairs
Management Homepage to restrict the NICs and separated by semicolons

Scripted deployment 47
Parameter Description Possible values
subnets to use for its web servers. (for example,
The IP-BINDING parameter must be set to yes for 10.1.1.1/255.255.255.0
this parameter to be used during installation. ;10.2.2.2/255.255.255.
(Applies to Linux PSP only.) 0)
IP-RESTRICTED-LOGINS This parameter is used by the HP Systems YES, NO (default)
Management Homepage to restrict login access. To enable restrictions on
(Applies to Linux PSP only.) who can log in to the web
server, this parameter must
be set to yes, and values
must be provided to the
IP-RESTRICTED-EXCLU
DE or
IP-RESTRICTED-INCLU
DE parameters.
IP-RESTRICTED-EXCLUDE This parameter is used by the HP Systems List of IP address ranges
Management Homepage to exclude specific IP separated by semicolons
address/NetMask pairs from logging into the web (for example,
services. (Applies to Linux PSP only.) 10.1.1.1-10.1.1.10;10.2.
This parameter is ignored unless the 2.2-10.2.2.10)
IP-RESTRICTED-LOGINS parameter is set to
yes.
IP-RESTRICTED-INCLUDE This parameter is used by the HP Systems List of IP address ranges
Management Homepage to enable login only from separated by semicolons
the IP address/NetMask pairs specified. (Applies (for example,
to Linux PSP only.) 10.1.1.1-10.1.1.10;10.2.
This parameter is ignored unless the 2.2-10.2.2.10)
IP-RESTRICTED-LOGINS parameter is set to
yes.
LOCALACCESS-ENABLED This parameter is used by the HP Systems • YES (default to include
Management Homepage to determine whether to anonymous access)
enable local anonymous access to the web • NO
services. (Applies to Linux PSP only.)
LOCALACCESS-TYPE This parameter is used by the HP Systems • Anonymous (default)
Management Homepage to determine the type of • Administrator
access granted to local users. (Applies to Linux PSP
CAUTION: Selecting local
only.)
access with administrator
privileges as the login
provides full access to any
user with access to the local
console, without prompting
for a user name or
password.
TRUSTMODE This parameter is used by the HP Systems • TrustByCert—If this
Management Homepage to set up the trust value is used, the
relationship mode. (Applies to Linux PSP only.) CERTLIST parameter
must be defined to
enable access to the
server.
• TrustByName—If this
value is used, the
XENAMELIST
parameter must be
defined.

Scripted deployment 48
Parameter Description Possible values
• 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 This parameter enables a user to provide a list of Certificate file name or
certificate files or servers where certificates can be Server DNS name
obtained for trust relationships for the HP Systems
Management Homepage. (Applies to Linux PSP
only.)
XENAMELIST This parameter enables a user to provide a list of Server DNS name
servers, separated by semicolons, for trust
relationships for the HP Systems Management
Homepage. (Applies to Linux PSP only.)
This parameter is only valid if the TRUSTMODE
parameter is set to TrustByName. (Applies to
Linux PSP only.)
HPQLA2X00FO This parameter is used by the hp_qla2x00 QLogic • SinglePath
Fibre Channel Driver to determine the failover • SecurePath
mode to use. (Applies to Linux PSP only.) • QLogicFailure
(No default value)
HPQLA2X00FORCE This parameter is used by the hp_qla2x00 QLogic "Y", "N" (default)
Fibre Channel Driver to determine whether to skip
detection of third-party storage. (Applies to Linux
PSP only.)
OAUID This parameter provides the username credentials User can define OAUID
for OA associated with VC. You must define a variable multiple times
value of these variables before HOST variable in before each HOST
[TARGETS] section. This parameter only applies for variable.
VC firmware.
OAPWD This parameter provides the password credentials User can define OAPWD
for OA associated with VC. You must define a variable multiple times
value of these variables before HOST variable in before each HOST
[TARGETS] section. This parameter only applies for variable.
VC firmware.

Examples of the HP SUM input file include:

REBOOTALLOWED = YES
REBOOTREQUIRED = NO
REBOOTMESSAGE = "Server is going down for a reboot"
REBOOTDELAY = 15

Scripted deployment 49
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 1: The two targets are passed to be updated. The targets do not necessarily have to be OAs. They
can be any target supported by HP SUM.
DRYRUN = YES
SILENT = YES
[TARGETS]
HOST = BL465C-01
HOST = 192.168.1.2
[END]
Example 2: 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 3
SILENT = YES
IGNOREERRORS = ServerNotFound,BadPassword, FailedDepedencies

Scripted deployment 50
 SKIPTARGET = NO
SOURCEPATH = C:\fwcd\firmware-8.70-0\hp\swpackages
[GROUPS]
HOST=winserver
UID=Userid
PWD=password
[END]
Example 4
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]
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]

Reports
HP SUM generates three types of reports about the specified system or repository. These reports are
generated using the command-line arguments provided. If no additional arguments are specified on the
command line, the local host and default repository locations (the directory where HP SUM was initiated) are
used. You can specify a target with appropriate credentials and a repository using other command-line
parameters to generate reports for other systems and repositories. For specific commands, see
"Command-line interface (on page 31)."

Scripted deployment 51
Report type Description Report file information*
/report This argument generates a report listing, The report files generated are:
a target summary, and how the • hpsum_Report_<date>.html
components in the repository affect the • hpsum_Report_<date>.xml
target. Ffor example, whether each
component applies to the target.
Usage: hpsum /report
/inventory_report This argument generates a report listing The report files generated are:
of the components in the specified • hpsum_Inventory_Report_<date>.ht
repository. ml
Usage: hpsum /inventory_report • hpsum_Inventory_Report_<date>.x
ml
/firmware_report This argument generates a report listing The report files generated are:
of the firmware in the specified • hpsum_Report_<date>.html
repository. • fwreport.xml is placed in a folder
Usage: hpsum /firmware_report named
HPSUM_Firmware_Report_<date>

The reports are generated as an XML and HTML file which can be viewed in a web browser. The supported
browsers for viewing the report files are Microsoft Internet Explorer 6.0 and Mozilla Firefox 3.5 and above.
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.
The HP SUM log files are located in these folders:
• On Windows operating systems: C:\cpqsystem\hp\log
• On Linux operating systems: /var/hp/log
When generating the report, the HP SUM GUI does not appear. When the report is generated, HP SUM
displays the report file location.

Scripted deployment 52
The following figure illustrates the HP SUM report in HTML format.

Scripted deployment 53
The following figure illustrates the HP SUM Inventory report in HTML format.

Scripted deployment 54
The following figure illustrates the HP SUM Firmware report in HTML format.

Scripted deployment 55
Advanced topics

Configuring IPv6 networks with HP Smart Update

Manager
Starting with HP Smart Update Manager version 3.2.0, you can deploy to remote targets in IPv6-based
networks for Windows® and Linux target servers. Using HP Smart Update Manager with IPv6 networks
presents challenges for IT administrators.
For Windows®-based servers, to communicate with remote target servers, HP Smart Update Manager uses
either existing credentials or user-provided user name and password to connect to the admin$ share. This
share is an automatic share provided by Windows Server®. After HP Smart Update Manager 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 Smart Update Manager uses this service to communicate between the local and remote target
server. During this process, HP Smart Update Manager opens ports in the Windows® firewall to enable HP
Smart Update Manager to use SOAP calls over SSL to pass data among local and remote systems. These
ports are defined in Allowing ports in HP Smart Update Manager ("Enabling ports in HP Smart Update
Manager" on page 67). After the installation is completed or canceled, HP Smart Update Manager 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 Smart Update Manager starts by using
the user-provided user name and password to create a SSH connection to the target server. After the HP
Smart Update Manager connects, copies a small service to the target server for the duration of the
installation. After this service starts, HP Smart Update Manager uses this service to communicate between the
local and remote target server. During this process, HP Smart Update Manager opens ports in the iptables
firewall to enable HP Smart Update Manager to use SOAP calls over SSL to pass data between the local and
remote systems. These ports are defined in Allowing ports in HP Smart Update Manager. When the
installation is completed or canceled, HP Smart Update Manager 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.

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
(http://www.microsoft.com/downloads/details.aspx?FamilyID=fd7e1354-3a3b-43fd-955f-11edd39551
d7&displaylang=en).
Before using HP Smart Update Manager 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 make the registry entry:
1. Start the Registry Editor (Regedt32.exe).
2. Locate and click the following key in the registry:

Advanced topics 56
 HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Para
meters
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. Quit the Registry Editor.
For more information about these steps, see the Microsoft® Knowledge Base Item 281308 on the Microsoft®
website (http://www.microsoft.com).
IPv6 addresses can be passed to HP Smart Update Manager in command line arguments or using the HP
Smart Update Manager user interface. In the HP Smart Update Manager 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 Smart Update Manager 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
Smart Update Manager in an IPv6 environment, see the troubleshooting section ("Troubleshooting HP Smart
Update Manager in IPv6 networks" on page 70).
After you connect to the target server, all other HP Smart Update Manager functions work identically. Log
files for IPv6 hosts are stored with all other HP Smart Update Manager files in the
\CPQSYSTEM\hp\log\<ip_address> directory.

Configuring IPv6 for Windows Server 2008

HP Smart Update Manager provides the most robust support for remote deployment when using Windows
Vista® as a client to Windows Server® 2008-based servers. Using HP Smart Update Manager 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 target servers. Windows Vista®, when used as a client to run HP Smart
Update Manager to remote Windows Server® 2008 operating systems or as a target operating system on
HP Workstation server blades, provides the infrastructure that supports full IPv6 deployment of software and
firmware updates from HP Smart Update Manager.

NOTE: Windows® XP clients are not supported in IPv6 networks for HP Smart Update Manager
deployment.

IPv6 addresses can be passed to HP Smart Update Manager in command line arguments or using the HP
Smart Update Manager user interface. In the HP Smart Update Manager 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 Smart Update Manager 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 Smart
Update Manager in an IPv6 environment, see the troubleshooting section ("Troubleshooting HP Smart
Update Manager in IPv6 networks" on page 70).

Advanced topics 57
 After you connect to the target server, all other HP Smart Update Manager functions work identically. Log
files for IPv6 hosts are stored with all other HP Smart Update Manager files in the
\CPQSYSTEM\hp\log\<ip_address> directory.

Limitations of IPv6 for Windows Server 2003 and Windows

Server 2008
Windows Server® 2003 requires site-local addresses to provide the necessary file-sharing capabilities
needed by HP Smart Update Manager. This means that link-local and global IPv6 addresses are not
supported as remote targets with HP Smart Update Manager.
Windows Server® 2008 or Windows® environments do not have any known limitations to using HP Smart
Update Manager.

NOTE: Windows® XP clients are not supported in IPv6 networks for HP Smart Update Manager
deployment.

Configuring IPv6 for Linux

HP Smart Update Manager leverages the IPv6 capabilities of Linux as provided by the Red Hat Enterprise
Linux and Novell SUSE Linux Enterprise Server products. Using HP Smart Update Manager 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 target servers. Remote target servers must have the iptables-ipv6 RPM
installed before targeting them from HP Smart Update Manager. Failure to install the iptables-ipv6 RPM
prevents HP Smart Update Manager from opening the communications port needed to send data to the
initiating Linux workstation. You can disable the Linux firewall to allow HP Smart Update Manager 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
(http://www.linux.com/learn/docs/ldp/592-linuxipv6-howto).

Advanced topics 58
IPv6 addresses can be passed to HP Smart Update Manager in command line arguments or using the HP
Smart Update Manager user interface. In the HP Smart Update Manager 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 Smart Update Manager 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 Smart
Update Manager in an IPv6 environment, see the troubleshooting section ("Troubleshooting HP Smart
Update Manager in IPv6 networks" on page 70).
After you connect to the target server, all other HP Smart Update Manager functions work identically. Log
files for IPv6 hosts are stored with all other HP Smart Update Manager files in the
/var/hp/log/<ip_address> directories.

Advanced topics 59
Limitations of IPv6 for Linux
The only current limitation of HP Smart Update Manager in a Linux IPv6 environment is that all remote target
Linux-based servers must have the iptables-ipv6 rpm file installed. You can find the file on the distribution
media for both Red Hat Enterprise Linux and Novell SUSE Linux Enterprise Server operating systems. HP
Smart Update Manager uses this file to open a port in the IPv6 firewall to communicate with the Linux system
that runs HP Smart Update Manager. Failure to install iptables-ipv6 results in HP Smart Update Manager
reporting a discovery failure unless you disable the firewall.

Server virtualization detection and support

HP SUM, running in the context of a Windows® PSP or ISP, supports server virtualization that runs on a
Windows® host. However, HP SUM, running in the context of a Windows® PSP, does not run on a VMware
host or on a guest operating system environment regardless of what host hypervisor you use.
HP SUM, running in the context of the HP Smart Update Firmware DVD, does not support server virtualization
that runs on a Windows® or Linux host and blocks attempts to install firmware from a guest or child virtual
machine. The server virtualization does not run on a VMware host or on a guest operating system
environment regardless of which host hypervisor you use. The HP Smart Update Firmware DVD does not boot
to a guest operating system environment.

Advanced topics 60
Troubleshooting

Recovering from a failed ROM upgrade

Recovering from a failed system ROM upgrade
Use redundant ROM or ROMPaq to recover from a system ROM upgrade failure.

Redundant ROM recovery

When you flash the system ROM, ROMPaq writes over the backup ROM and saves the current ROM as a
backup, enabling you to switch easily to the alternate ROM version if the new ROM becomes corrupted for
any reason. This feature protects the existing ROM version, even if you experience a power failure while
flashing the ROM.
When the server boots, the server detects if the current ROM is corrupt. If a corrupt ROM is detected, then the
system boots from the backup ROM and sends an alert through POST that the ROM is corrupt.
To access the redundant ROM through RBSU:
1. Power up your desktop. A prompt appears in the upper right corner of the screen.
2. Access RBSU by pressing F9.
3. Select Advanced Options.
4. Select ROM Selection.
5. Select Switch to Backup ROM.
6. Press the Enter key.
7. To exit the current menu, press the Esc key, or to exit RBSU, press the F10 key. The server restarts.
If RBSU is inaccessible, then you can switch ROM images by changing the switch settings on the system
configuration switch. For more information, see your server documentation.
If both ROM images are corrupt, use ROMPaq recovery.

ROMPaq recovery
The Disaster Recovery feature supports systems that do not support the Redundant ROM feature. Disaster
Recovery only applies to platforms with nonredundant system ROM. If both the up-to-date and backup
versions of the ROM are corrupt, then perform ROMPaq Disaster Recovery procedures:
1. On another server, download and save the ROMPaq image to the hard drive from the HP website
(http://www.hp.com).
2. Execute the ROMPaq image to create the ROMPaq disk.
3. Switch to the server with the corrupted ROM.
4. Power down the server.
5. Insert the ROMPaq disk.

Troubleshooting 61
 6. Power up the server.
The server generates one long beep and two short beeps to indicate that it is in disaster recovery mode.
If the disk is not in the correct drive, then the system continues to beep until a valid ROMPaq disk is
inserted.
The ROMPaq disk flashes both system ROM images. If successful, a sequence of ascending audible
beeps is generated. If unsuccessful, a sequence of descending audible beeps is generated, and you
must repeat the disaster recovery process.
7. Power down the server.
8. Remove the ROMPaq disk.
9. Power up the server.
To manually set the server for ROMPaq disaster recovery:
1. Power down the server.
2. Remove the access panel.
3. Set the system maintenance switch positions for disaster recovery. Switch positions are
server-specific.For information about the correct settings for your server, see the server documentation.
4. Insert a ROMPaq diskette with the latest system ROM from the HP Smart Update Firmware DVD or the
HP website (http://www.hp.com/support (http://www.hp.com/support)).
5. Install the access panel.
6. Power up the server.
7. Allow the system to boot completely.
8. Repeat steps 1 and 2.
9. Reset the system maintenance switch positions to the original settings.
10. Repeat steps 5 and 6.

Recovering from a failed option ROM upgrade

To recover from an option ROM upgrade failure, use the recovery method that is appropriate to the specific
option.

Array controller ROMs

Array controllers support Recovery ROM, which is a redundancy feature that ensures continuous system
availability by providing a backup ROM. During the flash process, a new version of the firmware can be
flashed to the ROM while the controller maintains the last known version of the firmware. If the firmware
becomes corrupt, the controller reverts back to the redundant version of the firmware and continues
operating.

NOTE: Storage option ROMs cannot be downgraded with ROMPaq because ROMPaqs have
been retired as a delivery method for storage options.

Lights-Out management ROMs

To perform disaster recovery for RILOE II, iLO, and iLO 2, see the documentation for your particular
Lights-Out management product on the Remote management website
(http://www.hp.com/servers/lights-out).

Troubleshooting 62
Recovering from an installation failure
Collecting trace directories
HP SUM generates a set of debug trace logs located in the %TEMP%\hp_sum directory on Windows
systems. These files contain internal process and debug information, which can be useful in determining HP
Smart Update Manager failures.
The debug trace files can be located under %temp%\hp_sum for windows. The log files can be located under
C:\cpqsystem\hp\log. These files provide the following information and are appended in each HP SUM
session.
HP SUM has a utility named GatherLogs.exe (Windows) or GatherLogs.sh (Linux) to create a compressed file
(Windows: .zip; Linux: tar.Z) 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.
Debug Trace Files Function

Opman.trace Provides operations manager trace data of the overall installation process, details of
repository/ components added/removed and general errors if any.
InventoryResults.xml Provides details of the component inventory from the repositories.
Settings.xml Provides general settings information of HP SUM such as Force downgrade or
upgrade.
SourceClient.trace Provides trace data of repository manager and general errors if any.
Hpsumiserver\Hpsumis This log contains trace data for HP SUM SOAP server sessions.
erver.log
Hpsumiserver\Hpsumse
rverW32.log
Hpsumiserver\localhps Contains information of the HP SUM SOAP server.
umsoapserver.log
Sesssion.log This log contains the data and time for each session has started. This file is saved in
separate directory named with the date.
RepositoryManager This directory provides the repository and component information This directory can be
excluded in the trace data when collecting the trace files.
<target>\Discoveryma Provides the details of interaction between the Operations Manager and the remote
nager.log 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>\Installmanage Provides the interaction between the Operations Manager and the remote discovery
r.log 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 Provides the trace data from operations manager for specific target.
name>_log.txt
<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 This log contains information of HP SUM discovery, installation status and errors if any.

Note: <Target> is the

name of the target in the
source selections

Troubleshooting 63
 Log Files Function
screen.

Hpsum_detail_log.txt This file contains the log data of the components.

hpsum_execution_log_ Provides detailed information of execution of HP SUM
<date>_<time>.log
hpsum.ini Stores persistent data on the user's system.

It is possible to look in the OpMan.trace file and see which component was winnowed from the installation
set and which ones were added. Normally, components are winnowed if:
• They do not support installation on the given OS
• The hardware they are designed for is not discovered to be present in the server
• The component is not for the type of target selected
• The component does not report itself capable of being deployed to a given target
• The component cannot be deployed in either the online or offline environment HP Smart Update
Manager detects it is running in
The following is an example of the output trace in the OpMan.trace on how to determine if a component was
prevented from being shown on the Select Items to Install screen or being deployed from the silent console
mode. In the example, the binary image files 0.bin and 1.bin (which represented iLO firmware files),
components cp011301.exe and cp011500.exe, and the HP BladeSystem Firmware Update Bundle for
Windows represented by bundle file bp000648.xml were added to the installation set. All the other
components were removed for various reasons.
InstallSet.cpp[212]: Winnow--Adding FileName 0.bin
InstallSet.cpp[212]: Winnow--Adding FileName 1.bin
InstallSet.cpp[222]: Winnow--Removing FileName 2.bin
InstallSet.cpp[212]: Winnow--Adding FileName cp011301.exe
InstallSet.cpp[222]: Winnow--Removing FileName cp011321.exe
InstallSet.cpp[222]: Winnow--Removing FileName cp011489.exe
InstallSet.cpp[222]: Winnow--Removing FileName cp011497.exe
InstallSet.cpp[212]: Winnow--Adding FileName cp011500.exe
InstallSet.cpp[222]: Winnow--Removing FileName cp011504.exe
InstallSet.cpp[222]: Winnow--Removing FileName cp011505.exe
InstallSet.cpp[222]: Winnow--Removing FileName cp011550.exe
InstallSet.cpp[222]: Winnow--Removing FileName cp011560.exe
InstallSet.cpp[242]: Target 0: Added Bundle bp000648.xml

Recovering from a discovery failure

Troubleshooting connection errors
If you receive HP SUM Connection Error or Discovery Failed messages, follow these troubleshooting tips:

Troubleshooting 64
 • 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
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 username in DOMAIN\USER format, where <user> is the
administrative username, and <domain> is either the NETBIOS computer name or the AD domain
name for this user account.
• For Linux, ensure the SSH port is not blocked.
• In rare cases, external storage enclosures might cause HP SUM to report a discovery failure or to hang.
To resolve this issue, disconnect the external storage until the firmware updates are completed.
• 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 on any routers in the network as documented in the Enabling ports in HP Smart
Update Manager section of this document.
• The SEP 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 (on page 63)".
• Ensure the server has a valid serial number.

HP SUM hangs during discovery

If a system hang is observed during HP SUM discovery and the system is connected to external storage, in
most cases disconnecting the external storage should resolve the issue.

HP SUM hangs during boot

If a system hangs while booting the Firmware DVD or Service Pack for ProLiant, the DVD or SPP uses the IP
address 192.168.0.1 to resolve the hang condition during a PXE boot.

Troubleshooting 65
Recovering from a loss of Linux remote functionality
Configuring firewall settings
When the Unable to Access Host message appears, the target firewall is enabled. By default, the target
firewall is enabled in Linux.
To recover remote Linux functionality, the target and host firewall must be disabled or reconfigured to allow
IP traffic through the ports needed by HP Smart Update Manager to deploy firmware. For a list of the ports
that need to be configured in the firewall, see Allowing ports in HP Smart Update Manager ("Enabling ports
in HP Smart Update Manager" on page 67).

Recovering from a blocked program on Microsoft

Windows
Configuring Windows firewall settings
The Windows® Security Alert appears when a program is blocked from accepting connections from the
Internet or a network.

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.

Troubleshooting 66
Enabling ports in HP Smart Update Manager
The ports that HP SUM uses cannot be configured. When HP SUM initiates communications to remote targets,
it uses several well-known ports, depending on the operating system. For Windows, ports 138 and 445 are
used to connect to remote targets (equivalent to remote and file print share functionality). For Linux, port 22
(SSH) is used to start the communications with the remote target.
HP SUM uses defined ports to communicate between the remote target and the workstation where HP SUM
is executing. When you run HP SUM, the administrator/root privileges are used to dynamically register the
port with the default Windows and Linux firewalls for the length of the application execution, then the port is
closed and deregistered. All communications are over a SOAP server using SSL with additional functionality
to prevent man-in-the-middle, packet spoofing, packet replay, and other attacks. The randomness of the port
helps prevent port scanning software from denying service to the application. The SOAP server is deployed
on the remote target using the initial ports described above (ports 138, 445, and 22) and then allocates
another independent port as documented below for its communications back to the workstation where HP
SUM is running. During shutdown of HP SUM, the SOAP server is shutdown and removed from the target
server, leaving the log files.
To deploy software to remote targets on their secure networks using HP SUM, the following ports are used.
Windows
Ports Description
Ports 445 and 137/138/139 These ports are needed to connect to the remote ADMIN$ share on
(Port 137 is used only if you are target servers. These are the standard ports Windows servers use to
using NetBIOS naming service.) connect to remote file shares. If you can connect remotely to a remote
Windows file share on the target server, the proper ports are open.
Ports 60000-60007 Random ports are used in this range to pass messages back and forth
between the local and remote systems using SSL. These ports are used on
the system running HP SUM to send data to the target server.
Several internal processes within HP SUM automatically use port 60000
when it is available. If there is a port conflict, the manager uses the next
available port. There is no guarantee that the upper limit is 60007 as it
is dependent on how many target devices are selected for installation.
Ports 61000-61007 These ports are used from the target server back to the system running HP
SUM. The same mechanism is used by the remote access code as the
60000 ports, with the first trial port being 61000. There is no guarantee
that the upper limit is 61007 when a conflict occurs. For the case of
ipv4-only and one NIC, the lowest available port is used by HP SUM to
pass information between processes on the local workstation where HP
SUM is executed, and the next available port is used to receive messages
from remote servers.
Port 62286 This port is the default port for some internal communications. It is the
listening on the remote side if there is no conflict. If a conflict occurs, the
next available port is used.

Troubleshooting 67
Ports 80 or 63000-63005 For Integrity servers and c-Class OA, port 80 must be opened on the
local system for the remote system to be able to pull the firmware file from
the HP SUM HTTP server.
The logs are passed to the target and retrieved using an internal, secure
web server that uses port 80 if it is available or a random port between
63000 and 63005 if port 80 is not available. This support enables
updates to the iLO firmware without the need to access the host server
and enables servers running VMware or other virtualization platforms to
update their iLO without the need to reboot the server or migrate the
virtual machines to other servers.

Linux
Port Description
Port 22 This port is establishes a connection to the remote Linux server using SSH.
Ports 60000-60007 Random ports are used in this range to pass messages back and forth
between the local and remote systems using SSL. These ports are used on
the system running HP SUM to send data to the target server.
Several internal processes within HP SUM automatically use port 60000
when it is available. If there is a port conflict, the manager uses the next
available port. There is no guarantee that the upper limit is 60007, as it
is dependent on how many target devices are selected for installation.
Ports 61000-61007 These ports are used from the target server back to the system running HP
SUM. The same mechanism is used by the remote access code as the
60000 ports, with the first trial port as 61000. There is no guarantee that
the upper limit is 61007 when a conflict occurs. For the case of ipv4-only
and one NIC, the lowest available port is used by HP SUM to pass
information between processes on the local workstation where HP SUM
is executed, and the next available port is used to receive messages from
remote servers.
Port 62286 This port is the default port for some internal communications. It is used
for listening on the remote side if there is no conflict. If a conflict occurs,
the next available port is used.
Ports 80 or 63000-63005 For Integrity servers and c-Class OA, port 80 must be opened on the
local system for the remote system to be able to pull the firmware file from
the HP SUM HTTP server.
The logs are passed to the target and retrieved using an internal secure
web server that uses port 80 if it is available or a random port between
63000 and 63005, if port 80 is not available. This support enables
updates to the iLO firmware without the need to access the host server
and enables servers running VMware or other virtualization platforms to
update their iLO without the need to reboot the server or migrate the
virtual machines to other servers.

Troubleshooting 68
Recovering from operating system limitations when
using a Japanese character set
Displaying the user-specified reboot message using a Japanese
character set when running on a Linux operating system
You might 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 a Linux operating system, the message
does not appear properly.

Rebooting with the user-specified reboot message using a

Japanese character set when running on a Windows operating
system
You might 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 a Windows® operating system, the
message causes the reboot not to occur automatically.
For a successful reboot, you must click Exit. When the message is entered using CLI, the reboot message
looks corrupted since the Japanese character set is not supported in CLI.

Running in a directory path containing multi-byte

characters
HP SUM hangs when it is run in a directory path that contains multi-bye character.
Do not run HP Smart Update Manager in directories containing multi-byte characters in the path name.

Recovering a lost HP Smart Update Manager

connection
HP Smart Update Firmware DVD mounted using iLO virtual media
When either iLO and NIC firmware are updated, the HP SUM connection is lost and cannot install
components.
Booting the Firmware DVD from iLO virtual media is only supported in Offline Automatic Firmware Update
mode. Users attempting to boot in this manner might experience issues from connection timeouts, difficulties
updating iLO firmware, and mouse syncing issues. If an access error exists, HP SUM cancels the installation.

Troubleshooting 69
Troubleshooting HP Smart Update Manager in IPv6
networks
If HP Smart Update Manager 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.

Troubleshooting HP Smart Update Manager in IPv6 Windows

Server 2003 environment
To validate that the IPv6 network is configured correctly for HP Smart Update Manager 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 Windows® operating systems, 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 Smart Update Manager
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 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
Smart Update Manager user interface or when passing IPv6 address using command line
parameters to HP Smart Update Manager.

After you validate that you can access the admin$ share on the remote target server, HP Smart
Update Manager works unless other network or hardware issues exist.
• Ensure you have made the registry change on remote target servers as mentioned in the HP Smart
Update Manager Usage in a Windows Server® 2003 IPv6 environment.
• Move back to an IPv4 network address to ensure HP Smart Update Manager properly finds the remote
target server without any issues.
You can always copy HP Smart Update Manager to the target servers and execute using the local installation
method.

Troubleshooting 70
Troubleshooting HP Smart Update Manager in IPv6 Windows
Server 2008 environment
To validate that the IPv6 network is configured correctly for HP Smart Update Manager support, you must
verify the following based on your operating system version.
• Validate that you can ping the remote target server. With Windows® operating systems, you can 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.
• Verify that you can connect to the admin$ share using the credentials within HP Smart Update Manager
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 Smart Update
Manager works unless there are other network or hardware issues.

Troubleshooting HP Smart Update Manager 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 Smart Update Manager 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>.
• Ensure you can ping the IPv6 loopback address: ping6 ::1.
• Use the DNS hostname instead of IPv6 address to ensure the address is correct.
• Use ipconfig to validate you have IPv6 addresses assigned to your NICs. For more information about
troubleshooting your configuration, see the Linux IPv6 How-To
(http://www.linux.com/learn/docs/ldp/592-linuxipv6-howto).
• For more information about setting up and troubleshooting IPv6 networks, see Getting Around IPv6 by
Carla Schroder (http://www.enterprisenetworkingplanet.com/netsp/article.php/3634596).
• Move back to an IPv4 network address to ensure HP Smart Update Manager properly finds the remote
target server without any issues.
• HP Smart Update Manager can always be copied to the target servers and executed using the local
installation method.

Troubleshooting 71
HP SUM found new hardware message
During the discovery progress, HP SUM might display the following pop-up message: Found New
Hardware. This message appears because one of the self-discovery components is loading a new driver
and the Windows operating systems discovers it as a new piece of hardware.
Similar pop-up messages might occur with Windows® 2008 operating systems when the Allow Non-bundle
version option on the Select Bundle Filter screen is selected.

Non-matching systems error reported when building

source Linux RPMs or installing Linux RPMs built from
source
If HP SUM reports non-matching systems error when trying to build source Linux RPMs or installing Linux RPMs
built from source, then 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 4.7 and RHEL 4.8 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.
Resolution options:
1. Run HP SUM on the target server itself instead of remotely deploying HP SUM.
2. 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 the user to deploy it anywhere they choose.

Linux component version discrepancy for source RPMs

You might observe differences in the RPM component name which might appear to be a version mismatch for
the component on the Select Item to be Installed screen and the Installation Results screen. 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.

Troubleshooting 72
HP SUM displays No components found in the
selected repository(ies) message
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.
To resolve this issue, make sure no spaces are in the path name.

Additional/Optional Actions columns are grayed

when HP SUM is maximized
If the Select Items to be Installed screen or Installation Results screen in HP SUM is maximized, the Additional
column and sometimes the Optional Actions columns are grayed out.
To resolve this issue, restore the screen to the original size.

Installation of components failed with 'Update

returned an error' when installing Linux RPMs
When installing any component, if the installation fails, then HP SUM displays Update returned an
error message. To determine the installation failure, review the associated component log.
However, when installing RPMs using HP SUM you might see this error when the RPMs for more than one
Linux distribution are present in a single repository and a PSP bundle from the Select Bundle Filter screen is
not selected.
In this scenario, 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 are returned. HP SUM cannot
determine which source RPMs go with which distribution because the RPMs do not contain any operating
system information.
To resolve this issue, make sure to select the bundle for the OS distribution on the Select Bundle Filter screen
for installation or remove the RPMs from the directory that are not applicable to the Linux distribution you are
using.

HP SUM fails on Windows Vista® due to McAfee

firewalls
This is a known issue with McAfee that McAfee firewalls block HP SUM traffic.
To resolve this issue, enable the port traffic associated with the HP SUM application by performing the
following steps:
1. From the system tray, click the McAfee icon.
2. Select Manage Features.
3. Select McAfee Host Intrusion Prevention.

Troubleshooting 73
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.

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).

Troubleshooting 74
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.

11. Restart HP SUM.

Troubleshooting 75
 Performing these steps allows HP SUM to function, although after a period of time (ranging from minutes
to hours), McAfee disables HP SUM access.

Downgrade of ProLiant G6 Server ROM from

2010.03.30 or later to 2010.03.01 or earlier using
HP SUM is not supported
When HP SUM is launched, all the available versions of ROM components in the repository are listed under
Updates to be installed section of the Select Items to be Installed screen.
If ROM downgrade is attempted from 2010.03.30 or later to 2010.03.01 or earlier using HP SUM for
ProLiant G6 servers, the ROM components with unsupported version are automatically removed from the
updates to be installed. ROM components do not have the ability to block downgrades.
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.

Troubleshooting 76
Technical support

Reference documentation
• To download the ProLiant Firmware Maintenance CD, Smart Update Firmware DVD, SmartStart, and
other CD/DVDs, see the SmartStart download website (http://www.hp.com/go/ssdownloads).
• For information about firmware support, see the ProLiant Firmware Maintenance CD/DVD Matrix
(http://www.hp.com/servers/smartstart/supportmatrices).
• For information about SmartStart support, see the SmartStart support matrices
(http://www.hp.com/servers/smartstart/supportmatrices).
• To download the latest PSPs, see the software and drivers download page
(http://www.hp.com/servers/swdrivers).
• For more information about PSPs, see the PSP website (http://www.hp.com/servers/psp).
• For more information about ISPs and Windows on Integrity releases, see the Integrity website
(http://h20341.www2.hp.com/integrity/w1/en/os/windows-on-integrity-releases.html).
• For more information about Windows on Integrity support, see the support matrices
(http://h20341.www2.hp.com/integrity/w1/en/os/windows-on-integrity-support-matrix.html).
• To download the Integrity Smart Setup, Management, or Smart Update DVDs, see the Integrity website
(http://h20341.www2.hp.com/integrity/w1/en/software/essentials-windows-on-integrity.html).
• For an overview of the HP Integrity family of servers, see the Integrity website
(http://www.hp.com/go/integrity).
• For other documents supporting the Windows Server operating system on HP Integrity servers, see the
Windows on Integrity documents (http://www.hp.com/go/windows-on-integrity-docs).
• For information about HP Subscriber's Choice, see the Subscriber's Choice website.
(http://www.hp.com/go/subscriberschoice)
• For information about the SmartStart Scripting Toolkit, see the Toolkit website
(http://www.hp.com/servers/sstoolkit).
• For information about the HP Insight Control server deployment software, see the HP Insight Rapid
Deployment software website (http://www.hp.com/servers/rdp).
• For information about operating systems supported by ProLiant servers, see the operating system
support matrices. (http://www.hp.com/go/supportos)

Operating system information

For information about Microsoft® Windows® operating systems, see the Microsoft® website
(http://www.microsoft.com).
For information about Linux operating systems, see one of the following websites:
• Red Hat Linux (http://www.redhat.com)

Technical support 77
 • SUSE Linux (http://www.novell.com/linux)

HP contact information
For United States and worldwide contact information, see the Contact HP website
(http://www.hp.com/go/assistance).
In the United States:
• To contact HP by phone, call 1-800-334-5144. For continuous quality improvement, calls may be
recorded or monitored.
• If you have purchased a Care Pack (service upgrade), see the Support & Drivers website
(http://www8.hp.com/us/en/support-drivers.html). If the problem cannot be resolved at the website,
call 1-800-633-3600. For more information about Care Packs, see the HP website
(http://pro-aq-sama.houston.hp.com/services/cache/10950-0-0-225-121.html).

Technical support 78
Acronyms and abbreviations

AMS
agentless management services

CLI
Command Line Interface

DNS
domain name system

FPGA
Field Programmable Gate Array

GUI
graphical user interface

HP SUM
HP Smart Update Manager

iLO
Integrated Lights-Out

iLO 3
Integrated Lights-Out 3

ISP
Integrity Support Pack

MP
Monarch (primary)

NIC
network interface controller

OA
Onboard Administrator

Acronyms and abbreviations 79

POST
Power-On Self Test

PSP
HP ProLiant Support Pack

RBSU
ROM-Based Setup Utility

RILOE II
Remote Insight Lights-Out Edition II

SEP
Symantec Endpoint Protection

SNMP
Simple Network Management Protocol

SOAP
Simple Object Access Protocol

SSH
Secure Shell

SSL
Secure Sockets Layer

UNC
Universal Naming Convention

WBEM
Web-Based Enterprise Management

WMI
Windows Management Instrumentation

Acronyms and abbreviations 80

Index

errors 64, 72, 73

A execution, first time 11

advanced topics 56
F
arguments 32
authorized reseller 77, 78 failed dependencies 27
files, creating input 41, 42
B firewall settings, configuring 66, 73
firmware 13, 14
blocked HP Smart Update Manager, recovering
Firmware Maintenance DVD 16
from 66
bundle filter options 19, 20, 27
H
C hardware, found new 72
hosts 28
CLI (Command Line Interface) 31, 32, 38
HP ProLiant Servers 14
command line arguments 32
HP Smart Update Firmware DVD 13
command line examples 38
HP website 78
command line interface, using 31
command line syntax 31
I
command-line usage of input file 42
component configuration 20 iLO (Integrated Lights-Out) 69
component configuration, Windows 38 input file parameters 42, 43
components 28, 73 input file, command-line age 42
configuring components 20 installation 25
configuring firewall settings 66 installation issues 63, 73
creating input files 41 installation options 28, 29
credentials 24 introduction 6
IPv6 network configurations 56, 57, 58
D IPv6, troubleshooting 70, 71

deliverables 10
K
deploying firmware 13
deployment overview 11 keyboard support 16
deployment scenarios 16
deployment, scripted 31 L
disaster recovery 61
Lights-Out Management ROMs 62
Disaster Recovery, ROMPaq 61
limitations, Linux IPv6 environment 60
discovery issues, troubleshooting 65
limitations, Windows Server IPv6 environment 58
Discovery Process screen 21
Linux component version discrepancy 72
double-byte characters 42, 69
Linux IPv6 environment 58
downgrading firmware 76
Linux remote functionality, recovering 66
Linux RPM return codes 41
E
Linux smart components, return codes 40
editing hosts 20

Index 81
M selecting bundles to filter, first time 27
selecting components to install 28
maximizing a window to single display 73 server virtualization detection and support 60
minimum requirements 7 source selections 17
minimum requirements for Linux servers 8 support 77
minimum requirements for Windows servers 7
mounting virtual media 69
T
N target interfaces 22, 23, 24, 25, 28
technical support 77, 78
non-matching system error 72 trace logs 63
troubleshooting 61, 65, 69, 76
O troubleshooting, Linux component discrepancy
operating system problems 69 issue 72
operating systems 69, 77 troubleshooting, non-matching system error 72
overview, HP Smart Update Manager 6 troubleshooting, reboot 69
troubleshooting, repository 73
P
U
parameters 43
proxy settings 18 using this guide 7

R V
Reboot Options 29 version discrepancy issue 72
reboot settings 69 virtual media access 69
reboot, troubleshooting 69
recovering from a failed option ROM upgrade 62 W
recovering from a failed system ROM upgrade 61, website, HP 78
63 Windows components, adding 38
redundant ROM 61 Windows smart components, return codes 40
references 77
remote functionality, recovering 66
reports 30, 51
reports, creating 30, 51
repository 19, 20, 73
return codes 40, 41
return codes, Linux smart components 40
return codes, Windows smart components 40
ROM recovery, redundant 61
ROM redundancy 61
ROM upgrade, recovering from failed option 62
ROM upgrade, recovering from failed system 61
ROM, array controller 62
ROM, Lights-Out management 62
ROM, storage 62
ROMPaq Disaster Recovery 61
RPM return codes, Linux 41

S
scripted deployment 31

Index 82