Home » HP Manuals » Servers » HP ProLiant WS460c » Manual Viewer

HP ProLiant WS460c HP Smart Update Manager 6.0.0 User Guide - Page 65

Troubleshooting, Collecting trace directories

Add to My Manuals
Save this manual to your list of manuals

Page 65 highlights

6 Troubleshooting Collecting trace directories HP SUM generates a set of debug trace logs located in the %TEMP%\HPSUM 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 are located under %temp%\hp_sum for Windows. The log files are 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.bat (Windows) or Gatherlogs.sh (Linux) to create a compressed .zip (Windows) or tar.Z (Linux) file 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 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 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. Collecting trace directories 65

Section	Page
HP Smart Update Manager User Guide	1
Contents	3
1 Introduction	7
HP SUM overview	7
About the graphical user interface	8
Status icon descriptions	9
HP SUM new terms	9
2 Downloading, installing, and launching HP SUM	10
Downloading HP SUM	10
Downloading HP SUM from the HP SUM website	10
Downloading HP SUM from the SDR website	10
Migrating nodes from HP SUM 5.x to HP SUM 6	10
Deploying HP SUM	11
Running HP SUM	11
Deploying firmware for HP ProLiant servers using the HP Service Pack for ProLiant	11
Deploying HP Integrity firmware bundles with HP SUM	12
Deployment modes	12
Deployment scenarios	12
Disabling BitLocker to permit firmware updates (Windows only)	13
Launching and logging into HP SUM	14
Launching HP SUM	14
Logging into HP SUM	15
Logging out of the HP SUM GUI	15
3 Using the HP SUM GUI	16
Using the Home screen	16
Using the Activity screen	16
Using Guided Update	16
Using the Baseline Library screen	18
Adding a baseline	18
Creating a custom baseline	19
Deleting a baseline	21
Configuring components	21
Using the Nodes screen	21
Selecting multiple nodes	22
Adding a node	22
Editing a node	25
Aborting a node update	25
Node inventory	25
Deploying a node	26
Deploying all partitions in an HP Integrity BL870c i4 or BL890c i4 node	27
Node reports	28
Deleting a node	28
Server overview	29
Integrity node overview	29
Using the Enclosures screen	29
Adding an enclosure	29
Editing an enclosure	29
Aborting an enclosure update	29
Enclosure inventory	30
Deploying an enclosure	30
Enclosure reports	30
Deleting an enclosure	30
Using the Servers screen	30
Adding a server	30
Editing a server	30
Aborting a server update	30
Server inventory	30
Deploying a server	31
Server reports	31
Deleting a server	31
Using the Switches screen	31
Adding a switch	31
Editing a switch	31
Aborting a switch update	31
Switch inventory	31
Deploying a switch	31
Switch reports	32
Deleting a switch	32
Using the VM Hosts screen	32
Adding a VM host	32
Editing a VM host	32
Aborting a VM host update	32
VM hosts inventory	32
Deploying a VM host	32
VM host reports	32
Deleting a VM host	33
Using the iLO screen	33
Adding an iLO	33
Editing an iLO	33
Aborting an iLO update	33
iLO inventory	33
Deploying an iLO	33
iLO reports	33
Deleting an iLO	33
Using the Intelligent Power Distribution Units screen	33
Adding an iPDU	34
Editing an iPDU	34
Aborting an iPDU update	34
iPDU inventory	34
Deploying an iPDU	34
iPDU reports	34
Deleting an iPDU	34
Using the Virtual Connects screen	34
Adding a Virtual Connect	34
Editing a Virtual Connect	35
Aborting a Virtual Connect update	35
Virtual Connect inventory	35
Deploying a Virtual Connect	35
Virtual Connect reports	35
Deleting a Virtual Connect	35
4 Using legacy scripts to deploy updates	36
Command-line interface	36
Command-line syntax	36
Using Linux root credentials	36
Prerequisites for using Linux root credentials	36
Switch update commands	37
Command-line arguments	37
Command-line examples	45
Return codes	46
Windows smart-component return codes	47
Linux smart-component return codes	47
Linux RPM return codes	48
VMware ESXi smart-component return codes	48
Input files	48
Input file format and rules	49
File encoding	49
Error reporting	50
Input file parameters	50
Reports	61
Downloading HP SUM and components from the SDR	62
5 Advanced topics	63
Configuring IPv6 networks	63
Network ports used by HP SUM	63
GatherLogs	64
6 Troubleshooting	65
Collecting trace directories	65
Baseline troubleshooting	66
HP SUM lists SUSE Enterprise Linux dependencies for Red Hat Enterprise Linux systems	66
HP SUM displays two versions of the same component when creating a custom baseline	66
HP SUM stops responding when performing inventory on large baselines	66
HP SUM does not return an error when you enter incorrect credentials forDownload from hp.com	66
Node troubleshooting	66
HP SUM does not respond when editing a node with sudo	66
HP SUM does not display the Deploy button on the Deploy Nodes screen	67
An HP-UX node displays the error Inventory failed. The pciinfo module requires manual update on remote target	67
HP SUM does not detect solid state hard drives	67
After HP SUM finishes an inventory, the inventory screen does not close	67
Cannot add a Windows node when running HP SUM on a Linux host	67
HP SUM does not display the Reboot button after it finishes a deployment	67
HP SUM does not automatically reboot a node	67
HP SUM does not display a reboot message in Guided Update	67
When multiple nodes are selected, HP SUM does not display the most correct status	67
HP SUM displays message Unable to locate the item you requested	67
HP SUM stops responding when performing inventory on multiple nodes	67
HP SUM displays the message Unable to login or identify node as a supported device when HP SUM cannot find a node	67
HP SUM displays the message Ready for deployment while HP SUM is performing inventory on a node	68
HP SUM does not display an entire screen	68
HP SUM displays extra credentials boxes on the Edit Node screen	68
You can edit a node while HP SUM is deploying updates to the node	68
HP SUM displays an associated node multiple times	68
HP SUM automatically performs inventory on a node after editing the node	68
Activity screen troubleshooting	68
HP SUM does not update the Activity screen accurately	68
VMware troubleshooting	68
HP SUM displays an inventory error on a VMware node	68
Reports troubleshooting	68
HP SUM does not generate reports for nodes that are offline	68
HP SUM displays only requested reports in CSV and XML format	68
HP SUM service troubleshooting	69
HP SUM service stops running when HP SUM is mounted from a virtual media source	69
HP SUM allows all users to log in	69
Some screens are not translated from English	69
Legacy CLI commands troubleshooting	69
HP SUM does not deploy multiple components at in one command	69
The /use_web Legacy CLI command does not work	69
7 Support and other resources	70
Contacting HP	70
Subscription service	70
Related information	70
Typographic conventions	71
HP Insight Remote Support software	72
HP Insight Online	72
8 Documentation feedback	73
Glossary	74

Match case Limit results 1 per page

6 Troubleshooting

Collecting trace directories

HP SUM generates a set of debug trace logs located in the

%TEMP%\HPSUM

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 are located under

%temp%\hp_sum

for Windows. The log files are 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.bat

(Windows) or

Gatherlogs.sh

(Linux) to create a compressed .zip (Windows) or tar.Z (Linux) file 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 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

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

Collecting trace directories