smilint output for ./ENTITY-SENSOR-MIB
Message Severities |
Severity | Count |
warning | 2 |
Message Types |
Type | Count |
type-without-format (warning) | 2 |
Messages:
ENTITY-SENSOR-MIB
1: -- extracted from rfc3433.txt
2: -- at Mon Dec 23 06:11:31 2002
156:
157: EntitySensorPrecision ::= TEXTUAL-CONVENTION
157: warning -
warning: type `EntitySensorPrecision' has no format specification
158: STATUS current
159: DESCRIPTION
160: "An object using this data type represents a sensor
161: precision range.
162:
163: An object of this type SHOULD be defined together with
164: objects of type EntitySensorDataType and
165: EntitySensorDataScale. Together, associated objects of
166: these three types are used to identify the semantics of an
167: object of type EntitySensorValue.
168:
169: If an object of this type contains a value in the range 1 to
170: 9, it represents the number of decimal places in the
171: fractional part of an associated EntitySensorValue fixed-
172: point number.
173:
174: If an object of this type contains a value in the range -8
175: to -1, it represents the number of accurate digits in the
176: associated EntitySensorValue fixed-point number.
177:
178: The value zero indicates the associated EntitySensorValue
179: object is not a fixed-point number.
180:
181: Agent implementors must choose a value for the associated
182: EntitySensorPrecision object so that the precision and
183: accuracy of the associated EntitySensorValue object is
184: correctly indicated.
185:
186: For example, a physical entity representing a temperature
187: sensor that can measure 0 degrees to 100 degrees C in 0.1
188: degree increments, +/- 0.05 degrees, would have an
189: EntitySensorPrecision value of '1', an EntitySensorDataScale
190: value of 'units(9)', and an EntitySensorValue ranging from
191: '0' to '1000'. The EntitySensorValue would be interpreted
192: as 'degrees C * 10'."
193: SYNTAX Integer32 (-8..9)
194:
195: EntitySensorValue ::= TEXTUAL-CONVENTION
195: warning -
warning: type `EntitySensorValue' has no format specification
196: STATUS current
197: DESCRIPTION
198: "An object using this data type represents an Entity Sensor
199: value.
200: An object of this type SHOULD be defined together with
201: objects of type EntitySensorDataType, EntitySensorDataScale
202: and EntitySensorPrecision. Together, associated objects of
203: those three types are used to identify the semantics of an
204: object of this data type.
205:
206: The semantics of an object using this data type are
207: determined by the value of the associated
208: EntitySensorDataType object.
209:
210: If the associated EntitySensorDataType object is equal to
211: 'voltsAC(3)', 'voltsDC(4)', 'amperes(5)', 'watts(6),
212: 'hertz(7)', 'celsius(8)', or 'cmm(11)', then an object of
213: this type MUST contain a fixed point number ranging from
214: -999,999,999 to +999,999,999. The value -1000000000
215: indicates an underflow error. The value +1000000000
216: indicates an overflow error. The EntitySensorPrecision
217: indicates how many fractional digits are represented in the
218: associated EntitySensorValue object.
219:
220: If the associated EntitySensorDataType object is equal to
221: 'percentRH(9)', then an object of this type MUST contain a
222: number ranging from 0 to 100.
223:
224: If the associated EntitySensorDataType object is equal to
225: 'rpm(10)', then an object of this type MUST contain a number
226: ranging from -999,999,999 to +999,999,999.
227:
228: If the associated EntitySensorDataType object is equal to
229: 'truthvalue(12)', then an object of this type MUST contain
230: either the value 'true(1)' or the value 'false(2)'.
231: If the associated EntitySensorDataType object is equal to
232: 'other(1)' or unknown(2)', then an object of this type MUST
233: contain a number ranging from -1000000000 to 1000000000."
234: SYNTAX Integer32 (-1000000000..1000000000)