cc/td/doc/product/wanbu/mgx8850/20x
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

SENSOR MIB File

SENSOR MIB File

This chapter describes the individual MIB objects that comprise the PXM45-specific MIB files. The SENSOR MIB resides in the CISCO-ENTITY-SENSOR-MIB.my file. It is used to monitor the values of sensors in the ENTITY MIB (refer to RFC 2037) entPhysicalTable.

Contents of this chapter include:

SENSOR MIB Textual Conventions

The names of the textual conventions are specified in the object syntax.

The MIB objects are listed in Table 5-1.


Note   Textual Conventions do not have any object identifiers.


Table 5-1: SENSOR MIB Textual Conventions MIB Objects
Name Syntax Description Default Value

SensorDataType

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)}

Describes the valid values that are used for SensorDataType.

Status: current

The following are the values for SensorDataType:

none

Sensor Measurement Valid Value

other(1)

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

SensorDataScale

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)}

Displays the International System of Units prefixes.

Status: current

The following lists the prefix and the value:

none

Prefix Value

yocto (1)

10-24

zepto (2)

10-21

atto (3)

10-18

femto (4)

10-15

pico (5)

10-12

nano (6)

10-9

micro (7)

10-6

milli (8)

10-3

Units (9)

100

kilo (10)

103

mega (11)

106

giga (12)

109

tera (13)

1012

exa (14)

1015

peta (15)

1018

zetta (16)

1021

yotta (17)

1024

SensorPrecision

Integer (-8..9)

Determines the number of decimal places in the fractional part of a SensorValue fixed-point number. When the range is from -8 to -1, SensorPrecision is the number of accurate digits in a SensorValue fixed-point number. SensorPrecision is 0 for non-fixed-point numbers.

Agents must choose a value for SensorPrecision so that the precision and accuracy of a SensorValue is correctly indicated.

For example, a temperature sensor that measures from 0° to 100° C in 0.1° increments, ±0.05°, would have a SensorPrecision of 1, a SensorDataScale of Units (0), and a SensorValue ranging from 0 to 1000. The SensorValue is interpreted as (°C * 10). If that temperature sensor's precision were 0.1° but the accuracy is only ±0.5°, the SensorPrecision is set to 0. The SensorValue is 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, can 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 is always 0.

Status: current

none

SensorValue

Integer (-1000000000..1000000000)

Measures AC volts, DC volts, amperes, watts, hertz, celsius, and cmm. SensorValue 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 percent RH, 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 and entPhysicalVendorType to learn about the sensor type. For OID1 values assigned to entPhysicalVendorType, see Table 1-5.

Status: current

none

SensorStatus

Integer {ok (1), unavailable (2), nonoperational (3)}

Indicates the operational status of the sensor.

Status: current

The following are the values for SensorStatus:

none

Sensor Measurement Valid Value

ok (1)

The agent can read the sensor value.

unavailable (2)

The agent presently cannot report the sensor value.

nonoperational (3)

The sensor can have a hard failure (disconnected wire), or a soft failure such as out-of-range, jittery, or fluctuating readings.

SensorValue
UpdateRate

Integer (0..999999999)

Indicates the interval in seconds between updates to the sensor value.

A value of zero indicates one or more of the following:

  • Sensor value is updated on demand (when polled by the agent for a get-request).

  • Sensor value changes (event-driven).

Agent does not know the rate.

Status: current

none

SensorThreshold
Severity

Integer {other (1), minor (10), major (20)}

Indicates the sensor threshold severity.

Status: current

The following are the values for SensorThresholdSeverity:

none

Sensor Measurement Valid Value

other (1)

Indicates a severity other than those listed below.

minor (10)

Minor problem threshold.

major (20)

Major problem threshold.

SensorThresholdRelation

Integer {lessThan (1), lessOrEqual (2), greaterThan (3), greaterOrEqual (4), equalTo (5),
notEqualTo (6)}

Displays the sensor threshold relational operator types.

Status: current

The following are the values for SensorThresholdRelation:

none

Sensor Threshold Valid Value

lessThan(1)

Sensor value is less than the threshold value.

lessOrEqual(2)

Sensor value is less than or equal to the threshold value.

greaterThan(3)

Sensor value is greater than the threshold value.

greaterOrEqual(4)

Sensor value is greater than or equal to the threshold value.

equalTo(5)

Sensor value is equal to the threshold value.

notEqualTo(6)

Sensor value is not equal to the threshold value.

1OID is defined as the object identifier.

SENSOR MIB Objects

The object identifier for each MIB object is listed in Table 5-2.


Table 5-2: SENSOR MIB Object Identifiers
Name Object Identifier

entSensorValueTable

::= { entSensorValues 1 }

entSensorValueEntry

::= { entSensorValueTable 1 }

entSensorType

::= { entSensorValueEntry 1 }

entSensorScale

::= { entSensorValueEntry 2 }

entSensorPrecision

::= { entSensorValueEntry 3 }

entSensorValue

::= { entSensorValueEntry 4 }

entSensorStatus

::= { entSensorValueEntry 5 }

entSensorValueTimeStamp

::= { entSensorValueEntry 6 }

entSensorValueUpdateRate

::= { entSensorValueEntry 7 }

The MIB objects are described in Table 5-3.


Table 5-3: SENSOR MIB Objects Table
Name Syntax Description Default Value

entSensorValueTable

Sequence of entSensorValueEntry

Lists the type, scale, and present value of a sensor listed in the ENTITY MIB entPhysicalTable.

Max-Access: not-accessible

Status: current

none

entSensorValueEntry

entSensorValueEntry

Describes the present reading of a sensor, the measurement units and scale, and the sensor operational status.

Max-Access: not-accessible

Status: current

The index contains entPhysicalIndex.

none

entSensorType

SensorDataType

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

Max-Access: read-only

Status: current

none

entSensorScale

SensorDataScale

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

Max-Access: read-only

Status: current

none

entSensorPrecision

SensorPrecision

Indicates the number of decimal places of precision in fixed-point sensor values reported by entSensorValue.

This object 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 object is set by the agent at start-up and the value does not change during operation.

Max-Access: read-only

Status: current

none

entSensorValue

SensorValue

Reports the most recent measurement seen by the sensor.

To correctly display or interpret this object'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.

Max-Access: read-only

Status: current

none

entSensorStatus

SensorStatus

Indicates the present operational status of the sensor.

Max-Access: read-only

Status: current

none

entSensorValueTime
Stamp

TimeStamp

Indicates the age of the value reported by entSensorValue.

Max-Access: read-only

Status: current

none

entSensorValueUpdateRate

SensorValueUpdateRate

Indicates the rate that the agent updates entSensorValue.

Units: seconds

Max-Access: read-only

Status: current

none

Ent Sensor Threshold Table

The object identifier for each MIB object is listed in Table 5-4.


Table 5-4: Ent Sensor Threshold Table Object Identifiers
Name Object Identifier

entSensorThresholdTable

::= { entSensorThresholds 1 }

entSensorThresholdEntry

::= { entSensorThresholdTable 1 }

entSensorThresholdIndex

::= { entSensorThresholdEntry 1 }

entSensorThresholdSeverity

::= { entSensorThresholdEntry 2 }

entSensorThresholdRelation

::= { entSensorThresholdEntry 3 }

entSensorThresholdValue

::= { entSensorThresholdEntry 4 }

entSensorThresholdEvaluation

::= { entSensorThresholdEntry 5 }

entSensorThresholdNotificationEnable

::= { entSensorThresholdEntry 6 }

The MIB objects are described in Table 5-5.


Table 5-5: Ent Sensor Threshold Table MIB Objects
Name Syntax Description Default Value

entSensorThreshold
Table

Sequence of entSensorThresholdEntry

Lists the threshold severity, relation, and comparison value for a sensor listed in the ENTITY MIB entPhysicalTable.

Max-Access: not-accessible

Status: current

none

entSensorThreshold
Entry

entSensorThresholdEntry

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 alarm, or Expression-MIB.

Entries are created by the agent at system startup and FRU insertion. Entries are deleted by the agent at FRU removal.

Max-Access: not-accessible

Status: current

The following are the indexes:

  • entPhysicalIndex

  • entSensorThresholdIndex

none

entSensorThreshold
Index

Integer32 (1..99999999)

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

Max-Access: not-accessible

Status: current

none

entSensorThreshold
Severity

SensorThresholdSeverity

Indicates the severity of the sensor threshold.

Max-Access: read-only

Status: current

none

entSensorThreshold
Relation

SensorThresholdRelation

Indicates the relation between sensor value (entSensorValue) and threshold value (entSensorThresholdValue), which are 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 the following:

...
if (entSensorStatus == ok) then
    if (evaluate(entSensorValue, entSensorThresholdRelation, entSensorThresholdValue)) then
      if (entSensorThresholdNotificationEnable == true)) then raise_alarm(entSensorThresholdAlarmOID);
endif
    endif
      endif
...

Max-Access: read-only

Status: current

none

entSensorThreshold
Value

SensorValue

Indicates the value of the threshold.

To correctly display or interpret this object'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.

Max-Access: read-only

Status: current

none

entSensorThreshold
Evaluation

TruthValue

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.

Max-Access: read-only

Status: current

none

entSensorThreshold
NotificationEnable

TruthValue

Controls the generation of entSensorThresholdNotification for this threshold.

When this object is true (1), the generation of entSensorThresholdNotification is enabled. When this object is false(2), the generation of entSensorThresholdNotification is disabled.

This object controls only the generation of entSensorThresholdNotification.

Max-Access: read-write

Status: current

none

SENSOR MIB Notification

According to RFC 2578, a notification is used to describe unsolicited transmissions of management information. NOTIFICATION-TYPE conveys the syntax and semantics of a notification.

The object identifier for the MIB object is listed in Table 5-6.


Table 5-6: SENSOR MIB Notification Object Identifier
Name Object Identifier

entSensorThresholdNotification

::= { entitySensorMIBNotifications 1 }

The MIB object is listed in Table 5-7.


Table 5-7: SENSOR MIB Notification MIB Object
Name Objects Description Default Value

entSensorThreshold
Notification

entSensorThresholdValue, entSensorValue

Generates a notification each time the sensor value crosses the threshold listed in entSensorThresholdTable. The agent implementation facilitates a prompt evaluation of threshold and generation.

Status: current

none

SENSOR MIB Conformance Information

The object identifier is listed in Table 5-8 for conformance.


Table 5-8: SENSOR MIB Conformance Group
Name Object Identifier

entitySensorMIBComplianceV01

::= { entitySensorMIBCompliances 1 }

Table 5-9 lists one object for conformance.


Table 5-9: SENSOR MIB Conformance Object
Name Module Description Default Value

entitySensorMIB
ComplianceV01

PXM45

Lists sensors in the entPhysicalTable.entitySensorMIBComplianceV01 object must implement this group as an ENTITY MIB.

Status: current

The mandatory groups are

  • entitySensorValueGroup

  • entitySensorThresholdGroup

  • entitySensorThresholdNotificationGroup

none

SENSOR MIB Units of Conformance

The object identifier is listed in Table 5-10 for units of conformance.


Table 5-10: SENSOR MIB Units of Conformance
Name Object Identifier

entitySensorValueGroup

::= { entitySensorMIBGroups 1 }

entitySensorThresholdGroup

::= { entitySensorMIBGroups 2 }

entitySensorThresholdNotificationGroup

::= { entitySensorMIBGroups 3 }

Table 5-11 lists the MIB objects for units of conformance.


Table 5-11: SENSOR MIB Units of Conformance Objects
Name Objects Description Default Value

entitySensorValue
Group

entSensorType, entSensorScale, entSensorPrecision, entSensorValue, entSensorStatus, entSensorValueTimeStamp, entSensorValueUpdateRate

Describes and monitors the values of the ENTITY MIB entPhysicalTable entries of sensors.

Status: current

none

entitySensorThresholdGroup

entSensorThresholdSeverity, entSensorThresholdRelation, entSensorThresholdValue, entSensorThresholdEvaluation, entSensorThresholdNotificationEnable

Describes and monitors the thresholds for sensors.

Stauts: current

none

entitySensorThresholdNotificationGroup

none

Monitors the sensor threshold activity for this collection of notifications.


Note   This notification is commented out because SMIC does not know about the Notification Group.

Notifications: entSensorThresholdNotification

Status: current

none


hometocprevnextglossaryfeedbacksearchhelp
Posted: Fri Sep 15 12:01:45 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.