Reference Guide

Table 31. NumericSensor (continued)
Property Description Supported
Operating
System(s)
● 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.
Possible values are:
● 0 = None
● 1 = Per MicroSecond
● 2 = Per MilliSecond
● 3 = Per Second
● 4 = Per Minute
● 5 = Per Hour
● 6 = Per Day
● 7 = Per Week
● 8 = Per Month
● 9 = Per Year
Windows, Linux
RequestedState An integer enumeration that indicates the last requested or desired state for the
element, irrespective of the mechanism through which it was requested. The actual
state of the element is represented by EnabledState. This property is provided to
compare the last requested and current enabled or disabled states. Note that when
EnabledState is set to 5 (Not Applicable), then this property has no meaning.
Refer to the EnabledState property description for explanations of the values in the
RequestedState enumeration.
NOTE: The value No Change (5) has been deprecated instead of indicating
the last requested state is Unknown (0). If the last requested or desired state
is unknown, RequestedState should have the value Unknown (0), but may
have the value No Change (5). Offline (6) indicates that the element has
been requested to transition to the Enabled but Offline EnabledState.
There are two new values in RequestedState that build on the statuses of
EnabledState. These are Reboot (10) and Reset (11).
Windows, Linux
Dell Command | Monitor 10.5 classes and properties 119