HP ProLiant DL360e HP Smart Update Firmware DVD User Guide - Page 28

Array controller ROMs, Lights-Out management ROMs, Recovering from an installation failure

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

Page 28 highlights

Array controller ROMs Array controllers support Recovery ROM, which is a redundancy feature that ensures continuous system availability by providing a backup ROM. During the flash process, a new version of the firmware can be flashed to the ROM while the controller maintains the last known version of the firmware. If the firmware becomes corrupt, the controller reverts back to the redundant version of the firmware and continues operating. NOTE: Storage option ROMs cannot be downgraded with ROMPaq because ROMPaqs have been retired as a delivery method for storage options. Lights-Out management ROMs To perform disaster recovery for RILOE II, iLO, iLO 2, iLO 3, and iLO 4, see the documentation for your particular Lights-Out management product on the Remote Management website at http:// www.hp.com/servers/lights-out. Recovering from an installation failure Collecting trace directories HP SUM generates a set of debug trace logs located in the %TEMP%\hp_sum directory on Windows systems and \tmp\hp_sum on Linux systems. These files contain internal process and debug information, which can be useful in determining HP SUM failures. HP SUM also has a log collecting utility for Windows (GatherLogs.exe) and Linux (GatherLogs.sh) that creates a compressed file (a Windows .zip file or a Linux tar.Z file) with all the logs. Run this utility to gather all the logs in one file. NOTE: To break out to a Linux console while booted to the Smart Update Firmware DVD or SPP, press Ctrl+Alt+d+b+x. Each key (d, b, and x) is hit in succession. This command allows you to collect logs from the \tmp\hp_sum directory. Examine the OpMan.trace, and the InstallManager.log trace files to determine the cause of the failure. These files provide the following information. Trace files Function OpMan.trace Provides operations trace of the overall installation process. InstallManager.log Provides the interaction between the Operations Manager and the remote installation client. Any failure in network communications is reported in this file and surfaced as an Installation Failed message for the affected component and potentially all components that follow the failing component. \InstallManager.log Provides the interaction between the Operations Manager and the remote installation client. Any failure in network communications is reported in this file and surfaced as an Installation Failed message for the affected component and potentially all components that follow the failing component. discagent.trace Provides the details of the execution of the discovery agent on either the local system during a local installation or the remote target server. If a discovery tool fails, it is reported to this trace file and surfaced as a Discovery Failed message. discmanager.trace 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. InventoryResults.xml Provides details of the component inventory from the repositories. Settings.xml Provides general settings information of HP SUM such as Force downgrade or upgrade. 28 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
Array controller ROMs
Array controllers support Recovery ROM, which is a redundancy feature that ensures continuous
system availability by providing a backup ROM. During the flash process, a new version of the
firmware can be flashed to the ROM while the controller maintains the last known version of the
firmware. If the firmware becomes corrupt, the controller reverts back to the redundant version of
the firmware and continues operating.
NOTE:
Storage option ROMs cannot be downgraded with ROMPaq because ROMPaqs have
been retired as a delivery method for storage options.
Lights-Out management ROMs
To perform disaster recovery for RILOE II, iLO, iLO 2, iLO 3, and iLO 4, see the documentation for
your particular Lights-Out management product on the Remote Management website at
h
t
tp://
w
w
w
.hp
.co
m/s
e
r
v
e
r
s/li
gh
ts
-o
u
t
.
Recovering from an installation failure
Collecting trace directories
HP SUM generates a set of debug trace logs located in the
%TEMP%\hp_sum
directory on Windows
systems and
\tmp\hp_sum
on Linux systems. These files contain internal process and debug
information, which can be useful in determining HP SUM failures.
HP SUM also has a log collecting utility for Windows (
GatherLogs.exe
) and Linux
(
GatherLogs.sh
) that creates a compressed file (a Windows
.zip
file or a Linux
tar.Z
file)
with all the logs. Run this utility to gather all the logs in one file.
NOTE:
To break out to a Linux console while booted to the Smart Update Firmware DVD or SPP,
press
Ctrl+Alt+d+b+x
. Each key (
d
,
b
, and
x
) is hit in succession. This command allows you
to collect logs from the
\tmp\hp_sum
directory.
Examine the
OpMan.trace
, and the
InstallManager.log
trace files to determine the cause
of the failure. These files provide the following information.
Function
Trace files
Provides operations trace of the overall installation process.
OpMan.trace
Provides the interaction between the Operations Manager and the remote
installation client. Any failure in network communications is reported in this file
InstallManager.log
and surfaced as an Installation Failed message for the affected component and
potentially all components that follow the failing component.
Provides the interaction between the Operations Manager and the remote
installation client. Any failure in network communications is reported in this file
<
target
>\InstallManager.log
and surfaced as an Installation Failed message for the affected component and
potentially all components that follow the failing component.
Provides the details of the execution of the discovery agent on either the local
system during a local installation or the remote target server. If a discovery tool
fails, it is reported to this trace file and surfaced as a Discovery Failed message.
discagent.trace
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.
discmanager.trace
Provides details of the component inventory from the repositories.
InventoryResults.xml
Provides general settings information of HP SUM such as Force downgrade or
upgrade.
Settings.xml
28
Troubleshooting