1FREEIPMI_INTERPRET_SENSOR(5) Configuration FREEIPMI_INTERPRET_SENSOR(5)
2
6 freeipmi_interpret_sensor.conf - specify sensor interpretation rules
7
9 The /etc/freeipmi//freeipmi_interpret_sensor.conf defines how IPMI sen‐
10 sors should be interpreted. IPMI based sensors specify a number of
11 states/thresholds when they are read. Based on those states/thresholds,
12 libraries and tools such as libfreeipmi(3), libipmimonitoring(3) and
13 ipmi-sensors(8) can report if a sensor reading is "good" or "bad" via a
14 report of a NOMINAL, WARNING, or CRITICAL state.
15 Each of the states listed below are (hopefully) descriptive enough to
17 describe the state conditions that may be set/unset for each sensor
18 type. For more detailed information on each of the individual states
19 listed below, please see the IPMI Specification "Sensor and Event Code
20 Tables". Ipmi-sensors(8) can be used to determine the sensor types and
21 the states/thresholds that exist on a system by outputting very verbose
22 output and seeing what types of Assertion or Deassertion events are
23 possible.
24 The possible values for all states/thresholds below are:
26 Nominal - Signal Nominal reading if state/threshold tripped
28 Warning - Signal Warning reading if state/treshold tripped
30 Critical - Signal Critical reading if state/threshold tripped
32 Not all IPMI sensor types and event types are currently supported. If
34 you would like more to be supported, please e-mail the FreeIPMI mailing
35 list.
36 The default values selected for individual states/thresholds being
38 tripped are based on best guesses and motherboards being analyzed. If
39 you think they should be changed, please e-mail the FreeIPMI mailing
40 list to discuss what the defaults should be.
41 Most default interpretations can be determined quite easily and can
43 meet the needs of most users. For example, a reading of "Perfor‐
44 mance_Met" is normally better than "Performance_Lags". However, some
45 sensors can be ambiguous and depend completely on the manufacturer. For
46 example, "State_Asserted" vs. "State_Deasserted" are completely at the
47 interpretation of the vendor. Users are advised to adjust the interpre‐
48 tations below as needed for their machines.
49 Every group of state conditions below includes a configuration for
51 "No_Event". This is the condition under which no sensor states/events
52 have occurred or are triggered. Under most conditions, a mapping to
53 "Nominal" is preferred. However, under some circumstances, it may be
54 useful to report something else. For example, if a sensor on a particu