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 67
Command-line arguments
HP SUM recognizes the following command-line arguments. These arguments prepopulate the GUI in the
Select Items to be Installed screen. If you specify the host or group, then the Select Items to be Installed screen
does not appear.
You cannot use some arguments, such as /romonly and /softwareonly together.
Command-line argument Description
Help
/h[elp] or /?
This argument displays command-line Help information.
Installation options
/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 rewrite the same version of firmware only for
multi-target devices such as hard drives and array controllers (applies to firmware
only).
/m[utual]
•
If the device you want to flash is in a shared storage environment, then this
argument informs the firmware flash engine to flash the firmware.
•
If the device to be flashed is in a shared storage environment, and the /m
option is not passed, then the component installation fails (applies to
firmware only).
/c[omponent]
<component to install> or
<component1_to_install>
<component2_to_install>
This argument specifies the components to install. Components to install can be
specified with or without the /c[omponent] argument.
•
If using the /c[omponent] argument, then only one component can be
specified with the argument. However, multiple /c arguments and
components can be specified on the same line.
•
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.
/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