HP ProLiant BL420c HP Service Pack for ProLiant User Guide - Page 17

Debug Trace Files Sesssion.log RepositoryManager \Discoverymanager.log \Installmanager.log \_log.txt \Settings.xml Function Contains the data and time for each session has started. This file is saved in separate directory named with the date. Provides 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 \hpsum_log.txt Note: is the name of the target in the source selections screen. Hpsum_detail_log.txt hpsum_execution_log__.log hpsum.ini Function Contains information on 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. From the OpMan.trace file you can see which components were winnowed from the installation set and which ones were added. Normally, components are winnowed when: • 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 HP iLO firmware files), components cp011301.exe and cp011500.exe, and the 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 Collecting debug information 17