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 104
denying service to the application. The SOAP server is deployed on the remote target using the initial ports
described above (ports 138, 445, and 22) and then allocates another independent port as documented
below for its communications back to the workstation where HP Smart Update Manager is running. During
shutdown of HP Smart Update Manager, the SOAP server is shutdown and removed from the target server,
leaving the log files.
To deploy software to remote targets on their secure networks using HP Smart Update Manager, the
following ports are used.
For Windows®
Ports Description
Ports 445 and 137/138/139
(Port 137 is used only if you are
using NetBIOS naming service.)
These ports are needed to connect to the remote ADMIN$ share on
target servers. These are the standard ports Windows® servers use to
connect to remote file shares. If you can connect remotely to a remote
Windows® file share on the target server, then you have the right ports
open.
Ports 60000-60007
Random ports are used in this range to pass messages back and forth
between the local and remote systems via SSL. These ports are used on
the system running HP Smart Update Manager to send data to the target
server.
Several internal processes within HP Smart Update Manager
automatically use the port from 60000 when no other application uses it.
If there is a port conflict, the manager uses the next available one. There
is no guarantee that the upper limit is 60007 as it is dependent on how
many target devices are selected for installation.
Ports 61000-61007
These ports are used from the target server back to the system running HP
Smart Update Manager. The same mechanism is used by the remote
access code as the 60000 ports, with the first trial port as 61000. There
is no guarantee that the upper limit is 61007 when a conflict occurs. For
the case of ipv4-only and one NIC, the lowest available one is used by
HP Smart Update Manager to pass information between processes on
the local workstation where HP Smart Update Manager is executed, and
the next available one is used to receive messages from remote servers.
Port 62286
This port is the default for some internal communications. It is the listening
on the remote side if there is no conflict. If a conflict occurs, the next
available one is used.
Ports 80 or 63000-63005
The logs are passed to the target and the logs are retrieved via an
internal secure web server that uses port 80 if it is available or a random
port between 63000 and 63005, if it is not. This support allows updates
of the iLO firmware without the need to access the host server and allows
servers running VMware or other virtualization platforms to update their
iLO without the need to reboot their server or migrate their virtual
machines to other servers.
For Linux
Port Description
Port 22
This port is establishes a connection to the remote Linux server via SSH.