HP ProLiant BL660c HP ProLiant and Integrity Firmware Management Best Practice - Page 48

Collecting trace directories, HP SUM 5.0.0 and later includes a utility named

Get HP ProLiant BL660c PDF manuals and user guides View all HP ProLiant BL660c manuals
Add to My Manuals
Save this manual to your list of manuals

Page 48 highlights

• Examine the trace directories for connection problems. For more information, see "Collecting trace directories" (page 48). • Ensure the server has a valid serial number. Collecting trace directories 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 5.0.0 and later includes 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 Opman.trace InventoryResults.xml Settings.xml SourceClient.trace Hpsumiserver\Hpsumiserver.log Hpsumiserver\HpsumserverW32.log Hpsumiserver\localhpsumsoapserver.log Sesssion.log RepositoryManager \Discoverymanager.log \Installmanager.log \_log.txt \Settings.xml 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 remote 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. 48 Troubleshooting

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
•
Examine the trace directories for connection problems. For more information, see
“Collecting
trace directories” (page 48)
.
•
Ensure the server has a valid serial number.
Collecting trace directories
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 5.0.0 and later includes 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.
Function
Debug Trace Files
Contains operations manager trace data of the overall
installation process, details of repository/components
added/removed and general errors if any.
Opman.trace
Contains details of the component inventory from the
repositories.
InventoryResults.xml
Includes general settings information of HP SUM such as
Force downgrade or upgrade.
Settings.xml
Includes trace data of repository manager and general
errors if any.
SourceClient.trace
Contains trace data for HP SUM SOAP server sessions.
Hpsumiserver\Hpsumiserver.log
Contains remote trace data for HP SUM SOAP server
sessions.
Hpsumiserver\HpsumserverW32.log
Contains information of the HP SUM SOAP server.
Hpsumiserver\localhpsumsoapserver.log
Contains the data and time for each session has started.
This file is saved in separate directory named with the date.
Sesssion.log
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
<target>\Discoverymanager.log
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
<target>\Installmanager.log
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.
<target>\<target name>_log.txt
Provides general settings information of HP SUM such as
Force downgrade or upgrade for specific target.
<target>\Settings.xml
48
Troubleshooting