Reference Guide

Table 31. NumericSensor (continued)
Property Description Supported
Operating
System(s)
● 9 = Stopping
● 10 = Stopped—Implies a clean and orderly stop
● 11 = In Service—Describes an element being configured, maintained, cleaned, or
otherwise administered.
● 12 = No Contact—Indicates that the monitoring system has knowledge of this
element, but has never been able to establish communications with it.
● 13 = Lost Communication—Indicates that the ManagedSystem Element is
known to exist and has been contacted successfully in the past, but is currently
unreachable.
● 14 = Aborted—Implies an abrupt stop where the state and configuration of the
element may need to be updated.
● 15 = Dormant - Indicates that the element is inactive or quiesced.
● 16 = Supporting Entity in Error—Indicates that this element may be OK but that
another element, on which it is dependent, is in error. An example is a network
service or endpoint that cannot function due to lower-layer networking
problems.
● 17 = Completed—Indicates that the element has completed its operation. This
value should be combined with either OK, Error, or Degraded so that a client
can tell if the complete operation Completed with OK (passed), Completed with
Error (failed), or Completed with Degraded (the operation finished, but it did
not complete OK or did not report an error).
● 18 = Power Mode—Indicates that the element has additional power model
information contained in the Associated PowerManagementService association.
● .. = DMTF Reserved
● 0x8000.. = Vendor Reserved
OperationalStatus replaces the Status property on ManagedSystemElement to
provide a consistent approach to enumerations, to address implementation needs
for an array property, and to provide a migration path from today's environment to
the future. This change was not made earlier because it required the deprecated
qualifier. Due to the widespread use of the existing Status property in management
applications, it is strongly recommended that providers or instrumentation provide
both the Status and OperationalStatus properties. Further, the first value of
OperationalStatus should contain the primary status for the element. When
instrumented, Status (because it is single-valued) should also provide the primary
status of the element.
PossibleStates
Enumerates the string outputs of the Sensor.
Example 1 - A Switch Sensor may output the states On, or Off. Another
implementation of the Switch may output the states Open, and Close.
Example 2 - Is a NumericSensor supporting thresholds. This Sensor can report the
states like Normal, Upper Non-Critical, Lower Non-Critical, and so on. A
NumericSensor that does not publish readings and thresholds, but stores this data
internally, can still report its states.
Windows, Linux
RateUnits
Specifies if the units returned by this Sensor are rate units. All the values returned
by this Sensor are represented in the units obtained by (BaseUnits * 10 raised to
the power of the UnitModifier). This is true unless this property (RateUnits) has a
value different than None. For example, if BaseUnits is Volts and the UnitModifier
is -6, then the units of the values returned are MicroVolts. But, if the RateUnits
property is set to a value other than None, then the units are further qualified as
rate units. In the above example, if RateUnits is set to Per Second, then the values
returned by the Sensor are in MicroVolts/Second. The units apply to all numeric
properties of the Sensor, unless explicitly overridden by the Units qualifier. Any
implementation of CurrentReading should be qualified with either a Counter or a
Gauge qualifier, depending on the characteristics of the sensor being modeled.
Windows, Linux
126 Dell Command | Monitor 10.4 classes and properties