Integrated Management Log; Server And Ilo Diagnostics - HP Integrated Lights-Out User Manual

To clear the <LOM_short_name:
Click Clear Event Log to clear the event log of all previously logged information.
1.
Click OK to confirm that you want to clear the event log. A line indicating that the log has been
2.
cleared is logged.

Integrated Management Log

The IML is a record of significant events that have occurred to the host platform. The events are generated
by the system ROM and by services like the System Management (Health) driver. iLO manages the IML,
which can be accessed by using a supported browser, even when the server is off. This capability can be
helpful when troubleshooting remote host server problems.
The IML enables you to view logged remote server events. Logged events include all server-specific events
recorded by the system health driver, including operating system information and ROM-based POST
codes. For more information, refer to the server guide.
Click Clear Event Log to clear the event log of all previously logged information.
1.
Click OK to confirm that you want to clear the event log. A line indicating that the log has been
2.
cleared is logged.

Server and iLO diagnostics

The Server and iLO Diagnostics option provides the following comprehensive diagnostic information:
POST diagnostic results for the host server (on page 69)
NVRAM environment variables listing (on page 70)
Virtual NMI button (on page 70)
iLO self-test results (on page 71)
NOTE:
You can log in using a local account only.
POST Diagnostic results for the host server
As an integrated management processor, iLO monitors the progress of the boot process of the server. The
host server ROM writes POST codes as it is booting. iLO records and displays these codes.
The POST codes document the booting process of the ROM BIOS. A code indicates the start of a
particular phase of the boot process. The POST code results can be used to determine the general phase
in which the boot process stopped prematurely. Use of the POST codes alone is usually not sufficient to
diagnose the actual root cause of a stopped boot process. The POST codes should be used in conjunction
with other tools, such as the IML, the local or iLO Remote Console, and the Diagnostic utilities to
determine the root cause of a stopped boot process.
The following list includes all of the POST codes and Diagnostic Results for the host server tracked by iLO
for a routine boot sequence on ProLiant servers.
Code Start of phase
FE04 EISA Initialization
FE08 PCI Initialization
When connected through the Diagnostics Port, the directory server is not available.
Using iLO 69