Key |
CreationClassName
|
string
|
|
CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. |
Name
|
string
|
|
The Name property uniquely identifies the ServiceAccessPoint and provides an indication of the function that is managed. This function is described in more detail in the Description property of the object. |
SystemCreationClassName
|
string
|
|
The CreationClassName of the scoping System. |
SystemName
|
string
|
|
The Name of the scoping System. |
Read Only |
AuthenticationMechanismsSupported
|
uint16
|
Unknown | 0 |
Other | 1 |
None | 2 |
Basic | 3 |
Digest | 4 |
|
Enumerated array describing the types of authentication supported by the ObjectManager, using the encoding/protocol. Specified in the property, CommunicationMechanism. The defined values represent the authentication defined in the DMTF document, Specification for CIM Operations over HTTP. |
CIMValidated
|
boolean
|
|
Describeswhether the CIM Server is strictly validating (validates the XML document against the DTD) or not (loosely validating). |
CommunicationMechanism
|
uint16
|
|
The only valid CommunicationMechanism for this subclass is CIM-XML. |
ElementName
|
string
|
|
A user-friendly name for the object. This property allows each instance to define a user-friendly name in addition to its key properties, identity data, and description information.The Name property of ManagedSystemElement is also defined as a user-friendly name. But, it is often subclassed to be a Key. The same property cannot convey both identity and a user-friendly name, without inconsistencies. Where Name exists and is not a Key (such as for instances of LogicalDevice), the same information can be present in both the Name and ElementName properties. |
FunctionalProfilesSupported
|
uint16
|
Unknown | 0 |
Other | 1 |
Basic Read | 2 |
Basic Write | 3 |
Schema Manipulation | 4 |
Instance Manipulation | 5 |
Association Traversal | 6 |
Query Execution | 7 |
Qualifier Declaration | 8 |
Indications | 9 |
|
Enumerated array describing the types of operations supported by the ObjectManager, using this encoding/protocol. The enumeration is based on the Functional Profiles defined for conformance in the DMTF document, Specification for CIM Operations over HTTP. |
MultipleOperationsSupported
|
boolean
|
|
Boolean indicating whether the ObjectManager supports multiple operation requests (TRUE) or only simple requests (FALSE). |
OperationalStatus
|
uint16
|
Unknown | 0 |
Other | 1 |
OK | 2 |
Degraded | 3 |
Stressed | 4 |
Predictive Failure | 5 |
Error | 6 |
Non-Recoverable Error | 7 |
Starting | 8 |
Stopping | 9 |
Stopped | 10 |
In Service | 11 |
No Contact | 12 |
Lost Communication | 13 |
Aborted | 14 |
Dormant | 15 |
Supporting Entity in Error | 16 |
Completed | 17 |
Power Mode | 18 |
DMTF Reserved | .. |
Vendor Reserved | 0x8000.. |
|
Indicates the current statuses of the element. Various operational statuses are defined. Many of the enumeration's values are self-explanatory. However, a few are not and are described here in more detail."Stressed"indicates that the element is functioning, but needs attention. Examples of"Stressed"states are overload, overheated, and so on."Predictive Failure"indicates that an element is functioningnominally but predicting a failure in the near future."In Service"describes an element being configured, maintained, cleaned, or otherwise administered."No Contact"indicates that the monitoring system has knowledge of this element, but has never been able to establish communications with it."Lost Communication"indicates that the ManagedSystem Element is known to exist and has been contacted successfully in the past, but is currently unreachable."Stopped"and"Aborted"are similar, although the former implies a clean and orderly stop, while the latter implies an abrupt stop where the state and configuration of the element might need to be updated."Dormant"indicates that the element is inactive or quiesced."Supporting Entity in Error"indicates that this element might 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."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)."Power Mode"indicates that the element has additional power model information contained in the Associated PowerManagementService association.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. |
Version
|
string
|
|
Enumeration describing the CIM-XML protocol version supported by the ObjectManager. |
Read Write |