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

Troubleshooting, Installation issues

Page 61 highlights

5 Troubleshooting Installation issues Components do not appear on the Select Items to Install screen or do not deploy from the silent console mode Solution: Components were not included in the installation set. Check the OpMan.trace file to see which components were not included. For the location and more information about trace files, see "Collecting trace directories" (page 61). Use the following checklist to determine the reason and solution for this error: Components are winnowed for the following reasons: • The components do not support installation on the given operating system • HP SUM does not discover the component's supported hardware on the targets. • The component is not for the type of target selected • HP SUM cannot deploy the component to the target. • The component cannot be deployed in either the online or offline environment Example: The following is an example of an output trace from the OpMan.trace file. In the example, the binary image files 0.bin and 1.bin (which are iLO firmware files), components cp011301.exe and cp011500.exe, and the HP SPP represented by bundle file bp000648.xml were added to the installation set. All the other components were removed. 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 InstallSet.cpp[222]: Winnow--Removing FileName cp011550.exe InstallSet.cpp[222]: Winnow--Removing FileName cp011560.exe InstallSet.cpp[242]: Target 0: Added Bundle bp000648.xml 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, that 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.exe (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. Installation issues 61

  • 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

5 Troubleshooting
Installation issues
Components do not appear on the Select Items to Install screen or do not deploy from
the silent console mode
Solution:
Components were not included in the installation set. Check the
OpMan.trace
file to
see which components were not included. For the location and more information about trace files,
see
“Collecting trace directories” (page 61)
.
Use the following checklist to determine the reason and solution for this error:
Components are winnowed for the following reasons:
The components do not support installation on the given operating system
HP SUM does not discover the component's supported hardware on the targets.
The component is not for the type of target selected
HP SUM cannot deploy the component to the target.
The component cannot be deployed in either the online or offline environment
Example:
The following is an example of an output trace from the
OpMan.trace
file. In the
example, the binary image files
0.bin
and
1.bin
(which are iLO firmware files), components
cp011301.exe
and
cp011500.exe
, and the HP SPP represented by bundle file
bp000648.xml
were added to the installation set. All the other components were removed.
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
InstallSet.cpp[222]: Winnow--Removing FileName cp011550.exe
InstallSet.cpp[222]: Winnow--Removing FileName cp011560.exe
InstallSet.cpp[242]: Target 0: Added Bundle bp000648.xml
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, that 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.exe
(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.
Installation issues
61