netttcim.dll.mui Transition Technology WMI Objects 27f447b21e0d07744d09cd0b5f7139c3

File info

File name: netttcim.dll.mui
Size: 174080 byte
MD5: 27f447b21e0d07744d09cd0b5f7139c3
SHA1: 739e9ff3eedd03b773b4b3f1198eaf076becf80a
SHA256: d854de0df205fddc58a405aaeae9d9611217bede26309b75c2f8b8e24c1ea7c6
Operating systems: Windows 10
Extension: MUI

Translations messages and strings

If an error occurred or the following message in French language and you cannot find a solution, than check answer in English. Table below helps to know how correctly this phrase sounds in English.

id French English
1InstanceID is an optional property that may be used to opaquely and uniquely identify an instance of this class within the scope of the instantiating Namespace. Various subclasses of this class may override this property to make it required, or a key. Such subclasses may also modify the preferred algorithms for ensuring uniqueness that are defined below.
To ensure uniqueness within the NameSpace, the value of InstanceID should be constructed using the following "preferred" algorithm:
:
Where and are separated by a colon (:), and where must include a copyrighted, trademarked, or otherwise unique name that is owned by the business entity that is creating or defining the InstanceID or that is a registered ID assigned to the business entity by a recognized global authority. (This requirement is similar to the _ structure of Schema class names.) In addition, to ensure uniqueness, must not contain a colon (:). When using this algorithm, the first colon to appear in InstanceID must appear between and .
is chosen by the business entity and should not be reused to identify different underlying (real-world) elements. If not null and the above "preferred" algorithm is not used, the defining entity must assure that the resulting InstanceID is not reused across any InstanceIDs produced by this or other providers for the NameSpace of this instance.
If not set to null for DMTF-defined instances, the "preferred" algorithm must be used with the set to CIM.
InstanceID is an optional property that may be used to opaquely and uniquely identify an instance of this class within the scope of the instantiating Namespace. Various subclasses of this class may override this property to make it required, or a key. Such subclasses may also modify the preferred algorithms for ensuring uniqueness that are defined below.
To ensure uniqueness within the NameSpace, the value of InstanceID should be constructed using the following "preferred" algorithm:
:
Where and are separated by a colon (:), and where must include a copyrighted, trademarked, or otherwise unique name that is owned by the business entity that is creating or defining the InstanceID or that is a registered ID assigned to the business entity by a recognized global authority. (This requirement is similar to the _ structure of Schema class names.) In addition, to ensure uniqueness, must not contain a colon (:). When using this algorithm, the first colon to appear in InstanceID must appear between and .
is chosen by the business entity and should not be reused to identify different underlying (real-world) elements. If not null and the above "preferred" algorithm is not used, the defining entity must assure that the resulting InstanceID is not reused across any InstanceIDs produced by this or other providers for the NameSpace of this instance.
If not set to null for DMTF-defined instances, the "preferred" algorithm must be used with the set to CIM.
2The Caption property is a short textual description (one- line string) of the object. The Caption property is a short textual description (one- line string) of the object.
3The Description property provides a textual description of the object. The Description property provides a textual description of the object.
4A 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.
Note that the Name property of ManagedSystemElement is also defined as a user-friendly name. But, it is often subclassed to be a Key. It is not reasonable that the same property can 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. Note that if there is an associated instance of CIM_EnabledLogicalElementCapabilities, restrictions on this properties may exist as defined in ElementNameMask and MaxElementNameLen properties defined in that class.
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.
Note that the Name property of ManagedSystemElement is also defined as a user-friendly name. But, it is often subclassed to be a Key. It is not reasonable that the same property can 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. Note that if there is an associated instance of CIM_EnabledLogicalElementCapabilities, restrictions on this properties may exist as defined in ElementNameMask and MaxElementNameLen properties defined in that class.
52.19.0 2.19.0
6ManagedElement is an abstract class that provides a common superclass (or top of the inheritance tree) for the non-association classes in the CIM Schema. ManagedElement is an abstract class that provides a common superclass (or top of the inheritance tree) for the non-association classes in the CIM Schema.
7Within the scope of the instantiating Namespace, InstanceID opaquely and uniquely identifies an instance of this class. To ensure uniqueness within the NameSpace, the value of InstanceID should be constructed using the following "preferred" algorithm:
:
Where and are separated by a colon (:), and where must include a copyrighted, trademarked, or otherwise unique name that is owned by the business entity that is creating or defining the InstanceID or that is a registered ID assigned to the business entity by a recognized global authority. (This requirement is similar to the _ structure of Schema class names.) In addition, to ensure uniqueness, must not contain a colon (:). When using this algorithm, the first colon to appear in InstanceID must appear between and .
is chosen by the business entity and should not be reused to identify different underlying (real-world) elements. If the above "preferred" algorithm is not used, the defining entity must assure that the resulting InstanceID is not reused across any InstanceIDs produced by this or other providers for the NameSpace of this instance.
For DMTF-defined instances, the "preferred" algorithm must be used with the set to CIM.
Within the scope of the instantiating Namespace, InstanceID opaquely and uniquely identifies an instance of this class. To ensure uniqueness within the NameSpace, the value of InstanceID should be constructed using the following "preferred" algorithm:
:
Where and are separated by a colon (:), and where must include a copyrighted, trademarked, or otherwise unique name that is owned by the business entity that is creating or defining the InstanceID or that is a registered ID assigned to the business entity by a recognized global authority. (This requirement is similar to the _ structure of Schema class names.) In addition, to ensure uniqueness, must not contain a colon (:). When using this algorithm, the first colon to appear in InstanceID must appear between and .
is chosen by the business entity and should not be reused to identify different underlying (real-world) elements. If the above "preferred" algorithm is not used, the defining entity must assure that the resulting InstanceID is not reused across any InstanceIDs produced by this or other providers for the NameSpace of this instance.
For DMTF-defined instances, the "preferred" algorithm must be used with the set to CIM.
8The user-friendly name for this instance of SettingData. In addition, the user-friendly name can be used as an index property for a search or query. (Note: The name does not have to be unique within a namespace.) The user-friendly name for this instance of SettingData. In addition, the user-friendly name can be used as an index property for a search or query. (Note: The name does not have to be unique within a namespace.)
9CIM_SettingData is used to represent configuration and and operational parameters for CIM_ManagedElement instances. There are a number of different uses of CIM_SettingData supported in the model today. Additional uses may be defined in the future.
Instances of CIM_SettingData may represent Aspects of a CIM_ManagedElement instance. This is modeled using the CIM_SettingsDefineState association. CIM_SettingData may be used to define capabilities when associated to an instance of CIM_Capabilities through the CIM_SettingsDefineCapabilities association.
Instances of CIM_SettingData may represent different types of configurations for a CIM_ManagedElement, including persistent configurations, in progress configuration changes, or requested configurations. The CIM_ElementSettingData association is used to model the relationship between a CIM_SettingData instance and the CIM_ManagedElement for which it is a configuration.
When an instance of CIM_SettingData represents a configuration, the current operational values for the parameters of the element are reflected by properties in the Element itself or by properties in its associations. These properties do not have to be the same values that are present in the SettingData object. For example, a modem might have a SettingData baud rate of 56Kb/sec but be operating at 19.2Kb/sec.
Note: The CIM_SettingData class is very similar to CIM_Setting, yet both classes are present in the model because many implementations have successfully used CIM_Setting. However, issues have arisen that could not be resolved without defining a new class. Therefore, until a new major release occurs, both classes will exist in the model. Refer to the Core White Paper for additional information. SettingData instances can be aggregated together into higher- level SettingData objects using ConcreteComponent associations.
CIM_SettingData is used to represent configuration and and operational parameters for CIM_ManagedElement instances. There are a number of different uses of CIM_SettingData supported in the model today. Additional uses may be defined in the future.
Instances of CIM_SettingData may represent Aspects of a CIM_ManagedElement instance. This is modeled using the CIM_SettingsDefineState association. CIM_SettingData may be used to define capabilities when associated to an instance of CIM_Capabilities through the CIM_SettingsDefineCapabilities association.
Instances of CIM_SettingData may represent different types of configurations for a CIM_ManagedElement, including persistent configurations, in progress configuration changes, or requested configurations. The CIM_ElementSettingData association is used to model the relationship between a CIM_SettingData instance and the CIM_ManagedElement for which it is a configuration.
When an instance of CIM_SettingData represents a configuration, the current operational values for the parameters of the element are reflected by properties in the Element itself or by properties in its associations. These properties do not have to be the same values that are present in the SettingData object. For example, a modem might have a SettingData baud rate of 56Kb/sec but be operating at 19.2Kb/sec.
Note: The CIM_SettingData class is very similar to CIM_Setting, yet both classes are present in the model because many implementations have successfully used CIM_Setting. However, issues have arisen that could not be resolved without defining a new class. Therefore, until a new major release occurs, both classes will exist in the model. Refer to the Core White Paper for additional information. SettingData instances can be aggregated together into higher- level SettingData objects using ConcreteComponent associations.
10Superclass SettingData for networking Superclass SettingData for networking
11PolicyStore property defines the store to retrieve the 6to4 configuration policy. PolicyStore property defines the store to retrieve the 6to4 configuration policy.
12Describes the 6to4 service state. One of the following values: enabled, disabled, default. Describes the 6to4 service state. One of the following values: enabled, disabled, default.
13default default
14automatic automatic
15enabled enabled
16disabled disabled
17Describes the 6to4 sharing state. One of the following values: enabled, disabled, default. Describes the 6to4 sharing state. One of the following values: enabled, disabled, default.
18Resolution interval in minutes. Resolution interval in minutes.
19Name of the 6to4 relay. Name of the 6to4 relay.
20State of the relay name resolution. One of the following values: enabled, disabled, automatic, default. State of the relay name resolution. One of the following values: enabled, disabled, automatic, default.
21Reset the 6to4 configuration. Reset the 6to4 configuration.
22Net6to4Configuration represents global 6to4 configuration shared across all 6to4 interfaces. Net6to4Configuration represents global 6to4 configuration shared across all 6to4 interfaces.
23The managed element. The managed element.
24The SettingData object associated with the element. The SettingData object associated with the element.
25An enumerated integer indicating that the referenced setting is a default setting for the element, or that this information is unknown. An enumerated integer indicating that the referenced setting is a default setting for the element, or that this information is unknown.
26Unknown Unknown
27Is Default Is Default
28Is Not Default Is Not Default
29An enumerated integer indicating that the referenced setting is currently being used in the operation of the element, or that this information is unknown. An enumerated integer indicating that the referenced setting is currently being used in the operation of the element, or that this information is unknown.
30Is Current Is Current
31Is Not Current Is Not Current
32An enumerated integer indicating whether or not the referenced setting is the next setting to be applied. For example, the application could take place on a re-initialization, reset, reconfiguration request. This could be a permanent setting, or a setting used only one time, as indicated by the flag. If it is a permanent setting then the setting is applied every time the managed element reinitializes, until this flag is manually reset. However, if it is single use, then the flag is automatically cleared after the settings are applied. Also note that if this flag is specified (i.e. set to value other than "Unknown"), then this takes precedence over any SettingData that may have been specified as Default. For example: If the managed element is a computer system, and the value of this flag is "Is Next", then the setting will be effective next time the system resets. And, unless this flag is changed, it will persist for subsequent system resets. However, if this flag is set to "Is Next For Single Use", then this setting will only be used once and the flag would be reset after that to "Is Not Next". So, in the above example, if the system reboots in a quick succession, the setting will not be used at the second reboot. An enumerated integer indicating whether or not the referenced setting is the next setting to be applied. For example, the application could take place on a re-initialization, reset, reconfiguration request. This could be a permanent setting, or a setting used only one time, as indicated by the flag. If it is a permanent setting then the setting is applied every time the managed element reinitializes, until this flag is manually reset. However, if it is single use, then the flag is automatically cleared after the settings are applied. Also note that if this flag is specified (i.e. set to value other than "Unknown"), then this takes precedence over any SettingData that may have been specified as Default. For example: If the managed element is a computer system, and the value of this flag is "Is Next", then the setting will be effective next time the system resets. And, unless this flag is changed, it will persist for subsequent system resets. However, if this flag is set to "Is Next For Single Use", then this setting will only be used once and the flag would be reset after that to "Is Not Next". So, in the above example, if the system reboots in a quick succession, the setting will not be used at the second reboot.
33Is Next Is Next
34Is Not Next Is Not Next
35Is Next For Single Use Is Next For Single Use
362.19.1 2.19.1
37ElementSettingData represents the association between ManagedElements and applicable setting data. This association also describes whether this is a default or current setting. ElementSettingData represents the association between ManagedElements and applicable setting data. This association also describes whether this is a default or current setting.
38A datetime value that indicates when the object was installed. Lack of a value does not indicate that the object is not installed. A datetime value that indicates when the object was installed. Lack of a value does not indicate that the object is not installed.
39The Name property defines the label by which the object is known. When subclassed, the Name property can be overridden to be a Key property. The Name property defines the label by which the object is known. When subclassed, the Name property can be overridden to be a Key property.
40Indicates 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 functioning nominally 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.
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 functioning nominally 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.
41Other Other
42OK OK
43Degraded Degraded
44Stressed Stressed
45Predictive Failure Predictive Failure
46Error Error
47Non-Recoverable Error Non-Recoverable Error
48Starting Starting
49Stopping Stopping
50Stopped Stopped
51In Service In Service
52No Contact No Contact
53Lost Communication Lost Communication
54Aborted Aborted
55Dormant Dormant
56Supporting Entity in Error Supporting Entity in Error
57Completed Completed
58Power Mode Power Mode
59DMTF Reserved DMTF Reserved
60Vendor Reserved Vendor Reserved
61Strings describing the various OperationalStatus array values. For example, if "Stopping" is the value assigned to OperationalStatus, then this property may contain an explanation as to why an object is being stopped. Note that entries in this array are correlated with those at the same array index in OperationalStatus. Strings describing the various OperationalStatus array values. For example, if "Stopping" is the value assigned to OperationalStatus, then this property may contain an explanation as to why an object is being stopped. Note that entries in this array are correlated with those at the same array index in OperationalStatus.
62A string indicating the current status of the object. Various operational and non-operational statuses are defined. This property is deprecated in lieu of OperationalStatus, which includes the same semantics in its enumeration. This change is made for 3 reasons:
1) Status is more correctly defined as an array. This definition overcomes the limitation of describing status using a single value, when it is really a multi-valued property (for example, an element might be OK AND Stopped.
2) A MaxLen of 10 is too restrictive and leads to unclear enumerated values.
3) The change to a uint16 data type was discussed when CIM V2.0 was defined. However, existing V1.0 implementations used the string property and did not want to modify their code. Therefore, Status was grandfathered into the Schema. Use of the deprecated qualifier allows the maintenance of the existing property, but also permits an improved definition using OperationalStatus.
A string indicating the current status of the object. Various operational and non-operational statuses are defined. This property is deprecated in lieu of OperationalStatus, which includes the same semantics in its enumeration. This change is made for 3 reasons:
1) Status is more correctly defined as an array. This definition overcomes the limitation of describing status using a single value, when it is really a multi-valued property (for example, an element might be OK AND Stopped.
2) A MaxLen of 10 is too restrictive and leads to unclear enumerated values.
3) The change to a uint16 data type was discussed when CIM V2.0 was defined. However, existing V1.0 implementations used the string property and did not want to modify their code. Therefore, Status was grandfathered into the Schema. Use of the deprecated qualifier allows the maintenance of the existing property, but also permits an improved definition using OperationalStatus.
63Indicates the current health of the element. This attribute expresses the health of this element but not necessarily that of its subcomponents. The possible values are 0 to 30, where 5 means the element is entirely healthy and 30 means the element is completely non-functional. The following continuum is defined:
"Non-recoverable Error" (30) - The element has completely failed, and recovery is not possible. All functionality provided by this element has been lost.
"Critical Failure" (25) - The element is non-functional and recovery might not be possible.
"Major Failure" (20) - The element is failing. It is possible that some or all of the functionality of this component is degraded or not working.
"Minor Failure" (15) - All functionality is available but some might be degraded.
"Degraded/Warning" (10) - The element is in working order and all functionality is provided. However, the element is not working to the best of its abilities. For example, the element might not be operating at optimal performance or it might be reporting recoverable errors.
"OK" (5) - The element is fully functional and is operating within normal operational parameters and without error.
"Unknown" (0) - The implementation cannot report on HealthState at this time.
DMTF has reserved the unused portion of the continuum for additional HealthStates in the future.
Indicates the current health of the element. This attribute expresses the health of this element but not necessarily that of its subcomponents. The possible values are 0 to 30, where 5 means the element is entirely healthy and 30 means the element is completely non-functional. The following continuum is defined:
"Non-recoverable Error" (30) - The element has completely failed, and recovery is not possible. All functionality provided by this element has been lost.
"Critical Failure" (25) - The element is non-functional and recovery might not be possible.
"Major Failure" (20) - The element is failing. It is possible that some or all of the functionality of this component is degraded or not working.
"Minor Failure" (15) - All functionality is available but some might be degraded.
"Degraded/Warning" (10) - The element is in working order and all functionality is provided. However, the element is not working to the best of its abilities. For example, the element might not be operating at optimal performance or it might be reporting recoverable errors.
"OK" (5) - The element is fully functional and is operating within normal operational parameters and without error.
"Unknown" (0) - The implementation cannot report on HealthState at this time.
DMTF has reserved the unused portion of the continuum for additional HealthStates in the future.
64Degraded/Warning Degraded/Warning
65Minor failure Minor failure
66Major failure Major failure
67Critical failure Critical failure
68Non-recoverable error Non-recoverable error
69CommunicationStatus indicates the ability of the instrumentation to communicate with the underlying ManagedElement. CommunicationStatus consists of one of the following values: Unknown, None, Communication OK, Lost Communication, or No Contact.
A Null return indicates the implementation (provider) does not implement this property.
"Unknown" indicates the implementation is in general capable of returning this property, but is unable to do so at this time.
"Not Available" indicates that the implementation (provider) is capable of returning a value for this property, but not ever for this particular piece of hardware/software or the property is intentionally not used because it adds no meaningful information (as in the case of a property that is intended to add additional info to another property).
"Communication OK " indicates communication is established with the element, but does not convey any quality of service.
"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 Managed Element is known to exist and has been contacted successfully in the past, but is currently unreachable.
CommunicationStatus indicates the ability of the instrumentation to communicate with the underlying ManagedElement. CommunicationStatus consists of one of the following values: Unknown, None, Communication OK, Lost Communication, or No Contact.
A Null return indicates the implementation (provider) does not implement this property.
"Unknown" indicates the implementation is in general capable of returning this property, but is unable to do so at this time.
"Not Available" indicates that the implementation (provider) is capable of returning a value for this property, but not ever for this particular piece of hardware/software or the property is intentionally not used because it adds no meaningful information (as in the case of a property that is intended to add additional info to another property).
"Communication OK " indicates communication is established with the element, but does not convey any quality of service.
"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 Managed Element is known to exist and has been contacted successfully in the past, but is currently unreachable.
70Not Available Not Available
71Communication OK Communication OK
72DetailedStatus compliments PrimaryStatus with additional status detail. It consists of one of the following values: Not Available, No Additional Information, Stressed, Predictive Failure, Error, Non-Recoverable Error, SupportingEntityInError. Detailed status is used to expand upon the PrimaryStatus of the element.
A Null return indicates the implementation (provider) does not implement this property.
"Not Available" indicates that the implementation (provider) is capable of returning a value for this property, but not ever for this particular piece of hardware/software or the property is intentionally not used because it adds no meaningful information (as in the case of a property that is intended to add additional info to another property).
"No Additional Information" indicates that the element is functioning normally as indicated by PrimaryStatus = "OK".
"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 functioning normally but a failure is predicted in the near future.
"Non-Recoverable Error " indicates that this element is in an error condition that requires human intervention.
"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.
DetailedStatus compliments PrimaryStatus with additional status detail. It consists of one of the following values: Not Available, No Additional Information, Stressed, Predictive Failure, Error, Non-Recoverable Error, SupportingEntityInError. Detailed status is used to expand upon the PrimaryStatus of the element.
A Null return indicates the implementation (provider) does not implement this property.
"Not Available" indicates that the implementation (provider) is capable of returning a value for this property, but not ever for this particular piece of hardware/software or the property is intentionally not used because it adds no meaningful information (as in the case of a property that is intended to add additional info to another property).
"No Additional Information" indicates that the element is functioning normally as indicated by PrimaryStatus = "OK".
"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 functioning normally but a failure is predicted in the near future.
"Non-Recoverable Error " indicates that this element is in an error condition that requires human intervention.
"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.
73No Additional Information No Additional Information
74OperatingStatus provides a current status value for the operational condition of the element and can be used for providing more detail with respect to the value of EnabledState. It can also provide the transitional states when an element is transitioning from one state to another, such as when an element is transitioning between EnabledState and RequestedState, as well as other transitional conditions.
OperatingStatus consists of one of the following values: Unknown, Not Available, In Service, Starting, Stopping, Stopped, Aborted, Dormant, Completed, Migrating, Emmigrating, Immigrating, Snapshotting. Shutting Down, In Test
A Null return indicates the implementation (provider) does not implement this property.
"Unknown" indicates the implementation is in general capable of returning this property, but is unable to do so at this time.
"None" indicates that the implementation (provider) is capable of returning a value for this property, but not ever for this particular piece of hardware/software or the property is intentionally not used because it adds no meaningful information (as in the case of a property that is intended to add additional info to another property).
"Servicing" describes an element being configured, maintained, cleaned, or otherwise administered.
"Starting" describes an element being initialized.
"Stopping" describes an element being brought to an orderly stop.
"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.
"Completed" indicates that the element has completed its operation. This value should be combined with either OK, Error, or Degraded in the PrimaryStatus 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).
"Migrating" element is being moved between host elements.
"Immigrating" element is being moved to new host element.
"Emigrating" element is being moved away from host element.
"Shutting Down" describes an element being brought to an abrupt stop.
"In Test" element is performing test functions.
"Transitioning" describes an element that is between states, that is, it is not fully available in either its previous state or its next state. This value should be used if other values indicating a transition to a specific state are not applicable.
"In Service" describes an element that is in service and operational.
OperatingStatus provides a current status value for the operational condition of the element and can be used for providing more detail with respect to the value of EnabledState. It can also provide the transitional states when an element is transitioning from one state to another, such as when an element is transitioning between EnabledState and RequestedState, as well as other transitional conditions.
OperatingStatus consists of one of the following values: Unknown, Not Available, In Service, Starting, Stopping, Stopped, Aborted, Dormant, Completed, Migrating, Emmigrating, Immigrating, Snapshotting. Shutting Down, In Test
A Null return indicates the implementation (provider) does not implement this property.
"Unknown" indicates the implementation is in general capable of returning this property, but is unable to do so at this time.
"None" indicates that the implementation (provider) is capable of returning a value for this property, but not ever for this particular piece of hardware/software or the property is intentionally not used because it adds no meaningful information (as in the case of a property that is intended to add additional info to another property).
"Servicing" describes an element being configured, maintained, cleaned, or otherwise administered.
"Starting" describes an element being initialized.
"Stopping" describes an element being brought to an orderly stop.
"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.
"Completed" indicates that the element has completed its operation. This value should be combined with either OK, Error, or Degraded in the PrimaryStatus 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).
"Migrating" element is being moved between host elements.
"Immigrating" element is being moved to new host element.
"Emigrating" element is being moved away from host element.
"Shutting Down" describes an element being brought to an abrupt stop.
"In Test" element is performing test functions.
"Transitioning" describes an element that is between states, that is, it is not fully available in either its previous state or its next state. This value should be used if other values indicating a transition to a specific state are not applicable.
"In Service" describes an element that is in service and operational.
75Servicing Servicing
76Migrating Migrating
77Emigrating Emigrating
78Immigrating Immigrating
79Snapshotting Snapshotting
80Shutting Down Shutting Down
81In Test In Test
82Transitioning Transitioning
83PrimaryStatus provides a high level status value, intended to align with Red-Yellow-Green type representation of status. It should be used in conjunction with DetailedStatus to provide high level and detailed health status of the ManagedElement and its subcomponents.
PrimaryStatus consists of one of the following values: Unknown, OK, Degraded or Error. "Unknown" indicates the implementation is in general capable of returning this property, but is unable to do so at this time.
"OK" indicates the ManagedElement is functioning normally.
"Degraded" indicates the ManagedElement is functioning below normal.
"Error" indicates the ManagedElement is in an Error condition.
PrimaryStatus provides a high level status value, intended to align with Red-Yellow-Green type representation of status. It should be used in conjunction with DetailedStatus to provide high level and detailed health status of the ManagedElement and its subcomponents.
PrimaryStatus consists of one of the following values: Unknown, OK, Degraded or Error. "Unknown" indicates the implementation is in general capable of returning this property, but is unable to do so at this time.
"OK" indicates the ManagedElement is functioning normally.
"Degraded" indicates the ManagedElement is functioning below normal.
"Error" indicates the ManagedElement is in an Error condition.
84CIM_ManagedSystemElement is the base class for the System Element hierarchy. Any distinguishable component of a System is a candidate for inclusion in this class. Examples of system components include:
- software components such as application servers, databases, and applications
- operating system components such as files, processes, and threads
- device components such as disk drives, controllers, processors, and printers
- physical components such as chips and cards.
CIM_ManagedSystemElement is the base class for the System Element hierarchy. Any distinguishable component of a System is a candidate for inclusion in this class. Examples of system components include:
- software components such as application servers, databases, and applications
- operating system components such as files, processes, and threads
- device components such as disk drives, controllers, processors, and printers
- physical components such as chips and cards.
852.22.0 2.22.0
86CIM_LogicalElement is a base class for all the components of a System that represent abstract system components, such as Files, Processes, or LogicalDevices. CIM_LogicalElement is a base class for all the components of a System that represent abstract system components, such as Files, Processes, or LogicalDevices.
872.6.0 2.6.0
88A free-form string that represents the status of the job. The primary status is reflected in the inherited OperationalStatus property. JobStatus provides additional, implementation-specific details. A free-form string that represents the status of the job. The primary status is reflected in the inherited OperationalStatus property. JobStatus provides additional, implementation-specific details.
89The time that the Job was submitted to execute. A value of all zeroes indicates that the owning element is not capable of reporting a date and time. Therefore, the ScheduledStartTime and StartTime are reported as intervals relative to the time their values are requested. The time that the Job was submitted to execute. A value of all zeroes indicates that the owning element is not capable of reporting a date and time. Therefore, the ScheduledStartTime and StartTime are reported as intervals relative to the time their values are requested.
90The time that the current Job is scheduled to start. This time can be represented by the actual date and time, or an interval relative to the time that this property is requested. A value of all zeroes indicates that the Job is already executing. The property is deprecated in lieu of the more expressive scheduling properties, RunMonth, RunDay, RunDayOfWeek, and RunStartInterval. The time that the current Job is scheduled to start. This time can be represented by the actual date and time, or an interval relative to the time that this property is requested. A value of all zeroes indicates that the Job is already executing. The property is deprecated in lieu of the more expressive scheduling properties, RunMonth, RunDay, RunDayOfWeek, and RunStartInterval.
91The time that the Job was actually started. This time can be represented by an actual date and time, or by an interval relative to the time that this property is requested. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run time can be stored in this single-valued property. The time that the Job was actually started. This time can be represented by an actual date and time, or by an interval relative to the time that this property is requested. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run time can be stored in this single-valued property.
92The time interval that the Job has been executing or the total execution time if the Job is complete. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run time can be stored in this single-valued property. The time interval that the Job has been executing or the total execution time if the Job is complete. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run time can be stored in this single-valued property.
93The number of times that the Job should be run. A value of 1 indicates that the Job is not recurring, while any non-zero value indicates a limit to the number of times that the Job will recur. Zero indicates that there is no limit to the number of times that the Job can be processed, but that it is terminated either after the UntilTime or by manual intervention. By default, a Job is processed once. The number of times that the Job should be run. A value of 1 indicates that the Job is not recurring, while any non-zero value indicates a limit to the number of times that the Job will recur. Zero indicates that there is no limit to the number of times that the Job can be processed, but that it is terminated either after the UntilTime or by manual intervention. By default, a Job is processed once.
94The month during which the Job should be processed. Specify 0 for January, 1 for February, and so on. The month during which the Job should be processed. Specify 0 for January, 1 for February, and so on.
95January January
96February February
97March March
98April April
99May May
100June June
101July July
102August August
103September September
104October October
105November November
106December December
107The day in the month on which the Job should be processed. There are two different interpretations for this property, depending on the value of DayOfWeek. In one case, RunDay defines the day-in-month on which the Job is processed. This interpretation is used when the DayOfWeek is 0. A positive or negative integer indicates whether the RunDay should be calculated from the beginning or end of the month. For example, 5 indicates the fifth day in the RunMonth and -1 indicates the last day in the RunMonth.

When RunDayOfWeek is not 0, RunDay is the day-in-month on which the Job is processed, defined in conjunction with RunDayOfWeek. For example, if RunDay is 15 and RunDayOfWeek is Saturday, then the Job is processed on the first Saturday on or after the 15th day in the RunMonth (for example, the third Saturday in the month). If RunDay is 20 and RunDayOfWeek is -Saturday, then this indicates the first Saturday on or before the 20th day in the RunMonth. If RunDay is -1 and RunDayOfWeek is -Sunday, then this indicates the last Sunday in the RunMonth.
The day in the month on which the Job should be processed. There are two different interpretations for this property, depending on the value of DayOfWeek. In one case, RunDay defines the day-in-month on which the Job is processed. This interpretation is used when the DayOfWeek is 0. A positive or negative integer indicates whether the RunDay should be calculated from the beginning or end of the month. For example, 5 indicates the fifth day in the RunMonth and -1 indicates the last day in the RunMonth.

When RunDayOfWeek is not 0, RunDay is the day-in-month on which the Job is processed, defined in conjunction with RunDayOfWeek. For example, if RunDay is 15 and RunDayOfWeek is Saturday, then the Job is processed on the first Saturday on or after the 15th day in the RunMonth (for example, the third Saturday in the month). If RunDay is 20 and RunDayOfWeek is -Saturday, then this indicates the first Saturday on or before the 20th day in the RunMonth. If RunDay is -1 and RunDayOfWeek is -Sunday, then this indicates the last Sunday in the RunMonth.
108A positive or negative integer used in conjunction with RunDay to indicate the day of the week on which the Job is processed. RunDayOfWeek is set to 0 to indicate an exact day of the month, such as March 1. A positive integer (representing Sunday, Monday, ..., Saturday) means that the day of week is found on or after the specified RunDay. A negative integer (representing -Sunday, -Monday, ..., -Saturday) means that the day of week is found on or BEFORE the RunDay. A positive or negative integer used in conjunction with RunDay to indicate the day of the week on which the Job is processed. RunDayOfWeek is set to 0 to indicate an exact day of the month, such as March 1. A positive integer (representing Sunday, Monday, ..., Saturday) means that the day of week is found on or after the specified RunDay. A negative integer (representing -Sunday, -Monday, ..., -Saturday) means that the day of week is found on or BEFORE the RunDay.
109-Saturday -Saturday
110-Friday -Friday
111-Thursday -Thursday
112-Wednesday -Wednesday
113-Tuesday -Tuesday
114-Monday -Monday
115-Sunday -Sunday
116ExactDayOfMonth ExactDayOfMonth
117Sunday Sunday
118Monday Monday
119Tuesday Tuesday
120Wednesday Wednesday
121Thursday Thursday
122Friday Friday
123Saturday Saturday
124The time interval after midnight when the Job should be processed. For example,
00000000020000.000000:000
indicates that the Job should be run on or after two o\'clock, local time or UTC time (distinguished using the LocalOrUtcTime property.
The time interval after midnight when the Job should be processed. For example,
00000000020000.000000:000
indicates that the Job should be run on or after two o\'clock, local time or UTC time (distinguished using the LocalOrUtcTime property.
125This property indicates whether the times represented in the RunStartInterval and UntilTime properties represent local times or UTC times. Time values are synchronized worldwide by using the enumeration value 2, "UTC Time". This property indicates whether the times represented in the RunStartInterval and UntilTime properties represent local times or UTC times. Time values are synchronized worldwide by using the enumeration value 2, "UTC Time".
126Local Time Local Time
127UTC Time UTC Time
128The time after which the Job is invalid or should be stopped. This time can be represented by an actual date and time, or by an interval relative to the time that this property is requested. A value of all nines indicates that the Job can run indefinitely. The time after which the Job is invalid or should be stopped. This time can be represented by an actual date and time, or by an interval relative to the time that this property is requested. A value of all nines indicates that the Job can run indefinitely.
129The User who is to be notified upon the Job completion or failure. The User who is to be notified upon the Job completion or failure.
130The User that submitted the Job, or the Service or method name that caused the job to be created. The User that submitted the Job, or the Service or method name that caused the job to be created.
131Indicates the urgency or importance of execution of the Job. The lower the number, the higher the priority. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the setting information that would influence the results of a job. Indicates the urgency or importance of execution of the Job. The lower the number, the higher the priority. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the setting information that would influence the results of a job.
132The percentage of the job that has completed at the time that this value is requested. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run data can be stored in this single-valued property.
Note that the value 101 is undefined and will be not be allowed in the next major revision of the specification.
The percentage of the job that has completed at the time that this value is requested. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run data can be stored in this single-valued property.
Note that the value 101 is undefined and will be not be allowed in the next major revision of the specification.
133Percent Percent
134Indicates whether or not the job should be automatically deleted upon completion. Note that the \'completion\' of a recurring job is defined by its JobRunTimes or UntilTime properties, or when the Job is terminated by manual intervention. If this property is set to false and the job completes, then the extrinsic method DeleteInstance must be used to delete the job instead of updating this property. Indicates whether or not the job should be automatically deleted upon completion. Note that the \'completion\' of a recurring job is defined by its JobRunTimes or UntilTime properties, or when the Job is terminated by manual intervention. If this property is set to false and the job completes, then the extrinsic method DeleteInstance must be used to delete the job instead of updating this property.
135A vendor-specific error code. The value must be set to zero if the Job completed without error. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run error can be stored in this single-valued property. A vendor-specific error code. The value must be set to zero if the Job completed without error. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run error can be stored in this single-valued property.
136A free-form string that contains the vendor error description. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run error can be stored in this single-valued property. A free-form string that contains the vendor error description. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run error can be stored in this single-valued property.
137Describes the recovery action to be taken for an unsuccessfully run Job. The possible values are:
0 = "Unknown", meaning it is unknown as to what recovery action to take
1 = "Other", indicating that the recovery action will be specified in the OtherRecoveryAction property
2 = "Do Not Continue", meaning stop the execution of the job and appropriately update its status
3 = "Continue With Next Job", meaning continue with the next job in the queue
4 = "Re-run Job", indicating that the job should be re-run
5 = "Run Recovery Job", meaning run the Job associated using the RecoveryJob relationship. Note that the recovery Job must already be in the queue from which it will run.
Describes the recovery action to be taken for an unsuccessfully run Job. The possible values are:
0 = "Unknown", meaning it is unknown as to what recovery action to take
1 = "Other", indicating that the recovery action will be specified in the OtherRecoveryAction property
2 = "Do Not Continue", meaning stop the execution of the job and appropriately update its status
3 = "Continue With Next Job", meaning continue with the next job in the queue
4 = "Re-run Job", indicating that the job should be re-run
5 = "Run Recovery Job", meaning run the Job associated using the RecoveryJob relationship. Note that the recovery Job must already be in the queue from which it will run.
138Do Not Continue Do Not Continue
139Continue With Next Job Continue With Next Job
140Re-run Job Re-run Job
141Run Recovery Job Run Recovery Job
142A string describing the recovery action when the RecoveryAction property of the instance is 1 ("Other"). A string describing the recovery action when the RecoveryAction property of the instance is 1 ("Other").
143KillJob is being deprecated because there is no distinction made between an orderly shutdown and an immediate kill. CIM_ConcreteJob.RequestStateChange() provides \'Terminate\' and \'Kill\' options to allow this distinction.
A method to kill this job and any underlying processes, and to remove any \'dangling\' associations.
KillJob is being deprecated because there is no distinction made between an orderly shutdown and an immediate kill. CIM_ConcreteJob.RequestStateChange() provides \'Terminate\' and \'Kill\' options to allow this distinction.
A method to kill this job and any underlying processes, and to remove any \'dangling\' associations.
144Success Success
145Not Supported Not Supported
146Timeout Timeout
147Failed Failed
148Access Denied Access Denied
149Not Found Not Found
150Vendor Specific Vendor Specific
151Indicates whether or not the Job should be automatically deleted upon termination. This parameter takes precedence over the property, DeleteOnCompletion. Indicates whether or not the Job should be automatically deleted upon termination. This parameter takes precedence over the property, DeleteOnCompletion.
152A Job is a LogicalElement that represents an executing unit of work, such as a script or a print job. A Job is distinct from a Process in that a Job can be scheduled or queued, and its execution is not limited to a single system. A Job is a LogicalElement that represents an executing unit of work, such as a script or a print job. A Job is distinct from a Process in that a Job can be scheduled or queued, and its execution is not limited to a single system.
1532.10.0 2.10.0
154Primary classification of the error. The following values are defined:
2 - Communications Error. Errors of this type are principally associated with the procedures and/or processes required to convey information from one point to another.
3 - Quality of Service Error. Errors of this type are principally associated with failures that result in reduced functionality or performance.
4 - Software Error. Error of this type are principally associated with a software or processing fault.
5 - Hardware Error. Errors of this type are principally associated with an equipment or hardware failure.
6 - Environmental Error. Errors of this type are principally associated with a failure condition relating the to facility, or other environmental considerations.
7 - Security Error. Errors of this type are associated with security violations, detection of viruses, and similar issues.
8 - Oversubscription Error. Errors of this type are principally associated with the failure to allocate sufficient resources to complete the operation.
9 - Unavailable Resource Error. Errors of this type are principally associated with the failure to access a required resource.
10 -Unsupported Operation Error. Errors of this type are principally associated with requests that are not supported.
Primary classification of the error. The following values are defined:
2 - Communications Error. Errors of this type are principally associated with the procedures and/or processes required to convey information from one point to another.
3 - Quality of Service Error. Errors of this type are principally associated with failures that result in reduced functionality or performance.
4 - Software Error. Error of this type are principally associated with a software or processing fault.
5 - Hardware Error. Errors of this type are principally associated with an equipment or hardware failure.
6 - Environmental Error. Errors of this type are principally associated with a failure condition relating the to facility, or other environmental considerations.
7 - Security Error. Errors of this type are associated with security violations, detection of viruses, and similar issues.
8 - Oversubscription Error. Errors of this type are principally associated with the failure to allocate sufficient resources to complete the operation.
9 - Unavailable Resource Error. Errors of this type are principally associated with the failure to access a required resource.
10 -Unsupported Operation Error. Errors of this type are principally associated with requests that are not supported.
155Communications Error Communications Error
156Quality of Service Error Quality of Service Error
157Software Error Software Error
158Hardware Error Hardware Error
159Environmental Error Environmental Error
160Security Error Security Error
161Oversubscription Error Oversubscription Error
162Unavailable Resource Error Unavailable Resource Error
163Unsupported Operation Error Unsupported Operation Error
164A free-form string describing the ErrorType when 1, "Other", is specified as the ErrorType. A free-form string describing the ErrorType when 1, "Other", is specified as the ErrorType.
165A string that uniquely identifies the entity that owns the definition of the format of the Message described in this instance. OwningEntity MUST include a copyrighted, trademarked or otherwise unique name that is owned by the business entity or standards body defining the format. A string that uniquely identifies the entity that owns the definition of the format of the Message described in this instance. OwningEntity MUST include a copyrighted, trademarked or otherwise unique name that is owned by the business entity or standards body defining the format.
166An opaque string that uniquely identifies, within the scope of the OwningEntity, the format of the Message. An opaque string that uniquely identifies, within the scope of the OwningEntity, the format of the Message.
167The formatted message. This message is constructed by combining some or all of the dynamic elements specified in the MessageArguments property with the static elements uniquely identified by the MessageID in a message registry or other catalog associated with the OwningEntity. The formatted message. This message is constructed by combining some or all of the dynamic elements specified in the MessageArguments property with the static elements uniquely identified by the MessageID in a message registry or other catalog associated with the OwningEntity.
168An array containing the dynamic content of the message. An array containing the dynamic content of the message.
169An enumerated value that describes the severity of the Indication from the notifier\'s point of view:
0 - the Perceived Severity of the indication is unknown or indeterminate.
1 - Other, by CIM convention, is used to indicate that the Severity\'s value can be found in the OtherSeverity property.
2 - Information should be used when providing an informative response.
3 - Degraded/Warning should be used when its appropriate to let the user decide if action is needed.
4 - Minor should be used to indicate action is needed, but the situation is not serious at this time.
5 - Major should be used to indicate action is needed NOW.
6 - Critical should be used to indicate action is needed NOW and the scope is broad (perhaps an imminent outage to a critical resource will result).
7 - Fatal/NonRecoverable should be used to indicate an error occurred, but it\'s too late to take remedial action.
2 and 0 - Information and Unknown (respectively) follow common usage. Literally, the Error is purely informational or its severity is simply unknown.
An enumerated value that describes the severity of the Indication from the notifier\'s point of view:
0 - the Perceived Severity of the indication is unknown or indeterminate.
1 - Other, by CIM convention, is used to indicate that the Severity\'s value can be found in the OtherSeverity property.
2 - Information should be used when providing an informative response.
3 - Degraded/Warning should be used when its appropriate to let the user decide if action is needed.
4 - Minor should be used to indicate action is needed, but the situation is not serious at this time.
5 - Major should be used to indicate action is needed NOW.
6 - Critical should be used to indicate action is needed NOW and the scope is broad (perhaps an imminent outage to a critical resource will result).
7 - Fatal/NonRecoverable should be used to indicate an error occurred, but it\'s too late to take remedial action.
2 and 0 - Information and Unknown (respectively) follow common usage. Literally, the Error is purely informational or its severity is simply unknown.
170Information Information
171Minor Minor
172Major Major
173Critical Critical
174Fatal/NonRecoverable Fatal/NonRecoverable
175An enumerated value that describes the probable cause of the error. An enumerated value that describes the probable cause of the error.
176Adapter/Card Error Adapter/Card Error
177Application Subsystem Failure Application Subsystem Failure
178Bandwidth Reduced Bandwidth Reduced
179Connection Establishment Error Connection Establishment Error
180Communications Protocol Error Communications Protocol Error
181Communications Subsystem Failure Communications Subsystem Failure
182Configuration/Customization Error Configuration/Customization Error
183Congestion Congestion
184Corrupt Data Corrupt Data
185CPU Cycles Limit Exceeded CPU Cycles Limit Exceeded
186Dataset/Modem Error Dataset/Modem Error
187Degraded Signal Degraded Signal
188DTE-DCE Interface Error DTE-DCE Interface Error
189Enclosure Door Open Enclosure Door Open
190Equipment Malfunction Equipment Malfunction
191Excessive Vibration Excessive Vibration
192File Format Error File Format Error
193Fire Detected Fire Detected
194Flood Detected Flood Detected
195Framing Error Framing Error
196HVAC Problem HVAC Problem
197Humidity Unacceptable Humidity Unacceptable
198I/O Device Error I/O Device Error
199Input Device Error Input Device Error
200LAN Error LAN Error
201Non-Toxic Leak Detected Non-Toxic Leak Detected
202Local Node Transmission Error Local Node Transmission Error
203Loss of Frame Loss of Frame
204Loss of Signal Loss of Signal
205Material Supply Exhausted Material Supply Exhausted
206Multiplexer Problem Multiplexer Problem
207Out of Memory Out of Memory
208Output Device Error Output Device Error
209Performance Degraded Performance Degraded
210Power Problem Power Problem
211Pressure Unacceptable Pressure Unacceptable
212Processor Problem (Internal Machine Error) Processor Problem (Internal Machine Error)
213Pump Failure Pump Failure
214Queue Size Exceeded Queue Size Exceeded
215Receive Failure Receive Failure
216Receiver Failure Receiver Failure
217Remote Node Transmission Error Remote Node Transmission Error
218Resource at or Nearing Capacity Resource at or Nearing Capacity
219Response Time Excessive Response Time Excessive
220Retransmission Rate Excessive Retransmission Rate Excessive
221Software Program Abnormally Terminated Software Program Abnormally Terminated
222Software Program Error (Incorrect Results) Software Program Error (Incorrect Results)
223Storage Capacity Problem Storage Capacity Problem
224Temperature Unacceptable Temperature Unacceptable
225Threshold Crossed Threshold Crossed
226Timing Problem Timing Problem
227Toxic Leak Detected Toxic Leak Detected
228Transmit Failure Transmit Failure
229Transmitter Failure Transmitter Failure
230Underlying Resource Unavailable Underlying Resource Unavailable
231Version Mismatch Version Mismatch
232Previous Alert Cleared Previous Alert Cleared
233Login Attempts Failed Login Attempts Failed
234Software Virus Detected Software Virus Detected
235Hardware Security Breached Hardware Security Breached
236Denial of Service Detected Denial of Service Detected
237Security Credential Mismatch Security Credential Mismatch
238Unauthorized Access Unauthorized Access
239Alarm Received Alarm Received
240Loss of Pointer Loss of Pointer
241Payload Mismatch Payload Mismatch
242Transmission Error Transmission Error
243Excessive Error Rate Excessive Error Rate
244Trace Problem Trace Problem
245Element Unavailable Element Unavailable
246Element Missing Element Missing
247Loss of Multi Frame Loss of Multi Frame
248Broadcast Channel Failure Broadcast Channel Failure
249Invalid Message Received Invalid Message Received
250Routing Failure Routing Failure
251Backplane Failure Backplane Failure
252Identifier Duplication Identifier Duplication
253Protection Path Failure Protection Path Failure
254Sync Loss or Mismatch Sync Loss or Mismatch
255Terminal Problem Terminal Problem
256Real Time Clock Failure Real Time Clock Failure
257Antenna Failure Antenna Failure
258Battery Charging Failure Battery Charging Failure
259Disk Failure Disk Failure
260Frequency Hopping Failure Frequency Hopping Failure
261Loss of Redundancy Loss of Redundancy
262Power Supply Failure Power Supply Failure
263Signal Quality Problem Signal Quality Problem
264Battery Discharging Battery Discharging
265Battery Failure Battery Failure
266Commercial Power Problem Commercial Power Problem
267Fan Failure Fan Failure
268Engine Failure Engine Failure
269Sensor Failure Sensor Failure
270Fuse Failure Fuse Failure
271Generator Failure Generator Failure
272Low Battery Low Battery
273Low Fuel Low Fuel
274Low Water Low Water
275Explosive Gas Explosive Gas
276High Winds High Winds
277Ice Buildup Ice Buildup
278Smoke Smoke
279Memory Mismatch Memory Mismatch
280Out of CPU Cycles Out of CPU Cycles
281Software Environment Problem Software Environment Problem
282Software Download Failure Software Download Failure
283Element Reinitialized Element Reinitialized
284Logging Problems Logging Problems
285Leak Detected Leak Detected
286Protection Mechanism Failure Protection Mechanism Failure
287Protecting Resource Failure Protecting Resource Failure
288Database Inconsistency Database Inconsistency
289Authentication Failure Authentication Failure
290Breach of Confidentiality Breach of Confidentiality
291Cable Tamper Cable Tamper
292Delayed Information Delayed Information
293Duplicate Information Duplicate Information
294Information Missing Information Missing
295Information Modification Information Modification
296Information Out of Sequence Information Out of Sequence
297Key Expired Key Expired
298Non-Repudiation Failure Non-Repudiation Failure
299Out of Hours Activity Out of Hours Activity
300Out of Service Out of Service
301Procedural Error Procedural Error
302Unexpected Information Unexpected Information
303A free-form string describing the probable cause of the error. A free-form string describing the probable cause of the error.
304A free-form string describing recommended actions to take to resolve the error. A free-form string describing recommended actions to take to resolve the error.
305The identifying information of the entity (i.e., the instance) generating the error. If this entity is modeled in the CIM Schema, this property contains the path of the instance encoded as a string parameter. If not modeled, the property contains some identifying string that names the entity that generated the error. The path or identifying string is formatted per the ErrorSourceFormat property. The identifying information of the entity (i.e., the instance) generating the error. If this entity is modeled in the CIM Schema, this property contains the path of the instance encoded as a string parameter. If not modeled, the property contains some identifying string that names the entity that generated the error. The path or identifying string is formatted per the ErrorSourceFormat property.
306The format of the ErrorSource property is interpretable based on the value of this property. Values are defined as:
0 - Unknown. The format is unknown or not meaningfully interpretable by a CIM client application.
1 - Other. The format is defined by the value of the OtherErrorSourceFormat property.2 - CIMObjectPath. A CIM Object Path as defined in the CIM Infrastructure specification. Note: CIM 2.5 and earlier used the term object names.
The format of the ErrorSource property is interpretable based on the value of this property. Values are defined as:
0 - Unknown. The format is unknown or not meaningfully interpretable by a CIM client application.
1 - Other. The format is defined by the value of the OtherErrorSourceFormat property.2 - CIMObjectPath. A CIM Object Path as defined in the CIM Infrastructure specification. Note: CIM 2.5 and earlier used the term object names.
307CIMObjectPath CIMObjectPath
308A string defining "Other" values for ErrorSourceFormat. This value MUST be set to a non NULL value when ErrorSourceFormat is set to a value of 1 ("Other"). For all other values of ErrorSourceFormat, the value of this string must be set to NULL. A string defining "Other" values for ErrorSourceFormat. This value MUST be set to a non NULL value when ErrorSourceFormat is set to a value of 1 ("Other"). For all other values of ErrorSourceFormat, the value of this string must be set to NULL.
309The CIM status code that characterizes this instance.
This property defines the status codes that MAY be return by a conforming CIM Server or Listener. Note that not all status codes are valid for each operation. The specification for each operation SHOULD define the status codes that may be returned by that operation.
The following values for CIM status code are defined:
1 - CIM_ERR_FAILED. A general error occurred that is not covered by a more specific error code.
2 - CIM_ERR_ACCESS_DENIED. Access to a CIM resource was not available to the client.
3 - CIM_ERR_INVALID_NAMESPACE. The target namespace does not exist.
4 - CIM_ERR_INVALID_PARAMETER. One or more parameter values passed to the method were invalid.
5 - CIM_ERR_INVALID_CLASS. The specified Class does not exist.
6 - CIM_ERR_NOT_FOUND. The requested object could not be found.
7 - CIM_ERR_NOT_SUPPORTED. The requested operation is not supported.
8 - CIM_ERR_CLASS_HAS_CHILDREN. Operation cannot be carried out on this class since it has instances.
9 - CIM_ERR_CLASS_HAS_INSTANCES. Operation cannot be carried out on this class since it has instances.
10 - CIM_ERR_INVALID_SUPERCLASS. Operation cannot be carried out since the specified superclass does not exist.
11 - CIM_ERR_ALREADY_EXISTS. Operation cannot be carried out because an object already exists.
12 - CIM_ERR_NO_SUCH_PROPERTY. The specified Property does not exist.
13 - CIM_ERR_TYPE_MISMATCH. The value supplied is incompatible with the type.
14 - CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED. The query language is not recognized or supported.
15 - CIM_ERR_INVALID_QUERY. The query is not valid for the specified query language.
16 - CIM_ERR_METHOD_NOT_AVAILABLE. The extrinsic Method could not be executed.
17 - CIM_ERR_METHOD_NOT_FOUND. The specified extrinsic Method does not exist.
18 - CIM_ERR_UNEXPECTED_RESPONSE. The returned response to the asynchronous operation was not expected.
19 - CIM_ERR_INVALID_RESPONSE_DESTINATION. The specified destination for the asynchronous response is not valid.
20 - CIM_ERR_NAMESPACE_NOT_EMPTY. The specified Namespace is not empty.
21 - CIM_ERR_INVALID_ENUMERATION_CONTEXT. The enumeration context supplied is not valid.
22 - CIM_ERR_INVALID_OPERATION_TIMEOUT. The specified Namespace is not empty.
23 - CIM_ERR_PULL_HAS_BEEN_ABANDONED. The specified Namespace is not empty.
24 - CIM_ERR_PULL_CANNOT_BE_ABANDONED. The attempt to abandon a pull operation has failed.
25 - CIM_ERR_FILTERED_ENUMERATION_NOT_SUPPORTED. Filtered Enumeratrions are not supported.
26 - CIM_ERR_CONTINUATION_ON_ERROR_NOT_SUPPORTED. Continue on error is not supported.
27 - CIM_ERR_SERVER_LIMITS_EXCEEDED. The WBEM Server limits have been exceeded (e.g. memory, connections, ...).
28 - CIM_ERR_SERVER_IS_SHUTTING_DOWN. The WBEM Server is shutting down.
29 - CIM_ERR_QUERY_FEATURE_NOT_SUPPORTED. The specified Query Feature is not supported.
The CIM status code that characterizes this instance.
This property defines the status codes that MAY be return by a conforming CIM Server or Listener. Note that not all status codes are valid for each operation. The specification for each operation SHOULD define the status codes that may be returned by that operation.
The following values for CIM status code are defined:
1 - CIM_ERR_FAILED. A general error occurred that is not covered by a more specific error code.
2 - CIM_ERR_ACCESS_DENIED. Access to a CIM resource was not available to the client.
3 - CIM_ERR_INVALID_NAMESPACE. The target namespace does not exist.
4 - CIM_ERR_INVALID_PARAMETER. One or more parameter values passed to the method were invalid.
5 - CIM_ERR_INVALID_CLASS. The specified Class does not exist.
6 - CIM_ERR_NOT_FOUND. The requested object could not be found.
7 - CIM_ERR_NOT_SUPPORTED. The requested operation is not supported.
8 - CIM_ERR_CLASS_HAS_CHILDREN. Operation cannot be carried out on this class since it has instances.
9 - CIM_ERR_CLASS_HAS_INSTANCES. Operation cannot be carried out on this class since it has instances.
10 - CIM_ERR_INVALID_SUPERCLASS. Operation cannot be carried out since the specified superclass does not exist.
11 - CIM_ERR_ALREADY_EXISTS. Operation cannot be carried out because an object already exists.
12 - CIM_ERR_NO_SUCH_PROPERTY. The specified Property does not exist.
13 - CIM_ERR_TYPE_MISMATCH. The value supplied is incompatible with the type.
14 - CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED. The query language is not recognized or supported.
15 - CIM_ERR_INVALID_QUERY. The query is not valid for the specified query language.
16 - CIM_ERR_METHOD_NOT_AVAILABLE. The extrinsic Method could not be executed.
17 - CIM_ERR_METHOD_NOT_FOUND. The specified extrinsic Method does not exist.
18 - CIM_ERR_UNEXPECTED_RESPONSE. The returned response to the asynchronous operation was not expected.
19 - CIM_ERR_INVALID_RESPONSE_DESTINATION. The specified destination for the asynchronous response is not valid.
20 - CIM_ERR_NAMESPACE_NOT_EMPTY. The specified Namespace is not empty.
21 - CIM_ERR_INVALID_ENUMERATION_CONTEXT. The enumeration context supplied is not valid.
22 - CIM_ERR_INVALID_OPERATION_TIMEOUT. The specified Namespace is not empty.
23 - CIM_ERR_PULL_HAS_BEEN_ABANDONED. The specified Namespace is not empty.
24 - CIM_ERR_PULL_CANNOT_BE_ABANDONED. The attempt to abandon a pull operation has failed.
25 - CIM_ERR_FILTERED_ENUMERATION_NOT_SUPPORTED. Filtered Enumeratrions are not supported.
26 - CIM_ERR_CONTINUATION_ON_ERROR_NOT_SUPPORTED. Continue on error is not supported.
27 - CIM_ERR_SERVER_LIMITS_EXCEEDED. The WBEM Server limits have been exceeded (e.g. memory, connections, ...).
28 - CIM_ERR_SERVER_IS_SHUTTING_DOWN. The WBEM Server is shutting down.
29 - CIM_ERR_QUERY_FEATURE_NOT_SUPPORTED. The specified Query Feature is not supported.
310CIM_ERR_FAILED CIM_ERR_FAILED
311CIM_ERR_ACCESS_DENIED CIM_ERR_ACCESS_DENIED
312CIM_ERR_INVALID_NAMESPACE CIM_ERR_INVALID_NAMESPACE
313CIM_ERR_INVALID_PARAMETER CIM_ERR_INVALID_PARAMETER
314CIM_ERR_INVALID_CLASS CIM_ERR_INVALID_CLASS
315CIM_ERR_NOT_FOUND CIM_ERR_NOT_FOUND
316CIM_ERR_NOT_SUPPORTED CIM_ERR_NOT_SUPPORTED
317CIM_ERR_CLASS_HAS_CHILDREN CIM_ERR_CLASS_HAS_CHILDREN
318CIM_ERR_CLASS_HAS_INSTANCES CIM_ERR_CLASS_HAS_INSTANCES
319CIM_ERR_INVALID_SUPERCLASS CIM_ERR_INVALID_SUPERCLASS
320CIM_ERR_ALREADY_EXISTS CIM_ERR_ALREADY_EXISTS
321CIM_ERR_NO_SUCH_PROPERTY CIM_ERR_NO_SUCH_PROPERTY
322CIM_ERR_TYPE_MISMATCH CIM_ERR_TYPE_MISMATCH
323CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED
324CIM_ERR_INVALID_QUERY CIM_ERR_INVALID_QUERY
325CIM_ERR_METHOD_NOT_AVAILABLE CIM_ERR_METHOD_NOT_AVAILABLE
326CIM_ERR_METHOD_NOT_FOUND CIM_ERR_METHOD_NOT_FOUND
327CIM_ERR_UNEXPECTED_RESPONSE CIM_ERR_UNEXPECTED_RESPONSE
328CIM_ERR_INVALID_RESPONSE_DESTINATION CIM_ERR_INVALID_RESPONSE_DESTINATION
329CIM_ERR_NAMESPACE_NOT_EMPTY CIM_ERR_NAMESPACE_NOT_EMPTY
330CIM_ERR_INVALID_ENUMERATION_CONTEXT CIM_ERR_INVALID_ENUMERATION_CONTEXT
331CIM_ERR_INVALID_OPERATION_TIMEOUT CIM_ERR_INVALID_OPERATION_TIMEOUT
332CIM_ERR_PULL_HAS_BEEN_ABANDONED CIM_ERR_PULL_HAS_BEEN_ABANDONED
333CIM_ERR_PULL_CANNOT_BE_ABANDONED CIM_ERR_PULL_CANNOT_BE_ABANDONED
334CIM_ERR_FILTERED_ENUMERATION_NOT_SUPPORTED CIM_ERR_FILTERED_ENUMERATION_NOT_SUPPORTED
335CIM_ERR_CONTINUATION_ON_ERROR_NOT_SUPPORTED CIM_ERR_CONTINUATION_ON_ERROR_NOT_SUPPORTED
336CIM_ERR_SERVER_LIMITS_EXCEEDED CIM_ERR_SERVER_LIMITS_EXCEEDED
337CIM_ERR_SERVER_IS_SHUTTING_DOWN CIM_ERR_SERVER_IS_SHUTTING_DOWN
338CIM_ERR_QUERY_FEATURE_NOT_SUPPORTED CIM_ERR_QUERY_FEATURE_NOT_SUPPORTED
339A free-form string containing a human-readable description of CIMStatusCode. This description MAY extend, but MUST be consistent with, the definition of CIMStatusCode. A free-form string containing a human-readable description of CIMStatusCode. This description MAY extend, but MUST be consistent with, the definition of CIMStatusCode.
3402.22.1 2.22.1
341CIM_Error is a specialized class that contains information about the severity, cause, recommended actions and other data related to the failure of a CIM Operation. Instances of this type MAY be included as part of the response to a CIM Operation. CIM_Error is a specialized class that contains information about the severity, cause, recommended actions and other data related to the failure of a CIM Operation. Instances of this type MAY be included as part of the response to a CIM Operation.
342Within the scope of the instantiating Namespace, InstanceID opaquely and uniquely identifies an instance of this class. In order to ensure uniqueness within the NameSpace, the value of InstanceID SHOULD be constructed using the following \'preferred\' algorithm:
:
Where and are separated by a colon \':\', and where must include a copyrighted, trademarked or otherwise unique name that is owned by the business entity that is creating or defining the InstanceID, or that is a registered ID that is assigned to the business entity by a recognized global authority. (This requirement is similar to the _ structure of Schema class names.) In addition, to ensure uniqueness must not contain a colon (\':\'). When using this algorithm, the first colon to appear in InstanceID must appear between and .
is chosen by the business entity and should not be re-used to identify different underlying (real-world) elements. If the above \'preferred\' algorithm is not used, the defining entity must assure that the resulting InstanceID is not re-used across any InstanceIDs produced by this or other providers for the NameSpace of this instance.
For DMTF defined instances, the \'preferred\' algorithm must be used with the set to \'CIM\'.
Within the scope of the instantiating Namespace, InstanceID opaquely and uniquely identifies an instance of this class. In order to ensure uniqueness within the NameSpace, the value of InstanceID SHOULD be constructed using the following \'preferred\' algorithm:
:
Where and are separated by a colon \':\', and where must include a copyrighted, trademarked or otherwise unique name that is owned by the business entity that is creating or defining the InstanceID, or that is a registered ID that is assigned to the business entity by a recognized global authority. (This requirement is similar to the _ structure of Schema class names.) In addition, to ensure uniqueness must not contain a colon (\':\'). When using this algorithm, the first colon to appear in InstanceID must appear between and .
is chosen by the business entity and should not be re-used to identify different underlying (real-world) elements. If the above \'preferred\' algorithm is not used, the defining entity must assure that the resulting InstanceID is not re-used across any InstanceIDs produced by this or other providers for the NameSpace of this instance.
For DMTF defined instances, the \'preferred\' algorithm must be used with the set to \'CIM\'.
343The user-friendly name for this instance of a Job. In addition, the user-friendly name can be used as a property for a search or query. (Note: Name does not have to be unique within a namespace.) The user-friendly name for this instance of a Job. In addition, the user-friendly name can be used as a property for a search or query. (Note: Name does not have to be unique within a namespace.)
344JobState is an integer enumeration that indicates the operational state of a Job. It can also indicate transitions between these states, for example, \'Shutting Down\' and \'Starting\'. Following is a brief description of the states:
New (2) indicates that the job has never been started.
Starting (3) indicates that the job is moving from the \'New\', \'Suspended\', or \'Service\' states into the \'Running\' state.
Running (4) indicates that the Job is running.
Suspended (5) indicates that the Job is stopped, but can be restarted in a seamless manner.
Shutting Down (6) indicates that the job is moving to a \'Completed\', \'Terminated\', or \'Killed\' state.
Completed (7) indicates that the job has completed normally.
Terminated (8) indicates that the job has been stopped by a \'Terminate\' state change request. The job and all its underlying processes are ended and can be restarted (this is job-specific) only as a new job.
Killed (9) indicates that the job has been stopped by a \'Kill\' state change request. Underlying processes might have been left running, and cleanup might be required to free up resources.
Exception (10) indicates that the Job is in an abnormal state that might be indicative of an error condition. Actual status might be displayed though job-specific objects.
Service (11) indicates that the Job is in a vendor-specific state that supports problem discovery, or resolution, or both.
Query pending (12) waiting for a client to resolve a query
JobState is an integer enumeration that indicates the operational state of a Job. It can also indicate transitions between these states, for example, \'Shutting Down\' and \'Starting\'. Following is a brief description of the states:
New (2) indicates that the job has never been started.
Starting (3) indicates that the job is moving from the \'New\', \'Suspended\', or \'Service\' states into the \'Running\' state.
Running (4) indicates that the Job is running.
Suspended (5) indicates that the Job is stopped, but can be restarted in a seamless manner.
Shutting Down (6) indicates that the job is moving to a \'Completed\', \'Terminated\', or \'Killed\' state.
Completed (7) indicates that the job has completed normally.
Terminated (8) indicates that the job has been stopped by a \'Terminate\' state change request. The job and all its underlying processes are ended and can be restarted (this is job-specific) only as a new job.
Killed (9) indicates that the job has been stopped by a \'Kill\' state change request. Underlying processes might have been left running, and cleanup might be required to free up resources.
Exception (10) indicates that the Job is in an abnormal state that might be indicative of an error condition. Actual status might be displayed though job-specific objects.
Service (11) indicates that the Job is in a vendor-specific state that supports problem discovery, or resolution, or both.
Query pending (12) waiting for a client to resolve a query
345New New
346Running Running
347Suspended Suspended
348Terminated Terminated
349Killed Killed
350Exception Exception
351Service Service
352Query Pending Query Pending
353The date or time when the state of the Job last changed. If the state of the Job has not changed and this property is populated, then it must be set to a 0 interval value. If a state change was requested, but rejected or not yet processed, the property must not be updated. The date or time when the state of the Job last changed. If the state of the Job has not changed and this property is populated, then it must be set to a 0 interval value. If a state change was requested, but rejected or not yet processed, the property must not be updated.
354The amount of time that the Job is retained after it has finished executing, either succeeding or failing in that execution. The job must remain in existence for some period of time regardless of the value of the DeleteOnCompletion property.
The default is five minutes.
The amount of time that the Job is retained after it has finished executing, either succeeding or failing in that execution. The job must remain in existence for some period of time regardless of the value of the DeleteOnCompletion property.
The default is five minutes.
355Requests that the state of the job be changed to the value specified in the RequestedState parameter. Invoking the RequestStateChange method multiple times could result in earlier requests being overwritten or lost.
If 0 is returned, then the task completed successfully. Any other return code indicates an error condition.
Requests that the state of the job be changed to the value specified in the RequestedState parameter. Invoking the RequestStateChange method multiple times could result in earlier requests being overwritten or lost.
If 0 is returned, then the task completed successfully. Any other return code indicates an error condition.
356Completed with No Error Completed with No Error
357Unknown/Unspecified Error Unknown/Unspecified Error
358Can NOT complete within Timeout Period Can NOT complete within Timeout Period
359Invalid Parameter Invalid Parameter
360In Use In Use
361Method Parameters Checked - Transition Started Method Parameters Checked - Transition Started
362Invalid State Transition Invalid State Transition
363Use of Timeout Parameter Not Supported Use of Timeout Parameter Not Supported
364Busy Busy
365Method Reserved Method Reserved
366RequestStateChange changes the state of a job. The possible values are as follows:
Start (2) changes the state to \'Running\'.
Suspend (3) stops the job temporarily. The intention is to subsequently restart the job with \'Start\'. It might be possible to enter the \'Service\' state while suspended. (This is job-specific.)
Terminate (4) stops the job cleanly, saving data, preserving the state, and shutting down all underlying processes in an orderly manner.
Kill (5) terminates the job immediately with no requirement to save data or preserve the state.
Service (6) puts the job into a vendor-specific service state. It might be possible to restart the job.
RequestStateChange changes the state of a job. The possible values are as follows:
Start (2) changes the state to \'Running\'.
Suspend (3) stops the job temporarily. The intention is to subsequently restart the job with \'Start\'. It might be possible to enter the \'Service\' state while suspended. (This is job-specific.)
Terminate (4) stops the job cleanly, saving data, preserving the state, and shutting down all underlying processes in an orderly manner.
Kill (5) terminates the job immediately with no requirement to save data or preserve the state.
Service (6) puts the job into a vendor-specific service state. It might be possible to restart the job.
367Start Start
368Suspend Suspend
369Terminate Terminate
370Kill Kill
371A timeout period that specifies the maximum amount of time that the client expects the transition to the new state to take. The interval format must be used to specify the TimeoutPeriod. A value of 0 or a null parameter indicates that the client has no time requirements for the transition.
If this property does not contain 0 or null and the implementation does not support this parameter, a return code of \'Use Of Timeout Parameter Not Supported\' must be returned.
A timeout period that specifies the maximum amount of time that the client expects the transition to the new state to take. The interval format must be used to specify the TimeoutPeriod. A value of 0 or a null parameter indicates that the client has no time requirements for the transition.
If this property does not contain 0 or null and the implementation does not support this parameter, a return code of \'Use Of Timeout Parameter Not Supported\' must be returned.
372When the job is executing or has terminated without error, then this method returns no CIM_Error instance. However, if the job has failed because of some internal problem or because the job has been terminated by a client, then a CIM_Error instance is returned. When the job is executing or has terminated without error, then this method returns no CIM_Error instance. However, if the job has failed because of some internal problem or because the job has been terminated by a client, then a CIM_Error instance is returned.
373Unspecified Error Unspecified Error
374If the OperationalStatus on the Job is not "OK", then this method will return a CIM Error instance. Otherwise, when the Job is "OK", null is returned. If the OperationalStatus on the Job is not "OK", then this method will return a CIM Error instance. Otherwise, when the Job is "OK", null is returned.
375A concrete version of Job. This class represents a generic and instantiable unit of work, such as a batch or a print job. A concrete version of Job. This class represents a generic and instantiable unit of work, such as a batch or a print job.
376EnabledState is an integer enumeration that indicates the enabled and disabled states of an element. It can also indicate the transitions between these requested states. For example, shutting down (value=4) and starting (value=10) are transient states between enabled and disabled. The following text briefly summarizes the various enabled and disabled states:
Enabled (2) indicates that the element is or could be executing commands, will process any queued commands, and queues new requests.
Disabled (3) indicates that the element will not execute commands and will drop any new requests.
Shutting Down (4) indicates that the element is in the process of going to a Disabled state.
Not Applicable (5) indicates the element does not support being enabled or disabled.
Enabled but Offline (6) indicates that the element might be completing commands, and will drop any new requests.
Test (7) indicates that the element is in a test state.
Deferred (8) indicates that the element might be completing commands, but will queue any new requests.
Quiesce (9) indicates that the element is enabled but in a restricted mode.
Starting (10) indicates that the element is in the process of going to an Enabled state. New requests are queued.
EnabledState is an integer enumeration that indicates the enabled and disabled states of an element. It can also indicate the transitions between these requested states. For example, shutting down (value=4) and starting (value=10) are transient states between enabled and disabled. The following text briefly summarizes the various enabled and disabled states:
Enabled (2) indicates that the element is or could be executing commands, will process any queued commands, and queues new requests.
Disabled (3) indicates that the element will not execute commands and will drop any new requests.
Shutting Down (4) indicates that the element is in the process of going to a Disabled state.
Not Applicable (5) indicates the element does not support being enabled or disabled.
Enabled but Offline (6) indicates that the element might be completing commands, and will drop any new requests.
Test (7) indicates that the element is in a test state.
Deferred (8) indicates that the element might be completing commands, but will queue any new requests.
Quiesce (9) indicates that the element is enabled but in a restricted mode.
Starting (10) indicates that the element is in the process of going to an Enabled state. New requests are queued.
377Enabled Enabled
378Disabled Disabled
379Not Applicable Not Applicable
380Enabled but Offline Enabled but Offline
381Deferred Deferred
382Quiesce Quiesce
383A string that describes the enabled or disabled state of the element when the EnabledState property is set to 1 ("Other"). This property must be set to null when EnabledState is any value other than 1. A string that describes the enabled or disabled state of the element when the EnabledState property is set to 1 ("Other"). This property must be set to null when EnabledState is any value other than 1.
384RequestedState is 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.
"Unknown" (0) indicates the last requested state for the element is unknown.
Note that the value "No Change" (5) has been deprecated in lieu 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.
It should be noted that there are two new values in RequestedState that build on the statuses of EnabledState. These are "Reboot" (10) and "Reset" (11). Reboot refers to doing a "Shut Down" and then moving to an "Enabled" state. Reset indicates that the element is first "Disabled" and then "Enabled". The distinction between requesting "Shut Down" and "Disabled" should also be noted. Shut Down requests an orderly transition to the Disabled state, and might involve removing power, to completely erase any existing state. The Disabled state requests an immediate disabling of the element, such that it will not execute or accept any commands or processing requests.

This property is set as the result of a method invocation (such as Start or StopService on CIM_Service), or can be overridden and defined as WRITEable in a subclass. The method approach is considered superior to a WRITEable property, because it allows an explicit invocation of the operation and the return of a result code.

If knowledge of the last RequestedState is not supported for the EnabledLogicalElement, the property shall be NULL or have the value 12 "Not Applicable".
RequestedState is 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.
"Unknown" (0) indicates the last requested state for the element is unknown.
Note that the value "No Change" (5) has been deprecated in lieu 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.
It should be noted that there are two new values in RequestedState that build on the statuses of EnabledState. These are "Reboot" (10) and "Reset" (11). Reboot refers to doing a "Shut Down" and then moving to an "Enabled" state. Reset indicates that the element is first "Disabled" and then "Enabled". The distinction between requesting "Shut Down" and "Disabled" should also be noted. Shut Down requests an orderly transition to the Disabled state, and might involve removing power, to completely erase any existing state. The Disabled state requests an immediate disabling of the element, such that it will not execute or accept any commands or processing requests.

This property is set as the result of a method invocation (such as Start or StopService on CIM_Service), or can be overridden and defined as WRITEable in a subclass. The method approach is considered superior to a WRITEable property, because it allows an explicit invocation of the operation and the return of a result code.

If knowledge of the last RequestedState is not supported for the EnabledLogicalElement, the property shall be NULL or have the value 12 "Not Applicable".
385Shut Down Shut Down
386No Change No Change
387Offline Offline
388Test Test
389Reboot Reboot
390Reset Reset
391An enumerated value indicating an administrator\'s default or startup configuration for the Enabled State of an element. By default, the element is "Enabled" (value=2). An enumerated value indicating an administrator\'s default or startup configuration for the Enabled State of an element. By default, the element is "Enabled" (value=2).
392No Default No Default
393The date or time when the EnabledState of the element last changed. If the state of the element has not changed and this property is populated, then it must be set to a 0 interval value. If a state change was requested, but rejected or not yet processed, the property must not be updated. The date or time when the EnabledState of the element last changed. If the state of the element has not changed and this property is populated, then it must be set to a 0 interval value. If a state change was requested, but rejected or not yet processed, the property must not be updated.
394AvailableRequestedStates indicates the possible values for the RequestedState parameter of the method RequestStateChange, used to initiate a state change. The values listed shall be a subset of the values contained in the RequestedStatesSupported property of the associated instance of CIM_EnabledLogicalElementCapabilities where the values selected are a function of the current state of the CIM_EnabledLogicalElement. This property may be non-null if an implementation is able to advertise the set of possible values as a function of the current state. This property shall be null if an implementation is unable to determine the set of possible values as a function of the current state. AvailableRequestedStates indicates the possible values for the RequestedState parameter of the method RequestStateChange, used to initiate a state change. The values listed shall be a subset of the values contained in the RequestedStatesSupported property of the associated instance of CIM_EnabledLogicalElementCapabilities where the values selected are a function of the current state of the CIM_EnabledLogicalElement. This property may be non-null if an implementation is able to advertise the set of possible values as a function of the current state. This property shall be null if an implementation is unable to determine the set of possible values as a function of the current state.
395Defer Defer
396TransitioningToState indicates the target state to which the instance is transitioning.
A value of 5 "No Change" shall indicate that no transition is in progress.A value of 12 "Not Applicable" shall indicate the implementation does not support representing ongoing transitions.
A value other than 5 or 12 shall identify the state to which the element is in the process of transitioning.
TransitioningToState indicates the target state to which the instance is transitioning.
A value of 5 "No Change" shall indicate that no transition is in progress.A value of 12 "Not Applicable" shall indicate the implementation does not support representing ongoing transitions.
A value other than 5 or 12 shall identify the state to which the element is in the process of transitioning.
397Requests that the state of the element be changed to the value specified in the RequestedState parameter. When the requested state change takes place, the EnabledState and RequestedState of the element will be the same. Invoking the RequestStateChange method multiple times could result in earlier requests being overwritten or lost.
A return code of 0 shall indicate the state change was successfully initiated.
A return code of 3 shall indicate that the state transition cannot complete within the interval specified by the TimeoutPeriod parameter.
A return code of 4096 (0x1000) shall indicate the state change was successfully initiated, a ConcreteJob has been created, and its reference returned in the output parameter Job. Any other return code indicates an error condition.
Requests that the state of the element be changed to the value specified in the RequestedState parameter. When the requested state change takes place, the EnabledState and RequestedState of the element will be the same. Invoking the RequestStateChange method multiple times could result in earlier requests being overwritten or lost.
A return code of 0 shall indicate the state change was successfully initiated.
A return code of 3 shall indicate that the state transition cannot complete within the interval specified by the TimeoutPeriod parameter.
A return code of 4096 (0x1000) shall indicate the state change was successfully initiated, a ConcreteJob has been created, and its reference returned in the output parameter Job. Any other return code indicates an error condition.
398Unknown or Unspecified Error Unknown or Unspecified Error
399Cannot complete within Timeout Period Cannot complete within Timeout Period
400Method Parameters Checked - Job Started Method Parameters Checked - Job Started
401The state requested for the element. This information will be placed into the RequestedState property of the instance if the return code of the RequestStateChange method is 0 (\'Completed with No Error\'), or 4096 (0x1000) (\'Job Started\'). Refer to the description of the EnabledState and RequestedState properties for the detailed explanations of the RequestedState values. The state requested for the element. This information will be placed into the RequestedState property of the instance if the return code of the RequestStateChange method is 0 (\'Completed with No Error\'), or 4096 (0x1000) (\'Job Started\'). Refer to the description of the EnabledState and RequestedState properties for the detailed explanations of the RequestedState values.
402May contain a reference to the ConcreteJob created to track the state transition initiated by the method invocation. May contain a reference to the ConcreteJob created to track the state transition initiated by the method invocation.
403A timeout period that specifies the maximum amount of time that the client expects the transition to the new state to take. The interval format must be used to specify the TimeoutPeriod. A value of 0 or a null parameter indicates that the client has no time requirements for the transition.
If this property does not contain 0 or null and the implementation does not support this parameter, a return code of \'Use Of Timeout Parameter Not Supported\' shall be returned.
A timeout period that specifies the maximum amount of time that the client expects the transition to the new state to take. The interval format must be used to specify the TimeoutPeriod. A value of 0 or a null parameter indicates that the client has no time requirements for the transition.
If this property does not contain 0 or null and the implementation does not support this parameter, a return code of \'Use Of Timeout Parameter Not Supported\' shall be returned.
404This class extends LogicalElement to abstract the concept of an element that is enabled and disabled, such as a LogicalDevice or a ServiceAccessPoint. This class extends LogicalElement to abstract the concept of an element that is enabled and disabled, such as a LogicalDevice or a ServiceAccessPoint.
405The Name property uniquely identifies the ServiceAccessPoint and provides an indication of the functionality that is managed. This functionality is described in more detail in the Description property of the object. The Name property uniquely identifies the ServiceAccessPoint and provides an indication of the functionality that is managed. This functionality is described in more detail in the Description property of the object.
406The CreationClassName of the scoping System. The CreationClassName of the scoping System.
407The Name of the scoping System. The Name of the scoping System.
408CreationClassName 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. 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.
409CIM_ServiceAccessPoint represents the ability to utilize or invoke a Service. Access points represent that a Service is made available for other entities to use. CIM_ServiceAccessPoint represents the ability to utilize or invoke a Service. Access points represent that a Service is made available for other entities to use.
410A string that identifies this ProtocolEndpoint with either a port or an interface on a device. To ensure uniqueness, the Name property should be prepended or appended with information from the Type or OtherTypeDescription properties. The method selected is described in the NameFormat property of this class. A string that identifies this ProtocolEndpoint with either a port or an interface on a device. To ensure uniqueness, the Name property should be prepended or appended with information from the Type or OtherTypeDescription properties. The method selected is described in the NameFormat property of this class.
411NameFormat contains the naming heuristic that is selected to ensure that the value of the Name property is unique. For example, you might choose to prepend the name of the port or interface with the Type of ProtocolEndpoint (for example, IPv4) of this instance followed by an underscore. NameFormat contains the naming heuristic that is selected to ensure that the value of the Name property is unique. For example, you might choose to prepend the name of the port or interface with the Type of ProtocolEndpoint (for example, IPv4) of this instance followed by an underscore.
412Note: This property is deprecated in lieu of the ProtocolIFType enumeration. This deprecation was done to have better alignment between the IF-MIB of the IETF and this CIM class.
Deprecated description: ProtocolType is an enumeration that provides information to categorize and classify different instances of this class. For most instances, information in this enumeration and the definition of the subclass overlap. However, there are several cases where a specific subclass of ProtocolEndpoint is not required (for example, there is no Fibre Channel subclass of ProtocolEndpoint). Therefore, this property is needed to define the type of Endpoint.
Note: This property is deprecated in lieu of the ProtocolIFType enumeration. This deprecation was done to have better alignment between the IF-MIB of the IETF and this CIM class.
Deprecated description: ProtocolType is an enumeration that provides information to categorize and classify different instances of this class. For most instances, information in this enumeration and the definition of the subclass overlap. However, there are several cases where a specific subclass of ProtocolEndpoint is not required (for example, there is no Fibre Channel subclass of ProtocolEndpoint). Therefore, this property is needed to define the type of Endpoint.
413IPv4 IPv4
414IPv6 IPv6
415IPX IPX
416AppleTalk AppleTalk
417DECnet DECnet
418SNA SNA
419CONP CONP
420CLNP CLNP
421VINES VINES
422XNS XNS
423ATM ATM
424Frame Relay Frame Relay
425Ethernet Ethernet
426TokenRing TokenRing
427FDDI FDDI
428Infiniband Infiniband
429Fibre Channel Fibre Channel
430ISDN BRI Endpoint ISDN BRI Endpoint
431ISDN B Channel Endpoint ISDN B Channel Endpoint
432ISDN D Channel Endpoint ISDN D Channel Endpoint
433IPv4/v6 IPv4/v6
434BGP BGP
435OSPF OSPF
436MPLS MPLS
437UDP UDP
438TCP TCP
439ProtocolIFType is an enumeration that is synchronized with the IANA ifType MIB. The ifType MIB is maintained at the URL, http://www.iana.org/assignments/ianaiftype-mib. Also, additional values defined by the DMTF are included. The property is used to categorize and classify instances of the ProtocolEndpoint class. Note that if the ProtocolIFType is set to 1 (Other), then the type information should be provided in the OtherTypeDescription string property. ProtocolIFType is an enumeration that is synchronized with the IANA ifType MIB. The ifType MIB is maintained at the URL, http://www.iana.org/assignments/ianaiftype-mib. Also, additional values defined by the DMTF are included. The property is used to categorize and classify instances of the ProtocolEndpoint class. Note that if the ProtocolIFType is set to 1 (Other), then the type information should be provided in the OtherTypeDescription string property.
440Regular 1822 Regular 1822
441HDH 1822 HDH 1822
442DDN X.25 DDN X.25
443RFC877 X.25 RFC877 X.25
444Ethernet CSMA/CD Ethernet CSMA/CD
445ISO 802.3 CSMA/CD ISO 802.3 CSMA/CD
446ISO 802.4 Token Bus ISO 802.4 Token Bus
447ISO 802.5 Token Ring ISO 802.5 Token Ring
448ISO 802.6 MAN ISO 802.6 MAN
449StarLAN StarLAN
450Proteon 10Mbit Proteon 10Mbit
451Proteon 80Mbit Proteon 80Mbit
452HyperChannel HyperChannel
453LAP-B LAP-B
454SDLC SDLC
455DS1 DS1
456E1 E1
457Basic ISDN Basic ISDN
458Primary ISDN Primary ISDN
459Proprietary Point-to-Point Serial Proprietary Point-to-Point Serial
460PPP PPP
461Software Loopback Software Loopback
462EON EON
463Ethernet 3Mbit Ethernet 3Mbit
464NSIP NSIP
465SLIP SLIP
466Ultra Ultra
467DS3 DS3
468SIP SIP
469RS-232 RS-232
470Parallel Parallel
471ARCNet ARCNet
472ARCNet Plus ARCNet Plus
473MIO X.25 MIO X.25
474SONET SONET
475X.25 PLE X.25 PLE
476ISO 802.211c ISO 802.211c
477LocalTalk LocalTalk
478SMDS DXI SMDS DXI
479Frame Relay Service Frame Relay Service
480V.35 V.35
481HSSI HSSI
482HIPPI HIPPI
483Modem Modem
484AAL5 AAL5
485SONET Path SONET Path
486SONET VT SONET VT
487SMDS ICIP SMDS ICIP
488Proprietary Virtual/Internal Proprietary Virtual/Internal
489Proprietary Multiplexor Proprietary Multiplexor
490IEEE 802.12 IEEE 802.12
491HIPPI Interface HIPPI Interface
492Frame Relay Interconnect Frame Relay Interconnect
493ATM Emulated LAN for 802.3 ATM Emulated LAN for 802.3
494ATM Emulated LAN for 802.5 ATM Emulated LAN for 802.5
495ATM Emulated Circuit ATM Emulated Circuit
496Fast Ethernet (100BaseT) Fast Ethernet (100BaseT)
497ISDN ISDN
498V.11 V.11
499V.36 V.36
500G703 at 64K G703 at 64K
501G703 at 2Mb G703 at 2Mb
502QLLC QLLC
503Fast Ethernet 100BaseFX Fast Ethernet 100BaseFX
504Channel Channel
505IEEE 802.11 IEEE 802.11
506IBM 260/370 OEMI Channel IBM 260/370 OEMI Channel
507ESCON ESCON
508Data Link Switching Data Link Switching
509ISDN S/T Interface ISDN S/T Interface
510ISDN U Interface ISDN U Interface
511LAP-D LAP-D
512IP Switch IP Switch
513Remote Source Route Bridging Remote Source Route Bridging
514ATM Logical ATM Logical
515DS0 DS0
516DS0 Bundle DS0 Bundle
517BSC BSC
518Async Async
519Combat Net Radio Combat Net Radio
520ISO 802.5r DTR ISO 802.5r DTR
521Ext Pos Loc Report System Ext Pos Loc Report System
522AppleTalk Remote Access Protocol AppleTalk Remote Access Protocol
523Proprietary Connectionless Proprietary Connectionless
524ITU X.29 Host PAD ITU X.29 Host PAD
525ITU X.3 Terminal PAD ITU X.3 Terminal PAD
526Frame Relay MPI Frame Relay MPI
527ITU X.213 ITU X.213
528ADSL ADSL
529RADSL RADSL
530SDSL SDSL
531VDSL VDSL
532ISO 802.5 CRFP ISO 802.5 CRFP
533Myrinet Myrinet
534Voice Receive and Transmit Voice Receive and Transmit
535Voice Foreign Exchange Office Voice Foreign Exchange Office
536Voice Foreign Exchange Service Voice Foreign Exchange Service
537Voice Encapsulation Voice Encapsulation
538Voice over IP Voice over IP
539ATM DXI ATM DXI
540ATM FUNI ATM FUNI
541ATM IMA ATM IMA
542PPP Multilink Bundle PPP Multilink Bundle
543IP over CDLC IP over CDLC
544IP over CLAW IP over CLAW
545Stack to Stack Stack to Stack
546Virtual IP Address Virtual IP Address
547MPC MPC
548IP over ATM IP over ATM
549ISO 802.5j Fibre Token Ring ISO 802.5j Fibre Token Ring
550TDLC TDLC
551Gigabit Ethernet Gigabit Ethernet
552HDLC HDLC
553LAP-F LAP-F
554V.37 V.37
555X.25 MLP X.25 MLP
556X.25 Hunt Group X.25 Hunt Group
557Transp HDLC Transp HDLC
558Interleave Channel Interleave Channel
559FAST Channel FAST Channel
560IP (for APPN HPR in IP Networks) IP (for APPN HPR in IP Networks)
561CATV MAC Layer CATV MAC Layer
562CATV Downstream CATV Downstream
563CATV Upstream CATV Upstream
564Avalon 12MPP Switch Avalon 12MPP Switch
565Tunnel Tunnel
566Coffee Coffee
567Circuit Emulation Service Circuit Emulation Service
568ATM SubInterface ATM SubInterface
569Layer 2 VLAN using 802.1Q Layer 2 VLAN using 802.1Q
570Layer 3 VLAN using IP Layer 3 VLAN using IP
571Layer 3 VLAN using IPX Layer 3 VLAN using IPX
572Digital Power Line Digital Power Line
573Multimedia Mail over IP Multimedia Mail over IP
574DTM DTM
575DCN DCN
576IP Forwarding IP Forwarding
577MSDSL MSDSL
578IEEE 1394 IEEE 1394
579IF-GSN/HIPPI-6400 IF-GSN/HIPPI-6400
580DVB-RCC MAC Layer DVB-RCC MAC Layer
581DVB-RCC Downstream DVB-RCC Downstream
582DVB-RCC Upstream DVB-RCC Upstream
583ATM Virtual ATM Virtual
584MPLS Tunnel MPLS Tunnel
585SRP SRP
586Voice over ATM Voice over ATM
587Voice over Frame Relay Voice over Frame Relay
588ISDL ISDL
589Composite Link Composite Link
590SS7 Signaling Link SS7 Signaling Link
591Proprietary P2P Wireless Proprietary P2P Wireless
592Frame Forward Frame Forward
593RFC1483 Multiprotocol over ATM RFC1483 Multiprotocol over ATM
594USB USB
595IEEE 802.3ad Link Aggregate IEEE 802.3ad Link Aggregate
596BGP Policy Accounting BGP Policy Accounting
597FRF .16 Multilink FR FRF .16 Multilink FR
598H.323 Gatekeeper H.323 Gatekeeper
599H.323 Proxy H.323 Proxy
600Multi-Frequency Signaling Link Multi-Frequency Signaling Link
601HDSL-2 HDSL-2
602S-HDSL S-HDSL
603DS1 Facility Data Link DS1 Facility Data Link
604Packet over SONET/SDH Packet over SONET/SDH
605DVB-ASI Input DVB-ASI Input
606DVB-ASI Output DVB-ASI Output
607Power Line Power Line
608Non Facility Associated Signaling Non Facility Associated Signaling
609TR008 TR008
610GR303 RDT GR303 RDT
611GR303 IDT GR303 IDT
612ISUP ISUP
613Proprietary Wireless MAC Layer Proprietary Wireless MAC Layer
614Proprietary Wireless Downstream Proprietary Wireless Downstream
615Proprietary Wireless Upstream Proprietary Wireless Upstream
616HIPERLAN Type 2 HIPERLAN Type 2
617Proprietary Broadband Wireless Access Point to Mulipoint Proprietary Broadband Wireless Access Point to Mulipoint
618SONET Overhead Channel SONET Overhead Channel
619Digital Wrapper Overhead Channel Digital Wrapper Overhead Channel
620ATM Adaptation Layer 2 ATM Adaptation Layer 2
621Radio MAC Radio MAC
622ATM Radio ATM Radio
623Inter Machine Trunk Inter Machine Trunk
624MVL DSL MVL DSL
625Long Read DSL Long Read DSL
626Frame Relay DLCI Endpoint Frame Relay DLCI Endpoint
627ATM VCI Endpoint ATM VCI Endpoint
628Optical Channel Optical Channel
629Optical Transport Optical Transport
630Proprietary ATM Proprietary ATM
631Voice over Cable Voice over Cable
632TE Link TE Link
633Q.2931 Q.2931
634Virtual Trunk Group Virtual Trunk Group
635SIP Trunk Group SIP Trunk Group
636SIP Signaling SIP Signaling
637CATV Upstream Channel CATV Upstream Channel
638Econet Econet
639FSAN 155Mb PON FSAN 155Mb PON
640FSAN 622Mb PON FSAN 622Mb PON
641Transparent Bridge Transparent Bridge
642Line Group Line Group
643Voice E&M Feature Group Voice E&M Feature Group
644Voice FGD EANA Voice FGD EANA
645Voice DID Voice DID
646MPEG Transport MPEG Transport
6476To4 6To4
648GTP GTP
649Paradyne EtherLoop 1 Paradyne EtherLoop 1
650Paradyne EtherLoop 2 Paradyne EtherLoop 2
651Optical Channel Group Optical Channel Group
652HomePNA HomePNA
653GFP GFP
654ciscoISLvlan ciscoISLvlan
655actelisMetaLOOP actelisMetaLOOP
656Fcip Fcip
657IANA Reserved IANA Reserved
658802.11a 802.11a
659802.11b 802.11b
660802.11g 802.11g
661802.11h 802.11h
662NFS NFS
663CIFS CIFS
664DAFS DAFS
665WebDAV WebDAV
666HTTP HTTP
667FTP FTP
668NDMP NDMP
669Telnet Telnet
670SSH SSH
671SM CLP SM CLP
672SMTP SMTP
673LDAP LDAP
674RDP RDP
675HTTPS HTTPS
676A string that describes the type of ProtocolEndpoint when the Type property of this class (or any of its subclasses) is set to 1 (Other). This property should be set to null when the Type property is any value other than 1. A string that describes the type of ProtocolEndpoint when the Type property of this class (or any of its subclasses) is set to 1 (Other). This property should be set to null when the Type property is any value other than 1.
677A communication point from which data can be sent or received. ProtocolEndpoints link system or computer interfaces to LogicalNetworks. A communication point from which data can be sent or received. ProtocolEndpoints link system or computer interfaces to LogicalNetworks.
6782.15.0 2.15.0
679A label or identifier for the LAN Segment to which the Endpoint is connected. If the Endpoint is not currently active/connected or this information is not known, then LANID is NULL. A label or identifier for the LAN Segment to which the Endpoint is connected. If the Endpoint is not currently active/connected or this information is not known, then LANID is NULL.
680An indication of the kind of technology used on the LAN. This property is deprecated in lieu of ProtocolType, which is an enumeration inherited from ProtocolEndpoint and which includes the Values specified here. An indication of the kind of technology used on the LAN. This property is deprecated in lieu of ProtocolType, which is an enumeration inherited from ProtocolEndpoint and which includes the Values specified here.
681A free-form string that describes the type of technology used on the LAN when the value of the LANType property is equal to 1 (i.e., "Other"). This property is deprecated since its purpose overlaps with OtherTypeDescription, which which is inherited from ProtocolEndpoint. A free-form string that describes the type of technology used on the LAN when the value of the LANType property is equal to 1 (i.e., "Other"). This property is deprecated since its purpose overlaps with OtherTypeDescription, which which is inherited from ProtocolEndpoint.
682The principal unicast address used in communication with the LANEndpoint. The MAC address is formatted as twelve hexadecimal digits (e.g., "010203040506"), with each pair representing one of the six octets of the MAC address in "canonical" bit order according to RFC 2469. The principal unicast address used in communication with the LANEndpoint. The MAC address is formatted as twelve hexadecimal digits (e.g., "010203040506"), with each pair representing one of the six octets of the MAC address in "canonical" bit order according to RFC 2469.
683Other unicast addresses that may be used to communicate with the LANEndpoint. Other unicast addresses that may be used to communicate with the LANEndpoint.
684Multicast addresses to which the LANEndpoint listens. Multicast addresses to which the LANEndpoint listens.
685The largest information field that may be sent or received by the LANEndpoint. The largest information field that may be sent or received by the LANEndpoint.
686Bits Bits
687A communication endpoint which, when its associated interface device is connected to a LAN, may send and receive data frames. LANEndpoints include Ethernet, Token Ring and FDDI interfaces. A communication endpoint which, when its associated interface device is connected to a LAN, may send and receive data frames. LANEndpoints include Ethernet, Token Ring and FDDI interfaces.
6882.7.0 2.7.0
6896to4 tunnel interface 6to4 tunnel interface
6906to4 global settings associated with this interface 6to4 global settings associated with this interface
691This class represents per-interface 6to4 Configuration settings. This class represents per-interface 6to4 Configuration settings.
692Indicates whether DNS64 is enabled or disabled Indicates whether DNS64 is enabled or disabled
693If true, do not send quad-A query before sending A query If true, do not send quad-A query before sending A query
694Delay in ms between sending quad-A query and A query Delay in ms between sending quad-A query and A query
695If true, return synthesized quad-A response even if A record was found If true, return synthesized quad-A response even if A record was found
696Mapping of IPv4 address ranges to IPv4 prefixes Mapping of IPv4 address ranges to IPv4 prefixes
697List of addresses that DNS64 should not translate List of addresses that DNS64 should not translate
698Name of interface on which to send outgoing queries Name of interface on which to send outgoing queries
699Names of interfaces on which to accept incoming queries Names of interfaces on which to accept incoming queries
700Enable DNS64 Enable DNS64
701Disable DNS64 Disable DNS64
702Reset DNS64 configuration Reset DNS64 configuration
703Configuration settings for DNS64 Configuration settings for DNS64
704The scoping System\'s CreationClassName. The scoping System\'s CreationClassName.
705The scoping System\'s Name. The scoping System\'s Name.
706An address or other identifying information to uniquely name the LogicalDevice. An address or other identifying information to uniquely name the LogicalDevice.
707Boolean indicating that the Device can be power managed. The use of this property has been deprecated. Instead, the existence of an associated PowerManagementCapabilities class (associated using the ElementCapabilities relationhip) indicates that power management is supported. Boolean indicating that the Device can be power managed. The use of this property has been deprecated. Instead, the existence of an associated PowerManagementCapabilities class (associated using the ElementCapabilities relationhip) indicates that power management is supported.
708An enumerated array describing the power management capabilities of the Device. The use of this property has been deprecated. Instead, the PowerCapabilites property in an associated PowerManagementCapabilities class should be used. An enumerated array describing the power management capabilities of the Device. The use of this property has been deprecated. Instead, the PowerCapabilites property in an associated PowerManagementCapabilities class should be used.
709Power Saving Modes Entered Automatically Power Saving Modes Entered Automatically
710Power State Settable Power State Settable
711Power Cycling Supported Power Cycling Supported
712Timed Power On Supported Timed Power On Supported
713The primary availability and status of the Device. (Additional status information can be specified using the Additional Availability array property.) For example, the Availability property indicates that the Device is running and has full power (value=3), or is in a warning (4), test (5), degraded (10) or power save state (values 13-15 and 17). Regarding the Power Save states, these are defined as follows: Value 13 ("Power Save - Unknown") indicates that the Device is known to be in a power save mode, but its exact status in this mode is unknown; 14 ("Power Save - Low Power Mode") indicates that the Device is in a power save state but still functioning, and may exhibit degraded performance; 15 ("Power Save - Standby") describes that the Device is not functioning but could be brought to full power \'quickly\'; and value 17 ("Power Save - Warning") indicates that the Device is in a warning state, though also in a power save mode. The primary availability and status of the Device. (Additional status information can be specified using the Additional Availability array property.) For example, the Availability property indicates that the Device is running and has full power (value=3), or is in a warning (4), test (5), degraded (10) or power save state (values 13-15 and 17). Regarding the Power Save states, these are defined as follows: Value 13 ("Power Save - Unknown") indicates that the Device is known to be in a power save mode, but its exact status in this mode is unknown; 14 ("Power Save - Low Power Mode") indicates that the Device is in a power save state but still functioning, and may exhibit degraded performance; 15 ("Power Save - Standby") describes that the Device is not functioning but could be brought to full power \'quickly\'; and value 17 ("Power Save - Warning") indicates that the Device is in a warning state, though also in a power save mode.
714Running/Full Power Running/Full Power
715Warning Warning
716Power Off Power Off
717Off Line Off Line
718Off Duty Off Duty
719Not Installed Not Installed
720Install Error Install Error
721Power Save - Unknown Power Save - Unknown
722Power Save - Low Power Mode Power Save - Low Power Mode
723Power Save - Standby Power Save - Standby
724Power Cycle Power Cycle
725Power Save - Warning Power Save - Warning
726Paused Paused
727Not Ready Not Ready
728Not Configured Not Configured
729Quiesced Quiesced
730The StatusInfo property indicates whether the Logical Device is in an enabled (value = 3), disabled (value = 4) or some other (1) or unknown (2) state. If this property does not apply to the LogicalDevice, the value, 5 ("Not Applicable"), should be used. StatusInfo has been deprecated in lieu of a more clearly named property with additional enumerated values (EnabledState), that is inherited from ManagedSystemElement.
If a Device is ("Enabled")(value=3), it has been powered up, and is configured and operational. The Device may or may not be functionally active, depending on whether its Availability (or AdditionalAvailability) indicate that it is ("Running/Full Power")(value=3) or ("Off line") (value=8). In an enabled but offline mode, a Device may be performing out-of-band requests, such as running Diagnostics. If ("Disabled") StatusInfo value=4), a Device can only be "enabled" or powered off. In a personal computer environment, ("Disabled") means that the Device\'s driver is not available in the stack. In other environments, a Device can be disabled by removing its configuration file. A disabled device is physically present in a System and consuming resources, but can not be communicated with until a load of a driver, a load of a configuration file or some other "enabling" activity has occurred.
The StatusInfo property indicates whether the Logical Device is in an enabled (value = 3), disabled (value = 4) or some other (1) or unknown (2) state. If this property does not apply to the LogicalDevice, the value, 5 ("Not Applicable"), should be used. StatusInfo has been deprecated in lieu of a more clearly named property with additional enumerated values (EnabledState), that is inherited from ManagedSystemElement.
If a Device is ("Enabled")(value=3), it has been powered up, and is configured and operational. The Device may or may not be functionally active, depending on whether its Availability (or AdditionalAvailability) indicate that it is ("Running/Full Power")(value=3) or ("Off line") (value=8). In an enabled but offline mode, a Device may be performing out-of-band requests, such as running Diagnostics. If ("Disabled") StatusInfo value=4), a Device can only be "enabled" or powered off. In a personal computer environment, ("Disabled") means that the Device\'s driver is not available in the stack. In other environments, a Device can be disabled by removing its configuration file. A disabled device is physically present in a System and consuming resources, but can not be communicated with until a load of a driver, a load of a configuration file or some other "enabling" activity has occurred.
731LastErrorCode captures the last error code reported by the LogicalDevice. LastErrorCode captures the last error code reported by the LogicalDevice.
732ErrorDescription is a free-form string supplying more information about the error recorded in LastErrorCode, and information on any corrective actions that may be taken. ErrorDescription is a free-form string supplying more information about the error recorded in LastErrorCode, and information on any corrective actions that may be taken.
733ErrorCleared is a boolean property indicating that the error reported in LastErrorCode is now cleared. ErrorCleared is a boolean property indicating that the error reported in LastErrorCode is now cleared.
734OtherIdentifyingInfo captures additional data, beyond DeviceID information, that could be used to identify a LogicalDevice. One example would be to hold the Operating System\'s user friendly name for the Device in this property. OtherIdentifyingInfo captures additional data, beyond DeviceID information, that could be used to identify a LogicalDevice. One example would be to hold the Operating System\'s user friendly name for the Device in this property.
735The number of consecutive hours that this Device has been powered, since its last power cycle. The number of consecutive hours that this Device has been powered, since its last power cycle.
736Hours Hours
737The total number of hours that this Device has been powered. The total number of hours that this Device has been powered.
738An array of free-form strings providing explanations and details behind the entries in the OtherIdentifyingInfo array. Note, each entry of this array is related to the entry in OtherIdentifyingInfo that is located at the same index. An array of free-form strings providing explanations and details behind the entries in the OtherIdentifyingInfo array. Note, each entry of this array is related to the entry in OtherIdentifyingInfo that is located at the same index.
739Additional availability and status of the Device, beyond that specified in the Availability property. The Availability property denotes the primary status and availability of the Device. In some cases, this will not be sufficient to denote the complete status of the Device. In those cases, the AdditionalAvailability property can be used to provide further information. For example, a Device\'s primary Availability may be "Off line" (value=8), but it may also be in a low power state (AdditonalAvailability value=14), or the Device could be running Diagnostics (AdditionalAvailability value=5, "In Test"). Additional availability and status of the Device, beyond that specified in the Availability property. The Availability property denotes the primary status and availability of the Device. In some cases, this will not be sufficient to denote the complete status of the Device. In those cases, the AdditionalAvailability property can be used to provide further information. For example, a Device\'s primary Availability may be "Off line" (value=8), but it may also be in a low power state (AdditonalAvailability value=14), or the Device could be running Diagnostics (AdditionalAvailability value=5, "In Test").
740The MaxQuiesceTime property has been deprecated. When evaluating the use of Quiesce, it was determine that this single property is not adequate for describing when a device will automatically exit a quiescent state. In fact, the most likely scenario for a device to exit a quiescent state was determined to be based on the number of outstanding requests queued rather than on a maximum time. This will be re-evaluated and repositioned later.
Maximum time in milliseconds, that a Device can run in a "Quiesced" state. A Device\'s state is defined in its Availability and AdditionalAvailability properties, where "Quiesced" is conveyed by the value 21. What occurs at the end of the time limit is device-specific. The Device may unquiesce, may offline or take other action. A value of 0 indicates that a Device can remain quiesced indefinitely.
The MaxQuiesceTime property has been deprecated. When evaluating the use of Quiesce, it was determine that this single property is not adequate for describing when a device will automatically exit a quiescent state. In fact, the most likely scenario for a device to exit a quiescent state was determined to be based on the number of outstanding requests queued rather than on a maximum time. This will be re-evaluated and repositioned later.
Maximum time in milliseconds, that a Device can run in a "Quiesced" state. A Device\'s state is defined in its Availability and AdditionalAvailability properties, where "Quiesced" is conveyed by the value 21. What occurs at the end of the time limit is device-specific. The Device may unquiesce, may offline or take other action. A value of 0 indicates that a Device can remain quiesced indefinitely.
741MilliSeconds MilliSeconds
742Sets the power state of the Device. The use of this method has been deprecated. Instead, use the SetPowerState method in the associated PowerManagementService class. Sets the power state of the Device. The use of this method has been deprecated. Instead, use the SetPowerState method in the associated PowerManagementService class.
743The power state to set. The power state to set.
744Full Power Full Power
745Power Save - Other Power Save - Other
746Time indicates when the power state should be set, either as a regular date-time value or as an interval value (where the interval begins when the method invocation is received. Time indicates when the power state should be set, either as a regular date-time value or as an interval value (where the interval begins when the method invocation is received.
747Requests a reset of the LogicalDevice. The return value should be 0 if the request was successfully executed, 1 if the request is not supported and some other value if an error occurred. In a subclass, the set of possible return codes could be specified, using a ValueMap qualifier on the method. The strings to which the ValueMap contents are \'translated\' may also be specified in the subclass as a Values array qualifier. Requests a reset of the LogicalDevice. The return value should be 0 if the request was successfully executed, 1 if the request is not supported and some other value if an error occurred. In a subclass, the set of possible return codes could be specified, using a ValueMap qualifier on the method. The strings to which the ValueMap contents are \'translated\' may also be specified in the subclass as a Values array qualifier.
748The EnableDevice method has been deprecated in lieu of the more general RequestStateChange method that directly overlaps with the functionality provided by this method.
Requests that the LogicalDevice be enabled ("Enabled" input parameter = TRUE) or disabled (= FALSE). If successful, the Device\'s StatusInfo/EnabledState properties should reflect the desired state (enabled/disabled). Note that this method\'s function overlaps with the RequestedState property. RequestedState was added to the model to maintain a record (i.e., a persisted value) of the last state request. Invoking the EnableDevice method should set the RequestedState property appropriately.
The return code should be 0 if the request was successfully executed, 1 if the request is not supported and some other value if an error occurred. In a subclass, the set of possible return codes could be specified, using a ValueMap qualifier on the method. The strings to which the ValueMap contents are \'translated\' may also be specified in the subclass as a Values array qualifier.
The EnableDevice method has been deprecated in lieu of the more general RequestStateChange method that directly overlaps with the functionality provided by this method.
Requests that the LogicalDevice be enabled ("Enabled" input parameter = TRUE) or disabled (= FALSE). If successful, the Device\'s StatusInfo/EnabledState properties should reflect the desired state (enabled/disabled). Note that this method\'s function overlaps with the RequestedState property. RequestedState was added to the model to maintain a record (i.e., a persisted value) of the last state request. Invoking the EnableDevice method should set the RequestedState property appropriately.
The return code should be 0 if the request was successfully executed, 1 if the request is not supported and some other value if an error occurred. In a subclass, the set of possible return codes could be specified, using a ValueMap qualifier on the method. The strings to which the ValueMap contents are \'translated\' may also be specified in the subclass as a Values array qualifier.
749If TRUE enable the device, if FALSE disable the device. If TRUE enable the device, if FALSE disable the device.
750The OnlineDevice method has been deprecated in lieu of the more general RequestStateChange method that directly overlaps with the functionality provided by this method.
Requests that the LogicalDevice be brought online ("Online" input parameter = TRUE) or taken offline (= FALSE). "Online" indicates that the Device is ready to accept requests, and is operational and fully functioning. In this case, the Device\'s Availability property would be set to a value of 3 ("Running/Full Power"). "Offline" indicates that a Device is powered up and operational, but not processing functional requests. In an offline state, a Device may be capable of running diagnostics or generating operational alerts. For example, when the "Offline" button is pushed on a Printer, the Device is no longer available to process print jobs, but could be available for diagnostics or maintenance.
If this method is successful, the Device\'s Availability and AdditionalAvailability properties should reflect the updated status. If a failure occurs trying to bring the Device online or offline, it should remain in its current state. IE, the request, if unsuccessful, should not leave the Device in an indeterminate state. When bringing a Device back "Online", from an "Offline" mode, the Device should be restored to its last "Online" state, if at all possible. Only a Device that has an EnabledState/StatusInfo of "Enabled" and has been configured can be brought online or taken offline.
OnlineDevice should return 0 if successful, 1 if the request is not supported at all, 2 if the request is not supported due to the current state of the Device, and some other value if any other error occurred. In a subclass, the set of possible return codes could be specified, using a ValueMap qualifier on the method. The strings to which the ValueMap contents are \'translated\' may also be specified in the subclass as a Values array qualifier.
Note that this method\'s function overlaps with the RequestedState property. RequestedState was added to the model to maintain a record (i.e., a persisted value) of the last state request. Invoking the OnlineDevice method should set the RequestedState property appropriately.
The OnlineDevice method has been deprecated in lieu of the more general RequestStateChange method that directly overlaps with the functionality provided by this method.
Requests that the LogicalDevice be brought online ("Online" input parameter = TRUE) or taken offline (= FALSE). "Online" indicates that the Device is ready to accept requests, and is operational and fully functioning. In this case, the Device\'s Availability property would be set to a value of 3 ("Running/Full Power"). "Offline" indicates that a Device is powered up and operational, but not processing functional requests. In an offline state, a Device may be capable of running diagnostics or generating operational alerts. For example, when the "Offline" button is pushed on a Printer, the Device is no longer available to process print jobs, but could be available for diagnostics or maintenance.
If this method is successful, the Device\'s Availability and AdditionalAvailability properties should reflect the updated status. If a failure occurs trying to bring the Device online or offline, it should remain in its current state. IE, the request, if unsuccessful, should not leave the Device in an indeterminate state. When bringing a Device back "Online", from an "Offline" mode, the Device should be restored to its last "Online" state, if at all possible. Only a Device that has an EnabledState/StatusInfo of "Enabled" and has been configured can be brought online or taken offline.
OnlineDevice should return 0 if successful, 1 if the request is not supported at all, 2 if the request is not supported due to the current state of the Device, and some other value if any other error occurred. In a subclass, the set of possible return codes could be specified, using a ValueMap qualifier on the method. The strings to which the ValueMap contents are \'translated\' may also be specified in the subclass as a Values array qualifier.
Note that this method\'s function overlaps with the RequestedState property. RequestedState was added to the model to maintain a record (i.e., a persisted value) of the last state request. Invoking the OnlineDevice method should set the RequestedState property appropriately.
751If TRUE, take the device online, if FALSE, take the device OFFLINE. If TRUE, take the device online, if FALSE, take the device OFFLINE.
752The QuiesceDevice method has been deprecated in lieu of the more general RequestStateChange method that directly overlaps with the functionality provided by this method.
Requests that the LogicalDevice cleanly cease all current activity ("Quiesce" input parameter = TRUE) or resume activity (= FALSE). For this method to quiesce a Device, that Device should have an Availability (or Additional Availability) of "Running/Full Power" (value=3) and an EnabledStatus/StatusInfo of "Enabled". For example, if quiesced, a Device may then be offlined for diagnostics, or disabled for power off and hot swap. For the method to "unquiesce" a Device, that Device should have an Availability (or AdditionalAvailability) of "Quiesced" (value=21) and an EnabledStatus/StatusInfo of "Enabled". In this case, the Device would be returned to an "Enabled" and "Running/Full Power" status.
The method\'s return code should indicate the success or failure of the quiesce. It should return 0 if successful, 1 if the request is not supported at all, 2 if the request is not supported due to the current state of the Device, and some other value if any other error occurred. In a subclass, the set of possible return codes could be specified, using a ValueMap qualifier on the method. The strings to which the ValueMap contents are \'translated\' may also be specified in the subclass as a Values array qualifier.
The QuiesceDevice method has been deprecated in lieu of the more general RequestStateChange method that directly overlaps with the functionality provided by this method.
Requests that the LogicalDevice cleanly cease all current activity ("Quiesce" input parameter = TRUE) or resume activity (= FALSE). For this method to quiesce a Device, that Device should have an Availability (or Additional Availability) of "Running/Full Power" (value=3) and an EnabledStatus/StatusInfo of "Enabled". For example, if quiesced, a Device may then be offlined for diagnostics, or disabled for power off and hot swap. For the method to "unquiesce" a Device, that Device should have an Availability (or AdditionalAvailability) of "Quiesced" (value=21) and an EnabledStatus/StatusInfo of "Enabled". In this case, the Device would be returned to an "Enabled" and "Running/Full Power" status.
The method\'s return code should indicate the success or failure of the quiesce. It should return 0 if successful, 1 if the request is not supported at all, 2 if the request is not supported due to the current state of the Device, and some other value if any other error occurred. In a subclass, the set of possible return codes could be specified, using a ValueMap qualifier on the method. The strings to which the ValueMap contents are \'translated\' may also be specified in the subclass as a Values array qualifier.
753If set to TRUE then cleanly cease all activity, if FALSE resume activity. If set to TRUE then cleanly cease all activity, if FALSE resume activity.
754Requests that the Device capture its current configuration, setup and/or state information in a backing store. The goal would be to use this information at a later time (via the RestoreProperties method), to return a Device to its present "condition". This method may not be supported by all Devices. The method should return 0 if successful, 1 if the request is not supported, and some other value if any other error occurred. In a subclass, the set of possible return codes could be specified, using a ValueMap qualifier on the method. The strings to which the ValueMap contents are \'translated\' may also be specified in the subclass as a Values array qualifier. Requests that the Device capture its current configuration, setup and/or state information in a backing store. The goal would be to use this information at a later time (via the RestoreProperties method), to return a Device to its present "condition". This method may not be supported by all Devices. The method should return 0 if successful, 1 if the request is not supported, and some other value if any other error occurred. In a subclass, the set of possible return codes could be specified, using a ValueMap qualifier on the method. The strings to which the ValueMap contents are \'translated\' may also be specified in the subclass as a Values array qualifier.
755Requests that the Device re-establish its configuration, setup and/or state information from a backing store. The intent is to capture this information at an earlier time (via the SaveProperties method), and use it to return a Device to this earlier "condition". This method may not be supported by all Devices. The method should return 0 if successful, 1 if the request is not supported, and some other value if any other error occurred. In a subclass, the set of possible return codes could be specified, using a ValueMap qualifier on the method. The strings to which the ValueMap contents are \'translated\' may also be specified in the subclass as a Values array qualifier. Requests that the Device re-establish its configuration, setup and/or state information from a backing store. The intent is to capture this information at an earlier time (via the SaveProperties method), and use it to return a Device to this earlier "condition". This method may not be supported by all Devices. The method should return 0 if successful, 1 if the request is not supported, and some other value if any other error occurred. In a subclass, the set of possible return codes could be specified, using a ValueMap qualifier on the method. The strings to which the ValueMap contents are \'translated\' may also be specified in the subclass as a Values array qualifier.
756An abstraction or emulation of a hardware entity, that may or may not be Realized in physical hardware. Any characteristics of a LogicalDevice that are used to manage its operation or configuration are contained in, or associated with, the LogicalDevice object. Examples of the operational properties of a Printer would be paper sizes supported, or detected errors. Examples of the configuration properties of a Sensor Device would be threshold settings. Various configurations could exist for a LogicalDevice. These configurations could be contained in Setting objects and associated with the LogicalDevice. An abstraction or emulation of a hardware entity, that may or may not be Realized in physical hardware. Any characteristics of a LogicalDevice that are used to manage its operation or configuration are contained in, or associated with, the LogicalDevice object. Examples of the operational properties of a Printer would be paper sizes supported, or detected errors. Examples of the configuration properties of a Sensor Device would be threshold settings. Various configurations could exist for a LogicalDevice. These configurations could be contained in Setting objects and associated with the LogicalDevice.
7572.8.0 2.8.0
758The bandwidth of the Port in Bits per Second. The bandwidth of the Port in Bits per Second.
759Bits per Second Bits per Second
760The maximum bandwidth of the Port in Bits per Second. The maximum bandwidth of the Port in Bits per Second.
761The requested bandwidth of the Port in Bits per Second. The actual bandwidth is reported in LogicalPort.Speed. The requested bandwidth of the Port in Bits per Second. The actual bandwidth is reported in LogicalPort.Speed.
762In some circumstances, a LogicalPort might be identifiable as a front end or back end port. An example of this situation would be a storage array that might have back end ports to communicate with disk drives and front end ports to communicate with hosts. If there is no restriction on the use of the port, then the value should be set to \'not restricted\'. In some circumstances, a LogicalPort might be identifiable as a front end or back end port. An example of this situation would be a storage array that might have back end ports to communicate with disk drives and front end ports to communicate with hosts. If there is no restriction on the use of the port, then the value should be set to \'not restricted\'.
763Front-end only Front-end only
764Back-end only Back-end only
765Not restricted Not restricted
766PortType is defined to force consistent naming of the \'type\' property in subclasses and to guarantee unique enum values for all instances of NetworkPort. When set to 1 ("Other"), related property OtherPortType contains a string description of the type of port. A range of values, DMTF_Reserved, has been defined that allows subclasses to override and define their specific types of ports. PortType is defined to force consistent naming of the \'type\' property in subclasses and to guarantee unique enum values for all instances of NetworkPort. When set to 1 ("Other"), related property OtherPortType contains a string description of the type of port. A range of values, DMTF_Reserved, has been defined that allows subclasses to override and define their specific types of ports.
767Describes the type of module, when PortType is set to 1 ("Other"). Describes the type of module, when PortType is set to 1 ("Other").
768The abstraction of a port or connection point of a Device. This object should be instantiated when the Port has independent management characteristics from the Device that includes it. Examples are a Fibre Channel Port and a USB Port. The abstraction of a port or connection point of a Device. This object should be instantiated when the Port has independent management characteristics from the Device that includes it. Examples are a Fibre Channel Port and a USB Port.
769The current bandwidth of the Port in Bits per Second. For ports that vary in bandwidth or for those where no accurate estimation can be made, this property should contain the nominal bandwidth. The current bandwidth of the Port in Bits per Second. For ports that vary in bandwidth or for those where no accurate estimation can be made, this property should contain the nominal bandwidth.
770Note: The use of this property is deprecated in lieu of CIM_LogicalPort.PortType.
Deprecated description: The type of module, when PortType is set to 1 ("Other".)
Note: The use of this property is deprecated in lieu of CIM_LogicalPort.PortType.
Deprecated description: The type of module, when PortType is set to 1 ("Other".)
771NetworkPorts are often numbered relative to either a logical module or a network element. NetworkPorts are often numbered relative to either a logical module or a network element.
772An enumeration of the types of links. When set to 1 ("Other"), the related property OtherLinkTechnology contains a string description of the type of link. An enumeration of the types of links. When set to 1 ("Other"), the related property OtherLinkTechnology contains a string description of the type of link.
773IB IB
774FC FC
775Token Ring Token Ring
776Infrared Infrared
777BlueTooth BlueTooth
778Wireless LAN Wireless LAN
779A string value that describes LinkTechnology when it is set to 1, "Other". A string value that describes LinkTechnology when it is set to 1, "Other".
780PermanentAddress defines the network address that is hardcoded into a port. This \'hardcoded\' address can be changed using a firmware upgrade or a software configuration. When this change is made, the field should be updated at the same time. PermanentAddress should be left blank if no \'hardcoded\' address exists for the NetworkAdapter. PermanentAddress defines the network address that is hardcoded into a port. This \'hardcoded\' address can be changed using a firmware upgrade or a software configuration. When this change is made, the field should be updated at the same time. PermanentAddress should be left blank if no \'hardcoded\' address exists for the NetworkAdapter.
781An array of strings that indicates the network addresses for the port. An array of strings that indicates the network addresses for the port.
782Boolean that indicates that the port is operating in full duplex mode. Boolean that indicates that the port is operating in full duplex mode.
783A Boolean that indicates whether the NetworkPort is capable of automatically determining the speed or other communications characteristics of the attached network media. A Boolean that indicates whether the NetworkPort is capable of automatically determining the speed or other communications characteristics of the attached network media.
784The maximum transmission unit (MTU) that can be supported. The maximum transmission unit (MTU) that can be supported.
785Bytes Bytes
786The active or negotiated maximum transmission unit (MTU) that can be supported. The active or negotiated maximum transmission unit (MTU) that can be supported.
787NetworkPort is the logical representation of network communications hardware such as a physical connector and the setup or operation of the network chips, at the lowest layers of a network stack. NetworkPort is the logical representation of network communications hardware such as a physical connector and the setup or operation of the network chips, at the lowest layers of a network stack.
788Network interface on which DNS queries are sent or received Network interface on which DNS queries are sent or received
789DNS64 settings associated with this interface DNS64 settings associated with this interface
790Association between DNS64 settings and accept/send interfaces Association between DNS64 settings and accept/send interfaces
791Number of successful AAAA queries Number of successful AAAA queries
792Number of failed AAAA queries Number of failed AAAA queries
793Number of synthesized AAAA queries Number of synthesized AAAA queries
794Number of translated PTR queries Number of translated PTR queries
795Number of succeeded non-AAAA queries Number of succeeded non-AAAA queries
796Number of failed non-AAAA queries Number of failed non-AAAA queries
797Query counters for DNS64 Query counters for DNS64
798Configuration type of this instance Configuration type of this instance
799Local Local
800GroupPolicy GroupPolicy
801ProfileGP ProfileGP
802Type of the interface Type of the interface
803Client Client
804Server Server
805State of the interface State of the interface
806Default Default
807Authentication mode Authentication mode
808None None
809Certificates Certificates
810Url on which the server interface listens for HTTP(S) requests OR Url to which the client interface sends HTTP(S) requests Url on which the server interface listens for HTTP(S) requests OR Url to which the client interface sends HTTP(S) requests
811Friendly name of the profile Friendly name of the profile
812Indicates whether the profile is active or not Indicates whether the profile is active or not
813Toggles Strong Certificate revocation list checking Toggles Strong Certificate revocation list checking
814Policy store in which this configuration object is stored Policy store in which this configuration object is stored
815Manually activate specified IP-HTTPs profile Manually activate specified IP-HTTPs profile
816Disable manual activation of IP-HTTPs profile Disable manual activation of IP-HTTPs profile
817Add HTTP SSL certificate Add HTTP SSL certificate
818Remove all HTTP SSL certificates Remove all HTTP SSL certificates
819Rename IP-HTTPs profile Rename IP-HTTPs profile
820Reset IP-HTTPs configuration Reset IP-HTTPs configuration
821Configuration settings for IP-HTTPs Configuration settings for IP-HTTPs
822IP-HTTPs tunnel interface IP-HTTPs tunnel interface
823IP-HTTPs global settings associated with this interface IP-HTTPs global settings associated with this interface
824Status of the IP-HTTPs interface Status of the IP-HTTPs interface
825Last error code for the IP-HTTPs interface Last error code for the IP-HTTPs interface
826This class represents per-interface IP-HTTPs Configuration settings. This class represents per-interface IP-HTTPs Configuration settings.
827PolicyStore property defines the store to retrieve the ISATAP configuration policy. PolicyStore property defines the store to retrieve the ISATAP configuration policy.
828Describes the ISATAP service state. One of the following values: disabled, enabled or default. Describes the ISATAP service state. One of the following values: disabled, enabled or default.
829Name of the ISATAP router. Name of the ISATAP router.
830The state of the ISATAP resolution. One of the following values: disabled, enabled, default. The state of the ISATAP resolution. One of the following values: disabled, enabled, default.
831Reset the ISATAP configuration. Reset the ISATAP configuration.
832This class represents global ISATAP Configuration shared across all ISATAP interfaces. This class represents global ISATAP Configuration shared across all ISATAP interfaces.
833ISATAP tunnel interface ISATAP tunnel interface
834ISATAP global settings associated with this interface ISATAP global settings associated with this interface
835This class represents per-interface ISATAP Configuration settings. This class represents per-interface ISATAP Configuration settings.
836Name of this instance of WinNAT Name of this instance of WinNAT
837Store in which this configuration object is stored Store in which this configuration object is stored
838PersistentStore PersistentStore
839ActiveStore ActiveStore
840Indicates whether NAT is enabled or disabled Indicates whether NAT is enabled or disabled
841Names of inbound interfaces Names of inbound interfaces
842Names of outbound interfaces Names of outbound interfaces
843Mapping of IPv4 address ranges to IPv6 prefixes Mapping of IPv4 address ranges to IPv6 prefixes
844Dedicated IPv4 address pool and port range Dedicated IPv4 address pool and port range
845Idle timout for established TCP sessions Idle timout for established TCP sessions
846Enable NAT64 Enable NAT64
847Disable NAT64 Disable NAT64
848Configuration settings for NAT Configuration settings for NAT
849Network interface on which NAT64 operates Network interface on which NAT64 operates
850NAT64 settings associated with this interface NAT64 settings associated with this interface
851Association between NAT64 settings and inbound/outbound interfaces Association between NAT64 settings and inbound/outbound interfaces
852Transport protocol being translated Transport protocol being translated
853Inbound address and port Inbound address and port
854Outbound address and port Outbound address and port
855NAT outbound address and port NAT outbound address and port
856Current active sessions for NAT Current active sessions for NAT
857PolicyStore property defines the store to retrieve the Teredo configuration policy. PolicyStore property defines the store to retrieve the Teredo configuration policy.
858Describes the Teredo service. One of the following values: disabled, client, enterpriseclient, natawareclient, server, default. Describes the Teredo service. One of the following values: disabled, client, enterpriseclient, natawareclient, server, default.
859relay relay
860client client
861server server
862enterpriseclient enterpriseclient
863natawareclient natawareclient
864Describes the name or IPv4 address of the Teredo server. Describes the name or IPv4 address of the Teredo server.
865Client refresh interval (in seconds). Client refresh interval (in seconds).
866Client's UDP port. Client's UDP port.
867IPv4 address of the server virtual ip. Not applicable if running as teredo client. IPv4 address of the server virtual ip. Not applicable if running as teredo client.
868This policy setting allows you to set Teredo to be ready to communicate, a process referred to as qualification. By default, Teredo enters a dormant state when not in use. The qualification process brings it out of a dormant state. This policy setting allows you to set Teredo to be ready to communicate, a process referred to as qualification. By default, Teredo enters a dormant state when not in use. The qualification process brings it out of a dormant state.
869If enabled, bypasses the tunnel miniport and IPv4 routing layer for high throughput on the Teredo Relay functionality of the Teredo Server. If enabled, bypasses the tunnel miniport and IPv4 routing layer for high throughput on the Teredo Relay functionality of the Teredo Server.
870Reset the Teredo configuration. Reset the Teredo configuration.
871NetTeredoConfiguration represents global Teredo configuration shared across all Teredo interfaces. NetTeredoConfiguration represents global Teredo configuration shared across all Teredo interfaces.
872Teredo tunnel interface Teredo tunnel interface
873Teredo global settings associated with this interface Teredo global settings associated with this interface
874Specifies the state of the teredo interface Specifies the state of the teredo interface
875Specifies the error of the teredo interface Specifies the error of the teredo interface
876This class represents per-interface Teredo Configuration settings. This class represents per-interface Teredo Configuration settings.
0x1Performing operation %1 on Target %2 Performing operation %1 on Target %2
0x2Enabling site %1 for DirectAccess connectivity Enabling site %1 for DirectAccess connectivity
0x3Disabling manual site selection for DirectAccess connectivity Disabling manual site selection for DirectAccess connectivity
0x4Invalid parameter: %1. Invalid parameter: %1.
0x5Latency must be less than 1000ms. Latency must be less than 1000ms.
0x6Each item in %1 must be of the form \"%2\". Each item in %1 must be of the form \"%2\".
0x7Only one %1 is supported. Only one %1 is supported.
0x8The specified interface was not found on the system. The specified interface was not found on the system.
0x9%1 must be a valid IPv6 prefix. %1 must be a valid IPv6 prefix.
0xAFailed to notify IP Helper Service of changes to local configuration. Failed to notify IP Helper Service of changes to local configuration.
0xBThis functionality is not supported on client SKUs. This functionality is not supported on client SKUs.
0xCThe WinNAT service is stopped. Please start the service to display configuration from active store. The WinNAT service is stopped. Please start the service to display configuration from active store.
0xDFailed to start WinNAT service. Failed to start WinNAT service.
0xE%1 cannot contain a semicolon. %1 cannot contain a semicolon.
0xFOnly the following prefix lengths are allowed for NAT64: 32, 40, 48, 56, 64, and 96. Only the following prefix lengths are allowed for NAT64: 32, 40, 48, 56, 64, and 96.
0x10Ports in port range must be in the range 1024-65535. Ports in port range must be in the range 1024-65535.
0x11To specify %1, %2 must also have a valid value. To specify %1, %2 must also have a valid value.
0x12%1 and %2 cannot be specified at the same time. %1 and %2 cannot be specified at the same time.
0x13Must specify required parameter %1. Must specify required parameter %1.
0x14Either %1 or %2 must be specified. Either %1 or %2 must be specified.
0x15The configuration has been corrupted. The configuration has been corrupted.
0x16Cannot create or modify instances in the specified policy store. Cannot create or modify instances in the specified policy store.
0x17The specified %1 is already in use. The specified %1 is already in use.
0x18None of the specified entry point ranges match the entry point IP address. None of the specified entry point ranges match the entry point IP address.
0x19The specified entry point ranges are not the best match for the entry point IP address. The specified entry point ranges are not the best match for the entry point IP address.
0x1AEntry point override has been restricted by your domain administrator. Entry point override has been restricted by your domain administrator.
0x1BNetwork Connectivity Assistant service is stopped or not responding. Network Connectivity Assistant service is stopped or not responding.
0x1CServerShunt and TCP Chimney can't be enabled together. TCP Chimney must be disabled for this operation. ServerShunt and TCP Chimney can't be enabled together. TCP Chimney must be disabled for this operation.
0x1DNo entry points found with name equal to \"%1\". No entry points found with name equal to \"%1\".
0x1EThe TCP mapping timeout cannot be less than 30 minutes. The TCP mapping timeout cannot be less than 30 minutes.
0x1FState cannot be set to OutsideEnabled for server interfaces. State cannot be set to OutsideEnabled for server interfaces.

EXIF

File Name:netttcim.dll.mui
Directory:%WINDIR%\WinSxS\amd64_microsoft-windows-i..ation-net.resources_31bf3856ad364e35_10.0.15063.0_fr-fr_46c24c6eb1b70810\
File Size:170 kB
File Permissions:rw-rw-rw-
File Type:Win32 DLL
File Type Extension:dll
MIME Type:application/octet-stream
Machine Type:Intel 386 or later, and compatibles
Time Stamp:0000:00:00 00:00:00
PE Type:PE32
Linker Version:14.10
Code Size:0
Initialized Data Size:173568
Uninitialized Data Size:0
Entry Point:0x0000
OS Version:10.0
Image Version:10.0
Subsystem Version:6.0
Subsystem:Windows GUI
File Version Number:10.0.15063.0
Product Version Number:10.0.15063.0
File Flags Mask:0x003f
File Flags:(none)
File OS:Windows NT 32-bit
Object File Type:Dynamic link library
File Subtype:0
Language Code:French
Character Set:Unicode
Company Name:Microsoft Corporation
File Description:Transition Technology WMI Objects
File Version:10.0.15063.0 (WinBuild.160101.0800)
Internal Name:netttcim.dll
Legal Copyright:© Microsoft Corporation. All rights reserved.
Original File Name:netttcim.dll.mui
Product Name:Microsoft® Windows® Operating System
Product Version:10.0.15063.0
Directory:%WINDIR%\WinSxS\x86_microsoft-windows-i..ation-net.resources_31bf3856ad364e35_10.0.15063.0_fr-fr_eaa3b0eaf95996da\

What is netttcim.dll.mui?

netttcim.dll.mui is Multilingual User Interface resource file that contain French language for file netttcim.dll (Transition Technology WMI Objects).

File version info

File Description:Transition Technology WMI Objects
File Version:10.0.15063.0 (WinBuild.160101.0800)
Company Name:Microsoft Corporation
Internal Name:netttcim.dll
Legal Copyright:© Microsoft Corporation. All rights reserved.
Original Filename:netttcim.dll.mui
Product Name:Microsoft® Windows® Operating System
Product Version:10.0.15063.0
Translation:0x40C, 1200