User Service Guide, Second Edition - HP Integrity BL60p Server Blade

Troubleshooting
Errors and Error Logs
Chapter 5
81
Errors and Error Logs
Event Log Definitions
Often the underlying root cause of an event is captured by server blade or BMC firmware in both the System
Event and Forward Progress Event Logs (SEL and FP, respectively). These errors are easily matched with
events by their timestamps. For example, the loss of a CPU’s VRM might cause a CPU fault. Decoding the
error logs would only identify the failed CPU as the most likely faulty FRU. Following are some
important points to remember about events and event logs:
• Event logs are the equivalent of the old chassis logs for status or error information output.
• Symbolic names are used in the source code; for example, MC_CACHE_CHECK.
• The hex code for each event log is 128 bits long with an architected format:
— Some enumerated fields can be mapped to defined text strings.
— All can be displayed in hex, keyword, or text mode.
• Events are created by firmware or OS code, and are sent over the PDH bus to the BMC for storage in
either or both of the SEL and FP logs (HP-UX shows an I/O path for the BMC).
• The MP displays event logs: SEL events are sent over the IPMB, between the BMC and the MP.
• Event logs are read back over the PDH bus by software (i.e., the IPMI driver or agent) for storage on disk.
Event Log Usage
To consult the event logs:
1. Connect to the system console.
2. Enter
Ctrl+B to access the MP Main Menu.
3. Enter the sl command to view event logs: System Event (E) and Forward Progress (F) logs are useful to
determine the context of an error.
NOTE The SEL E shows only event logs with alert level 2 or higher. The SEL defaults to alert level 2
on the BL60p because there are some level 2 events related to rack infrastructure change. the
alert level can be changed. The SEL is never overwritten unless first manually cleared. It does
get full.
The Forward Progress Log (F) shows all event log outputs. The FPL log is circular. It wraps,
automatically replacing the oldest events with the newest. It never get full. Oldest logs get
overwritten first.