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