EZ5 MIB Catalog

CISCO-ENTITY-SENSOR-MIB

2020-09-22

The CISCO-ENTITY-SENSOR-MIB is used to monitor the values of sensors in the Entity-MIB (RFC 2037) entPhysicalTable.

Download CISCO-ENTITY-SENSOR-MIB.txt Open CISCO-ENTITY-SENSOR-MIB.txt in a new tab

TABLES (2) · TRAPS (1)

Tables (2)

NameOID
entSensorValueTable1.3.6.1.4.1.9.9.91.1.1.1
entSensorThresholdTable1.3.6.1.4.1.9.9.91.1.2.1

Traps (1)

NameOID
entSensorThresholdNotification1.3.6.1.4.1.9.9.91.2.0.1

END OF TOC

Table details

entSensorValueTable

1.3.6.1.4.1.9.9.91.1.1.1

Index: entPhysicalIndex

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

from ENTITY-MIB

entPhysicalIndex

PhysicalIndexAn arbitrary value that uniquely identifies the physical entity. The value should be a small positive integer. Index values for different physical entities are not necessarily contiguous. (1..2147483647) · Integer32 · hint d

The index for this entry.

entSensorType

1.3.6.1.4.1.9.9.91.1.1.1.1.1

SensorDataType1 = other2 = unknown3 = voltsAC4 = voltsDC5 = amperes6 = watts7 = hertz8 = celsius9 = percentRH10 = rpm11 = cmm12 = truthvalue13 = specialEnumsensor 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 · Integer32

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.

entSensorScale

1.3.6.1.4.1.9.9.91.1.1.1.1.2

SensorDataScale1 = yocto2 = zepto3 = atto4 = femto5 = pico6 = nano7 = micro8 = milli9 = units10 = kilo11 = mega12 = giga13 = tera14 = exa15 = peta16 = zetta17 = yottaInternational System of Units (SI) prefixes. · Integer32

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.

entSensorPrecision

1.3.6.1.4.1.9.9.91.1.1.1.1.3

SensorPrecisionWhen 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. (-8..9) · Integer32

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.

entSensorValue

1.3.6.1.4.1.9.9.91.1.1.1.1.4

SensorValueFor 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. (-1000000000..1000000000) · Integer32

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.

entSensorStatus

1.3.6.1.4.1.9.9.91.1.1.1.1.5

SensorStatus1 = ok2 = unavailable3 = nonoperationalIndicates 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. · Integer32

This variable indicates the present operational status of the sensor.

entSensorValueTimeStamp

1.3.6.1.4.1.9.9.91.1.1.1.1.6

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

This variable indicates the age of the value reported by entSensorValue

entSensorValueUpdateRate

1.3.6.1.4.1.9.9.91.1.1.1.1.7

SensorValueUpdateRateIndicates 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 (0..999999999) · Integer32 · seconds

This variable indicates the rate that the agent updates entSensorValue.

entSensorMeasuredEntity

1.3.6.1.4.1.9.9.91.1.1.1.1.8

INTEGER (0..2147483647) · Integer32

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.

entSensorThresholdTable

1.3.6.1.4.1.9.9.91.1.2.1

Index: entPhysicalIndex · entSensorThresholdIndex

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

from ENTITY-MIB

entPhysicalIndex

PhysicalIndexAn arbitrary value that uniquely identifies the physical entity. The value should be a small positive integer. Index values for different physical entities are not necessarily contiguous. (1..2147483647) · Integer32 · hint d

The index for this entry.

entSensorThresholdIndex

1.3.6.1.4.1.9.9.91.1.2.1.1.1

Integer32 (1..99999999)

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

entSensorThresholdSeverity

1.3.6.1.4.1.9.9.91.1.2.1.1.2

SensorThresholdSeverity1 = other10 = minor20 = major30 = criticalsensor 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. · Integer32

This variable indicates the severity of this threshold.

entSensorThresholdRelation

1.3.6.1.4.1.9.9.91.1.2.1.1.3

SensorThresholdRelation1 = lessThan2 = lessOrEqual3 = greaterThan4 = greaterOrEqual5 = equalTo6 = notEqualTosensor 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 · Integer32

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 ...

entSensorThresholdValue

1.3.6.1.4.1.9.9.91.1.2.1.1.4

SensorValueFor 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. (-1000000000..1000000000) · Integer32

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.

entSensorThresholdEvaluation

1.3.6.1.4.1.9.9.91.1.2.1.1.5

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

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.

entSensorThresholdNotificationEnable

1.3.6.1.4.1.9.9.91.1.2.1.1.6

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

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.

Trap details

entSensorThresholdNotification

1.3.6.1.4.1.9.9.91.2.0.1

The sensor value crossed the threshold listed in entSensorThresholdTable. This notification is generated once each time the sensor value crosses the threshold. The agent implementation guarantees prompt, timely evaluation of threshold and generation of this notification.

entSensorThresholdValue

1.3.6.1.4.1.9.9.91.1.2.1.1.4

SensorValueFor 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. (-1000000000..1000000000) · Integer32

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.

entSensorValue

1.3.6.1.4.1.9.9.91.1.1.1.1.4

SensorValueFor 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. (-1000000000..1000000000) · Integer32

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.

↑ To TOC