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 109
• Ensure you can ping the IPv6 loopback address: ping6 ::1.
• Use the DNS hostname instead of IPv6 address to ensure the address is correct.
• Use ipconfig to validate you have IPv6 addresses assigned to your NICs. For more information about
troubleshooting your configuration, see the Linux IPv6 How-To
(http://www.linux.com/learn/docs/ldp/592-linuxipv6-howto).
• For more information about setting up and troubleshooting IPv6 networks, see Getting Around IPv6 by
Carla Schroder (http://www.enterprisenetworkingplanet.com/netsp/article.php/3634596).
• Move back to an IPv4 network address to ensure HP Smart Update Manager properly finds the remote
target server without any issues.
• HP Smart Update Manager can always be copied to the target servers and executed using the local
installation method.
HP SUM found new hardware message
During the discovery progress, HP SUM might display the following pop-up message: Found New
Hardware. This message appears because one of the self-discovery components is loading a new driver
and the Windows operating systems discovers it as a new piece of hardware.
Similar pop-up messages might occur with Windows® 2008 operating systems when the Allow Non-bundle
version option on the Select Bundle Filter screen is selected.
Non-matching systems error reported when building
source Linux RPMs or installing Linux RPMs built from
source
If HP SUM reports non-matching systems error when trying to build source Linux RPMs or installing Linux RPMs
built from source, then the operating system on the target server does not match the operating system from
which you are running HP SUM in one of the following ways:
• The distribution of the operating system does not match. For example, RHEL 4.7 and RHEL 4.8 would be
a mismatch.
• The architecture of the two operating systems does not match. For example, one server might be running
an operating system with x86 architecture and the other with x86_64 architecture.
• The kernel version running on the two systems does not match.
Resolution options:
1. Run HP SUM on the target server itself instead of remotely deploying HP SUM.
2. Build the driver RPM locally and take the resulting RPM file from the standard location (for example,
/usr/src/redhat/RPMS/i686/<driver>.rpm) and then copy it back into the HP SUM repository. HP
SUM will pick up the pre-built RPM and enable the user to deploy it anywhere they choose.