Recovering From A Discovery Failure; Troubleshooting Connection Errors - HP Integrity Superdome 2 16-socket User Manual

Log Files
<target>\hpsum_log.txt
Note: <Target> is the name of the target in the source
selections screen.
Hpsum_detail_log.txt
hpsum_execution_log_<date>_<time>.log
hpsum.ini
It is possible to look in the OpMan.trace file and see which component was winnowed from the
installation set and which ones were added. Normally, components are winnowed if:
They do not support installation on the given operating system
The hardware they are designed for is not discovered to be present in the server
The component is not for the type of target selected
The component does not report itself capable of being deployed to a given target
The component cannot be deployed in either the online or offline environment
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 cp01 1301.exe and cp01 1500.exe, and the HP SPP
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 receive 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
60 Troubleshooting
Function
Contains information of HP SUM discovery, installation
status and errors if any.
Contains the log data of the components.
Provides detailed information of execution of HP SUM
Stores persistent data on the user's system.