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 108
NOTE: You do not need to use the .ipv6-literal.net suffix when entering IPv6 address into the HP
Smart Update Manager user interface or when passing IPv6 address using command line
parameters to HP Smart Update Manager.
After you validate that you can access the admin$ share on the remote target server, HP Smart
Update Manager works unless other network or hardware issues exist.
• Ensure you have made the registry change on remote target servers as mentioned in the HP Smart
Update Manager Usage in a Windows Server® 2003 IPv6 environment ("Configuring IPv6 for
Windows Server 2003" on page 91).
• Move back to an IPv4 network address to ensure HP Smart Update Manager properly finds the remote
target server without any issues.
You can always copy HP Smart Update Manager to the target servers and execute using the local installation
method.
Troubleshooting HP Smart Update Manager in IPv6 Windows
Server 2008 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 you can ping the remote target server. With Windows® operating systems, you can 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.
• 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 use a user name that is different from the one 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®.
After you validate you can access the admin$ share on the remote target server, HP Smart Update
Manager works unless there are other network or hardware issues.
Troubleshooting HP Smart Update Manager in IPv6 Red Hat and
Novell SUSE-based Linux environments
• Verify that you can establish an SSH connection to the remote target server using the credentials within
HP Smart Update Manager by issuing the following command at a console prompt:
ssh <ipv6 address>
SSh 2101:db8:0:1::9
You must enter the root password for the target Linux server at the console to complete the IPv6
connection.
• Validate that you can ping the remote target server. In Linux, you need to use the ping6 command to
ping IPv6 addresses: ping6 <ipv6 address>.