HP ProLiant Support Pack - Manual (Page 37)

Troubleshooting 37
from remote servers.
Port 62286 This port is the default for some internal communications. This port is listening
on the remote side if a conflict does not exist. If a conflict occurs, the next
available port is used.
Ports 80 or 63000-63005 The logs are passed to the target, and the logs are retrieved using an internal
secure web server that uses port 80 (if available) or a random port between
63000 and 63005, if port 80 is not available.
This support enables updates of the iLO firmware without the need to access
the host server and enables servers running VMware or other virtualization
platforms to update their iLO without rebooting their server or migrating their
virtual machines to other servers.
• HP SUM is disconnected.
When either iLO or NIC firmware is updated, HP SUM loses the connection and cannot install
components. If an access error occurs, HP SUM cancels the installation.
• How do I recover from an installation failure?
HP SUM generates a set of debug trace logs located in the %TEMP%\hp_sum directory on Windows®
systems and \tmp\hp_sum on Linux systems. These files contain internal process and debug information
that can help you determine HP SUM failures.
• How do I reboot when running HP SUM on a Japanese version of Windows®?
You can specify a message to appear before shutting down the system during a reboot operation.
When using a Japanese character set and running on a Japanese version of a Windows® operating
system, the message prevents an automatic reboot. For a successful reboot, you must click Exit.
Troubleshooting installation of PSP for Linux
The following issues might be encountered when attempting to install Linux PSPs. The issues are in bold and
their resolutions follow.
If your issue is not listed in this section, you can find additional advisories related to the PSP for Linux by
performing a search on the HP website ( http://www.hp.com ) using the following keywords:
+ProLiant +advisory +note +linux|psp -"software and drivers" -download
• I used the -r flag to reboot the server and one of the components that was installed required a reboot,
but the server did not reboot. What is happening?
If any of the components chosen for installation fails the installation, a reboot does not occur. This
enables the administrator to examine a server to determine and resolve a software installation failure
before activating any changes.
• When I install storage components and restart the server, there are one or more new entries in the LILO
or GRUB tables for kernels to boot from. Is this normal?
Yes, this is normal. Each storage driver reconnects the driver to the base kernel and adds a new entry
in the LILO or GRUB tables that appear at boot. To ensure that you get the kernel with the latest drivers,
select the last entry in the table.
• I attempted to install a component that compiles from source code, but the installation fails on the make
command.
The build tools necessary to complete the build from kernel source are not located on the server where
the LDU is deploying. To build from source RPMs, the following RPMs must be installed on the server
where the HP SUM is deploying software: