Mini Kabibi Habibi

Current Path : C:/Windows/System32/wbem/en-US/

Current File : C:/Windows/System32/wbem/en-US/NetTCPIP.dll.mui

MZ����@��� �!�L�!This program cannot be run in DOS mode.

$5�<�q�R�q�R�q�R�e���p�R�e�P�p�R�Richq�R�PEL�!p

��@ dm8.rdata�@@.rsrcp n@@��$g
T88��$g$��8.rdata8x.rdata$zzzdbg �.rsrc$01�.�_.rsrc$02 �a�kJ2JyoLo1͸ʕ��󲜰ғ�$g��0�H�������H�����(�@�X�p��� ��
������
��0�H�`�x������������ �8�P�h������� ��!��"��#�$(�%@�&X�'p�(��)��*��+��,��-�.�/0�0H�1`�2x�3��4��5��6��7��8�9 �:8�;P�<h�=��>��?��@��A��B��C �D( �E@ �FX �Gp �H� �� �� � � � �

0
@
P
`
p
�
�
�
�
�
�
�
�
0 @ P ` p � � � � � � � � 0 @ P ` p � � � � � � � �

0
@
P
`
p
�
�
�
�
�
�
�
�
0 @ P ` p�.��@/�$�$T~��\��]~�,b���w�����+�\���X���L���<�l
��H��:�, J�x"���$*�((���*��`-�� /���1�!��S.��VV�@i��}����>�ܩ�����
�4����~���8���b�$��������*�������������L�B�������,����8�8�
�D��
�,�@ �� �����������t.� �D8l��>���E��0M��h���t��ăB�����P�P�&�x��!��x
���N
���� �T����;��R$��c���pt�w���w�Љ��MUI���Ւ2��l�&?�{�������+��!�r�M�Ǽ���MUIen-US)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:
<OrgID>:<LocalID>
Where <OrgID> and <LocalID> are separated by a colon (:), and where <OrgID> 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 <Schema Name>_<Class Name> structure of Schema class names.) In addition, to ensure uniqueness, <OrgID> must not contain a colon (:). When using this algorithm, the first colon to appear in InstanceID must appear between <OrgID> and <LocalID>.
<LocalID> 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 <OrgID> set to CIM.UThe Caption property is a short textual description (one- line string) of the object.FThe Description property provides a textual description of the object.)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.2.19.0�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.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:
<OrgID>:<LocalID>
Where <OrgID> and <LocalID> are separated by a colon \':\', and where <OrgID> MUST include a copyrighted, trademarked or otherwise unique name that is owned by the business entity creating/defining the InstanceID, or is a registered ID that is assigned to the business entity by a recognized global authority. (This is similar to the <Schema Name>_<Class Name> structure of Schema class names.) In addition, to ensure uniqueness <OrgID> MUST NOT contain a colon (\':\'). When using this algorithm, the first colon to appear in InstanceID MUST appear between <OrgID> and <LocalID>.
<LocalID> 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 resultant InstanceID is not re-used across any InstanceIDs produced by this or other providers for this instance\'s NameSpace.
For DMTF defined instances, the \'preferred\' algorithm MUST be used with the <OrgID> set to \'CIM\'.:The address which serves as the destination to be reached.�The specific administrative distance of this route, overriding any default distances specified by the system or routing service.�RouteMetric provides a numeric indication as to the preference of this route, compared to other routes that reach the same destination.\TRUE indicates that this is a static route, and FALSE indicates a dynamically-learned route.�An enumerated integer indicating whether the route is administrator-defined (value=2), computed (via a routing protocol/algorithm, value=3) or the actual route implemented in the network (value=4). The default is a computed route.Administrator Defined RouteComputed RouteActual RouteXNextHopRoute represents one of a series of \'hops\' to reach a network destination. A route is administratively defined, or calculated/learned by a particular routing process. A ConcreteDependency associaton may be instantiated between a route and its routing service to indicate this. (In this scenario, the route is dependent on the service.)The destination prefix."The user-friendly interface index.!The user-friendly interface name.(The next hop address or gateway address.�One of the following values: No: Not advertised in Route Advertisements. This is the default. Age: Advertised in Route Advertisements with a finite lifetime. Yes: Advertised in Route Advertisements with an infinite lifetime.NoAgeYesFLifetime over which the route is valid. The default value is infinite.JLifetime over which the route is preferred. The default value is infinite.�One of the following values: Active: Change only lasts until next boot. Persistent: Change is persistent. This is the default.
PersistentActiveBTo indicate whether the address family for this route is v4 or v6.IPv4PAIPv67The routing mechanism via which this route was learned.OtherLocalNetMgmtIcmpEgpGgpHelloRipIsIsEsIsIgrpBbnOspfBgpIdprEigrpDvmrpRplDhcp.The compartment in which route(s) are located.State of the route.AliveDeadProbe$The metric of the route's interface.Create the Route.UFinds the best local IP address and best route to reach the specified remote address.3Represents the Route class in TCPIP WMIv2 provider.�A datetime value that indicates when the object was installed. Lack of a value does not indicate that the object is not installed.�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.PA>
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.UnknownOKDegradedStressedPredictive FailureErrorNon-Recoverable ErrorStartingStoppingStopped
In Service
No ContactLost CommunicationAbortedDormantSupporting Entity in Error Completed
Power Mode
DMTF ReservedVendor ReservedAStrings 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.�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.QIndicates 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.Degraded/Warning
Minor failure
Major failureCritical failureNon-recoverable error�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.
Not AvailableCommunication OKPA�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.No Additional Informationm
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. Servicing Migrating
EmigratingImmigratingSnapshotting
Shutting DownIn Test
Transitioning�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.�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.2.22.0�CIM_LogicalElement is a base class for all the components of a System that represent abstract system components, such as Files, Processes, or LogicalDevices.2.6.0PA�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.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 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 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.VThe 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 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.eThe month during which the Job should be processed. Specify 0 for January, 1 for February, and so on.JanuaryFebruaryMarchAprilMayJuneJulyAugust SeptemberOctoberNovemberDecember#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.�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. -Saturday-Friday -Thursday
-Wednesday-Tuesday-Monday-SundayExactDayOfMonthSundayMondayTuesdayPA WednesdayThursdayFridaySaturday�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.�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".
Local TimeUTC TimeThe 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.BThe User who is to be notified upon the Job completion or failure.aThe User that submitted the Job, or the Service or method name that caused the job to be created.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.�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.Percent�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.QA 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.PA0A 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.�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.Do Not ContinueContinue With Next Job
Re-run JobRun Recovery JobhA string describing the recovery action when the RecoveryAction property of the instance is 1 ("Other").EKillJob 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.Success
Not SupportedTimeoutFailed
Access Denied Not FoundVendor Specific�Indicates whether or not the Job should be automatically deleted upon termination. This parameter takes precedence over the property, DeleteOnCompletion.�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.2.10.0Primary 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.Communications ErrorQuality of Service ErrorSoftware ErrorHardware ErrorEnvironmental ErrorSecurity ErrorOversubscription ErrorUnavailable Resource ErrorUnsupported Operation Error[A free-form string describing the ErrorType when 1, "Other", is specified as the ErrorType.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.kAn opaque string that uniquely identifies, within the scope of the OwningEntity, the format of the Message.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.7An array containing the dynamic content of the message.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.InformationMinorMajorCriticalFatal/NonRecoverableCAn enumerated value that describes the probable cause of the error.Adapter/Card ErrorApplication Subsystem FailureBandwidth ReducedConnection Establishment ErrorCommunications Protocol Error Communications Subsystem Failure!Configuration/Customization Error
CongestionPACorrupt DataCPU Cycles Limit ExceededDataset/Modem ErrorDegraded SignalDTE-DCE Interface ErrorEnclosure Door OpenEquipment MalfunctionExcessive VibrationFile Format Error
Fire DetectedFlood Detected
Framing ErrorHVAC ProblemHumidity UnacceptableI/O Device ErrorInput Device ErrorPA LAN ErrorNon-Toxic Leak DetectedLocal Node Transmission Error
Loss of FrameLoss of SignalMaterial Supply ExhaustedMultiplexer Problem
Out of MemoryOutput Device ErrorPerformance Degraded
Power ProblemPressure Unacceptable*Processor Problem (Internal Machine Error)Pump FailureQueue Size ExceededReceive FailureReceiver FailureRemote Node Transmission ErrorResource at or Nearing CapacityResponse Time ExcessiveRetransmission Rate Excessive&Software Program Abnormally Terminated*Software Program Error (Incorrect Results)Storage Capacity ProblemTemperature UnacceptableThreshold CrossedTiming ProblemToxic Leak DetectedTransmit FailureTransmitter FailureUnderlying Resource UnavailableVersion MismatchPAPrevious Alert ClearedLogin Attempts FailedSoftware Virus DetectedHardware Security BreachedDenial of Service DetectedSecurity Credential MismatchUnauthorized AccessAlarm ReceivedLoss of PointerPayload MismatchTransmission ErrorExcessive Error Rate
Trace ProblemElement UnavailableElement MissingLoss of Multi FrameBroadcast Channel FailureInvalid Message ReceivedRouting FailureBackplane FailureIdentifier DuplicationProtection Path FailureSync Loss or MismatchTerminal ProblemReal Time Clock FailureAntenna FailureBattery Charging FailureDisk FailureFrequency Hopping FailureLoss of RedundancyPower Supply FailureSignal Quality ProblemBattery DischargingBattery FailureCommercial Power ProblemFan FailureEngine FailureSensor FailureFuse FailureGenerator FailureLow BatteryLow Fuel Low Water
Explosive Gas
High WindsIce BuildupSmokeMemory MismatchOut of CPU CyclesSoftware Environment ProblemSoftware Download FailureElement ReinitializedLogging Problems
Leak DetectedProtection Mechanism FailureProtecting Resource FailureDatabase InconsistencyAuthentication FailureBreach of ConfidentialityCable TamperDelayed InformationDuplicate InformationInformation MissingInformation ModificationPAInformation Out of SequenceKey ExpiredNon-Repudiation FailureOut of Hours ActivityOut of ServiceProcedural ErrorUnexpected Information>A free-form string describing the probable cause of the error.OA free-form string describing recommended actions to take to resolve the error.�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 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.
CIMObjectPath�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.XThe 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.CIM_ERR_FAILEDCIM_ERR_ACCESS_DENIEDCIM_ERR_INVALID_NAMESPACECIM_ERR_INVALID_PARAMETERCIM_ERR_INVALID_CLASSCIM_ERR_NOT_FOUNDCIM_ERR_NOT_SUPPORTEDCIM_ERR_CLASS_HAS_CHILDRENCIM_ERR_CLASS_HAS_INSTANCESCIM_ERR_INVALID_SUPERCLASSCIM_ERR_ALREADY_EXISTSCIM_ERR_NO_SUCH_PROPERTYCIM_ERR_TYPE_MISMATCH$CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTEDCIM_ERR_INVALID_QUERYCIM_ERR_METHOD_NOT_AVAILABLECIM_ERR_METHOD_NOT_FOUNDCIM_ERR_UNEXPECTED_RESPONSEPA$CIM_ERR_INVALID_RESPONSE_DESTINATIONCIM_ERR_NAMESPACE_NOT_EMPTY#CIM_ERR_INVALID_ENUMERATION_CONTEXT!CIM_ERR_INVALID_OPERATION_TIMEOUTCIM_ERR_PULL_HAS_BEEN_ABANDONED CIM_ERR_PULL_CANNOT_BE_ABANDONED*CIM_ERR_FILTERED_ENUMERATION_NOT_SUPPORTED+CIM_ERR_CONTINUATION_ON_ERROR_NOT_SUPPORTEDCIM_ERR_SERVER_LIMITS_EXCEEDEDCIM_ERR_SERVER_IS_SHUTTING_DOWN#CIM_ERR_QUERY_FEATURE_NOT_SUPPORTED�A free-form string containing a human-readable description of CIMStatusCode. This description MAY extend, but MUST be consistent with, the definition of CIMStatusCode.2.22.1�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.>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:
<OrgID>:<LocalID>
Where <OrgID> and <LocalID> are separated by a colon \':\', and where <OrgID> 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 <Schema Name>_<Class Name> structure of Schema class names.) In addition, to ensure uniqueness <OrgID> must not contain a colon (\':\'). When using this algorithm, the first colon to appear in InstanceID must appear between <OrgID> and <LocalID>.
<LocalID> 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 <OrgID> set to \'CIM\'.�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.)PA�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 queryNewRunning Suspended
TerminatedKilled ExceptionService
Query PendingThe 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 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.DRequests 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.Completed with No ErrorUnknown/Unspecified Error&Can NOT complete within Timeout PeriodInvalid ParameterIn Use.Method Parameters Checked - Transition StartedInvalid State Transition&Use of Timeout Parameter Not SupportedBusyMethod Reserved�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.StartSuspend TerminateKill�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.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.Unspecified Error�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.yA concrete version of Job. This class represents a generic and instantiable unit of work, such as a batch or a print job.PA�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.EnabledDisabledNot ApplicableEnabled but OfflineDeferredQuiesce�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.`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". Shut Down No ChangeOfflineTestRebootReset�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).PA
No Default 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.�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.Defer�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.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.Unknown or Unspecified Error%Cannot complete within Timeout Period'Method Parameters Checked - Job StartedxThe 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.tMay contain a reference to the ConcreteJob created to track the state transition initiated by the method invocation.�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.�This class extends LogicalElement to abstract the concept of an element that is enabled and disabled, such as a LogicalDevice or a ServiceAccessPoint.�The Name property uniquely identifies the ServiceAccessPoint and provides an indication of the functionality that is managed. This functionality is described in more detail in the Description property of the object.,The CreationClassName of the scoping System.The Name of the scoping System.�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.�CIM_ServiceAccessPoint represents the ability to utilize or invoke a Service. Access points represent that a Service is made available for other entities to use.4A string that identifies this ProtocolEndpoint with either a port or an interface on a device. To ensure uniqueness, the Name property should be prepended or appended with information from the Type or OtherTypeDescription properties. The method selected is described in the NameFormat property of this class.NameFormat contains the naming heuristic that is selected to ensure that the value of the Name property is unique. For example, you might choose to prepend the name of the port or interface with the Type of ProtocolEndpoint (for example, IPv4) of this instance followed by an underscore.�Note: This property is deprecated in lieu of the ProtocolIFType enumeration. This deprecation was done to have better alignment between the IF-MIB of the IETF and this CIM class.
Deprecated description: ProtocolType is an enumeration that provides information to categorize and classify different instances of this class. For most instances, information in this enumeration and the definition of the subclass overlap. However, there are several cases where a specific subclass of ProtocolEndpoint is not required (for example, there is no Fibre Channel subclass of ProtocolEndpoint). Therefore, this property is needed to define the type of Endpoint.IPX AppleTalkDECnetSNACONPCLNPVINESXNSATMFrame RelayEthernet TokenRingFDDI
Infiniband
Fibre ChannelISDN BRI EndpointISDN B Channel EndpointISDN D Channel EndpointIPv4/v6BGPOSPFMPLSUDPTCP�ProtocolIFType is an enumeration that is synchronized with the IANA ifType MIB. The ifType MIB is maintained at the URL, http://www.iana.org/assignments/ianaiftype-mib. Also, additional values defined by the DMTF are included. The property is used to categorize and classify instances of the ProtocolEndpoint class. Note that if the ProtocolIFType is set to 1 (Other), then the type information should be provided in the OtherTypeDescription string property.Regular 1822HDH 1822PADDN X.25RFC877 X.25Ethernet CSMA/CDISO 802.3 CSMA/CDISO 802.4 Token BusISO 802.5 Token Ring
ISO 802.6 MANStarLANProteon 10MbitProteon 80MbitHyperChannelLAP-BSDLCDS1E1
Basic ISDNPAPrimary ISDN!Proprietary Point-to-Point SerialPPPSoftware LoopbackEONEthernet 3MbitNSIPSLIPUltraDS3SIPRS-232ParallelARCNetARCNet PlusMIO X.25SONETX.25 PLEISO 802.211c LocalTalkSMDS DXIFrame Relay ServiceV.35HSSIHIPPIModemAAL5
SONET PathSONET VT SMDS ICIPProprietary Virtual/InternalProprietary MultiplexorPAIEEE 802.12HIPPI InterfaceFrame Relay InterconnectATM Emulated LAN for 802.3ATM Emulated LAN for 802.5ATM Emulated CircuitFast Ethernet (100BaseT)ISDNV.11V.36G703 at 64KG703 at 2MbQLLCFast Ethernet 100BaseFXChannelIEEE 802.11PAIBM 260/370 OEMI ChannelESCONData Link SwitchingISDN S/T InterfaceISDN U InterfaceLAP-D IP SwitchRemote Source Route BridgingATM LogicalDS0
DS0 BundleBSCAsyncCombat Net RadioISO 802.5r DTRExt Pos Loc Report SystemPA AppleTalk Remote Access ProtocolProprietary ConnectionlessITU X.29 Host PADITU X.3 Terminal PADFrame Relay MPI ITU X.213ADSLRADSLSDSLVDSLISO 802.5 CRFPMyrinetVoice Receive and TransmitVoice Foreign Exchange OfficeVoice Foreign Exchange ServiceVoice EncapsulationPA
Voice over IPATM DXIATM FUNIATM IMAPPP Multilink BundleIP over CDLCIP over CLAWStack to StackVirtual IP AddressMPCIP over ATMISO 802.5j Fibre Token RingTDLCGigabit EthernetHDLCLAP-FPAV.37X.25 MLPX.25 Hunt GroupTransp HDLCInterleave ChannelFAST Channel IP (for APPN HPR in IP Networks)CATV MAC LayerCATV Downstream
CATV UpstreamAvalon 12MPP SwitchTunnelCoffeeCircuit Emulation ServiceATM SubInterfaceLayer 2 VLAN using 802.1QPALayer 3 VLAN using IPLayer 3 VLAN using IPXDigital Power LineMultimedia Mail over IPDTMDCN
IP ForwardingMSDSL IEEE 1394IF-GSN/HIPPI-6400DVB-RCC MAC LayerDVB-RCC DownstreamDVB-RCC UpstreamATM VirtualMPLS TunnelSRPVoice over ATMVoice over Frame RelayISDLComposite LinkSS7 Signaling LinkProprietary P2P Wireless
Frame ForwardRFC1483 Multiprotocol over ATMUSBIEEE 802.3ad Link AggregateBGP Policy AccountingFRF .16 Multilink FRH.323 GatekeeperH.323 ProxyMulti-Frequency Signaling LinkHDSL-2PAS-HDSLDS1 Facility Data LinkPacket over SONET/SDH
DVB-ASI InputDVB-ASI Output
Power Line!Non Facility Associated SignalingTR008 GR303 RDT GR303 IDTISUPProprietary Wireless MAC LayerProprietary Wireless DownstreamProprietary Wireless UpstreamHIPERLAN Type 28Proprietary Broadband Wireless Access Point to MulipointPASONET Overhead Channel Digital Wrapper Overhead ChannelATM Adaptation Layer 2 Radio MAC ATM RadioInter Machine TrunkMVL DSL
Long Read DSLFrame Relay DLCI EndpointATM VCI EndpointOptical ChannelOptical TransportProprietary ATMVoice over CableTE LinkQ.2931Virtual Trunk GroupSIP Trunk Group
SIP SignalingCATV Upstream ChannelEconetFSAN 155Mb PONFSAN 622Mb PONTransparent Bridge
Line GroupVoice E&M Feature GroupVoice FGD EANA Voice DIDMPEG Transport6To4GTPParadyne EtherLoop 1PAParadyne EtherLoop 2Optical Channel GroupHomePNAGFPciscoISLvlanactelisMetaLOOPFcip
IANA Reserved802.11a802.11b802.11g802.11hNFSCIFSDAFSWebDAVHTTPFTPNDMPTelnetSSHSM CLPSMTPLDAPRDPHTTPS�A string that describes the type of ProtocolEndpoint when the Type property of this class (or any of its subclasses) is set to 1 (Other). This property should be set to null when the Type property is any value other than 1.�A communication point from which data can be sent or received. ProtocolEndpoints link system or computer interfaces to LogicalNetworks.2.15.0qProtocolIFType\'s enumeration is limited to IP-related and reserved values for this subclass of ProtocolEndpoint.7The IPv4 address that this ProtocolEndpoint represents.7The IPv6 address that this ProtocolEndpoint represents.PAThe IP address that this ProtocolEndpoint represents, formatted according to the appropriate convention as defined in the AddressType property of this class (e.g., 171.79.6.40). This single property is deprecated to replace it by specific IPv4 and v6 addresses.JThe mask for the IPv4 address of this ProtocolEndpoint, if one is defined.TThe prefix length for the IPv6 address of this Protocol Endpoint, if one is defined.�An enumeration that describes the format of the Address property. It is deprecated since it is not needed, as the class contains both IPv4 and v6 addresses).This property explicitly defines support for different versions of the IP protocol, for this Endpoint. It is deprecated since the ProtocolIFType also provides this functionality by describing an endpoint as IPv4 only (value=4096), IPv6 only (value=4097), or IPv4/v6 (value=4098). IPv4 Only IPv6 OnlyBoth IPv4 and IPv6AddressOrigin identifies the method by which the IP Address, Subnet Mask, and Gateway were assigned to the IPProtocolEndpoint.A value of 3 "Static" shall indicate the values were assigned manually. A value of 4 "DHCP" shall indicate the values were assigned utilizing the Dynamic Host Configuration Protocol. See RFC 2131 and related.
A value of 5 "BOOTP" shall indicate the values were assigned utilizing BOOTP. See RFC 951 and related.
A value of 6 "IPv4 Link Local" shall indicate the values were assigned using the IPv4 Link Local protocol. See RFC 3927.
A value of 7 "DHCPv6" shall indicate the values were assigned using DHCPv6. See RFC 3315.
A value of 8 "IPv6 AutoConfig" shall indicate the values were assinged using the IPv6 AutoConfig Protocol. See RFC 4862.StaticDHCPBOOTPIPv4 Link LocalDHCPv6IPv6AutoConfig3A ProtocolEndpoint that is dedicated to running IP.2.19.1The IP address.GTo indicate whether the address family for this IP address is v4 or v6.�One of the following values: Unicast: Marks the address as a unicast address. This is the default. Anycast: Marks the address as an anycast address.UnicastAnycastqOne of the following values: Active: Set only lasts until next boot. Persistent: Set is persistent (default).Prefix origin of this address.Manual WellKnownRouterAdvertisementSuffix origin of this address.LinkRandomAddress lifetime state.InvalidPA Tentative Duplicate
Deprecated PreferredHLifetime over which the address is valid. The default value is infinite.LLifetime over which the address is preferred. The default value is infinite.[Do not use the address as source address for any outgoing packet unless explictly asked to.Create the IPAddress.4The representation of IPv4 address and IPv6 address.�Access or addressing information or a combination of this information for a remote connection. This information can be a host name, network address, or similar information.An enumerated integer that describes the format and interpretation of the AccessInfo property.
206\'Parameterized URL\'- a URL containing ${parameterName} strings. Those strings are intended to be replaced in their entirety by the value of the named parameter. The interpretation of such parameters is not defined by this subclass.
As an example use: If a parameter named \'CompanyURL\' has a value of \'www.DMTF.org\' and the value of AccessInfo was \'http:\${CompanyURL}\', then the resultant URL is intended to be \'http:\www.dmtf.org\'. Host NameIPv4 AddressIPv6 AddressIPX AddressDECnet AddressSNA AddressAutonomous System Number
MPLS LabelIPv4 Subnet AddressIPv6 Subnet AddressIPv4 Address RangeIPv6 Address RangeDial StringEthernet AddressToken Ring AddressATM AddressFrame Relay AddressURLFQDN User FQDNDER ASN1 DNPADER ASN1 GNKey IDParameterized URLFDescribes the format when the property InfoFormat is set to 1 (Other).nThe AccessContext property identifies the role this RemoteServiceAccessPoint is playing in the hosting system.Default Gateway
DNS ServerSNMP Trap DestinationMPLS Tunnel DestinationDHCP ServerSMTP ServerLDAP Server"Network Time Protocol (NTP) ServerManagement Service�When the AccessContext property contains a value of 1, "Other" then this is a free form string providing more information about the role of RemoteServiceAccessPoint in the hosting system.�RemoteServiceAccessPoint describes access or addressing information or a combination of this information for a remote connection that is known to a local network element. This information is scoped or contained by the local network element, because this is the context in which the connection is remote.
The relevance of the remote access point and information on its use are described by subclassing RemoteServiceAccessPoint or by associating to it.2.21.0Network address of neighbor.User-friendly interface index.User-friendly interface name.Link layer address of neighbor.�One of the following values: - active: Address will disappear on next boot. - persistent: Address will be persistent. This is the default.Neighbor Discovery State.Unreachable
IncompleteDelayStale Reachable PermanentETo indicate whether the address family for this neighbor is v4 or v6.Create the Neighbor.&Represents the Neighbor in TCPIP WMIv2PA�A label or identifier for the LAN Segment to which the Endpoint is connected. If the Endpoint is not currently active/connected or this information is not known, then LANID is NULL.�An indication of the kind of technology used on the LAN. This property is deprecated in lieu of ProtocolType, which is an enumeration inherited from ProtocolEndpoint and which includes the Values specified here.A free-form string that describes the type of technology used on the LAN when the value of the LANType property is equal to 1 (i.e., "Other"). This property is deprecated since its purpose overlaps with OtherTypeDescription, which which is inherited from ProtocolEndpoint.The principal unicast address used in communication with the LANEndpoint. The MAC address is formatted as twelve hexadecimal digits (e.g., "010203040506"), with each pair representing one of the six octets of the MAC address in "canonical" bit order according to RFC 2469.MOther unicast addresses that may be used to communicate with the LANEndpoint.5Multicast addresses to which the LANEndpoint listens.NThe largest information field that may be sent or received by the LANEndpoint.Bits�A communication endpoint which, when its associated interface device is connected to a LAN, may send and receive data frames. LANEndpoints include Ethernet, Token Ring and FDDI interfaces.2.7.0FTo indicate whether the address family for this interface is v4 or v6.ZWhether forwarding is enabled for incoming packets on this interface. Default is Disabled.fWhether MSS clamping is enabled for outgoing forwarded packets on this interface. Default is Disabled.TWhether router advertisments are to be sent on this interface. Default is Disabled.UThe Network Layer MTU of this interface. The default is the natural MTU of the link.aInterface metric, added to route metrics for all routes over the interface. Default is automatic.PA[Whether neighbor unreachability detection is enabled. Default depends on type of interface.Base reachable time (in ms).Retransmit time (in ms).0Number of duplicate address detection transmits.0Can be enabled, disabled, or controlled by DHCP.ControlledByDHCP Unchanged�Whether to use a stateful protocol (i.e., DHCP) to obtain an address. Setting this parameter will have no effect on an interface that has router discovery enabled & advertising disabled. In that case the parameter is controlled by router discovery.Whether to use a stateful protocol (i.e., DHCP) to obtain configuration information other than addresses. Setting this parameter will have no effect on an interface that has router discovery enabled & advertising disabled. In that case the parameter is controlled by router discovery.$Whether weak host sends are enabled.'Whether weak host receives are enabled.;Ignores default routes on the interface. Default: Disabled.)Router lifetime. Default is 1800 seconds.�Whether the interface should advertise itself as a default router regardless of whether the node has a default route itself. Valid only for advertising interfaces.Hop limit in outbound traffic.J- active: Set only lasts until next boot. - persistent: Set is persistent.PASTo indicate that ARP, Neighbor Discovery, Wake-On-LAN patterns should be turned on.ETo indicate that direct MAC Wake-On-LAN patterns should be turned on.pTo control ECN codepoints for outgoing packets. Four possible values: - Disabled - UseEct1 - UseEct0 - AppDecideUseEct1UseEct0 AppDecideaTo control whether DHCP is enabled on this IPInterface. Two possible values: - Disabled - EnabledReachable time (in ms).UTo control whether to use automatic metric. Two possible values: - Disabled - EnabledSTo show whether to neighbor discovery is supported. Two possible values: - No - YesbTo show whether the interface is connected or not. Two possible values: - Connected - DisconnectedDisconnected Connected4Duplicate address detection retransmit time (in ms).Routing compartment identifier.Network isolation identifier.?Locally unique identifier of the lowest interface in the stack.ARepresents the Interface class of Microsoft TCPIP WMIv2 provider.!Default HopLimit of packets sent.)Maximum number of neighbor cache entries.&Maximum number of route cache entries.+Maximum size of reassembly buffer in bytes.GWhether the path cache is updated in response to ICMP redirect packets.�Determines the behavior for source routed packets. Per RFC 5095 support for forwarding of source routed IPv6 packets has been removed, and the setting forward now has the same effect as dontforward.ForwardDontForwardDrop&Whether media sense is enabled or not..Whether media sense logging is enabled or not.�Level of multicast support. - None: Multicast packets can neither be sent nor received - SendOnly: Multicast packets can be sent but not received - All: Multicast packets can be sent as well as receivedNoneSendOnlyPAAll/Maximum IGMP/MLD version supported by the host.Version1Version2Version3+Whether multicast packets can be forwarded.IWhether fragments should be collected into groups before being forwarded.-Whether interface identifiers are randomized.>Whether the computer will respond to ICMP Address mask packets>Whether dead gateway detection is enabled. Default is enabled.LThe base class of IPv4 and IPv6 protocol for Microsoft TCPIP WMIv2 provider.]Minimum value of IPv4 MTU. The default value is 576. The value can range between 352 and 576.?Represents the IPv4 protocol of Microsoft TCPIP WMIv2 provider.Whether temporary addresses are enabled. It takes one of the following values: - No: Don't use temporary addresses. - Yes: Use temporary addresses. - Always: Use temporary addresses and always generate a new temporary address each time a network is connected.Always]Maximum duplicate address detection attempts for temporary addresses. The default value is 3.PAVMaximum lifetime over which a temporary address is valid. The default value is 7 days.YMaximum lifetime over which a temporary address is preferred. The default value is 1 day.nTime prior to deprecating a temporary address when a new address is generated. The default value is 5 seconds.eMaximum time to desynchronize temporary address preferred lifetimes. The default value is 10 minutes.@Represents the IPv6 protocol for Microsoft TCPIP WMIv2 provider.Prefix of the policy.MPrecedence value in the policy table, used for sorting destination addresses.~Label value that allows for policies that prefer a particular source address prefix for use with a destination address prefix.kOne of the following values: Active: Change only lasts until next boot. Persistent: Change is persistent.Create the PrefixPolicy.@Represents the prefix policy for Microsoft TCPIP WMIv2 provider.3A user-friendly name of this policy-related object.�An array of keywords for characterizing / categorizing policy objects. Keywords are of one of two types:
- Keywords defined in this and other MOFs, or in DMTF white papers. These keywords provide a vendor- independent, installation-independent way of characterizing policy objects.
- Installation-dependent keywords for characterizing policy objects. Examples include \'Engineering\', \'Billing\', and \'Review in December 2000\'.
This MOF defines the following keywords: \'UNKNOWN\', \'CONFIGURATION\', \'USAGE\', \'SECURITY\', \'SERVICE\', \'MOTIVATIONAL\', \'INSTALLATION\', and \'EVENT\'. These concepts are self-explanatory and are further discussed in the SLA/Policy White Paper. One additional keyword is defined: \'POLICY\'. The role of this keyword is to identify policy-related instances that may not be otherwise identifiable, in some implementations. The keyword \'POLICY\' is NOT mutually exclusive of the other keywords specified above.
An abstract class defining the common properties of the policy managed elements derived from CIM_Policy. The subclasses are used to create rules and groups of rules that work together to form a coherent set of policies within an administrative domain or set of domains.iThe name of the class or the subclass used in the creation of the System object in whose scope this PolicyAction is defined.

This property helps to identify the System object in whose scope this instance of PolicyAction exists. For a rule-specific PolicyAction, this is the System in whose context the PolicyRule is defined. For a reusable PolicyAction, this is the instance of PolicyRepository (which is a subclass of System) that holds the Action.

Note that this property, and the analogous property SystemName, do not represent propagated keys from an instance of the class System. Instead, they are properties defined in the context of this class, which repeat the values from the instance of System to which this PolicyAction is related, either directly via the PolicyActionInPolicyRepository association or indirectly via the PolicyActionInPolicyRule aggregation.�The name of the System object in whose scope this PolicyAction is defined.

This property completes the identification of the System object in whose scope this instance of PolicyAction exists. For a rule-specific PolicyAction, this is the System in whose context the PolicyRule is defined. For a reusable PolicyAction, this is the instance of PolicyRepository (which is a subclass of System) that holds the Action.For a rule-specific PolicyAction, the CreationClassName of the PolicyRule object with which this Action is associated. For a reusable PolicyAction, a special value, \'NO RULE\', should be used to indicate that this Action is reusable and not associated with a single PolicyRule. For a rule-specific PolicyAction, the name of the PolicyRule object with which this Action is associated. For a reusable PolicyAction, a special value, \'NO RULE\', should be used to indicate that this Action is reusable and not associated with a single PolicyRule.*A user-friendly name of this PolicyAction.RDoActionLogging causes a log message to be generated when the action is performed.�A class representing a rule-specific or reusable policy action to be performed if the PolicyConditions for a Policy Rule evaluate to TRUE. Since all operational details of a PolicyAction are provided in subclasses of this object, this class is abstract.2.8.0jOne of the following values: - DatacenterCustom, InternetCustom, Datacenter, Compat, Internet, Automatic.nControls TCP retransmission timeout in milliseconds. Value can range from 20 milliseconds to 300 milliseconds.^Controls initial congestion window in Maximum Segment Size. Values can range from 2 to 64 MSS.0Controls whether congestion window is restarted.�One of the following values: - Disabled: Disable memory pressure protection. - Enabled : Enable memory pressure protection. - Default : Restore memory pressure protection state to the system default.DefaulttControls the congestion provider. One of the following values: - Default - NewReno - CTCP - DCTCP - LEDBAT - CUBICNewRenoCTCPDCTCPLEDBATCUBIC�One of the following values: - Disabled: Fix the receive window at its default value. - HighlyRestricted: Allow the receive window to grow beyond its default value, but do so very conservatively. - Restricted: Allow the receive window to grow beyond its default value, but limit such growth in some scenarios. - Normal: Allow the receive window to grow to accommodate almost all scenarios. - Experimental: Allow the receive window to grow to accomodate extreme scenarios.HighlyRestricted
RestrictedNormalExperimental�Controls the TCP ECN Capability. Disabled by default in client, enabled by default in server. The value can be one of the following values: - Disabled: Disable ECN Capability. - Enabled : Enable ECN Capability.nOne of the following values: - Disabled: Disable RFC 1323 timestamps. - Enabled: Enable RFC 1323 timestamps.BConnect (SYN) retransmit timeout (in milliseconds). default: 3000.yOne of the following values: - Disabled: Disable window scaling heuristics. - Enabled : Enable window scaling heuristics.)Starting port number between 1 and 65535.SNumber of ports starting from the DynamicPortRangeStartPort for dynamic port range.�One of the following values: - Disabled: Set the receive window at its default value. - HighlyRestricted: Allow the receive window to grow beyond its default value, but do so very conservatively. - Restricted: Allow the receive window to grow beyond its default value, but limit such growth in some scenarios. - Normal: Allow the receive window to grow to accomodate almost all scenarios. - Experimental: Allow the receive window to grow to accomodate extreme scenarios.�The effective setting of auto-tuning level. This can be one of the following value: - Local: the effective auto-tuning level is from the local setting - GroupPolicy: the effective auto-tuning level is from the group policy settingGroupPolicyPAlControls TCP delayed ACK time-out in milliseconds. Value can range from 10 milliseconds to 600 milliseconds.}Specifies the number of ACKs that will be outstanding before the delayed ACK timer is ignored. Value can range from 1 to 255.�Controls whether Automatic template chooses between custom templates. - Disabled: Automatic chooses between Datacenter and Internet. - Enabled: Automatic chooses between DatacenterCustom and InternetCustom.�One of the following values: - Disabled: Disable rtt resiliency for non sack clients. - Enabled : Enable rtt resiliency for non sack clients.�One of the following values: - Disabled: Disable force window scaling on retransmit. - Enabled : Enable force window scaling on retransmit.^Specifies the number of connect retry attempts using SYN packets. Value can range from 2 to 8.<Starting automatic reuse port number between 1025 and 65535.]Number of ports starting from the AutoReusePortRangeStartPort for automatic reuse port range.HRepresents the TCP parameter setting for Microsoft TCPIP WMIv2 provider.HRepresents the UDP parameter setting for Microsoft TCPIP WMIv2 provider._The Name property defines the label by which the Filter Entry is known and uniquely identified.0The scoping ComputerSystem\'s CreationClassName.#The scoping ComputerSystem\'s Name.�Boolean indicating that the match condition described in the properties of the FilterEntryBase subclass should be negated. This property is defined for ease of use when filtering on simple negations - for example, to select all source ports except 162. It is not recommended that this Boolean be set to True when filtering on multiple criteria, such as defining an IPHeadersFilter based on source/destination addresses, ports, and DiffServ Code Points.A FilterList aggregates instances of (subclasses of) FilterEntryBase via the aggregation EntriesInFilterList. The filter entries are always ANDed together when grouped by the FilterList. Note that it is possible to aggregate different types of filters into a single FilterList - for example, packet header filters (represented by the IpHeadersFilter class) and IPsec security filters.

A FilterList is weak to the network device (e.g., the ComputerSystem) that contains it. Hence, the ComputerSystem keys are propagated to this class..One of the following protocols: - TCP - UDPPA#The start of the local port number.!The end of the local port number.$The start of the remote port number."The end of the remote port number.&The destination prefix to be filtered.(The associated TCPSetting's SettingName.cRepresents the filter for transport protocol parameter setting for Microsoft TCPIP WMI v2 provider.�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:
<OrgID>:<LocalID>
Where <OrgID> and <LocalID> are separated by a colon \':\', and where <OrgID> MUST include a copyrighted, trademarked or otherwise unique name that is owned by the business entity creating/defining the InstanceID, or is a registered ID that is assigned to the business entity by a recognized global authority. (This is similar to the <Schema Name>_<Class Name> structure of Schema class names.) In addition, to ensure uniqueness <OrgID> MUST NOT contain a colon (\':\'). When using this algorithm, the first colon to appear in InstanceID MUST appear between <OrgID> and <LocalID>. (For DMTF defined instances, the \'preferred\' algorithm MUST be used with the <OrgID> set to \'CIM\'.)
<LocalID> MUST include either a vendor specified unique identifier, or if mapping from an ITU M.3100 environment, the trailID, connectionID or subNetworkConnectionID of the instances of PipeR2.Indicates whether the pipe is bi-directional (value = 2), unidirectional (value = 3), or this information is not known (value = 0). For unidirectional pipes, the source and sink are indicated by a property (SourceOrSink) of the association, EndpointOfNetworkPipe.Bi-DirectionalUnidirectionalIndicates whether the pipe is composed of lower-level pipes, and if so, how these lower-level pipes are aggregated (in parallel or in sequence). The specific instances of NetworkPipe that are combined are described using the NetworkPipeComposition association.

In the context of M.3100, the ability to be composed of lower-level pipes is modeled as a Trail. A Trail is made up of one or more Connections. (Note that both Trails and Connections are subclasses of Pipe). Because of the flexibility of the NetworkPipeComposition association, there is no need to subclass NetworkPipe, as was done in M.3100, but merely to instantiate the NetworkPipeComposition association to describe the bundling of the lower-level pipes (i.e., the connections), or the sequencing of them.No Lower-Level CompositionCombined In ParallelCombined In Sequence=NetworkPipe is a subclass of EnabledLogicalElement, representing the state and management of a connection or trail between endpoints. This object is different than the association between the endpoints (CIM_ActiveConnection) since the emphasis is NOT on the endpoints but on the management of the pipe itself - its state, configuration, etc. NetworkPipes are defined in the context of a CIM_Network and represent the \'transfer of information . . . between . . . endpoints\'. These concepts are aligned with the definition of the Pipe object in ITU\'s M.3100 specification.PA$The local address of the connection.!The local port of the connection.The PID of the owning process.Creation time.NRepresents the transport connection class for Microsoft TCPIP WMIv2 provider.)The remote address of the TCP connection.&The remote port of the TCP connection.�The state of the TCP connection. The value can be: - Closed, - Listen, - SynSent, - SynReceived, - Established, - FinWait1, - FinWait2, - CloseWait, - Closing, - LastAck, - TimeWaitClosedListenSynSentSynReceivedEstablishedFinWait1FinWait2 CloseWaitClosingLastAckTimeWait DeleteTCB�The setting applied for this TCP connection. The value can be: - Internet, - Datacenter, - Compat, - InternetCustom, - DatacenterCustomInternet
DatacenterCompatDatacenterCustomInternetCustom7The TCP_CONNECTION_OFFLOAD_STATE of the TCP connection.InHost
Offloading Offloaded UploadingGRepresents the TCP connection class for Microsoft TCPIP WMIv2 provider.PAGRepresents the UDP connection class for Microsoft TCPIP WMIv2 provider.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:
<OrgID>:<LocalID>
Where <OrgID> and <LocalID> are separated by a colon (:), and where <OrgID> 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 <Schema Name>_<Class Name> structure of Schema class names.) In addition, to ensure uniqueness, <OrgID> must not contain a colon (:). When using this algorithm, the first colon to appear in InstanceID must appear between <OrgID> and <LocalID>.
<LocalID> 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 <OrgID> set to CIM.�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.)GCIM_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.%Superclass SettingData for networking\Whether to turn on receive side scaling. One of the following values: - Disabled - EnabledbWhether to turn on receive segment coalescing. One of the following values: - Disabled - EnableddWhether to turn on Chimney offload. One of the following values: - Disabled - Enabled - Automatic AutomaticTWhether to turn on task offload. One of the following values: - Disabled - EnabledUWhether to turn on NetworkDirect. One of the following values: - Disabled - EnabledaWhether to turn on packet coalescing filters. One of the following values: - Disabled - Enabled�Whether NetworkDirect connectivity outside of local IP subnet is allowed or not. One of the following values: - Blocked - AllowedBlockedAllowedORepresents the offload global setting class for Microsoft TCPIP WMIv2 provider.AAntecedent represents the independent object in this association.DDependent represents the object that is dependent on the Antecedent.kCIM_Dependency is a generic association used to establish dependency relationships between ManagedElements.4The endpoint used to reach the route\'s destination.The route using the endpoint.�RouteUsesEndpoint depicts the relationship between a next hop route and the local Endpoint that is used to transmit the traffic to the \'next hop\'.'The route associated with the interfaceJRepresents the IPInterfaceRoute association class in TCPIP WMIv2 provider. The required ServiceAccessPoint.>The ServiceAccessPoint that is dependent on an underlying SAP.kCIM_SAPSAPDependency is an association between one ServiceAccessPoint and another ServiceAccessPoint that indicates that the latter is required for the former to utilize or connect with its Service. For example, to print to a network printer, local Print Access Points must utilize underlying network-related SAPs, or ProtocolEndpoints, to send the print request.5The lower-level endpoint that is accessed by the SAP.RThe AccessPoint or ProtocolEndpoint that is dependent on the lower-level endpoint.�This association establishes a ServiceAccessPoint as a requestor of protocol services from a ProtocolEndpoint. Typically, this association runs between SAPs and endpoints on a single system. Because a ProtocolEndpoint is a kind of ServiceAccessPoint, this binding can be used to establish a layering of two protocols, with the upper layer represented by the Dependent and the lower layer represented by the Antecedent.3The underlying LANEndpoint, which is depended upon.AThe AccessPoint or ProtocolEndpoint dependent on the LANEndpoint.�This describes the framing method for the upper layer SAP or Endpoint that is bound to the LANEndpoint. Note: "Raw802.3" is only known to be used with the IPX protocol.802.2SNAPRaw802.3}This association makes explicit the dependency of a SAP or ProtocolEndpoint on an underlying LANEndpoint, on the same system.1The IPInterface associated with the IP addresses./The IP address associated with the IP interfaceNRepresents the IPInterfaceIPAddress association class in TCPIP WMIv2 provider.+The IPInterface used to reach the neighbor.-The neighbor associated with the IP interfaceMRepresents the IPInterfaceNeighbor association class in TCPIP WMIv2 provider.(The scoping System\'s CreationClassName.The scoping System\'s Name.OAn address or other identifying information to uniquely name the LogicalDevice.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.�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.PA(Power Saving Modes Entered AutomaticallyPower State SettablePower Cycling SupportedTimed Power On Supported�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.Running/Full PowerWarning Power OffOff LineOff Duty
Not Installed
Install ErrorPower Save - UnknownPower Save - Low Power ModePower Save - StandbyPower CyclePower Save - WarningPaused Not ReadyNot ConfiguredQuiesced&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.ILastErrorCode captures the last error code reported by the LogicalDevice.�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.fErrorCleared is a boolean property indicating that the error reported in LastErrorCode is now cleared.�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.^The number of consecutive hours that this Device has been powered, since its last power cycle.Hours<The total number of hours that this Device has been powered.�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._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").KThe 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.MilliSeconds�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.The power state to set.
Full PowerPower Save - Other�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.�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.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.7If TRUE enable the device, if FALSE disable the device.�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.CIf TRUE, take the device online, if FALSE, take the device OFFLINE.qThe 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.IIf set to TRUE then cleanly cease all activity, if FALSE resume activity.�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 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.`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.The LogicalDevice.;The ServiceAccessPoint implemented using the LogicalDevice.�An association between a ServiceAccessPoint (SAP) and how it is implemented. The cardinality of this association is many-to-many. A SAP can be provided by more than one LogicalDevice, operating in conjunction. And, any Device can provide more than one ServiceAccessPoint. When many LogicalDevices are associated with a single SAP, it is assumed that these elements operate in conjunction to provide the AccessPoint. If different implementations of a SAP exist, each of these implementations would result in individual instantiations of the ServiceAccessPoint object. These individual instantiations would then have associations to the unique implementations.-The bandwidth of the Port in Bits per Second.Bits per Second5The maximum bandwidth of the Port in Bits per Second.nThe requested bandwidth of the Port in Bits per Second. The actual bandwidth is reported in LogicalPort.Speed.fIn 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\'.Front-end only
Back-end onlyNot restricted�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.BDescribes the type of module, when PortType is set to 1 ("Other").�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.GThe LogicalPort that represents the Device behind the ProtocolEndpoint.<The ProtocolEndpoint that is implemented on the LogicalPort.PortImplementsEndpoint associates a LogicalPort with one or more ProtocolEndpoints that are implemented on it. This class specializes the DeviceSAPImplementation association. It indicates that the referenced Endpoint is dependent on the operations of the Port Device.�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.�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".)YNetworkPorts are often numbered relative to either a logical module or a network element.�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.IBFC
Token RingInfrared BlueToothWireless LANJA string value that describes LinkTechnology when it is set to 1, "Other".TPermanentAddress 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.FAn array of strings that indicates the network addresses for the port.FBoolean that indicates that the port is operating in full duplex mode.�A Boolean that indicates whether the NetworkPort is capable of automatically determining the speed or other communications characteristics of the attached network media.:The maximum transmission unit (MTU) that can be supported.BytesOThe active or negotiated maximum transmission unit (MTU) that can be supported.�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.0The IPInterface associated with the NetworkPort./The NetworkPort associated with the IPInterfaceLRepresents the IPInterfaceAdapter association class in TCPIP WMIv2 provider.+The filter associated with the TCP setting.*The TCP setting associated with the filterSRepresents the TransportFilterTCPSetting association class in TCPIP WMIv2 provider.Compartment identifier.'Compartment globally unique identifier.&User-friendly compartment description.Compartment type.UnspecifiedNative
RoutingDomain>Represents the Compartment for Microsoft TCPIP WMIv2 provider.PA%TCan not find the required property %1

�Not all required properties are specified: %1 and either one of %2 %3

�Not all required properties are specified: either one of %1 %2 and either one of %3 %4

�Not all required properties are specified: %1 %2 and either one of %3 %4

�Not all required properties are specified: %1 and either %2 %3 %4 %5 or %6 %7

�Only the custom templates InternetCustom and DatacenterCustom can be modified.

�%1 must be the same as %2, %3 must be the same as %4 or only one of the ranges must be wildcard (0, 65535)

�Properties that need modification should not include any of the following %1 %2 %3 %4 %5 %6

�Properties that need modification should not include any of the following %1 %2 %3 %4 %5 %6 %7 %8 %9 %10

�Properties that need modification should not include any of the following %1 %2 %3 %4 %5 %6 %7 %8 %9 %10 %11 %12

<Instance %1 %2 not found

@Instance %1 already exists

pInvalid parameter %1 %2, %3 should not be specified

�Invalid parameter %1 Days: %2!lu! Hours: %3!lu! Minutes: %4!lu! Seconds: %5!lu! Microseconds: %6!lu!

4Invalid parameter %1

8Invalid parameter %1 %2

DInvalid parameter %1 %2 %3 %4

@Invalid parameter %1 %2!lu!

XInconsistent parameters %1 %2 and %3 %4

�Value of property %1 should be at most the value of property %2

dValue of property %1 should be at most %2!lu!

<Property %1 is read-only

`This feature is available on servers only.

|Properties %1 and %2 should have values at the same time

�Properties %1 and %2 should not have values at the same time

tWhen property %1 is %2!lu!, %3 and %4 can not be set

�Properties %1 %2 %3 %4 and %5 %6 should not have values at the same time

�Can only modify/create/delete Neighbor object whose State is Permanent

`Default loopback address cannot be deleted

\Default loopback route cannot be deleted

HIPv4 protocol is not installed.

\This feature is not available on servers.

DefaultGateway %1 is not on the same network segment (subnet) that is defined by the IP address %2 and PrefixLength %3!lu!.

xInterface %1 does not support setting LinkLayerAddress.

PThe parameter %1 must be specified.

xBoth IP addresses must be from the same address family.

(Not supported.

�4VS_VERSION_INFO��
aJ
aJ?�StringFileInfo�040904B0LCompanyNameMicrosoft CorporationNFileDescriptionTCPIP WMI Providerh$FileVersion10.0.19041.1 (WinBuild.160101.0800):
InternalNameNetTCPIP.dll�.LegalCopyright� Microsoft Corporation. All rights reserved.JOriginalFilenameNetTCPIP.dll.muij%ProductNameMicrosoft� Windows� Operating System>
ProductVersion10.0.19041.1DVarFileInfo$Translation �PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPAD