HP Integrity Superdome 2 8/16 HP Smart Update Manager 5.3 User Guide - Page 62

the installation set and which ones were added., It is possible to look in

Get HP Integrity Superdome 2 8/16 PDF manuals and user guides View all HP Integrity Superdome 2 8/16 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 62 highlights

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. is the name of the target in the source selections screen. Provides general settings information of HP SUM such as Force downgrade or upgrade for specific target. Log Files \hpsum_log.txt Hpsum_detail_log.txt hpsum.ini Function Contains information of HP SUM discovery, installation status and errors if any. is the name of the target in the source selections screen. 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 components were winnowed from the installation set and which ones were added. 62 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
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
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
<target>
is the name of the target in the source selections
screen.
Provides general settings information of HP SUM such as
Force downgrade or upgrade for specific target.
<target>\Settings.xml
Function
Log Files
Contains information of HP SUM discovery, installation
status and errors if any.
<target>\hpsum_log.txt
<target>
is the name of the target in the source selections
screen.
Contains the log data of the components.
Hpsum_detail_log.txt
Stores persistent data on the user's system.
hpsum.ini
It is possible to look in the
OpMan.trace
file and see which components were winnowed from
the installation set and which ones were added.
62
Troubleshooting