HP ProLiant BL465c Server Blade - Manual (Page 29)

Function Trace files
Provides general settings information of HP SUM such as Force downgrade or
upgrade for a specific target. <target>\Settings.xml
Provides trace data of repository manager and general errors if any. SourceClient.trace
This log contains trace data for HP SUM SOAP server sessions. Hpsumiserver\
Hpsumiserver.log
This log contains trace data for HP SUM SOAP server sessions. Hpsumiserver\
HpsumserverW32.log
This log contains information for the HP SUM SOAP server. Hpsumiserver\
localhpsumsoapserver.log
This log contains the data and time for each session has started. This file is saved
in separate directory named with the date. Session.log
This directory provides the repository and component information This directory
can be excluded in the trace data when collecting the trace files. RepositoryManager
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. <target>\Discoveryma
nager.log
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. <target>\Installmanager.log
Provides the trace data from operations manager for specific target. <target>\<target
name>_log.txt
You can 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 that it can be deployed to a given target
•
The component cannot be deployed in either the online or offline environment that HP SUM
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.
For example:
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
Recovering from an installation failure 29