File name: | NetAdapterCim.dll.mui |
Size: | 240640 byte |
MD5: | aa310598d4f8576f40329d504c024e0c |
SHA1: | 303521a47048c9b8ff2daa0188ee216ff9dc7633 |
SHA256: | df3cdd1ff87cd49408d2324739c06cbde8a532945e86981682fe37735cacff61 |
Operating systems: | Windows 10 |
Extension: | MUI |
If an error occurred or the following message in English (British) 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 | English (British) | English |
---|---|---|
1 | 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. |
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. |
2 | The 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. |
3 | The Description property provides a textual description of the object. | The Description property provides a textual description of the object. |
4 | 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. |
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. |
5 | 2.19.0 | 2.19.0 |
6 | 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. | 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. |
7 | A 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. |
8 | 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. | 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. |
9 | 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. |
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. |
10 | Unknown | Unknown |
11 | Other | Other |
12 | OK | OK |
13 | Degraded | Degraded |
14 | Stressed | Stressed |
15 | Predictive Failure | Predictive Failure |
16 | Error | Error |
17 | Non-Recoverable Error | Non-Recoverable Error |
18 | Starting | Starting |
19 | Stopping | Stopping |
20 | Stopped | Stopped |
21 | In Service | In Service |
22 | No Contact | No Contact |
23 | Lost Communication | Lost Communication |
24 | Aborted | Aborted |
25 | Dormant | Dormant |
26 | Supporting Entity in Error | Supporting Entity in Error |
27 | Completed | Completed |
28 | Power Mode | Power Mode |
29 | DMTF Reserved | DMTF Reserved |
30 | Vendor Reserved | Vendor Reserved |
31 | 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. | 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. |
32 | 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. |
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. |
33 | 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. |
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. |
34 | Degraded/Warning | Degraded/Warning |
35 | Minor failure | Minor failure |
36 | Major failure | Major failure |
37 | Critical failure | Critical failure |
38 | Non-recoverable error | Non-recoverable error |
39 | 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. |
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. |
40 | Not Available | Not Available |
41 | Communication OK | Communication OK |
42 | 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. |
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. |
43 | No Additional Information | No Additional Information |
44 | 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. |
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. |
45 | Servicing | Servicing |
46 | Migrating | Migrating |
47 | Emigrating | Emigrating |
48 | Immigrating | Immigrating |
49 | Snapshotting | Snapshotting |
50 | Shutting Down | Shutting Down |
51 | In Test | In Test |
52 | Transitioning | Transitioning |
53 | 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. |
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. |
54 | 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. |
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. |
55 | 2.22.0 | 2.22.0 |
56 | CIM_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. |
57 | 2.6.0 | 2.6.0 |
58 | 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. | 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. |
59 | 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. | 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. |
60 | 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. | 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. |
61 | 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. | 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. |
62 | 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. | 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. |
63 | 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. | 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. |
64 | The 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. |
65 | January | January |
66 | February | February |
67 | March | March |
68 | April | April |
69 | May | May |
70 | June | June |
71 | July | July |
72 | August | August |
73 | September | September |
74 | October | October |
75 | November | November |
76 | December | December |
77 | 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. |
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. |
78 | 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. | 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. |
79 | -Saturday | -Saturday |
80 | -Friday | -Friday |
81 | -Thursday | -Thursday |
82 | -Wednesday | -Wednesday |
83 | -Tuesday | -Tuesday |
84 | -Monday | -Monday |
85 | -Sunday | -Sunday |
86 | ExactDayOfMonth | ExactDayOfMonth |
87 | Sunday | Sunday |
88 | Monday | Monday |
89 | Tuesday | Tuesday |
90 | Wednesday | Wednesday |
91 | Thursday | Thursday |
92 | Friday | Friday |
93 | Saturday | Saturday |
94 | 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. |
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. |
95 | 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". | 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". |
96 | Local Time | Local Time |
97 | UTC Time | UTC Time |
98 | 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. | 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. |
99 | The 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. |
100 | The 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. |
101 | 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. | 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. |
102 | 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. |
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. |
103 | Percent | Percent |
104 | 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. | 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. |
105 | 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. | 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. |
106 | 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. | 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. |
107 | 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. |
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. |
108 | Do Not Continue | Do Not Continue |
109 | Continue With Next Job | Continue With Next Job |
110 | Re-run Job | Re-run Job |
111 | Run Recovery Job | Run Recovery Job |
112 | A 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"). |
113 | 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. |
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. |
114 | Success | Success |
115 | Not Supported | Not Supported |
116 | Timeout | Timeout |
117 | Failed | Failed |
118 | Access Denied | Access Denied |
119 | Not Found | Not Found |
120 | Vendor Specific | Vendor Specific |
121 | Indicates 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. |
122 | 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. | 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. |
123 | 2.10.0 | 2.10.0 |
124 | 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. |
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. |
125 | Communications Error | Communications Error |
126 | Quality of Service Error | Quality of Service Error |
127 | Software Error | Software Error |
128 | Hardware Error | Hardware Error |
129 | Environmental Error | Environmental Error |
130 | Security Error | Security Error |
131 | Oversubscription Error | Oversubscription Error |
132 | Unavailable Resource Error | Unavailable Resource Error |
133 | Unsupported Operation Error | Unsupported Operation Error |
134 | A 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. |
135 | 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. | 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. |
136 | An 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. |
137 | 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. | 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. |
138 | An array containing the dynamic content of the message. | An array containing the dynamic content of the message. |
139 | 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. |
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. |
140 | Information | Information |
141 | Minor | Minor |
142 | Major | Major |
143 | Critical | Critical |
144 | Fatal/NonRecoverable | Fatal/NonRecoverable |
145 | An enumerated value that describes the probable cause of the error. | An enumerated value that describes the probable cause of the error. |
146 | Adapter/Card Error | Adapter/Card Error |
147 | Application Subsystem Failure | Application Subsystem Failure |
148 | Bandwidth Reduced | Bandwidth Reduced |
149 | Connection Establishment Error | Connection Establishment Error |
150 | Communications Protocol Error | Communications Protocol Error |
151 | Communications Subsystem Failure | Communications Subsystem Failure |
152 | Configuration/Customization Error | Configuration/Customization Error |
153 | Congestion | Congestion |
154 | Corrupt Data | Corrupt Data |
155 | CPU Cycles Limit Exceeded | CPU Cycles Limit Exceeded |
156 | Dataset/Modem Error | Dataset/Modem Error |
157 | Degraded Signal | Degraded Signal |
158 | DTE-DCE Interface Error | DTE-DCE Interface Error |
159 | Enclosure Door Open | Enclosure Door Open |
160 | Equipment Malfunction | Equipment Malfunction |
161 | Excessive Vibration | Excessive Vibration |
162 | File Format Error | File Format Error |
163 | Fire Detected | Fire Detected |
164 | Flood Detected | Flood Detected |
165 | Framing Error | Framing Error |
166 | HVAC Problem | HVAC Problem |
167 | Humidity Unacceptable | Humidity Unacceptable |
168 | I/O Device Error | I/O Device Error |
169 | Input Device Error | Input Device Error |
170 | LAN Error | LAN Error |
171 | Non-Toxic Leak Detected | Non-Toxic Leak Detected |
172 | Local Node Transmission Error | Local Node Transmission Error |
173 | Loss of Frame | Loss of Frame |
174 | Loss of Signal | Loss of Signal |
175 | Material Supply Exhausted | Material Supply Exhausted |
176 | Multiplexer Problem | Multiplexer Problem |
177 | Out of Memory | Out of Memory |
178 | Output Device Error | Output Device Error |
179 | Performance Degraded | Performance Degraded |
180 | Power Problem | Power Problem |
181 | Pressure Unacceptable | Pressure Unacceptable |
182 | Processor Problem (Internal Machine Error) | Processor Problem (Internal Machine Error) |
183 | Pump Failure | Pump Failure |
184 | Queue Size Exceeded | Queue Size Exceeded |
185 | Receive Failure | Receive Failure |
186 | Receiver Failure | Receiver Failure |
187 | Remote Node Transmission Error | Remote Node Transmission Error |
188 | Resource at or Nearing Capacity | Resource at or Nearing Capacity |
189 | Response Time Excessive | Response Time Excessive |
190 | Retransmission Rate Excessive | Retransmission Rate Excessive |
191 | Software Program Abnormally Terminated | Software Program Abnormally Terminated |
192 | Software Program Error (Incorrect Results) | Software Program Error (Incorrect Results) |
193 | Storage Capacity Problem | Storage Capacity Problem |
194 | Temperature Unacceptable | Temperature Unacceptable |
195 | Threshold Crossed | Threshold Crossed |
196 | Timing Problem | Timing Problem |
197 | Toxic Leak Detected | Toxic Leak Detected |
198 | Transmit Failure | Transmit Failure |
199 | Transmitter Failure | Transmitter Failure |
200 | Underlying Resource Unavailable | Underlying Resource Unavailable |
201 | Version Mismatch | Version Mismatch |
202 | Previous Alert Cleared | Previous Alert Cleared |
203 | Login Attempts Failed | Login Attempts Failed |
204 | Software Virus Detected | Software Virus Detected |
205 | Hardware Security Breached | Hardware Security Breached |
206 | Denial of Service Detected | Denial of Service Detected |
207 | Security Credential Mismatch | Security Credential Mismatch |
208 | Unauthorized Access | Unauthorized Access |
209 | Alarm Received | Alarm Received |
210 | Loss of Pointer | Loss of Pointer |
211 | Payload Mismatch | Payload Mismatch |
212 | Transmission Error | Transmission Error |
213 | Excessive Error Rate | Excessive Error Rate |
214 | Trace Problem | Trace Problem |
215 | Element Unavailable | Element Unavailable |
216 | Element Missing | Element Missing |
217 | Loss of Multi Frame | Loss of Multi Frame |
218 | Broadcast Channel Failure | Broadcast Channel Failure |
219 | Invalid Message Received | Invalid Message Received |
220 | Routing Failure | Routing Failure |
221 | Backplane Failure | Backplane Failure |
222 | Identifier Duplication | Identifier Duplication |
223 | Protection Path Failure | Protection Path Failure |
224 | Sync Loss or Mismatch | Sync Loss or Mismatch |
225 | Terminal Problem | Terminal Problem |
226 | Real Time Clock Failure | Real Time Clock Failure |
227 | Antenna Failure | Antenna Failure |
228 | Battery Charging Failure | Battery Charging Failure |
229 | Disk Failure | Disk Failure |
230 | Frequency Hopping Failure | Frequency Hopping Failure |
231 | Loss of Redundancy | Loss of Redundancy |
232 | Power Supply Failure | Power Supply Failure |
233 | Signal Quality Problem | Signal Quality Problem |
234 | Battery Discharging | Battery Discharging |
235 | Battery Failure | Battery Failure |
236 | Commercial Power Problem | Commercial Power Problem |
237 | Fan Failure | Fan Failure |
238 | Engine Failure | Engine Failure |
239 | Sensor Failure | Sensor Failure |
240 | Fuse Failure | Fuse Failure |
241 | Generator Failure | Generator Failure |
242 | Low Battery | Low Battery |
243 | Low Fuel | Low Fuel |
244 | Low Water | Low Water |
245 | Explosive Gas | Explosive Gas |
246 | High Winds | High Winds |
247 | Ice Buildup | Ice Buildup |
248 | Smoke | Smoke |
249 | Memory Mismatch | Memory Mismatch |
250 | Out of CPU Cycles | Out of CPU Cycles |
251 | Software Environment Problem | Software Environment Problem |
252 | Software Download Failure | Software Download Failure |
253 | Element Reinitialized | Element Reinitialized |
254 | Logging Problems | Logging Problems |
255 | Leak Detected | Leak Detected |
256 | Protection Mechanism Failure | Protection Mechanism Failure |
257 | Protecting Resource Failure | Protecting Resource Failure |
258 | Database Inconsistency | Database Inconsistency |
259 | Authentication Failure | Authentication Failure |
260 | Breach of Confidentiality | Breach of Confidentiality |
261 | Cable Tamper | Cable Tamper |
262 | Delayed Information | Delayed Information |
263 | Duplicate Information | Duplicate Information |
264 | Information Missing | Information Missing |
265 | Information Modification | Information Modification |
266 | Information Out of Sequence | Information Out of Sequence |
267 | Key Expired | Key Expired |
268 | Non-Repudiation Failure | Non-Repudiation Failure |
269 | Out of Hours Activity | Out of Hours Activity |
270 | Out of Service | Out of Service |
271 | Procedural Error | Procedural Error |
272 | Unexpected Information | Unexpected Information |
273 | A free-form string describing the probable cause of the error. | A free-form string describing the probable cause of the error. |
274 | A 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. |
275 | 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. | 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. |
276 | 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. |
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. |
277 | CIMObjectPath | CIMObjectPath |
278 | 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. | 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. |
279 | 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. |
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. |
280 | CIM_ERR_FAILED | CIM_ERR_FAILED |
281 | CIM_ERR_ACCESS_DENIED | CIM_ERR_ACCESS_DENIED |
282 | CIM_ERR_INVALID_NAMESPACE | CIM_ERR_INVALID_NAMESPACE |
283 | CIM_ERR_INVALID_PARAMETER | CIM_ERR_INVALID_PARAMETER |
284 | CIM_ERR_INVALID_CLASS | CIM_ERR_INVALID_CLASS |
285 | CIM_ERR_NOT_FOUND | CIM_ERR_NOT_FOUND |
286 | CIM_ERR_NOT_SUPPORTED | CIM_ERR_NOT_SUPPORTED |
287 | CIM_ERR_CLASS_HAS_CHILDREN | CIM_ERR_CLASS_HAS_CHILDREN |
288 | CIM_ERR_CLASS_HAS_INSTANCES | CIM_ERR_CLASS_HAS_INSTANCES |
289 | CIM_ERR_INVALID_SUPERCLASS | CIM_ERR_INVALID_SUPERCLASS |
290 | CIM_ERR_ALREADY_EXISTS | CIM_ERR_ALREADY_EXISTS |
291 | CIM_ERR_NO_SUCH_PROPERTY | CIM_ERR_NO_SUCH_PROPERTY |
292 | CIM_ERR_TYPE_MISMATCH | CIM_ERR_TYPE_MISMATCH |
293 | CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED | CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED |
294 | CIM_ERR_INVALID_QUERY | CIM_ERR_INVALID_QUERY |
295 | CIM_ERR_METHOD_NOT_AVAILABLE | CIM_ERR_METHOD_NOT_AVAILABLE |
296 | CIM_ERR_METHOD_NOT_FOUND | CIM_ERR_METHOD_NOT_FOUND |
297 | CIM_ERR_UNEXPECTED_RESPONSE | CIM_ERR_UNEXPECTED_RESPONSE |
298 | CIM_ERR_INVALID_RESPONSE_DESTINATION | CIM_ERR_INVALID_RESPONSE_DESTINATION |
299 | CIM_ERR_NAMESPACE_NOT_EMPTY | CIM_ERR_NAMESPACE_NOT_EMPTY |
300 | CIM_ERR_INVALID_ENUMERATION_CONTEXT | CIM_ERR_INVALID_ENUMERATION_CONTEXT |
301 | CIM_ERR_INVALID_OPERATION_TIMEOUT | CIM_ERR_INVALID_OPERATION_TIMEOUT |
302 | CIM_ERR_PULL_HAS_BEEN_ABANDONED | CIM_ERR_PULL_HAS_BEEN_ABANDONED |
303 | CIM_ERR_PULL_CANNOT_BE_ABANDONED | CIM_ERR_PULL_CANNOT_BE_ABANDONED |
304 | CIM_ERR_FILTERED_ENUMERATION_NOT_SUPPORTED | CIM_ERR_FILTERED_ENUMERATION_NOT_SUPPORTED |
305 | CIM_ERR_CONTINUATION_ON_ERROR_NOT_SUPPORTED | CIM_ERR_CONTINUATION_ON_ERROR_NOT_SUPPORTED |
306 | CIM_ERR_SERVER_LIMITS_EXCEEDED | CIM_ERR_SERVER_LIMITS_EXCEEDED |
307 | CIM_ERR_SERVER_IS_SHUTTING_DOWN | CIM_ERR_SERVER_IS_SHUTTING_DOWN |
308 | CIM_ERR_QUERY_FEATURE_NOT_SUPPORTED | CIM_ERR_QUERY_FEATURE_NOT_SUPPORTED |
309 | A 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. |
310 | 2.22.1 | 2.22.1 |
311 | 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. | 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. |
312 | 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\'. |
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\'. |
313 | 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.) | 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.) |
314 | 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 |
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 |
315 | New | New |
316 | Running | Running |
317 | Suspended | Suspended |
318 | Terminated | Terminated |
319 | Killed | Killed |
320 | Exception | Exception |
321 | Service | Service |
322 | Query Pending | Query Pending |
323 | 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. | 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. |
324 | 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. |
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. |
325 | 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. |
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. |
326 | Completed with No Error | Completed with No Error |
327 | Unknown/Unspecified Error | Unknown/Unspecified Error |
328 | Can NOT complete within Timeout Period | Can NOT complete within Timeout Period |
329 | Invalid Parameter | Invalid Parameter |
330 | In Use | In Use |
331 | Method Parameters Checked - Transition Started | Method Parameters Checked - Transition Started |
332 | Invalid State Transition | Invalid State Transition |
333 | Use of Timeout Parameter Not Supported | Use of Timeout Parameter Not Supported |
334 | Busy | Busy |
335 | Method Reserved | Method Reserved |
336 | 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. |
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. |
337 | Start | Start |
338 | Suspend | Suspend |
339 | Terminate | Terminate |
340 | Kill | Kill |
341 | 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. |
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. |
342 | 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. | 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. |
343 | Unspecified Error | Unspecified Error |
344 | 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. | 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. |
345 | A 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. |
346 | 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. |
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. |
347 | Enabled | Enabled |
348 | Disabled | Disabled |
349 | Not Applicable | Not Applicable |
350 | Enabled but Offline | Enabled but Offline |
351 | Deferred | Deferred |
352 | Quiesce | Quiesce |
353 | 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. | 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. |
354 | 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". |
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". |
355 | Shut Down | Shut Down |
356 | No Change | No Change |
357 | Offline | Offline |
358 | Test | Test |
359 | Reboot | Reboot |
360 | Reset | Reset |
361 | 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). | 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). |
362 | No Default | No Default |
363 | 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. | 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. |
364 | 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. | 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. |
365 | Defer | Defer |
366 | 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. |
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. |
367 | 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. |
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. |
368 | Unknown or Unspecified Error | Unknown or Unspecified Error |
369 | Cannot complete within Timeout Period | Cannot complete within Timeout Period |
370 | Method Parameters Checked - Job Started | Method Parameters Checked - Job Started |
371 | 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. | 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. |
372 | May 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. |
373 | 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. |
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. |
374 | This 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. |
375 | The scoping System\'s CreationClassName. | The scoping System\'s CreationClassName. |
376 | The scoping System\'s Name. | The scoping System\'s Name. |
377 | 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. | 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. |
378 | An address or other identifying information to uniquely name the LogicalDevice. | An address or other identifying information to uniquely name the LogicalDevice. |
379 | 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. | 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. |
380 | 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. | 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. |
381 | Power Saving Modes Entered Automatically | Power Saving Modes Entered Automatically |
382 | Power State Settable | Power State Settable |
383 | Power Cycling Supported | Power Cycling Supported |
384 | Timed Power On Supported | Timed Power On Supported |
385 | 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. | 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. |
386 | Running/Full Power | Running/Full Power |
387 | Warning | Warning |
388 | Power Off | Power Off |
389 | Off Line | Off Line |
390 | Off Duty | Off Duty |
391 | Not Installed | Not Installed |
392 | Install Error | Install Error |
393 | Power Save - Unknown | Power Save - Unknown |
394 | Power Save - Low Power Mode | Power Save - Low Power Mode |
395 | Power Save - Standby | Power Save - Standby |
396 | Power Cycle | Power Cycle |
397 | Power Save - Warning | Power Save - Warning |
398 | Paused | Paused |
399 | Not Ready | Not Ready |
400 | Not Configured | Not Configured |
401 | Quiesced | Quiesced |
402 | 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. |
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. |
403 | LastErrorCode captures the last error code reported by the LogicalDevice. | LastErrorCode captures the last error code reported by the LogicalDevice. |
404 | 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. | 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. |
405 | ErrorCleared 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. |
406 | 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. | 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. |
407 | The 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. |
408 | Hours | Hours |
409 | The total number of hours that this Device has been powered. | The total number of hours that this Device has been powered. |
410 | 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. | 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. |
411 | 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"). | 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"). |
412 | 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. |
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. |
413 | MilliSeconds | MilliSeconds |
414 | 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. | 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. |
415 | The power state to set. | The power state to set. |
416 | Full Power | Full Power |
417 | Power Save - Other | Power Save - Other |
418 | 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. | 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. |
419 | 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. | 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. |
420 | 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. |
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. |
421 | If TRUE enable the device, if FALSE disable the device. | If TRUE enable the device, if FALSE disable the device. |
422 | 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. |
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. |
423 | If TRUE, take the device online, if FALSE, take the device OFFLINE. | If TRUE, take the device online, if FALSE, take the device OFFLINE. |
424 | 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. |
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. |
425 | If 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. |
426 | 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. | 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. |
427 | 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. | 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. |
428 | 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. | 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. |
429 | 2.8.0 | 2.8.0 |
430 | The bandwidth of the Port in Bits per Second. | The bandwidth of the Port in Bits per Second. |
431 | Bits per Second | Bits per Second |
432 | The maximum bandwidth of the Port in Bits per Second. | The maximum bandwidth of the Port in Bits per Second. |
433 | The 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. |
434 | 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\'. | 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\'. |
435 | Front-end only | Front-end only |
436 | Back-end only | Back-end only |
437 | Not restricted | Not restricted |
438 | 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. | 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. |
439 | Describes the type of module, when PortType is set to 1 ("Other"). | Describes the type of module, when PortType is set to 1 ("Other"). |
440 | 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. | 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. |
441 | 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. | 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. |
442 | 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".) |
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".) |
443 | NetworkPorts 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. |
444 | 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. | 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. |
445 | Ethernet | Ethernet |
446 | IB | IB |
447 | FC | FC |
448 | FDDI | FDDI |
449 | ATM | ATM |
450 | Token Ring | Token Ring |
451 | Frame Relay | Frame Relay |
452 | Infrared | Infrared |
453 | BlueTooth | BlueTooth |
454 | Wireless LAN | Wireless LAN |
455 | A 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". |
456 | 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. | 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. |
457 | An array of strings that indicates the network addresses for the port. | An array of strings that indicates the network addresses for the port. |
458 | Boolean that indicates that the port is operating in full duplex mode. | Boolean that indicates that the port is operating in full duplex mode. |
459 | A 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. |
460 | The maximum transmission unit (MTU) that can be supported. | The maximum transmission unit (MTU) that can be supported. |
461 | Bytes | Bytes |
462 | The active or negotiated maximum transmission unit (MTU) that can be supported. | The active or negotiated maximum transmission unit (MTU) that can be supported. |
463 | 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. | 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. |
464 | Interface Description, a.k.a. ifDescr or friendly name is a unique name assigned to the network adapter during installation. This name cannot be changed and is persisted as long as the network adapter is not uninstalled. | Interface Description, a.k.a. ifDescr or friendly name is a unique name assigned to the network adapter during installation. This name cannot be changed and is persisted as long as the network adapter is not uninstalled. |
465 | The locally unique identifier for the network interface. in InterfaceType_NetluidIndex format. Ex: Ethernet_2. | The locally unique identifier for the network interface. in InterfaceType_NetluidIndex format. Ex: Ethernet_2. |
466 | The locally unique identifier (LUID) for the network interface as a 64 bit number. | The locally unique identifier (LUID) for the network interface as a 64 bit number. |
467 | The GUID for the network interface. | The GUID for the network interface. |
468 | The index that identifies the network interface. This index value may change when a network adapter is disabled and then enabled, and should not be considered persistent. | The index that identifies the network interface. This index value may change when a network adapter is disabled and then enabled, and should not be considered persistent. |
469 | The name of the device object for this adapter. | The name of the device object for this adapter. |
470 | An index assigned to the network adapter at the time of installation. This index is unique in the scope of interface type. |
An index assigned to the network adapter at the time of installation. This index is unique in the scope of interface type. |
471 | Network adapter emulates a physical network card. | Network adapter emulates a physical network card. |
472 | Network adapter is hidden and does not appear in any user interface. | Network adapter is hidden and does not appear in any user interface. |
473 | Network adapter cannot be removed by the user. | Network adapter cannot be removed by the user. |
474 | Network adapter is the adapter edge of an intermediate filter component. | Network adapter is the adapter edge of an intermediate filter component. |
475 | The interface type as defined by the Internet Assigned Names Authority (IANA). | The interface type as defined by the Internet Assigned Names Authority (IANA). |
476 | The interface for the network adapter is provided by a hardware device. | The interface for the network adapter is provided by a hardware device. |
477 | The lower-level interface of the network adapter is a WDM bus driver such as USB. | The lower-level interface of the network adapter is a WDM bus driver such as USB. |
478 | This interface is an endpoint device and is not a true network interface that connects to a network. | This interface is an endpoint device and is not a true network interface that connects to a network. |
479 | The interface is used by iSCSI software initiator and is in the paging path. | The interface is used by iSCSI software initiator and is in the paging path. |
480 | The plug and play state of the network adapter. |
The plug and play state of the network adapter. |
481 | Present | Present |
482 | Started | Started |
483 | Network adapter media type. | Network adapter media type. |
484 | 802.3 | 802.3 |
485 | 802.5 | 802.5 |
486 | WAN | WAN |
487 | Local Talk | Local Talk |
488 | DIX | DIX |
489 | Raw Arcnet | Raw Arcnet |
490 | 878.2 | 878.2 |
491 | Wireless WAN | Wireless WAN |
492 | IRDA | IRDA |
493 | BPC | BPC |
494 | Connection Oriented WAN | Connection Oriented WAN |
495 | IP 1394 | IP 1394 |
496 | Tunnel | Tunnel |
497 | Native 802.11 | Native 802.11 |
498 | Loopback | Loopback |
499 | WiMAX | WiMAX |
500 | IP | IP |
501 | The types of physical media that the network adapter supports |
The types of physical media that the network adapter supports |
502 | Unspecified | Unspecified |
503 | Cable Modem | Cable Modem |
504 | Phone Line | Phone Line |
505 | Power Line | Power Line |
506 | DSL | DSL |
507 | 1394 | 1394 |
508 | Infiniband | Infiniband |
509 | UWB | UWB |
510 | Wired WAN | Wired WAN |
511 | Wired Connection Oriented WAN | Wired Connection Oriented WAN |
512 | Current network interface operational status. | Current network interface operational status. |
513 | Up | Up |
514 | Down | Down |
515 | Testing | Testing |
516 | Not Present | Not Present |
517 | Lower layer down | Lower layer down |
518 | The default port of the network adapter is not authenticated. | The default port of the network adapter is not authenticated. |
519 | The network adapter is not in a media-connected state. | The network adapter is not in a media-connected state. |
520 | The network adapter is in the paused state. | The network adapter is in the paused state. |
521 | The network adapter is in a low power state. | The network adapter is in a low power state. |
522 | Network adapter administrative status, as described in RFC 2863. | Network adapter administrative status, as described in RFC 2863. |
523 | Specifies the network adapter connection state. | Specifies the network adapter connection state. |
524 | Connected | Connected |
525 | Disconnected | Disconnected |
526 | The maximum transfer unit (MTU) size the network adapter supports. This value does not include the size of the link-layer header. | The maximum transfer unit (MTU) size the network adapter supports. This value does not include the size of the link-layer header. |
527 | The Virtual LAN Identifier set on the network adapter. | The Virtual LAN Identifier set on the network adapter. |
528 | The transmit link speed in bits per second. | The transmit link speed in bits per second. |
529 | The receive link speed in bits per second. | The receive link speed in bits per second. |
530 | TRUE if the interface is in promiscuous mode or FALSE if it is not. | TRUE if the interface is in promiscuous mode or FALSE if it is not. |
531 | TRUE if the network adapter supports wake-on-LAN capability and the capability is enabled, or FALSE if it does not | TRUE if the network adapter supports wake-on-LAN capability and the capability is enabled, or FALSE if it does not |
532 | Indicates if a connector is present on the network adapter. This value is set to TRUE if this is a physical adapter or FALSE if this is not a physical adapter. | Indicates if a connector is present on the network adapter. This value is set to TRUE if this is a physical adapter or FALSE if this is not a physical adapter. |
533 | The media duplex state of the network adapter. | The media duplex state of the network adapter. |
534 | Half | Half |
535 | Full | Full |
536 | The network adapter driver date in YYYY-MM-DD format. | The network adapter driver date in YYYY-MM-DD format. |
537 | The network adapter driver date in FILETIME format. This is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601 (UTC). | The network adapter driver date in FILETIME format. This is a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601 (UTC). |
538 | A string representing the network adapter driver version. | A string representing the network adapter driver version. |
539 | The name of the network adapter driver. | The name of the network adapter driver. |
540 | The description for the network adapter driver. | The description for the network adapter driver. |
541 | The major version of network adapter driver. | The major version of network adapter driver. |
542 | The minor version of network adapter driver. | The minor version of network adapter driver. |
543 | The major NDIS version the network adapter driver conforms to. | The major NDIS version the network adapter driver conforms to. |
544 | The minor NDIS version the network adapter driver conforms to. | The minor NDIS version the network adapter driver conforms to. |
545 | The Plug and Play Device ID. | The Plug and Play Device ID. |
546 | The driver provider name. | The driver provider name. |
547 | The PnP component ID, a.k.a. Hardware ID of the network adapter. | The PnP component ID, a.k.a. Hardware ID of the network adapter. |
548 | The interface indices of lower layer interfaces. | The interface indices of lower layer interfaces. |
549 | The interface indices of higher layer interfaces. | The interface indices of higher layer interfaces. |
550 | The management state of the network adapter. If True, the network adapter is locked and many of its properties cannot be changed unless the adapter is unlocked. | The management state of the network adapter. If True, the network adapter is locked and many of its properties cannot be changed unless the adapter is unlocked. |
551 | Enables a network adapter | Enables a network adapter |
552 | Disables a network adapter | Disables a network adapter |
553 | Restarts a network adapter | Restarts a network adapter |
554 | Locks a network adapter | Locks a network adapter |
555 | Unlocks a network adapter | Unlocks a network adapter |
556 | Renames a network adapter | Renames a network adapter |
557 | A logical network adapters | A logical network adapters |
558 | 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. |
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. |
559 | 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.) | 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.) |
560 | 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. |
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. |
561 | Superclass SettingData for networking | Superclass SettingData for networking |
562 | Name, a.k.a. Connection Name, ifAlias, or InterfaceAlias, is a unique name assigned to the adapter during installation. The Name of the adapter can be changed by the administrator and is persisted across the boot or network adapter restart. | Name, a.k.a. Connection Name, ifAlias, or InterfaceAlias, is a unique name assigned to the adapter during installation. The Name of the adapter can be changed by the administrator and is persisted across the boot or network adapter restart. |
563 | The source of the setting data. |
The source of the setting data. |
564 | Device | Device |
565 | Persistent storage | Persistent storage |
566 | Represents the base class for network adapter settings. | Represents the base class for network adapter settings. |
567 | The property description in user interface. This property is only valid if the parameter is displayed in user interface. |
The property description in user interface. This property is only valid if the parameter is displayed in user interface. |
568 | The description for the current value of the property. This property is only valid if the parameter is displayed in user interface. |
The description for the current value of the property. This property is only valid if the parameter is displayed in user interface. |
569 | The description for the default value of the parameter. This property is only valid if the parameter is displayed in user interface. |
The description for the default value of the parameter. This property is only valid if the parameter is displayed in user interface. |
570 | This property specifies the type of the parameter. The "int", "long", "word", and "dword" types specify a numeric parameter; "edit" and "enum" types specify a text parameter. Note that the values for all the parameters that are displayed in the user interface, including numeric parameters, are stored in the registry as REG_SZ (null terminated string) data type. This property is only valid if the parameter is displayed in user interface. |
This property specifies the type of the parameter. The "int", "long", "word", and "dword" types specify a numeric parameter; "edit" and "enum" types specify a text parameter. Note that the values for all the parameters that are displayed in the user interface, including numeric parameters, are stored in the registry as REG_SZ (null terminated string) data type. This property is only valid if the parameter is displayed in user interface. |
571 | int | int |
572 | long | long |
573 | word | word |
574 | dword | dword |
575 | enum | enum |
576 | edit | edit |
577 | If True, specifying this parameter is optional. Otherwise it is mandatory. This property is only valid if the parameter is displayed in user interface. |
If True, specifying this parameter is optional. Otherwise it is mandatory. This property is only valid if the parameter is displayed in user interface. |
578 | An array of integers specifying the registry keyword values used to represent a parameter of the "enum" type. This property is only valid if the parameter is displayed in user interface. |
An array of integers specifying the registry keyword values used to represent a parameter of the "enum" type. This property is only valid if the parameter is displayed in user interface. |
579 | An array of strings representing the descriptions for the registry keyword values used in EnumParameterRegistryValues. This property is only valid if the parameter is displayed in user interface. |
An array of strings representing the descriptions for the registry keyword values used in EnumParameterRegistryValues. This property is only valid if the parameter is displayed in user interface. |
580 | The "Base" used in representing a numeric parameter. This property is only valid if the parameter is displayed in user interface. |
The "Base" used in representing a numeric parameter. This property is only valid if the parameter is displayed in user interface. |
581 | The minimum value of a numeric parameter. This property is only valid if the parameter is displayed in user interface. |
The minimum value of a numeric parameter. This property is only valid if the parameter is displayed in user interface. |
582 | The maximum value of a numeric parameter. This property is only valid if the parameter is displayed in user interface. |
The maximum value of a numeric parameter. This property is only valid if the parameter is displayed in user interface. |
583 | The "Step" value of a numeric parameter. This property is only valid if the parameter is displayed in user interface. |
The "Step" value of a numeric parameter. This property is only valid if the parameter is displayed in user interface. |
584 | Registry keyword name of the parameter. Registry keywords may be associated with a parameter displayed in user interface. Some registry keywords are not associated to any parameter displayed in user interface. |
Registry keyword name of the parameter. Registry keywords may be associated with a parameter displayed in user interface. Some registry keywords are not associated to any parameter displayed in user interface. |
585 | Registry keyword data type. For parameters displayed in user interface, this value is always REG_SZ even if the parameter is a numeric parameter. | Registry keyword data type. For parameters displayed in user interface, this value is always REG_SZ even if the parameter is a numeric parameter. |
586 | REG_SZ | REG_SZ |
587 | REG_DWORD | REG_DWORD |
588 | REG_MULTI_SZ | REG_MULTI_SZ |
589 | REG_QWORD | REG_QWORD |
590 | Current value of the registry keyword. For a parameter that is displayed in user interface and is of "enum" type, this is a value in EnumParameterRegistryValues array and not the description for the current value of the parameter. | Current value of the registry keyword. For a parameter that is displayed in user interface and is of "enum" type, this is a value in EnumParameterRegistryValues array and not the description for the current value of the parameter. |
591 | Default registry value for the parameter. This property is only valid if the parameter is displayed in user interface. |
Default registry value for the parameter. This property is only valid if the parameter is displayed in user interface. |
592 | Resets the advanced property of a network adapter to its factory default value. | Resets the advanced property of a network adapter to its factory default value. |
593 | This class represents the advanced properties of a network adapter stored in the registry. | This class represents the advanced properties of a network adapter stored in the registry. |
594 | The managed element. | The managed element. |
595 | The SettingData object associated with the element. | The SettingData object associated with the element. |
596 | An 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. |
597 | Is Default | Is Default |
598 | Is Not Default | Is Not Default |
599 | An 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. |
600 | Is Current | Is Current |
601 | Is Not Current | Is Not Current |
602 | 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. | 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. |
603 | Is Next | Is Next |
604 | Is Not Next | Is Not Next |
605 | Is Next For Single Use | Is Next For Single Use |
606 | 2.19.1 | 2.19.1 |
607 | ElementSettingData 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. |
608 | Associates a network port with its configuration data. | Associates a network port with its configuration data. |
609 | Advanced properties for the network adapter. | Advanced properties for the network adapter. |
610 | Associates a network port with its advanced property configuration stored in the registry. | Associates a network port with its advanced property configuration stored in the registry. |
611 | The bitmask for a set of logical processors in a group. | The bitmask for a set of logical processors in a group. |
612 | The group number for a set of logical processors. | The group number for a set of logical processors. |
613 | This class represents a processor affinity mask. | This class represents a processor affinity mask. |
614 | Not using interrupts. | Not using interrupts. |
615 | Using line based interrupts. | Using line based interrupts. |
616 | MSI is supported. | MSI is supported. |
617 | MSI is enabled. | MSI is enabled. |
618 | MSI-X is supported. | MSI-X is supported. |
619 | MSI-X is enabled. | MSI-X is enabled. |
620 | The number of MSI-X table entries supported by the hardware. | The number of MSI-X table entries supported by the hardware. |
621 | The number of MSI messages allocated by the network adapter driver. | The number of MSI messages allocated by the network adapter driver. |
622 | The NUMA node of the network adapter. | The NUMA node of the network adapter. |
623 | The location information for a PCI network adapter. This string includes bus, device and function number for the network adapter as displayed in device manager. | The location information for a PCI network adapter. This string includes bus, device and function number for the network adapter as displayed in device manager. |
624 | The segment number of a PCI network adapter. | The segment number of a PCI network adapter. |
625 | The bus number of a PCI network adapter. | The bus number of a PCI network adapter. |
626 | The device number of a PCI network adapter. | The device number of a PCI network adapter. |
627 | The function number of a PCI network adapter. | The function number of a PCI network adapter. |
628 | The slot number of a PCI network adapter. | The slot number of a PCI network adapter. |
629 | The type of PCI device. | The type of PCI device. |
630 | Conventional PCI | Conventional PCI |
631 | PCI-X | PCI-X |
632 | PCI Express endpoint | PCI Express endpoint |
633 | PCI Express legacy endpoint | PCI Express legacy endpoint |
634 | PCI Express Root Complex integrated endpoint | PCI Express Root Complex integrated endpoint |
635 | PCI Express treated as PCI | PCI Express treated as PCI |
636 | The current speed and mode, valid only for conventional PCI devices | The current speed and mode, valid only for conventional PCI devices |
637 | Conventional PCI 33MHz | Conventional PCI 33MHz |
638 | Conventional PCI 66MHz | Conventional PCI 66MHz |
639 | The current speed and mode, valid only for PCI-X devices | The current speed and mode, valid only for PCI-X devices |
640 | PCI-X Mode conventional PCI | PCI-X Mode conventional PCI |
641 | PCI-X Mode1 66MHz | PCI-X Mode1 66MHz |
642 | PCI-X Mode1 100MHz | PCI-X Mode1 100MHz |
643 | PCI-X Mode1 133MHz | PCI-X Mode1 133MHz |
644 | PCI-X Mode1 ECC 66MHz | PCI-X Mode1 ECC 66MHz |
645 | PCI-X Mode1 ECC 100MHz | PCI-X Mode1 ECC 100MHz |
646 | PCI-X Mode1 ECC 133MHz | PCI-X Mode1 ECC 133MHz |
647 | PCI-X Mode2 266 66MHz | PCI-X Mode2 266 66MHz |
648 | PCI-X Mode2 266 100MHz | PCI-X Mode2 266 100MHz |
649 | PCI-X Mode2 266 133MHz | PCI-X Mode2 266 133MHz |
650 | PCI-X Mode2 533 66MHz | PCI-X Mode2 533 66MHz |
651 | PCI-X Mode2 533 100MHz | PCI-X Mode2 533 100MHz |
652 | PCI-X Mode2 533 133MHz | PCI-X Mode2 533 133MHz |
653 | Current payload size in bytes, valid only for PCI-E devices. | Current payload size in bytes, valid only for PCI-E devices. |
654 | Maximum payload size in bytes, valid only for PCI-E devices. | Maximum payload size in bytes, valid only for PCI-E devices. |
655 | Maximum read request size in bytes, valid only for PCI-E devices | Maximum read request size in bytes, valid only for PCI-E devices |
656 | Current link speed encoded, valid only for PCI-E devices. | Current link speed encoded, valid only for PCI-E devices. |
657 | 2.5 Gbps | 2.5 Gbps |
658 | 5 Gbps | 5 Gbps |
659 | Current link width (1, 2, 4, .., 32), valid only for PCI-E devices. | Current link width (1, 2, 4, .., 32), valid only for PCI-E devices. |
660 | Maximum link speed encoded, valid only for PCI-E devices. | Maximum link speed encoded, valid only for PCI-E devices. |
661 | Maximum link width (1, 2, 4, .., 32), valid only for PCI-E devices. | Maximum link width (1, 2, 4, .., 32), valid only for PCI-E devices. |
662 | PCI Express specification version, valid for PCI-E devices. | PCI Express specification version, valid for PCI-E devices. |
663 | 1.0 | 1.0 |
664 | 1.1 | 1.1 |
665 | If True, line-based interrupts are supported. | If True, line-based interrupts are supported. |
666 | If True, MSI interrupts are supported. | If True, MSI interrupts are supported. |
667 | If True, MSI-X interrupts are supported. | If True, MSI-X interrupts are supported. |
668 | Maximum number of message interrupts a device supports in hardware. Valid only if the device supports message interrupts. | Maximum number of message interrupts a device supports in hardware. Valid only if the device supports message interrupts. |
669 | An array of processor affinity masks of MSI-X messages allocated by the network adapter driver. | An array of processor affinity masks of MSI-X messages allocated by the network adapter driver. |
670 | Indicates if a device supports 64-bit DMA. | Indicates if a device supports 64-bit DMA. |
671 | This property indicates the status of SR-IOV support for the device. | This property indicates the status of SR-IOV support for the device. |
672 | Supported | Supported |
673 | MissingAcs | MissingAcs |
674 | MissingPfDriver | MissingPfDriver |
675 | NoBusResources | NoBusResources |
676 | NoIoMmuSupport | NoIoMmuSupport |
677 | NoVfBarSpace | NoVfBarSpace |
678 | NoOscSupport | NoOscSupport |
679 | Indicates if a device can wake up via PME while the system is in S0. | Indicates if a device can wake up via PME while the system is in S0. |
680 | This property provides the unique ID associated with a PCI device. | This property provides the unique ID associated with a PCI device. |
681 | This property provides an identification string associated with a PCI device. | This property provides an identification string associated with a PCI device. |
682 | Hardware information for a network adapter | Hardware information for a network adapter |
683 | The hardware information setting data for network adapter. | The hardware information setting data for network adapter. |
684 | Associates a network adapter with its hardware data. | Associates a network adapter with its hardware data. |
685 | Indicates network adapter support for Transmit Checksum Offload for this encapsulated packet type. | Indicates network adapter support for Transmit Checksum Offload for this encapsulated packet type. |
686 | Indicates network adapter support for Receive Checksum Offload for this encapsulated packet type. | Indicates network adapter support for Receive Checksum Offload for this encapsulated packet type. |
687 | Indicates network adapter support for Large Send Offload (LSO) V2 for this encapsulated packet type. | Indicates network adapter support for Large Send Offload (LSO) V2 for this encapsulated packet type. |
688 | Indicates network adapter support for Receive Side Scaling (RSS) for this encapsulated packet type. | Indicates network adapter support for Receive Side Scaling (RSS) for this encapsulated packet type. |
689 | Indicates network adapter support for Virtual Machine Queue (VMQ) for this encapsulated packet type. | Indicates network adapter support for Virtual Machine Queue (VMQ) for this encapsulated packet type. |
693 | Enables the Encapsulation Offload properties on the network adapter. | Enables the Encapsulation Offload properties on the network adapter. |
694 | Disables the Encapsulation Offload properties on the network adapter. | Disables the Encapsulation Offload properties on the network adapter. |
695 | Encapsulated packet task offload properties for a network adapter. | Encapsulated packet task offload properties for a network adapter. |
696 | The Encapsulated Packet Task Offload setting data for network adapter. | The Encapsulated Packet Task Offload setting data for network adapter. |
697 | Associates a network adapter with its Encapsulation Offload data. | Associates a network adapter with its Encapsulation Offload data. |
698 | Specifies that no encapsulation offload is supported. | Specifies that no encapsulation offload is supported. |
699 | Specifies NULL encapsulation. | Specifies NULL encapsulation. |
700 | Specifies IEEE 802.3 encapsulation. | Specifies IEEE 802.3 encapsulation. |
701 | Specifies IEEE 802.3p and IEEE 802.3q encapsulation. | Specifies IEEE 802.3p and IEEE 802.3q encapsulation. |
702 | Specifies that IEEE 802.3p and IEEE 802.3q encapsulation settings are specified in the NetBufferList as OOB info. | Specifies that IEEE 802.3p and IEEE 802.3q encapsulation settings are specified in the NetBufferList as OOB info. |
703 | Specifies logical link control (LLC) encapsulation for routed protocols. Also used to indicate Ethernet LLC/SNAP encapsulation. | Specifies logical link control (LLC) encapsulation for routed protocols. Also used to indicate Ethernet LLC/SNAP encapsulation. |
704 | Defines the encapsulation types the Adapter can support for LSO. | Defines the encapsulation types the Adapter can support for LSO. |
705 | Defines the LSOv1 encapsulation settings for the Adapter. | Defines the LSOv1 encapsulation settings for the Adapter. |
706 | Maximum bytes of user data in a single packet supported by the Adapter. | Maximum bytes of user data in a single packet supported by the Adapter. |
707 | Minimum number of segments that a large TCP packet must be divisible by before offloading to Adapter for segmentation. | Minimum number of segments that a large TCP packet must be divisible by before offloading to Adapter for segmentation. |
708 | Indicates if the Adapter supports segmentation of a packet containing TCP options. | Indicates if the Adapter supports segmentation of a packet containing TCP options. |
709 | Indicates if the Adapter supports segmentation of a packet containing IPv4 options. | Indicates if the Adapter supports segmentation of a packet containing IPv4 options. |
710 | This class is used to report LSOv1 capabilities on a network adapter. | This class is used to report LSOv1 capabilities on a network adapter. |
711 | Defines the IPv4 LSOv2 encapsulation settings for the Adapter. | Defines the IPv4 LSOv2 encapsulation settings for the Adapter. |
712 | Maximum bytes of user data in a single packet supported by the Adapter for IPv4 packets. | Maximum bytes of user data in a single packet supported by the Adapter for IPv4 packets. |
713 | Minimum number of segments that a large TCP packet must be divisible by before offloading to Adapter for segmentation for IPv4 packets. | Minimum number of segments that a large TCP packet must be divisible by before offloading to Adapter for segmentation for IPv4 packets. |
714 | Defines the IPv6 LSOv2 encapsulation settings for the Adapter. | Defines the IPv6 LSOv2 encapsulation settings for the Adapter. |
715 | Maximum bytes of user data in a single packet supported by the Adapter for IPv6 packets. | Maximum bytes of user data in a single packet supported by the Adapter for IPv6 packets. |
716 | Minimum number of segments that a large TCP packet must be divisible by before offloading to Adapter for segmentation for IPv6 packets. | Minimum number of segments that a large TCP packet must be divisible by before offloading to Adapter for segmentation for IPv6 packets. |
717 | Indicates if the Adapter supports segmentation of a packet containing IPv6 Extension headers. | Indicates if the Adapter supports segmentation of a packet containing IPv6 Extension headers. |
718 | This class is used to report LSOv2 capabilities on a network adapter. | This class is used to report LSOv2 capabilities on a network adapter. |
719 | Indicates if LSOv1 is currently enabled for TCP packets. | Indicates if LSOv1 is currently enabled for TCP packets. |
720 | Indicates if LSOv2 is currently enabled for IPv4 TCP packets. | Indicates if LSOv2 is currently enabled for IPv4 TCP packets. |
721 | Indicates if LSOv2 is currently enabled for IPv6 TCP packets. | Indicates if LSOv2 is currently enabled for IPv6 TCP packets. |
722 | Indicates the highest version of LSO supported by the Adapter. | Indicates the highest version of LSO supported by the Adapter. |
723 | LSOv1 | LSOv1 |
724 | LSOv2 | LSOv2 |
725 | The LSO V1 hardware capabilities of the Adapter. | The LSO V1 hardware capabilities of the Adapter. |
726 | The LSO V2 current capabilities of the Adapter. | The LSO V2 current capabilities of the Adapter. |
727 | Enables the Large Send Offload (LSO) properties on the network adapter. | Enables the Large Send Offload (LSO) properties on the network adapter. |
728 | Disables the Large Send Offload (LSO) properties on the network adapter. | Disables the Large Send Offload (LSO) properties on the network adapter. |
729 | LSO properties for a network adapter. | LSO properties for a network adapter. |
730 | The LSO setting data for network adapter. | The LSO setting data for network adapter. |
731 | Associates a network adapter with its Large Send Offload (LSO) data. | Associates a network adapter with its Large Send Offload (LSO) data. |
732 | Supplies the type of offload. | Supplies the type of offload. |
733 | IPv4Arp | IPv4Arp |
734 | IPv6NS | IPv6NS |
735 | RsnRekey | RsnRekey |
736 | Supplies the identifier ID of this offload, assigned by the system. | Supplies the identifier ID of this offload, assigned by the system. |
737 | Supplies the priority of this offload. A lower value implies a higher priority offload. | Supplies the priority of this offload. A lower value implies a higher priority offload. |
738 | Supplies the friendly name of the offload. | Supplies the friendly name of the offload. |
739 | MSFT_NetAdapterPowerManagement_Offload is the base class for various network adapter offloads. | MSFT_NetAdapterPowerManagement_Offload is the base class for various network adapter offloads. |
740 | Supplies an optional IPv4 address representing the Source Protocol Address (SPA) of the ARP request. | Supplies an optional IPv4 address representing the Source Protocol Address (SPA) of the ARP request. |
741 | Supplies the IPv4 address used as the Source Protocol Address (SPA) in ARP responses. | Supplies the IPv4 address used as the Source Protocol Address (SPA) in ARP responses. |
742 | Supplies the MAC address used as the Source Hardware Address (SHA) field of the ARP response. | Supplies the MAC address used as the Source Hardware Address (SHA) field of the ARP response. |
743 | MSFT_NetAdapterPowerManagement_Offload_Arp contains settings related to ARP offloading. | MSFT_NetAdapterPowerManagement_Offload_Arp contains settings related to ARP offloading. |
744 | Supplies an optional IPv6 address representing the Source Address field in the IPv6 header of the NS message. | Supplies an optional IPv6 address representing the Source Address field in the IPv6 header of the NS message. |
745 | Supplies the solicited node IPv6 address. | Supplies the solicited node IPv6 address. |
746 | Supplies the MAC address used in the TLLA field of the NA message. | Supplies the MAC address used in the TLLA field of the NA message. |
747 | Supplies an array of two IPv6 addresses. An NA message will be sent in response to any NS message with a Target Address field matching either address in this array. | Supplies an array of two IPv6 addresses. An NA message will be sent in response to any NS message with a Target Address field matching either address in this array. |
748 | MSFT_NetAdapterPowerManagement_Offload_NS contains settings related to Neighbor Solicitation offloading. | MSFT_NetAdapterPowerManagement_Offload_NS contains settings related to Neighbor Solicitation offloading. |
749 | Supplies the key confirmation key (KCK). | Supplies the key confirmation key (KCK). |
750 | Supplies the key encryption key (KEK). | Supplies the key encryption key (KEK). |
751 | Supplies the replay counter. | Supplies the replay counter. |
752 | MSFT_NetAdapterPowerManagement_Offload_RsnRekey contains parameters for offloading the RSN Rekey protocol. | MSFT_NetAdapterPowerManagement_Offload_RsnRekey contains parameters for offloading the RSN Rekey protocol. |
753 | Supplies the type of wake pattern. | Supplies the type of wake pattern. |
754 | BitmapPattern | BitmapPattern |
755 | MagicPacket | MagicPacket |
756 | IPv4TcpSyn | IPv4TcpSyn |
757 | IPv6TcpSyn | IPv6TcpSyn |
758 | EapolRequestIdMessage | EapolRequestIdMessage |
759 | WildCard | WildCard |
760 | Supplies the system defined ID of the wake pattern | Supplies the system defined ID of the wake pattern |
761 | Supplies the priority of the wake pattern. | Supplies the priority of the wake pattern. |
762 | Supplies the friendly name of the wake pattern. | Supplies the friendly name of the wake pattern. |
763 | MSFT_NetAdapterPowerManagement_WakePattern defines a Wake-on-LAN (WOL) pattern. | MSFT_NetAdapterPowerManagement_WakePattern defines a Wake-on-LAN (WOL) pattern. |
764 | MSFT_NetAdapterPowerManagement_WakePattern_MagicPacket defines settings for 'Wake on Magic Packet'. | MSFT_NetAdapterPowerManagement_WakePattern_MagicPacket defines settings for 'Wake on Magic Packet'. |
765 | Supplies the source address of the SYN packet. | Supplies the source address of the SYN packet. |
766 | Supplies the destination address of the SYN packet. | Supplies the destination address of the SYN packet. |
767 | Supplies the TCP source port number of the SYN packet. | Supplies the TCP source port number of the SYN packet. |
768 | Supplies the TCP destination port number of the SYN packet. | Supplies the TCP destination port number of the SYN packet. |
769 | MSFT_NetAdapterPowerManagement_WakePattern_TcpSyn defines settings for a TCP SYN wake pattern. | MSFT_NetAdapterPowerManagement_WakePattern_TcpSyn defines settings for a TCP SYN wake pattern. |
770 | MSFT_NetAdapterPowerManagement_WakePattern_EapolRequestId defines settings for an 802.1X EAPOL wake pattern. | MSFT_NetAdapterPowerManagement_WakePattern_EapolRequestId defines settings for an 802.1X EAPOL wake pattern. |
771 | Supplies the pattern to match against incoming packets. | Supplies the pattern to match against incoming packets. |
772 | Supplies a mask indicating which bits of the pattern to match against incoming packets. | Supplies a mask indicating which bits of the pattern to match against incoming packets. |
773 | MSFT_NetAdapterPowerManagement_WakePattern_Bitmap defines settings for waking on a bitmap/mask wake pattern. | MSFT_NetAdapterPowerManagement_WakePattern_Bitmap defines settings for waking on a bitmap/mask wake pattern. |
774 | MSFT_NetAdapterPowerManagement_WakePattern_WildCard defines settings for 'Wake on any Packet'. | MSFT_NetAdapterPowerManagement_WakePattern_WildCard defines settings for 'Wake on any Packet'. |
775 | Supplies the setting for power management of the adapter. If the property is anything other than Enabled, the remaining property values are undefined. | Supplies the setting for power management of the adapter. If the property is anything other than Enabled, the remaining property values are undefined. |
776 | Unsupported | Unsupported |
777 | Supplies the setting for D0 Packet Coalescing on the adapter. | Supplies the setting for D0 Packet Coalescing on the adapter. |
778 | Supplies the setting for sleeping on media disconnect. If this property is Enabled, then the adapter may enter a low power state on a media disconnect event. | Supplies the setting for sleeping on media disconnect. If this property is Enabled, then the adapter may enter a low power state on a media disconnect event. |
779 | Inactive | Inactive |
780 | Supplies the setting for ARP offloads on the adapter. | Supplies the setting for ARP offloads on the adapter. |
781 | Supplies the setting for NS offloads on the adapter. | Supplies the setting for NS offloads on the adapter. |
782 | Supplies the setting for 802.11i RSN offloading. | Supplies the setting for 802.11i RSN offloading. |
783 | Supplies the parameters for protocol offloads on the adapter. | Supplies the parameters for protocol offloads on the adapter. |
784 | Supplies the setting for selective suspend on the adapter. | Supplies the setting for selective suspend on the adapter. |
785 | Supplies the setting for waking on Magic Packets. If this property is Enabled, then the adapter wakes the system on receipt of a Magic Packet. | Supplies the setting for waking on Magic Packets. If this property is Enabled, then the adapter wakes the system on receipt of a Magic Packet. |
786 | Supplies the setting for waking on a packet pattern. If this property is Enabled, then the adapter wakes the system on receipt of a specified pattern. | Supplies the setting for waking on a packet pattern. If this property is Enabled, then the adapter wakes the system on receipt of a specified pattern. |
787 | Supplies the list of packet patterns programmed to wake the system. | Supplies the list of packet patterns programmed to wake the system. |
788 | Provides a method to enable specific power management capabilities on the adapter. | Provides a method to enable specific power management capabilities on the adapter. |
789 | Provides a method to disable specific power management capabilities on the adapter. | Provides a method to disable specific power management capabilities on the adapter. |
790 | MSFT_NetAdapterPowerManagementSettingData represents the Power Management settings and features of a network adapter. | MSFT_NetAdapterPowerManagementSettingData represents the Power Management settings and features of a network adapter. |
791 | The Power Management setting data for the network adapter. | The Power Management setting data for the network adapter. |
792 | MSFT_NetAdapterPowerManagementElementSetting associates a network adapter with its MSFT_NetAdapterPowerManagementSettingData. | MSFT_NetAdapterPowerManagementElementSetting associates a network adapter with its MSFT_NetAdapterPowerManagementSettingData. |
793 | NDKPI Major Version Number | NDKPI Major Version Number |
794 | NDKPI Minor Version Number | NDKPI Minor Version Number |
795 | Vendor's organizational unique identifier (OUI) | Vendor's organizational unique identifier (OUI) |
796 | Vendor defined device ID | Vendor defined device ID |
797 | Maximum size (in bytes) of a single memory registration that the adapter can address. | Maximum size (in bytes) of a single memory registration that the adapter can address. |
798 | Maximum size (in bytes) for a single memory window | Maximum size (in bytes) for a single memory window |
799 | Fast-register memory region (FRMR) size (in PAGE_SIZE pages) for which the adapter supports the most number of FRMRs | Fast-register memory region (FRMR) size (in PAGE_SIZE pages) for which the adapter supports the most number of FRMRs |
800 | Maximum number of SGEs that can be specified in a single request over an initiator queue | Maximum number of SGEs that can be specified in a single request over an initiator queue |
801 | Maximum number of SGEs that can be specified in a single request over a receive queue | Maximum number of SGEs that can be specified in a single request over a receive queue |
802 | Maximum number of SGEs that can be specified in a read request (This overrides the MaxInitiatorRequestSge value for read requests.) | Maximum number of SGEs that can be specified in a read request (This overrides the MaxInitiatorRequestSge value for read requests.) |
803 | Maximum total length that can be referenced by all SGEs in a single send, receive, read, or write request | Maximum total length that can be referenced by all SGEs in a single send, receive, read, or write request |
804 | Maximum amount of inline data in bytes that can be sent in a single send or write request | Maximum amount of inline data in bytes that can be sent in a single send or write request |
805 | Maximum number of in-progress incoming read operations per QP | Maximum number of in-progress incoming read operations per QP |
806 | Maximum number of in-progress outgoing read operations per QP | Maximum number of in-progress outgoing read operations per QP |
807 | Maximum number of outstanding requests per receive queue | Maximum number of outstanding requests per receive queue |
808 | Maximum number of outstanding requests per initiator queue | Maximum number of outstanding requests per initiator queue |
809 | Maximum number of outstanding requests per shared receive queue. 0 means no SRQ support. | Maximum number of outstanding requests per shared receive queue. 0 means no SRQ support. |
810 | Maximum number of completion entries per completion queue | Maximum number of completion entries per completion queue |
811 | Data size hint (in bytes) above which read and write operations will yield better results than send and receive operations | Data size hint (in bytes) above which read and write operations will yield better results than send and receive operations |
812 | Maximum size, in bytes, of the private data that can be sent via a connect request | Maximum size, in bytes, of the private data that can be sent via a connect request |
813 | Maximum size, in bytes, of the private data that can be sent via an accept or reject request | Maximum size, in bytes, of the private data that can be sent via an accept or reject request |
814 | Whether the provider writes incoming data into the consumer's buffer in order, i.e., the last byte position in the consumer's buffer is guaranteed NOT to be updated before any prior byte position. | Whether the provider writes incoming data into the consumer's buffer in order, i.e., the last byte position in the consumer's buffer is guaranteed NOT to be updated before any prior byte position. |
815 | Whether the provider supports resizing CQ objects or not. If this is false, CQ resize request must NOT be used by the NDKPI consumer. | Whether the provider supports resizing CQ objects or not. If this is false, CQ resize request must NOT be used by the NDKPI consumer. |
816 | Whether the provider supports loopback connections (from a local network address on a given RNIC to the same local address on the same RNIC). | Whether the provider supports loopback connections (from a local network address on a given RNIC to the same local address on the same RNIC). |
817 | Whether the provider requires NDKPI consumer to use NDK_MR_FLAG_RDMA_READ_SINK or NDK_OP_FLAG_RDMA_READ_SINK flags when registering sink buffers for RDMA Read requests. | Whether the provider requires NDKPI consumer to use NDK_MR_FLAG_RDMA_READ_SINK or NDK_OP_FLAG_RDMA_READ_SINK flags when registering sink buffers for RDMA Read requests. |
818 | Whether the provider supports programmable interrupt moderation per completion queue through NDKPI. | Whether the provider supports programmable interrupt moderation per completion queue through NDKPI. |
819 | Whether the provider supports multiple execution engines on a given RNIC. | Whether the provider supports multiple execution engines on a given RNIC. |
820 | Network Direct Interface capabilities supported by a network adapter | Network Direct Interface capabilities supported by a network adapter |
821 | Connect performance counter missing | Connect performance counter missing |
822 | Accept performance counter missing | Accept performance counter missing |
823 | ConnectFailure performance counter missing | ConnectFailure performance counter missing |
824 | ConnectionError performance counter missing | ConnectionError performance counter missing |
825 | ActiveConnection performance counter missing | ActiveConnection performance counter missing |
826 | CompletionQueueError performance counter missing | CompletionQueueError performance counter missing |
827 | RDMAInOctets performance counter missing | RDMAInOctets performance counter missing |
828 | RDMAOutOctets performance counter missing | RDMAOutOctets performance counter missing |
829 | RDMAInFrames performance counter missing | RDMAInFrames performance counter missing |
830 | RDMAOutFrames performance counter missing | RDMAOutFrames performance counter missing |
831 | RDMA missing performance counter information for a network adapter. NetworkDirect providers are required to support all the performance counters included in NDIS_NDK_PERFORMANCE_COUNTERS. However, in the rare case that a provider cannot support a counter due to an exceptional circumstance, it must indicate so. | RDMA missing performance counter information for a network adapter. NetworkDirect providers are required to support all the performance counters included in NDIS_NDK_PERFORMANCE_COUNTERS. However, in the rare case that a provider cannot support a counter due to an exceptional circumstance, it must indicate so. |
832 | Indicates whether the ND interface is enabled or disabled on the adapter | Indicates whether the ND interface is enabled or disabled on the adapter |
833 | Maximum number of queue pairs supported by the adapter | Maximum number of queue pairs supported by the adapter |
834 | Maximum number of completion queues supported by the adapter | Maximum number of completion queues supported by the adapter |
835 | Maximum number of memory regions supported by the adapter | Maximum number of memory regions supported by the adapter |
836 | Maximum number of protection domains supported by the adapter | Maximum number of protection domains supported by the adapter |
837 | Maximum number of incoming outstanding read requests supported by the adapter. If this field is 0, there's no adapter-wide limit. There is still a limit per queue pair, which is indicated by the NetworkDirectAdapterInfo.MaxInboundReadLimit field. | Maximum number of incoming outstanding read requests supported by the adapter. If this field is 0, there's no adapter-wide limit. There is still a limit per queue pair, which is indicated by the NetworkDirectAdapterInfo.MaxInboundReadLimit field. |
838 | Maximum number of outgoing outstanding read requests supported by the adapter If this field is 0, there's no adapter-wide limit. There is still a limit per queue pair, which is indicated by the NetworkDirectAdapterInfo.MaxOutboundReadLimit field. | Maximum number of outgoing outstanding read requests supported by the adapter If this field is 0, there's no adapter-wide limit. There is still a limit per queue pair, which is indicated by the NetworkDirectAdapterInfo.MaxOutboundReadLimit field. |
839 | Maximum number of memory windows supported by the adapter | Maximum number of memory windows supported by the adapter |
840 | Maximum number of shared receive queues supported by the adapter If this field is 0, adapter does not support shared receive queues. | Maximum number of shared receive queues supported by the adapter If this field is 0, adapter does not support shared receive queues. |
841 | Rdma missing performance counter information for a network adapter. | Rdma missing performance counter information for a network adapter. |
842 | Structure that denotes NDK adapter capabilities and limits that are relevant for an individual NDKPI consumer (in contrast to system-wide limits). | Structure that denotes NDK adapter capabilities and limits that are relevant for an individual NDKPI consumer (in contrast to system-wide limits). |
843 | Enables Rdma on the network adapter. | Enables Rdma on the network adapter. |
844 | Disables Rdma on the network adapter. | Disables Rdma on the network adapter. |
845 | Rdma settings for a network adapter | Rdma settings for a network adapter |
846 | The NDI setting data for network adapter. | The NDI setting data for network adapter. |
847 | Associates a network port with its Rdma data. | Associates a network port with its Rdma data. |
848 | Indicates if the Adapter supports RSC for IPv4 TCP packets | Indicates if the Adapter supports RSC for IPv4 TCP packets |
849 | Indicates if the Adapter supports RSC for IPv6 TCP packets | Indicates if the Adapter supports RSC for IPv6 TCP packets |
850 | This class is used to report RSC capabilities on a network adapter. | This class is used to report RSC capabilities on a network adapter. |
851 | Controls RSC setting for IPv4 TCP packets. | Controls RSC setting for IPv4 TCP packets. |
852 | Controls RSC setting for IPv6 TCP packets. | Controls RSC setting for IPv6 TCP packets. |
853 | The RSC hardware capabilities of the Adapter. | The RSC hardware capabilities of the Adapter. |
854 | Indicates if RSC is currently operational for IPv4 TCP packets. | Indicates if RSC is currently operational for IPv4 TCP packets. |
855 | Indicates if RSC is currently operational for IPv6 TCP packets. | Indicates if RSC is currently operational for IPv6 TCP packets. |
856 | Indicates the cause for RSC being disabled for IPv4 TCP packets. | Indicates the cause for RSC being disabled for IPv4 TCP packets. |
857 | NoFailure | NoFailure |
858 | NicPropertyDisabled | NicPropertyDisabled |
859 | WFPCompatibility | WFPCompatibility |
860 | NDISCompatibility | NDISCompatibility |
861 | ForwardingEnabled | ForwardingEnabled |
862 | NetOffloadGlobalDisabled | NetOffloadGlobalDisabled |
863 | Indicates the cause for RSC being disabled for IPv6 TCP packets. | Indicates the cause for RSC being disabled for IPv6 TCP packets. |
864 | Enables the Receive Segment Coalescing (RSC) properties on the network adapter. | Enables the Receive Segment Coalescing (RSC) properties on the network adapter. |
865 | Disables the Receive Segment Coalescing (RSC) properties on the network adapter. | Disables the Receive Segment Coalescing (RSC) properties on the network adapter. |
866 | RSC properties for a network adapter. | RSC properties for a network adapter. |
867 | The Receive Segment Coalescing (RSC) setting data for network adapter. | The Receive Segment Coalescing (RSC) setting data for network adapter. |
868 | Associates a network adapter with its Receive Segment Coalescing (RSC) data. | Associates a network adapter with its Receive Segment Coalescing (RSC) data. |
869 | MSFT_NetAdapter_ProcessorNumber | MSFT_NetAdapter_ProcessorNumber |
870 | NDIS_RSS_PROCESSOR | NDIS_RSS_PROCESSOR |
871 | Specifies the processor selection and load balancing profile applied. | Specifies the processor selection and load balancing profile applied. |
872 | Closest Processor | Closest Processor |
873 | Closest Processor Static | Closest Processor Static |
874 | NUMA Scaling | NUMA Scaling |
875 | NUMA Scaling Static | NUMA Scaling Static |
876 | Conservative Scaling | Conservative Scaling |
877 | Specifies the processor group number for the first RSS processor. | Specifies the processor group number for the first RSS processor. |
878 | Specifies the processor number for the first RSS processor. | Specifies the processor number for the first RSS processor. |
879 | Specifies the processor group number for the last RSS processor. | Specifies the processor group number for the last RSS processor. |
880 | Specifies the processor number for the last RSS processor. | Specifies the processor number for the last RSS processor. |
881 | Specifies the maximum number of RSS processors for the network adapter. | Specifies the maximum number of RSS processors for the network adapter. |
882 | Enables the Receive Side Scaling (RSS) properties on the network adapter. | Enables the Receive Side Scaling (RSS) properties on the network adapter. |
883 | Disables the Receive Side Scaling (RSS) properties on the network adapter. | Disables the Receive Side Scaling (RSS) properties on the network adapter. |
884 | Receive Side Scale (RSS) settings for a network adapter | Receive Side Scale (RSS) settings for a network adapter |
885 | The RSS setting data for the network adapter. | The RSS setting data for the network adapter. |
886 | Associates a network adapter with its Receive Side Scale (RSS) setting data. | Associates a network adapter with its Receive Side Scale (RSS) setting data. |
887 | If True, the binding has been enabled by admin. If False, the binding has been disabled. | If True, the binding has been enabled by admin. If False, the binding has been disabled. |
888 | The display name of the transport or filter. | The display name of the transport or filter. |
889 | The component ID of the transport or filter. | The component ID of the transport or filter. |
890 | The name used by NDIS. This is typically the service name for the protocol. | The name used by NDIS. This is typically the service name for the protocol. |
891 | The class name of the network component represented by this binding. | The class name of the network component represented by this binding. |
892 | The class GUID of the network component represented by this binding. | The class GUID of the network component represented by this binding. |
893 | Characteristics of the network component represented by this binding. | Characteristics of the network component represented by this binding. |
894 | Enables a binding to a network adapter. | Enables a binding to a network adapter. |
895 | Disables a binding to a network adapter. | Disables a binding to a network adapter. |
896 | This class represents the binding information of a network adapter. | This class represents the binding information of a network adapter. |
897 | Binding information for the network adapter. | Binding information for the network adapter. |
898 | Associates a network port with its binding information. | Associates a network port with its binding information. |
899 | Reserved | Reserved |
900 | Default | Default |
901 | TCP Port | TCP Port |
902 | UDP Port | UDP Port |
903 | TCP or UDP Port | TCP or UDP Port |
904 | Ethertype | Ethertype |
905 | NetDirect Port | NetDirect Port |
906 | Specifies the protocol used in the ProtocolSpecificValue field. | Specifies the protocol used in the ProtocolSpecificValue field. |
907 | Specifies a protocol-specific value for classification. For example, this property is set to a TCP port number if ProtocolSelector is set to "TCP Port", or Ethertype value is ProtocolSelector is set to "Ethertype". | Specifies a protocol-specific value for classification. For example, this property is set to a TCP port number if ProtocolSelector is set to "TCP Port", or Ethertype value is ProtocolSelector is set to "Ethertype". |
908 | Specifies the IEEE 802.1p priority value to use when a match is made. | Specifies the IEEE 802.1p priority value to use when a match is made. |
909 | This class describes a QoS classification element. | This class describes a QoS classification element. |
910 | Transmission Selection settings are enabled. | Transmission Selection settings are enabled. |
911 | Priority to Traffic Class assignments. | Priority to Traffic Class assignments. |
912 | Transmission Selection Algorithm assignments per Traffic Class. | Transmission Selection Algorithm assignments per Traffic Class. |
913 | Bandwidth assignments per Traffic Class. | Bandwidth assignments per Traffic Class. |
914 | Flow Control settings are enabled. | Flow Control settings are enabled. |
915 | IEEE 802.1Qbb Priority Flow Control enabled per Priority. | IEEE 802.1Qbb Priority Flow Control enabled per Priority. |
916 | Classification settings are enabled. | Classification settings are enabled. |
917 | Number of classification entries. | Number of classification entries. |
918 | Classification entries. | Classification entries. |
919 | This class represents QoS settings on a network adapter. | This class represents QoS settings on a network adapter. |
920 | MACsec bypass for IEEE 802.1Qbb Priority-based Flow Control is supported. | MACsec bypass for IEEE 802.1Qbb Priority-based Flow Control is supported. |
921 | CEE DCBX is supported. | CEE DCBX is supported. |
922 | IEEE DCBX is supported. | IEEE DCBX is supported. |
923 | Number of traffic classes supported. | Number of traffic classes supported. |
924 | Number of supported traffic classes that can be enabled for IEEE 802.1Qaz Enhanced Transmission Selection. | Number of supported traffic classes that can be enabled for IEEE 802.1Qaz Enhanced Transmission Selection. |
925 | Number of supported traffic classes that can be enabled for IEEE 802.1Qbb Priority-based Flow Control. | Number of supported traffic classes that can be enabled for IEEE 802.1Qbb Priority-based Flow Control. |
926 | This class is used to report QoS capabilities on a network adapter. | This class is used to report QoS capabilities on a network adapter. |
927 | QoS functionality is enabled for the network adapter. | QoS functionality is enabled for the network adapter. |
928 | The QoS capabilities reported by the network adapter. | The QoS capabilities reported by the network adapter. |
929 | The QoS capabilities currently enabled on the network adapter. | The QoS capabilities currently enabled on the network adapter. |
930 | The operational QoS settings currently configured for the network adapter. | The operational QoS settings currently configured for the network adapter. |
931 | The remote QoS settings currently reported by the network adapter's link peer. | The remote QoS settings currently reported by the network adapter's link peer. |
932 | Enables QoS on the network adapter. | Enables QoS on the network adapter. |
933 | Disables QoS on the network adapter. | Disables QoS on the network adapter. |
934 | QoS properties for a network adapter. | QoS properties for a network adapter. |
935 | The QoS properties for the network adapter. | The QoS properties for the network adapter. |
936 | Associates a network port with its QoS properties. | Associates a network port with its QoS properties. |
937 | MSFT_NetAdapter_EncapsulationTypes | MSFT_NetAdapter_EncapsulationTypes |
938 | Defines the checksum offload encapsulation settings for the Adapter for IPv4 transmit packets. | Defines the checksum offload encapsulation settings for the Adapter for IPv4 transmit packets. |
939 | Indicates if the Adapter supports IPv4 options for transmit checksum offload. | Indicates if the Adapter supports IPv4 options for transmit checksum offload. |
940 | Indicates if the Adapter supports TCP options for transmit checksum offload on IPv4 packets. | Indicates if the Adapter supports TCP options for transmit checksum offload on IPv4 packets. |
941 | Indicates if the Adapter supports TCP checksum computation offload for transmit IPv4 packets. | Indicates if the Adapter supports TCP checksum computation offload for transmit IPv4 packets. |
942 | Indicates if the Adapter supports UDP checksum computation offload for transmit IPv4 packets. | Indicates if the Adapter supports UDP checksum computation offload for transmit IPv4 packets. |
943 | Indicates if the Adapter supports IP checksum computation offload for transmit IPv4 packets. | Indicates if the Adapter supports IP checksum computation offload for transmit IPv4 packets. |
944 | Defines the checksum offload encapsulation settings for the Adapter for IPv4 receive packets. | Defines the checksum offload encapsulation settings for the Adapter for IPv4 receive packets. |
945 | Indicates if the Adapter supports IPv4 options for receive checksum offload. | Indicates if the Adapter supports IPv4 options for receive checksum offload. |
946 | Indicates if the Adapter supports TCP options for receive checksum offload on IPv4 packets. | Indicates if the Adapter supports TCP options for receive checksum offload on IPv4 packets. |
947 | Indicates if the Adapter supports TCP checksum validation offload for receive IPv4 packets. | Indicates if the Adapter supports TCP checksum validation offload for receive IPv4 packets. |
948 | Indicates if the Adapter supports UDP checksum validation offload for receive IPv4 packets. | Indicates if the Adapter supports UDP checksum validation offload for receive IPv4 packets. |
949 | Indicates if the Adapter supports IP checksum validation offload for receive IPv4 packets. | Indicates if the Adapter supports IP checksum validation offload for receive IPv4 packets. |
950 | Defines the checksum offload encapsulation settings for the Adapter for IPv6 transmit packets. | Defines the checksum offload encapsulation settings for the Adapter for IPv6 transmit packets. |
951 | Indicates if the Adapter supports IPv6 extension headers for transmit checksum offload. | Indicates if the Adapter supports IPv6 extension headers for transmit checksum offload. |
952 | Indicates if the Adapter supports TCP options for transmit checksum offload on IPv6 packets. | Indicates if the Adapter supports TCP options for transmit checksum offload on IPv6 packets. |
953 | Indicates if the Adapter supports TCP checksum computation offload for transmit IPv6 packets. | Indicates if the Adapter supports TCP checksum computation offload for transmit IPv6 packets. |
954 | Indicates if the Adapter supports UDP checksum computation offload for transmit IPv6 packets. | Indicates if the Adapter supports UDP checksum computation offload for transmit IPv6 packets. |
955 | Defines the checksum offload encapsulation settings for the Adapter for IPv6 receive packets. | Defines the checksum offload encapsulation settings for the Adapter for IPv6 receive packets. |
956 | Indicates if the Adapter supports IPv6 extension headers for receive checksum offload. | Indicates if the Adapter supports IPv6 extension headers for receive checksum offload. |
957 | Indicates if the Adapter supports TCP options for receive checksum offload on IPv6 packets. | Indicates if the Adapter supports TCP options for receive checksum offload on IPv6 packets. |
958 | Indicates if the Adapter supports TCP checksum validation offload for receive IPv6 packets. | Indicates if the Adapter supports TCP checksum validation offload for receive IPv6 packets. |
959 | Indicates if the Adapter supports UDP checksum validation offload for receive IPv6 packets. | Indicates if the Adapter supports UDP checksum validation offload for receive IPv6 packets. |
960 | MSFT_NetAdapter_ChecksumOffload | MSFT_NetAdapter_ChecksumOffload |
961 | Indicates if IP checksum offload is currently enabled for IPv4 packets on this Adapter. | Indicates if IP checksum offload is currently enabled for IPv4 packets on this Adapter. |
962 | TxEnabled | TxEnabled |
963 | RxEnabled | RxEnabled |
964 | RxTxEnabled | RxTxEnabled |
965 | Indicates if TCP checksum offload is currently enabled for IPv4 packets on this Adapter. | Indicates if TCP checksum offload is currently enabled for IPv4 packets on this Adapter. |
966 | Indicates if TCP checksum offload is currently enabled for IPv6 packets on this Adapter. | Indicates if TCP checksum offload is currently enabled for IPv6 packets on this Adapter. |
967 | Indicates if UDP checksum offload is currently enabled for IPv4 packets on this Adapter. | Indicates if UDP checksum offload is currently enabled for IPv4 packets on this Adapter. |
968 | Indicates if UDP checksum offload is currently enabled for IPv6 packets on this Adapter. | Indicates if UDP checksum offload is currently enabled for IPv6 packets on this Adapter. |
969 | The checksum offload hardware capabilities of the Adapter. | The checksum offload hardware capabilities of the Adapter. |
970 | Enables the TCPIP checksum offload properties on the network adapter. | Enables the TCPIP checksum offload properties on the network adapter. |
971 | Disables the TCPIP checksum offload properties on the network adapter. | Disables the TCPIP checksum offload properties on the network adapter. |
972 | MSFT_NetAdapterChecksumOffloadSettingData | MSFT_NetAdapterChecksumOffloadSettingData |
973 | The TCPIP checksum offload setting data for network adapter. | The TCPIP checksum offload setting data for network adapter. |
974 | Associates a network adapter with its TCPIP checksum offload data. | Associates a network adapter with its TCPIP checksum offload data. |
975 | A boolean value that is set to TRUE if VMQ is enabled and FALSE if it is not. | A boolean value that is set to TRUE if VMQ is enabled and FALSE if it is not. |
976 | Number of receive queues that the network adapter supports. | Number of receive queues that the network adapter supports. |
977 | The total number of MAC addresses that the network adapter supports. | The total number of MAC addresses that the network adapter supports. |
978 | Number of supported MAC addresses per port. | Number of supported MAC addresses per port. |
979 | Number of VLANs supported per port. | Number of VLANs supported per port. |
980 | Indicates that the network adapter supports filtering received packets based on the VLAN ID. | Indicates that the network adapter supports filtering received packets based on the VLAN ID. |
981 | Indicates that the network adapter supports splitting the received packets at a lookahead offset. | Indicates that the network adapter supports splitting the received packets at a lookahead offset. |
982 | The minimum size, in bytes, of the lookahead segment if lookahead split is enabled. | The minimum size, in bytes, of the lookahead segment if lookahead split is enabled. |
983 | The maximum size, in bytes, of the lookahead segment if lookahead split is enabled. | The maximum size, in bytes, of the lookahead segment if lookahead split is enabled. |
984 | Indicates that the network adapter supports filtering received packets matching a MAC address and any arbitrary VLAN ID. | Indicates that the network adapter supports filtering received packets matching a MAC address and any arbitrary VLAN ID. |
985 | Indicates that the network adapter supports changing the processor affinity of a queue dynamically and without restarting the queue. | Indicates that the network adapter supports changing the processor affinity of a queue dynamically and without restarting the queue. |
986 | Indicate that the network adapter supports using the same interrupt vector for multiple queues when all those queues are targeted to the same processor. | Indicate that the network adapter supports using the same interrupt vector for multiple queues when all those queues are targeted to the same processor. |
987 | Specifies the processor group number for the first VMQ processor. | Specifies the processor group number for the first VMQ processor. |
988 | Specifies the processor number for the first VMQ processor. | Specifies the processor number for the first VMQ processor. |
989 | Specifies the maximum number of VMQ processors for the network adapter. | Specifies the maximum number of VMQ processors for the network adapter. |
990 | Specifies the NUMA Node for the RSS Processors. | Specifies the NUMA Node for the RSS Processors. |
991 | Enables the Virtual Machine Queue (VMQ) on the network adapter. | Enables the Virtual Machine Queue (VMQ) on the network adapter. |
992 | Disables the Virtual Machine Queue (VMQ) on the network adapter. | Disables the Virtual Machine Queue (VMQ) on the network adapter. |
993 | Network adapter Virtual Machine Queue (VMQ) settings | Network adapter Virtual Machine Queue (VMQ) settings |
994 | The VMQ setting data for the network adapter. | The VMQ setting data for the network adapter. |
995 | Associates a network adapter with its Virtual Machine Queue (VMQ) setting data. | Associates a network adapter with its Virtual Machine Queue (VMQ) setting data. |
996 | Indicates if VLANs are supported | Indicates if VLANs are supported |
997 | Indicates if Interrupt moderation is supported per VPort | Indicates if Interrupt moderation is supported per VPort |
998 | Indicates if asymmetric queue pairs are supported for non-default VPorts | Indicates if asymmetric queue pairs are supported for non-default VPorts |
999 | Indicates if VF RSS is supported | Indicates if VF RSS is supported |
1000 | Indicates if a single VPort Pool is supported | Indicates if a single VPort Pool is supported |
1001 | The maximum number of switches that can be created on the adapter | The maximum number of switches that can be created on the adapter |
1002 | The maximum number of VPorts that can be created on the adapter | The maximum number of VPorts that can be created on the adapter |
1003 | The maximum number of Virtual Functions that can be created on the adapter | The maximum number of Virtual Functions that can be created on the adapter |
1004 | The maximum number of queue pairs that can be allocated on the adapter | The maximum number of queue pairs that can be allocated on the adapter |
1005 | The maximum number of queue pairs for the non-default VPort | The maximum number of queue pairs for the non-default VPort |
1006 | The maximum number of MAC addresses that can be allocated on the adapter | The maximum number of MAC addresses that can be allocated on the adapter |
1007 | SRIOV Capabilities | SRIOV Capabilities |
1008 | Indicates if SRIOV is currently enabled on the Adapter. | Indicates if SRIOV is currently enabled on the Adapter. |
1009 | Indicates the SRIOV support for the device. | Indicates the SRIOV support for the device. |
1010 | The SRIOV capabilities reported by the network adapter. | The SRIOV capabilities reported by the network adapter. |
1011 | The SRIOV capabilities currently enabled on the network adapter. | The SRIOV capabilities currently enabled on the network adapter. |
1012 | External | External |
1013 | Indicates the type of the embedded switch | Indicates the type of the embedded switch |
1014 | The name of the switch | The name of the switch |
1015 | The number of Virtual Functions that can be allocated on the switch | The number of Virtual Functions that can be allocated on the switch |
1016 | The number of Virtual Functions currently allocated. | The number of Virtual Functions currently allocated. |
1017 | The number of VPorts that can be allocated on the switch | The number of VPorts that can be allocated on the switch |
1018 | The number of VPorts currently allocated on the switch | The number of VPorts currently allocated on the switch |
1019 | The number of Queue pairs for the default VPort | The number of Queue pairs for the default VPort |
1020 | The number of Queue pairs for the non-default VPort | The number of Queue pairs for the non-default VPort |
1021 | The number of active MAC addresses on the default VPort. | The number of active MAC addresses on the default VPort. |
1022 | The number of active MAC addresses on the non-default VPorts | The number of active MAC addresses on the non-default VPorts |
1023 | The number of active VLAN IDs on the default VPort | The number of active VLAN IDs on the default VPort |
1024 | The number of active VLAN IDs on the non-default VPorts | The number of active VLAN IDs on the non-default VPorts |
1025 | Enables the SRIOV properties on the network adapter. | Enables the SRIOV properties on the network adapter. |
1026 | Disables the SRIOV properties on the network adapter. | Disables the SRIOV properties on the network adapter. |
1027 | SRIOV settings for a network adapter | SRIOV settings for a network adapter |
1028 | The RSS setting data for network adapter. | The RSS setting data for network adapter. |
1029 | Associates a network port with its SRIOV data. | Associates a network port with its SRIOV data. |
1030 | Filter identifier. | Filter identifier. |
1031 | The MAC address filter. | The MAC address filter. |
1032 | The VLAN ID filter. This value may be NULL. | The VLAN ID filter. This value may be NULL. |
1033 | MAC address and VLAN ID filters for VMQ and VPorts | MAC address and VLAN ID filters for VMQ and VPorts |
1034 | The queue identifier | The queue identifier |
1035 | The operational state of the queue. | The operational state of the queue. |
1036 | Undefined | Undefined |
1037 | DmaStopped | DmaStopped |
1038 | The number of MAC address and VLAN ID filters set on the queue. | The number of MAC address and VLAN ID filters set on the queue. |
1039 | A bitmap that specifies the CPU that the queue has affinity with. For example, setting bit 0 indicates CPU 0 is used, setting bit 1 indicates CPU 1 is used, and so on. | A bitmap that specifies the CPU that the queue has affinity with. For example, setting bit 0 indicates CPU 0 is used, setting bit 1 indicates CPU 1 is used, and so on. |
1040 | The group number for the processors specified in ProcessorAffinityMask property. | The group number for the processors specified in ProcessorAffinityMask property. |
1041 | The ID of the Virtual Machine to which the queue is assigned. | The ID of the Virtual Machine to which the queue is assigned. |
1042 | The friendly name the Virtual Machine to which the queue is assigned. | The friendly name the Virtual Machine to which the queue is assigned. |
1043 | A string that identifies the queue. | A string that identifies the queue. |
1044 | An array of MAC address and VLAN ID pair filters set on the queue. | An array of MAC address and VLAN ID pair filters set on the queue. |
1045 | Network adapter VMQ settings for each queue | Network adapter VMQ settings for each queue |
1046 | The VMQ Queue setting data for the network adapter. | The VMQ Queue setting data for the network adapter. |
1047 | Associates a network adapter with the setting data of its VMQ queues. | Associates a network adapter with the setting data of its VMQ queues. |
1048 | The ID of the VPort. | The ID of the VPort. |
1049 | The name of the VPort. | The name of the VPort. |
1050 | The identifier of the switch. | The identifier of the switch. |
1051 | The ID of the attached function. This could be the Vf or the PF ID. | The ID of the attached function. This could be the Vf or the PF ID. |
1052 | The number of queue pairs. | The number of queue pairs. |
1053 | Adaptive | Adaptive |
1054 | Off | Off |
1055 | Low | Low |
1056 | Medium | Medium |
1057 | High | High |
1058 | The interrupt moderation for the VPort. | The interrupt moderation for the VPort. |
1059 | Activated | Activated |
1060 | DeActivated | DeActivated |
1061 | The state of the VPort. | The state of the VPort. |
1062 | An array of MAC address and VLAN ID pair filters set on the VPort. | An array of MAC address and VLAN ID pair filters set on the VPort. |
1063 | Network adapter Virtual Port settings. | Network adapter Virtual Port settings. |
1064 | The VPort setting data for the network adapter. | The VPort setting data for the network adapter. |
1065 | Associates a network adapter with its virtual port data. | Associates a network adapter with its virtual port data. |
1066 | The Virtual Function ID. | The Virtual Function ID. |
1067 | The friendly name of the Virtual Machine to which the Virtual Function is assigned. | The friendly name of the Virtual Machine to which the Virtual Function is assigned. |
1068 | The ID of the Virtual Machine to which the Virtual Function is assigned. | The ID of the Virtual Machine to which the Virtual Function is assigned. |
1069 | The VM NIC ID to which the Virtual Function is associated. | The VM NIC ID to which the Virtual Function is associated. |
1070 | The current MAC address of the Virtual Function. | The current MAC address of the Virtual Function. |
1071 | The permanent MAC address of the Virtual Function. | The permanent MAC address of the Virtual Function. |
1072 | The list of Virtual Port IDs attached to this Virtual Function. | The list of Virtual Port IDs attached to this Virtual Function. |
1073 | SRIOV VPort settings for a network adapter | SRIOV VPort settings for a network adapter |
1074 | The SRIOV setting data for a network adapter. | The SRIOV setting data for a network adapter. |
1075 | Associates a network port with its SRIOV VF data. | Associates a network port with its SRIOV VF data. |
1076 | Set the IPsec Task Offload v2 properties on the network adapter. | Set the IPsec Task Offload v2 properties on the network adapter. |
1077 | Enable IPsec Task Offload v2 on the network adapter. | Enable IPsec Task Offload v2 on the network adapter. |
1078 | Disable IPsec Task Offload v2 on the network adapter. | Disable IPsec Task Offload v2 on the network adapter. |
1079 | IPsec Task Offload v2 settings for a network adapter | IPsec Task Offload v2 settings for a network adapter |
1080 | Associates a network adapter with its IPsec Task Offload v2 setting data. | Associates a network adapter with its IPsec Task Offload v2 setting data. |
1081 | Number of outbound RDMA connections established successfully | Number of outbound RDMA connections established successfully |
1082 | Number of inbound RDMA connections established successfully | Number of inbound RDMA connections established successfully |
1083 | Number of inbound and outbound failed RDMA connection attempts | Number of inbound and outbound failed RDMA connection attempts |
1084 | Number of successfully established RDMA connections on which an error occurred before being disconnected by local or remote client | Number of successfully established RDMA connections on which an error occurred before being disconnected by local or remote client |
1085 | Number of active RDMA connections | Number of active RDMA connections |
1086 | Number of RDMA completion queues that went into an error state | Number of RDMA completion queues that went into an error state |
1087 | Number of bytes received at layer 2 for all inbound RDMA traffic | Number of bytes received at layer 2 for all inbound RDMA traffic |
1088 | Number of bytes sent at layer 2 for all outbound RDMA traffic | Number of bytes sent at layer 2 for all outbound RDMA traffic |
1089 | Number of layer 2 frames received for all inbound RDMA traffic | Number of layer 2 frames received for all inbound RDMA traffic |
1090 | Number of layer 2 frames sent for all outbound RDMA traffic | Number of layer 2 frames sent for all outbound RDMA traffic |
1091 | RDMA statistics supported by a network adapter | RDMA statistics supported by a network adapter |
1092 | Total number of packets that have resulted from one or more coalescing events | Total number of packets that have resulted from one or more coalescing events |
1093 | Total number of bytes that have resulted from one or more coalescing events | Total number of bytes that have resulted from one or more coalescing events |
1094 | Total number of cases where an incoming packet is found eligible for coalescing | Total number of cases where an incoming packet is found eligible for coalescing |
1095 | Total number of cases where an incoming packet is found ineligible for coalescing | Total number of cases where an incoming packet is found ineligible for coalescing |
1096 | RSC statistics supported by a network adapter | RSC statistics supported by a network adapter |
1097 | The supported statistics | The supported statistics |
1098 | The number of bytes of data received without errors through this interface. This value includes bytes in unicast, broadcast, and multicast packets. | The number of bytes of data received without errors through this interface. This value includes bytes in unicast, broadcast, and multicast packets. |
1099 | The number of unicast packets received without errors through this interface. | The number of unicast packets received without errors through this interface. |
1100 | The number of multicast packets received without errors through this interface. | The number of multicast packets received without errors through this interface. |
1101 | The number of broadcast packets received without errors through this interface. | The number of broadcast packets received without errors through this interface. |
1102 | The number of unicast bytes received without errors through this interface. | The number of unicast bytes received without errors through this interface. |
1103 | The number of multicast bytes received without errors through this interface. | The number of multicast bytes received without errors through this interface. |
1104 | The number of broadcast bytes received without errors through this interface. | The number of broadcast bytes received without errors through this interface. |
1105 | The number of inbound packets which were chosen to be discarded even though no errors were detected to prevent the packets from being deliverable to a higher-layer protocol. | The number of inbound packets which were chosen to be discarded even though no errors were detected to prevent the packets from being deliverable to a higher-layer protocol. |
1106 | The number of incoming packets that were discarded because of errors. | The number of incoming packets that were discarded because of errors. |
1107 | The number of bytes of data transmitted without errors through this interface. This value includes bytes in unicast, broadcast, and multicast packets. | The number of bytes of data transmitted without errors through this interface. This value includes bytes in unicast, broadcast, and multicast packets. |
1108 | The number of unicast packets transmitted without errors through this interface. | The number of unicast packets transmitted without errors through this interface. |
1109 | The number of multicast packets transmitted without errors through this interface. | The number of multicast packets transmitted without errors through this interface. |
1110 | The number of broadcast packets transmitted without errors through this interface. | The number of broadcast packets transmitted without errors through this interface. |
1111 | The number of unicast bytes transmitted without errors through this interface. | The number of unicast bytes transmitted without errors through this interface. |
1112 | The number of multicast bytes transmitted without errors through this interface. | The number of multicast bytes transmitted without errors through this interface. |
1113 | The number of broadcast bytes transmitted without errors through this interface. | The number of broadcast bytes transmitted without errors through this interface. |
1114 | The number of outgoing packets that were discarded even though they did not have errors. | The number of outgoing packets that were discarded even though they did not have errors. |
1115 | The number of outgoing packets that were discarded because of errors. | The number of outgoing packets that were discarded because of errors. |
1116 | RDMA statistics | RDMA statistics |
1117 | RSC statistics | RSC statistics |
1118 | Network adapter statistics | Network adapter statistics |
1119 | The statistics setting data for the network adapter. | The statistics setting data for the network adapter. |
1120 | Associates a network adapter with the setting data of its statistics. | Associates a network adapter with the setting data of its statistics. |
1121 | Capability | Capability |
1122 | Drain notification is supported on any PD queue. | Drain notification is supported on any PD queue. |
1123 | Moderation of drain notifications based on a moderation interval value on any PD queue is supported. | Moderation of drain notifications based on a moderation interval value on any PD queue is supported. |
1124 | Moderation of drain notifications based on a moderation count value on any PD queue is supported. | Moderation of drain notifications based on a moderation count value on any PD queue is supported. |
1125 | Maximum number of partial PD_BUFFERs which can be posted to a PD transmit queue as a chain to be transmitted as a single layer 2 frame. | Maximum number of partial PD_BUFFERs which can be posted to a PD transmit queue as a chain to be transmitted as a single layer 2 frame. |
1126 | Maximum number of partial PD_BUFFERs which can be returned by the PD provider from a PD receive queue as a chain which forms a single coalesced packet. | Maximum number of partial PD_BUFFERs which can be returned by the PD provider from a PD receive queue as a chain which forms a single coalesced packet. |
1127 | Maximum number of PD receive queues that can be allocated on the adapter. RSS receive queues are not included in this number. | Maximum number of PD receive queues that can be allocated on the adapter. RSS receive queues are not included in this number. |
1128 | Maximum number of PD transmit queues that can be allocated on the adapter. | Maximum number of PD transmit queues that can be allocated on the adapter. |
1129 | Maximum number of PD receive queues that can be allocated on the default VPort. RSS receive queues are not included in this number. | Maximum number of PD receive queues that can be allocated on the default VPort. RSS receive queues are not included in this number. |
1130 | Maximum number of PD transmit queues that can be allocated on the default VPort. | Maximum number of PD transmit queues that can be allocated on the default VPort. |
1131 | Maximum number of PD receive queues that can be allocated on a nondefault VPort. RSS receive queues are not included in this number. | Maximum number of PD receive queues that can be allocated on a nondefault VPort. RSS receive queues are not included in this number. |
1132 | Maximum number of PD transmit queues that can be allocated on a nondefault VPort. | Maximum number of PD transmit queues that can be allocated on a nondefault VPort. |
1133 | Shortest moderation interval supported in nanoseconds. | Shortest moderation interval supported in nanoseconds. |
1134 | Longest moderation interval supported in nanoseconds. | Longest moderation interval supported in nanoseconds. |
1136 | Maximum supported size for a PD receive queue. A value of 0 indicates that the adapter does not have a hard limit. | Maximum supported size for a PD receive queue. A value of 0 indicates that the adapter does not have a hard limit. |
1137 | Maximum supported size for a PD transmit queue. A value of 0 indicates that the adapter does not have a hard limit. | Maximum supported size for a PD transmit queue. A value of 0 indicates that the adapter does not have a hard limit. |
1138 | This class is used to report PacketDirect capabilities on a network adapter. | This class is used to report PacketDirect capabilities on a network adapter. |
1139 | PacketDirect functionality is administratively enabled for the network adapter. | PacketDirect functionality is administratively enabled for the network adapter. |
1140 | PacketDirect functionality is operational on the network adapter. | PacketDirect functionality is operational on the network adapter. |
1142 | PacketDirect buffer management domain identifier for the adapter. | PacketDirect buffer management domain identifier for the adapter. |
1143 | DMA address width supported by the adapter. | DMA address width supported by the adapter. |
1144 | The PacketDirect capabilities reported by the network adapter. | The PacketDirect capabilities reported by the network adapter. |
1145 | Enables PacketDirect on the network adapter. | Enables PacketDirect on the network adapter. |
1146 | Disables PacketDirect on the network adapter. | Disables PacketDirect on the network adapter. |
1147 | PacketDirect properties for a network adapter. | PacketDirect properties for a network adapter. |
1148 | The PacketDirect properties for the network adapter. | The PacketDirect properties for the network adapter. |
1149 | Associates a network port with its PacketDirect properties. | Associates a network port with its PacketDirect properties. |
1150 | Granularity of intermediate moderation interval values supported between the MinimumModerationInterval and MaximumModerationInterval values. | Granularity of intermediate moderation interval values supported between the MinimumModerationInterval and MaximumModerationInterval values. |
1151 | PacketDirect diagnostic state of the adapter. | PacketDirect diagnostic state of the adapter. |
1156 | Indicates if VXLAN Encapsulated Packet Task Offloads are currently enabled for this Adapter | Indicates if VXLAN Encapsulated Packet Task Offloads are currently enabled for this Adapter |
1159 | Describes VXLAN Encapsulated Packet Task Offload hardware capabilities of this Adapter | Describes VXLAN Encapsulated Packet Task Offload hardware capabilities of this Adapter |
1160 | Type of Encapsulation - NVGRE (1) or VXLAN (2) with possibility to bitwise combine | Type of Encapsulation - NVGRE (1) or VXLAN (2) with possibility to bitwise combine |
1161 | Specifies the UDP Port Number for VXLAN Traffic. | Specifies the UDP Port Number for VXLAN Traffic. |
1162 | This class is used to define the capabilities of the NVGRE encapsulation type supported by a network adapter for task offloads. | This class is used to define the capabilities of the NVGRE encapsulation type supported by a network adapter for task offloads. |
1163 | This class is used to define the capabilities of the VXLAN encapsulation type supported by a network adapter for task offloads. | This class is used to define the capabilities of the VXLAN encapsulation type supported by a network adapter for task offloads. |
1164 | NVGRE | NVGRE |
1165 | VXLAN | VXLAN |
1166 | Indicates if NVGRE Encapsulated Packet Task Offloads are currently enabled for this Adapter | Indicates if NVGRE Encapsulated Packet Task Offloads are currently enabled for this Adapter |
1167 | Describes NVGRE Encapsulated Packet Task Offload hardware capabilities of this Adapter | Describes NVGRE Encapsulated Packet Task Offload hardware capabilities of this Adapter |
1168 | Specifies whether or not the UDP Port Number for VXLAN Traffic can be configured. | Specifies whether or not the UDP Port Number for VXLAN Traffic can be configured. |
2101 | ARP Offload | ARP Offload |
2102 | Filtered Interrupt Moderation | Filtered Interrupt Moderation |
2103 | Sleep on Disconnect | Sleep on Disconnect |
2104 | NS Offload | NS Offload |
2105 | WiFi Rekey Offload | WiFi Rekey Offload |
2106 | Selective Suspend | Selective Suspend |
2107 | Wake on Magic Packet | Wake on Magic Packet |
2108 | Wake on Pattern | Wake on Pattern |
2120 | Applying new settings to %1!s! | Applying new settings to %1!s! |
2121 | Adapter %1!s! not found. | Adapter %1!s! not found. |
2122 | Adapter %1!s!: %2!s!: Set failed with error %3!8.8x! | Adapter %1!s!: %2!s!: Set failed with error %3!8.8x! |
2123 | Adapter %1!s!: %2!s!: Invalid configuration value %3!d! | Adapter %1!s!: %2!s!: Invalid configuration value %3!d! |
2124 | Adapter %1!s!: Restarting | Adapter %1!s!: Restarting |
2125 | Adapter %1!s!: |
Adapter %1!s!: |
2126 | %1!s! will be enabled |
%1!s! will be enabled |
2127 | %1!s! will be disabled |
%1!s! will be disabled |
2128 | The adapter will be restarted to apply the changes. | The adapter will be restarted to apply the changes. |
2129 | The adapter will not be restarted. | The adapter will not be restarted. |
2130 | The computer will be allowed to power down the device. |
The computer will be allowed to power down the device. |
2131 | The computer will not be allowed to power down the device. |
The computer will not be allowed to power down the device. |
2201 | $true | $true |
2202 | $false | $false |
2203 | -Enabled $true | -Enabled $true |
2204 | -Enabled $false | -Enabled $false |
2205 | -NoRestart | -NoRestart |
2206 | -IncludeHidden | -IncludeHidden |
2207 | -PassThru | -PassThru |
2208 | -Name "%1!s!' | -Name "%1!s!' |
2209 | -InterfaceDescription '%1!s!' | -InterfaceDescription '%1!s!' |
2350 | Rename-NetAdapter -Name '%1!s!' -NewName '%2!s!' | Rename-NetAdapter -Name '%1!s!' -NewName '%2!s!' |
2351 | Enable-NetAdapter '%1!s!' | Enable-NetAdapter '%1!s!' |
2352 | Disable-NetAdapter '%1!s!' | Disable-NetAdapter '%1!s!' |
2353 | Restart-NetAdapter '%1!s!' | Restart-NetAdapter '%1!s!' |
2356 | Set-NetAdapter '%1!s!' | Set-NetAdapter '%1!s!' |
2357 | -MacAddress %1!s! | -MacAddress %1!s! |
2358 | -VlanID %1!d! | -VlanID %1!d! |
2420 | Set-NetAdapterRss '%1!s!' | Set-NetAdapterRss '%1!s!' |
2421 | Enable-NetAdapterRss '%1!s!' | Enable-NetAdapterRss '%1!s!' |
2422 | Disable-NetAdapterRss '%1!s!' | Disable-NetAdapterRss '%1!s!' |
2423 | -BaseProcessorGroup %1!d! | -BaseProcessorGroup %1!d! |
2424 | -BaseProcessorNumber %1!d! | -BaseProcessorNumber %1!d! |
2425 | -MaxProcessors %1!d! | -MaxProcessors %1!d! |
2426 | -NumaNode %1!d! | -NumaNode %1!d! |
2427 | -NumberOfReceiveQueues %1!d! | -NumberOfReceiveQueues %1!d! |
2428 | -Profile %1!d! | -Profile %1!d! |
2429 | -MaxProcessorGroup %1!d! | -MaxProcessorGroup %1!d! |
2430 | -MaxProcessorNumber %1!d! | -MaxProcessorNumber %1!d! |
2520 | Set-NetAdapterVmq '%1!s!' | Set-NetAdapterVmq '%1!s!' |
2521 | Enable-NetAdapterVmq '%1!s!' | Enable-NetAdapterVmq '%1!s!' |
2522 | Disable-NetAdapterVmq '%1!s!' | Disable-NetAdapterVmq '%1!s!' |
2600 | Invalid registry data type specified for keyword '%1!s!'. Valid types are REG_SZ, REG_DWORD, REG_MULTI_SZ, and REG_QWORD. | Invalid registry data type specified for keyword '%1!s!'. Valid types are REG_SZ, REG_DWORD, REG_MULTI_SZ, and REG_QWORD. |
2601 | Either a display value or registry value must be specified | Either a display value or registry value must be specified |
2603 | -AllProperties | -AllProperties |
2604 | Registry keyword must be configured by specifying a registry value | Registry keyword must be configured by specifying a registry value |
2605 | Registry data type cannot be changed | Registry data type cannot be changed |
2606 | Cannot reset a property that has no default value | Cannot reset a property that has no default value |
2607 | No matching combination of display and keyword values found. The following are valid display values: %1!s! The corresponding valid keyword values: %2!s! |
No matching combination of display and keyword values found. The following are valid display values: %1!s! The corresponding valid keyword values: %2!s! |
2608 | No matching display value found. The following are valid display values: %1!s! | No matching display value found. The following are valid display values: %1!s! |
2609 | No matching keyword value found. The following are valid keyword values: %1!s! | No matching keyword value found. The following are valid keyword values: %1!s! |
2610 | Value must be within the range %1!s! - %2!s! | Value must be within the range %1!s! - %2!s! |
2611 | Value must be within the range %1!s! - %2!s!, in increments of %3!s! | Value must be within the range %1!s! - %2!s!, in increments of %3!s! |
2620 | Set-NetAdapterAdvancedProperty '%1!s!' | Set-NetAdapterAdvancedProperty '%1!s!' |
2621 | New-NetAdapterAdvancedProperty '%1!s!' | New-NetAdapterAdvancedProperty '%1!s!' |
2622 | Remove-NetAdapterAdvancedProperty '%1!s!' | Remove-NetAdapterAdvancedProperty '%1!s!' |
2623 | Reset-NetAdapterAdvancedProperty '%1!s!' | Reset-NetAdapterAdvancedProperty '%1!s!' |
2624 | -DisplayName '%1!s!' | -DisplayName '%1!s!' |
2625 | -DisplayValue '%1!s!' | -DisplayValue '%1!s!' |
2626 | -RegistryKeyword '%1!s!' | -RegistryKeyword '%1!s!' |
2627 | -RegistryValue '%1!s!' | -RegistryValue '%1!s!' |
2629 | -RegistryDataType REG_DWORD | -RegistryDataType REG_DWORD |
2630 | -RegistryDataType REG_QWORD | -RegistryDataType REG_QWORD |
2631 | -RegistryDataType REG_SZ | -RegistryDataType REG_SZ |
2632 | -RegistryDataType REG_MULTI_SZ | -RegistryDataType REG_MULTI_SZ |
2634 | ,'%1!s!' | ,'%1!s!' |
2700 | Network Configuration | Network Configuration |
2701 | Waiting for an outstanding configuration task to complete | Waiting for an outstanding configuration task to complete |
2720 | Set-NetAdapterBinding '%1!s!' | Set-NetAdapterBinding '%1!s!' |
2721 | Enable-NetAdapterBinding '%1!s!' | Enable-NetAdapterBinding '%1!s!' |
2722 | Disable-NetAdapterBinding '%1!s!' | Disable-NetAdapterBinding '%1!s!' |
2724 | -ComponentID '%1!s!' | -ComponentID '%1!s!' |
2800 | Set-NetAdapterQos '%1!s!' | Set-NetAdapterQos '%1!s!' |
2801 | Enable-NetAdapterQos '%1!s!' | Enable-NetAdapterQos '%1!s!' |
2802 | Disable-NetAdapterQos '%1!s!' | Disable-NetAdapterQos '%1!s!' |
2920 | Set-NetAdapterRdma "%1!s!" | Set-NetAdapterRdma "%1!s!" |
2921 | Enable-NetAdapterRdma "%1!s!" | Enable-NetAdapterRdma "%1!s!" |
2922 | Disable-NetAdapterRdma "%1!s!" | Disable-NetAdapterRdma "%1!s!" |
3000 | Set-NetAdapterChecksumOffload "%1!s!" | Set-NetAdapterChecksumOffload "%1!s!" |
3001 | Enable-NetAdapterChecksumOffload "%1!s!" | Enable-NetAdapterChecksumOffload "%1!s!" |
3002 | Disable-NetAdapterChecksumOffload "%1!s!" | Disable-NetAdapterChecksumOffload "%1!s!" |
3007 | -IpIPv4 '%1!s!' | -IpIPv4 '%1!s!' |
3008 | -TcpIPv4 '%1!s!' | -TcpIPv4 '%1!s!' |
3009 | -TcpIPv6 '%1!s!' | -TcpIPv6 '%1!s!' |
3010 | -UdpIPv4 '%1!s!' | -UdpIPv4 '%1!s!' |
3011 | -UdpIPv6 '%1!s!' | -UdpIPv6 '%1!s!' |
3100 | Set-NetAdapterLso "%1!s!" | Set-NetAdapterLso "%1!s!" |
3101 | Enable-NetAdapterLso "%1!s!" | Enable-NetAdapterLso "%1!s!" |
3102 | Disable-NetAdapterLso "%1!s!" | Disable-NetAdapterLso "%1!s!" |
3103 | -V1IPv4 '%1!s!' | -V1IPv4 '%1!s!' |
3104 | -IPv4 '%1!s!' | -IPv4 '%1!s!' |
3105 | -IPv6 '%1!s!' | -IPv6 '%1!s!' |
3200 | Set-NetAdapterRsc "%1!s!" | Set-NetAdapterRsc "%1!s!" |
3201 | Enable-NetAdapterRsc "%1!s!" | Enable-NetAdapterRsc "%1!s!" |
3202 | Disable-NetAdapterRsc "%1!s!" | Disable-NetAdapterRsc "%1!s!" |
3300 | Set-NetAdapterEncapsulatedPacketTaskOffload "%1!s!" | Set-NetAdapterEncapsulatedPacketTaskOffload "%1!s!" |
3301 | Enable-NetAdapterEncapsulatedPacketTaskOffload "%1!s!" | Enable-NetAdapterEncapsulatedPacketTaskOffload "%1!s!" |
3302 | Disable-NetAdapterEncapsulatedPacketTaskOffload "%1!s!" | Disable-NetAdapterEncapsulatedPacketTaskOffload "%1!s!" |
3303 | -EncapsulatedPacketTaskOffload '%1!s!' | -EncapsulatedPacketTaskOffload '%1!s!' |
3304 | -NvreEncapsulatedPacketTaskOffload '%1!s!' | -NvreEncapsulatedPacketTaskOffload '%1!s!' |
3305 | -VxlanEncapsulatedPacketTaskOffload '%1!s!' | -VxlanEncapsulatedPacketTaskOffload '%1!s!' |
3306 | -VxlanUDPPortNumber '%1!d!' | -VxlanUDPPortNumber '%1!d!' |
3400 | Set-NetAdapterSriov '%1!s!' | Set-NetAdapterSriov '%1!s!' |
3401 | Enable-NetAdapterSriov '%1!s!' | Enable-NetAdapterSriov '%1!s!' |
3402 | Disable-NetAdapterSriov '%1!s!' | Disable-NetAdapterSriov '%1!s!' |
3403 | -NumVFs %1!d! | -NumVFs %1!d! |
3500 | Set-NetAdapterPacketDirect '%1!s!' | Set-NetAdapterPacketDirect '%1!s!' |
3501 | -DomainId %1!d! | -DomainId %1!d! |
3502 | Enable-NetAdapterPacketDirect '%1!s!' | Enable-NetAdapterPacketDirect '%1!s!' |
3503 | Disable-NetAdapterPacketDirect '%1!s!' | Disable-NetAdapterPacketDirect '%1!s!' |
12010 | Failed to restart network adapter '%1!s!' | Failed to restart network adapter '%1!s!' |
12011 | Failed to set '%1!s!' of '%2!s!' configuration of adapter '%3!s!' | Failed to set '%1!s!' of '%2!s!' configuration of adapter '%3!s!' |
12013 | Requested operation not supported on adapter '%1!s!' | Requested operation not supported on adapter '%1!s!' |
12014 | Cannot set property '%1!s!' on network adapter '%2!s!' because it is not supported | Cannot set property '%1!s!' on network adapter '%2!s!' because it is not supported |
12100 | The adapter name '%1!s!' is not valid | The adapter name '%1!s!' is not valid |
12101 | Cannot rename '%1!s!' to '%2!s!' because the new name is already in use | Cannot rename '%1!s!' to '%2!s!' because the new name is already in use |
12105 | The network address %1!s! is already used on a network adapter with the name '%2!s!' | The network address %1!s! is already used on a network adapter with the name '%2!s!' |
12200 | The operation cannot continue because another application is in the process of changing network configuration | The operation cannot continue because another application is in the process of changing network configuration |
File Description: | Network Adapter WMI Provider |
File Version: | 10.0.15063.0 (WinBuild.160101.0800) |
Company Name: | Microsoft Corporation |
Internal Name: | NetAdapter.dll |
Legal Copyright: | © Microsoft Corporation. All rights reserved. |
Original Filename: | NetAdapter.dll.mui |
Product Name: | Microsoft® Windows® Operating System |
Product Version: | 10.0.15063.0 |
Translation: | 0x809, 1200 |