false false false Bag false false false false false false false false false false false true false false false false 0 0 false false CurrentContext true false false false false false true2.7.0ManagedElement is an abstract class that provides a common superclass (or top of the inheritance tree) for the non-association classes in the CIM Schema.The Caption property is a short textual description (one- line string) of the object.64The 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 ManagedSystemElement's Name property 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 MAY be present in both the Name and ElementName properties. truetrue2.6.0CIM_Dependency is a generic association used to establish dependency relationships between ManagedElements.trueAntecedent represents the independent object in this association.trueDependent represents the object dependent on the Antecedent. 2.7.0CIM_ConcreteDependency is a generic association used to establish dependency relationships between ManagedElements. It is defined as a concrete subclass of the abstract CIM_Dependency class, to be used in place of many specific subclasses of Dependency that add no semantics - i.e., that do not clarify the type of dependency, update cardinalities, or add/remove qualifiers. Note that when defining additional semantics for Dependency that this class MUST NOT be subclassed. Specific semantics continue to be defined as subclasses of the abstract CIM_Dependency. ConcreteDependency is limited in its use as a concrete form of a general dependency. It was deemed more prudent to create this concrete subclass than to change Dependency from an abstract to a concrete class. Dependency already had multiple abstract subclasses in the CIM Schema, and wider industry usage and impact could not be anticipated.trueAntecedentAntecedent represents the independent object in this association.trueDependentDependent represents the object dependent on the Antecedent.true truetruetrue2.7.0CIM_Component is a generic association used to establish 'part of' relationships between Managed Elements. For example, it could be used to define the components or parts of a System.truetrueThe parent element in the association.trueThe child element in the association. 2.7.0CIM_ConcreteComponent is a generic association used to establish 'part of' relationships between ManagedElements. It is defined as a concrete subclass of the abstract CIM_Component class, to be used in place of many specific subclasses of Component that add no semantics - i.e., that do not clarify the type of composition, update cardinalities, or add/remove qualifiers. Note that when defining additional semantics for Component that this class MUST NOT be subclassed. Specific semantics continue to be defined as subclasses of the abstract CIM_Component. ConcreteComponent is limited in its use as a concrete form of a general composition. It was deemed more prudent to create this concrete subclass than to change Component from an abstract to a concrete class. Industry usage and impact could not be anticipated.truetrueGroupComponentThe parent element in the association.truetruePartComponentThe child element in the association.true truetrue2.7.0CIM_LogicalIdentity is an abstract and generic association, indicating that two ManagedElements represent different aspects of the same underlying entity. This relationship conveys what could be defined with multiple inheritance. In most scenarios, the Identity relationship is determined by the equivalence of Keys or some other identifying properties of the related Elements. One of the scenarios where this relationship is reasonable is to represent that a LogicalDevice is both a 'bus' entity and a 'functional' entity. For example, a Device could be both a USB (bus) and a Keyboard (functional) entity.trueSystemElement represents one aspect of the Managed Element. The use of 'System' in the role name does not limit the scope of the association. The role name was defined in the original association, where the referenced elements were limited to LogicalElements. Since that time, it has been found valuable to instantiate these types of relationships for ManagedElements, such as Collections. So, the referenced elements of the association were redefined to be ManagedElements. Unfortunately, the role name could not be changed without deprecating the entire association. This was not deemed necessary just to correct the role name.trueSameElement represents an alternate aspect of the ManagedElement. 2.7.0CIM_ConcreteIdentity associates two elements representing different aspects of the same underlying entity. It is defined as a concrete subclass of the abstract CIM_LogicalIdentity class, to be used in place of many specific subclasses of LogicalIdentity that add no semantics - i.e., that do not clarify the type of identity, update cardinalities, or add/remove qualifiers. Note -that when defining additional semantics for LogicalIdentity that this class should not be subclassed. Specifc semantics continue to be defined as subclasses of the abstract CIM_LogicalIdentity. ConcreteIdentity is limited in its use as a concrete form of a general identity relationship. It was deemed more prudent to create this concrete subclass than to change LogicalIdentity from an abstract to a concrete class. LogicalIdentity already had multiple abstract subclasses in the CIM Schema, and wider industry usage and impact could not be anticipated.trueSystemElementOne aspect of the ManagedElement. The use of 'System' in the name does not limit the scope of the association. This is an artifact of the original definition of the association.trueSameElementAnother aspect of the ManagedElement.true true2.8.0CIM_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.A datetime value indicating when the object was installed. A lack of a value does not indicate that the object is not installed.MIF.DMTF|ComponentID|001.5The Name property defines the label by which the object is known. When subclassed, the Name property can be overridden to be a Key property.1024Indicates the current status(es) of the element. Various health and operational statuses are defined. Many of the enumeration's values are self- explanatory. However, a few are not and are described in more detail. "Stressed" indicates that the element is functioning, but needs attention. Examples of "Stressed" states are overload, overheated, etc. "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 element's state and configuration may need to be updated. "Dormant" indicates that the element is inactive or quiesced. "Supporting Entity in Error" describes that this element may be "OK" but that another element, on which it is dependent, is in error. An example is a network service or endpoint that cannot function due to lower layer networking problems. "Completed" indicates the element has completed its operation. This value should be combined with either OK, Error, or Degraded so that a client can till if the complete operation passed (Completed with OK), and failure (Completed with Error). Completed with Degraded would imply the operation finished, but did not complete OK or report an error. "Power Mode" indicates 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 since it required the DEPRECATED qualifier. Due to the widespread use of the existing Status property in management applications, it is strongly RECOMMENDED that providers/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 (since it is single-valued) SHOULD also provide the primary status of the element.0123456789101112131415161718..0x8000..UnknownOtherOKDegradedStressedPredictive FailureErrorNon-Recoverable ErrorStartingStoppingStoppedIn ServiceNo ContactLost CommunicationAbortedDormantSupporting Entity in ErrorCompletedPower ModeDMTF ReservedVendor ReservedIndexedCIM_ManagedSystemElement.StatusDescriptionsStrings 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.IndexedCIM_ManagedSystemElement.OperationalStatusCIM_ManagedSystemElement.OperationalStatusA 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 overcomes the limitation of describing status via a single value, when it is really a multi-valued property (for example, an element may be OK AND Stopped. 2) A MaxLen of 10 is too restrictive and leads to unclear enumerated values. And, 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.OKErrorDegradedUnknownPred FailStartingStoppingServiceStressedNonRecoverNo ContactLost CommStopped10 2.8.0HostedDependency defines a ManagedElement in the context of another ManagedElement in which it resides.trueAntecedent1The scoping ManagedElement.trueDependentThe hosted ManagedElement.true true2.6.0CIM_LogicalElement is a base class for all the components of a System that represent abstract system components, such as Files, Processes, or LogicalDevices. true2.8.0A Job is a LogicalElement representing 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, queued, and its execution is not limited to a single system.A free form string representing the Job's status. The primary status is reflected in the inherited OperationalStatus property. JobStatus provides additional, implementation-specific details.CIM_ManagedSystemElement.OperationalStatusThe 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.CIM_Job.RunMonthCIM_Job.RunDayCIM_Job.RunDayOfWeekCIM_Job.RunStartIntervaltrueThe time that the current Job is scheduled to start. This may 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 may 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 is necessary to capture the processing information for recurring Jobs, since only the 'last' run time can be stored in this single-valued property.The time interval that the Job has been executing or the total execution time if the Job is complete. Note that this property is also present in the JobProcessingStatistics class. This is necessary to capture the processing information for recurring Jobs, since only the 'last' run time can be stored in this single-valued property.trueNumber 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.1trueThe month during which the Job should be processed. Specify 0 for January, 1 for February, and so on.01234567891011JanuaryFebruaryMarchAprilMayJuneJulyAugustSeptemberOctoberNovemberDecemberCIM_Job.RunDayCIM_Job.RunDayOfWeekCIM_Job.RunStartIntervaltrueThe 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 the end of the month. For example, 5 indicates the fifth day in 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 (e.g., 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.-3131CIM_Job.RunMonthCIM_Job.RunDayOfWeekCIM_Job.RunStartIntervaltruePositive 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.-7-6-5-4-3-2-101234567-Saturday-Friday-Thursday-Wednesday-Tuesday-Monday-SundayExactDayOfMonthSundayMondayTuesdayWednesdayThursdayFridaySaturdayCIM_Job.RunMonthCIM_Job.RunDayCIM_Job.RunStartIntervaltrueThe 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.CIM_Job.RunMonthCIM_Job.RunDayCIM_Job.RunDayOfWeekCIM_Job.RunStartIntervaltrueThis 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".12Local TimeUTC TimetrueThe time after which the Job is invalid or should be stopped. This may 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.CIM_Job.LocalOrUtcTimetrueUser to be notified upon the Job completion or failure.The User that submitted the Job or the Service/method name/etc. that caused the job to be created.CIM_OwningJobElementtrueIndicates 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 is necessary to capture the setting information that would influence a Job's results.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 is necessary to capture the processing information for recurring Jobs, since only the 'last' run data can be stored in this single-valued property.Percent0101trueIndicates 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 versus updating this property.A vendor specific error code. This MUST be set to zero if the Job completed without error. Note that this property is also present in the JobProcessingStatistics class. This is necessary to capture the processing information for recurring Jobs, since only the 'last' run error can be stored in this single-valued property.CIM_Job.ErrorDescriptionA free form string containing the vendor error description. Note that this property is also present in the JobProcessingStatistics class. This is necessary to capture the processing information for recurring Jobs, since only the 'last' run error can be stored in this single-valued property.CIM_Job.ErrorCodeDescribes 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 property, OtherRecoveryAction 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 on the queue from which it will run.012345UnknownOtherDo Not ContinueContinue With Next JobRe-run JobRun Recovery JobCIM_Job.OtherRecoveryActionA string describing the recovery action when the instance's RecoveryAction property is 1 ("Other").CIM_Job.RecoveryActionCIM_ConcreteJob.RequestStateChange()KillJob is being deprecated because there is no distiction 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.0123467..32768..65535SuccessNot SupportedUnknownTimeoutFailedAccess DeniedNot FoundDMTF ReservedVendor SpecifictrueIndicates whether or not the Job should be automatically deleted upon termination. This parameter takes precedence over the property, DeleteOnCompletion. 2.8.0A concrete version of Job. This class represents a generic and instantiable unit of work, such as a batch or a print job.trueWithin 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'.trueNameThe user friendly name for this instance of 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.)1024JobState 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 may be restarted in a seamless manner. Shutting Down (6) indicates 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 may 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 may have been left running and cleanup may be required to free up resources. Exception (10) indicates that the Job is in an abnormal state that may be indicative of an error condition. Actual status may be surfaced though job-specific objects. Service (11) indicates that the Job is in a vendor-specific state that supports problem discovery and/or resolution.23456789101112..3276732768..65535NewStartingRunningSuspendedShutting DownCompletedTerminatedKilledExceptionServiceDMTF ReservedVendor ReservedThe date/time when the Job's State 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.Requests that the job's state be changed to the value specified in the RequestedState parameter. Invoking the RequestStateChange method multiple times could result in earlier requests being overwritten/lost. If 0 is returned, then the task completed successfully. Any other return code indicates an error condition.0123456..40964097409840994100..3276732768..65535Completed with No ErrorNot SupportedUnknown/Unspecified ErrorCan NOT complete within Timeout PeriodFailedInvalid ParameterIn UseDMTF ReservedMethod Parameters Checked - Transition StartedInvalid State TransitionUse of Timeout Parameter Not SupportedBusyMethod ReservedVendor SpecifictrueChanges the state of a job. Start (2) changes the state to 'Running'. Suspend (3) stops the job temporarily. The intention is to subsequently restart the job with 'Start'. It may be possible to enter the 'Service' state while suspended - this is job-specific. Terminate (4) stops the job cleanly, saving data, preserving 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 state. Service (6) puts the job into a vendor-specific service state. The job may be able to be restarted.234567..3276732768..65535StartSuspendTerminateKillServiceDMTF ReservedVendor ReservedtrueA 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 doesn't support this parameter. A return code of 'Use Of Timeout Parameter Not Supported' MUST be returned. true2.8.0This class extends LogicalElement to abstract the concept of an element that is enabled and disabled, such as a LogicalDevice or a ServiceAccessPoint.EnabledState is an integer enumeration that indicates the enabled/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/disabled states: Enabled (2) indicates that the element is/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 doesn't support being enabled/disabled. Enabled but Offline (6) indicates that the element may 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 may be completing commands, but will queue any new requests. Quiesce (9) indicates that the element is enabled but in a restricted mode. The element's behavior is similar to the Enabled state, but it only processes a restricted set of commands. All other requests are queued. Starting (10) indicates that the element is in the process of going to an Enabled state. New requests are queued.01234567891011..3276732768..65535UnknownOtherEnabledDisabledShutting DownNot ApplicableEnabled but OfflineIn TestDeferredQuiesceStartingDMTF ReservedVendor ReservedCIM_EnabledLogicalElement.OtherEnabledState5A string describing the element's enabled/disabled state when the EnabledState property is set to 1 ("Other"). This property MUST be set to NULL when EnabledState is any value other than 1.CIM_EnabledLogicalElement.EnabledStateRequestedState is an integer enumeration indicating the last requested or desired state for the element. The actual state of the element is represented by EnabledState. This property is provided to compare the last requested and current enabled/disabled states. Note that when EnabledState is set to 5 ("Not Applicable"), then this property has no meaning. By default, the element's RequestedState is 5 ("No Change"). Refer to the EnabledState's property Description for explanations of the values in the RequestedState enumeration. 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). The former, Reboot, refers to doing a "Shut Down" and then moving to an "Enabled" state. The latter, Reset, indicates that the element is first "Disabled" and then "Enabled". The distinction between requesting "Shut Down" and "Disabled" should also be noted. The former, Shut Down, requests an orderly transition to the Disabled state, and MAY involve removing power, to completely erase any existing state. The latter, 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 may be overridden and defined as WRITEable in a subclass. The method approach is considered superior to a WRITEable property, since it allows an explicit invocation of the operation and the return of a result code.234567891011..32768..65535EnabledDisabledShut DownNo ChangeOfflineTestDeferredQuiesceRebootResetDMTF ReservedVendor ReservedCIM_EnabledLogicalElement.EnabledState5trueAn enumerated value indicating an administrator's default/startup configuration for an element's Enabled State. By default, the element is "Enabled" (value=2).235678..3276732768..65535EnabledDisabledNot ApplicableEnabled but OfflineNo DefaultDMTF ReservedVendor Reserved2The date/time when the element's EnabledState 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.Requests that the element's state be changed to the value specified in the RequestedState parameter. When the requested state change takes place, the element's EnabledState and RequestedState will be the same. Invoking the RequestStateChange method multiple times could result in earlier requests being overwritten/lost. If 0 is returned, then the task completed successfully and the use of ConcreteJob was not required. If 4096 (0x1000) is returned, then the task will take some time to complete, ConcreteJob will be created, and its reference returned in the output parameter Job. Any other return code indicates an error condition.0123456..40964097409840994100..3276732768..65535Completed with No ErrorNot SupportedUnknown/Unspecified ErrorCan NOT complete within Timeout PeriodFailedInvalid ParameterIn UseDMTF ReservedMethod Parameters Checked - Job StartedInvalid State TransitionUse of Timeout Parameter Not SupportedBusyMethod ReservedVendor SpecificCIM_EnabledLogicalElement.RequestedStatetrueThe state requested for the element. This information will be placed into the instance's RequestedState property if the RequestStateChange method's return code is 0, 3, or 4096 (0x1000) - 'Completed with No Error', 'Timeout', or 'Job Started' respectively. Refer to the description of the EnabledState and RequestedState properties for the detailed meanings of the RequestedState values.23467891011..32768..65535EnabledDisabledShut DownOfflineTestDeferQuiesceRebootResetDMTF ReservedVendor ReservedCIM_EnabledLogicalElement.RequestedStatefalsetrueReference to the job (may be null if task completed).trueA 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 doesn't support this parameter. A return code of 'Use Of Timeout Parameter Not Supported' MUST be returned. true2.8.0Indicates that two ManagedElements were aligned or made to be equivalent at the specified point in time. If the boolean property SyncMaintained is TRUE, then synchronization of the Elements is preserved. Both like and unlike objects may be synchronized. For example, two WatchDog timers may be aligned, or the contents of a LogicalFile may be synchronized with the contents of a StorageExtent.trueSystemElement represents one ManagedElement that is synchronized with the entity referenced as SyncedElement.trueSyncedElement represents another ManagedElement that is synchronized with the entity referenced as SystemElement.The point in time that the Elements were synchronized.Boolean indicating whether synchronization is maintained. true2.7.0CIM_System represents an entity made up of component parts (defined by the SystemComponent relationship), that operates as a 'functional whole'. Systems are top level objects in the CIM hierarchy, requiring no scoping or weak relationships in order to exist and have context. It should be reasonable to uniquely name and manage a System at an enterprise level. For example, a ComputerSystem is a kind of System that can be uniquely named and independently managed in an enterprise. However, this is not true for the power supply (or the power supply sub-'system') within the computer. Although a System may be viewed as a Collection, this is not the correct model. A Collection is simply a 'bag' that 'holds' its members. A System is a higher level abstraction, built out of its individual components. It is more than a sum of its parts. Note that System is a subclass of EnabledLogicalElement which allows the entire abstraction to be functionally enabled/disabled - at a higher level than enabling/disabling its component parts.trueCreationClassName 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.256trueNameThe inherited Name serves as key of a System instance in an enterprise environment.256The System object and its derivatives are Top Level Objects of CIM. They provide the scope for numerous components. Having unique System keys is required. A heuristic can be defined in individual System subclasses to attempt to always generate the same System Name Key. The NameFormat property identifies how the System name was generated, using the subclass' heuristic.64trueThe name of the primary system owner. The system owner is the primary user of the system.64MIF.DMTF|General Information|001.3trueA string that provides information on how the primary system owner can be reached (e.g. phone number, email address, ...).256MIF.DMTF|General Information|001.4trueAn array (bag) of strings that specify the administrator -defined roles this System plays in the managed environment. Examples might be 'Building 8 print server' or 'Boise user directories'. A single system may perform multiple roles. Note that instrumentation's view of a System's 'roles' is defined by instantiating a specific subclass of System and/ or by properties in a subclass. For example, a ComputerSystem's purpose is defined using the Dedicated and OtherDedicatedDescription properties. 2.7.0CIM_SystemComponent is a specialization of the CIM_Component association that establishes 'part of' relationships between a System and any ManagedSystemElements of which it is composed. The use of this association is cautioned - versus the use of a subclass such as SystemDevice, or a peer association such as HostedService. This class is very broadly defined which can lead to erroneous use. For example, Access Points that are dependent on (and hosted on) a System are NOT Components of the System. The System is not made up of any AccessPoint 'parts', which is why a Dependency association, HostedAccessPoint, was defined. Similarly, a PhysicalPackage is not a 'part' of a System, since the physical element exists independently of any internal components, software, etc. In fact, again, a Dependency relationship is true - where a ComputerSystem is Dependent on its packaging, as described by the ComputerSystemPackage association.truetrueGroupComponentThe parent System in the Association.truetruePartComponentThe child element that is a component of a System.true 2.8.0This is a special grouping of ManagedSystemElements. The grouping is viewed as a single entity, reflecting that all of its components are administered similarly - either by the same user, group of users or policy. It serves as an aggregation point to associate one or more of the following elements: network devices, such as routers and switches, servers, and other resources that can be accessed by end systems. This grouping of devices plays an essential role in ensuring that the same administrative policy and actions are applied to all of the devices in the grouping. The specific behavior and/or semantics of the AdminDomain can be identified through its aggregated and associated entities.NameFormatThe NameFormat property identifies how the Name of the AdminDomain is generated, using the heuristic specified in the CIM V2 System Model spec. It assumes that the documented rules are traversed in order, to determine and assign a Name. The NameFormat Values list defines the precedence order for assigning the Name of the AdminDomain. "FC" has been deprecated and replaced by "WWN" to be consistent with the other ValueMaps.OtherASNAPNOCPOPRNPIPIPXSNADialWANLANISDNFrame RelayATME.164IBFCPolicy RepositoryWWNOtherAutonomous SystemNetwork Access ProviderNetwork Operations CenterPoint of PresenceRegional Network ProviderIPIPXSNADialWANLANISDNFrame RelayATME.164InfinibandFibre ChannelPolicy RepositoryFibre Channel Worldwide NameCIM_AdminDomain.Name64 2.6.0A relationship that aggregates one or more lower-level AdminDomain instances into a higher-level AdminDomain.truetrueAn AdminDomain that aggregates other AdminDomains.GroupComponenttruetrueAn AdminDomain aggregated by another AdminDomain.PartComponenttrue true2.7.0A CIM_Service is a Logical Element that contains the information necessary to represent and manage the functionality provided by a Device and/or SoftwareFeature. A Service is a general-purpose object to configure and manage the implementation of functionality. It is not the functionality itself.trueCIM_System.CreationClassNameThe scoping System's CreationClassName.256trueCIM_System.NameThe scoping System's Name.256trueCreationClassName 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.256trueNameThe Name property uniquely identifies the Service and provides an indication of the functionality that is managed. This functionality is described in more detail in the object's Description property.256trueThe name of the primary owner for the service, if one is defined. The primary owner is the initial support contact for the Service.64MIF.DMTF|General Information|001.3trueA string that provides information on how the primary owner of the Service can be reached (e.g. phone number, email address, ...).256MIF.DMTF|General Information|001.4CIM_Service.EnabledDefaultStartMode is a string value indicating whether the Service is automatically started by a System, Operating System, etc. or only started upon request. This property is deprecated in lieu of the EnabledDefault property inherited from EnabledLogicalElement, which addresses the same semantics. 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, StartMode was grandfathered into the Schema. Use of the Deprecated qualifier allows the maintenance of the existing property, but also permits an improved, clarified definition using EnabledDefault.AutomaticManual10Started is a boolean indicating whether the Service has been started (TRUE), or stopped (FALSE).The StartService method places the Service in the started state. 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 StartService method should set the RequestedState property appropriately. The method returns an integer value of 0 if the Service was successfully started, 1 if the request is not supported and any other number to indicate an error. 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 overlaps in semantics with the RequestStateChange method inherited from EnabledLogicalElement. This method is maintained since it has been widely implemented, and its simple 'start' semantics are convenient to use.The StopService method places the Service in the stopped state. 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 StopService method should set the RequestedState property appropriately. The method returns an integer value of 0 if the Service was successfully stopped, 1 if the request is not supported and any other number to indicate an error. 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 overlaps in semantics with the RequestStateChange method inherited from EnabledLogicalElement. This method is maintained since it has been widely implemented, and its simple 'stop' semantics are convenient to use. 2.8.0CIM_HostedService is an association between a Service and the System on which the functionality resides. The cardinality of this association is 1-to-many. A System may host many Services. Services are weak with respect to their hosting System. Heuristic: A Service is hosted on the System where the LogicalDevices or SoftwareFeatures that implement the Service are located. The model does not represent Services hosted across multiple systems. This is modeled as an ApplicationSystem that acts as an aggregation point for Services, that are each located on a single host.true11The hosting System.AntecedenttruetrueThe Service hosted on the System.Dependenttrue CIM_ServiceAvailableToElement2.7.0The use of the CIM_ProvidesServiceToElement class has been deprecated. Instead, ServiceAvailableToElement conveys the semantics of 'use', while the subclasses of ProvidesService ToElement (or the ConcreteDependency association) describe dependency relationships. CIM_ProvidesServiceToElement was meant to generalize the ServiceServiceDependency association. It tried to indicate that ManagedElements may use the functionality provided by one or more Services. An example is that a Processor and an enclosure (a PhysicalElement) may use AlertOnLAN Services to signal an incomplete or erroneous boot. In reality, AlertOnLAN is simply a HostedService on a computer system that is generally 'available for 'use' and not a dependency of the processor or enclosure. To describe that use of the service may be restricted or have limited availability/ applicability, then the CIM_ServiceAvailableToElement association would be instantiated.trueCIM_ServiceAvailableToElement.ServiceProvidedAntecedentThe Service provided.trueCIM_ServiceAvailableToElement.UserOfServiceDependentThe ManagedElement dependent on the Service.true true2.7.0CIM_ServiceAvailableToElement conveys the semantics of a Service being available for the 'use' of a ManagedElement. An example is that a Processor and an enclosure (a PhysicalElement) may use AlertOnLAN Services to signal an incomplete or erroneous boot. In reality, AlertOnLAN is simply a HostedService on a computer system that is generally 'available for use', and not a dependency of the processor or enclosure. To describe that use of this service is restricted or has limited availability/applicability, then the CIM_ServiceAvailableToElement association would be instantiated between the Service and specific CIM_Processors and CIM_Chassis .trueThe Service that is available.trueThe ManagedElement that may use the Service. true2.7.0ServiceAffectsElement represents an association between a Service and the ManagedElement(s) that may be affected by its execution. Instantiating this association indicates that running the service will pose some burden on the ManagedElement that may affect performance, throughput, availability, etc.trueThe Managed Element affected by the Service.trueThe Service that is affecting the ManagedElement.An enumeration describing the 'effect' on the ManagedElement. This array corresponds to the OtherElementEffectsDescriptions array, where the latter provides details related to the high-level 'effects' enumerated by this property. Additional detail is required if the ElementEffects array contains the value 1, "Other".01234UnknownOtherExclusive UsePerformance ImpactElement IntegrityIndexedCIM_ServiceAffectsElement.OtherElementEffectsDescriptionsProvides details for the 'effect' at the corresponding array position in ElementEffects. This information is required ElementEffects contains the value 1 ("Other").IndexedCIM_ServiceAffectsElement.ElementEffects 2.7.0CIM_ServiceServiceDependency is an association between a Service and another Service, indicating that the latter is required to be present, required to have completed, or must be absent for the former Service to provide its functionality. For example, Boot Services may be dependent upon underlying system initialization Services. In the case of the initialization Services, the Boot Service may be dependent on the init Services completing. Examining the ServiceServiceDependency class definition, note that its superclass ProvidesServiceToElement is deprecated. Unfortunately, ProvidesServiceToElement cannot be removed from the object hierarchy without a major Schema release. When/if this occurs, the ProvidesServiceToElement superclass will be removed, and ServiceServiceDependency will subclass from CIM_Dependency directly.trueThe required Service.AntecedenttrueThe Service that is dependent on an underlying Service.DependenttrueThe nature of the Service to Service dependency. This property describes that the associated Service must have completed (value=2), must be started (3) or must not be started (4) in order for the Service to function.01234UnknownOtherService Must Have CompletedService Must Be StartedService Must Not Be StartedThis property describes that the Antecedent Service must be restarted after the Dependent operation is complete. 2.6.0The ServiceComponent aggregation models a set of subordinate Services that are aggregated together to form a higher-level service.truetrueGroupComponentThe parent Service.truetruePartComponentThe component Service.true true2.6.0CIM_ServiceAccessPoint represents the ability to utilize or invoke a Service. Access points represent that a Service is made available to other entities for use.trueCIM_System.CreationClassNameThe scoping System's CreationClassName.256trueCIM_System.NameThe scoping System's Name.256trueCreationClassName 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.256trueNameThe 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 object's Description property.256 2.8.0CIM_HostedAccessPoint is an association between a Service AccessPoint and the System on which it is provided. The cardinality of this association is 1-to-many and is weak with respect to the System. Each System may host many ServiceAccessPoints. Heuristic: If the implementation of the ServiceAccessPoint is modeled, it must be implemented by a Device or SoftwareFeature that is part of the System hosting the ServiceAccessPoint.true11The hosting System.AntecedenttruetrueThe SAP(s) that are hosted on this System.Dependenttrue true2.8.0CIM_SAPAvailableForElement conveys the semantics of a Service Access Point being available for a ManagedElement. When CIM_SAPAvailableForElement is not instantiated then the SAP is assumed to be generally available. If instantiated, the SAP is only available for the associated ManagedElements. For example, a device might provide management access through a URL. This association allows the URL to be advertised for the device.trueThe Service Access Point that is available.trueThe ManagedElement for which the SAP is available. 2.6.0CIM_ServiceSAPDependency is an association between a Service and a ServiceAccessPoint indicating that the referenced SAP is utilized by the Service to provide its functionality. For example, Boot Services may invoke BIOS' Disk Services (interrupts) in order to function.trueAntecedentThe required ServiceAccessPoint.trueDependentThe Service that is dependent on an underlying SAP.true 2.6.0CIM_ServiceAccessBySAP is an association that identifies the access points for a Service. For example, a printer may be accessed by Netware, MacIntosh or Windows ServiceAccess Points, potentially hosted on different Systems.trueAntecedentThe Service.trueDependentAn Access Point for a Service. Access points are dependent in this relationship since they have no function without a corresponding Service.true 2.6.0CIM_SAPSAPDependency is an association between a Service AccessPoint and another ServiceAccessPoint indicating that the latter is required in order for the former ServiceAccess Point to utilize or connect with its Service. For example, to print at a network printer, local Print Access Points must utilize underlying network-related SAPs, or ProtocolEndpoints, in order to send the print request.trueAntecedentThe required ServiceAccessPoint.trueDependentThe ServiceAccessPoint that is dependent on an underlying SAP.true 2.7.0This association defines a connection that is currently communicating, or is configured to communicate, between two ServiceAccessPoints. It is used when the connection is not treated as a ManagedElement itself (i.e., with Status, statistics, etc.), but its existence is known. The SAPs that are connected are typically at the same networking or application layer.trueA ServiceAccessPoint that is configured to communicate and/or is actively communicating with the Dependent SAP. In a unidirectional connection, this is the SAP which is transmitting.AntecedenttrueA second SeriveAccessPoint that is/can communicate with the Antecedent SAP. In a unidirectional connection, this is the SAP that is receiving the communication.DependenttrueNo valueThe type of traffic that is carried over this connection. This property is deprecated since it is incorrectly placed on the association. Unicast, broadcast or other traffic types are not a function of the connection between the referenced endpoints, but on the addressing, protocol, and basic functionality of the endpoints.012345UnknownOtherUnicastBroadcastMulticastAnycastCIM_ActiveConnection.OtherTrafficDescriptionNo valueA string describing the type of traffic that is being carried over this instance when its Type property is set to 1 (e.g., 'Other'). This property is deprecated since it is incorrectly placed on the association. Unicast, broadcast or other traffic types are not a function of the connection between the referenced endpoints, but on the addressing, protocol, and basic functionality of the endpoints.64CIM_ActiveConnection.TrafficTypeTRUE means that this connection is uni-directional; FALSE means that this connection is bi-directional. When the connection is unidirectional, the 'speaker' should be defined as the Antecedent reference. In a bidirectional connection, the selection of which AccessPoint is the Antecedent or Dependent is immaterial. 2.8.0RemoteServiceAccessPoint describes access and/or addressing information for a remote connection, that is known to a 'local' network element. This information is scoped/contained by the 'local' network element, since this is the context in which it is 'remote'. Why the remote access point is relevant and information on its use are described by subclassing RemoteService AccessPoint, or by associating to it.Access and/or addressing information for a remote connection. This can be a host name, network address or similar information.