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 71
Command-line argument Description
password> 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 (for OA
username) and
OAPWD
(for OA password) must be used.
Log files
/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
/veryv[erbose]
These arguments enable you to set the verbosity level for the HP SUM execution
log file, 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
/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 the file name formats: HPSUM_ Report_<date>_<time>.html and HPSUM_
Report_<date>_<time>.xml.
By default, the files are 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.
Including other arguments on the command line can modify the contents of the
report. Using the /target argument will allow reports to be generated for
different targets.
/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 files are 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.
Including other arguments on the command line can modify the contents of the
report. Using the /target argument will allow reports to be generated for
different targets.
/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_<date>_<time>.html and fwreport.xml in the
directory named HPSUM_Firmware_Report_<date>_<time>.
By default, this directory 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