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 70
Command-line argument Description
installation.
/reboot_message
“reboot message”
This argument displays the specified reboot message on remote consoles
connected to the server you want to reboot. You must use this argument with the
/reboot
option or the argument is ignored.
/reboot delay
timeout_in_seconds
This argument delays the reboot of the server for the length of time specified by
the 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, then 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.
Creating host groups
/group
“group_name”
This argument specifies an already defined group name in the HP SUM GUI.
Simulating HP SUM
/dryrun
This argument simulates the installation for a test run. Nothing is installed.
Targets
/user <username> or
/username <username>
This argument enables you to log in to the remote targets (except for the OA
associated with VC target) with the user ID.
For the OA associated with VC target, see
/oa_username
argument.
/psswd <password>
This argument enables you to use the password for the user ID specified in the
/user argument to log in to remote targets (except for the OA associated with
VC target).
For the OA associated with VC target, see
/oa_password
argument.
/current_credential
This argument enables the credentials of the local 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).
/target "netAddress"
This argument is the IP address or the 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 argument should be
the active Onboard Administrator. When specifying the IP address, you can use
either the IPv4 or IPv6 format.
/oa_username <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 (for OA
username) and
OAPWD
(for OA password) must be used.
/oa_password
<OA
This argument provides the username credential for OA associated with VC