Status in source: mandatory.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"hpiSensorEventAssertion",
"OBJECT-TYPE",
"SYNTAX",
"TruthValue",
"ACCESS",
"read-only",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"Sensor Events and Sensor Event States: Each Event State may be asserted or deasserted. The set of Event States a sensor may support is defined by the sensor's 'Event Category.' A particular sensor, however, does not have to support all the Event States defined for its event category. The specific Event States that a particular sensor supports are indicated in the 'Events' field in the sensor's RDR. A sensor is not required to support any Event States. If no Event States are supported by a sensor, the 'Events' field will be 0x0000. A sensor may not support any Event States that are not defined for its event category. Each Event State is independent, although in some event categories the meaning assigned to the Event States will imply that certain Event States will be mutually exclusive. For example, a sensor that uses the SAHPI_EC_LIMIT event category should only have one of the two Event States, SAHPI_ES_LIMIT_NOT_EXCEEDED or SAHPI_ES_LIMIT_EXCEEDED asserted at any one time. Except where mutual exclusion is implied, however, sensors may have multiple Event States asserted simultaneously. For example, the event category SAHPI_EC_THRESHOLD uses six different event states to report the relationship between the value currently measured by the sensor and up to six different 'threshold' values. Each threshold is independently examined, and each Event State that represents a threshold that has been 'crossed' will be asserted. Threshold values must be configured so that 'Minor', 'Major' and 'Critical' thresholds are increasingly extreme readings, such that when a 'Major' threshold has been crossed, the corresponding 'Minor' threshold will also have been crossed, and thus both Event States will be asserted. When a sensor Event State is asserted or deasserted, an event may be generated by the resource. The generated event identifies the sensor and the event state being asserted or deasserted. The HPI implementation may assign event severity levels for each event state assertion or deassertion on an individual sensor basis.\"",
"::=",
"{",
"hpiSensorEventEntry",
"4",
"}"
],
"syntax_tree": [
[
"row",
"TruthValue"
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"Sensor Events and Sensor Event States: Each Event State may be asserted or deasserted. The set of Event States a sensor may support is defined by the sensor's 'Event Category.' A particular sensor, however, does not have to support all the Event States defined for its event category. The specific Event States that a particular sensor supports are indicated in the 'Events' field in the sensor's RDR. A sensor is not required to support any Event States. If no Event States are supported by a sensor, the 'Events' field will be 0x0000. A sensor may not support any Event States that are not defined for its event category. Each Event State is independent, although in some event categories the meaning assigned to the Event States will imply that certain Event States will be mutually exclusive. For example, a sensor that uses the SAHPI_EC_LIMIT event category should only have one of the two Event States, SAHPI_ES_LIMIT_NOT_EXCEEDED or SAHPI_ES_LIMIT_EXCEEDED asserted at any one time. Except where mutual exclusion is implied, however, sensors may have multiple Event States asserted simultaneously. For example, the event category SAHPI_EC_THRESHOLD uses six different event states to report the relationship between the value currently measured by the sensor and up to six different 'threshold' values. Each threshold is independently examined, and each Event State that represents a threshold that has been 'crossed' will be asserted. Threshold values must be configured so that 'Minor', 'Major' and 'Critical' thresholds are increasingly extreme readings, such that when a 'Major' threshold has been crossed, the corresponding 'Minor' threshold will also have been crossed, and thus both Event States will be asserted. When a sensor Event State is asserted or deasserted, an event may be generated by the resource. The generated event identifies the sensor and the event state being asserted or deasserted. The HPI implementation may assign event severity levels for each event state assertion or deassertion on an individual sensor basis."
],
null,
null,
null,
null
]
}