Reference Guide

Property Description
Possible values are:
• 0 = Unknown
• 1 = Other
• 2 = OK
• 3 = Degraded
• 4 = Stressed - Indicates that the element is functioning, but
needs attention. Examples of "Stressed" states are
overload, overheated, and so on.
• 5 = Predictive Failure - Indicates that an element is
functioning nominally but predicting a failure in the near
future.
• 6 = Error
• 7 = Non-Recoverable Error
• 8 = Starting
• 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
194