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.
- IPMI_Threshold_Sensor
- 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.
- IPMI_Temperature_State
- The following states correspond to Temperature sensor events that report
an assertion or deassertion.
- IPMI_Temperature_Limit
- The following states correspond to Temperature sensor events that report
on limits.
- IPMI_Temperature_Transition_Severity
- The following states correspond to Temperature sensor events that report
on transition severity.
- IPMI_Voltage_State
- The following states correspond to Voltage sensor events that report an
assertion or deassertion.
- IPMI_Voltage_Limit
- The following states correspond to Voltage sensor events that report on
limits.
- IPMI_Voltage_Performance
- The following states correspond to Voltage sensor events that report on
performance.
- IPMI_Voltage_Transition_Severity
- The following states correspond to Voltage sensor events that report on
device severity.
- IPMI_Current_Transition_Severity
- The following states correspond to Current sensor events that report on
device severity.
- IPMI_Fan_State
- The following states correspond to Fan sensor events that report an
assertion or deassertion.
- IPMI_Fan_Transition_Severity
- The following states correspond to Fan sensor events that report on device
severity.
- IPMI_Fan_Device_Present
- The following states correspond to Fan sensor events that report on device
installation.
- IPMI_Fan_Transition_Availability
- The following states correspond to Fan sensor events that report on device
availability.
- IPMI_Fan_Redundancy
- The following states correspond to Fan sensor events that report on
redundancy.
- IPMI_Physical_Security
- The following states correspond to Physical Security sensor events w/
Physical Security specific output events.
- IPMI_Platform_Security_Violation_Attempt
- The following states correspond to Platform Violation Attempt sensor
events w/ Platform Security Violation Attempt specific output events.
- IPMI_Processor
- The following states correspond to Processor sensor events w/ Processor
specific output events.
- IPMI_Processor_State
- The following states correspond to Processor sensor events that report an
assertion or deassertion.
- IPMI_Power_Supply
- The following states correspond to Power Supply sensor events w/ Power
Supply specific output events.
- IPMI_Power_Supply_State
- The following states correspond to Power_Supply sensor events that report
an assertion or deassertion.
- IPMI_Power_Supply_Transition_Severity
- The following states correspond to Power Supply sensor events that report
on device severity.
- IPMI_Power_Supply_Redundancy
- The following states correspond to Power Supply sensor events that report
on redundancy.
- IPMI_Power_Unit
- The following states correspond to Power Unit sensor events w/ Power Unit
specific output events.
- IPMI_Power_Unit_Device_Present
- The following states correspond to Power Unit sensor events that report on
device installation.
- IPMI_Power_Unit_Redundancy
- The following states correspond to Power Unit sensor events that report on
redundancy.
- IPMI_Cooling_Device_Redundancy
- The following states correspond to Cooling Device sensor events that
report on redundancy.
- IPMI_Memory
- The following states correspond to Memory sensor events w/ Memory specific
output events.
- IPMI_Memory_State
- The following states correspond to Memory sensor events that report an
assertion or deassertion.
- IPMI_Memory_Transition_Severity
- The following states correspond to Memory sensor events that report on
transition severity.
- IPMI_Memory_Redundancy
- The following states correspond to Memory sensor events that report on
redundancy.
- IPMI_Drive_Slot
- The following states correspond to Drive Slot sensor events w/ Drive Slot
specific output events.
- IPMI_Drive_Slot_State
- The following states correspond to Drive Slot sensor events that report an
assertion or deassertion.
- IPMI_Drive_Slot_Predictive_Failure
- The following states correspond to Drive_Slot sensor events that report a
predictive failure assertion or deassertion.
- IPMI_Drive_Slot_Device_Present
- The following states correspond to Drive Slot sensor events that report on
device installation.
- IPMI_POST_Memory_Resize_State
- The following states correspond to POST Memory Resize sensor events that
report an assertion or deassertion.
- IPMI_System_Firmware_Progress
- The following states correspond to System Firmware Progress sensor events
w/ System Firmware Progress specific output events.
- IPMI_System_Firmware_Progress_Transition_Severity
- The following states correspond to System Firmware Progress sensor events
that report on device severity.
- IPMI_Event_Logging_Disabled
- The following states correspond to Event Logging Disabled sensor events
w/
- IPMI_System_Event
- The following states correspond to System Event sensor events w/ System
Event specific output events.
- IPMI_System_Event_Transition_State
- The following states correspond to System Event sensor events that report
a transition state.
- IPMI_System_Event_State
- The following states correspond to System Event sensor events that report
an assertion or deassertion.
- IPMI_Critical_Interrupt
- The following states correspond to Critical Interrupt sensor events w/
Critical Interrupt specific output events.
- IPMI_Button_Switch
- The following states correspond to Button/Switch sensor events w/
Button/Switch specific output events.
- IPMI_Button_Switch_State
- The following states correspond to Button/Switch sensor events that report
an assertion or deassertion.
- IPMI_Button_Switch_Transition_Severity
- The following states correspond to Button Switch sensor events that report
on device severity.
- IPMI_Module_Board_State
- The following states correspond to Module/Board sensor events that report
an assertion or deassertion.
- IPMI_Module_Board_Device_Present
- The following states correspond to Module/Board sensor events that report
on device installation.
- IPMI_Chassis_Transition_Severity
- The following states correspond to Chassis sensor events that report on
device severity.
- IPMI_Chip_Set
- The following states correspond to Chip Set sensor events w/ Chip Set
specific output events.
- IPMI_Chip_Set_Transition_Severity
- The following states correspond to Chip Set sensor events that report on
device severity.
- IPMI_Cable_Interconnect
- The following states correspond to Cable/Interconnect sensor events w/
Cable/Interconnect specific output events.
- IPMI_Cable_Interconnect_Transition_Severity
- The following states correspond to Cable/Interconnect sensor events that
report on device severity.
- IPMI_System_Boot_Initiated
- 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.
- IPMI_Boot_Error
- The following states correspond to Boot Error sensor events w/ Boot Error
specific output events.
- IPMI_Boot_Error_State
- The following states correspond to Boot Error sensor events that report an
assertion or deassertion.
- IPMI_Boot_Error_Transition_Severity
- The following states correspond to Boot Error sensor events that report on
device severity.
- IPMI_OS_Boot
- 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.
- IPMI_OS_Critical_Stop
- 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.
- IPMI_OS_Critical_Stop_State
- The following states correspond to OS Critical Stop sensor events that
report an assertion or deassertion.
- IPMI_Slot_Connector
- The following states correspond to Slot Connector sensor events w/ Slot
Connector specific output events.
- IPMI_Slot_Connector_Transition_Severity
- The following states correspond to Slot Connector sensor events that
report on device severity.
- IPMI_System_ACPI_Power_State
- IPMI_Watchdog2
- The following states correspond to Watchdog 2 sensor events w/ Watchdog 2
specific output events.
- IPMI_Platform_Alert
- 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.
- IPMI_Platform_Alert_State
- The following states correspond to Platform Alert sensor events that
report an assertion or deassertion.
- IPMI_Entity_Presence
- The following states correspond to Entity Presence sensor events w/ Entity
Presence specific output events.
- IPMI_Entity_Presence_Device_Present
- The following states correspond to Entity Presence sensor events that
report on device installation.
- IPMI_LAN
- 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.
- IPMI_Management_Subsystem_Health
- The following states correspond to Management Subsystem Health sensor
events w/ Management Subsystem Health specific output events.
- IPMI_Battery
- The following states correspond to Battery sensor events w/ Battery
specific output events.
- IPMI_Session_Audit
- The following states correspond to Session Audit sensor events w/ Session
Audit specific output events.
- IPMI_Version_Change_Transition_Severity
- The following states correspond to Version Change sensor events that
Version Change specific output events.
- IPMI_FRU_State
- The following states correspond to FRU State sensor events w/ FRU State
specific output events.
- IPMI_OEM
- 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 separted 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_Sensor_System_Event_Record
<Manufacturer-ID>:<Product-ID>,...
Event-Reading-Type-Code Sensor-Type Event-Direction
EventData1 EventData2 EventData3 State
- 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
<Manufacturer-ID>:<Product-ID>,...
Record-Type OEMDATA1 OEMDATA2 OEMDATA3
OEMDATA4 OEMDATA5 OEMDATA6 State
- 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
<Manufacturer-ID>:<Product-ID>,...
Record-Type OEMDATA1 OEMDATA2 OEMDATA3
OEMDATA4 OEMDATA5 OEMDATA6 OEMDATA7
OEMDATA8 OEMDATA9 OEMDATA10 OEMDATA11
OEMDATA12 OEMDATA13 State
- 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.