SensorDataType |
|
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
dBm(14): dB relative to 1mW of power
dB(15): decibel |
TEXTUAL-CONVENTION |
|
|
|
|
INTEGER |
other(1), unknown(2), voltsAC(3), voltsDC(4), amperes(5), watts(6), hertz(7), celsius(8), percentRH(9), rpm(10), cmm(11), truthvalue(12), specialEnum(13), dBm(14), dB(15) |
|
SensorDataScale |
|
International System of Units (SI) prefixes. |
TEXTUAL-CONVENTION |
|
|
|
|
INTEGER |
yocto(1), zepto(2), atto(3), femto(4), pico(5), nano(6), micro(7), milli(8), units(9), kilo(10), mega(11), giga(12), tera(13), exa(14), peta(15), zetta(16), yotta(17) |
|
SensorValue |
|
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 |
|
|
|
|
INTEGER |
-1000000000..1000000000 |
|
EntSensorThresholdEntry |
|
SEQUENCE |
|
|
|
|
entSensorThresholdIndex |
Integer32 |
|
|
entSensorThresholdSeverity |
SensorThresholdSeverity |
|
|
entSensorThresholdRelation |
SensorThresholdRelation |
|
|
entSensorThresholdValue |
SensorValue |
|
|
entSensorThresholdEvaluation |
TruthValue |
|
|
entSensorThresholdNotificationEnable |
TruthValue |
|
entSensorValueEntry |
1.3.6.1.4.1.9.9.91.1.1.1.1 |
An entSensorValueTable entry describes the
present reading of a sensor, the measurement units
and scale, and sensor operational status. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
EntSensorValueEntry |
|
|
entSensorThresholdEntry |
1.3.6.1.4.1.9.9.91.1.2.1.1 |
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. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
EntSensorThresholdEntry |
|
|