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.CIM_RemoteServiceAccessPoint.InfoFormatAn enumerated integer describing the format and interpretation of the AccessInfo property.12345678910111213100101102103104200201202203204205..32768..65535OtherHost NameIPv4 AddressIPv6 AddressIPX AddressDECnet AddressSNA AddressAutonomous System NumberMPLS LabelIPv4 Subnet AddressIPv6 Subnet AddressIPv4 Address RangeIPv6 Address RangeDial StringEthernet AddressToken Ring AddressATM AddressFrame Relay AddressURLFQDNUser FQDNDER ASN1 DNDER ASN1 GNKey IDDMTF ReservedVendor ReservedCIM_RemoteServiceAccessPoint.OtherInfoFormatDescriptionDescribes the format when the property InfoFormat is set to 1 ("Other").CIM_RemoteServiceAccessPoint.InfoFormat 2.7.0RemotePort adds port information to the access data (such as IP Address), specified in and inherited from RemoteServiceAccessPoint. For example, using the additional properties in this class, one could indicate that UDP Port 123 is accessed at IP Address xyz. The IP Address would be specified in the inherited AccessInfo property, while the UDP Port number would be specified in this class' property, PortInfo.Port information that may further specify the remote access information.CIM_RemotePort.PortProtocolAn enumerated integer describing the protocol of the port addressed by PortInformation.12332768..65535OtherTCPUDPVendor SpecificCIM_RemotePort.OtherProtocolDescriptionDescribes the protocol when the property PortProtocol is set to 1 ("Other").CIM_RemotePort.PortProtocol 2.7.0CIM_ServiceAccessURI represents the ability to utilize or invoke a Service via a uniform resource identifier. RFC 1738 describes the Uniform Resource Locator which is a more specific form of a URI, and RFC 2396 describes the broader, inclusive URI. Quoting from the RFC, 'A Uniform Resource Identifier (URI) is a compact string of characters for identifying an abstract or physical resource.' In the context of a ServiceAccessPoint, a URI contains the information necessary to access an associated service (associated via ServiceAccessBySAP), using a syntax specific to that service.trueThe LabeledURI property is based on RFC 2079 and its value and syntax is service specific.256 2.8.0A communication point from which data may be sent or received. ProtocolEndpoints link system/computer interfaces to LogicalNetworks.DescriptionMIB.IETF|IF-MIB.ifDescrThe Description property provides a textual description of the object.OperationalStatusMIB.IETF|IF-MIB.ifOperStatusIndicates 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.StatusDescriptionsEnabledStateMIB.IETF|IF-MIB.ifAdminStatusEnabledState 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.OtherEnabledStateTimeOfLastStateChangeMIB.IETF|IF-MIB.ifLastChangeThe 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.A string which 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 chosen is described in the NameFormat property of this class.256trueNameNameFormat contains the naming heuristic that is chosen to ensure that the value of the Name property is unique. For example, one might choose to prepend the name of the port or interface with the Type of ProtocolEndpoint that this instance is (e.g., IPv4) followed by an underscore.256CIM_ProtocolEndpoint.ProtocolIFTypeProtocolType is an enumeration providing information to categorize and classify different instances of this class. For most instances, information in this enumeration and the subclass' definition 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). Hence, this property is needed to define the type of Endpoint. This property is deprecated in lieu of the ProtocolIFType enumeration. This is done to have better alignment between the IETF's IF-MIB and this CIM class.0123456789101112131415161718192021222324252627UnknownOtherIPv4IPv6IPXAppleTalkDECnetSNACONPCLNPVINESXNSATMFrame RelayEthernetTokenRingFDDIInfinibandFibre ChannelISDN BRI EndpointISDN B Channel EndpointISDN D Channel EndpointIPv4/v6BGPOSPFMPLSUDPTCPCIM_ProtocolEndpoint.OtherTypeDescriptionProtocolIFType is an enumeration synchronized with the IANA ifType MIB, 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.0123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224..409540964097409840994100410141024103410441054106410741084109411041114112411341144115..3276732768..UnknownOtherRegular 1822HDH 1822DDN X.25RFC877 X.25Ethernet CSMA/CDISO 802.3 CSMA/CDISO 802.4 Token BusISO 802.5 Token RingISO 802.6 MANStarLANProteon 10MbitProteon 80MbitHyperChannelFDDILAP-BSDLCDS1E1Basic ISDNPrimary ISDNProprietary Point-to-Point SerialPPPSoftware LoopbackEONEthernet 3MbitNSIPSLIPUltraDS3SIPFrame RelayRS-232ParallelARCNetARCNet PlusATMMIO X.25SONETX.25 PLEISO 802.211cLocalTalkSMDS DXIFrame Relay ServiceV.35HSSIHIPPIModemAAL5SONET PathSONET VTSMDS ICIPProprietary Virtual/InternalProprietary MultiplexorIEEE 802.12Fibre ChannelHIPPI 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.11IBM 260/370 OEMI ChannelESCONData Link SwitchingISDN S/T InterfaceISDN U InterfaceLAP-DIP SwitchRemote Source Route BridgingATM LogicalDS0DS0 BundleBSCAsyncCombat Net RadioISO 802.5r DTRExt Pos Loc Report SystemAppleTalk Remote Access ProtocolProprietary ConnectionlessITU X.29 Host PADITU X.3 Terminal PADFrame Relay MPIITU X.213ADSLRADSLSDSLVDSLISO 802.5 CRFPMyrinetVoice Receive and TransmitVoice Foreign Exchange OfficeVoice Foreign Exchange ServiceVoice EncapsulationVoice over IPATM DXIATM FUNIATM IMAPPP Multilink BundleIP over CDLCIP over CLAWStack to StackVirtual IP AddressMPCIP over ATMISO 802.5j Fibre Token RingTDLCGigabit EthernetHDLCLAP-FV.37X.25 MLPX.25 Hunt GroupTransp HDLCInterleave ChannelFAST ChannelIP (for APPN HPR in IP Networks)CATV MAC LayerCATV DownstreamCATV UpstreamAvalon 12MPP SwitchTunnelCoffeeCircuit Emulation ServiceATM SubInterfaceLayer 2 VLAN using 802.1QLayer 3 VLAN using IPLayer 3 VLAN using IPXDigital Power LineMultimedia Mail over IPDTMDCNIP ForwardingMSDSLIEEE 1394IF-GSN/HIPPI-6400DVB-RCC MAC LayerDVB-RCC DownstreamDVB-RCC UpstreamATM VirtualMPLS TunnelSRPVoice over ATMVoice over Frame RelayISDLComposite LinkSS7 Signaling LinkProprietary P2P WirelessFrame ForwardRFC1483 Multiprotocol over ATMUSBIEEE 802.3ad Link AggregateBGP Policy AccountingFRF .16 Multilink FRH.323 GatekeeperH.323 ProxyMPLSMulti-Frequency Signaling LinkHDSL-2S-HDSLDS1 Facility Data LinkPacket over SONET/SDHDVB-ASI InputDVB-ASI OutputPower LineNon Facility Associated SignalingTR008GR303 RDTGR303 IDTISUPProprietary Wireless MAC LayerProprietary Wireless DownstreamProprietary Wireless UpstreamHIPERLAN Type 2Proprietary Broadband Wireless Access Point to MulipointSONET Overhead ChannelDigital Wrapper Overhead ChannelATM Adaptation Layer 2Radio MACATM RadioInter Machine TrunkMVL DSLLong Read DSLFrame Relay DLCI EndpointATM VCI EndpointOptical ChannelOptical TransportProprietary ATMVoice over CableInfinibandTE LinkQ.2931Virtual Trunk GroupSIP Trunk GroupSIP SignalingCATV Upstream ChannelEconetFSAN 155Mb PONFSAN 622Mb PONTransparent BridgeLine GroupVoice E&M Feature GroupVoice FGD EANAVoice DIDMPEG Transport6To4GTPParadyne EtherLoop 1Paradyne EtherLoop 2Optical Channel GroupHomePNAGFPciscoISLvlanactelisMetaLOOPFcipIANA ReservedIPv4IPv6IPv4/v6IPXDECnetSNACONPCLNPVINESXNSISDN B Channel EndpointISDN D Channel EndpointBGPOSPFUDPTCP802.11a802.11b802.11g802.11hDMTF ReservedVendor ReservedMIB.IETF|IF-MIB.ifTypeCIM_ProtocolEndpoint.OtherTypeDescriptionA string describing the type of ProtocolEndpoint when the Type property of this class (or any of its subclasses) is set to 1 (i.e., "Other"). This property should be set to NULL when the Type property is any value other than 1.64CIM_ProtocolEndpoint.ProtocolTypeCIM_ProtocolEndpoint.ProtocolIFType 2.6.0This 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. Since a ProtocolEndpoint is a kind of ServiceAccessPoint, this binding can be used to establish a layering of two protocols, the upper layer represented by the Dependent and the lower layer represented by the Antecedent.trueThe lower-level endpoint which is accessed by the SAP.AntecedenttrueThe AccessPoint or ProtocolEndpoint dependent on the lower level endpoint.Dependenttrue 2.7.0This association represents a ProtocolEndpoint provided by a Service, to allow access to the Service.trueThe Service that is accessed by the ProtocolEndpoint.AntecedenttrueThe ProtocolEndpoint that provides access to the Service.Dependenttrue true2.8.0Subclasses of CIM_PhysicalElement define any component of a System that has a distinct physical identity. Instances of this class can be defined in terms of labels that can be physically attached to the object. All Processes, Files, and LogicalDevices are considered not to be Physical Elements. For example, it is not possible to attach a label to a modem. It is only possible to attach a label to the card that implements the modem. The same card could also implement a LAN adapter. These are tangible Managed SystemElements (usually actual hardware items) that have a physical manifestation of some sort. A ManagedSystem Element is not necessarily a discrete component. For example, it is possible for a single Card (which is a type of PhysicalElement) to host more than one LogicalDevice. The card would be represented by a single PhysicalElement associated with multiple Devices.trueAn arbitrary string that uniquely identifies the Physical Element and serves as the Element's key. The Tag property can contain information such as asset tag or serial number data. The key for PhysicalElement is placed very high in the object hierarchy in order to independently identify the hardware/entity, regardless of physical placement in or on Cabinets, Adapters, etc. For example, a hotswappable or removeable component may be taken from its containing (scoping) Package and be temporarily unused. The object still continues to exist - and may even be inserted into a different scoping container. Therefore, the key for Physical Element is an arbitrary string and is defined independently of any placement or location-oriented hierarchy.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.256ElementNameMIB.IETF|Entity-MIB.entPhysicalNameA 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.The name of the organization responsible for producing the PhysicalElement. This may be the entity from whom the Element is purchased, but this is not necessarily true. The latter information is contained in the Vendor property of CIM_Product.256MIB.IETF|Entity-MIB.entPhysicalMfgNameThe name by which the PhysicalElement is generally known.256MIB.IETF|Entity-MIB.entPhysicalDescrThe stock keeping unit number for this PhysicalElement.64A manufacturer-allocated number used to identify the Physical Element.256MIB.IETF|Entity-MIB.entPhysicalSerialNumA string indicating the version of the PhysicalElement.64MIB.IETF|Entity-MIB.entPhysicalHardwareRevThe part number assigned by the organization responsible for producing or manufacturing the PhysicalElement.256MIB.IETF|Entity-MIB.entPhysicalModelNametrueOtherIdentifyingInfo captures additional data, beyond that of Tag information, that could be used to identify a Physical Element. One example is bar code data associated with an Element that also has an asset tag. Note that if only bar code data is available and is unique/able to be used as an Element key, this property would be NULL and the bar code data used as the class key, in the Tag property.MIB.IETF|Entity-MIB.entPhysicalAliasBoolean indicating that the PhysicalElement is powered on (TRUE), or is currently off (FALSE).Date that this PhysicalElement was manufactured.A vendor-specific hardware type for the PhysicalElement. It describes the specific equipment type for the element, as defined by the vendor/manufacturer.MIB.IETF|Entity-MIB.entPhysicalVendorTypetrueUser-assigned and writeable asset tracking identifier for the PhysicalElement.MIB.IETF|Entity-MIB.entPhysicalAssetIDBoolean indicating whether this PhysicalElement can be FRUed (TRUE) or not (FALSE).MIB.IETF|Entity-MIB.entPhysicalIsFRU 2.6.0The Location class specifies the position and address of a PhysicalElement.trueName is a free-form string defining a label for the Location. It is a part of the key for the object.256truePosition is a free-form string indicating the placement of a PhysicalElement. It can specify slot information on a HostingBoard, mounting site in a Cabinet, or latitude and longitude information, for example, from a GPS. It is part of the key of the Location object.256Address is a free-form string indicating a street, building or other type of address for the PhysicalElement's Location.1024 true2.7.0ElementLocation associates a ManagedElement with a Location for positioning, inventory, maintenance and similar purposes. PhysicalElements can certainly have Locations - this is explicitly defined in a subclass, PhysicalElement Location. However, other ManagedElements may also be associated with Locations. For example, Organizations may be 'in' one or more Locations, or Services may be restricted to a Location.trueThe ManagedElement whose Location is specified.trueThe element's Location. 2.7.0PhysicalElementLocation associates a PhysicalElement with a Location object for inventory or replacement purposes.trueElementThe PhysicalElement whose Location is specified.truePhysicalLocation1The PhysicalElement's Location.true true2.7.0ContainedLocation defines one location in the context of another. For example, a campus may 'contain' a building, which in turn 'contains' a floor.truetrueGroupComponent1The containing location.truetruePartComponentThe contained location.true 2.7.0Similar to the way that LogicalDevices are 'Realized' by PhysicalElements, Systems may be associated with specific packaging/PhysicalElements. This association explicitly defines the relationship between a System and its packaging.trueAntecedentThe PhysicalElement(s) that provide the packaging of a System.trueDependentThe System whose packaging is described.true 2.8.0SoftwareIdentity represents software, viewed as an asset and/or individually identifiable entity (similar to Physical Element). It does NOT indicate whether the software is installed, executing, etc. (The latter is the role of the SoftwareFeature/ SoftwareElement classes and the Application Model.) Since software may be acquired, SoftwareIdentity can be associated with a Product using the ProductSoftwareComponent relationship. Note that the Application Model manages the deployment and installation of software via the classes, SoftwareFeatures and SoftwareElements. The deployment/installation concepts are related to the asset/identity one. In fact, a SoftwareIdentity may correspond to a Product, or to one or more SoftwareFeatures or SoftwareElements - depending on the granularity of these classes and the deployment model. The correspondence of Software Identity to Product, SoftwareFeature or SoftwareElement is indicated using the ConcreteIdentity association. Note that there may not be sufficient detail or instrumentation to instantiate ConcreteIdentity. And, if the association is instantiated, some duplication of information may result. For example, the Vendor described in the instances of Product and SoftwareIdentity MAY be the same. However, this is not necessarily true, and it is why vendor and similar information are duplicated in this class. Note that ConcreteIdentity can also be used to describe the relationship of the software to any LogicalFiles that result from installing it. As above, there may not be sufficient detail or instrumentation to instantiate this association.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'.The major number component of the software's version information - for example, '12' from version 12.1(3)T. This property is defined as a numeric value to allow the determination of 'newer' vs. 'older' releases. A 'newer' major release is indicated by a larger numeric value.The minor number component of the software's version information - for example, '1' from version 12.1(3)T. This property is defined as a numeric value to allow the determination of 'newer' vs. 'older' releases. A 'newer' minor release is indicated by a larger numeric value.The revision or maintenance release component of the software's version information - for example, '3' from version 12.1(3)T. This property is defined as a numeric value to allow the determination of 'newer' vs. 'older' releases. A 'newer' revision is indicated by a larger numeric value.The build number of the software.A string representing the complete software version information - for example, '12.1(3)T'. This string and the numeric major/minor/revision/build properties are complementary. Since vastly different representations and semantics exist for versions, it is not assumed that one representation is sufficient to permit a client to perform computations (i.e., the values are numeric) and a user to recognize the software's version (i.e., the values are understandable and readable). Hence, both numeric and string representations of version are provided.Specifies the target operating systems of the software. Due to the extreme variability in operating systems, this property is defined as a string array.Manufacturer of this software.The language editions supported by the software. The language codes defined in ISO 639 should be used.An array of enumerated integers that classify this software. For example, the software MAY be instrumentation (value=5) or firmware and diagnostic software (10 and 7). The use of value 6, Firmware/BIOS, is being deprecated. Instead, either the value 10 (Firmware) and/or 11 (BIOS/FCode) SHOULD be used.01234567891011..0x8000..0xFFFFUnknownOtherDriverConfiguration SoftwareApplication SoftwareInstrumentationFirmware/BIOSDiagnostic SoftwareOperating SystemMiddlewareFirmwareBIOS/FCodeDMTF ReservedVendor ReservedIndexedCIM_SoftwareIdentity.ClassificationDescriptionsAn array of free-form strings providing more detailed explanations for any of the entries in the Classifications array. Note that each entry is related to one in the Classifications array located at the same index.IndexedCIM_SoftwareIdentity.ClassificationsA manufacturer-allocated number used to identify the software. 2.8.0ElementSoftwareIdentity allows a Managed Element to report its software related asset information (firmware, drivers, configuration software, and etc.)trueAntecedentA LogicalElement's Software Asset.trueDependentThe ManagedElement that requires or uses the software.trueIndicates the element's ability to upgrade this software asset. 'Resides off element'(2), indicates the persistence of the software is outside of the element. Typically for a element this software is part of the OperatingSystem is typically upgradeable. 'Owner Upgradeable' (3), indicates the persistence of the software is on the element and is upgradeable by the owner. 'FactoryUpgradeable' (4),indicates the persistence of the software is on the element and is upgradeable by the manufacturer. 'Not Upgradeable' (5), indicates the presistence of the software is on the element and is not upgradeable. (i.e. burned into a non replaceable ROM chip.012345..0x8000..0xFFFFUnknownOtherResides off deviceOwner UpgradeableFactory UpgradeableNot UpgradeableDMTF ReservedVendor ReservedCIM_ElementSoftwareIdentity.OtherUpgradeConditionDescribes the upgrade condition, when UpgradeCondition is set to 1 ("Other").CIM_ElementSoftwareIdentity.UpgradeCondition true2.8.0The InstalledSoftwareIdentity association identifies the System on which a SoftwareIdentity is installed. This class is a corollary to InstalledSoftwareElement, but deals with the asset aspects of software (as indicated by SoftwareIdentity), versus the deployment aspects (as indicated by SoftwareElement).trueThe system on which the software is installed.trueThe SoftwareIdentity that is installed. true2.8.0An 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.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.256trueAn address or other identifying information to uniquely name the LogicalDevice.64CIM_PowerManagementCapabilitiesBoolean 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.CIM_PowerManagementCapabilities.PowerCapabilitiesAn 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.01234567UnknownNot SupportedDisabledEnabledPower Saving Modes Entered AutomaticallyPower State SettablePower Cycling SupportedTimed Power On SupportedThe 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.123456789101112131415161718192021OtherUnknownRunning/Full PowerWarningIn TestNot ApplicablePower OffOff LineOff DutyDegradedNot InstalledInstall ErrorPower Save - UnknownPower Save - Low Power ModePower Save - StandbyPower CyclePower Save - WarningPausedNot ReadyNot ConfiguredQuiescedMIF.DMTF|Operational State|006.5MIB.IETF|HOST-RESOURCES-MIB.hrDeviceStatusMIF.DMTF|Host Device|001.5CIM_LogicalDevice.AdditionalAvailabilityCIM_EnabledLogicalElement.EnabledStateThe 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.12345OtherUnknownEnabledDisabledNot ApplicableMIF.DMTF|Operational State|006.4CIM_DeviceErrorData.LastErrorCodeLastErrorCode captures the last error code reported by the LogicalDevice.CIM_DeviceErrorData.ErrorDescriptionErrorDescription is a free-form string supplying more information about the error recorded in LastErrorCode, and information on any corrective actions that may be taken.CIM_ManagedSystemElement.OperationalStatusErrorCleared 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.256IndexedCIM_LogicalDevice.IdentifyingDescriptionsThe number of consecutive hours that this Device has been powered, since its last power cycle.HourstrueThe total number of hours that this Device has been powered.HourstrueAn 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.IndexedCIM_LogicalDevice.OtherIdentifyingInfoAdditional 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").123456789101112131415161718192021OtherUnknownRunning/Full PowerWarningIn TestNot ApplicablePower OffOff LineOff DutyDegradedNot InstalledInstall ErrorPower Save - UnknownPower Save - Low Power ModePower Save - StandbyPower CyclePower Save - WarningPausedNot ReadyNot ConfiguredQuiescedCIM_LogicalDevice.AvailabilityNo valueThe 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.MilliSecondsCIM_PowerManagementService.SetPowerStateSets the power state of the Device. The use of this method has been deprecated. Instead, use the SetPowerState method in the associated PowerManagementService class.trueThe power state to set.123456Full PowerPower Save - Low Power ModePower Save - StandbyPower Save - OtherPower CyclePower OfftrueTime 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.CIM_EnabledLogicalElement.RequestStateChangeThe 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.trueIf TRUE enable the device, if FALSE disable the device.CIM_EnabledLogicalElement.RequestStateChangeThe 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.trueIf TRUE, take the device online, if FALSE, take the device OFFLINE.CIM_EnabledLogicalElement.RequestStateChangeThe 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.trueIf 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. 2.6.0CIM_Realizes is the association that defines the mapping between LogicalDevices and the PhysicalElements that implement them.trueAntecedentThe physical component that implements the Device.trueDependentThe LogicalDevice.true true2.7.0LogicalDevices may be aggregated by a System. This relationship is made explicit by the SystemDevice association.truetrue11The parent system in the Association.GroupComponenttruetruetrueThe LogicalDevice that is a component of a System.PartComponenttrue 2.6.0An association between a Service and how it is implemented. The cardinality of this association is many-to-many. A Service may be provided by more than one Logical Device, operating in conjunction. And, any Device may provide more than one Service. When multiple Devices are associated with a single Service, it is assumed that these elements operate in conjunction to provide the Service. If different implementations of a Service exist, each of these implementations would result in individual instantiations of the Service object. These individual instantiations would then have associations to the unique implementations.trueAntecedentThe LogicalDevice.trueDependentThe Service implemented using the Logical Device.true 2.6.0An association between a ServiceAccessPoint and how it is implemented. The cardinality of this association is many-to-many. A SAP may be provided by more than one LogicalDevice, operating in conjunction. And, any Device may 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.trueAntecedentThe LogicalDevice.trueDependentThe ServiceAccessPoint implemented using the LogicalDevice.true 2.8.0StorageExtent describes the capabilities and management of the various media that exist to store data and allow data retrieval. This superclass could be used to represent the various components of RAID (Hardware or Software) or as a raw logical extent on top of physical media.Type of data organization used.01234OtherUnknownFixed BlockVariable BlockCount Key DataA free form string describing the media and/or its use.MIB.IETF|HOST-RESOURCES-MIB.hrStorageDescrAccess describes whether the media is readable (value=1), writeable (value=2), or both (value=3). "Unknown" (0) and "Write Once" (4) can also be defined.01234UnknownReadableWriteableRead/Write SupportedWrite OnceErrorMethodology is a free-form string describing the type of error detection and correction supported by this StorageExtent.Size in bytes of the blocks which form this StorageExtent. If variable block size, then the maximum block size in bytes should be specified. If the block size is unknown or if a block concept is not valid (for example, for AggregateExtents, Memory or LogicalDisks), enter a 1.BytesMIF.DMTF|Host Storage|001.4MIB.IETF|HOST-RESOURCES-MIB.hrStorageAllocationUnitsMIF.DMTF|Storage Devices|001.5Total number of logically contiguous blocks, of size Block Size, which form this Extent. The total size of the Extent can be calculated by multiplying BlockSize by NumberOfBlocks. If the BlockSize is 1, this property is the total size of the Extent.MIF.DMTF|Host Storage|001.5MIB.IETF|HOST-RESOURCES-MIB.hrStorageSizeThe maximum number of blocks, of size BlockSize, which are available for consumption when layering StorageExtents using the BasedOn association. This property only has meaning when this StorageExtent is an Antecedent reference in a BasedOn relationship. For example, a StorageExtent could be composed of 120 blocks. However, the Extent itself may use 20 blocks for redundancy data. If another StorageExtent is BasedOn this Extent, only 100 blocks would be available to it. This information ('100 blocks is available for consumption') is indicated in the ConsumableBlocks property.True indicates that the underlying StorageExtent(s) participate in a StorageRedundancyGroup.Boolean set to TRUE if the Storage is sequentially accessed by a MediaAccessDevice. A TapePartition is an example of a sequentially accessed StorageExtent. StorageVolumes, Disk Partitions and LogicalDisks represent randomly accessed Extents.StorageExtents have additional status information beyond that captured in the OperationalStatus and other properties, inherited from ManagedSystemElement. This additional information (for example, "Protection Disabled", value=9) is captured in the VolumeStatus property.0123456789101112131415..3276732768..65535OtherUnknownNone/Not ApplicableBrokenData LostDynamic ReconfigExposedFractionally ExposedPartially ExposedProtection DisabledReadyingRebuildRecalculateSpare in UseVerify In ProgressDMTF ReservedVendor ReservedIndicates whether or not there exists no single point of failure.CIM_StorageSetting.NoSinglePointOfFailureNumber of complete copies of data currently maintained.CIM_StorageSetting.DataRedundancyGoalCIM_StorageSetting.DataRedundancyMaxCIM_StorageSetting.DataRedundancyMinHow many physical packages can currently fail without data loss. For example, in the storage domain, this might be disk spindles.CIM_StorageSetting.PackageRedundancyGoalCIM_StorageSetting.PackageRedundancyMaxCIM_StorageSetting.PackageRedundancyMinCurrent value for Delta reservation. This is a percentage that specifies the amount of space that should be reserved in a replica for caching changes.Percentage1100CIM_StorageSetting.DeltaReservationGoalCIM_StorageSetting.DeltaReservationMaxCIM_StorageSetting.DeltaReservationMinIf true, "Primordial" indicates that the containing System does not have the ability to create or delete this operational element. This is important because StorageExtents are assembled into higher-level abstractions using the BasedOn association. Although the higher-level abstractions can be created and deleted, the most basic, (i.e. primordial), hardware-based storage entities cannot. They are physically realized as part of the System, or are actually managed by some other System and imported as if they were physically realized. In other words, a Primordial StorageExtent exists in, but is not created by its System and conversely a non-Primordial StorageExtent is created in the context of its System. For StorageVolumes, this property will generally be false. One use of this property is to enable algorithms that aggregate StorageExtent.ConsumableSpace across all, StorageExtents but that also want to distinquish the space that underlies Primordial StoragePools. Since implementations are not required to surface all Component StorageExtents of a StoragePool, this information is not accessible in any other way.false 2.6.0BasedOn is an association describing how StorageExtents can be assembled from lower level Extents. For example, ProtectedSpaceExtents are parts of PhysicalExtents, while VolumeSets are assembled from one or more Physical or ProtectedSpaceExtents. As another example, CacheMemory can be defined independently and realized in a PhysicalElement or can be 'based on' Volatile or NonVolatileStorageExtents.trueAntecedentThe lower level StorageExtent.trueDependentThe higher level StorageExtent.trueStartingAddress indicates where in lower level storage, the higher level Extent begins.EndingAddress indicates where in lower level storage, the higher level Extent ends. This property is useful when mapping non-contiguous Extents into a higher level grouping.If there is an order to the BasedOn associations that describe how a higher level StorageExtent is assembled, the OrderIndex property indicates this. When an order exists, the instances of BasedOn with the same Dependent value (i.e., the same higher level Extent) should place unique values in the OrderIndex property. The lowest value implies the first member of the collection of lower level Extents, and increasing values imply successive members of the collection. If there is no ordered relationship, a value of zero should be specified. An example of the use of this property is to define a RAID-0 striped array of 3 disks. The resultant RAID array is a StorageExtent that is dependent on (BasedOn) the StorageExtents that describe each of the 3 disks. The OrderIndex of each BasedOn association from the disk Extents to the RAID array could be specified as 1, 2 and 3 to indicate the order in which the disk Extents are used to access the RAID data. true2.6.0Collection is an abstract class that provides a common superclass for data elements that represent collections of ManagedElements and its subclasses. truetrue2.6.0CIM_MemberOfCollection is an aggregation used to establish membership of ManagedElements in a Collection.truetrueThe Collection that aggregates members.trueThe aggregated member of the Collection. 2.7.0CIM_OrderedMemberOfCollection is an aggregation used to establish an ordered membership of ManagedElements in a Collection.truetrueAssignedSequence is an unsigned integer 'n' that indicates the relative position of members within a Collection. When 'n' is a positive integer, it indicates a place in the sequence of members, with smaller integers indicating earlier positions in the sequence. The special value '0' indicates 'don't care'. If two or more members have the same non-zero sequence number, then the ordering between those members is irrelavent, but they must all be ordered at the appropriate place in the overall sequence. A series of examples will make ordering of members clearer: If all members have the same sequence number, regardless of whether it is '0' or non-zero, any order is acceptable. o The values: 1:MEMBER A 2:MEMBER B 1:MEMBER C 3:MEMBER D indicate two acceptable orders: A,C,B,D or C,A,B,D, since A and C can be ordered in either sequence, but only at the '1' position. Note that the non-zero sequence numbers need not start with '1', and they need not be consecutive. All that matters is their relative magnitude. 2.7.0SystemSpecificCollection represents the general concept of a collection which is scoped (or contained) by a System. It represents a Collection that only has meaning in the context of a System, and/or whose elements are restricted by the definition of the System. This is explicitly described by the (required) association, HostedCollection. An example of a SystemSpecificCollection is a Fibre Channel zone that collects network ports, port groupings and aliases (as required by a customer) in the context of an AdminDomain. The Collection is not a part of the domain, but merely an arbitrary grouping of the devices and other Collections in the domain. In other words, the context of the Collection is restricted to the domain, and its members are also limited by the domain.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'. 2.8.0A concrete version of Collection. This class represents a generic and instantiable collection, such as a group of ComputerSystems (e.g., a pool of hosts available for executing Jobs). It is defined as a concrete subclass of the abstract CIM_Collection class, to be used in place of many specific subclasses that add no semantics. Note that when defining additional semantics for Collection that this class MUST NOT be subclassed. Specific semantics continue to be defined as subclasses of the abstract CIM_Collection. ConcreteCollection is limited in its use as a concrete form of a general collection or bag. It was deemed more prudent to create this concrete subclass than to change Collection from an abstract to a concrete class.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. 2.7.0HostedCollection defines a SystemSpecificCollection in the context of a scoping System. It represents a Collection that only has meaning in the context of a System, and/or whose elements are restricted by the definition of the System.true11The scoping system.AntecedenttrueThe collection defined in the context of a system.Dependenttrue true2.6.0The CollectionOfMSEs object allows the grouping of Managed SystemElements for various identification purposes and to reduce the complexity of associating Settings and Configurations. It is abstract to require further definition and semantic refinement in subclasses. The CollectionOfMSEs object does not carry any state or status information, but only represents a grouping or 'bag' of Elements. For this reason, it is incorrect to subclass groups that have state/ status from CollectionOfMSEs - an example is CIM_Redundancy Group (which is subclassed from LogicalElement). Collections typically aggregate 'like'objects, but are not required to do so. They simply identify 'bags' and may represent an optimization. This is especially true with respect to their association to Settings and Configurations. Without Collections, one is forced to define individual ElementSetting andElementConfiguration associations, to tie Settings and Configuration objects to individual ManagedSystemElements. There may be much duplication in assigning the same Setting to multiple objects. In addition, using the Collection object allows the determination that the Setting and Configuration associations are indeed the same for the Collection's members. This information would otherwise be obtained by defining the Collection in a proprietary manner, and then querying the ElementSetting and ElementConfiguration associations to determine ifthe Collection set is completely covered.The identification of the Collection object. When subclassed, the CollectionID property can be overridden to be a Key property.256 truetrue2.6.0CIM_CollectedCollections is an aggregation association representing that a CollectionOfMSEs may itself be contained in a CollectionOfMSEs.truetrueThe 'higher level' or parent element in the aggregation.trueThe 'collected' Collection. 2.6.0CIM_CollectedMSEs is a generic association used to establish the members of the grouping object, CollectionOf MSEs.truetrueCollectionThe grouping or 'bag' object that represents the Collection.truetrueMemberThe members of the Collection.true 2.8.0A class derived from LogicalElement that is a special collection of ManagedSystemElements. This collection indicates that the aggregated components together provide redundancy. All elements aggregated in a RedundancyGroup should be instantiations of the same object class.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 RedundancyGroup Name serves as the key for the Group's instance in an enterprise environment.256RedundancyStatus provides information on the state of the RedundancyGroup. "Fully Redundant" (value=2) means that all of the configured redundancy is still available; "Degraded Redundancy" (3) means that some failures have been experienced but some reduced amount of redundancy is still available; "Redundancy Lost" (4) means that a sufficient number of failures have been experienced such that no redundancy is available and the next failure experienced will cause overall failure. Also, the values, "Other" (1) and "Unknown" (0), are defined.01234UnknownOtherFully RedundantDegraded RedundancyRedundancy Lost 2.7.1A RedundancyGroup aggregates Managed System Elements and indicates that these elements, taken together, provide redundancy. All elements aggregated in a RedundancyGroup should be instantiations of the same object class.truetrueGroupComponentThe RedundancyComponent association indicates that 'this set of fans' or 'these physical extents' participate in a single RedundancyGroup.truetruePartComponentThe component of the redundancy group.true 2.6.0A class derived from RedundancyGroup indicating that one or more of the aggregated elements can be spared. (The actual Spares are defined using the ActsAsSpare association.) An example is the use of redundant NICs in a ComputerSystem - where one NIC is primary and the other is Spare. The 'primary' NIC would be a member of the SpareGroup (associated using the RedundancyComponent class) and the 'other' NIC would be associated using the ActsAsSpare relationship.This method is forces a failover from one ManagedSystem Element to another. There are two parameters to the Failover method, FailoverFrom and FailoverTo. The FailoverFrom parameter is a reference to the primary ManagedSystemElement that will become inactive after the method. This Element should be associated with the SpareGroup through the RedundancyComponent relationship. The FailoverTo parameter is a reference to the ManagedSystemElement that will take over for the primary. This Element should be associated with the SpareGroup through the ActsAsSpare association. Once the failover has occurred, the SpareGroup and the Redundancy Component and ActsAsSpare associations will be updated with current status. For example, the ActsAsSpare association that contained the FailoverTo Element will be deleted and a new RedundancyComponent association instantiated in its place. 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.trueThe primary ManagedSystemElement that will become inactive after the method.trueThe ManagedSystemElement that will take over from the primary MSE. true2.6.0The ActsAsSpare association indicates which elements can spare or replace the other aggregated elements. The fact that a spare can operate in "hot standby" mode is specified on an element by element basis.trueThe SpareGroup.trueA ManagedSystemElement acting as a spare and participating in the SpareGroup.HotStandby is a boolean indicating that the spare is operating as a hot standby. 2.7.0A class derived from RedundancyGroup containing mass storage-related redundancy information. StorageRedundancy Groups are used to protect user data. They act on one or more underlying StorageExtents, associated via ExtentRedundancyComponent and produce one or more protected StorageExtents that are associated to the underlying StorageExtents via ProtectedExtentBasedOn or CompositeExtentBasedOn. StorageRedundancyGroups may overlap. However, the underlying StorageExtents within the overlap should not contain any check data.The TypeOfAlgorithm specifies the algorithm used for data redundancy and reconstruction. For example, "P+Q" (value =5) or "P+S" (7) may be specified. The value of 0, is defined as "None" to indicate that data redundancy is not active. An inactive redundancy should only be instantiated if data striping or concatenation are active. These are indicated by the IsStriped or IsConcatentated boolean properties of this RedundancyGroup.01234567NoneOtherUnknownCopyXORP+QSP+SMIF.DMTF|Redundancy Group|001.2StorageRedundancy provides additional information on the state of the RedundancyGroup, beyond the RedundancyStatus property. Information like "Reconfig In Progress" (value =1) or "Redundancy Disabled" can be specified using this property.012345678No Additional StatusReconfig In ProgressData LostNot Currently ConfiguredProtected RebuildRedundancy DisabledUnprotected RebuildRecalculatingVerifyingTrue indicates that the data is striped across the various StorageExtents in the Group.True indicates that the data is concatenated across the various StorageExtents in the Group. 2.6.0A class derived from RedundancyGroup indicating that the aggregated elements have more capacity or capability than is needed. An example of this type of redundancy is the installation of N+1 power supplies or fans in a system.MinNumberNeeded indicates the smallest number of elements that must be operational in order to have redundancy. For example, in an N+1 redundancy relationship, the MinNumberNeeded property should be set equal to N.Boolean indicating whether load balancing is supported by the ExtraCapacityGroup. 2.6.0Describes the StorageExtents participating in a Storage RedundancyGroup.truetrueThe StorageRedundancyGroup.GroupComponenttruetrueThe StorageExtent participating in the RedundancyGroup.PartComponenttrue 2.7.0CIM_Product is a concrete class that aggregates PhysicalElements, software (SoftwareIdentity and SoftwareFeatures), Services and/or other Products, and is acquired as a unit. Acquisition implies an agreement between supplier and consumer which may have implications to Product licensing, support and warranty. Non-commercial (e.g., in-house developed Products) should also be identified as an instance of CIM_Product. Note that software is handled a bit differently in the list of aggregated entities, above. This is because software can be viewed as a tangible asset (similar to PhysicalElements) AND/ OR as a set of features that make up a Product and are deployed. These are two different concepts, usually managed by different units in a business' organization. When software 'features' are described, the CIM_SoftwareFeature class from the Application Model is instantiated (where Features are Weak to/scoped by a Product). When a specific piece of software is acquired and perhaps warrantied as part of a Product, this is addressed by the class, SoftwareIdentity.trueCommonly used Product name.256MIF.DMTF|ComponentID|001.2PRS_Product.ProductNametrueProduct identification such as a serial number on software, a die number on a hardware chip, or (for non-commercial Products) a project number.64MIF.DMTF|ComponentID|001.4trueThe name of the Product's supplier, or entity selling the Product (the manufacturer, reseller, OEM, etc.). Corresponds to the Vendor property in the Product object in the DMTF Solution Exchange Standard.256MIF.DMTF|ComponentID|001.1PRS_Product.VendortrueProduct version information.64MIF.DMTF|ComponentID|001.3PRS_Product.VersionProduct SKU (stock keeping unit) information.64If this Product is under warranty, the start date of the warranty.MIF.DMTF|FRU|002.9CIM_Product.WarrantyDurationIf this Product is under warranty, the duration of the warranty in days.DaysMIF.DMTF|FRU|002.10CIM_Product.WarrantyStartDate true2.7.0The CIM_ProductComponent association defines a containment and component relationship among Products. For example, a Product may come bundled with other Products. Note that this association duplicates ProductParentChild. The latter association is maintained for legacy reasons. This association, ProductComponent, is added for ease of query and modeling consistency. Using ProductComponent, an application can query for all Component relationships for a Product, versus querying the various Component relationships AND ProductParentChild.truetrueGroupComponentThe Product which contains another Product as a component. The cardinality of this reference takes the default values (no minimum or maximum) since an instance of Product can describe either a general product type, or a specific item that is acquired. In the case of a specific item, a cardinality of Max(1) is indicated. However, when dealing with the general description/templating of a Product, then it may be a component of several others and a cardinality of Max(1) would be invalid.PRS_ProductComponent.AntecedenttruetruePartComponentThe contained Product.PRS_ProductComponent.Dependenttrue truetruetrue2.7.0The CIM_ProductParentChild association defines a parent child hierarchy among Products. For example, a Product may come bundled with other Products.truetrueThe parent Product in the association.trueThe child Product in the association. true2.6.0CIM_CompatibleProduct is an association between Products that can indicate a wide variety of information. For example, it can indicate that the two referenced Products interoperate, that they can be installed together, that one can be the physical container for the other, etc. The string property, CompatibilityDescription, defines how the Products interoperate or are compatible, any limitations regarding interoperability or installation, ...trueThe Product for which compatible offerings are defined.trueThe compatible Product.CompatibilityDescription is a free-form string defining how the two referenced Products interoperate or are compatible, any limitations to compatibility, etc. true2.6.0CIM_ProductProductDependency is an association between two Products, indicating that one must be installed, or must be absent, for the other to function. This is conceptually equivalent to the ServiceServiceDependency association.trueThe required Product.trueThe Product that is dependent on another Product.The nature of the Product dependency. This property describes that the associated Product must be installed (value=2) or must be absent (value=3) in order for the Product to function.0123UnknownOtherProduct Must Be InstalledProduct Must Not Be Installed 2.6.0The CIM_SupportAccess association defines how to obtain assistance for a Product.trueSupportAccessID is an arbitrary, free form string defined by the Product Vendor or by the organization that deploys the Product. This property, since it is a key, should be unique throughout the enterprise.256DescriptionA textual description of the type of Support provided.MIF.DMTF|Support|001.3CommunicationInfo provides the details of the Communication Mode. For example, if the CommunicationMode is 'Phone', CommunicationInfo specifies the phone number to be called.MIF.DMTF|FRU|002.11MIF.DMTF|FRU|002.12CommunicationMode defines the form of communication in order to obtain support. For example, phone communication (value =2), fax (3) or email (8) can be specified.12345678OtherPhoneFaxBBSOnline ServiceWeb PageFTPE-mailMIF.DMTF|Support|001.5Locale defines the geographic region and/or language dialect to which this Support resource pertains.64MIF.DMTF|Support|001.2 true2.6.0CIM_ProductSupport is an association between Product and SupportAccess that conveys how support is obtained for the Product. This is a many-to-many relationship, implying that various types of Support are available for a Product, and that the same Support object can provide assistance for multiple Products.trueThe Product.trueSupport for the Product. 2.6.0The CIM_FRU class is a vendor-defined collection of Products and/or PhysicalElements that is associated with a Product for the purpose of supporting, maintaining or upgrading that Product at the customer's location. FRU is an acronym for 'field replaceable unit'.trueFRU ordering information.64MIF.DMTF|FRU|002.6trueFRU identification such as a serial number on software or a die number on a hardware chip.64MIF.DMTF|FRU|002.7trueThe name of the FRU's supplier.256MIF.DMTF|FRU|002.4DescriptionA textual description of the FRU.MIF.DMTF|FRU|002.3FRU name.256The FRU's revision level.64MIF.DMTF|FRU|002.8Indicates whether the FRU is customer replaceable. true2.6.0CIM_ProductFRU is an association between Product and FRU that provides information regarding what Product components have been or are being replaced. The association is one to many, conveying that a Product can have many FRUs, and that a particular instance of a FRU is only applied to one (instance of a) Product.true1The Product to which the FRU is applied.trueThe FRU. true2.6.0ReplaceableProductFRU is an association between Product and FRU that shows what Product components may be replaced. The association is one to many, conveying that a Product can have many FRUs, and that a particular instance of a FRU is only applied to one (instance of a) Product.true1The Product to which the FRU is applied.trueThe FRU. true2.7.0Indicates that the referenced PhysicalElement is acquired as part of a Product.truetrueGroupComponent1The Product.truetruePartComponentThe PhysicalElement which is a part of the Product.true true2.7.0Indicates that the referenced SoftwareIdentity is acquired as part of a Product.truetrueGroupComponent1The Product.truetruePartComponentThe software which is a part of the Product.true true2.7.0Indicates that the referenced Service is acquired as part of a Product. Examples of Services that may be acquired are outsourced storage and networking services, or support and warranty services. Expanding on the examples, Services represent generic functionality - so, it is possible to model the existence of storage volume management or warranty services as individual instances of subclasses of CIM_Service. These 'Services' may be enabled/disabled, started/stopped, signal an error, etc. (They behave as standard ManagedSystemElements.) Specific requests against the Services - for example, a request for warranty service or increased storage space - are NOT new instances of Service, but may be requested via the methods of the Service subclass, or be instantiated as specific subclasses of ManagedElement.truetrueGroupComponent1The Product.truetruePartComponentThe Service which is a part of the Product.true trueCIM_ProductPhysicalComponenttruetrue2.7.0Indicates the PhysicalElement(s) that make up a Product. This association is deprecated in order to correctly place it in the inheritance hierarchy and align the definition with other new classes that are being added to the model, such as CIM_ProductServiceComponent. ProductPhysicalElements was defined in the original CIM V2.0 release, when a Managed Element and a Component relationship between ManagedElements did not exist.CIM_ProductPhysicalComponent.GroupComponenttruetrue1The Product.CIM_ProductPhysicalComponent.PartComponenttrueThe PhysicalElement which is a part of the Product. truetruetrue2.7.0Indicates the PhysicalElements that make up a FRU.truetrue1The FRU.trueThe PhysicalElement which is a part of the FRU. truetruetrue2.7.0Indicates that a FRU may be composed of other Product(s).truetrue1The FRU.trueThe Product which is a part of the FRU. true2.7.0Capabilities is an abstract class whose subclasses describe abilities and/or potential for use. For example, one may describe the maximum number of VLANs that can be supported on a system using a subclass of Capabilities. Capabilities are tied to the elements which they describe using the ElementCapabilities association. Note that the cardinality of the ManagedElement reference is Min(1), Max(1). This cardinality mandates the instantiation of the ElementCapabilities association for the referenced instance of Capabilities. ElementCapabilities describes the existence requirements and context for the referenced instance of ManagedElement. Specifically, the ManagedElement MUST exist and provides the context for the Capabilities. Note that Capabilities do not indicate what IS configured or operational, but what CAN or CANNOT exist, be defined or be used. Note that it is possible to describe both supported and excluded abilities and functions (both capabilities and limitations) using this class.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'.trueElementNameThe user friendly name for this instance of Capabilities. In addition, the user friendly name can be used as a index property for a search of query. (Note: Name does not have to be unique within a namespace.) true2.7.0ElementCapabilities represents the association between ManagedElements and their Capabilities. Note that the cardinality of the ManagedElement reference is Min(1), Max(1). This cardinality mandates the instantiation of the ElementCapabilities association for the referenced instance of Capabilities. ElementCapabilities describes the existence requirements and context for the referenced instance of ManagedElement. Specifically, the ManagedElement MUST exist and provides the context for the Capabilities.true11The managed element.trueThe Capabilities object associated with the element. true2.7.0The SettingData class represents configuration-related and operational parameters for one or more ManagedElement(s). A ManagedElement may have multiple SettingData objects associated with it. The current operational values for an Element's parameters are reflected by properties in the Element itself or by properties in its associations. These properties do not have to be the same values present in the SettingData object. For example, a modem may have a SettingData baud rate of 56Kb/sec but be operating at 19.2Kb/sec. Note that the CIM_SettingData class is very similar to CIM_Setting, yet both classes are present in the model. This is 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.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'.trueElementNameThe user friendly name for this instance of SettingData. In addition, the user friendly name can be used as a index property for a search of query. (Note: Name does not have to be unique within a namespace.) true2.7.0The ScopedSettingData class represents the general concept of SettingData which is scoped/contained by a ManagedElement (i.e. settings that are specifically defined for a system, device, etc). ScopedSettingData is tied to a ManagedElement using the ScopedSetting association. Note that the cardinality of the ManagedElement reference is Min(1), Max(1). This cardinality mandates the instantiation of the ScopedSetting association for the referenced instance of ScopedSettingData. ScopedSetting describes the existence requirements and context for the referenced instance of ManagedElement. Specifically, the ManagedElement MUST exist and provides the context for the ScopedSettingData. 2.8.0ScopedSetting defines a setting in the context of the Managed Element which it resides.true11The scoping ManagedElement.AntecedenttrueThe setting defined for the ManagedElement.Dependenttrue true2.7.0ElementSettingData represents the association between ManagedElements and applicable setting data. This association also describes whether this is a default or current setting.trueThe managed element.trueThe SettingData object associated with the element.An enumerated integer indicating that the referenced setting is a default setting for the element, or that this information is unknown.012UnknownIs DefaultIs Not DefaultAn enumerated integer indicating that the referenced setting is currently being used in the operation of the element, or that this information is unknown.012UnknownIs CurrentIs Not Current 2.7.0Profile specifies a general collection of Settings/SettingData that are logically grouped together. Note that the CIM_Profile class uses simplified naming/identity and collection algorithms, as compared to CIM_Configuration. The settings are 'collected' into the Profile using the MemberOfCollection association. Note that a Profile obtains its setting data and other necessary information from collected Setting/SettingData instances, and by the definition of additional properties in subclasses. One example of a Profile is to define the collection of settings for a particular person. Another is to define the collection of settings appropriate when initializing a system. Profile is tied to a ManagedElement using the ElementProfile association. The ManagedElement provides context for the Profile, and the settings collected by Profile SHOULD be settings of the associated ManagedElement. Note that a ManagedElement MAY NOT exist when the Profile is instantiated. This is true when the Profile is used in the creation of the real world entity represented by (and then instantiated in) the ManagedElement.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'. true2.7.0ElementProfile represents the association between ManagedElements and the Profiles (collection of settings) defined for them. This association describes that the settings collected by the Profile apply to the associated ManagedElement.trueThe managed element.trueThe Profile object associated with the element. true2.7.0The Setting class represents configuration-related and operational parameters for one or more ManagedSystemElement(s). An Element may have multiple Setting objects associated with it. The current operational values for an Element's parameters are reflected by properties in the Element itself or by properties in its associations. These properties do not have to be the same values present in the Setting object. For example, a modem may have a Setting baud rate of 56Kb/sec but be operating at 19.2Kb/sec. Note that the CIM_SettingData class is very similar to CIM_Setting, yet both classes are present in the model. This is 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.The identifier by which the Setting object is known.256The VerifyOKToApplyToMSE method is used to verify that this Setting can be 'applied' to the referenced Managed SystemElement, at the given time or time interval. This method takes three input parameters: MSE (the Managed SystemElement that is being verified), TimeToApply (which, being a datetime, can be either a specific time or a time interval), and MustBeCompletedBy (which indicates the required completion time for the method). The return value should be 0 if it is OK to apply the Setting, 1 if the method is not supported, 2 if the Setting cannot be applied within the specified times, and any other number 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.trueThe Managed SystemElement that is being verified.trueTimeToApply can be either a specific time or a time interval.trueThe required completion time for the method.The ApplyToMSE method performs the actual application of the Setting to the referenced ManagedSystemElement. It takes three input parameters: MSE (the ManagedSystem Element to which the Setting is being applied), TimeToApply (which, being a datetime, can be either a specific time or a time interval), and MustBeCompletedBy (which indicates the required completion time for the method). Note that the semantics of this method are that individual Settings are either wholly applied or not applied at all to their target ManagedSystemElement. The return value should be 0 if the Setting is successfully applied to the referenced ManagedSystemElement, 1 if the method is not supported, 2 if the Setting was not applied within the specified times, and any other number 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. Note: If an error occurs in applying the Setting to a ManagedSystemElement, the Element must be configured as when the 'Apply' attempt began. That is, the Element should NOT be left in an indeterminate state.trueThe ManagedSystem Element to which the Setting is being applied.trueTimeToApply can be either a specific time or a time interval.trueThe required completion time for the method.The VerifyOKToApplyToCollection method is used to verify that this Setting can be 'applied' to the referenced Collection of ManagedSystemElements, at the given time or time interval, without causing adverse effects to either the Collection itself or its surrounding environment. The net effect is to execute the VerifyOKToApply method against each of the Elements aggregated by the Collection. This method takes three input parameters: Collection (the Collection of Managed SystemElements that is being verified), TimeToApply (which, being a datetime, can be either a specific time or a time interval), and MustBeCompletedBy (which indicates the required completion time for the method). The return value should be 0 if it is OK to apply the Setting, 1 if the method is not supported, 2 if the Setting cannot be applied within the specified times, and any other number if an error occurred. One output parameter is defined - CanNotApply - which is a string array that lists the keys of the ManagedSystemElements to which the Setting can NOT be applied. This enables those Elements to be revisited and either fixed, or other corrective action taken. 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.trueThe Collection of Managed SystemElements that is being verified.trueTimeToApply can be either a specific time or a time interval.trueThe required completion time for the method.falsetrueA string array that lists the keys of the ManagedSystemElements to which the Setting can NOT be applied.The ApplyToCollection method performs the application of the Setting to the referenced Collection of ManagedSystem Elements. The net effect is to execute the ApplyToMSE method against each of the Elements aggregated by the Collection. If the input value ContinueOnError is FALSE, this method applies the Setting to all Elements in the Collection until it encounters an error, in which case it stops execution, logs the key of the Element that caused the error in the CanNotApply array, and issues a return code of 2. If the input value ContinueOnError is TRUE, then this method applies the Setting to all the ManagedSystemElements in the Collection, and reports the failed Elements in the array, CanNotApply. For the latter, processing will continue until the method is applied to all Elements in the Collection, regardless of any errors encountered. The key of each ManagedSystemElement to which the Setting could not be applied is logged into the CanNotApply array. This method takes four input parameters: Collection (the Collection of Elements to which the Setting is being applied), TimeToApply (which, being a datetime, can be either a specific time or a time interval), ContinueOnError (TRUE means to continue processing on encountering an error), and MustBeCompletedBy (which indicates the required completion time for the method). The return value should be 0 if the Setting is successfully applied to the referenced Collection, 1 if the method is not supported, 2 if the Setting was not applied within the specified times, 3 if the Setting cannot be applied using the input value for ContinueOnError, and any other number if an error occurred. One output parameter is defined, CanNotApplystring, which is an array that lists the keys of the ManagedSystemElements to which the Setting was NOT able to be applied. This output parameter has meaning only when the ContinueOnError parameter is TRUE. 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: if an error occurs in applying the Setting to a ManagedSystemElement in the Collection, the Element must be configured as when the 'Apply' attempt began. That is, the Element should NOT be left in an indeterminate state.trueThe Collection of Managed SystemElements to be applied.trueTimeToApply can be either a specific time or a time interval.trueTRUE means to continue processing on encountering an error.trueThe required completion time for the method.falsetrueA string array that lists the keys of the ManagedSystemElements to which the Setting was NOT be applied.The VerifyOKToApplyIncrementalChangeToMSE method is used to verify that a subset of the properties in this Setting can be 'applied' to the referenced Managed SystemElement, at the given time or time interval. This method takes four input parameters: MSE (the Managed SystemElement that is being verified), TimeToApply (which, being a datetime, can be either a specific time or a time interval), MustBeCompletedBy (which indicates the required completion time for the method), and a PropertiesToApply array (which contains a list of the property names whose values will be verified.) If the array is null, empty or contains the string "ALL" as a property name, then all Settings properties shall be verified. If it is set to "NONE", then no Settings properties will be verified. The return value should be 0 if it is OK to apply the Setting, 1 if the method is not supported, 2 if the Setting cannot be applied within the specified times, and any other number 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.trueThe ManagedSystem Element for which the Setting is being verified.trueTimeToApply can be either a specific time or a time interval.trueThe required completion time for the method.trueA list of the property names whose values will be verified.The ApplyIncrementalChangeToMSE method performs the actual application of a subset of the properties in the Setting to the referenced ManagedSystemElement. It takes four input parameters: MSE (the ManagedSystem Element to which the Setting is being applied), TimeToApply (which, being a datetime, can be either a specific time or a time interval), MustBeCompletedBy (which indicates the required completion time for the method), and a PropertiesToApply array (which contains a list of the property names whose values will be applied.) If a property is not in this list, it will be ignored by the Apply. If the array is null, empty or contains the string "ALL" as a property name, then all Settings properties shall be applied. If it is set to "NONE", then no Settings properties will be applied. Note that the semantics of this method are that individual Settings are either wholly applied or not applied at all to their target ManagedSystemElement. The return value should be 0 if the Setting is successfully applied to the referenced ManagedSystemElement, 1 if the method is not supported, 2 if the Setting was not applied within the specified times, and any other number 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. Note: If an error occurs in applying the Setting to a ManagedSystemElement, the Element must be configured as when the 'Apply' attempt began. That is, the Element should NOT be left in an indeterminate state.trueThe ManagedSystem Element to which the Setting is being applied.trueTimeToApply can be either a specific time or a time interval.trueThe required completion time for the method.trueA list of the property names whose values will be applied.The VerifyOKToApplyIncrementalChangeToCollection method is used to verify that a subset of the properties in this Setting can be 'applied' to the referenced Collection of ManagedSystemElements, at the given time or time interval, without causing adverse effects to either the Collection itself or its surrounding environment. The net effect is to execute the VerifyOKToApplyIncrementalChangeToMSE method against each of the Elements aggregated by the Collection. This method takes three input parameters: Collection (the Collection of Managed SystemElements that is being verified), TimeToApply (which, being a datetime, can be either a specific time or a time interval), MustBeCompletedBy (which indicates the required completion time for the method), and a PropertiesToApply array (which contains a list of the property names whose values will be verified. If they array is null or empty or constains the string "all" as a property name then all Settings properties shall be verified. If it is set to "none" then no Settings properties will be verified). The return value should be 0 if it is OK to apply the Setting, 1 if the method is not supported, 2 if the Setting cannot be applied within the specified times, and any other number if an error occurred. One output parameter is defined - CanNotApply - which is a string array that lists the keys of the ManagedSystemElements to which the Setting can NOT be applied. This enables those Elements to be revisited and either fixed, or other corrective action taken. 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.trueThe Collection of Managed SystemElements for which the setting is being verified.trueTimeToApply can be either a specific time or a time interval.trueThe required completion time for the method.trueA list of the property names whose values will be verified.falsetrueA string array that lists the keys of the ManagedSystemElements to which the Setting can NOT be applied.The ApplyIncrementalChangeToCollection method performs the application of a subset of the properties in this Setting to the referenced Collection of ManagedSystem Elements. The net effect is to execute the ApplyIncrementalChangeToMSE method against each of the Elements aggregated by the Collection. If the input value ContinueOnError is FALSE, this method applies the Setting to all Elements in the Collection until it encounters an error, in which case it stops execution, logs the key of the Element that caused the error in the CanNotApply array, and issues a return code of 2. If the input value ContinueOnError is TRUE, then this method applies the Setting to all the ManagedSystemElements in the Collection, and reports the failed Elements in the array, CanNotApply. For the latter, processing will continue until the method is applied to all Elements in the Collection, regardless of any errors encountered. The key of each ManagedSystemElement to which the Setting could not be applied is logged into the CanNotApply array. This method takes four input parameters: Collection (the Collection of Elements to which the Setting is being applied), TimeToApply (which, being a datetime, can be either a specific time or a time interval), ContinueOnError (TRUE means to continue processing on encountering an error), and MustBeCompletedBy (which indicates the required completion time for the method), and a PropertiesToApply array (which contains a list of the property names whose values will be applied.) If a property is not in this list, it will be ignored by the Apply. If the array is null or empty or contains the string "ALL" as a property name, then all Settings properties shall be applied. If it is set to "NONE", then no Settings properties will be applied. The return value should be 0 if the Setting is successfully applied to the referenced Collection, 1 if the method is not supported, 2 if the Setting was not applied within the specified time, 3 if the Setting cannot be applied using the input value for ContinueOnError, and any other number if an error occurred. One output parameter is defined, CanNotApplystring, which is an array that lists the keys of the ManagedSystemElements to which the Setting was NOT able to be applied. This output parameter has meaning only when the ContinueOnError parameter is TRUE. 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: if an error occurs in applying the Setting to a ManagedSystemElement in the Collection, the Element must be configured as when the 'Apply' attempt began. That is, the Element should NOT be left in an indeterminate state.trueThe Collection of Elements to which the Setting is being applied.trueA specific time or a time interval.trueTRUE means to continue processing on encountering an error.trueThis parameter indicates the required completion time for the method.trueA list of the property names whose values will be verified.falsetrueA string array that lists the keys of the ManagedSystemElements to which the Setting can NOT be applied. true2.6.0ElementSetting represents the association between Managed SystemElements and the Setting class(es) defined for them.trueThe ManagedSystemElement.trueThe Setting object associated with the ManagedSystem Element. 2.6.0DefaultSetting represents the association between a Managed SystemElement and the single Setting class that is defined to be the default setting for this Element.trueSetting1The Setting object which is the default.true true2.6.0CIM_SystemSetting represents the general concept of a CIM_Setting which is scoped by/weak to a System.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.256trueSettingID256The identifier by which the Setting object is known. 2.8.0CIM_SettingForSystem defines a Setting in the context of the System on which it resides.true11The hosting System.AntecedenttruetrueThe Setting defined for the System.Dependenttrue 2.6.0The Configuration object allows the grouping of sets of parameters (defined in Setting objects) and dependencies for one or more ManagedSystemElements. It represents a certain behavior, or a desired functional state for the ManagedSystem Elements. Note that the CIM_Profile class uses simplified naming/identity and collection algorithms as compared to CIM_Configuration. The desired functional state of the Configuration is typically driven by external requirements such as time or location. For example, to connect to a Mail System from 'home', a dependency on a modem exists, but a dependency on a network adapter exists at 'work'. Settings for the pertinent LogicalDevices (in this example, POTSModem and NetworkAdapter) can be defined and aggregated by the Configuration. Therefore, two 'Connect to Mail' Configurations may be defined grouping the relevant dependencies and Setting objects.trueThe label by which the Configuration object is known.256 truetrue2.6.0ConfigurationComponent aggregates 'lower-level' Configuration objects into a 'high-level' Configuration. This enables the assembly of complex Configurations by grouping together simpler ones. For example, a logon policy for the United States could consist of two Configuration groups, one for the east coast and one for the west coast. Each of these could in turn consist of multiple Configurations to handle different aspects of the logon process.truetrueThe Configuration that aggregates additional Configurations.trueA Configuration that is part of a 'higher-level' Configuration. true2.6.0This association relates a Configuration object to one or more ManagedSystemElements. The Configuration object represents a certain behavior, or a desired functional state for the associated ManagedSystemElements.trueThe ManagedSystemElement.trueThe Configuration object that groups the Settings and dependencies associated with the ManagedSystemElement. true2.6.0This association relates a Configuration object to one or more CollectionOfMSEs objects. The Configuration object represents a certain behavior, or a desired functional state for the associated Collection.trueThe CollectionOfMSEs.trueThe Configuration object that groups the Settings and dependencies associated with the Collection. truetrue2.6.0This relationship associates a Dependency with one or more Configuration objects. For example, a ComputerSystem's dependencies could change based on the site/network to which the System is attached.truetrueThe Configuration object that aggregates the Dependency.trueAn aggregated Dependency. truetrue2.6.0This relationship associates Configuration objects with Setting objects. For example, a NetworkAdapter's Settings could change based on the site/network to which its hosting ComputerSystem is attached. In this case, the ComputerSystem would have two different Configuration objects, corresponding to the differences in network configuration for the two network segments. Configuration A would aggregate a Setting object for the NetworkAdapter when operating on segment "ANet", whereas Configuration B would aggregate a different NetworkAdapter Setting object, specific to segment "BNet". Note that many Settings of the computer are independent of the network Configuration. For example, both Configurations A and B would aggregate the same Setting object for the ComputerSystem's MonitorResolution.truetrueThe Configuration object that aggregates the Setting.trueAn aggregated Setting. true2.6.0CollectionSetting represents the association between a CollectionOfMSEs class and the Setting class(es) defined for them.trueThe CollectionOfMSEs.trueThe Setting object associated with the Collection. 2.6.0CIM_SystemConfiguration represents the general concept of a CIM_Configuration which is scoped by/weak to a System. This class is a peer of CIM_Configuration since the key structure of Configuration is currently defined and cannot be modified with additional properties.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.256trueThe label by which the Configuration object is known.256 2.8.0CIM_ConfigurationForSystem defines a Configuration in the context of the System on which it resides.true11The hosting System.AntecedenttruetrueThe Configuration defined for the System.Dependenttrue truetrue2.6.0This relationship associates System-specific Configuration objects with System-specific Setting objects, similar to the SettingContext association.truetrueThe Configuration object that aggregates the Setting.trueAn aggregated Setting. true2.8.0CIM_StatisticalData is a root class for any arbitrary collection of statistical data and/or metrics applicable to one or more ManagedElements. These statistics MUST represent the most recent observations and MUST NOT be provided if irrelevant or stale. Note that this class uses a simplified naming/identity algorithm as compared to CIM_StatisticalInformation.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'.trueElementNameThe user friendly name for this instance of StatisticalData. In addition, the user friendly name can be used as a index property for a search of query. (Note: Name does not have to be unique within a namespace.)The time, relative to managed element where the statistic was collected, when the first measurement was taken. If the statistic is reset, the StartStatisticTime is the time when the reset was performed.The time the most recent measurement was taken, relative to the managed element where the statistic was collected.Some statistics are sampled at consistent time intervals. This property provides the sample interval so that client applications can determine the minimum time that new statistics should be pulled. If the statistics are not sampled at consistent time intervals, this property must be set to a zero time interval.00000000000000.000000:000Method to reset one or more of the instance's statistics. The method takes one parameter as input - an array of strings indicating which statistics to reset. If all the statistics in the instance should be reset, the first element of the array MUST be set to "All" or "ALL". If one or more individual statistics should be reset, the corresponding property names are entered into the elements of the array. The method returns 0 if successful, 1 if not supported, and any other value if an error occurred. A method is specified so that the StatisticalInformation's provider/ instrumentation, which calculates the statistics, can reset its internal processing, counters, etc. 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.trueArray of strings indicating which statistics to reset. true2.7.0CIM_ElementStatisticalData is an association that relates a ManagedElement to its StatisticalData. Note that the cardinality of the ManagedElement reference is Min(1), Max(1). This cardinality mandates the instantiation of the ElementStatisticalData association for the referenced instance of CIM_StatisticalData. ElementStatisticalData describes the existence requirements and context for the CIM_StatisticalData, relative to a specific ManagedElement.true11The ManagedElement for which statistical or metric data is defined.trueThe statistic information/object. true2.7.0CIM_RelatedStatisticalData is an association that defines hierarchies and/or dependencies of related CIM_Statistical Data classes.trueThe statistic information/object.trueThe related statistics.A free-form string describing how the statistics are related. true2.6.0CIM_StatisticalInformation is a root class for any arbitrary collection of statistical data and/or metrics applicable to one or more ManagedSystemElements. Note that the CIM_ StatisticalData class uses a simplified naming/identity algorithm as compared to this class. StatisticalInformation is not deprecated since its naming algorithm is still in use in various implementations.The Name property defines the label by which the statistic or metric is known. When subclassed, the property can be overridden to be a Key property.256 true2.6.0CIM_Statistics is an association that relates Managed Elements to the StatisticalGroup(s) that apply to them.trueThe statistic information/object.trueThe ManagedElement for which statistical or metric data is defined. true2.6.0CIM_RelatedStatistics is an association that defines hierarchies and/or dependencies of related CIM_Statistical Information classes.trueThe statistic information/object.trueThe related statistics or metrics. 2.6.0Statistical information associated with a System object or one of its subclasses.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, inherited from StatisticalInformation, serves as part of the object key.256 2.6.0SystemStatistics relates the SystemStatisticalInformation class to the System to which it applies.trueStatstrueThe statistical object.trueElement11The System to which the statistics apply.true 2.6.0Statistical information associated with a Service object or one of its subclasses.trueCIM_Service.SystemCreationClassNameThe scoping System's CreationClassName.256trueCIM_Service.SystemNameThe scoping System's Name.256trueCIM_Service.CreationClassNameThe scoping Service's CreationClassName.256trueCIM_Service.NameThe scoping Service'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, inherited from StatisticalInformation, serves as part of the object key.256 2.6.0ServiceStatistics relates the ServiceStatisticalInformation class to the Service to which it applies.trueStatstrueThe statistical object.trueElement11The Service to which the statistics apply.true 2.6.0Statistical information associated with a Service AccessPoint object or one of its subclasses.trueCIM_ServiceAccessPoint.SystemCreationClassNameThe scoping System's CreationClassName.256trueCIM_ServiceAccessPoint.SystemNameThe scoping System's Name.256trueCIM_ServiceAccessPoint.CreationClassNameThe scoping SAP's CreationClassName.256trueCIM_ServiceAccessPoint.NameThe scoping SAP'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, inherited from StatisticalInformation, serves as part of the object key.256 2.6.0SAPStatistics relates the SAPStatisticalInformation class to the ServiceAccessPoint to which it applies.trueStatstrueThe statistical object.trueElement11The ServiceAccessPoint to which the statistics apply.true 2.6.0Statistical information associated with a LogicalDevice or one of its subclasses.trueCIM_LogicalDevice.SystemCreationClassNameThe scoping System's CreationClassName.256trueCIM_LogicalDevice.SystemNameThe scoping System's Name.256trueCIM_LogicalDevice.CreationClassNameThe scoping Device's CreationClassName.256trueCIM_LogicalDevice.DeviceIDThe scoping Device's ID.64trueCreationClassName 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, inherited from StatisticalInformation, serves as part of the object key.256 2.6.0DeviceStatistics relates the DeviceStatisticalInformation class to the LogicalDevice to which it applies.trueStatstrueThe statistical object.trueElement11The Device to which the statistics apply.true 2.6.0Statistical information associated with a PhysicalElement or one of its subclasses.trueCIM_PhysicalElement.CreationClassNameThe scoping Element's CreationClassName.256trueCIM_PhysicalElement.TagThe scoping Element's identifying Tag.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, inherited from StatisticalInformation, serves as part of the object key.256 2.6.0PhysicalStatistics relates the PhysicalStatisticalInformation class to the PhysicalElement to which it applies.trueStatstrueThe statistical object.trueElement11The PhysicalElement to which the statistics apply.true 2.8.0CIM_StatisticalSetting is the class for setting the collection criteria of statistical data and/or metrics applicable to one or more ManagedElements.trueThe time, relative to managed element where the statistic is to be collected, when the first measurement is to be taken.CIM_StatisticalData.StartStatisticTimetrueThe time, relative to managed element where the statistic is to be collected, when the measurement is to end.trueSome statistics are sampled at consistent time intervals. This property when set indicates the desired minimum time that new statistics should be polled or calculated.CIM_StatisticalData.SampleInterval true2.6.0CIM_MethodParameters represents a set of values to be used as the parameters of a method. These parameters may be passed to the method, diretly used by the method in its invocation, or accessed by the method when it is called. The properties of a concrete subclass of MethodParameters are mapped to the parameters of a method by the method itself or by the method caller. This is an implementation detail independent of the definition of the class. For ease of use, property names should match parameter names. Property values should be set before the method is invoked. The ModelCorrespondence qualifier can be used to indicate if the property value should come from another class's property. The instances that the property values should be gleaned from should be associated with MethodParameters using the Parameter ValueSources association. If the property is declared as an array, then the same property value (identified by the Model Correspondence) will be retrieved from all appropriate ParameterValueSources instances and stored in the array. If the property is declared as an array and the Model Correspondence is to an array property, then only one instance of the array will be copied from one ParameterValueSource. If the property is not declared as an array and there are multiple instances of the class and property associated with it through ModelCorrespondence where the values are not all the same, then an error will occur and the property's value will not be set. Several MethodParameters instances can be associated with any ManagedElement's methods. This allows the maintenance of 'canned' method invocation and reduces the overhead of recreating all method parameters for every method invocation.The identifier by which the MethodParameters object is known.256The resetValues method updates the values of the properties of MethodParameters which have ModelCorrespondence to the SourceME ManagedElement. This allows the association of several source candidates with the MethodParameters with one being chosen as the source for this set of values. If resetValues is invoked and sourceME is null, then all associated MEs in ParameterValueSources will be used to set the values of the MethodParameters properties.trueThe source Managed Element. true2.6.0ParameterValueSources represents the association between a MethodParameters instance and the ManagedElement instances which contain properties to be used to create values for the MethodParameters properties.trueThe MethodParameters instance whose property values are to be set.trueThe ManagedElement which contains properties to be used to populate the values of the properties of the MethodParameters instance. true2.6.0ParametersForMethod represents the association between MethodParameters class(es) and a ManagedElement which has a method that may use the MethodParameters during its invocation. This association is optional, as the Method Parameters instance may be passed as a parameter to a method or used to create a method signature before the method is invoked. This association is useful for finding all the valid MethodParameters instances for a particular method. It may be particularly useful for user-oriented interfaces and automated or policy driven method invocations.trueThe MethodParameters instance which may be used by the ParametersForMethod's method invocation.trueThe ManagedElement which has a method that may use this instance of MethodParameters.trueThe name of the method that may use the referenced instance of MethodParameters during its invocation.64 2.7.0A class derived from Capabilities that describes the power management aspects of an element (typically a system or device). The element's power management capabilities are decoupled from a PowerManagementService, since a single service could apply to multiple elements, each with specific capabilities.An enumeration indicating the specific power-related capabilities of a managed element. Since this is an array, multiple values may be specified. The current values in the enumeration are: 0 = Unknown 1 = Other 2 = Power Saving Modes Entered Automatically, describing that a managed element can change its power state based on usage or other criteria 3 = Power State Settable, indicating that the SetPowerState method is supported 4 = Power Cycling Supported, indicating that the SetPowerState method can be invoked with the PowerState input variable set to 'Power Cycle' 5 = Timed Power On Supported, indicating that the SetPowerState method can be invoked with the PowerState input variable set to 'Power Cycle' and the Time parameter set to a specific date and time, or interval, for power-on.012345UnknownOtherPower Saving Modes Entered AutomaticallyPower State SettablePower Cycling SupportedTimed Power On SupportedMIF.DMTF|System Power Controls|001.2CIM_PowerManagementCapabilities.OtherPowerCapabilitiesDescriptionsCIM_PowerManagementService.SetPowerStateAn array of strings describing an element's additional power management capabilities, used when the PowerCapabilities array includes the value 1, "Other".CIM_PowerManagementCapabilities.PowerCapabilities 2.7.0A class derived from Service that describes power management functionality, hosted on a System. The fact that this service may be used to affect the power state of a particular element is defined by the CIM_ServiceAvailable ToElement association.SetPowerState defines the desired power state of the managed element, and when the element should be put into that state. The SetPowerState method has three input parameters, no output parameters, and a result. - PowerState indicates the desired power state. - ManagedElement indicates the element whose state is set. This element SHOULD be associated to the service using the ServiceAvailableToElement relationship. - 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). Note that when the PowerState parameter is equal to 5, "Power Cycle", the Time parameter indicates when the managed element should powered on again. Power off is immediate. SetPowerState should return 0 if successful, 1 if the specified State and Time request is not supported for the element, 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.trueThe power state for ManagedElement.12345678Full PowerPower Save - Low Power ModePower Save - StandbyPower Save - OtherPower CyclePower OffHibernateSoft OfftrueManagedElement indicates the element whose state is set.trueTime 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. 2.8.0The PhysicalPackage class represents PhysicalElements that contain or host other components. Examples are a Rack enclosure or an adapter Card.The RemovalCapabilites property is used to describe the conditions under which a PhysicalPackage can be removed. Since all PhysicalPackages are not removable, this property defaults to 2, 'Not Applicable'.0234UnknownNot ApplicableRemovable when offRemovable when on or off2CIM_PhysicalPackage.RemovalConditionsThe use of this property is being deprecated. Instead RemovalConditions should be used. The RemovalConditions property addresses whether a PhysicalPackage is removable with or without power being applied. A PhysicalPackage is Removable if it is designed to be taken in and out of the physical container in which it is normally found, without impairing the function of the overall packaging. A Package can still be Removable if power must be 'off' in order to perform the removal. If power can be 'on' and the Package removed, then the Element is both Removable and HotSwappable. For example, an extra battery in a laptop is Removable, as is a disk drive Package inserted using SCA connectors. However, the latter is also HotSwappable. A laptop's display is not Removable, nor is a non-redundant power supply. Removing these components would impact the function of the overall packaging or is impossible due to the tight integration of the Package.No ValueThe use of this property is being deprecated because it is redundant with the FRU class and its associations. A PhysicalPackage is Replaceable if it is possible to replace (FRU or upgrade) the Element with a physically different one. For example, some ComputerSystems allow the main Processor chip to be upgraded to one of a higher clock rating. In this case, the Processor is said to be Replaceable. Another example is a power supply Package mounted on sliding rails. All Removable packages are inherently Replaceable.CIM_PhysicalPackage.RemovalConditionsThe use of this property is being deprecated. Instead RemovalConditions should be used. The RemovalConditions property addresses whether a PhysicalPackage is removable with or without power being applied. A PhysicalPackage is HotSwappable if it is possible to replace the Element with a physically different but equivalent one while the containing Package has power applied to it (ie, is 'on'). For example, a disk drive Package inserted using SCA connectors is both Removable and HotSwappable. All HotSwappable packages are inherently Removable and Replaceable.The height of the PhysicalPackage in inches.InchesThe depth of the PhysicalPackage in inches.InchesThe width of the PhysicalPackage in inches.InchesThe weight of the PhysicalPackage in pounds.PoundsNo ValueThis method is being deprecated. A PhysicalPackage cannot determine if it is compatible with another object. The IsCompatible method verifies whether the referenced PhysicalElement may be contained by or inserted into the PhysicalPackage. 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.trueThe element to check for compatibility with this one. 2.6.0The Container association represents the relationship between a contained and a containing PhysicalElement. A containing object must be a PhysicalPackage.truetrueGroupComponent1The PhysicalPackage that contains other PhysicalElements, including other Packages.MIB.IETF|Entity-MIB.entPhysicalContainedIntruetruePartComponentThe PhysicalElement which is contained in the Package.trueA free-form string representing the positioning of the PhysicalElement within the PhysicalPackage. Information relative to stationary elements in the Container (for example, 'second drive bay from the top'), angles, altitudes and other data may be recorded in this property. This string could supplement or be used in place of instantiating the CIM_Location object.MIB.IETF|Entity-MIB.entPhysicalParentRelPos 2.7.0PhysicalFrame is a superclass of Rack, Chassis and other frame enclosures, as they are defined in extension classes. Properties like visible or audible alarm, and data related to security breaches are in this superclass.CableManagementStrategy is a free-form string that contains information on how the various cables are connected and bundled for the Frame. With many networking, storage-related and power cables, cable management can be a complex and challenging endeavor. This string property contains information to aid in assembly and service of the Frame.ServicePhilosophy is an enumerated, integer-valued array that indicates whether the Frame is serviced from the top (value=2), front (3), back (4) or side (5), whether it has sliding trays (6) or removable sides (7), and/or whether the Frame is moveable (8), for example, having rollers.012345678UnknownOtherService From TopService From FrontService From BackService From SideSliding TraysRemovable SidesMoveableIndexedCIM_PhysicalFrame.ServiceDescriptionsAn array of free-form strings providing more detailed explanations for any of the entries in the Service Philosophy array. Note, each entry of this array is related to the entry in ServicePhilosophy that is located at the same index.IndexedCIM_PhysicalFrame.ServicePhilosophyBoolean indicating whether the Frame is protected with a lock.Boolean indicating whether the Frame is equipped with an audible alarm.Boolean indicating that the equipment includes a visible alarm.SecurityBreach is an enumerated, integer-valued property indicating whether a physical breach of the Frame was attempted but unsuccessful (value=4) or attempted and successful (5). Also, the values, "Unknown", "Other" or "No Breach", can be specified.12345OtherUnknownNo BreachBreach AttemptedBreach SuccessfulMIF.DMTF|Physical Container Global Table|004.12CIM_PhysicalFrame.BreachDescriptionBreachDescription is a free-form string providing more information if the SecurityBreach property indicates that a breach or some other security-related event occurred.CIM_PhysicalFrame.SecurityBreachBoolean indicating that the Frame is currently locked. 2.6.0A Rack is a PhysicalFrame that represents an enclosure in which Chassis are placed. Typically a Rack is nothing more than the enclosure, and all the functioning componentry is packaged in the Chassis, loaded in the Rack.HeightThe height of the PhysicalPackage in 'U's. A 'U' is a standard unit of measure for the height of a Rack or rack-mountable component. It is equal to 1.75 inches or 4.445 cm.UsEnumeration indicating the type of Rack. Information such as "Telco" rack (value=2) or standard 19 inch rack (1) can be specified. The country for which the Rack is manufactured is defined in the the Country Designation property.01234UnknownStandard 19 InchTelcoEquipment ShelfNon-StandardCIM_Rack.CountryDesignationDesignation of the country for which the Rack is designed. Country code strings are as defined by ISO/IEC 3166. The rack type is specified in the TypeOf Rack property.CIM_Rack.TypeOfRack 2.8.0The Chassis class represents the PhysicalElements that enclose other Elements and provide definable functionality, such as a desktop, processing node, UPS, disk or tape storage, or a combination of these.Integer indicating the number of power cords which must be connected to the Chassis, for all the componentry to operate.Current required by the Chassis at 120V. If power is provided by the Chassis (as in the case of a UPS), this property may indicate the amperage produced, as a negative number.Amps at 120 VoltsAmount of heat generated by the Chassis in BTU/hour.BTU per HourCIM_Chassis.ChassisPackageTypeCIM_Chassis.MultipleSystemSupportThe use of this property is deprecated in lieu of ChassisPackageType. A physical package should not have multiple form factors. Therefore, this property is being deprecated in lieu of a single value property. An enumerated, integer-valued array indicating the type of Chassis.12345678910111213141516171819202122232425OtherUnknownDesktopLow Profile DesktopPizza BoxMini TowerTowerPortableLapTopNotebookHand HeldDocking StationAll in OneSub NotebookSpace-SavingLunch BoxMain System ChassisExpansion ChassisSubChassisBus Expansion ChassisPeripheral ChassisStorage ChassisRack Mount ChassisSealed-Case PCMulti-system ChassisMIF.DMTF|Physical Container Global Table|004.1IndexedCIM_Chassis.TypeDescriptionsCIM_Chassis.ChassisTypeDescriptionThe use of this property is deprecated in lieu of a single value property, ChassisTypeDescription. An array of free-form strings providing more information on the ChassisTypes array entries. Note, each entry of this array is related to the entry in ChassisTypes that is located at the same index.IndexedCIM_Chassis.ChassisTypesChassisPackageType indicates the physical form factor for the type of Chassis.012345678910111213141516171819202122232425..0x8000..0xFFFFUnknownOtherSMBIOS ReservedDesktopLow Profile DesktopPizza BoxMini TowerTowerPortableLapTopNotebookHand HeldDocking StationAll in OneSub NotebookSpace-SavingLunch BoxMain System ChassisExpansion ChassisSubChassisBus Expansion ChassisPeripheral ChassisStorage ChassisSMBIOS ResevedSealed-Case PCSMBIOS ReservedDMTF ReservedVendor ReservedMIF.DMTF|Physical Container Global Table|004.1CIM_Chassis.ChassisTypeDescriptionA string providing more information on the ChassisPackageType.CIM_Chassis.ChassisPackageTypeMultipleSystemSupport indicates whether or not this chassis supports multiple systems, for example server blades.012UnknownTrueFalseRackMountable indicates whether or not the chassis is Rack Mountable.012UnknownTrueFalse 2.8.0The PhysicalConnector class represents any PhysicalElement that is used to connect to other Elements. Any object that can be used to connect and transmit signals or power between two or more PhysicalElements is a descendant (or member) of this class. For example, Slots and D-shell connectors are types of PhysicalConnectors.A free-form string describing the pin configuration and/or signal usage of a PhysicalConnector.CIM_PhysicalConnector.NumPhysicalPinsCIM_PhysicalConnector.ConnectorGenderCIM_PhysicalConnector.ConnectorElectricalCharacteristicsCIM_PhysicalConnector.NumPhysicalPinsCIM_PhysicalConnector.ConnectorLayoutAn array of integers defining the type of PhysicalConnector. An array is specified to allow the description of 'combinations' of Connector information. For example, one array entry could specify RS-232 (value=25), another DB-25 (value=23) and a third entry define the Connector as "Male" (value=2). This single property is being deprecated in lieu of using separate properties to describe the various aspects of the connector. The separation allows for a more generic means of describing the connectors. Obsolete connectors were intentionally removed from the new list.0123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122UnknownOtherMaleFemaleShieldedUnshieldedSCSI (A) High-Density (50 pins)SCSI (A) Low-Density (50 pins)SCSI (P) High-Density (68 pins)SCSI SCA-I (80 pins)SCSI SCA-II (80 pins)Fibre Channel (DB-9, Copper)Fibre Channel (Optical Fibre)Fibre Channel SCA-II (40 pins)Fibre Channel SCA-II (20 pins)Fibre Channel BNCATA 3-1/2 Inch (40 pins)ATA 2-1/2 Inch (44 pins)ATA-2ATA-3ATA/66DB-9DB-15DB-25DB-36RS-232CRS-422RS-423RS-485RS-449V.35X.21IEEE-488AUIUPT Category 3UPT Category 4UPT Category 5BNCRJ11RJ45Fiber MICApple AUIApple GeoPortPCIISAEISAVESAPCMCIAPCMCIA Type IPCMCIA Type IIPCMCIA Type IIIZV PortCardBusUSBIEEE 1394HIPPIHSSDC (6 pins)GBICDINMini-DINMicro-DINPS/2InfraredHP-HILAccess.busNuBusCentronicsMini-CentronicsMini-Centronics Type-14Mini-Centronics Type-20Mini-Centronics Type-26Bus MouseADBAGPVME BusVME64ProprietaryProprietary Processor Card SlotProprietary Memory Card SlotProprietary I/O Riser SlotPCI-66MHZAGP2XAGP4XPC-98PC-98-HiresoPC-H98PC-98NotePC-98FullSSA SCSICircularOn Board IDE ConnectorOn Board Floppy Connector9 Pin Dual Inline25 Pin Dual Inline50 Pin Dual Inline68 Pin Dual InlineOn Board Sound ConnectorMini-jackPCI-XSbus IEEE 1396-1993 32 bitSbus IEEE 1396-1993 64 bitMCAGIOXIOHIONGIOPMCMTRJVF-45Future I/OSCSGElectricalOpticalRibbonGLM1x9Mini SGLCHSSCVHDCI Shielded (68 pins)InfiniBandAGP8XMIF.DMTF|Bus Port|004.10IndexedCIM_PhysicalConnector.OtherTypeDescriptionCIM_PhysicalConnector.ConnectorDescriptionA string describing the Connector - used when the ConnectorType property is set to 1 ("Other"). OtherType Description should be set to NULL when ConnectorType is any value other than 1. The use of this property is deprecated in lieu of Connector Description.MIF.DMTF|Bus Port|004.11CIM_PhysicalConnector.ConnectorTypeDescribes the gender of the connector.023UnknownMaleFemaleDescribes the electrical characteristic for this connector.012345678UnknownOtherSingle EndedDifferentialLow Voltage DifferentialOpticalCopperShieldedUnshieldedIndexedCIM_PhysicalConnector.OtherElectricalCharacteristicsA string describing the connector's electrical characteristics - used when the ConnectorElectricalCharacteristics property contains an entry of 1 (Other). OtherElectricalCharacteristics should be set to NULL when ConnectorElectricalCharacteristics does not contain an value of 1.IndexedCIM_PhysicalConnector.ConnectorElectricalCharacteristicsDescribes the number of physical pins (male/female) that are present on this connector.CIM_PhysicalConnector.ConnectorPinoutDescribes the type of packaging normally associated with this type of connector.012345678910UnknownOtherRS232BNCRJ11RJ45DB9SlotSCSI High DensitySCSI Low DensityRibbonCIM_PhysicalConnector.ConnectorDescriptionA string describing the Connector - used when the ConnectorLayout property is set to 1 ("Other"). Connector Description should be set to NULL when ConnectorLayout is any value other than 1.MIF.DMTF|Bus Port|004.11CIM_PhysicalConnector.ConnectorLayout 2.6.0Racks, as simple enclosures, contain Chassis that provide the physical componentry realizing processing nodes, storage devices, UPSs, etc. The ChassisInRack association makes explicit the 'containing' relationship between the Rack and the Chassis.truetrue1The Rack that contains the Chassis.GroupComponentMIB.IETF|Entity-MIB.entPhysicalContainedIntruetrueThe Chassis which is mounted in the Rack.PartComponenttrueAn integer indicating the lowest or 'bottom' U in which the Chassis is mounted. A 'U' is a standard unit of measure for the height of a Rack or rack-mountable component. It is equal to 1.75 inches or 4.445 cm.Us 2.6.0A Chassis can contain other Packages, such as other Chassis and Cards. The PackageInChassis association makes explicit this relationship.truetrue1The Chassis that contains other PhysicalPackages.GroupComponentMIB.IETF|Entity-MIB.entPhysicalContainedIntruetrueThe PhysicalPackage which is contained in the Chassis.PartComponenttrue 2.6.0A laptop, a type of Chassis, may be docked in another type of Chassis, a Docking Station. This is the relationship represented by the Docked association. Because this is such a typical relationship, it is explicitly described.MIF.DMTF|Dynamic States|001.2trueAntecedent1The Docking Station.trueDependent1The Laptop that is 'Docked'.true 2.8.0The Card class represents a type of physical container that can be plugged into another Card or HostingBoard, or is itself a HostingBoard/Motherboard in a Chassis. The CIM_Card class includes any package capable of carrying signals and providing a mounting point for PhysicalComponents, such as Chips, or other PhysicalPackages, such as other Cards.Boolean indicating that this Card is a Motherboard or, more generically, a baseboard in a Chassis.SlotLayout is a free-form string that describes the slot positioning, typical usage, restrictions, individual slot spacings or any other pertinent information for the slots on a Card.Boolean indicating that at least one daughterboard or auxiliary Card is required in order to function properly.Boolean indicating that this Card is physically unique from other Cards of the same type and therefore requires a special Slot. For example, a double-wide Card requires two Slots. Another example is where a certain Card may be used for the same general function as other Cards but requires a special Slot (e.g., extra long), whereas the other Cards can be placed in any available Slot. If set to TRUE, then the corresponding property, RequirementsDescription, should specify the nature of the uniqueness or purpose of the Card.CIM_Card.RequirementsDescriptionA free-form string describing the way(s) in which this Card is physically unique from other Cards. This property only has meaning when the corresponding boolean property, SpecialRequirements, is set to TRUE.CIM_Card.SpecialRequirementsOperating voltages required by the Card.MilliVoltsThis method manipulates the power to a PhysicalConnector on a Card. It is intended to be used by a Card (especially by a motherboard - i.e., HostingBoard=TRUE) to turn the power on and off for a specific PhysicalConnector located on it. For example, in a personal computer, a system slot does not know how to turn itself on and off. However, the motherboard hosting this slot may have that capability. This is important in order to support hot swapping of an adapter card in a system slot. 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.trueThe connector to change the power setting for.trueIf TRUE, turn power on for the connector. If FALSE, turn power off. 2.8.0The SystemBusCard class represents additional information for a CIM_Card, detailing the Card's bus type and data width. These properties dictate the type of Slot into which the Card can be inserted. For example, using the properties of this class, one can define that a Card is a PCI, 64 bit adapter.An enumerated integer describing the System bus type for this Card. It indicates the type of Slot into which the Card can plug. The list of permissible values aligns with the System bus types in CIM_PhysicalConnector.Connector Type.43444546474849505264657374757677787980818283848586879899100101102103104105106109110111PCIISAEISAVESAPCMCIAPCMCIA Type IPCMCIA Type IIPCMCIA Type IIICardBusAccess.busNuBusAGPVME BusVME64ProprietaryProprietary Processor Card SlotProprietary Memory Card SlotProprietary I/O Riser SlotPCI-66MHZAGP2XAGP4XPC-98PC-98-HiresoPC-H98PC-98NotePC-98FullPCI-XSbus IEEE 1396-1993 32 bitSbus IEEE 1396-1993 64 bitMCAGIOXIOHIONGIOPMCFuture I/OInfiniBandAGP8XCIM_PhysicalConnector.ConnectorTypeSystem bus width (in bits) required by this Card. If 'unknown', enter 0. If 'other' than the values, 8, 16, 32, 64 or 128, enter 1. The list of permissible values aligns with the data in CIM_Slot.MaxBusWidth.Bits018163264128CIM_Slot.MaxDataWidth 2.6.0Cards may be plugged into Motherboards/baseboards, are daughtercards of an adapter, or support special Card-like modules. These relationships are described by the CardOnCard association.truetrue1The Card that hosts another Card.GroupComponentMIB.IETF|Entity-MIB.entPhysicalContainedIntruetrueThe Card that is plugged into or otherwise mounted on another Card.PartComponenttrueA string describing and identifying how the Card is mounted on or plugged into the 'other' Card. Slot information could be included in this field and may be sufficient for certain management purposes. If so, this avoids creating instantiations of Connector/Slot objects just to model the relationship of Cards to HostingBoards or other adapters. On the other hand, if Slot and Connector information is available, this field could be used to provide more detailed mounting or slot insertion data. 2.8.0PackageLocation is a space/hole/shelf, possibly with mounting brackets or other connecting hardware, where other PhysicalPackages may be placed. This class describes an entity that holds something else and is not just a 'place' (as is conveyed by the CIM_Location object). This class has several corollaries to HostingBoard. Where a HostingBoard (backplane) has connectors/slots to describe the capabilities of holding additional PhysicalPackages, a PackageLocation is used to describe the same case for the general package, where there may or may not be no connectors. Examples of PackageLocations would include a disk cage in a tower PC or the chassis area where the power supply is mounted.LocationCoordinates represent the physical location of the the FrameSlot instance. The property is defined as a free-form string to allow the location information to be described in vendor-unique terminology. 2.8.0StorageMediaLocation is a PackageLocation where PhysicalMedia may be placed. This class is typically used in the context of a StorageLibrary. Examples of StorageMediaLocations are Media AccessDevices, InterLibraryPorts or 'slots' in a Library's panel.The type of Location. For example, whether this is an individual Media "Slot" (value=2), a MediaAccessDevice (value=4) or a "Magazine" (value=3) is indicated in this property.0123456789UnknownOtherSlotMagazineMediaAccessDeviceInterLibrary PortLimited Access PortDoorShelfVaultCertain StorageMediaLocations may only be able to accept a limited set of PhysicalMedia MediaTypes. This property defines an array containing the types of Media that are acceptable for placement in the Location. Additional information and description of the contained MediaTypes can be provided using the TypesDescription array. Also, size data (for example, DVD disc diameter) can be specified using the MediaSizesSupported array. Values defined here correspond to those in the CIM_Physical Media.MediaType property. This allows quick comparisons using value equivalence calculations. It is understood that there is no external physical difference between (for example) DVD- Video and DVD-RAM. But, equivalent values in both the Physical Media and StorageMediaLocation enumerations allows for one for one comparisons with no additional processing logic (i.e., the following is not required ... if "DVD-Video" then value="DVD").0123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566UnknownOtherTape CartridgeQIC CartridgeAIT CartridgeDTF CartridgeDAT Cartridge8mm Tape Cartridge19mm Tape CartridgeDLT CartridgeHalf-Inch Magnetic Tape CartridgeCartridge DiskJAZ DiskZIP DiskSyQuest DiskWinchester Removable DiskCD-ROMCD-ROM/XACD-ICD RecordableWORMMagneto-OpticalDVDDVD-RW+DVD-RAMDVD-ROMDVD-VideoDivxFloppy/DisketteHard DiskMemory CardHard CopyClik DiskCD-RWCD-DACD+DVD RecordableDVD-RWDVD-AudioDVD-5DVD-9DVD-10DVD-18Magneto-Optical RewriteableMagneto-Optical Write OnceMagneto-Optical Rewriteable (LIMDOW)Phase Change Write OncePhase Change RewriteablePhase Change Dual RewriteableAblative Write OnceNear Field RecordingMiniQicTravan8mm Metal Particle8mm Advanced Metal EvaporateNCTPLTO UltriumLTO Accelis9 Track Tape18 Track Tape36 Track TapeMagstar 3590Magstar MPD2 TapeTape - DST SmallTape - DST MediumTape - DST LargeIndexedCIM_PhysicalMedia.MediaTypeCIM_StorageMediaLocation.MediaSizesSupportedThe sizes (in inches) of the particular MediaTypes that may be placed in the Location. Note, each entry of this array is related to the entry in the MediaTypesSupported array that is located at the same index.InchesIndexedCIM_PhysicalMedia.MediaTypeCIM_StorageMediaLocation.MediaSizesSupportedCIM_StorageMediaLocation.TypeDescriptionsA StorageMediaLocation may hold more than one PhysicalMedia - for example, a Magazine. This property indicates the Physical Media capacity of the Location.This property provides additional detail related to the entries in the MediaTypesSupported array. This is especially critical when the MediaTypesSupported value is 1 ("Other"). Note, each entry of this array is related to the entry in MediaTypesSupported that is located at the same index.IndexedCIM_StorageMediaLocation.MediaTypesSupported 2.6.0StorageMediaLocations are typically slots or spaces where removable media are located. However, a specific kind of MediaLocation is a Magazine. This entity represents a single physical container with multiple StorageMediaLocations in it. All the MediaLocations within the Magazine are added/removed together. Often, this container has a Barcode or other label for identification. This is the unique data captured in the CIM_Magazine class. Magazine's label properties are defined exactly as are labels for PhysicalMedia.One or more strings on 'labels' on the Magazine. The format of the labels and their state (readable, unreadable, upside-down) are indicated in the corresponding LabelFormats and LabelStates array properties.IndexedCIM_Magazine.LabelStatesCIM_Magazine.LabelFormatsAn array of enumerated integers describing the states of each of the labels on a Magazine. The Labels themselves are listed in the PhysicalLabels property. Note, each entry of this array is related to the entry in PhysicalLabels that is located at the same index.012OK/ReadableUnreadableUpside DownIndexedCIM_Magazine.PhysicalLabelsAn array of enumerated integers describing the formats of each of the labels on a Magazine. The Labels themselves are listed in the PhysicalLabels property. Note, each entry of this array is related to the entry in PhysicalLabels that is located at the same index.012345BarcodeRadio Frequency IdentificationOCR (Optical Character Recognition)MICR (Magnetic Ink Character Recognition)7 Character Barcode9 Character BarcodeIndexedCIM_Magazine.PhysicalLabels 2.7.0Statistics related to reading physical labels and picks/puts at a specific StorageMediaLocation, or for a specific piece of PhysicalMedia. The same class is used to represent this data - whether for a Location (independent of the Media), OR for the Media (independent of its StorageMediaLocation). The element whose statistics are described is associated using the relationship, ElementStatisticalData.The number of successful physical label scans.trueThe number of failed physical label scans.trueThe number of retried physical label scans.trueThe number of successful picks.trueThe number of failed picks.trueThe number of retried picks.trueThe number of successful puts.trueThe number of failed puts.trueThe number of retried puts.true CIM_MediaPhysicalStatData2.7.0Statistics related to reading physical labels and picks/puts at a specific StorageMediaLocation, or for a specific piece of PhysicalMedia. Although the same class is used to represent this data, at the instance level the object holds information for the Location (independent of the Media), OR for the Media (independent of its StorageMediaLocation). This class is deprecated in lieu of MediaPhysicalStatData, to take advantage of the simplified key structure defined there.CIM_MediaPhysicalStatData.ScanSuccessesThe number of successful physical label scans.trueCIM_MediaPhysicalStatData.ScanFailuresThe number of failed physical label scans.trueCIM_MediaPhysicalStatData.ScanRetriesThe number of retried physical label scans.trueCIM_MediaPhysicalStatData.PickSuccessesThe number of successful picks.trueCIM_MediaPhysicalStatData.PickFailuresThe number of failed picks.trueCIM_MediaPhysicalStatData.PickRetriesThe number of retried picks.trueCIM_MediaPhysicalStatData.PutSuccessesThe number of successful puts.trueCIM_MediaPhysicalStatData.PutFailuresThe number of failed puts.trueCIM_MediaPhysicalStatData.PutRetriesThe number of retried puts.trueCIM_StatisticalData.ResetSelectedStatsMethod to reset the statistical counters. The method takes one parameter as input - an integer indicating which counter to reset. For this input parameter, 0 indicates all, 1-3 reset the scan-related counters, 4-6 reset the 'pick'-related counters, and 7-9 reset the 'put'-related counters. The method returns 0 if successful, 1 if not supported, and any other value if an error occurred. A method is specified so that the Element's instrumentation can also reset its internal processing and counters. The set of possible return codes should be specified in a ValueMap qualifier on the method. The strings to which the ValueMap contents are 'translated' should be specified as a Values array qualifier on the method.trueThe counter to reset.0123456789AllScan SuccessesScan FailuresScan RetriesPick SuccessesPick FailuresPick RetriesPut SuccessesPut FailuresPut Retries 2.6.0The ConnectedTo association indicates that two or more PhysicalConnectors are connected together.trueAntecedentThe Antecedent represents a PhysicalConnector that serves as one end of the connection.trueDependentThe Dependent represents another PhysicalConnector that serves as the other end of the connection.true 2.7.0The Slot class represents Connectors into which Packages are inserted. For example, a PhysicalPackage that is a DiskDrive may be inserted into an SCA 'Slot'. As another example, a Card (subclass of PhysicalPackage) may be inserted into a 16-, 32-, or 64-bit expansion 'Slot' on a HostingBoard. PCI or PCMCIA Type III Slots are examples of the latter.ConnectorType