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 101
The following is an example of the output trace in the OpMan.trace on how to determine if a component was
prevented from being shown on the Select Items to Install screen or being deployed from the silent console
mode. In the example, the binary image files 0.bin and 1.bin (which represented iLO firmware files),
components cp011301.exe and cp011500.exe, and the HP BladeSystem Firmware Update Bundle for
Windows represented by bundle file bp000648.xml were added to the installation set. All the other
components were removed for various reasons.
InstallSet.cpp[212]: Winnow--Adding FileName 0.bin
InstallSet.cpp[212]: Winnow--Adding FileName 1.bin
InstallSet.cpp[222]: Winnow--Removing FileName 2.bin
InstallSet.cpp[212]: Winnow--Adding FileName cp011301.exe
InstallSet.cpp[222]: Winnow--Removing FileName cp011321.exe
InstallSet.cpp[222]: Winnow--Removing FileName cp011489.exe
InstallSet.cpp[222]: Winnow--Removing FileName cp011497.exe
InstallSet.cpp[212]: Winnow--Adding FileName cp011500.exe
InstallSet.cpp[222]: Winnow--Removing FileName cp011504.exe
InstallSet.cpp[222]: Winnow--Removing FileName cp011505.exe
InstallSet.cpp[222]: Winnow--Removing FileName cp011550.exe
InstallSet.cpp[222]: Winnow--Removing FileName cp011560.exe
InstallSet.cpp[242]: Target 0: Added Bundle bp000648.xml
Recovering from a discovery failure
Troubleshooting connection errors
If you are receiving an HP SUM Connection Error or Discovery Failed messages, follow these troubleshooting
tips:
• Ensure your workstation does not have an existing connection to the ADMIN$ share on the target IP
address. If it does, it prevents HP SUM from connecting to the remote server’s share because Windows
only allows one connection from a client to a server’s share. This can be verified by entering net use
at a command prompt. If a share to the target IP address \admin$ share exists, delete it, and then
attempt the installation again.
• Ensure that the target IP address server’s admin$ share is accessible. Validate the target server can be
accessed by entering net use x: \\<ip_address_or_dns_name>\admin$ for the target server
IP address or DNS name. When the connection is validated, ensure that it is deleted by entering net
use x: /d at the command prompt.
• Ensure the user ID being used to connect to the target IP address server is part of the administrator’s
group. If it is not, HP SUM blocks installation to the target.
• Ensure WMI is enabled and running on all Windows target servers.
• For Windows target servers, enter the username in DOMAIN\USER format, where <user> is the
administrative username, and <domain> is either the NETBIOS computer name or the AD domain
name for this user account.
• For Linux, ensure the SSH port is not blocked.