HP Smart Update Manager 4.2 User Guide
Table Of Contents
- HP Smart Update Manager User Guide
- Abstract
- Notice
- Contents
- Introduction
- HP Smart Update Manager overview
- Using this guide
- New features of HP SUM 4.2.0
- Minimum requirements
- Supported deliverables overview
- Deployment from HP SUM
- Executing HP SUM
- Deploying software using the ProLiant Support Pack (PSP) for Microsoft Windows
- Deploying software using the Integrity Support Pack (ISP) for Microsoft Windows
- Deploying software using the ProLiant Support Pack for Linux
- Deploying firmware for ProLiant servers using the HP Smart Update Firmware DVD
- Deploying firmware using the HP Smart Update Firmware - HP Integrity BL860c/BL870c/BL890c i2 Servers Bundles
- HP SUM User Interface
- Deployment scenarios
- Keyboard support
- Local host installations
- Multiple-host installations
- Selecting remote hosts or groups
- Searching for remote hosts
- Managing hosts
- Managing groups
- Entering credentials for hosts
- Selecting bundles to filter on multiple hosts
- Selecting components to install on multiple hosts
- Updating Firmware on HP Integrity BL860c/BL870c/BL890c i2 Servers
- Viewing the installation results for multiple hosts
- Scripted deployment
- Advanced topics
- Troubleshooting
- Recovering from a failed ROM upgrade
- Recovering from an installation failure
- Recovering from a discovery failure
- Recovering from a loss of Linux remote functionality
- Recovering from a blocked program on Microsoft Windows
- Recovering from operating system limitations when using a Japanese character set
- Recovering from Fatal Error - application will exit message
- Recovering from a missing reboot message when running on SUSE LINUX Enterprise Server 9
- Recovering a lost HP Smart Update Manager connection
- Troubleshooting HP Smart Update Manager in IPv6 networks
- HP SUM found new hardware message
- Non-matching systems error reported when building source Linux RPMs or installing Linux RPMs built from source
- Linux component version discrepancy for source RPMs
- HP SUM displays No components found in the selected repository(ies) message
- Additional/Optional Actions columns are grayed when HP SUM is maximized
- Installation of components failed with 'Update returned an error' when installing Linux RPMs
- Issues related to bundle filtering on the Select Items to be Installed and Select Bundle Filter screens
- HP SUM fails on Windows Vista® due to McAfee firewalls
- Technical support
- Acronyms and abbreviations
- Index

Scripted deployment 75
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.