Scroll to navigation

FREEIPMI_INTERPRET_SEL(5) Configuration FREEIPMI_INTERPRET_SEL(5)

NAME

freeipmi_interpret_sel.conf - specify system event log (SEL) interpretation rules

DESCRIPTION

The /etc/freeipmi//freeipmi_interpret_sel.conf defines how IPMI system event log entries should be interpreted. IPMI system events specify a number of states/thresholds when they are read. Based on those states/thresholds, libraries and tools such as libipmimonitoring(3) and ipmi-sel(8) can report if an event is "good" or "bad" via a report of a NOMINAL, WARNING, or CRITICAL state. A different state can be reported for an event depending on if it is asserted or deasserted.

Each of the states listed below are (hopefully) descriptive enough to describe the state conditions that may be set/unset for each sensor or event type. For more detailed information on each of the individual states listed below, please see the IPMI Specification "Sensor and Event Code Tables". Ipmi-sensors(8) can be used to determine the sensor types and the states/thresholds that exist on a system by outputting very verbose output and seeing what types of Assertion or Deassertion events are possible.

Each of the events below may may take 1 or 2 of the following states as input.

Nominal - Signal Nominal reading if event tripped

Warning - Signal Warning reading if event tripped

Critical - Signal Critical reading if event tripped

If only one state is listed, that state will be interpreted when the event is asserted or deasserted. If two states are listed, the first state will be interpreted when an event is asserted, and the later will be interpreted when an event is deasserted.

Not all IPMI sensor types and event types are currently supported. If you would like more to be supported, please e-mail the FreeIPMI mailing list.

The default values selected for individual events being tripped are based on best guesses and motherboards being analyzed. If you think they should be changed, please e-mail the FreeIPMI mailing list to discuss what the defaults should be.

Most default interpretations can be determined quite easily and can meet the needs of most users. For example, a reading of "Performance_Met" is normally better than "Performance_Lags". However, some sensors can be ambiguous and depend completely on the manufacturer. For example, "State_Asserted" vs. "State_Deasserted" are completely at the interpretation of the vendor. Users are advised to adjust the interpretations below as needed for their machines.

FORMAT

The configuration options that can be specified in the configuration file are listed below. Each configuration option must be listed on a separate line. Arguments for an option are separated by any amount of whitespace. Multiple arguments are also separated by whitespace. Comments can be marked by using the pound sign ("#") character, and lines can be continued on the next using backslash ("\").

OPTIONS

The following states correspond to threshold sensor events. This normally applies to events that dealing with non-discrete values, such as temperatures, voltages, RPM, etc.
The following states correspond to Temperature sensor events that report an assertion or deassertion.
Defaults to Nominal.
Defaults to Warning.
The following states correspond to Temperature sensor events that report on limits.
Defaults to Nominal.
Defaults to Critical.
The following states correspond to Temperature sensor events that report on transition severity.
The following states correspond to Voltage sensor events that report an assertion or deassertion.
Defaults to Nominal.
Defaults to Warning.
The following states correspond to Voltage sensor events that report on limits.
Defaults to Nominal.
Defaults to Critical.
The following states correspond to Voltage sensor events that report on performance.
Defaults to Nominal/Nominal.
Defaults to Critical/Warning.
The following states correspond to Voltage sensor events that report on device severity.
The following states correspond to Current sensor events that report on device severity.
The following states correspond to Fan sensor events that report an assertion or deassertion.
Defaults to Nominal.
Defaults to Warning.
The following states correspond to Fan sensor events that report on device severity.
The following states correspond to Fan sensor events that report on device installation.
The following states correspond to Fan sensor events that report on device availability.
Defaults to Nominal/Nominal.
Defaults to Warning/Warning.
Defaults to Warning/Warning.
Defaults to Warning/Warning.
Defaults to Warning/Warning.
Defaults to Warning/Warning.
Defaults to Critical/Warning.
Defaults to Warning/Warning.
Defaults to Critical/Critical.
The following states correspond to Fan sensor events that report on redundancy.
The following states correspond to Physical Security sensor events w/ Physical Security specific output events.
The following states correspond to Platform Violation Attempt sensor events w/ Platform Security Violation Attempt specific output events.
The following states correspond to Processor sensor events w/ Processor specific output events.
The following states correspond to Processor sensor events that report an assertion or deassertion.
Defaults to Nominal.
Defaults to Critical.
The following states correspond to Power Supply sensor events w/ Power Supply specific output events.
Defaults to Nominal/Nominal.
Defaults to Critical/Critical.
Defaults to Critical/Critical.
Defaults to Critical/Warning.
Defaults to Critical/Warning.
Defaults to Critical/Warning.
Defaults to Critical/Critical.
Defaults to Warning/Warning.
The following states correspond to Power_Supply sensor events that report an assertion or deassertion.
Defaults to Critical.
Defaults to Nominal.
The following states correspond to Power Supply sensor events that report on device severity.
The following states correspond to Power Supply sensor events that report on redundancy.
The following states correspond to Power Unit sensor events w/ Power Unit specific output events.
Defaults to Nominal/Nominal.
Defaults to Nominal/Nominal.
Defaults to Warning/Nominal.
Defaults to Warning/Warning.
Defaults to Critical/Warning.
Defaults to Critical/Critical.
Defaults to Critical/Critical.
Defaults to Critical/Critical.
The following states correspond to Power Unit sensor events that report on device installation.
The following states correspond to Power Unit sensor events that report on redundancy.
The following states correspond to Cooling Device sensor events that report on redundancy.
The following states correspond to Memory sensor events w/ Memory specific output events.
Defaults to Warning.
Defaults to Critical.
Defaults to Critical.
Defaults to Critical.
Defaults to Critical.
Defaults to Warning.
Defaults to Nominal.
Defaults to Critical.
Defaults to Nominal.
Defaults to Warning.
Defaults to Critical.
The following states correspond to Memory sensor events that report an assertion or deassertion.
Defaults to Nominal.
Defaults to Critical.
The following states correspond to Memory sensor events that report on transition severity.
The following states correspond to Memory sensor events that report on redundancy.
The following states correspond to Drive Slot sensor events w/ Drive Slot specific output events.
Defaults to Nominal.
Defaults to Critical.
IPMI_Drive_Slot_Predictive_Failure
Defaults to Critical.
Defaults to Nominal.
Defaults to Nominal.
Defaults to Critical.
Defaults to Critical.
Defaults to Nominal.
Defaults to Critical.
The following states correspond to Drive Slot sensor events that report an assertion or deassertion.
Defaults to Warning.
Defaults to Nominal.
The following states correspond to Drive_Slot sensor events that report a predictive failure assertion or deassertion.
The following states correspond to Drive Slot sensor events that report on device installation.
The following states correspond to POST Memory Resize sensor events that report an assertion or deassertion.
The following states correspond to System Firmware Progress sensor events w/ System Firmware Progress specific output events.
The following states correspond to System Firmware Progress sensor events that report on device severity.
The following states correspond to Event Logging Disabled sensor events w/
The following states correspond to System Event sensor events w/ System Event specific output events.
The following states correspond to System Event sensor events that report a transition state.
The following states correspond to System Event sensor events that report an assertion or deassertion.
Defaults to Nominal.
Defaults to Warning.
The following states correspond to Critical Interrupt sensor events w/ Critical Interrupt specific output events.
Defaults to Critical.
Defaults to Critical.
Defaults to Critical.
Defaults to Warning.
Defaults to Critical.
Defaults to Critical.
Defaults to Critical.
Defaults to Warning.
Defaults to Critical.
Defaults to Critical.
Defaults to Critical. IPMI_Critical_Interrupt_Bus_Degraded Defaults to Warning.
The following states correspond to Button/Switch sensor events w/ Button/Switch specific output events.
The following states correspond to Button/Switch sensor events that report an assertion or deassertion.
The following states correspond to Button Switch sensor events that report on device severity.
The following states correspond to Module/Board sensor events that report an assertion or deassertion.
Defaults to Nominal.
Defaults to Critical.
The following states correspond to Module/Board sensor events that report on device installation.
The following states correspond to Chassis sensor events that report on device severity.
The following states correspond to Chip Set sensor events w/ Chip Set specific output events.
Defaults to Critical.
Defaults to Critical.
The following states correspond to Chip Set sensor events that report on device severity.
The following states correspond to Cable/Interconnect sensor events w/ Cable/Interconnect specific output events.
The following states correspond to Cable/Interconnect sensor events that report on device severity.
The following states correspond to System Boot Initiated sensor events w/ System Boot Initiated specific output events.
IPMI_System_Boot_Initiated_Initiated_By_Power_Up Defaults to Nominal. IPMI_System_Boot_Initiated_Initiated_By_Hard_Reset Defaults to Nominal. IPMI_System_Boot_Initiated_Initiated_By_Warm_Reset Defaults to Nominal. IPMI_System_Boot_Initiated_User_Requested_PXE_Boot Defaults to Nominal. IPMI_System_Boot_Initiated_Automatic_Boot_To_Diagnostic Defaults to Nominal. IPMI_System_Boot_Initiated_OS_Run_Time_Software_Initiated_Hard_Reset Defaults to Warning. IPMI_System_Boot_Initiated_OS_Run_Time_Software_Initiated_Warm_Reset Defaults to Warning. IPMI_System_Boot_Initiated_System_Restart Defaults to Nominal.
The following states correspond to Boot Error sensor events w/ Boot Error specific output events.
The following states correspond to Boot Error sensor events that report an assertion or deassertion.
Defaults to Nominal.
Defaults to Critical.
The following states correspond to Boot Error sensor events that report on device severity.
The following states correspond to OS Boot sensor events w/ OS Boot specific output events.
IPMI_OS_Boot_A_Boot_Completed Defaults to Nominal. IPMI_OS_Boot_C_Boot_Completed Defaults to Nominal. IPMI_OS_Boot_PXE_Boot_Completed Defaults to Nominal. IPMI_OS_Boot_Diagnostic_Boot_Completed Defaults to Nominal. IPMI_OS_Boot_CD_ROM_Boot_Completed Defaults to Nominal. IPMI_OS_Boot_ROM_Boot_Completed Defaults to Nominal. IPMI_OS_Boot_Boot_Completed_Boot_Device_Not_Specified Defaults to Warning. IPMI_OS_Boot_Base_OS_Hypervisor_Installation_Started Defaults to Nominal. IPMI_OS_Boot_Base_OS_Hypervisor_Installation_Completed Defaults to Nominal. IPMI_OS_Boot_Base_OS_Hypervisor_Installation_Aborted Defaults to Warning. IPMI_OS_Boot_Base_OS_Hypervisor_Installation_Failed Defaults to Critical.
The following states correspond to OS Critical Stop sensor events w/ OS Critical Stop specific output events.
IPMI_OS_Critical_Stop_Critical_Stop_During_OS_Load Defaults to Critical. IPMI_OS_Critical_Stop_Run_Time_Critical_Stop Defaults to Critical. IPMI_OS_Critical_Stop_OS_Graceful_Stop Defaults to Warning. IPMI_OS_Critical_Stop_OS_Graceful_Shutdown Defaults to Warning. IPMI_OS_Critical_Stop_Soft_Shutdown_Initiated_By_PEF Defaults to Warning. IPMI_OS_Critical_Stop_Agent_Not_Responding Defaults to Critical.
The following states correspond to OS Critical Stop sensor events that report an assertion or deassertion.
The following states correspond to Slot Connector sensor events w/ Slot Connector specific output events.
The following states correspond to Slot Connector sensor events that report on device severity.
The following states correspond to Watchdog 2 sensor events w/ Watchdog 2 specific output events.
Defaults to Warning.
Defaults to Critical.
Defaults to Critical.
Defaults to Critical.
Defaults to Nominal.
Defaults to Nominal.
Defaults to Nominal.
Defaults to Nominal.
Defaults to Warning.
The following states correspond to Platform Alert sensor events w/ Platform Alert specific output events.
IPMI_Platform_Alert_Platform_Generated_Page Defaults to Nominal. IPMI_Platform_Alert_Platform_Generated_LAN_Alert Defaults to Nominal. IPMI_Platform_Alert_Platform_Event_Trap_Generated Defaults to Nominal. IPMI_Platform_Alert_Platform_Generated_SNMP_Trap Defaults to Nominal.
The following states correspond to Platform Alert sensor events that report an assertion or deassertion.
The following states correspond to Entity Presence sensor events w/ Entity Presence specific output events.
The following states correspond to Entity Presence sensor events that report on device installation.
The following states correspond to LAN sensor events w/ LAN specific output events.
IPMI_LAN_Heartbeat Defaults to Nominal. IPMI_LAN_Heartbeat_Lost Defaults to Warning.
The following states correspond to Management Subsystem Health sensor events w/ Management Subsystem Health specific output events.
The following states correspond to Battery sensor events w/ Battery specific output events.
Defaults to Warning.
Defaults to Critical.
Defaults to Nominal.
The following states correspond to Session Audit sensor events w/ Session Audit specific output events.
The following states correspond to Version Change sensor events that Version Change specific output events.
The following states correspond to FRU State sensor events w/ FRU State specific output events.
The following configuration options can be used to configure OEM system event log events. Interpretations rules for a specific combination of Manufacturer-ID, Product-ID, and Record-Type, are iterated through and the worst resulting sensor state is returned (i.e. Warning < Nominal, Critical < Warning). If no match is found, no state is returned for the OEM event. For each of the configuration options below, <Manufacturer-ID> is the numeric IANA manufacturer ID for the manufacturer in question. The <Product-ID> is one or more numeric IDs representing the manufacturer's product. The <Product-ID> can be listed as a single numeric number (e.g. 1234), a range of IDs separated by a dash (e.g. 12-20), or a list of specific product IDs separated by a plus (e.g. 12+19+22). Both the Manufacturer-ID and Product-ID can be found using bmc-info(8). Multiple <Manufacturer-ID> and <Product-ID> pairs can be input separated by commas.
IPMI_OEM_System_Event_Record can be used to configure a state interpretation for a specific Manufacturer-ID, Product-ID, Event-Reading-Type-Code, and Sensor-Type combination, and a specific Event-Direction, EventData1, EventData2, and EventData3. The Event-Direction field must specify Assertion, Deassertion, or ANY. Each of the EventData fields must specify a hex byte to match or the keyword ANY to match anything. The Event-Reading-Type-Code and Sensor-Type need not be OEM types. They may be non-OEM types and used to provide interpretation rules for sensors that may be behaving outside the standard of the IPMI specification.
IPMI_OEM_Timestamped_Record can be used to configure an interpretation for a specific Manufacturer-ID, Product-ID, Record-Type, and OEM data combination. The Record-Type must be a legal record type for OEM Timestamped Records (currently 0xC0-0xDF). Each of the OEMDATA fields must specify a hex byte to match or the keyword ANY to match anything.
IPMI_OEM_Non_Timestamped_Record can be used to configure an interpretation for a specific Manufacturer-ID, Product-ID, Record-Type, and OEM data combination. The Record-Type must be a legal record type for OEM Non-Timestamped Records (currently 0xEO-0xFF). Each of the OEMDATA fields must specify a hex byte to match or the keyword ANY to match anything.

FILES

/etc/freeipmi//freeipmi_interpret_sel.conf

REPORTING BUGS

Report bugs to <freeipmi-users@gnu.org> or <freeipmi-devel@gnu.org>.

COPYRIGHT

Copyright (C) 2007-2015 Lawrence Livermore National Security, LLC.

This library is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version.

SEE ALSO

libfreeipmi(3), libipmimonitoring(3), ipmi-sel(8)

http://www.gnu.org/software/freeipmi/

2024-02-24 FreeIPMI 1.6.13