WBEM Indication Providers and EMS Hardware Monitors
Hardware monitors are available to monitor the following components (these monitors are distributed
free on the OE media):
• Chassis/Fans/Environment
• CPU monitor
• UPS monitor
• FC Hub monitor
• FC Switch monitor
• Memory monitor
• Core Electronics Components
• Disk drives
• Ha_disk_array
Errors and Error Logs
Event Log Definitions
Often the underlying root cause of an MCA event is captured by server blade or BMC firmware
in both the System Event Log (SEL) and Forward Progress Event Logs (FP). These errors are easily
matched with MCA events by their timestamps. For example, the loss of a processor VRM might
cause a processor fault. Decoding the MCA error logs would only identify the failed processor 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 iLO 2 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.
Errors and Error Logs 101
To Next Page
Loading...
Need help?
General