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 74
Return codes
HP SUM has consolidated return codes from Linux and Windows® smart components into a new, enhanced
return code mapping. These return codes determine the status of the component installation. You can also use
return codes in a script to control the execution of the script and determine any required branching.
In Linux, the negative return codes are reported. These return codes are determined by subtracting the
negative value from 256.
To view the installation log file locations, see "Viewing the installation results (on page 44)."
Return code Value Linux Windows® Text
SUCCESS_NO_REBOOT
0 0 0 The installation was successful.
SUCCESS_REBOOT
1 1 1 The installation was successful, but
a reboot is required.
SUCCESS_NOT_REQUIRED
3 3 3 The component was current or not
required.
FAILURE_GENERAL
-1 255 255 A general failure occurred. For
details, see the error log.
FAILURE_BAD_PARM
-2 254 254 A bad input parameter was
encountered.
FAILURE_COMPONENT_FAILED
-3 253 253 The installation of the component
failed.
Windows smart component return codes
Error level Meaning
0
The smart component failed to install. For more details, see the log file.
1
The smart component installed successfully.
2
The smart component installed successfully, but the system must be restarted.
3
The installation was not attempted because the required hardware is not present, the software
is current, or there is nothing to install.
Linux smart component return codes
Single target servers:
Error level Meaning
0
The smart component installed successfully.
1
The smart component installed successfully, but the system must be restarted.
2
The installation was not attempted because the required hardware is not present, the software
is current, or there is nothing to install.
3
The smart component failed to install. For more details, see the log file.
Multi-target servers:
Error level Meaning
0
The installation of the deliverable is successful. No reboot is required.