Collecting trace directories

HP Smart Update Manager 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, which can be useful in determining HP Smart Update Manager failures.

NOTE: To break out to a Linux console while booted to the Firmware Maintenance CD, press Ctrl Alt d b x. Each key (d, b, x) is hit in succession. This command allows you to collect logs from the \tmp\hp_sum directory.

Examine the OpMan.trace, IPScout.trace, OSScout.trace, InstallClient.log, and InstallManager.log trace files to determine the cause of the failure. These files provide the following information.

Trace files	Function
OpMan.trace	Provides operations trace of the overall installation process.
IPScout.trace	Provides the information on whether the remote target might be contacted and the type of target found (iLO, server, VC, OA).
OSScout.trace	Provides the details of the connection setup and is responsible for cleaning up after an installation and initiating a reboot, if needed and selected by the user, on the target system.
InstallClient.log	Provides the details of the execution of the individual components, including the command line parameters, used to launch the components and the component return code before it is converted to HP Smart Update Manager return codes.
InstallManager.log	Provides the interaction between the Operations Manager and the remote installation client. Any failure in network communications is reported in this file and surfaced as an Installation Failed message for the affected component and potentially all components that follow the failing component.
discagent.trace	Provides the details of the execution of the discovery agent on either the local system during a local installation or the remote target server. If a discovery tool fails, it is reported to this trace file and surfaced as a Discovery Failed message.
discmanager.trace	Provides the interaction between the Operations Manager and the remote discovery client. If a discovery tool fails, it is reported to this trace file and surfaced as a Discovery Failed message.

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 OS
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 HP Smart Update Manager detects it is running in
The component is for a particular class (p-Class or c-Class) of BladeSystem enclosure and the component does not find that class of enclosure.

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