HP SUM generates a set of debug trace logs located in the %TEMP%\hp_sum directory on Windows systems. These files contain internal process and debug information, which can be useful in determining HP SUM failures.
The debug trace files can be located under %temp%\hp_sum for windows. The log files can be located under C:\cpqsystem\hp\log. These files provide the following information and are appended in each HP SUM session.
HP SUM has a utility named GatherLogs.exe (Windows) or GatherLogs.sh (Linux) to create a compressed file (Windows: .zip; Linux: tar.Z) with all the logs. If you need to review the log files, you can run this utility to gather all the logs in one file.
NOTE: Exit HP SUM before running the GatherLogs utility. | |
Debug Trace Files |
Function |
---|---|
|
Contains operations manager trace data of the overall installation process, details of repository/ components added/removed and general errors if any. |
|
Contains details of the component inventory from the repositories. |
|
Includes general settings information of HP SUM such as Force downgrade or upgrade. |
|
Includes trace data of repository manager and general errors if any. |
|
Contains trace data for HP SUM SOAP server sessions. |
|
|
|
Contains information of the HP SUM SOAP server. |
|
Contains the data and time for each session has started. This file is saved in separate directory named with the date. |
|
Provides the repository and component information This directory can be excluded in the trace data when collecting the trace files. |
|
Provides the details of 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. This log is target specific. |
|
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. This log is target specific. |
|
Provides the trace data from operations manager for specific target. |
|
Provides general settings information of HP SUM such as Force downgrade or upgrade for specific target. |
Log Files |
Function |
---|---|
Note: |
Contains information of HP SUM discovery, installation status and errors if any. |
|
Contains the log data of the components. |
|
Stores persistent data on the user's system. |
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 cp011301.exe and cp011500.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