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
Troubleshooting 107
Recovering a lost HP Smart Update Manager
connection
HP Smart Update Firmware DVD mounted using iLO virtual media
When either iLO and NIC firmware are updated, the HP SUM connection is lost and cannot install
components.
Booting the Firmware DVD from iLO virtual media is only supported in Offline Automatic Firmware Update
mode. Users attempting to boot in this manner might experience issues from connection timeouts, difficulties
updating iLO firmware, and mouse syncing issues. If an access error exists, HP SUM cancels the installation.
Troubleshooting HP Smart Update Manager in IPv6
networks
If HP Smart Update Manager cannot connect to the remote server, you might receive a Discovery Failed
error. Discovery failures can be caused by third-party storage, failure to access the remote target server, and
an inability to access system resources. For IPv6 networks, host discovery failures can be caused by the
incorrect configuration of the IPv6 network.
Troubleshooting HP Smart Update Manager in IPv6 Windows
Server 2003 environment
To validate that the IPv6 network is configured correctly for HP Smart Update Manager support, you must
verify the following based on your operating system version.
• Validate that the addresses are site-local. Site-local addresses normally start with "FEC0:". Global and
link-local IPv6 addresses are not supported when the remote target is Windows Server® 2003.
• Validate that you can ping the remote target server. With Windows® operating systems, you can still
use the ping command to ping IPv6 addresses: ping <ipv6 address>.
• Ensure you can ping the IPv6 loopback address: ping ::1.
• Use the DNS hostname instead of IPv6 address to ensure the address is correct.
• Ensure you have installed the IPv6 protocol. It is not installed by default in Windows Server® 2003. Be
sure to reboot the server after installing the protocol to ensure addresses are properly obtained.
• Verify that you can connect to the admin$ share using the credentials within HP Smart Update Manager
by issuing the following command at a console prompt:
net use * \\<ipv6-address>.ipv6-literal.net\admin$ /user:<username>
net use * \\fec0::2.ipv6-literal.net\admin$ /user:administrator
You might need to provide the password if you are using a user name that is not the same as you
used to log in to the local system. All network shares require the use of the .ipv6-literal.net name
string to be properly configured by Windows®.