CISCO-ENTITY-SENSOR-MIB

TEXTUAL-CONVENTION

International System of Units (SI) prefixes.

TEXTUAL-CONVENTION

sensor measurement data types. valid values are: other(1): a measure other than those listed below unknown(2): unknown measurement, or arbitrary, relative numbers voltsAC(3): electric potential voltsDC(4): electric potential amperes(5): electric current watts(6): power hertz(7): frequency celsius(8): temperature percentRH(9): percent relative humidity rpm(10): shaft revolutions per minute cmm(11),: cubic meters per minute (airflow) truthvalue(12): value takes { true(1), false(2) } specialEnum(13): value takes user defined enumerated values

TEXTUAL-CONVENTION

When in the range 1 to 9, SensorPrecision is the number of decimal places in the fractional part of a SensorValue fixed-point number. When in the range -8 to -1, SensorPrecision is the number of accurate digits in a SensorValue fixed-point number. SensorPrecision is 0 for non-fixed-point numbers. Agent implementors must choose a value for SensorPrecision so that the precision and accuracy of a SensorValue is correctly indicated. For example, a temperature sensor that can measure 0o to 100o C in 0.1o increments, +/- 0.05o, would have a SensorPrecision of 1, a SensorDataScale of units(0), and a SensorValue ranging from 0 to 1000. The SensorValue would be interpreted as (degrees C * 10). If that temperature sensor's precision were 0.1o but its accuracy were only +/- 0.5o, then the SensorPrecision would be 0. The SensorValue would be interpreted as degrees C. Another example: a fan rotation speed sensor that measures RPM from 0 to 10,000 in 100 RPM increments, with an accuracy of +50/-37 RPM, would have a SensorPrecision of -2, a SensorDataScale of units(9), and a SensorValue ranging from 0 to 10000. The 10s and 1s digits of SensorValue would always be 0.

TEXTUAL-CONVENTION

Indicates the operational status of the sensor. ok(1) means the agent can read the sensor value. unavailable(2) means that the agent presently can not report the sensor value. nonoperational(3) means that the agent believes the sensor is broken. The sensor could have a hard failure (disconnected wire), or a soft failure such as out-of-range, jittery, or wildly fluctuating readings.

TEXTUAL-CONVENTION

sensor threshold relational operator types. valid values are: lessThan(1): if the sensor value is less than the threshold value lessOrEqual(2): if the sensor value is less than or equal to the threshold value greaterThan(3): if the sensor value is greater than the threshold value greaterOrEqual(4): if the sensor value is greater than or equal to the threshold value equalTo(5): if the sensor value is equal to the threshold value notEqualTo(6): if the sensor value is not equal to the threshold value

TEXTUAL-CONVENTION

sensor threshold severity. Valid values are: other(1) : a severity other than those listed below. minor(10) : Minor Problem threshold. major(20) : Major Problem threshold. critical(30): Critical problem threshold. A system might shut down the sensor associated FRU automatically if the sensor value reach the critical problem threshold.

TEXTUAL-CONVENTION

For sensors that measure voltsAC, voltsDC, amperes, watts, hertz, celsius, cmm this item is a fixed point number ranging from -999,999,999 to +999,999,999. Use the value -1000000000 to indicate underflow. Use the value +1000000000 to indicate overflow. Use SensorPrecision to indicate how many fractional digits the SensorValue has. For sensors that measure percentRH, this item is a number ranging from 0 to 100. For sensors that measure rpm, this item can take only nonnegative values, 0..999999999. For sensors of type truthvalue, this item can take only two values: true(1), false(2). For sensors of type specialEnum, this item can take any value in the range (-1000000000..1000000000), but the meaning of each value is specific to the sensor. For sensors of type other and unknown, this item can take any value in the range (-1000000000..1000000000), but the meaning of the values are specific to the sensor. Use Entity-MIB entPhysicalTable.entPhysicalVendorType to learn about the sensor type.

TEXTUAL-CONVENTION

Indicates the interval in seconds between updates to the sensor's value. The value zero indicates: - the sensor value is updated on demand (when polled by the agent for a get-request), - or when the sensor value changes (event-driven), - or the agent does not know the rate

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

This table lists the type, scale, and present value of a sensor listed in the Entity-MIB entPhysicalTable.

OBJECT-TYPE

An entSensorValueTable entry describes the present reading of a sensor, the measurement units and scale, and sensor operational status.

OBJECT-TYPE

This variable indicates the type of data reported by the entSensorValue. This variable is set by the agent at start-up and the value does not change during operation.

OBJECT-TYPE

This variable indicates the exponent to apply to sensor values reported by entSensorValue. This variable is set by the agent at start-up and the value does not change during operation.

OBJECT-TYPE

This variable indicates the number of decimal places of precision in fixed-point sensor values reported by entSensorValue. This variable is set to 0 when entSensorType is not a fixed-point type: voltsAC(1), voltsDC(2), amperes(3), watts(4), hertz(5), celsius(6), or cmm(9). This variable is set by the agent at start-up and the value does not change during operation.

OBJECT-TYPE

This variable reports the most recent measurement seen by the sensor. To correctly display or interpret this variable's value, you must also know entSensorType, entSensorScale, and entSensorPrecision. However, you can compare entSensorValue with the threshold values given in entSensorThresholdTable without any semantic knowledge.

OBJECT-TYPE

This variable indicates the present operational status of the sensor.

OBJECT-TYPE

This variable indicates the age of the value reported by entSensorValue

OBJECT-TYPE

This variable indicates the rate that the agent updates entSensorValue.

OBJECT-TYPE

This object identifies the physical entity for which the sensor is taking measurements. For example, for a sensor measuring the voltage output of a power-supply, this object would be the entPhysicalIndex of that power-supply; for a sensor measuring the temperature inside one chassis of a multi-chassis system, this object would be the enPhysicalIndex of that chassis. This object has a value of zero when the physical entity for which the sensor is taking measurements can not be represented by any one row in the entPhysicalTable, or that there is no such physical entity.

OBJECT-IDENTITY

OBJECT-TYPE

This table lists the threshold severity, relation, and comparison value, for a sensor listed in the Entity-MIB entPhysicalTable.

OBJECT-TYPE

An entSensorThresholdTable entry describes the thresholds for a sensor: the threshold severity, the threshold value, the relation, and the evaluation of the threshold. Only entities of type sensor(8) are listed in this table. Only pre-configured thresholds are listed in this table. Users can create sensor-value monitoring instruments in different ways, such as RMON alarms, Expression-MIB, etc. Entries are created by the agent at system startup and FRU insertion. Entries are deleted by the agent at FRU removal.

OBJECT-TYPE

An index that uniquely identifies an entry in the entSensorThreshold table. This index permits the same sensor to have several different thresholds.

OBJECT-TYPE

This variable indicates the severity of this threshold.

OBJECT-TYPE

This variable indicates the relation between sensor value (entSensorValue) and threshold value (entSensorThresholdValue), required to trigger the alarm. when evaluating the relation, entSensorValue is on the left of entSensorThresholdRelation, entSensorThresholdValue is on the right. in pseudo-code, the evaluation-alarm mechanism is: ... if (entSensorStatus == ok) then if (evaluate(entSensorValue, entSensorThresholdRelation, entSensorThresholdValue)) then if (entSensorThresholdNotificationEnable == true)) then raise_alarm(entSensorThresholdAlarmOID); endif endif endif ...

OBJECT-TYPE

This variable indicates the value of the threshold. To correctly display or interpret this variable's value, you must also know entSensorType, entSensorScale, and entSensorPrecision. However, you can directly compare entSensorValue with the threshold values given in entSensorThresholdTable without any semantic knowledge.

OBJECT-TYPE

This variable indicates the result of the most recent evaluation of the threshold. If the threshold condition is true, entSensorThresholdEvaluation is true(1). If the threshold condition is false, entSensorThresholdEvaluation is false(2). Thresholds are evaluated at the rate indicated by entSensorValueUpdateRate.

OBJECT-TYPE

This variable controls generation of entSensorThresholdNotification for this threshold. When this variable is true(1), generation of entSensorThresholdNotification is enabled. When this variable is false(2), generation of entSensorThresholdNotification is disabled. This variable only controls generation of entSensorThresholdNotification.

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY