Using Event Logs - HPE Integrity rx2800 i2 series User's & Service Manual

processor fault. Decoding the MCA error logs would only identify the failed processor as the most likely
faulty CRU. Following are some important points to remember about events and event logs:
• Event logs are the equivalent of the old server 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 iLO MP for storage
in either or both of the SEL and FPL logs (HP-UX shows an I/O path for the iLO MP).
• The iLO 3 MP can display event logs: SEL events are sent over the IPMB.
• Event logs can also be read back over the PDH bus by software (for example, the IPMI driver or
agent) for storage on disk.

Using event logs

To consult the event logs:
Procedure
1. Connect to the system console.
2. Use Ctrl-B to access the iLO 3 MP menu.
3. Use the sl command to view event logs: System Event (E) and Forward Progress (F) logs are very
useful in determining the context of an error (see the following figure for an example):
NOTE:
Remember that:
• E shows only event logs for Warning, Critical, or Fatal faults by default; F shows all event log
outputs.
• System Event Logs are never overwritten, unless they are first manually cleared. When the SEL
is filled, no more events are logged. Forward Progress Logs (FPL) are circular and contain
additional, non-critical information.
• The alert threshold can be changed.
iLO 3 MP event logs
The iLO 3 MP provides diagnostic and configuration capabilities. See the HPE Integrity iLO 3 Operations
Guide for details on the iLO 3 MP commands.
http://www.hpe.com/info/integrity_servers-docs
To access the iLO 3 MP:
106 Using event logs