Acer R700 manual System Event Log, Platform Event Management

19

You can use the FRU/SDR Load Utility (see “FRU/SDR Load Utility Description” on page 76) to initialize or update the FRU and SDR information. Acer server boards are shipped from the factory with some sensors disabled, because the actual configuration of the chassis is only determined when the user completes the system configuration. Chassis-specific information in the FRU, such as chassis part number, is also absent. For these reasons, it is important to run the FRU/SDR Load Utility as part of the system setup process. You should also run the FRU/ SDR Load Utility whenever you change the number of fans, processors, or power supplies in the server.

System Event Log

The BMC manages a system event log (SEL), where it records significant or critical system events. Such events include temperatures and events. The BIOS, software, and other devices can also log events by sending messages to the BMC. The SEL is stored in nonvolatile storage.

You can view the current contents of the SEL by using the System Setup Utility (see “Viewing the System Event Log” on page 63).

Platform Event Management

Events can trigger alerts and other actions by the BMC. The server is configured with the following set of standard events:

•Temperature sensor out of range

•Voltage sensor out of range

•Fan failure

•Chassis intrusion

•Power supply fault

•BIOS uncorrectable ECC error

•BIOS POST error

•Processor fault resilient booting (FRB) failure

•Fatal nonmaskable interrupt (NMI) from a source other than the front panel switch

•Watchdog timer reset, power down, or power cycle

•System restart (reboot)

Alerts can take either of these forms: