false false false Bag 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.64The Caption property is a short textual description (one-line string) of the object.The 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.0 CIM_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.0 CIM_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.0 CIM_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 ManagedElement. 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.0 CIM_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.7.0CIM_ManagedSystemElement is the base class for the System Element hierarchy. Membership Criteria: Any distinguishable component of a System is a candidate for inclusion in this class. Examples: software components, such as files; and devices, such as disk drives and controllers, and 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.51024The Name property defines the label by which the object is known. When subclassed, the Name property can be overridden to be a Key property. Indicates 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 ManagedSystemElement 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. 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. As always, Status (since it is single-valued) provides the primary status of the element.01234567891011121314151617UnknownOtherOKDegradedStressedPredictive FailureErrorNon-Recoverable ErrorStartingStoppingStoppedIn ServiceNo ContactLost CommunicationAbortedDormantSupporting Entity in ErrorCompletedIndexedCIM_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.OperationalStatus10CIM_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 CommStopped 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.7.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=8) 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. 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.CIM_EnabledLogicalElement.EnabledState2345678910..3276732768..65535EnabledDisabledShut DownNo ChangeOfflineTestDeferredQuiesceDMTF ReservedVendor Reserved5trueAn enumerated value indicating an administrator's default/startup configuration for an element's EnabledState. By default, the element is "Enabled" (value=2).235678..3276732768..65535EnabledDisabledNot ApplicableEnabled but OfflineNo DefaultDMTF ReservedVendor Reserved2 true2.6.0Indicates that two LogicalElements 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 LogicalElement that is synchronized with the entity referenced as SyncedElement.trueSyncedElement represents another LogicalElement 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.true256CreationClassName 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.true256NameThe inherited Name serves as key of a System instance in an enterprise environment.64The 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.MIF.DMTF|General Information|001.3256trueA string that provides information on how the primary system owner can be reached (e.g. phone number, email address, ...).MIF.DMTF|General Information|001.4true An 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.6.0 This 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.OtherASNAPNOCPOPRNPIPIPXSNADialWANLANISDNFrame RelayATME.164IBFCPolicy RepositoryOtherAutonomous SystemNetwork Access ProviderNetwork Operations CenterPoint of PresenceRegional Network ProviderIPIPXSNADialWANLANISDNFrame RelayATME.164InfinibandFibre ChannelPolicy Repository64 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.CIM_System.CreationClassNametrue256The scoping System's CreationClassName.CIM_System.Nametrue256The scoping System's Name.true256CreationClassName 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.Nametrue256The 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.64trueThe name of the primary owner for the service, if one is defined. The primary owner is the initial support contact for the Service.MIF.DMTF|General Information|001.3256trueA string that provides information on how the primary owner of the Service can be reached (e.g. phone number, email address, ...).MIF.DMTF|General Information|001.410CIM_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.AutomaticManualStarted 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.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. 2.6.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.trueAntecedent11The hosting System.trueDependenttrueThe Service hosted on the System.true CIM_ServiceAvailableToElement2.7.0The use of the CIM_ProvidesServiceToElement class has been deprecated. Instead, ServiceAvailableToElement conveys the semantics of 'use', while the subclasses of ProvidesServiceToElement (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.trueAntecedentCIM_ServiceAvailableToElement.ServiceProvidedThe Service provided.trueDependentCIM_ServiceAvailableToElement.UserOfServiceThe 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".Indexed01234UnknownOtherExclusive UsePerformance ImpactElement IntegrityCIM_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.0 CIM_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.CIM_System.CreationClassNametrue256The scoping System's CreationClassName.CIM_System.Nametrue256The scoping System's Name.true256CreationClassName 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.Nametrue256The 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. 2.6.0CIM_HostedAccessPoint is an association between a ServiceAccessPoint 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.trueAntecedent11The hosting System.trueDependenttrueThe SAP(s) that are hosted on this System.true 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 ServiceAccessPoints, 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 ServiceAccessPoint and another ServiceAccessPoint indicating that the latter is required in order for the former ServiceAccessPoint 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 value64A 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.CIM_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.7.0 RemoteServiceAccessPoint 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 RemoteServiceAccessPoint, 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.12345678910..99100101102103104105..19920032768..65535OtherHost NameIpv4 AddressIpv6 AddressIPX AddressDECnet AddressSNA AddressAutonomous System NumberMPLS LabelDMTF ReservedDial StringEthernet AddressToken Ring AddressATM AddressFrame Relay AddressDMTF ReservedURLVendor SpecificCIM_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.true256The LabeledURI property is based on RFC 2079 and its value and syntax is service specific. 2.7.0A communication point from which data may be sent or received. ProtocolEndpoints link system/computer interfaces to LogicalNetworks.256A 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.Nametrue256NameFormat 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.ProtocolType 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 Endpoint). Hence, this property is needed to define the type of Endpoint. Note that in a future major release of the CIM Schema, it is likely that ProtocolEndpoint will be ABSTRACT, forcing subclassing and removing the need for this property.0123456789101112131415161718192021222324252627UnknownOtherIPv4IPv6IPXAppleTalkDECnetSNACONPCLNPVINESXNSATMFrame RelayEthernetTokenRingFDDIInfinibandFibre ChannelISDN BRI EndpointISDN B Channel EndpointISDN D Channel EndpointIPv4/v6BGPOSPFMPLSUDPTCPCIM_ProtocolEndpoint.OtherTypeDescription64A 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.CIM_ProtocolEndpoint.ProtocolType 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.7.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 PhysicalElements. 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 ManagedSystemElements (usually actual hardware items) that have a physical manifestation of some sort. A ManagedSystemElement 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.true256An arbitrary string that uniquely identifies the PhysicalElement 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 PhysicalElement is an arbitrary string and is defined independently of any placement or location-oriented hierarchy.true256CreationClassName 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.ElementNameMIB.IETF|Entity-MIB.entPhysicalName 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.256The 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.MIB.IETF|Entity-MIB.entPhysicalMfgName256The name by which the PhysicalElement is generally known.MIB.IETF|Entity-MIB.entPhysicalDescr64The stock keeping unit number for this PhysicalElement.256A manufacturer-allocated number used to identify the PhysicalElement.MIB.IETF|Entity-MIB.entPhysicalSerialNum64A string indicating the version of the PhysicalElement.MIB.IETF|Entity-MIB.entPhysicalHardwareRev256The part number assigned by the organization responsible for producing or manufacturing the PhysicalElement.MIB.IETF|Entity-MIB.entPhysicalModelNametrueOtherIdentifyingInfo captures additional data, beyond that of Tag information, that could be used to identify a PhysicalElement. 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. 2.6.0The Location class specifies the position and address of a PhysicalElement.true256Name is a free-form string defining a label for the Location. It is a part of the key for the object.true256Position 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.1024Address is a free-form string indicating a street, building or other type of address for the PhysicalElement's Location. 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, PhysicalElementLocation. 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.7.0 SoftwareIdentity represents software, viewed as an asset and/or individually identifiable entity (similar to PhysicalElement). 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 SoftwareIdentity 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 could be instrumentation (value=5) or firmware and diagnostic software (6 and 7).0123456789UnknownOtherDriverConfiguration SoftwareApplication SoftwareInstrumentationFirmware/BIOSDiagnostic SoftwareOperating SystemMiddlewareIndexedCIM_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.Classifications true2.7.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.CIM_System.CreationClassNametrue256The scoping System's CreationClassName.CIM_System.Nametrue256The scoping System's Name.true256CreationClassName 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.true64An address or other identifying information to uniquely name the LogicalDevice.CIM_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 AdditionalAvailability 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.EnabledStatus The StatusInfo property indicates whether the LogicalDevice 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.4LastErrorCode captures the last error code reported by the LogicalDevice.ErrorDescription is a free-form string supplying more information about the error recorded in LastErrorCode, and information on any corrective actions that may be taken.ErrorCleared is a boolean property indicating that the error reported in LastErrorCode is now cleared.256IndexedOtherIdentifyingInfo captures additional data, beyond DeviceID information, that could be used to identify a LogicalDevice. One example would be to hold the OperatingSystem's user friendly name for the Device in this property.CIM_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.HourstrueIndexedAn 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.CIM_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.AvailabilityMaximum 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.true123456Full PowerPower Save - Low Power ModePower Save - StandbyPower Save - OtherPower CyclePower OfftrueRequests a reset of the LogicalDevice. The return value should be 0 if the request was successfully executed, 1 if the request is not supported and some other value if an error occurred. In a subclass, the set of possible return codes could be specified, using a ValueMap qualifier on the method. The strings to which the ValueMap contents are 'translated' may also be specified in the subclass as a Values array qualifier. Requests 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.trueRequests 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.trueRequests 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 AdditionalAvailability) of "Running/Full Power" (value=3) and an EnabledState/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 EnabledState/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. 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 QuiesceDevice method should set the RequestedState property appropriately.trueRequests 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 LogicalDevice, 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 LogicalDevice.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.7.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 BlockSize, 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, DiskPartitions 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 Reserved 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: o 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.0 SystemSpecificCollection 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.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.trueAntecedent11The scoping system.trueDependentThe collection defined in the context of a system.true true2.6.0 The CollectionOfMSEs object allows the grouping of ManagedSystemElements 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_RedundancyGroup (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.256The identification of the Collection object. When subclassed, the CollectionID property can be overridden to be a Key property. 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, CollectionOfMSEs.truetrueCollectionThe grouping or 'bag' object that represents the Collection.truetrueMemberThe members of the Collection.true 2.7.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.true256CreationClassName 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.Nametrue256The RedundancyGroup Name serves as the key for the Group's instance in an enterprise environment.RedundancyStatus 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 ManagedSystemElement 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 RedundancyComponent 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.truetrue 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. StorageRedundancyGroups 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 orCompositeExtentBasedOn. 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 StorageRedundancyGroup.truetrueThe StorageRedundancyGroup.GroupComponenttruetrueThe StorageExtent participating in the RedundancyGroup.PartComponenttrue 2.7.0 CIM_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.true256Commonly used Product name.CIM.DMTF|PRS_Product.ProductNameMIF.DMTF|ComponentID|001.2true64Product identification such as a serial number on software, a die number on a hardware chip, or (for non-commercial Products) a project number.MIF.DMTF|ComponentID|001.4true256The 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.CIM.DMTF|PRS_Product.VendorMIF.DMTF|ComponentID|001.1true64Product version information.CIM.DMTF|PRS_Product.VersionMIF.DMTF|ComponentID|001.364Product SKU (stock keeping unit) information.If this Product is under warranty, the start date of the warranty.CIM_Product.WarrantyDurationMIF.DMTF|FRU|002.9If this Product is under warranty, the duration of the warranty in days.DaysCIM_Product.WarrantyStartDateMIF.DMTF|FRU|002.10 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.truetrueGroupComponentPRS_ProductComponent.AntecedentThe 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.truetruePartComponentPRS_ProductComponent.DependentThe contained Product.true 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.true256SupportAccessID 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.DescriptionA textual description of the type of Support provided.MIF.DMTF|Support|001.3CommunicationInfo provides the details of the CommunicationMode. 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.564Locale defines the geographic region and/or language dialect to which this Support resource pertains.MIF.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'.true64FRU ordering information.MIF.DMTF|FRU|002.6true64FRU identification such as a serial number on software or a die number on a hardware chip.MIF.DMTF|FRU|002.7true256The name of the FRU's supplier.MIF.DMTF|FRU|002.4DescriptionA textual description of the FRU.MIF.DMTF|FRU|002.3256FRU name.64The FRU's revision level.MIF.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.1trueThe 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.1trueThe 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 truetrueCIM_ProductPhysicalComponenttrue2.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 ManagedElement and a Component relationship between ManagedElements did not exist.1truetrueCIM_ProductPhysicalComponent.GroupComponentThe Product.trueCIM_ProductPhysicalComponent.PartComponentThe PhysicalElement which is a part of the Product. truetruetrue2.7.0Indicates the PhysicalElements that make up a FRU.1truetrueThe FRU.trueThe PhysicalElement which is a part of the FRU. truetruetrue2.7.0Indicates that a FRU may be composed of other Product(s).1truetrueThe FRU.trueThe Product which is a part of the FRU. true2.7.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'.ElementNametrueThe 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.)Method 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.true 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. trueCIM_RelatedStatisticalData is an association that defines hierarchies and/or dependencies of related CIM_StatisticalData 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.256The 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. true2.6.0CIM_Statistics is an association that relates ManagedElements 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_StatisticalInformation classes.trueThe statistic information/object.trueThe related statistics or metrics. 2.6.0Statistical information associated with a System object or one of its subclasses.CIM_System.CreationClassNametrue256The scoping System's CreationClassName.CIM_System.Nametrue256The scoping System's Name.true256CreationClassName 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.true256NameThe Name property, inherited from StatisticalInformation, serves as part of the object key. 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.CIM_Service.SystemCreationClassNametrue256The scoping System's CreationClassName.CIM_Service.SystemNametrue256The scoping System's Name.CIM_Service.CreationClassNametrue256The scoping Service's CreationClassName.CIM_Service.Nametrue256The scoping Service's Name.true256CreationClassName 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.true256NameThe Name property, inherited from StatisticalInformation, serves as part of the object key. 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 ServiceAccessPoint object or one of its subclasses.CIM_ServiceAccessPoint.SystemCreationClassNametrue256The scoping System's CreationClassName.CIM_ServiceAccessPoint.SystemNametrue256The scoping System's Name.CIM_ServiceAccessPoint.CreationClassNametrue256The scoping SAP's CreationClassName.CIM_ServiceAccessPoint.Nametrue256The scoping SAP's Name.true256CreationClassName 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.true256NameThe Name property, inherited from StatisticalInformation, serves as part of the object key. 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.CIM_LogicalDevice.SystemCreationClassNametrue256The scoping System's CreationClassName.CIM_LogicalDevice.SystemNametrue256The scoping System's Name.CIM_LogicalDevice.CreationClassNametrue256The scoping Device's CreationClassName.CIM_LogicalDevice.DeviceIDtrue64The scoping Device's ID.true256CreationClassName 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.true256NameThe Name property, inherited from StatisticalInformation, serves as part of the object key. 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.CIM_PhysicalElement.CreationClassNametrue256The scoping Element's CreationClassName.CIM_PhysicalElement.Tagtrue256The scoping Element's identifying Tag.true256CreationClassName 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.true256NameThe Name property, inherited from StatisticalInformation, serves as part of the object key. 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 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'.ElementNametrueThe 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.0 The 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'.ElementNametrueThe 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.7.0ScopedSetting defines a setting in the context of the ManagedElement which it resides.trueAntecedent11The scoping ManagedElement.trueDependentThe setting defined for the ManagedElement.true 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.0 Profile 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.0 The 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.256The identifier by which the Setting object is known.The VerifyOKToApplyToMSE method is used to verify that this Setting can be 'applied' to the referenced ManagedSystemElement, at the given time or time interval. This method takes three input parameters: MSE (the ManagedSystemElement 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.truetruetrue The ApplyToMSE method performs the actual application of the Setting to the referenced ManagedSystemElement. It takes three input parameters: MSE (the ManagedSystemElement 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.truetruetrue 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 ManagedSystemElements 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.truetruetruefalsetrue The ApplyToCollection method performs the application of the Setting to the referenced Collection of ManagedSystemElements. 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.truetruetruetruefalsetrueThe VerifyOKToApplyIncrementalChangeToMSE method is used to verify that a subset of the properties in this Setting can be 'applied' to the referenced ManagedSystemElement, at the given time or time interval. This method takes four input parameters: MSE (the ManagedSystemElement 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.truetruetruetrue 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 ManagedSystemElement 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.truetruetruetrue 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 ManagedSystemElements 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.truetruetruetruefalsetrue The ApplyIncrementalChangeToCollection method performs the application of a subset of the properties in this Setting to the referenced Collection of ManagedSystemElements. 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.truetruetruetruetruefalsetrue true2.6.0ElementSetting represents the association between ManagedSystemElements and the Setting class(es) defined for them.trueThe ManagedSystemElement.trueThe Setting object associated with the ManagedSystemElement. 2.6.0DefaultSetting represents the association between a ManagedSystemElement 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.CIM_System.CreationClassNametrue256The scoping System's CreationClassName.CIM_System.Nametrue256The scoping System's Name.true256CreationClassName 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.SettingIDtrue256The identifier by which the Setting object is known. 2.6.0CIM_SettingForSystem defines a Setting in the context of the System on which it resides.trueAntecedent11The hosting System.trueDependenttrueThe Setting defined for the System.true 2.6.0 The 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 ManagedSystemElements. 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.true256The label by which the Configuration object is known. 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.CIM_System.CreationClassNametrue256The scoping System's CreationClassName.CIM_System.Nametrue256The scoping System's Name.true256CreationClassName 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.true256The label by which the Configuration object is known. 2.6.0CIM_ConfigurationForSystem defines a Configuration in the context of the System on which it resides.trueAntecedent11The hosting System.trueDependenttrueThe Configuration defined for the System.true 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.6.0 CIM_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 ParameterValueSources association. If the property is declared as an array, then the same property value (identified by the ModelCorrespondence) will be retrieved from all appropriate ParameterValueSources instances and stored in the array. If the property is declared as an array and the ModelCorrespondence 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.256The identifier by which the MethodParameters object is known.The 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.true 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 MethodParameters 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.true64The name of the method that may use the referenced instance of MethodParameters during its invocation. 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_ServiceAvailableToElement 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.true12345678Full PowerPower Save - Low Power ModePower Save - StandbyPower Save - OtherPower CyclePower OffHibernateSoft Offtruetrue 2.6.0The PhysicalPackage class represents PhysicalElements that contain or host other components. Examples are a Rack enclosure or an adapter Card.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.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.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.PoundsThe 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.true 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.Indexed012345678UnknownOtherService From TopService From FrontService From BackService From SideSliding TraysRemovable SidesMoveableCIM_PhysicalFrame.ServiceDescriptionsAn array of free-form strings providing more detailed explanations for any of the entries in the ServicePhilosophy 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 CountryDesignation 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 TypeOfRack property.CIM_Rack.TypeOfRack 2.7.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 HourAn enumerated, integer-valued array indicating the type of Chassis.Indexed12345678910111213141516171819202122232425OtherUnknownDesktopLow 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.1CIM_Chassis.TypeDescriptionsAn 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.ChassisTypes 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.6.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.truetrue 2.7.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.ConnectorType.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.MaxBusWidth 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.6.0StorageMediaLocation is a PhysicalPackage where PhysicalMedia may be placed. This class describes an entity that holds Media and is not just a 'place' (as is conveyed by the CIM_Location object). This class is typically used in the context of a StorageLibrary. Examples of StorageMediaLocations are MediaAccessDevices, 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 PortDoorShelfVaultLocationCoordinates represent the physical location of the the StorageMediaLocation instance. The property is defined as a free-form string to allow the location information to be described in vendor-unique terminology. Certain 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_PhysicalMedia.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 PhysicalMedia 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").Indexed0123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566UnknownOtherTape 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 LargeCIM_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.IndexedInchesCIM_PhysicalMedia.MediaTypeCIM_StorageMediaLocation.MediaSizesSupportedCIM_StorageMediaLocation.TypeDescriptionsA StorageMediaLocation may hold more than one PhysicalMedia - for example, a Magazine. This property indicates the PhysicalMedia 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.Indexed012OK/ReadableUnreadableUpside DownCIM_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.Indexed012345BarcodeRadio Frequency IdentificationOCR (Optical Character Recognition)MICR (Magnetic Ink Character Recognition)7 Character Barcode9 Character BarcodeCIM_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 2.7.0CIM_MediaPhysicalStatDataStatistics 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.true0123456789AllScan SuccessesScan FailuresScan RetriesPick SuccessesPick FailuresPick RetriesPut SuccessesPut FailuresPut Retries 2.7.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 signal usage of a PhysicalConnector.An 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).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.10CIM_PhysicalConnector.OtherTypeDescriptionA 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.CIM_PhysicalConnector.ConnectorTypeMIF.DMTF|Bus Port|004.11 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.ConnectorTypeMIF.DMTF|System Slot|005.2An 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).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)InfiniBandAGP8XCIM_PhysicalConnector.OtherTypeDescriptionPoweredOnMIF.DMTF|System Slot|005.13Boolean indicating that the PhysicalElement is powered on (TRUE), or is currently off (FALSE).Boolean indicating whether the Slot supports hot-plug of adapter Cards.Maximum height of an adapter Card that can be inserted into the Slot, in inches.InchesMaximum length of an adapter Card that can be inserted into the Slot, in inches.InchesMaximum bus width of adapter Cards that can be inserted into this Slot, in bits. If the value is 'unknown', enter 0. If the value is other than 8, 16, 32, 64 or 128, enter 1.Bits018163264128MIF.DMTF|System Slot|005.3An array of enumerated integers indicating the Vcc voltage supported by this Slot.0123UnknownOther3.3V5VMIF.DMTF|System Slot|005.9An array of enumerated integers indicating the Vpp voltage supported by this Slot.01234UnknownOther3.3V5V12VMIF.DMTF|System Slot|005.10Maximum thermal dissipation of the Slot in milliwatts.MilliWattsMIF.DMTF|System Slot|005.11Boolean indicating that this Slot is physically unique and may hold special types of hardware, e.g. a graphics processor slot. If set to TRUE, then the property, SpecialPurposeDescription (a string), should specify the nature of the uniqueness or purpose of the Slot.CIM_Slot.PurposeDescriptionA free-form string describing that this Slot is physically unique and may hold special types of hardware. This property only has meaning when the corresponding boolean property, SpecialPurpose, is set to TRUE.CIM_Slot.SpecialPurposeThe Number property indicates the physical slot number, which can be used as an index into a system slot table, whether or not that slot is physically occupied.MIF.DMTF|System Slot|005.1CIM_PhysicalElement.PoweredOnA boolean indicating whether the Slot is currently powered (TRUE) or not (FALSE).MIF.DMTF|System Slot|005.13A boolean indicating whether the switch state of the Slot is currently open (TRUE) or closed (FALSE). This switch state determines whether the contents of the Slot can be hot-plugged.MIF.DMTF|System Slot|005.15 2.6.0Slots are special types of Connectors into which adapter Cards are typically inserted. The SlotInSlot relationship represents the ability of a special adapter to extend the existing Slot structure to enable otherwise incompatible Cards to be plugged into a Frame or HostingBoard. The adapter effectively creates a new Slot and can be thought of (conceptually) as a Slot in a Slot. This enables Cards that would otherwise be physically and/or electrically incompatible with the existing Slots to be supported, by interfacing to the Slot provided by the adapter. This has many practical uses. For example, networking boards are very expensive. As new hardware becomes available, Chassis and even Card configurations change. To protect the investment of their customers, networking vendors will manufacture special adapters that enable old Cards to fit into new Chassis or HostingBoards and/or new Cards to fit into old. This is done using a special adapter that fits over one or more existing Slots and presents a new Slot into which the Card can plug.trueThe Antecedent represents the existing Slot(s) of the HostingBoard, or Frame that are being adapted to accommodate a Card that would otherwise not be physically and/or electrically compatible with it.Antecedenttrue1The new Slot provided by the adapter board.Dependenttrue true2.6.0AdjacentSlots describes the layout of Slots on a HostingBoard or adapter Card. Information like the distance between the Slots and whether they are 'shared' (if one is populated, then the other Slot can not be used), is conveyed as properties of the association.trueOne of the adjacent Slots.trueThe 'other' adjacent Slot.The distance, in inches, between adjacent Slots.InchesSlots can be located in close proximity on HostingBoards or other Cards, such that if one of these Slots is populated by an adapter Card, the other Slot must be left empty. This relationship is indicated by the SharedSlots boolean set to TRUE. 2.6.0Adapter cards and other 'packaging' are plugged into System Connectors for power and/or to transfer data. This relationship is defined by PackageInConnector. For example, it would be used to describe the insertion of a daughtercard onto another Card. Various subclasses of PackageInConnector are also defined. PackageInSlot and its subclass, CardInSlot, are two examples of subclasses.trueAntecedentThe Connector into which the Package is inserted.trueDependent1The Package in the Connector.true 2.6.0Complex networking devices often are Chassis-based. These Chassis allow for enhancement and/or augmentation of their base functionality by accepting additional Chassis devices, similar to accepting functionality in the form of adding Cards. This association models this capability.trueThe Slot into which the PhysicalPackage is inserted.Antecedenttrue1The Package in the Slot.Dependenttrue 2.6.0Slots are special types of Connectors into which adapter Cards are inserted. This relationship of a Card in a Slot is made explicit using the CardInSlot association.MIF.DMTF|System Slot|005.4trueThe Slot into which the Card is inserted.Antecedenttrue1The Card in the Slot.Dependenttrue 2.6.0PhysicalPackages contain Connectors as well as other PhysicalElements. The ConnectorOnPackage association makes explicit the containment relationship between Connectors and Packages.truetrue1The PhysicalPackage that has a Connector.GroupComponentMIB.IETF|Entity-MIB.entPhysicalContainedIntruetrueThe PhysicalConnector.PartComponenttrue 2.6.0The PhysicalLink class represents the cabling of PhysicalElements together. For example, serial or Ethernet cables, and infrared Links would be subclasses (if additional properties or associations are defined) or instances of PhysicalLink. In many cases, the numerous physical cables within a PhysicalPackage or Network will not be modeled. However, where these cables or Links are critical components, or are tagged assets of the company, these objects can be instantiated using this class or one of its descendent classes.The maximum length of the PhysicalLink in feet.FeetThe current length of the PhysicalLink in feet. For some connections, especially wireless technologies, this property may not be applicable and should be left uninitialized.FeetBoolean indicating whether the PhysicalLink is an actual cable (TRUE) or a wireless connection (FALSE).The MediaType property defines the particular type of Media through which transmission signals pass. Common network media include twisted-pair (value=11 or 12), coaxial (7, 8 or 9) and fiber-optic cable (10).01234567891011121314151617UnknownOtherCat1Cat2Cat3Cat4Cat550-ohm Coaxial75-ohm Coaxial100-ohm CoaxialFiber-opticUTPSTPRibbon CableTwinaxialOptical 9umOptical 50umOptical 62.5umMIF.DMTF|Fibre Channel Bus Port Extensions|001.4 2.6.0The ElementsLinked association indicates which PhysicalElements are cabled together by a PhysicalLink.trueAntecedentThe PhysicalLink.trueDependentThe PhysicalElement that is linked.true 2.6.0Cables and Links utilize PhysicalConnectors to actually 'connect' PhysicalElements. This association explicitly defines this relationship of Connectors for PhysicalLinks.truetrueGroupComponent1The PhysicalLink that has a Connector.truetruePartComponentThe PhysicalConnector.true 2.6.0The PhysicalComponent class represents any low-level or basic Component within a Package. A Component object either can not or does not need to be decomposed into its constituent parts. For example, an ASIC (or Chip) can not be further decomposed. A tape for data storage (PhysicalMedia) does not need to be decomposed. Any PhysicalElement that is not a Link, Connector, or Package is a descendent (or member) of this class. For example, the UART chipset on an internal modem Card would be a subclass (if additional properties or associations are defined) or an instance of PhysicalComponent.A PhysicalComponent 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 Component can still be Removable if power must be 'off' in order to perform the removal. If power can be 'on' and the Component removed, then the Element is both Removable and HotSwappable. For example, an upgradeable Processor chip is Removable.A PhysicalComponent 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. All Removable Components are inherently Replaceable.A PhysicalComponent 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 fan Component may be designed to be HotSwappable. All HotSwappable Components are inherently Removable and Replaceable. 2.6.0A Component is typically contained by a PhysicalPackage, such as a Chassis or Card. The PackagedComponent association makes this relationship explicit. In the first sentence, the word, 'typically', is used. This is because a Component may be removed from, or not yet inserted into, its containing Package (ie, the Removable boolean is TRUE). Therefore, a Component may not always be associated with a container.truetrue1The PhysicalPackage that contains Component(s).GroupComponentMIB.IETF|Entity-MIB.entPhysicalContainedIntruetrueThe PhysicalComponent which is contained in the Package.PartComponenttrue 2.6.0The Chip class represents any type of integrated circuit hardware, including ASICs, processors, memory chips, etc.The implementation form factor for the Chip. For example, values such as SIMM (7), TSOP (9) or PGA (10) can be specified.01234567891011121314151617181920212223UnknownOtherSIPDIPZIPSOJProprietarySIMMDIMMTSOPPGARIMMSODIMMSRIMMSMDSSMPQFPTQFPSOICLCCPLCCBGAFPBGALGA 2.7.0PhysicalMemory is a subclass of CIM_Chip, representing low level memory devices - SIMMS, DIMMs, raw memory chips, etc.FormFactorMIF.DMTF|Memory Device|005.6The implementation form factor for the Chip. For example, values such as SIMM (7), TSOP (9) or PGA (10) can be specified.01234567891011121314151617181920212223UnknownOtherSIPDIPZIPSOJProprietarySIMMDIMMTSOPPGARIMMSODIMMSRIMMSMDSSMPQFPTQFPSOICLCCPLCCBGAFPBGALGAThe type of PhysicalMemory.01234567891011121314151617181920UnknownOtherDRAMSynchronous DRAMCache DRAMEDOEDRAMVRAMSRAMRAMROMFlashEEPROMFEPROMEPROMCDRAM3DRAMSDRAMSGRAMRDRAMDDRMIF.DMTF|Memory Device|005.9Total width, in bits, of the PhysicalMemory, including check or error correction bits. If there are no error correction bits, the value in this property should match that specified for DataWidth.BitsMIF.DMTF|Memory Device|005.7Data width of the PhysicalMemory, in bits. A data width of 0 and a TotalWidth of 8 would indicate that the Memory is solely used to provide error correction bits.BitsMIF.DMTF|Memory Device|005.8The speed of the PhysicalMemory, in nanoseconds.NanoSecondsMIF.DMTF|Memory Device|005.24The total capacity of this PhysicalMemory, in bytes.BytesMIF.DMTF|Memory Device|005.5A string identifying the physically labeled bank where the Memory is located - for example, 'Bank 0' or 'Bank A'.64MIF.DMTF|Memory Device|005.4Specifies the position of the PhysicalMemory in a 'row'. For example, if it takes two 8-bit memory devices to form a 16-bit row, then a value of '2'means that this Memory is the second device. 0 is an invalid value for this property.MIF.DMTF|Memory Device Mapped Addresses|001.6The position of this PhysicalMemory in an interleave. 0 indicates non-interleaved. 1 indicates the first position, 2 the second position and so on. For example, in a 2:1 interleave, a value of '1' would indicate that the Memory is in the 'even' position.MIF.DMTF|Memory Device Mapped Addresses|001.7 2.6.0PhysicalMemory can be located on HostingBoards, adapter Cards, etc. This association explicitly defines this relationship of Memory to Cards.truetrue1The Card that includes or 'contains' Memory.GroupComponentMIB.IETF|Entity-MIB.entPhysicalContainedIntruetrueThe PhysicalMemory which is located on the Card.PartComponenttrue 2.6.0The PhysicalMedia class represents any type of documentation or storage medium, such as tapes, CDROMs, etc. This class is typically used to locate and manage Removable Media (versus Media sealed with the MediaAccessDevice, as a single Package, as is the case with hard disks). However, 'sealed' Media can also be modeled using this class, where the Media would then be associated with the PhysicalPackage using the PackagedComponent relationship.The number of bytes that can be read from or written to a Media. This property is not applicable to "Hard Copy" (documentation) or cleaner Media. Data compression should not be assumed, as it would increase the value in this property. For tapes, it should be assumed that no filemarks or blank space areas are recorded on the Media.BytesSpecifies the type of the PhysicalMedia, as an enumerated integer. The MediaDescription property is used to provide more explicit definition of the Media type, whether it is pre-formatted, compatability features, etc.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 Small Tape - DST MediumTape - DST LargeCIM_PhysicalMedia.MediaDescriptionAdditional detail related to the MediaType enumeration. For example, if value 3 ("QIC Cartridge") is specified, this property could indicate whether the tape is wide or 1/4 inch, whether it is pre-formatted, whether it is Travan compatible, etc.CIM_PhysicalMedia.MediaTypeBoolean specifying whether the Media is currently write protected by some kind of physical mechanism, such as a protect tab on a floppy diskette.Boolean indicating that the PhysicalMedia is used for cleaning purposes and not data storage.Size of the Media in inches. For example, '3.5' would be entered for a 3.5 inch disk, or '12' would be entered for a 12 inch optical disk. On the other hand, '0.5' would be defined for a 1/2 inch tape.InchesFor removable Media, the maximum number of times that the Media can be mounted before it should be retired. For cleaner Media, this is the maximum number of Drive cleans that can be performed. For nonremovable Media, such as hard disks, this property is not applicable and should be set to 0.For removable or cleaner Media, the number of times that the Media has been mounted for data transfer or to clean a Drive. For nonremovable Media, such as hard disks, this property is not applicable and should be set to 0.trueCIM_PhysicalMedia.MaxMountsBoolean indicating that the Media has two recording sides (TRUE) or only a single side (FALSE). Examples of dual sided Media include DVD-ROM and some optical disks. Examples of single sided Media are tapes and CD-ROM.One or more strings on 'labels' on the PhysicalMedia. The format of the labels and their state (readable, unreadable, upside-down) are indicated in the LabelFormats and LabelStates array properties.IndexedCIM_PhysicalMedia.LabelStatesCIM_PhysicalMedia.LabelFormatsAn array of enumerated integers describing the states of each of the labels on a PhysicalMedia. 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.Indexed012OK/ReadableUnreadableUpside DownCIM_PhysicalMedia.PhysicalLabelsAn array of enumerated integers describing the formats of each of the labels on a PhysicalMedia. 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.Indexed012345BarcodeRadio Frequency IdentificationOCR (Optical Character Recognition)MICR (Magnetic Ink Character Recognition)7 Character Barcode9 Character BarcodeCIM_PhysicalMedia.PhysicalLabelsFor removable or cleaner Media, the date and time that the Media was last mounted. For nonremovable Media, such as hard disks, this property has no meaning and is not applicable.For removable or cleaner Media, the total time (in seconds) that the Media has been mounted for data transfer or to clean a Drive. For nonremovable Media, such as hard disks, this property is not applicable and should be set to 0.Seconds 2.6.0MemoryWithMedia indicates that Memory is associated with a PhysicalMedia and its cartridge. The Memory provides media identification and also stores user-specific data. trueAntecedentThe Memory associated with PhysicalMedia. trueDependentThe PhysicalMedia.true 2.6.0Within a StorageLibrary, all Media should be accounted for, and be present in some Storage Location. This relationship is made explicit by the PhysicalMediaInLocation association.In addition, one can determine if a Location is empty or full based on whether this association exists for the StorageMediaLocation.trueAntecedent1The StorageMediaLocation which holds the PhysicalMedia.trueDependentThe Media in the Location.trueAn enumeration expressing which 'Side' of the Media is facing up. Since sides can be named by various schemes (0/1 or A/B), both schemes are expressed in the Values array of this property. Also, the value 5 ("Not Applicable" describes that orientation is not pertinent for this Media.012345UnknownSide 0Side 1Side ASide BNot ApplicableThe date and time that the Media was last placed into the referenced Location. 2.6.0The PhysicalTape class represents additional data for a Tape Media. Information on the tape length and whether it must be unloaded from BOT are properties of this class.The physical length of the Tape in feet.FeetBoolean set to TRUE if the Tape can be unloaded at any position on the Media. It is set to FALSE if the tape must be at a certain position for unload - such as at the beginning of tape (BOT) area, or at mid-tape point for TapeDrives with mid-tape load. 2.6.0 In a StorageLibrary or repository for PhysicalMedia, it is reasonable that a specific Media always be placed in a specific Location (rather than anywhere in the repository/Library). The default location for a PhysicalMedia is called its 'home'. This information is expressed by the HomeForMedia dependency association. (Note that a PhysicalMedia can have at most one 'home', and a StorageMediaLocation can be 'home' to at most one Media.)trueAntecedent1The Location that is 'home' to a piece of PhysicalMedia.trueDependent1The PhysicalMedia whose 'home' or default Location is defined.true 2.6.0The ReplacementSet class aggregates PhysicalElements that must be 'replaced' or 'FRUed' together. For example, when replacing a memory card, the component memory chips could be removed and replaced as well. Or, a set of memory chips may be specified to be replaced or upgraded together using this association.true256Name is a free-form string defining a label for the ReplacementSet. It is the key for the object. truetrue2.6.0ParticipatesInSet indicates which PhysicalElements should be replaced together.truetrueThe ReplacementSet.trueThe PhysicalElement which should be replaced with other Elements, as a Set. true2.7.0PhysicalCapacity is an abstract class describing a PhysicalElement's minimum/maximum requirements and ability to support different types of hardware. For example, minimum and maximum memory requirements can be modeled as a subclass of CIM_PhysicalCapacity. Note that the items described in subclasses of PhysicalCapacity, for example the class ConfigurationCapacity, are either directly PhysicalElements (such as I/O slots or storage library magazines) or closely associated to PhysicalElements via the Realizes relationship (i.e., LogicalDevices such as batteries or processors).256The Name property defines the label by which the PhysicalCapacity object is known. When subclassed, the Name property can be overridden to be a Key property. true2.6.0ElementCapacity associates a PhysicalCapacity object with one or more PhysicalElements. It serves to associate a description of min/max hardware requirements or capabilities (stored as a kind of PhysicalCapacity), with the PhysicalElements being described.truePhysicalCapacity describes the minimum and maximum requirements, and ability to support different types of hardware for a PhysicalElement.true1The PhysicalElement being described. 2.6.0MemoryCapacity describes the type of Memory that can be installed on a PhysicalElement and its minimum/maximum configurations. Information on what memory is currently 'installed', versus an Element's min/max requirements, is located in instances of the PhysicalMemory class.NametrueThe inherited Name serves as a part of the MemoryCapacity object key.256trueThe type of memory. This is a part of the object key. Values correspond to the list of possible memory types in the PhysicalMemory class.01234567891011121314151617181920UnknownOtherDRAMSynchronous DRAMCache DRAMEDOEDRAMVRAMSRAMRAMROMFlashEEPROMFEPROMEPROMCDRAM3DRAMSDRAMSGRAMRDRAMDDRCIM_PhysicalMemory.MemoryTypeMinimum amount of memory, in Kbytes, that is needed for the associated PhysicalElement to operate correctly. KiloBytesMaximum amount of memory, in Kbytes, that can be supported by the associated PhysicalElement. KiloBytes 2.6.0ConfigurationCapacity provides information on the minimum and maximum numbers of power supplies, fans, disk drives, etc. that can be connected to or placed on/into a PhysicalElement (and the number that must be connected/added/removed at a time). The PhysicalElement whose configuration is described is identified using the ElementCapacity association, inherited from PhysicalCapacity. The object whose capacities are indicated (ie, the power supply or fan) is identified in the ObjectType property of this class. Since the same min/max configurations can apply to multiple instances, this class is not defined as 'weak'. Examples of the use of the ConfigurationCapacity class are to describe that a 'control unit' Chassis may be connected to (at most) 4 other I/O chassis, or to describe what a StorageLibrary's cabinet may contain. Continuing the latter example, a particular StorageLibrary's cabinet might hold a minimum of 3 and a maximum of 9 TapeDrives, and a minimum of 88 and a maximum of 264 StorageMediaLocations ("Slots"). This information would be described in two instances of ConfigurationCapacity, both associated to the StorageLibrary's PhysicalPackage. This class does NOT represent the tradeoffs that are likely to be required of one resource for another. It simply represents capacities. In the case of the StorageLibrary, there may be only 2 valid configurations - 9 TapeDrives with 88 Slots, or 3 TapeDrives with 264 Slots. This class only conveys that 'up to' 9 Drives and 'up to' 264 slots may be available and are supported.NametrueThe inherited Name serves as a part of the ConfigurationCapacity object key.256trueThe type of object (power supply, fan, disk drive, ...) whose capacities are indicated. This information is part of the class' key.0123456789101112131415161718192021222324OtherProcessorsPower SuppliesFansBatteriesI/O SlotsMemory SlotsMediaAccessDevices (Drives)StorageMediaLocation SlotsStorageMediaLocation MagazinesStorageMediaLocation PanelsStorageMediaLocation InterLibrary PortsStorageMediaLocation Limited Access PortsDoorsMediaTransferDevice PickersMediaTransferDevice ChangersLabelReadersContained ChassisConnected ChassisConnected FramesFront Side I/O SlotsBack Side I/O SlotsCache MemoryNVS MemoryVolatile MemoryCIM_ConfigurationCapacity.OtherTypeDescriptionA string describing the object type - used when the ObjectType property is set to 0 ("Other"). OtherTypeDescription should be set to NULL when ObjectType is any value other than 0.64CIM_ConfigurationCapacity.ObjectTypeMinimum number of Elements of type, ObjectType, that must be installed.Maximum number of Elements of type, ObjectType, that may be installed.Increment in which Elements must be added or removed. 2.7.0A class derived from System that is a special collection of ManagedSystemElements. This collection provides compute capabilities and serves as aggregation point to associate one or more of the following elements: FileSystem, OperatingSystem, Processor and Memory (Volatile and/or NonVolatile Storage).NameFormatThe ComputerSystem object and its derivatives are Top Level Objects of CIM. They provide the scope for numerous components. Having unique System keys is required. The NameFormat property identifies how the ComputerSystem Name is generated. The NameFormat ValueMap qualifier defines the various mechanisms for assigning the name. Note that another name can be assigned and used for the ComputerSystem that better suit a business, using the inherited ElementName property.OtherIPDialHIDNWAHWAX25ISDNIPXDCCICDE.164SNAOID/OSIWWN64256IndexedOtherIdentifyingInfo captures additional data, beyond System Name information, that could be used to identify a ComputerSystem. One example would be to hold the Fibre Channel World-Wide Name (WWN) of a node. Note that if only the Fibre Channel name is available and is unique (able to be used as the System key), then this property would be NULL and the WWN would become the System key, its data placed in the Name property.CIM_ComputerSystem.IdentifyingDescriptionsIndexedAn 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.CIM_ComputerSystem.OtherIdentifyingInfo Enumeration indicating whether the ComputerSystem is a special-purpose System (ie, dedicated to a particular use), versus being 'general purpose'. For example, one could specify that the System is dedicated to "Print" (value=11) or acts as a "Hub" (value=8). A clarification is needed with respect to the value 17 ("Mobile User Device"). An example of a dedicated user device is a mobile phone or a barcode scanner in a store that communicates via radio frequency. These systems are quite limited in functionality and programmability, and are not considered 'general purpose' computing platforms. Alternately, an example of a mobile system that is 'general purpose' (i.e., is NOT dedicated) is a hand-held computer. Although limited in its programmability, new software can be downloaded and its functionality expanded by the user.01234567891011121314151617Not DedicatedUnknownOtherStorageRouterSwitchLayer 3 SwitchCentral Office SwitchHubAccess ServerFirewallPrintI/OWeb CachingManagementBlock ServerFile ServerMobile User DeviceCIM_ComputerSystem.OtherDedicatedDescriptionsA string describing how or why the system is dedicated when the Dedicated array includes the value 2, "Other".CIM_ComputerSystem.DedicatedIf enabled (value = 4), the ComputerSystem can be reset via hardware (e.g. the power and reset buttons). If disabled (value = 3), hardware reset is not allowed. In addition to Enabled and Disabled, other Values for the property are also defined - "Not Implemented" (5), "Other" (1) and "Unknown" (2).12345OtherUnknownDisabledEnabledNot ImplementedMIF.DMTF|System Hardware Security|001.4CIM_PowerManagementCapabilities.PowerCapabilitiesAn enumerated array describing the power management capabilities of the ComputerSystem. 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 SupportedMIF.DMTF|System Power Controls|001.2CIM_PowerManagementService.SetPowerStateSets the power state of the computer. The use of this method has been deprecated. Instead, use the SetPowerState method in the associated PowerManagementService class.true12345678Full PowerPower Save - Low Power ModePower Save - StandbyPower Save - OtherPower CyclePower OffHibernateSoft Offtrue 2.7.2Indicates general capabilities of a ComputerSystem node, such as the ability to support a battery (and be portable), and ECC memory. To tie these capabilities to a ComputerSystem instance, the ElementCapabilities association is used.trueEnumeration indicating whether a battery is installable/supportable on this System. This is independent of whether one is currently installed. The latter is indicated by an instance of the CIM_Battery class associated using the SystemDevice relationship.023UnknownBattery SupportedBattery Not SupportedtrueEnumeration indicating whether ECC single or multi-bit memory is supported on this node. This is independent of whether ECC memory is actually installed. The latter is indicated by an instance of CIM_PhysicalMemory that 'Realizes' the CIM_Memory of the System (associated using SystemDevice).023UnknownSingle-bit ECCMulti-bit ECCMIF.DMTF|Physical Memory|002.10 true2.7.0A ComputerSystem can aggregate another ComputerSystem. This association can be used to model MPP Systems with workstation frontends, an I2O subsystem embedded in a UnitaryComputerSystem, or a System that splits functionality between two processors, potentially running different OperatingSystems. For example, if a CISC Processor and its associated OperatingSystem, are used for user interface and file support, and a RISC Processor and its OS are used for complex mathematical operations, this could be modeled as two ComputerSystems where one aggregates the other. In some cases, this could be modeled as a Cluster. The difference is the focus of the relationship. ComponentCS represents that unique and distinct ComputerSystems are aggregated by a higher level CS object. However, each of the component CSs are still distinguishable entities and are only viewed as such. Alternately, with a Cluster, the ComputerSystems that participate in it are inconsequential, when viewed through the 'Cluster System'. When instantiating or subclassing the ComponentCS relationship, care should be taken that the component ComputerSystem meets the definitional requirements of a ComputerSystem - ie, a functional whole that provides compute capabilities and aggregates System Devices, an OperatingSystem, etc.truetrueThe ComputerSystem that contains and/or aggregates other Systems.GroupComponenttruetrueThe contained (Sub)ComputerSystem.PartComponenttrue 2.7.0A class derived from ComputerSystem that represents a Desktop, Mobile, NetPC, Server or other type of a single node Computer System.This object contains the data needed to find either the initial load device (its key) or the boot service to request the operating system to start up. In addition, the load parameters (ie, a pathname and parameters) may also be specified.This object contains the data identifying either the initial load device (its key) or the boot service that requested the last operating system load. In addition, the load parameters (ie, a pathname and parameters) may also be specified.MIB.IETF|HOST-RESOURCES-MIB.hrSystemInitialLoadDeviceMIB.IETF|HOST-RESOURCES-MIB.hrSystemInitialLoadParametersMIF.DMTF|Host System|001.3CIM_PowerManagementCapabilitiesWhen TRUE, indicates that the computer can be power managed. The use of this property has been deprecated. Instead, the existence of an associated PowerManagementCapabilities class (associated using the ElementCapabilites relationship) indicates that power management is supported.Indicates the current power state of the ComputerSystem and its associated OperatingSystem. Regarding the Power Save states, these are defined as follows: Value 4 ("Power Save - Unknown") indicates that the System is known to be in a power save mode, but its exact status in this mode is unknown; 2 ("Power Save - Low Power Mode") indicates that the System is in a power save state but still functioning, and may exhibit degraded performance; 3 ("Power Save - Standby") describes that the System is not functioning but could be brought to full power 'quickly'; value 7 ("Power Save - Warning") indicates that the ComputerSystem is in a warning state, though also in a power save mode; and, values 8 and 9 describe the ACPI "Hibernate" and "Soft Off" states.0123456789UnknownFull PowerPower Save - Low Power ModePower Save - StandbyPower Save - UnknownPower CyclePower OffPower Save - WarningPower Save - HibernatePower Save - Soft OffThe event that caused the System to power up. This information is available in SMBIOS, in the Type 1 structure, the Wake Up Type attribute.012345678ReservedOtherUnknownAPM TimerModem RingLAN RemotePower SwitchPCI PME#A/C Power Restored 2.7.0A Partition is an instance of a UnitaryComputerSystem (with its own OperatingSystem and Devices dedicated to the Partition) that is supported by underlying hardware and software. A Partition is not a virtualization of a ComputerSystem, but the segmentation of the System's compute capabilities. Partitions can run independent copies of possibly different OperatingSystems and have dedicated Devices. The 'real', underlying System (perhaps a Cluster or another UnitaryComputerSystem) aggregates its Partitions. These semantics are described by the SystemPartition association.truetruetrue1The 'underlying' ComputerSystem that hosts a Partition.GroupComponenttruetrueThe System Partition.PartComponenttrue 2.6.0A class derived from ComputerSystem that represents the ability to virtualize or emulate another ComputerSystem.A string describing the type of System or hardware platform that is virtualized. OperatingSystem information is obtained via the RunningOS inherited from ComputerSystem. 2.6.0A VirtualComputerSystem is hosted on another ComputerSystem. This association makes that relationship explicit.trueAntecedent1The hosting ComputerSystem.trueDependentThe VirtualComputerSystem.true 2.6.0A class derived from ComputerSystem that 'is made up of' two or more ComputerSystems which operate together as an atomic, functional whole to increase the performance, resources and/or RAS (Reliability, Availability and Serviceability) of the component ComputerSystems, related to some aspects of these ComputerSystems.Interconnect is a free form string that describes the interconnection mechanism for the Cluster.InterconnectAddress indicates the address of the Cluster System, which is dependent on the interconnection scheme. If no address is available or applicable, a null string should be used.The cluster types. This specifies whether the cluster is for failover (value=2), performance (3), etc. The values which can be specified are not mutually exclusive. Thus, Types is an array.0123456UnknownOtherFailoverPerformanceDistributed OSNode GroupingSysPlexIndicates the maximum number of nodes that may participate in the Cluster. If unlimited, enter 0.Indicates the state of the Cluster. The cluster can be defined to be on-line (value=2), off-line (3), in a degraded mode of operation (4) or unavailable (5).012345UnknownOtherOn-lineOff-lineDegradedUnavailable 2.6.0A Cluster is composed of two or more ComputerSystems, operating together. A ComputerSystem may participate in multiple Clusters. When first establishing or bringing up a Cluster, only one ComputerSystem may be defined as participating in it. Therfore, the cardinality of the association for the ComputerSystem reference is Min (1). trueAntecedent1The ComputerSystem which participates in the Cluster. trueDependentThe Cluster.trueStateOfNode indicates the condition of the participating ComputerSystem in the Cluster. For example, one value is "Joining" (2).0123456UnknownOtherJoiningPausedAvailableUnavailableDegradedRoleOfNode indicates whether the Cluster nodes are peers (value = 2), connected in a master-slave/primary-secondary relationship (values = 3 for primary, 4 for secondary), available in a standby configuration (5) or of some other (1) or unknown (0) relationship. In a System/390 environment, the nodes are identified as "Base Plex" (value=6) or "Enhanced Plex" (value=7).01234567UnknownOtherPeerPrimarySecondaryStandbyBase PlexEnhanced Plex 2.6.0ClusteringService represents the functionality provided by a Cluster. For example, failover functionality may be modeled as a Service of a failover Cluster.AddNode brings a new ComputerSystem into a Cluster. The node to be added is specified as a parameter to the method. The return value should be 0 if the ComputerSystem is successfully added, 1 if the method is not supported 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.trueEvictNode removes a ComputerSystem from a Cluster. The node to be evicted is specified as a parameter to the method. The return value should be 0 if the ComputerSystem is successfully evicted, 1 if the method is not supported 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.true 2.6.0A representation of the access points of a ClusteringService. 2.6.0ClusterServiceAccessBySAP is the relationship between a ClusteringService and its access points.trueThe ClusteringService.AntecedenttrueAn access point for the ClusteringService.Dependenttrue 2.6.0HostedClusterService defines the hosting Cluster for a ClusteringService. Since this relationship is subclassed from HostedService, it inherits the scoping/naming scheme defined for Service - where a Service is weak to its hosting System. In this case, a ClusteringService must be weak to its hosting Cluster System.true11The Cluster.AntecedenttrueThe ClusteringService that is hosted on the Cluster.Dependenttruetrue 2.6.0HostedClusterSAP defines the hosting ComputerSystem for a ClusteringSAP. Since this relationship is subclassed from HostedAccessPoint, it inherits the scoping/naming scheme defined for AccessPoint - where an AccessPoint is weak to its hosting System. In this case, a ClusteringSAP must be weak to its hosting ComputerSystem.true11The ComputerSystem.AntecedenttrueThe ClusteringSAP that is hosted on the ComputerSystem.Dependenttruetrue 2.7.0Similar to the way that LogicalDevices are 'Realized' by PhysicalElements, UnitaryComputerSystems are realized in one or more PhysicalPackages. The ComputerSystemPackage association explicitly defines this relationship.trueThe PhysicalPackage(s) that realize a UnitaryComputerSystem.AntecedenttrueThe UnitaryComputerSystem.DependenttrueA Gloabally Unique Identifier for the System's Package. 2.7.0A file or dataset store local to a System (such as a ComputerSystem or an ApplicationSystem) or remotely mounted from a file server.CIM_System.CreationClassNametrue256The scoping System's CreationClassName. Note that this class was originally defined in the scope of a ComputerSystem, and was later allowed to be scoped by any System (for example, a computer or application system). Unfortunately, the property name, CSCreationClassName, could not be changed (for example, to SystemCreationClassName) without deprecating the class. This change was not deemed critical to the semantics and therefore did not merit deprecation. So, the property name remains.CIM_System.Nametrue256The scoping System's Name. Note that this class was originally defined in the scope of a ComputerSystem, and was later allowed to be scoped by any System (for example, a computer or application system). Unfortunately, the property name, CSName, could not be changed (for example, to SystemName) without deprecating the class. This change was not deemed critical to the semantics and therefore did not merit deprecation. So, the property name remains.true256CreationClassName 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.Nametrue256The inherited Name serves as key of a FileSystem instance within a ComputerSystem.Path name or other information defining the root of the FileSystem.MIB.IETF|HOST-RESOURCES-MIB.hrFSMountPointMIF.DMTF|Host File System|001.2FileSystems can read/write data in blocks which are defined independently of the underlying StorageExtents. This property captures the FileSystem's block size for data storage and retrieval.BytesThe FileSystemSize property stores the total size of the FileSystem in bytes. If unknown, enter 0.BytesMIF.DMTF|Host File System|001.13trueAvailableSpace indicates the total amount of free space for the FileSystem, in bytes. If unknown, enter 0.BytesMIF.DMTF|Host File System|001.14MIF.DMTF|Partition|002.4Indicates that the FileSystem is designated as read only.MIB.IETF|HOST-RESOURCES-MIB.hrFSAccessMIF.DMTF|Host File System|001.5A free form string indicating the algorithm or tool used to encrypt the FileSystem. If it is not possible or not desired to describe the encryption scheme (perhaps for security reasons), recommend using the following words: "Unknown" to represent that it is not known whether the FileSystem is encrypted or not, "Encrypted" to represent that the FileSystem is encrypted but either its encryption scheme is not known or not disclosed, and "Not Encrypted" to represent that the FileSystem is not encrypted.MIF.DMTF|Partition|002.8A free form string indicating the algorithm or tool used to compress the FileSystem. If it is not possible or not desired to describe the compression scheme (perhaps because it is not known), recommend using the following words: "Unknown" to represent that it is not known whether the FileSystem is compressed or not, "Compressed" to represent that the FileSystem is compressed but either its compression scheme is not known or not disclosed, and "Not Compressed" to represent that the FileSystem is not compressed.MIF.DMTF|Partition|002.7Indicates that case sensitive file names are supported.Indicates that the case of file names are preserved.Array defining the character sets or encoding supported by the FileSystem. For example, the values, "ASCII" (2) or "ISO2022" (4), may be specified.012345678UnknownOtherASCIIUnicodeISO2022ISO8859Extended UNIX CodeUTF-8UCS-2Integer indicating the maximum length of a file name within the FileSystem. 0 indicates that there is no limit on file name length.The minimum file allocation size (an integral number of blocks), imposed by the FileSystem. (The size of a block is specified in the BlockSize property for the FileSystem.) Minimum allocation size is the smallest amount of storage allocated to a LogicalFile by the FileSystem. This is not a mandatory minimum allocation for all FileSystems. Under stress conditions, some FileSystems may allocate storage in amounts smaller than the ClusterSize.String describing the type of FileSystem and therefore, its conventions. For example, "NTFS" or "S5" may be listed as well as any additional information on the FileSystem's implementation. Since various flavors of FileSystems (like S5) exist, this property is defined as a string.MIF.DMTF|Partition|002.6MIF.DMTF|Host File System|001.4 2.6.0A class derived from FileSystem that represents the file store controlled by a ComputerSystem through local means (e.g., direct device driver access). In this case, the file store is managed directly by the ComputerSystem without the need for another computer to act as a file server. This definition does not breakdown in the case of a Clustered File System. In this scenario, the FileSystem is a LocalFileSystem, weak to the Cluster. 2.6.0A class derived from FileSystem that represents access of the FileSystem via a network-related service. In this case, the file store is hosted by a computer, acting as a file server. For example, the file store for an NFS FileSystem is typically NOT on a ComputerSystem's locally controlled media, nor is it directly accessed through a device driver. Subclasses of RemoteFileSystem contain client-side configuration information related to the access of the FileSystem. 2.6.0A class derived from RemoteFileSystem representing that the FileSystem is mounted, using the NFS protocol, from a ComputerSystem. The properties of the NFS object deal with the operational aspects of the mount and represent the client-side configuration for NFS access. The FileSystemType (inherited from FileSystem) should be set to indicate the type of this FileSystem as it appears to the client.If set to true: Once the FileSystem is mounted, NFS requests are retried until the hosting System responds. If set to false: Once the FileSystem is mounted, an error is returned if the hosting System does not respond.If set to true: Retries are performed in the foreground. If set to false: If the first mount attempt fails, retries are performed in the background.If set to true: Interrupts are permitted for hard mounts. If set to false: Interrupts are ignored for hard mounts.Maximum number of mount failure retries allowed.Maximum number of NFS retransmissions allowed.NFS timeout in tenths of a second.Tenths of SecondsRead buffer size in bytes.BytesWrite buffer size in bytes.BytesThe remote ComputerSystem's (ie, the NFS File 'Server's) UDP port number.If set to true: Control attribute caching is enabled. If set to false: Control attribute caching is disabled.Minimum number of seconds that cached attributes are held after file modification.SecondsMaximum number of seconds that cached attributes are held after file modification.SecondsMinimum number of seconds that cached attributes are held after directory update.SecondsMaximum number of seconds that cached attributes are held after directory update.Seconds 2.6.0A LogicalFile is a named collection of data or executable code, or represents a LogicalDevice or Directory. It is located within the context of a FileSystem, on a StorageExtent.CIM_FileSystem.CSCreationClassNametrue256The scoping ComputerSystem's CreationClassName.CIM_FileSystem.CSNametrue256The scoping ComputerSystem's Name.CIM_FileSystem.CreationClassNametrue256The scoping FileSystem's CreationClassName.CIM_FileSystem.Nametrue256The scoping FileSystem's Name.true256CreationClassName 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.Nametrue1024The inherited Name serves as part of the key of a LogicalFile instance within a FileSystem. A unique identifier (such as a full path name) is required as a Name value. Since Files are weak to their FileSystem (and not to a Directory which would provide a more granular naming algorithm), care must be taken to make LogicalFile's Name unique for a given CreationClassName and FileSystem. A full path name is one way to do this.trueSize of the File in bytes.BytesFile's creation date.Time that the File was last modified.Time that the File was last accessed.Boolean indicating that the File can be read.Boolean indicating that the File can be written.Indicates the file is executable.A free form string indicating the algorithm or tool used to compress the LogicalFile. If it is not possible or not desired to describe the compression scheme (perhaps because it is not known), recommend using the following words: "Unknown" to represent that it is not known whether the LogicalFile is compressed or not, "Compressed" to represent that the File is compressed but either its compression scheme is not known or not disclosed, and "Not Compressed" to represent that the LogicalFile is not compressed.A free form string indicating the algorithm or tool used to encrypt the LogicalFile. If it is not possible or not desired to describe the encryption scheme (perhaps for security reasons), recommend using the following words: "Unknown" to represent that it is not known whether the LogicalFile is encrypted or not, "Encrypted" to represent that the File is encrypted but either its encryption scheme is not known or not disclosed, and "Not Encrypted" to represent that the LogicalFile is not encrypted.trueInteger indicating the number of 'file opens' that are currently active against the File. 2.6.0DataFile is a type of LogicalFile that is a named collection of data or executable code. 2.6.0Directory is a type of File that logically groups Files 'contained' in it, and provides path information for the grouped Files. 2.6.0DeviceFile is a special type of LogicalFile that represents a Device. This convention is useful for some operating systems that manage devices using a byte stream I/O model. The LogicalDevice that is associated with this file is specified using the DeviceAccessedByFile relationship. 2.6.0FIFOPipeFile is a special type of LogicalFile that represents an interprocess FIFO (sometimes referred to as a "named pipe"). Operating systems use this convention to manage interprocess communication through processes reading and writing the FIFO. The FIFO can be accessed by unrelated processes, in contrast to the more well-known command line redirection mechanism (e.g. UNIX's 'ps -eaf | grep foo', also known as an "unnamed pipe"). An exemplary operating system implementation (using the FIFO concept) is the UNIX S_IFIFO file type. 2.6.0This class is a special type of LogicalFile that represents a Symbolic Link. This convention is useful for some operating systems that want to represent a single file in multiple places or a single file that is represented via multiple names.trueThe target file of the symbolic link. 2.6.0Specifies the LogicalDevice that is associated with, and accessed using the referenced DeviceFile.trueAntecedentThe DeviceFile.trueDependent1The Device that is accessed using the DeviceFile.true true2.7.0Specifies the hierarchical arrangement of LogicalFiles in a Directory.truetrueGroupComponent1The Directory.truetruePartComponentThe LogicalFile 'contained within' the Directory.true 2.6.0An association between a FileSystem and a Directory which indicates that the Directory is being attached to the FileSystem. The semantics of this relationship require that the mounted Directory be contained by a FileSystem (via the FileStorage association) that is different from the FileSystem referenced as the Dependent. The Directory's containing FileSystem could be either local or remote. For example, a LocalFileSystem on a Solaris ComputerSystem can mount a Directory from the FileSystem accessed via the machine's CDROM drive, i.e., another LocalFileSystem. On the other hand, in a 'remote' case, the Directory is first exported by its FileSystem, which is hosted on another ComputerSystem acting (for example) as a file server. In order to distinguish these two types of Mount, it is recommended that a CIM_Export association always be defined for the remotely accessed/mounted Directories.trueAntecedent1The Directory mounted.trueDependentThe FileSystem the Directory is mounted on.true true2.6.0An association between a LocalFileSystem and its Directories indicating that the specified Directories are available for mount. When exporting an entire FileSystem, the Directory should reference the topmost directory of the FileSystem.true1The LocalFileSystem.trueThe Directory exported for mount.Name under which the Directory is exported. true2.7.0A link between the System (such as a Computer or ApplicationSystem) and the FileSystem that is a part of it.truetrue11The System that hosts the FileSystem.GroupComponenttruetruetrueThe FileSystem that is part of the System and hosted on it.PartComponenttrue true2.7.0A link between the FileSystem and the LogicalFile(s) addressed through this FileSystem.truetrueGroupComponent11The FileSystem.truetruePartComponenttrueThe LogicalFile stored in the context of the FileSystem.true 2.6.0An association between a FileSystem and the StorageExtent where it is located. Typically, a FileSystem ResidesOn a LogicalDisk.trueAntecedentThe StorageExtent.trueDependentThe FileSystem that is located on the StorageExtent.true 2.7.0An OperatingSystem is software/firmware that makes a ComputerSystem's hardware usable, and implements and/or manages the resources, file systems, processes, user interfaces, services, ... available on the ComputerSystem.CIM_ComputerSystem.CreationClassNametrue256The scoping ComputerSystem's CreationClassName.CIM_ComputerSystem.Nametrue256The scoping ComputerSystem's Name.true256CreationClassName 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.Nametrue256The inherited Name serves as key of an OperatingSystem instance within a ComputerSystem.MIF.DMTF|Operating System|001.2A integer indicating the type of OperatingSystem.01234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768UnknownOtherMACOSATTUNIXDGUXDECNTTru64 UNIXOpenVMSHPUXAIXMVSOS400OS/2JavaVMMSDOSWIN3xWIN95WIN98WINNTWINCENCR3000NetWareOSFDC/OSReliant UNIXSCO UnixWareSCO OpenServerSequentIRIXSolarisSunOSU6000ASERIESTandemNSKTandemNTBS2000LINUXLynxXENIXVMInteractive UNIXBSDUNIXFreeBSDNetBSDGNU HurdOS9MACH KernelInfernoQNXEPOCIxWorksVxWorksMiNTBeOSHP MPENextStepPalmPilotRhapsodyWindows 2000DedicatedOS/390VSETPFWindows (R) MeCaldera Open UNIXOpenBSDNot ApplicableWindows XPz/OSCIM_OperatingSystem.OtherTypeDescriptionCIM_SoftwareElement.TargetOperatingSystemA string describing the manufacturer and OperatingSystem type - used when the OperatingSystem property, OSType, is set to 1 or 59 ("Other" or "Dedicated"). The format of the string inserted in OtherTypeDescription should be similar in format to the Values strings defined for OSType. OtherTypeDescription should be set to NULL when OSType is any value other than 1 or 59.64CIM_OperatingSystem.OSTypeA string describing the Operating System's version number. The format of the version information is as follows: <Major Number>.<Minor Number>.<Revision> or <Major Number>.<Minor Number>.<Revision Letter>.MIF.DMTF|Operating System|001.3Time when the OperatingSystem was last booted.MIF.DMTF|General Information|001.5OperatingSystem's notion of the local date and time of day.MIB.IETF|HOST-RESOURCES-MIB.hrSystemDateMIF.DMTF|General Information|001.6CurrentTimeZone indicates the number of minutes the OperatingSystem is offset from Greenwich Mean Time. Either the number is positive, negative or zero.MinutesNumber of user licenses for the OperatingSystem. If unlimited, enter 0.Number of user sessions for which the OperatingSystem is currently storing state information.trueMIF.DMTF|Host System|001.4MIB.IETF|HOST-RESOURCES-MIB.hrSystemNumUsersNumber of process contexts currently loaded or running on the OperatingSystem.trueMIF.DMTF|Host System|001.5MIB.IETF|HOST-RESOURCES-MIB.hrSystemProcessesMaximum number of process contexts the OperatingSystem can support. If there is no fixed maximum, the value should be 0.On systems that have a fixed maximum, this object can help diagnose failures that occur when the maximum is reached.MIF.DMTF|Host System|001.6MIB.IETF|HOST-RESOURCES-MIB.hrSystemMaxProcessesTotal swap space in Kbytes. This value may be NULL (unspecified) if swap space is not distinguished from page files. However, some Operating Systems distinguish these concepts. For example, in UNIX, whole processes can be 'swapped out' when the free page list falls and remains below a specified amount.KiloBytesNumber of Kbytes of virtual memory. For example, this may be calculated by adding the amount of total RAM to the amount of paging space (ie, adding the amount of memory in/aggregated by the ComputerSystem to the property, SizeStoredInPagingFiles.KiloBytesMIF.DMTF|System Memory Settings|001.5trueNumber of Kbytes of virtual memory currently unused and available. For example, this may be calculated by adding the amount of free RAM to the amount of free paging space (ie, adding the properties, FreePhysicalMemory and FreeSpaceInPagingFiles).KiloBytesMIF.DMTF|System Memory Settings|001.6trueNumber of Kbytes of physical memory currently unused and available.KiloBytesMIF.DMTF|System Memory Settings|001.2MIF.UNIX|Host Physical Memory|6.1The total amount of physical memory (in Kbytes) available to the OperatingSystem. This value does not necessarily indicate the true amount of physical memory, but what is reported to the OperatingSystem as available to it.KiloBytesThe total number of KBytes that can be stored in the OperatingSystem's paging files. 0 indicates that there are no paging files.KiloBytesMIF.DMTF|System Memory Settings|001.3trueThe total number of KBytes that can be mapped into the OperatingSystem's paging files without causing any other pages to be swapped out. 0 indicates that there are no paging files.KiloBytesMIF.DMTF|System Memory Settings|001.4Maximum number of Kbytes of memory that can be allocated to a Process. For Operating Systems with no virtual memory, this value is typically equal to the total amount of physical Memory minus memory used by the BIOS and OS. For some Operating Systems, this value may be infinity - in which case, 0 should be entered. In other cases, this value could be a constant - for example, 2G or 4G.KiloBytesBoolean indicating whether the OperatingSystem is distributed across several ComputerSystem nodes. If so, these nodes should be grouped as a Cluster.A value that indicates the maximum processes that a user can have associate with it.Requests a reboot of the OperatingSystem. The return value should be 0 if the request was successfully executed, 1 if the request is not supported and some other value if an error occurred. In a subclass, the set of possible return codes could be specified, using a ValueMap qualifier on the method. The strings to which the ValueMap contents are 'translated' may also be specified in the subclass as a Values array qualifier.Requests a shutdown of the OperatingSystem. 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. It is up to the implementation or subclass of OperatingSystem to establish dependencies between the Shutdown and Reboot methods, and for example, to provide more sophisticated capabilities such as scheduled shutdown/reboot, 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. true2.7.0A link between the ComputerSystem and the OperatingSystem(s) installed or loaded on it. An OperatingSystem is 'installed' on a ComputerSystem, when placed on one of its StorageExtents - for example, copied to a disk drive or downloaded to Memory. Using this definition, an OperatingSystem is 'installed' on a NetPC when downloaded via the network.truetrue11The ComputerSystem.GroupComponenttruetruetrueThe OperatingSystem installed on the ComputerSystem.PartComponenttrueBoolean indicating that the OperatingSystem is the default OS for the ComputerSystem.MIF.DMTF|Operating System|001.4 2.6.0RunningOS indicates the currently executing OperatingSystem. At most one OperatingSystem can execute at any time on a ComputerSystem. 'At most one' is specified, since the ComputerSystem may not be currently booted, or its OperatingSystem may be unknown.trueAntecedent1The OperatingSystem currently running on the ComputerSystem.trueDependent1The ComputerSystem.true 2.6.0A link between the OperatingSystem and the FileSystem(s) from which this OperatingSystem is loaded. The association is many-to-many since a Distributed OS could depend on several FileSystems in order to correctly and completely load.trueAntecedentThe FileSystem from which the OperatingSystem is loaded.trueDependentThe OperatingSystem.true 2.7.0Each instance of the CIM_Process class represents a single instance of a running program. A user of the OperatingSystem will typically see a Process as an application or task. Within an OperatingSystem, a Process is defined by a workspace of memory resources and environmental settings that are allocated to it. On a multitasking System, this workspace prevents intrusion of resources by other Processes. Additionally, a Process can execute as multiple Threads, all which run within the same workspace.CIM_OperatingSystem.CSCreationClassNametrue256The scoping ComputerSystem's CreationClassName.CIM_OperatingSystem.CSNametrue256The scoping ComputerSystem's Name.CIM_OperatingSystem.CreationClassNametrue256The scoping OperatingSystem's CreationClassName.CIM_OperatingSystem.Nametrue256The scoping OperatingSystem's Name.true256CreationClassName 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.true256A string used to identify the Process. A Process ID is a kind of Process Handle.MIF.DMTF|Process Information|001.1NameThe name of the process.MIF.DMTF|Process Information|001.61024Priority indicates the urgency or importance of execution of a Process. If a priority is not defined for a Process, a value of 0 should be used.MIF.DMTF|Process Information|001.10Indicates the current operating condition of the Process. Values include ready (2), running (3), and blocked (4), among others.0123456789UnknownOtherReadyRunningBlockedSuspended BlockedSuspended ReadyTerminatedStoppedGrowingMIF.DMTF|Process Information|001.9MIF.UNIX|Process Information|13.9A string describing the state - used when the instance's ExecutionState property is set to 1 ("Other"). OtherExecutionDescription should be set to NULL when the ExecutionState property is any value other than 1.Time that the Process began executing.Time that the Process was stopped or terminated.Time in kernel mode, in milliseconds. If this information is not available, or if the operating system does not distinguish between time in kernel and in user mode, a value of 0 should be used.MilliSecondsMIF.DMTF|Process Information|001.13Time in user mode, in milliseconds. If this information is not available, a value of 0 should be used. If the operating system does not distinguish between time in kernel mode and user mode, the time should be returned in this property.MilliSecondsMIF.DMTF|Process Information|001.14trueThe amount of memory in bytes that a Process needs to execute efficiently, for an OperatingSystem that uses page-based memory management. If an insufficient amount of memory is available (< working set size), thrashing will occur. If this information is not known, NULL or 0 should be entered. If this data is provided, it could be monitored to understand a Process' changing memory requirements as execution proceeds.Bytes true2.7.0A link between the OperatingSystem and Process(es) running in the context of this OperatingSystem.truetrueGroupComponent11The OperatingSystem.truetruePartComponenttrueThe Process running in the context of the OperatingSystem.true 2.6.0A link between a Process and a DataFile indicating that the File participates in the execution of the Process.trueAntecedentThe DataFile participating in the execution of the Process.trueDependentThe Process.true true2.6.0CIM_ServiceProcess is an association used to establish relationships between Services and Processes. It is used to indicate if a Service is running in a particular Process. It is also used to indicate, via the ExecutionType property, if the Service started and is wholly responsible for the Process, or if the Service is running in an existing Process, perhaps with other unrelated Services, which is owned or started by a different entity. This association relates a Service with an externally visible system signature. trueThe Service whose Process is described by this association.trueThe Process which represents or hosts the executing Service. Enumeration indicating how the Service runs in the context of, or owns the Process. "Unknown" indicates that the ExecutionType is not known. "Other" indicates that the ExecutionType does not match any of the values in the ExecutionType enumeration. "Executes in Existing Process" indicates that the Service is hosted in a Process that already exists in the system. The lifecycle of the Service is separate from that of the Process. "Exeutes as Independent Process" indicates that the Service is responsible for the lifecycle of the Process. When the Service is started, the Process is created. For example, ServletEngines can run "InProcess" within the existing Apache processes or "OutOfProcess" in its own servlet engine process. In this case the Apache process would communicate with the servlet engine process based on the content of the request. The association may be many to many.0123UnknownOtherExecutes in Existing ProcessExecutes as Independent Process 2.7.0Threads represent the ability to execute units of a Process or task in parallel. A Process can have many Threads, each of which is weak to the Process.CIM_Process.CSCreationClassNametrue256The scoping ComputerSystem's CreationClassName.CIM_Process.CSNametrue256The scoping ComputerSystem's Name.CIM_Process.OSCreationClassNametrue256The scoping OperatingSystem's CreationClassName.CIM_Process.OSNametrue256The scoping OperatingSystem's Name.CIM_Process.CreationClassNametrue256The scoping Process' CreationClassName.CIM_Process.Handletrue256The scoping Process' Handle.true256CreationClassName 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 allow all instances of this class and its subclasses to be uniquely identified.true256A string used to identify the Thread.Priority indicates the urgency or importance of execution of a Thread. A Thread may have a different priority than its owning Process. If this information is not available for a Thread, a value of 0 should be used.Indicates the current operating condition of the Thread. Values include ready (2), running (3), and blocked (4), among others.0123456UnknownOtherReadyRunningBlockedSuspended BlockedSuspended ReadyTime in kernel mode, in milliseconds. If this information is not available, a value of 0 should be used.MilliSecondsTime in user mode, in milliseconds. If this information is not available, a value of 0 should be used.MilliSeconds true2.7.0A link between a Process and the Thread(s) running in the context of this Process.truetrueGroupComponent11The Process.truetruePartComponenttrueThe Thread running in the context of the Process.true true2.7.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.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.trueThe 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 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.The time interval that the Job has been executing or the total execution time if the Job is complete.trueThe 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.trueUser 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.The percentage of the job that has completed at the time that this value is requested. 1010PercenttrueIndicates whether or not the job should be automatically deleted upon completion. If this property is set to falseand the job completes, then the extrinsic method DeleteInstanceMUST be used to delete the job versus updating this property.A vendor specific error code. This will be set to zero if the job completed without error.CIM_Job.ErrorDescriptionA free form string containing the vendor error description.CIM_Job.ErrorCodeA 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. true2.7.0OwningJobElement represents an association between a Job and the ManagedElement responsible for the creation of the Job. This association may not be possible, given that the execution of jobs can move between systems and that the lifecycle of the creating entity may not persist for the total duration of the job. However, this can be very useful information when available. This association defines a more specific 'owner' than is provided by the CIM_Job.Owner string.CIM_Job.Ownertrue1The ManagedElement responsible for the creation of the Job.trueThe Job created by the ManagedElement. true2.7.0AffectedJobElement represents an association between a Job and the ManagedElement(s) that may be affected by its execution. It may not be feasible for the Job to describe all of the affected elements. The main purpose of this association is to provide information when a Job requires exclusive use of the 'affected' ManagedElment(s) or when describing that side effects may result. trueThe ManagedElement affected by the execution of the Job.trueThe Job 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".Indexed01234UnknownOtherExclusive UsePerformance ImpactElement IntegrityCIM_AffectedJobElement.OtherElementEffectsDescriptionsProvides details for the 'effect' at the corresponding array position in ElementEffects. This information is required whenever ElementEffects contains the value 1 ("Other").IndexedCIM_AffectedJobElement.ElementEffects 2.7.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'.NametrueThe 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.)1024 true2.7.0ProcessOfJob describes that the referenced Process is the result of the execution of the Job. A Job may cause multiple Processes to run, perhaps on different operating systems. This is allowed by the '*' cardinality of the Process reference. Note that a Process can result from only one Job - hence, the '0..1' cardinality on Job.truetrueGroupComponentExecution of the Job results in the creation of the Process referenced as PartComponent. The Job aggregates the Process(es) that are created when it is executed.truetruePartComponentThe Process that results from the execution of the Job.true 2.7.0JobDestination is an EnabledLogicalElement representing where a Job is submitted for processing. It can refer to a queue that contains zero or more Jobs, such as a print queue containing print Jobs. JobDestinations are hosted on Systems, similar to the way that Services are hosted on Systems. Also, they may be enabled/disabled similar to Services.CIM_System.CreationClassNametrue256The scoping System's CreationClassName.CIM_System.Nametrue256The scoping System's Name.true256CreationClassName 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.Nametrue256The inherited Name serves as key of a JobDestination instance in a System. 2.6.0An association between a JobDestination and a System on which it resides. The cardinality of this association is 1-to-many. A System may host many Job queues. JobDestinations are weak with respect to their hosting System. Heuristic: A JobDestination is hosted on the System where the LogicalDevices, SoftwareFeatures or Services that implement/provide the JobDestination are located.trueAntecedent11The hosting System.trueDependenttrueThe JobDestination hosted on the System.true 2.6.0An association describing where a Job is submitted for processing, ie to which JobDestination.trueAntecedent1The JobDestination, possibly a queue.trueDependentThe Job that is in the Job queue/Destination.true 2.6.0BootService represents the functionality provided by a Device, software or via a Network to load an Operating System on a UnitaryComputerSystem. 2.6.0A representation of the access points of a BootService. 2.6.0BootServiceAccessBySAP is the relationship between a BootService and its access points.trueThe BootService.AntecedenttrueAn access point for the BootService.Dependenttrue 2.6.0HostedBootService defines the hosting System for a BootService. Since this relationship is subclassed from HostedService, it inherits the scoping/naming scheme defined for Service - where a Service is weak to its hosting System.true11The hosting System.AntecedenttrueThe BootService hosted on the System.Dependenttruetrue 2.7.0HostedBootSAP defines the hosting UnitaryComputerSystem for a BootSAP. Since this relationship is subclassed from HostedAccessPoint, it inherits the scoping/naming scheme defined for AccessPoint - where an AccessPoint is weak to its hosting System. In this case, a BootSAP must be weak to its hosting UnitaryComputerSystem.true11The UnitaryComputerSystem.AntecedenttrueThe BootSAP hosted on the UnitaryComputerSystem.Dependenttruetrue 2.6.0This Service is implemented by a LogicalDevice (e.g. a NetworkAdapter or Modem) that is capable of sending alert messages to a remote destination. The alert messages reflect the state of one or more ManagedSystemElements. The Elements for which alert messages are forwarded, are defined by enumerating the ProvidesServiceToElement association for the Service. Out of Band (OOB) refers to the mechanisms in use when normal OS-based management mechanisms are not possible. This occurs when the OS is down or not functioning properly.The type of the alert destination. For example, the alert may be received by an application listening on a UDP Port on a remote destination, or could be sent to a pager (values 4 or 2, respectively).01234UnknownOtherPagerTCP PortUDP PortCIM_OOBAlertService.OtherDestinationTypeDescriptionThe description of the alert DestinationType. This is used when the DestinationType is set to "Other" (value=1).CIM_OOBAlertService.DestinationTypeThe address where this Service sends the alerts. The format of this address depends on the DestinationType. For example, if the DestinationType is a UDP Port (value=4), then this property contains a string identifying the IP address of the Port (for example, 111.222.333.444:4567). If DestinationType is a pager (value=2), then the address is a Pager number (for example, 18002257654).The format of the Alert Message sent by the Service.012345UnknownOtherNumericAlphaNumericFree Form TextPlatform Event TrapCIM_OOBAlertService.OtherMessageFormatDescriptionThe description of the format of the alert message used by the Service when the AlertMessageFormat property is set to "Other" (value=1).CIM_OOBAlertService.MessageFormatIf the AlertService only uses a fixed message to send an alert, then this flag should be set to TRUE.The AlertService may require some fixed data to send as part of the message. This may include things like the address or name of the System. This string contains the complete message when the property, OnlySendsFixedMessage, is set to TRUE.If the destination is capable of sending an acknowledgement to the alert, then this flag is set to TRUE. The format of the acknowledgement is determined by the DestinationType and the MessageFormat.The AlertService may retry and send an alert more than once. The RetryCount identifies how often the operation will be repeated. If DestinationIsAckCapable is set to TRUE, then the retry will only be done if an Ack is not received. Otherwise, the retries are done unconditionally.The interval between each successive retry, in seconds. If DestinationIsAckCapable is set to TRUE, then this interval is used as a timeout interval, before the next retry is done.SecondstrueIf the OOB Alerting service is capable of sending Presence heart beat messages.When set to true causes the OOBAlertService to send Presenceheart beat messages.CIM_OOBAlertService.PresenceHeartbeatCapable 2.6.0WakeUpService allows a UnitaryComputerSystem to be woken up from a low power sleep state. This Service is implemented by a LogicalDevice (e.g. NetworkAdapter or Modem) that is capable of receiving wakeup messages, and notifying the System.The Type of the WakeUp Service.01234UnknownOtherWake On LAN - Magic PacketWake on LAN - Packet FilteringWake On RingCIM_WakeUpServcice.OtherWakeUpTypeDescriptionA description of the type of WakeUpService used when WakeUpType is set to "Other" (value=1).CIM_WakeUpService.WakeUpTypeThe filter type on the packets/messages that trigger the WakeUpService. This field is only used when the WakeUpType is set to "Wake On LAN - Packet Filtering" (value=3).01234567UnknownOtherARP BroadcastNeighbor Discovery MulticastIP Packet with Directed MAC AddressIPX Diagnostic ResponderNBT Name QueryBinary MatchCIM_WakeUpService.OtherFilterTypeDescriptiontrueThe binary data that is used to compare the contents of the received packet. This is used when the FilterType is set to "Binary Match" (value=7). This could also be used when the FilterType is set to "Other" (value=1).The description of the format of the FilterType used by the Service when the FilterType is set to "Other" (value=1).CIM_WakeUpService.FilterType 2.6.0The TimeZone class is a set of properties defining a particular time zone. These properties include the concept of daylight saving time.trueTime zone identifier. The Id MAY be expressed in the form 'area name/city name' (e.g., "America/New_York"), or as a time zone name (for example, EST or EDT).trueThe date and time at which this time zone definition takes effect. The value is specified in UTC.Full name of the 'standard' time zone (e.g., "U.S. Eastern Standard Time"), suitable for presentation to the user in the default locale.CIM_TimeZone.StandardCaptionShort name of the 'standard' time zone (e.g., "EST"), suitable for presentation to the user in the default locale. Note that a specific StandardCaption property is defined, instead of using the inherited Caption. This is done to force consistent property naming for the StandardXXX and DaylightXXX properties.CIM_TimeZone.StandardNameThe number of minutes by which this 'standard' time differs from UTC. For example, U.S. EST differs from UTC by -5.0 hours or -300 minutes, whereas Australia Adelaide Standard Time differs by 9.5 hours or 570 minutes.MinutesThe month in which daylight saving time ends (and 'standard' time begins). Specify 0 for January, 1 for February, and so on.01234567891011JanuaryFebruaryMarchAprilMayJuneJulyAugustSeptemberOctoberNovemberDecemberCIM_TimeZone.StandardDay-3131There are two different interpretations for this property, depending on the value of StandardDayOfWeek. In one case, StandardDay defines the day-in-month on which daylight saving time ends. This interpretation is used when the StandardDayOfWeek is 0. A positive or negative integer is specified to indicate whether the StandardDay should be calculated from the beginning or the end of the month. For example, 5 indicates the fifth day in the StandardMonth and -1 indicates the last day in the StandardMonth. When StandardDayOfWeek is not 0, StandardDay is the day-in-month on which daylight saving time ends, defined in conjunction with StandardDayOfWeek. For example, if StandardDay is 15 and StandardDayOfWeek is Saturday, then daylight saving time ends on the first Saturday on or after the 15th day in the StandardMonth (i.e., the third Saturday in the month). If StandardDay is 20 and StandardDayOfWeek is -Saturday, then this indicates the first Saturday on or before the 20th day in the StandardMonth. If StandardDay is -1 and StandardDayOfWeek is -Sunday, then this indicates the last Sunday in the StandardMonth.CIM_TimeZone.StandardDayOfWeekPositive or negative integer used in conjunction with StandardDay to indicate the day of the week on which daylight saving time ends (and 'standard' time begins). StandardDayOfWeek 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 StandardDay. A negative integer (representing -Sunday, -Monday, ..., -Saturday) means that the day of week is found on or before the StandardDay.-7-6-5-4-3-2-101234567-Saturday-Friday-Thursday-Wednesday-Tuesday-Monday-SundayExactDayOfMonthSundayMondayTuesdayWednesdayThursdayFridaySaturdayCIM_TimeZone.StandardDayThe time interval after midnight when daylight saving time ends. For example, 00000000020000.000000:000 indicates that daylight saving time ends at two o'clock, local time (usually, daylight saving time).Full name of the 'daylight' time zone (e.g., "U.S. Eastern Daylight Saving Time"), suitable for presentation to the user in the default locale.CIM_TimeZone.DaylightCaptionShort name of the 'daylight' time zone (e.g., "EDT"), suitable for presentation to the user in the default locale. Note that a specific DaylightCaption property is defined, instead of using the inherited Caption. This is done to force consistent property naming for the StandardXXX and DaylightXXX properties.CIM_TimeZone.DaylightNameThe number of minutes by which this daylight saving time differs from UTC. For example, U.S. EDT differs from UTC by -4.0 hours or -240 minutes, whereas Australia Adelaide Daylight Time differs by 10.5 hours or 630 minutes.MinutesThe month in which daylight saving time starts. Specify 0 for January, 1 for February, and so on.01234567891011JanuaryFebruaryMarchAprilMayJuneJulyAugustSeptemberOctoberNovemberDecemberCIM_TimeZone.DaylightDay-3131There are two different interpretations for this property, depending on the value of DaylightDayOfWeek. In one case, DaylightDay defines the day-in-month on which daylight saving time starts. This interpretation is used when the DaylightDayOfWeek is 0. A positive or negative integer is specified to indicate whether the DaylightDay should be calculated from the beginning or the end of the month. For example, 5 indicates the fifth day in the DaylightMonth and -1 indicates the last day in the DaylightMonth. When DaylightDayOfWeek is not 0, DaylightDay is the day-in-month on which daylight saving time starts, defined in conjunction with DaylightDayOfWeek. For example, if DaylightDay is 15 and DaylightDayOfWeek is Saturday, then daylight saving time starts on the first Saturday on or after the 15th day in the DaylightMonth (i.e., the third Saturday in the month). If DaylightDay is 20 and DaylightDayOfWeek is -Saturday, then this indicates the first Saturday on or before the 20th day in the DaylightMonth. If DaylightDay is -1 and DaylightDayOfWeek is -Sunday, then this indicates the last Sunday in the month.CIM_TimeZone.DaylightDayOfWeekPositive or negative integer used in conjunction with DaylightDay to indicate the day of the week on which daylight saving time starts. Set DaylightDayOfWeek to 0 to indicate an exact day of month, such as March 1. Positive integer (Sunday, Monday, ..., Saturday) means that the day of week is found on or after DaylightDay. Negative integer (-Sunday, -Monday, ..., -Saturday) means that the day of week is found on or before DaylightDay. -7-6-5-4-3-2-101234567-Saturday-Friday-Thursday-Wednesday-Tuesday-Monday-SundayExactDayOfMonthSundayMondayTuesdayWednesdayThursdayFridaySaturdayCIM_TimeZone.DaylightDayThe time interval after midnight when daylight saving time starts. For example, 00000000020000.000000:000 indicates that daylight saving time starts at two o'clock, local time (usually, standard time). 2.6.0A class derived from LocalFileSystem that represents the Unix environment view of a file store controlled by a ComputerSystem through local means (e.g., direct device driver access). In this case, the file store is managed directly by the ComputerSystem without the need for another computer to act as a file server. This definition does not breakdown in the case of a Clustered File System. In this scenario, the FileSystem is a LocalFileSystem, weak to the Cluster.The number of free inodes present in the file system. This value is only valid if TotalSlots is non-zero.MIF.DMTF|Host File System|001.12CIM_UnixLocalFileSystem.TotalSlotsThe total number of inodes available in the file system. A value of zero for TotalInodes indicates that this file system does not have a preset limit.MIF.DMTF|Host File System|001.11The reserve data capacity of the file system in bytes.MIF.DMTF|Host File System|001.15Bytes 2.6.0Each instance of the CIM_UnixProcess class represents a single instance of a running program. A user of the Operating System will typically see a Process as an application or task. Within an OperatingSystem, a Process is defined by a workspace of memory resources and environmental settings that are allocated to it. On a multitasking System, this workspace prevents intrusion of resources by other Processes. Additionally, a Process can execute as multiple Threads, all which run within the same workspace.trueThe parent process ID of this executing process.MIF.DMTF|Process Information|001.2trueThe Real User ID of this currently executing process.MIF.DMTF|Process Information|001.4trueThe Group ID of this currently executing process.MIF.DMTF|Process Information|001.2If part of a group of processes are under the control of a session leader, this property holds the session ID for the group.The TTY currently associated with this process.MIF.DMTF|Process Information|001.5The executing process's command path.MIF.DMTF|Process Information|001.7The operating system parameters provided to the executing process. These are the argv[] values.MIF.DMTF|Process Information|001.8The process's 'nice' value. Used to compute its priority.MIF.DMTF|Process Information|001.11A description of the event this process is currently sleeping for. The precise nature of this string is implementation defined, but is typically the address of a system data structure that will be modified when the event occurs. This string only has meaning when the ExecutionState is "Blocked" or "SuspendedBlocked".CIM_Process.ExecutionState 2.6.0The statistics associated with a Unix process.CIM_Process.CSCreationClassNametrue256The scoping Process's ComputerSystem CreationClassName.CIM_Process.CSNametrue256The scoping Process's ComputerSystem Name.CIM_Process.OSCreationClassNametrue256The scoping Process's OperatingSystem CreationClassName.CIM_Process.OSNametrue256The scoping Process's OperatingSystem Name.CIM_Process.Handletrue256The scoping Process's Handle.CIM_Process.CreationClassNametrue256The scoping Process's CreationClassName.true256NameA string used to identify the related statistics of a Process.A string used to identify the related statistics of a Process. This key allows multiple instances of statistics to correspond to a single process. The multiple instances could be used in applications such as time-sliced statistics.MIF.DMTF|Process Information|001.12PercentThe number of KiloBytes of real text space used by the process.MIF.DMTF|Process Information|001.15KiloBytesThe number of KiloBytes of real data space used by the process.MIF.DMTF|Process Information|001.16KiloBytesThe number of KiloBytes of real stack space used by the process.MIF.DMTF|Process Information|001.17KiloBytesThe number of KiloBytes of virtual text space used by the process.MIF.DMTF|Process Information|001.18KiloBytesThe number of KiloBytes of virtual data space used by the process.MIF.DMTF|Process Information|001.19KiloBytesThe number of KiloBytes of virtual stack space used by the process.MIF.DMTF|Process Information|001.20KiloBytesThe number of KiloBytes of virtual space used for memory mapped files by the process.MIF.DMTF|Process Information|001.22KiloBytesThe number of KiloBytes of shared memory used by theprocess.MIF.DMTF|Process Information|001.21KiloBytesCPU time of terminated child processes in clock ticks.Clock TickstrueSystem time of terminated child processes in clock ticks.Clock Tickstrue 2.6.0CIM_UnixProcessStatistics is an association that relates a CIM_UnixProcess to its StatisticalInformation.trueElement11The Process for which statistical or metric data is defined.trueStatstrueThe UNIX Process statistical information/object.true 2.6.0Threads represent the ability to execute units of a Process or task in parallel. A UnixThread inherits from the superclass, CIM_Thread, which is weak to the Process. The values used are defined in sched.h and psched.h.Indicates the thread's scheduling policy. Set to "Other" when using OtherSchedPolicy to specifiy additional values. "Other" represents SCHED_OTHER as defined in sched.h.0123UnknownOtherSCHED_FIFOSCHED_RRCIM_UnixThread.OtherSchedPolicyIndicates the thread's scheduling policy when SchedPolicy is set to "Other".CIM_UnixThread.SchedPolicyIndicates the size of the guard area for a created thread's stack.Indicates the creation state of the thread.023UnknownPTHREAD_CREATE_DETACHEDPTHREAD_CREATE_JOINABLEIndicates how the scheduling attributes are to be set.023UnknownPTHREAD_INHERIT_SCHEDPTHREAD_EXPLICIT_SCHEDIndicates the contention scope of the thread.023UnknownPTHREAD_SCOPE_SYSTEMPTHREAD_SCOPE_PROCESSIndicates the size of storage to be used for the thread's stack.Indicates the thread's concurrency level.Indicates the thread's cancelability state.023UnknownPTHREAD_CANCEL_ENABLEPTHREAD_CANCEL_DISABLEIndicates the thread's cancelability type.023UnknownPTHREAD_CANCEL_DEFERREDPTHREAD_CANCEL_ASYNCHRONOUS 2.6.0The UnixFile class holds properties that are valid for various subclasses of LogicalFile, in a Unix environment. This is defined as a separate and unique class since it is applicable to Unix files, directories, etc. It is associated via a FileIdentity relationship to these subclasses of LogicalFile. Unless this approach of creating and associating a separate class is used, it is necessary to subclass each of the inheritance hierarchies under LogicalFile, duplicating the properties in this class. The referenced _PC* and _POSIX* constants are defined in unistd.h. Some properties indicate whether the UNIX implementation support a feature such as asynchronous I/O or priority I/O. If supported, sysconf returns the value as defined in the appropriate header file such as unistd.h. If a feature is not supported, then pathconf returns a -1. In this case, the corresponding property should be returned without any value.CIM_LogicalFile.CSCreationClassNametrue256The scoping ComputerSystem's CreationClassName.CIM_LogicalFile.CSNametrue256The scoping ComputerSystem's Name.CIM_LogicalFile.FSCreationClassNametrue256The scoping FileSystem's CreationClassName.CIM_LogicalFile.FSNametrue256The scoping FileSystem's Name.CIM_LogicalFile.CreationClassNametrue256The scoping LogicalFile's CreationClassName. CIM_LogicalFile.Nametrue1024The scoping LogicalFile's Name. trueAn Identifer that uniquely describes the owner of this file.trueAn identifier that describes the group that owns this file.Indicates restricted deletion for directories, or possible implementation defined properties for executable files. For directories this is known as the sticky bit.Count of the number of names for this file.trueFile Inode number, as printed by "ls -i".UNIX.TOG|ls -iIndicates whether the associated file has setuid permissions.Indicates whether the associated file has setgid permissions.The time that the Inode was last modified. This includes the Inode creation time, state modification, and etc.Maximum number of links to a single file. 8POSIX.TOG|pathconf|_PC_LINK_MAXMaximum number of bytes in a filename, not including terminating null.14BytesPOSIX.TOG|pathconf|_POSIX_NAME_MAXMaximum number of bytes in a pathname, including the terminating null character.255BytesPOSIX.TOG|pathconf|_POSIX_PATH_MAXThe use of chown() is restricted to a process with appropriate privileges. chown() is used to change the group ID of a file. The group ID can be changed to the effective group ID or one of its supplementary group IDs.POSIX.TOG|pathconf|_PC_CHOWN_RESTRICTEDIndicates whether pathname components longer than NameMax generate an error.CIM_UnixFile.NameMaxPOSIX.TOG|pathconf|_PC_NO_TRUNCIndicates whether asynchronous input or output operations may be performed for the associated file.POSIX.TOG|pathconf|_PC_ASYNC_IOIndicates whether prioritized input or output operations may be performed for the associated file.POSIX.TOG|pathconf|_PC_PRIO_IOIndicates whether synchronised input or output operations may be performed for the associated file.POSIX.TOG|pathconf|_PC_SYNC_IO 2.6.0CIM_FileIdentity indicates that a UnixFile describes Unix-specific aspects of the various subclasses of LogicalFile. The association exists since it forces UnixFile to be weak to (scoped by) the LogicalFile. This is not true in the association's superclass, LogicalIdentity.trueSystemElement11The Logical File.trueSameElementtrue1SameElement represents the additional aspects of the Unix/Linux Logical file.true 2.6.0UnixDirectory is a type of File that logically groups UnixFiles 'contained' in it.Minimum number of bits needed to represent the maximum size of a Unix file allowed in the specified directory, as a signed integer value. Thus, a value of 32 indicates a maximum size of 2**31 bytes.32BitsPOSIX.TOG|pathconf|_PC_FILESIZEBITS 2.6.0DeviceFile is a special type of LogicalFile that represents a Device. This class is a specialization of DeviceFile for a Unix environment.The type of device file0123UnknownOtherBlockCharacterCIM_UnixDeviceFile.OtherTypeDescriptionAdditional information when the Type property is set to "Other".CIM_UnixDeviceFile.TypetrueThe device Identifier: this is the st_rdev field in the stat structure.Additional information provided by the driver. This property may be null if no information is available, or a general description of the device when available, e.g. "Non-rewind tape streamer".trueThe Device's Major Id.trueThe Device's Minor Id. true2.7.0An entity managed by BIOS, an OperatingSystem or other software, which is available for use by application software and/or LogicalDevices. Resources are individually identified and allocated entities, that are assignable, reservable, counted/tracked, releasable, reset-able, etc. Examples of software Resources are message queues, shared memory segments (identified by a key value), and named pipes, while examples of hardware Resources (in an x86 environment) are IRQs, DMA channels and memory mapped I/O.Boolean indicating whether the Resource can be shared.Indicates whether the Resource is implemented in hardware, software or both.0234UnknownHardware OnlySoftware OnlyHardware and Software 2.6.0Personal computer architecture IRQ.CIM_ComputerSystem.CreationClassNametrue256The scoping ComputerSystem's CreationClassName.CIM_ComputerSystem.Nametrue256The scoping ComputerSystem's Name.true256CreationClassName 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.trueA part of the object's key value, IRQ Number.MIF.DMTF|IRQ|002.1Availability of the IRQ.12345OtherUnknownAvailableIn Use/Not AvailableIn Use and Available/ShareableMIF.DMTF|IRQ|002.2IRQ trigger type indicating whether edge (value=4) or level triggered (value=3) interrupts occur. Also, "Other" (1) and "Unknown" (2) may be defined.1234OtherUnknownLevelEdgeMIF.DMTF|IRQ|002.3MIF.DMTF|System Resource IRQ Info|001.2IRQ trigger level indicating whether the interrupt is triggered by the hardware signal going high (value=4) or low (value=3). Also, "Other" (1) and "Unknown" (2) may be defined.1234OtherUnknownActive LowActive HighMIF.DMTF|System Resource IRQ Info|001.3ShareableBoolean indicating whether the IRQ can be shared.MIF.DMTF|IRQ|002.4The Hardware property indicates whether the interrupt is hardware or software based. (If TRUE, the interrupt is hardware based.) On a personal computer, a hardware IRQ is a physical wire to a programmable interrupt controller (PIC) chip, through which the CPU can be notified of time critical events. Some IRQ lines are reserved for standard Devices such as the keyboard, floppy disk drives, and the system clock. A software interrupt is a programmatic mechanism to allow an application to get the attention of the Processor. 2.6.0Personal Computer architecture Memory Mapped I/O. This class addresses both memory and port I/O resources. The property, MappedResource, defines whether memory or I/O is mapped (and for I/O whether the mapping is to a memory or a port space).CIM_ComputerSystem.CreationClassNametrue256The scoping ComputerSystem's CreationClassName.CIM_ComputerSystem.Nametrue256The scoping ComputerSystem's Name.true256CreationClassName 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.trueA part of the object's key value, the starting address of memory mapped I/O.MIF.DMTF|Memory Mapped I/O|001.1Ending address of memory mapped I/O.MIF.DMTF|Memory Mapped I/O|001.2Type of memory mapped I/O. MappedResource defines whether memory or I/O is mapped, and for I/O, whether the mapping is to a memory or a port space.0123OtherMapped MemoryI/O Mapped to Memory SpaceI/O Mapped to Port Space 2.6.0Since the MemoryMappedIO class applies to memory AND port resources, there is the potential for key conflict. For example, both a memory resource and a port resource may be located at address 0. Since StartingAddress is the distinguishing key of MemoryMappedIO, two instances would be created with the same key. This is prevented by defining memory and port resource subclasses of MemoryMappedIO, and allowing the CreationClassName key property to distinguish between them and force uniqueness in their keys. 2.6.0Since the MemoryMappedIO class applies to memory AND port resources, there is the potential for key conflict. For example, both a memory resource and a port resource may be located at address 0. Since StartingAddress is the distinguishing key of MemoryMappedIO, two instances would be created with the same key. This is prevented by defining memory and port resource subclasses of MemoryMappedIO, and allowing the CreationClassName key property to distinguish between them and force uniqueness in their keys. 2.6.0Personal computer architecture DMA.CIM_ComputerSystem.CreationClassNametrue256The scoping ComputerSystem's CreationClassName.CIM_ComputerSystem.Nametrue256The scoping ComputerSystem's Name.true256CreationClassName 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.trueA part of the object's key value, the DMA Channel number.MIF.DMTF|DMA|001.1Availability of the DMA.12345OtherUnknownAvailableIn Use/Not AvailableIn Use and Available/ShareableMIF.DMTF|DMA|001.2Indication that the DMA Channel supports burst mode.MIF.DMTF|DMA|001.3An array indicating all the transfer widths (in bits) supported by this DMA Channel. Permissible values are 8, 16, 32, 64 or 128 bits. If unknown, enter 0.Bits08163264128MIF.DMTF|System Resource DMA Info|001.2An integer indicating the DMA Channel address size in bits. Permissible values are 8, 16, 32 or 64 bits. If unknown, enter 0.Bits08163264MIF.DMTF|System Resource DMA Info|001.3The maximum number of bytes that can be transferred by this DMA Channel. If unknown, enter 0.BytesMIF.DMTF|System Resource DMA Info|001.4Indicates whether DMA may execute in 'count by byte' mode (value=4) or not (value=3). Also, "Other" (1) and "Unknown" (2) may be defined.1234OtherUnknownNot execute in 'count by byte' modeExecute in 'count by byte' modeMIF.DMTF|System Resource DMA Info|001.7Indicates whether DMA may execute in 'count by word' mode (value=4) or not (value=3). Also, "Other" (1) and "Unknown" (2) may be defined.1234OtherUnknownNot execute in 'count by word' modeExecute in 'count by word' modeMIF.DMTF|System Resource DMA Info|001.8DMA channel timing. For example, "Type A" (value =4) or "Type F" (6) could be specified.123456OtherUnknownISA CompatibleType AType BType FMIF.DMTF|System Resource DMA Info|001.9Indicates whether C type (burst) timing is supported (value=5) or not (value=4). Also, "Other" (1), "Unknown" (2) and "ISA Compatible" (3) are defined.12345OtherUnknownISA CompatibleNot SupportedSupportedMIF.DMTF|System Resource DMA Info|001.10 true2.7.2An association between a System and a SystemResource that exists and is allocated in the context of the System.truetrue11The System in whose context the Resource exists and is allocated.GroupComponenttruetrueA Resource of the System.PartComponenttrue 2.7.0An association between a ComputerSystem and the SystemResources available on it.truetruetrue11The ComputerSystem.GroupComponenttruetrueA SystemResource of the ComputerSystem.PartComponenttrue 2.7.0An association between a ComputerSystem and the IRQs available on it.truetruetrue11The ComputerSystem.GroupComponenttruetruetrueAn IRQ of the ComputerSystem.PartComponenttrue 2.7.0An association between a ComputerSystem and the Memory Mapped I/O ports available on it.truetruetrue11The ComputerSystem.GroupComponenttruetruetrueA memory mapped I/O port of the ComputerSystem.PartComponenttrue 2.7.0An association between a ComputerSystem and the DMA channels available on it.truetruetrue11The ComputerSystem.GroupComponenttruetruetrueA DMA channel of the ComputerSystem.PartComponenttrue 2.6.0An association between LogicalDevices and SystemResources, indicating that the Resource is assigned to the Device.trueAntecedentThe Resource.trueDependentThe LogicalDevice to which the Resource is assigned.true 2.6.0An association between a LogicalDevice and a DMA SystemResource indicating that the DMA Channel is assigned to the Device.trueThe DMA Channel.AntecedenttrueThe LogicalDevice to which the Resource is assigned.DependenttrueBoolean indicating whether the LogicalDevice can act as a bus master on the DMA Channel.MIF.DMTF|System Resource DMA Info|001.6 2.7.0MessageLog represents any type of event, error or informational register or chronicle. The object describes the existence of the log and its characteristics. Several methods are defined for retrieving, writing and deleting log entries, and maintaining the log.true256CreationClassName 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.Nametrue256The inherited Name serves as part of the key (a unique identifier) for the MessageLog instance.An array of integers indicating the Log capabilities. Information such as "Write Record Supported" (value=2) or "Variable Length Records Supported" (8) is specified in this property.Indexed012345678910UnknownOtherWrite Record SupportedDelete Record SupportedCan Move Backward in LogFreeze Log SupportedClear Log SupportedSupports Addressing by Ordinal Record NumberVariable Length Records SupportedVariable Formats for RecordsCan Flag Records for OverwriteCIM_MessageLog.CapabilitiesDescriptionsAn array of free-form strings providing more detailed explanations for any of the Log features indicated in the Capabilities array. Note, each entry of this array is related to the entry in the Capabilities array that is located at the same index.IndexedCIM_MessageLog.CapabilitiesThe maximum size, in bytes, to which the Log can grow. If there is no maximum, then MaxLogSize should be set to 0.BytesThe size of the Log header, in bytes, if one is present. If there is no Log header, then this property should be set to 0. Headers may include general information about the Log such as the current number of records, time of last update, or a pointer to the location of the first Log entry. Note that this property is NOT the size of the header for an individual Log entry. The latter is described by the property, SizeOfRecordHeader.BytesIf the SizeOfHeader property is non-zero, this property describes the structure and format of the Log header. It is a free-form string. If the SizeOfHeader property is 0, then the information in this property is undefined.Maximum size, in bytes, to which an individual Log entry (record) can grow - if the Capabilities array includes a value of 7 ("Variable Length Records Supported"). If the Capabilities array does not include a 7, then the Log only supports fixed length entries. The size of these entries is described by this property.BytesThe size of the header for the Log's individual entries, in bytes, if record headers are defined. If there are no record headers, then this property should be set to 0. Record headers may include information such as the type of the Log entry, the date/time that the entry was last updated, or a pointer to the start of optional data. Note that this property defines the header size for individual records in the Log, while the SizeOfHeader property describes the Log's overall header, typically located at the start of the MessageLog.BytesIf the SizeOfRecordHeader property is non-zero, this property describes the structure and format of the record headers. It is a free-form string. If the SizeOfRecordHeader property is 0, then the information in this property is undefined.Maximum number of records that can be captured in the Log. If undefined, a value of zero should be specified. Note that when the Capabilities array indicates that variable length records are supported (value=7), then it is possible that this maximum may not be achieved.Current number of entries (records) in the Log.trueAn enumeration describing the behavior of the Log, when it becomes full or near full. For example, the Log may wrap (value=2) or may simply stop recording entries (value=7). Some of the property's possible values need further explanation: 3="Clear When Near Full" indicates that all of the Log's entries will be deleted when a specified record capacity is reached. The capacity is specified in percentage, using the property, PercentageNearFull. 'Near Full' may be less than 100% if the Log takes time to clear, and a position should always be available for new records. 4="Overwrite Outdated When Needed" describes that Log entries (timestamped later than the date/time specified in the property, TimeWhenOutdated) can be overwritten. 5="Remove Outdated Records" specifies that records (timestamped later than the date/time specified in the property, TimeWhenOutdated) are logically and/or physically removed from the Log. 6="Overwrite Specific Records" indicates that specially flagged records may be overwritten. This property only makes sense when the Capabilities array includes a value of 10, "Can Flag Records for Overwrite".01234567UnknownOtherWraps When FullClear When Near FullOverwrite Outdated When NeededRemove Outdated RecordsOverwrite Specific RecordsNever OverwriteCIM_MessageLog.OtherPolicyDescriptionCIM_MessageLog.TimeWhenOutdatedCIM_MessageLog.PercentageNearFullWhen the OverwritePolicy specifies a value of 1 ("Other"), the Log's behavior can be explained using this property. If OverwritePolicy is not 1, then this property's contents are undefined.CIM_MessageLog.OverwritePolicyIf the OverwritePolicy is based on 'outdated' records (values 4 or 5), this property defines when a Log entry is considered to be outdated - either by time interval or at a specific date and time.CIM_MessageLog.OverwritePolicyIf the OverwritePolicy is based on clearing records when the Log is near full (value=3), this property defines the record capacity (in percentage) that is considered to be 'near full'.PercentCIM_MessageLog.OverwritePolicyAn enumeration describing the last change to the MessageLog.01234UnknownAddDeleteModifyLog ClearedWhen a change is made to the Log, the date/time of that modification is captured. This property could be used to event against any update to the MessageLog.When a change is made to the Log, the record number that was modified is captured.Boolean indicating that the Log is currently frozen and modifications are not allowed.An enumeration describing the character set used to record data in the individual Log entries. For example, the Log records may contain ASCII data (value=2), or be raw octet strings (value=10).01234567891011UnknownOtherASCIIUnicodeISO2022ISO8859Extended UNIX CodeUTF-8UCS-2Bitmapped DataOctetStringDefined by Individual RecordsRequests that the MessageLog be cleared of all entries. 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. If the request is not supported, check the Capabilities array that a value of 6 ("Clear Log Supported") is specified. Note: In a subclass, the set of possible return codes could be described 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 an iteration of the MessageLog be established and that the iterator be set to the first entry in the Log. An identifier for the iterator is returned as an output parameter of the method. Regarding iteration, you have 2 choices: 1) Embed iteration data in the method call, and allow implementations to track/store this data manually; or, 2) Iterate using a separate object (for example, class ActiveIterator) as an iteration agent. The first approach is used here for interoperability. The second requires an instance of the Iterator object for EACH iteration in progress. 2's functionality could be implemented underneath 1. The return value from PositionToFirstRecord 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.falsetrueRequests that the Log's iteration identifier be advanced or retreated a specific number of records, or set to the entry at a specified numeric location. These two different behaviors are accomplished using the input parameters of the method. Advancing or retreating is achieved by setting the MoveAbsolute boolean to FALSE, and then specifying the number of entries to advance or retreat as positive or negative values in the RecordNumber parameter. Moving to a specific record number is accomplished by setting the MoveAbsolute input parameter to TRUE, and then placing the record number into the RecordNumber parameter. This can only be done if the Capabilities array includes a value of 7, "Supports Addressing by Ordinal Record Number". After the method completes and if ordinal record numbers are supported (the Capabilities array includes a 7), the current record number is returned in the RecordNumber output parameter. Otherwise, the value of the parameter is undefined. IterationIdentifier is defined as an Input/Output method parameter to allow the Log to embed state information in the Identifier and potentially let the identifier be maintained by the using application. The return value from PositionAtRecord should be 0 if the request was successfully executed, 1 if the request is not supported and some other value if an error occurred. If the request is not supported, check the Capabilities array regarding support for ordinal record number addressing and backward movement in the Log (values 7 and 4, respectively). Note: In a subclass, the set of possible return codes could be described 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.truetruetrueAdvancing or retreating the IterationIdentifier is achieved by setting the MoveAbsolute boolean to FALSE, and specifying the number of entries to advance or retreat as positive or negative values in the RecordNumber parameter. Moving to a specific record number is accomplished by setting the MoveAbsolute parameter to TRUE, and placing the record number into the RecordNumber parameter.truetrueRequests that the record indicated by the IterationIdentifier be retrieved from the MessageLog. After retrieval, the IterationIdentifier may be advanced to the next record by setting the PositionToNext input parameter to TRUE. Two output parameters are defined for the method - RecordData which holds the contents of the Log entry (as an array of bytes that can be recast to an appropriate format), and RecordNumber which returns the current record number addressed via the IterationIdentifier. The RecordNumber parameter is only defined/valid when the Capabilities array indicates that ordinal record number addressing is supported (a value of 7). IterationIdentifier is defined as an Input/Output method parameter to allow the Log to embed state information in the Identifier and potentially let the identifier be maintained by the using application. The return value from GetRecord 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.truetruetrueBoolean indicating that the IterationIdentifier should be advanced to the next record, after retrieving the current Log entry.falsetruefalsetrueRequests that the record indicated by the IterationIdentifier be deleted from the MessageLog. After deletion, the IterationIdentifier may be advanced to the next record by setting the PositionToNext input parameter to TRUE. If set to FALSE, then the IterationIdentifier will be positioned at the previous record. Two output parameters are defined for the method - RecordData which holds the contents of the deleted Log entry (as an array of bytes that can be recast to an appropriate format or discarded), and RecordNumber which returns the current record number addressed via the IterationIdentifier. The RecordNumber parameter is only defined/valid when the Capabilities array indicates that ordinal record number addressing is supported (a value of 7). IterationIdentifier is defined as an Input/Output method parameter to allow the Log to embed state information in the Identifier and potentially let the identifier be maintained by the using application. The return value from DeleteRecord should be 0 if the request was successfully executed, 1 if the request is not supported, and some other value if an error occurred. If the request is not supported, check the Capabilities array that a value of 3 ("Delete Record Supported") is specified. Note: In a subclass, the set of possible return codes could be described 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.truetruetrueBoolean that when set to TRUE requests the IterationIdentifier to be advanced to the next record, after the current entry is deleted. If set to FALSE, IterationIdentifier is set to the previous record.falsetruefalsetrueRequests that a record be inserted at the Log position indicated by the IterationIdentifier. The entry's data is provided in the RecordData input parameter. After insertion, the IterationIdentifier may be advanced to the next record by setting the PositionToNext input parameter to TRUE. The output parameter, RecordNumber, returns the current record number addressed via the IterationIdentifier. This parameter is only defined/valid when the Capabilities array indicates that ordinal record number addressing is supported (a value of 7). IterationIdentifier is defined as an Input/Output method parameter to allow the Log to embed state information in the Identifier and potentially let the identifier be maintained by the using application. The return value from WriteRecord should be 0 if the request was successfully executed, 1 if the request is not supported, and some other value if an error occurred. If the request is not supported, check the Capabilities array that a value of 2 ("Write Record Supported") is specified. Note: In a subclass, the set of possible return codes could be described 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.truetruetrueBoolean indicating that the IterationIdentifier should be advanced to the next record, after writing the Log entry.truefalsetrueRequests that an iteration of the Log, identified by the IterationIdentifier input parameter, be stopped. The return value from CancelIteration 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.trueRequests that the MessageLog be placed in a frozen state ("Freeze" input parameter = TRUE) or 'unfrozen' (= FALSE). If frozen, modifications to the Log will not be allowed. If successful, the Log's IsFrozen boolean property will be updated to reflect the desired state. The method's 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. If the request is not supported, check the Capabilities array that a value of 5 ("Freeze Log Supported") is specified. Note: In a subclass, the set of possible return codes could be described 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.trueRequests that the record indicated by the IterationIdentifier be flagged as overwriteable. This method is only supported when the Capabilities array includes a value of 10, "Can Flag Records for Overwrite". After updating the entry, the IterationIdentifier may be advanced to the next record by setting the PositionToNext input parameter to TRUE. One output parameter is defined for the method RecordNumber. It returns the current record number addressed via the IterationIdentifier. This parameter is only defined/valid when the Capabilities array indicates that ordinal record number addressing is supported (a value of 7). IterationIdentifier is defined as an Input/Output method parameter to allow the Log to embed state information in the Identifier and potentially let the identifier be maintained by the using application. The return value from FlagRecordForOverwrite 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.truetruetrueBoolean indicating that the IterationIdentifier should be advanced to the next record, after updating the current Log entry.falsetrue 2.6.0The LogRecord object can describe the definitional format for entries in a MessageLog, or can be used to instantiate the actual records in the Log. The latter approach provides a great deal more semantic definition and management control over the individual entries in a MessageLog, than do the record manipulation methods of the Log class. It is recommended that the data in individual Log entries be modeled using subclasses of LogRecord, to avoid the creation of LogRecords with one property (such as RecordData) without semantics. Definitional formats for LogRecords could be specified by establishing a naming convention for the RecordID and MessageTimestamp key properties.CIM_MessageLog.CreationClassNametrue256The scoping Log's CreationClassName.CIM_MessageLog.Nametrue256The scoping Log's Name.true256CreationClassName 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.true256RecordID, with the MessageTimestamp property, serve to uniquely identify the LogRecord within a MessageLog. Note that this property is different than the RecordNumber parameters of the MessageLog methods. The latter are ordinal values only, useful to track position when iterating through a Log. On the other hand, RecordID is truly an identifier for an instance of LogRecord. It may be set to the record's ordinal position, but this is not required.trueA LogRecord's key structure includes a timestamp for the entry.A free-form string describing the LogRecord's data structure. truetruetrue2.7.0RecordInLog describes the aggregation or location of Log entries within a MessageLog.truetrue11The Message Log.truetrueThe Log entry contained within the MessageLog. 2.6.0MessageLogs can reside in data files, on specially allocated storage areas such as disks or memory, or output as raw I/O streams. In fact, a single Log may use each of these mechanisms to output or capture its contents. The LogInDeviceFile association describes a Log outputting to a raw I/O stream DeviceFile - for example, a serial port on a UNIX system.trueAntecedentThe I/O stream DeviceFile.trueDependentThe MessageLog outputting to the DeviceFile.true 2.6.0MessageLogs can reside in data files, on specially allocated storage areas such as disks or memory, or output as raw I/O streams. In fact, a single Log may use each of these mechanisms to output or capture its contents. The LogInDataFile association describes a Log stored as a DataFile.trueAntecedentThe DataFile.trueDependentThe MessageLog residing in the DataFile.true 2.6.0MessageLogs can reside in data files, on specially allocated storage areas such as disks or memory, or output as raw I/O streams. In fact, a single Log may use each of these mechanisms to output or capture its contents. The LogInStorage association describes a Log located in a specially allocated portion of a StorageExtent. The offset of the Log, within the Extent, is defined using a property of the association, StartingOffset.trueAntecedentThe StorageExtent.trueDependentThe MessageLog located within the Extent.trueStartingOffset indicates where in the Extent that the Log begins. 2.6.0ManagedSystemElements may record their event, error or informational data within MessageLogs. The use of a Log to hold a ManagedSystemElement's data is described by this association. The type of Element data captured by the Log can be specified using the RecordedData string property.trueAntecedentThe MessageLog.trueDependentThe ManagedSystemElement whose information is recorded in the MessageLog.trueA free-form string describing the use of the Log by the ManagedSystemElement. 2.7.0Specific diagnostic test parameters and execution instructions are defined by subclassing and/or instantiating the DiagnosticSetting object. To provide more detailed Settings for a type of test (i.e., additional properties), subclassing is appropriate. When only the generic Setting information is required, instantiation of the DiagnosticSetting class may suffice. Data from DiagnosticSetting is captured in DiagnosticResult. When RunTest starts execution the settings, which are time sensitive, should be evaluated and captured. This is suggested since the DiagnosticSetting object can be modified at any time, and therefore the current test settings could be lost.true256SettingIDThe identifier by which the DiagnosticSetting object is known and uniquely named. One possible naming scheme is to name the SettingID using the DiagnosticTest's CreationClassName and DiagnosticName, plus a GUID (Globally Unique IDentifier). Note that at an enterprise level, there is typically not a one to one mapping between a DiagnosticSetting and all copies of the DiagnosticTest. The proposed naming convention willscale to the entrprise level.trueSets the level of warning messages to be logged. If for example no warning information is required, the level would be set to "No Warnings" (value=0). Using "Missing Resources" (value=1) will cause warnings to be generated when required resources or hardware are not found. Setting the value to 2, "Testing Impacts", results in both missing resources and 'test impact' warnings (for example, multiple retries required) to be reported.0123No WarningsMissing ResourcesTesting ImpactsAll WarningstrueWhen this flag is true, the diagnostic test will report 'soft errors'. In this context, a soft error is a message from the diagnostic reporting a known defect in the hardware or driver configuration, or execution environment. Examples are: 'Not enough memory', 'Driver IOCTL not implemented', 'Video RAM compare failed during polygon fill test (A known defect in the video chipset)', etc.trueWhen this flag is true, the diagnostic test will report 'status messages'. In this context, a status message indicates that the diagnostic code is at a checkpoint. Examples are: "Completion of phase 1", "Complex pattern", etc.trueWhen this flag is true, the test will halt after finding the first error.trueWhen this flag is true, the test software should attempt to run in an accelerated fashion either by reducing the coverage or number of tests performed.truePercent0100Requests the diagnostic software to reduce test coverage to the specified percentage. For example, a hard drive scan test could be asked to run at 50%. The most effective way to accomplish this is for the test software to scan every other track, as opposed to only scanning the first half of a drive. It is assumed that the effectiveness of the test is impacted proportional to the percentage of testing requested. Permissible values for this property range from 0 to 100. This property may not be applicable to all tests. If it can be set for a test, the value 7 ("Supports PercentOfTestCoverage") should be entered into the DiagnosticTest's Characteristics array.CIM_DiagnosticTest.CharacteristicstrueArray entries contain parameters corresponding to entries in the LoopControl array, limiting the number of times a test should be repeated with a single invocation of RunTest by a CIM client.IndexedCIM_DiagnosticSetting.LoopControltrueLoopControl, used in conjunction with LoopControlParameter, sets one or more loop control mechanisms that limits the number of times a test should be repeated with a single invocation of RunTest by a CIM client. There is an array-positional correspondence between LoopControl entries & LoopControlParameter entries. The entries in these coupled arrays of loop controls can be used in a logical OR fashion to achieve the desired loop control. For example, if a client wants to loop a test 1000 times, but quit if a timer runs out, it could set both controls into the LoopControl array as two separate entries in each array. The looping test will terminate when the first of the two ORed conditions are met. The descriptions for each loop control are given below: Unknown/Default (= 0) Other (= 1) : Additional detail may be found in OtherLoopControlDescription. Continuous (= 2) : The corresponding LoopControlParameter is ignored and the test will execute continuously. Tests that use this control should also support DiscontinueTest. Count (= 3) : The corresponding LoopControlParameter is interpreted as a loop count (uint32), indicating the number of times the test should be repeated with a single invocation of RunTest by a CIM client. Timer (= 4) : The corresponding LoopControlParameter is interpreted as an initial value (uint32) for a test loop timer, given in seconds. The looping is terminated when this timer has lapsed. ErrorCount (= 5) : The corresponding LoopControlParameter is interpreted as an error count (uint32). The loop will continue until the number of errors that have occurred exceeds the ErrorCount. Note: the ErrorCount only refers to hard test errors; it does not include soft errors or warnings. Indexed012345Unknown/DefaultOtherContinuousCountTimerError CountCIM_DiagnosticSetting.LoopControlParameterCIM_DiagnosticSetting.OtherLoopControlDescriptiontrueProvides additional information for LoopControl when its value is set to 1 ('Other').CIM_DiagnosticSetting.LoopControlParametertrueThe ResultPersistence property is a directive from a diagnostic client to a diagnostic provider. It allows the client to specify to the diagnostic service provider how long to persist the messages that result from execution of a diagnostic service. This applies to instances of DiagnosticResult. The timeout period starts upon completion of the diagnostic action described by the DiagnosticTest. Here is a summary of the choices and behaviors for different ResultPersistence values: 0 = "No Persistence": Setting the timer to zero tells the provider not to persist the diagnostic result. The diagnostic information is only available while the diagnostic is executing or at its conclusion. Value > 0 and < 0xFFFFFFFF = "Persist With TimeOut": Setting the ResultPersistenceOption to a integer will cause the DiagnosticResult to be persisted for that number of seconds. At the end of that time, the DiagnosticResult may be deleted by the diagnostic service provider. 0xFFFFFFFF = "Persist Forever": By setting the timeout value to the very large value, 0xFFFFFFFF, the provider shall persist results forever. In this case, the client MUST bear the responsibility for deleting them.Seconds 2.7.0When a DiagnosticTest Service is running, test results are reported using a DiagnosticResult object, or one of its subclasses. A DiagnosticTest may be running because its Service is Started or due to an invocation of the RunTest method. DiagnosticResults are related to their Test via an instance of the DiagnosticResultsForMSE association. For every running of DiagnosticTest, a new instance of DiagnosticResult, or one of it's subclasses should be created.CIM_DiagnosticTest.CreationClassNametrue256The scoping Test's CreationClassName.CIM_DiagnosticTest.Nametrue256The scoping Test's Name.CIM_DiagnosticTest.SystemCreationClassNametrue256The scoping Test's SystemCreationClassName.CIM_DiagnosticTest.SystemNametrue256The scoping Test's SystemName.true1024The Unique identifier for an instance of DiagnosticResults.The date and time the result was last updated.No valueThis property is being deprecated. Tests should begrouped at the test level, not by the model. /nIf this property is TRUE, then this DiagnosticResult summarizes the results from the execution of a packaged set of DiagnosticTests. The Tests in the package can be identified by following the DiagnosticResultForTest association to the test and then using the DiagnosticTestInPackage aggregation. The individual Results can be broken out by instantiating DiagnosticResults for the individual lower level tests and aggregating into the 'summary' Result using the DiagnosticResultInPackage association.The date and time when this test started.The date and time when this test completed.Describes how the test is progressing. For example, if the test was discontinued, the TestState will be "Stopped" (value=5), or if testing is currently executing, TestState will be "In Progress" (4).012345UnknownOtherPassedFailedIn ProgressStoppedCIM_DiagnosticResult.OtherStateDescriptionWhen "Other" (value=1) is entered in the TestState property, OtherStateDescription can be used to describe the test's state.CIM_DiagnosticResult.TestStateSecondsEstimated number of seconds to perform the DiagnosticTest indicated by the DiagnosticCreationClassName and DiagnosticName properties. After the test has completed, the actual elapsed time can be determined by subtracting the TestStartTime from the TestCompletionTime. A similar property is defined in the association, DiagnosticTestForMSE. The difference between the two properties is that the value stored in the association is a generic test execution time for the Element and the Test. But, the value here (in DiagnosticResult) is the estimated time that this instance with the given settings would take to run the test. A CIM Consumer can compare this value with the value in the association DiagnosticTestForMSE to get an idea what impact their settings have on test execution.CIM_DiagnosticTestForMSE.EstimatedTimeOfPerformingTestResults stores one or more textual results from the execution of the DiagnosticTest(s) referenced by the DiagnosticCreationClassName and DiagnosticName properties. Note that this property is defined as an 'ordered' array type, to maintain the order in which the results are stored. One entry is considered a cell location in the array. Each entry is time stamped and contains information in the following format: CIMDateTime|TestName|MessageText, where: "CIMDateTime" is the standard CIM data type with the following format: yyyymmddhhmmss.mmmmmmsutc, where yyyy = year, e.g. 2003 mm = month (01 - 12) dd = day (01 - 31) hh = hour (00 - 24) mm = minute (00-59) ss = second (00-59) mmmmmm = microsecond (000000-999999) s = "+" or "-" indicating the sign of the UTC correction field utc = offset from UTC (Universal Coordinated Time) in minutes "TestName" is the name of the internal test that produced the message "MessageText" is a free form string that is the 'test result' "|" is a delimiter character.OrderedPercent0100The percentage of the test that has executed thus far, if the TestState property is set to "In Progress" or the percentage of the complete test that was executed if the TestState property is set to any of the completed states ("Passed", "Failed" or "Stopped"). Final results may be based on less than 100% coverage due to the parameters defined in DiagnosticSetting (such as QuickMode, PercentOfTestCoverage or HaltOnError).If applicable, this string should contain one or more vendor specific error codes that the diagnostic service detected. These error codes may be used by the vendor for variety of purposes such as: fault data base indexing, field service trouble ticketing, product quality tracking, part failure history, etc. Since these codes are for vendor purposes they may assume any form. Details on suggested use cases will be left to white papers. The array of error codes has model correspondence with an ErrorCount array so the number of errors reported can be analyzed by individual error code.CIM_DiagnosticResult.ErrorCountIndexedSince some tests may detect transient and correctable errors such as a network diagnostic or memory test, an error count is useful to indicate the severity of the failure. This field contains an integer value of the number of errors detected by the test. The ErrorCount is an array with model correspondence to ErrorCode so that the test can report an ErrorCount on each type of error encountered. It is recommended that hard errors and correctable or recoverable errors be given different codes so that clients with knowledge of the error codes can evaluate correctable, recoverable, and hard errors independently.CIM_DiagnosticResult.ErrorCodeIndexedSince some tests may be looped, it is useful to report how many iterations passed and failed. This is relevant in analyzing transitory failures. For example, if all the errors occurred in just one of 100 iterations, the device may be viewed as OK or marginal, to be monitored further rather then failed. Note: LoopsPassed & LoopsFailed should add up to the loops completed.Since some tests may be looped, it is useful to report how many iterations passed and failed. This is relevant in analyzing transitory failures. For example if all the errors occurred in in just one of 100 iterations, the device may be viewed as OK or marginal, to be monitored further rather then failed. Note: LoopsPassed & LoopsFailed should add up to the loops completed.Sets the level of warning messages to be logged. If for example no warning information is required, the level would be set to "No Warnings" (value=0). Using "Missing Resources" (value=1) will cause warnings to be generated when required resources or hardware are not found. Setting the value to 2, "Testing Impacts", results in both missing resources and 'test impact' warnings (for example, multiple retries required) to be reported.0123No WarningsMissing ResourcesTesting ImpactsAll WarningsCIM_DiagnosticSetting.TestWarningLevelWhen this flag is true, the diagnostic test reports 'soft errors'. In this context, a soft error is a message from the diagnostic, reporting a known defect in the hardware or driver configuration, or execution environment. Examples are: 'Not enough memory', 'Driver IOCTL not implemented', 'Video RAM compare failed during polygon fill test (A known defect in the video chipset)', etc.CIM_DiagnosticSetting.ReportSoftErrorsWhen this flag is true, the diagnostic test reports 'status messages'. In this context, a status message indicates that the diagnostic code is at a checkpoint. Examples are: "Completion of phase 1", "Complex pattern", etc.CIM_DiagnosticSetting.ReportStatusMessagesWhen this flag is true, the test halts after finding the first error.CIM_DiagnosticSetting.HaltOnErrorWhen this flag is true, the test software attempts to run in an accelerated fashion either by reducing the coverage or number of tests performed.CIM_DiagnosticSetting.QuickModePercent0100Specifies the test coverage performed by the diagnostic. For example, a hard drive scan test could be asked to run at 50%. The most effective way to accomplish this is for the test software to scan every other track, as opposed to only scanning the first half of a drive. It is assumed that the effectiveness of the test is impacted proportional to the percentage of testing performed. Permissible values for this property range from 0 to 100.CIM_DiagnosticSetting.PercentOfTestCoverageArray entries contain parameters corresponding to entries in the LoopControl array, limiting the number of times a test should be repeated with a single invocation of RunTest by a CIM client.IndexedCIM_DiagnosticSetting.LoopControlParameterCIM_DiagnosticResults.LoopControlLoopControl, used in conjunction with LoopControlParameter, sets one or more loop control mechanisms that limits the number of times a test should be repeated with a single invocation of RunTest by a CIM client. There is an array-positional correspondence between LoopControl entries & LoopControlParameter entries. The entries in these coupled arrays of loop controls can be used in a logical OR fashion to achieve the desired loop control. For example, if a client wants to loop a test 1000 times, but quit if a timer runs out, it could set both controls into the LoopControl array as two separate entries in each array. The looping test will terminate when the first of the two ORed conditions are met. The descriptions for each loop control are given below: Unknown/Default (= 0) Other (= 1) : Additional detail may be found in OtherLoopControlDescription. Continuous (= 2) : The corresponding LoopControlParameter is ignored and the test will execute continuously. Tests that use this control should also support DiscontinueTest. Count (= 3) : The corresponding LoopControlParameter is interpreted as a loop count (uint32), indicating the number of times the test should be repeated with a single invocation of RunTest by a CIM client. Timer (= 4) : The corresponding LoopControlParameter is interpreted as an initial value (uint32) for a test loop timer, given in seconds. The looping is terminated when this timer has lapsed. ErrorCount (= 5) : The corresponding LoopControlParameter is interpreted as an error count (uint32). The loop will continue until the number of errors that have occurred exceeds the ErrorCount. Note: the ErrorCount only refers to hard test errors; it does not include soft errors or warnings. Indexed012345Unknown/DefaultOtherContinuousCountTimerError CountCIM_DiagnosticSetting.LoopControlCIM_DiagnosticResults.LoopControlParameterCIM_DiagnosticResults.OtherLoopControlDescriptionProvides additional information for LoopControl when its value is set to 1 ('Other').CIM_DiagnosticSetting.OtherLoopControlDescriptionCIM_DiagnosticResults.LoopControlParameterThe ResultPersistence property is a directive from a diagnostic client to a diagnostic provider. It allows the client to specify to the diagnostic service provider how long to persist the messages that result from execution of a diagnostic service. This applies to instances of DiagnosticResult. The timeout period starts upon completion of the diagnostic action described by the DiagnosticTest. Here is a summary of the choices and behaviors for different ResultPersistence values: 0 = "No Persistence": Setting the timer to zero tells the provider not to persist the diagnostic result. The diagnostic information is only available while the diagnostic is executing or at its conclusion. Value > 0 and < 0xFFFFFFFF = "Persist With TimeOut": Setting the ResultPersistenceOption to a integer will cause the DiagnosticResult to be persisted for that number of seconds. At the end of that time, the DiagnosticResult may be deleted by the diagnostic service provider. 0xFFFFFFFF = "Persist Forever": By setting the timeout value to the very large value, 0xFFFFFFFF, the provider shall persist results forever. In this case, the client MUST bear the responsibility for deleting them.SecondsCIM_DiagnosticSetting.ResultPersistence 2.6.0The CIM_DiagnosticTest class represents the framework for running diagnostic tests. Specific diagnostic tests may be defined by subclassing and/or instantiating this object. To provide more detail for a type of test(s) (i.e, additional properties and methods), subclassing is appropriate. Note that a DiagnosticTest can be simultaneously executed against several elements. If so, a DiagnosticTest may launch a ConcreteJob to represent each execution.The descriptions for each Characteristic are below: * "Is Exclusive" (value=2) is specified for the test module only if the diagnostic cannot run more than one test at a time, regardless of how many SystemElements are supported. Typically, this occurs when hardware or software constraints prevent the test from running as multiple, concurrent instances. If the diagnostic can be run against multiple SystemElements, but only once per Element, then set the IsExclusiveForMSE boolean property on the appropriate instances of DiagnosticTestForMSE. * If "Is Interactive" (value=3) is set, then the diagnostic displays a message either before, during or after testing. * Set "Is Destructive" (value=4) if the diagnostic will destroy data, or reconfigure the Element that is being tested. * "Is Risky" (value=5) indicates that data loss may occur if the test is interrupted. Some tests make copies of data, perform the test, and restore the data returning the tested entity to its previous configuration. If the test is interrupted, then loss of data or reconfiguration of the tested ManagedSystemElement may occur. * If "Is Package" (value=6) is set, this test is actually a set of lower level diagnostics, that are 'packaged' together. "Supports PercentOfTestCoverage" (value=7) indicates that a request for reduced test coverage can be specified using the PercentOfTestCoverage property of Diagnostic Setting. Also, the values "Unknown" (0) and "Other" (1) may be specified. If "Other" is defined, additional detail may be found in the OtherCharacteristicDescription property of this class.UnknownOtherIs ExclusiveIs InteractiveIs DestructiveIs RiskyIs PackageSupports PercentOfTestCoverageCIM_DiagnosticTest.OtherCharacteristicDescriptionProvides additional information for the Characteristic when its value is set to 1 ("Other").CIM_DiagnosticTest.CharacteristicsIf this test is currently being performed, the InUse property is set to TRUE. To determine which ManagedSystemElement is being tested, query the DiagnosticResult objects associated with this test (query DiagnosticResultForTest), and for which the TestState equals 4 ("In Progress"). The DiagnosticResult object is associated with the SystemElement under test, using DiagnosticResultForMSE.The "Expensive" qualifier can be applied to this class and its RunTest method. If so, the ResourcesUsed property describes the resources that are capitalized, based on a default setup for the test. Multiple resources can be specified since the property is an array.CPUMemoryHard DiskCDROMFloppyPCI BusUSB Bus1394 BusSCSI BusIDE BusNetworkISA BusEISA BusVESA BusPCMCIA BusCardBusAccess.busNuBusAGPVME BusSbus IEEE 1396-1993MCA BusGIO BusXIO BusHIO BusPMC BusSIO BusThe RunTest method executes this diagnostic for the specified ManagedSystemElement (defined using the SystemElement input parameter). Results of the test are stored in a DiagnosticResult object, a reference to which is returned as the Result output parameter. How the test should execute, i.e. its settings, is defined in a DiagnosticSetting object (or by a subclass of DiagnosticSetting). A reference to a Setting object is specified using the Setting input parameter. If a reference is not passed into the method, then a default DiagnosticSetting may be used. This default Setting is associated with the DiagnoticTest using the DefaultSetting relationship of the Core Model. When RunTest starts execution, the settings, which are time sensitive, should be evaluated and captured. This is suggested since the DiagnosticSetting object can be modified at any time, and therefore the current test settings could be lost. The method's return codes are expected to adhere to the XML return codes as they are introduced. Currently, the standard return values are: 0 = OK (function succeeded, but the test itself may have failed 1 = Unspecified Error (function failed for unspecified reasons) 2 = Not Implemented (function is not implemented for this instance) 3 = Out Of Resources (component could not allocate required resources, e.g. memory, disk space, 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.truetruefalsetrueExecution of this method will delete all instances of the DiagnosticResultForMSE object, for this DiagnosticTest and the specified ManagedSystemElement (defined using the SystemElement input parameter). The DiagnosticResults referenced in the DiagnosticResultForMSE instances will be deleted. Also the association DiagnosticResultForTest that refers to the DiagnosticResult object, and this test will be deleted. One output parameter is defined - ResultsNotCleared - which is a string array that lists the keys of the DiagnosticResults which could not be deleted. This information enables those Results to be revisited and either manually removed, or other corrective action taken. The method's return codes are expected to adhere to the XML return codes as they are introduced. Currently, the standard return values are: 0 = OK (function succeeded, but the test itself may have failed) 1 = Unspecified Error (function failed for unspecified reasons) 2 = Not Implemented (function is not implemented for this instance) 3 = Out Of Resources (component could not allocate required resources, e.g. memory, disk space, 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.truefalsetrueAfter invocation of this method and its completion, the specified test(s) will be discontinued for the indicated ManagedSystemElement (defined by the SystemElement input parameter). The test to discontinue is specified using the Result input parameter. If all instances of this test should be stopped for the SystemElement, then the Result reference should be NULL. Upon completion of the method, test status and other information (such as PercentComplete) will be stored in the DiagnosticResult instance defined by the Result input parameter. The output parameter, TestingStopped, is used as follows: Set to TRUE if testing was successfully stopped. Set to FALSE if the current test(s) can not be stopped. If set to FALSE, testing will stop when the diagnostic is able to do so safely. To determine if/when the testing is stopped, check the TestState property in the DiagnosticResult instance defined by the Result parameter. TestState will change from "In Progress" to "Stopped" (from 4 to 5). The method's return codes are expected to adhere to the XML return codes as they are introduced. Currently, the standard return values are: 0 = OK (function succeeded, but the test itself may have failed 1 = Unspecified Error (function failed for unspecified reasons) 2 = Not Implemented (function is not implemented for this instance) 3 = Out Of Resources (component could not allocate required resources, e.g. memory, disk space, 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.truetruefalsetrue true2.6.0This is an association class relating diagnostic test results to the ManagedSystemElement that is/was tested.trueThe diagnostic result.trueThe ManagedSystemElement to which the diagnostic result applies. true2.6.0This is an association class to relate the results of a test to the test itself.true11trueThe result object.true11The test that generated the result object. 2.6.0This is an association class that relates a DiagnosticTest to a ManagedSystemElement. Consumers wishing to 'diagnose' a particular Element could query this association, for the Element, to determine what tests are available. Examining the DiagnosticTestForMSE 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 DiagnosticTestForMSE will subclass from CIM_Dependency directly.trueThe test that may be run against a ManagedSystemElement.AntecedenttrueThe ManagedSystemElement that can be tested.DependenttrueSecondsEstimated number of seconds to perform the referenced DiagnosticTest against the ManagedSystemElement. Since execution times could vary by Element, this property is located in the association between the two entities. It is also captured in DiagnosticResult, in the EstimatedTimeOfPerforming property. A CIM Consumer can compare this value with the value inDiagnosticResult to get an idea of what impact theirsettings have on test execution.CIM_DiagnosticResult.EstimatedTimeOfPerformingIf the DiagnosticTest referenced in this object can be run concurrently against multiple SystemElements, but only run one at a time for the referenced ManagedSystemElement, then this boolean is set to TRUE. Alternately, if the test can NOT be run concurrently irregardless of the SystemElements being tested, then the more general "Is Exclusive" enumerated value (2) should be set in DiagnosticTest.Characteristics. 2.7.0No valueThis class is being deprecated. Tests should be grouped at the test level, not in the model. Therefore, the association is not appropriate. /nThis is an association class that identifies a DiagnosticTest as made up of lower level Tests. In this case, the test identified as the GroupComponent reference (i.e, the higher level test) would have the "Is Package" enumerated value specified in DiagnosticTest.Characteristics.truetrueGroupComponentNo valueThe DiagnosticTest object that acts as the container for all the tests of the package.truetruePartComponentNo valueThe DiagnosticTest object that is one of the elements of the package.true truetrue2.7.0No valueThis class is being deprecated. Tests should be grouped at the test level, not by the model. Therefore, this association is no longer appropriate. /nThis is an association class that identifies a DiagnosticResult as made up of lower level Results. In this case, the Result identified as the PackageResult reference (i.e., the higher level result) would have its IsPackage property set to TRUE.truetrueNo valueThe DiagnosticResult object that acts as the container for all the results of the package.trueNo valueThe DiagnosticResult object that is one of the elements of the package. 2.6.0This is an association class to relate test settings with diagnostic tests.trueElementThe Test that can use the Setting object.trueSettingThe Setting that can be applied to the execution of the DiagnosticTest.true truetrue2.7.0CIM_Indication is the abstract root class for all notifications about changes in schema, objects and their data, and about events detected by providers and instrumentation. Subclasses represent specific types of notifications. To receive an Indication, a consumer (or subscriber) must create an instance of CIM_IndicationFilter describing the criteria of the notification, an instance of CIM_IndicationHandler describing the delivery of the notification, and an instance of CIM_IndicationSubscription associating the Filter and Handler.An identifier for the Indication. This property is similar to a key value in that it can be used for identification, when correlating Indications (see the CorrelatedIndications array). Its value SHOULD be unique as long as Alert correlations are reported, but MAY be reused or left NULL if no future Indications will reference it in their CorrelatedIndications array.Recommendation.ITU|X733.Notification identifierA list of IndicationIdentifiers whose notifications are correlated with (related to) this one.Recommendation.ITU|X733.Correlated notificationsThe time and date of creation of the Indication. The property may be set to NULL if the entity creating the Indication is not capable of determing this information. Note that IndicationTime may be the same for two Indications that are generated in rapid succession. true2.6.0CIM_ClassIndication is an abstract superclass describing changes in the definition of the schema. Subclasses represent specific types of change notifications, such as class creation, deletion and modification.truetruetrueThe current definition of the class that is created, changed or deleted in the schema. In the case of a CIM_ClassDeletion Indication, the definition for the class just prior to deletion should be placed in this property. 2.6.0CIM_ClassCreation notifies when a new class is defined in the schema.true 2.6.0CIM_ClassDeletion notifies when a class is deleted from the schema.true 2.6.0CIM_ClassModification notifies when a class definition in the schema is modified.truetruetrueA copy of the 'previous' class definition whose change generated the Indication. PreviousClassDefinition contains an 'older' copy of the class' information, as compared to what is found in the ClassDefinition property (inherited from ClassIndication). true2.6.0CIM_InstIndication is an abstract superclass describing changes to instances. Subclasses represent specific types of change notifications, such as instance creation, deletion and modification.truetruetrueA copy of the instance that changed to generate the Indication. SourceInstance contains the current values of the properties selected by the IndicationFilter's Query. In the case of CIM_InstDeletion, the property values are copied before the instance is deleted. 2.6.0CIM_InstCreation notifies when a new instance is created.true 2.6.0CIM_InstDeletion notifies when an existing instance is deleted.true 2.6.0CIM_InstModification notifies when an instance is modified.truetruetrueA copy of the 'previous' instance whose change generated the Indication. PreviousInstance contains 'older' values of an instance's properties (as compared to SourceInstance), selected by the IndicationFilter's Query. 2.6.0CIM_InstMethodCall notifies when an instance's method is invoked.truetrueThe name of the method invoked.trueThe parameters of the method, formatted as an EmbeddedObject (with a predefined class name of "__MethodParameters".ReturnValue's data is dependent on the PreCall property. When PreCall is TRUE, this property is NULL describing that there is no method return value (since the method has not yet executed). When PreCall is FALSE, ReturnValue contains a string representation of the method's return value.CIM_InstMethodCall.PreCalltrueBoolean indicating whether the Indication is sent before the method begins executing (TRUE) or when the method completes (FALSE). When TRUE, the inherited property SourceInstance contains the value of the instance (the properties defined by the Filter's Query clause), before execution of the method. When PreCall is FALSE, SourceInstance embeds the instance as it appears after the completion of the method. 2.6.0CIM_InstRead notifies when an instance is read but not modified.true true2.6.0An abstract superclass for specialized Indication classes, addressing specific changes and alerts published by providers and instrumentation. Subclasses include AlertIndication (with properties such as PerceivedSeverity and ProbableCause), and SNMPTrapIndication (which recasts Traps as CIM indications).true 2.6.0A concrete class for mapping an SNMP Trap to CIM based on the IETF RFC 1157. The usefulness of this class is to describe common trap semantics. But, a complete understanding of any trap data received relies on the Indicaton recipient having access to the sender's MIB. Understanding can be improved by mapping the SNMP domain to CIM, and using CIM LifeCycle and standard subclasses of CIM_ProcessIndication.trueType of object generating the trap.PDU.IETF|RFC1157-TRAP-PDU.enterpriseAddress of the object generating the trap.PDU.IETF|RFC1157-TRAP-PDU.agent-addrAn enumerated value that describes the generic trap type: - The coldStart(0) trap signifies that the sending protocol entity is reinitializing itself such that the agent's configuration or the protocol entity implementation may be altered. - The warmStart(1) trap signifies that the sending protocol entity is reinitializing itself such that neither the agent configuration nor the protocol entity implementation is altered. - The linkDown(2) trap signifies that the sending protocol recognizes a failure in one of the communication links represented in the agent's configuration. The Trap-PDU of type linkDown contains as the first element of its variable-bindings the name and value of the ifIndex instance for the affected interface. - The linkUp(3) trap signifies that the sending protocol entity recognizes that one of the communication links represented in the agent's configuration has come up. The Trap-PDU of type linkUp contains as the first element of its variable-bindings, the name and value of the ifIndex instance for the affected interface. - An authenticationFailure(4) trap signifies that the sending protocol entity is the adressee of a protocol message that was not properly authenticated. While implementations of SNMP must be capable of generating this trap, they must also be capable of suppressing the emission of such traps via an implementation-specific mechanism. - An egpNeighborLoss(5) trap signifies that an EGP neighbor for whom the sending protocol entity was an EGP peer has been marked as down and the peer relationship no longer pertains. The Trap-PDU of type egpNeighborLoss contains as the first element of its variable-bindings, the name and value of the egpNeighAddr instance for the affected neighbor. - An enterpriseSpecific(6) trap signifies that the sending protocol entity recognizes that some enterprise-specific event has occurred. The specific-trap field identifies the particular trap which occurred.Cold StartWarm StartLink DownLink UpAuthentication FailureEGP Neighbor LossEnterprise SpecificPDU.IETF|RFC1157-TRAP-PDU.generic-trapSpecific trap code.PDU.IETF|RFC1157-TRAP-PDU.specific-trapTime elapsed between the last (re)intialization of the managed entity and the generation of the trap.PDU.IETF|RFC1157-TRAP-PDU.time-stampObject naming information (an OID) from the 'variable binding' portion of the Trap. This array is correlated with the VarBindSyntaxes and VarBindValues arrays. Each entry is related to the entries in the other arrays, that are located at the same index. In this way, the variable binding's name/syntax/value tuple can be constructed.IndexedCIM_SNMPTrapIndication.VarBindSyntaxesCIM_SNMPTrapIndication.VarBindValuesPDU.IETF|RFC1157-TRAP-PDU.variable-bindingsObject syntax information (defined as an enumerated value) from the 'variable binding' portion of the Trap. This array is correlated with the VarBindNames and VarBindValues arrays. Each entry is related to the entries in the other arrays, that are located at the same index. In this way, the variable binding's name/syntax/value tuple can be constructed.Indexed12345678IntegerOctetStringObjectIdentifierNetworkAddressCounterGaugeTimeTicksOpaqueCIM_SNMPTrapIndication.VarBindNamesCIM_SNMPTrapIndication.VarBindValuesPDU.IETF|RFC1157-TRAP-PDU.variable-bindingsAn OctetString representing object value information from the 'variable binding' portion of the Trap. This array is correlated with the VarBindNames and VarBindSyntaxes arrays. Each entry is related to the entries in the other arrays, that are located at the same index. In this way, the variable binding's name/syntax/value tuple can be constructed.IndexedtrueCIM_SNMPTrapIndication.VarBindNamesCIM_SNMPTrapIndication.VarBindSyntaxesPDU.IETF|RFC1157-TRAP-PDU.variable-bindings 2.7.0A concrete superclass for CIM Alert notifications. An AlertIndication is a specialized type of CIM_Indication that contains information about the severity, cause, recommended actions and other data of a real world event. This event and its data may or may not be modeled in the CIM class hierarchy.trueA short description of the Indication.Recommendation.ITU|X733.Additional textThe identifying information of the entity (ie, the instance) for which this Indication is generated. The property contains the path of an instance, encoded as a string parameter - if the instance is modeled in the CIM Schema. If not a CIM instance, the property contains some identifying string that names the entity for which the Alert is generated.truePrimary classification of the Indication. The following values are defined: 1 - Other. The Indication's OtherAlertType property conveys its classification. Use of "Other" in an enumeration is a standard CIM convention. It means that the current Indication does not fit into the categories described by this enumeration. 2 - Communications Alert. An Indication of this type is principally associated with the procedures and/or processes required to convey information from one point to another. 3 - Quality of Service Alert. An Indication of this type is principally associated with a degradation or errors in the performance or function of an entity. 4 - Processing Error. An Indication of this type is principally associated with a software or processing fault. 5 - Device Alert. An Indication of this type is principally associated with an equipment or hardware fault. 6 - Environmental Alert. An Indication of this type is principally associated with a condition relating to an enclosure in which the hardware resides, or other environmental considerations. 7 - Model Change. The Indication addresses changes in the Information Model. For example, it may embed a Lifecycle Indication to convey the specific model change being alerted. 8 - Security Alert. An Indication of this type is associated with security violations, detection of viruses, and similar issues.12345678OtherCommunications AlertQuality of Service AlertProcessing ErrorDevice AlertEnvironmental AlertModel ChangeSecurity AlertRecommendation.ITU|X733.Event typeA string describing the Alert type - used when the AlertType property is set to 1, "Other State Change".CIM_AlertIndication.AlertTypetrueAn enumerated value that describes the severity of the AlertIndication from the notifier's point of view: 1 - Other, by CIM convention, is used to indicate that the Severity's value can be found in the OtherSeverity property. 3 - Degraded/Warning should be used when its appropriate to let the user decide if action is needed. 4 - Minor should be used to indicate action is needed, but the situation is not serious at this time. 5 - Major should be used to indicate action is needed NOW. 6 - Critical should be used to indicate action is needed NOW and the scope is broad (perhaps an imminent outage to a critical resource will result). 7 - Fatal/NonRecoverable should be used to indicate an error occurred, but it's too late to take remedial action. 2 and 0 - Information and Unknown (respectively) follow common usage. Literally, the AlertIndication is purely informational or its severity is simply unknown.UnknownOtherInformationDegraded/WarningMinorMajorCriticalFatal/NonRecoverableRecommendation.ITU|X733.Perceived severityHolds the value of the user defined severity value when 'Severity' is 1 ("Other").CIM_AlertIndication.PerceivedSeveritytrueAn enumerated value that describes the probable cause of the situation which resulted in the AlertIndication.0123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130UnknownOtherAdapter/Card ErrorApplication Subsystem FailureBandwidth ReducedConnection Establishment ErrorCommunications Protocol ErrorCommunications Subsystem FailureConfiguration/Customization ErrorCongestionCorrupt DataCPU Cycles Limit ExceededDataset/Modem ErrorDegraded SignalDTE-DCE Interface ErrorEnclosure Door OpenEquipment MalfunctionExcessive VibrationFile Format ErrorFire DetectedFlood DetectedFraming ErrorHVAC ProblemHumidity UnacceptableI/O Device ErrorInput Device ErrorLAN ErrorNon-Toxic Leak DetectedLocal Node Transmission ErrorLoss of FrameLoss of SignalMaterial Supply ExhaustedMultiplexer ProblemOut of MemoryOutput Device ErrorPerformance DegradedPower ProblemPressure UnacceptableProcessor Problem (Internal Machine Error)Pump FailureQueue Size ExceededReceive FailureReceiver FailureRemote Node Transmission ErrorResource at or Nearing CapacityResponse Time ExcessiveRetransmission Rate ExcessiveSoftware ErrorSoftware Program Abnormally TerminatedSoftware Program Error (Incorrect Results)Storage Capacity ProblemTemperature UnacceptableThreshold CrossedTiming ProblemToxic Leak DetectedTransmit FailureTransmitter FailureUnderlying Resource UnavailableVersion MisMatchPrevious Alert ClearedLogin Attempts FailedSoftware Virus DetectedHardware Security BreachedDenial of Service DetectedSecurity Credential MisMatchUnauthorized AccessAlarm ReceivedLoss of PointerPayload MismatchTransmission ErrorExcessive Error RateTrace ProblemElement UnavailableElement MissingLoss of Multi FrameBroadcast Channel FailureInvalid Message ReceivedRouting FailureBackplane FailureIdentifier DuplicationProtection Path FailureSync Loss or MismatchTerminal ProblemReal Time Clock FailureAntenna FailureBattery Charging FailureDisk FailureFrequency Hopping FailureLoss of RedundancyPower Supply FailureSignal Quality ProblemBattery DischargingBattery FailureCommercial Power ProblemFan FailureEngine FailureSensor FailureFuse FailureGenerator FailureLow BatteryLow FuelLow WaterExplosive GasHigh WindsIce BuildupSmokeMemory MismatchOut of CPU CyclesSoftware Environment ProblemSoftware Download FailureElement ReinitializedTimeoutLogging ProblemsLeak DetectedProtection Mechanism FailureProtecting Resource FailureDatabase InconsistencyAuthentication FailureBreach of ConfidentialityCable TamperDelayed InformationDuplicate InformationInformation MissingInformation ModificationInformation Out of SequenceKey ExpiredNon-Repudiation FailureOut of Hours ActivityOut of ServiceProcedural ErrorUnexpected InformationRecommendation.ITU|X733.Probable causeRecommendation.ITU|M3100.probableCauseITU-IANA-ALARM-TCCIM_AlertIndication.ProbableCauseDescriptionCIM_AlertIndication.EventIDCIM_AlertIndication.EventTimeProvides additional information related to the ProbableCause.CIM_AlertIndication.ProbableCauseProvides information on trending - trending up, down or no change.UnknownNot ApplicableTrending UpTrending DownNo ChangeRecommendation.ITU|X733.TrendIndicationFree form descriptions of the recommended actions to take to resolve the cause of the notification.Recommendation.ITU|X733.Proposed repair actionsAn instrumentation or provider specific value that describes the underlying "real-world" event represented by the Indication. Two Indications with the same, non NULL EventID value are considered, by the creating entity, to represent the same event. The comparison of two EventID values is only defined for Alert Indications with identical, non NULL values of SystemCreateClassName, SystemName and ProviderName.CIM_AlertIndication.ProbableCauseThe time and date the underlying event was first detected. If specified, this property MUST be set to NULL if the creating entity is not capable of providing this information. This value is based on the notion of local date and time of the Managed System Element generating the Indication.CIM_AlertIndication.ProbableCause256The scoping System's CreationClassName for the Provider generating this Indication.256The scoping System's Name for the Provider generating this Indication.256The name of the Provider generating this Indication. 2.6.0A subclass of CIM_AlertIndications carrying additional threshold information related to the notification. This subclass is used when one of the ProbableCauses is set to 53, "Threshold Crossed".trueA string describing the threshold or naming the property that represents the threshold, if modeled in the CIM hierarchy. In the latter case, the value should be written as <schema name>_<class name>.<property name>.Recommendation.ITU|X733.Threshold informationA string holding the current value of the threshold. This is modeled as a string for universal mapping, similar to the CIM_Sensor properties in the Device Model.Recommendation.ITU|X733.Threshold informationA string holding the current reading value that exceeds the threshold. This is modeled as a string for universal mapping, similar to the CIM_Sensor properties in the Device Model.Recommendation.ITU|X733.Threshold information 2.6.0A subclass of CIM_AlertIndication that embeds a CIM_InstIndication. It is used when adding AlertIndication data to a LifeCycle Indication.trueAlertTypeThe primary classification of the Indication, defaulted to 7, "Model Change", for this class. This is done because: 1) the primary purpose of AlertInstIndication is to add Alert data to a LifeCycle Indication; and 2) LifeCycle Indications deal with 'model changes'.true12345678OtherCommunications AlertQuality of Service AlertProcessing ErrorDevice AlertEnvironmental AlertModel ChangeSecurity AlertRecommendation.ITU|X733.Event type7truetrueEmbeds the InstIndication that is part of this AlertIndication. Only the properties selected by the IndicationFilter's Query are included. 2.6.0CIM_IndicationFilter defines the criteria for generating an Indication and what data should be returned in the Indication. It is derived from CIM_ManagedElement to allow modeling the dependency of the filter on a specific service.true256A System's CreationClassName. The Filter is defined in the context of a CIM_System, where it is hosted or to which it applies. In a future release, a weak relationship will be explicitly added to the model. This is not done now to allow further refinement of the Filter definition and its inheritance tree. Keys are defined now to allow the class to be instantiated.true256A System's Name. The Filter is defined in the context of a CIM_System, where it is hosted or to which it applies. In a future release, a weak relationship will be explicitly added to the model. This is not done now to allow further refinement of the Filter definition and its inheritance tree. Keys are defined now to allow the class to be instantiated.true256Indicates 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, it allows all instances of this class and its subclasses to be uniquely identified.trueThe name of the filter.The path to a local namespace where the Indications originate. If NULL, the namespace of the Filter registration is assumed.trueA query expression that defines the condition(s) under which Indications will be generated. For some Indication classes, the query expression may also define the instance properties to be copied to the CIM_InstIndication's SourceInstance and PreviousInstance properties. Query language semantics include projection (e.g., Select), range (e.g., From) and predicate (e.g., Where).CIM_IndicationFilter.QueryLanguagetrueThe language in which the query is expressed. true2.7.0CIM_IndicationHandler is an abstract superclass describing how an Indication is to be processd/delivered/'handled'. This may define a destination and protocol for delivering Indications, or it may define a process to invoke. This class is derived from CIM_ManagedElement to allow modeling the dependency of the Handler on a specific service.true256A System's CreationClassName. The Handler is defined in the context of a CIM_System, where it is hosted or to which it applies. In a future release, a weak relationship will be explicitly added to the model. This is not done now to allow further refinement of the Handler definition and its inheritance tree. Keys are defined now to allow the class to be instantiated.true256A System's Name. The Handler is defined in the context of a CIM_System, where it is hosted or to which it applies. In a future release, a weak relationship will be explicitly added to the model. This is not done now to allow further refinement of the Handler definition and its inheritance tree. Keys are defined now to allow the class to be instantiated.true256Indicates 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, it allows all instances of this class and its subclasses to be uniquely identified.true256Indicates the name of this Handler.The name of the entity that created and/or maintains this Handler.Describes the Persistence Type of the destination defined by this instance. If the value of PersistenceType is not set, the value of PersistenceType MUST be treated as 2 ("Permanent"). A value of 2 ("Permanent") declares that the destination is always expected to be available (e.g., system log file). Inability to access this destination MUST be treated as an error condition. A value of 3 ("Transient") indicates that the destination is short-lived. Inability to access the destination MAY be treated as a normal termination condition. Subscriptions with "Transient" destinations MAY be deleted when the destination terminates or is no longer available.123OtherPermanentTransientCIM_IndicationHandler.OtherPersistenceTypeA string describing ("Other") values for PersistenceType. This value MUST be set to a non NULL value when the PersistenceType is 1 ("Other"). For all other values of PersistenceType, the value of OtherPersistenceType MUST be NULL.CIM_IndicationHandler.PersistenceType 2.6.0CIM_IndicationHandlerCIMXML describes the destination for Indications to be delivered via CIM-XML.trueThe destination URL to which CIM-XML Indication messages are to be delivered. The scheme prefix MUST be consistent with the DMTF CIM-XML Specifications. If a scheme prefix is not specified, the scheme "http:" MUST be assumed. true2.7.0CIM_IndicationSubscription describes a flow of Indications. The flow is specified by the referenced Filter, and directed to the referenced destination or process in the Handler. Property values of the referenced CIM_IndicationFilter instance and CIM_IndicationHandler instance MAY significantly effect the definition of the subscription. E.g., a subscription associated with a "Transient" destination MAY be deleted when the destination terminates or is no longer available.trueThe Filter that defines the criteria and data of the possible Indications of this subscription.trueThe Handler addressing delivery of the possible Indications of this subscription.Defines the desired behavior for a subscription when a fatal error occurs in one of the Indication processing subcomponents (e.g., Indication processor, Indication or instance provider, or Indication handler) and the Indication cannot be successfully sent. Specifically, a failure implies that some aspect of Indication generation,processing or dispatch is no longer functioning and Indications may be lost. If the value of OnFatalErrorPolicy is 2 ("Ignore") or not set (NULL), the subscription MUST continue to be processed in a 'best effort' mode. This mode of operation can lead to unpredictable, and potentially misleading results, because Indications may be lost. If the value is 3 ("Disable"), the subscription MUST be disabled. With this policy, no new Indications will be generated or dispatched until the subscription is explicitly enabled. This is accomplished via the property, SubscriptionState.If the value is 4 ("Remove"), the subscription MUST be deleted. Selecting this policy has the same effect as issuing a DeleteInstance operation on this subscription instance.1234OtherIgnoreDisableRemoveA string defining "Other" values for OnFatalErrorPolicy. This value MUST be set to a non NULL value when OnFatalErrorPolicy is set to a value of 1 ("Other"). For all other values, the OtherOnFatalErrorPolicy MUST be NULL.The FailureTriggerTimeInterval is used by the client to specify a recommended minimum delay before the OnFatalErrorPolicy is implemented.SecondstrueIndicates the current processing state of the subscription. 01234UnknownOtherEnabledEnabled DegradedDisabledA string defining "Other" values for SubscriptionState. This value MUST be set to a non NULL value when SubscriptionState is set to a value of 1 ("Other"). For all other values, the OtherSubscriptionState MUST be NULL.Date and time of the last state change. This value is based on the notion of local date and time of the Managed System Element running the Indication processing subcomponents.trueSubscriptionDuration defines the desired length of the subscription. Indications generated after the duration of the subscription has exceeded SubscriptionDuration MUST NOT be sent. The duration of a subscription MAY be changed by modifying this property. An expired subscription MAY be deleted and MUST NOT be modified. If the value ofSubscriptionDuration is not set, the subscription MUST be treated as having no expiration date. SecondsfalseSubscriptionStartTime is the time the subscription was started. The value of this property is computed based on the notion of date and time of the ManagedSystemElement running the Indication processing subcomponents.falseSubscriptionTimeRemaining is a computed value thatprovides a snapshot of the time remaining in theSubscription.SecondsThe RepeatNotificationPolicy property defines the desired behavior for handling Indications that report the occurrence of the same underlying event (e.g., the disk is still generating I/O errors and has not yet been repaired). The defined semantics for the RepeatNotificationCount, RepeatNotificationInterval, and RepeatNotificationGap properties depend on the value of RepeatNotificationPolicy, but values for these properties MUST be set if the property is defined for the selected policy. If the value of RepeatNotificationPolicy is 0 ("Unknown") or not set, no special processing for repeat Indications is defined by the subscription. The semantics associated with the handling of repeat Indications MAY be defined by the Indication processing subcomponents. If the value of RepeatNotificationPolicy is 2 ("None"), special processing of repeat Indications MUST NOT be performed. If the value is 3 ("Suppress") the first RepeatNotificationCount Indications, describing the same event, MUST be sent and all subsequent Indications for this event suppressed for the remainder of the time interval RepeatNotificationInterval. A new interval starts when the next Indication for this event is received. If the value of RepeatNotificationPolicy is 4 ("Delay") and an Indication is received, this Indication MUST be suppressed if, including this Indication, RepeatNoticationCount or fewer Indications for this event have been received during the prior time interval defined by RepeatNotificationInterval. If this Indication is the RepeatNotificationCount + 1 Indication, this Indication MUST be sent and all subsequent Indications for this event ignored until the RepeatNotificationGap has elapsed. A RepeatNotificationInterval MAY NOT overlap a RepeatNotificationGap time interval.01234UnknownOtherNoneSuppressDelayA string defining "Other" values for RepeatNotificationPolicy. This value MUST be set to a non NULL value when RepeatNotificationPolicy is set to a value of 1 ("Other"). For all other values, the OtherRepeatNotificationPolicy MUST be NULL.Defines the time interval for the repeat notification policy calculation.SecondsDefines the gap interval for the repeat notification policy calculation.SecondsDefines the count property for the repeat notification policy calculation. true2.6.0An abstract class for WBEM services such as the ObjectManager (CIM Server), Providers, protocol adapters, or other pluggable components. A type of CIM_Service that provides associated capabilities and details about the communication capabilities, namespaces, etc. for a specific WBEMService. 2.7.0A type of CIM_Service that defines the capabilities of the CIM Server in which this ObjectManager class resides. Details related to communicating with the ObjectManager, and the Manager's basic capabilities, are stored in instances of the associated CommunicationMechanism class available through the CommMechanismForManager association. It is assumed that Basic Read operations must be supported by all ObjectManager's in order to retrieve any additional detail.trueThe GatherStatisticalData property is used to control the gathering of statistical data made accessible through the CIM_CIMOMStatisticalData objects. If set to true, the data is gathered and can be accessed. If false, the CIM_CIMOMStatisticalData instance MAY exist but MUST show zero values for the counter properties.true 2.7.0The class, ObjectManagerCommunicationMechanism, describes access to an ObjectManager. It describes a protocol and data encoding that can be used for communication. When all instances of this class are enumerated for an ObjectManager (using the CommMechanismForManager association), all possible protocol and encoding schemes will be known. Also, specific capabilities (for example, basic read or query) that are supported in the protocol/encoding are described - using the ProfilesSupported property.trueCommunicationMechanism describes an encoding and protocol which can be used to communicate with the ObjectManager. At this time, only one encoding and protocol are standardized by the DMTF - 2 "CIM-XML". If this is supported by an ObjectManager, the specified value should be indicated. In the future, other 'standard' mechanisms may be defined. In addition, a vendor specific encoding/protocol value may be specified by using the value 1, "Other", and defining the mechanism in the OtherComminicationMechanismDescription property.012UnknownOtherCIM-XMLCIM_ObjectManagerCommunicationMechanism.OtherCommunicationMechanismDescriptionA free-form string providing a description of the supported encoding and protocol when 1, "Other", is specified in CommunicationMechanism.CIM_ObjectManagerCommunicationMechanism.CommunicationMechanismtrueEnumerated array describing the types of operations supported by the ObjectManager, using the encoding/protocol specified in the property, CommunicationMechanism. The enumeration is based on the Functional Profiles defined for conformance in the DMTF document, Specification for CIM Operations over HTTP.0123456789UnknownOtherBasic ReadBasic WriteSchema ManipulationInstance ManipulationAssociation TraversalQuery ExecutionQualifier DeclarationIndicationsIndexedCIM_ObjectManagerCommunicationMechanism.FunctionalProfileDescriptionsFree-form strings providing descriptions of the supported operations of the object manager. Entries in the array are correlated with those in the ProfilesSupported array. An entry in this Descriptions array MUST be provided when 1, "Other", is specified in the ProfilesSupported array.IndexedCIM_ObjectManagerCommunicationMechanism.FunctionalProfilesSupportedtrueBoolean indicating whether the ObjectManager supports multiple operation requests (TRUE) or only simple requests (FALSE).trueEnumerated array describing the types of authentication supported by the ObjectManager, using the encoding/protocol. specified in the property, CommunicationMEchanism. The defined values represent the authentication defined in the DMTF document, Specification for CIM Operations over HTTP.01234UnknownOtherNoneBasicDigestIndexedCIM_ObjectManagerCommunicationMechanism.AuthenticationMechanismDescriptionsFree-form strings providing descriptions of the supported mechanisms. Entries in this array are correlated with those in the AuthenticationMechanismsSupported array. An entry in this Descriptions array MUST be provided when 1, "Other", is specified in AuthenticationMechanismsSupported.IndexedCIM_ObjectManagerCommunicationMechanism.AuthenticationMechanismsSupportedtrueProvides the protocol version for this service access point. Version information MUST be in the form of M.N, where M is a numeric that describes the Major version and N is a numeric that describes the minor version. 2.6.0This class specializes ObjectManagerCommunicationMechanism, adding properties specific to the CIM-XML protocol (XML encoding and CIM Operations).CommunicationMechanismtrueCommunicationMechanism describes an encoding and protocol which can be used to communicate with the ObjectManager. At this time, only one encoding and protocol are standardized by the DMTF - 2 "CIM-XML". If this is supported by an ObjectManager, the specified value should be indicated. In the future, other 'standard' mechanisms may be defined. In addition, a vendor specific encoding/protocol value may be specified by using the value 1, "Other", and defining the mechanism in the OtherComminicationMechanismDescription property.012UnknownOtherCIM-XMLCIM_ObjectManagerCommunicationMechanism.OtherCommunicationMechanismDescription2VersionEnumeration describing the CIM-XML protocol version supported by the ObjectManager.1.01.11.2trueCIM_CIMXMLCommunicationMechanism.VersiontrueEnumeration describing the CIM-XML protocol version supported by the ObjectManager. It is deprecated in lieu of a more general, inherited property (Version).01Unknown1.0trueDescribes whether the CIM Server is strictly validating (validates the XML document against the DTD) or not (loosely validating). 2.6.0CommMechanismForManager is an association between an ObjectManager and an ObjectManagerCommunicationMechanism class. The latter describes a possible encoding/protocol/set of operations for accessing the referenced ObjectManager.true11The specific ObjectManager whose communication mechanism is described.Antecedenttrue1The encoding/protocol/set of operations that may be used to communicate with the referenced ObjectManager.Dependenttrue 2.7.0A ProtocolAdapter is a Service of the CIM Object Manager. It is responsible for accepting incoming requests on a particular protocol, and translating and forwarding the request to the CIM Object Manager. It is also responsible for translating and sending the response from the CIM Object Manager.A human-readable name that uniquely identifies the ProtocolAdapter within a system.Nametrue256trueAn implementation specific string that identifies the handle to the ProtocolAdapter.trueProtocolAdapterType enumerates the kind of ProtocolAdapter.123OtherClientProviderCIM_ProtocolAdapter.OtherProtocolAdapterTypeThe type(s) of ProtocolAdapter when "Other" is included in ProtocolAdapterType property.CIM_ProtocolAdapter.ProtocolAdapterType 2.7.0CommMechanismForAdapter is an association between an ObjectManager's communication mechanism and a ProtocolAdapter that supports that mechanism to translate requests and responses for the Object Manager.trueAntecedentThe specific ProtocolAdapter whose communication mechanism with the CIM Object Manager is described.trueDependent1The encoding/protocol/set of operations that may be used to communicate between the Object Manager and the referenced ProtocolAdapter.true 2.6.0Namespace provides a domain (in other words, a container), in which the instances [of a class] are guaranteed to be unique per the KEY qualifier definitions. It is named relative to the CIM_ObjectManager implementation that provides such a domain.CIM_ObjectManager.SystemCreationClassNametrue256The scoping System's CreationClassName.CIM_ObjectManager.SystemNametrue256The scoping System's Name.CIM_ObjectManager.CreationClassNametrue256The scoping ObjectManager's CreationClassName.CIM_ObjectManager.Nametrue256The scoping ObjectManager's Name.true256CreationClassName 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.true256A string to uniquely identify the Namespace within the ObjectManager.truetrueEnumeration indicating the organization/schema of the Namespace's objects. For example, they may be instances of classes of a specific CIM version.012345678910200201202UnknownOtherCIM 1.0CIM 2.0CIM 2.1CIM 2.2CIM 2.3CIM 2.4CIM 2.5CIM 2.6CIM 2.7DMI RecastSNMP RecastCMIP RecastCIM_Namespace.DescriptionOfClassInfotrueA string providing more detail (beyond the general classification in ClassInfo) for the object hierarchy of the Namespace.CIM_Namespace.ClassInfo 2.7.0A Namespace may represent data for one or many systems, that are local, remote (different than the system on which the ObjectManager is running) or aggregated. The SystemIdentification class provides enough data to identify the system(s) represented in the Namespace. It is weak to the Namespace.CIM_Namespace.SystemCreationClassNametrue256The scoping System's CreationClassName.CIM_Namespace.SystemNametrue256The scoping System's Name.CIM_Namespace.ObjectManagerCreationClassNametrue256The scoping ObjectManager's CreationClassName.CIM_Namespace.ObjectManagerNametrue256The scoping ObjectManager's Name.CIM_Namespace.CreationClassNametrue256The scoping Namespace's CreationClassName.CIM_Namespace.Nametrue256The scoping Namespace's Name.true256CreationClassName 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.true256A string uniquely identifying the name of the system represented in the Namespace.truetrueEnumeration indicating the format of the system identification and/or addressing information.01234567891011UnknownOtherShort DNS NameFully qualified DNS NameWindows Domain NameNetWare Server NameUnix HostnameGlobally Unique System IdentifierIP AddressModem Dialup StringMAC AddressIPMI AddressIndexedCIM_SystemIdentification.IdentificationDataCIM_SystemIdentification.FormatDescriptionstrueStrings further describing the format of the system identification information.IndexedCIM_SystemIdentification.IdentificationFormatsCIM_SystemIdentification.IdentificationDatatrueStrings containing the system identification information. The format is described by the corresponding array item in IdentificationFormats.IndexedCIM_SystemIdentification.IdentificationFormatsCIM_SystemIdentification.FormatDescriptions 2.7.0NamespaceInManager is an association describing the Namespaces hosted by a CIM ObjectManager.trueAntecedent11The ObjectManager containing a Namespace.trueDependenttrueThe Namespace in an ObjectManager.true true2.6.0SystemInNamespace is an association that allows enumeration of the system(s) represented in a Namespace.true11The Namespace containing management objects from one or more systems.truetrueIdentification information for systems in the Namespace.truetrueA list of enumerated values providing a high level description of the data contained and allowed in the Namespace. Additional clarification is provided in the DescriptionOfContainedData array.Indexed01234UnknownOtherLocal System DataData Aggregated from Multiple SystemsProxied DataCIM_SystemInNamespace.DescriptionOfContainedDatatrueAn array of free-form strings providing more detailed explanations for the data/objects contained in the Namespace, as described by the ContainedData array. Note, each entry of this array is related to the entry in the ContainedData array that is located at the same index.IndexedCIM_SystemInNamespace.ScopeOfContainedData 2.6.0IdentificationOfManagedSystem is an association that links the SystemIdentification object to the CIM_System(s) that are being identified and represented in the Namespace.trueAntecedent1The System which is identified.trueDependent1The SystemIdentification information.true 2.7.0CIM_CIMOMStatisticalData provides statistical data about the performance of the CIM Object Manager. Each object of this class provides elapsed time and size data for a particular type of CIM operation. All operations of that type, regardless of the CIM operations protocol being used, are accumulated in one object and covers the CIM operations issued by all clients of the Object Manager scoping the instance. Batched CIM operations are accumulated into a separate operation type for "Batched". The counters in this class SHOULD be implemented such that they always increment and naturally wrap around when their numerical limit is exceeded. A client that calculates the difference of two snapshots of a counter at the beginning and end of a measurement interval should get the correct result, even if there was a wrap-around in between obtaining the two snapshots. (Two or more wrap arounds will result in wrong data being calculated.) The gathering of the data can be controlled through the property, CIM_ObjectManager.GatherStatisticalData. The time interval to which the statistical data applies, ends at the current time and therefore includes the most current CIM operations. The interval starts when the statistical data gathering was last turned on for the Object Manager.InstanceIdThe InstanceId property opaquely identifies a unique instance of CIMOMStatisticalData and MUST be unique within a namespace. In order to ensure uniqueness, the value of InstanceIdD MUST be constructed in the following manner: CIM<ID> The <ID> MUST include a CIM Object Manager specified unique identifier.truetrueThe OperationType property identifies the type of CIM operation for which data is reported in this instance. Batched CIM operations (consisting of multiple simple CIM operations) are reported against the "Batched" type only.01234567891011121314151617181920212223242526UnknownOtherBatchedGetClassGetInstanceDeleteClassDeleteInstanceCreateClassCreateInstanceModifyClassModifyInstanceEnumerateClassesEnumerateClassNamesEnumerateInstancesEnumerateInstanceNamesExecQueryAssociatorsAssociatorNamesReferencesReferenceNamesGetPropertySetPropertyGetQualifierSetQualifierDeleteQualifierEnumerateQualifiersIndicationDeliveryCIM_CIMOMStatisticalData.OtherOperationTypeThe OtherOperationType property identifies the operation if the OperationType property has a value of 1 ("Other"). For all other values of OperationType, the property is NULL.64CIM_CIMOMStatisticalData.OperationTypetrueThe NumberOfOperations property contains the number of CIM operations of the specified type. This property can be used to calculate average values per CIM operation.truetrueThe CimomElapsedTime property contains the elapsed time spent in the CIM Object Manager for this operation type, not counting the elapsed time spent in providers and the underlying instrumentation. The measurement points for this property SHOULD be at the transport layer interface on the network side, and at the provider interface on the instrumentation side of the CIM Object Manager.truetrueThe ProviderElapsedTime property contains the elapsed time spent in all providers involved with this operation type, including the underlying instrumentation. The measurement point for this property SHOULD be from the provider interface of the CIM Object Manager.trueThe RequestSize property contains the size of the operation requests sent to the CIM Object Manager. Any overhead of protocols above the transport protocol SHOULD be included in the count. For example, for the HTTP protocol, the size would include the size of the HTTP payload and the size of the HTTP headers.trueBytesThe ResponseSize property contains the size of the operation responses sent back from the CIM Object Manager. Any overhead of protocols above the transport protocol SHOULD be included in the count. For example, for the HTTP protocol, the size would include the size of the HTTP payload and the size of the HTTP headers.trueBytes 2.6.0CIM_MemberPrincipal is an aggregation used to establish membership of principals (i.e., users) in a Collection. That membership can be established either directly or indirectly as indicated in the UsersAccessBy property. For example, a user may be identified directly by their userid (i.e., Account object instance) or the user may be identified indirectly by realm from which a ticket was issued (i.e., CredentialManagementService object instance). The latter case is useful, for example, for specifying that only users identified by an internal credential service are permitted to access very sensitive information.truetrueCollectiontruetrueThe Collection that aggregates members.MembertrueThe aggregated member of the Collection.A MemberPrincipal may be identifed in several ways that may be either direct or indirect membership in the collection. - A 'UsersAccess' membership directly identifies the user by the UsersAccess object instance. - An 'Account' membership directly identifies the user by the Account object class instance. - A 'UsingElement' membership indirectly identifies the user by the ManagedElement object instance that has ElementAsUser associations to UsersAccess object instances. Hence, all UsersAccess instances are indirectly included in the collection.1234UsersAccessAccountUsingElementCredentialManagementService truetrue2.6.0CIM_CollectionInSystem is an association used to establish a parent-child relationship between a collection and an 'owning' System such as an AdminDomain or ComputerSystem. A single collection should not have both a CollectionInOrganization and a CollectionInSystem association.true1trueThe parent system responsible for the collection.trueThe collection. true2.6.0OrganizationalEntity is an abstract class from which classes that fit into an organizational structure are derived. truetrue2.6.0CIM_OrgStructure is an association used to establish parent-child relationships between OrganizationalEntity instances. This is used to capture organizational relationships between object instances such as those that are imported from an LDAP-accessible directory.true1trueThe organizational parent in this association.trueThe organizational child in this association, i.e., the sub-unit or other owned object instance. truetrue2.6.0CIM_CollectionInOrganization is an association used to establish a parent-child relationship between a collection and an 'owning' OrganizationalEntity. A single collection should not have both a CollectionInOrganization and a CollectionInSystem association.true1trueThe parent organization responsible for the collection.trueThe collection. 2.6.0The Organization class is used to represent an organization such as a corporation or other autonomous entity. The class is defined so as to incorporate commonly-used LDAP attributes to permit implementations to easily derive this information from LDAP-accessible directories. This class's properties are a subset of a related class, OtherOrganizationInformation, which defines all the group properties and in array form for directory compatibility.true256CreationClassName 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.true1024The Name property defines the label by which the object is known. In the case of an LDAP-derived instance, the Name property value may be set to the distinguishedName of the LDAP-accessed object instance.128This property describes the kind of business performed by an organization.The organization's facsimile telephone number.This property contains the name of a locality, such as a city, county or other geographic region.Based on RFC1274, the mail box addresses for the organization as defined in RFC822.trueThe name of the organization.The Postal Address property values specify the address information required for the physical delivery of postal messages by the postal authority to the organization.40The Postal Code property specifies the postal code of the organization. If this value is present it will be part of the object's postal address.The State or Province Name property specifies a state or province.32The Telephone Number property specifies a telephone number of the organization, e.g. + 44 582 10101). 2.6.0The OtherOrganizationInformation class is used to provide additional information about an associated Organization instance. This class is defined so as to incorporate commonly-used LDAP attributes to permit implementations to easily derive this information from LDAP-accessible directories.true256CreationClassName 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.true1024The Name property defines the label by which the object is known. In the case of an LDAP-derived instance, the Name property value may be set to the distinguishedName of the LDAP-accessed object instance.In the case of an LDAP-derived instance, the ObjectClass property value(s) may be set to the objectClass attribute values.128This property describes the kind of business performed by an organization.1024The Descriptions property values may contain human-readable descriptions of the object. In the case of an LDAP-derived instance, the description attribute may have multiple values that, therefore, cannot be placed in the inherited Description property.128This property is used for the organization's telegram service.The organization's facsimile telephone number.16The organization's International ISDN number.Uniform Resource Identifier with optional label as defined in RFC2079.This property contains the name of a locality, such as a city, county or other geographic region.Based on RFC1274, the mail box addresses for the organization as defined in RFC822.The manager for the organization. In the case of an LDAP-derived instance, the Manager property value may contain the distinguishedName of the Manager.The name of the organization.Based on RFC1274, this property may be used for electronic mail box addresses other than RFC822 and X.400.128The Physical Delivery Office Name property specifies the name of the city, village, etc. where a physical delivery office is situated.The Postal Address property values specify the address information required for the physical delivery of postal messages by the postal authority to the organization.40The Postal Code property specifies the postal code of the organization. If this value is present it will be part of the object's postal address.40The Post Office Box property specifies the Post Office Box by which the organization will receive physical postal delivery. If present, the property value is part of the object's postal address.The Preferred Delivery Method property specifies the organization's preferred method to be used for communicating with it.This property specifies a postal address suitable for receipt of telegrams or expedited documents, where it is necessary to have the recipient accept delivery.This property value is for use by X.500 clients in constructing search filters.In the case of an LDAP-derived instance, the See Also property specifies distinguishedName of other Directory objects which may be other aspects (in some sense) of the same real world object.The State or Province Name property specifies a state or province.128The Street Address property specifies a site for the local distribution and physical delivery in a postal address, i.e. the street name, place, avenue, and the number.32The Telephone Number property specifies a telephone number of the organization, e.g. + 44 582 10101).The Teletex Terminal Identifier property specifies the Teletex terminal identifier (and, optionally, parameters) for a teletex terminal associated with the organization.The Telex Number property specifies the telex number, country code, and answerback code of a telex terminal for the organization.trueAn image of the organization logo.A unique identifier that may be assigned in an environment to differentiate between uses of a given named organization instance.trueIn the case of an LDAP-derived instance, the UserPassword property may contain an encrypted password used to access the organization's resources in a directory.15An X.121 address for the organization. 2.7.0CIM_MoreOrganizationInfo is an association used to extend the information in a CIM_Organization class instance.true11AntecedentThe Organization which has more information.true1DependentAdditional data concerning the Organization.true 2.6.0The OrgUnit class is used to represent a sub-unit of an organization such a division or department. The class is defined so as to incorporate commonly-used LDAP attributes to permit implementations to easily derive this information from LDAP-accessible directories. This class's properties are a subset of a related class, OtherOrgUnitInformation, which defines all the group properties and in array form for directory compatibility.true256CreationClassName 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.true1024The Name property defines the label by which the object is known. In the case of an LDAP-derived instance, the Name property value may be set to the distinguishedName of the LDAP-accessed object instance.128This property describes the kind of business performed by an organizational unit.The organizational unit's facsimile telephone number.This property contains the name of a locality, such as a city, county or other geographic region.trueThe name of the organizational unit.The Postal Address property values specify the address information required for the physical delivery of postal messages by the postal authority to the organizational unit.40The Postal Code property specifies the postal code of the organizational unit. If this value is present it will be part of the object's postal address.The State or Province Name property specifies a state or province.32The Telephone Number property specifies a telephone number of the organizational unit, e.g. + 44 582 10101). 2.6.0The OtherOrgUnitInformation class is used to provide additional information about an associated OrgUnit instance. This class is defined so as to incorporate commonly-used LDAP attributes to permit implementations to easily derive this information from LDAP-accessible directories.true256CreationClassName 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.true1024The Name property defines the label by which the object is known. In the case of an LDAP-derived instance, the Name property value may be set to the distinguishedName of the LDAP-accessed object instance.In the case of an LDAP-derived instance, the ObjectClass property value(s) may be set to the objectClass attribute values.128This property describes the kind of business performed by an organizational unit.1024The Descriptions property values may contain human-readable descriptions of the object. In the case of an LDAP-derived instance, the description attribute may have multiple values that, therefore, cannot be placed in the inherited Description property.128This property is used for the organizational unit's telegram service.The organizational unit's facsimile telephone number.16The organizational unit's International ISDN number.This property contains the name of a locality, such as a city, county or other geographic region.The name of the organizational unit.128The Physical Delivery Office Name property specifies the name of the city, village, etc. where a physical delivery office is situated.The Postal Address property values specify the address information required for the physical delivery of postal messages by the postal authority to the organizational unit.40The Postal Code property specifies the postal code of the organizational unit. If this value is present it will be part of the object's postal address.40The Post Office Box property specifies the Post Office Box by which the organizational unit will receive physical postal delivery. If present, the property value is part of the object's postal address.The Preferred Delivery Method property specifies the organizational unit's preferred method to be used for communicating with it.This property value is for use by X.500 clients in constructing search filters.In the case of an LDAP-derived instance, the See Also property specifies distinguishedName of other Directory objects which may be other aspects (in some sense) of the same real world object.The State or Province Name property specifies a state or province.128The Street Address property specifies a site for the local distribution and physical delivery in a postal address, i.e. the street name, place, avenue, and the number.32The Telephone Number property specifies a telephone number of the organizational unit, e.g. + 44 582 10101).The Teletex Terminal Identifier property specifies the Teletex terminal identifier (and, optionally, parameters) for a teletex terminal associated with the organizational unit.The Telex Number property specifies the telex number, country code, and answerback code of a telex terminal for the organization.trueIn the case of an LDAP-derived instance, the UserPassword property may contain an encrypted password used to access the organizational unit's resources in a directory.15An X.121 address for the organization. 2.7.0CIM_MoreOrgUnitInfo is an association used to extend the information in an CIM_OrgUnit class instance.true11AntecedentThe OrgUnit which has more information.true1DependentAdditional data concerning the OrgUnit.true true2.6.0UserEntity is an abstract class that represents users. 2.6.0CIM_SystemAdministrator is an association used to identify the UserEntity as a system administrator of a CIM_System.trueAntecedentThe administered system.trueDependentThe UserEntity that provides the admininstrative function for the associated system.true 2.7.0The Person object class is used to represent people. The class is defined so as to incorporate commonly-used LDAP attributes to permit implementations to easily derive this information from LDAP-accessible directories. This class's properties are a subset of a related class, OtherPersonInformation, which defines all the group properties and in array form for directory compatibility.true256CreationClassName 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.true1024The Name property defines the label by which the object is known. In the case of an LDAP-derived instance, the Name property value may be set to the distinguishedName of the LDAP-accessed object instance.128This property describes the kind of business performed by an organization.trueA Common Name is a (possibly ambiguous) name by which the role is commonly known in some limited scope (such as an organization) and conforms to the naming conventions of the country or culture with which it is associated.Based on inetOrgPerson, the Employee Number property specifies a numeric or an alphanumeric identifier assigned to a person.Based on inetOrgPerson, the Employee Type property is used to identify the employer to employee relationship. Typical values used may include 'Contractor', 'Employee', 'Intern', 'Temp', 'External', and 'Unknown' but any value may be used.The person's facsimile telephone number.The Given Name property is used for the part of a person's name that is not their surname nor their middle name (i.e., their first name).32Based on RFC1274, the Home Phone property specifies a home telephone number for the person, e.g. + 44 582 10101).The Home Postal Address property values specify the home address information required for the physical delivery of postal messages by the postal authority.From inetOrgPerson, the JPEG Phto property values may be used for one or more images of a person using the JPEG File Interchange Format.This property contains the name of a locality, such as a city, county or other geographic region.Based on RFC1274, the mail box addresses for the person as defined in RFC822.The person's manager within the organization. In the case of an LDAP-derived instance, the Manager property value may contain the distinguishedName of the Manager.32Based on RFC1274, the Mobile Phone property specifies a mobile telephone number for the person, e.g. + 44 582 10101).The name of an organizational unit related to the person.32Based on RFC1274, the Pager property specifies a pager telephone number for the person, e.g. + 44 582 10101).The Postal Address property values specify the address information required for the physical delivery of postal messages by the postal authority to the person.40The Postal Code property specifies the postal code of the organization. If this value is present it will be part of the object's postal address.Based on inetOrgPerson, the person's preferred written or spoken language.Based on RFC1274, the Secretary property may be used to specify a secretary for the person. In the case of an LDAP-derived object instance, the value may be a distinguishedName.The State or Province Name property specifies a state or province.trueThe Surname property specifies the linguistic construct that normally is inherited by an individual from the individual's parent or assumed by marriage, and by which the individual is commonly known.32The Telephone Number property specifies a telephone number of the organization, e.g. + 44 582 10101).The Title property may be used to specify the person's designated position or function of the object within an organization, e.g., Manager, Vice-President, etc.A User ID property. Based on RFC1274, the property may be used to specify a computer system login name. 2.7.0The OtherPersonInformation class is used to provide additional information about an associated Person instance. This class is defined so as to incorporate commonly-used LDAP attributes to permit implementations to easily derive this information from LDAP-accessible directories.true256CreationClassName 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.true1024The Name property defines the label by which the object is known. In the case of an LDAP-derived instance, the Name property value may be set to the distinguishedName of the LDAP-accessed object instance.In the case of an LDAP-derived instance, the ObjectClass property value(s) may be set to the objectClass attribute values.trueThe Audio property may be used to store an audio clip of the person.128This property describes the kind of business performed by an organization.128The Car License property is used to record the values of the vehicle license or registration plate associated with an individual.A Common Name is a (possibly ambiguous) name by which the role is commonly known in some limited scope (such as an organization) and conforms to the naming conventions of the country or culture with which it is associated.The Country Name property specifies a country as defined in ISO 3166.Based on inetOrgPerson, the Department Number is a code for department to which a person belongs. This can be strictly numeric (e.g., 1234) or alphanumeric (e.g., ABC/123).1024The Descriptions property values may contain human-readable descriptions of the object. In the case of an LDAP-derived instance, the description attribute may have multiple values that, therefore, cannot be placed in the inherited Description property.128This property is used for the organization's telegram service.Based on inetOrgPerson, the Display Name property values are used when displaying an entry.Based on inetOrgPerson, the Employee Number property specifies a numeric or an alphanumeric identifier assigned to a person.Based on inetOrgPerson, the Employee Type property is used to identify the employer to employee relationship. Typical values used may include 'Contractor', 'Employee', 'Intern', 'Temp', 'External', and 'Unknown' but any value may be used.The person's facsimile telephone number.Based on liPerson, the GenerationQualifier property specifies a name qualifier that represents the person's generation (e.g., JR., III, etc.).The Given Name property is used for the part of a person's name that is not their surname nor their middle name.Based on liPerson, the Home Fax property specifies the person's facsimile telephone number at home.32Based on RFC1274, the Home Phone property specifies a home telephone number for the person, e.g. + 44 582 10101).The Home Postal Address property values specify the home address information required for the physical delivery of postal messages by the postal authority.Based on inetOrgPerson, the Initials property specifies the first letters of the person's name, typically the property values will exclude the first letter of the surname.16The person's International ISDN number.From inetOrgPerson, the JPEG Phto property values may be used for one or more images of a person using the JPEG File Interchange Format.Uniform Resource Identifier with optional label as defined in RFC2079.This property contains the name of a locality, such as a city, county or other geographic region.Based on RFC1274, the mail box addresses for the person as defined in RFC822.The person's manager within the organization. In the case of an LDAP-derived instance, the Manager property value may contain the distinguishedName of the Manager.Based on liPerson, the middle name of the person.32Based on RFC1274, the Mobile Phone property specifies a mobile telephone number for the person, e.g. + 44 582 10101).trueThe name of the person's organization.Based on RFC1274, the OrganizationalStatus property specifies a category by which a person is often referred to within an organization. Examples of usage in academia might include undergraduate student, researcher, lecturer, etc.Based on RFC1274, this property may be used for electronic mail box addresses other than RFC822 and X.400.The name of an organizational unit related to the person.32Based on RFC1274, the Pager property specifies a pager telephone number for the person, e.g. + 44 582 10101).Based on liPerson, the PersonalTitle property may be used to specify the person's personal title such as Mr., Ms., Dr., Prof. etc.trueBased on RFC1274, the Photo property may be used to specify a photograph for the person encoded in G3 fax as explained in recommendation T.4, with an ASN.1 wrapper to make it compatible with an X.400 BodyPart as defined in X.420.128The Physical Delivery Office Name property specifies the name of the city, village, etc. where a physical delivery office is situated.The Postal Address property values specify the address information required for the physical delivery of postal messages by the postal authority to the person.40The Postal Code property specifies the postal code of the organization. If this value is present it will be part of the object's postal address.40The Post Office Box property specifies the Post Office Box by which the person will receive physical postal delivery. If present, the property value is part of the object's postal address.The Preferred Delivery Method property specifies the preferred method to be used for contacting the person.Based on inetOrgPerson, the person's preferred written or spoken language.This property specifies a postal address suitable for receipt of telegrams or expedited documents, where it is necessary to have the recipient accept delivery.Based on RFC1274, the Room Number property specifies the room number for the person.Based on RFC1274, the Secretary property may be used to specify a secretary for the person. In the case of an LDAP-derived object instance, the value may be a distinguishedName.In the case of an LDAP-derived instance, the See Also property specifies distinguishedName of other Directory objects which may be other aspects (in some sense) of the same real world object.The State or Province Name property specifies a state or province.128The Street Address property specifies a site for the local distribution and physical delivery in a postal address, i.e. the street name, place, avenue, and the number.The Surname property specifies the linguistic construct that normally is inherited by an individual from the individual's parent or assumed by marriage, and by which the individual is commonly known.32The Telephone Number property specifies a telephone number of the organization, e.g. + 44 582 10101).The Teletex Terminal Identifier property specifies the Teletex terminal identifier (and, optionally, parameters) for a teletex terminal associated with the organization.The Telex Number property specifies the telex number, country code, and answerback code of a telex terminal for the organization.trueA small image of the person's organization logo.trueA small image of the person.The Title property may be used to specify the person's designated position or function of the object within an organization, e.g., Manager, Vice-President, etc.Based on RFC1274, the UserID property may be used to specify a computer system login name.A unique identifier that may be assigned in an environment to differentiate between uses of a given named person instance.trueBased on inetOrgPerson and for directory compatibility, the User Certificate property may be used to specify a public key certificate for the person.trueIn the case of an LDAP-derived instance, the UserPassword property may contain an encrypted password used to access the person's resources in a directory.trueBased on inetOrgPerson and for directory compatibility, the UserPKCS12 property value may be used to provide a format for exchange of personal identity information. The property values are PFX PDUs stored as Octetstrings.trueBased on inetOrgPerson, the User S/MIME Certificate property may be used to specify the person's an S/MIME (RFC1847) signed message with a zero-length body. It contains the entire certificate chain and the signed attribute that describes their algorithm capabilities. If available, this property is preferred over the UserCertificate property for S/MIME applications.15An X.121 address for the organization.trueAn X.500 specified unique identifier that may be assigned in an environment to differentiate between uses of a given named person object instance. 2.7.0CIM_MorePersonInfo is an association used to extend the information in a CIM_Person class instance.true11AntecedentThe Person which has more information.true1DependentAdditional data concerning the Person.true 2.6.0The Group class is used to collect ManagedElements into groups. This class is defined so as to incorporate commonly-used LDAP attributes to permit implementations to easily derive this information from LDAP-accessible directories. This class's properties are a subset of a related class, OtherGroupInformation, which defines all the group properties and in array form for directory compatibility.true256CreationClassName 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.true1024The Name property defines the label by which the object is known. In the case of an LDAP-derived instance, the Name property value may be set to the distinguishedName of the LDAP-accessed object instance.128The BusinessCategory property may be used to describe the kind of business activity performed by the members of the group.trueA Common Name is a (possibly ambiguous) name by which the group is commonly known in some limited scope (such as an organization) and conforms to the naming conventions of the country or culture with which it is associated. 2.6.0The OtherGroupInformation class provides additional information about an associated Group instance. This class is defined so as to incorporate commonly-used LDAP attributes to permit implementations to easily derive this information from LDAP-accessible directories.true256CreationClassName 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.true1024The Name property defines the label by which the object is known. In the case of an LDAP-derived instance, the Name property value may be set to the distinguishedName of the LDAP-accessed object instance.In the case of an LDAP-derived instance, the ObjectClass property value(s) may be set to the objectClass attribute values.128The BusinessCategory property may be used to describe the kind of business activity performed by the members of the group.A Common Name is a (possibly ambiguous) name by which the group is commonly known in some limited scope (such as an organization) and conforms to the naming conventions of the country or culture with which it is associated.1024The Descriptions property values may contain human-readable descriptions of the object. In the case of an LDAP-derived instance, the description attribute may have multiple values that, therefore, cannot be placed in the inherited Description property.The name of an organization related to the group.The name of an organizational unit related to the group.The Owner property specifies the name of some object that has some responsibility for the group. In the case of an LDAP-derived instance, a property value for Owner may be a distinguishedName of owning persons, groups, roles, etc.In the case of an LDAP-derived instance, the See Also property specifies distinguishedName of other Directory objects which may be other aspects (in some sense) of the same real world object. 2.7.0CIM_MoreGroupInfo is an association used to extend the information in a CIM_Group class instance.true11AntecedentThe Group which has more information.true1DependentAdditional data concerning the Group.true 2.6.0CIM_SystemAdministratorGroup is an association used to identify a Group that has system administrator responsibilities for a CIM_System.trueAntecedentThe administered system.trueDependentThe Group of administrators.true 2.6.0The Role object class is used to represent a position or set of responsibilities within an organization, organizational unit or system administration scope and is filled by a person or persons (or non-human entities represented by ManagedSystemElement subclasses) that may be explicitly or implicitly members of this collection subclass. The class is defined so as to incorporate commonly-used LDAP attributes to permit implementations to easily derive this information from LDAP-accessible directories. The members of a role are frequently called role occupants. This class's properties are a subset of a related class, OtherRoleInformation, which defines all the group properties and in array form for directory compatibility.true256CreationClassName 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.true1024The Name property defines the label by which the object is known. In the case of an LDAP-derived instance, the Name property value may be set to the distinguishedName of the LDAP-accessed object instance.128This property may be used to describe the kind of business activity performed by the members (role occupants) in the position or set of responsibilities represented by the Role.trueA Common Name is a (possibly ambiguous) name by which the role is commonly known in some limited scope (such as an organization) and conforms to the naming conventions of the country or culture with which it is associated. 2.6.0The OtherRoleInformation class is used to provide additional information about an associated Role instance. This class is defined so as to incorporate commonly-used LDAP attributes to permit implementations to easily derive this information from LDAP-accessible directories.true256CreationClassName 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.true1024The Name property defines the label by which the object is known. In the case of an LDAP-derived instance, the Name property value may be set to the distinguishedName of the LDAP-accessed object instance.In the case of an LDAP-derived instance, the ObjectClass property value(s) may be set to the objectClass attribute values.128This property may be used to describe the kind of business activity performed by the members (role occupants) in the position or set of responsibilities represented by the Role.A Common Name is a (possibly ambiguous) name by which the role is commonly known in some limited scope (such as an organization) and conforms to the naming conventions of the country or culture with which it is associated.1024The Descriptions property values may contain human-readable descriptions of the object. In the case of an LDAP-derived instance, the description attribute may have multiple values that, therefore, cannot be placed in the inherited Description property.128This property is used for the role occupants' telegram service.The role occupants' facsimile telephone number.16The role occupants' International ISDN number.The name of an organizational unit related to the role.128The Physical Delivery Office Name property specifies the name of the city, village, etc. where a physical delivery office is situated.The Postal Address property values specify the address information required for the physical delivery of postal messages by the postal authority to the role occupants.40The Postal Code property specifies the postal code for the role occupants. If this value is present it will be part of the object's postal address.40The Post Office Box property specifies the Post Office Box by which the role occupants will receive physical postal delivery. If present, the property value is part of the object's postal address.The Preferred Delivery Method property specifies the role occupants' preferred method to be used for contacting them in their role.This property specifies a postal address suitable for receipt of telegrams or expedited documents, where it is necessary to have the recipient accept delivery.In the case of an LDAP-derived instance, the See Also property specifies distinguishedName of other Directory objects which may be other aspects (in some sense) of the same real world object.The State or Province Name property specifies a state or province.128The Street Address property specifies a site for the local distribution and physical delivery in a postal address, i.e. the street name, place, avenue, and the number.32The Telephone Number property specifies a telephone number of the role occupants, e.g. + 44 582 10101).The Teletex Terminal Identifier property specifies the Teletex terminal identifier (and, optionally, parameters) for a teletex terminal associated with the role occupants.The Telex Number property specifies the telex number, country code, and answerback code of a telex terminal for the role occupants.15An X.121 address for the role occupants. 2.7.0CIM_MoreRoleInfo is an association used to extend the information in a CIM_Role class instance.true11AntecedentThe Role which has more information.true1DependentAdditional data concerning the Role.true 2.6.0CIM_SystemAdministratorRole is an association used to identify a system administrator Role for a CIM_System.trueAntecedentThe administered system.trueDependentThe system administration role.true true2.6.0A service providing security functionaity. 2.6.0This relationship associates a Service with the SecurityServices that it uses.trueThe required Service.AntecedenttrueThe Service that is dependent on an underlying Service.Dependenttrue 2.6.0The CIM_SecurityServiceForSystem provides the association between a System and a SecurityService that provides services for that system. Examining the SecurityServiceForSystem 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 SecurityServiceForSystem will subclass from CIM_Dependency directly. trueThe SecurityService that provides services for the system.AntecedenttrueThe system that is dependent on the security service.Dependenttrue 2.6.0CIM_AuthenticationService verifies users' identities through some means. These services are decomposed into a subclass that provides credentials to users and a subclass that provides for the verification of the validity of a credential and, perhaps, the appropriateness of its use for access to target resources. The persistent state information used from one such verification to another is maintained in an Account for that Users Access on that AuthenticationService. 2.6.0CIM_VerificationService is the authentication service that verifies a credential for use and may also verify the appropriateness of a particular credential in conjunction with a particular target resource. 2.6.0CIM_CredentialManagementService issues credentials and manages the credential lifecycle. 2.6.0CIM_TrustHierarchy is an association between two CredentialManagementService instances that establishes the trust hierarchy between them.trueAntecedent1The superior CredentialManagementService from which the dependent service gets its authority.trueDependentThe subordinate CredentialManagementService.true 2.6.0CIM_CredentialManagementSAP represents the ability to utilize or invoke a CredentialManagementService.The URL for the access point. 2.6.0CIM_LocalCredentialManagementService is a credential management service that provides management of credentials used by the local system. 2.6.0CIM_AuthorizationService determines whether a user, by association with an Account used by the AuthorizationService, is permitted access a resource or set of resources. true2.7.0Subclasses of CIM_Credential define materials, information, or other data which are used to prove the identity of a CIM_UsersAccess to a particular CIM_SecurityService. Generally, there may be some shared information, or credential material which is used to identify and authenticate ones self in the process of gaining access to, or permission to use, an Account. Such credential material may be used to authenticate a users access identity initially, as done by a CIM_AuthenticationService (see later), and additionally on an ongoing basis during the course of a connection or other security association, as proof that each received message or communication came from the owning user access of that credential material.The date and time when the credential was issued. Use a value of all 0s if this information is not applicable.The date and time when the credential expires (and is not appropriate for use for authentication/authorization). Use a value of all 9s if this information is not applicable. Note that this property does not define how the expiration is set - but that there IS an expiration. The property may be set to either a specific date/time or an interval (calculated from the Issued datetime). For example, for Certificate Authority-signed public key, the expiration is determined by the CA. Another example is a voice mail password that expires 60 days after it is set/issued. 2.6.0This relationship associates a CredentialManagementService with the Credential it manages.trueAntecedent11The credential management service.trueDependentThe managed credential.true 2.6.0CIM_AuthenticationRequirement provides, through its associations, the authentication requirements for access to system resources. For a particular set of target resources, the AuthenticationService may require that credentials be issued by a specific CredentialManagementService. The AuthenticationRequirement class is weak to the system (e.g., Computer System or Administrative Domain) for which the requirements apply.CIM_System.CreationClassNametrue256Hosting system creation class name.CIM_System.Nametrue256Hosting system name.true256CreationClassName 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.true256NameThe Name property defines the unique label, in the context of the hosting system, by which the AuthenticationRequirement is known.The SecurityClassification property specifies a named level of security associated with the AuthenticationRequirement, e.g., 'Confidential', 'Top Secret', etc. 2.6.0CIM_HostedAuthenticationRequirement is an association used to provide the namespace scoping of AuthenticationRequirement. The hosted requirements may or may not apply to resources on the hosting system.true11AntecedentThe hosting system.trueDependenttrueThe hosted AuthenticationRequirement.true 2.6.0CIM_AuthenticateForUse is an association used to provide an AuthenticationService with the AuthenticationRequirement it needs to do its job.trueAntecedentAuthenticationRequirement for use.trueDependentAuthenticationService that uses the requirements.true 2.6.0CIM_RequireCredentialsFrom is an association used to require that credentials are issued by particular Credential Management Services in order to authenticate a user.trueAntecedentCredentialManagementService from which credentials are accepted for the associated AuthenticationRequirement.trueDependentAuthenticationRequirement that limit acceptable credentials.true 2.6.0CIM_AuthenticationTarget is an association used to apply authentication requirements for access to specific resources. For example, a shared secret may be sufficient for access to unclassified resources, but for confidential resources, a stronger authentication may be required.trueAntecedentAuthenticationRequirement that apply to specific resources.trueDependentTarget resources that may be in a Collection or an individual ManagedElement. These resources are protected by the AuthenticationRequirement.true 2.6.0The Kerberos KDC.The Realm served by this KDC.Nametrue256The version of Kerberos supported by this service.0123V4V5DCEMS 2.7.0A CIM_KerberosTicket represents a credential issued by a particular Kerberos Key Distribution Center (KDC) to a particular CIM_UsersAccess as the result of a successful authentication process. There are two types of tickets that a KDC may issue to a Users Access - a TicketGranting ticket, which is used to protect and authenticate communications between the Users Access and the KDC, and a Session ticket, which the KDC issues to two Users Access to allow them to communicate with each other.CIM_KerberosKeyDistributionCenter.SystemCreationClassNametrue256The scoping System's CCN.CIM_KerberosKeyDistributionCenter.SystemNametrue256The scoping System's Name.CIM_KerberosKeyDistributionCenter.CreationClassNametrue256The scoping Service's CCN.CIM_KerberosKeyDistributionCenter.Nametrue256The scoping Service's Name. The Kerberos KDC Realm of CIM_KerberosTicket is used to record the security authority, or Realm, name so that tickets issued by different Realms can be separately managed and enumerated.true256The name of the service for which this ticket is used.true256RemoteID is the name by which the user is known at the KDC security service.The Type of CIM_KerberosTicket is used to indicate whether the ticket in question was issued by the Kerberos Key Distribution Center (KDC) to support ongoing communication between the Users Access and the KDC ("TicketGranting"), or was issued by the KDC to support ongoing communication between two Users Access entities ("Session").01SessionTicketGranting 2.6.0The KDC issues and owns Kerberos tickets. This association captures the relationship between the KDC and its issued tickets.true11The issuing KDC.AntecedenttruetrueThe managed credential.Dependenttrue 2.6.0A Certificate Authority (CA) is a credential management service that issues and cryptographically signs certificates thus acting as an trusted third-party intermediary in establishing trust relationships. The CA authenicates the holder of the private key related to the certificate's public key; the authenicated entity is represented by the UsersAccess class.The CAPolicyStatement describes what care is taken by the CertificateAuthority when signing a new certificate. The CAPolicyStatment may be a dot-delimited ASN.1 OID string which identifies to the formal policy statement.trueA CRL, or CertificateRevocationList, is a list of certificates which the CertificateAuthority has revoked and which are not yet expired. Revocation is necessary when the private key associated with the public key of a certificate is lost or compromised, or when the person for whom the certificate is signed no longer is entitled to use the certificate.Certificate Revocation Lists may be available from a number of distribution points. CRLDistributionPoint array values provide URIs for those distribution points.Certificates refer to their issuing CA by its Distinguished Name (as defined in X.501).trueThe frequency, expressed in hours, at which the CA will update its Certificate Revocation List. Zero implies that the refresh frequency is unknown.HoursThe maximum number of certificates in a certificate chain permitted for credentials issued by this certificate authority or it's subordinate CAs. The MaxChainLength of a superior CA in the trust hierarchy should be greater than this value and the MaxChainLength of a subordinate CA in the trust hierarchy should be less than this value. 2.6.0CIM_PublicKeyManagementService is a credential management service that provides local system management of public keys used by the local system. 2.6.0A Public Key Certificate is a credential that is cryptographically signed by a trusted Certificate Authority (CA) and issued to an authenticated entity (e.g., human user, service,etc.) called the Subject in the certificate and represented by the UsersAccess class. The public key in the certificate is cryptographically related to a private key that is to be held and kept private by the authenticated Subject. The certificate and its related private key can then be used for establishing trust relationships and securing communications with the Subject. Refer to the ITU/CCITT X.509 standard as an example of such certificates.CIM_CertificateAuthority.SystemCreationClassNametrue256The scoping System's CCN.CIM_CertificateAuthority.SystemNametrue256The scoping System's Name.CIM_CertificateAuthority.CreationClassNametrue256The scoping Service's CCN.CIM_CertificateAuthority.Nametrue256The scoping Service's Name.true256Certificate subject identifier.256Alternate subject identifier for the Certificate.trueThe DER-encoded raw public key. 2.6.0A CertificateAuthority may have certificates issued by other CAs. This association is essentially an optimization of the CA having a UsersAccess instance with an association to a certificate thus mapping more closely to LDAP-based certificate authority implementations.true1AntecedentThe Certificate used by the CA.trueDependentThe CA that uses a Certificate.true 2.7.0This relationship associates a CertificateAuthority with the certificates it signs.true11The CA which signed the certificate.AntecedenttruetrueThe certificate issued by the CA.DependenttrueThe Serial Number.trueThe Signature.CIM_Credential.ExpiresThe time it expires.The Authority's revocation list distribution points. 2.6.0A CIM_UnsignedPublicKey represents an unsigned public key credential. The local UsersAccess (or subclass thereof) accepts the public key as authentic because of a direct trust relationship rather than via a third-party Certificate Authority.CIM_PublicKeyManagementService.SystemCreationClassNametrue256The scoping System's CCN.CIM_PublicKeyManagementService.SystemNametrue256The scoping System's Name.CIM_PublicKeyManagementService.CreationClassNametrue256The scoping Service's CCN.CIM_PublicKeyManagementService.Nametrue256The scoping Service's Name.true256The Identity of the Peer with whom a direct trust relationship exists. The public key may be used for security functions with the Peer.CIM_PublicKeyManagementService.PeerIdentityTypePeerIdentityType is used to describe the type of the PeerIdentity. The currently defined values are used for IKE identities.01234567891011OtherIPV4_ADDRFQDNUSER_FQDNIPV4_ADDR_SUBNETIPV6_ADDRIPV6_ADDR_SUBNETIPV4_ADDR_RANGEIPV6_ADDR_RANGEDER_ASN1_DNDER_ASN1_GNKEY_IDCIM_PublicKeyManagementService.PeerIdentitytrueThe DER-encoded raw public key. 2.6.0CIM_LocallyManagedPublicKey association provides the relationship between a PublicKeyManagementService and an UnsignedPublicKey.true11The PublicKeyManagementService that manages an unsigned public key.AntecedenttruetrueAn unsigned public key.Dependenttrue 2.6.0CIM_SharedSecretService is a service which ascertains whether messages received are from the Principal with whom a secret is shared. Examples include a login service that proves identity on the basis of knowledge of the shared secret, or a transport integrity service (like Kerberos provides) that includes a message authenticity code that proves each message in the messsage stream came from someone who knows the shared secret session key.256The Algorithm used to convey the shared secret, such as HMAC-MD5,or PLAINTEXT.The Protocol supported by the SharedSecretService. 2.6.0CIM_SharedSecret is the secret shared between a Users Access and a particular SharedSecret security service. Secrets may be in the form of a password used for initial authentication, or as with a session key, used as part of a message authentication code to verify that a message originated by the pricinpal with whom the secret is shared. It is important to note that SharedSecret is not just the password, but rather is the password used with a particular security service.CIM_SharedSecretService.SystemCreationClassNametrue256The scoping System's CCN.CIM_SharedSecretService.SystemNametrue256The scoping System's Name.CIM_SharedSecretService.CreationClassNametrue256The scoping Service's CCN.CIM_SharedSecretService.Nametrue256The scoping Service's Name.true256RemoteID is the name by which the user is known at the remote secret key authentication service.The secret known by the Users Access.The transformation algorithm, if any, used to protect passwords before use in the protocol. For instance, Kerberos doesn't store passwords as the shared secret, but rather, a hash of the password.The protocol with which the SharedSecret is used. 2.6.0This relationship associates a SharedSecretService with the SecretKey it verifies.true11The credential management service.AntecedenttruetrueThe managed credential.Dependenttrue 2.6.0CIM_NamedSharedIKESecret indirectly represents a shared secret credential. The local identity, IKEIdentity, and the remote peer identity share the secret that is named by the SharedSecretName. The SharedSecretName is used SharedSecretService to reference the secret.CIM_SharedSecretService.SystemCreationClassNametrue256The scoping System's CCN.CIM_SharedSecretService.SystemNametrue256The scoping System's Name.CIM_SharedSecretService.CreationClassNametrue256The scoping Service's CCN.CIM_SharedSecretService.Nametrue256The scoping Service's Name.true256The local Identity with whom the direct trust relationship exists.CIM_NamedSharedIKESecret.LocalIdentityTypetrueLocalIdentityType is used to describe the type of the LocalIdentity.1234567891011IPV4_ADDRFQDNUSER_FQDNIPV4_ADDR_SUBNETIPV6_ADDRIPV6_ADDR_SUBNETIPV4_ADDR_RANGEIPV6_ADDR_RANGEDER_ASN1_DNDER_ASN1_GNKEY_IDCIM_NamedSharedIKESecret.LocalIdentitytrue256The peer identity with whom the direct trust relationship exists.CIM_NamedSharedIKESecret.PeerIdentityTypetruePeerIdentityType is used to describe the type of the PeerIdentity.1234567891011IPV4_ADDRFQDNUSER_FQDNIPV4_ADDR_SUBNETIPV6_ADDRIPV6_ADDR_SUBNETIPV4_ADDR_RANGEIPV6_ADDR_RANGEDER_ASN1_DNDER_ASN1_GNKEY_IDCIM_NamedSharedIKESecret.PeerIdentitySharedSecretName is an indirect reference to a shared secret. The SecretService does not expose the actual secret but rather provides access to the secret via a name. 2.6.0CIM_IKESecretIsNamed association provides the relationship between a SharedSecretService and a NamedSharedIKESecret.true11The SharedSecretService that manages a NamedSharedIKESecret.AntecedenttruetrueThe managed NamedSharedIKESecret.Dependenttrue 2.6.0The UsersAccess object class is used to specify a system user that permitted access to system resources. The ManagedElement that has access to system resources (represented in the model in the ElementAsUser association) may be a person, a service, a service access point or any collection thereof. Whereas the Account class represents the user's relationship to a system from the perspective of the security services of the system, the UserAccess class represents the relationships to the systems independent of a particular system or service.true256CreationClassName 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.true256The Name property defines the label by which the object is known.trueThe ElementID property uniquely specifies the ManagedElement object instance that is the user represented by the UsersAccess object instance. The ElementID is formatted similarly to a model path except that the property-value pairs are ordered in alphabetical order (US ASCII lexical order).Biometric information used to identify a person. The property value is left null or set to 'N/A' for non-human user or a user not using biometric information for authentication.012345678N/AOtherFacialRetinaMarkFingerVoiceDNA-RNAEEG 2.6.0CIM_ElementAsUser is an association used to establish the 'ownership' of UsersAccess object instances. That is, the ManagedElement may have UsersAccess to systems and, therefore, be 'users' on those systems. UsersAccess instances must have an 'owning' ManagedElement. Typically, the ManagedElements will be limited to Collection, Person, Service and ServiceAccessPoint. Other non-human ManagedElements that might be thought of as having UsersAccess (e.g., a device or system) have services that have the UsersAccess.true11AntecedentThe ManagedElement that has UsersAccess.trueDependentThe 'owned' UsersAccess.true 2.6.0CIM_UsersCredential is an association used to establish the credentials that may be used for a UsersAccess to a system or set of systems.trueAntecedentThe issued credential that may be used.trueDependentThe UsersAccess that has use of a credential.true 2.6.0CIM_Notary is an AuthenticationService (credential management service) which compares the biometric characteristics of a person with the known characteristics of a Users Access, and determines whether the person is the UsersAccess. An example is a bank teller who compares a picture ID with the person trying to cash a check, or a biometric login service that uses voice recognition to identify a user.The types of biometric information which this Notary can compare.012345678N/AOtherFacialRetinaMarkFingerVoiceDNA-RNAEEGThe SealProtocol is how the decision of the Notary is recorded for future use by parties who will rely on its decision. For instance, a drivers licence frequently includes tamper-resistent coatings and markings to protect the recorded decision that a driver, having various biometric characteristics of height, weight, hair and eye color, using a particular name, has features represented in a photograph of their face.CharterIssued documents when the Notary is first authorized, by whoever gave it responsibility, to perform its service.CharterExpired documents when the Notary is no longer authorized, by whoever gave it responsibility, to perform its service. 2.6.0This relationship associates a Notary service with the Users Access whose biometric information is verified.trueAntecedentThe Notary service that verifies biometric information.trueDependentThe UsersAccess that represents a person using biometric information for authentication.true 2.6.0This relationship associates a PublicKeyCertificate with the Principal who has the PrivateKey used with the PublicKey. The PrivateKey is not modeled, since it is not a data element that ever SHOULD be accessible via management applications, other than key recovery services, which are outside our scope.trueAntecedentThe issued credential that may be used.trueDependentThe UsersAccess that has use of a credential.trueThe Certificate may be used for signature only or for confidentiality as well as signature.01SignOnlyConfidentialityOrSignatureIndicates if the certificate can be NonRepudiation.Indicates if the certificate can be backed up.The repository in which the certificate is backed up. 2.6.0CIM_Account is the information held by a SecurityService to track identity and privileges managed by that service. Common examples of an Account are the entries in a UNIX /etc/passwd file. Several kinds of security services use various information from those entries - the /bin/login program uses the account name ('root') and hashed password to authenticate users, and the file service, for instance, uses the UserID field ('0') and GroupID field ('0') to record ownership and determine access control privileges on files in the file system. This class is defined so as to incorporate commonly-used LDAP attributes to permit implementations to easily derive this information from LDAP-accessible directories.CIM_System.CreationClassNametrue256The scoping System's CCN.CIM_System.Nametrue256The scoping System's Name.true256CreationClassName 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.trueName1024The Name property defines the label by which the object is known. The value of this property may be set to be the same as that of the UserID property or, in the case of an LDAP-derived instance, the Name property value may be set to the distinguishedName of the LDAP-accessed object instance.256UserID is the value used by the SecurityService to represent identity. For an authentication service, the UserID may be the name of the user, or for an authorization service the value which serves as a handle to a mapping of the identity.In the case of an LDAP-derived instance, the ObjectClass property value(s) may be set to the objectClass attribute values.1024The Descriptions property values may contain human-readable descriptions of the object. In the case of an LDAP-derived instance, the description attribute may have multiple values that, therefore, cannot be placed in the inherited Description property.Based on RFC1274, the host name of the system(s) for which the account applies. The host name may be a fully-qualified DNS name or it may be an unqualified host name.This property contains the name of a locality, such as a city, county or other geographic region.trueThe name of the organization related to the account.The name of an organizational unit related to the account.In the case of an LDAP-derived instance, the See Also property specifies distinguishedName of other Directory objects which may be other aspects (in some sense) of the same real world object.trueBased on inetOrgPerson and for directory compatibility, the User Certificate property may be used to specify a public key certificate for the person.trueIn the case of an LDAP-derived instance, the UserPassword property may contain an encrypted password used to access the person's resources in a directory. 2.6.0A system (e.g., ApplicationSystem, ComputerSystem, AdminDomain) aggregates Accounts and scopes the uniqueness of the Account names (i.e., userids).truetrue11The aggregating system also provides name scoping for the Account.GroupComponenttruetruetrueThe subordinate Account.PartComponenttrue 2.6.0This relationship associates UsersAccess with the Accounts with which they're able to interact.trueAntecedentThe user's Account.trueDependentThe User as identified by their UsersAccess instance.true 2.6.0This relationship may be used to associate an Account used by an AuthenticationService to an Account used for Authorization. For instance, this mapping occurs naturally in the UNIX /etc/passwd file, where the AuthenticationSerice Account ('root') is mapped to the AuthorizationService Account ('0'). The two are separate accounts, as evidenced by the ability to have another AuthenticationService Account which ALSO maps to the AuthorizationService Account ('0') without ambiguity. This association may be used for other account mappings as well such as for coordinating single signon for multiple accounts for the same user.trueAntecedentAn Account.trueDependentA related Account.true 2.6.0This relationship associates SecurityService instances to the Accounts they use in the course of their work.trueAntecedenttrueAntecedent represents the independent object in this association.DependenttrueDependent represents the object dependent on the Antecedent. 2.6.0CIM_AccountManagementService creates, manages, and if necessary destroys Accounts on behalf of other SecuritySerices. 2.6.0This relationship associates the AccountManagement security service to the Accounts for which it is responsible.trueAntecedenttrueAntecedent represents the independent object in this association.DependenttrueDependent represents the object dependent on the Antecedent. 2.6.0The CIM_ManagesAccountOnSystem provides the association between a System and the AccountManagementService that manages accounts for that system.trueAn AccountManagementService that manages accounts for the system.AntecedenttrueThe system that is dependent on the AccountManagementService.Dependenttrue 2.6.0CIM_AccessControlInformation provides, through its properties and its associations, the specification of the access rights granted to a set of subject users to a set of target resources. The AccessControlInformation class is weak to the system (e.g., Computer System or Administrative Domain) for which the access controls apply.CIM_System.CreationClassNametrue256Hosting system creation class name.CIM_System.Nametrue256Hosting system name.true256CreationClassName 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.true256NameThe Name property defines the unique label, in the context of the hosting system, by which the AccessControlInformation is known.The SecurityClassification property specifies a named level of security associated with the AccessControlInformation, e.g., 'Confidential', 'Top Secret', etc.The AccessType property is an array of string values that specifies the type of access for which the corresponding permission applies. For example, it can be used to specify a generic access such as 'Read-only', 'Read/Write', etc. for file or record access control or it can be used to specifiy an entry point name for service access control.CIM_AccessControlInformation.AccessQualifierCIM_AccessControlInformation.PermissionThe AccessQualifier property is an array of string values may be used to further qualify the type of access for which the corresponding permission applies. For example, it may be used to specify a set of parameters that are permitted or denied in conjunction with the corresponding AccessType entry point name.CIM_AccessControlInformation.AccessTypeCIM_AccessControlInformation.PermissionThe Permission property is an array of string values indicating the permission that applies to the corrsponding AccessType and AccessQualifier array values. The values may be extended in subclasses to provide more specific access controls.UnknownAllowDenyManageCIM_AccessControlInformation.AccessTypeCIM_AccessControlInformation.AccessQualifier 2.6.0CIM_HostedACI is an association used to provide the namespace scoping of AccessControlInformation. The hosted ACI may or may not apply to resources on the hosting system.true11AntecedentThe hosting system.trueDependenttrueThe hosted AccessControlInformation.true 2.6.0CIM_AuthorizedUse is an association used to provide an AuthorizationService with the AccessControlInformation it needs to do its job.trueAntecedentAccess Control Information.trueDependentAuthorizationService that uses an ACI.true 2.6.0CIM_AuthorizationSubject is an association used to apply authorization decisions to specific subjects (i.e., users). The subjects may be identified directly or they may be aggregated into a collection that may, in turn, use the MemberPrincipal association to provide further indirection in the specification of the subject set.trueAntecedentAccessControlInformation that applies to a subject set.trueDependentThe subject set may be specified as a collection or as a set of associations to ManagedElements that represent users.true 2.6.0CIM_AuthorizationTarget is an association used to apply authorization decisions to specific target resources. The target resources may be aggregated into a collection or may be represented as a set of associations to ManagedElements.trueAntecedentAccessControlInformation that applies to the target set.trueDependentThe target set of resources may be specified as a collection or as a set of associations to ManagedElements that represent target resources.true true2.6.0An abstract class defining the common properties of the policy managed elements derived from CIM_Policy. The subclasses are used to create rules and groups of rules that work together to form a coherent set of policies within an administrative domain or set of domains.A user-friendly name of this policy-related object.An array of keywords for characterizing / categorizing policy objects. Keywords are of one of two types: - Keywords defined in this and other MOFs, or in DMTFwhite papers. These keywords provide a vendor-independent, installation-independent way of characterizing policy objects. - Installation-dependent keywords for characterizing policy objects. Examples include 'Engineering', 'Billing', and 'Review in December 2000'. This MOF defines the following keywords: 'UNKNOWN', 'CONFIGURATION', 'USAGE', 'SECURITY', 'SERVICE', 'MOTIVATIONAL', 'INSTALLATION', and 'EVENT'. These concepts are self-explanatory and are further discussed in the SLA/Policy White Paper. One additional keyword is defined: 'POLICY'. The role of this keyword is to identify policy-related instances that may not be otherwise identifiable, in some implementations. The keyword 'POLICY' is NOT mutually exclusive of the other keywords specified above. true2.7.0PolicySet is an abstract class that represents a set of policies that form a coherent set. The set of contained policies has a common decision strategy and a common set of policy roles. Subclasses include PolicyGroup and PolicyRule.PolicyDecisionStrategy defines the evaluation method used for policies contained in the PolicySet. FirstMatching enforces the actions of the first rule that evaluates to TRUE. It is the only value currently defined.1First MatchingThe PolicyRoles property represents the roles associated with a PolicySet. All contained PolicySet instances inherit the values of the PolicyRoles of the aggregating PolicySet but the values are not copied. A contained PolicySet instance may, however, add additional PolicyRoles to those it inherits from its aggregating PolicySet(s). Each value in PolicyRoles multi-valued property represents a role for which the PolicySet applies, i.e., the PolicySet should be used by any enforcement point that assumes any of the listed PolicyRoles values. Although not officially designated as 'role combinations', multiple roles may be specified using the form: <RoleName>[&&<RoleName>]* where the individual role names appear in alphabetical order (according to the collating sequence for UCS-2). Implementations may treat PolicyRoles values that are specified as 'role combinations' as simple strings.Indicates whether this PolicySet is administratively enabled, administratively disabled, or enabled for debug. The "EnabledForDebug" property value is deprecated and, when it or any value not understood by the receiver is specified, the receiving enforcement point treats the PolicySet as "Disabled". To determine if a PolicySet is "Enabled", the containment hierarchy specified by the PolicySetComponent aggregation is examined and the Enabled property values of the hierarchy are ANDed together. Thus, for example, everything aggregated by a PolicyGroup may be disabled by setting the Enabled property in the PolicyGroup instance to "Disabled" without changing the Enabled property values of any of the aggregated instances. The default value is 1 ("Enabled").123EnabledDisabledEnabled For Debug1 2.6.0An aggregation of PolicySet instances (PolicyGroups and/or PolicyRules) that have the same decision strategy and inherit policy roles. PolicyGroup instances are defined and named relative to the CIM_System that provides their context.CIM_System.CreationClassNametrue256The scoping System's CreationClassName.CIM_System.Nametrue256The scoping System's Name.true256CreationClassName 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.true256A user-friendly name of this PolicyGroup. 2.7.0The central class used for representing the 'If Condition then Action' semantics of a policy rule. A PolicyRule condition, in the most general sense, is represented as either an ORed set of ANDed conditions (Disjunctive Normal Form, or DNF) or an ANDed set of ORed conditions (Conjunctive Normal Form, or CNF). Individual conditions may either be negated (NOT C) or unnegated (C). The actions specified by a PolicyRule are to be performed if and only if the PolicyRule condition (whether it is represented in DNF or CNF) evaluates to TRUE. The conditions and actions associated with a PolicyRule are modeled, respectively, with subclasses of PolicyCondition and PolicyAction. These condition and action objects are tied to instances of PolicyRule by the PolicyConditionInPolicyRule and PolicyActionInPolicyRule aggregations. A PolicyRule may also be associated with one or more policy time periods, indicating the schedule according to which the policy rule is active and inactive. In this case it is the PolicySetValidityPeriod aggregation that provides this linkage. The PolicyRule class uses the property ConditionListType, to indicate whether the conditions for the rule are in DNF (disjunctive normal form), CNF (conjunctive normal form) or, in the case of a rule with no conditions, as an UnconditionalRule. The PolicyConditionInPolicyRule aggregation contains two additional properties to complete the representation of the Rule's conditional expression. The first of these properties is an integer to partition the referenced PolicyConditions into one or more groups, and the second is a Boolean to indicate whether a referenced Condition is negated. An example shows how ConditionListType and these two additional properties provide a unique representation of a set of PolicyConditions in either DNF or CNF. Suppose we have a PolicyRule that aggregates five PolicyConditions C1 through C5, with the following values in the properties of the five PolicyConditionInPolicyRule associations: C1: GroupNumber = 1, ConditionNegated = FALSE C2: GroupNumber = 1, ConditionNegated = TRUE C3: GroupNumber = 1, ConditionNegated = FALSE C4: GroupNumber = 2, ConditionNegated = FALSE C5: GroupNumber = 2, ConditionNegated = FALSE If ConditionListType = DNF, then the overall condition for the PolicyRule is: (C1 AND (NOT C2) AND C3) OR (C4 AND C5) On the other hand, if ConditionListType = CNF, then the overall condition for the PolicyRule is: (C1 OR (NOT C2) OR C3) AND (C4 OR C5) In both cases, there is an unambiguous specification of the overall condition that is tested to determine whether to perform the PolicyActions associated with the PolicyRule. PolicyRule instances may also be used to aggregate other PolicyRules and/or PolicyGroups. When used in this way to implement nested rules, the conditions of the aggregating rule apply to the subordinate rules as well. However, any side effects of condition evaluation or the execution of actions MUST NOT affect the result of the evaluation of other conditions evaluated by the rule engine in the same evaluation pass. That is, an implementation of a rule engine MAY evaluate all conditions in any order before applying the priority and determining which actions are to be executed.CIM_System.CreationClassNametrue256The scoping System's CreationClassName.CIM_System.Nametrue256The scoping System's Name.true256CreationClassName 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.true256A user-friendly name of this PolicyRule.Indicates whether the list of PolicyConditions associated with this PolicyRule is in disjunctive normal form (DNF), conjunctive normal form (CNF), or has no conditions (i.e., is an UnconditionalRule) and is automatically evaluated to "True." The default value is 1 ("DNF").012Unconditional RuleDNFCNF1A free-form string that can be used to provide guidelines on how this PolicyRule should be used.CIM_PolicySetComponent.PriorityPolicyRule.Priority is deprecated and replaced by providing the priority for a rule (and a group) in the context of the aggregating PolicySet instead of the priority being used for all aggregating PolicySet instances. Thus, the assignment of priority values is much simpler. A non-negative integer for prioritizing this PolicyRule relative to other Rules. A larger value indicates a higher priority. The default value is 0.No ValueA flag indicating that the evaluation of the PolicyConditions and execution of PolicyActions (if the Conditions evaluate to TRUE) is required. The evaluation of a PolicyRule MUST be attempted if the Mandatory property value is TRUE. If the Mandatory property is FALSE, then the evaluation of the Rule is 'best effort' and MAY be ignored.This property gives a policy administrator a way of specifying how the ordering of the PolicyActions associated with this PolicyRule is to be interpreted. Three values are supported: o mandatory(1): Do the actions in the indicated order, or don't do them at all. o recommended(2): Do the actions in the indicated order if you can, but if you can't do them in this order, do them in another order if you can. o dontCare(3): Do them -- I don't care about the order. The default value is 3 ("DontCare").123MandatoryRecommendedDont Care3ExecutionStrategy defines the strategy to be used in executing the sequenced actions aggregated by this PolicyRule. There are three execution strategies: Do Until Success - execute actions according to predefined order, until successful execution of a single action. Do All - execute ALL actions which are part of the modeled set, according to their predefined order. Continue doing this, even if one or more of the actions fails. Do Until Failure - execute actions according to predefined order, until the first failure in execution of an action instance.123Do Until SuccessDo AllDo Until Failure 2.6.0A class representing an administratively defined container for reusable policy-related information. This class does not introduce any additional properties beyond those in its superclass AdminDomain. It does, however, participate in a unique association for containing policy elements. An instance of this class uses the NameFormat value"ReusablePolicyContainer". CIM_ReusablePolicyContainer2.7.0The term 'PolicyRepository' has been confusing to both developers and users of the model. The replacement class name describes model element properly and is less likely to be confused with a data repository. A class representing an administratively defined container for reusable policy-related information. This class does not introduce any additional properties beyond those in its superclass AdminDomain. It does, however, participate in a number of unique associations. An instance of this class uses the NameFormat value"PolicyRepository". true2.6.0A class representing a rule-specific or reusable policy condition to be evaluated in conjunction with a PolicyRule. Since all operational details of a PolicyCondition are provided in subclasses of this object, this class is abstract.true256The name of the class or the subclass used in the creation of the System object in whose scope this PolicyCondition is defined. This property helps to identify the System object in whose scope this instance of PolicyCondition exists. For a rule-specific PolicyCondition, this is the System in whose context the PolicyRule is defined. For a reusable PolicyCondition, this is the instance of PolicyRepository (which is a subclass of System) that holds the Condition. Note that this property, and the analogous property SystemName, do not represent propagated keys from an instance of the class System. Instead, they are properties defined in the context of this class, which repeat the values from the instance of System to which this PolicyCondition is related, either directly via the PolicyConditionInPolicyRepository association or indirectly via the PolicyConditionInPolicyRule aggregation.true256The name of the System object in whose scope this PolicyCondition is defined. This property completes the identification of the System object in whose scope this instance of PolicyCondition exists. For a rule-specific PolicyCondition, this is the System in whose context the PolicyRule is defined. For a reusable PolicyCondition, this is the instance of PolicyRepository (which is a subclass of System) that holds the Condition.true256For a rule-specific PolicyCondition, the CreationClassName of the PolicyRule object with which this Condition is associated. For a reusable PolicyCondition, a special value, 'NO RULE', should be used to indicate that this Condition is reusable and not associated with a single PolicyRule.true256For a rule-specific PolicyCondition, the name of the PolicyRule object with which this Condition is associated. For a reusable PolicyCondition, a special value, 'NO RULE', should be used to indicate that this Condition is reusable and not associated with a single PolicyRule.true256CreationClassName 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.true256A user-friendly name of this PolicyCondition. 2.7.0This class provides a means of representing the time periods during which a PolicySet is valid, i.e., active. At all times that fall outside these time periods, the PolicySet has no effect. A PolicySet is treated as valid at ALL times, if it does not specify a PolicyTimePeriodCondition. In some cases a Policy Consumer may need to perform certain setup / cleanup actions when a PolicySet becomes active / inactive. For example, sessions that were established while a PolicySet was active might need to be taken down when the PolicySet becomes inactive. In other cases, however, such sessions might be left up. In this case, the effect of deactivating the PolicySet would just be to prevent the establishment of new sessions. Setup / cleanup behaviors on validity period transitions are not currently addressed by the Policy Model, and must be specified in 'guideline' documents or via subclasses of CIM_PolicySet, CIM_PolicyTimePeriodCondition or other concrete subclasses of CIM_Policy. If such behaviors need to be under the control of the policy administrator, then a mechanism to allow this control must also be specified in the subclasses. PolicyTimePeriodCondition is defined as a subclass of PolicyCondition. This is to allow the inclusion of time-based criteria in the AND/OR condition definitions for a PolicyRule. Instances of this class may have up to five properties identifying time periods at different levels. The values of all the properties present in an instance are ANDed together to determine the validity period(s) for the instance. For example, an instance with an overall validity range of January 1, 2000 through December 31, 2000; a month mask that selects March and April; a day-of-the-week mask that selects Fridays; and a time of day range of 0800 through 1600 would be represented using the following time periods: Friday, March 5, 2000, from 0800 through 1600; Friday, March 12, 2000, from 0800 through 1600; Friday, March 19, 2000, from 0800 through 1600; Friday, March 26, 2000, from 0800 through 1600; Friday, April 2, 2000, from 0800 through 1600; Friday, April 9, 2000, from 0800 through 1600; Friday, April 16, 2000, from 0800 through 1600; Friday, April 23, 2000, from 0800 through 1600; Friday, April 30, 2000, from 0800 through 1600. Properties not present in an instance of PolicyTimePeriodCondition are implicitly treated as having their value 'always enabled'. Thus, in the example above, the day-of-the-month mask is not present, and so the validity period for the instance implicitly includes a day-of-the-month mask that selects all days of the month. If this 'missing property' rule is applied to its fullest, we see that there is a second way to indicate that a PolicySet is always enabled: associate with it an instance of PolicyTimePeriodCondition whose only properties with specific values are its key properties.This property identifies an overall range of calendar dates and times over which a PolicySet is valid. It is formatted as a string representing a start date and time, in which the character 'T' indicates the beginning of the time portion, followed by the solidus character '/', followed by a similar string representing an end date and time. The first date indicates the beginning of the range, while the second date indicates the end. Thus, the second date and time must be later than the first. Date/times are expressed as substrings of the form yyyymmddThhmmss. For example: 20000101T080000/20000131T120000 defines January 1, 2000, 0800 through January 31, 2000, noon There are also two special cases in which one of the date/time strings is replaced with a special string defined in RFC 2445. o If the first date/time is replaced with the string 'THISANDPRIOR', then the property indicates that a PolicySet is valid [from now] until the date/time that appears after the '/'. o If the second date/time is replaced with the string 'THISANDFUTURE', then the property indicates that a PolicySet becomes valid on the date/time that appears before the '/', and remains valid from that point on.CIM_PolicyTimePeriodCondition.MonthOfYearMaskCIM_PolicyTimePeriodCondition.DayOfMonthMaskCIM_PolicyTimePeriodCondition.DayOfWeekMaskCIM_PolicyTimePeriodCondition.TimeOfDayMaskCIM_PolicyTimePeriodCondition.LocalOrUtcTimetrueThe purpose of this property is to refine the valid time period that is defined by the TimePeriod property, by explicitly specifying in which months the PolicySet is valid. These properties work together, with the TimePeriod used to specify the overall time period in which the PolicySet is valid, and the MonthOfYearMask used to pick out the months during which the PolicySet is valid. This property is formatted as an octet string, structured as follows: o a 4-octet length field, indicating the length of the entire octet string; this field is always set to 0x00000006 for this property; o a 2-octet field consisting of 12 bits identifying the 12 months of the year, beginning with January and ending with December, followed by 4 bits that are always set to '0'. For each month, the value '1' indicates that the policy is valid for that month, and the value '0' indicates that it is not valid. The value 0x000000060830, for example, indicates that a PolicySet is valid only in the months May, November, and December. If a value for this property is not provided, then the PolicySet is treated as valid for all twelve months, and only restricted by its TimePeriod property value and the other Mask properties.CIM_PolicyTimePeriodCondition.TimePeriodCIM_PolicyTimePeriodCondition.LocalOrUtcTimetrueThe purpose of this property is to refine the valid time period that is defined by the TimePeriod property, by explicitly specifying in which days of the month the PolicySet is valid. These properties work together, with the TimePeriod used to specify the overall time period in which the PolicySet is valid, and the DayOfMonthMask used to pick out the days of the month during which the PolicySet is valid. This property is formatted as an octet string, structured as follows: o a 4-octet length field, indicating the length of the entire octet string; this field is always set to 0x0000000C for this property; o an 8-octet field consisting of 31 bits identifying the days of the month counting from the beginning, followed by 31 more bits identifying the days of the month counting from the end, followed by 2 bits that are always set to '0'. For each day, the value '1' indicates that the PolicySet is valid for that day, and the value '0' indicates that it is not valid. The value 0x0000000C8000000100000000, for example, indicates that a PolicySet is valid on the first and last days of the month. For months with fewer than 31 days, the digits corresponding to days that the months do not have (counting in both directions) are ignored. If a value for this property is not provided, then the PolicySet is treated as valid for all days of the month, and only restricted by its TimePeriod property value and the other Mask properties.CIM_PolicyTimePeriodCondition.TimePeriodCIM_PolicyTimePeriodCondition.LocalOrUtcTimetrueThe purpose of this property is to refine the valid time period that is defined by the TimePeriod property, by explicitly specifying in which days of the week the PolicySet is valid. These properties work together, with the TimePeriod used to specify the overall time period in which the PolicySet is valid, and the DayOfWeekMask used to pick out the days of the week during which the PolicySet is valid. This property is formatted as an octet string, structured as follows: o a 4-octet length field, indicating the length of the entire octet string; this field is always set to 0x00000005 for this property; o a 1-octet field consisting of 7 bits identifying the 7 days of the week, beginning with Sunday and ending with Saturday, followed by 1 bit that is always set to '0'. For each day of the week, the value '1' indicates that the PolicySet is valid for that day, and the value '0' indicates that it is not valid. The value 0x000000057C, for example, indicates that a PolicySet is valid Monday through Friday. If a value for this property is not provided, then the PolicySet is treated as valid for all days of the week, and only restricted by its TimePeriod property value and the other Mask properties.CIM_PolicyTimePeriodCondition.TimePeriodCIM_PolicyTimePeriodCondition.LocalOrUtcTimeThe purpose of this property is to refine the valid time period that is defined by the TimePeriod property, by explicitly specifying a range of times in a day during which the PolicySet is valid. These properties work together, with the TimePeriod used to specify the overall time period in which the PolicySet is valid, and the TimeOfDayMask used to pick out the range of time periods in a given day of during which the PolicySet is valid. This property is formatted in the style of RFC 2445: a time string beginning with the character 'T', followed by the solidus character '/', followed by a second time string. The first time indicates the beginning of the range, while the second time indicates the end. Times are expressed as substrings of the form 'Thhmmss'. The second substring always identifies a later time than the first substring. To allow for ranges that span midnight, however, the value of the second string may be smaller than the value of the first substring. Thus, 'T080000/T210000' identifies the range from 0800 until 2100, while 'T210000/T080000' identifies the range from 2100 until 0800 of the following day. When a range spans midnight, it by definition includes parts of two successive days. When one of these days is also selected by either the MonthOfYearMask, DayOfMonthMask, and/or DayOfWeekMask, but the other day is not, then the PolicySet is active only during the portion of the range that falls on the selected day. For example, if the range extends from 2100 until 0800, and the day of week mask selects Monday and Tuesday, then the PolicySet is active during the following three intervals: From midnight Sunday until 0800 Monday; From 2100 Monday until 0800 Tuesday; From 2100 Tuesday until 23:59:59 Tuesday. If a value for this property is not provided, then the PolicySet is treated as valid for all hours of the day, and only restricted by its TimePeriod property value and the other Mask properties.CIM_PolicyTimePeriodCondition.TimePeriodCIM_PolicyTimePeriodCondition.LocalOrUtcTimeThis property indicates whether the times represented in the TimePeriod property and in the various Mask properties represent local times or UTC times. There is no provision for mixing of local times and UTC times: the value of this property applies to all of the other time-related properties. TimePeriods are synchronized worldwide by using the enumeration value 'UTCTime'. If the goal is to synchronize worldwide on a particular local time (such as 0300 - 0500 in New York), then if the TimePeriod property spans a Daylight Savings Time transition in New York, it will be necessary to create multiple instances of PolicyTimePeriodCondition, one based on the offset UTC-0500 for the part of each year when standard time is used in New York, and one based on the offset UTC-0400 for the part of each year when Daylight Savings Time is used there.12Local TimeUTC TimeCIM_PolicyTimePeriodCondition.TimePeriodCIM_PolicyTimePeriodCondition.MonthOfYearMaskCIM_PolicyTimePeriodCondition.DayOfMonthMaskCIM_PolicyTimePeriodCondition.DayOfWeekMaskCIM_PolicyTimePeriodCondition.TimeOfDayMask 2.7.0CompoundPolicyCondition is used to represent compound conditions formed by aggregating simpler policy conditions. Compound conditions are constructed by associating subordinate condition terms together using the PolicyConditionInPolicyCondition aggregation.Indicates whether the list of CompoundPolicyConditions associated with this PolicyRule is in disjunctive normal form (DNF) or conjunctive normal form (CNF). The default value is 1 ("DNF").12DNFCNF 2.6.0A class that provides a general extension mechanism for representing PolicyConditions that have not been modeled with specific properties. Instead, the two properties Constraint and ConstraintEncoding are used to define the content and format of the Condition, as explained below. As its name suggests, VendorPolicyCondition is intended for vendor-specific extensions to the Policy Core Information Model. Standardized extensions are not expected to use this class.trueThis property provides a general extension mechanism for representing PolicyConditions that have not been modeled with specific properties. The format of the octet strings in the array is left unspecified in this definition. It is determined by the OID value stored in the property ConstraintEncoding. Since ConstraintEncoding is single-valued, all the values of Constraint share the same format and semantics.CIM_VendorPolicyCondition.ConstraintEncodingAn OID encoded as a string, identifying the format and semantics for this instance's Constraint property.CIM_VendorPolicyCondition.Constraint true2.6.0A class representing a rule-specific or reusable policy action to be performed if the PolicyConditions for a PolicyRule evaluate to TRUE. Since all operational details of a PolicyAction are provided in subclasses of this object, this class is abstract.true256The name of the class or the subclass used in the creation of the System object in whose scope this PolicyAction is defined. This property helps to identify the System object in whose scope this instance of PolicyAction exists. For a rule-specific PolicyAction, this is the System in whose context the PolicyRule is defined. For a reusable PolicyAction, this is the instance of PolicyRepository (which is a subclass of System) that holds the Action. Note that this property, and the analogous property SystemName, do not represent propagated keys from an instance of the class System. Instead, they are properties defined in the context of this class, which repeat the values from the instance of System to which this PolicyAction is related, either directly via the PolicyActionInPolicyRepository association or indirectly via the PolicyActionInPolicyRule aggregation.true256The name of the System object in whose scope this PolicyAction is defined. This property completes the identification of the System object in whose scope this instance of PolicyAction exists. For a rule-specific PolicyAction, this is the System in whose context the PolicyRule is defined. For a reusable PolicyAction, this is the instance of PolicyRepository (which is a subclass of System) that holds the Action.true256For a rule-specific PolicyAction, the CreationClassName of the PolicyRule object with which this Action is associated. For a reusable PolicyAction, a special value, 'NO RULE', should be used to indicate that this Action is reusable and not associated with a single PolicyRule.true256For a rule-specific PolicyAction, the name of the PolicyRule object with which this Action is associated. For a reusable PolicyAction, a special value, 'NO RULE', should be used to indicate that this Action is reusable and not associated with a single PolicyRule.true256CreationClassName 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.true256A user-friendly name of this PolicyAction. 2.6.0A class that provides a general extension mechanism for representing PolicyActions that have not been modeled with specific properties. Instead, the two properties ActionData and ActionEncoding are used to define the content and format of the Action, as explained below. As its name suggests, VendorPolicyAction is intended for vendor-specific extensions to the Policy Core Information Model. Standardized extensions are not expected to use this class.trueThis property provides a general extension mechanism for representing PolicyActions that have not been modeled with specific properties. The format of the octet strings in the array is left unspecified in this definition. It is determined by the OID value stored in the property ActionEncoding. Since ActionEncoding is single-valued, all the values of ActionData share the same format and semantics.CIM_VendorPolicyAction.ActionEncodingAn OID encoded as a string, identifying the format and semantics for this instance's ActionData property.CIM_VendorPolicyAction.ActionData 2.6.0CompoundPolicyAction is used to represent an expression consisting of an ordered sequence of action terms. Each action term is represented as a subclass of the PolicyAction class. Compound actions are constructed by associating dependent action terms together using the PolicyActionInPolicyAction aggregation.This property gives a policy administrator a way of specifying how the ordering of the PolicyActions associated with this PolicyRule is to be interpreted. Three values are supported: o mandatory(1): Do the actions in the indicated order, or don't do them at all. o recommended(2): Do the actions in the indicated order if you can, but if you can't do them in this order, do them in another order if you can. o dontCare(3): Do them -- I don't care about the order. The default value is 3 ("DontCare").123MandatoryRecommendedDont CareExecutionStrategy defines the strategy to be used in executing the sequenced actions aggregated by this CompoundPolicyAction. There are three execution strategies: Do Until Success - execute actions according to predefined order, until successful execution of a single action. Do All - execute ALL actions which are part of the modeled set, according to their predefined order. Continue doing this, even if one or more of the actions fails. Do Until Failure - execute actions according to predefined order, until the first failure in execution of an action instance. The default value is 2 ("Do All").123Do Until SuccessDo AllDo Until Failure 2.7.0PolicyRoleCollection is used to represent a collection of managed elements that share a common policy role. The PolicyRoleCollection always exists in the context of a system, specified using the PolicyRoleCollectionInSystem aggregation. The value of the PolicyRole property in this class specifies the role, and can be matched with the value(s) in the PolicyRoles array in PolicyRules and PolicyGroups. ManagedElements that share the role defined in this collection are aggregated into the Collection via the ElementInPolicyRoleCollection association.trueThe PolicyRole property role name for the managed elements aggregated into the PolicyRoleCollection. This role name is the same role name that appears in related PolicySet instances. true2.6.0CIM_PolicyComponent is a generic association used to establish 'part of' relationships between the subclasses of CIM_Policy. For example, the PolicyConditionInPolicyRule association defines that PolicyConditions are part of a PolicyRule.truetrueGroupComponentThe parent Policy in the association.truetruePartComponentThe child/part Policy in the association.true true2.6.0CIM_PolicyInSystem is a generic association used to establish dependency relationships between Policies and the Systems that host them. These Systems may be ComputerSystems where Policies are 'running' or they may be PolicyRepositories where Policies are stored. This relationship is similar to the concept of CIM_Services being dependent on CIM_Systems as defined by the HostedService association. Cardinality is Max (1) for the Antecedent/System reference since Policies can only be hosted in at most one System context. Some subclasses of the association will further refine this definition to make the Policies Weak to Systems. Other subclasses of PolicyInSystem will define an optional hosting relationship. Examples of each of these are the PolicyRuleInSystem and PolicyConditionInPolicyRepository associations, respectively.trueAntecedent1The hosting System.trueDependentThe hosted Policy.true true2.6.0PolicySetInSystem is an abstract association class that represents a relationship between a System and a PolicySet used in the administrative scope of that system (e.g., AdminDomain, ComputerSystem). The Priority property is used to assign a relative priority to a PolicySet within the administrative scope in contexts where it is not a component of another PolicySet.true11The System in whose scope a PolicySet is defined.AntecedenttrueA PolicySet named within the scope of a System.DependenttrueThe Priority property is used to specify the relative priority of the referenced PolicySet when there are more than one PolicySet instances applied to a managed resource that are not PolicySetComponents and, therefore, have no other relative priority defined. The priority is a non-negative integer; a larger value indicates a higher priority. 2.6.0An association that links a PolicyGroup to the System in whose scope the Group is defined.true11The System in whose scope a PolicyGroup is defined.AntecedenttruetrueA PolicyGroup named within the scope of a System.Dependenttrue 2.6.0An association that links a PolicyRule to the System in whose scope the Rule is defined.true11The System in whose scope a PolicyRule is defined.AntecedenttruetrueA PolicyRule named within the scope of a System.Dependenttrue 2.6.0PolicySetComponent is a concrete aggregation that collects instances of the subclasses of PolicySet (i.e., PolicyGroups and PolicyRules). Instances are collected in sets that use the same decision strategy. They are prioritized relative to each other, within the set, using the Priority property of this aggregation. Together, the PolicySet.PolicyDecisionStrategy and PolicySetComponent.Priority properties determine the processing for the groups and rules contained in a PolicySet. A larger priority value represents a higher priority. Note that the Priority property MUST have a unique value when compared with others defined for the same aggregating PolicySet. Thus, the evaluation of rules within a set is deterministically specified.truetrueA PolicySet that aggregates other PolicySet instances.GroupComponenttruetrueA PolicySet aggregated into a PolicySet.PartComponenttrueA non-negative integer for prioritizing this PolicySet component relative to other elements of the same PolicySet. A larger value indicates a higher priority. The Priority property MUST have a unique value when compared with others defined for the same aggregating PolicySet. CIM_PolicySetComponent2.7.0PolicySetComponent provides a more general mechanism for aggregating both PolicyGroups and PolicyRules and doing so with the priority value applying only to the aggregated set rather than policy wide. A relationship that aggregates one or more lower-level PolicyGroups into a higher-level Group. A PolicyGroup may aggregate PolicyRules and/or other PolicyGroups.truetrueCIM_PolicySetComponent.GroupComponentA PolicyGroup that aggregates other Groups.GroupComponenttruetrueCIM_PolicySetComponent.PartComponentA PolicyGroup aggregated by another Group.PartComponenttrue CIM_PolicySetComponent2.7.0PolicySetComponent provides a more general mechanism for aggregating both PolicyGroups and PolicyRules and doing so with the priority value applying only to the aggregated set rather than policy wide. A relationship that aggregates one or more PolicyRules into a PolicyGroup. A PolicyGroup may aggregate PolicyRules and/or other PolicyGroups.truetrueCIM_PolicySetComponent.GroupComponentA PolicyGroup that aggregates one or more PolicyRules.GroupComponenttruetrueCIM_PolicySetComponent.PartComponentA PolicyRule aggregated by a PolicyGroup.PartComponenttrue 2.7.0The PolicySetValidityPeriod aggregation represents scheduled activation and deactivation of a PolicySet. A PolicySet is considered "active" if it is both "Enabled" and in a valid time period. If a PolicySet is associated with multiple policy time periods via this association, then the Set is in a valid time period if at least one of the time periods evaluates to TRUE. If a PolicySet is contained in another PolicySet via the PolicySetComponent aggregation (e.g., a PolicyRule in a PolicyGroup), then the contained PolicySet (e.g., PolicyRule) is in a valid period if at least one of the aggregate's PolicyTimePeriodCondition instances evaluates to TRUE and at least one of its own PolicyTimePeriodCondition instances also evalutes to TRUE. (In other words, the PolicyTimePeriodConditions are ORed to determine whether the PolicySet is in a valid time period and then ANDed with the ORed PolicyTimePeriodConditions of each of PolicySet instances in the PolicySetComponent hierarchy to determine if the PolicySet is in a valid time period and, if also "Enabled", therefore, active, i.e., the hierachy ANDs the ORed PolicyTimePeriodConditions of the elements of the hierarchy. A Time Period may be aggregated by multiple PolicySets. A Set that does not point to a PolicyTimePeriodCondition via this association, from the point of view of scheduling, is always in a valid time period.truetrueThis property contains the name of a PolicySet that contains one or more PolicyTimePeriodConditions.GroupComponenttruetrueThis property contains the name of a PolicyTimePeriodCondition defining the valid time periods for one or more PolicySets.PartComponenttrue CIM_PolicySetValidityPeriod2.7.0The PolicyRuleValidityPeriod aggregation represents scheduled activation and deactivation of a PolicyRule. If a PolicyRule is associated with multiple policy time periods via this association, then the Rule is active if at least one of the time periods indicates that it is active. (In other words, the PolicyTimePeriodConditions are ORed to determine whether the Rule is active.) A TimePeriod may be aggregated by multiple PolicyRules. A Rule that does not point to a PolicyTimePeriodCondition via this association is, from the point of view of scheduling, always active. It may, however, be inactive for other reasons. For example, the Rule's Enabled property may be set to "disabled" (value=2).truetrueCIM_PolicySetValidityPeriod.GroupComponentThis property contains the name of a PolicyRule that contains one or more PolicyTimePeriodConditions.GroupComponenttruetrueCIM_PolicySetValidityPeriod.PartComponentThis property contains the name of a PolicyTimePeriodCondition defining the valid time periods for one or more PolicyRules.PartComponenttrue true2.7.0PolicyConditions may be aggregated into rules and into compound conditions. PolicyConditionStructure is the abstract aggregation class for the structuring of policy conditions. The Conditions aggregated by a PolicyRule or CompoundPolicyCondition are grouped into two levels of lists: either an ORed set of ANDed sets of conditions (DNF, the default) or an ANDed set of ORed sets of conditions (CNF). Individual PolicyConditions in these lists may be negated. The property ConditionListType specifies which of these two grouping schemes applies to a particular PolicyRule or CompoundPolicyCondition instance. One or more PolicyTimePeriodConditions may be among the conditions associated with a PolicyRule or CompoundPolicyCondition via the PolicyConditionStructure subclass association. In this case, the time periods are simply additional Conditions to be evaluated along with any others that are specified. truetrueThis property represents the Policy that contains one or more PolicyConditions.GroupComponenttruetrueThis property holds the name of a PolicyCondition contained by one or more PolicyRule or CompoundPolicyCondition instances.PartComponenttrueUnsigned integer indicating the group to which the contained PolicyCondition belongs. This integer segments the Conditions into the ANDed sets (when the ConditionListType is "DNF") or, similarly, into the ORed sets (when the ConditionListType is "CNF").Indication of whether the contained PolicyCondition is negated. TRUE indicates that the PolicyCondition IS negated, FALSE indicates that it IS NOT negated. 2.7.0A PolicyRule aggregates zero or more instances of the PolicyCondition class, via the PolicyConditionInPolicyRule association. A Rule that aggregates zero Conditions is not valid; it may, however, be in the process of being defined. Note that a PolicyRule should have no effect until it is valid.truetrueThis property represents the PolicyRule that contains one or more PolicyConditions.GroupComponenttruetrueThis property holds the name of a PolicyCondition contained by one or more PolicyRules.PartComponenttrue 2.7.0A CompoundPolicyCondition aggregates zero or more instances of the PolicyCondition class, via the PolicyConditionInPolicyCondition association. A CompoundPolicyCondition that aggregates zero Conditions is not valid; it may, however, be in the process of being defined. Note that a CompoundPolicyCondition should have no effect until it is valid.truetrueThis property represents the CompoundPolicyCondition that contains one or more PolicyConditions.GroupComponenttruetrueThis property holds the name of a PolicyCondition contained by one or more PolicyRules.PartComponenttrue true2.6.0PolicyActions may be aggregated into rules and into compound actions. PolicyActionStructure is the abstract aggregation class for the structuring of policy actions.truetruePolicyAction instances may be aggregated into either PolicyRule instances or CompoundPolicyAction instances.GroupComponenttruetrueA PolicyAction aggregated by a PolicyRule or CompoundPolicyAction.PartComponenttrueActionOrder is an unsigned integer 'n' that indicates the relative position of a PolicyAction in the sequence ofactions associated with a PolicyRule or CompoundPolicyAction. When 'n' is a positive integer, it indicates a place in the sequence of actions to be performed, with smaller integers indicating earlier positions in the sequence. The special value '0' indicates 'don't care'. If two or more PolicyActions have the same non-zero sequence number, they may be performed in any order, but they must all be performed at the appropriate place in the overall action sequence. A series of examples will make ordering of PolicyActions clearer: o If all actions have the same sequence number, regardless of whether it is '0' or non-zero, any order is acceptable. o The values: 1:ACTION A 2:ACTION B 1:ACTION C 3:ACTION D indicate two acceptable orders: A,C,B,D or C,A,B,D, since A and C can be performed in either order, but only at the '1' position. o The values: 0:ACTION A 2:ACTION B 3:ACTION C 3:ACTION D require that B,C, and D occur either as B,C,D or as B,D,C. Action A may appear at any point relative to B, C, and D. Thus the complete set of acceptable orders is: A,B,C,D; B,A,C,D; B,C,A,D; B,C,D,A; A,B,D,C; B,A,D,C; B,D,A,C; B,D,C,A. 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.6.0A PolicyRule aggregates zero or more instances of the PolicyAction class, via the PolicyActionInPolicyRule association. A Rule that aggregates zero Actions is not valid--it may, however, be in the process of being entered into a PolicyRepository or being defined for a System. Alternately, the actions of the policy may be explicit in the definition of the PolicyRule. Note that a PolicyRule should have no effect until it is valid. The Actions associated with a PolicyRule may be given a required order, a recommended order, or no order at all. For Actions represented as separate objects, the PolicyActionInPolicyRule aggregation can be used to express an order. This aggregation does not indicate whether a specified action order is required, recommended, or of no significance; the property SequencedActions in the aggregating instance of PolicyRule provides this indication.truetrueThis property represents the PolicyRule that contains one or more PolicyActions.GroupComponenttruetrueThis property holds the name of a PolicyAction contained by one or more PolicyRules.PartComponenttrue 2.6.0PolicyActionInPolicyAction is used to represent the compounding of policy actions into a higher-level policy action.truetrueThis property represents the CompoundPolicyAction that contains one or more PolicyActions.GroupComponenttruetrueThis property holds the name of a PolicyAction contained by one or more CompoundPolicyActions.PartComponenttrue 2.6.0A relationship that aggregates one or more lower-level ReusablePolicyContainer instances into a higher-level ReusablePolicyContainer.truetrueA ReusablePolicyContainer that aggregates other ReusablePolicyContainers.GroupComponenttruetrueA ReusablePolicyContainer aggregated by another ReusablePolicyContainer.PartComponenttrue CIM_PolicyContainerInPolicyContainer2.7.0The term 'PolicyRepository' has been confusing to both developers and users of the model. The replacement class name describes model element properly and is less likely to be confused with a data repository. ContainedDomain is a general purpose mechanism for expressing domain hierarchy. A relationship that aggregates one or more lower-level PolicyRepositories into a higher-level Repository.truetrueCIM_PolicyContainerInPolicyContainer.GroupComponentA PolicyRepository that aggregates other Repositories.GroupComponenttruetrueCIM_PolicyContainerInPolicyContainer.PartComponentA PolicyRepository aggregated by another Repository.PartComponenttrue 2.6.0The ReusablePolicy association provides for the reuse of any subclass of Policy in a ReusablePolicyContainer.true1This property identifies a ReusablePolicyContainer that provides the administrative scope for the reuse of the referenced policy element.AntecedenttrueA reusable policy element.Dependenttrue 2.7.0An ElementInPolicyRoleCollection aggregates zero or more ManagedElement subclass instances with a PolicyRoleCollection object that represents a role played by these ManagedElements.truetrueCollectionThe PolicyRoleCollection.truetrueMemberThe ManagedElement that plays the role represented by the PolicyRoleCollection.true 2.7.0PolicyRoleCollectionInSystem is an association used to establish a relationship between a collection and an 'owning' System such as an AdminDomain or ComputerSystem.true11The parent system responsible for the collection.AntecedenttrueThe Collection.Dependenttrue CIM_ReusablePolicy2.7.0The ReusablePolicy association is a more general relationship that incorporates both Conditions and Actions as well as any other policy subclass. A class representing the hosting of reusable PolicyConditions by a PolicyRepository. A reusable PolicyCondition is always related to a single PolicyRepository, via this association. Note, that an instance of PolicyCondition can be either reusable or rule-specific. When the Condition is rule-specific, it shall not be related to any PolicyRepository via the PolicyConditionInPolicyRepository association.true1CIM_ReusablePolicy.AntecedentThis property identifies a PolicyRepository hosting one or more PolicyConditions. A reusable PolicyCondition is always related to exactly one PolicyRepository via the PolicyConditionInPolicyRepository association. The [0..1] cardinality for this property covers the two types of PolicyConditions: 0 for a rule-specific PolicyCondition, 1 for a reusable one.AntecedenttrueCIM_ReusablePolicy.DependentThis property holds the name of a PolicyConditionhosted in the PolicyRepository.Dependenttrue CIM_ReusablePolicy2.7.0The ReusablePolicy association is a more general relationship that incorporates both Conditions and Actions as well as any other policy subclass. A class representing the hosting of reusable PolicyActions by a PolicyRepository. A reusable PolicyAction is always related to a single PolicyRepository, via this association. Note, that an instance of PolicyAction can be either reusable or rule-specific. When the Action is rule-specific, it shall not be related to any PolicyRepository via the PolicyActionInPolicyRepository association.true1CIM_ReusablePolicy.AntecedentThis property represents a PolicyRepository hosting one or more PolicyActions. A reusable PolicyAction is always related to exactly one PolicyRepository via the PolicyActionInPolicyRepository association. The [0..1] cardinality for this property covers the two types of PolicyActions: 0 for a rule-specific PolicyAction, 1 for a reusable one.AntecedenttrueCIM_ReusablePolicy.DependentThis property holds the name of a PolicyActionhosted in the PolicyRepository.Dependenttrue 2.6.0The CIM_ApplicationSystem class is used to represent an application or a software system that supports a particular business function and that can be managed as an independent unit. Such a system can be decomposed into its functional components using the CIM_SoftwareFeature class. The Features for a particular application or software system are located using the CIM_ApplicationSystemSoftwareFeature association. 2.7.0The CIM_SoftwareElement class is used to decompose a CIM_SoftwareFeature object into a set of individually manageable or deployable parts, for a particular platform. A SoftwareElement's platform is uniquely identified by its underlying hardware architecture and operating system (for example Sun Solaris on Sun Sparc or Windows NT on Intel platforms). As such, to understand the details of how the functionality of a particular SoftwareFeature is provided on a particular platform, the CIM_SoftwareElement objects referenced by CIM_SoftwareFeatureSoftwareElements associations are organized in disjoint sets based on the TargetOperatingSystem property. A CIM_SoftwareElement object captures the management details of a part or component in one of four states characterized by the SoftwareElementState property.true256NameThe name used to identify this SoftwareElement.true64Software Version should be in the form <Major>.<Minor>.<Revision> or <Major>.<Minor><letter><revision>.MIF.DMTF|SubComponent Software |001.4trueThe SoftwareElementState is defined in this model to identify various states of a SoftwareElement's life cycle. - A SoftwareElement in the deployable state describes the details necessary to successfully distribute it and the details (Checks and Actions) required to move it to the installable state (i.e, the next state). - A SoftwareElement in the installable state describes the details necessary to successfully install it and the details (Checks and Actions) required to create an element in the executable state (i.e., the next state). - A SoftwareElement in the executable state describes the details necessary to successfully start it and the details (Checks and Actions) required to move it to the running state (i.e., the next state). - A SoftwareElement in the running state describes the details necessary to manage the started element.0123DeployableInstallableExecutableRunningtrue256This is an identifier for the SoftwareElement and is designed to be used in conjunction with other keys to create a unique representation of the element.trueMIF.DMTF|SubComponent Software|001.8The TargetOperatingSystem property specifies the element's operating system environment. The value of this property does not ensure that it is binary executable. Two other pieces of information are needed. First, the version of the OS needs to be specified using the class, CIM_OSVersionCheck. The second piece of information is the architecture that the OS runs on. This information is verified using CIM_ArchitectureCheck. The combination of these constructs clearly identifies the level of OS required for a particular SoftwareElement.01234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768UnknownOtherMACOSATTUNIXDGUXDECNTTru64 UNIXOpenVMSHPUXAIXMVSOS400OS/2JavaVMMSDOSWIN3xWIN95WIN98WINNTWINCENCR3000NetWareOSFDC/OSReliant UNIXSCO UnixWareSCO OpenServerSequentIRIXSolarisSunOSU6000ASERIESTandemNSKTandemNTBS2000LINUXLynxXENIXVMInteractive UNIXBSDUNIXFreeBSDNetBSDGNU HurdOS9MACH KernelInfernoQNXEPOCIxWorksVxWorksMiNTBeOSHP MPENextStepPalmPilotRhapsodyWindows 2000DedicatedOS/390VSETPFWindows (R) MeCaldera Open UNIXOpenBSDNot ApplicableWindows XPz/OSCIM_OperatingSystem.OSTypeThe OtherTargetOS property records the manufacturer and operating system type for a SoftwareElement when the TargetOperatingSystem property has a value of 1 ("Other"). For all other values of TargetOperatingSystem, the OtherTargetOS property is NULL.64CIM_OperatingSystem.OtherTypeDescription256MIF.DMTF|SubComponent Software|001.3Manufacturer of this SoftwareElement.64MIF.DMTF|Software Component Information|002.4The internal identifier for this compilation of SoftwareElement.64MIF.DMTF|ComponentID|001.4The assigned serial number of this SoftwareElement.64The code set used by this SoftwareElement. It defines the bit patterns that a system uses to identify characters. ISO defines various code sets such as UTF-8 and ISO8859-1.64MIF.DMTF|SubComponent Software|001.6The manufacturer's identifier for this SoftwareElement. Often this will be a stock keeping unit (SKU) or a part number.32MIF.DMTF|SubComponent Software|001.7The value of this property identifies the language edition of this SoftwareElement. The language codes defined in ISO 639 should be used. Where the element represents a multi-lingual or international version, the string "Multilingual" should be used. 2.6.0 The CIM_SoftwareFeature class defines a particular function or capability of a product or application system. This class captures a level of granularity describing a unit of installation, rather than the units that reflect how the product is built or packaged. The latter detail is captured using a CIM_SoftwareElement class. When a SoftwareFeature can exist on multiple platforms or operating systems (for example, a client component of a three tiered client/server application that runs on Solaris, Windows NT, and Windows 95), the Feature is a collection of all the SoftwareElements for these different platforms. In this case, the users of the model must be aware of this situation since typically they will be interested in a sub-collection of the SoftwareElements required for a particular platform. SoftwareFeatures are always defined in the context of a CIM_Product, using the CIM_ProductSoftwareFeature association. Features are delivered through Products. Optionally, SoftwareFeatures from one or more Products can be organized into ApplicationSystems using the CIM_ApplicationSystemSoftwareFeature association.CIM_Product.IdentifyingNumbertrue64The scoping Product's identification.CIM_Product.Nametrue256The scoping Product's commonly used name.CIM_Product.Vendortrue256The scoping Product's supplier.CIM_Product.Versiontrue64The scoping Product's version.trueName256The Name property defines the unique label by which the SoftwareFeature is identified. This label should be a human-readable name that uniquely identifies the element in the context of the element's namespace. 2.6.0SoftwareFeatureSoftwareElements identifies the SoftwareElements that make up a particular SoftwareFeature.truetrueGroupComponentThe SoftwareFeature that groups the SoftwareElement.truetruePartComponentThe SoftwareElement that makes up the Feature.true 2.6.0The SoftwareFeatureComponent aggregation models a set of subordinate or independent Software Features of a Product. These are aggregated together to form a higher-level or large grain Feature under the same Product.truetrueGroupComponentThe parent SoftwareFeature.truetruePartComponentThe component SoftwareFeature.true truetrue2.6.0The ProductSoftwareFeatures association identifies the SoftwareFeatures for a particular Product.true11trueThe Product that scopes the SoftwareFeatures.truetrueThe SoftwareFeature in a Product. 2.6.0The ApplicationSystemSoftwareFeature association identifies the Features that make up a particular ApplicationSystem. The SoftwareFeatures can be scoped by different Products.truetrueThe ApplicationSystem that aggregates the Features.GroupComponenttruetrueThe Features in an ApplicationSystem.PartComponenttrue 2.6.0 An association between a Service and how it is implemented in software. The cardinality of this association is many-to-many. A Service may be provided by more than one SoftwareFeature. When multiple SoftwareFeatures are associated with a single Service, it is assumed that these elements operate in conjunction to provide the Service. Note that any SoftwareFeature may provide more than one 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 their own associations to the unique implementations.trueAntecedentThe SoftwareFeature implementing the Service.trueDependentThe Service being implemented.true 2.6.0 An association between a ServiceAccessPoint and how it is implemented in software. The cardinality of this association is many-to-many. A SAP may be provided by more than one SoftwareFeature. When multiple SoftwareFeatures are associated with a single SAP, it is assumed that these elements operate in conjunction to provide the AccessPoint. Note that any SoftwareFeature may provide more than one ServiceAccessPoint. 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 their own associations to the unique implementations.trueAntecedentThe SoftwareFeature implementing the SAP.trueDependentThe AccessPoint being implemented.true truetrue2.6.0 The FRUIncludesSoftwareFeature association identifies the SoftwareFeature(s) packaged with a particular FRU. A common usage is to determine whether the FRU is compatible with a hardware/software platform. In order to determine this, the following conditions need to be verified: (1) Is the physical package of the FRU compatible with the slots or equivalent packaging of the hardware? (2) Are there any physical constraints (such as power consumption) that prevent the FRU from being installed? (3) Are the SoftwareFeatures packaged with the FRU compatiable with the underlying operating system and other software already installed/to be installed on the platform? This latter question can be answered by first checking if an instance of FRUIncludesSoftwareFeature exists. If it does, then the compatibility of each SoftwareFeature can be determined by evaluating the Check classes for the SoftwareElements that are part of the Feature (found by traversing the association, SoftwareFeatureSoftwareElements). For example, there might be a SoftwareElementVersionCheck that declares that a SoftwareElement (of the FRU's SoftwareFeature) is not compatible with current software.true1trueThe field replaceable unit.trueThe SoftwareFeature which is included in the FRU and whoseSoftwareElements should be evaluated. 2.6.0 An association between a Service and how it is implemented by one or more executable SoftwareElements. Note that this association is restricted to 'executable' Elements. In earlier phases of deployment, the SoftwareFeatureServiceImplementation association is adequate and recommended. The relationship between this association and SoftwareFeatureServiceImplementation is more fully described here. SoftwareElementServiceImplementation allows the description of greater granularity than SoftwareFeatureServiceImplementation, when a SoftwareFeature is fully deployed and results in several executable Elements. These Elements may implement several different Services. Since SoftwareFeatures decompose into SoftwareElements, it is possible to describe how software implements a Service by using either this association or the SoftwareFeatureServiceImplementation relationship. One or the other should be chosen. Both associations should not be used for a single Service instance, since their information is redundant. This relationship is especially important when the SoftwareFeature and Product aspects are not described for a SoftwareElement (ie, when the acquisition and deployment of the software is not detailed). In this case, the SoftwareElementServiceImplementation association is the only one available to describe how a Service is implemented in software. Since SoftwareFeatures are not instantiated, it is not possible to use the SoftwareFeatureServiceImplementation association. The cardinality of this association is many-to-many. A Service may be provided by more than one SoftwareElement. If this is true, it is assumed that the SoftwareElements operate in conjunction. And, any SoftwareElement may provide more than one Service.trueAntecedentThe executable SoftwareElement implementing the Service.trueDependentThe Service implemented by the SoftwareElement.true 2.6.0 An association between a ServiceAccessPoint and how it is implemented by one or more executable SoftwareElements. Note that this association is restricted to 'executable' Elements. In earlier phases of deployment, the SoftwareFeatureSAPImplementation association is adequate and recommended. The relationship between this association and SoftwareFeatureSAPImplementation is more fully described here. SoftwareElementSAPImplementation allows the description of greater granularity than SoftwareFeatureSAPImplementation, when a SoftwareFeature is fully deployed and results in several executable Elements. These Elements may implement several different ServiceAccessPoints. Since SoftwareFeatures decompose into SoftwareElements, it is possible to describe how software implements a SAP by using either this association or the SoftwareFeatureSAPImplementation relationship. One or the other should be chosen. Both associations should not be used for a particular AccessPoint, since their information is redundant. This relationship is especially important when the SoftwareFeature and Product aspects are not described for a SoftwareElement (ie, when the acquisition and deployment of the software is not detailed). In this case, the SoftwareElementSAPImplementation association is the only one available to describe how an AccessPoint is implemented in software. Since SoftwareFeatures are not instantiated, it is not possible to use the SoftwareFeatureSAPImplementation association. The cardinality of this association is many-to-many. A ServiceAccessPoint may be provided by more than one SoftwareElement. (If this is true, it is assumed that the SoftwareElements operate in conjunction.) And, any SoftwareElement may provide more than one SAP.trueAntecedentThe executable SoftwareElement implementing the SAP.trueDependentThe ServiceAccessPoint implemented by the SoftwareElement.true 2.6.0 The InstalledProduct object allows the grouping of SoftwareFeatures and SoftwareElements that represent the result of the installation of a purchased Product. InstalledProduct is defined to be Weak to a Product. Often, Products are purchased once but may be installed several times in different locations on one or more systems. All of the SoftwareElements and SoftwareFeatures of a single install are grouped by an instance of InstalledProduct. These are defined using the associations, CollectedSoftwareFeatures and CollectedSoftwareElements.CIM_Product.IdentifyingNumbertrue64The scoping Product's identification.CIM_Product.Nametrue256The scoping Product's commonly used name.CIM_Product.Vendortrue256The scoping Product's name.CIM_Product.Versiontrue64The scoping Product's version information.true256The identifying information of the System (ie, the instance) on which the Product is installed. If the System is not known, this property returns NULL. If the System is known and represented in CIM, the property contains the namespace and model paths of the instance, encoded as a string parameter. If known but not represented in CIM, the property contains some identifying string that names the System on which the Product is installed.true256The identification of the InstalledProduct object. This key can be used to differentiate between Product installations and could include the installation location.256The Name property defines the label by which the object is known to the world, outside the data processing system. This label is a human-readable name that uniquely identifies the element in the context of the element's namespace. truetrue2.6.0InstalledProductImage identifies the collection of SoftwareFeatures and SoftwareElements that are the result of the installation of the referenced Product.true11trueThe product that has been installed.truetrueThe collection containing the set of SoftwareFeatures and SoftwareElements that are the result of installing the Product. 2.6.0CollectedSoftwareElements defines the SoftwareElements that are collected by InstalledProduct (ie, the installed image of a Product).truetrueCollectionThe collection representing the installed image of a Product.truetrueMemberA SoftwareElement that is a member of the InstalledProduct collection.true 2.6.0CollectedSoftwareFeatures defines the SoftwareFeatures that are collected by InstalledProduct (ie, the installed image of a Product).truetrueCollectionThe collection representing the installed image of a Product.truetrueMemberThe SoftwareFeature that is a member of the InstalledProduct collection.true true2.7.0 A CIM_Check is a condition or characteristic that is expected to be true in an environment defined or scoped by an instance of a CIM_ComputerSystem. The Checks associated with a particular SoftwareElement are organized into one of two groups using the Phase property of the CIM_SoftwareElementChecks association. Conditions that are expected to be true when a SoftwareElement is in a particular state and environment are known as 'in-state' conditions. Conditions that need to be satisfied in order to transition the SoftwareElement to its next state are known as 'next-state' conditions. A CIM_ComputerSystem object represents the environment in which CIM_SoftwareElements are already deployed/installed or into which the elements will be deployed/installed. For the case in which an element is already installed, the CIM_InstalledSoftwareElement association identifies the CIM_ComputerSystem object that represents the "environment". When a SoftwareElement is being deployed for installation on a ComputerSystem, that system is the target of the Check and is identified using the TargetSystem reference of the InvokeOnSystem method.CIM_SoftwareElement.Nametrue256The name used to identify the SoftwareElement that is being checked.CIM_SoftwareElement.Versiontrue64The version of the SoftwareElement being checked.CIM_SoftwareElement.SoftwareElementStatetrueThe SoftwareElementState of the SoftwareElement being checked.0123DeployableInstallableExecutableRunningCIM_SoftwareElement.SoftwareElementIDtrue256This is an identifier for the SoftwareElement being checked.CIM_SoftwareElement.TargetOperatingSystemtrueThe Target Operating System of the SoftwareElement being checked.01234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768UnknownOtherMACOSATTUNIXDGUXDECNTTru64 UNIXOpenVMSHPUXAIXMVSOS400OS/2JavaVMMSDOSWIN3xWIN95WIN98WINNTWINCENCR3000NetWareOSFDC/OSReliant UNIXSCO UnixWareSCO OpenServerSequentIRIXSolarisSunOSU6000ASERIESTandemNSKTandemNTBS2000LINUXLynxXENIXVMInteractive UNIXBSDUNIXFreeBSDNetBSDGNU HurdOS9MACH KernelInfernoQNXEPOCIxWorksVxWorksMiNTBeOSHP MPENextStepPalmPilotRhapsodyWindows 2000DedicatedOS/390VSETPFWindows (R) MeCaldera Open UNIXOpenBSDNot ApplicableWindows XPz/OStrue256An identifier used in conjunction with other keys to uniquely identify the Check.The CheckMode property is used to indicate whether the condition is expected to exist or not exist in the environment. When the value is True, the condition is expected to exist (e.g., a file is expected to be on a system), so the Invoke methods are expected to return True. When the value is False, the condition is not expected to exist (e.g., a file is not to be on a system), so the Invoke methods are expected to return False. The Invoke method evaluates this Check. The details of the evaluation are described by the specific subclasses of CIM_Check. When the SoftwareElement being checked is already installed, the CIM_InstalledSoftwareElement association identifies the CIM_ComputerSystem in whose context the Invoke is executed. If this association is not in place, then the InvokeOnSystem method should be used - since it identifies the TargetSystem as an input parameter of the method. The results of the Invoke method are based on the return value. A zero is returned if the condition is satisfied. A one is returned if the method is not supported. Any other value indicates the condition is not satisfied. The InvokeOnSystem method evaluates this Check. The details of the evaluation are described by the specific subclasses of CIM_Check. The method's TargetSystem input parameter specifies the ComputerSystem in whose context the method is invoked. The results of the InvokeOnSystem method are based on the return value. A zero is returned if the condition is satisfied. A one is returned if the method is not supported. Any other value indicates the condition is not satisfied.true 2.6.0The CIM_DirectorySpecification class captures the major directory structure of a SoftwareElement. This class is used to organize the files of a SoftwareElement into manageable units that can be relocated on a computer system.The DirectoryType property characterizes the type of directory being described. 01234567891011121314151617Product base directoryProduct executable directoryProduct library directoryProduct configuration directoryProduct include directoryProduct working directoryProduct log directoryShared base directoryShared executable directoryShared library directoryShared include directorySystem base directorySystem executable directorySystem library directorySystem configuration directorySystem include directorySystem log directoryOtherMIF.DMTF|Location|001.21024The DirectoryPath property is used to capture the name of a directory. The value supplied by an application provider is actually a default or recommended path name. The value can be changed for a particular environment. 2.7.0ArchitectureCheck specifies the hardware platform on which a SoftwareElement can run. The details of this Check are compared with the information found in the CIM_Processor object, related to the CIM_ComputerSystem instance that describes the environment (related by the association, CIM_ComputerSystemProcessor). There should be at least one CIM_Processor that satisfies the details of the Check. In other words, all the processors on the relevant computer system do not need to satisfy the Check.The ArchitectureType property identifies a particular type of architecture or architectural family that is required to properly execute a particular SoftwareElement. The intent is to capture the details about the machine instructions exploited by the executables of the SoftwareElement.1234567891011121314151617181924252627282930313233343536373839484950515253545564656667686980818283848586878896979899100101112120121128130144145146147148149150160176177178179180181182183184185190200201202203204250251260261280281300301302320350500OtherUnknown80868028680386804868087802878038780487Pentium(R) brandPentium(R) ProPentium(R) IIPentium(R) processor with MMX(TM) technologyCeleron(TM)Pentium(R) II Xeon(TM)Pentium(R) IIIM1 FamilyM2 FamilyK5 FamilyK6 FamilyK6-2K6-3AMD Athlon(TM) Processor FamilyAMD(R) Duron(TM) ProcessorAMD29000 FamilyK6-2+Power PC FamilyPower PC 601Power PC 603Power PC 603+Power PC 604Power PC 620Power PC X704Power PC 750Alpha FamilyAlpha 21064Alpha 21066Alpha 21164Alpha 21164PCAlpha 21164aAlpha 21264Alpha 21364MIPS FamilyMIPS R4000MIPS R4200MIPS R4400MIPS R4600MIPS R10000SPARC FamilySuperSPARCmicroSPARC IImicroSPARC IIepUltraSPARCUltraSPARC IIUltraSPARC IIiUltraSPARC IIIUltraSPARC IIIi6804068xxx Family68000680106802068030Hobbit FamilyCrusoe(TM) TM5000 FamilyCrusoe(TM) TM3000 FamilyWeitekItanium(TM) ProcessorPA-RISC FamilyPA-RISC 8500PA-RISC 8000PA-RISC 7300LCPA-RISC 7200PA-RISC 7100LCPA-RISC 7100V30 FamilyPentium(R) III Xeon(TM)Pentium(R) III Processor with Intel(R) SpeedStep(TM) TechnologyPentium(R) 4Intel(R) Xeon(TM)AS400 FamilyIntel(R) Xeon(TM) processor MPAMD Athlon(TM) XP FamilyAMD Athlon(TM) MP FamilyIntel(R) Itanium(R) 2Intel(R) Pentium(R) 4 processor with HT TechnologyK7S/390 and zSeries FamilyESA/390 G4ESA/390 G5ESA/390 G6z/Architectur basei860i960SH-3SH-4ARMStrongARM6x86MediaGXMIIWinChipDSPVideo ProcessorMIF.DMTF|Processor|017.3CIM_Processor.Family 2.6.0MemoryCheck specifies a condition for the minimum amount of memory that needs to be available on a system. The amount is specified in the MemorySize property. The details of this Check are compared with the value of the CIM_OperatingSystem.FreePhysicalMemory property - where the CIM_OperatingSystem object is related (using InstalledOS) to the CIM_ComputerSystem instance that describes the environment. When the value of the FreePhysicalMemory property is greater than or equal to the value specified in MemorySize, the Check is satisfied.The amount of memory that needs to exist on a computer system for a SoftwareElement to execute properly.KiloBytesCIM_OperatingSystem.FreePhysicalMemory 2.6.0DiskSpaceCheck describes the amount of disk space that needs to be available on the computer system. The amount is specified in the AvailableDiskSpace property. The details of this Check are compared with the value of the CIM_FileSystem.AvailableSpace property - where the CIM_FileSystem object is related (using HostedFileSystem) to the CIM_ComputerSystem instance that describes the environment. When the value of the AvailableSpace property is greater than or equal to the value specified in AvailableDiskSpace, the Check is satisfied.KiloBytesThe AvailableDiskSpace property specifies the minimum amount of disk space that needs to be available on the target system.CIM_FileSystem.AvailableSpace 2.6.0SwapSpaceCheck specifies the amount of swap space that needs to be available on the computer system. The amount is specified in the SwapSpaceSize property. The details of this Check are compared with the value of the CIM_OperatingSystem.TotalSwapSpaceSize property - where the CIM_OperatingSystem object is related (using RunningOS) to the CIM_ComputerSystem instance that describes the environment. When the value of TotalSwapSpaceSize property is greater than or equal to the value specified in SwapSpaceSize, the Check is satisfied.KiloBytesThe SwapSpaceSize property specifies the minimum number of KiloBytes of swap space that needs to be available on the target system.CIM_OperatingSystem.TotalSwapSpaceSize 2.6.0 The OSVersionCheck class specifies the versions of the operating system that can support/execute this SoftwareElement. The operating system itself (whose version should be validated) is defined in the TargetOperatingSystem property of the Check's scoping SoftwareElement. This Check can be for a specific, minimum, maximum or a range of releases of an OS. To identify a specific version of the OS, the minimum and maximum versions must be the same. To specify a minimum, only the minimum version needs to be defined. To specify a maximum version, only the maximum version needs to be defined. To specify a range, both minimum and maximum versions need to be defined. The data gathered from the Check and SoftwareElement objects are compared with the corresponding details found in the CIM_OperatingSystem object (referenced by the InstalledOS association), for the CIM_ComputerSystem object that defines the environment. The OSType property of CIM_OperatingSystem must match the value of CIM_SoftwareElement.TargetOperatingSystem. Also, the OS' version information should be within the range of CIM_OSVersionCheck.Minimum/MaximumValue properties. Note that all the operating systems on the relevant computer do not need to satisfy the Check.64Minimum version of the required operating system. The value is encoded as <major>.<minor>.<revision> or <major>.<minor><letter revision>.CIM_OperatingSystem.Version64Maximum version of the required operating system. The value is encoded as <major>.<minor>.<revision> or <major>.<minor><letter revision>.CIM_OperatingSystem.Version 2.7.0SoftwareElementVersionCheck specifies the release of a SoftwareElement that must exist in the environment. This Check can be for a specific, minimum, maximum or a range of versions. To specify a specific version, the lower and upper versions must be the same. To specify a minimum, only the lower version needs to be defined. To specify a maximum version, only the upper version needs to be defined. To specify a range, both upper and lower versions need to be defined. The details of this Check are compared with the corresponding details found in a CIM_SoftwareElement object, associated to the CIM_ComputerSystem instance that describes the environment (related by the association, CIM_InstalledSoftwareElement). There should be at least one CIM_SoftwareElement that satisfies the details of the Check. In other words, all the SoftwareElements on the relevant computer system do not need to satisfy the Check.256The name of the SoftwareElement being checked.CIM_SoftwareElement.Name64The minimum version of the SoftwareElement being checked.CIM_SoftwareElement.Version64The maximum version of the SoftwareElement being checked.CIM_SoftwareElement.VersionThe state of the SoftwareElement being checked.0123DeployableInstallableExecutableRunningCIM_SoftwareElement.SoftwareElementStateThe target operating system of the SoftwareElement being checked.01234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768UnknownOtherMACOSATTUNIXDGUXDECNTTru64 UNIXOpenVMSHPUXAIXMVSOS400OS/2JavaVMMSDOSWIN3xWIN95WIN98WINNTWINCENCR3000NetWareOSFDC/OSReliant UNIXSCO UnixWareSCO OpenServerSequentIRIXSolarisSunOSU6000ASERIESTandemNSKTandemNTBS2000LINUXLynxXENIXVMInteractive UNIXBSDUNIXFreeBSDNetBSDGNU HurdOS9MACH KernelInfernoQNXEPOCIxWorksVxWorksMiNTBeOSHP MPENextStepPalmPilotRhapsodyWindows 2000DedicatedOS/390VSETPFWindows (R) MeCaldera Open UNIXOpenBSDNot ApplicableWindows XPz/OSCIM_SoftwareElement.TargetOperatingSystem 2.6.0FileSpecification identifies a file that is either to be on or off the system. The file is to be located in the directory identified in FileName, or by the CIM_DirectorySpecificationFile association. When the Invoke methods are executed, it is expected that they will use a combination of information to check for file existence. Therefore, any of the properties with a NULL value are not checked. So, if only the FileName and MD5Checksum properties have values, they are the only ones considered by the Invoke methods.1024Either the name of the file or the name of the file with a directory prefix.The creation date and time of the file.KiloBytesA checksum calculated as the 16-bit sum of the first 32 bytes of the file.MIF.DMTF|Software Signature|002.4The CRC1 property is the CRC value calculated using the middle 512K bytes of the file.MIF.DMTF|Software Signature|002.5The CRC2 property is the CRC value for the middle 512K bytes of the file, modulo 3.MIF.DMTF|Software Signature|002.632The MD5 algorithm is a well-known algorithm for computing a 128-bit checksum for any file or object. For purposes of MOF specification of the MD5Checksum property, the MD5 algorithm always generates a 32 character string. For example: The string abcdefghijklmnopqrstuvwxyz generates the string c3fcd3d76192e4007dfb496cca67e13b. See http://www.ietf.org - RFC1321 for details on the implementation of the MD5 algorithm. 2.6.0The VersionCompatibilityCheck class specifies whether it is permissible to create the next state of a SoftwareElement.The AllowDownVersion property indicates that this SoftwareElement can transition to its next state even if a higher or later version of the element already exists in the environment.The AllowMultipleVersions option controls the ability to configure multiple versions of a SoftwareElement on a system.The Reinstall property indicates that this SoftwareElement can transition to its next state even if an element of the same version already exists in the environment. 2.6.0This class specifies information needed to verify a particular 'setting' file, for a specific entry in the file. The file entry is checked whether it contains or matches the value defined in EntryValue. All compares are assumed to be case insensitive.256Key or label for the section of the file containing the settings to be checked.256Name of the setting entry to be checked.Value to be compared for the named entry.CheckType specifies how the setting value should be compared.01MatchesContains1024File name of the 'setting' file to be checked. truetrue2.6.0This association ties a SoftwareElement to a specific Check to validate its state or its movement to the next state. Note that SoftwareElements in a running state cannot transition to another state. Therefore, the value of the Phase property is restricted to 0 ("In-State") for SoftwareElements in the running state.true11trueThe SoftwareElement being checked.truetrueThe Check for the element.The Phase property indicates whether the referenced Check is an in-state or a next-state Check.01In-StateNext-State true2.6.0The CIM_DirectorySpecificationFile association identifies the directory that contains the file being checked in the CIM_FileSpecification class.true1The directory to be checked.trueThe file to be checked. true2.7.0 A CIM_Action is an operation that is part of a process to either create a SoftwareElement in its next state or to eliminate the SoftwareElement in its current state. A CIM_ComputerSystem object represents the environment in which CIM_SoftwareElements are already deployed/installed or into which the elements will be deployed/installed. For the case in which an element is already installed, the CIM_InstalledSoftwareElement association identifies the CIM_ComputerSystem object that represents the "environment". When a SoftwareElement is being deployed for installation on a ComputerSystem, that system is the target of the Action and is identified using the TargetSystem reference of the InvokeOnSystem method.CIM_SoftwareElement.Nametrue256The name used to identify the SoftwareElement that is being acted upon.CIM_SoftwareElement.Versiontrue64The version of the SoftwareElement being acted upon.CIM_SoftwareElement.SoftwareElementStatetrueThe SoftwareElementState of the SoftwareElement being acted upon.0123DeployableInstallableExecutableRunningCIM_SoftwareElement.SoftwareElementIDtrue256This is an identifier for the SoftwareElement being acted upon.CIM_SoftwareElement.TargetOperatingSystemtrueThe Target Operating System of the SoftwareElement being acted upon.01234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768UnknownOtherMACOSATTUNIXDGUXDECNTTru64 UNIXOpenVMSHPUXAIXMVSOS400OS/2JavaVMMSDOSWIN3xWIN95WIN98WINNTWINCENCR3000NetWareOSFDC/OSReliant UNIXSCO UnixWareSCO OpenServerSequentIRIXSolarisSunOSU6000ASERIESTandemNSKTandemNTBS2000LINUXLynxXENIXVMInteractive UNIXBSDUNIXFreeBSDNetBSDGNU HurdOS9MACH KernelInfernoQNXEPOCIxWorksVxWorksMiNTBeOSHP MPENextStepPalmPilotRhapsodyWindows 2000DedicatedOS/390VSETPFWindows (R) MeCaldera Open UNIXOpenBSDNot ApplicableWindows XPz/OStrue256The ActionID property is a unique identifier assigned to a particular Action for a SoftwareElement.The Direction property is used to indicate whether this Action is part of a sequence to transition the SoftwareElement to its next state ("Install") or to remove the element ("Uninstall").01InstallUninstall The Invoke method takes this Action. The details of how the Action is implemented are described by specific subclasses of CIM_Action. When the SoftwareElement being transitioned or eliminated is already installed, the CIM_InstalledSoftwareElement association identifies the CIM_ComputerSystem in whose context the Invoke is executed. If this association is not in place, then the InvokeOnSystem method should be used - since it identifies the TargetSystem as a parameter of the method. The results of the Invoke method are based on the return value. A zero is returned if the Action is satisfied. A one is returned if the method is not supported. Any other value indicates the Action is not satisfied. The InvokeOnSystem method takes this Action. The details of how the Action is implemented are described by specific subclasses of CIM_Action. The method's TargetSystem input parameter specifies the ComputerSystem in whose context the method is invoked. The results of the InvokeOnSystem method are based on the return value. A zero is returned if the Action is satisfied. A one is returned if the method is not supported. Any other value indicates the Action is not satisfied.true true2.6.0DirectoryAction is an abstract class used to manage directories. The creation of directories is handled by CreateDirectoryAction and removal is handled by RemoveDirectoryAction.1024The name of the directory being managed. 2.6.0CreateDirectoryAction creates empty directories for SoftwareElements to be installed locally. 2.6.0RemoveDirectoryAction removes directories from the computer system that defines the Action's environment.Boolean property indicating that the directory must be empty in order to be removed. If this condition is not satisfied, then the Invoke methods return an error. true2.6.0FileAction locates files that already exist on the CIM_ComputerSystem that defines the Action's environment. These files are removed or moved/copied to a new location. 2.6.0CopyFileAction specifies the files to be moved or copied to a new location. The to/from information for the copy is specified using either the ToDirectorySpecification/FromDirectorySpecification or the ToDirectoryAction/FromDirectoryAction associations. The first set is used when the source and/or the target are to exist before any Actions are taken. The second set is used when the source and/or target are created as a part of a previous Action (specified using the association, ActionSequence).1024The source directory.1024The destination directory.Boolean indicating that the file should be deleted after being copied. 2.6.0The RemoveFileAction uninstalls files.1024The file to be removed. 2.6.0RebootAction causes a reboot of the computer system that defines the Action's environment. 2.6.0ExecuteProgram causes programs to be executed on the computer system that defines the Action's environment.1024The location or 'path' where the program is found.A string that can be executed and invokes program(s), from a system's command line. 2.6.0This class specifies the information used to modify a 'setting' file, for a specific entry in the file. The new 'setting' value is created as a new entry or appends to, replaces, removes from, or deletes the specified entry. All additions are assumed to be case sensitive. Removes are assumed to be case insensitive.256This is the key or label of the section of the file to be modified.256Name of setting entry to be modified.This is the value to add, append, or replace the specified setting.1024File name of the 'setting' file.Type of Action to be performed on the specified setting entry. 0=Create - Creates the specified entry. 1=Delete - Deletes the specified entry. 2=Append - Appends to the end of the specified entry. 3=Remove - Removes the value from the specified entry.0123CreateDeleteAppendRemove true2.6.0 The CIM_ActionSequence association defines a series of operations that either transition a SoftwareElement, referenced by the CIM_SoftwareElementActions association, to the next state or removes the element from its current state. The Action classes participating in this association must have the same value for the Action.Direction property - since they are either part of a sequence to transition a SoftwareElement into its next state or to uninstall it. The next-state and uninstall Actions associated with a particular SoftwareElement must be a continuous sequence. ActionSequence is an association that loops on the Action classes with roles for the 'prior' and 'next' Actions in the sequence. The need for a continuous sequence imples: (1)Within the set of next-state or uninstall Actions, there is one and only one Action that does not have an instance of ActionSequence referencing it in the 'next' role. This is the first Action in the sequence. (2) Within the set of next-state or uninstall Actions, there is one and only one Action that does not have an instance of ActionSequence referencing it in the 'prior' role. This is the last Action in the sequence. (3) All other Actions within the set of next-state and uninstall Actions must participate in two instances of ActionSequence, one in a 'prior' role and the other in the 'next' role.true1The next Action in the sequence.true1The previous Action in the sequence. truetrue2.6.0This association identifies the Actions for a SoftwareElement.true11trueThe element that scopes the Action.truetrueThe software Action to move or uninstall a SoftwareElement. true2.6.0The ToDirectorySpecification association identifies the target directory for a FileAction. When this association is used, the assumption is that the target directory already exists. This association cannot co-exist with a ToDirectoryAction association, since a FileAction can only involve a single target directory.true1The destination directory of the Action.trueThe Action against the directory. true2.6.0The FromDirectorySpecification association identifies the source directory for a FileAction. When this association is used, the assumption is that the source directory already exists. This association cannot co-exist with a FromDirectoryAction association, since a FileAction can only involve a single source directory.true1The source directory of the Action.trueThe Action against the directory. true2.6.0The ToDirectoryAction association identifies the target directory for a FileAction. When this association is used, the assumption is that the target directory was created by a previous Action. This association cannot co-exist with a ToDirectorySpecification association, since a FileAction can only involve a single target directory.true1The destination directory of the Action.trueThe Action against the directory. true2.6.0The FromDirectoryAction association identifies the source directory for a FileAction. When this association is used, the assumption is that the source directory was created by a previous Action. This association cannot co-exist with a FromDirectorySpecification association, since a FileAction can only involve a single source directory.true1The source directory of the Action.trueThe Action against the directory. true2.6.0The InstalledSoftwareElement association allows the identification of the ComputerSystem on which a particular SoftwareElement is installed.trueReference to the Software Element that is installed.true1Reference to the ComputerSystem hosting a particular SoftwareElement. 2.6.0Indicates the SoftwareFeatures that make up the OperatingSystem. The SoftwareFeatures can be part of different Products.truetrueGroupComponentThe OperatingSystem.truetruePartComponentThe SoftwareFeatures that make up the OperatingSystem.true 2.6.0This is an association class relating DiagnosticTest to the SoftwareElements that provide this test. SoftwareElement describes vendor/version information and other deployment data.trueAntecedentVendor/version and other information about the software that runs as the DiagnosticTest.trueDependentThe DiagnosticTest whose software is described.true 2.6.0BIOSFeature represents the capabilities of the low-level software that is used to bring up and configure a ComputerSystem.An array of integers that specify the features supported by the BIOS. For example, one can specify that PnP capabilities are provided (value=9) or that infrared devices are supported (21). Values specified in the enumeration are taken from both DMI and SMBIOS (the Type 0 structure, the BIOS Characteristics and BIOS Characteristics Extension Bytes attributes.12345678910111213141516171819202122232425262728293031160OtherUnknownUndefinedISA SupportMCA SupportEISA SupportPCI SupportPCMCIA SupportPnP SupportAPM SupportUpgradeable BIOSBIOS Shadowing AllowedVL VESA SupportESCD SupportLS-120 Boot SupportACPI SupportI2O Boot SupportUSB Legacy SupportAGP SupportPC CardIR1394I2CSmart BatteryATAPI ZIP Drive Boot Support1394 Boot SupportBoot from CDSelectable BootBIOS ROM is SocketedBoot from PCMCIAEDD Specification SupportPC-98MIF.DMTF|BIOS Characteristic|004.3IndexedCIM_BIOSFeature.CharacteristicDescriptionsAn array of free-form strings providing more detailed explanations for any of the BIOS features indicated in the Characteristics array. Note, each entry of this array is related to the entry in the Characteristics array that is located at the same index.IndexedMIF.DMTF|BIOS Characteristic|004.4CIM_BIOSFeature.Characteristics 2.6.0BIOSElement represents the low-level software that is loaded into non-volatile storage and used to bring up and configure a ComputerSystem.VersionMIF.DMTF|System BIOS|001.3true64Software Version should be in the form <Major>.<Minor>.<Revision> or <Major>.<Minor><letter><revision>.ManufacturerMIF.DMTF|System BIOS|001.2256Manufacturer of this SoftwareElement.If true, this is the primary BIOS of the ComputerSystem.MIF.DMTF|System BIOS|001.9A list of installable languages for the BIOS. This information can be obtained from SMBIOS, from the string list that follows the Type 13 structure. An ISO 639 Language Name should be used to specify the BIOS' installable languages. The ISO 3166 Territory Name and the encoding method may also be specified, following the Language Name.The currently selected language for the BIOS. This information can be obtained from SMBIOS, using the Current Language attribute of the Type 13 structure, to index into the string list following the structure. The property is formatted using the ISO 639 Language Name, and may be followed by the ISO 3166 Territory Name and the encoding method.CIM_BIOSElement.ListOfLanguagesThe starting address of the memory which this BIOS occupies.MIF.DMTF|System BIOS|001.5The ending address of the memory which this BIOS occupies.MIF.DMTF|System BIOS|001.664A free form string describing the BIOS flash/load utility that is required to update the BIOSElement. Version and other information may be indicated in this property.MIF.DMTF|System BIOS|001.7Date that this BIOS was released.MIF.DMTF|System BIOS|001.8 2.6.0A link between BIOSFeature and its aggregated BIOSElements.truetrueThe BIOSFeature.GroupComponenttruetrueThe BIOSElement that implements the capabilities described by BIOSFeature.PartComponenttrue 2.7.0SystemBIOS associates a UnitaryComputerSystem's BIOS with the System itself.truetrue1The ComputerSystem that boots from the BIOS.GroupComponenttruetrueThe System's BIOS.PartComponenttrue 2.6.0VideoBIOSFeature represents the capabilities of the low-level software that is used to bring up, configure and use a ComputerSystem's VideoController and Display.An array of integers that specify the features supported by the VideoBIOS. For example, one could indicate support for VESA power management (value=6) or video BIOS shadowing (8). The value, 3, is not valid in the CIM Schema since in DMI it represents that no BIOS Features are supported. In this case, the object should not be instantiated.123456789OtherUnknownUndefinedStandard Video BIOSVESA BIOS Extensions SupportedVESA Power Management SupportedVESA Display Data Channel SupportedVideo BIOS Shadowing AllowedVideo BIOS UpgradeableIndexedMIF.DMTF|Video BIOS Characteristic|001.3CIM_VideoBIOSFeature.CharacteristicDescriptionsAn array of free-form strings providing more detailed explanations for any of the VideoBIOS features indicated in the Characteristics array. Note, each entry of this array is related to the entry in the Characteristics array that is located at the same index.IndexedMIF.DMTF|Video BIOS Characteristic|001.4CIM_VideoBIOSFeature.Characteristics 2.6.0VideoBIOSElement represents the low-level software that is loaded into non-volatile storage and used to bring up, configure and access a ComputerSystem's VideoController and Display.VersionMIF.DMTF|Video BIOS|001.3true64Software Version should be in the form <Major>.<Minor>.<Revision> or <Major>.<Minor><letter><revision>.ManufacturerMIF.DMTF|Video BIOS|001.2256Manufacturer of this SoftwareElement.If true, indicates that the Video BIOS is shadowed.MIF.DMTF|Video BIOS|001.5Date that this BIOS was released.MIF.DMTF|Video BIOS|001.4 2.6.0A link between VideoBIOSFeature and its aggregated VideoBIOSElements.truetrueThe VideoBIOSFeature.GroupComponenttruetrueThe VideoBIOSElement that implements the capabilities described by VideoBIOSFeature.PartComponenttrue 2.6.0AGPSoftwareFeature adds two attributes to SoftwareFeature to represent the capabilities of an AGP device driver. An instance of this class would be associated with the Driver's SoftwareElement using the SoftwareFeatureSoftwareElements relationship. The driver's SoftwareElement is associated with the AGPVideoController via the DeviceSoftware relationship.An array of integers indicating various capabilities and characteristics of the AGPVideoController.Indexed0123456UnknownOtherOS supportHardware AccelerationHardware BlitOpenGL SupportCache CoherencyCIM_AGPSoftwareFeature.CharacteristicDescriptionsAn array of free-form strings providing more detailed explanations for any of the features indicated in the Characteristics array. Each entry in this array is related to the Characteristics array entry located at the same index.IndexedCIM_AGPSoftwareFeature.Characteristics 2.7.0CIM_BaseMetricDefinition represents the definitional aspects of a metric, i.e., a definition template containing meta data about a new metric. Since CIM_BaseMetricDefinition does not capture metric instance information, it does not contain the value of the metric. The associated class CIM_BaseMetricValue holds the metric value and encapsulates its runtime behavior. The purpose of CIM_BaseMetricDefinition is to provide a convenient mechanism for introducing a new metric definition at runtime and capturing its instance values in a separate class. This mechanism is targeted specifically at CIM users who would like to enhance existing CIM schemas by introducing domain-specific metrics that are not captured in the existing CIM schemas. In addition, vendors of managed resources may make use of this mechanism if a small subset of a potentially large and heterogeneous amount of performance-related data needs to be exposed, based on the context in which the data is captured. Additional meta data for a metric can be provided by subclassing from CIM_BaseMetricDefinition. The CIM_BaseMetricDefinition should be associated with the CIM_ManagedElement(s) to which it applies.trueA string that uniquely identifies the metric definition. The use of OSF UUID/GUIDs is recommended.The name of the metric. This name does not have to be unique, but should be descriptive and may contain blanks.The data type of the metric. For example, "boolean" (value=1) or "datetime" (=3) may be specified. Thesetypes represent the datatypes defined for CIM.1234567891011121314booleanchar16datetimereal32real64sint16sint32sint64sint8stringuint16uint32uint64uint8An enumerated value that describes the characteristics of the metric, for purposes of performing calculations. The property can take one of the following values: 1="Non-calculable" -> a string. Arithmetic makes no sense. 2="Summable" -> It is reasonable to sum this value over many instances of e.g., UnitOfWork, such as the number of files processed in a backup job. For example, if each backup job is a UnitOfWork, and each job backs up 27,000 files on average, then it makes sense to say that 100 backup jobs processed 2,700,000 files. 3="Non-summable" -> It does not make sense to sum this value over many instances of UnitOfWork. An example would be a metric that measures the queue length when a job arrives at a server. If each job is a UnitOfWork, and the average queue length when each job arrives is 33, it does not make sense to say that the queue length for 100 jobs is 3300. It does make sense to say that the mean is 33.123Non-calculableSummableNon-summableIdentifies the specific units of a value. Examples are Bytes,Packets, Jobs, Files, Milliseconds, and Amps.Defines one or more strings that can be used to refine (break down) queries against the BaseMetricValues along a certain dimension. An example is a transaction name, allowing the break down of the total value for all transactions into a set of values, one for each transaction name. Other examples might be application system or user group name. The strings are free format and should be meaningful to the end users of the metric data. The strings indicate which break down dimensions are supported for this metric definition, by the underlying instrumentation. 2.7.0 Each CIM_BaseMetricValue object represents the instance value of a metric. Since the gathering of metric information can involve large quantities of information there may be many instances of this class. The use of this class as an instrumentation source may be inefficient unless the rate of metrics are known. The length of time a CIM_BaseMetricValue instance exists after the metric information is captured is not defined and is implementation dependent. Most metric data values change over time. There are two ways of mapping this into CIM_BaseMetricValue objects: The value for the next point in time may use the same object and just change its properties (such as the value or timestamp), or the existing objects remain unchanged and a new object is created for the new point in time. The first method is typically used for snapshot data and the second method for historical data. Which method is used, is indicated by the Volatile property.trueA unique identifier of this instance of the metric value. This must be a globally unique identifier.trueThe key of the BaseMetricDefinition instance for this CIM_BaseMetricValue instance value.CIM_BaseMetricDefinition.Id A descriptive name for the element to which the metric value belongs (i.e., the measured element). This property is required by behavior if there is no association defined to a ManagedElement, but may be used in other cases to provide supplemental information. This allows metrics to be captured independently of any ManagedElement. An example is where a metric value belongs to a combination of elements, such as the input and output ports of the traffic in a switch. If there are multiple ManagedElements associated with the metric value, then usually there is one that naturally belongs to the metric value and that one should be used to create the supplemental information. The property is not meant to be used as a foreign key to search on the measured element. Instead, the association to the ManagedElement should be used.Identifies the time when the value of a metric instance is computed. Note that this is different from the time when the instance is created. For a given CIM_BaseMetricValue instance, the TimeStamp changes whenever a new measurement snapshot is taken if Volatile is true. A managmenet application may establish a time series of metric data by retrieving the instances of CIM_BaseMetricValue and sorting them according to their TimeStamp.Property that represents the time duration over which this metric value is valid. This property should not exist for timestamps that apply only to a point in time but should be defined for values that are considered valid for a certain time period (ex. sampling). If the "Duration" property exists and is nonNull, the TimeStamp is to be considered the end of the interval.trueThe value of the metric represented as a string. Its original data type is specified in CIM_BaseMetricDefinition.If present, specifies one BreakdownDimension from the BreakdownDimensions array defined in the associated CIM_BaseMetricDefinition. This is the dimension along which this set of metric values is broken down. For a description of the concept, see the class CIM_BaseMetricDefinition.Defines a value of the BreakdownDimension property defined for this metric value instance. For instance, if the BreakdownDimension is "TransactionName", this property could name the actual transaction to which this particular metric value applies.If true, Volatile indicates that the value for the next point in time may use the same object and just change its properties (such as the value or timestamp). If false, the existing objects remain unchanged and a new object is created for the new point in time. 2.7.0Weak association of metric value objects with their metric definition. This association ties an instance of CIM_BaseMetricValue to its CIM_BaseMetricDefinition; it is weak because the existence of a CIM_BaseMetricValue depends on the existence of its associated CIM_BaseMetricDefinition: An instance of CIM_BaseMetricValue must not exist without being associated to its corresponding CIM_BaseMetricDefinition.trueAntecedent11The CIM_BaseMetricDefinition for this particular CIM_BaseMetricValue.trueDependentA CIM_BaseMetricValue instance holding the Value.true 2.7.0This association ties a CIM_BaseMetricDefinition to a CIM_ManagedElement to define metrics for the latter. The metrics definition is given context by the ManagedElement, which is why the definition is dependent on the element.trueAntecedentThe CIM_ManagedElement that can have metrics of this type associated with it.trueDependentA CIM_BaseMetricDefinition for a CIM_ManagedElement.true 2.7.0This association links a ManagedElement to the metric values being maintained for it.trueAntecedentManagedElement to which the metric values belong.trueDependentA metric value for the ManagedElement.true 2.7.0A LogicalElement that describes units of work (e.g. transactions). This class represents the definitional components of a unit of work, and not the unit itself.NameThe name of the Definition. This name does not have to be unique, but should be descriptive. It may contain blanks.1024A free format string describing the context of the defined UnitOfWork. For example an 'Add Order' Unit could be defined in the context of a book ordering application, whereas another 'Add Order' UnitOfWork could be defined for a computer ordering application. It may contain blanks.true16A 16 byte value that uniquely identifies the UnitOfWorkDefinition. The use of OSF UUID/GUIDs is recommended.16CIM_TraceLevelType.InstanceId A 16 byte value that uniquely identifies the applied semantics and format of the trace levels used in the instances of UnitOfWork. The use of OSF UUID/GUIDs is recommended. TraceLevelTypeId allows management applications to efficiently discriminate between different trace level semantics of different UnitOfWorkDefinitions. I.E., CIM_UnitOfWork.TraceLevel = 1 may have different semantics if TraceLevelTypeId is different for the respective instances of UnitOfWork. It is not assumed that different trace level semantics are used within the same UnitOfWorkDefinition in order to promote uniform trace level encodings. (Keep in mind: At least the developers of the business actions represented by the same UnitOfWorkDefinition instance should strive to use the same trace level encoding, otherwise the administrator will have a hard time to figure out what detailed information to expect.) If the string is empty no traces are expected to be produced. If the string is not empty, an associated instance of TraceLevelType may be attached to the UnitOfWorkDefinition instance. Still, it is useful to incorporate TraceLevelTypeId into UnitOfWorkDefinition, to relate to an instance of TraceLevelType. The management application can more easily detect different trace level types. 2.7.0The metrics that are associated with a UnitOfWork. These metrics usually describe some aspect of a UnitOfWork such as how much work was done, or the size of the UnitOfWork. For example, the size of a print job or the number of pages printed could be metrics of a 'print' UnitOfWork.Id16A 16 byte value that uniquely identifies the MetricDefinition. The use of OSF UUID/GUIDs is recommended.trueAn enumerated value describing when the Metric may be considered valid. Some metrics are valid only at the beginning of a transaction (e.g., bytes to print), while the transaction is running (e.g., percent complete), or when the transaction is finished (e.g., pages printed). If a metric is valid at more than one of the enumerated values, such as both when the unit of work starts and when it stops, it is recommended to not use Validity.123At StartIn MiddleAt Stop 2.7.0TraceLevelType defines the encoding and semantics of trace levels. A trace is data that is produced during the execution of program code in order to provide information on the behaviour of the code (e.g. textual data written to files). Traces may be used for error detection/analysis or debugging. Trace levels define the granularity and/or type of the traces that are to be produced by the program code. Depending on the program implementation, levels may be applied on the fly. The possible levels are also implementation dependent, since no general rules or standards exist. In consequence, program developers could reuse their existing trace level scheme. Traces are valuable information sources for management applications in cases of error detection/analysis. In order to correctly set trace levels to the level needed (exciting exhaustive tracing by accident may result in significant system resources consumption in terms of processing time and storage) and to efficiently interpret which level of detail to expect from traces already produced by some resource, the possible trace level values and their meaning (semantics) must be known by the user and/or the management application. The type does not define the location or access method of the traces, since traces of a particular type can have multiple locations as well as multiple access methods.true16CIM_UnitOfWorkDefinition.TraceLevelTypeIdA 16 byte value that uniquely identifies the trace level type. The use of OSF UUID/GUIDs is recommended.Describes the technical encoding of the trace level. 0: bit map = switches to turn on/off appropriate trace production (e.g. 0x00000010, 0x0000F000); the use of bit maps implies that the switches can be or-ed bitwise: Values[1] | Values[2] | ... . 1: number = plain numbers that define levels (e.g. 1, 2, 7); the recommended and most common encoding scheme 2: any other encoding scheme you could think of (e.g. mixture of bit maps and numbers).OtherBitmapNumber123IndexedtrueEach entry in the array is one possible value of the trace level of this type. Depending on the base type, these are either switches defined as bit maps (e.g. 0x00000001, 0x000000F0, ...) or plain numbers (1, 2, 3, ...). In either encoding, the value 0 is reserved for the equivalent of 'no trace'.IndexedtrueThe index corresponds to TraceLevelType.TraceValues[]. The array provides human-readable descriptions of the semantics of each value entered in the TraceValues array. 2.6.0An association that describes the Metrics related to a UnitOfWorkDefinition. This is a Dependency relationship since the MetricDefinition relies on the UnitOfWorkDefinition for context. At least one context must be defined for a MetricDefinition, hence the Min (1) qualifier is placed on the UnitOfWorkDefinition reference.trueAntecedent1The UnitOfWorkDefinition where the Metric applies.trueDependentThe MetricDefinition for a particular UnitOfWork.true 2.7.0Each instance of UnitOfWork identifies a transaction that is either in-process or already completed. Because instances of 'in-process' UnitsOfWork can be very short-lived and there can be a great number of active ones, use of this class as an instrumentation source for determining response time may be incorrect or inefficient, unless the rate and duration of the UnitsOfWork are known. The intended use is to respond to queries about currently active or recently completed UnitsOfWork. The length of time that a UnitOfWork instance exists after the UnitOfWork completes is not defined and should be assumed to be implementation-dependent. This class is weak to its definition (CIM_UnitOfWorkDefintion).DescriptionSince UnitOfWork is designed to be an extremely lightweight object, it is recommended that this property not be used. The Description specified for the instance's associated CIM_UnitOfWorkDefintion should apply.trueThe identifier of the UnitOfWork, within the context of the UnitOfWorkDefinition.true16CIM_UnitOfWorkDefinition.IdA 16 byte value that uniquely identifies the UnitOfWorkDefinition. The use of OSF UUID/GUIDs is recommended.The name of the user who initiated the UnitOfWork. This may be a real user's login name or a logical name representing an application.The time that the UnitOfWork was started.The elapsed time since the UnitOfWork was started. Upon completion of the UnitOfWork, this property contains the total amount of time taken in processing the entire UnitOfWork.An enumeration identifing the status of the UnitOfWork. Most of the property values are self-explanatory, but a few need additional text: 3="Completed" - Should be used to represent a 'completed' transaction whose status ('good', 'failed' or 'aborted') is unknown. 6="Completed Aborted" - Should be used when a UnitOfWork has completed but was not allowed to end normally. An example would be when the Stop or Back buttons are selected from a web browser, before a page is fully loaded.123456ActiveSuspendedCompletedCompleted GoodCompleted FailedCompleted Aborted Indicates the granularity at which traces are written for this particular instance of UnitOfWork. Traces allow providing more detailed information on the course of the execution of the UnitOfWork than just the status and the elapsed time. The trace level does not indicate where the traces are found (i.e. in which file or CIM instances). TraceLevel cannot be set (i.e. written) since an instance of UnitOfWork only publishes information. So, the application code that executes the unit of work must receive the desired trace level by its caller (e.g. the parent module, the user or some remote system that initiates the unit of work). If its value is 0, no traces are available. If its value is > 0, traces are available. Except 0, the possible values and their semantics are implementation dependent. Two instances of UnitOfWork (even with the same definition) may have different trace levels since the desired or required granularity of traces may be dependent on the execution context (detection of an error, analysis of an error, etc.) of the unit of work. The trace level can be encoded as a bit map (each individual bit indicates a certain trace type and/or level of detail) or numbers (that are further defined by a value map). No encoding scheme is imposed since no general rules or standards exist and in consequence, application developers could reuse their existing trace level scheme. A string that uniquely identifies the mutual context of UnitOfWork instances. The context is defined as an individual action that several UnitOfWork instances participate in. The use of Ids such as OSF UUID/GUIDs is recommended, although some implementations may require longer Ids. (This is the reason why no maxlen(16) qualifier has been used.) MutualContextId explicitly identifies the context for instances of UnitOfWork, that is otherwise provided implicitly by SubUoW association instances. In addition, one can query directly (i.e. without following the associations) for UnitOfWork instances that participate in some individual action (i.e., the mutual context). If no mutual context is needed or if it is not supported by the implementation, the value is NULL. Note that the MutualContextId value is to be transferred internally between the participating UnitOfWork implementations such that each UnitOfWork instance implementation receives its value from its predecessor/parent or initially creates the value if it is the first instance of the context. 2.6.0This association ties a MetricDefinition to an instance of a UnitOfWork. Its primary purpose is to specify the value of the Metric for the instance of UnitOfWork. It is defined as a Dependency since the Metric value relies on the specific UnitOfWork for context.trueAntecedentThe UnitOfWork whose Metric value is specified.trueDependentThe MetricDefinition for this particular UnitOfWork and value. Note that the MetricDefinition must be associated (via UoWMetricDefinition) to the same UnitOfWorkDefinition to which the UnitOfWork is weakly associated.trueThe value of the Metric for the referenced UnitOfWork. Note that the type of the data and other information are defined by the properties of MetricDefinition. 2.6.0This association links a UnitOfWork (which is a 'started' transaction) to its Definition.trueAntecedent11The Definition object for the UnitOfWork.trueDependenttrueAn instance of a UnitOfWork that has started executing.true 2.6.0This association links a LogicalElement to the UnitsOfWork that it can perform. For example, a Printer Device may have associated UnitOfWorkDefinitions representing PrintJobs. This is a Dependency relationship since the Definitions are given context by the LogicalElement.trueAntecedentThe LogicalElement that is providing the UnitOfWork.trueDependentThe UnitOfWorkDefinition associated with the LogicalElement.true 2.6.0This association defines the sub-UnitsOfWork (the sub-transactions) for a particular UnitOfWorkDefinition. For example, an 'AddOrder' UnitOfWork could have sub-Units of 'ValidateCustomer', 'ValidatePartNumber', 'UpdateDatabase', etc. This is a Dependency relationship since the sub-UnitsOfWork are put in context relative to the parent Unit. It is not an aggregation relationship - since (using another example) a 'DatabaseWrite' transaction is likely to be dependent upon a 'DiskWrite', but the two transactions are separate concepts and one is not 'contained' by the other.trueAntecedentThe parent UnitOfWorkDefinition.trueDependentThe sub-UnitOfWorkDefinition.true 2.6.0This association identifies a specific execution of a UnitOfWork with the specific LogicalElement that is performing/has performed it. Where the LogicalElementUnitOfWorkDef association describes what an Element can do, this relationship describes what a particular Element is doing or has done.trueAntecedentThe LogicalElement performing the UnitOfWork.trueDependentThe UnitOfWork being performed.true 2.6.0Similar to the SubUoWDef association (which describes the relationship between definitional UnitsOfWork), this association identifies the executional UnitOfWork Dependencies. It associates executing/executed UnitsOfWork with their parent Units. In most cases, the SubUoW reflects the execution side of the relationship defined in SubUoWDef. However, there may be cases where the SubUoWDef is not defined, but for a particular UnitOfWork, the SubUoW relationship is valid. Therefore, it is not a requirement (but it is desirable) that there be a corresponding SubUoWDef for each instance of SubUoW.trueAntecedent1The parent executing/executed UnitOfWork. On the execution side, it is expected that a sub-Unit is associated with only one parent UnitOfWork.trueDependentThe sub-UnitOfWork. On the execution side, it is expected that a sub-Unit is associated with only one parent UnitOfWork.true true2.7.0Refers to the refinement of the UnitOfWorkDefinition: the trace level type. It is not required that a UnitOfWork be associated to a TraceLevelType. But if it is associated, only one Type can be specified for the Definition. In contrast, TraceLevelTypes can be reused for multiple Definitions.true1The trace level type description that is implemented by the UnitOfWorkDefinition.trueThe UnitOfWorkDefinition which is refined by the instance of TraceLevelType. 2.7.0Network is a subclass of AdminDomain that groups interconnected networking and computing objects capable of exchanging information. Instances of CIM_Network can represent an enterprise's global network or specific connectivity domains within the global network. These concepts are similar to those defined for the Network object in ITU's M.3100 specification.Recommendation.ITU|M3100.Network 2.6.0An Autonomous System (AS) is a fundamental concept in networking. An AS provides a structured view of routing by segregating the system that is using routing (e.g., the Internet, or an extranet) into a set of separately administered domains that each have their own independent routing policies. These domains are called autonomous systems. The classic definition of an AS, from RFC1771, is '...a set of routers under a single technical administration, using an interior gateway protocol and common metrics to route packets within the AS, and using an exterior gateway protocol to route packets to other ASs'. The RFC continues: 'Since this classic definition was developed, it has become common for a single AS to use several interior gateway protocols and sometimes several sets of metrics within an AS. The use of the term Autonomous System here stresses the fact that, even when multiple IGPs and metrics are used, the administration of an AS appears to other ASs to have a single coherent interior routing plan and presents a consistent picture of what destinations are reachable through it.'An ASNumber is an integer between 1 and 65535, with the range 64512 through 65535 reserved for private use. Every AS has a unique AS number, which is assigned to it by an Internet Registry or a provider. IANA assigns and administers AS numbers.IsSingleHomed is a boolean that, when its value is TRUE, indicates that this AS reaches networks outside of its domain through a single exit point.IsTransit is a boolean that, when its value is TRUE, indicates that this AS will advertise routes that it learns from other ASs. A non-transit AS will only advertise its own routes.RequireIGPSync is a boolean that, when its value is TRUE, indicates that this AS must obey the following rule: a router should not advertise destinations learned from internal neighbors to external destinations unless those destinations are also known via some internal gateway protocol. Otherwise, a router may receive traffic that cannot yet be routed. However, since this is a costly choice, it is common practice to allow this rule to be broken under certain carefully controlled circumstances.RoutingUpdateSource defines how routing information is to be injected. Statically injected routes are maintained by the routing table and are independent of the status of the networks to which they refer. This is done simply by defining static routes in the routing table. Dynamically injected routes are of two types. Dynamic routes refer to distributing all of the IGP routes. Semi-dynamic routes define a set of specific IGP routes that will be injected.0123UnknownStaticDynamicSemi-DynamicRoute aggregation refers to summarizing ranges of routes into one or more aggregate routes. This is done to minimize the number of routes in the global routing table. A potential drawback is that specific path information (e.g., the Path attribute value) is lost, which may lead to potential routing loops. There are a variety of ways to ensure that this does not happen. Note that BGP4 is required to do this. There are many ways to form aggregate routes. The following are the most popular: 'Aggregate only', where only the aggregate is advertised, and all of its more specific routes are suppressed; 'Aggregate Plus Specific Routes', where both the aggregate as well as its more specific routes are advertised (e.g., send the aggregate to the NAP, but send the more specific routes to providers); 'Aggregate Based on a Subset of Specific Routes', where the aggregate route is formed by looking at certain more specific routes and forming an aggregate on them, suppressing all others.01234UnknownNoneAggregate Only Aggregate And All Specific Routes Aggregate Based on Subset of Specific Routes true2.7.0This aggregation establishes 'whole-part' relationships between an AutonomousSystem and the routers that it contains. In addition, the routers in the AS share common configuration information, and are commonly administered.truetrue1The AutonomousSystem that aggregates the routers belonging to it and administers them.GroupComponenttruetrueThe Routers that are contained in the AS.PartComponenttrueThis is an array of strings that contain the BGP attributes supported by this router.TRUE means that the community value of this router is added to the existing community value, and FALSE means that the community value of this router replaces the existing community value.This is an enumeration that defines the function, from the point of view of BGP, of this router.01234567UnknownOtherConventional BGP SpeakerRoute ReflectorRouter Reflector ClientRoute Reflector Non-ClientPeer Group MemberConfederation MemberCIM_BGPService.OtherRoleDescription64A string describing the type of function that this router has in its AS when the value of the Role property of this class is set to 1 (i.e., "Other"). The format of the string inserted in this property should be similar in format to the values defined for the Role property. This property should be set to NULL when the Role property is any value other than 1.CIM_BGPService.Role CIM_ConnectivityCollection2.7.0A LogicalNetwork groups together a set of ProtocolEndpoints of a given type which are able to communicate with each other directly. It is used for describing the characteristics of the grouping and/or its associated medium. A LogicalNetwork represents the ability to send and/or receive data over a network. This class is deprecated in lieu of ConnectivityCollection. The latter better defines that a LogicalNetwork 'collects' ProtocolEndpoints and other related entities, and is hosted within an AdminDomain.trueNo valueCIM_AdminDomain.CreationClassName256The scoping AdminDomain's CreationClassName.trueNo valueCIM_AdminDomain.Name256The scoping AdminDomain's Name.trueNo value256CreationClassName 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.trueCIM_ConnectivityCollection.InstanceID256The Name property defines the label by which the object is known.CIM_ConnectivityCollection.ConnectivityTypeType is an enumeration that provides additional information that can be used to help categorize and classify different instances of this class. Subclasses should ensure that they are of the appropriate type defined in the Type enumeration. That is, the IPSubnet subclass should define its property as either IPv4 or IPv6, as opposed to, for example, ATM.0123456789101112131415161718UnknownOtherIPv4IPv6IPXAppleTalkDECnetSNACONPCLNPVINESXNSATMFrame RelayEthernetTokenRingFDDIInfinibandFibre ChannelCIM_LogicalNetwork.OtherTypeDescriptionCIM_ConnectivityCollection.OtherTypeDescription64A string describing the type of protocol that is being run by this LogicalNetwork, when the value of the Type property (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.CIM_LogicalNetwork.NetworkType true2.7.0CIM_HostedCollectionThis association is used to define the set of LogicalNetworks contained in an AdminDomain. This has the implied semantics that this set of LogicalNetworks are all managed by the same network administrator that manages the domain. Since the LogicalNetwork class is deprecated in lieu of ConnectivityCollection, this association is no longer necessary. It is deprecated to the HostedCollection association, that is inherited by ConnectivityCollection from its superclass, SystemSpecificCollection.trueCIM_HostedCollection.Antecedent11The AdminDomain that hosts the various LogicalNetworks.truetrueCIM_HostedCollection.DependentThe LogicalNetworks that are hosted by the AdminDomain. CIM_IPConnectivitySubnet2.7.0An IPSubnet represents a group of related IPProtocolEndpoints that can communicate with each other directly using IP. It is used for describing the characteristics of the grouping. Since this class' superclass (LogicalNetwork) has been deprecated (in order to define more consistent 'collection' semantics), this class is also deprecated.CIM_IPConnectivitySubnet.SubnetNumberThe IP address of the entire subnet, formatted according to the appropriate convention as defined in the AddressType property of this class.CIM_IPConnectivitySubnet.SubnetMaskThe mask for the starting IPv4 address of the IPSubnet, if needed (i.e., if the AddressType property is 1, "IPv4").CIM_IPConnectivitySubnet.PrefixLengthThe prefix length for IPv6 addresses in the IPSubnet, if needed (i.e., if the AddressType property is 2, "IPv6").CIM_IPConnectivitySubnet.AddressTypeAn enumeration that describes the format of the address properties in IPSubnet.012UnknownIPv4IPv6 CIM_LANConnectivitySegment2.7.0A collection of LAN Endpoints of a particular type that are able to intercommunicate directly without the assistance of bridging or routing services. Since this class' superclass (LogicalNetwork) has been deprecated (in order to define more consistent 'collection' semantics), this class is also deprecated.CIM_LANConnectivitySegment.LANID64A label or identifier for the LAN Segment.CIM_LANEndpoint.LANIDCIM_LANConnectivitySegment.ConnectivityTypeAn indication of the kind of technology used on the LAN.01234UnknownOtherEthernetTokenRingFDDICIM_LANEndpoint.LANTypeCIM_LANConnectivitySegment.OtherTypeDescription64A string describing the type of technology used on the LAN when the value of the LANType property of this class (or any of its subclasses) is set to 1 (i.e., "Other"). The format of the string inserted in this property should be similar in format to the values defined for the LANType property. This property should be set to NULL when the LANType property is any value other than 1.CIM_LANSegment.LANType CIM_IPXConnectivityNetwork2.7.0A network or subnet that uses the IPX protocol. Since this class' superclass (LogicalNetwork) has been deprecated (in order to define more consistent 'collection' semantics), this class is also deprecated.CIM_IPXConnectivityNetwork.NetworkNumberAn IPX network number formatted as eight hexadecimal digits (e.g., "00112233"). CIM_MemberOfCollection2.7.0This association defines a ProtocolEndpoint as a member of a specific LogicalNetwork. Since the LogicalNetwork class is deprecated in lieu of ConnectivityCollection, this association is no longer necessary. It is deprecated to the MemberOfCollection association, that is inherited by ConnectivityCollection from its superclass, Collection.truetrueCIM_MemberOfCollection.CollectionThe LogicalNetwork that groups the ProtocolEndpoint instances.CollectiontruetrueCIM_MemberOfCollection.MemberThe child ProtocolEndpoints that are components of the LogicalNetwork.Membertrue 2.7.0The class RangeOfIPAddresses represents an implicit grouping (or 'pool') of IP addresses specified by the properties, Start and EndAddress. It is defined as scoped/contained by a system such as an individual network element or an admin domain.The starting IP address of the AddressRange, formatted according to the appropriate convention as defined in the AddressType property of this class (e.g., 171.79.6.40).CIM_RangeOfIPAddresses.AddressTypeThe ending IP address of the AddressRange, formatted according to the appropriate convention as defined in the AddressType property of this class (e.g., 171.79.6.40).CIM_RangeOfIPAddresses.AddressTypeAn enumeration that defines how the address and mask properties are formatted.012UnknownIPv4IPv6 true2.7.0CIM_RangeOfIPAddressesIPAddressRange represents a grouping of specific addresses, and provides additional semantics for this group if appropriate. The class is deprecated in lieu of the concrete class RangeOfIPAddresses since there is sufficient information for the class to be instantiated. In addition, an address range should be defined in the context of a System (for example, a network element or an admin domain). These semantics are incorporated in the RangeOfIPAddresses class.CIM_RangeOfIPAddresses.StartAddressThe starting IP address of the AddressRange, formatted according to the appropriate convention as defined in the AddressType property of this class (e.g., 171.79.6.40).CIM_RangeOfIPAddresses.EndAddressThe ending IP address of the AddressRange, formatted according to the appropriate convention as defined in the AddressType property of this class (e.g., 171.79.6.40).CIM_RangeOfIPAddresses.AddressTypeAn enumeration that defines how to format the address and mask of the address range that defines this IPSubnet. Whenever possible, IPv4-compatible addresses should be used instead of IPv6 addresses (see RFC 2373, section 2.5.4). In order to have a consistent format for IPv4 addresses in a mixed IPv4/v6 environment, all IPv4 addresses and both IPv4-compatible IPv6 addresses and IPv4-mapped IPv6 addresses, per RFC 2373, section 2.5.4, should be formatted in standard IPv4 format.012UnknownIPv4IPv6No valueThis attribute defines the region that addresses can be allocated to.012345678UnknownMultiregional: 192.0.0.0 to 193.255.255.255Europe: 194.0.0.0 to 195.255.255.255Others: 196.0.0.0 to 197.255.255.255North America: 198.0.0.0 to 199.255.255.255Central & South America: 200.0.0.0 to 201.255.255.255Pacific Rim: 202.0.0.0 to 203.255.255.255Others: 204.0.0.0 to 205.255.255.255Others: 206.0.0.0 to 207.255.255.255 2.7.0A NamedAddressCollection groups ProtocolEndpoints/addresses and other network identifiers for the purposes of assigning a single name (i.e., an alias). It is a subclass of SystemSpecificCollection to force the definition of the 'named collection' in the context of a System (for example, either a ComputerSystem or an AdminDomain hosting a naming alias).truetrueA name (alias) for the NamedAddressCollection which is unique in the context of the hosting System. 2.7.0A ConnectivityCollection groups together a set of ProtocolEndpoints of the same 'type' (i.e., class) which are able to communicate with each other. It may also group related Systems, users or other ManagedElements. A ConnectivityCollection represents the ability to send and/or receive data over a set of ProtocolEndpoints. The collection is defined in the context of an AdminDomain or scoping ComputerSystem. This is mandated by the HostedCollection association on the SystemSpecificCollection superclass. Note that the entities aggregated into the Collection are specified using the association, MemberOfCollection.An enumeration describing the current or potential connectivity between endpoints in this collection. Connectivity may be provided or not, or may be in a degraded/partitioned state if one or more endpoints or links have failed. The latter would prevent full connectivity between all elements in the Collection, but would permit connectivity between subsets.0234UnknownConnectivity/UpNo Connectivity/DownPartitioned 2.7.0An IPConnectivitySubnet represents a group of related IPProtocolEndpoints that can communicate with each other, as members of a subnet. The class describes the characteristics of the subnet.The IP address of the entire subnet, formatted according to the appropriate convention as defined in the AddressType property of this class.CIM_IPConnectivitySubnet.AddressTypeThe mask for the starting IPv4 address of the IP subnet, if needed (i.e., if the AddressType property is 1, "IPv4").The prefix length for IPv6 addresses in the IP subnet, if needed (i.e., if the AddressType property is 2, "IPv6").An enumeration that describes the format of the address properties in IPConnectivitySubnet.012UnknownIPv4IPv6 2.7.0A collection of LAN Endpoints of a particular type (i.e., Ethernet or Token Ring), that are able to intercommunicate without the assistance of bridging or routing services. 64A label or identifier for the LAN segment.CIM_LANEndpoint.LANIDAn enumeration that categorizes and classifies instances of this class. Instances SHOULD aggregate entities of the appropriate 'type', as defined by the value of this enumeration.01234UnknownOtherEthernetTokenRingFDDICIM_LANConnectivitySegment.OtherTypeDescriptionA string describing the type of connectivity that is supported by this Collection, when the value of the Type property is set to 1 (i.e., "Other"). This property should be set to NULL when the Type property is any value other than 1.CIM_LANConnectivitySegment.ConnectivityType 2.7.0A network or subnet that uses the IPX protocol.An IPX network number formatted as eight hexadecimal digits (e.g., "00112233"). 2.7.0A communication endpoint which, when its associated interface device is connected to a LAN, may send and receive data frames. LANEndpoints include Ethernet,Token Ring and FDDI interfaces.A label or identifier for the LAN Segment to which the Endpoint is connected. If the Endpoint is not currently active/connected or this information is not known, then LANID is NULL.CIM_LANConnectivitySegment.LANIDCIM_LANSegment.LANIDCIM_ProtocolEndpoint.ProtocolTypeAn indication of the kind of technology used on the LAN. This property is deprecated in lieu of ProtocolType, which is an enumeration inherited from ProtocolEndpoint and which includes the Values specified here.01234UnknownOtherEthernetTokenRingFDDICIM_LANConnectivitySegment.ConnectivityTypeCIM_LANSegment.LANTypeCIM_ProtocolEndpoint.OtherTypeDescriptionA free-form string that describes the type of technology used on the LAN when the value of the LANType property is equal to 1 (i.e., "Other"). This property is deprecated since its purpose overlaps with OtherTypeDescription, which which is inherited from ProtocolEndpoint.CIM_LANConnectivitySegment.OtherTypeDescriptionCIM_LANEndpoint.LANType12The principal unicast address used in communication with the LANEndpoint. The MAC address is formatted as twelve hexadecimal digits (e.g., "010203040506"), with each pair representing one of the six octets of the MAC address in "canonical" bit order according to RFC 2469.Other unicast addresses that may be used to communicate with the LANEndpoint.Multicast addresses to which the LANEndpoint listens.The largest information field that may be sent or received by the LANEndpoint.Bits CIM_MemberOfCollection2.7.0Defines a LANEndpoint as a member of a specific LANSegment. Note that one of this association's references (LANSegment) is deprecated, as well as its superclass (InLogicalNetwork). Following the same logic as its parent, this association is deprecated to the MemberOfCollection association.truetrueCIM_MemberOfCollection.Collection1The LANSegment that groups the LANEndpoint instances.CollectiontruetrueCIM_MemberOfCollection.MemberA child LANEndpoint that is a component of the LANSegment.Membertrue 2.6.0This association makes explicit the dependency of a SAP or ProtocolEndpoint on an underlying LANEndpoint, on the same system.trueThe underlying LANEndpoint, which is depended upon.AntecedenttrueThe AccessPoint or ProtocolEndpoint dependent on the LANEndpoint.DependenttrueThis describes the framing method for the upper layer SAP or Endpoint that is bound to the LANEndpoint. Note: "Raw802.3" is only known to be used with the IPX protocol.01234UnknownEthernet802.2SNAPRaw802.3 2.7.0A ProtocolEndpoint that is dedicated to running IP.The IPv4 address that this ProtocolEndpoint represents.The IPv6 address that this ProtocolEndpoint represents.CIM_IPProtocolEndpoint.IPv4AddressCIM_IPProtocolEndpoint.IPv6AddressThe IP address that this ProtocolEndpoint represents, formatted according to the appropriate convention as defined in the AddressType property of this class (e.g., 171.79.6.40). This single property is deprecated to replace it by specific IPv4 and v6 addresses.The mask for the IPv4 address of this ProtocolEndpoint, if one is defined.The prefix length for the IPv6 address of this ProtocolEndpoint, if one is defined.No valueAn enumeration that describes the format of the Address property. It is deprecated since it is not needed, as the class contains both IPv4 and v6 addresses).012UnknownIPv4IPv6This property explicitly defines support for different versions of the IP protocol, for this Endpoint.0123UnknownIPv4 OnlyIPv6 OnlyBoth IPv4 and IPv6 2.7.0A ProtocolEndpoint that is dedicated to running BGP.A boolean that, when TRUE, signifies that this is an instance of the external version of BGP (FALSE is the internal version).Normally, two routers running EBGP must be physically connected. This boolean, when TRUE, denotes a LOGICAL connection between two routers that are running EBGP (e.g., there is an intermediate router or interface between them).This is the unique identifier of the local BGP router. This is often the router ID (e.g., an IP address).MIB.IETF|BGP4-MIB.bgpIdentifierThis is the unique identifier of the peer BGP router. This is often the router ID (e.g., an IP address).MIB.IETF|BGP4-MIB.bgpPeerIdentifierThis defines the current connection state of the BGP Peer.123456IdleConnectActiveOpenSetOpenConfirmEstablishedMIB.IETF|BGP4-MIB.bgpPeerStateCIM_EnabledLogicalElement.RequestedStateThis defines the desired state of the BGP connection. It is equivalent to the RequestedState property (i.e., enabled/disabled status) that is inherited from EnabledLogicalElement. AdminStatus is deprecated in lieu of this inherited property.12StopStartMIB.IETF|BGP4-MIB.bgpPeerAdminStatusThis defines the negotiated version of BGP that is running between the two peers.MIB.IETF|BGP4-MIB.bgpPeerNegotiatedVersionCIM_BindsToCIM_IPProtocolEndpointThis is the local IP address of this router's BGP connection. It is deprecated since a binding should be defined using the CIM_BindsTo association. Ideally the binding is to a TCPProtocolEndpoint which then handles the association to its IPEndpoint.MIB.IETF|BGP4-MIB.bgpPeerLocalAddrCIM_BindsToCIM_TCPProtocolEndpointThis is the local port number for the TCP connection of this router's BGP connection. It is deprecated since a binding should be defined (to a TCPProtocolEndpoint) using the CIM_BindsTo association.MIB.IETF|BGP4-MIB.bgpPeerLocalPortCIM_BindsToCIM_RemoteServiceAccessPointThis is the remote IP address of this router's BGP connection. It is deprecated since a binding to a RemoteServiceAccessPoint should be instantiated, using CIM_BindsTo.MIB.IETF|BGP4-MIB.bgpPeerRemoteAddrCIM_BindsToCIM_RemotePortThis is the remote port number for the TCP connection of this router's BGP connection. It is deprecated since a binding to a RemotePort should be instantiated, using CIM_BindsTo.MIB.IETF|BGP4-MIB.bgpPeerRemotePortThis is the remote AS number for this router's BGP connection.MIB.IETF|BGP4-MIB.bgpPeerRemoteAsThis defines the time interval, in seconds, for the ConnectRetry timer. The suggested value is 120 seconds.SecondsMIB.IETF|BGP4-MIB.bgpConnectRetryInterval120This defines the time interval in seconds for the Hold Time configured for this BGP speaker with a peer. This value is placed in an OPEN message sent to a peer by this BGP speaker, and is compared with the Hold Time field in the OPEN message received from the peer. It enables this speaker to establish a mutually agreeable Hold Time with the peer. This value must not be less than three seconds. If it is zero, then the Hold Time is NOT to be established with the peer. The suggestedvalue for this timer is 90 seconds.SecondsMIB.IETF|BGP4-MIB.bgpPeerHoldTimeConfigured90This defines the time interval in seconds for the KeepAlive timer configured for this BGP speaker with a peer. This value will determine the frequency of the KEEPALIVE messages relative to the value of the HoldTimeConfigured property; the actual frequency is specified by the value of the KeepAlive property. A reasonable value is one third of that of the value of the HoldTimeConfigured property. If it is zero, then NO periodic KEEPALIVE messages are sent to the peer. The suggested value for this property is 30 seconds. The maximum value of this property is 21845 seconds.SecondsMIB.IETF|BGP4-MIB.bgpPeerKeepAliveConfigured30This defines the time interval in seconds for the MinASOriginationInterval timer. The suggested value for this property is 15 seconds.SecondsMIB.IETF|BGP4-MIB.bgpPeerMinASOriginationInterval15This defines the time interval in seconds for the MinRouteAdvertisementInterval timer. The suggested value for this property is 30 seconds.SecondsMIB.IETF|BGP4-MIB.bgpPeerMinRouteAdvertisementInterval30This defines the maximum amount of time in seconds that may elapse between the receipt of successive KEEPALIVE or UPDATE messages. This is instrumented as a counter that increments from zero to the value specified in this property. The value of this property is calculated by the BGP speaker by using the smaller of the values of bgpPeerHoldTimeConfigured and the Hold Time received in the OPEN message. This value, if not zero seconds, must be at least three seconds, up to a maximum of 65535 seconds. Receipt of either a KEEPALIVE or an UPDATE message resets this value.SecondsMIB.IETF|BGP4-MIB.bgpPeerHoldTimeThis defines the time interval in seconds for the KeepAlive timer established with the peer. The value of this property is calculated by the speaker such that, when compared with the HoldTime property, it has the same proportion as the KeepAliveConfigured property has with the HoldTimeConfigured property. A value of 0 indicates that the KeepAlive timer has not yet been established. The maximum value of this property is 21845 seconds.SecondsMIB.IETF|BGP4-MIB.bgpPeerKeepAlive true2.7.0This aggregation defines the different router interfaces that are running BGP in the AutonomousSystem.truetrue1The AutonomousSystem that aggregates the router interfaces that are running BGP.GroupComponenttruetrueThe router interfaces that are contained in the AS.PartComponenttrue 2.6.0An IPX communication point from which data may be sent or received.An IPX address formatted as eight hexadecimal digits representing the network number, followed by a colon, followed by twelve hexadecimal digits representing the host address (e.g. "00112233:010203040506"). 2.7.0A protocol endpoint that is dedicated to running TCP.The TCP port number. 2.7.0A protocol endpoint that is dedicated to running UDP.The UDP port number. 2.7.0Base class for OSPF protocol endpoints, defining severalgeneral properties.EnabledStateThe operational status of the interface, see ospfIfAdminStat in RFC 1850. This is an integer enumeration whose complete definition is found in the EnabledLogicalElement class.MIB.IETF|OSPF-MIB.ospfIfAdminStat01234567891011..3276732768..65535UnknownOtherEnabledDisabledShutting DownNot ApplicableEnabled but OfflineIn TestDeferredQuiesceStartingDMTF ReservedVendor ReservedCIM_EnabledLogicalElement.OtherEnabledStateEstimated delay, in seconds that it takes to transmit a Link State Update Packet over this interface, see C.3 in RFC 2328.SecondsMIB.IETF|OSPF-MIB.ospfIfTransitDelayThe number of seconds between LSA (Link State Advertisement) retransmissions, see C.3 in RFC 2328.SecondsMIB.IETF|OSPF-MIB.ospfIfRetransIntervaltrueIdentifies the authentication procedure to be used on the attached network, see C.3 in RFC 2328.MIB.IETF|OSPF-MIB.ospfIfAuthType1234OtherNull authenticationSimple passwordCryptographic authenticationSpecifies the authentication procedure if the value, "Other" (1) is set for AuthType.CIM_OSPFProtocolEndpoint.AuthTypeThis key is used during the authentication procedure to verify OSPF protocol packets, see C.3 RFC 2328. It is used in the "Simple password" and in the "Cryptographic authentication" case too.MIB.IETF|OSPF-MIB.ospfIfAuthKey 2.7.0This class represents the OSPF configuration of an interface running OSPF. The instance of this class should be connected to an IPProtocolEndpoint instance via a BindsTo association. The IPProtocolEndpoint instance is the Antecedent and the OSPFProtocolEndpoint instance is the Dependent in the BindsTo association.When two routers attached to a network both attempt to become the Designated Router, the one with the highest (i.e. largest) Priority takes precedence, see C.3 in RFC 2328. Only routers with greater than zero priority are eligible to become Designated Router.MIB.IETF|OSPF-MIB.ospfIfRtrPriorityIf a neighbouring router on an NBMA (NonBroadcast MultiAccess) link becomes inactive, it is still necessary to send Hello Packets to the dead neighbor. These packets will be sent at the reduced rate, which should be much larger than HelloInterval, see C.5 in RFC 2328.SecondsMIB.IETF|OSPF-MIB.ospfIfPollIntervalThe cost of the routes through this OSPF endpoint, see C.3 in RFC 2328.MIB.IETF|OSPF-MIB.ospfIfMetricStatusIndicates whether the interface connects to an on-demand circuit, see RFC 1793.MIB.IETF|OSPF-MIB.ospfIfDemand 2.7.0This class represent an OSPF protocol endpoint on a virtual link. The definition of a virtual link from RFC2328, is 'Virtual links can be configured between any two backbone routers that have an interface to a common non-backbone area. Virtual links belong to the backbone. The protocol treats two routers joined by a virtual link as if they were connected by an unnumbered point-to-point backbone network.' 2.6.0CIM_EndpointIdentity indicates that two ProtocolEndpoints represent different aspects of the same underlying address or protocol-specific ID. This association refines the CIM_LogicalIdentity superclass by restricting it to the Endpoint level and defining its use in well understood scenarios. One of these scenarios is to represent that an Endpoint has both 'LAN' and protocol-specific aspects. For example, an Endpoint could be both a LANEndpoint as well as a DHCPEndpoint.trueSystemElementSystemElement represents one aspect of the Endpoint.trueSameElementSameElement represents an alternate aspect of the Endpoint.true 2.7.0Switch Port from which frames are received and out which they are transmitted. This endpoint is associated with its networking interface (such as Ethernet) via the EndpointIdentity relationship.Numeric identifier for a switch port.MIB.IETF|BRIDGE-MIB.dot1dPort true2.7.0A FilterList aggregates instances of (subclasses of) FilterEntryBase via the aggregation EntriesInFilterList. The filter entries are always ANDed together when grouped by the FilterList. Note that it is possible to aggregate different types of filters into a single FilterList - for example, packet header filters (represented by the IpHeadersFilter class) and IPsec security filters. A FilterList is weak to the network device (e.g., the ComputerSystem) that contains it. Hence, the ComputerSystem keys are propagated to this class.CIM_ComputerSystem.CreationClassNametrue256The scoping ComputerSystem's CreationClassName.CIM_ComputerSystem.Nametrue256The scoping ComputerSystem's Name.true256CreationClassName 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.Nametrue256The Name property defines the label by which the FilterEntry is known and uniquely identified.Boolean indicating that the match condition described in the properties of the FilterEntryBase subclass should be negated. 2.7.0A FilterEntry is used by network devices to identify traffic and either forward it (with possibly further processing) to its destination, or to deny its forwarding. It is one of the building block of FilterLists. This class is oriented towards packet filtering. Other subclasses of FilterEntryBase can be defined to do other types of filtering. A FilterEntry is weak to the network device (i.e., the ComputerSystem) that contains it. Hence, the ComputerSystem keys are propagated to this class.This defines the type of traffic that is being filtered. This will affect the filtering rules in the MatchCondition property of this class.012345UnknownIPv4IPXIPv6AnyOtherCIM_FilterEntry.OtherTrafficTypeIf the value of the TrafficType property in this class is 5 (i.e., "Other"), then the specific type of traffic is specified in this property.CIM_FilterEntry.TrafficTypeThis specifies one of a set of ways to identify traffic. If the value is 1 (i.e., "Other"), then the specific type of filtering is specified in the OtherMatchConditionType property of this class.12345678910111213OtherSource Address and MaskDestination Address and MaskSource PortSource Port RangeDestination PortDestination Port RangeProtocol TypeProtocol Type and OptionDSCPToS Value802.1P Priority ValueAnyCIM_FilterEntry.OtherMatchConditionTypeIf the value of the MatchConditionType property in this class is 1 (i.e., "Other"), then the specific type of filtering is specified in this property.CIM_FilterEntry.MatchConditionTypeThis is the value of the condition that filters the traffic. It corresponds to the condition specified in the MatchConditionType property. If, however, the value of the MatchConditionProperty is 1, then it corresponds to the condition specified in the OtherMatchConditionType property.This defines whether the action should be to forward or deny traffic meeting the match condition specified in this filter.12PermitDenyThis defines whether this FilterEntry is the default entry to use by its FilterList.This defines the traffic class that is being matched by this FilterEntry. Note that FilterEntries are aggregated into FilterLists by the EntriesInFilterList relationship. If the EntrySequence property of the aggregation is set to 0, this means that all the FilterEntries should be ANDed together. Consequently, the TrafficClass property of each of the aggregated Entries should be set to the same value. 2.6.0IPHeadersFilter contains the most commonly required properties for performing filtering on IP, TCP or UDP headers. Properties not present in an instance of the IPHeadersFilter are treated as 'all values'.HdrIPVersion identifies the version of the IP addresses for IP header filters. It is also used to determine the sizes of the OctetStrings in the six properties HdrSrcAddress, HdrSrcAddressEndOfRange, HdrSrcMask, HdrDestAddress, HdrDestAddressEndOfRange and HdrDestMask, as follows: ipv4(4): OctetString(SIZE (4)) ipv6(6): OctetString(SIZE (16|20)), depending on whether a scope identifier is present. If a value for this property is not provided, then the filter does not consider IP version in selecting matching packets, i.e., IP version matches for all values. In this case, the HdrSrcAddress, HdrSrcAddressEndOfRange, HdrSrcMask, HdrDestAddress, HdrDestAddressEndOfRange and HdrDestMask must also be not present.46IPv4IPv6CIM_IPHeadersFilter.HdrSrcAddressCIM_IPHeadersFilter.HdrSrcAddressEndOfRangeCIM_IPHeadersFilter.HdrSrcMaskCIM_IPHeadersFilter.HdrDestAddressCIM_IPHeadersFilter.HdrDestAddressEndOfRangeCIM_IPHeadersFilter.HdrDestMasktrueHdrSrcAddress is an OctetString, of a size determined by the value of the HdrIPVersion property, representing a source IP address. When there is no HdrSrcAddressEndOfRange value, this value is compared to the source address in the IP header, subject to the mask represented in the HdrSrcMask property. (Note that the mask is ANDed with the address.) When there is a HdrSrcAddressEndOfRange value, this value is the start of the specified range (i.e., the HdrSrcAddress is lower than the HdrSrcAddressEndOfRange) that is compared to the source address in the IP header and matches on any value in the range. If a value for this property is not provided, then the filter does not consider HdrSrcAddress in selecting matching packets, i.e., HdrSrcAddress matches for all values.CIM_IPHeadersFilter.HdrIPVersiontrueHdrSrcAddressEndOfRange is an OctetString, of a size determined by the value of the HdrIPVersion property, representing the end of a range of source IP addresses (inclusive), where the start of the range is the HdrSrcAddress property value. If a value for HdrSrcAddress is not provided, then this property also MUST NOT be provided. If a value for this property is provided, then HdrSrcMask MUST NOT be provided.CIM_IPHeadersFilter.HdrIPVersiontrueHdrSrcMask is an OctetString, of a size determined by the value of the HdrIPVersion property, representing a mask to be used in comparing the source address in the IP header with the value represented in the HdrSrcAddress property. If a value for this property is not provided, then the filter does not consider HdrSrcMask in selecting matching packets, i.e., the value of the HdrSrcAddress or the source address range must match the source address in the packet exactly. If a value for this property is provided, then HdrSrcAddressEndOfRange MUST NOT be provided.CIM_IPHeadersFilter.HdrIPVersiontrueHdrDestAddress is an OctetString, of a size determined by the value of the HdrIPVersion property, representing a destination IP address. When there is no HdrDestAddressEndOfRange value, this value is compared to the destination address in the IP header, subject to the mask represented in the HdrDestMask property. (Note that the mask is ANDed with the address.) When there is a HdrDestAddressEndOfRange value, this value is the start of the specified range (i.e., the HdrDestAddress is lower than the HdrDestAddressEndOfRange) that is compared to the source address in the IP header and matches on any value in the range. If a value for this property is not provided, then the filter does not consider HdrDestAddress in selecting matching packets, i.e., HdrDestAddress matches for all values.CIM_IPHeadersFilter.HdrIPVersiontrueHdrDestAddressEndOfRange is an OctetString, of a size determined by the value of the HdrIPVersion property, representing the end of a range of destination IP addresses (inclusive), where the start of the range is the HdrDestAddress property value. If a value for HdrDestAddress is not provided, then this property also MUST NOT be provided. If a value for this property is provided, then HdrDestMask MUST NOT be provided.CIM_IPHeadersFilter.HdrIPVersiontrueHdrDestMask is an OctetString, of a size determined by the value of the HdrIPVersion property, representing a mask to be used in comparing the destination address in the IP header with the value represented in the HdrDestAddress property. If a value for this property is not provided, then the filter does not consider HdrDestMask in selecting matching packets, i.e., the value of the HdrDestAddress or the destination address range must match the destination address in the packet exactly. If a value for this property is provided, then HdrDestAddressEndOfRange MUST NOT be provided.CIM_IPHeadersFilter.HdrIPVersionHdrProtocolID is an 8-bit unsigned integer, representing an IP protocol type. This value is compared to the Protocol field in the IP header. If a value for this property is not provided, then the filter does not consider HdrProtocolID in selecting matching packets, i.e., HdrProtocolID matches for all values.HdrSrcPortStart represents the lower end of a range of UDP or TCP source ports. The upper end of the range is represented by the HdrSrcPortEnd property. The value of HdrSrcPortStart MUST be no greater than the value of HdrSrcPortEnd. A source port filter is evaluated by testing whether the source port identified in the IP header falls within the range of values between HdrSrcPortStart and HdrSrcPortEnd, INCLUDING these two end points. If a value for this property is not provided, then the filter does not consider HdrSrcPortStart in selecting matching packets, i.e., there is no lower bound in matching source port values.HdrSrcPortEnd represents the upper end of a range of UDP or TCP source ports. The lower end of the range is represented by the HdrSrcPortStart property. The value of HdrSrcPortEnd MUST be no less than the value of HdrSrcPortStart. A single port is indicated by equal values for HdrSrcPortStart and HdrSrcPortEnd. A source port filter is evaluated by testing whether the source port identified in the IP header falls within the range of values between HdrSrcPortStart and HdrSrcPortEnd, INCLUDING these two end points. If a value for this property is not provided, then the filter does not consider HdrSrcPortEnd in selecting matching packets, i.e., there is no upper bound in matching source port values.HdrDestPortStart represents the lower end of a range of UDP or TCP destination ports. The upper end of the range is represented by the HdrDestPortEnd property. The value of HdrDestPortStart MUST be no greater than the value of HdrDestPortEnd. A single port is indicated by equal values for HdrDestPortStart and HdrDestPortEnd. A destination port filter is evaluated by testing whether the destination port identified in the IP header falls within the range of values between HdrDestPortStart and HdrDestPortEnd, INCLUDING these two end points. If a value for this property is not provided, then the filter does not consider HdrDestPortStart in selecting matching packets, i.e., there is no lower bound in matching destination port values.HdrDestPortEnd represents the upper end of a range of UDP or TCP destination ports. The lower end of the range is represented by the HdrDestPortStart property. The value of HdrDestPortEnd MUST be no less than the value of HdrDestPortStart. A single port is indicated by equal values for HdrDestPortStart and HdrDestPortEnd. A destination port filter is evaluated by testing whether the destination port identified in the IP header falls within the range of values between HdrDestPortStart and HdrDestPortEnd, INCLUDING these two end points. If a value for this property is not provided, then the filter does not consider HdrDestPortEnd in selecting matching packets, i.e., there is no upper bound in matching destination port values.63HdrDSCP is defined as a set of discrete DiffServ code points, with no inherent structure. There is no semantically significant relationship between different HdrDSCPs. Consequently, there is no provision for specifying a range of HdrDSCPs. Since, in IPv4, the HdrDSCP field may contain bits to be interpreted as the TOS IP Precedence, this property is also used to filter on IP Precedence. Similarly, the IPv6 Traffic Class field is also filtered using the value(s) in this property. HdrDSCP is defined as an array, to provide the ability to specify several discrete DSCPs in a single instance of IPHeadersFilter, that would be OR'ed together to define the filter criteria. If a value for this property is not provided, then the filter does not consider HdrDSCP in selecting matching packets, i.e., HdrDSCP matches for all values.trueThe 20-bit Flow Label field in the IPv6 header may be used by a source to label sequences of packets for which it requests special handling by the IPv6 devices, such as non-default quality of service or 'real-time' service. In the filter, this 20-bit string is encoded in a 24-bit octetstring by right-adjusting the value and padding on the left with b'0000'. If a value for this property is not provided, then the filter does not consider HdrFlowLabel in selecting matching packets, i.e., HdrFlowLabel matches for all values. 2.7.08021Filter allows 802.1.source and destination MAC addresses, as well as the 802.1 protocol ID, priority, and VLAN identifier fields, to be expressed in a single object to classify and identify traffic.trueThis property is an OctetString of size 6, representing a 48-bit source MAC address in canonical format. This value is compared to the SourceAddress field in the MAC header, subject to the mask represented in the 8021HdrSrcMACMask property. If a value for this property is not provided, then the filter does not consider 8021HdrSrcMACAddr in selecting matching packets, i.e., 8021HdrSrcMACAddr matches for all values.trueThis property is an OctetString of size 6, representing a 48-bit mask to be used in comparing the SourceAddress field in the MAC header with the value represented in the 8021HdrSrcMACAddr property. If a value for this property is not provided, then the filter does not consider 8021HdrSrcMACMask in selecting matching packets, i.e., the value of 8021HdrSrcMACAddr must match the source MAC address in the packet exactly.trueThis property is an OctetString of size 6, representing a 48-bit destination MAC address in canonical format. This value is compared to the DestinationAddress field in the MAC header, subject to the mask represented in the 8021HdrDestMACMask property. If a value for this property is not provided, then the filter does not consider 8021HdrDestMACAddr in selecting matching packets, i.e., 8021HdrDestMACAddr matches for all values.trueThis property is an OctetString of size 6, representing a 48-bit mask to be used in comparing the DestinationAddress field in the MAC header with the value represented in the 8021HdrDestMACAddr property. If a value for this property is not provided, then the filter does not consider 8021HdrDestMACMask in selecting matching packets, i.e., the value of 8021HdrDestMACAddr must match the destination MAC address in the packet exactly.This property is a 16-bit unsigned integer, representing an Ethernet protocol type. This value is compared to the Ethernet Type field in the 802.3 MAC header. If a value for this property is not provided, then the filter does not consider 8021HdrProtocolID in selecting matching packets, i.e., 8021HdrProtocolID matches for all values.07This property is an 8-bit unsigned integer, representing an 802.1Q priority. This value is compared to the Priority field in the 802.1Q header. Since the 802.1Q Priority field consists of 3 bits, the values for this property are limited to the range 0..7. If a value for this property is not provided, then the filter does not consider 8021HdrPriorityValue in selecting matching packets, i.e., 8021HdrPriorityValue matches for all values.04095This property is an 32-bit unsigned integer, representing an 802.1Q VLAN Identifier. This value is compared to the VLAN ID field in the 802.1Q header. Since the 802.1Q VLAN ID field consists of 12 bits, the values for this property are limited to the range 0..4095. If a value for this property is not provided, then the filter does not consider 8021HdrVLANID in selecting matching packets, i.e., 8021HdrVLANID matches for all values. 2.7.0PreambleFilter allows the classification of packets using traffic-conditioning results (where the results are determined by a PreambleMarkerService and stored in a 'packet preamble'). This permits information about the treatment that a packet receives on an ingress interface to be communicated along with the packet to the egress interface. An instance of PreambleFilter selects packets based on a two-part string (type and value pair) identifying a specific entry in the preamble. The logic for this match is 'at least one.' That is, a packet with multiple entries/results in its preamble matches a filter if at least one of these matches the filter.To foster interoperability, the basic format of the information captured by a PreambleMarker is specified. That information is contained in the FilterItemList property (an ordered, string array). Each entry in the array takes the form 'type,value'. When entries are added, they are appended to the end of the list. A limited set of standardized 'type's exist. They are: - ConformingFromMeter, NonConformingFromMeter and PartConformingFromMeter to convey metering results (where the 'value' is the name of the meter) - VlanId to describe the traffic's VLAN information (where the 'value' is the VLAN ID). An implementation is free to define and use other preamble 'types'. Note that a wildcard value of "any" is allowed to indicate that the preamble entry matches for any 'value' of the specified 'type'. For example, using the wildcard, an administrator can define a filter to select all packets that were found to be conforming ('type' = "ConformingFromMeter") without having to name each meter individually.Ordered 2.7.0A FilterList is used by network devices to identify routes by aggregating a set of FilterEntries into a unit, called a FilterList. FilterLists can also be used to accept or deny routing updates. A FilterList is weak to the network device (i.e., the ComputerSystem) that contains it. Hence, the ComputerSystem keys are propagated to this class.CIM_ComputerSystem.CreationClassNametrue256The scoping ComputerSystem's CreationClassName.CIM_ComputerSystem.Nametrue256The scoping ComputerSystem's Name.trueThe type of class that this instance is.Nametrue256This is the name of the FilterList.This defines whether the FilterList is used for input, output, or both input and output filtering. All values are used with respect to the interface for which the FilterList applies. "Not Applicable" (0) is used when there is no direction applicable to the FilterList. "Input" (1) is used when the FilterList applies to packets that are inbound on the related interface. "Output" (2) is used when the FilterList applies to packets that are outbound on the related interface. "Both" (3) is used to indicate that the direction is immaterial, e.g., to filter on a source subnet regardless of whether the flow is inbound or outbound. "Mirrored" (4) is also applicable to both inbound and outbound flow processing, but indicates that the filter criteria are applied asymmetrically to traffic in both directions and, thus, specifies the reversal of source and destination criteria (as opposed to the equality of these criteria as indicated by "Both"). The match conditions in the aggregated FilterEntryBase subclass instances are defined from the perspective of outbound flows and applied to inbound flows as well by reversing the source and destination criteria. So, for example, consider a FilterList with 3 FilterEntries indicating destination port = 80, and source and destination addresses of a and b, respectively. Then, for the outbound direction, the filter entries match as specified and the 'mirror' (for the inbound direction) matches on source port = 80 and source and destination addresses of b and a, respectively.01234Not ApplicableInputOutputBothMirrored 2.7.0CIM_HostedFilterEntryBaseAll filter entries (FilterEntryBase and its subclasses) are defined in the context of a ComputerSystem/network device, where they are used to identify and act on network traffic. Note that this class is deprecated since its subclassing is not correct. It subclasses from SystemComponent, but a FilterEntryBase is NOT a Component of a System. Instead, it is hosted/scoped by the System. In versions up to CIM 2.6, FilterEntryInSystem was a mandatory, Weak relationship. This is no longer true, beginning with CIM V2.7.truetrue1CIM_HostedFilterEntryBase.AntecedentThe ComputerSystem/network device that scopes the FilterEntryBase.GroupComponenttruetrueCIM_HostedFilterEntryBase.DependentThe FilterEntryBase on the System.PartComponenttrue 2.7.0CIM_HostedFilterListFilterLists are defined in the context of a ComputerSystem (e.g., a router, firewall or host). Note that this class is deprecated since its subclassing is not correct. It subclasses from SystemComponent, but a FilterList is NOT a Component of a System. Instead, it is hosted/scoped by the System. In versions up to CIM 2.6, FilterListInSystem was a mandatory, Weak relationship. This is no longer true, beginning with CIM V2.7.truetrue1CIM_HostedFilterList.AntecedentThe ComputerSystem/network device that scopes the FilterList and administers it.GroupComponenttruetrueCIM_HostedFilterList.DependentThe FilterList on the System.PartComponenttrue 2.7.0All filter entries (FilterEntryBase and its subclasses) are defined in the context of a ComputerSystem/network device, where the filter entries are used and administered.trueAntecedent11The ComputerSystem/network device that scopes the FilterEntryBase.trueDependenttrueThe FilterEntryBase on the System.true 2.7.0FilterLists are defined in the context of a ComputerSystem/network device, where the list is used and administered.trueAntecedent11The ComputerSystem/network device that scopes the FilterList.trueDependenttrueThe FilterList on the System.true 2.7.0This is a specialization of the CIM_Component aggregation which is used to define a set of filter entries (subclasses of FilterEntryBase) that are aggregated by a particular FilterList.truetrueGroupComponent1The FilterList, which aggregates the set of FilterEntries.truetruePartComponentAny subclass of FilterEntryBase which is a part of the FilterList.true0The order of the Entry relative to all others in the FilterList. The only permissible value is zero - indicating that all the Entries are ANDed together.0 true2.7.0CIM_ServiceThis is an abstract base class, derived from the Service class. It is deprecated in Version 2.7 with the recommendation that the Service class be subclassed instead. Distinguishing between services that modify traffic versus supporting basic communication has not proved useful.No valueThis is a free-form array of strings that provide descriptive words and phrases that can be used in queries. To-date, this property has not been implemented, since it is not standardized. Also, if this was a necessary query construct, then it would be required higher in the inheritance hierarchy. The latter has not proven necessary. Therefore, the property is deprecated.CIM_ServiceAccessURIThis is a URL that provides the protocol, network location, and other service-specific information required in order to access the service. It is deprecated with the recommendation that ServiceAccessURI be instantiated instead. This new class correctly positions the semantics of the service access, and clarifies the format of the information.No valueThis is a free-form array of strings that specify any specific pre-conditions that must be met in order for this service to start correctly. It was expected that subclasses would refine the inherited StartService() method to suit their specific needs. To-date, this refinement has not been necessary. Also, the property is not very useful, since it is not standardized. If this was a necessary construct, then it would be required higher in the inheritance hierarchy (on Service). The latter has not proven true. Therefore, the property is deprecated.No valueThis is a free-form array of strings that specify any specific parameters that must be supplied to the StartService() method in order for this service to start correctly. It was expected that subclasses would refine the inherited StartService() methods to suit their specific needs. To-date, this refinement has not been necessary. If indeed the method were refined, then its parameters would more formally convey this information. Therefore, the property is deprecated. 2.7.0CIM_DependencyThis association establishes the Dependency relationships that exist between an administrative domain and the NetworkServices that it hosts. It is deprecated since AdminDomains can contain any ManagedSystemElements. There is no special relationship needed for NetworkServices. In addition, the Min (1) cardinality on AdminDomain is not valid - since it may not be possible to define every NetworkService in the context of one or more Domains.trueAntecedentCIM_Dependency.AntecedentThe AdminDomain that hosts and administers the various network services.trueDependentCIM_Dependency.DependentThe network service that is hosted in the administrative domain.true true2.7.0No valueA LogicalNetworkService represents network services that either originate and/or terminate in a LogicalNetwork. This association is deprecated since LogicalNetworks aggregate ProtocolEndpoints, not their backing Services.trueNo valueThe LogicalNetwork that contains the network service.trueNo valueThe NetworkService that is running in the LogicalNetwork. No valueAn enumeration that explicitly defines this network service as originating, terminating, or residing in this LogicalNetwork. 0123UnknownOriginates InTerminates InResides In 2.7.0This class represents the functions used in forwarding network traffic. Its instances act on packets receivedfrom one or more ProtocolEndpoints or Services, and drop (discard), or send those packets to one or more other ProtocolEndpoints or Services. The explicit Endpoints being forwarded between, are described using the ForwardsAmong association (or one of its subclasses). Generally, the Endpoints are at the same protocol layer and are usually of similar types, or of the same type. ForwardingService is different than RouteCalculationService in that it represents the function of forwarding traffic independent of calculating routing information. Examining the ForwardingService class definition, note that its superclass NetworkService is deprecated. Therefore, NetworkService's properties need not be implemented in an instance of ForwardingService. Unfortunately, NetworkService cannot be removed from the object hierarchy without a major Schema release. When/if this occurs, the NetworkService superclass will be removed, and ForwardingService will subclass from CIM_Service directly. Also note that there are a large number of additional protocols that are not currently modeled. These will be added over time.This defines the type of protocol that is being forwarded.012345678910111213141516171819UnknownOtherIPv4IPv6IPv4/IPv6IPXAppleTalkDECnetSNACONPCLNPVINESXNSATMFrame RelayEthernetTokenRingFDDIInfinibandFibre ChannelCIM_ForwardingService.OtherProtocolType32This defines the type of protocol that is being forwarded when the value of the ProtocolType attribute is 1 (i.e., "Other"). This provides for future extensibility.CIM_ForwardingService.ProtocolType 2.6.0This association represents the dependency that exists between the ProtocolEndpoints that are used to forward data and the ForwardingService that is performing the forwarding of data.trueThe ProtocolEndpoints that are used to forward the data.AntecedenttrueThe service that is forwarding the data.Dependenttrue 2.7.1CIM_HostedServiceThis is a specialization of CIM_HostedService, which is an association between a Service and the System on which the functionality resides. The class, HostedForwardingServices, is deprecated since it provides no additional semantics over HostedService, and unecessarily restricts the Service to a single ComputerSystem, when the Service could reside in a Network or other higher level System.true11CIM_HostedService.AntecedentThe hosting router.AntecedenttrueCIM_HostedService.DependentThe Service hosted on the System.Dependenttruetrue true2.7.0This is an abstract base class, derived from Service, that represents the route calculation aspects of a system. This class also addresses functions performed by the system when it exchanges routing information. Examining the RouteCalculationService class definition, note that its superclass NetworkService is deprecated. Therefore, NetworkService's properties need not be implemented in an instance of RouteCalculationService. Unfortunately, NetworkService cannot be removed from the object hierarchy without a major Schema release. When/if this occurs, the NetworkService superclass will be removed, and RouteCalculationService will subclass from CIM_Service directly. Also note that there are a large number of additional routing protocols that are not currently modeled. These will be added over time.The RouterID uniquely identifies the router that is performing the route calculation. It is the highest IP address on the router (or the highest loopback interface, if there is one).This is an enumerated value that defines the routing algorithm used in this route calculation.012345678UnknownRIPv1RIPv2OSPFv1OSPFv2BGPv1BGPv2BGPv3BGPv4 2.7.0This is a specialization of the ServiceSAPDependency association, indicating that the referenced ProtocolEndpoint is utilized by the RouteCalculationService to provide its functionality.trueThe required ProtocolEndpoint.AntecedenttrueThe RouteCalculationService, which is dependent on the underlying ProtocolEndpoint.DependenttrueNo valueTRUE indicates that this ProtocolEndpoint represents a static route, and FALSE means that it represents a dynamically-learned route. This property is deprecated since a Service may use an Endpoint to output several routes, some static and others dynamic. 2.7.1CIM_HostedServiceThis is a specialization of CIM_HostedService, which is an association between a Service and the System on which the functionality resides. The class, HostedRoutingServices, is deprecated since it provides no additional semantics over HostedService, and unecessarily restricts the Service to a single ComputerSystem, when the Service could reside in a Network or other higher level System.true11CIM_HostedService.AntecedentThe hosting router.AntecedenttrueCIM_HostedService.DependentThe Service hosted on the System.Dependenttruetrue 2.7.0A Routing Protocol Domain is a collection of routers which coordinate their routing knowledge using a single [instance of a] routing protocol. This class represents the area/layer/level/zone like property of a routing protocol, such as an OSPF (area), IS-IS (layer) or PNNI (level). It does not represent the entire routing domain in every case. For example for OSPF, it represents an Area, but in the case of RIP, it represents the whole RIP domain. Any common attributes of these routing domains can be placed in this class in future versions of CIM. 2.7.0This assocation connects an AutonomousSystem to the routing domains that it contains.truetrue1The autonomous system.GroupComponenttruetrueThe routing domain.PartComponenttrue 2.7.0This class is used to implement routing policies. It aggregates a set of FilterLists, along with other appropriate constructs, into a unit. One of the most important uses of this class is to change the routing policy by changing values of various attributes in a consistent manner. A RoutingPolicy is weak to the network device (i.e., the ComputerSystem) that contains it. Hence, the ComputerSystem keys are propagated to this class. Note that this class was defined before the Policy Model and hence is not positioned in that hierarchy. The class will be repositioned in a later release of the Network Model.CIM_ComputerSystem.CreationClassNametrue256The scoping ComputerSystem's CreationClassName.CIM_ComputerSystem.Nametrue256The scoping ComputerSystem's Name.true256CreationClassName 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.Nametrue256This is the name of the Routing Policy.This defines the type of action that will be performed if the match conditions of the policy are met. The match conditions are defined by the associated ListsInRoutingPolicy. There are essentially three choices: forward the traffic unmodified, forward the traffic but modify either the attributes describing the route and/or other attributes that define how to condition the traffic (e.g., its ToS byte settings), or prevent the traffic from being forwarded.123456789Accept As IsAccept With Protocol Attribute ChangesAccept and Remark PacketAccept With Protocol Attribute Changes and RemarkAccept With Other ActionAccept With Protocol Attribute Changes and Other ActionAccept with Remark and Other ActionAccept with Protocol Attribute Changes, Remark and Other ActionDenyThis controls whether protocol-specific attributes replace, get prepended, or get appended to their existing values.123ReplacePrependAppendCIM_RoutingPolicy.BGPActionThis defines one or more BGP-specific attributes that should be used to modify this routing update.12345678910OriginAS_PathNEXT_HOPMulti_Exit_DiscLocal_PrefAtomic_AggregateAggregatorCommunityOriginator_IDCluster_ListCIM_RoutingPolicy.BGPValueThe value for the corresponding BGPAction.CIM_RoutingPolicy.BGPActionThis defines a remarking action for this traffic.1234567Change DSCPChange ToSChange 802.1Q ValueChange CIRChange CBRChange ABRChange VBRCIM_RoutingPolicy.RemarkValueThe value for the corresponding RemarkAction.CIM_RoutingPolicy.RemarkActionThis defines another action to be taken for this traffic.1234567OtherInput Flow PolicingOutput Flow PolicingInput Aggregate PolicingOutput Aggregate PolicingPolice By Marking DownPolice By Dropping DownCIM_RoutingPolicy.ConditioningValueCIM_RoutingPolicy.OtherConditioningActionIf the value of the ConditioningAction property of this class is 1, this contains an application-specific type of conditioning that is to be performed. Otherwise, if the ConditioningAction property is any other value, the value of this property should be NULL.CIM_RoutingPolicy.ConditioningActionThe value for the corresponding ConditioningAction, if appropriate.CIM_RoutingPolicy.ConditioningAction 2.6.0A RoutingPolicy is weak to the network device (i.e., the ComputerSystem) that contains it. This association formalizes that relationship.trueAntecedent11The network device/computer system that scopes the RoutingPolicy.trueDependenttrueThe routing policy defined in the context of the network device.true 2.6.0This is a specialization of the CIM_Component aggregation which is used to define a set of FilterLists that are aggregated by a particular RoutingPolicy.truetrueGroupComponentThe RoutingPolicy, which aggregates the set of FilterLists.truetruePartComponentA FilterList, which is part-of the RoutingPolicy.trueThe position of the FilterList relative to all other entries in the RoutingPolicy. 2.7.0NextHopRoute represents one of a series of 'hops' to reach a network destination. A route is administratively defined, or calculated/learned by a particular routing process. A ConcreteDependency associaton may be instantiated between a route and its routing service to indicate this. (In this scenario, the route is dependent on the service.)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 address which serves as the destination to be reached.The specific administrative distance of this route, overriding any default distances specified by the system or routing service.RouteMetric provides a numeric indication as to the preference of this route, compared to other routes that reach the same destination.TRUE indicates that this is a static route, and FALSE indicates a dynamically-learned route.An enumerated integer indicating whether the route is administrator-defined (value=2), computed (via a routing protocol/algorithm, value=3) or the actual route implemented in the network (value=4). The default is a computed route.234Administrator Defined RouteComputed RouteActual Route3 2.7.0HostedRoute describes the relationship between the route and the system in whose context it is defined.trueAntecedent11The network element that scopes/provides context for the route.trueDependentThe next hop route defined on the System.true 2.7.0NextHopIPRoute specifies routing in an IP network.An enumerated integer indicating how the route was derived. This is useful for display and query purposes.01234567891011UnknownOtherConnectedUser-DefinedIGRPEIGRPRIPHelloEGPBGPISISOSPFCIM_NextHopIPRoute.OtherDerivationA string describing how the route was derived when the RouteDerivation property is 1 ("Other").CIM_NextHopIPRoute.RouteDerivationThe mask for the Ipv4 destination address.The prefix length for the IPv6 destination address.An enumeration that describes the format of the address properties.012UnknownIPv4IPv6 2.7.0RouteUsesEndpoint depicts the relationship between a next hop route and the local Endpoint that is used to transmit the traffic to the 'next hop'.trueAntecedent1The endpoint used to reach the route's destination.trueDependentThe route using the endpoint.true 2.7.0AssociatedNextHop depicts the relationship between a route and the specification of its next hop. The next hop is external to a System, and hence is defined as a kind of RemoteServiceAccessPoint. Note that this relationship is independent of RouteUsesEndpoint (the local Endpoint used to transmit the traffic), and both may be defined for a route.trueAntecedent1The next hop for the route.trueDependentThe route sending traffic to the next hop.true trueCIM_NextHopRoute2.7.0NextHopRouting relates a destination address to the address or interface through which the remote address may be reached. An instance of this class can represent either static or dynamic routing, and may represent a routing table entry (but it is not required that all NextHopRoutes be in a routing table). Static routes are distinguished by setting the IsStatic boolean property to TRUE. Subclasses of NextHopRouting provide specific protocol and Key information. NextHopRoutes are dependent on at least one ForwardingService to execute them. This is conveyed by the CIM_NextHopForwardedByService association. NextHopRouting is deprecated in lieu of the more general, concrete NextHopRoute class. NextHopRoute allows the definition of BOTH a next hop address and an interface for transmission of the traffic. Also, it does not mandate the instantiation of a ForwardingService class. The latter is not needed if the sole purpose of the instance is to specify a 'desired/configured' route. This is simply a specification of the next hop.CIM_NextHopRoute.DestinationAddressThe address which serves as the destination to be reached.CIM_NextHopRoute.DestinationMaskThe mask for the DestinationAddress.CIM_AssociatedNextHop.AntecedentCIM_RouteUsesEndpoint.AntecedentThis contains either the address of the next-hop router, or the interface used to reach the destination.CIM_NextHopRoute.IsStaticTRUE indicates that this is a static route, and FALSE indicates a dynamically-learned route. true2.7.0CIM_NextHopIPRouteAn IPRoute relates a destination address to the address or interface through which the remote address may be reached. The destination address may be a specific IP endpoint or a subnet, dependent on the mask. An instance of this class represents either static or dynamic routing. Static routes are distinguished by setting the IsStatic boolean property to TRUE. Since many routes between endpoints can be defined (using different route calculation algorithms), the CIM_IPRoute class is defined as Abstract. This forces subclassing (for example, see CIM_BGPIPRoute) and allows the instances of its subclasses to be distinguished based on their CreationClassName key property. IPRoute is deprecated in lieu of the more general, concrete NextHopIPRoute class. NextHopIPRoute allows the definition of BOTH a next hop address and an interface for transmission of the traffic. Also, it does not mandate the instantiation of a ForwardingService class.No valueCIM_ForwardingService.SystemCreationClassNametrue256The scoping ForwardingService's SystemCreationClassName.No valueCIM_ForwardingService.SystemNametrue256The scoping ForwardingService's SystemName.No valueCIM_ForwardingService.CreationClassNametrue256The scoping ForwardingService's CreationClassName.No valueCIM_ForwardingService.Nametrue256The scoping ForwardingService's Name.No valuetrue256CreationClassName 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.trueCIM_NextHopIPRoute.DestinationAddressThe IP address which serves as the destination of the traffic, formatted according to the appropriate convention as defined in the AddressType property of this class. This property has the same semantics as DestinationAddress inherited from the NextHopRouting superclass, but a different property name. This is because this property and class were defined before NextHopRouting and are Key properties. They cannot be removed. ModelCorrespondence indicates that they should be set to equivalent values for consistency and ease of query.CIM_IPRoute.DestinationAddresstrueCIM_NextHopIPRoute.DestinationMaskThe mask for the destination IP address, formatted according to the appropriate convention as defined in the AddressType property of this class. This property has the same semantics as DestinationMask inherited from the NextHopRouting superclass, but a different property name. This is because this property and class were defined before NextHopRouting and are Key properties. They cannot be removed. ModelCorrespondence indicates that they should be set to equivalent values for consistency and ease of query.CIM_IPRoute.DestinationMasktrueCIM_NextHopIPRoute.AddressTypeAn enumeration that describes the format of the address property. Addresses that can be formatted in IPv4 format, must be formatted that way to ensure mixed IPv4/IPv6 support. AddressType is part of the key so that an IPv4 and an IPv6 route to IP subnets with the same network number but different IP versions (v4/v6) can coexist.012UnknownIPv4IPv6DestinationAddressCIM_IPRoute.IPDestinationAddressThe address which serves as the destination to be reached.DestinationMaskCIM_IPRoute.IPDestinationMaskThe mask for the DestinationAddress. No value2.7.0This assocation makes explicit the next hops that are forwarded by a specific ForwardingService, to reach the destination. Every ForwardingService can have its own unique set of routing destinations and next hops. The association is deprecated since it is incorrect to mandate the existence of a ForwardingService in order to define the existence of a route.trueNo valueAntecedent1The forwarding service for the route.trueNo valueDependentThe route being forwarded.trueCIM_NextHopRoute.AdminDistanceThis property contains the current administrative distance of this route, for the ForwardingService. Note that this property indicates current, specific values - whereas an instance of the CIM_AdministrativeDistance class defines default distances.CIM_NextHopRoute.RouteMetricPathMetric provides a numeric indication as to the preference of this route compared to other routes that reach the same destination. No value2.7.0This assocation makes explicit the IP routes that are defined in the context of a specific ForwardingService. Every ForwardingService can have its own unique set of IP routing destinations. The association is deprecated since it is incorrect to mandate the existence of a ForwardingService in order to define the existence of a route.trueNo value11The forwarding service for the route.AntecedenttrueNo valuetrueThe IP route being forwarded.Dependenttrue 2.7.0CIM_ConcreteDependencyCIM_NextHopIPRoute.RouteDerivationThis assocation makes explicit the routes that are calculated by a specific RouteCalculationService. Thus, every RouteCalculationService can have its own unique set of calculated routes. The association is not necessary in the model and has been deprecated. An instance of the general ConcreteDependency association can tie a NextHopIPRoute to a RouteCalculationService. In addition, information on how the route was derived is available in NextHopIPRoute's RouteDerivation enumeration.trueCIM_ConcreteDependency.AntecedentCIM_NextHopIPRoute.RouteDerivationAntecedent1The route's calculation service.trueCIM_ConcreteDependency.DependentDependentThe IP route calculated by a specific service.true 2.7.0Information in this class affects the choice of one protocol over another, when two protocols learn the same route. Properties define the preference of a protocol, called its distance. The lower the distance, the higher the preference for that protocol. This class affects ALL routes and contains the default distances. Specific administrative distances relative to an individual route and ForwardingService are defined in the NextHopForwardedByService association, its AdminDistance property. AdministrativeDistance, being a global object, is weak to the AdminDomain that contains it. Hence, the AdminDomain keys are propagated to this class.CIM_AdminDomain.CreationClassNametrue256The scoping AdminDomain's CreationClassName.CIM_AdminDomain.Nametrue256The scoping AdminDomain's Name.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.Nametrue256This is the name of the AdministrativeDistance class.The distance for directly connected peers. It has a default value of 0.0The distance for staticly connected peers. It has a default value of 1.1The distance for peers using EBGP. It has a default value of 20.20The distance for peers using internal EIGRP. It has a default value of 90.90The distance for peers using IGRP. It has a default value of 100.100The distance for peers using OSPF. It has a default value of 110.110The distance for peers using ISIS. It has a default value of 115.115The distance for peers using RIP. It has a default value of 120.120The distance for peers using EGP. It has a default value of 140.140The distance for peers using external EIGRP. It has a default value of 170.170The distance for peers using IBGP. It has a default value of 200.200The distance for peers using BGP locally. It has a default value of 200.200The distance for peers using an unknown protocol. It has a default value of 255.255 2.6.0AdministrativeDistance, being a global object, is weak to the AdminDomain that contains it. This association formalizes that relationship.trueAntecedent11The AdminDomain that scopes the AdministrativeDistance.trueDependenttrueThe table of (global) administrative distances that are defined in the context of the AdminDomain.true 2.7.0NetworkPipe is a subclass of EnabledLogicalElement, representing the state and management of a connection or trail between endpoints. This object is different than the association between the endpoints (CIM_ActiveConnection) since the emphasis is NOT on the endpoints but on the management of the pipe itself - its state, configuration, etc. NetworkPipes are defined in the context of a CIM_Network and represent the 'transfer of information . . . between . . . endpoints'. These concepts are aligned with the definition of the Pipe object in ITU's M.3100 specification.Recommendation.ITU|M3100.PipeRecommendation.ITU|M3100.TrailR1Recommendation.ITU|M3100.ConnectionR1Recommendation.ITU|M3100.SubNetworkConnectiontrueWithin the scope of the instantiating Namespace, InstanceID opaquely and uniquely identifies an instance of this class. In order to ensure uniqueness within the NameSpace, the value of InstanceID SHOULD be constructed using the following 'preferred' algorithm: <OrgID>:<LocalID> Where <OrgID> and <LocalID> are separated by a colon ':', and where <OrgID> MUST include a copyrighted, trademarked or otherwise unique name that is owned by the business entity creating/defining the InstanceID, or is a registered ID that is assigned to the business entity by a recognized global authority. (This is similar to the <Schema Name>_<Class Name> structure of Schema class names.) In addition, to ensure uniqueness <OrgID> MUST NOT contain a colon (':'). When using this algorithm, the first colon to appear in InstanceID MUST appear between <OrgID> and <LocalID>. (For DMTF defined instances, the 'preferred' algorithm MUST be used with the <OrgID> set to 'CIM'.) <LocalID> MUST include either a vendor specified unique identifier, or if mapping from an ITU M.3100 environment, the trailID, connectionID or subNetworkConnectionID of the instances of PipeR2.Recommendation.ITU|M3100.TrailR1.trailIdRecommendation.ITU|M3100.ConnectionR1.connectionIDRecommendation.ITU|M3100.SubNetworkConnection.subNetworkConnectionIDIndicates whether the pipe is bi-directional (value = 2), unidirectional (value = 3), or this information is not known (value = 0). For unidirectional pipes, the source and sink are indicated by a property (SourceOrSink) of the association, EndpointOfNetworkPipe.023UnknownBi-DirectionalUnidirectionalRecommendation.ITU|M3100.Pipe.directionality Indicates whether the pipe is composed of lower-level pipes, and if so, how these lower-level pipes are aggregated (in parallel or in sequence). The specific instances of NetworkPipe that are combined are described using the NetworkPipeComposition association. In the context of M.3100, the ability to be composed of lower-level pipes is modeled as a Trail. A Trail is made up of one or more Connections. (Note that both Trails and Connections are subclasses of Pipe). Because of the flexibility of the NetworkPipeComposition association, there is no need to subclass NetworkPipe, as was done in M.3100, but merely to instantiate the NetworkPipeComposition association to describe the bundling of the lower-level pipes (i.e., the connections), or the sequencing of them.0234UnknownNo Lower-Level CompositionCombined In ParallelCombined In SequenceEnabledStateRecommendation.ITU|M3100.Pipe.operationalStateEnabledState 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=8) 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.OtherEnabledStateRequestedStatetrueRecommendation.ITU|M3100.Pipe.administrativeStateRequestedState 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. 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.CIM_EnabledLogicalElement.EnabledState2345678910..3276732768..65535EnabledDisabledShut DownNo ChangeOfflineTestDeferredQuiesceDMTF ReservedVendor Reserved5 2.7.0HostedNetworkPipe is an association between a pipe and the network in whose context the pipe is defined. The cardinality of this association is 1-to-many. A network may host many pipes, and pipes are scoped/contained by only one network.trueAntecedent11The hosting network.trueDependentThe pipe in the network.true 2.7.0EndpointOfNetworkPipe describes the endpoints between which a pipe transfers information. Whether an endpoint is a source or sink is indicated by a property of the association, SourceOrSink.Recommendation.ITU|M3100.Pipe.a-TPInstanceRecommendation.ITU|M3100.Pipe.z-TPInstancetrueAntecedent22One of the endpoints of the pipe.trueDependentThe pipe which is dependent on the endpoints as the source or sink of the transferred information.trueIndicates whether the endpoint is a source (value = 2), or sink (value = 3) for the pipe. If this information is not applicable, the property is set to 4. If the information is not known, the property is set to 0.0234UnknownSourceSinkNot Applicable true2.7.0NetworkPipeComposition describes the makeup a pipe, based on lower-level ones. If the pipe is not composed of lower-level entities (i.e., its AggregationBehavior property is set to 2), then no instances of this association should be defined where the pipe has the role of GroupComponent. In the context of M.3100, this semantic is modeled as a Trail that is made up of one or more Connections. Both Trails and Connections are subclasses of M.3100's Pipe. Because of the flexibility of the NetworkPipeComposition association, there is no need to subclass NetworkPipe, as was done in M.3100, but merely to instantiate this association to describe the bundling of the lower-level pipes (connections), or the sequencing of them. How the lower-level pipes are aggregated is described by the property, AggregationBehavior, of NetworkPipe. If the pipes are combined in a sequence, the ordering is conveyed via the property, AggregationSequence, on this association.Recommendation.ITU|M3100.TrailR1.serverConnectionListPackageRecommendation.ITU|M3100.TrailR1.clientConnectionListPackagetruetrueGroupComponentThe higher level pipe that is composed of lower-level parts/pipes.truetruePartComponentA pipe which is a part of a higher-level one.trueIndicates the ordering of the PartComponent pipes in the GroupComponent. If the AggregationBehavior property of the GroupComponent pipe is set to 0 or 3 ("Unknown" or "Combined In Parallel"), then this property MUST be set to 0. If the AggregationBehavior is set to 4 ("Combined In Sequence"), then this property SHOULD indicate the ordering of the component pipes. Ordering starts with 1 and larger numbers indicate subsequent pipes. The numbering does not have to be in sequence. The word SHOULD is used in this Description, since the specific ordering of all the component pipes may not be known. In these cases, a value of 0 would be placed in AggregationSequence to indicate that ordering information is not available. 2.6.0This class represents the use of buffers by a QueuingService. The existence and management of individual buffers will be modeled in a future release. At the current level of abstraction, modeling the existence of the BufferPool is necessary. Long term, it is not sufficient. In implementations where there are multiple buffer sizes, an instance of BufferPool should be defined for each set of buffers with identical or similar sizes. These instances of buffer pools can then be grouped together using the CollectedBuffersPool association. Note that this class is derived from CollectionOfMSEs, and not from Forwarding or ConditioningService. BufferPool is only a collection of storage, and is NOT a Service.trueCollectionID256This property is defined in the CollectionOfMSEs class, but is overridden here to serve as part of the (composite) key that identifies the BufferPool instance.true256CreationClassName 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.256The Name property defines the label by which the object is known.This property is a 16-bit unsigned integer, and defines the number of bytes in each buffer.BytesThis property is a 32-bit unsigned integer, and defines the total number of buffers in the Pool.This property is a 32-bit unsigned integer, and defines the number of buffers in the Pool that are currently not allocated to any instance of a QueuingService. Buffers allocated to a QueuingService could either be in use (containing packet data), or allocated to a Queue pending the arrival of new packet data.This property is a 32-bit unsigned integer, and defines the number of buffers in the Pool that have been simultaneously allocated to multiple instances of QueuingService. 2.6.0CIM_CollectedBufferPool is an aggregation association representing that a Pool may itself be contained in a 'higher level' Pool.truetrueCollectionThe 'higher level' or parent Pool.truetrueMemberThe 'collected' Pool.true 2.7.0SNMPService represents an SNMP agent running on a hosting system. The UDP port to use to contact the agent is an instance of UDPProtocolEndpoint. The endpoint is associated with the SNMPService via a Dependency relationship. The community string(s) to use when contacting the SNMP agent reside in instances of SNMPCommunityString, that are associated with the SNMPService via the ServiceAccessBySAP relationship. 2.7.0SNMPCommunityString is an access point for an SNMPService. Each instance stores a community string that can be used for making SNMP requests.The SNMP community string/password used for read or read/write access to the agent's data.MIB.IETF|ENTITY-MIB.entLogicalCommunityAn enumerated integer describing whether read or read/write access is granted, or whether this information is unknown.UnknownRead OnlyRead/WriteThis array contains one or more object identifiers indicating the MIB modules/object subtrees that are accessed using the CommunityString. Either text strings of numbers (such as 1.2.3.4.5), or words (such as 'system') are specified. When using text strings of numbers, an asterisk (*) can replace any subidentifier to specify a subtree family - for example, 1.2.*.5. Descriptions related to each entry in the array are found at the corresponding index of the LogicalEntitiesDescriptions property.IndexedCIM_SNMPCommunityString.LogicalEntitiesDescriptionsMIB.IETF|ENTITY-MIB.entLogicalTypeFree-form textual descriptions of the logical entities indicated in the LogicalEntitiesAccessed array. There is a correspondence between the entity identifier in the LogicalEntitiesAccessed array, and the description in this array at the corresponding index.IndexedCIM_SNMPCommunityString.LogicalEntitiesAccessedMIB.IETF|ENTITY-MIB.entLogicalDescr 2.7.0SNMPTrapTarget contains information describing a remote system, to which Informs and Traps are sent. An SNMPService is related via a ServiceSAPDependency association to one or more instances of this class.AccessInfoThe host address.CIM_RemoteServiceAccessPoint.InfoFormatPortProtocolA UDP port to which the traps/informs are sent.12332768..65535OtherTCPUDPVendor SpecificCIM_RemotePort.OtherProtocolDescription3PortInfoThe UDP port number to which the traps/informs are sent. The default is port 162.CIM_RemotePort.PortProtocol162Allows the selection of the notification message - Traps or Informs. By default, Traps are selected.12TrapsInforms1The SNMP version used to send the traps or informs. Note that v1 does not support informs.123v1v2Cv3A community string/password to send with the trap operation. 2.7.0TrapSourceForSNMPService specifies the protocol endpoint/interface (and hence its IP address) from which traps originate.true1The endpoint that acts as the trap source.AntecedenttrueThe SNMP service that sends the notifications.Dependenttrue 2.7.0This class represents an OSPF area. The definition of an OSPF area from RFC2328, is 'OSPF allows sets of networks to be grouped together. Such a grouping is called an area. The topology of an area is hidden from the rest of the Autonomous System. This information hiding enables a significant reduction in routing traffic. Also, routing within the area is determined only by the area's own topology, lending the area protection from bad routing data.' This class has a 'Type' propery, which distinguishes between the different area types. This approach was chosen, because it provides a simpler way to indicate the type of an area, and additional subclassing is not needed at this time.The area ID of this OSPF area, see C.2 in RFC 2328.MIB.IETF|OSPF-MIB.ospfAreaIdtrueThe type of the OSPF area.234PlainStubNSSAWhen the number of non-default AS-external-LSAs in a router's link-state database reaches this limit, the router enters OverflowState, see 2.1 in RFC 1765.MIB.IETF|OSPF-MIB.ospfExtLsdbLimit 2.7.0This class is used to represent the basic operation of OSPF. It is derived from the RouteCalculationService, the superclass of all routing protocols.This attribute indicates whether this router is running MOSPF (multicast enhancements to OSPF) or not, see B.1 in RFC 1584. This attribute only can be true, when the SupportMOSPF property in OSPFService Capabilities is also true. If SupportMOSPF is false, then this property has no meaning.MIB.IETF|OSPF-MIB.ospfMulticastExtensionsCIM_OSPFServiceCapabillities.SupportMOSPFThis attribute indicates whether this router will forward multicast datagrams between OSPF areas or not, see B.1 in RFC 1584.MIB.IETF|OSPF-MIB.ospfMulticastExtensionsThis attribute indicates whether this router will forward multicast datagrams between Autonomous Systems or not, see B.1 in RFC 1584.MIB.IETF|OSPF-MIB.ospfMulticastExtensionsThe number of seconds that, after entering OverflowState, a router will attempt to leave OverflowState. When set to 0, the router will not leave OverflowState until restarted, see 2.1 in RFC 1765.MIB.IETF|OSPF-MIB.ospfExitOverflowIntervalSecondsControls the preference rules used in choosing among multiple AS-external-LSAs advertising the same destination. When set to TRUE, the preference rules remain those specified by RFC 1583. When set to FALSE, the preference rules are those stated in RFC 2328, which prevent routing loops when AS-external-LSAs for the same destination have been originated from different areas. See C.1 in RFC2328. 2.7.0The OSPFServiceCapabilities class represents the capabilities of an OSPF service.This attribute indicates whether this router supports NSSA ("not-so-stubby") areas or not, see RFC 1587.This attribute indicates whether this router supports on-demand circuits or not, see RFC 1793.MIB.IETF|OSPF-MIB.ospfDemandExtensionsThis attribute indicates whether this router supports MOSPF (multicast enhancements to OSPF) or not, see B.1 in RFC 1584.MIB.IETF|OSPF-MIB.ospfMulticastExtensions 2.7.0Each OSPF router has an association to one or more OSPF areas. Into these areas, a router advertises summaries filtered by specific address ranges. This would natively be modeled as a ternary association (router/OSPFService to OSPFArea to RangeOfIPAddresses), which is problematic in some implementations. To get around this issue, the OSPFAreaConfiguration class is defined to act as a focal point to bring together the router (indicated as a ComputerSystem with an instance of OSPFService, associated to the AreaConfiguration using OSPFServiceConfiguration), the area (indicated as an OSPFArea, associated to the AreaConfiguration using AreaOfConfiguration) and the address ranges for advertising (indicated as instances of RangeOfIPAddresses, associated to the AreaConfiguration using RangesOfConfiguration). There would be an instance of OSPFAreaConfiguration for each connected area of a router/OSPFService. When network administrators want to control the advertisements of OSPF routers by filters, they first define the relevant ranges. In order for a router to handle a range, an instance of RangeOfIPAddresses MUST be associated to the relevant OSPFAreaConfiguration (using the relationship, RangesOfConfiguration). The association between the range and area configuration contains a property defining the handling (EnableAdvertise) to allow or disallow advertisements in the range. Notes: - Because RangeOfIPAddresses is scoped by a System (via the HostedCollection association), an instance of RangeOfIPAddresses would be associated to an OSPFArea, satisfying this semantic. - This class is inherited from LogicalElement, because a suitable subclass 'lower' in the inheritance hiearchy does not exist.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>:<OSPFService ID><Area Configuration ID> where: <OrgID> and the remainder of the InstanceID 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 the <OSPFService ID>. For DMTF defined instances, the 'preferred' algorithm MUST be used, and the <OrgID> set to 'CIM'. <OSPFService ID> and <Area Configuration ID> MUST specify vendor-unique identifiers for the OSPFServiceand AreaConfiguration.This attribute contains the value of the default route that this router advertises into a stub area, see C.2 RFC 2328.MIB.IETF|OSPF-MIB.ospfStubMetricThis attribute contains the type of metric advertised as a default route into a stub area, see 3. in RFC 1850.MIB.IETF|OSPF-MIB.ospfStubMetricType234OSPF MetricComparable CostNonComparable 2.7.0This class is used to represent OSPF connectivity between two or more OSPF protocol endpoints.trueThe type of the OSPF link, see section 1.2 in RFC 2328.2345Point-To-PointPoint-To-MultipointBroadcastNBMAThe time, in seconds, between sending OSPF Hello-packets over the interface, see section C.3 in RFC 2328.MIB.IETF|OSPF-MIB.ospfIfHelloIntervalSecondsAfter ceasing to hear a router's Hello-packets, the number of seconds before its neighbors declare the router down, see section C.3 in RFC 2328.MIB.IETF|OSPF-MIB.ospfIfRtrDeadIntervalSecondstrueThis parameter indicates whether IP multicast datagrams should be forwarded over this OSPF link, and if so, how the forwarding should be done, see section B.2 in RFC 1584.MIB.IETF|OSPF-MIB.ospfIfMulticastForwarding234DisabledData-link MulticastData-link Unicast 2.7.0This association connects an area configuration to its area. The OSPFAreaConfiguration class is defined to act as a focal point to bring together the router (indicated as a ComputerSystem with an instance of OSPFService, associated to the AreaConfiguration using OSPFServiceConfiguration), the area (indicated as an OSPFArea, associated to the AreaConfiguration using AreaOfConfiguration) and the address ranges for advertising (indicated as instances of RangeOfIPAddresses, associated to the AreaConfiguration using RangesOfConfiguration). There is an instance of OSPFAreaConfiguration for each connected area of a router/OSPFService.trueAntecedent1The OSPF area.trueDependentThe configuration which is applied to an OSPF area. This is the Dependent reference in this association, since it depends on the area for any functional significance.true 2.7.0OSPFServiceConfiguration connects an OSPF service to its area configurations. The configurations are defined for the OSPFService, and so do not make sense as stand alone objects. This is the reason for the Min (1), Max (1) cardinalities on OSPFService. They mandate the instantiation of the service and of this association for the referenced instance of OSPFAreaConfiguration. The area configuration acts as a focal point to bring together the router (indicated as a ComputerSystem with an instance of OSPFService, associated to the AreaConfiguration using this relationship), the area (indicated as an OSPFArea, associated to the AreaConfiguration using AreaOfConfiguration) and the address ranges for advertising (indicated as instances of RangeOfIPAddresses, associated to the AreaConfiguration using RangesOfConfiguration). There would be an instance of OSPFAreaConfiguration for each connected area of a router/OSPFService.trueAntecedent11The OSPF service.trueDependentThe area configuration.true 2.7.0This association connects address ranges to the OSPF area configuration. When network administrators want to control the advertisements of OSPF routers by filters, they first define the relevant ranges. In order for a router to handle a range, an instance of RangeOfIPAddresses MUST be associated to the router's OSPFAreaConfiguration, using this relationship. The association between the range and area configuration contains a property (EnableAdvertise) defining the handling - to allow or disallow advertismenets in the range.trueAntecedentThe address range that is in the OSPF area configuration.trueDependentThe OSPF area configuration that contains the range.trueThe address range is advertised (TRUE) or not (FALSE), see C.2 in RFC 2328. 2.7.0This association connects an OSPFLink to the OSPFProtocolEndpoints that this link aggregates.truetrueCollection1The OSPF link.truetrueMemberThe OSPF protocol endpoint.true true2.7.0This relation connects an OSPF endpoint to an area.truetrueGroupComponent11The OSPF area.truetruePartComponentThe OSPF endpoint in the area.true 2.7.0This class is used to represent the basic operation of BGP. It is derived from RouteCalculationService, the superclass of all routing protocols.The BGPVersion property defines the version of BGP that this router is using. This is part of the BGP peer negotiation process).MIB.IETF|BGP4-MIB.bgpVersionBGP sends errors using a NOTIFICATION message. This message contains an error code, an error subcode, and error data. The error code defines the type of the notification. The 'Cease' error is for all fatal errors that are not one of the other five types of errors. For several of the errors, subcode information is also enumerated in other properties of this class.0123456NoneMessage Header ErrorOPEN Message ErrorUPDATE Message ErrorHold Timer ExpiredFinite State Machine ErrorCeaseThis defines the BGP error subcode for message header errors (LastErrorCode = 1). If LastErrorCode is any other value, then this property should be set to NULL.0123NoneConnection Not SynchronizedBad Message LengthBad Message TypeCIM_BGPService.ErrorCodeThis defines the BGP error subcode for OPEN message errors (LastErrorCode = 2). If LastErrorCode is any other value, then this property should be set to NULL.0123456NoneUnsupported Version NumberBad Peer ASBad BGP IdentifierUnsupported Optional ParameterAuthentication FailureUnacceptable Hold TimeCIM_BGPService.ErrorCodeThis defines the BGP error subcode for UPDATE message errors (LastErrorCode = 3). If LastErrorCode is any other value, then this property should be set to NULL.01234567891011NoneMalformed Attribute ListUnrecognized Well-Known AttributeMissing Well-Known AttributeAttribute Flags ErrorAttribute Length ErrorInvalid Origin AttributeAS Routing LoopInvalid NEXT_HOP AttributeOptional Attribute ErrorInvalid Network FieldMalformed AS_pathCIM_BGPService.ErrorCode 2.6.0This is a specialization of the Dependency association, and defines the relationship between a BGPService and the AdministrativeDistances that it uses to control the (BGP) routing decisions that it makes.trueAntecedent11The table of (global) administrative distances that are used by the BGPService.trueDependentThe BGPService object that makes BGP routing decisions.true 2.6.0The BGP speakers in an AS are required to be fully meshed. This can lead to a huge number of TCP connections per router. One way to reduce the peering requirements is to use a route reflector. This is based on specifying one or more routers to act as focal points for IBGP sessions. The route reflector as a whole is called a cluster. It is logically divided into three types of routers: reflectors, clients of the route reflector(s), and non-clients of the route reflector. There can be more than one route reflector in a cluster, and there can be more than one cluster in an AS.trueIf a cluster has more than one route reflector, all of the route reflectors in the cluster need to be configured with a 4-byte cluster ID. This allows route reflectors to recognize updates from other route reflectors in the same cluster. 2.6.0This aggregation establishes the routers (ComputerSystems) in a BGPCluster. At least three routers are required to form a cluster - a reflector and two clients. The routers that form a cluster share common configuration information.truetrue1The Cluster that aggregates the routers participating in it.Collectiontruetrue3The routers that form the Cluster.Membertrue truetruetrue2.7.0This aggregation establishes 'whole-part' relationships between an AutonomousSystem and the BGPClusters that it contains.truetrue1The AutonomousSystem that aggregates the Clusters belonging to it and administers them.trueThe Clusters that are contained in the AS. true2.7.0The BGP speakers in an AS are required to be fully meshed. This can lead to a huge number of TCP connections per router. One way to reduce the peering requirements is to use a confederation. A confederation effectively partitions one AS into a group of 'sub-ASs'. This enables all of the benefits of IBGP to be applied inside the confederation, while enabling EBGP to be run between each confederation. It also enables certain BGP attribute values to be preserved between confederations. However, to the outside world, the AS with its confederations appear to be a single AS.truetrue1The AutonomousSystem that contains the confederations.GroupComponenttruetrueThe Confederation within the AutonomousSystem.PartComponenttrueA unique identifier of the AutonomousSystem that contains the confederations.A unique identifier of the Confederation within the AutonomousSystem. 2.6.0BGPIPRoute describes a BGP routing entry that connects two peer routers that are running BGP. The source and destination addresses may be either specific IP endpoints or IP subnets. Examining the BGPIPRoute class definition, note that its superclass IPRoute is deprecated. Unfortunately, IPRoute cannot be removed from the object hierarchy without a major Schema release. When/if this occurs, the IPRoute superclass will be removed, and BGPIPRoute will subclass from CIM_NextHopRouting directly. Usually, the administrative distance is used to determine which route gets installed in the routing table. Using this scheme, routes learned via EBGP will win over routes learned via an IGP. If this is not desired, then this assigns the administrative distance of this route to be equal to that of a local route, which means that the same route learned by an IGP will have a lower administrative distance and be installed instead.Loopback interfaces are often used by IBGP peers, because they eliminate a dependency that would otherwise occur if the actual IP address of a physical interface was used to configure BGP. The loopback interface instead instructs the router to use any available interface. 2.6.0This association defines a BGP route, and makes explicit the dependency between a BGPIPRoute and a BGPProtocolEndpoint.trueAntecedent2The BGPProtocolEndpoints that represent the source and destination (or at least the next hop) of the BGP route.trueDependent1The routing table entry that represents a BGP route.true 2.6.0This is a specialization of ServiceServiceDependency, and captures the dependency that external gateway protocols (such as BGP) have on interior gateway protocols (such as OSPF).trueThe independent RouteCalculationService that provides routing information from the AS, for the EGP to use.AntecedenttrueThe dependent RouteCalculationService (e.g., the RouteCalculationService) that is functioning as an EGP.DependenttrueSometimes it is necessary to inject EGP information, such as that from BGP, into IGPs. This attribute defines whether this should be done for the two routing protocols that are defined by this association. The values below mean that no, partial, and full EGP information is injected into the IGP, respectively.123NonePartialFull 2.7.0A BGP Peer Group is a set of BGP neighbors that share the same update policies. This enables an administrator to assign policies to the peer group, instead of individually. This enables the routers in the Peer Group to optimize UPDATE messages. Consequently, Peer Groups have a set of restrictions that must be followed in order to work correctly with external BGP peers. Otherwise, loss of routing information could occur. A BGPPeerGroup is weak to the AutonomousSystem that contains it. Therefore, the keys from System must be propagated to it.CIM_AutonomousSystem.CreationClassNametrue256The scoping AutonomousSystem's CreationClassName.CIM_AutonomousSystem.Nametrue256The scoping AutonomousSystem's Name.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.256trueThis is the name of the BGP Peer Group.This defines the time interval, in seconds, for the ConnectRetry timer for the endpoints of the routers in the PeerGroup. The suggested value is 120 seconds.SecondsMIB.IETF|BGP4-MIB.bgpConnectRetryInterval120This defines the time interval in seconds for the HoldTimeConfigured property of the endpoints of the routers in the PeerGroup. This value must not be less than three seconds. The suggested value for this timer is 90 seconds.SecondsMIB.IETF|BGP4-MIB.bgpPeerHoldTimeConfigured90This defines the time interval in seconds for the KeepAliveConfigured timer for the endpoints of the routers in the PeerGroup. The suggested value for this property is 30 seconds. The maximum value of this property is 21845 seconds.SecondsMIB.IETF|BGP4-MIB.bgpPeerKeepAliveConfigured30This defines the time interval in seconds for the MinASOriginationInterval timer for the endpoints of the routers in the PeerGroup. The suggested value for this property is 15 seconds.SecondsMIB.IETF|BGP4-MIB.bgpPeerMinASOriginationInterval15This defines the time interval in seconds for the MinRouteAdvertisementInterval timer for the endpoints of the routers in the PeerGroup. The suggested value for this property is 30 seconds.SecondsMIB.IETF|BGP4-MIB.bgpPeerMinRouteAdvertisementInterval30 2.6.0A BGPPeerGroup is weak to the AutonomousSystem that contains it. This association formalizes that relationship.trueAntecedent11The AutonomousSystem that scopes the BGP peer group.trueDependenttrueThe BGP peer group defined in the context of the AutonomousSystem.true 2.6.0This aggregation defines the specific routers (i.e., ComputerSystems) that participate in a PeerGroup.truetrue1The PeerGroup that aggregates the routers.Collectiontruetrue2The routers that comprise the PeerGroup.Membertrue 2.7.0This defines the relationship between a BGPService and a specific BGPPeerGroup in which it is executing.trueAntecedentThe BGPPeerGroup in which the BGPService is executing.trueDependentThe BGPService that is executing in the BGPPeerGroup.true 2.6.0This association will serve as the base class for defining and distributing BGP routing information for the reflector of this Cluster.trueAntecedent1The Cluster for which this Service is being defined.trueDependent1The BGPService which distributes routing information in the Cluster.true 2.6.0This association will serve as the base class for handling BGP routing information for clients of the reflector of this Cluster.trueAntecedent1The Cluster for which this Service is being defined.trueDependent1The BGPService to handles routing information as a client in the Cluster.true 2.6.0This association will serve as the base class for handling BGP routing information for the non-clients of the reflector of this Cluster.trueAntecedent1The Cluster for which this Service is being defined.trueDependentThe BGPService which handles routing information as a non-client of the Cluster.true 2.6.0This is a specialization of the Dependency association, and defines the relationship between a BGPService and the RoutingPolicy that control it.trueAntecedentThe BGP routing policy object.trueDependentThe BGPService that operates according to the routing policy.true 2.7.0This class defines the BGP Attributes, that can be used to affect routing decisions. BGPAttributes are specific to a given AutonomousSystem that contains it. Hence, the keys of the AutonomousSystem are propagated to this class.CIM_AutonomousSystem.CreationClassNametrue256The scoping AutonomousSystem's CreationClassName.CIM_AutonomousSystem.Nametrue256The scoping AutonomousSystem's Name.trueThis defines the version of the BGP protocol.This defines the priority, or preference, of a route, in order to better compare it with other routes for the same destination. Higher values indicate a higher preference for a route.MIB.IETF|BGP4-MIB.bgp4PathAttrLocalPrefThis attribute is a sequences of the AS numbers through which routing information carried in this UPDATE message has passed. The components of this list can be AS_SETs or AS_SEQUENCEs.MIB.IETF|BGP4-MIB.bgp4PathAttrASPathThis is the set of all elements contained in all specific paths that are being summarized, so that those attributes will remain available to the routing decision process.This attribute defines the IP address of the border router that should be used as the next hop to the destinations listed in the UPDATE message.MIB.IETF|BGP4-MIB.bgp4PathAttrNextHopThis defines the next hop to be the IP address of the border IBGP neighbor.This is used on external (e.g., inter-AS) links to indicate which is the preferred entry point into an AS, when that AS has multiple entry points. Lower MED values have preference.MIB.IETF|BGP4-MIB.bgp4PathAttrMultiExitDiscThis defines a group of destinations that share a similar property. Communities are not restricted to a single AS, and can span multiple ASs. This attribute is used to simplify routing policies by basing policies on a logical value, as opposed to an IP address or an AS number.This property is set to TRUE if there are overlapping routes, and a less-specific route is selected instead of a more specific one (e.g., a system propagates an aggregate that causes loss of information). The value is set to FALSE if a less-specific route is NOT selected.MIB.IETF|BGP4-MIB.bgp4PathAttrAtomicAggregateThis specifies the AS and IP address of the router that has generated an aggregate.MIB.IETF|BGP4-MIB.bgp4PathAttrAggregatorASThis is generated by the AS that originates the routing information. There are three types of origins - IGP, EGP, and INCOMPLETE. These correspond to whether the information was learned internally in the AS, externally via an EGP, or by some other means.123IGPEGPINCOMPLETEMIB.IETF|BGP4-MIB.bgp4PathAttrOriginThis is the router ID for the ORIGIN attribute. 2.7.0The class BGPAttributes is weak to the AutonomousSystem that contains it. This association formalizes that relationship.trueAntecedent11The AutonomousSystem that scopes the BGP attributes.trueDependenttrueThe BGP attributes defined in the context of the AutonomousSystem.true 2.7.0This is a specialization of the Component aggregation, which is used to define the set of BGP Attributes that are used by a particular Routing Policy.truetrueGroupComponentThe RoutingPolicy, which aggregates a set of BGP attributes.truetruePartComponentA BGP attribute, which is part-of the RoutingPolicy.true 2.7.0A route map is used to control and modify routing information as well as to define when a route is redistributed between routing domains. Route maps are placed in router configuration files, and several instances of the same route map may be used to implement different actions. RouteMaps MAY use FilterLists to identify the route. A BGPRouteMap is specific to a given AutonomousSystem that contains it. Hence, the keys of the AutonomousSystem are propagated to this class.CIM_AutonomousSystem.CreationClassNametrue256The scoping AutonomousSystem's CreationClassName.CIM_AutonomousSystem.Nametrue256The scoping AutonomousSystem's Name.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.Nametrue256This is the name of the RouteMap class.This defines whether this RouteMap is used for input, output, or both input and output filtering.123InputOutputBothThis defines whether the action should be to forward or deny traffic meeting the match condition specified in this RouteMap.12PermitDenyThis specifies the criteria that must be matched in order for the corresponding MatchAction to take effect. The matching of the criteria may be specified by using a FilterList. For example, the command 'match ip address foo' uses the FilterList named 'foo' to do the matching of IP addresses.123456789OtherSource Address and MaskDestination Address and MaskSource PortSource Port RangeDestination PortDestination Port RangeProtocol TypeProtocol Type and OptionCIM_RouteMap.OtherMatchConditionTypeIf the value of the MatchConditionType property in this class is 1 (i.e., "Other"), then the specific type of filtering is specified in this property.CIM_RouteMap.MatchConditionTypeThis defines an additional action to take if the MatchCondition is satisfied. This definition is specifically limited to BGP filtering at this time. The actual value of the metric is specified in the SetMetricValue property.123456789OriginAS_PathNEXT_HOPMulti_Exit_DiscLocal_PrefAtomic_AggregateAggregatorCommunityOriginator_IDCIM_BGPRouteMap.SetMetricValueThis is the value of the metric that is being set for the BGP attribute defined in the SetMetricType property. 2.6.0A BGPRouteMap is weak to the AutonomousSystem that contains it. This association formalizes that relationship.trueAntecedent11The AutonomousSystem that scopes the BGPRouteMap.trueDependenttrueThe BGPRouteMap defined in the context of the AutonomousSystem.true 2.6.0This aggregation defines the BGPRouteMaps that are used by a particular RoutingPolicy object. Multiple instances of the same RouteMap may be used in the same RoutingPolicy instance. If this is desired, then the Sequence attribute of this aggregation can be used to disambiguate them.truetrueGroupComponentThe RoutingPolicy that aggregates the RouteMaps.truetruePartComponentThe RouteMaps that are used by the RoutingPolicy.trueThis defines the position of this RouteMap instance relative to all other instances of the same RouteMap. 2.6.0This association defines the RouteMaps that are aggregated and used by a particular BGPPeerGroup object. Multiple instances of the same RouteMap may be aggregated into the same BGPPeerGroup. If this is desired, then the MapSequence attribute of the association can be used to disambiguate them.truetrueThe BGPPeerGroup that aggregates the RouteMaps.CollectiontruetrueThe RouteMaps that are used by the BGPPeerGroup.MembertrueThis defines the position of this RouteMap instance relative to all other instances of the same RouteMap. 2.6.0RouteMaps do not have to use FilterLists, but if they do, this association defines which FilterList is used by a particular RouteMap.trueAntecedentThe FilterList used by a RouteMap.trueDependentThe RouteMap using the FilterList.true 2.7.0This class defines the per-path information used to process specific BGP attribute information, as defined in the bgp4PathAttrTable of RFC 1657.true512A comma-separated list of AS numbers, as would be stored in the value portion of the path segment in the PathAttrASPathSegment property. This list can be ordered or unordered.true32This is the address of the border router that should be used for the destination network.MIB.IETF|BGP4-MIB.bgp4PathAttrNextHoptrueThis property and its description are taken directly from RFC 1657. The property represents a sequence of AS path segments. Each AS path segment is represented by the tuple: <type, length, value> The type is a 1-octet field which has two possible values: 1 = AS_SET 2 = AS_SEQUENCE An AS_SET is an unordered set of ASs representing the path that an UPDATE message has traversed, and an AS_SEQUENCE is an ordered set of ASs representing the path that an UPDATE message has traversed. The length is a 1-octet field containing the number of ASs in the value field. The value field contains one or more AS numbers, each AS is represented in the octet string as a pair of octets according to the following algorithm: first-byte-of-pair = ASNumber / 256; second-byte-of-pair = ASNumber & 255; This property is mapped from the bgp4PathAttrASPathSegment MIB variable, which is an OctetString. Its length is defined as a minimum of 2 and a maximum of 255 octets.MIB.IETF|BGP4-MIB.bgp4PathAttrASPathSegmentThis is an enumeration that defines the ultimate origin of the path information. The value 'IGP' means that the origin is interior; the value 'EGP' means that it was learned via an EGP; the value 'INCOMPLETE' means that the origin is undetermined.123IGPEGPIncompleteMIB.IETF|BGP4-MIB.bgp4PathAttrOriginThis metric is used to discriminate between multiple adjacent autonomous systems. A value of -1 indicates the absence of this attribute. The range of this attribute is defined to be -1 to 2147483647.MIB.IETF|BGP4-MIB.bgp4PathAttrMultiExitDiscThis is the originating BGP4 speaker's degree of preference for an advertised route. A value of -1 indicates the absence of this attribute. The range of this attribute is defined to be -1 to 2147483647.MIB.IETF|BGP4-MIB.bgp4PathAttrLocalPrefThis is an enumeration that defines whether or not the local system has selected a less specific route without selecting a more specific route. There are two values, 1 and 2, indicating that a less specific route has not and has been selected, respectively. This is a 32-bit integer to correspond to the IETF MIB.012UnknownLess Specific Not SelectedLess Specific SelectedMIB.IETF|BGP4-MIB.bgp4PathAttrAtomicAggregateThis is the AS number of the last BGP speaker that performed route aggregation. A value of 0 indicates the absence of this attribute. The range of this attribute is defined to be 0 to 65535.MIB.IETF|BGP4-MIB.bgp4PathAttrAggregatorASThis is the IP address of the last BGP speaker that performed route aggregation. A value of 0.0.0.0 indicates the absence of this attribute.MIB.IETF|BGP4-MIB.bgp4PathAttrAggregatorAddrThis is the degree of preference calculated by the receiving BGP speaker for an advertised route. A value of -1 indicates the absence of this attribute. The range of this attribute is defined to be -1 to 2147483647.MIB.IETF|BGP4-MIB.bgp4PathAttrCalcLocalPrefThis is an indication of whether or not this route was chosen as the best BGP route. There are three possible values, 0 (Unknown), 1 (FALSE) and 2 (TRUE).012UnknownFalseTrueMIB.IETF|BGP4-MIB.bgp4PathAttrBesttrueThis contains one or more path atributes not understood by this BGP speaker. It is a array of path attributes that are not understood. The number of attributes is placed in a separate property of this class, PathAttrUnknownNumber.CIM_BGPPathAttributes.PathAttrUnknownNumberMIB.IETF|BGP4-MIB.bgp4PathAttrUnknownThe number of unknown attributes in the array, PathAttrUnknown.CIM_BGPPathAttributes.PathAttrUnknownMIB.IETF|BGP4-MIB.bgp4PathAttrUnknown 2.7.0This defines the attributes that are transmitted between BGP peers on a per-route basis.trueAntecedent1The BGPPathAttribute object that may be associated with a BGPIPRoute.trueDependent1The BGPIPRoute that may have an associated set of per-peer attributes.trueThis defines the IP address of the peer where the path information was learned.CIM_BGPPathAttributes.PathAttrIpAddrPrefixLenCIM_BGPPathAttributes.PathAttrIpAddrPrefixMIB.IETF|BGP4-MIB.bgp4PathAttrPeerThis defines the length in bits of the IP address prefix for the property, PathAttrPeer. The range is 0 to 32.CIM_BGPPathAttributes.PathAttrPeerMIB.IETF|BGP4-MIB.bgp4PathAttrIpAddrPrefixLenThe IP address prefix of the property, PathAttrPeer. Its length is specified by the property, PathAttrIpAddrPrefixLen.CIM_BGPPathAttributes.PathAttrPeerCIM_BGPPathAttributes.PathAttrIpAddrPrefixLenMIB.IETF|BGP4-MIB.bgp4PathAttrIpAddrPrefix No value2.7.0This is a specialization of the Component aggregation. This aggregation defines the set of BGPPathAttributes that are transmitted in per-path UPDATE messages. The association is deprecated since it is incorrectly defined as a Component relationship, and since the properties of BGPPathAttribute are path/endpoint-specific (not defined at the level of the Service).truetrueGroupComponent1No valueThe BGPService that aggregates BGPPathAttributes as part of its routing information.truetruePartComponent1No valueThe BGP attribute, which are part-of the BGP UPDATE message.true 2.7.0This class contains statistical information for a connection on a BGPProtocolEndpoint. It is defined as a subclass of StatisticalData and associated with the Endpoint using the relationship, ElementStatisticalData.trueThis is the number of BGP UPDATE messages received on this router's BGP connection. This is a 32-bit counter.MIB.IETF|BGP4-MIB.bgpPeerInUpdatestrueThis is the number of BGP UPDATE messages transmitted on this router's BGP connection. This is a 32-bit counter.MIB.IETF|BGP4-MIB.bgpPeerOutUpdatestrueThis is the total number of BGP messages received on this router's BGP connection. This is a 32-bit counter.MIB.IETF|BGP4-MIB.bgpPeerInTotalMessagestrueThis is the total number of BGP messages transmitted on this router's BGP connection. This is a 32-bit counter.MIB.IETF|BGP4-MIB.bgpPeerOutTotalMessagesThis contains the last error code and error subcode for this router's BGP connection. If no error has occurred, then each integer in the array is zero.MIB.IETF|BGP4-MIB.bgpPeerLastErrortrueThis contains the total number of times that the BGP Finite State Machine has transitioned into the established state for this router's BGP connection. This is a 32-bit counter.MIB.IETF|BGP4-MIB.bgpPeerFsmEstablishedTransitionstrueThis indicates how long, in seconds, this peer has been in the established state, or how long since this peer was last in the established state. It is set to zero when a new peer is configured or when the router is booted. This has the semantics of a 32-bit gauge.SecondsMIB.IETF|BGP4-MIB.bgpPeerFsmEstablishedTimetrueThis defines the time in seconds since the last BGP UPDATE message was received from the peer. This has the semantics of a 32-bit gauge.SecondsMIB.IETF|BGP4-MIB.bgpPeerInUpdateElapsedTime CIM_BGPEndpointStatistics2.7.0This class contains statistical information for a Service's sessions. It is deprecated since the statistics are defined in the BGP4 MIB at the level of individual peers/endpoints.CIM_BGPEndpointStatistics.InUpdatestrueThis is the number of BGP UPDATE messages received on this router's BGP connection. This is a 32-bit counter.MIB.IETF|BGP4-MIB.bgpPeerInUpdatesCIM_BGPEndpointStatistics.OutUpdatestrueThis is the number of BGP UPDATE messages transmitted on this router's BGP connection. This is a 32-bit counter.MIB.IETF|BGP4-MIB.bgpPeerOutUpdatesCIM_BGPEndpointStatistics.InTotalMessagestrueThis is the total number of BGP messages received on this router's BGP connection. This is a 32-bit counter.MIB.IETF|BGP4-MIB.bgpPeerInTotalMessagesCIM_BGPEndpointStatistics.OutTotalMessagestrueThis is the total number of BGP messages transmitted on this router's BGP connection. This is a 32-bit counter.MIB.IETF|BGP4-MIB.bgpPeerOutTotalMessagesCIM_BGPEndpointStatistics.LastErrorThis contains the last error code and error subcode for this router's BGP connection. If no error has occurred, then each integer in the array is zero.MIB.IETF|BGP4-MIB.bgpPeerLastErrorCIM_BGPEndpointStatistics.FsmEstablishedTransitionstrueThis contains the total number of times that the BGP Finite State Machine has transitioned into the established state for this router's BGP connection. This is a 32-bit counter.MIB.IETF|BGP4-MIB.bgpPeerFsmEstablishedTransitionsCIM_BGPEndpointStatistics.FsmEstablishedTimetrueThis indicates how long, in seconds, this peer has been in the established state, or how long since this peer was last in the established state. It is set to zero when a new peer is configured or when the router is booted. This has the semantics of a 32-bit gauge.SecondsMIB.IETF|BGP4-MIB.bgpPeerFsmEstablishedTimeCIM_BGPEndpointStatistics.InUpdateEstablishedTimetrueThis defines the time in seconds since the last BGP UPDATE message was received from the peer. This has the semantics of a 32-bit gauge.SecondsMIB.IETF|BGP4-MIB.bgpPeerInUpdateElapsedTime CIM_ElementStatisticalData2.7.0This association defines statistics collected for a BGP Service. The relationship is deprecated since the class BGPStatistics is deprecated. It is incorrectly associated with a BGPService, but should instead be associated with a BGPProtocolEndpoint using the ElementStatisticalData relationship.true1CIM_ElementStatisticalData.StatsThe statistics object for the BGP session.Statstruetrue11CIM_ElementStatisticalData.ManagedElementThe BGPService for which statistics are being gathered.Elementtrue 2.7.0Generic switch (bridging) service class. Additional switching functions are incorporated as subordinate services related to this class via ServiceComponent associations.32Address used by this SwitchService when it must be uniquely identified. For an ethernet bridge, the MAC Address serves as the BridgeAddress. When concatenated with a SpanningTreeService Priority, a unique bridge identifier results. The MAC address is formatted as twelve hexadecimal digits (e.g., "010203040506"), with each pair representing one of the six octets of the MAC address in "canonical" bit order according to RFC 2469.In other scenarios, like Ipv6, the address is formatted as "ffff:ffff:ffff:ffff".CIM_SwitchService.BridgeAddressTypeMIB.IETF|BRIDGE-MIB.dot1dBaseBridgeAddressThe number of switch ports controlled by this switching service.MIB.IETF|BRIDGE-MIB.dot1dBaseNumPortsIndicates what type of switching service can be performed.1234UnknownTransparent-onlySourceRoute-onlySRTMIB.IETF|BRIDGE-MIB.dot1dBaseTypeBridgeAddressType defines the type of addressing scheme used for this Bridge and its BridgeAddress property.12345OtherIPv4IPv6MACMAC + Spanning Tree PriorityCIM_SwitchingService.BridgeAddress 2.6.0A SwitchService switches frames between SwitchPorts. This association makes that relationship explicit.trueThe switch port.Antecedenttrue1The switching service.Dependenttrue CIM_EndpointIdentity2.7.0A switch port has a LANEndpoint that is exposed via this relationship. The associaiton is deprecated since a binding is not the correct relationship. The SwitchPort is simply another aspect of the LANEndpoint - which is indicated by the EndpointIdentity relationship.true1CIM_EndpointIdentity.SystemElementThe switch port.Antecedenttrue1CIM_EndpointIdentity.SameElementThe LAN endpoint.Dependenttrue 2.7.0This service class represents the learning/transparent bridging aspect of a SwitchService.The timeout period in seconds for aging out dynamically learned forwarding information. 802.1D-1990 recommends a default of 300 seconds.SecondsMIB.IETF|BRIDGE-MIB.dot1dTpAgingTime300Filtering Database Identifier used by VLAN-aware switches that have more than one filtering database. 2.6.0An association linking a SwitchService to a component TransparentBridgingService. The cardinality of the TransparentBridgingService is 0..1 for a VLAN-unaware switch.truetrue1The parent SwitchService.GroupComponenttruetrueThe component BridgingService.PartComponenttrue 2.7.0This service class represents the capability of a switch to participate in the distributed construction of a spanning tree.The version of the spanning tree protocol used by the switch.123UnknownDEC LB100IEEE 802dMIB.IETF|BRIDGE-MIB.dot1dStpProtocolSpecificationThe format of the priority bits are the first two octets of the 8-octet long Bridge ID. The other (last) 6 octets of the Bridge ID are given by the value of the Bridge Address. A priority that can be assigned to the switch for use in constructing the spanning tree. The unique identifier for a switch is constructed by concatenating the MAC address associated with the switch for spanning tree operations to the two-byte priority. Choice of the priority value influences election of the root bridge.MIB.IETF|BRIDGE-MIB.dot1dStpPriorityMAC address used by the spanning tree service when it must be uniquely identified. When concatenated with a SpanningTreeService Priority, a unique bridge identifier results. This property is defined for use of switches supporting multiple spanning tree services. Note that the MAC address is formatted as twelve hexadecimal digits (e.g., "010203040506"), with each pair representing one of the six octets of the MAC address in "canonical" bit order according to RFC 2469.16The complete Bridge ID (Priority + MAC Address) of the root bridge. The format of the priority bits are the first two octets of the 8-octet long Bridge ID. Note that the MAC address is formatted as twelve hexadecimal digits (e.g., "010203040506"), with each pair representing one of the six octets of the MAC address in "canonical" bit order according to RFC 2469.MIB.IETF|BRIDGE-MIB.dot1dStpDesignatedRootThe cost of the path from the switch to the root.MIB.IETF|BRIDGE-MIB.dot1dStpRootCostThe port number of the port having the lowest cost path to the root bridge.MIB.IETF|BRIDGE-MIB.dot1dStpRootPortThe current value for the maximum age of Spanning Tree information before discard, as learned from the network.Hundredths of SecondsMIB.IETF|BRIDGE-MIB.dot1dStpMaxAgeThe current value of the interval between transmission of bridge PDUs by the switch, on any port for which it is the spanning tree root or trying to become so, as learned from the network.Hundredths of SecondsMIB.IETF|BRIDGE-MIB.dot1dStpHelloTimeThe minimum interval between transmission of bridge PDUs through a given port, as learned from the network.Hundredths of SecondsMIB.IETF|BRIDGE-MIB.dot1dStpHoldTimeThe time spent by a port in the listening state before transitioning to the learning state, and in the learning state before transitioning to the forwarding state, as learned from the network. This value is also used during the period of a topology change as the maximum age of Spanning Tree information before discard.Hundredths of SecondsMIB.IETF|BRIDGE-MIB.dot1dStpForwardDelayThe MaxAge parameter to be used by all switches in the network if this switch becomes the root.Hundredths of SecondsMIB.IETF|BRIDGE-MIB.dot1dStpBridgeMaxAgeThe HelloTime parameter to be used by all switches in the network if this switch becomes the root.Hundredths of SecondsMIB.IETF|BRIDGE-MIB.dot1dStpBridgeHelloTimeThe ForwardDelay parameter to be used by all switches in the network if this switch becomes the root.Hundredths of SecondsMIB.IETF|BRIDGE-MIB.dot1dStpBridgeForwardDelay 2.6.0An association linking SwitchService to a component SpanningTreeService. The cardinality of the SpanningTreeService is 0..1 for a VLAN-unaware switch.truetrue1The parent SwitchService.GroupComponenttruetrueThe component SpanningTreeService.PartComponenttrue 2.7.0A switch participating in the spanning tree maintains spanning-tree specific information about each port whose forwarding is determined by the spanning tree. This association represents that information.trueThe SwitchPort.AntecedenttrueThe SpanningTreeService.DependenttrueThe priority assigned to the port. Contained in the first octet of the two-octet port ID; the other octet is the port number.MIB.IETF|BRIDGE-MIB.dot1dStpPortPriorityThe current state of the port as determined by the spanning tree protocol.123456DisabledBlockingListeningLearningForwardingBrokenMIB.IETF|BRIDGE-MIB.dot1dStpPortStateCIM_EnabledLogicalElement.EnabledStateThe enabled/disabled status of the port. This property is deprecated since the status of the port is available by inheritance from EnabledLogicalElement.12EnabledDisabledMIB.IETF|BRIDGE-MIB.dot1dStpPortEnableThe contribution of this port to the path cost of paths towards the spanning tree root which include this port.MIB.IETF|BRIDGE-MIB.dot1dStpPortPathCostThe bridge identifier of the root bridge for the segment to which the port is attached, as transmitted by the designated bridge for the segment.MIB.IETF|BRIDGE-MIB.dot1dStpPortDesignatedRootThe cost of the path to the root offered by the designated bridge for the segment.MIB.IETF|BRIDGE-MIB.dot1dStpPortDesignatedCostThe bridge identifier of the designated bridge for the segment to which the port is attached.MIB.IETF|BRIDGE-MIB.dot1dStpPortDesignatedBridgeThe port identifier of the port on the designated bridge serving the segment to which the port is attached.MIB.IETF|BRIDGE-MIB.dot1dStpPortDesignatedPort 2.7.0A DynamicForwardingEntry represents an entry in the forwarding (filtering) database associated with the TransparentBridgingService. The entry is Weak to the Service as specified by TransparentBridgingDynamicForwarding.CIM_System.CreationClassNametrue256The scoping System's CreationClassName.CIM_System.Nametrue256The scoping System's Name.CIM_Service.CreationClassNametrue256The scoping Service's CreationClassName.CIM_Service.Nametrue256The scoping Service's Name.true256CreationClassName 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.true12Unicast MAC address for which the TransparentBridging Service has forwarding and/or filtering information. Note that the MAC address is formatted as twelve hexadecimal digits (e.g., "010203040506"), with each pair representing one of the six octets of the MAC address in "canonical" bit order according to RFC 2469.MIB.IETF|BRIDGE-MIB.dot1dTpFdbAddressThe status of the entry.12345OtherInvalidLearnedSelfMgmtMIB.IETF|BRIDGE-MIB.dot1dTpFdbStatus 2.6.0This association links an instance of the TransparentBridgingService to the entries of its forwarding database. The forwarding database is weak to the Service.trueAntecedent11The transparent bridging service.trueDependenttrueDynamic Forwarding Entry of forwarding database.true 2.7.0This association links a DynamicForwardingEntry and the SwitchPort to which the entry applies.trueAntecedent1The SwitchPort.trueDependentDynamicForwardingEntry of the forwarding database.true 2.7.0A StaticForwardingEntry represents an entry in the static (destination-address filtering) database associated with the TransparentBridgingService. The entry is Weak to the Service as specified by TransparentBridgingStaticForwarding.CIM_System.CreationClassNametrue256The scoping System's CreationClassName.CIM_System.Nametrue256The scoping System's Name.CIM_Service.CreationClassNametrue256The scoping Service's CreationClassName.CIM_Service.Nametrue256The scoping Service's Name.true256CreationClassName 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.true12Destination MAC address (unicast, multicast or broadcast) to which the filtering information applies. Note that the MAC address is formatted as twelve hexadecimal digits (e.g., "010203040506"), with each pair representing one of the six octets of the MAC address in "canonical" bit order according to RFC 2469.MIB.IETF|BRIDGE-MIB.dot1dStaticAddressThe status of the entry.12345OtherInvalidPermanentDeleteOnResetDeleteOnTimeoutMIB.IETF|BRIDGE-MIB.dot1dStaticStatusThe ports to which frames with the destination MAC address arriving on the port represented by the SwitchPortStaticForwarding association are allowed to be forwarded. 2.6.0This association links an instance of the TransparentBridgingService to the entries of its static (destination-address filtering) database.trueAntecedent11The TransparentBridgingService.trueDependenttrueStaticForwardingEntry of the forwarding database.true 2.6.0This association links a static database entry and the SwitchPort to which the entry applies.trueAntecedent1The SwitchPort.trueDependentStaticForwardingEntry of static database.true 2.7.0SourceRoutingService represents the capability of a switch to participate in the source routing of frames received at its ports. It is a system-level Service that provides and supports local switching only. The SourceRoutingService is aggregated into a higher level SwitchService through the SwitchServiceSourceRouting association.Indicates whether the bridge operates using older 3 bit length negotiation fields or the newer 6 bit length field in its RIF.12Mode3Mode6MIB.IETF|SOURCE-ROUTING-MIB.dot1dSrBridgeLfMode 2.6.0An association linking SwitchService to a component SourceRoutingService. The cardinality of the SourceRoutingService is 0..1 for a VLAN-unaware switch.truetrue1The parent SwitchService.GroupComponenttruetrueThe component SourceRoutingService.PartComponenttrue 2.7.0This association represents information regarding port pairings that is used by the SourceRoutingService of a switch.trueThe lower numbered port.AntecedenttrueThe higher numbered port.DependenttrueA bridge number that uniquely identifies the path provided by this source routing bridge between the segments connected to high and low ports. The purpose of bridge number is to disambiguate between multiple paths connecting the same two LANs.MIB.IETF|SOURCE-ROUTING-MIB.dot1dPortPairBridgeNumThe state of the pairing. Writing 'invalid(3)' to this property removes the association instance.123EnabledDisabledInvalidMIB.IETF|SOURCE-ROUTING-MIB.dot1dPortPairBridgeState 2.7.0A switch capable of source routing maintains source-routing specific information about each port. This association represents that information.trueThe SwitchPort.Antecedenttrue1The SourceRoutingService.DependenttrueThe maximum number of routing descriptors allowed in an All Paths or Spanning Tree Explorer frames.MIB.IETF|SOURCE-ROUTING-MIB.dot1dSrPortHopCountThe segment number that uniquely identifies the segment to which this port is connected. Current source routing protocols limit this value to the range: 0 through 4095. (The value 0 is used by some management applications for special test cases.) A value of 65535 signifies that no segment number is assigned to this port.MIB.IETF|SOURCE-ROUTING-MIB.dot1dSrPortLocalSegmentA bridge number uniquely identifies a bridge when more than one bridge is used to span the same two segments. Current source routing protocols limit this value to the range: 0 through 15. A value of 65535 signifies that no bridge number is assigned to this bridge.MIB.IETF|SOURCE-ROUTING-MIB.dot1dSrPortBridgeNumThe segment number that corresponds to the target segment to which this port is considered connected. Current source routing protocols limit this value to the range: 0 through 4095. (The value 0 is used by some management applications for special test cases.) A value of 65535 signifies that no target segment is assigned to this port.MIB.IETF|SOURCE-ROUTING-MIB.dot1dSrPortTargetSegmentDetermines how the port behaves when presented with a Spanning Tree Explorer frame. The value 'disabled(2)' indicates that the port will not accept or send Spanning Tree Explorer packets; any STE packets received will be silently discarded. The value 'forced(3)' indicates the port will always accept and propagate Spanning Tree Explorer frames. (This allows a manually configured Spanning Tree for this class of packet to be configured.) Note that unlike transparent bridging, it is not catastrophic to the network if there are loops. The value 'auto-span(1)' can only be returned by a bridge that both implements the Spanning Tree Protocol and has use of the protocol enabled on this port. The behavior of the port for Spanning Tree Explorer frames is determined by the value of the State property of the SwitchPortSpanningTree association for the port. If the port is in the 'forwarding' state, the frame will be accepted or propagated. Otherwise, it will be silently discarded.123Auto-SpanDisabledForcedCIM_SwitchPortSpanningTree.StateMIB.IETF|SOURCE-ROUTING-MIB.dot1dSrPortSTESpanMod 2.7.0This association identifies the spanning tree in which a forwarding database (TransparentBridgingService) is nested.trueThe TransparentBridgingService that supports a SpanningTreeService.Antecedenttrue1The SpanningTree in which a TransparentBridgingService is nested.Dependenttrue 2.7.0Statistical information regarding the TransparentBridgingService.trueThe total number of Forwarding Database entries, which have been or would have been learnt, but have been discarded due to a lack of space to store them in the Forwarding Database.MIB.IETF|BRIDGE-MIB.dot1dTpLearnedEntryDiscards 2.7.0Statistical information regarding the SpanningTreeService.The time since the last topology change was detected by the switch.Hundredths of SecondsMIB.IETF|BRIDGE-MIB.dot1dStpTimeSinceTopologyChangetrueThe total number of topology changes detected by the switch since the counter was last reset or initialized.MIB.IETF|BRIDGE-MIB.dot1dStpTopChanges 2.7.0Statistical information regarding a generic SwitchPort, independent of the specific kind of switching done on frames arriving at the port.trueThe number of frames discarded by this port due to excessive transit delay through the bridge.MIB.IETF|BRIDGE-MIB.dot1dBasePortDelayExceededDiscardstrueThe number of frames discarded by this port due to an excessive size.MIB.IETF|BRIDGE-MIB.dot1dBasePortMtuExceededDiscards 2.7.0Statistical information regarding a SwitchPort, at which transparent bridging is performed.trueThe number of frames that have been received by the port from its segment. Note that a frame is only counted if and only if it is for a protocol being processed by the local bridging function, including bridge management frames.MIB.IETF|BRIDGE-MIB.dot1dTpPortInFramestrueThe number of frames that have been transmitted by the port to its segment. Note that a frame is only counted if and only if it is for a protocol being processed by the local bridging function, including bridge management frames.MIB.IETF|BRIDGE-MIB.dot1dTpPortOutFramestrueCount of valid frames received which were discarded (i.e., filtered) by the forwarding process.MIB.IETF|BRIDGE-MIB.dot1dTpPortInDiscards 2.7.0Statistical information regarding a SwitchPort participating in the spanning tree.trueThe number of times the port has transitioned from the Learning state to the Forwarding state.MIB.IETF|BRIDGE-MIB.dot1dStpPortForwardTransitions 2.7.0Statistical information regarding a SwitchPort supporting source routing.trueThe number of Specifically Routed frames, also referred to as Source Routed Frames, that have been received from the segment attached to the port.MIB.IETF|SOURCE-ROUTING-MIB.dot1dSrPortSpecInFramestrueThe number of Specifically Routed frames, also referred to as Source Routed Frames, that the port has transmitted on its segment.MIB.IETF|SOURCE-ROUTING-MIB.dot1dSrPortSpecOutFramestrueThe number of All Paths Explorer frames, also referred to as All Routes Explorer frames, that have been received by the port from its segment.MIB.IETF|SOURCE-ROUTING-MIB.dot1dSrPortApeInFramestrueThe number of all Paths Explorer Frames, also referred to as All Routes Explorer frames, that have been transmitted by the port on its segment.MIB.IETF|SOURCE-ROUTING-MIB.dot1dSrPortApeOutFramestrueThe number of spanning tree explorer frames that have been received by the port from its segment.MIB.IETF|SOURCE-ROUTING-MIB.dot1dSrPortSteInFramestrueThe number of spanning tree explorer frames that have been transmitted by the port on its segment.MIB.IETF|SOURCE-ROUTING-MIB.dot1dSrPortSteOutFramestrueThe number of explorer frames that have been discarded by the port because the routing descriptor field contained an invalid adjacent segment value.MIB.IETF|SOURCE-ROUTING-MIB.dot1dSrPortSegmentMismatchDiscardstrueThe number of frames that have been discarded by the port because the routing descriptor field contained a duplicate segment identifier.MIB.IETF|SOURCE-ROUTING-MIB.dot1dSrPortDuplicateSegmentDiscardstrueThe number of explorer frames that have been discarded by the port because the Routing Information Field has exceeded the maximum route descriptor length.MIB.IETF|SOURCE-ROUTING-MIB.dot1dSrPortHopCountExceedsDiscardstrueThe number of duplicate LAN IDs or Tree errors. This helps in detection of problems in networks containing older Source Routing Bridges.MIB.IETF|SOURCE-ROUTING-MIB.dot1dSrPortDupLanIdOrTreeErrorstrueThe number of ARE and STE frames that were discarded because the last LAN ID in the routing information field did not equal the LAN-in ID. This error can occur in implementations which do only a LAN-in ID and Bridge Number check instead of a LAN-in ID, Bridge Number, and LAN-out ID check before they forward broadcast frames.MIB.IETF|SOURCE-ROUTING-MIB.dot1dSrPortLanIdMismatches 2.6.0An instance of VLAN represents a VLAN within a switch. In a particular switch, there should be an instance of VLAN for every VLAN available. For example, in a switch with port-based VLANs, if there are 16 VLANs to which ports can be assigned (VLAN 1 through VLAN 16), there should be an instance of CIM_VLAN for each of VLAN 1 through VLAN 16. VLAN inherits Name from ServiceAccessPoint. Use this for the textual name of the VLAN, if there is one. Otherwise, synthesize a textual name, e.g., VLAN 0003. (Consider leading zero fill, as shown, to ensure that if the textual VLAN names are extracted and presented by a management applictions, the VLAN names will sort in the expected order.) The numeric part of the name should be at least four digits wide since 802.1Q specifies 4095 VLANs. It is intended that VLAN be subclassed only if necessary to add attributes. The type of the VLAN can be inferred from the VLANService(s) with which the VLAN is associated in the VLANFor association. An instance of VLAN may be associated with more than one VLANService. For example, there are switches that support both 802.1Q VLANs and the vendor's proprietary VLANs. In some such switches, if a broadcast packet is received on a port in an 802.1Q VLAN (VLAN 5, for example), it may be be transmitted from a port in a 'proprietary' VLAN 5. In effect, there is only one VLAN 5, and the type of port only determines the packet format for tagged packets. In the case just described, only one instance of CIM_VLAN should be instantiated for VLAN 5, and it should be associated both with the 802.1Q VLANService and the proprietary VLANService. In typical VLAN-aware switches, packets can be assigned to a VLAN based on the port on which they are received (port-based VLANS), based on the source MAC address (MAC-based VLANs), or based on the value of a set of bits in the packet (protocol-based VLANs). If it is desirable to represent the VLAN assignment predicate for some MAC-based VLAN switch, it will be necessary to subclass VLAN. The list of MAC addresses associated with a VLAN might be an attribute of the subclass. If it is desirable to representthe VLAN assignment predicate in a protocol-based VLAN switch, it will also be necessary to subclass VLAN, InboundVLAN, or both. If the predicate applies to all ports in the switch, then only VLAN need be used/instantiated. If the predicate may vary based on the port, then InboundVLAN must be subclassed, and CIM_VLAN might have to be subclassed as well.VLAN identifying number. 2.6.0This association makes explicit the operational dependencies of a SwitchPort when operating in a VLAN. If there is an association between a particular SwitchPort and a particular VLAN, then there is the possibility that a packet received by the port will be assigned to the VLAN (or if the packet already has a VLAN tag, that the packet will not be dropped). If there is no such association, then there is NO possibility that a packet received by the port will progress through the switch having been assigned to the referenced VLAN.trueThe VLAN to which the SwitchPort is assigned.AntecedenttrueThe SwitchPort on the VLAN.DependenttrueIf TRUE, packets already tagged with this VLAN number will be accepted when arriving at this port. For example, if there is an InboundVLAN association between port 12 and VLAN 7 for which Tagged is true, then when a packet tagged with VLAN 7 arrives at port 12, the packet will be accepted into the switch for further processing. If there is no such association, then the packet will be dropped. If FALSE, it means that any untagged packets arriving at this port MIGHT be classified into the associated VLAN. If, for a particular SwitchPort, there is only one instance of the association for which Tagged is FALSE, then all incoming untagged packets will be classified into that VLAN. This is the typical configuration of a non-trunk port in a switch implementing port-based VLANs. If there is more than one such association instance, then the packet MIGHT be classified into any one of them, based on some criterion other than the identity of the switch port. For example, in a MAC-based VLAN switch, the decision would be based on the source MAC address. In a protocol-based VLAN switch, the decision would be based on the values of some set of bits in the packet. Note that the MAC address is formatted as twelve hexadecimal digits (e.g., "010203040506"), with each pair representing one of the six octets of the MAC address in "canonical" bit order according to RFC 2469.Default should be TRUE if untagged packets received by the SwitchPort are assigned to the VLAN. For 802.1Q-compliant ports, the Default property should be TRUE on the association instance connecting a SwitchPort to the VLAN corresponding to the port's PVID. Default MUST never be TRUE if Tagged is true -- it applies only to untagged packets. 2.6.0This association makes explicit the operational dependencies of a SwitchPort when operating in a VLAN. If there is no instance of OutboundVLAN between a given SwitchPort and VLAN, then any packet that has been assigned to the VLAN and whose destination address is associated with the port will be dropped by the switch without being transmitted. Otherwise, the packet will be transmitted.trueThe VLAN to which the SwitchPort is assigned.AntecedenttrueThe SwitchPort on the VLAN.DependenttrueIf Tagged is TRUE, then the packet will be transmitted in encapsulated form, tagged with the associated VLAN tag. If Tagged is FALSE, the packet will be trasmitted without any VLAN tag. true2.6.0VLANService represents the VLAN aspects of the function performed by a switch. Some VLAN-aware devices participate in protocols where VLAN information is propagated among switches, e.g., GVRP in 802.1Q switches and VTP in Cisco Catalyst switches. VLANService also represents the function performed by the switch as a participant in such a protocol. VLANService must be subclassed so that the type of instance can be distinguished by its class. 2.6.0If a switch supports 802.1Q, an instance of this class should be instantiated in the switch. If the switch supports GVRP, this class represents the function that the switch performs with respect to GVRP. 2.6.0The VLAN for the VLAN Service.trueThe VLAN for the VLANService.Antecedenttrue1The VLANService which uses the VLAN for processing.Dependenttrue 2.6.0An association linking SwitchService to a component VLANService.truetrue11The SwitchService containing the VLANService.GroupComponenttruetrueThe VLANService that is a component of the SwitchService.PartComponenttrue 2.6.0The association between a VLAN and the forwarding database (some use the term filtering database) used to determine which port a packet should be transmitted on, given that it is assigned to the VLAN and that it has a particular destination MAC address. The TransparentBridgingService represents a forwarding database.trueThe VLAN.AntecedenttrueThe BridgingService that determines the port, given the the VLAN and addressing information.Dependenttrue 2.7.0This is a concrete class that represents the ability to conceptualize a QoS service as a set of coordinated sub-services. This enables the network administrator to map business rules to the network, and the network designer to engineer the network such that it can provide different functions for different traffic streams. This class has two main purposes. First, it serves as a common base class for defining various sub-services that are needed to build higher-level QoS services. Second, it serves as a way to consolidate relationships between different types of QoS services and different types of ConditioningServices. For example, Gold Service may be defined as a QoSService which aggregates two other QoSServices together. Each of these 'other' QoSServices could be DiffServServices - one representing the servicing of very high demand packets (instantiated as a DiffServService directly), and one representing the service given to most of the packets (instantiated as an AFService). The high demand DiffServService instance would use QoSConditioningSubService to aggregate together the necessary classifiers to indicate which traffic it applies to, the appropriate meters for contract limits, the marker to mark the EF PHB in the packets, and the queuing-related services. The AFService instance would similarly use QoSConditioningSubService to aggregate its classifiers, meters, the several markers used to mark the different AF PHBs in the packets, and the queuing-related services needed to deliver the packet treatment. true2.7.0The associations - QoSSubService and QoSConditioningSubService - operate in conjunction. High level QoS definitions, such as 'John gets Gold Service', map to lower level, more concrete QoSServices (the subclasses of QoSService). This is described by the QoSSubService association. In turn, each of the SubServices may require their own conditioning. This is modeled using the QoSConditioningSubService aggregation. Note that a more concrete QoSService may only be aggregated into one higher level Service, using this association. The cardinality on the GroupComponent reference is Max (1).truetrue1The higher level QoSService that is constructed by aggregating one or more lower-level QoSServices.GroupComponenttruetrueThe more concrete QoSService that is used to provide the higher level Service.PartComponenttrue 2.7.0CIM_QoSServiceThis class represents a specialization of the general concept of forwarding network traffic by adding specific semantics that define how traffic is forwarded based on the value of the ToS byte of a packet. This class is used to enable DiffServ devices and non-DiffServ devices to exchange traffic. This is done by defining a sibling class, DiffServService, to represent devices that forward traffic based on the DiffServ code point. This enables the administrator to define mappings between devices that do not support DiffServ (and instead use IP Precedence) and those that do support DiffServ. PrecedenceService is deprecated since forwarding based on the value of the ToS byte is specified using a FilterList, which is associated with a ClassifierElement. If there is a need to distinguish a higher-level set of coordinated QoS services, the QoSService class can be instantiated directly.CIM_IPHeadersFilter.HdrDSCPThis property is an 8-bit unsigned integer that defines the notion of precedence for different types of traffic. 2.7.0DiffServService represents the use of standard or custom DiffServ services (associated with particular Per Hop Behaviors, PHBs) to implement a (higher-level) QoSService. Note that the DiffServService may be just one of a set of coordinated QoSSubServices that together implement a higher-level QoSService. The relationship between the QoSServices is described using the association, QoSSubService.CIM_DiffServService.PHBIDThis property is an unsigned 8-bit integer, and defines the Differentiated Services Code Point (DSCP) that this link uses to represent various types of differentiated services through device-specific configuration commands. Itis deprecated since this information is conveyed via filter lists, associated with ClassifierElements. The DiffServService is better represented as a Per Hop Behavior.A 16-bit unsigned integer which identifies a particular per hop behavior, or family of per hop behaviors. The value is a Per Hop Behavior Identification Code, as defined in [R3140]. Note that as defined, these identification codes use the default, recommended, code points for PHBs as part of their structure. These values may well be different from the actual value used in the marker, as the marked value is domain-dependent. The ability to indicate the PHB Identification Code associated with a DiffServService is helpful when tying the QoSService to reference documents, and for inter-domain coordination and operation. 2.7.0CIM_QoSServiceThis class represents a specialization of the general concept of forwarding network traffic by adding specific semantics that define how traffic is forwarded based on the value of the Priority field in the 802.1P header. This class is used to enable DiffServ domains and domains that support 802.1P only to exchange traffic. It represents the mapping between implementations that only support 802.1P priority marking to be mapped to implementations that support DiffServ, which use DSCPs. 8021PService is deprecated since forwarding based on the value of the Priority field in the 802.1P header is specified using a FilterList, which is associated with a ClassifierElement. If there is a need to distinguish a higher-level set of coordinated QoS services, the QoSService class can be instantiated directly.CIM_8021Filter.8021HdrPriorityValueThis property is an 8-bit unsigned integer that defines the notion of priority as specified in 802.1P implementations. 2.7.0This class represents a specialization to the general concept of forwarding network traffic by adding specific semantics that characterize the operation of the Assured Forwarding (AF) Service (RFC2597). This RFC defines four different AF classes to represent four different treatments of traffic (e.g., a different amount of forwarding resources, such as buffer space and bandwidth, are allocated). Within each AF class, IP packets are marked with one of three possible drop precedence values. The drop precedence of a packet determines the relative importance of that packet compared to other packets within the same AF class if congestion occurs. A congested interface will try to avoid dropping packets with a lower drop precedence value by instead discarding packets with a higher drop precedence value. Note that [R2597] defines 12 DSCPs that together represent the AF Per Hop Behavior (PHB) group. Implementations are free to extend this (e.g., add more classes and/or drop precedences). The AFService class is modeled as a specialization of DiffServService, which is in turn a specialization of QoSService. This enables it to be related to higher-level QoSServices, as well as to lower-level conditioning sub-services (e.g., classification, metering, dropping, queuing, and others).This property is an 8-bit unsigned integer that indicates the number of AF classes that this AF implementation uses. Among the instances aggregated into AFService (using QoSConditioningSubService), one SHOULD find markers with as many distinct values as is indicated by ClassNumber.This property is an 8-bit unsigned integer that indicates the number of drop precedence values that this AF implementation uses. The number of drop precedence values is the number PER AF CLASS. The corresponding droppers are found in the collection of ConditioningServices aggregated by QoSConditioningSubService. 2.7.0This class represents a service that supports a particular microflow. The microflow is identified by the string-valued property FlowID. In some implementations, an instance of this class corresponds to an entry in the implementation's flow table.This property is a string containing an identifier for a microflow. 2.7.0CIM_DiffServServiceThis class represents a specialization of the general concept of forwarding network traffic by adding specific semantics that characterize the operation of the Expedited Forwarding (EF) Service (defined in RFC 2598). The EF PHB can be used to build a low loss, low latency, low jitter, assured bandwidth, end-to-end service through DiffServ domains. Such a service appears to the endpoints like a point-to-point connection or a virtual leased line. This service has also been described as Premium service in the IETF literature. RFC 2598 defines one DSCP for the EF service. Thus, there is no need to define any attributes in this class, since an instance of the EFService class, by definition, means that this particular DSCP is used. EFService is deprecated since forwarding based on the value of the DiffServ Code Point is specified using a FilterList, which is associated with a ClassifierElement. If there is a need to distinguish a higher-level set of coordinated QoS services, the DiffServService class can be instantiated directly. true2.6.0The IETF's RFC2597 describes a Differentiated Services Per-Hop-Behavior (PHB) Group called Assured Forwarding (AF). Quoting from the RFC, 'The AF PHB group provides delivery of IP packets in four independently forwarded AF classes. Within each AF class, an IP packet can be assigned one of three different levels of drop precedence.' The AFRelatedServices association describes the precedence of the individual AF drop-related Services within an AF IP packet-forwarding class.true1The AFService with a lower drop precedence (ie, lower probability of dropping packets).trueAn AFService at the same IP packet-forwarding class level, but at a higher drop precedence. 2.7.0ConditioningService represents the ability to define how traffic is conditioned in the data-forwarding path of a device. The subclasses of ConditioningService define the particular types of conditioning that are done. These are the services performed by a classifier, a meter, a marker, a dropper, a queue, and a scheduler. Other, more sophisticated types of conditioning may be defined in the future. ConditioningService is a concrete class because its superclass (ForwardingService) is concrete. While this class can be instantiated, an instance of it does not accomplish anything, because the nature of the conditioning, and the parameters that control it, are specified only in the subclasses of ConditioningService. Two associations in which ConditioningService participates are critical to its usage in QoS - QoSConditioningSubService and NextService. QoSConditioningSubService aggregates ConditioningServices into a particular QoS service (such as AF), to describe the specific conditioning functionality that underlies that QoSService in a particular device. NextService indicates the subsequent conditioning service(s) for different traffic streams.CIM_EnabledLogicalElement.EnabledStateThis property is a boolean that, if TRUE, signifies that one or more conditioning functions can be performed on traffic encountered by this ConditioningService. This allows one or more ConditioningServices to be enabled or disabled to provide different types of conditioning for traffic. Enabled is deprecated in lieu of a similar (but more generally and completely defined) property which is inherited. 2.7.0A QoSService utilizes underlying ConditioningServices as part of its overall functionality. This is modeled using the QoSConditioningSubService association. Note that a ConditioningService may only be part of a single QoSService - the cardinality on the QoSService reference is Max (1).truetrueThis aggregation identifies the set of ConditioningServices that together condition traffic for a particular QoSService.GroupComponenttruetrueThe ConditioningService.PartComponenttrue 2.7.0CIM_IngressConditioningServiceOnEndpointCIM_EgressConditioningServiceOnEndpointThe QoS Model describes the traffic conditioning functions in place for a network device. In order to 'be conditioned', a packet is received at a ProtocolEndpoint. After 'conditioning', a packet is dropped or leaves the device via a ProtocolEndpoint. This dependency on ProtocolEndpoints is defined by the ConditioningServiceOnEndpoint association. A property of the association, ServiceType, indicates whether the ConditioningService handles incoming ("Ingress") or out-going ("Egress") packets. This association is deprecated since different cardinalities are needed on the ingress and egress classes. This cannot be done using a single association.trueCIM_IngressConditioningServiceOnEndpoint.AntecedentCIM_EgressConditioningServiceOnEndpoint.Antecedent Antecedent1The ProtocolEndpoint through which traffic arrives at or leaves from a network device.trueCIM_IngressConditioningServiceOnEndpoint.DependentCIM_EgressConditioningServiceOnEndpoint.DependentDependentThe ConditioningService which begins or ends the traffic conditioning processing within a network device.trueCIM_IngressConditioningServiceOnEndpointCIM_EgressConditioningServiceOnEndpointIndicates whether a packet is incoming (value = 1, "Ingress") or out-going (value = 2, "Egress") at the ProtocolEndpoint, relative to the ConditioningService.012UnknownIngressEgress 2.7.0This association represents the binding, in the ingress direction, between a ProtocolEndpoint and the first ConditioningService that processes packets received via that Endpoint. Since there can only be one 'first' ConditioningService for a ProtocolEndpoint, the cardinality for the Dependent object reference is narrowed from 0..n to 0..1. On the other hand, a single ConditioningService can be the first to process packets received via multiple ProtocolEndpoints. So, the cardinality of the Antecedent object reference remains 0..n.trueThe ProtocolEndpoint through which traffic arrives at a network device.Antecedenttrue1The ConditioningService which begins the traffic conditioning processing within a network device.Dependenttrue 2.7.0This association represents the binding, in the egress direction, between a ProtocolEndpoint and the last ConditioningService that processes packets before they leave a network device (via that ProtocolEndpoint). This 'last' ConditioningService is ordinarily a scheduler, but it does not have to be. There can be multiple 'last' ConditioningServices for an Endpoint (for example, in the case of a fallback scheduler). Therefore, the cardinality for the Dependent object reference remains 0..n. On the other hand, a single ConditioningService cannot be the last one to process packets for multiple Endpoints. So, the cardinality of the Antecedent object reference is narrowed from 0..n to 0..1.true1The ProtocolEndpoint through which traffic leaves a network device.AntecedenttrueThe ConditioningService which ends the traffic conditioning processing within a network device.Dependenttrue true2.7.0NextService establishes a predecessor-successor relationship between two ConditioningService objects. This association is used to indicate the sequence of ConditioningServices required to process a particular type of traffic. Instances describe the various relationships between different ConditioningServices (such as classifiers, meters, droppers, etc.) that are used collectively to condition traffic. Both one-to-one and more complicated fan-in and/or fan-out relationships can be described. The ConditioningServices may feed one another directly, or they may be mapped to multiple 'next' Services based on the characteristics of the packet.trueThe preceding ConditioningService, 'earlier' in the processing sequence for a packet.trueThe 'next' or following ConditioningService. 2.7.0ClassifierService represents a logical entity associated with an ingress or egress interface of a device, that takes a single input stream, and sorts it into one or more output streams. The sorting is done by a set of filters that select packets based on the packet contents, or possibly based on other attributes associated with the packet. Each output stream is the result of matching a particular filter. Rather than being linked directly to its filters (instantiated as FilterLists), a classifier is modeled as an aggregation of ClassifierElements. Each of these ClassifierElements is linked to a single FilterList, by the association ClassifierElementUsesFilterList. Note that ClassifierServices are designed to allow hierarchical classification. When hierarchical classification is used, a ClassifierElement may point to another ClassifierService (via the association, NextServiceAfterClassifierElement). When this is true, the ClassifierElement MUST NOT use the ClassifierElementUsesFilterList association. A classifier is modeled as a ConditioningService so that it can be aggregated into a QoSService (using the QoSConditioningSubService aggregation), and can use the NextService association to identify the subsequent ConditioningServices for different traffic streams. 2.7.0ClassifierElement represents the linkage, within a single ClassifierService, between a FilterList (that defines the criteria to select packets from the stream of packets coming into the Service) and the next ConditioningService (to which the selected packets go after they leave the ClassifierService). ClassifierElement has no properties of its own. It is present to serve as an aggregated entity into ClassifierService (using the ClassifierElementInClassifierService association), and for associations with its FilterList (ClassifierElementUsesFilterList) and its next ConditioningService (NextServiceAfterClassifierElement). Note that a ClassifierElement may be associated with a ClassifierService through the NextServiceAfterClassifierElement association. This will occur when implementing hierarchical classification. In this case, the ClassifierElement MUST NOT instantiate the ClassifierElementUsesFilterList association. Further, when a ClassifierElement is associated with a ClassifierService as described above, the order of processing of the associated ClassifierService is a function of the ClassifierOrder property of the ClassifierElementInClassifierService aggregation. true2.7.0This aggregation represents the relationship between a ClassifierService and the ClassifierElements that provide its fan-out function. ClassifierElements represent the traffic selectors for the Service. A ClassifierService typically aggregates multiple ClassifierElements. An individual Element, however, is aggregated only by a single ClassifierService.truetrue11The ClassifierService which aggregates ClassifierElements.GroupComponenttruetrueThe aggregated ClassifierElement, defined in the context of one ClassifierService.PartComponenttrueBecause the filters for a classifier can overlap, it is necessary to specify the order in which the ClassifierElements are aggregated by a ClassifierService. This then dictates the order in which packets coming into the classifier are presented. Values are represented in ascending order: first '1', then '2', and so on. Different values MUST be assigned for each of the ClassifierElements aggregated by a given ClassifierService. 2.7.0This association relates one or more ClassifierElements with a FilterList that defines the criteria to select packets for the classifier to process. Note that a classifier is always modeled as a ClassifierService that aggregates a set of ClassifierElements. Each of these ClassifierElements is EITHER associated with a single FilterList OR associated to another ClassifierService (via NextServiceAfterClassifierElement to describe hierarchical classification).trueAntecedent1The FilterList that specifies the traffic criteria for a ClassifierElement.trueDependentThe ClassifierElement that depends on the FilterList for its traffic criteria.true 2.7.0An association used to establish a predecessor-successor relationship between a single ClassifierElement (within a ClassifierService) and the next ConditioningService object that further processes the selected traffic. Note that the cardinalities indicate that a FollowingService MUST be defined, after the ClassifierElement. This is because there is no reason to classify traffic unless further processing will be done.truePrecedingServiceThe ClassifierElement that selects traffic to be passed to the FollowingService.trueFollowingService11The ConditioningService that follows the ClassifierElement.true CIM_ClassifierElementUsesFilterListClassifierElementInClassifierService2.7.0In order for a ClassifierService to correctly identify and process network traffic, that traffic must be described by FilterEntries, which are aggregated into FilterLists. This association defines the Dependency of the ClassifierService on FilterLists (and therefore, their FilterEntries). The cardinality of the association requires that the ClassifierService operate against at least one FilterList. The association is deprecated in lieu of associating FilterLists to ClassifierElements, and ClassifierElements into ClassifierServices. The latter approach is very flexible regarding the implementations that can be modeled, and removes the need to track individual traffic streams using an artificial model property, TrafficClass. Using ClassifierElements, each stream is processed beginning with a single FilterList and progressing through various ConditioningServices, associated via instances of NextService.trueCIM_ClassifierElementUsesFilterList.AntecedentAntecedentThe FilterList aggregating FilterEntries, these in turn describe how traffic is identified and processed by the ClassifierService.trueCIM_ClassifierElementUsesFilterList.DependentDependentThe ClassifierService which uses the FilterList and its aggregated FilterEntries.trueCIM_ClassifierElementInClassifierService.ClassifierOrderThe ordering of the FilterLists used in the classification and forwarding functions of the ClassifierService. 2.7.0This class represents the metering of network traffic. Metering is the function of monitoring the arrival times of packets of a traffic stream and determining the level of conformance of each packet with respect to a pre-established traffic profile. A meter has the ability to invoke different ConditioningServices for conforming and non-conforming traffic. Traffic leaving a meter may be further conditioned (e.g., dropped or queued) by routing the packet to another conditioning element. This class is modeled as a ConditioningService so that it can be aggregated into a QoSService (using the QoSConditioningSubService association), to indicate that its functionality underlies that QoS service. MeterService also participates in a subclass of the NextService association, to identify the subsequent ConditioningServices for conforming and non-conforming traffic.This property is an enumerated 16-bit unsigned integer that is used to specify the particular type of meter. Defined values of the enumeration are: 1: Other 2: Average Rate Meter 3: Exponentially Weighted Moving Average Meter 4: Token Bucket Meter Note: The MeterType property and the MeterService subclasses provide similar information. This property is defined for query purposes and for future expansion. It is assumed that not all MeterServices will require a subclass to define them. Therefore, MeterService will be instantiated directly and the Type property is needed.1234OtherAverage Rate MeterExponentially Weighted Moving Average MeterToken Bucket MeterCIM_MeterService.OtherMeterTypeThis property is a string used in conjunction with the MeterType property. When the value of MeterType is 1 (i.e., "Other"), then the name of the conformance level for this meter is defined in this property.CIM_MeterService.MeterTypeAn unsigned integer indicating the number of conformance levels supported by the Meter. For example, when only 'in-profile' or 'out of profile' metering is supported. ConformanceLevels is set to 2. 2.7.0This is a concrete subclass of MeterService that represents a simple meter, called an Average Rate Meter. This type of meter measures the average rate at which packets are submitted to it over a specified time. Packets are defined as conformant if their average arrival rate does not exceed the specified measuring rate of the meter. Any packet that causes the specified measuring rate to be exceeded is defined to be non-conforming.This property is a 32-bit unsigned integer that defines the rate used to determine whether admitted packets are in conformance or not. The value is specified in kilobits per second.KiloBits per SecondThis property is a 64-bit unsigned integer that defines the time period over which the average measurement should be taken. The value is specified in microseconds.MicroSeconds 2.7.0This is a concrete subclass of the MeterService class that represents an exponentially weighted moving average meter. This meter is a simple low-pass filter that measures the rate of incoming packets over a small, fixed sampling interval. Any admitted packet that pushes the average rate over a pre-defined limit is defined to be non-conforming.This property is a 32-bit unsigned integer that defines the average rate against which the sampled arrival rate of packets should be measured. Any packet that causes the sampled rate to exceed this rate is deemed non-conforming. The value is specified in kilobits per second.KiloBits Per SecondThis property is a 64-bit unsigned integer that defines the sampling interval used to measure the arrival rate. The calculated rate is averaged over this interval and checked against the AverageRate property. All packets whose computed average arrival rate is less than the AverageRate are deemed conforming. The value is specified in microseconds.MicroSecondsThis property is a 32-bit unsigned integer representing the reciprocal of the time constant (e.g., frequency response) of what is essentially a simple low-pass filter. For example, the value 64 for this property represents a time constant value of 1/64. 2.7.0This is a concrete subclass of the MeterService class that represents the metering of network traffic using a token bucket meter. Two types of token bucket meters are defined using this class - a simple, two-parameter bucket meter, and a multi-stage meter. A simple token bucket usually has two parameters, an average token rate and a burst size, and has two conformance levels: 'conforming' and 'non-conforming'. This class also defines an excess burst size, which enables the meter to have three conformance levels ('conforming', 'partially conforming', and 'non-conforming'). In this case, packets that exceed the excess burst size are deemed non-conforming, while packets that exceed the smaller burst size but are less than the excess burst size are deemed partially conforming.This property is a 32-bit unsigned integer that is used to define the committed rate of the meter. The value is expressed in kilobits per second.KiloBits per SecondThis attribute is a 32-bit unsigned integer that is used to define the peak rate of the meter. The value is expressed in kilobits per second.KiloBits per SecondThis property is a 32-bit unsigned integer that is used to define the maximum number of tokens available for the committed rate (specified by the AverageRate property). The value is specified in kilobytes.KiloBytesThis property is a 32-bit unsigned integer that is used to define the maximum number of tokens available for the peak rate (specified by the PeakRate property). The value is specified in kilobytes.KiloBytes true2.7.0This association describes a predecessor-successor relationship between a MeterService and one or more ConditioningService objects that process traffic from the meter. For example, for devices that implement preamble marking, the FollowingService reference (after the meter) is a PreambleMarkerService - to record the results of the metering in the preamble. It might be expected that the NextServiceAfterMeter association would subclass from NextService. However, meters are 1:n fan-out elements, and require a mechanism to distinguish between the different results/outputs of the meter. Therefore, this association defines a new key property, MeterResult, which is used to record the result and identify the output through which this traffic left the meter.trueThe preceding MeterService, 'earlier' in the processing sequence for a packet.trueThe 'next' or following ConditioningService.trueInformation on the result of the metering. Traffic is distinguished as being conforming, non-conforming, or partially conforming. More complicated metering can be built either by extending the enumeration or by cascading meters.0123UnknownConformingPartially ConformingNon-Conforming 2.6.0MarkerService represents the general process of marking a selected field in a network packet with a specified value. Packets are marked in order to control the conditioning that they will subsequently receive. Subclasses of MarkerService identify the specific fields to be marked, and introduce properties to represent the values used in marking these fields. Markers are usually invoked as a result of a preceding classifier match. MarkerService is a concrete class because its superclass (ConditioningService) is concrete. While this class can be instantiated, an instance of it does not accomplish anything, because both the field to be marked and the value used to mark it are defined in subclasses. MarkerService is modeled as a ConditioningService so that it can be aggregated into a QoSService (using the QoSConditioningSubService association). This association indicates that the MarkerService's functionality underlies the QoSService. MarkerService also participates in the NextService association to identify the subsequent ConditioningService(s) that act on packets after they have been marked. 2.7.0PreambleMarkerService models the storing of traffic-conditioning results in a packet preamble. An instance appends a two-part string of the form '<type>,<value>' to the packet preamble. The concept of 'type's is discussed more fully in the Description of the class' FilterItemList property.To foster interoperability, the basic format of the information captured by a PreambleMarker is specified. That information is contained in the FilterItemList property (an ordered, string array). Each entry in the array takes the form 'type,value'. When entries are added, they are appended to the end of the list. A limited set of standardized 'type's exist. They are: - ConformingFromMeter, NonConformingFromMeter and PartConformingFromMeter to convey metering results (where the 'value' is the name of the meter) - VlanId to describe the traffic's VLAN information (where the 'value' is the VLAN ID). An implementation is free to define and use other preamble 'types'. Note that a wildcard value of "any" is allowed to indicate that the preamble entry matches for any 'value' of the specified 'type'. For example, using the wildcard, an administrator can define a filter to select all packets that were found to be conforming ('type' = "ConformingFromMeter") without having to name each meter individually.Ordered 2.7.0ToSMarkerService marks the ToS (type of service) field in the IPv4 packet header [R791] with a specific value. Packets are marked in order to control the conditioning that they will subsequently receive. Following common practice, the value to be written into the ToS field is represented as an unsigned 8-bit integer.This property is an unsigned 8-bit integer, representing a value to be used for marking the type of service (ToS) field in the IPv4 packet header. The ToS field is defined to be a complete octet, so the range for this property is 0..255. Some implementations, however, require that the lowest-order bit in the field is always 0. Such an implementation cannot support an odd TosValue. 2.7.0DSCPMarkerService marks the differentiated services codepoint (DSCP) within the DS field in the IPv4 and IPv6 packet headers, as defined in [R2474]. It is marked with the specific value defined in the property, DSCPValue. Following common practice, the value to be written into the field is represented as an unsigned 8-bit integer.063This property is an unsigned 8-bit integer, representing a value to be used for marking the DSCP field in an IPv4 or Ipv6 packet header. Since the DSCP consists of 6 bits, the values for this property are limited to the range 0..63. When the DSCP is marked, the remaining two bits in the DS field are left unchanged. 2.7.08021QMarkerService marks the Priority field in an 802.1Q-compliant frame, with a specified value. Frames are marked in order to control the conditioning that they will subsequently receive. Following common practice, the value to be written into the field is represented as an unsigned 8-bit integer.07This property is an unsigned 8-bit integer, representing a value to be used for marking the Priority field in the 802.1Q header. Since the Priority field consists of 3 bits, the values for this property are limited to the range 0..7. When the Priority field is marked, the remaining two bits in the octet are left unchanged. 2.7.0DropperService represents the ability to selectively drop network traffic, and/or to invoke another ConditioningService (indicated using the NextService association) for further processing of traffic that is not dropped. It is the base class for different types of droppers. Droppers are distinguished by the algorithm that they use to drop traffic. The NextService association has special semantics for droppers, in addition to conveying the general information of 'what happens next' (that apply to all ConditioningServices). The queue(s) from which a particular dropper drops packets are identified by following chain(s) of NextService associations 'rightwards' from the dropper, until they reach a queue.This property is an enumerated 16-bit unsigned integer that defines the type of dropper. Its Values are: 1: Other 2: Random 3: HeadTail 4: Absolute Dropper Note: The DropperType property and the DropperService subclasses provide similar information. This property is defined for query purposes and to not require a subclass for all types of DropperServices (for example, to describe an Absolute Dropper in today's model). Therefore, DropperService can be instantiated directly and the Type property is needed.1234OtherRandomHeadTailAbsolute DropperCIM_DropperService.OtherDropperTypeThis property contains a vendor-specific value for the type of dropping that is done. It is used when the value of the DropperType property is 1 (Other).CIM_DropperService.DropperTypeCIM_DropperService.TypeOfDropper (=4, Absolute Dropper)This property indicates whether the Dropper will always drop incoming packets (value=1) regardless of their type. It is deprecated since its information is conveyed by the TypeOfDropper property (value=4, 'Absolute Dropper').012UnknownAlways DropDo Not Always DropThis enumeration indicates the point in the associated queue (associated via the NextService relationship) from which packets should be dropped. If the value is 0 "Unknown", then packets MAY be dropped from any location in the queue.012UnknownHeadTailThis property is an enumerated unsigned 16-bit integer that defines the metric used to trigger the start of dropping packets. This does NOT mean that all packets will be dropped; it does mean that SOME packets will start to be dropped. The number and type of packets dropped is a function of the type of algorithm used by this Dropper. Values are: 1: Other 2: Queue Threshold 3: Arrival Rate 123OtherQueue ThresholdArrival RateThis property is an enumerated unsigned 16-bit integer that defines the metric used to determine when ALL packets will be dropped REGARDLESS of the type of algorithm used by this Dropper. Values are: 1: Other 2: Queue Threshold 3: Arrival Rate 123OtherQueue ThresholdArrival Rate 2.7.0REDDropperService represents the ability to drop network traffic using a Random Early Detection (RED) algorithm. The purpose of a RED algorithm is to avoid congestion (as opposed to managing congestion). Instead of waiting for the queues to fill up, and then dropping large numbers of packets, RED works by monitoring average queue depth. When the queue depth exceeds a minimum threshold, packets are randomly discarded. These discards cause TCP to slow its transmission rate for those connections that experienced the packet discards. Other connections are not affected by these discards. A RED dropper always drops packets from a single queue, which is related to the dropper as the following Service in the NextService association. The queue(s) examined by the drop algorithm are found by following the CalculationServiceForDropper association(s) to determine the dropper's DropThresholdCalculationService(s), and then following the CalculationBasedOnQueue association to find the queue being watched by each CalculationService.This is an unsigned 32-bit integer that defines the minimum average queue depth at which packets are subject to being dropped. (See the ThresholdUnits property to determine the units of the threshold.) The slope of the drop probability function is described by the Start/StopProbability properties.CIM_REDDropperService.ThresholdUnits01000This is an unsigned 32-bit integer that defines the maximum average queue length at which packets are subject to always being dropped, regardless of the dropping algorithm and probabilities being used. (See the ThresholdUnits property to determine the units of the threshold.)CIM_REDDropperService.ThresholdUnitsThis is an unsigned 32-bit integer, used in conjunction with the StopDropProbability property. The start and stop probabilities define the slope of the drop probability function. This function governs the rate at which packets are subject to being dropped, as a function of the queue length. This property expresses a drop probability in drops per thousand packets. For example, the value 100 indicates a drop probability of 100 per 1000 packets, that is, 10%. Min and max values are 0 to 1000.Per Thousand PacketsCIM_REDDropperService.StopProbability01000This is an unsigned 32-bit integer, used in conjunction with the StartDropProbability property. The start and stop probabilities define the slope of the drop probability function. This function governs the rate at which packets are subject to being dropped, as a function of the queue length. This property expresses a drop probability in drops per thousand packets. For example, the value 100 indicates a drop probability of 100 per 1000 packets, that is, 10%. Min and max values are 0 to 1000.Per Thousand PacketsCIM_REDDropperService.StartProbabilityThresholdUnits is an enumerated integer that identifies the units for the Min and MaxQueueThreshold properties. The values are either bytes (1) or packets (2).12BytesPackets 2.7.0No valueThis class represents a logical entity that resides in the data forwarding path of a network device. It describes the ability to drop network traffic using a Weighted Random Early Detection (WRED) algorithm. Like RED, the purpose of WRED is to avoid congestion (as opposed to managing congestion). This modification of the basic RED algorithm enables packets belonging to different traffic classes to be dropped at different queue depths. This algorithm also enables discard to be done based on different information contained in the packet header, such as IP Precedence, RSVP session parameters, or even on other factors not directly encoded in the packet header, such as the queue depth. Implementation of this class has shown that weighting should not be a property of the class (but on an association to it), and that there is insufficient data to process the drop metric. The class is deprecated pending further definition by the DMTF.No valueThis property is an enumerated 16-bit unsigned integer, and defines the type of metric that is used to drop traffic. Values are: 1: Other 2: IP Precedence 3: DSCP Value 4: 802.1P Priority Value 5: RSVP Session 6: Queue Depth 7: Packet Arrival Rate 1234567OtherIP PrecedenceDSCP Value802.1P Priority ValueRSVP SessionQueue DepthPacket Arrival RateCIM_WeightedREDDropperService.OtherDropMetricNo valueThis string property is used in conjunction with the DropMetric property. When the value of DropMetric is 1 (i.e., "Other"), then the type of metric to be used is defined in this property.CIM_WeightedREDDropperService.DropMetricCIM_DropperThresholdCalculationService.SmoothingWeight0100This is a 32-bit real number that represents the weighting factor used to determine which queues get more service. 2.7.0HeadTailDropper describes the threshold information of a head or tail dropper. The inherited property DropFrom indicates whether a particular instance of this class is a head dropper or a tail dropper. A head dropper always examines the same queue from which it drops packets, and this queue is always related to the dropper as the following service in the NextService association.This is an unsigned 32-bit integer that indicates the queue depth (in bytes) at which traffic is dropped. For a tail dropper, all newly arriving traffic is dropped. For a head dropper, packets at the front of the queue are dropped to make room for new packets, which are added at the end.Bytes 2.7.0QueuingService represents the ability to queue network traffic, and to specify the characteristics for determining long-term congestion. It is modeled as a ConditioningService so that it can be aggregated into a QoSService (using the QoSConditioningSubService association). This indicates that its functionality underlies the QoSService.trueIndicates the current depth of this queue in units specified by DepthUnits. This value may be important in diagnosing unexpected behavior.CIM_QueuingService.DepthUnitsDepthUnits is an enumerated integer that identifies the units for the CurrentQueueDepth property. The values are either bytes (1) or packets (2).12BytesPackets 2.7.0This class calculates an average depth for a queue, based on a smoothing weight and a sampling time interval. The latter are properties of this Service, describing how it operates and its necessary parameters. The Service does the calculation on behalf of a RED dropper (as indicated by the association, CalculationServiceForDroppper). A DropThresholdCalculationService is always associated to the single queue that it examines via the CalculationBasedOnQueue relationship.0100000This property is a 32-bit unsigned integer, ranging between 0 and 100,000 - specified in thousandths. It defines the weighting of past history in affecting the calculation of the current average queue depth. The current queue depth calculation uses the inverse of this value as its factor, and one minus that inverse as the factor for the historical average. The calculation takes the form: average = (old_average*(1-inverse of SmoothingWeight)) + (current_queue_depth*inverse of SmoothingWeight) Implementations may choose to limit the acceptable set of values to a specified set, such as powers of 2.ThousandthsThis property is a 32-bit unsigned integer, and defines the number of nanoseconds between each calculation of average/smoothed queue depth. When this property is not specified, the CalculationService may determine an appropriate interval.NanoSeconds 2.7.0No valueDescribes the reliance of a QueuingService on other, supporting queues and their QueuingServices. A given Service can only act in support of one QueuingService; but a higher level queue may be supported by many lower level QueuingServices. The class is deprecated since a queue only stores network traffic. It does not support other queues, or manipulate their entries. This type of processing is described using NextService associations 'rightwards' from the QueuingService. These associations reference 'other' ConditioningServices that may send traffic to 'other' queues).trueNo valueThe supporting queue(s) and its QueuingService. This Service can only support at most one, higher level QueuingService.Antecedenttrue1No valueThe QueuingService dependent on other, supporting QueuingServices.Dependenttrue 2.7.0This association is a subclass of ServiceServiceDependency, and represents the reliance of a REDDropperService on one or more DropThresholdCalculationServices. The latter calculate average queue depth, based on the observed depths of a queue. The specific queue examined by each CalculationService is defined using the CalculationBasedOnQueue association.true1A calculation service for the dropper.AntecedenttrueThe RED dropper which is dependent on average queue depth calculations by the Antecedent Service.Dependenttrue 2.7.0This association establishes a dependency relationship between a QueuingService and an instance of the DropThresholdCalculationService class. The queue's current depth is used by the CalculationService in calculating an average/smoothed queue depth.true11The queue examined by the CalculationService.AntecedenttrueThe CalculationService that provides an average queue depth.Dependenttrue 2.7.0This association describes the relationship between a head or tail dropper and the queue that it monitors to determine when to drop traffic. The referenced queue's depth is compared against the Dropper's threshold property. Although the dropper drops from only one queue, the drop decision may be influenced by the state of several queues. The rule for combining the multiple inputs is simple addition: if the sum of the lengths of the monitored queues exceeds the dropper's QueueThreshold value, then packets are dropped. Note that this rule for combining inputs may be overridden.trueAntecedent1A QueuingService examined by the CalculationService.trueDependentThe CalculationService that provides an average queue depth.true 2.6.0Describes the reliance of a QueuingService on the availability of space in a BufferPool.trueAntecedentThe BufferPool supporting packet storage for a QueuingService.trueDependentThe QueuingService dependent on the BufferPool for storage space.true0100This property is an 8-bit unsigned integer representing a percentage from 0 to 100. It defines the percentage of the BufferPool that should be allocated to the referenced QueuingService. If absolute sizes are desired, this is accomplished by defining individual BufferPools of the specified sizes, with QueueAllocation.AllocationPercentages set to 100.Percent 2.7.0This class represents the scheduling service, which is a process that determines whether a queued packet should be removed from a queue and sent to an output interface. Note that output interfaces can be physical network interfaces or interfaces to components internal to systems, such as crossbars or backplanes. In either case, if multiple queues are involved, schedulers are used to provide access to the interface. Each instance of a PacketSchedulingService describes a scheduler from the perspective of the queues that the scheduler is servicing. One can describe that different schedulers support different queues, or that a scheduler supports several queues. PacketSchedulingService is modeled as a ConditioningService so that it can be aggregated into a QoSService (using the QoSConditioningSubService association) to indicate that its functionality underlies that QoS service. It participates in the NextService association to identify a subsequent ConditioningService, if any, that acts on traffic after it has been processed by the scheduler.This property is an enumerated 16-bit unsigned integer, and defines the type of scheduler. Values are: 1: Other 2: FIFO 3: Priority 4: Allocation 5: Bounded Priority 6: Weighted Round Robin Packet If no value is specified, 2 ("FIFO") should be assumed.123456OtherFIFOPriorityAllocationBounded PriorityWeighted Round Robin PacketCIM_PacketSchedulingService.OtherSchedulerTypeThis string property is used in conjunction with the SchedulerType property. When the value of SchedulerType is 1 (i.e., "Other"), then the type of scheduler to be used is defined in this attribute.CIM_ PacketSchedulingService.SchedulerType 2.7.0This association is a subclass of NextService, and defines a predecessor-successor relationship between PacketSchedulingServices. In a hierarchical queuing configuration (where a second scheduler treats the output of a first scheduler as a single, aggregated input), the two schedulers are related via the NextScheduler association.truePrecedingServiceThe PacketSchedulingService whose output is treated as a single, aggregated input by the FollowingService scheduler. The [0..n] cardinality indicates that a single FollowingService scheduler may bring together the aggregated outputs of multiple prior schedulers.trueFollowingService1A scheduler that includes among its inputs the aggregated outputs of one or more PrecedingService schedulers.true 2.7.0CIM_QueueToScheduleCIM_SchedulingServiceToScheduleIn order to remove queued packets, a process or Service (identified as a PacketSchedulingService) runs. This association describes the Dependency of the queue and its QueuingService on a SchedulingService, which empties it. The association is deprecated in lieu of associating QueuingServices to SchedulingElements, and SchedulingElements into SchedulingServices. The latter approach is very flexible regarding the implementations that can be modeled, and removes the need to track individual traffic streams using an artificial model property, TrafficClass.trueCIM_QueueToSchedule.Queue1The PacketSchedulingService which empties the QueuingService's queue.AntecedenttrueCIM_QueueToSchedule.SchedElementThe queue and its QueuingService from which packets are emptied.Dependenttrue 2.7.0A type of packet scheduler, that is capable of operating in a non-work conserving manner. This class does not add any properties beyond those it inherits from PacketSchedulingService. It does, however, participate in one additional association, FailNextScheduler. 2.7.0This association is a subclass of NextScheduler, and defines a predecessor-successor relationship between a NonWorkConservingSchedulingService and another PacketSchedulingService. It indicates that the NonWorkConserving scheduler may pass up a scheduling opportunity (thereby behaving in a non-work conserving manner), and make the resulting bandwidth available to the FollowingService scheduler.trueThe NonWorkConservingSchedulingService whose excess bandwidth is made available to the scheduler identified by the FollowingService reference. The [0..n] cardinality indicates that a single FollowingService scheduler may have the opportunity to use the unused bandwidth of multiple prior non-work-conserving schedulers.PrecedingServicetrue1A scheduler that may use the bandwidth available from the non-work conserving scheduler.FollowingServicetrue true2.7.0SchedulingElement represents the configuration information that a PacketSchedulingService has for one of the elements that it is scheduling. The scheduled element is either a QueuingService or another PacketSchedulingService. Among the subclasses of this class, some are defined in such a way that all of their instances are work conserving. Other subclasses, however, have instances that either are or are not work conserving. In this class, the boolean property WorkConserving indicates whether an instance is or is not work conserving. Note that WorkConserving is restricted to TRUE in the subclasses that are inherently work conserving, since instances of these classes cannot be anything else.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'.trueA boolean property indicating whether the PacketSchedulingService tied to this instance (by the ElementInSchedulingService aggregation) is treating thequeue/input tied to this instance, in a work-conserving manner. The queue/input is indicated by either the QueueToSchedule or SchedulingServiceToSchedule association. Note that this property is writeable, indicating that an administrator can change the behavior of the SchedulingElement - but only for those elements that can operate in a non-work conserving mode. 2.7.0This class is a subclass of the abstract class SchedulingElement. It introduces five new properties to support bandwidth-based scheduling. As is the case with all subclasses of SchedulingElement, the input associated with an instance of AllocationSchedulingElement is of one of two types: either a queue, or another scheduler.A 16-bit unsigned integer enumeration that identifies the units in which the BandwidthAllocation and BurstAllocation properties are expressed. The following values are defined: - Bytes(1) - Packets(2) - Cells(3) (fixed-size, for example, ATM) If no value is specified, 1 ("Bytes") should be assumed.123BytesPacketsCellsA 32-bit bit unsigned integer defining the number of 'units' per second that should be allocated to the associated input. 'Units' are identified by the AllocationUnits property.CIM_AllocationSchedulingElement.AllocationUnitsA 32-bit bit unsigned integer specifying the amount of temporary or short-term bandwidth (in 'units' per second) that can be allocated to an input, beyond the amount of bandwidth allocated through the BandwidthAllocation property. If the maximum actual bandwidth allocation for the input were to be measured, it would be the sum of the BurstAllocation and the BandwidthAllocation properties. 'Units' are identified by the AllocationUnits property.CIM_AllocationSchedulingElement.AllocationUnitsA boolean property that, if TRUE, enables unused bandwidth from the associated input to be allocated to other inputs serviced by the Scheduler.A boolean property that, if TRUE, indicates that the behavior of the scheduler relative to this input can be altered by changing the value of the inherited property, WorkConserving. 2.7.0This class is a subclass of the abstract class SchedulingElement. It introduces a new property, WeightingFactor, to give some inputs a higher probability of being serviced than other inputs. It also introduces a Priority property, to serve as a tiebreaker to be used when inputs have equal weighting factors. As is the case with all subclasses of SchedulingElement, the input associated with an instance of WRRSchedulingElement is of one of two types: either a queue, or another scheduler. Because scheduling of this type is always work conserving, the inherited boolean property, WorkConserving, is restricted to TRUE in this class.WorkConservingtrueA boolean property indicating whether the PacketSchedulingService tied to this instance (by the ElementInSchedulingService aggregation) is treating thequeue/input tied to this instance, in a work-conserving manner. The queue/input is indicated by either the QueueToSchedule or SchedulingServiceToSchedule association. Note that this property is writeable, indicating that an administrator can change the behavior of the SchedulingElement - but only for those elements that can operate in a non-work conserving mode.true0100000A 32-bit bit unsigned integer defining the weighting factor that offers some inputs a higher probability of being serviced than other inputs. The property's minimum value is 0, its maximum value is 100000, and its Units are thousandths.ThousandthsA 16-bit bit unsigned integer which serves as a tiebreaker, in the event that two or more inputs have equal weights. A larger value represents a higher priority. While this condition may not occur in some implementations of a weighted round robin scheduler, many implementations require a priority to resolve an equal-weight condition. In the instances where this behavior is not necessary or is undesirable, the property may be left unspecified. 2.7.0This class is a subclass of the abstract class SchedulingElement. It indicates that a scheduler is taking packets from a set of inputs using the priority scheduling discipline. As is the case with all subclasses of SchedulingElement, the input associated with an instance of PrioritySchedulingElement is of one of two types: either a queue, or another scheduler. The Priority property represents the priority for an input, relative to the priorities of all the other inputs to which the scheduler (that aggregates this PrioritySchedulingElement) is associated. Inputs to which the scheduler is related via other scheduling disciplines do not figure in this prioritization. Because scheduling of this type is always work conserving, the inherited boolean property, WorkConserving, is restricted to TRUE in this class.WorkConservingtrueA boolean property indicating whether the PacketSchedulingService tied to this instance (by the ElementInSchedulingService aggregation) is treating thequeue/input tied to this instance, in a work-conserving manner. The queue/input is indicated by either the QueueToSchedule or SchedulingServiceToSchedule association. Note that this property is writeable, indicating that an administrator can change the behavior of the SchedulingElement - but only for those elements that can operate in a non-work conserving mode.trueA 16-bit unsigned integer indicating the priority level of this SchedulingElement's input, relative to the other inputs serviced by the SchedulingElement's aggregating PacketSchedulingService. A larger value represents a higher priority. 2.7.0This class is a subclass of the class PrioritySchedulingElement, which is itself derived from the abstract class SchedulingElement. As is the case with all subclasses of SchedulingElement, the input associated with an instance of BoundedPrioritySchedulingElement is of one of two types: either a queue, or another scheduler. BoundedPrioritySchedulingElement adds an upper bound (BandwidthBound in kilobits per second) on how much traffic can be handled from an input. This data is specific to that one input. It is needed when bounded strict priority scheduling is performed. Note that this class inherits from its superclass the restriction of the inherited boolean property WorkConserving to TRUE.WorkConservingtrueA boolean property indicating whether the PacketSchedulingService tied to this instance (by the ElementInSchedulingService aggregation) is treating thequeue/input tied to this instance, in a work-conserving manner. The queue/input is indicated by either the QueueToSchedule or SchedulingServiceToSchedule association. Note that this property is writeable, indicating that an administrator can change the behavior of the SchedulingElement - but only for those elements that can operate in a non-work conserving mode.trueA 32-bit unsigned integer that defines the upper limit on the amount of traffic that can be handled from the input (through this SchedulingElement). This is not a shaped upper bound, since bursts can occur. It is a strict bound, limiting the impact of the input. Units are kilobits per second.KiloBits per Second true2.7.0This is a top-level association, representing the relationship between a queue (QueuingService) and a SchedulingElement. The SchedulingElement, in turn, represents the information in a packet scheduling service that is specific to this queue, such as relative priority or allocated bandwidth. Although it cannot be expressed formally with the association cardinalities, there is an additional constraint on participation in this association. A particular instance of (a subclass of) SchedulingElement always participates either in exactly one instance of this association, or in exactly one instance of the association SchedulingServiceToSchedule.true1The queue and its QueuingService from which packets are emptied.trueThe SchedulingElement for the input queue. true2.7.0This is a top-level association, representing the relationship between a scheduler (PacketSchedulingService) and a SchedulingElement, in a configuration involving cascaded schedulers. The SchedulingElement, in turn, represents the information in a packet scheduling service that is specific to this scheduler, such as relative priority or allocated bandwidth. Although it cannot be expressed formally with the association cardinalities, there is an additional constraint on participation in this association. A particular instance of (a subclass of) SchedulingElement always participates either in exactly one instance of this association, or in exactly one instance of the association QueueToSchedule.true1The scheduler being cascaded.trueA SchedulingElement in the subsequent scheduler. true2.7.0This association represents the relationship between a PacketSchedulingService and the set of SchedulingElements that tie it to its inputs (either QueuingServices or other PacketSchedulingServices).truetrueGroupComponent1The scheduler aggregating the SchedulingElement. A SchedulingElement can be associated with at most one SchedulingService.truetruePartComponent1A SchedulingElement that ties either a queue or another scheduler to the referenced PacketSchedulingService. Every PacketSchedulingService MUST have at least one SchedulingElement/input.true 2.7.0The CIM_DatabaseSystem class is used to represent the application software portion of a database environment. A database environment is composed of a database system (the application software represented by this class), one or more database services, and one or more databases. See the descriptions of CIM_DatabaseService and CIM_CommonDatabase to get more detailed information about database services and databases. Many of the management capabilities needed to represent the software aspects of a database system have already been modeled in the CIM_ApplicationSystem class from which CIM_DatabaseSystem extends. This class provides a logical entity to define the relationships that are specific to the database management domain. 2.7.0A database is a collection of interrelated data, treated as a unit, which is organized into one or more schemas. The CIM_CommonDatabase class defines the properties that are common across database model and vendor implementations for the database entity that is represented by the unit of interrelated data. Databases are manipulated through one or more database services. More detailed information on database services is provided in the description of the CIM_DatabaseService 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'.The version number for the database. If the version is not relevant, the value for this property must be set to NULL.MIB.IETF|RDBMS-MIB.rdbmsDbInfoVersionThe date and time when the latest complete or partial backup of the database was performed. If the database has never been backed up, then this property has no meaning. The value of this property should be set to all zeros if the database has never been backed up.MIB.IETF|RDBMS-MIB.rdbmsDbInfoLastBackupThe estimated amount of disk space (in units) that has been reserved for database use.MIB.IETF|RDBMS-MIB.rdbmsDbInfoSizeAllocatedThe units for the SizeAllocated property and the SizeUsed property that is defined in the CIM_CommonDatabaseStatistics class. Mapping is 1 - Bytes, 2 - Kilobytes, 3 - Megabytes, 4 - Gigabytes and 5 - Terabytes.12345BytesKilobyesMegabytesGigabytesTerabytesMIB.IETF|RDBMS-MIB.rdbmsDbInfoSizeUnits 2.7.0The CIM_AssociatedDatabaseSystem association identifies the database system that is responsible for the database.trueAntecedent1The database system that is responsible for the database.trueDependentThe database.true 2.7.0The CIM_DatabaseAdministrator association identifies a CIM_UserEntity as a database administrator of a CIM_CommonDatabase.trueAntecedentThe database that is being administered.trueDependentThe user entity who is responsible for the administration of the database.true 2.7.0Database services perform tasks for a database. Examples of tasks that are performed by a database service include providing user access to the database, performing data and metadata manipulation, database administration, and maintenance operations. One or more database services can perform tasks for a database. The database services can reside on the same computer system as the database or on different computer systems. Database services may be implemented as one or more processes.The date and time when the database service was last started. If the database service has an OperationalStatus of Stopped or Starting, then this value is not meaningful and the contents MUST be set to zeros.MIB.IETF|RDBMS-MIB.rdbmsSrvInfoStartupTimeOperationalStatusThis property contains the operational status of the database service. OK means that the database service is operational and available for general use. Stopped means that the service is unavailable and cannot be used. Service implies an administrative state of unavailability. Degraded means that the database service is operating at a less than optimal level. Starting means that the database service is in the process of becoming operational. These status values map to the RFC1697 OperStatus values as follows: OK - UP, Stopped - DOWN, In Service - HALTED, Stressed - CONGESTED, and Starting - RESTARTING. Any additional status variables that are defined are CIM specific.MIB.IETF|RDBMS-MIB.rdbmsSrvInfoOperStatus01234567891011121314151617UnknownOtherOKDegradedStressedPredictive FailureErrorNon-Recoverable ErrorStartingStoppingStoppedIn ServiceNo ContactLost CommunicationAbortedDormantSupporting Entity in ErrorCompletedIndexedCIM_ManagedSystemElement.StatusDescriptionsThe date and time when the status of the database service last changed.MIB.IETF|RDBMS-MIB.rdbmsSrvInfoLastChangeThe maximum number of active inbound connections that can be concurrently opened on the service.MIB.IETF|RDBMS-MIB.rdbmsSrvInfoMaxInboundAssociations 2.7.0The CIM_ServiceAvailableToDatabase association relates databases to the database services that are available for database use.trueServiceProvidedThe database service that is providing service.trueUserOfServiceThe database that is being served.trueThe AvailableState property indicates the current state of a database service regarding its ability to access a specific database. A service can be actively using a database (ACTIVE), or it can be waiting for a task to perform (AVAILABLE), or the service can be less than completely available for use by the database (RESTRICTED), or the database is not accessible from this service (UNAVAILABLE). Any service states that do not match one of these values should specify (OTHER).12345OtherActiveAvailableRestrictedUnavailableMIB.IETF|RDBMS-MIB.rdbmsRelStateCIM_ServiceAvailableToDatabase.OtherAvailableStateA string describing the service's available state when the AvailableState property is set to 1 ("Other"). This property MUST be set to NULL when AvailableState is any value other than 1.CIM_ServiceAvailableToDatabase.AvailableStateThe time that the database was made active by this service. If the AvailableState property is not active, then the value of this property MUST be set to zero.MIB.IETF|RDBMS-MIB.rdbmsRelActiveTime true2.7.0The CIM_DatabaseParameter class extends from CIM_ScopedSettingData. This is an abstract class that specifies the database and service configuration parameters that are common across database models and vendor implementations. The SNMP RDBMS MIB defines database and service parameters as name/value pair combinations rather than as specific named properties of the class. In order to maintain a consistent mapping between SNMP and CIM a CIM_SNMPDatabaseParameter class extends from the abstract CIM_DatabaseParameter class which defines parameters as a name value pair. In a future release of the database MOF, the working group may choose to create a new class that extends from CIM_DatabaseParameter that specifies properties for common configuration parameters. The parameter context for a specific database or database service is established by collecting the SettingData using the CIM_ElementProfile association. The SNMP RDBMS MIB defines generic tables that contain rows of named database or service configuration entries. A parameter entry contains a parameter name, description, and value. See the description of the rdbmsDbParamTable or the rdbmsSrvParamTable for more information on the SNMP definitions. 2.7.0The CIM_SNMPDatabaseParameter class extends from CIM_DatabaseParameter. This class is included in the CIM database schema to provide explicit mapping to the way that the SNMP MIB defines database and service parameters. More information on the SNMP MIB parameters can be found in RFC 1697. The SNMP RDBMS MIB defines generic tables that contain rows of named database or service configuration entries. A parameter entry contains a parameter name, description, and value. See the description of the rdbmsDbParamTable or the rdbmsSrvParamTable for more information on the SNMP definitions.The value of a database or service parameter represented as a string.MIB.IETF|RDBMS-MIB.rdbmsDbParamCurrValue 2.7.0The CIM_DatabaseServiceStatistics class contains the current statistics for a database service. These are counters that are relative to the start of the service or from the time when a reset was issued.The date and time when the most recent inbound activity was observed for the database service. A value of all zeros indicates that no inbound activity has taken place since the service was started.MIB.IETF|RDBMS-MIB.rdbmsSrvInfoLastInboundActivitytrueThe number of active inbound connections that are currently using the service.MIB.IETF|RDBMS-MIB.rdbmsSrvInfoapplInboundAssociationtrueThe total number of inbound connections to the service since it was started.MIB.IETF|RDBMS-MIB.rdbmsSrvInfoapplAccumulatedInboundAssociationstrueThe total number of inbound connections that were rejected by the service since it was started.MIB.IETF|RDBMS-MIB.rdbmsSrvInfoapplRejectedInboundAssociationstrueThe total number of transactions that have been completed by a commit or abort. Some database operations, such as read-only queries, may not create a transaction.MIB.IETF|RDBMS-MIB.rdbmsSrvInfoFinishedTransactionstrueThe total number of database file reads that were issued by the service since it was started.MIB.IETF|RDBMS-MIB.rdbmsSrvInfoDiskReadstrueThe total number of database file writes that were issued by the service since it was started.MIB.IETF|RDBMS-MIB.rdbmsSrvInfoDiskWritestrueThe total number of logical database file reads that were issued by the service since it was started.MIB.IETF|RDBMS-MIB.rdbmsSrvInfoLogicalReadstrueThe total number of logical database file writes that were issued by the service since it was started. A logical write is a count of the number of times that parts of database files have been marked dirty to indicate that they need to be written to disk.MIB.IETF|RDBMS-MIB.rdbmsSrvInfoLogicalWritestrueThe total number of database pages that have been read by the service since it was started.MIB.IETF|RDBMS-MIB.rdbmsSrvInfoPageReadstrueThe total number of database pages that have been written by the service since it was started.MIB.IETF|RDBMS-MIB.rdbmsSrvInfoPageWritestrueThe total number of times the database requested disk space and it was not available since the service was started.MIB.IETF|RDBMS-MIB.rdbmsSrvInfoDiskOutOfSpacestrueThe total number of requests that have been received by the service since it was started.MIB.IETF|RDBMS-MIB.rdbmsSrvInfoHandledRequeststrueThe total number of receive operations made by the service during request processing since it was started.MIB.IETF|RDBMS-MIB.rdbmsSrvInfoRequestRecvstrueThe total number of send operations made by the service during request processing since it was started.MIB.IETF|RDBMS-MIB.rdbmsSrvInfoRequestsSenttrueThe maximum number of active inbound connections that have been concurrently using the service since it was started.MIB.IETF|RDBMS-MIB.rdbmsSrvInfoHighwaterInboundAssociations 2.7.0The CIM_CommonDatabaseStatistics class contains the current statistics for a database.The estimated amount of disk space (in units) that is currently used by the database.MIB.IETF|RDBMS-MIB.rdbmsDbInfoSizeUsed 2.7.0The CIM_DatabaseServiceStatistics class contains the current statistics for a database resource. This class maps to the database and server limited resource tables in the SNMP RDBMS MIB as defined in RFC 1697.trueThe current value of a limited database resource.MIB.IETF|RDBMS-MIB.rdbmsDbLimitedResourceCurrentThe maximum value that the database resource can attain.MIB.IETF|RDBMS-MIB.rdbmsDbLimitedResourceLimittrueThe number of database resources used measured from the time when the first service was started for the database. Other external factors, such as an explicit reset of the statistics may cause this measurement to begin at a later point in time.MIB.IETF|RDBMS-MIB.rdbmsDbLimitedResourceHighwatertrueThe number of times that the system wanted to exceed the database resource limit measured from the time when the first service was started for the database.MIB.IETF|RDBMS-MIB.rdbmsDbLimitedResourceFailures 2.6.0The DeviceConnection relationship indicates that two or more Device are connected together.trueAntecedentA LogicalDevice.trueDependentA second LogicalDevice connected to the Antecedent Device.trueWhen several bus and/or connection speeds are possible, the NegotiatedSpeed property defines the one in use between the Devices. Speed is specified in bits per second. If connection or bus speeds are not negotiated, or if this information is not available/important to Device management, the property should be set to 0.Bits per SecondMIF.DMTF|Bus Port Association|001.2When several bus and/or connection data widths are possible, the NegotiatedDataWidth property defines the one in use between the Devices. Data width is specified in bits. If data width is not negotiated, or if this information is not available/important to Device management, the property should be set to 0.BitsMIF.DMTF|Bus Port Association|001.3 2.6.0CIM_DeviceIdentity indicates that two LogicalDevices represent different aspects of the same underlying entity. This association refines the CIM_LogicalIdentity superclass by restricting it to the Device level and defining its use in well understood scenarios. One of these scenarios is to represent that a Device is both a 'bus' entity and a 'functional' entity. For example, a Device could be both a PCI Device (or a USB Device), as well as a CIM_Keyboard. The other scenario is where a Device plays multiple functional roles that can not be distinguished by their hardware realization alone. For example, a Fibre Channel adapter might have aspects of both a NetworkAdapter and a SCSIController.trueSystemElementSystemElement represents one aspect of the Device.trueSameElementSameElement represents an alternate aspect of the System entity.true 2.6.0A LogicalDevice is installed in a Package such as a Chassis or a Rack, not for a specific Device, but to function with the Package in general. This relationship is described by the PackageDependency association.trueAntecedentThe Logical Device for the Package.trueDependentThe PhysicalPackage whose environment is affected.true 2.6.0The DeviceSoftware relationship identifies any software that is associated with a Device - such as drivers, configuration or application software, or firmware.trueAntecedentThe SoftwareElement.trueDependentThe LogicalDevice that requires or uses the software.trueAn enumerated integer to indicate the role this software plays in regards to its associated Device. For example, this software could be instrumentation (value=5) or firmware (6).012345678UnknownOtherDriverConfiguration SoftwareApplication SoftwareInstrumentationFirmwareBIOSBoot ROMCIM_DeviceSoftware.PurposeDescriptionMIF.DMTF|SubComponent Software|001.2A free-form string to provide more information for the Purpose property, e.g. "Application Software".CIM_DeviceSoftware.PurposeBoolean indicating that the software is 'burned into' or otherwise located on the hardware of the LogicalDevice.Boolean indicating whether the software is upgradeable, when it is LoadedOnDevice. Software that is loaded as part of the OperatingSystem is typically changeable and upgradeable. However, when DeviceSoftware is burned into EEPROM or a chip that Realizes the LogicalDevice, then it may not be upgradeable. This property indicates the ability to update and upgrade DeviceSoftware. 2.7.0DeviceErrorCounts is a statistical class containing error-related counters for a LogicalDevice. The types of errors are as defined by CCITT (Rec X.733) and ISO (IEC 10164-4). Note that the CIM_DeviceErrorCountData class uses a simplified naming/identity algorithm as compared to this class. DeviceErrorCounts is not deprecated since its naming algorithm is still in use in various implementations.CIM_LogicalDevice.SystemCreationClassNametrue256The scoping System's CreationClassName. CIM_LogicalDevice.SystemNametrue256The scoping System's Name. CIM_LogicalDevice.CreationClassNametrue256The scoping Device's CreationClassName. CIM_LogicalDevice.DeviceIDtrue64The scoping Device's ID. Nametrue256The inherited Name serves as part of the key for the DeviceErrorCounts instance. The object is scoped by the LogicalDevice to which the statistics apply. Count of the indeterminate errors. trueCount of the critical errors. MIF.DMTF|Operational State|006.7trueCount of the major errors. MIF.DMTF|Operational State|006.8trueCount of the minor errors. trueCount of the warnings. MIF.DMTF|Operational State|006.9trueMethod to reset the error and warning counters. The method takes one parameter as input - an integer indicating which counter to reset. For this input parameter, 0 indicates all, 1 indicates a reset of the indeterminate error counter, 2 the critical error counter, 3 the major error counter, 4 the minor error counter and 5 the warning counter. 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 LogicalDevice's instrumentation, which tabulates the errors and warnings, can also reset its internal processing and counters. 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.true012345AllIndeterminate Error CounterCritical Error CounterMajor Error CounterMinor Error CounterWarning Counter 2.6.0ErrorCountersForDevice relates the DeviceErrorCounts class to the LogicalDevice to which it applies. trueStatstrueThe statistical object - in this case, the error counter class.trueElement11The Device to which the error counters apply. true 2.7.0DeviceErrorData is a statistical class containing error-related counters for a LogicalDevice. The types of errors are as defined by CCITT (Rec X.733) and ISO (IEC 10164-4).The element whose statistics are described is associated using the relationship, ElementStatisticalData. Note that this class uses a simplified identity/naming algorithm over CIM_DeviceErrorCounts.Count of the indeterminate errors. trueCount of the critical errors. MIF.DMTF|Operational State|006.7trueCount of the major errors. MIF.DMTF|Operational State|006.8trueCount of the minor errors. trueCount of the warnings. MIF.DMTF|Operational State|006.9true 2.6.0Capabilities and management of CoolingDevices.ActiveCooling is a boolean indicating that the CoolingDevice provides active (as opposed to passive) cooling. 2.6.0Capabilities and management of a Refrigeration CoolingDevice. 2.6.0Capabilities and management of a HeatPipe CoolingDevice. 2.6.0Capabilities and management of a Fan CoolingDevice.Indication of whether the fan supports variable speeds.DesiredSpeed is the currently requested fan speed, defined in Revolutions per Minute, when a variable speed fan is supported (VariableSpeed boolean = TRUE). The current speed is determined via a sensor (CIM_Tachometer) that is associated with the Fan using the CIM_AssociatedSensor relationship.Revolutions per MinuteRequests that the Fan speed be set to the value specified in the method's input parameter. 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.true 2.6.0Many Devices, such as processors or power supplies, require their own cooling devices. This association indicates where fans or other CoolingDevices are specific to a Device, versus providing enclosure or cabinet cooling.trueAntecedentThe CoolingDevice.trueDependentThe LogicalDevice being cooled.true 2.7.0Capabilities and management of the Battery LogicalDevice. This class applies to both batteries in Laptop Systems and other internal/external batteries, such as used in, or as UPSs.Description of the Battery's charge status. Values such as "Fully Charged" (value=3) or "Partially Charged" (11) can be specified. The value, 10, is not valid in the CIM Schema since in DMI it represents that no battery is installed. In this case, this object should not be instantiated.1234567891011OtherUnknownFully ChargedLowCriticalChargingCharging and HighCharging and LowCharging and CriticalUndefinedPartially ChargedMIF.DMTF|Portable Battery|003.14TimeOnBattery indicates the elapsed time in seconds since the ComputerSystem, UPS, ... last switched to battery power, or the time since the System or UPS was last restarted, whichever is less. Zero shall be returned if the Battery is 'on line'.SecondsEstimatedRunTime is an estimate in minutes of the time to battery charge depletion under the present load conditions if the utility power is off, or lost and remains off, or a Laptop is disconnected from a power source.MinutesMIF.DMTF|Portable Battery|003.15trueAn estimate of the percentage of full charge remaining.PercentAn enumeration that describes the Battery's chemistry.12345678OtherUnknownLead AcidNickel CadmiumNickel Metal HydrideLithium-ionZinc airLithium PolymerMIF.DMTF|Portable Battery|003.7The design capacity of the battery in mWatt-hours. If this property is not supported, enter 0.MilliWattHoursMIF.DMTF|Portable Battery|003.8The full charge capacity of the battery in mWatt-hours. Comparison of this value to the Battery DesignCapacity determines when the Battery requires replacement. A Battery's end of life is typically when the FullChargeCapacity falls below 80% of the DesignCapacity. If this property is not supported, enter 0.MilliWattHoursMIF.DMTF|Portable Battery|003.11The design voltage of the battery in mVolts. If this attribute is not supported, enter 0.MilliVoltsMIF.DMTF|Portable Battery|003.964The Smart Battery Data Specification version number supported by this Battery. If the Battery does not support this function, the value should be left blank.MIF.DMTF|Portable Battery|003.10The remaining time to charge the battery fully in minutes at the current charging rate and usage.MinutesMIF.DMTF|Portable Battery|003.16Indicates the Battery's expected lifetime in minutes, assuming that the Battery is fully charged. This property represents the total expected life of the Battery, not its current remaining life, which is indicated by the EstimatedRunTime property. MinutesMaxRechargeTime indicates the maximum time, in minutes, to fully charge the Battery. This property represents the time to recharge a fully depleted Battery, not the current remaining charging time, which is indicated in the TimeToFullCharge property. Minutes 2.6.0A LogicalDevice may use or require one or more Batteries. This relationship is described by the AssociatedBattery dependency. It is also possible to model the individual Batteries that comprise a UPS, using this association.trueAntecedentThe Battery.trueDependentThe LogicalDevice needing or associated with the Battery.true 2.7.0Capabilities and management of the PowerSupply LogicalDevice.Boolean indicating that the PowerSupply is a switching (vs linear) supply.The low voltage of Input Voltage Range 1 for this PowerSupply, in millivolts. A value of 0 denotes 'unknown'.MilliVoltsMIF.DMTF|Power Supply|004.7The high voltage of Input Voltage Range 1 for this PowerSupply, in millivolts. A value of 0 denotes 'unknown'.MilliVoltsMIF.DMTF|Power Supply|004.8The frequency (in Hertz) at the low end of this PowerSupply's Input Frequency Range 1. A value of zero implies DC.HertzMIF.DMTF|Power Supply|004.17The frequency (in Hertz) at the high end of this PowerSupply's Input Frequency Range 1. A value of zero implies DC.HertzMIF.DMTF|Power Supply|004.18The low voltage of Input Voltage Range 2 for this PowerSupply, in millivolts. A value of 0 denotes 'unknown'.MilliVoltsMIF.DMTF|Power Supply|004.11The high voltage of Input Voltage Range 2 for this PowerSupply, in millivolts. A value of 0 denotes 'unknown'.MilliVoltsMIF.DMTF|Power Supply|004.12The frequency (in Hertz) at the low end of this PowerSupply's Input Frequency Range 2. A value of zero implies DC.HertzMIF.DMTF|Power Supply|004.19The frequency (in Hertz) at the high end of this PowerSupply's Input Frequency Range 2. A value of zero implies DC.HertzMIF.DMTF|Power Supply|004.20ActiveInputVoltage indicates which input voltage range is currently in use. Range 1, 2 or both can be specified using the values 3, 4 or 5, respectively. If the Supply is not currently drawing power, the value 6 ("Neither") can be specified. This information is necessary in the case of a UPS, a subclass of PowerSupply.123456OtherUnknownRange 1Range 2BothNeitherMIF.DMTF|Power Supply|004.15TypeOfRangeSwitching describes the kind of input voltage range switching implemented in this PowerSupply. For example, autoswitching can be specified (value=4).123456OtherUnknownManualAutoswitchWide RangeNot ApplicableMIF.DMTF|Power Supply|004.16Represents the total output power of the PowerSupply in milliWatts. 0 denotes 'unknown'.MilliWattsMIF.DMTF|Power Supply|004.21 2.6.0The SuppliesPower relationship indicates that a Device is in the power domain of the referenced PowerSupply or UPS. It indicates which Device(s) are dependent on the PowerSupply, and hence, which Devices are affected if the Supply is lost.trueAntecedentThe Supply providing power.trueDependentA LogicalDevice in the power domain of the Supply.true 2.6.0Capabilities and management of an UninterruptiblePowerSupply. The properties of the UPS Device indicate when incoming power is trimmed or boosted, and the aggregated information of the batteries, generators, etc. that comprise the Device. These individual components (for example, multiple batteries) can also be independently modeled and associated with the UPS.Range1InputVoltageLowIf the voltage (in millivolts) drops below the value specified by Range1InputVoltageLow, the UPS will compensate by boosting the voltage using its power source(s). A value of 0 indicates that the voltage at which boosting occurs is 'unknown'.MilliVoltsMIF.DMTF|Power Supply|004.7Range1InputVoltageHighIf the voltage (in millivolts) rises above the value specified by Range1InputVoltageHigh, the UPS will compensate by trimming the voltage. A value of 0 indicates that the voltage at which trimming occurs is 'unknown'.MilliVoltsMIF.DMTF|Power Supply|004.8Range2InputVoltageLowIf the voltage (in millivolts) drops below the value specified by Range2InputVoltageLow, the UPS will compensate by boosting the voltage using its power source(s). A value of 0 indicates that the voltage at which boosting occurs is 'unknown'.MilliVoltsMIF.DMTF|Power Supply|004.11Range2InputVoltageHighIf the voltage (in millivolts) rises above the value specified by Range2InputVoltageHigh, the UPS will compensate by trimming the voltage. A value of 0 indicates that the voltage at which trimming occurs is 'unknown'.MilliVoltsMIF.DMTF|Power Supply|004.12The indication of the capacity remaining in the UPS' batteries, generator, ... A value of "Normal" (2) indicates that the remaining estimated minutes of run-time is greater than the UPS' defined 'low power' state (typically two minutes). A value of "Low" (3) indicates that the remaining estimated minutes of run-time is less than or equal to the UPS' defined 'low power' state. A value of "Depleted" (4) indicates that the UPS will be unable to sustain the present load when and if the utility power is lost (including the possibility that the utility power is currently absent).1234UnknownNormalLowDepletedMIF.DMTF|UPS Battery|001.1TimeOnBackup indicates the elapsed time in seconds since the UPS last switched to battery power, generator, ... Or, the time since the UPS was last restarted, whichever is less. Zero shall be returned if the UPS is 'on line'.SecondsMIF.DMTF|UPS Battery|001.2EstimatedRunTime is an estimate in minutes of the time to battery, generator, ... depletion under the present load conditions if the utility power is off, or lost and remains off.MinutesMIF.DMTF|UPS Battery|001.3trueAn estimate of the percentage of full charge remaining for a UPS (that uses battery technology).PercentMIF.DMTF|UPS Battery|001.4 2.7.0CIM_PackageDependencyOften, a CoolingDevice is installed in a Package such as a Chassis or a Rack, not for a specific Device, but to assist in the cooling of the Package in general. The use of this association has been deprecated. Instead, the more generic PackageDependency relationship should be used.trueCIM_PackageDependency.AntecedentThe CoolingDevice for the Package.AntecedenttrueCIM_PackageDependency.DependentThe PhysicalPackage whose environment is cooled.Dependenttrue 2.7.0CIM_Watchdog is a timer implemented in system hardware. It allows the hardware to monitor the state of the OperatingSystem, BIOS or a software component installed on the System. If the monitored component fails to re-arm the timer before its expiration, the hardware assumes that the System is in a critical state, and could reset the ComputerSystem. This feature can also be used as an application watchdog timer for a mission-critical application. In this case, the application would assume responsibility for re-arming the timer before expiration.The entity that is currently being monitored by the WatchDog. This property is used to identify the module that is responsible for or whose information is used to re-arm the watchdog at periodic intervals.012345678UnknownOtherOperating SystemOperating System Boot ProcessOperating System Shutdown ProcessFirmware Boot ProcessBIOS Boot ProcessApplicationService Processor256A string describing more textual information about the monitored entity.The timeout interval used by the watchdog, in MicroSeconds.MicroSecondsResolution of the timer. For example, if this value is 100, then the timer can expire anytime between (TimeoutInterval-100) microseconds or (TimeoutInterval+100) microseconds.MicroSecondsThe time of the last timer expiry.Monitored entity at the time of last timer expiry.012345678UnknownOtherOperating SystemOperating System Boot ProcessOperating System Shutdown ProcessFirmware Boot ProcessBIOS Boot ProcessApplicationService ProcessorThe action that should happen upon the expiry of the watchdog.012345None - Status OnlySystem ResetSystem Power OffSystem Power Off, then OnGenerate System NonMaskableInterrupt (NMI)Generate System Management Interrupt (SMI)A method to re-arm the timer. This method is only used if the MonitoredEntity is "Application". It returns 0 if successful, 1 if unsupported, and any 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. 2.7.0Capabilities and management of the Processor LogicalDevice.A free form string describing the role of the Processor - for example, "Central Processor" or "Math Processor".The Processor family type. For example, values include "Pentium(R) processor with MMX(TM) technology" (14) and "68040" (96).1234567891011121314151617181924252627282930313233343536373839484950515253545564656667686980818283848586878896979899100101112120121128130144145146147148149150160176177178179180181182183184185190200201202203204250251260261280281300301302320350500OtherUnknown80868028680386804868087802878038780487Pentium(R) brandPentium(R) ProPentium(R) IIPentium(R) processor with MMX(TM) technologyCeleron(TM)Pentium(R) II Xeon(TM)Pentium(R) IIIM1 FamilyM2 FamilyK5 FamilyK6 FamilyK6-2K6-3AMD Athlon(TM) Processor FamilyAMD(R) Duron(TM) ProcessorAMD29000 FamilyK6-2+Power PC FamilyPower PC 601Power PC 603Power PC 603+Power PC 604Power PC 620Power PC X704Power PC 750Alpha FamilyAlpha 21064Alpha 21066Alpha 21164Alpha 21164PCAlpha 21164aAlpha 21264Alpha 21364MIPS FamilyMIPS R4000MIPS R4200MIPS R4400MIPS R4600MIPS R10000SPARC FamilySuperSPARCmicroSPARC IImicroSPARC IIepUltraSPARCUltraSPARC IIUltraSPARC IIiUltraSPARC IIIUltraSPARC IIIi6804068xxx Family68000680106802068030Hobbit FamilyCrusoe(TM) TM5000 FamilyCrusoe(TM) TM3000 FamilyWeitekItanium(TM) ProcessorPA-RISC FamilyPA-RISC 8500PA-RISC 8000PA-RISC 7300LCPA-RISC 7200PA-RISC 7100LCPA-RISC 7100V30 FamilyPentium(R) III Xeon(TM)Pentium(R) III Processor with Intel(R) SpeedStep(TM) TechnologyPentium(R) 4Intel(R) Xeon(TM)AS400 FamilyIntel(R) Xeon(TM) processor MPAMD Athlon(TM) XP FamilyAMD Athlon(TM) MP FamilyIntel(R) Itanium(R) 2Intel(R) Pentium(R) 4 processor with HT TechnologyK7S/390 and zSeries FamilyESA/390 G4ESA/390 G5ESA/390 G6z/Architectur basei860i960SH-3SH-4ARMStrongARM6x86MediaGXMIIWinChipDSPVideo ProcessorMIF.DMTF|Processor|017.3CIM_Processor.OtherFamilyDescription64A string describing the Processor Family type - used when the Family property is set to 1 ("Other"). This string should be set to NULL when the Family property is any value other than 1.CIM_Processor.FamilyCPU socket information including data on how this Processor can be upgraded (if upgrades are supported). This property is an integer enumeration.1234567891011121314151617OtherUnknownDaughter BoardZIF SocketReplacement/Piggy BackNoneLIF SocketSlot 1Slot 2370 Pin SocketSlot ASlot MSocket 423Socket A (Socket 462)Socket 478Socket 754Socket 940MIF.DMTF|Processor|017.7The maximum speed (in MHz) of this Processor.MegaHertzMIF.DMTF|Processor|017.5The current speed (in MHz) of this Processor.MegaHertzMIF.DMTF|Processor|017.6Processor data width in bits.BitsProcessor address width in bits.BitstrueLoading of this Processor, averaged over the last minute, in Percent.PercentMIB.IETF|HOST-RESOURCES-MIB.hrProcessorLoadStepping is a free-form string indicating the revision level of the Processor within the Processor.Family.CIM_Processor.FamilyA globally unique identifier for the Processor. This identifier may only be unique within a Processor Family.The CPUStatus property indicates the current status of the Processor. For example, it may be disabled by the user via BIOS (value=2), or disabled due to a POST error (value=3). Information in this property can be obtained from SMBIOS, the Type 4 structure, the Status attribute.012347UnknownCPU EnabledCPU Disabled by User via BIOS SetupCPU Disabled By BIOS (POST Error)CPU Is IdleOther CIM_SystemDevice2.7.0Association indicating the processor(s) of a UnitaryComputerSystem. ComputerSystemProcessor is depreacted in lieu of its superclass, SystemDevice, since it adds no detail and changes none of the cardinalities in the superclass' definition.truetruetrueCIM_SystemDevice.GroupComponentThe UnitaryComputerSystem.11GroupComponenttruetrueCIM_SystemDevice.PartComponentThe Processor which is part of the UnitaryComputerSystem.truePartComponenttrue true2.7.0Controller is a superclass for grouping the miscellaneous control-related Devices that exist. Examples of Controllers are SCSIControllers, USBControllers, SerialControllers, ... The Controller class is an abstraction for Devices with a single protocol stack, which exist to control communications (data, control, and reset) with devices.Time of last reset of the Controller.The protocol used by the Controller to access 'controlled' Devices.1234567891011121314151617181920212223242526272829303132333435363738394041424344454647OtherUnknownEISAISAPCIATA/ATAPIFlexible Diskette1496SCSI Parallel InterfaceSCSI Fibre Channel ProtocolSCSI Serial Bus ProtocolSCSI Serial Bus Protocol-2 (1394)SCSI Serial Storage ArchitectureVESAPCMCIAUniversal Serial BusParallel ProtocolESCONDiagnosticI2CPowerHIPPIMultiBusVMEIPIIEEE-488RS232IEEE 802.3 10BASE5IEEE 802.3 10BASE2IEEE 802.3 1BASE5IEEE 802.3 10BROAD36IEEE 802.3 100BASEVGIEEE 802.5 Token-RingANSI X3T9.5 FDDIMCAESDIIDECMDST506DSSIQIC2Enhanced ATA/IDEAGPTWIRP (two-way infrared)FIR (fast infrared)SIR (serial infrared)IrBusMIF.DMTF|Bus Port|004.2MIF.DMTF|Disks|003.3CIM_Controller.ProtocolDescriptionMaximum number of directly addressable entities supported by this Controller. A value of 0 should be used if the number is unknown or unlimited.MIF.DMTF|Bus Port|004.9A free form string providing more information related to the ProtocolSupported by the Controller.CIM_Controller.ProtocolSupportedMIF.DMTF|Bus Port|004.3 2.7.0The association indicates a relationship between a StorageVolume exposed as a LUN through a slave SCSI Controller. A new relationship is required in order to distinguish between the 'Host' connection (represented by SCSIInterface) and the 'Target' connection (represented by SCSILUN).trueThe Controller.AntecedenttrueThe controlled Device.DependenttrueThe State property indicates whether the Controller is actively commanding or accessing the Device (value=1) or not (value=2). Also, the value, "Unknown" (0), can be defined. This information is necessary when a LogicalDevice can be commanded by, or accessed through, multiple Controllers.012UnknownActiveInactiveThe time that the downstream Device was last reset by the Controller.Number of hard resets issued by the Controller. A hard reset returns the Device to its initialization or 'boot-up' state. All internal Device state information and data are lost.trueNumber of soft resets issued by the Controller. A soft reset does not completely clear current Device state and/or data. Exact semantics are dependent on the Device, and on the protocols and mechanisms used to communicate to it.true 2.6.0Capabilities and management of an ESCONController. 2.6.0Capabilities and management of an IDEController. 2.6.0Capabilities and management of an InfraredController. 2.6.0Capabilities and managment of a ManagementController. An I2C microcontroller is a type of ManagementController. 2.6.0Capabilities and management of the ParallelController.Set to true if the ParallelController supports DMA.MIF.DMTF|Parallel Ports|003.7An integer enumeration indicating the capabilities of the ParallelController.Indexed012345678UnknownOtherXT/AT CompatiblePS/2 CompatibleECPEPPPC-98PC-98-HiresoPC-H98MIF.DMTF|Parallel Ports|003.8CIM_ParallelController.CapabilityDescriptionsAn array of free-form strings providing more detailed explanations for any of the ParallelController features indicated in the Capabilities array. Note, each entry of this array is related to the entry in the Capabilities array that is located at the same index.IndexedCIM_ParallelController.CapabilitiesAn enumeration indicating the operational security for the Controller. For example, information that the Device's external interface is locked out (value=4) or "Boot Bypass" (value=6) can be described using this property.123456OtherUnknownNoneExternal Interface Locked OutExternal Interface EnabledBoot BypassMIF.DMTF|Parallel Ports|003.10 2.6.0Capabilities and management of a PCMCIAController. 2.7.0Capabilities and management of the SCSIController.An integer enumeration indicating whether or not the SCSIController provides redundancy or protection against device failures.123456OtherUnknownUnprotectedProtectedProtected through SCC (SCSI-3 Controller Command)Protected through SCC-2 (SCSI-3 Controller Command)MIF.DMTF|Storage Controller|001.3Maximum data width (in bits) supported by the SCSIController.BitsMIF.DMTF|Bus Port|004.7Maximum transfer rate (in Bits per Second) supported by the SCSIController.Bits per SecondMIF.DMTF|Bus Port|004.8Number of SCSIController timeouts that have occurred since the TimeOfLastReset.trueSignal capabilities that can be supported by the SCSIController. For example, the Controller may support "Single Ended" and "Differential". In this case, the values 3 and 4 would be written to the SignalCapabilities array.123456OtherUnknownSingle EndedDifferentialLow Voltage DifferentialOpticalCIM_SCSIInterface.SCSISignal 2.7.0SCSIInterface is a ControlledBy relationship indicating which Devices are accessed through a SCSIController and the characteristics of this access.trueThe SCSIController.AntecedenttrueNumber of SCSI timeouts that have occurred since last hard or soft reset related to the controlled Device. The time of last reset is indicated in the TimeOfDeviceReset property, inherited from the ControlledBy association.trueNumber of SCSI retries that have occurred since last hard or soft reset related to the controlled Device. The time of last reset is indicated in the TimeOfDeviceReset property, inherited from the ControlledBy association.trueMIF.DMTF|Mass Storage Statistics|001.18The SCSI Initiator ID.MIF.DMTF|Bus Port|004.5The SCSI Target ID.MIF.DMTF|Bus Port|004.5The SCSI Target LUN.MIF.DMTF|Storage Devices|001.4SCSIReservation indicates the type of SCSI reservation that currently exists between the source and destination.0123UnknownNoneSimplePersistentThe SCSI signal characteristics being used for this connection. The value listed here must also be listed in the SCSIController's SignalCapabilities field.123456OtherUnknownSingle EndedDifferentialLow Voltage DifferentialOpticalMIF.DMTF|Bus Port|004.4CIM_SCSIController.SignalCapabilitiesMaximum number of Command Descriptor Blocks (CDBs) that can be supported by the target. This data can not be obtained under all circumstances.The maximum number of concurrent Command Descriptor Blocks (CDBs) that the initiator will send to the target. This value should never be greater than MaxQueueDepth. 2.6.0Capabilities and management of the SerialController.The Capabilities property defines chip level compatibility for the SerialController. Therefore, this property describes the buffering and other capabilities of the SerialController, that may be inherent in the chip hardware. The property is an enumerated integer.Indexed123456160161OtherUnknownXT/AT Compatible16450 Compatible16550 Compatible16550A Compatible8251 Compatible8251FIFO CompatibleMIF.DMTF|Serial Ports|004.7CIM_SerialController.CapabilityDescriptionsAn array of free-form strings providing more detailed explanations for any of the SerialController features indicated in the Capabilities array. Note, each entry of this array is related to the entry in the Capabilities array that is located at the same index.IndexedCIM_SerialController.CapabilitiesMaximum baud rate in Bits per Second supported by the SerialController.Bits per SecondMIF.DMTF|Serial Ports|004.6An enumeration indicating the operational security for the Controller. For example, information that the Device's external interface is locked out (value=4) or "Boot Bypass" (value=6) can be described using this property.123456OtherUnknownNoneExternal Interface Locked OutExternal Interface EnabledBoot BypassMIF.DMTF|Serial Ports|004.9 2.6.0SerialInterface is a ControlledBy relationship indicating which Devices are accessed through the SerialController and the characteristics of this access.trueThe SerialController.AntecedenttrueNegotiatedDataWidthFor the SerialInterface, NegotiatedDataWidth is the number of data bits to be transmitted, without stop bits or parity.BitsMIF.DMTF|Bus Port Association|001.3Number of stop bits to be transmitted.BitsInformation on the parity setting for transmitted data. No parity (value=1), even (2) or odd (3) can be specified.0123UnknownNoneEvenOddAn integer enumeration indicating the flow control (Xon-Xoff and/or RTS/CTS) for transmitted data.012345UnknownNot SupportedNoneXonXoffRTS/CTSBoth XonXoff and RTS/CTS 2.6.0Capabilities and management of an SSAController (Serial Storage Architecture). 2.6.0Capabilities and managment of a USB Host Controller.Indicates the latest USB Version supported by the Controller. The property is expressed as a Binary-Coded Decimal (BCD) where a decimal point is implied between the 2nd and 3rd digits. For example, a value of 0x201 indicates that version 2.01 is supported.The type of interface used between the host system software and the USBController.0123UnknownOtherUHCIOHCICIM_USBController.ControllerVersionIndicates the version of the USB Host Controller register set, specific to the InterfaceType. The property is expressed as a Binary-Coded Decimal (BCD) value where a decimal point is implied between the 2nd and 3rd digits. For example, a value of 0x103 indicates that version 1.03 is supported.CIM_USBController.InterfaceType 2.7.0Capabilities and management of the VideoController.DescriptionMIF.DMTF|Video|004.18The Description property provides a textual description of the object.A free-form string describing the video processor/Controller.An integer enumeration indicating the type of video memory.12345678910111213OtherUnknownVRAMDRAMSRAMWRAMEDO RAMBurst Synchronous DRAMPipelined Burst SRAMCDRAM3DRAMSDRAMSGRAMMIF.DMTF|Video|004.6Number of video pages supported given the current resolutions and available memory.Maximum amount of memory supported in bytes.BytesAn array of integers indicating the graphics and 3D capabilities of the VideoController.012345678UnknownOtherGraphics Accelerator3D AcceleratorPCI Fast WriteMultiMonitor SupportPCI MasteringSecond Monochrome Adapter SupportLarge Memory Address SupportCIM_VideoController.CapabilityDescriptionsAn array of free-form strings providing more detailed explanations for any of the video Accelerator features indicated in the Capabilities array. Note, each entry of this array is related to the entry in the Capabilities array that is located at the same index.IndexedCIM_VideoController.AcceleratorCapabilitiesThe number of bits used to display each pixel.BitsMIF.DMTF|Video|004.12Current number of horizontal pixels.PixelsMIF.DMTF|Video|004.11Current number of vertical pixels.PixelsMIF.DMTF|Video|004.10Maximum refresh rate of the VideoController in Hertz.HertzMIF.DMTF|Video|004.5Minimum refresh rate of the Video Controller in Hertz.HertzMIF.DMTF|Video|004.4Current refresh rate in Hertz.HertzMIF.DMTF|Video|004.15Current scan mode. "Interlaced" (value=3) or "Non Interlaced" (4) can be defined using this property.1234OtherUnknownInterlacedNon InterlacedMIF.DMTF|Video|004.8If in character mode, number of rows for this VideoController. Otherwise, enter 0.MIF.DMTF|Video|004.13If in character mode, number of columns for this VideoController. Otherwise, enter 0.MIF.DMTF|Video|004.14Number of colors supported at the current resolutions. 2.6.0Capabilities and management of a PCVideoController, a subtype of VideoController.The video architecture. For example, VGA (value=5) or PC-98 (160) may be specified.123456789101112160OtherUnknownCGAEGAVGASVGAMDAHGCMCGA8514AXGALinear Frame BufferPC-98MIF.DMTF|Video|004.2Current video mode.MIF.DMTF|Video|004.3Current number of color planes. If this value is not applicable for the current video configuration, enter 0. 2.7.0Capabilities and management of an AGPVideoController.VideoController.AcceleratorCapabilitiesThis property has been incorporated into the inherited AcceleratorCapabilities property. Capabilities of the AGP Graphics Controller. For example, the Device may support multiple monitors, PCI Mastering and large memory addresses. In this case, the values 3, 4 and 6 would be written to the Capabilities array.Indexed0123456UnknownOtherPCI Fast WriteMultiMonitor SupportPCI MasteringSecond Monochrome Adapter SupportLarge Memory Address SupportCIM_AGPVideoController.CapabilityDescriptionsSize of the non-local video memory in KB.KiloBytesWidth of the internal bus in the graphics Controller, in bits.BitsAn integer enumeration indicating the usage model of the graphics Controller. Usage model indicates how the Controller does manipulations of graphics surfaces, textures, etc. in memory. DMA indicates that the graphics Controller brings structures from the system memory to its local memory to perform needed manipulations or renderings. Execute specifies that the graphics Controller can directly access a specified region in main memory (called the graphics aperture) using GART - Graphics Aperture Remapping Table. It then performs manipulations in that range as if that whole graphics aperture were part of its local memory. A value of "Both" DMA and Execute models may also be specified.01234UnknownOtherExecuteDMABothAn integer enumeration indicating the data transfer rate of the graphics Controller.01234UnknownOther1X2X4XAn integer enumeration indicating the addressing mode of the graphics Controller.0123UnknownOtherSidebandPipelineThe maximum number of AGP Transaction requests that the master (AGP Graphics Controller) is allowed to enqueue into the target.The number of AGP Transaction that the core logic (chipset) can accept into its transaction request queue from the Controller.Size of the graphics aperture in KB.KiloBytesA string containing the AGP specification version to which this graphics Controller conforms. 2.6.0VideoControllerResolution describes the various video modes that a VideoController can support. Video modes are defined by the possible horizontal and vertical resolutions, refresh rate, scan mode and number of colors settings supported by a Controller. The actual resolutions, etc. that are in use, are the values specified in the VideoController object.SettingIDtrue256The inherited SettingID serves as part of the key for a VideoControllerResolution instance.Controller's horizontal resolution in Pixels.PixelsCIM_VideoController.CurrentHorizontalResolutionMIF.DMTF|Monitor Resolutions|002.2Controller's vertical resolution in Pixels.PixelsCIM_VideoController.CurrentVerticalResolutionMIF.DMTF|Monitor Resolutions|002.3Refresh rate in Hertz. If a range of rates is supported, use the MinRefreshRate and MaxRefreshRate properties, and set RefreshRate (this property) to 0.HertzCIM_VideoController.CurrentRefreshRateMIF.DMTF|Monitor Resolutions|002.4Minimum refresh rate in Hertz, when a range of rates is supported at the specified resolutions.HertzCIM_VideoController.MinRefreshRateMIF.DMTF|Monitor Resolutions|002.6Maximum refresh rate in Hertz, when a range of rates is supported at the specified resolutions.HertzCIM_VideoController.MaxRefreshRateMIF.DMTF|Monitor Resolutions|002.7Integer indicating whether the Controller operates in interlaced (value=5) or non-interlaced (4) mode.12345OtherUnknownNot SupportedNon-Interlaced OperationInterlaced OperationCIM_VideoController.CurrentScanModeMIF.DMTF|Monitor Resolutions|002.5Number of colors supported at the current resolutions.CIM_VideoController.CurrentNumberOfColors 2.6.0VideoSetting associates the VideoControllerResolution Setting with the Controller(s) to which it applies.trueElementThe VideoController.trueSettingThe resolutions, refresh rates, scan mode and number of colors that can be set for the Controller.true 2.6.0PCIController is a superclass for the PCIBridge and PCIDevice classes. These classes model adapters and bridges on a PCI bus. The properties in PCIController and its subclasses are defined in the various PCI Specifications published by the PCI SIG.Current contents of the register that provides basic control over the device's ability to respond to, and/or perform PCI accesses.An array of integers indicating controller capabilities. Information such as "Supports 66MHz" (value=2) is specified in this property. The data in the Capabilities array is gathered from the PCI Status Register and the PCI Capabilities List as defined in the PCI Specification.Indexed0123456789101112UnknownOtherSupports 66MHzSupports User Definable FeaturesSupports Fast Back-to-Back TransactionsPCI-X CapablePCI Power Management SupportedMessage Signaled Interrupts SupportedParity Error Recovery CapableAGP SupportedVital Product Data SupportedProvides Slot IdentificationHot Swap SupportedCIM_PCIController.CapabilityDescriptionsAn array of free-form strings providing more detailed explanations for any of the PCIController features indicated in the Capabilities array. Note, each entry of this array is related to the entry in the Capabilities array that is located at the same index.IndexedCIM_PCIController.CapabilitiesThe slowest device select timing for a target device.012345UnknownOtherFastMediumSlowReservedRegister of 8 bits that identifies the basic function of the PCI device. This is only the upper byte (offset 0Bh) of the 3 byte ClassCode field. Note that the property's ValueMap array specifies the decimal representation of this information.0123456789101112131415161718..254255Pre 2.0Mass StorageNetworkDisplayMultimediaMemoryBridgeSimple CommunicationsBase PeripheralInputDocking StationProcessorSerial BusWirelessIntelligent I/OSatellite CommunicationEncryption/DecryptionData Acquisition and Signal ProcessingPCI ReservedOtherSpecifies the system cache line size in doubleword increments (e.g., a 486-based system would store the value 04h, indicating a cache line size of four doublewords.DoubleWordsDefines the minimum amount of time, in PCI clock cycles, that the bus master can retain ownership of the bus.PCI clock cyclesDefines the PCI interrupt request pin (INTA# to INTD#) to which a PCI functional device is connected.012345NoneINTA#INTB#INTC#INTD#UnknownDoubleword Expansion ROM base memory address.DoubleWordsReports if the PCI device can perform the self test function. Returns bit 7 of the BIST register as a boolean.Method to invoke PCI device self-test. This method sets bit 6 of the BIST register. The return result is the lower four bits of the BIST register where 0 indicates success and non-zero is a device dependent failure. Support for this method is optional in the PCI Specification. 2.6.0Capabilities and management of a PCI device controller on an adapter card.Array of doubleword base memory addresses.Subsystem identifier code.Subsystem vendor ID. ID information is reported from a PCIDevice via protocol-specific requests. The correct place in the CIM Schema for this information is in CIM_PhysicalElement (the Manufacturer property) for hardware, and CIM_Product (the Vendor property) if the information is related to Product acquisition. This data is also reported here since it is part of the standard output from the Device, and as an optimization.Register indiating how long the master would like to retain PCI bus ownership whenever it initiates a transaction. A zero value indicates no requirement.250 nanosecondsRegister specifying how often the device needs access to the PCI bus in 250ns. A zero value indicates no requirement.250 nanoseconds 2.6.0Capabilities and management of a PCI controller providing bridge to bridge capability.Array of doubleword base memory addresses.The type of bridge. Except for "Host" (value=0), the type of bridge is PCI to <value>. For type "Host", the device is a Host to PCI bridge.012345678128HostISAEISAMicro ChannelPCIPCMCIANuBusCardBusRACEwayOtherThe timeslice for the secondary interface when the bridge is acting as an initiator. A zero value indicates no requirement.PCI clock cyclesThe number of the highest numbered bus that exists behind the bridge.The number of the PCI bus segment to which the secondary interface of the bridge is connected.The number of the PCI bus segment to which the primary interface of the bridge is connected.The contents of the Bridge's SecondaryStatusRegister. For more information on the contents of this register, refer to the PCI-to-PCI Bridge Architecture Specification.The slowest device select timing for a target device on the secondary bus.012345UnknownOtherFastMediumSlowReservedEnd address of the I/O addresses supported by the bus. The upper four bits of this property specify the address bits, AD[15::12], of the I/O address. The remaining 12 bits of the I/O address are assumed to be all 1's.Base address of I/O addresses supported by the bus. The upper four bits of this property specify the address bits, AD[15::12], of the I/O address. The remaining 12 bits of the I/O address are assumed to be 0.End address of the memory supported by the bus. The upper twelve bits of this property specify the address bits, AD[31::20], of a 32-bit memory address. The remaining 20 bits of the address are assumed to be all 1's.Base address of the memory supported by the bus. The upper twelve bits of this property specify the address bits, AD[31::20], of a 32-bit memory address. The remaining 20 bits of the address are assumed to be 0.End address of the memory that can be prefetched by the bus. The upper twelve bits of this property specify the address bits, AD[31::20], of a 32-bit memory address. The remaining 20 bits of the address are assumed to be all 1's.Base address of the memory that can be prefetched by the bus. The upper twelve bits of this property specify the address bits, AD[31::20], of a 32-bit memory address. The remaining 20 bits of the address are assumed to be 0.Upper 32 bits of the supported prefetch end address when 64-bit addressing is used. The lower 32 bits are assumed to be all 1's.Upper 32 bits of the supported prefetch base address when 64-bit addressing is used. The lower 32 bits are assumed to be 0.Upper 16 bits of the supported I/O end address when 32-bit I/O addressing is used. The lower 16 bits are assumed to be all 1's.Upper 16 bits of the supported I/O base address when 32-bit I/O addressing is used. The lower 16 bits are assumed to be 0. 2.7.0The abstraction of a port or connection point of a Device. This object should be instantiated when the Port has independent management characteristics from the Device that includes it. Examples are a Fibre Channel Port and a USB Port.The bandwidth of the Port in Bits per Second.Bits per SecondThe maximum bandwidth of the Port in Bits per Second.Bits per Second 2.6.0PortOnDevice associates a Port or connection point with its Device.trueAntecedentThe Device that includes the Port.trueDependentThe Port on the Device.true 2.7.0A collection of one or more ports logically grouped for administrative purposes. This class is created for specific ease of query when a Port is associated to more than one SystemSpecificCollection. In FibreChannel, this is the case (e.g. Node, Zone, ZoneSet). 2.7.0NetworkPort is the logical representation of network communications hardware - a physical connector and the setup/operation of the network chips, at the lowest layers of a network stack.SpeedThe current bandwidth of the Port in Bits per Second. For ports that vary in bandwidth or for those where no accurate estimation can be made, this property should contain the nominal bandwidth.Bits per SecondMIB.IETF|MIB-II.ifSpeedMIF.DMTF|Network Adapter 802 Port|001.5PortType is defined to force consistent naming of the 'type' property in subclasses and to guarantee unique enum values for all instances of NetworkPort. When set to 1 ("Other"), related property OtherPortType contains a string description the of the port's type. A range of values, DMTF_Reserved, has been defined that allows subclasses to override and define their specific port types.0123..1599916000..65535UnknownOtherNot ApplicableDMTF ReservedVendor ReservedCIM_NetworkPort.OtherNetworkPortTypeDescribes the type of module, when PortType is set to 1 ("Other").CIM_NetworkPort.PortTypeNetworkPorts are often numbered relative to either a logical modules or a network element.An enumeration of the types of links. When set to 1 ("Other"), the related property OtherLinkTechnology contains a string description of the link's type.012345678UnknownOtherEthernetIBFCFDDIATMToken RingFrame RelayCIM_NetworkPort.OtherLinkTechnologyA string value describing LinkTechnology when it is set to 1, "Other".CIM_NetworkPort.LinkTechnology64PermanentAddress defines the network address hardcoded into a port. This 'hardcoded' address may be changed via firmware upgrade or software configuration. If so, this field should be updated when the change is made. PermanentAddress should be left blank if no 'hardcoded' address exists for the NetworkAdapter.MIF.DMTF|Network Adapter 802 Port|001.264An array of strings indicating the network addresses for the port.MIF.DMTF|Network Adapter 802 Port|001.3Boolean indicating that the port is operating in full duplex mode.A boolean indicating whether the NetworkPort is capable of automatically determining the speed or other communications characteristics of the attached network media.The maximum transmission unit (MTU) that can be supported.BytesThe active or negotiated maximum transmission unit (MTU) that can be supported.Bytes 2.7.0Capabilities and management of an EthernetPort.PortTypeThe specific mode currently enabled for the Port. When set to 1 ("Other"), the related property OtherPortType contains a string description of the port's type.015051525316000..65535UnknownOther10BaseT10-100BaseT100BaseT1000BaseTVendor ReservedCIM_NetworkPort.OtherNetworkPortTypeNetworkAddressesEthernet/802.3 MAC addresses formatted as twelve hexadecimal digits (e.g. "010203040506"), with each pair representing one of the six octets of the MAC address in "canonical" bit order. (Thus, the Group address bit is found in the low order bit of the first character of the string.)64MIF.DMTF|Network Adapter 802 Port|001.3The maximum size of the INFO (non-MAC) field that will be received or transmitted.MIB.IETF|BRIDGE-MIB.dot1dTpPortMaxInfoCapabilities of the EthernetPort. For example, the Device may support AlertOnLan, WakeOnLan, Load Balancing and/or FailOver. If failover or load balancing capabilities are listed, a SpareGroup (failover) or ExtraCapacityGroup (load balancing) should also be defined to completely describe the capability.Indexed012345UnknownOtherAlertOnLanWakeOnLanFailOverLoadBalancingCIM_EthernetPort.CapabilityDescriptionsAn array of free-form strings providing more detailed explanations for any of the EthernetPort features indicated in the Capabilities array. Note, each entry of this array is related to the entry in the Capabilities array that is located at the same index.IndexedCIM_EthernetPort.CapabilitiesSpecifies which capabilities are enabled from the list of all supported ones, defined in the Capabilities array.Indexed012345UnknownOtherAlertOnLanWakeOnLanFailOverLoadBalancingCIM_EthernetPort.CapabilitiesCIM_EthernetPort.OtherEnabledCapabilitiesAn array of free-form strings providing more detailed explanations for any of the enabled capabilities that are specified as 'Other'.IndexedCIM_EthernetPort.EnabledCapabilities 2.7.0Capabilities and management of a TokenRingPort.NetworkAddressesToken Ring/802.5 MAC addresses formatted as twelve hexadecimal digits (e.g. "010203040506"), with each pair representing one of the six octets of the MAC address in "canonical" bit order. (Thus, the Group address bit is found in the low order bit of the first character of the string.)64MIF.DMTF|Network Adapter 802 Port|001.3The maximum size of the INFO (non-MAC) field that will be received or transmitted.MIB.IETF|BRIDGE-MIB.dot1dTpPortMaxInfoCapabilities of the TokenRingPort. For example, the Device may support AlertOnLan, WakeOnLan, Load Balancing and/or Failover. If failover or load balancing capabilities are listed, a SpareGroup (failover) or ExtraCapacityGroup (load balancing) should also be defined to completely describe the capability.Indexed012345UnknownOtherAlertOnLanWakeOnLanFailOverLoadBalancingCIM_TokenRingPort.CapabilityDescriptionsAn array of free-form strings providing more detailed explanations for any of the TokenRingAPort features indicated in the Capabilities array. Note, each entry of this array is related to the entry in the Capabilities array that is located at the same index.IndexedCIM_TokenRingPort.CapabilitiesSpecifies which of the capabilities from the "Capabilities" property are currently enabled.Indexed012345UnknownOtherAlertOnLanWakeOnLanFailOverLoadBalancingCIM_TokenRingPort.CapabilitiesCIM_TokenRingPort.OtherEnabledCapabilitiesAn array of free-form strings providing more detailed explanations for any of the enabled capabilities that are specified as 'Other'.IndexedCIM_TokenRingPort.EnabledCapabilitiesThe current status which can be used to diagnose fluctuating problems that can occur on token rings, after a station has successfully been added to the ring. Before an open is completed, this object contains the value indicating "no status" (131072). (The RingState and RingOpenStatus properties are also provided for debugging problems when the station can not even enter the ring.) The property's value is a sum of values, one for each currently applicable condition. The following values are defined for various conditions: 0 = No Problems Detected, 32 = Ring Recovery, 64 = Single Station, 256 = Remove Received, 512 = Reserved, 1024 = Auto-Removal Error, 2048 = Lobe Wire Fault, 4096 = Transmit Beacon, 8192 = Soft Error, 16384 = Hard Error, 32768 = Signal Loss, 131072 = No Status, Open Not Completed.MIB.IETF|IEEE 802.5 Token Ring MIB.dot5RingStatusThe current Device state with respect to entering or leaving the ring.012345OpenedClosedOpeningClosingOpen FailureRing FailureMIB.IETF|IEEE 802.5 Token Ring MIB.dot5RingStateThis property indicates the success, or the reason for failure, of the station's most recent attempt to enter the ring.012345678910No Open AttemptedBad ParameterLobe FailedSignal LossInsertion TimeoutRing FailedBeaconingDuplicate MACRequest FailedRemove ReceivedLast Open SuccessfulMIB.IETF|IEEE 802.5 Token Ring MIB.dot5RingOpenStatusThe ring's bandwidth.01234UnknownOtherOne MegabitFour MegabitSixteen MegabitMIB.IETF|IEEE 802.5 Token Ring MIB.dot5RingSpeed 2.7.0OOBAlertServiceOnNetworkPort defines where the out of band alerting Service is implemented. Currently, the Service can either employ a Modem or a NetworkPort to send alerts.true1The NetworkPort which implements the Service.AntecedenttrueThe alerting Service provided on the NetworkPort.Dependenttrue 2.7.0WakeUpServiceOnNetworkPort defines where the WakeUpService is implemented. Currently, the Service can either employ a Modem or a NetworkPort for wakeup.true1The NetworkPort which implements the Service.AntecedenttrueThe wakeup Service provided on the NetworkPort.Dependenttrue 2.6.0PortImplementsEndpoint associates a LogicalPort with one or more ProtocolEndpoints that are implemented on it. This class specializes the DeviceSAPImplementation association. It indicates that the referenced Endpoint is dependent on the operations of the Port Device.trueThe LogicalPort that represents the Device behind the ProtocolEndpoint.AntecedenttrueThe ProtocolEndpoint implemented on the LogicalPort.Dependenttrue 2.7.0The NetworkPortStatistics class describes the statistics for the NetworkPort.trueThe total number of bytes transmitted, including framing characters.MIB.IETF|MIB-II.ifOutOctetsMIF.DMTF|Network Adapter 802 Port|001.7BytestrueThe total number of bytes received, including framing characters.MIB.IETF|MIB-II.ifInOctetsMIF.DMTF|Network Adapter 802 Port|001.9BytestrueThe total number of packets transmitted.trueThe total number of packets received. 2.7.0The EthernetPortStatistics class describes the statistics for the EthernetPort.PacketsTransmittedtrueThe total number of packets transmitted.MIF.DMTF|Network Adapter 802 Port|001.6PacketsReceivedtrueThe total number of packets received.MIF.DMTF|Network Adapter 802 Port|001.8trueThe number of times there was an invalid data symbol when a valid carrier was present. The count is incremented at most once per carrier event, even if multiple symbol errors occur during the carrier event.MIB.IETF|EtherLike-MIB.dot3StatsSymbolErrorstrueA count of frames received on a particular interface that are not an integral number of octets in length and do not pass the FCS check. The count represented by an instance of this object is incremented when the alignment error status is returned by the MAC layer to the LLC (or other MAC user). Received frames for which multiple error conditions obtain are, according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status presented to the LLC.MIB.IETF|EtherLike-MIB.dot3StatsAlignmentErrorstrueA count of frames received on a particular interface that are an integral number of octets in length but do not pass the FCS check. The count represented by an instance of this object is incremented when the frame check error status is returned by the MAC layer to the LLC (or other MAC user). Received frames for which multiple error conditions obtain are, according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status presented to the LLC.MIB.IETF|EtherLike-MIB.dot3StatsFCSErrorstrueA count of successfully transmitted frames on a particular interface for which transmission is inhibited by exactly one collision. A frame that is counted by an instance of this object is not counted by the corresponding instance of the MultipleCollisionFrames property.MIB.IETF|EtherLike-MIB.dot3StatsSingleCollisionFramestrueA count of successfully transmitted frames on a particular interface for which transmission is inhibited by more than one collision. A frame that is counted by an instance of this object is not counted by the corresponding instance of the SingleCollisionFrames property.MIB.IETF|EtherLike-MIB.dot3StatsMultipleCollisionFramestrueA count of times that the SQE TEST ERROR message is generated by the PLS sublayer for a particular interface. The SQE TEST ERROR message is defined in section 7.2.2.2.4 of ANSI/IEEE 802.3-1985 and its generation is described in section 7.2.4.6 of the same document.MIB.IETF|EtherLike-MIB.dot3StatsSQETestErrorstrueA count of frames for which the first transmission attempt on a particular interface is delayed because the medium is busy. The count represented by an instance of this object does not include frames involved in collisions.MIB.IETF|EtherLike-MIB.dot3StatsDeferredTransmissionstrueThe number of times that a collision is detected on a particular interface later than 512 bit-times into the transmission of a packet. Five hundred and twelve bit-times corresponds to 51.2 microseconds on a 10 Mbit/s system. A (late) collision included in a count represented by an instance of this object is also considered as a (generic) collision for purposes of other collision-related statistics.MIB.IETF|EtherLike-MIB.dot3StatsLateCollisionstrueA count of frames for which transmission on a particular interface fails due to excessive collisions.MIB.IETF|EtherLike-MIB.dot3StatsExcessiveCollisionstrueA count of frames for which transmission on a particular interface fails due to an internal MAC sublayer transmit error. A frame is only counted by an instance of this object if it is not counted by the corresponding instance of either the LateCollisions property, the ExcessiveCollisions property, or the CarrierSenseErrors property. The precise meaning of the count represented by an instance of this object is implementation-specific. In particular, an instance of this object may represent a count of transmission errors on a particular interface that are not otherwise counted.MIB.IETF|EtherLike-MIB.dot3StatsInternalMacTransmitErrorstrueA count of frames for which reception on a particular interface fails due to an internal MAC sublayer receive error. A frame is only counted by an instance of this object if it is not counted by the corresponding instance of either the FrameTooLongs property, the AlignmentErrors property, or the FCSErrors property. The precise meaning of the count represented by an instance of this object is implementation-specific. In particular, an instance of this object may represent a count of receive errors on a particular interface that are not otherwise counted.MIB.IETF|EtherLike-MIB.dot3StatsInternalMacReceiveErrorstrueThe number of times that the carrier sense condition was lost or never asserted when attempting to transmit a frame on a particular interface. The count represented by an instance of this object is incremented at most once per transmission attempt, even if the carrier sense condition fluctuates during a transmission attempt.MIB.IETF|EtherLike-MIB.dot3StatsCarrierSenseErrorstrueA count of frames received on a particular interface that exceed the maximum permitted frame size. The count represented by an instance of this object is incremented when the FrameTooLong status is returned by the MAC layer to the LLC (or other MAC user). Received frames for which multiple error conditions obtain are, according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status presented to the LLC.MIB.IETF|EtherLike-MIB.dot3StatsFrameTooLongs 2.7.0The TokenRingPortStatistics class describes the statistics for the TokenRingPort.trueThis counter is incremented when a station detects the absence of transitions for five half-bit timers (burst-five errors).MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsBurstErrorstrueThis counter is incremented when a station receives an AMP or SMP frame in which A is equal to C is equal to 0, and then receives another SMP frame with A equal to C equal to 0 without first receiving an AMP frame. It denotes a station that cannot set the AC bits properly.MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsACErrorstrueThis counter is incremented when a station transmits an abort delimiter while transmitting data.MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsAbortTransErrorstrueThis counter is incremented when a station recognizes an internal error.MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsInternalErrorstrueThis counter is incremented when a station is transmitting and its TRR timer expires. This denotes a condition where a transmitting station in strip mode does not receive the trailer of the frame before the TRR timer goes off.MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsLostFrameErrorstrueThis counter is incremented when a station recognizes a frame addressed to its specific address, but has no available buffer space - indicating that the station is congested.MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsReceiveCongestionstrueThis counter is incremented when a station recognizes a frame addressed to its specific address and detects that the FS field A bits are set to 1 indicating a possible line hit or duplicate address.MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsFrameCopiedErrorstrueThis counter is incremented when a station acting as the active monitor recognizes an error condition that needs a token transmitted.MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsTokenErrorstrueThe number of Soft Errors that the Device has detected. It directly corresponds to the number of Report Error MAC frames that this Device has transmitted. Soft Errors are those which are recoverable by the MAC layer protocols.MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsSoftErrorstrueThe number of times this Device has detected an immediately recoverable fatal error. It denotes the number of times this Device is either transmitting or receiving beacon MAC frames.MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsHardErrorstrueThe number of times this Device has detected the loss of signal condition from the ring.MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsSignalLosstrueThe number of times this Device has transmitted a beacon frame.MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsTransmitBeaconstrueThe number of Claim Token MAC frames received or transmitted after the Device has received a Ring Purge MAC frame. This counter signifies the number of times the ring has been purged and is being recovered back into a normal operating state.MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsRecoverystrueThe number of times the Device has detected an open or short circuit in the lobe data path. The port will be closed and RingState will signify this condition.MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsLobeWirestrueThe number of times the Device has received a Remove Ring Station MAC frame request. When this frame is received, the Device will enter the close state and RingState will signify this condition.MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsRemovestrueThe number of times the Device has sensed that it is the only station on the ring. This will happen if the Device is the first one up on a ring, or if there is a hardware problem.MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsSinglestrueThe number of times the Device has detected that the frequency of the incoming signal differs from the expected frequency by more than that specified by the IEEE 802.5 standard.MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsFreqErrors trueCIM_NetworkPort2.7.0The use of the CIM_NetworkAdpater class has been deprecated in lieu of CIM_NetworkPort. This better reflects that the hardware of a single port is described and managed. NetworkAdapter is an Abstract class defining general networking hardware concepts (for example, PermanentAddress or Speed of operation).CIM_NetworkPort.PermanentAddress64PermanentAddress defines the network address hardcoded into an adapter. This 'hardcoded' address may be changed via firmware upgrade or software configuration. If so, this field should be updated when the change is made. PermanentAddress should be left blank if no 'hardcoded' address exists for the NetworkAdapter.MIF.DMTF|Network Adapter 802 Port|001.2CIM_NetworkPort.NetworkAddress64An array of strings indicating the network addresses for an adapter.IndexedMIF.DMTF|Network Adapter 802 Port|001.3CIM_NetworkPort.SpeedAn estimate of the current bandwidth in Bits per Second. For Adapters which vary in bandwidth or for those where no accurate estimation can be made, this property should contain the nominal bandwidth.Bits per SecondMIB.IETF|RFC1213-MIB.ifSpeedMIF.DMTF|Network Adapter 802 Port|001.5CIM_NetworkPort.MaxSpeedThe maximum speed, in Bits per Second, for the NetworkAdapter.Bits per SecondCIM_NetworkPort.FullDuplexBoolean indicating that the Adapter is operating in full duplex mode.CIM_NetworkPort.AutoSenseA boolean indicating whether the NetworkAdapter is capable of automatically determining the speed or other communications characteristics of the attached network media.CIM_NetworkPortStatistics.BytesTransmittedThe use of OctetsTransmitted is deprecated. The replacement is CIM_NetworkPortStatistics.BytesTransmitted.MIB.IETF|RFC1213-MIB.ifOutOctetsMIF.DMTF|Network Adapter 802 Port|001.7trueCIM_NetworkPortStatistics.BytesReceivedThe use of OctetsReceived is deprecated. The replacement is CIM_NetworkPortStatistics.BytesReceived.MIB.IETF|RFC1213-MIB.ifInOctetsMIF.DMTF|Network Adapter 802 Port|001.9true CIM_ EthernetAdapter2.7.0The use of the CIM_EthernetAdapter class has been deprecated, consistent with NetworkAdapter. Instead use the CIM_EthernetPort class. This class describes the capabilities and management aspects of an EthernetAdapter.CIM_EthernetPort.NetworkAddressesNetworkAddressesEthernet/802.3 MAC addresses formatted as twelve hexadecimal digits (e.g. "010203040506"), with each pair representing one of the six octets of the MAC address in "canonical" bit order. (Thus, the Group address bit is found in the low order bit of the first character of the string.)64IndexedMIF.DMTF|Network Adapter 802 Port|001.3CIM_EthernetPortStatistics.MaxDataSizeThe maximum size of the INFO (non-MAC) field that will be received or transmitted.MIB.IETF|BRIDGE-MIB.dot1dTpPortMaxInfoCIM_EthernetPort.CapabilitiesCapabilities of the EthernetAdapter. For example, the Device may support AlertOnLan, WakeOnLan, Load Balancing and/or FailOver. If failover or load balancing capabilities are listed, a SpareGroup (failover) or ExtraCapacityGroup (load balancing) should also be defined to completely describe the capability.Indexed012345UnknownOtherAlertOnLanWakeOnLanFailOverLoadBalancingCIM_EthernetAdapter.CapabilityDescriptionsCIM_EthernetPort.CapabilityDescriptionsAn array of free-form strings providing more detailed explanations for any of the EthernetAdapter features indicated in the Capabilities array. Note, each entry of this array is related to the entry in the Capabilities array that is located at the same index.IndexedCIM_EthernetAdapter.CapabilitiesCIM_EthernetPort.EnabledCapabilitiesSpecifies which capabilities are enabled from the list of all supported ones, defined in the Capabilities array.012345UnknownOtherAlertOnLanWakeOnLanFailOverLoadBalancingCIM_EthernetAdapter.CapabilitiesCIM_EthernetPortStatistics.SymbolErrorsThe number of times there was an invalid data symbol when a valid carrier was present. The count is incremented at most once per carrier event, even if multiple symbol errors occur during the carrier event.MIB.IETF|EtherLike-MIB.dot3StatsSymbolErrorstrueCIM_NetworkPortStatistics.TotalPacketsTransmittedThe total number of packets transmitted.MIF.DMTF|Network Adapter 802 Port|001.6trueCIM_NetworkPortStatistics.TotalPacketsReceivedThe total number of packets received.MIF.DMTF|Network Adapter 802 Port|001.8trueCIM_EthernetPortStatistics.AlignmentErrorsA count of frames received on a particular interface that are not an integral number of octets in length and do not pass the FCS check. The count represented by an instance of this object is incremented when the alignmentError status is returned by the MAC layer to the LLC (or other MAC user). Received frames for which multiple error conditions obtain are, according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status presented to the LLC.MIB.IETF|EtherLike-MIB.dot3StatsAlignmentErrorstrueCIM_EthernetPortStatistics.FCSErrorsA count of frames received on a particular interface that are an integral number of octets in length but do not pass the FCS check. The count represented by an instance of this object is incremented when the frameCheckError status is returned by the MAC layer to the LLC (or other MAC user). Received frames for which multiple error conditions obtain are, according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status presented to the LLC.MIB.IETF|EtherLike-MIB.dot3StatsFCSErrorstrueCIM_EthernetPortStatistics.SingleCollisionFramesA count of successfully transmitted frames on a particular interface for which transmission is inhibited by exactly one collision. A frame that is counted by an instance of this object is not counted by the corresponding instance of the MultipleCollisionFrames property.MIB.IETF|EtherLike-MIB.dot3StatsSingleCollisionFramestrueCIM_EthernetPortStatistics.MultipleCollisionFramesA count of successfully transmitted frames on a particular interface for which transmission is inhibited by more than one collision. A frame that is counted by an instance of this object is not counted by the corresponding instance of the SingleCollisionFrames property.MIB.IETF|EtherLike-MIB.dot3StatsMultipleCollisionFramestrueCIM_EthernetPortStatistics.SQETestErrorsA count of times that the SQE TEST ERROR message is generated by the PLS sublayer for a particular interface. The SQE TEST ERROR message is defined in section 7.2.2.2.4 of ANSI/IEEE 802.3-1985 and its generation is described in section 7.2.4.6 of the same document.MIB.IETF|EtherLike-MIB.dot3StatsSQETestErrorstrueCIM_EthernetPortStatistics.DeferredTransmissionsA count of frames for which the first transmission attempt on a particular interface is delayed because the medium is busy. The count represented by an instance of this object does not include frames involved in collisions.MIB.IETF|EtherLike-MIB.dot3StatsDeferredTransmissionstrueCIM_EthernetPortStatistics.LateCollisionsThe number of times that a collision is detected on a particular interface later than 512 bit-times into the transmission of a packet. Five hundred and twelve bit-times corresponds to 51.2 microseconds on a 10 Mbit/s system. A (late) collision included in a count represented by an instance of this object is also considered as a (generic) collision for purposes of other collision-related statistics.MIB.IETF|EtherLike-MIB.dot3StatsLateCollisionstrueCIM_EthernetPortStatistics.ExcessiveCollisionsA count of frames for which transmission on a particular interface fails due to excessive collisions.MIB.IETF|EtherLike-MIB.dot3StatsExcessiveCollisionstrueCIM_EthernetPortStatistics.InternalMACTransmitErrorsA count of frames for which transmission on a particular interface fails due to an internal MAC sublayer transmit error. A frame is only counted by an instance of this object if it is not counted by the corresponding instance of either the LateCollisions property, the ExcessiveCollisions property, or the CarrierSenseErrors property. The precise meaning of the count represented by an instance of this object is implementation-specific. In particular, an instance of this object may represent a count of transmission errors on a particular interface that are not otherwise counted.MIB.IETF|EtherLike-MIB.dot3StatsInternalMacTransmitErrorstrueCIM_EthernetPortStatistics.InternalMACReceiveErrorsA count of frames for which reception on a particular interface fails due to an internal MAC sublayer receive error. A frame is only counted by an instance of this object if it is not counted by the corresponding instance of either the FrameTooLongs property, the AlignmentErrors property, or the FCSErrors property. The precise meaning of the count represented by an instance of this object is implementation-specific. In particular, an instance of this object may represent a count of receive errors on a particular interface that are not otherwise counted.MIB.IETF|EtherLike-MIB.dot3StatsInternalMacReceiveErrorstrueCIM_EthernetPortStatistics.CarrierSenseErrorsThe number of times that the carrier sense condition was lost or never asserted when attempting to transmit a frame on a particular interface. The count represented by an instance of this object is incremented at most once per transmission attempt, even if the carrier sense condition fluctuates during a transmission attempt.MIB.IETF|EtherLike-MIB.dot3StatsCarrierSenseErrorstrueCIM_EthernetPortStatistics.FrameTooLongsA count of frames received on a particular interface that exceed the maximum permitted frame size. The count represented by an instance of this object is incremented when the FrameTooLong status is returned by the MAC layer to the LLC (or other MAC user). Received frames for which multiple error conditions obtain are, according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status presented to the LLC.MIB.IETF|EtherLike-MIB.dot3StatsFrameTooLongstrue CIM_TokenRingAdapter2.7.0The use of the CIM_TokenRingAdapter class has been deprecated, consistent with NetworkAdapter. Instead use the CIM_TokenRingPort class. This class describes the capabilities and management aspects of a TokenRingAdapter.CIM_TokenRingAdapter.NetworkAddressesNetworkAddressesToken Ring/802.5 MAC addresses formatted as twelve hexadecimal digits (e.g. "010203040506"), with each pair representing one of the six octets of the MAC address in "canonical" bit order. (Thus, the Group address bit is found in the low order bit of the first character of the string.)64IndexedMIF.DMTF|Network Adapter 802 Port|001.3CIM_TokenRingPort.MaxDataSizeThe maximum size of the INFO (non-MAC) field that will be received or transmitted.MIB.IETF|BRIDGE-MIB.dot1dTpPortMaxInfoCIM_TokenRingPort.CapabilitiesCapabilities of the TokenRingAdapter. For example, the Device may support AlertOnLan, WakeOnLan, Load Balancing and/or Failover. If failover or load balancing capabilities are listed, a SpareGroup (failover) or ExtraCapacityGroup (load balancing) should also be defined to completely describe the capability.Indexed012345UnknownOtherAlertOnLanWakeOnLanFailOverLoadBalancingCIM_TokenRingPort.CapabilityDescriptionsCIM_TokenRingPort.CapabilityDescriptionsAn array of free-form strings providing more detailed explanations for any of the TokenRingAdapter features indicated in the Capabilities array. Note, each entry of this array is related to the entry in the Capabilities array that is located at the same index.IndexedCIM_TokenRingAdapter.CapabilitiesCIM_TokenRingPort.EnabledCapabilitiesSpecifies which of the capabilities from the "Capabilities" property are currently enabled.012345UnknownOtherAlertOnLanWakeOnLanFailOverLoadBalancingCIM_TokenRingAdapter.CapabilitiesCIM_TokenRingPort.RingStatusThe current status which can be used to diagnose fluctuating problems that can occur on token rings, after a station has successfully been added to the ring. Before an open is completed, this object contains the value indicating "no status" (131072). (The RingState and RingOpenStatus properties are also provided for debugging problems when the station can not even enter the ring.) The property's value is a sum of values, one for each currently applicable condition. The following values are defined for various conditions: 0= No Problems Detected, 32= Ring Recovery, 64= Single Station, 256= Remove Received, 512= Reserved, 1024= Auto-Removal Error, 2048= Lobe Wire Fault, 4096= Transmit Beacon, 8192= Soft Error, 16384= Hard Error, 32768= Signal Loss, 131072= No Status, Open Not Completed.MIB.IETF|IEEE 802.5 Token Ring MIB.dot5RingStatusCIM_TokenRingPort.RingStateThe current Device state with respect to entering or leaving the ring.012345OpenedClosedOpeningClosingOpen FailureRing FailureMIB.IETF|IEEE 802.5 Token Ring MIB.dot5RingStateCIM_TokenRingPort.RingOpenStatusThis property indicates the success, or the reason for failure, of the station's most recent attempt to enter the ring.012345678910No Open AttemptedBad ParameterLobe FailedSignal LossInsertion TimeoutRing FailedBeaconingDuplicate MACRequest FailedRemove ReceivedLast Open SuccessfulMIB.IETF|IEEE 802.5 Token Ring MIB.dot5RingOpenStatusCIM_TokenRingPort.RingSpeedThe ring's bandwidth.01234UnknownOtherOne MegabitFour MegabitSixteen MegabitMIB.IETF|IEEE 802.5 Token Ring MIB.dot5RingSpeedCIM_TokenRingPortStatistics.BurstErrorsThis counter is incremented when a station detects the absence of transitions for five half-bit timers (burst-five errors).MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsBurstErrorstrueCIM_TokenRingPortStatistics.ACErrorsThis counter is incremented when a station receives an AMP or SMP frame in which A is equal to C is equal to 0, and then receives another SMP frame with A equal to C equal to 0 without first receiving an AMP frame. It denotes a station that cannot set the AC bits properly.MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsACErrorstrueCIM_TokenRingPortStatistics.AbortTransErrorsThis counter is incremented when a station transmits an abort delimiter while transmitting data.MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsAbortTransErrorstrueCIM_TokenRingPortStatistics.InternalErrorsThis counter is incremented when a station recognizes an internal error.MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsInternalErrorstrueCIM_TokenRingPortStatistics.LostFrameErrorsThis counter is incremented when a station is transmitting and its TRR timer expires. This denotes a condition where a transmitting station in strip mode does not receive the trailer of the frame before the TRR timer goes off.MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsLostFrameErrorstrueCIM_TokenRingPortStatistics.ReceiveCongestionsThis counter is incremented when a station recognizes a frame addressed to its specific address, but has no available buffer space - indicating that the station is congested.MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsReceiveCongestionstrueCIM_TokenRingPortStatistics.FrameCopiedErrorsThis counter is incremented when a station recognizes a frame addressed to its specific address and detects that the FS field A bits are set to 1 indicating a possible line hit or duplicate address.MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsFrameCopiedErrorstrueCIM_TokenRingPortStatistics.TokenErrorsThis counter is incremented when a station acting as the active monitor recognizes an error condition that needs a token transmitted.MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsTokenErrorstrueCIM_TokenRingPortStatistics.SoftErrorsThe number of Soft Errors that the Device has detected. It directly corresponds to the number of Report Error MAC frames that this Device has transmitted. Soft Errors are those which are recoverable by the MAC layer protocols.MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsSoftErrorstrueCIM_TokenRingPortStatistics.HardErrorsThe number of times this Device has detected an immediately recoverable fatal error. It denotes the number of times this Device is either transmitting or receiving beacon MAC frames.MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsHardErrorstrueCIM_TokenRingPortStatistics.SignalLossCountThe number of times this Device has detected the loss of signal condition from the ring.MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsSignalLosstrueCIM_TokenRingPortStatistics.TransmittedBeaconsThe number of times this Device has transmitted a beacon frame.MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsTransmitBeaconstrueCIM_TokenRingPortStatistics.RecoverysThe number of Claim Token MAC frames received or transmitted after the Device has received a Ring Purge MAC frame. This counter signifies the number of times the ring has been purged and is being recovered back into a normal operating state.MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsRecoverystrueCIM_TokenRingPortStatistics.LobeWiresThe number of times the Device has detected an open or short circuit in the lobe data path. The adapter will be closed and RingState will signify this condition.MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsLobeWirestrueCIM_TokenRingPortStatistics.RemovesThe number of times the Device has received a Remove Ring Station MAC frame request. When this frame is received, the Device will enter the close state and RingState will signify this condition.MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsRemovestrueCIM_TokenRingPortStatistics.SinglesThe number of times the Device has sensed that it is the only station on the ring. This will happen if the Device is the first one up on a ring, or if there is a hardware problem.MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsSinglestrueCIM_TokenRingPortStatistics.FrequencyErrorsThe number of times the Device has detected that the frequency of the incoming signal differs from the expected frequency by more than that specified by the IEEE 802.5 standard.MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsFreqErrorstrue CIM_OOBAlertServiceOnNetworkPort2.7.0The use of the CIM_OOBAlertServiceOnNetworkAdapter class has been deprecated, since NetworkAdapter has been deprecated. Instead use the CIM_OOBAlertServiceOnNetworkPort class. OOBAlertServiceOnNetworkAdapter defines where the out of band alerting Service is implemented.true1CIM_OOBAlertServiceOnNetworkPort.AntecedantThe NetworkAdapter which implements the Service.AntecedenttrueCIM_OOBAlertServiceOnNetworkPort.DependentThe alerting Service provided on the NetworkAdapter.Dependenttrue CIM_WakeUpServiceOnNetworkPort2.7.0The use of the CIM_WakeUpServiceOnNetworkAdapter class has been deprecated, since NetworkAdapter is deprecated. Instead use the CIM_WakeUpServiceOnNetworkPort class. WakeUpServiceOnNetworkAdapter defines where the WakeUpService is implemented.true1CIM_WakeUpServiceOnNetworkPort.AntecedentThe NetworkAdapter which implements the Service.AntecedenttrueCIM_WakeUpServiceOnNetworkPort.DependentThe wakeup Service provided on the NetworkAdapter.Dependenttrue CIM_OrderedMemberOfCollection2.7.0The use of the CIM_NetworkAdapterRedundancyComponent class has been deprecated since a specific association is not needed. Instead use the CIM_ OrderedMemberOfCollection class. CIM_NetworkAdapterRedundancyComponent indicates the role that a NetworkAdapter plays in a ExtraCapacityGroup, providing load balancing.truetrueCIM_OrderedMemberOfCollection.CollectionThe RedundancyGroup representing a set of load balanced NetworkAdapters.GroupComponenttruetrueCIM_OrderedMemberOfCollection.MemberThe Network Adapter(s) belonging to the RedundancyGroup.PartComponenttrueNo valueIndicates the scope of load balancing for the NetworkAdapters involved in the RedundancyGroup. Load balancing may be restricted to transmitting data only (value=1), receiving data only (value=2), or used for both transmit and receive (value=3).0123UnknownLoad Balancing - Transmit OnlyLoad Balancing - Receive OnlyFull Load BalancingCIM_OrderedMemberOfCollection.AssignedSequenceBoolean indicating whether the Network Adapter is an original primary adapter (value=1), a preferred primary adapter (2), or both (3). Values of "Unknown" and "Not Applicable" may also be specified.01234UnknownOriginal PrimaryPreferred PrimaryBothNot Applicable CIM_ConcreteIdentity2.7.0The use of the CIM_NetworkVirtualAdapter class has been deprecated. A specific association is not needed. Instead use the CIM_ConcreteIdentity class. NetworkVirtualAdapter describes that an instance of NetworkAdapter is actually the result of several Adapters participating in a load balanced RedundancyGroup.trueSystemElementCIM_ConcreteIdentity.SystemElementThe 'virtual' NetworkAdapter.trueSameElementCIM_ConcreteIdentity.SameElementThe ExtraCapacity RedundancyGroup that describes the load balancing. The result of the load balancing is the 'virtual' Adapter.true CIM_PortActiveConnection2.7.0The use of the CIM_AdapterActiveConnection class has been deprecated, since NetworkAdapter is deprecated. Instead use the CIM_PortActiveConnection class. The AdapterActiveConnection relationship indicates that a NetworkAdapter is using the referenced PhysicalConnector to output to the network. This relationship is important when the Adapter can choose to output from one of several Connectors. The Connectors may be associated with the NetworkAdapter in a Realizes relationship - but this is not required. This association provides additional information (i.e., 'in use for communication') different than Realizes.trueAntecedentCIM_PortActiveConnection.AntecedentThe PhysicalConnector.trueDependentCIM_PortActiveConnection.DependentThe NetworkAdapter that transmits using the Connector.true 2.7.0CIM_FCPortThe use of the CIM_FibreChannelAdapter class is deprecated, consistent with the deprecation of NetworkAdapter. Instead use CIM_FCPort. This class describes the capabilities and management aspects of a Fibre Channel Adapter.CIM_NetworkPort.SupportedMaximumTransmissionUnitThe maximum frame size, in bytes, supported by the Adapter.BytesCIM_FCPort.SupportedCOSThe Fibre Channel Classes of Service that are supported by the Adapter, on its Ports. The currently negotiated COS for a connection is a property (NegotiatedCOS) on the FibrePortActiveLogin association.0123456Unknown12346FCIM_FCPort.SupportedFC4TypesAn array of integers indicating the Fibre Channel FC-4 protocols supported by the Adapter. The protocols that are active and running are indicated in the CurrentFC4Types property. The values used in this array are taken from the FC-GS2 (bitmapped) field defined in Table 11 of the standard. Also, FC-SB-2 codes are included from the T11 document, 236V0. If the FC4 Type is "Vendor Unique" (value=255), then the specific vendor values (in the range, 0xE0 to 0xFF) should be listed in the FC4VendorUniqueTypes property.01458917181921222325262728323436648081828896255UnknownOtherISO/IEC 8802 - 2 LLCIP over FCSCSI - FCPSCSI - GPPIPI - 3 MasterIPI - 3 SlaveIPI - 3 PeerCP IPI - 3 MasterCP IPI - 3 SlaveCP IPI - 3 PeerSBCCS ChannelSBCCS Control UnitFC-SB-2 ChannelFC-SB-2 Control UnitFibre Channel Services (FC-GS, FC-GS-2, FC-GS-3)FC-SWFC - SNMPHIPPI - FPBBL ControlBBL FDDI Encapsulated LAN PDUBBL 802.3 Encapsulated LAN PDUFC - VIFC - AVVendor UniqueCIM_FibreChannelAdapter.FC4VendorUniqueTypes240255CIM_FCPort.SupportedFC4TypesWhen the FC4TypesSupported array contains the value 255 ("Vendor Unique"), then the property, FC4VendorUniqueTypes, lists of all the vendor specific protocols supported by the Adapter. These values are in the range, 0xE0 to 0xFF.CIM_FCPort.ActiveFC4TypeAn array of integers indicating the Fibre Channel FC-4 protocols currently running on the Adapter. A list of all protocols supported by the Adapter is indicated in the FC4TypesSupported property. The values used in this array are taken from the FC-GS2 (bitmapped) field defined in Table 11 of the standard. Also, FC-SB-2 codes are included from the T11 document, 236V0. If the FC4 Type is "Vendor Unique" (value=255), then the specific vendor values (in the range, 0xE0 to 0xFF) that are currently running should be listed in the CurrentFC4VendorTypes property.01458917181921222325262728323436648081828896255UnknownOtherISO/IEC 8802 - 2 LLCIP over FCSCSI - FCPSCSI - GPPIPI - 3 MasterIPI - 3 SlaveIPI - 3 PeerCP IPI - 3 MasterCP IPI - 3 SlaveCP IPI - 3 PeerSBCCS ChannelSBCCS Control UnitFC-SB-2 ChannelFC-SB-2 Control UnitFibre Channel Services (FC-GS, FC-GS-2, FC-GS-3)FC-SWFC - SNMPHIPPI - FPBBL ControlBBL FDDI Encapsulated LAN PDUBBL 802.3 Encapsulated LAN PDUFC - VIFC - AVVendor UniqueCIM_FibreChannelAdapter.FC4TypesSupportedCIM_FibreChannelAdapter.CurrentFC4VendorTypes240255CIM_FCPort.ActiveFC4TypeWhen the CurrentFC4Types array contains the value 255 ("Vendor Unique"), then the property, CurrentFC4VendorTypes, lists all the vendor specific protocols running on the Adapter. These values are in the range, 0xE0 to 0xFF.CIM_FibreChannelAdapter.FC4VendorUniqueTypesNo valueA list of the Capabilities of the Fibre Channel Adapter. For example, that the Adapter utilizes the Directory Server, or that it generates State Change Notifications can be indicated using the values 2 and 12, respectively.Indexed0123456789101112131415UnknownOtherUtilizes the Directory ServerUtilizes the Time ServerUtilizes the Management ServerUtilizes the Alias ServerUtilizes the Security Key Distribution ServerUtilizes the Clock Synchronization ServerUtilizes the Multicast ServerUtilizes QoS FacilitatorUtilizes Broadcast ServicesSupports Fabric Login ServerGenerates State Change NotificationsRegisters for State Change NotificationsResponds to Read Connection StatusSupports Third Party Process LogoutNo valueAn array of free-form strings providing more detailed explanations for any of the Adapter features indicated in the Capabilities array. Note, each entry of this array is related to the entry in the Capabilities array that is located at the same index.IndexedCIM_FibreChannelAdapter.CapabilitiesCIM_FCPortStatistics.ErrorFramestrueThe number of times that a frame was received but no buffer was available.CIM_FCPortStatistics.ErrorFramestrueThe number of times that a frame was received but no end-to-end credit was available.No valueA 'long' timeout value (in milliseconds) for determining when to reinstate a Recovery_Qualifier. The default value is 120 seconds (120000 milliseconds). It is typically set to the ErrorDetectTimeout value + 2*(fabric delay time).MilliSecondsNo valueA 'short' timeout value (in milliseconds) for determining that an error has occurred. The default value is 10 seconds (10000 milliseconds).MilliSecondsNo valuetrueNumber of Class 1 sequences sent since last reset of the Device.No valuetrueNumber of Class 2 sequences sent since last reset of the Device.No valuetrueNumber of Class 3 sequences sent since last reset of the Device.No valuetrueNumber of Class 4 sequences sent since last reset of the Device.CIM_FCPortStatistics.BytesReceivedtrueNumber of octets received by the Adapter when running Class 2 service.CIM_FCPortStatistics.BytesTransmittedtrueNumber of octets transmitted by the Adapter when running Class 2 service.CIM_FCPortStatistics.PacketsReceivedtrueNumber of frames received by the Adapter when running Class 2 service.CIM_FCPortStatistics.PacketsTransmittedtrueNumber of frames transmitted by the Adapter when running Class 2 service.No valuetrueNumber of frames discarded by the Adapter when running Class 2 service.CIM_FCPortStatistics.BytesReceivedtrueNumber of octets received by the Adapter when running Class 3 service.CIM_FCPortStatistics.BytesTransmittedtrueNumber of octets transmitted by the Adapter when running Class 3 service.CIM_FCPortStatistics.PacketsReceivedtrueNumber of frames received by the Adapter when running Class 3 service.CIM_FCPortStatistics.PacketsTransmittedtrueNumber of frames transmitted by the Adapter when running Class 3 service.No valuetrueNumber of frames discarded by the Adapter when running Class 3 service.CIM_FCPortStatistics.ErrorFramestrueNumber of parity errors detected somewhere in the data path.CIM_FCPortStatistics.ErrorFramestrueNumber of Class 1 or 2 frames that are not ACKed within the time indicated by ErrorDetectTimeout.CIM_FCPortStatistics.BufferCreditNotProvidedtrueNumber of times that the Device has been without a buffer credit for a time longer than ErrorDetectTimeout.CIM_FCPortStatistics.BufferCreditNotReceivedtrueNumber of times that the Device has been without an end credit for a time longer than ErrorDetectTimeout.CIM_FCPortStatistics.DelimiterErrorstrueNumber of frames received out of order. 2.7.0CIM_FCPortThe use of the FibrePort class is deprecated, since FibreChannel Adapter has been deprecated in lieu of FCPort. And, this class overlaps with FCPort. The new FCPort class should be used in lieu of both FibreChannelAdapter and FibrePort. FibrePort describes the capabilities and management aspects of a Fibre Channel Port Device.CIM_FCPort.PermanentAddressAn address value used to identify the source (S_ID) or destination (D_ID) of a frame. The FC-SW standard includes a table of special address identifier values and their meanings. Consult the FC-SW documentation for additional information.No valueAn array indicating the modes in which the Port can operate. PortType values describe the role and behavior of the Fibre Channel entity: "N" = Node Port, "NL" = Node Port supporting FC arbitrated loop, "E" = Expansion Port connecting fabric elements (for example, FC switches), "F" = Fabric (element) Port, "FL" = Fabric (element) Port supporting FC arbitrated loop, and "B" = Bridge Port. PortTypes are defined in the ANSI X3 standards. A particular mode may be listed multiple times in the SupportedPortTypes array in order to define that multiple, unique version levels are supported. Version information is defined in the PortTypeVersions property. Note that each entry of the SupportedPortTypes array is related to the entry in PortTypeVersions that is located at the same index.Indexed01234567UnknownNNL-PrivateNL-PublicEFFLBCIM_FibrePort.PortTypeVersionsNo valueVersion information for each of the SupportedPortTypes. A particular PortType (mode) may be listed multiple times in the SupportedPortTypes array in order to define multiple, unique version levels. Note that each entry of this array is related to the entry in SupportedPortTypes that is located at the same index.IndexedCIM_FibrePort.SupportedPortTypesNo valueThe specific modes currently enabled for the Port. The values are equal to, or a subset of the values in the SupportedPortTypes array.01234567UnknownNNL-PrivateNL-PublicEFFLBCIM_FibrePort.SupportedPortTypesCIM_FibrePort.EnabledVersionsNo valueVersion information for each of the EnabledPortTypes. A particular PortType (mode) may be listed multiple times in the EnabledPortTypes array in order to define multiple, unique version levels. Note that each entry of this array is related to the entry in EnabledPortTypes that is located at the same index.IndexedCIM_FibrePort.EnabledPortTypesCIM_FCPort.PortTypeThe specific mode in which the Port is currently running. The value is one of the entries in the EnabledPortTypes array. The current port type/mode is dependent on the fibre technology. For example, in a public loop network, you might indicate a port type of "FL" (value=6) or "NL" (value=2).01234567UnknownNNL-PrivateNL-PublicEFFLBCIM_FibrePort.EnabledPortTypesCIM_FibrePort.CurrentVersionNo valueVersion information for the CurrentPortType that is active.CIM_FibrePort.CurrentPortTypeCIM_FCPort.NetworkAddressesOne or more address identifiers that may be recognized by the Port, in addition to its port-specific identifier. Multicast or hunt group addresses that are recognized by the Port would be identified in this array.CIM_FCPortStatistics.LossOfSignalCountertrueNumber of times that signal is lost on the Port since last reset of the Device.CIM_FCPortStatistics.LossOfSyncCountertrueNumber of times that synchronization is lost on the Port since last reset of the Device. Synchronization is assumed lost after a timeout period identified by the ReceiverTransmitterTimeout property.CIM_FCPortStatistics.CRCErrorstrueNumber of times that the CRC in a frame does not match the CRC computed by the receiver.CIM_FCPortStatistics.InvalidTransmissionWordstrueThe number of transmission words that had an 8b10b code violation in one or more of its characters, had a K28.5 in its second, third or fourth character positions, and/or was an ordered set that had an incorrect Beginning Running Disparity.CIM_FCPortStatistics.FramesTooShorttrueThe number of frames received that were shorter than 28 octets. The value of 28 is calculated based on an assumption of 24 header bytes plus 4 CRC bytes. The count does not include SOF/EOF bytes which are not data.CIM_FCPortStatistics.FramesTooLongtrueThe number of frames received that were longer than 2140 octets. The value of 2140 is calculated based on an assumption of 24 header bytes plus 4 CRC bytes and 2112 bytes of payload.No valuetrueThe number of times that a fill word could not be inserted, when required. The Elasticity Buffer is defined in FC-AL. This event might cause data corruption and may indicate a configuration error or a device out of spec.No valuetrueThe number of times that a fill word could not be deleted, when required. The Elasticity Buffer is defined in FC-AL. This event might cause data corruption and may indicate a configuration error or a device out of spec.No valueTimeout value in milliseconds used to determine when loss of synchronization has occurred. The typical default is 100 msec.MillisecondsNo valueIndication of whether the Port is currently bypassed (value=2) or not (value=1). A value of 3 ("Forced Insert") describes that the Port is forced active, when it would otherwise be "Bypassed".0123UnknownNot BypassedBypassedForced InsertNo valueThe type of cabling as sensed by the Port. Not all FibrePorts are capable of providing this information. In this case, a value of 0, "Unknown", will be returned. Also, when single or multi-mode fiber cabling can not be distinguished, the more general value - 4, "Fiber-optic" - can be specified.0123456UnknownOtherNo MediaCopper/TwinaxialFiber-opticFiber Single ModeFiber Multimode 2.7.0No valueThe use of FibrePortOnFCAdapter is deprecated since both FibrePort and FibreChannelAdapter have been deprecated. No replacement is needed, since the 2 classes are combined into a single class. FibrePortOnFCAdapter associates a FibrePort with a FibreChannelAdapter.trueNo value1The FibreChannelAdapter that includes the Port.Antecedenttrue1No valueThe FibrePort on the Adapter.Dependenttrue true2.7.0CIM_ActiveConnectionCIM_FCPortThe use of FibrePortActiveLogin is deprecated since FibrePort is deprecated. Its information is found by examining the individual FCPorts, and an ActiveConnection between the FCProtocolEndpoints associated with the ports. FibrePortActiveLogin indicates that two FibrePorts are connected via a login and have negotiated their Class Of Service, frame size and other link characteristics, as specified by an instance of this class.trueCIM_ActiveConnection.DependentThe originator of the login.trueCIM_ActiveConnection.AntecedentThe responder to the login.trueCIM_FCPort.ActiveCOSThe Fibre Channel Class of Service that is currently running between the Ports. Since two Ports can be simultaneously connected at different Classes of Service, this property had to be part of the object's key and therefore, an instance's identity.0123456Unknown12346FCIM_FibreChannelAdapter.SupportedCOSMIF.DMTF|Fibre Channel Bus Port Extensions|001.5CIM_FCPort.ActiveMaximumTransmissionUnitThe Fibre Channel frame size, in bytes, that is currently negotiated between the two Ports.BytesCIM_FCPort.SpeedThe speed for communications that is currently negotiated between the two Ports. Speed is specified in bits per second. If this information is not available, the property should be set to 0.Bits per SecondNo valueAcknowledgement model negotiated during Port login. For example, ACK-1 indicates that each frame should be acknowledged.0123UnknownACK-0ACK-1ACK-NMIF.DMTF|Fibre Channel Bus Port Extensions|001.6No valueThe buffer-to-buffer model negotiated during Port login. Either the model defined by the FC-PH standard is used (value=1, "Regular"), or an "Alternate" model is negotiated.012UnknownRegularAlternateNo valueOriginatorBufferCredit reflects the buffer credit of the Port defined as the LoginOriginator. It is the number of frame buffers made available BY the originating Port, TO the responder Port. Buffer credits are used in point to point connections, when an NL-Local Port is logged into another NL-Local Port, and when Nx Ports are logged into Fx Ports. In other scenarios, this value is undefined.MIF.DMTF|Fibre Channel Bus Port Extensions|001.3No valueResponderBufferCredit reflects the buffer credit of the Port defined as the LoginResponder. It is the number of frame buffers made available BY the responder Port, TO the originating Port. Buffer credits are used in point to point connections, when an NL-Local Port is logged into another NL-Local Port, and when Nx Ports are logged into Fx Ports. In other scenarios, this value is undefined.MIF.DMTF|Fibre Channel Bus Port Extensions|001.3No valueOriginatorEndCredit reflects the end credit of the Port defined as the LoginOriginator. It is the number of frame buffers made available BY the originating Port, TO the responder Port. End credits are used in point to point connections, when an NL-Local Port is logged into another NL-Local Port, and when Nx Ports are logged into remote Nx Ports. In other scenarios, this value is undefined.MIF.DMTF|Fibre Channel Bus Port Extensions|001.2No valueResponderEndCredit reflects the end credit of the Port defined as the LoginResponder. It is the number of frame buffers made available BY the responder Port, TO the originating Port. End credits are used in point to point connections, when an NL-Local Port is logged into another NL-Local Port, and when Nx Ports are logged into remote Nx Ports. In other scenarios, this value is undefined.MIF.DMTF|Fibre Channel Bus Port Extensions|001.2 2.7.0CIM_FCPortStatisticsThe use of the FCAdapterEventCounters class is deprecated since FibreChannelAdapter is deprecated. FCPortStatistics should be used instead, but redefines the level at which data is collected. This is why there is no direct translation of the individual counters between the two classes. This object describes event counters specific to a FibreChannelAdapter.No valuetrueThe number of Abort sequence frames received.No valuetrueThe number of Abort sequence frames sent.No valuetrueThe number of frames busied by the Fabric.No valuetrueThe number of frames busied by the receiving Node.No valuetrueThe number of frames busied by the Adapter itself.No valuetrueThe number of frames rejected by the Fabric.No valuetrueThe number of frames rejected by the receiving Node.No valuetrueThe number of frames rejected by the Adapter itself.No valuetrueThe number of PRLI frames sent where the response was LS_RJT.No valuetrueThe number of PRLO frames sent where the response was LS_RJT.No valuetrueThe number of Abort sequence frames sent where the response was BA_RJT.FCPortStatistics.ResetSelectedStats()Method to reset the Adapter event counters. The method takes one parameter as input - an integer indicating which counter to reset. For this input parameter, 0 indicates all, 1 through 11 indicate a reset of the individual 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 Device's instrumentation, which tabulates the errors and warnings, can also reset its internal processing and counters. 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.true01234567891011AllABTSFramesReceivedABTSFramesSentFBSYReceivedPBSYReceivedPBSYSentFRJTReceivedPRJTReceivedPRJTSentPRLIRejectedPRLORejectedABTSFramesRejected 2.7.0CIM_FCPortStatisticsThe use of the FibrePortEventCounters class is deprecated, since FibrePort is deprecated. FCPortStatistics should be used instead, but redefines the level at which data is collected. This is why there is no direct translation of the individual counters between the two classes. This object defines error counters specific to a FibrePort.No valuetrueThe number of login frames received.No valuetrueThe number of login frames sent.No valuetrueNumber of frames received containing 'EOF Abort'.No valuetrueNumber of frames transmitted containing 'EOF Abort'.No valuetrueThe number of logouts received from various targets.No valuetrueThe number of logout frames sent.No valuetrueThe number of PLOGI frames sent where the response was LS_RJT.No valuetrueThe number of PLOGO frames sent where the response was LS_RJT.CIM_FCPortStatistics.ResetSelectedStatsMethod to reset the Port event counters. The method takes one parameter as input - an integer indicating which counter to reset. For this input parameter, 0 indicates all, 1 through 8 indicate a reset of the individual 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 Device's instrumentation, which tabulates the errors and warnings, can also reset its internal processing and counters. 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.true012345678AllPLOGIsReceivedPLOGIsSentEOFAbortsReceivedEOFAbortsTransmittedPLOGOsReceivedPLOGOsSentPLOGIsRejectedPLOGOsRejected 2.7.1Capabilities and management of a Fibre Channel Port Device.PortTypeThe specific mode currently enabled for the Port. The values: "N" = Node Port, "NL" = Node Port supporting FC arbitrated loop, "E" = Expansion Port connecting fabric elements (for example, FC switches), "F" = Fabric (element) Port, "FL" = Fabric (element) Port supporting FC arbitrated loop, "B" = Bridge and "G" = Generic Port. PortTypes are defined in the ANSI X3 standards. When set to 1 ("Other"), the related property OtherPortType contains a string description of the port's type.0110111213141516171816000..65535UnknownOtherNNLF/NLNxEFFLBGVendor ReservedCIM_NetworkPort.OtherNetworkPortTypeAn array of integers indicating the Fibre Channel Classes of Service that are supported. The active COS are indicated in ActiveCOS.01234567Unknown123456FAn array of integers indicating the Classes of Service that are active. The Active COS is indicated in ActiveCOS.01234567Unknown123456FCIM_FCPort.SupportedCOSAn array of integers indicating the Fibre Channel FC-4 protocols supported. The protocols that are active and running are indicated in the ActiveFC4Types property.01458917181921222325262728323436648081828896255UnknownOtherISO/IEC 8802 - 2 LLCIP over FCSCSI - FCPSCSI - GPPIPI - 3 MasterIPI - 3 SlaveIPI - 3 PeerCP IPI - 3 MasterCP IPI - 3 SlaveCP IPI - 3 PeerSBCCS ChannelSBCCS Control UnitFC-SB-2 ChannelFC-SB-2 Control UnitFibre Channel Services (FC-GS, FC-GS-2, FC-GS-3)FC-SWFC - SNMPHIPPI - FPBBL ControlBBL FDDI Encapsulated LAN PDUBBL 802.3 Encapsulated LAN PDUFC - VIFC - AVVendor UniqueAn array of integers indicating the Fibre Channel FC-4 protocols currently running. A list of all protocols supported is indicated in the SupportedFC4Types property.01458917181921222325262728323436648081828896255UnknownOtherISO/IEC 8802 - 2 LLCIP over FCSCSI - FCPSCSI - GPPIPI - 3 MasterIPI - 3 SlaveIPI - 3 PeerCP IPI - 3 MasterCP IPI - 3 SlaveCP IPI - 3 PeerSBCCS ChannelSBCCS Control UnitFC-SB-2 ChannelFC-SB-2 Control UnitFibre Channel Services (FC-GS, FC-GS-2, FC-GS-3)FC-SWFC - SNMPHIPPI - FPBBL ControlBBL FDDI Encapsulated LAN PDUBBL 802.3 Encapsulated LAN PDUFC - VIFC - AVVendor UniqueCIM_FCPort.SupportedFC4Types 2.7.0A ZoneSet is a group of zones that are managed collectively by the same domain. The managing domain is indicated by the HostedCollection association. For example, for Fibre Channel, this would indicate a set of zones that are part of a fabric. The zones are only under zone enforcement by the fabric,if the zoneset is set to active.ElementNametruetrueA user-friendly name for the ZoneSet that is unique within the AdminDomain.truetrueIndicates that this ZoneSet is currently active (i.e. under enforcement of a fabric). This property can be used to distinguish between a ZoneSet that is currently active and a snapshot of a ZoneSet (with the same InstanceName) that is for "offline" editing. 2.7.0A zone is a group of Ports, Endpoints, Nodes, Zones, and/or NamedAddressCollections that are managed collectively by the same domain. The managing domain is indicated by the HostedCollection association. For Fibre Channel, a zone indicates a set of members that are participating together in the fabric.ElementNametruetrueA user-friendly name for the Zone that is unique within the AdminDomain.trueIndicates that this Zone is currently active (i.e. under enforcement of a fabric). This property can be used to distinguish between a Zone that is currently active and a snapshot of a Zone (with the same InstanceName) that is for "offline" editing.trueThe type of zoning to be enforced.0123..32768..65535UnknownOtherDefaultProtocolDMTF ReservedVendor ReservedCIM_Zone.OtherZoneTypeDescriptionA string describing the ZoneType when the ZoneType value is 1 "Other".CIM_Zone.ZoneTypeSpecific clarification when necessary when the ProtocolType has an enumeration that requires it. Specifically, if ProtocolType is "Protocol", then SubType the Fibre Channel FC4 type.01234..32768..65535UnknownOtherSCSIVIIPDMTF ReservedVendor ReservedCIM_Zone.OtherZoneSubTypeDescriptionA string describing the ZoneSubType when the ZoneSubType value is 1 "Other".CIM_Zone.ZoneSubType 2.7.0ZoneMembershipSettingData provides the identification criteria for possible Zone and ZoneAlias members.trueThis specifies the type of identification used in the ConnectivityMemberID field. For Fibre Channel: * A ConnectivityMemberType of 'PermanentAddress', the ConnectivityMemberID is the NxPort WWN; * A ConnectivityMemberType of 'NetworkAddress', the ConnectivityMemberID is the NXPort Address ID; * A ConnectivityMemberType of 'SwitchPortID', the ConnectivityMemberID is 'Domain:PortNumber'.012345..32768..65535UnknownOtherPermanentAddressNetworkAddressSwitchPortIDLogicalPortGroupDMTF ReservedVendor ReservedCIM_ConnectivityMemberSettingData.ConnectivityMemberIDtrueThe identification of the member based on the type specified by ConnectivityMemberType.CIM_ConnectivityMemberSettingData.ConnectivityMemberType 2.7.0The ZoneService if responsible for managing the zone enforcement for the fabric. The ZoneService is hosted on an AdminDomain. This is depicted by the HostedService association. 2.6.0FibreProtocolService abstracts and allows the management of the Alias, Management, Time, Security, Directory (Naming) and other services and functions available in a Fibre Channel network. This class will be further defined in a later release of CIM. 2.7.0FCPortStatistics is the statistics for the FCPort.trueLIPCount is the number of LIP events that have occurred on an arbitrated loop.trueNOSCount is the number of NOS events that have occurred on the switched fabric.trueErrorFrames is the number of frames that have been received in error.trueDumpedFrames is the number of frames that were lost due to a lack of host buffers available.trueLinkFailure is the number of times a link error has occurred. This count is part of the Link Error Status Block (LESB).trueNumber of times that signal is lost on the Port since last reset of the Device. This count is part of the Link Error Status Block (LESB).trueNumber of times that synchronization is lost on the Port since last reset of the Device. Synchronization is assumed lost after a timeout period (identified by the ReceiverTransmitterTimeout property) is exceeded. This count is part of the Link Error Status Block (LESB).trueCount of primitive sequence protocol errors detected at this port. This count is part of the Link Error Status Block (LESB).trueNumber of times that the CRC in a frame does not match the CRC computed by the receiver. This count is part of the Link Error Status Block (LESB).trueThe number of transmission words that had an invalid character (8b10b code violation) in one or more of its characters, had a K28.5 (8b10b control) in its second, third or fourth character positions, and/or had an incorrect Beginning Running Disparity. This count is part of the Link Error Status Block (LESB).trueThe number of frames received that were shorter than 28 octets. The value of 28 is calculated based on an assumption of 24 header bytes plus 4 CRC bytes. The count does not include SOF/EOF bytes which are not data.trueThe number of frames received that were longer than 2140 octets. The value of 2140 is calculated based on an assumption of 24 header bytes plus 4 CRC bytes and 2112 bytes of payload.trueCount of frames received with unknown addressing. An example is an unknown SID or DID. The SID or DID is not known to the routing algorithm.trueCount of occurrences when all input buffers of a port were full and outbound buffer-to-buffer credit transitioned to zero. There is no credit to provide to other side.trueCount of transitions in/out of BBcredit zero state. The other side is not providing any credit.true Count of invalid frame delimiters received at this port. An example is a frame with a class 2 start and a class 3 at the end.trueCount of disparity errors received at this port.trueCount of Link resets. This is the number of LRs received.trueCount of Link resets. This is the number of LRs transmitted.trueCount of Multicast Frames or Packets received.trueCount of Multicast Frames or Packets transmitted. 2.7.0An Infiniband Subnet Manager (SM) is an entity responsible for configuring and managing an IB subnet. It uses Subnet Management Agents (SMA) to access and manage individual nodes. The SM is hosted in the context of a specific computer system (i.e., hosted by an instance of UnitaryComputerSystem), as described by the HostedService association. Note that there may be multiple SMs operating in a subnet, but only the elected master is allowed to perform configuration functions.Administratively assigned priority for this SM, used to establish the master. A higher number indicates a higher priority and likelihood of becoming the master. The property value can be reset by the master SM.trueMAD.IBTA | SMInfo | PriorityEnumerated value that indicates the Subnet Manager's State. The values are fairly self-explanatory except for "Not Active". This value indicates that the SM is available to participate in the subnet, but has not been given permission. A value "Unknown" (0) is also defined.01234UnknownNot ActiveDiscoveringStandbyMasterMAD.IBTA | SMInfo | SMState 2.6.0A MediaAccessDevice represents the ability to access one or more media and use this media to store and retrieve data.Capabilities of the MediaAccessDevice. For example, the Device may support "Random Access", removeable media and "Automatic Cleaning". In this case, the values 3, 7 and 9 would be written to the array. Several of the enumerated values require some explanation: 1) Value 11, Supports Dual Sided Media, distinguishes a Device that can access both sides of dual sided Media, from a Device that reads only a single side and requires the Media to be flipped; and, 2) Value 12, Predismount Eject Not Required, indicates that Media does not have to be explicitly ejected from the Device before being accessed by a PickerElement.Indexed0123456789101112UnknownOtherSequential AccessRandom AccessSupports WritingEncryptionCompressionSupports Removeable MediaManual CleaningAutomatic CleaningSMART NotificationSupports Dual Sided MediaPredismount Eject Not RequiredMIF.DMTF|Storage Devices|001.9MIF.DMTF|Storage Devices|001.11MIF.DMTF|Storage Devices|001.12MIF.DMTF|Disks|003.7MIF.DMTF|Host Disk|001.2MIF.DMTF|Host Disk|001.4CIM_MediaAccessDevice.CapabilityDescriptionsAn array of free-form strings providing more detailed explanations for any of the AccessDevice features indicated in the Capabilities array. Note, each entry of this array is related to the entry in the Capabilities array that is located at the same index.IndexedCIM_MediaAccessDevice.CapabilitiesErrorMethodology is a free-form string describing the type(s) of error detection and correction supported by this Device.A free form string indicating the algorithm or tool used by the device to support compression. If it is not possible or not desired to describe the compression scheme (perhaps because it is not known), recommend using the following words: "Unknown" to represent that it is not known whether the device supports compression capabilities or not, "Compressed" to represent that the device supports compression capabilities but either its compression scheme is not known or not disclosed, and "Not Compressed" to represent that the devices does not support compression capabilities.When the MediaAccessDevice supports multiple individual Media, this property defines the maximum number which can be supported or inserted.Maximum size, in KBytes, of media supported by this Device. KBytes is interpreted as the number of bytes multiplied by 1000 (NOT the number of bytes multiplied by 1024).MIF.DMTF|Sequential Access Devices|001.2MIF.DMTF|Host Disk|001.5Default block size, in bytes, for this Device.BytesMaximum block size, in bytes, for media accessed by this Device.BytesMinimum block size, in bytes, for media accessed by this Device.BytesBoolean indicating that the MediaAccessDevice needs cleaning. Whether manual or automatic cleaning is possible is indicated in the Capabilities array property.True indicates that the media is locked in the Device and can not be ejected. For non-removeable Devices, this value should be true.An enumeration indicating the operational security defined for the MediaAccessDevice. For example, information that the Device is "Read Only" (value=4) or "Boot Bypass" (value=6) can be described using this property.1234567OtherUnknownNoneRead OnlyLocked OutBoot BypassBoot Bypass and Read OnlyMIF.DMTF|Disks|003.22The date and time on which the Device was last cleaned.Time in milliseconds to move from the first location on the Media to the location that is furthest with respect to time. For a DiskDrive, this represents full seek + full rotational delay. For TapeDrives, this represents a search from the beginning of the tape to the most physically distant point. (The end of a tape may be at its most physically distant point, but this is not necessarily true.)MilliSecondsThe sustained data transfer rate in KB/sec that the Device can read from and write to a Media. This is a sustained, raw data rate. Maximum rates or rates assuming compression should not be reported in this property.KiloBytes per SecondTime in milliseconds from 'load' to being able to read or write a Media. For example, for DiskDrives, this is the interval between a disk not spinning to the disk reporting that it is ready for read/write (ie, the disk spinning at nominal speeds). For TapeDrives, this is the time from a Media being injected to reporting that it is ready for an application. This is usually at the tape's BOT area.MilliSecondsTime in milliseconds from being able to read or write a Media to its 'unload'. For example, for DiskDrives, this is the interval between a disk spinning at nominal speeds and a disk not spinning. For TapeDrives, this is the time for a Media to go from its BOT to being fully ejected and accessible to a PickerElement or human operator.MilliSecondsFor a MediaAccessDevice that supports removable Media, the number of times that Media have been mounted for data transfer or to clean the Device. For Devices accessing nonremovable Media, such as hard disks, this property is not applicable and should be set to 0.trueFor a MediaAccessDevice that supports removable Media, the most recent date and time that Media was mounted on the Device. For Devices accessing nonremovable Media, such as hard disks, this property has no meaning and is not applicable.For a MediaAccessDevice that supports removable Media, the total time (in seconds) that Media have been mounted for data transfer or to clean the Device. For Devices accessing nonremovable Media, such as hard disks, this property is not applicable and should be set to 0.Defines 'Units' relative to its use in the property, MaxUnitsBeforeCleaning. This describes the criteria used to determine when the MediaAccessDevice should be cleaned.CIM_MediaAccessDevice.MaxUnitsBeforeCleaningCIM_MediaAccessDevice.UnitsUsedAn unsigned integer indicating the maximum 'units' that can be used, with respect to the AccessDevice, before the Device should be cleaned. The property, UnitsDescription, defines how 'units' should be interpreted.CIM_MediaAccessDevice.UnitsDescriptionAn unsigned integer indicating the currently used 'units' of the AccessDevice, helpful to describe when the Device may require cleaning. The property, UnitsDescription, defines how 'units' should be interpreted.trueCIM_MediaAccessDevice.UnitsDescriptionCIM_MediaAccessDevice.MaxUnitsBeforeCleaningMethod to lock and unlock the media in a removeable AccessDevice. The method takes one parameter as input - a boolean indicating whether to lock or unlock. TRUE indicates that the media should be locked in the Device, FALSE indicates that the media should be unlocked. The method returns 0 if successful, 1 if not supported, and any other value if an error occurred. 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.true 2.6.0Capabilities and managment of a DiskDrive, a subtype of MediaAccessDevice. 2.6.0Capabilities and managment of a DisketteDrive, a subtype of MediaAccessDevice. 2.6.0Capabilities and managment of a CDROMDrive, a subtype of MediaAccessDevice. 2.6.0Capabilities and management of a DVDDrive, a subtype of MediaAccessDevice.The CD and DVD formats that are supported by this Device. For example, the Drive may support "CD-ROM" and "DVD-RAM". In this case, the values 16 and 24 would be written to the array. This property's values align with those defined in PhysicalMedia.MediaType.011617181922232425262733343536373839404142UnknownOtherCD-ROMCD-ROM/XACD-ICD RecordableDVDDVD-RW+DVD-RAMDVD-ROMDVD-VideoDivxCD-RWCD-DACD+DVD RecordableDVD-RWDVD-AudioDVD-5DVD-9DVD-10DVD-18CIM_PhysicalMedia.MediaType 2.6.0Capabilities and managment of a WORMDrive, a subtype of MediaAccessDevice. 2.6.0Capabilities and managment of a MagnetoOpticalDrive, a subtype of MediaAccessDevice. 2.6.0Capabilities and managment of a TapeDrive, a subtype of MediaAccessDevice.EOTWarningZoneSize indicates the size, in bytes, of the area designated as 'end of tape'. Access in this area generates an 'end of tape' warning.BytesMaximum partition count for the TapeDrive.Padding indicates the number of bytes inserted between blocks on a tape Media.BytesTime in milliseconds to move from the most physically distant point on the tape to the beginning.MilliSeconds 2.6.0Statistics related to reading and writing at a specific MediaAccessDevice, or for a specific StorageExtent. Although the same class is used to represent this data, at the instance level the object holds information for the MediaAccessDevice (independent of the StorageExtent), OR for the Extent (independent of its AccessDevice). Note that this class models the same properties as MediaAccessStatData. The latter, however, uses the simplified key mechanisms of the StatisticalData class.trueThe number of attempted read operations.trueThe number of unrecoverable read operations.trueThe number of attempted write operations.trueThe number of unrecoverable write operations.trueThe number of recovered read operations.trueThe number of recovered write operations.trueThe number of recovered seek operations.trueThe number of unrecoverable seek operations.Method 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-2 and 5 reset the 'read operation'-related counters, 3-4 and 6 reset the 'write operation'-related counters, and 7-8 reset the seek-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 Device's instrumentation can also reset its internal processing and counters. In a subclass, 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' can be specified as a Values array qualifier.true012345678AllRead OperationsUnrecoverable Read OperationsWrite OperationsUnrecoverable Write OperationsRecovered Read OperationsRecovered Write OperationsRecovered SeeksUnrecoverable Seeks 2.7.0Statistics related to reading and writing at a specific MediaAccessDevice, or for a specific StorageExtent. The same class is used to represent this data - whether for the MediaAccessDevice (independent of the StorageExtent), OR for the Extent (independent of its AccessDevice). The element whose statistics are described is associated using the relationship, ElementStatisticalData. Note that this class models the same properties as MediaAccessStatInfo. This class, however, uses the simplified key mechanisms of its superclass, StatisticalData.trueThe number of attempted read operations.trueThe number of unrecoverable read operations.trueThe number of attempted write operations.trueThe number of unrecoverable write operations.trueThe number of recovered read operations.trueThe number of recovered write operations.trueThe number of recovered seek operations.trueThe number of unrecoverable seek operations. 2.6.0Where a StorageExtent must be accessed through a MediaAccessDevice, this relationship is described by the MediaPresent association.MIF.DMTF|Storage Devices|001.8trueAntecedentThe MediaAccessDevice.trueDependentThe StorageExtent accessed using the MediaAccessDevice.trueBoolean indicating that the accessed StorageExtent is fixed in the MediaAccessDevice and can not be ejected. 2.6.0StorageExtents can be realized by PhysicalComponents. For example, disks or tapes are realized by PhysicalMedia. Memory is realized by PhysicalMemory. This relationship of Extents to PhysicalComponents is made explicit by the RealizesExtent association. In addition, the StartingAddress of the StorageExtent on the Component is specified here.true1The PhysicalComponent on which the Extent is realized.AntecedenttrueThe StorageExtent that is located on the Component.DependenttrueThe starting address on the PhysicalComponent where the StorageExtent begins. Ending address of the StorageExtent is determined using the NumberOfBlocks and BlockSize properties of the StorageExtent object. 2.6.0Since removable PhysicalMedia can be dual-sided, there is the possibility for StorageExtents to be realized on a single side of the Media. This association is a specialization of the RealizesExtent relationship, adding a Side property to express the Media's orientation details.true1The PhysicalMedia on which the Extent is realized.AntecedenttrueThe StorageExtent that is located on the Component.DependenttrueAn enumeration expressing on which 'Side' the Extent is realized. Since sides can be named by various schemes (0/1 or A/B), both schemes are expressed in the Values array of this property.01234UnknownSide 0Side 1Side ASide B 2.7.0A StorageVolume is an Extent that is presented to the OperatingSystem (for example, by a hardware RAID cabinet), to a FileSystem (for example, by a software volume manager) or to another entity. StorageVolumes do NOT participate in StorageRedundancyGroups. They are directly Realized in hardware or are the end result of assembling lower level Extents. 2.6.0A MediaPartition is a presentation of a contiguous range of logical blocks and has identifying data written on/to it. It may include a signature written by the OS or by an application. This class is a common superclass for Disk and TapePartions. Partitions are directly realized by PhysicalMedia (indicated by the RealizesExtent association) or built on StorageVolumes (indicated by the BasedOn association).Boolean indicating that the Partition is labeled as bootable. (Note that this does not mean that an OperatingSystem is actually loaded on the Partition.) With the advent of bootable Tape and other bootable media, this property is included in the higher level MediaPartition class, rather than in a subclass such as DiskPartition.Boolean indicating that the Partition is available and may be allocated for use.An identifying string written to the Partition. Additional information related to this 'Signature' may be found in the properties, SignatureState and SignatureAlgorithm.CIM_MediaPartition.SignatureStateCIM_MediaPartition.SignatureAlgorithmA free-form string describing the algorithm used to define the Partition Signature. The value of this property is dependent on the Signature's State.CIM_MediaPartition.SignatureCIM_MediaPartition.SignatureStateAn enumeration describing the state of the Partition's identifying Signature string. Information such as "Uninitialized" (value=2), or "Assigned by Owning Application" (value=5) are possible entries. 012345UnknownUnimplementedUninitializedCalculated by Operating SystemCalculated by a Media ManagerAssigned by Owning ApplicationCIM_MediaPartition.SignatureCIM_MediaPartition.SignatureAlgorithmBoolean indicating that the Partition can be grown/extended without reformatting. 2.6.0A DiskPartition is a presentation of a contiguous range of logical blocks that is identifiable by the OperatingSystem via the Partition's type and subtype fields. DiskPartitions should be directly realized by PhysicalMedia (indicated by the RealizesDiskPartition association) or built on StorageVolumes (indicated by the PartitionBasedOnVolume association.Boolean indicating that the DiskPartition is labelled as the primary partition for a ComputerSystem.The type of Partition.0123UnknownPrimaryExtendedLogicalThe 'sub' type of a primary, extended, or logical Partition. The list of possible values corresponds to the decimal representation of the typical values in the Partition record.01234567891011121415161718202223272833353638495152535455606465666780818283848586979910010110210310410511311511611711811912012112812913013113213413514714816116316416516617717918018218318419319619819921621922522722822923023924024124224324424625425565535Empty | MicrosoftDOS 12-bit FATXENIX rootXENIX usrDOS 16-bit FATDOS ExtendedDOS 16-bit FAT (> 32MB)OS/2 HPFS | Win NTFS | QNX Ver 2 | Adv UNIXAIX Boot | OS /2 | Dell (Array) | Commodore DOSAIX Data, CoherentOS/2 Boot Manager32-bit FAT32-bit FATMicrosoft 16-bit FATMicrosoft DOS ExtendedOPUS | OS/2 2.0OS/2 (MOSS) Inactive Type 1Compaq Diagnostics Partition | MicrosoftOS/2 (MOSS) Inactive Type 4OS/2 (MOSS) Inactive Type 6OS/2 (MOSS) Inactive Type 7OS/2 (MOSS) Inactive Type BOS/2 (MOSS) Inactive Type CMicrosoftMicrosoftMicrosoftMicrosoftMicrosoftMicrosoftMicrosoftOS/2 Logical Volume ManagerMicrosoftOS/2 JFS LogPowerQuestVENIX 80286 | Series/1 DiskPersonal RISC BootVeritasVeritasOnTrack Disk Manager Read Only DOSOnTrack Disk Manager Read/Write DOSCPM | Microport System V/386 | OnTrack Disk Mgr | MicrosoftOnTrack Disk ManagerOnTrack Disk Manager Non-DOSMicro House EZ-Drive Non-DOSGolden Bow Vfeature | MicrosoftStorage Dimensions SpeedStor | MicrosoftUNIX - AT&T System V/386 | SCO UNIXNovell NetWare | SpeedstoreNovell NetWareNovell NetWareNovellNovellNovellMicrosoftMicrosoftMicrosoftPC/IX IBMMicrosoftQNX POSIXQNX POSIX (Secondary)QNX POSIX (Secondary)Minix (<=1.4a) | Linux | MicrosoftMinix (>=1.4b) | MicrosoftLinux Swap | PrimeLinux Native | AppleSystem Hibernation for APMMicrosoftHPFS FT mirrorAmoeba | MicrosoftAmoeba BBT | MicrosoftMicrosoftMicrosoftMicrosoftBSD/386MicrosoftMicrosoftMicrosoftMicrosoftMicrosoftBSDI fs | MicrosoftBSDI Swap | MicrosoftMicrosoftMicrosoftMicrosoftSyrinx | HPFS FT Disabled MirrorCP/M 86Digital Research CPM-86 | Concurrent DOS | OUTRIGGERSpeedStor 12-bit FAT ExtendedDOS Read-Only | Storage DimensionsSpeedStor 16-bit FAT ExtendedMicrosoftMicrosoftIntelOS/2 Raw DataStorage DimensionsDOS (Secondary)MicrosoftSpeedStor Large | Storage DimensionsMicrosoftLan Step | SpeedStor | IBM PS/2 IMLBad Block TablesUnknown 2.6.0DiskPartitions should be BasedOn a single StorageVolume (for example, exposed by a hardware RAID cabinet), an SCC VolumeSet, or realized directly in PhysicalMedia. The first two relationships are made explicit in this association. The latter is conveyed by the RealizesDiskPartition association.true1The StorageVolume.AntecedenttrueThe DiskPartition which is built on the Volume.Dependenttrue 2.6.0Capabilities and management of a TapePartition StorageExtent. Note that if a PhysicalTape is not partitioned, only a generic StorageExtent that represents the entire Tape should be instantiated. TapePartitions may be BasedOn other StorageExtents or directly Realized on a PhysicalTape.Number of blocks that are currently unused/not written on the Partition. When this number is multiplied by the BlockSize, inherited from StorageExtent, the total number of bytes available for writing can be computed.true 2.6.0TapePartitionOnSurface represents the ability to have one or more TapePartitions on each surface of a PhysicalTape. The individual surfaces are represented as instances of CIM_StorageExtent.true1The StorageExtent that represents the Tape's surface.AntecedenttrueThe TapePartition which is built on the Extent.Dependenttrue 2.6.0TapePartitions are realized on PhysicalTape. This relationship is made explicit by the RealizesTapePartition association.true1The PhysicalTape on which the Partition is realized.AntecedenttrueThe TapePartition that is located on the Media.Dependenttrue 2.6.0A LogicalDisk is a presentation of a contiguous range of logical blocks that is identifiable by a FileSystem via the Disk's DeviceId (key) field. For example in a Windows environment, the DeviceID field would contain a drive letter. In a Unix environment, it would contain the access path; and in a NetWare environment, DeviceID would contain the volume name. LogicalDisks are typically built on a DiskPartition or StorageVolume (for example, exposed by a software volume manager) using the LogicalDiskBasedOnPartition or LogicalDiskBasedOnVolume associations. However, it can be based on other StorageExtents, like CIM_Memory, in the case of a RAM disk. The latter is described using the LogicalDiskBasedOnExtent relationship. (Indeed, the BasedOnExtent association is the superclass for the BasedOnPartition and BasedOnVolume relationships.) 2.6.0LogicalDisks can be BasedOn a single StorageVolume, Memory (in the case of a RAM Disk), a DiskPartition or other StorageExtent. These relationships are made explicit in this association. Subclasses of the association, LogicalDiskBasedOnPartition and LogicalDiskBasedOnVolume, detail the 'typical' semantics.true1The StorageExtent.AntecedenttrueThe LogicalDisk which is built on the StorageExtent.Dependenttrue 2.6.0LogicalDisks can be BasedOn a single Volume (for example, exposed by a software volume manager), or be BasedOn a DiskPartition directly. The former relationship is made explicit in this association.true1The StorageVolume.AntecedenttrueThe LogicalDisk which is built on the StorageExtent.Dependenttrue 2.6.0LogicalDisks can be BasedOn a DiskPartition. For example, a personal computer's C: drive may be located on a Partition on local PhysicalMedia. In this association of LogicalDisks to Partitions, note that the cardinality of the Antecedent, DiskPartition, is Max (1). This dictates that a LogicalDisk can not span more than one Partition. However, there are cases where this is true. When it occurs, the LogicalDisk is really based on some kind of RAID configuration (for example, a mirror or stripe set). In these scenarios, the LogicalDisk is more correctly BasedOn a StorageVolume. To prevent incorrectly using the LogicalDiskBasedOnPartition association, the Max (1) qualifier was put on the Antecedent reference to the DiskPartition.true1The DiskPartition.AntecedenttrueThe LogicalDisk which is built on the StorageExtent.Dependenttrue 2.6.0StorageError defines blocks of media or memory space that are mapped 'out of use' due to errors. The Key of the class is the StartingAddress of the bytes in error.CIM_StorageExtent.SystemCreationClassNametrue256The scoping System's CreationClassName.CIM_StorageExtent.SystemNametrue256The scoping System's Name.CIM_StorageExtent.CreationClassNametrue256The scoping StorageExtent's CreationClassName.CIM_StorageExtent.DeviceIDtrue64The scoping StorageExtent's DeviceID.trueThe starting address of the bytes in error.The ending address of the bytes in error. truetrue2.6.0The StorageDefect aggregation collects the StorageErrors for a StorageExtent.truetrue11The Extent reference defines the StorageExtent on which the errors occurred.truetrueError references the Error object, defining the starting and ending addresses that are 'mapped out' of the StorageExtent. 2.6.0DiskPartitions can be directly realized on a PhysicalMedia. This is used to model the creation of Partitions on a raw SCSI or IDE drive, using the fdisk (DOS and Unix) or pdisk (Unix) command. The StartingAddress of the DiskPartition on the PhysicalMedia is also specified as a property of this relationship. An alternative is that Partitions can be BasedOn StorageVolumes, such as a VolumeSet or a Volume exposed by a hardware RAID cabinet. The latter relationship is modeled using the DiskPartitionBasedOnVolume association.true1The PhysicalMedia on which the Extent is realized.AntecedenttrueThe DiskPartition that is located on the Media.Dependenttrue 2.7.0Protected StorageExtents map to an underlying StorageExtent. This mapping includes information about the placement of check data on the underlying extent. The mapping is made explicit in this association.trueThe underlying StorageExtent.AntecedenttrueThe Protected Space is built on this StorageExtent.DependenttrueStartingAddressThe starting logical block address of the underlying StorageExtent from which this protected StorageExtent is derived. In SCC, this is equivalent to the START LBA_P field in the Redundancy Group P_Extent Descriptor.MIF.DMTF|Physical Extent|001.2The size of the protected space. Note that this is limited by the Antecedent->NumberOfBlocks, but is included explicitly to provide for the DMTF MIF mapping. In SCC, this is equivalent to the NUMBER OF LBA_P(s) field in the Redundancy Group P_Extent Descriptor.CIM_StorageExtent.NumberOfBlocksMIF.DMTF|Physical Extent|001.3The block size of the protected space. Note that this is limited by the Antecedent->BlockSize. In SCC, this is equivalent to the NUMBER OF BYTES PER LBA_P field in the Redundancy Group P_Extent Descriptor.CIM_StorageExtent.BlockSizeMIF.DMTF|Physical Extent|001.4BytesNumber of bytes of user data to skip before starting the check data interleave.BytesMIF.DMTF|Physical Extent|001.6Number of bytes to be reserved for check data.BytesMIF.DMTF|Physical Extent|001.7Number of bytes to be reserved for user data.BytesMIF.DMTF|Physical Extent|001.8 2.7.0A CompositeExtent is used to model the distribution of user data across one or more underlying StorageExtents, which may or not be protected by some redundancy mechanism. CompositeExtents represent a contiguous range of logical blocks. CompositeExtents may overlap, however, the underlying StorageExtents within the overlap shall not contain any check data. Distribution of check data may be specified using the CompositeExtentBasedOn association.NumberOfBlocksMIF.DMTF|Volume Set|001.3Total number of logically contiguous blocks, of size BlockSize, 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.Number of contiguous underlying StorageExtents counted before looping back to the first underlying StorageExtent of the current stripe. It is the number of StorageExtents forming the user data stripe.MIF.DMTF|Volume Set|001.4Number of StorageExtents to stripe as a collective set. In SCC, this value is defined as the number of stripes to count before continuing to map into the next contiguous set of Extents, beyond the current stripe.MIF.DMTF|Volume Set|001.5True indicates that the data is concatenated across the various StorageExtents in the Group. 2.7.0This specialization defines how data is striped across StorageExtents. Additionally, it includes information on distribution of check data so that the 'usual case' RAID devices can be created in one step.true1The underlying StorageExtent.AntecedenttrueThe CompositeExtent which is built on the StorageExtent.DependenttrueOrderIndextrueOrder matters to CompositeExtents. An example of the use of this property is when defining a RAID-0 striped array of 3 disks. The resultant RAID array is a CompositeExtent that is dependent on (as described by CompositeExtentBasedOn) the StorageExtents that represent each of the 3 disks. The OrderIndex of each CompositeExtentBasedOn 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.MIF.DMTF|Protected Space Extent|001.1True if logical blocks in the underlying StorageExtents are mapped in decrementing order. This property corresponds to the INCDEC value in the SCC-2 Volume Set PS_Extent Descriptor.True if the logical block mapping algorithm includes check data bytes. This property corresponds to the NOCHKSKIP attribute in the SCC-2 Volume Set PS_Extent Descriptor.The total number of blocks that will be consumed on the Dependent Extent. This is limited by the Antecedent's NumberOfBlocks, but is included explicitly to provide for the DMTF MIF mapping. In SCC, this is equivalent to the NUMBER OF LBA_PS(s) field in the Volume Set PS_Extent Descriptor.CIM_StorageExtent.NumberOfBlocksMIF.DMTF|Protected Space Extent|001.3The Dependent's BlockSize is limited by the Antecedent's. In SCC, this is equivalent to the NUMBER OF BYTES PER LBA_PS field in the RedundancyGroup P_Extent Descriptor.CIM_StorageExtent.BlockSizeMIF.DMTF|Protected Space Extent|001.4BytesNumber of bytes which form the stripe size for the Dependent StorageExtent. If the CompositeExtent is concatenated instead of striped, then UserDataStripeDepth should be set to zero.BytesMIF.DMTF|Protected Space Extent|001.6Number of bytes of user data to skip before starting the check data interleave.BytesMIF.DMTF|Physical Extent|001.6Number of bytes to be reserved for check data.BytesMIF.DMTF|Physical Extent|001.7Number of bytes to be reserved for user data.BytesMIF.DMTF|Physical Extent|001.8 CIMProtectedExtentBasedOnCIM_CompositeExtentBasedOn2.7.0Deprecated - use CIM_ProtectedExtentBasedOn or CIM_CompositeExtentBasedOn instead. The information on check and user data is better expressed in the association that layers the storage, than in the extent itself. A PhysicalExtent is used to model an SCC RAID implementation. It defines the consecutive addressable block addresses on a single storage device, that are treated as a single StorageExtent and that are in the same StorageRedundancyGroup. An alternate possibility, if automatic configuration is used, is to instantiate or extend the AggregatePExtent class.BlockSizeCIM_CompositeExtentBasedOn.BlockSizeCIM_ProtectedExtentBasedOn.BlockSizeMIF.DMTF|Physical Extent|001.4Size 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.BytesNumberOfBlocksCIM_CompositeExtentBasedOn.NumberOfBlocksCIM_ProtectedExtentBasedOn.NumberOfBlocksMIF.DMTF|Physical Extent|001.3Total number of logically contiguous blocks, of size BlockSize, 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.CIM_CompositeExtentBasedOn.UnitsBeforeCheckDataInterleaveCIM_ProtectedExtentBasedOn.UnitsBeforeCheckDataInterleaveNumber of bytes of user data to skip before starting the check data interleave.BytesMIF.DMTF|Physical Extent|001.6CIM_CompositeExtentBasedOn.UnitsOfCheckDataCIM_ProtectedExtentBasedOn.UnitsOfCheckDataNumber of bytes to be reserved for check data.BytesMIF.DMTF|Physical Extent|001.7CIM_CompositeExtentBasedOn.UnitsOfUserDataCIM_ProtectedExtentBasedOn.UnitsOfUserDataNumber of bytes to be reserved for user data.BytesMIF.DMTF|Physical Extent|001.8 CIM_ProtectedExtentBasedOnCIM_CompositeExtentBasedOn2.7.0Deprecated - use CIM_ProtectedExtentBasedOn or CIM_CompositeExtentBasedOn instead. The information on check and user data is better expressed in the association that layers the storage, than in the extent itself. A ProtectedSpaceExtent is used to model an SCC RAID implementation. ProtectedSpaceExtent defines addressable logical block addresses, treated as a single Extent, located on one or more PhysicalExtents. ProtectedSpaceExtents exclude any logical blocks mapped as check data and contain user data stripe depth mapping information. An alternate possibility, if automatic configuration is used, is to instantiate or extend the AggregatePSExtent class.BlockSizeCIM_CompositeExtentBasedOn.BlockSizeCIM_ProtectedExtentBasedOn.BlockSizeMIF.DMTF|Protected Space Extent|001.4Size 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.BytesNumberOfBlocksCIM_CompositeExtentBasedOn.NumberOfBlocksCIM_ProtectedExtentBasedOn.NumberOfBlocksThe number of user data blocks contained in this Extent.MIF.DMTF|Protected Space Extent|001.3CIM_CompositeExtentBasedOn.UserDataStripeDepthFor a ProtectedSpaceExtent that is allocated to a VolumeSet (i.e. is named in a CIM_VolumeSetBasedOnPSExtent association), this property is the number of user data bytes placed on this ProtectedSpaceExtent before moving on to the next ProtectedSpaceExtent in the VolumeSet. Otherwise, this ProtectedSpaceExtent is considered to be unallocated, and this property shall be set to zero (0h.)BytesMIF.DMTF|Protected Space Extent|001.6 2.7.0CIM_ProtectedExtentBasedOnCIM_CompositeExtentBasedOnCovered by ProtectedExtentBasedOn or CompositeExtentBasedOn, since PhysicalExtent itself is deprecated in lieu of these associations. ProtectedSpaceExtents are BasedOn a PhysicalExtent. This relationship is made explicit by this association.trueCIM_CompositeExtentBasedOn.AntecedentCIM_ProtectedExtentBasedOn.AntecedentThe PhysicalExtent.AntecedenttrueCIM_CompositeExtentBasedOn.DependentCIM_ProtectedExtentBasedOn.DependentThe ProtectedSpaceExtent which is built on the PhysicalExtent.DependenttrueStartingAddressCIM_CompositeExtentBasedOn.StartingAddressCIM_ProtectedExtentBasedOn.StartingAddressThe starting logical block address of the PhysicalExtent from which this ProtectedSpaceExtent is derived.MIF.DMTF|Protected Space Extent|001.2 CIM_CompositeExtent2.7.0VolumeSet is deprecated in lieu of CompositeExtent, which removes the restriction that the Set must be exported. A VolumeSet can be used to model an SCC RAID implementation. VolumeSets represent a contiguous range of logical blocks presented to the operating environment. VolumeSets may overlap. However, the underlying PhysicalExtents within the overlap shall not contain any check data. They are BasedOn one or more ProtectedSpaceExtents. These BasedOn associations should be instantiated or subclassed as needed.NumberOfBlocksCIM_CompositeExtent.NumberOfBlocksMIF.DMTF|Volume Set|001.3Total number of logically contiguous blocks, of size BlockSize, 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.CIM_CompositeExtent.ExtentStripeLengthNumber of contiguous ProtectedSpaceExtents counted before looping back to the first ProtectedSpaceExtent of the current stripe. It is the number of Extents forming the user data stripe.MIF.DMTF|Volume Set|001.4CIM_CompositeExtent.ExtentInterleaveDepthNumber of ProtectedSpaceExtents to stripe as a collective set. In SCC, this value is defined as the number of stripes to count before continuing to map into the next contiguous set of Extents, beyond the current stripe.MIF.DMTF|Volume Set|001.5No valueVolumeSets in SCC have additional status information beyond that captured in the Availability and other properties, inherited from ManagedSystemElement. This additional information (for example, "Protection Disabled", value=9) is captured in the VolumeStatus property.01234567891011121314OtherUnknownNone/Not ApplicableBrokenData LostDynamic ReconfigExposedFractionally ExposedPartially ExposedProtection DisabledReadyingRebuildRecalculateSpare in UseVerify In Progress 2.7.0CIM_CompositeExtentBasedOnThis association is deprecated in lieu of CompositeExtentBasedOn, since VolumeSets and ProtectedSpaceExtents are themselves deprecated. The relationship describes that VolumeSets are BasedOn on one or more ProtectedSpaceExtents.true1CIM_CompositeExtentBasedOn.AntecedentThe ProtectedSpaceExtent.AntecedenttrueCIM_CompositeExtentBasedOn.DependentThe VolumeSet which is built on the ProtectedSpaceExtent.DependenttrueCIM_CompositeExtentBasedOn.LBAsMappedByDecrementingTrue if logical blocks in the ProtectedSpaceExtent are mapped in decrementing order. This property corresponds to the INCDEC value in the SCC-2 Volume Set PS_Extent Descriptor.CIM_CompositeExtentBasedOn.LBAMappingIncludesCheckDataTrue if the logical block mapping algorithm includes check data bytes. This property corresponds to the NOCHKSKIP attribute in the SCC-2 Volume Set PS_Extent Descriptor. 2.7.0CIM_BasedOnThis association describes that LogicalDisks can be BasedOn a VolumeSet. However, there is no need for the specificity of this association. It is deprecated in lieu of the generic BasedOn relationship.true1CIM_BasedOn.AntecedentThe VolumeSet.Antecedenttrue CIM_StorageExtentCIM_CompositeExtentBasedOn2.7.0This class is deprecated in lieu of the generic StorageExtent object and the ProtectedExtentBasedOn association. An AggregatePExtent is used to model an SCC RAID implementation. AggregatePExtents provide summary information about the addressable logical blocks which are in the same StorageRedundancyGroup and reside on the same storage device. This is an alternative grouping for PhysicalExtents, when only summary information is needed or when automatic configuration is used.NumberOfBlocksCIM_CompositeExtentBasedOn.NumberOfBlocksCIM_StorageExtent.NumberOfBlocksTotal number of blocks (including the check data blocks) contained in this AggregatePExtent. The block size (an inherited property) should be set to the same value as for the MediaAccessDevice associated with this Extent.MIF.DMTF|Aggregate Physical Extent|001.2CIM_CompositeExtentBasedOn.UnitsOfCheckDataThe number of blocks contained in this AggregatePExtent to be used as check data. If this AggregatePExtent is available, then this value shall be zero.MIF.DMTF|Aggregate Physical Extent|001.3 CIM_StorageExtentCIM_CompositeExtentBasedOn2.7.0Similar to AggregatePExtent, this class is deprecated in lieu of the generic StorageExtent object and the ProtectedExtentBasedOn association. An AggregatePSExtent is used to model an SCC RAID implementation. AggregatePSExtents define the number of addressable logical blocks on a single storage device, excluding any logical blocks mapped as check data. This is an alternative grouping for ProtectedSpaceExtents, when only summary information is needed or when automatic configuration is used.NumberOfBlocksCIM_CompositeExtentBasedOn.NumberOfBlocksCIM_StorageExtent.NumberOfBlocksTotal number of user data blocks that are contained in this Extent.MIF.DMTF|Aggregate Protected Space Extent|001.2 CIM_ProtectedSpaceBasedOn2.7.0This association is deprecated in lieu of ProtectedSpaceBasedOn, since PhysicalExtents and AggregatePSExtents are themselves deprecated. The association describes that AggregatePSExtents are BasedOn a single PhysicalExtent.true1CIM_ProtectedSpaceBasedOn.AntecedentThe PhysicalExtent.AntecedenttrueCIM_ProtectedSpaceBasedOn.DependentThe AggregatePSExtent which is built on the PhysicalExtent.Dependenttrue CIM_ProtectedSpaceBasedOn2.7.0This association is deprecated in lieu of ProtectedSpaceBasedOn, since AggregatePExtents and AggregatePSExtents are themselves deprecated. The association describes that AggregatePSExtents are BasedOn a single AggregatePExtent.true1CIM_ProtectedSpaceBasedOn.AntecedentThe AggregatePExtent.AntecedenttrueCIM_ProtectedSpaceBasedOn.DependentThe AggregatePSExtent which is built on the AggregatePExtent.Dependenttrue CIM_ExtentRedundancyComponent2.7.0Describes the PhysicalExtents participating in a StorageRedundancyGroup. However, there is no need for the specificity of this association. It is deprecated in lieu of the generic ExtentRedundancyComponent relationship, its superclass.truetrueCIM_ExtentRedundancyComponent.GroupComponentThe StorageRedundancyGroup.GroupComponenttruetrueCIM_ExtentRedundancyComponent.PartComponentThe PhysicalExtent participating in the RedundancyGroup.PartComponenttrue CIM_ExtentRedundancyComponent2.7.0Describes the AggregatePExtent in a StorageRedundancyGroup. However, there is no need for the specificity of this association. It is deprecated in lieu of the generic ExtentRedundancyComponent relationship, its superclass.truetrueCIM_ExtentRedundancyComponent.GroupComponentThe StorageRedundancyGroup.GroupComponenttruetrueCIM_ExtentRedundancyComponent.PartComponentThe AggregatePExtent participating in the RedundancyGroup.PartComponenttrue 2.7.0CIM_RealizesExtentPhysicalExtents are realized on a PhysicalMedia. This is described by RealizesPExtent. However, there is no need for the specificity of this association. It is deprecated in lieu of the generic RealizesExtent relationship.true1CIM_RealizesExtent.AntecedentThe PhysicalMedia on which the Extent is realized.AntecedenttrueCIM_RealizesExtent.DependentThe PhysicalExtent that is located on the Media.Dependenttrue 2.7.0CIM_RealizesExtentAggregatePExtents are realized on a PhysicalMedia. This is described by RealizesAggregatePExtent. However, there is no need for the specificity of this association. It is deprecated in lieu of the generic RealizesExtent relationship.true1CIM_RealizesExtent.AntecedentThe PhysicalMedia on which the Extent is realized.AntecedenttrueCIM_RealizesExtent.DependentThe AggregatePExtent that is located on the Media.Dependenttrue 2.7.0No ValueDeprecated. Snapshots are now modeled in a more abstrct way using StorageExtent and StorageSynchronized. The Snapshot class is an optional construct. It can be used to represent an Extent that contains a full copy of another Extent, or the changes to that Extent when performing a delta-based (delta before or delta after) copy. Snapshot's definition in CIM is not equivalent to the act of creating a volume or file-based snapshot, or a point in time copy. It is at a much lower level and represents the use of storage to hold a copied image of an Extent, or to hold changes to an Extent. Use of the Snapshot object when making a full copy is only recommended if the purpose is to describe the existence of a copy. (This use will be very infrequent.) The problem with describing an Extent solely as a 'snapshot' is that when the snapshot/copy is broken, the object must be destroyed. Typically, this object still holds valid data, and would have to be reinstantiated. If the 'full copy' object is to be treated as a StorageVolume or more general Extent, then it should be modeled as such from the beginning - i.e., not as an instance of Snapshot but as an instance of a generic StorageExtent or StorageVolume. In this case, the Synchronized association would be used to describe that one StorageExtent is synchronized with another. When describing a delta-based snapshot/point in time copy, the Snapshot object represents the store holding the before/after image changes to the original Extent. For example, when doing a 'delta before' Snapshot, the resultant target would be modeled as a StorageExtent that is BasedOn the original Extent and the instance of Snapshot (that holds the changes to the original Extent).CIM_Synchronized.SyncMaintainedTrue indicates that the snapshot is synced.CIM_Synchronized.WhenSyncedThe time stamp indicating when the sync occurred. 2.7.0No ValueDeprecated. Snapshots are now modeled in a more abstract way using StorageExtent and CIM_StorageSynchronized. SnapshotOfExtent is an association between an Extent and its Snapshot. This relationship is made explicit in this association.trueNo ValueAntecedent1The StorageExtent.trueNo ValueDependentThe Snapshot.trueCIM_StorageSynchronized.CopyTypeThe type of snapshot.01234OtherUnknownCopyBefore DeltaAfter Delta 2.7.0Indicates that two Storage objects were replicated at the specified point in time. If the CopyType property is set to 'Sync' (=3), then synchronization of the Storage objects is preserved.trueSystemElementSystemElement represents the Storage that is the source of the replication.trueSyncedElementSyncedElement represents the Storage that is the target of the replication.trueCopyType describes the Replication Policy. Values are: Async: create and maintain an asynchronous copy of the source. Sync: create and maintain a synchronized copy of the source. UnSyncAssoc: create an unsynchronized copy and maintain an association to the source.234..32768..65535AsyncSyncUnSyncAssocDMTF ReservedVendor Specific 2.7.0StorageSetting is roughly equivalent to a Service Level Agreement (SLA) It defines the characteristics, qualities of service and goals when used in a CreateOrModifyElementFromStoragePool or CreateOrModifyStoragePool method in the StorageConfigurationService. It specifies a series of properties with Maximum and Minimum values that define the (inclusive) bounds that the object should maintain. Note that the setting is associated to a StorageVolume, using ElementSetting.trueIndicates the desired value for No Single Point of Failure. Possible values are false = single point of failure, and true = no single point of failure.true1DataRedundancyMax describes the maximum number of complete copies of data to be maintained. Examples would be RAID 5 where 1 copy is maintained and RAID 1 where 2 or more copies are maintained. Possible values are 1 to n. The desired redundancy is specified using DataRedundancyGoal, while the minimum is defined by DataRedundancyMin.CIM_StorageSetting.DataRedundancyMinCIM_StorageSetting.DataRedundancyGoaltrue1DataRedundancyMin describes the minimum number of complete copies of data to be maintained. Examples would be RAID 5 where 1 copy is maintained and RAID 1 where 2 or more copies are maintained. Possible values are 1 to n. The desired redundancy is specified using DataRedundancyGoal, while the maximum is defined by DataRedundancyMax.CIM_StorageSetting.DataRedundancyMaxCIM_StorageSetting.DataRedundancyGoaltrue1DataRedundancyGoal describes the desired number of complete copies of data to be maintained. Examples would be RAID 5 where 1 copy is maintained and RAID 1 where 2 or more copies are maintained. Possible values are 1 to n. The bounds (max and min) for redundancy are defined using the properties, DataRedundancyMax and DataRedundancyMin.CIM_StorageSetting.DataRedundancyMaxCIM_StorageSetting.DataRedundancyMintruePackageRedundancyMax describes the maximum number of redundant packages to be used. For example, in the storage domain, package redundancy describes how many disk spindles can fail without data loss including, at most, one spare. An example would be RAID5 with a spare disk which would have a PackageRedundancy of 2. Possible values are 0 to n. The desired redundancy is specified using PackageRedundancyGoal, while the minimum is defined by PackageRedundancyMin.CIM_StorageSetting.PackageRedundancyMinCIM_StorageSetting.PackageRedundancyGoaltruePackageRedundancyMin describes the minimum number of redundant packages to be used. For example, in the storage domain, package redundancy describes how many disk spindles can fail without data loss including, at most, one spare. An example would be RAID5 with a spare disk which would have a PackageRedundancy of 2. Possible values are 0 to n. The desired redundancy is specified using PackageRedundancyGoal, while the maximum is defined by PackageRedundancyMax.CIM_StorageSetting.PackageRedundancyMaxCIM_StorageSetting.PackageRedundancyGoaltruePackageRedundancyGoal describes the desired number of redundant packages to be used. For example, in the storage domain, package redundancy describes how many disk spindles can fail without data loss including, at most, one spare. An example would be RAID5 with a spare disk which would have a PackageRedundancy of 2. Possible values are 0 to n. The bounds (max and min) for redundancy are defined using the properties, PackageRedundancyMax and PackageRedundancyMin.CIM_StorageSetting.PackageRedundancyMaxCIM_StorageSetting.PackageRedundancyMin1100DeltaReservationMax is a number between 1 (1%) and a 100 (100%) which specifies the maximum amount of space that should be reserved in a replica for caching changes. For a complete copy this would be 100%. The desired reservation is specified using DeltaReservationGoal, while the minimum is defined by DeltaReservationMin.PercentageCIM_StorageSetting.DeltaReservationMinCIM_StorageSetting.DeltaReservationGoal1100DeltaReservationMin is a number between 1 (1%) and a 100 (100%) which specifies the minimum amount of space that should be reserved in a replica for caching changes. For a complete copy this would be 100%. The desired reservation is specified using DeltaReservationGoal, while the maximum is defined by DeltaReservationMax.PercentageCIM_StorageSetting.DeltaReservationMaxCIM_StorageSetting.DeltaReservationGoal1100DeltaReservationGoal is a number between 1 (1%) and a 100 (100%) which specifies the desired amount of space that should be reserved in a replica for caching changes. For a complete copy this would be 100%. The bounds (max and min) for the reservation are defined using the properties, DeltaReservationMax and DeltaReservationMin.PercentageCIM_StorageSetting.DeltaReservationMinCIM_StorageSetting.DeltaReservationMax 2.7.0A pool of Storage that is managed within the scope of a particular System. StoragePools may consist of component StoragePools or StorageExtents. StorageExtents that belong to the StoragePool have a Component relationship to the StoragePool. StorageExtents/StoragePools that are elements of a pool have their available space aggregated into the pool. StoragePools and StorageVolumes may be created from StoragePools. This is indicated by the AllocatedFromStoragePool association. StoragePool is scoped to a system by the HostedStoragePool 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'.true256A unique name in the context of the System that identifies this pool.Maximum available formatted space (in bytes) available via this pool.Bytes 2.7.0A subclass of Capabilities that defines the Capabilities of a StorageService or StoragePool. For example, an instance of StorageCapabilities could beassociated with either a StorageConfigurationService or StoragePool by using ElementCapabilities.Enumeration indicating the type of element to which this StorageCapabilities applies.0123456UnknownReservedAny TypeStorageVolumeStorageExtentStoragePoolStorageConfigurationServiceIndicates whether or not the associated element supports no single point of failure. Values are: FALSE = does not support no single point of failure, and TRUE = supports no single point of failure.CIM_StorageCapabilities.NoSinglePointOfFailureDefaultIndicates the default value for the NoSinglePointOfFailure property.CIM_StorageCapabilities.NoSinglePointOfFailure1DataRedundancyMax describes the maximum number of complete copies of data that can be maintained. Examples would be RAID 5 (where 1 copy is maintained) and RAID 1 (where 2 or more copies are maintained). Possible values are 1 to n. The default redundancy is specified using DataRedundancyDefault, while the minimum is defined by DataRedundancyMin.CIM_StorageCapabilities.DataRedundancyMinCIM_StorageCapabilities.DataRedundancyDefault1DataRedundancyMin describes the minimum number of complete copies of data that can be maintained. Examples would be RAID 5 where 1 copy is maintained and RAID 1 where 2 or more copies are maintained). Possible values are 1 to n. The default redundancy is specified using DataRedundancyDefault, while the maximum is defined by DataRedundancyMax.CIM_StorageCapabilities.DataRedundancyMaxCIM_StorageCapabilities.DataRedundancyDefault1DataRedundancyDefault describes the default number of complete copies of data that can be maintained. Examples would be RAID 5 where 1 copy is maintained and RAID 1 where 2 or more copies are maintained. Possible values are 1 to n. The bounds for the redundancy (max and min) are defined by DataRedundancyMax and DataRedundancyMin.CIM_StorageCapabilities.DataRedundancyMaxCIM_StorageCapabilities.DataRedundancyMinPackageRedundancyMax describes the maximum number of redundant packages that can be used. For example, in the storage domain, package redundancy describes how many disk spindles can fail without data loss including, at most, one spare. An example would be RAID5 with a spare disk which would have a PackageRedundancy of 2. Possible values are 0 to n.The default redundancy is specified using PackageRedundancyDefault, while the maximum is defined by PackageRedundancyMax.CIM_StorageCapabilities.PackageRedundancyMinCIM_StorageCapabilities.PackageRedundancyDefaultPackageRedundancyMin describes the minimum number of redundant packages that can be used. For example, in the storage domain, package redundancy describes how many disk spindles can fail without data loss including, at most, one spare. An example would be RAID5 with a spare disk which would have a PackageRedundancy of 2. Possible values are 0 to n.The default redundancy is specified using PackageRedundancyDefault, while the minimum is defined by PackageRedundancyMin.CIM_StorageCapabilities.PackageRedundancyMaxCIM_StorageCapabilities.PackageRedundancyDefaultPackageRedundancyDefault describes the default number of redundant packages that will be used. For example, in the storage domain, package redundancy describes how many disk spindles can fail without data loss including, at most, one spare. An example would be RAID5 with a spare disk which would have a PackageRedundancy of 2. Possible values are 0 to n.The bounds for redundancy are specified using the properties, PackageRedundancyMax and PackageRedundancyMin.CIM_StorageCapabilities.PackageRedundancyMinCIM_StorageCapabilities.PackageRedundancyMax1100DeltaReservatioMax is a number between 1 (1%) and a 100 (100%) that specifies the maximum amount of space reserved in a replica for caching changes. For a complete copy this would be 100%, but it can be lower in some implementations. This parameter sets the upper limit, while DeltaReservationMin sets the lower limit.PercentageCIM_StorageCapabilities.DeltaReservationMinCIM_StorageCapabilities.DeltaReservationDefault1100DeltaReservationMin is a number between 1 (1%) and a 100 (100%) that specifies the minimum amount of space that should be reserved in a replica for caching changes. For a complete copy this would be 100%, but it can be lower in some implementations. This parameter sets the lower limit, while DeltaReservationMax sets the upper limit.PercentageCIM_StorageCapabilities.DeltaReservationMaxCIM_StorageCapabilities.DeltaReservationDefault1100Delta reservation is a number between 1 (1%) and a 100 (100%) that specifies how much space should be reserved by default in a replica for caching changes. For a complete copy this would be 100%, but it can be lower in some implementations. This parameter sets the default value, while DeletaReservationMax and DeltReservationMin set the upper and lower bounds.PercentageCIM_StorageCapabilities.DeltaReservationMaxCIM_StorageCapabilities.DeltaReservationMin 2.7.0This service allows the active management of a Storage Server. It allows jobs to be started for the creation, modification and deletion of storage objects (StoragePools and StorageVolumes).Starts a job to create (or modify) a StoragePool. The StoragePool will be (or must be) scoped to the same System as this Service. One of the parameters for this method is Size. As an input parameter, Size specifies the desired size of the pool. As an output parameter, it specifies the size achieved. Space is taken from either or both of the specified input StoragePools and StorageExtents (InPools and InExtents). The capability requirements that the Pool must support are defined using the Goal parameter. If the requested pool size cannot be created, no action will be taken, the Return Value will be 4097/0x1001, and the output value of Size will be set to the nearest possible size. If 0 is returned, then the task completed successfully and the use of ConcreteJob was not required. If the task will take some time to complete, a ConcreteJob will be created and its reference returned in the output parameter Job.0123456..409640974098..3276732768..65535Job Completed with No ErrorNot SupportedUnknownTimeoutFailedInvalid ParameterIn UseDMTF ReservedMethod Parameters Checked - Job StartedSize Not SupportedMethod ReservedVendor SpecifictrueA end user relevant name for the pool being created. If NULL, then a system supplied default name can be used. The value will be stored in the 'ElementName' property for the created pool. If not NULL, this parameter will supply a new name when modifying an existing pool.truefalseReference to the job (may be null if job completed).trueReference to an instance of StorageSetting that defines the desired capabilities of the StoragePool. If set to a null value, the default configuration from the source pool will be used. If not NULL, this parameter will supply a new Goal setting when modifying an existing pool.truetrueAs an input parameter this specifies the desired pool size in bytes. As an output parameter this specifies the size achieved.BytestrueArray of strings containing representations of references to CIM_StoragePool instances, that are used to create the Pool or modify the source pools.trueArray of strings containing representations of references to CIM_StorageExtent instances, that are used to create the Pool or modify the source extents.truetrueAs an input parameter: if null, creates a new StoragePool. If not null, modifies the referenced Pool. When returned, it is a reference to the resulting StoragePool.Start a job to create (or modify) a specified element (for example a StorageVolume or StorageExtent) from a StoragePool. One of the parameters for this method is Size. As an input parameter, Size specifies the desired size of the element. As an output parameter, it specifies the size achieved. Space is taken from the input StoragePool. The desired settings for the element are specified by the Goal parameter. If the requested size cannot be created, no action will be taken, and the Return Value will be 4097/0x1001. Also, the output value of Size is set to the nearest possible size. If 0 is returned, the function completed successfully and no ConcreteJob instance was required. If 4096/0x1000 is returned, a ConcreteJob will be started to create the element. The Job's reference will be returned in the output parameter Job.0123456..409640974098..3276732768..65535Job Completed with No ErrorNot SupportedUnknownTimeoutFailedInvalid ParameterIn UseDMTF ReservedMethod Parameters Checked - Job StartedSize Not SupportedMethod ReservedVendor SpecifictrueA end user relevant name for the element being created. If NULL, then a system supplied default name can be used. The value will be stored in the 'ElementName' property for the created element. If not NULL, this parameter will supply a new name when modifying an existing element.trueEnumeration indicating the type of element being created or modified. If the input parameter TheElement is specified when the operation is a 'modify', this type value must match the type of that instance.0123..32768..65535UnknownReservedStorageVolumeStorageExtentDMTF ReservedVendor SpecifictruefalseReference to the job (may be null if job completed).trueThe requirements for the element to maintain. If set to a null value, the default configuration from the source pool will be used. This parameter should be a reference to a Setting or Profile appropriate to the element being created. If not NULL, this parameter will supply a new Goal when modifying an existing element.truetrueAs an input parameter Size specifies the desired size. If not NULL, this parameter will supply a new size when modifying an existing element.As an output parameter Size specifies the size achieved.BytestrueThe Pool from which to create the element. This parameter must be set to null if the input parameter TheElement is specified (in the case of a 'modify' operation).truetrueAs an input parameter: if null, creates a new element. If not null, then the method modifies the specified element. As an output parameter, it is a reference to the resulting element.Start a job to delete a StoragePool. The freed space is returned source StoragePools (indicated by AllocatedFromStoragePool) or back to underlying storage extents. If 0 is returned, the function completed successfully, and no ConcreteJob was required. If 4096/0x1000 is returned, a ConcreteJob will be started to delete the StoragePool. A reference to the Job is returned in the Job parameter.0123456..40964097..3276732768..65535Job Completed with No ErrorNot SupportedUnknownTimeoutFailedInvalid ParameterIn UseDMTF ReservedMethod Parameters Checked - Job StartedMethod ReservedVendor SpecifictruefalseReference to the job (may be null if job completed).trueReference to the pool to delete.Start a job to delete an element previously created from a StoragePool. The freed space is returned to the source StoragePool. If 0 is returned, the function completed successfully and no ConcreteJob was required. If 4096/0x1000 is returned, a ConcreteJob will be started to delete the element. A reference to the Job is returned in the Job parameter.0123456..40964097..3276732768..65535Job Completed with No ErrorNot SupportedUnknownTimeoutFailedInvalid ParameterIn UseDMTF ReservedMethod Parameters Checked - Job StartedMethod ReservedVendor SpecifictruefalseReference to the job (may be null if job completed).trueReference to the element to return to the StoragePool.Start a job to create a new storage object which is a replica of the specified source storage object. (SourceElement). Note that using the input paramter, CopyType, this function can be used to instantiate the replica, and to create an ongoing association between the source and replica. If 0 is returned, the function completed successfully and no ConcreteJob instance is created. If 4096/0x1000 is returned, a ConcreteJob is started, a reference to which is returned in the Job output parameter.0123456..40964097..3276732768..65535Job Completed with No ErrorNot SupportedUnknownTimeoutFailedInvalid ParameterIn UseDMTF ReservedMethod Parameters Checked - Job StartedMethod ReservedVendor SpecifictrueA end user relevant name for the element being created. If NULL, then a system supplied default name can be used. The value will be stored in the 'ElementName' property for the created element.truefalseReference to the job (may be null if job completed).truetrueThe source storage object which may be a StorageVolume or storage object.truefalseReference to the created target storage element (i.e., the replica).trueThe definition for the StorageSetting to be maintained by the target storage object (the replica).trueThe underlying storage for the target element (the replica) will be drawn from TargetPool if specified, otherwise the allocation is implementation specific.trueCopyType describes the type of copy that will be made. Values are: Async: Create and maintain an asynchronous copy of the source. Sync: Create and maintain a synchronized copy of the source. UnSyncAssoc: Create an unsynchronized copy and maintain an association to the source. UnSyncUnAssoc: Create unassociated copy of the source element.2345..32768..65535AsyncSyncUnSyncAssocUnSyncUnAssocDMTF ReservedVendor SpecificStarts a job to modify the synchronization association between two storage objects. If 0 is returned, the function completed successfully and no ConcreteJob instance was created. If 4096/0x1000 is returned, a ConcreteJob was started. A reference to this Job is returned in the Job output parameter.0123456..40964097..3276732768..65535Job Completed with No ErrorNot SupportedUnknownTimeoutFailedInvalid ParameterIn UseDMTF ReservedMethod Parameters Checked - Job StartedMethod ReservedVendor SpecifictrueOperation describes the type of modification to be made to the replica. Values are: Detach: 'Forget' the synchronization between two storage objects. Start to treat the objects as independent. Fracture: Suspend the synchronization between two storage objects. The association and (typically) changes are remembered to allow a fast resynchronization. This may be used during a backup cycle to allow one of the objects to be copied while the other remains in production. Resync Replica: Re-establish the synchronization of a replica. This will negate the action of a previous Fracture operation. Restore from Replica: Renew the contents of the original storage object from a replica.012345..32768..65535 DMTF ReservedDMTF ReservedDetachFractureResync ReplicaRestore from ReplicaDMTF ReservedVendor SpecifictruefalseReference to the job (may be null if job completed).trueThe referenced to the StorageSynchronized association describing the storage source/replica relationship. 2.7.1This subclass of StorageSetting allows a client to specify 'hint's for optimization of the volume performance. The effect of these hints is implementation dependent.010This hint is an indication from a client of the importance placed on data availability. Values are 0=Don't Care to 10=Very Important.010This hint is an indication from a client of the randomness of accesses. Values are 0=Entirely Sequential to 10=Entirely Random.010This hint is an indication from a client of the direction of accesses. Values are 0=Entirely Read to 10=Entirely Write.This hint is an indication from a client of the optimal access sizes (in bytes). Since this property is an array, several sizes can be specified. Bytes010This hint is an indication from a client how important access latency is. Values are 0=Don't Care to 10=Very Important.010This hint is an indication from a client of bandwidth prioritization. Values are 0=Don't Care to 10=Very Important.010This hint is an indication of the importance the client places on the cost of storage. Values are 0=Don't Care to 10=Very Important. A StorageVolume provider might choose to place data on low cost or high cost drives based on this parameter.010This hint is an indication of the importance placed on storage space efficiency by the client. Values are 0=Don't Care to 10=Very Important. A StorageVolume provider might choose different RAID levels based on this hint. 2.7.0AllocatedFromStoragePool is an association describing how LogicalElements are allocated from underlying StoragePools. These elements typically would be subclasses of StorageExtents or StoragePools.trueAntecedentThe StoragePool.trueDependentThe subsidiary element.trueSpace consumed from this Pool, in bytes.Bytes true2.7.0SystemStoragePool is a specialization of SystemComponent association that establishes that the StoragePool is defined in the context of the System.truetrue11The parent system in the Association.GroupComponenttruetrueThe StoragePool that is a component of a System.PartComponenttrue Service to provide reports on current configuration and potential for growth. The service may be used in several circumstances: - To report growth potential (how many can I have) - To report information on objects not directly modeled for performance or other reasons. It can also report counts of 'things' or counts of 'units'. For example, the number of disk drives could be reported or the capacity that they would provide.Returns a list of classes that the given ManagedElement supports or has installed.01234..32768..65535SuccessNot SupportedUnknownTimeoutFailedDMTF ReservedVendor Specifictrue23SupportsInstalledThe type of inquiry to be performed.trueFalse : Only report on elements directly contained in/attached to the given ManagedElement. True : Report on all objects contained in/attached to the given ManagedElement.trueThe target of query, for example a rack or a chassis.truefalseArray containing the class names (typically the leaf classes) that the given ManagedElement can support or has installed.Returns a list of UnitTypes that are installed for a given ClassType on a given ManagedElement.01234..32768..65535SuccessNot SupportedUnknownTimeoutFailedDMTF ReservedVendor Specifictrue23SupportedInstalledThe type of inquiry to be performed.trueFalse : Only report on elements directly contained in/attached to the given ManagedElement. True : Report on all objects contained in/attached to the given ManagedElement.trueThe target of query, for example a rack or a chassis.trueThe ClassType for the query. This should be a entry returned in the GetClassTypes.ClassTypes property.truefalseA list of supported UnitTypes.2345678910..32768..65535NoneFront SideBack SideContainedConnectedI/OMemoryStorageMediaLocationMegabytesDMTF ReservedVendor SpecificCIM_ConfigurationReportingService.ReportCapacity(UnitType)Returns the maximum number supported or the number of currently installed units for the given UnitType, for a given ClassType on a given ManagedElement.01234..32768..65535SuccessNot SupportedUnknownTimeoutFailedDMTF ReservedVendor Specifictrue23SupportedInstalledThe type of inquiry to be performed.trueFalse : Only report on elements directly contained in/attached to the given ManagedElement. True : Report on all objects contained in/attached to the given ManagedElement.trueThe target of query, for example a rack or a chassis.trueThe ClassType for the query. This should be a entry returned in the GetClassTypes.ClassTypes property.trueThe UnitType for the query.2345678910..32768..65535NoneFront SideBack SideContainedConnectedI/OMemoryStorageMediaLocationMegabytesDMTF ReservedVendor SpecificCIM_ConfigurationReportingService.GetUnitTypes(UnitTypes)truefalseThe maximum number of supported or the number of currently installed units. 2.6.0A StorageLibrary is a collection of ManagedSystemElements that operate together to provide cartridge library capabilities. This object serves as an aggregation point to group the following elements: MediaTransferDevices, a LabelReader, a library Door, MediaAccessDevices, and other Library components.Capabilities of the StorageLibrary. For example, it can be indicated that the Library can perform automatic cleaning of the MediaAccessDevices contained in it (value=1) or that the Library provides physical door access for an operator (value=2).01234UnknownOtherAutomatic CleaningManual OperationFront Panel LockableBoolean set to TRUE if there are more PhysicalMedia in a Library than there are StorageMediaLocations to contain them. For instance, if all MediaAccessDevices have a Media loaded in them, and all StorageMediaLocations are loaded by an operator, then an Overfilled condition exists.Boolean set to TRUE if the Library can not currently report the correct state of each PhysicalMedia within its proper StorageMediaLocation.Boolean set to TRUE if an audit of the location of some or all of the Library's PhysicalMedia is currently being performed. That an individual Changer is currently doing an audit is indicated by a similar AuditInProgress boolean property on the Changer object.Maximum time in seconds that it takes for the StorageLibrary to perform a complete audit of each StorageMediaLocation, to determine the absence or presence of a PhysicalMedia. If automated support is not provided, then this property's value is undefined.SecondsBoolean set to TRUE if the Library includes a robotics mechanism that can be controlled by a ComputerSystem, to automatically load and unload PhysicalMedia to/from MediaAccessDevices and StorageMediaLocations. The property is set to FALSE if the Library represents a repository of Media that are inaccessible to a MediaAccessDevice without human intervention. An example of a non-automated Library is a 'shelf' or 'vault' where PhysicalMedia are kept for extended periods of time.Boolean indicating whether the Library's robotics are currently active/enabled. If TRUE, then the Library may not be safe for a human to enter.Requests that the Library robotics be enabled for automated operation (input parameter, Enabled, set to TRUE), or disabled for manual operation (input parameter set to FALSE). 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.true 2.7.0Similar to the way that LogicalDevices are 'Realized' by PhysicalElements, a StorageLibrary can be realized in one or more PhysicalPackages. The LibraryPackage association explicitly defines this relationship.trueThe PhysicalPackage(s) that realize a StorageLibrary.AntecedenttrueThe StorageLibrary.Dependenttrue 2.6.0A MediaTransferDevice represents hardware that moves PhysicalMedia. It is a superclass for Devices like PickerElement, ChangerDevice and InterLibraryPort. 2.6.0Within an automated StorageLibrary, Media should be accessible to the various robotics and MediaTransferDevices (Pickers, Changers, InterLibraryPorts, etc.). The Library may be serviced by different TransferDevices, each responsible for a subset of the Library's StorageMediaLocations. The DeviceServicesLocation association indicates that the TransferDevice handles Media stored in the referenced Location. For example, LibraryPort 'A' may only service Media from Slots 1-10, while LibraryPort 'B' covers Slots 11-33. This detail is conveyed by this association.trueAntecedentThe MediaTransferDevice that handles Media from the StorageMediaLocation.trueDependentThe MediaLocation that is serviced.trueBoolean indicating that the referenced StorageMediaLocation is not currently accessible to the MediaTransferDevice. For example, the Location could be the realization of an InterLibraryPort that is currently servicing another Library. The DeviceServicesLocation association describes that the TransferDevice COULD service the MediaLocation. This boolean indicates that that this is temporarily not possible. 2.6.0PickerElements represent hardware used to pick or place PhysicalMedia from/into StorageMediaLocations.The maximum time in seconds for a PickerElement to grab a PhysicalMedia from a StorageMediaLocation, once the Picker has arrived at that Location. The maximum time interval for moving a Media from one point to another is the sum of the PickerElement's MaxPickTime, the ChangerDevice's MaxTransitTime and the PickerElement's MaxPutTime.SecondsThe maximum time in seconds for a PickerElement to place a PhysicalMedia into a StorageMediaLocation, once the Picker has arrived at that Location. The maximum time interval for moving a Media from one point to another is the sum of the PickerElement's MaxPickTime, the ChangerDevice's MaxTransitTime and the PickerElement's MaxPutTime.SecondsString describing the location in the StorageLibrary where the Picker is currently positioned. 2.6.0ChangerDevices represent hardware that moves PhysicalMedia within a System, such as a StorageLibrary.The maximum time in seconds between a PickerElement pick and place. It should be reported as the transit time between the two most physically distant StorageMediaLocations in a System. The maximum time interval for moving a Media from one point to another is the sum of the PickerElement's MaxPickTime, the ChangerDevice's MaxTransitTime and the PickerElement's MaxPutTime.SecondsBoolean set to TRUE if the Changer supports media flipping. Media needs to be flipped when multi-sided PhysicalMedia are placed into a MediaAccessDevice that does NOT support dual sided access.Boolean set to TRUE if an audit is currently being performed by the Changer.trueA count of the number of audits performed by the Changer. 2.6.0PickerForChanger indicates the PickerElement(s) that access StorageMediaLocations and deliver PhysicalMedia to the Changer, for movement through the System. A Changer may have several Pickers for faster exchange of Media.trueAntecedentThe PickerElement that accesses StorageMediaLocations to deliver Media to the Changer.trueDependent1The ChangerDevice.true 2.6.0LimitedAccessPorts represent hardware that transports PhysicalMedia into or out of a System, such as a StorageLibrary. They are identified as 'limited' since these Ports do not provide access to ALL the PhysicalMedia or StorageMediaLocations in a Library, but only to a subset.Boolean indicating that the Port is 'locked' (TRUE) or 'unlocked' (FALSE). When the Port is locked, access its Media Locations is prevented without the use of a physical key, front panel activity or the issuance of a software unlock command.When a Port is 'Extended' or 'open' (value=TRUE), its StorageMediaLocations are accessible to a human operator. If not extended (value=FALSE), the Locations are accessible to a PickerElement.When a LimitedAccessPort is 'Extended', all related media-transfer componentry may be stopped. The ExtendTimeout property provides a mechanism to event on a Port left open for a period of time (in seconds) exceeding the property's value.SecondsDate and time that the Port was last extended.trueThe number of times that the LimitedAccessPort was used to move a PhysicalMedia into the System/StorageLibrary.trueThe number of times that the LimitedAccessPort was used to move a PhysicalMedia out of the System/StorageLibrary.An enumeration expressing whether the Port is used for import into the Library/System which scopes and names it (value=1), export from the Library/System (value=2), or both (value=3).0123UnknownImportExportBoth Import and Export 2.6.0InterLibraryPorts represent hardware that transports PhysicalMedia between connected StorageLibraries. The LibraryExchange association identifies the connected Libraries, by identifying the connected InterLibraryPorts.Date and time that the Port was last accessed by its System/StorageLibrary. This value may be different than that specified for the Port(s) to which this InterLibraryPort is connected. Connected Ports are identified using the LibraryExchange association.trueThe number of times that the InterLibraryPort was used to move a PhysicalMedia into the System/StorageLibrary.trueThe number of times that the InterLibraryPort was used to move a PhysicalMedia out of the System/StorageLibrary.An enumeration expressing whether the Port is used for import into the Library/System which scopes and names it (value=1), export from the Library/System (value=2), or both (value=3).0123UnknownImportExportBoth Import and Export 2.6.0LibraryExchange indicates that two StorageLibraries are connected through their InterLibraryPorts.trueAntecedentThe InterLibraryPort of one StorageLibrary.trueDependentThe InterLibraryPort of the connected Library.trueEnumeration indicating whether the Antecedent (value=1), Dependent (value=2), or neither Library (value=3) currently has access to the Port.0123UnknownAntecedentDependentNeither 2.6.0LabelReaders represent hardware capable of scanning or reading a physical label or the NonVolatileMemory on a PhysicalMedia. Examples of labels include barcode and OCR tags.An array of enumerated integers describing the formats of the labels that can be read or scanned by the LabelReader. The values specified for this property correspond to those defined for CIM_PhysicalMedia.LabelFormats.012345BarcodeRadio Frequency IdentificationOCR (Optical Character Recognition)MICR (Magnetic Ink Character Recognition)7 Character Barcode9 Character BarcodeCIM_PhysicalMedia.LabelFormatsThe technology used by the LabelReader. One entry of the Values array requires some explanation - "Memory Reader". The latter describes the ability to access memory in a PhysicalMedia's packaging (for example, memory on an AIT tape). The existence of this Memory is indicated by the MemoryWithMedia association on the physical side, or by AssociatedMemory on the logical side.0123456UnknownOtherLaserInfraredRFCameraMemory Reader 2.6.0A LogicalDevice may use or require one or more LabelReaders, to scan barcodes or otherwise identify entities. This relationship is described by the AssociatedLabelReader dependency.trueAntecedentThe LabelReader.trueDependentThe Device that is dependent on the Reader Device.true 2.6.0PickerLabelReader is used to indicate that one or more LabelReaders works in conjunction with PickerElements, to identify PhysicalMedia as they are being picked/placed.trueThe LabelReader.AntecedenttrueThe PickerElement that is dependent on the Reader Device.Dependenttrue 2.6.0AccessLabelReader is used to indicate that one or more LabelReaders works in conjunction with MediaAccessDevices, to identify PhysicalMedia before read/write.trueThe LabelReader.AntecedenttrueThe MediaAccessDevice that is dependent on the Reader Device.Dependenttrue 2.6.0Statistics for a LabelReader, related to read successes, failures and retries.trueThe number of successful physical label scans.trueThe number of failed physical label scans.trueThe number of retried physical label scans.Method 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 resets the "Scan Successes" counter, 2 resets the "Scan Failures" counter, and 3 resets the "Scan Retries" counter. 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 Device's instrumentation can also reset its internal processing and counters. In a subclass, 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' can be specified as a Values array qualifier.true0123AllScan SuccessesScan FailuresScan Retries 2.6.0Statistics for a PickerElement, related to pick/put successes, retries and failures.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.Method 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 'pick'-related counters, and 4-6 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 Device's instrumentation can also reset its internal pocessing and counters. In a subclass, 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' can be specified as a Values array qualifier.true0123456AllPick SuccessesPick FailuresPick RetriesPut SuccessesPut FailuresPut Retries 2.7.0Statistics for a LabelReader, related to read successes, failures and retries. The element whose statistics are described is associated using the relationship, ElementStatisticalData.trueThe number of successful physical label scans.trueThe number of failed physical label scans.trueThe number of retried physical label scans. 2.7.0Statistics for a PickerElement, related to pick/put successes, retries and failures. The element whose statistics are described is associated using the relationship, ElementStatisticalData.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. true2.6.0UserDevices are LogicalDevices that allow a ComputerSystem's users to input, view or hear data. It is a superclass from which other classes, such as Keyboard or DesktopMonitor, descend.An indication of whether the Device is locked, preventing user input or output. 2.7.0PointingDevice represents those Devices used to 'point' to regions of a Display.The type of the pointing device.123456789OtherUnknownMouseTrack BallTrack PointGlide PointTouch PadTouch ScreenMouse - Optical SensorMIF.DMTF|Pointing Device|003.1Number of buttons. If the PointingDevice has no buttons, enter 0.MIF.DMTF|Pointing Device|003.4Integer indicating whether the PointingDevice is configured for right (value=2) or left handed operation (value=3). Also, the values, "Unknown" (0) and "Not Applicable" (1), can be defined.0123UnknownNot ApplicableRight Handed OperationLeft Handed OperationTracking resolution of the PointingDevice in Counts per Inch.Counts per Inch 2.7.0Capabilities and management of the Keyboard LogicalDevice.Number of function keys on the Keyboard.A free-form string indicating the format and layout of the Keyboard.MIF.DMTF|Keyboard|004.1An integer indicating whether a hardware-level password is enabled at the keyboard (value=4), preventing local input. Other values are: "Disabled" (3), "Not Implemented" (5), "Other" (1) and "Unknown" (2).12345OtherUnknownDisabledEnabledNot ImplementedMIF.DMTF|System Hardware Security|001.2 true2.6.0Display is a superclass for grouping the miscellaneous display devices that exist. 2.6.0Capabilities and management of the DesktopMonitor (CRT) LogicalDevice.The type of DesktopMonitor or CRT. For example, multiscan color or monochrome monitors (values 2 or 3, respectively) can be indicated in this property.012345UnknownOtherMultiscan ColorMultiscan MonochromeFixed Frequency ColorFixed Frequency MonochromeMonitor's bandwidth in MHertz. If unknown, enter 0.MegaHertzThe logical height of the Display in screen coordinates.The logical width of the Display in screen coordinates. 2.6.0Capabilities and management of the FlatPanel LogicalDevice.FlatPanel's horizontal resolution in Pixels.PixelsFlatPanel's vertical resolution in Pixels.PixelsA FlatPanel's scan mode indicating either single (value=2) or dual scan (3).0123UnknownOtherSingle ScanDual ScanAn integer enumeration describing the type of flat panel display.012345678UnknownOtherPassive Matrix LCDActive Matrix LCDCholesteric LCDField Emission DisplayElectro Luminescent DisplayGas PlasmaLEDA description of the display illumination type. For example, backlit (value=2) or reflective (4) can be specified.01234UnknownOtherBacklitEdgelitReflectiveBoolean indicating whether the FlatPanel supports color display. 2.6.0Capabilities and management of the Scanner LogicalDevice. 2.6.0A Door is the abstraction of hardware providing access to the internal componentry of a System. When a Door is 'opened', typically all accessible, moving components are stopped or suspended to prevent physical harm.Boolean indicating the 'open' (TRUE) or 'closed' (FALSE) status of the Door.Boolean indicating that the Door is 'locked' (TRUE) or 'unlocked' (FALSE). When the Door is locked, access to the componentry is prevented, without the use of a physical key or the issuance of a software unlock command.When a Door is 'Open', all accessible, moving componentry and Device operation are typically stopped. The Timeout property provides a mechanism to event on a Door left open for a period of time (in seconds) exceeding the property's value.SecondsDate and time that the Door was last opened.The Capabilities of the Door. For example, information on whether the Door is "Host System Lockable" (value=2) and/or whether a key is available (value=3) are specified in this property. The value 4, "All Drives Dismounted Before Access", pertains to a Door on a StorageLibrary or set of drive bays. If specified for the Door, it means that it can not be opened unless all Media are first unloaded from the accessible MediaAccessDevices.01234UnknownOtherHost System LockablePhysical KeyAll Drives Dismounted Before Access 2.6.0Doors provide access to PhysicalElements for hot swap, repair and similar activities. The entities accessed through a Door are indicated in this relationship.trueAntecedentThe Door that provides access.trueDependentThe PhysicalElement that is accessed.true 2.6.0Doors provide access to PhysicalElements for hot swap, repair and similar activities. In turn, PhysicalElements 'Realize' LogicalDevices. Since it may not be possible to define all the PhysicalElements that exist, and optimizing the retrieval of Devices 'behind' the Door may be desirable, the DoorAccessToDevice association provides a shortcut mechanism for defining the LogicalDevices ('hardware') accessed through a Door.trueAntecedentThe Door that provides access.trueDependentThe LogicalDevice that is accessed.true 2.6.0MonitorResolution describes the relationship between horizontal and vertical resolutions, refresh rate and scan mode for a DesktopMonitor. The actual resolutions, etc. that are in use, are the values specified in the VideoController object.SettingIDtrue256The inherited SettingID serves as part of the key for a MonitorResolution instance.Monitor's horizontal resolution in Pixels.PixelsCIM_VideoController.CurrentHorizontalResolutionMIF.DMTF|Monitor Resolutions|002.2Monitor's vertical resolution in Pixels.PixelsCIM_VideoController.CurrentVerticalResolutionMIF.DMTF|Monitor Resolutions|002.3Monitor's refresh rate in Hertz. If a range of rates is supported, use the MinRefreshRate and MaxRefreshRate properties, and set RefreshRate (this property) to 0.HertzCIM_VideoController.CurrentRefreshRateMIF.DMTF|Monitor Resolutions|002.4Monitor's minimum refresh rate in Hertz, when a range of rates is supported at the specified resolutions.HertzCIM_VideoController.MinRefreshRateMIF.DMTF|Monitor Resolutions|002.6Monitor's maximum refresh rate in Hertz, when a range of rates is supported at the specified resolutions.HertzCIM_VideoController.MaxRefreshRateMIF.DMTF|Monitor Resolutions|002.7Integer indicating whether the monitor operates in interlaced (value=5) or non-interlaced (4) mode.12345OtherUnknownNot SupportedNon-Interlaced OperationInterlaced OperationCIM_VideoController.CurrentScanModeMIF.DMTF|Monitor Resolutions|002.5 2.6.0MonitorSetting associates the MonitorResolution Setting object with the DesktopMonitor to which it applies.trueElementThe DesktopMonitor.trueSettingThe MonitorResolution associated with the DesktopMonitor.true 2.7.0Capabilities and management of Memory-related LogicalDevices.ErrorMethodologyErrorMethodology for Memory is a string property that indicates whether parity or CRC algorithms, ECC or other mechanisms are used. Details on the algorithm can also be supplied.MIF.DMTF|Physical Memory Array|001.7The beginning address, referenced by an application or operating system and mapped by a memory controller, for this Memory object. The starting address is specified in KBytes.KiloBytesMIF.DMTF|Memory Array Mapped Addresses|001.3MIF.DMTF|Memory Device Mapped Addresses|001.4The ending address, referenced by an application or operating system and mapped by a memory controller, for this Memory object. The ending address is specified in KBytes.KiloBytesMIF.DMTF|Memory Array Mapped Addresses|001.4MIF.DMTF|Memory Device Mapped Addresses|001.5An integer enumeration describing the type of error that occurred most recently. For example, single (value=6) or double bit errors (7) can be specified using this property. The values, 12-14, are undefined in the CIM Schema since in DMI, they mix the semantics of the type of error and whether it was correctable or not. The latter is indicated in the property, CorrectableError.1234567891011121314OtherUnknownOKBad ReadParity ErrorSingle-Bit ErrorDouble-Bit ErrorMulti-Bit ErrorNibble ErrorChecksum ErrorCRC ErrorUndefinedUndefinedUndefinedMIF.DMTF|Memory Device|005.12MIF.DMTF|Physical Memory Array|001.8CIM_Memory.OtherErrorDescriptionFree form string providing more information if the ErrorType property is set to 1, "Other". If not set to 1, this string has no meaning.CIM_Memory.ErrorInfoBoolean indicating that the most recent error was correctable. If the ErrorInfo property is equal to 3, "OK", then this property has no meaning.MIF.DMTF|Physical Memory Array|001.8The time that the last memory error occurred. The type of error is described by the ErrorInfo property. If the ErrorInfo property is equal to 3, "OK", then this property has no meaning.An integer enumeration indicating the memory access operation that caused the last error. The type of error is described by the ErrorInfo property. If the ErrorInfo property is equal to 3, "OK", then this property has no meaning.12345OtherUnknownReadWritePartial WriteMIF.DMTF|Physical Memory Array|001.10The size of the data transfer in bits that caused the last error. 0 indicates no error. If the ErrorInfo property is equal to 3, "OK", then this property should be set to 0.BitsMIF.DMTF|Physical Memory Array|001.11trueData captured during the last erroneous mebmory access. The data occupies the first n octets of the array necessary to hold the number of bits specified by the ErrorTransferSize property. If ErrorTransferSize is 0, then this property has no meaning.IndexedMIF.DMTF|Physical Memory Array|001.12The ordering for data stored in the ErrorData property. "Least Significant Byte First" (value=1) or "Most Significant Byte First" (2) can be specified. If ErrorTransferSize is 0, then this property has no meaning.012UnknownLeast Significant Byte FirstMost Significant Byte FirstSpecifies the address of the last memory error. The type of error is described by the ErrorInfo property. If the ErrorInfo property is equal to 3, "OK", then this property has no meaning.MIF.DMTF|Memory Device|005.19MIF.DMTF|Physical Memory Array|001.14Boolean indicating whether the address information in the property, ErrorAddress, is a system-level address (TRUE) or a physical address (FALSE). If the ErrorInfo property is equal to 3, "OK", then this property has no meaning.Specifies the range, in bytes, to which the last error can be resolved. For example, if error addresses are resolved to bit 11 (ie, on a typical page basis), then errors can be resolved to 4K boundaries and this property is set to 4000. If the ErrorInfo property is equal to 3, "OK", then this property has no meaning.BytesMIF.DMTF|Memory Device|005.21MIF.DMTF|Physical Memory Array|001.15trueAn array of octets holding additional error information. An example is ECC Syndrome or the return of the check bits if a CRC-based ErrorMethodology is used. In the latter case, if a single bit error is recognized and the CRC algorithm is known, it is possible to determine the exact bit that failed. This type of data (ECC Syndrome, Check Bit or Parity Bit data, or other vendor supplied information) is included in this field. If the ErrorInfo property is equal to 3, "OK", then AdditionalErrorData has no meaning.MIF.DMTF|Memory Device|005.18MIF.DMTF|Physical Memory Array|001.13 2.6.0LogicalDevices may have Memory installed on them or otherwise associated with them - such as CacheMemory. This is made explicit in this association.trueAntecedentMemory installed on or associated with a Device.trueDependentThe LogicalDevice.true 2.7.0Association indicating that memory is installed and required for the UnitaryComputerSystem to operate. At least one Memory StorageExtent is required. Note that this relationship inherits from the SystemDevice association, and therefore, the Memory StorageExtent is weak to the aggregating UnitaryComputerSystem.truetruetrueThe UnitaryComputerSystem.11GroupComponenttruetrueThe Memory StorageExtent which is part of the UnitaryComputerSystem.truePartComponenttrue 2.6.0Associates the Processor and system Memory, or a Processor's Cache. trueThe Processor that accesses the Memory or uses the Cache.DependenttrueSpeed of the bus, in MHertz, between the Processor and Memory. MegaHertz 2.7.0Capabilities and management of NV Storage. Non-volatile memory natively includes flash and ROM storage. In addition, NV memory can be BasedOn VolatileStorage, if the volatile memory is backed by a Battery. This scenario would be completely described by an instance of the AssociatedBattery relationship, referencing the NonVolatileStorage as the Dependent and the Battery as the Antecedent, and an instance of the BasedOn relationship, referencing the NonVolatileStorage as the Dependent and the VolatileStorage as the Antecedent.Indicating that the NV storage is writeable.Boolean indicating that at least some portion of the NonVolatileStorage is writeable by applications.When at least some portion of the NonVolatileStorage is writeable (ApplicationWriteable property = TRUE), StartAddressforApplcationWrite indicates the starting address for application data. If the ApplicationWriteable property is FALSE, this property is undefined.CIM_NonVolatileStorage.ApplicationWriteableWhen at least some portion of the NonVolatileStorage is writeable (ApplicationWriteable property = TRUE), ApplicationWritableSize indicates the number of bits available for application data. If the ApplicationWriteable property is FALSE, this property is undefined.BitsCIM_NonVolatileStorage.ApplicationWriteable 2.6.0A link between BIOSElement and NonVolatileStorage where the BIOS is loaded.trueAntecedentThe non-volatile storage.trueDependentThe BIOS stored in the NonVolatile Extent.trueThe starting address where the BIOS is located in non-volatile storage.The ending address where the BIOS is located in non-volatile storage. 2.6.0Capabilities and management of Volatile Storage.Indicates whether this Memory can be cached or not.MIF.DMTF|System Resource Memory Info|002.5An enumeration indicating the cache type that is compatible with this Memory. For example, 4 indicates write-through cache. If the Cacheable property is set to false, then this property does not have meaning and should be set to 5, "Not Applicable".12345OtherUnknownWrite-BackWrite-ThroughNot ApplicableMIF.DMTF|System Resource Memory Info|002.6 2.7.0Capabilities and management of Cache Memory. Cache memory is dedicated or allocated RAM that a Processor searches first for data, before going to 'regular' memory. CacheMemory is used to speed up the delivery of data to a Processor. It is usually described by its closeness to the Processor (for example, Primary or Secondary Cache). If a DiskDrive includes RAM allocated for holding the disk's most recently read and/or adjacent data (in order to speed up retrieval), this also would be modeled as CacheMemory. Note that CacheMemory is NOT operating system or application level buffers but actual RAM allocated for caching data for a Processor, from a hard disk, etc.Defines whether this is the Primary (value=3), Secondary (value=4) or Tertiary (value=5) Cache. Also, "Other" (1), "Unknown" (2) and "Not Applicable" (6) can be defined.123456OtherUnknownPrimarySecondaryTertiaryNot ApplicableMIF.DMTF|System Cache|006.2Defines whether this is write-back (value=3) or write-through (value=4) Cache, or whether this information "Varies with Address" (5) or is defined individually for each I/O (6). Also, "Other" (1) and "Unknown" (2) can be specified.123456OtherUnknownWrite BackWrite ThroughVaries with AddressDetermination Per I/OMIF.DMTF|System Cache|006.5Defines whether this is for instruction caching (value=3), data caching (value=4) or both (value=5, "Unified"). Also, "Other" (1) and "Unknown" (2) can be defined.12345OtherUnknownInstructionDataUnifiedMIF.DMTF|System Cache|006.9Size, in bytes, of a single cache bucket or line.BytesMIF.DMTF|System Cache|006.10An integer enumeration describing the algorithm to determine which cache lines or buckets should be re-used.12345678OtherUnknownLeast Recently Used (LRU)First In First Out (FIFO)Last In First Out (LIFO)Least Frequently Used (LFU)Most Frequently Used (MFU)Data Dependent Multiple AlgorithmsMIF.DMTF|System Cache|006.12Policy that shall be employed by the Cache for handling read requests. For example, "Read", "Read-Ahead" or both can be specified using the values, 3, 4 or 5, respectively. If the read policy is determined individually (ie, for each request), then the value 6 ("Determination per I/O") should be specified. "Other" (1) and "Unknown" (2) are also valid values.123456OtherUnknownReadRead-AheadRead and Read-AheadDetermination Per I/OMIF.DMTF|System Cache|006.13Maximum amount of time, in seconds, dirty lines or buckets may remain in the Cache before they are flushed. A value of zero indicated that a cache flush is not controlled by a flushing timer.SecondsMIF.DMTF|System Cache|006.14An integer enumeration defining the system cache associativity. For example, 6 indicates a fully associative cache.12345678OtherUnknownDirect Mapped2-way Set-Associative4-way Set-AssociativeFully Associative8-way Set-Associative16-way Set-AssociativeMIF.DMTF|System Cache|006.15 true2.6.0CIM_Modem is the superclass for grouping the numerous types of Modems. true2.6.0CIM_ConnectionBasedModem is the superclass for grouping the numerous types of connection-based Modems. A CableModem is a type of connection-based Modem.VendorID information is reported via Modem-specific requests. For example, for ADSLModem Devices the VendorID is assigned by T1E1.4 according to T1.413, Appendix D. The correct place in the CIM Schema for this information is in PhysicalElement (the Manufacturer property) for hardware and Product (the Vendor property) if the information is related to Product acquisition. This data is also reported here since it is part of the standard output from the Device, and as an optimization. 2.6.0The DSLModem class represents the superclass for Digital Subscriber Line (DSL) Devices. Properties will be defined in a future release of the model. 2.6.0The ADSLModem class represents Modems of the DSL type = ADSL, Asymmetric Digital Subscriber Line.Noise Margin of this Modem with respect to its received signal, in tenths of dB.Tenths of DecibelstrueMeasured difference in the total power transmitted by the peer Modem and the total power received by this Modem. This is measured in tenths of dB.Tenths of DecibelsStatus indicates the current state of the connection (line). The property holds a bitmap describing the possible conditions. For example, 1) No Defect - There no defects on the line; 2) Loss Of Framing - ATUR failure due to not receiving valid frame; 4) Loss Of Signal - ATUR failure due to not receiving signal; 8) Loss Of Power - ATUR failure due to loss of power; 32) Loss Of Signal Quality - Loss of Signal Quality is declared when the NoiseMargin falls below the minimum NoiseMargin, or the bit-error-rate exceeds 10^-7.124832No DefectLoss Of FramingLoss Of SignalLoss Of PowerLoss Of Signal QualitytrueMeasured total output power (in tenths of dB) transmitted by this Modem.Tenths of DecibelsIndicates the maximum currently attainable data rate for the Modem. This value will be equal or greater than the current line rate.Bits per Second 2.6.0The CableModem class represents a device for transmission across a cable infrastructure. 2.6.0The HDSLModem class represents Modems of the DSL type = HDSL, High data rate Digital Subscribe Line, capable of delivering T1 or E1 speeds. Properties will be defined in a future release of the model. 2.6.0The SDSLModem class represents Modems of the DSL type = SDSL, Symmetric Digital Subscriber Line. Properties will be defined in a future release of the model. 2.6.0The VDSLmodem class represents Modems of the DSL type = VDSL, Very high data rate Digital Subscriber Line. Properties will be defined in a future release of the model. true2.6.0CIM_CallBasedModem is the superclass for grouping the numerous types of call-based modems. The POTSModem is a type of call-based Modem.Indicates whether online fallback is enabled, to be negotiated by the Modem.An array enumerating all the compression protocols supported by the Modem.0123456789UnknownOtherNo CompressionMNP 5V.42bisMNP 3MNP 4V.58PEPHSTCIM_CallBasedModem.OtherCompressionDescriptionDescription of the compression type when "Other " (value=1) is defined in the CompressionSupported array. If there are multiple "Other" types, then combine their descriptions into a single string.CIM_CallBasedModem.CompressionSupportedDescribes the current data compression characteristics of the Modem. 0123456789UnknownOtherNo CompressionMNP 5V.42bisMNP 3MNP 4V.58PEPHSTCIM_CallBasedModem.CompressionSupportedCIM_CallBasedModem.OtherCompressionInfoDescriptionDescription of the current compression type when "Other" (value=1) is specified in the CompressionInfo property.CIM_CallBasedModem.CompressionInfoAn array enumerating all the modulation protocols supported by the Modem. The beginning entries in the Values qualifier array are mapped from the CIM_POTSModem ModulationScheme property.01234567891011121314151617181920212223242526272829UnknownOtherNot SupportedBell 103Bell 212AV.22bisV.32V.32bisV.terboV.FCV.34V.34bisV.17 (G3 Fax Call)V.21V.22V.23 Constant Carrier (1200/75)V.23 Switched Carrier (Half Duplex)V.26bisV.26terV.27ter (G3 Fax Call)V.29 HD (G3 Fax Call)V.34 HD (G3 Fax Call)V.90 Issue 1 (Asymmetric)V.90 Issue 2 (Symmetric)V.58X2K56FLEXV.FastPEPHSTCIM_CallBasedModem.OtherModulationDescriptionDescription of the current modulation type when "Other" (value=1) is specified in the ModulationSupported property. If there are multiple "Other" types, then combine their descriptions into a single string.CIM_CallBasedModem.ModulationSupportedDescribes the current modulation scheme of the Modem.01234567891011121314151617181920212223242526272829UnknownOtherNot SupportedBell 103Bell 212AV.22bisV.32V.32bisV.terboV.FCV.34V.34bisV.17 (G3 Fax Call)V.21V.22V.23 Constant Carrier (1200/75)V.23 Switched Carrier (Half Duplex)V.26bisV.26terV.27ter (G3 Fax Call)V.29 HD (G3 Fax Call)V.34 HD (G3 Fax Call)V.90 Issue 1 (Asymmetric)V.90 Issue 2 (Symmetric)V.58X2K56FLEXV.FastPEPHSTCIM_CallBasedModem.ModulationSupportedCIM_CallBasedModem.OtherSchemeDescriptionDescription of the current modulation type when "Other" (value=1) is specified in the ModulationScheme property.CIM_CallBasedModem.ModulationSchemeAn array enumerating the error control protocols supported by the Modem. The beginning entries in the Values qualifier array are mapped from the CIM_POTSModem ErrorControlInfo property.012345678910111213UnknownOtherNo Error CorrectionMNP 4LAPMV.58ECP Enhanced Cellular ProtocolETC Enhanced Throughput CellularMNP 1MNP 2MNP 3MNP10PEPHSTCIM_CallBasedModem.OtherErrorControlDescriptionDescription of the error control type when "Other" (value=1) is specified in the ErrorControlSupported property. If there are multiple "Other" types, then combine their descriptions into a single string.CIM_CallBasedModem.ErrorControlSupportedDescribes the current error correction characteristics of the Modem.012345678910111213UnknownOtherNo Error CorrectionMNP 4LAPMV.58ECP Enhanced Cellular ProtocolETC Enhanced Throughput CellularMNP 1MNP 2MNP 3MNP10PEPHSTCIM_CallBasedModem.ErrorControlSupportedCIM_CallBasedModem.OtherErrorControlInfoDescriptionDescription of the error control when "Other" (value=1) is defined as the value of the ErrorControlInfo property.CIM_CallBasedModem.ErrorControlInfoTime of last reset of the Modem.The rate at which the receiver and transmitter are or were last cooperating, on a call, before disconnection.Bits per SecondStatus of the Modem. For example, information regarding modem negotiation or whether the modem is connected (values 8 and 9, respectively) can be conveyed in this property.012345678910UnknownOtherOfflineOn HookDialingWaiting for AnswerRingingModem DetectedNegotiatingOnlineErrorTotal number of characters sent by the Device on the last or current call. That a call is in-progress is indicated by the CallStatus property.trueTotal number of characters received by the Device on the last or current call. That a call is in-progress is indicated by the CallStatus property.trueTotal number of characters lost by the Device on the last or current call. That a call is in-progress is indicated by the CallStatus property.trueTotal number of blocks sent by the Device on the last or current call. That a call is in-progress is indicated by the CallStatus property.trueTotal number of blocks resent by the Device on the last or current call. That a call is in-progress is indicated by the CallStatus property.trueTotal number of blocks received by the Device on the last or current call. That a call is in-progress is indicated by the CallStatus property.trueTotal number of block errors seen by the Device on the last or current call. That a call is in-progress is indicated by the CallStatus property.trueLength of the last or current call. That a call is in-progress is indicated by the CallStatus property. The 'interval' format of the datetime data type should be used for the property value.Last or current number dialed to which the statistics apply, or NULL if the call was incoming. 2.6.0The ISDNModem class, a kind of call-based Modem. Properties will be defined in a future release of the model. 2.6.0The POTSModem class represents a Device that translates binary data into wave modulations for sound based transmission. It connects to the POTS (Plain Old Telephone System) network.Capabilities of the POTSModem. For example, the Device may support distinctive ring, caller ID, fax, voice, etc.Indexed0123456789101112UnknownOtherDistinctive RingCaller IDVoiceFax Class 1Fax Class 2WakeOnRingFax Group 3GSM SupportAMPS SupportOOB AlertingWorldwide Country SupportCIM_POTSModem.CapabilityDescriptionsAn array of free-form strings providing more detailed explanations for any of the POTSModem features indicated in the Capabilities array. Note, each entry of this array is related to the entry in the Capabilities array that is located at the same index.IndexedCIM_POTSModem.CapabilitiesSpecifies which capabilities are enabled from the list of ones supported, defined in the Capabilities array.0123456789101112UnknownOtherDistinctive RingCaller IDVoiceFax Class 1Fax Class 2WakeOnRingFax Group 3GSM SupportAMPS SupportOOB AlertingWorldwide Country SupportCIM_POTSModem.CapabilitiesDefines the maximum settable communication speed to the COM Port for an external modem. Enter 0 if not applicable.Bits per SecondDefines the maximum settable communication speed for accessing the phone system.Bits per SecondBoolean indicating that synchronous, as well as asynchronous, communication is supported.DialType is an integer indicating whether tone (value=1) or pulse dialing (value=2) is used. "Unknown" (0) can also be defined.012UnknownTonePulseInactivityTimeout defines the time limit (in seconds) for automatic disconnection of the phone line, if no data is exchanged. A value of 0 indicates that this feature is present but not enabled.SecondsDescribes the volume level of the audible tones from the Modem. For example, high, medium or low volume can be reported (values 3, 4 or 5, respectively).01234567UnknownOtherNot SupportedHighMediumLowOffAuto64CountriesSupported is an array of strings defining the countries in which the POTSModem operates.64CountrySelected is a string value defining the country for which the Modem is currently programmed. When multiple countries are supported, this property defines which one is currently selected for use.Number of rings before the Modem answers an incoming call.MaxNumberOfPasswords specifies the number of passwords definable in the Modem itself. If this feature is not supported, enter 0.24CurrentPasswords is an array containing the currently defined passwords for the Modem. This array may be left blank for security reasons.Indication of whether the Modem supports call-back.AnswerMode defines the current auto-answer/call-back setting for the Modem.012345UnknownOtherDisabledManual AnswerAuto AnswerAuto Answer with Call-BackThe current equalization setting for the Modem.0123UnknownOtherLongShortList of black-listed numbers for the Modem. 2.6.0Unimodem is a POTSModem that supports the Unimodem 1.0 Specification.Current call setup result code.01234567891011No Previous CallNo Dial Tone DetectedReorder Signal Detected, Network BusyBusy Signal DetectedNo Recognized Signal DetectedVoice DetectedText Telephone DetectedData Answering Signal DetectedData Calling Signal DetectedFax Answering Signal DetectedFax Calling Signal DetectedV.8bis Signal DetectedCurrent multi-media mode of the Unimodem.012345678910Data OnlyFax OnlyVoice OnlyVoice ViewASVD V.61ASVD V.34QDSVD Multi-TechDSVD 1.2DSVD V.70Video Telephony H.324Other V.80 CallCurrent DTE-DCE interface mode of the Unimodem, such as asynchronous, v.80 transparent or framed synchronous modes.012Async DataV.80 Transparent Synchronous ModeV.80 Framed Synchronous ModeThe active transmit modulation scheme.01234567891011121314151617181920212223..65535V.17 (G3 Fax Call)V.21V.22V.22bisV.23 Constant Carrier (1200/75)V.23 Switched Carrier (Half Duplex)V.26bisV.26terV.27ter (G3 Fax Call)V.29 HD (G3 Fax Call)V.32V.32bisV.34V.34 HD (G3 Fax Call)V.90 Issue 1 (Asymmetric)V.90 Issue 2 (Symmetric)Reserved (V.58)X2K56FLEXV.FCV.32terboBell 212ABell 103Reserved for MfgsThe active receive modulation scheme.01234567891011121314151617181920212223..65535V.17 (G3 Fax Call)V.21V.22V.22bisV.23 Constant Carrier (1200/75)V.23 Switched Carrier (Half Duplex)V.26bisV.26terV.27ter (G3 Fax Call)V.29 HD (G3 Fax Call)V.32V.32bisV.34V.34 HD (G3 Fax Call)V.90 Issue 1 (Asymmetric)V.90 Issue 2 (Symmetric)Reserved (V.58)X2K56FLEXV.FCV.32terboBell 212ABell 103Reserved for MfgsInitial transmit carrier data rate for the current or last call, in bits per second.Bits per SecondInitial receive carrier data rate for the current or last call, in bits per second.Bits per SecondThe number of carrier retrains requested during the current or last call.trueThe number of carrier retrains granted during the current or last call.trueFinal transmit carrier data rate of the current or last call, in bits per second.Bits per SecondFinal receive carrier data rate of the current or last call, in bits per second.Bits per SecondCause of last call termination.01234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950Cause UnidentifiedNo Previous CallCall Is Still in ProgressCall Waiting Signal DetectedDelayedNMS Initiated Dial CallNMS Initiated Leased Line RestoralNMS Initiated RedialNMS Initiated Dial DisconnectPower LossEquipment FailureFront Panel Disconnect RequestedFront Panel Leased Line RestoralAutomatic Leased Line RestoralInactivity Timer Expiredcct116 Restoral Requestcct108 Is Off Inhibits Dialcct108 Turned OffNo Number ProvidedBlacklisted NumberCall Attempts Limit ExceededExtension Phone Off HookCall Setup Fail Timer ExpiredIncoming Call DetectedLoop Current InterruptedNo Dial ToneVoice DetectedReorder ToneSit ToneEngaged ToneLong Space DisconnectCarrier LostTraining FailedNo Modulation in CommonRetrain FailedRetrain Attempt Count ExceededGSTN Cleardown ReceivedFax DetectedIn Test ModeIntrusive Self Test InitiatedAny Key AbortDTE Hangup CommandDTE Reset CommandFrame RejectNo Error Control EstablishedProtocol Violationn400 ExceededNegotiation FailedDisconnect Frame ReceivedSabme Frame ReceivedLoss Of SynchronizationDiagnostic Command Specification, Unimodem revision number.trueEstimated noise level for the last or current call in -dBm. Values are in the range of 0-100.-dBmNormalized mean squared error for the last or current call.Temporary carrier loss event count for the last or current call.trueCarrier Rate re-negotiation event count for the last or current call.trueError Control frame size in bytes for the last or current call.BytesError control link timeouts in transmission for the last or current call.trueError control link NAKs received for the last or current call.trueThe flow control mechanism used in transmitting data.0123UnknownOffDC1/DC3V.24 ckt 106/133The flow control mechanism used in receiving data.0123UnknownOffDC1/DC3V.24 ckt 106/133Number of transmit chars sent from the DTE for the last or current call. A continuous connection may exceed this value, given enough time. Typically these counters are implemented as 32 bit counters, but additional bits may be provided and are accounted for in this property. If these counters hit maximum value, the DCE manufacturer may roll over to 0.trueNumber of receive chars sent to the DTE for the last or current call. A continuous connection may exceed this value, given enough time. Typically these counters are implemented as 32 bit counters, but additional bits may be provided and are accounted for in this property. If these counters hit maximum value, the DCE manufacturer may roll over to 0.trueNumber of transmit characters lost for the last or current call. A DCE may limit this counter to 16 bits, but additional bits may be provided and are accounted for in this property.trueNumber of receive characters lost for the last or current call. A DCE may limit this counter to 16 bits, but additional bits may be provided and are accounted for in this property.trueNumber of I-Frames transmitted for the last or current call. A continuous connection may exceed this value, given enough time. Typically these counters are implemented as 32 bit counters, but additional bits may be provided and are accounted for in this property. If these counters hit maximum value, the DCE manufacturer may roll over to 0.trueNumber of I-Frames received for the last or current call. A continuous connection may exceed this value, given enough time. Typically these counters are implemented as 32 bit counters, but additional bits may be provided and are accounted for in this property. If these counters hit maximum value, the DCE manufacturer may roll over to 0.trueNumber of I-Frame errors detected for the last or current call, if error control protocol is running. A DCE may limit this counter to 16 bits, but additional bits may be provided and are accounted for in this property.trueNumber of I-Frame errors detected for the last or current call, if error control protocol is running. A DCE may limit this counter to 16 bits, but additional bits may be provided and are accounted for in this property.trueNumber of Call waiting events detected for the last or current call.true 2.6.0OOBAlertServiceOnModem defines where the out of band alerting Service is implemented. The Service can either employ a Modem or NetworkAdapter to send alerts.true1The Modem which implements the alerting Service.AntecedenttrueThe alerting Service provided on the Modem.Dependenttrue 2.6.0WakeUpServiceOnModem defines where the WakeUpService is implemented. The Service can either employ a Modem or NetworkAdapter to receive a wakeup signal.true1The Modem which implements the WakeUpService.AntecedenttrueThe wakeup Service provided on the Modem.Dependenttrue 2.7.1Capabilities and management of the Printer LogicalDevice.Status information for a Printer, beyond that specified in the LogicalDevice Availability property. Values include "Idle" (3) and an indication that the Device is currently printing (4).1234567OtherUnknownIdlePrintingWarmupStopped PrintingOfflineMIB.IETF|Printer-MIB.hrPrinterStatusPrinter error information.01234567891011UnknownOtherNo ErrorLow PaperNo PaperLow TonerNo TonerDoor OpenJammedOfflineService RequestedOutput Bin FullCIM_Printer.ErrorInformationMIB.IETF|Printer-MIB.hrPrinterDetectedErrorStateAn array providing supplemental information for the current error state, indicated in DetectedErrorState.CIM_Printer.DetectedErrorStateAn integer array indicating the types of paper supported.0123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475UnknownOtherABCDELetterLegalNA-10x13-EnvelopeNA-9x12-EnvelopeNA-Number-10-EnvelopeNA-7x9-EnvelopeNA-9x11-EnvelopeNA-10x14-EnvelopeNA-Number-9-EnvelopeNA-6x9-EnvelopeNA-10x15-EnvelopeA0A1A2A3A4A5A6A7A8A9A10B0B1B2B3B4B5B6B7B8B9B10C0C1C2C3C4C5C6C7C8ISO-DesignatedJIS B0JIS B1JIS B2JIS B3JIS B4JIS B5JIS B6JIS B7JIS B8JIS B9JIS B10NA-LetterNA-LegalB4-EnvelopeB5-EnvelopeC3-EnvelopeC4-EnvelopeC5-EnvelopeC6-EnvelopeDesignated-Long-EnvelopeMonarch-EnvelopeExecutiveFolioInvoiceLedgerQuartoAn array of free-form strings specifying the types of paper that are currently available on the Printer. Each string should be expressed in the form specified by ISO/IEC 10175 Document Printing Application (DPA) which is also summarized in Appendix C of RFC 1759 (Printer MIB). Examples of valid strings are "iso-a4-colored" and "na-10x14-envelope". By definition a paper size that is available and listed in PaperTypesAvailable should also appear in the PaperSizesSupported property.IndexedCIM_PrintJob.RequiredPaperTypeCIM_PrintService.PaperTypesAvailableMIB.IETF|Printer-MIB.prtInputMediaNameSpecifies the paper type that the Printer will use if a PrintJob does not specify a particular type. The string should be expressed in the form specified by ISO/IEC 10175 Document Printing Application (DPA) which is also summarized in Appendix C of RFC 1759 (Printer MIB).CIM_Printer.PaperTypesAvailableSpecifies the paper type that the Printer is currently using. The string should be expressed in the form specified by ISO/IEC 10175 Document Printing Application (DPA) which is also summarized in Appendix C of RFC 1759 (Printer MIB).CIM_Printer.PaperTypesAvailableAn array indicating the print languages natively supported.1234567891011121314151617181920212223242526272829303132333435363738394041424344454647485051525354555657585960OtherUnknownPCLHPGLPJLPSPSPrinterIPDSPPDSEscapePEpsonDDIFInterpressISO6429Line DataMODCAREGISSCSSPDLTEK4014PDSIGPCodeVDSCDSEWPSLN03CCITTQUICCPAPDecPPLSimple TextNPAPDOCimPressPinwriterNPDLNEC201PLAutomaticPagesLIPSTIFFDiagnosticCaPSLEXCLLCDSXESMIMETIPSIPrescribeLinePrinterIDPXJCLPDFRPDLIntermecIPLUBIFingerprintUBIDirectProtocolFujitsuPCLXLMIB.IETF|Printer-MIB.prtInterpreterLangFamilyCIM_Printer.MimeTypesSupportedCIM_PrintJob.LanguageCIM_PrintService.LanguagesSupportedAn array of free-form strings providing more detailed explanations of any mime types that are supported by the Printer. If data is provided for this property, then the value 47, "Mime", should be included in the LanguagesSupported property.CIM_Printer.LanguagesSupportedCIM_PrintJob.MimeTypesCIM_PrintService.MimeTypesSupportedIndicates the current printer language being used. A language that is being used by the Printer should also be listed in LanguagesSupported.1234567891011121314151617181920212223242526272829303132333435363738394041424344454647485051525354555657585960OtherUnknownPCLHPGLPJLPSPSPrinterIPDSPPDSEscapePEpsonDDIFInterpressISO6429Line DataMODCAREGISSCSSPDLTEK4014PDSIGPCodeVDSCDSEWPSLN03CCITTQUICCPAPDecPPLSimple TextNPAPDOCimPressPinwriterNPDLNEC201PLAutomaticPagesLIPSTIFFDiagnosticCaPSLEXCLLCDSXESMIMETIPSIPrescribeLinePrinterIDPXJCLPDFRPDLIntermecIPLUBIFingerprintUBIDirectProtocolFujitsuPCLXLCIM_Printer.LanguagesSupportedCIM_Printer.CurrentMimeTypeSpecifies the mime type currently being used by the Printer if the CurrentLanguage is set to indicate a mime type is in use (value = 47).CIM_Printer.CurrentLanguageIndicates the default printer language. A language that is used as a default by the Printer should also be listed in LanguagesSupported.1234567891011121314151617181920212223242526272829303132333435363738394041424344454647485051525354555657585960OtherUnknownPCLHPGLPJLPSPSPrinterIPDSPPDSEscapePEpsonDDIFInterpressISO6429Line DataMODCAREGISSCSSPDLTEK4014PDSIGPCodeVDSCDSEWPSLN03CCITTQUICCPAPDecPPLSimple TextNPAPDOCimPressPinwriterNPDLNEC201PLAutomaticPagesLIPSTIFFDiagnosticCaPSLEXCLLCDSXESMIMETIPSIPrescribeLinePrinterIDPXJCLPDFRPDLIntermecIPLUBIFingerprintUBIDirectProtocolFujitsuPCLXLCIM_Printer.LanguagesSupportedCIM_Printer.DefaultMimeTypeSpecifies the default mime type used by the Printer if the DefaultLanguage is set to indicate a mime type is in use (value=47).CIM_Printer.DefaultLanguagePrinter jobs processed since last reset. These jobs may be processed from one or more PrintQueues.trueTime of last reset of the Printer Device.An array of integers indicating Printer capabilities. Information such as "Duplex Printing" (value=3) or "Transparency Printing" (7) is specified in this property.Indexed0123456789101112131415161718192021UnknownOtherColor PrintingDuplex PrintingCopiesCollationStaplingTransparency PrintingPunchCoverBindBlack and White PrintingOne SidedTwo Sided Long EdgeTwo Sided Short EdgePortraitLandscapeReverse PortraitReverse LandscapeQuality HighQuality NormalQuality LowCIM_Printer.CapabilityDescriptionsCIM_PrintJob.FinishingCIM_PrintService.CapabilitiesAn array of free-form strings providing more detailed explanations for any of the Printer features indicated in the Capabilities array. Note, each entry of this array is related to the entry in the Capabilities array that is located at the same index.IndexedCIM_Printer.CapabilitiesSpecifies which finishings and other capabilities of the Printer will be used by default. An entry in DefaultCapabilities should also be listed in the Capabilities array.0123456789101112131415161718192021UnknownOtherColor PrintingDuplex PrintingCopiesCollationStaplingTransparency PrintingPunchCoverBindBlack and White PrintingOne SidedTwo Sided Long EdgeTwo Sided Short EdgePortraitLandscapeReverse PortraitReverse LandscapeQuality HighQuality NormalQuality LowCIM_Printer.CapabilitiesSpecifies which finishings and other capabilities of the Printer are currently being used. An entry in this property should also be listed in the Capabilities array.0123456789101112131415161718192021UnknownOtherColor PrintingDuplex PrintingCopiesCollationStaplingTransparency PrintingPunchCoverBindBlack and White PrintingOne SidedTwo Sided Long EdgeTwo Sided Short EdgePortraitLandscapeReverse PortraitReverse LandscapeQuality HighQuality NormalQuality LowCIM_Printer.CapabilitiesThe maximum number of copies that can be produced by the Printer from a single Job.CIM_PrintJob.CopiesThe number of copies that will be produced for a single Job unless otherwise specified.The maximum number of print-stream pages that the Printer can render onto a single media sheet.CIM_PrintJob.NumberUpThe number of print-stream pages that the Printer will render onto a single media sheet unless a Job specifies otherwise.Printer's horizontal resolution in Pixels per Inch.Pixels per InchCIM_PrintJob.HorizontalResolutionPrinter's vertical resolution in Pixels per Inch.Pixels per InchCIM_PrintJob.HorizontalResolutionIdentifies the available character sets for the output of text related to managing the Printer. Strings provided in this property should conform to the semantics and syntax specified by section 4.1.2 ("Charset parameter") in RFC 2046 (MIME Part 2) and contained in the IANA character-set registry. Examples include "utf-8", "us-ascii" and "iso-8859-1".IndexedCIM_PrintJob.CharSetMIB.IETF|Printer-MIB.prtLocalizationCharacterSetSpecifies the current character set being used for the output of text relating to management of the Printer. The character set described by this property should also be listed in CharsetsSupported. The string specified by this property should conform to the semantics and syntax specified by section 4.1.2 ("Charset parameter") in RFC 2046 (MIME Part 2) and contained in the IANA character-set registry. Examples include "utf-8", "us-ascii" and "iso-8859-1".CIM_Printer.CharSetsSupportedIdentifies the available languages for strings used by the Printer for the output of management information. The strings should conform to RFC 1766, for example "en" is used for English.IndexedMIB.IETF|Printer-MIB.prtLocalizationLanguageCIM_PrintJob.NaturalLanguageIdentifies the current language being used by the Printer for management. The language listed in the CurrentNaturalLanguage property should also be listed in NaturalLanguagesSupported.CIM_Printer.NaturalLanguagesSupportedSpecifies the largest Job (as a byte stream) that the Printer will accept in units of Kbytes. A value of zero indicates that no limit has been set.KiloBytesCIM_PrintJob.JobSizeDescribes all of the job sheets that are available on the Printer. This can also be used to describe the banner that a Printer might provide at the beginning of each Job, or can describe other user specified options.CIM_PrintJob.RequiredJobSheetsSpecifies the marking technology used by the Printer.123456789101112131415161718192021222324252627OtherUnknownElectrophotographic LEDElectrophotographic LaserElectrophotographic OtherImpact Moving Head Dot Matrix 9pinImpact Moving Head Dot Matrix 24pinImpact Moving Head Dot Matrix OtherImpact Moving Head Fully FormedImpact BandImpact OtherInkjet AqueousInkjet SolidInkjet OtherPenThermal TransferThermal SensitiveThermal DiffusionThermal OtherElectroerosionElectrostaticPhotographic MicrofichePhotographic ImagesetterPhotographic OtherIon DepositioneBeamTypesetterMIB.IETF|Printer-MIB.prtMarkerMarkTech 2.7.0Capabilities and management of a Printer Queue. A PrintQueue holds PrintJobs - which are placed on the Queue by a PrintService. Jobs can move from Queue to Queue.CIM_EnabledLogicalElement.EnabledStateIndicates that Jobs on the Queue will be passed to a Printer. When FALSE, a Job will remain on the Queue and will not be passed to a Printer for output. This property, coupled with the information in QueueAccepting, aligns with various values of the inherited EnabledState property: - When both QueueEnabled and QueueAccepting are TRUE, then EnabledState is set to 2 ("Enabled") - When both QueueEnabled and QueueAccepting are FALSE, then EnabledState is set to 3 ("Disabled") - When QueueEnabled is TRUE and QueueAccepting is FALSE (i.e., when the Queue is outputting jobs to the printer, but not accepting new jobs), then EnabledState is set to 6 ("Enabled but Offline") - When QueueEnabled is FALSE and QueueAccepting is TRUE (i.e., when the Queue is accepting print jobs but not sending them to a printer), then EnabledState is set to 8 ("Deferred") Both this property and QueueAccepting are deprecated in lieu of EnabledState.CIM_EnabledLogicalElement.EnabledStateWhen FALSE, no PrintService can place PrintJobs on the PrintQueue. The ability of an individual PrintService to place a Job on the Queue can be specified using the QueueAcceptingFromService property in the QueueForPrintService association. This property, coupled with the information in QueueEnabled, aligns with various values of the inherited EnabledState property: - When both QueueEnabled and QueueAccepting are TRUE, then EnabledState is set to 2 ("Enabled") - When both QueueEnabled and QueueAccepting are FALSE, then EnabledState is set to 3 ("Disabled") - When QueueEnabled is TRUE and QueueAccepting is FALSE (i.e., when the Queue is outputting jobs to the printer, but not accepting new jobs), then EnabledState is set to 6 ("Enabled but Offline") - When QueueEnabled is FALSE and QueueAccepting is TRUE (i.e., when the Queue is accepting print jobs but not sending them to a printer), then EnabledState is set to 8 ("Deferred") Both this property and QueueEnabled are deprecated in lieu of EnabledState.The current number of Jobs on the Queue.trueGives Queue-specific status information, beyond the ManagedSystemElement.Status property. This may be used to provide further qualification as to the status of the Queue or to indicate a secondary condition (e.g. spool area is full).0123OtherUnknownNo Additional StatusQueueSpoolAreaFullProvides a textual explanation for the status of the Queue. The settings of both QueueStatus and the Status property inherited from ManagedSystemElement may be described by QueueStatusInfo. For example, if "Stopping" is the value assigned to Status, then this property may contain an explanation as to why the Queue is being stopped.Specifies the largest possible Job (in terms of a single byte stream) that may be submitted to this Queue. A value of zero indicates that no limit has been set. Units are Kbytes.KiloBytesCIM_PrintJob.JobSizeSpecifies the priority that will be assigned to a new Job being submitted to this Queue, if the Job does not explicitly specify a priority. The range of valid priorities and the interpretation of priorities may be determined from the JobPriorityHigh and JobPriorityLow properties.CIM_PrintQueue.JobPriorityHighCIM_PrintQueue.JobPriorityLowSpecifies the numeric value that is used to represent the highest priority Jobs that are submitted to this Queue. The range of numeric values for priority may be inversed, e.g. a high priority job is represented by a low integer value. This is indicated by JobPriorityLow being greater than JobPriorityHigh. If both values (PriorityLow and PriorityHigh) are assigned to zero, then the Queue does not support Job priorities.CIM_PrintQueue.JobPriorityLowCIM_Job.PrioritySpecifies the numeric value that is used to represent the lowest priority Jobs that are submitted to this Queue. The range of numeric values for priority may be inversed, e.g. a low priority job is represented by a high integer value. This is indicated by JobPriorityLow being greater than JobPriorityHigh. If both values (PriorityLow and PriorityHigh) are assigned to zero, then the Queue does not support Job priorities.CIM_PrintQueue.JobPriorityHighCIM_Job.PrioritySpecifies the job sheets that are supported by this Queue. Typically the job sheets provided by a Queue will be the union or aggregation of those provided by all the Printers that it supports. However, a system administrator may choose to restrict access to some job sheets on a particular Queue. A Queue might also support additional job sheets through the use of a filter that adds a banner or some other page when a Job is taken from the Queue.CIM_PrintJob.RequiredJobSheets 2.7.1Description of a print request that is either waiting on a Queue for a Printer to become available, in the process of being output on a Printer, or that has previously been printed on a Printer. PrintJobs are weak to their current Queue, or to the last Queue that held them.CIM_PrintQueue.SystemCreationClassNametrue256The scoping System's CreationClassName.CIM_PrintQueue.SystemNametrue256The scoping System's Name.CIM_PrintQueue.CreationClassNametrue256The scoping Queue's CreationClassName.CIM_PrintQueue.Nametrue256The scoping Queue's Name.JobStatusThe inherited JobStatus is used to provide additional information about the status of a PrintJob beyond that enumerated by PrintJobStatus.CIM_PrintJob.PrintJobStatustrueUniquely identifies this Job within its scoping Queue.Provides additional textual descriptions of how this Job should be scheduled.Specifies the size of the PrintJob (as a byte stream) in units of Kbytes.KiloBytesCIM_Printer.MaxSizeSupportedCIM_PrintQueue.MaxJobSizeSpecifies the print language used by this Job.1234567891011121314151617181920212223242526272829303132333435363738394041424344454647485051525354555657585960OtherUnknownPCLHPGLPJLPSPSPrinterIPDSPPDSEscapePEpsonDDIFInterpressISO6429Line DataMODCAREGISSCSSPDLTEK4014PDSIGPCodeVDSCDSEWPSLN03CCITTQUICCPAPDecPPLSimple TextNPAPDOCimPressPinwriterNPDLNEC201PLAutomaticPagesLIPSTIFFDiagnosticCaPSLEXCLLCDSXESMIMETIPSIPrescribeLinePrinterIDPXJCLPDFRPDLIntermecIPLUBIFingerprintUBIDirectProtocolFujitsuPCLXLMIB.IETF|Printer-MIB.prtInterpreterLangFamilyCIM_Printer.LanguagesSupportedCIM_PrintService.LanguagesSupportedCIM_PrintJob.MimeTypesSpecifies the mime types used by the PrintJob if Language is set to indicate a mime type is in use (value=47).CIM_PrintJob.LanguageCIM_Printer.MimeTypesSupportedCIM_PrintService.MimeTypesSupportedA string specifying the type of paper that is required by this PrintJob. Each string should be expressed in the form specified by ISO/IEC 10175 Document Printing Application (DPA) which is also summarized in Appendix C of RFC 1759 (Printer MIB). Examples of valid strings are "iso-a4-colored" and "na-10x14-envelope".CIM_Printer.PaperTypesAvailableCIM_PrintService.PaperTypesAvailableAn array of integers indicating the type of finishing required by this Job. It is equivalent to the Capabilities property provided by the Printer.Indexed0123456789101112131415161718192021UnknownOtherColor PrintingDuplex PrintingCopiesCollationStaplingTransparency PrintingPunchCoverBindBlack and White PrintingOne SidedTwo Sided Long EdgeTwo Sided Short EdgePortraitLandscapeReverse PortraitReverse LandscapeQuality HighQuality NormalQuality LowCIM_Printer.CapabilitiesCIM_PrintService.CapabilitiesThe number of physical copies of the output that will be produced from this Job.CIM_Printer.MaxCopiesThe horizontal resolution in Pixels per Inch for the Job.Pixels per InchCIM_Printer.HorizontalResolutionThe vertical resolution in Pixels per Inch for the Job.Pixels per InchCIM_Printer.VerticalResolutionSpecifies the character set and encoding method that should be used by the Printer for the management of this Job. The strings should conform to the semantics and syntax specified by section 4.1.2 ("Charset parameter") in RFC 2046 (MIME Part 2) and contained in the IANA character-set registry. Examples include "utf-8", "us-ascii" and "iso-8859-1".CIM_Printer.CharSetsSupportedIdentifies the language that should be used by the Printer for the management of this Job. The specified value should conform to RFC 1766. For example, "en" is used for English.CIM_Printer.NaturalLanguagesSupportedThe number of print-stream pages that should be rendered onto a single media sheet when the Printer outputs this PrintJob.CIM_Printer.MaxNumberUpDescribes the current state of this Job with respect to the PrintQueue and the Printer. Additional information may be specified in JobStatus.1234567OtherUnknownPendingBlockedCompleteCompleted With ErrorPrintingCIM_PrintJob.TimeCompletedCIM_PrintJob.JobStatusTime when this Job was completed. This value is only valid if the PrintJobStatus has been assigned to "Complete" (value=5) or "Completed With Error" (value=6).CIM_PrintJob.PrintJobStatusDescribes the job sheets that should be used when this Job is output on the Printer.CIM_Printer.AvailableJobSheetsProvides additional information, beyond Job Owner inherited from CIM_Job, to identify the origins of the PrintJob. This property could include information such as the System, application or Process that created the Job. 2.6.0The ServiceAccessPoint for a printing Service.Specifies the print procotols that this AccessPoint uses. Note that each entry of this array is related to the entry in the PrintProtocolInfo array that is located at the same index.Indexed01234567UnknownOtherSMBBSDSYSVHPNPIPPLocalCIM_PrintSAP.PrintProtocolInfoProvides clarifying or additional information about the protocols supported by this AccessPoint. Note, each entry of this array is related to the entry in the PrintProtocol array that is located at the same index.IndexedCIM_PrintSAP.PrintProtocol 2.7.1The Service that provides support for printing. The basic assumption of the Printing Model is that a PrintService accepts a PrintJob for processing, via its PrintSAP. The Job is then placed on a PrintQueue (indicated by the QueueForPrintService association). Printers take Jobs from Queues (indicated by the PrinterServicingQueue association).An array of free-form strings specifying the types of paper that may be used by Jobs that are submitted to this PrintService. This may be different than the paper types that are installed on the Printer, because the PrintService may include support for manually making other types available or only a subset of paper types may be exported via this Service. Each string should be expressed in the form specified by ISO/IEC 10175 Document Printing Application (DPA) which is also summarized in Appendix C of RFC 1759 (Printer MIB). Examples of valid strings are "iso-a4-colored" and "na-10x14-envelope".CIM_Printer.PaperTypesAvailableCIM_PrintJob.RequiredPaperTypeAn array indicating the print languages supported by the PrintService. A PrintService may support more languages than those available on the underlying Printer through the use of filters. An administrator may also choose to prevent some languages from being exported by the PrintService.1234567891011121314151617181920212223242526272829303132333435363738394041424344454647485051525354555657585960OtherUnknownPCLHPGLPJLPSPSPrinterIPDSPPDSEscapePEpsonDDIFInterpressISO6429Line DataMODCAREGISSCSSPDLTEK4014PDSIGPCodeVDSCDSEWPSLN03CCITTQUICCPAPDecPPLSimple TextNPAPDOCimPressPinwriterNPDLNEC201PLAutomaticPagesLIPSTIFFDiagnosticCaPSLEXCLLCDSXESMIMETIPSIPrescribeLinePrinterIDPXJCLPDFRPDLIntermecIPLUBIFingerprintUBIDirectProtocolFujitsuPCLXLIndexedMIB.IETF|Printer-MIB.prtInterpreterLangFamilyCIM_Printer.LanguagesSupportedCIM_PrintJob.LanguageCIM_PrintService.MimeTypesSupportedAn array of free-form strings providing more detailed explanations for any mime types that are supported by the PrintService. Support for mime types is indicated by specifying a value of 47 in the LanguagesSupported array.CIM_Printer.MimeTypesSupportedCIM_PrintJob.MimeTypesCIM_PrintService.LanguagesSupportedAn array of integers indicating the capabilities supported by this service. Information such as "Duplex Printing" (value=3) or "Transparency Printing" (7) is specified in this property.Indexed0123456789101112131415161718192021UnknownOtherColor PrintingDuplex PrintingCopiesCollationStaplingTransparency PrintingPunchCoverBindBlack and White PrintingOne SidedTwo Sided Long EdgeTwo Sided Short EdgePortraitLandscapeReverse PortraitReverse LandscapeQuality HighQuality NormalQuality LowCIM_Printer.CapabilitiesCIM_PrintJob.FinishingCIM_PrintService.CapabilityDescriptionsAn array of free-form strings providing more detailed explanations for any of the Printer features indicated in the Capabilities array. Note, each entry of this array is related to the entry in the Capabilities array that is located at the same index.IndexedCIM_PrintService.CapabilitiesDescribes the filters that are available within this PrintService. For example, a PrintService may be able to convert a Job submitted in one page description language to another, so that it can be passed to an available Printer. 2.6.0This association indicates that a Printer can be passed PrintJobs from a particular Queue.trueAntecedentA destination Printer for Jobs enqueued on the Dependent Queue.trueDependentA Queue that is providing Jobs to the Printer.true 2.6.0This association indicates that a Printer is currently servicing a particular PrintJob.trueAntecedentThe destination Printer for a PrintJob.trueDependentThe PrintJob.true 2.6.0This association indicates which files are associated with a PrintJob.truetrueGroupComponentThe PrintJob that is based on one or more Files.truetruePartComponentThe File(s) that make up a PrintJob.true 2.6.0This association indicates that a PrintService utilizes a particular PrintQueue.trueAntecedentThe PrintQueue that the Service utilizes.trueDependentThe PrintService that puts Jobs on the Queue.trueIndicates that the PrintService can accept Jobs and place them on the Queue. 2.6.0This association indicates that the Jobs from a PrintQueue can be sent to the referenced PrintSAP, to be handled by the SAP's backing PrintService.trueAntecedentThe PrintSAP for the PrintService.trueDependentThe PrintQueue that forwards Jobs to the SAP.true 2.6.0This association indicates which Queue holds a PrintJob and where the Job is located within that Queue. A Job may remain on its final Queue once it has been printed with a PrintJobStatus of "Complete" or "Completed With Error".true11The PrintQueue on which the Job is held.AntecedenttruetrueThe PrintJob.DependenttrueThe position of the PrintJob on the Queue. The top of the Queue is indicated by a value of 1 with higher values being used to represent Jobs that are further away from the top of the Queue. A QueuePosition of zero indicate that the Job has completed (either with or without error). true2.6.0A Sensor is a hardware device capable of measuring the characteristics of some physical property - for example, the temperature or voltage characteristics of a UnitaryComputerSystem.The Type of the Sensor, e.g. Voltage or Temperature Sensor. If the type is set to "Other", then the OtherSensorTypeDescription can be used to further identify the type, or if the Sensor has numeric readings, then the type of the Sensor can be implicitly determined by the Units. A description of the different Sensor types is as follows: A Temperature Sensor measures the environmental temperature. Voltage and Current Sensors measure electrical voltage and current readings. A Tachometer measures speed/revolutions of a Device. For example, a Fan Device can have an associated Tachometer which measures its speed. A Counter is a general purpose Sensor that measures some numerical property of a Device. A Counter value can be cleared, but it never decreases. A Switch Sensor has states like Open/Close, On/Off, or Up/Down. A Lock has states of Locked/Unlocked. Humidity, Smoke Detection and Air Flow Sensors measure the equivalent environmental characteristics. A Presence Sensor detects the presence of a PhysicalElement.0123456789101112UnknownOtherTemperatureVoltageCurrentTachometerCounterSwitchLockHumiditySmoke DetectionPresenceAir FlowCIM_Sensor.OtherSensorTypeDescription128A string describing the Sensor type - used when the SensorType property is set to "Other".CIM_Sensor.SensorType128PossibleStates enumerates the string outputs of the Sensor. For example, a "Switch" Sensor may output the states "On", or "Off". Another implementation of the Switch may output the states "Open", and "Close". Another example is a NumericSensor supporting thresholds. This Sensor can report the states like "Normal", "Upper Fatal", "Lower Non-Critical", etc. A NumericSensor that does not publish readings and thresholds, but stores this data internally, can still report its states.128The current state indicated by the Sensor. This is always one of the "PossibleStates".The polling interval that the Sensor hardware or the instrumentation uses to determine the current state of the Sensor.NanoSeconds 2.6.0Many Devices include Sensors or have Sensors installed nearby, in order to measure critical input and output properties. This association indicates that relationship.trueAntecedentThe Sensor.trueDependentThe LogicalDevice for which information is measured by the Sensor.true 2.6.0A BinarySensor provides a boolean output. Given the addition of the CurrentState and PossibleStates properties to Sensor, the BinarySensor subclass is no longer necessary, but is retained for backward compatibility. A BinarySensor can be created by instantiating a Sensor with two PossibleStates.The current value indicated by the Sensor.ExpectedReading indicates the 'normal' value for the Sensor.64InterpretationOfTrue is a string indicating what a 'True' value from the BinarySensor means. This information could be displayed to a user.64InterpretationOfFalse is a string indicating what a 'False' value from the BinarySensor means. This information could be displayed to a user. 2.6.0A Multi-StateSensor is a multi-member set of Sensors. true2.7.0The CollectionOfSensors association indicates the Sensors that make up a MultiStateSensor.truetrueGroupComponent1The MultiStateSensor.truetruePartComponent2A Sensor that is part of the MultiStateSensor.true 2.6.0A Numeric Sensor is capable of returning numeric readings and optionally supports thresholds settings.The base unit of the values returned by this Sensor. All the values returned by this Sensor are represented in the units obtained by (BaseUnits * 10 raised to the power of the UnitModifier). For example, if BaseUnits is Volts and the UnitModifier is -6, then the units of the values returned are MicroVolts. However, if the RateUnits property is set to a value other than "None", then the units are further qualified as rate units. In the above example, if RateUnits is set to "Per Second", then the values returned by the Sensor are in MicroVolts/Second. The units apply to all numeric properties of the Sensor, unless explicitly overridden by the Units qualifier.01234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465UnknownOtherDegrees CDegrees FDegrees KVoltsAmpsWattsJoulesCoulombsVANitsLumensLuxCandelaskPaPSINewtonsCFMRPMHertzSecondsMinutesHoursDaysWeeksMilsInchesFeetCubic InchesCubic FeetMetersCubic CentimetersCubic MetersLitersFluid OuncesRadiansSteradiansRevolutionsCyclesGravitiesOuncesPoundsFoot-PoundsOunce-InchesGaussGilbertsHenriesFaradsOhmsSiemensMolesBecquerelsPPM (parts/million)DecibelsDbADbCGraysSievertsColor Temperature Degrees KBitsBytesWords (data)DoubleWordsQuadWordsPercentageCIM_NumericSensor.UnitModifierCIM_NumericSensor.RateUnitsThe unit multiplier for the values returned by this Sensor. All the values returned by this Sensor are represented in the units obtained by (BaseUnits * 10 raised to the power of the UnitModifier). For example, if BaseUnits is Volts and the UnitModifier is -6, then the units of the values returned are MicroVolts. However, if the RateUnits property is set to a value other than "None", then the units are further qualified as rate units. In the above example, if RateUnits is set to "Per Second", then the values returned by the Sensor are in MicroVolts/Second. The units apply to all numeric properties of the Sensor, unless explicitly overridden by the Units qualifier.CIM_NumericSensor.BaseUnitsCIM_NumericSensor.RateUnitsSpecifies if the units returned by this Sensor are rate units. All the values returned by this Sensor are represented in the units obtained by (BaseUnits * 10 raised to the power of the UnitModifier). This is true unless this property (RateUnits) has a value different than "None". For example, if BaseUnits is Volts and the UnitModifier is -6, then the units of the values returned are MicroVolts. But, if the RateUnits property is set to a value other than "None", then the units are further qualified as rate units. In the above example, if RateUnits is set to "Per Second", then the values returned by the Sensor are in MicroVolts/Second. The units apply to all numeric properties of the Sensor, unless explicitly overridden by the Units qualifier. Any implementation of CurrentReading should be qualified with either a Counter or a Gauge qualifier, depending on the characteristics of the sensor being modeled.0123456789NonePer MicroSecondPer MilliSecondPer SecondPer MinutePer HourPer DayPer WeekPer MonthPer YearCIM_NumericSensor.UnitModifierCIM_NumericSensor.BaseUnitsThe current value indicated by the Sensor.NominalReading indicates the 'normal' or expected value for the NumericSensor.NormalMax provides guidance for the user as to the normal maximum range for the NumericSensor.NormalMin provides guidance for the user as to the normal minimum range for the NumericSensor.MaxReadable indicates the largest value of the measured property that can be read by the NumericSensor.MinReadable indicates the smallest value of the measured property that can be read by the NumericSensor.Resolution indicates the ability of the Sensor to resolve differences in the measured property. This value may vary depending on whether the Device is linear over its dynamic range.Indicates the tolerance of the Sensor for the measured property. Tolerance, along with Resolution and Accuracy, is used to calculate the actual value of the measured physical property. Tolerance may vary depending on whether the Device is linear over its dynamic range.Indicates the accuracy of the Sensor for the measured property. Its value is recorded as plus/minus hundredths of a percent. Accuracy, along with Resolution and Tolerance, is used to calculate the actual value of the measured physical property. Accuracy may vary depending on whether the Device is linear over its dynamic range.Hundredths of PercentIndicates that the Sensor is linear over its dynamic range.Indicates the margin built around the thresholds. This margin prevents unnecessary state changes when the Sensor reading may fluctuate very close to its thresholds. This could be due to the Sensor's tolerance/accuracy/resolution or due to environmental factors. Once a threshold is crossed, the state of the Sensor should change. However, the state should not fluctuate between the old and new states unless the Sensor's change in the reading exceeds the hysteresis value.The Sensor's threshold values specify the ranges (min and max values) for determining whether the Sensor is operating under Normal, NonCritical, Critical or Fatal conditions. If CurrentReading is between LowerThresholdNonCritical and UpperThresholdNonCritical, then the Sensor is reporting a normal value. If CurrentReading is between LowerThresholdNonCritical and LowerThresholdCritical, then the CurrentState is NonCritical.The Sensor's threshold values specify the ranges (min and max values) for determining whether the Sensor is operating under Normal, NonCritical, Critical or Fatal conditions. If the CurrentReading is between LowerThresholdNonCritical and UpperThresholdNonCritical, then the Sensor is reporting a normal value. If the CurrentReading is between UpperThresholdNonCritical and UpperThresholdCritical, then the CurrentState is NonCritical.The Sensor's threshold values specify the ranges (min and max values) for determining whether the Sensor is operating under Normal, NonCritical, Critical or Fatal conditions. If the CurrentReading is between LowerThresholdCritical and LowerThresholdFatal, then the CurrentState is Critical.The Sensor's threshold values specify the ranges (min and max values) for determining whether the Sensor is operating under Normal, NonCritical, Critical or Fatal conditions. If the CurrentReading is between UpperThresholdCritical and UpperThresholdFatal, then the CurrentState is Critical.The Sensor's threshold values specify the ranges (min and max values) for determining whether the Sensor is operating under Normal, NonCritical, Critical or Fatal conditions. If the CurrentReading is below LowerThresholdFatal, then the CurrentState is Fatal.The Sensor's threshold values specify the ranges (min and max values) for determining whether the Sensor is operating under Normal, NonCritical, Critical or Fatal conditions. If the CurrentReading is above UpperThresholdFatal, then the CurrentState is Fatal.An array representing the thresholds supported by this Sensor.012345LowerThresholdNonCriticalUpperThresholdNonCriticalLowerThresholdCriticalUpperThresholdCriticalLowerThresholdFatalUpperThresholdFatalAn array representing the thresholds that are currently enabled for this Sensor.012345LowerThresholdNonCriticalUpperThresholdNonCriticalLowerThresholdCriticalUpperThresholdCriticalLowerThresholdFatalUpperThresholdFatalAn array representing the writable thresholds supported by Sensor.012345LowerThresholdNonCriticalUpperThresholdNonCriticalLowerThresholdCriticalUpperThresholdCriticalLowerThresholdFatalUpperThresholdFatalThis method resets the values of the thresholds to hardware defaults. This method returns 0 if successful, 1 if unsupported and any 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.For a non-linear Sensor, the resolution, accuracy, tolerance and hysteresis vary as the current reading moves. This method can be used to get these factors for a given reading. It returns 0 if successful, 1 if unsupported, and any 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.truefalsetruefalsetruefalsetruefalsetrue 2.6.0A DiscreteSensor has a set of legal string values, that it can report. These values are enumerated in the Sensor's PossibleValues property. A DiscreteSensor will always have a 'current reading' that corresponds to one of the enumerated values. Given the addition of the CurrentState and PossibleStates properties to Sensor, the DiscreteSensor subclass is no longer necessary, but is retained for backward compatibility. Information in the CurrentReading and PossibleValues properties will typically have the same values and semantics as for the CurrentState and PossibleStates properties, inherited from Sensor.64The current value indicated by the Sensor.64PossibleValues enumerates the string outputs that can be reported by the DiscreteSensor.64AcceptableValues details which of the PossibleValues strings are considered 'acceptable' (ie, 'not an error'). 2.6.0This class exists for backward compatibility to earlier CIM Schema definitions. With additions to Sensor and NumericSensor in V2.2, it is no longer necessary. A TempertatureSensor can be defined by setting the SensorType property, inherited from Sensor, to 2 ("Temperature"). Other properties of this class are hard-coded to constant values to correspond to definitions in the Sensor hierarchy.SensorTypeThe Type of the Sensor, e.g. Voltage or Temperature Sensor. If the type is set to "Other", then the OtherSensorTypeDescription can be used to further identify the type, or if the Sensor has numeric readings, then the type of the Sensor can be implicitly determined by the Units. A description of the different Sensor types is as follows: A Temperature Sensor measures the environmental temperature. Voltage and Current Sensors measure electrical voltage and current readings. A Tachometer measures speed/revolutions of a Device. For example, a Fan Device can have an associated Tachometer which measures its speed. A Counter is a general purpose Sensor that measures some numerical property of a Device. A Counter value can be cleared, but it never decreases. A Switch Sensor has states like Open/Close, On/Off, or Up/Down. A Lock has states of Locked/Unlocked. Humidity, Smoke Detection and Air Flow Sensors measure the equivalent environmental characteristics. A Presence Sensor detects the presence of a PhysicalElement.0123456789101112UnknownOtherTemperatureVoltageCurrentTachometerCounterSwitchLockHumiditySmoke DetectionPresenceAir FlowCIM_Sensor.OtherSensorTypeDescription2BaseUnitsThe base unit of the values returned by this Sensor. All the values returned by this Sensor are represented in the units obtained by (BaseUnits * 10 raised to the power of the UnitModifier). For example, if BaseUnits is Volts and the UnitModifier is -6, then the units of the values returned are MicroVolts. However, if the RateUnits property is set to a value other than "None", then the units are further qualified as rate units. In the above example, if RateUnits is set to "Per Second", then the values returned by the Sensor are in MicroVolts/Second. The units apply to all numeric properties of the Sensor, unless explicitly overridden by the Units qualifier.01234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465UnknownOtherDegrees CDegrees FDegrees KVoltsAmpsWattsJoulesCoulombsVANitsLumensLuxCandelaskPaPSINewtonsCFMRPMHertzSecondsMinutesHoursDaysWeeksMilsInchesFeetCubic InchesCubic FeetMetersCubic CentimetersCubic MetersLitersFluid OuncesRadiansSteradiansRevolutionsCyclesGravitiesOuncesPoundsFoot-PoundsOunce-InchesGaussGilbertsHenriesFaradsOhmsSiemensMolesBecquerelsPPM (parts/million)DecibelsDbADbCGraysSievertsColor Temperature Degrees KBitsBytesWords (data)DoubleWordsQuadWordsPercentageCIM_NumericSensor.UnitModifierCIM_NumericSensor.RateUnits2UnitModifierThe unit multiplier for the values returned by this Sensor. All the values returned by this Sensor are represented in the units obtained by (BaseUnits * 10 raised to the power of the UnitModifier). For example, if BaseUnits is Volts and the UnitModifier is -6, then the units of the values returned are MicroVolts. However, if the RateUnits property is set to a value other than "None", then the units are further qualified as rate units. In the above example, if RateUnits is set to "Per Second", then the values returned by the Sensor are in MicroVolts/Second. The units apply to all numeric properties of the Sensor, unless explicitly overridden by the Units qualifier.CIM_NumericSensor.BaseUnitsCIM_NumericSensor.RateUnits-1RateUnitsSpecifies if the units returned by this Sensor are rate units. All the values returned by this Sensor are represented in the units obtained by (BaseUnits * 10 raised to the power of the UnitModifier). This is true unless this property (RateUnits) has a value different than "None". For example, if BaseUnits is Volts and the UnitModifier is -6, then the units of the values returned are MicroVolts. But, if the RateUnits property is set to a value other than "None", then the units are further qualified as rate units. In the above example, if RateUnits is set to "Per Second", then the values returned by the Sensor are in MicroVolts/Second. The units apply to all numeric properties of the Sensor, unless explicitly overridden by the Units qualifier. Any implementation of CurrentReading should be qualified with either a Counter or a Gauge qualifier, depending on the characteristics of the sensor being modeled.0123456789NonePer MicroSecondPer MilliSecondPer SecondPer MinutePer HourPer DayPer WeekPer MonthPer YearCIM_NumericSensor.UnitModifierCIM_NumericSensor.BaseUnits0CurrentReadingMIF.DMTF|Temperature Probe|002.5The current value indicated by the Sensor.NominalReadingMIF.DMTF|Temperature Probe|002.6NominalReading indicates the 'normal' or expected value for the NumericSensor.NormalMaxMIF.DMTF|Temperature Probe|002.7NormalMax provides guidance for the user as to the normal maximum range for the NumericSensor.NormalMinMIF.DMTF|Temperature Probe|002.8NormalMin provides guidance for the user as to the normal minimum range for the NumericSensor.MaxReadableMIF.DMTF|Temperature Probe|002.9MaxReadable indicates the largest value of the measured property that can be read by the NumericSensor.MinReadableMIF.DMTF|Temperature Probe|002.10MinReadable indicates the smallest value of the measured property that can be read by the NumericSensor.ResolutionHundredths of Degrees CMIF.DMTF|Temperature Probe|002.17Resolution indicates the ability of the Sensor to resolve differences in the measured property. This value may vary depending on whether the Device is linear over its dynamic range.ToleranceMIF.DMTF|Temperature Probe|002.18Indicates the tolerance of the Sensor for the measured property. Tolerance, along with Resolution and Accuracy, is used to calculate the actual value of the measured physical property. Tolerance may vary depending on whether the Device is linear over its dynamic range.AccuracyMIF.DMTF|Temperature Probe|002.19Indicates the accuracy of the Sensor for the measured property. Its value is recorded as plus/minus hundredths of a percent. Accuracy, along with Resolution and Tolerance, is used to calculate the actual value of the measured physical property. Accuracy may vary depending on whether the Device is linear over its dynamic range.Hundredths of PercentLowerThresholdNonCriticalMIF.DMTF|Temperature Probe|002.11The Sensor's threshold values specify the ranges (min and max values) for determining whether the Sensor is operating under Normal, NonCritical, Critical or Fatal conditions. If CurrentReading is between LowerThresholdNonCritical and UpperThresholdNonCritical, then the Sensor is reporting a normal value. If CurrentReading is between LowerThresholdNonCritical and LowerThresholdCritical, then the CurrentState is NonCritical.UpperThresholdNonCriticalMIF.DMTF|Temperature Probe|002.12The Sensor's threshold values specify the ranges (min and max values) for determining whether the Sensor is operating under Normal, NonCritical, Critical or Fatal conditions. If the CurrentReading is between LowerThresholdNonCritical and UpperThresholdNonCritical, then the Sensor is reporting a normal value. If the CurrentReading is between UpperThresholdNonCritical and UpperThresholdCritical, then the CurrentState is NonCritical.LowerThresholdCriticalMIF.DMTF|Temperature Probe|002.13The Sensor's threshold values specify the ranges (min and max values) for determining whether the Sensor is operating under Normal, NonCritical, Critical or Fatal conditions. If the CurrentReading is between LowerThresholdCritical and LowerThresholdFatal, then the CurrentState is Critical.UpperThresholdCriticalMIF.DMTF|Temperature Probe|002.14The Sensor's threshold values specify the ranges (min and max values) for determining whether the Sensor is operating under Normal, NonCritical, Critical or Fatal conditions. If the CurrentReading is between UpperThresholdCritical and UpperThresholdFatal, then the CurrentState is Critical.LowerThresholdFatalMIF.DMTF|Temperature Probe|002.15The Sensor's threshold values specify the ranges (min and max values) for determining whether the Sensor is operating under Normal, NonCritical, Critical or Fatal conditions. If the CurrentReading is below LowerThresholdFatal, then the CurrentState is Fatal.UpperThresholdFatalMIF.DMTF|Temperature Probe|002.16The Sensor's threshold values specify the ranges (min and max values) for determining whether the Sensor is operating under Normal, NonCritical, Critical or Fatal conditions. If the CurrentReading is above UpperThresholdFatal, then the CurrentState is Fatal. 2.6.0This class exists for backward compatibility to earlier CIM Schema definitions. With additions to Sensor and NumericSensor in V2.2, it is no longer necessary. A CurrentSensor can be defined by setting the SensorType property, inherited from Sensor, to 4 ("Current"). Other properties of this class are hard-coded to constant values to correspond to definitions in the Sensor hierarchy.SensorTypeThe Type of the Sensor, e.g. Voltage or Temperature Sensor. If the type is set to "Other", then the OtherSensorTypeDescription can be used to further identify the type, or if the Sensor has numeric readings, then the type of the Sensor can be implicitly determined by the Units. A description of the different Sensor types is as follows: A Temperature Sensor measures the environmental temperature. Voltage and Current Sensors measure electrical voltage and current readings. A Tachometer measures speed/revolutions of a Device. For example, a Fan Device can have an associated Tachometer which measures its speed. A Counter is a general purpose Sensor that measures some numerical property of a Device. A Counter value can be cleared, but it never decreases. A Switch Sensor has states like Open/Close, On/Off, or Up/Down. A Lock has states of Locked/Unlocked. Humidity, Smoke Detection and Air Flow Sensors measure the equivalent environmental characteristics. A Presence Sensor detects the presence of a PhysicalElement.0123456789101112UnknownOtherTemperatureVoltageCurrentTachometerCounterSwitchLockHumiditySmoke DetectionPresenceAir FlowCIM_Sensor.OtherSensorTypeDescription4BaseUnitsThe base unit of the values returned by this Sensor. All the values returned by this Sensor are represented in the units obtained by (BaseUnits * 10 raised to the power of the UnitModifier). For example, if BaseUnits is Volts and the UnitModifier is -6, then the units of the values returned are MicroVolts. However, if the RateUnits property is set to a value other than "None", then the units are further qualified as rate units. In the above example, if RateUnits is set to "Per Second", then the values returned by the Sensor are in MicroVolts/Second. The units apply to all numeric properties of the Sensor, unless explicitly overridden by the Units qualifier.01234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465UnknownOtherDegrees CDegrees FDegrees KVoltsAmpsWattsJoulesCoulombsVANitsLumensLuxCandelaskPaPSINewtonsCFMRPMHertzSecondsMinutesHoursDaysWeeksMilsInchesFeetCubic InchesCubic FeetMetersCubic CentimetersCubic MetersLitersFluid OuncesRadiansSteradiansRevolutionsCyclesGravitiesOuncesPoundsFoot-PoundsOunce-InchesGaussGilbertsHenriesFaradsOhmsSiemensMolesBecquerelsPPM (parts/million)DecibelsDbADbCGraysSievertsColor Temperature Degrees KBitsBytesWords (data)DoubleWordsQuadWordsPercentageCIM_NumericSensor.UnitModifierCIM_NumericSensor.RateUnits6UnitModifierThe unit multiplier for the values returned by this Sensor. All the values returned by this Sensor are represented in the units obtained by (BaseUnits * 10 raised to the power of the UnitModifier). For example, if BaseUnits is Volts and the UnitModifier is -6, then the units of the values returned are MicroVolts. However, if the RateUnits property is set to a value other than "None", then the units are further qualified as rate units. In the above example, if RateUnits is set to "Per Second", then the values returned by the Sensor are in MicroVolts/Second. The units apply to all numeric properties of the Sensor, unless explicitly overridden by the Units qualifier.CIM_NumericSensor.BaseUnitsCIM_NumericSensor.RateUnits-3RateUnitsSpecifies if the units returned by this Sensor are rate units. All the values returned by this Sensor are represented in the units obtained by (BaseUnits * 10 raised to the power of the UnitModifier). This is true unless this property (RateUnits) has a value different than "None". For example, if BaseUnits is Volts and the UnitModifier is -6, then the units of the values returned are MicroVolts. But, if the RateUnits property is set to a value other than "None", then the units are further qualified as rate units. In the above example, if RateUnits is set to "Per Second", then the values returned by the Sensor are in MicroVolts/Second. The units apply to all numeric properties of the Sensor, unless explicitly overridden by the Units qualifier. Any implementation of CurrentReading should be qualified with either a Counter or a Gauge qualifier, depending on the characteristics of the sensor being modeled.0123456789NonePer MicroSecondPer MilliSecondPer SecondPer MinutePer HourPer DayPer WeekPer MonthPer YearCIM_NumericSensor.UnitModifierCIM_NumericSensor.BaseUnits0CurrentReadingMIF.DMTF|Electrical Current Probe|001.5The current value indicated by the Sensor.NominalReadingMIF.DMTF|Electrical Current Probe|001.6NominalReading indicates the 'normal' or expected value for the NumericSensor.NormalMaxMIF.DMTF|Electrical Current Probe|001.7NormalMax provides guidance for the user as to the normal maximum range for the NumericSensor.NormalMinMIF.DMTF|Electrical Current Probe|001.8NormalMin provides guidance for the user as to the normal minimum range for the NumericSensor.MaxReadableMIF.DMTF|Electrical Current Probe|001.9MaxReadable indicates the largest value of the measured property that can be read by the NumericSensor.MinReadableMIF.DMTF|Electrical Current Probe|001.10MinReadable indicates the smallest value of the measured property that can be read by the NumericSensor.ResolutionTenths of MilliAmpsMIF.DMTF|Electrical Current Probe|001.17Resolution indicates the ability of the Sensor to resolve differences in the measured property. This value may vary depending on whether the Device is linear over its dynamic range.ToleranceMIF.DMTF|Electrical Current Probe|001.18Indicates the tolerance of the Sensor for the measured property. Tolerance, along with Resolution and Accuracy, is used to calculate the actual value of the measured physical property. Tolerance may vary depending on whether the Device is linear over its dynamic range.AccuracyMIF.DMTF|Electrical Current Probe|001.19Indicates the accuracy of the Sensor for the measured property. Its value is recorded as plus/minus hundredths of a percent. Accuracy, along with Resolution and Tolerance, is used to calculate the actual value of the measured physical property. Accuracy may vary depending on whether the Device is linear over its dynamic range.Hundredths of PercentLowerThresholdNonCriticalMIF.DMTF|Electrical Current Probe|001.11The Sensor's threshold values specify the ranges (min and max values) for determining whether the Sensor is operating under Normal, NonCritical, Critical or Fatal conditions. If CurrentReading is between LowerThresholdNonCritical and UpperThresholdNonCritical, then the Sensor is reporting a normal value. If CurrentReading is between LowerThresholdNonCritical and LowerThresholdCritical, then the CurrentState is NonCritical.UpperThresholdNonCriticalMIF.DMTF|Electrical Current Probe|001.12The Sensor's threshold values specify the ranges (min and max values) for determining whether the Sensor is operating under Normal, NonCritical, Critical or Fatal conditions. If the CurrentReading is between LowerThresholdNonCritical and UpperThresholdNonCritical, then the Sensor is reporting a normal value. If the CurrentReading is between UpperThresholdNonCritical and UpperThresholdCritical, then the CurrentState is NonCritical.LowerThresholdCriticalMIF.DMTF|Electrical Current Probe|001.13The Sensor's threshold values specify the ranges (min and max values) for determining whether the Sensor is operating under Normal, NonCritical, Critical or Fatal conditions. If the CurrentReading is between LowerThresholdCritical and LowerThresholdFatal, then the CurrentState is Critical.UpperThresholdCriticalMIF.DMTF|Electrical Current Probe|001.14The Sensor's threshold values specify the ranges (min and max values) for determining whether the Sensor is operating under Normal, NonCritical, Critical or Fatal conditions. If the CurrentReading is between UpperThresholdCritical and UpperThresholdFatal, then the CurrentState is Critical.LowerThresholdFatalMIF.DMTF|Electrical Current Probe|001.15The Sensor's threshold values specify the ranges (min and max values) for determining whether the Sensor is operating under Normal, NonCritical, Critical or Fatal conditions. If the CurrentReading is below LowerThresholdFatal, then the CurrentState is Fatal.UpperThresholdFatalMIF.DMTF|Electrical Current Probe|001.16The Sensor's threshold values specify the ranges (min and max values) for determining whether the Sensor is operating under Normal, NonCritical, Critical or Fatal conditions. If the CurrentReading is above UpperThresholdFatal, then the CurrentState is Fatal. 2.6.0This class exists for backward compatibility to earlier CIM Schema definitions. With additions to Sensor and NumericSensor in V2.2, it is no longer necessary. A VoltageSensor can be defined by setting the SensorType property, inherited from Sensor, to 3 ("Voltage"). Other properties of this class are hard-coded to constant values to correspond to definitions in the Sensor hierarchy.SensorTypeThe Type of the Sensor, e.g. Voltage or Temperature Sensor. If the type is set to "Other", then the OtherSensorTypeDescription can be used to further identify the type, or if the Sensor has numeric readings, then the type of the Sensor can be implicitly determined by the Units. A description of the different Sensor types is as follows: A Temperature Sensor measures the environmental temperature. Voltage and Current Sensors measure electrical voltage and current readings. A Tachometer measures speed/revolutions of a Device. For example, a Fan Device can have an associated Tachometer which measures its speed. A Counter is a general purpose Sensor that measures some numerical property of a Device. A Counter value can be cleared, but it never decreases. A Switch Sensor has states like Open/Close, On/Off, or Up/Down. A Lock has states of Locked/Unlocked. Humidity, Smoke Detection and Air Flow Sensors measure the equivalent environmental characteristics. A Presence Sensor detects the presence of a PhysicalElement.0123456789101112UnknownOtherTemperatureVoltageCurrentTachometerCounterSwitchLockHumiditySmoke DetectionPresenceAir FlowCIM_Sensor.OtherSensorTypeDescription3BaseUnitsThe base unit of the values returned by this Sensor. All the values returned by this Sensor are represented in the units obtained by (BaseUnits * 10 raised to the power of the UnitModifier). For example, if BaseUnits is Volts and the UnitModifier is -6, then the units of the values returned are MicroVolts. However, if the RateUnits property is set to a value other than "None", then the units are further qualified as rate units. In the above example, if RateUnits is set to "Per Second", then the values returned by the Sensor are in MicroVolts/Second. The units apply to all numeric properties of the Sensor, unless explicitly overridden by the Units qualifier.01234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465UnknownOtherDegrees CDegrees FDegrees KVoltsAmpsWattsJoulesCoulombsVANitsLumensLuxCandelaskPaPSINewtonsCFMRPMHertzSecondsMinutesHoursDaysWeeksMilsInchesFeetCubic InchesCubic FeetMetersCubic CentimetersCubic MetersLitersFluid OuncesRadiansSteradiansRevolutionsCyclesGravitiesOuncesPoundsFoot-PoundsOunce-InchesGaussGilbertsHenriesFaradsOhmsSiemensMolesBecquerelsPPM (parts/million)DecibelsDbADbCGraysSievertsColor Temperature Degrees KBitsBytesWords (data)DoubleWordsQuadWordsPercentageCIM_NumericSensor.UnitModifierCIM_NumericSensor.RateUnits5UnitModifierThe unit multiplier for the values returned by this Sensor. All the values returned by this Sensor are represented in the units obtained by (BaseUnits * 10 raised to the power of the UnitModifier). For example, if BaseUnits is Volts and the UnitModifier is -6, then the units of the values returned are MicroVolts. However, if the RateUnits property is set to a value other than "None", then the units are further qualified as rate units. In the above example, if RateUnits is set to "Per Second", then the values returned by the Sensor are in MicroVolts/Second. The units apply to all numeric properties of the Sensor, unless explicitly overridden by the Units qualifier.CIM_NumericSensor.BaseUnitsCIM_NumericSensor.RateUnits-3RateUnitsSpecifies if the units returned by this Sensor are rate units. All the values returned by this Sensor are represented in the units obtained by (BaseUnits * 10 raised to the power of the UnitModifier). This is true unless this property (RateUnits) has a value different than "None". For example, if BaseUnits is Volts and the UnitModifier is -6, then the units of the values returned are MicroVolts. But, if the RateUnits property is set to a value other than "None", then the units are further qualified as rate units. In the above example, if RateUnits is set to "Per Second", then the values returned by the Sensor are in MicroVolts/Second. The units apply to all numeric properties of the Sensor, unless explicitly overridden by the Units qualifier. Any implementation of CurrentReading should be qualified with either a Counter or a Gauge qualifier, depending on the characteristics of the sensor being modeled.0123456789NonePer MicroSecondPer MilliSecondPer SecondPer MinutePer HourPer DayPer WeekPer MonthPer YearCIM_NumericSensor.UnitModifierCIM_NumericSensor.BaseUnits0CurrentReadingMIF.DMTF|Voltage Probe|001.5The current value indicated by the Sensor.NominalReadingMIF.DMTF|Voltage Probe|001.6NominalReading indicates the 'normal' or expected value for the NumericSensor.NormalMaxMIF.DMTF|Voltage Probe|001.7NormalMax provides guidance for the user as to the normal maximum range for the NumericSensor.NormalMinMIF.DMTF|Voltage Probe|001.8NormalMin provides guidance for the user as to the normal minimum range for the NumericSensor.MaxReadableMIF.DMTF|Voltage Probe|001.9MaxReadable indicates the largest value of the measured property that can be read by the NumericSensor.MinReadableMIF.DMTF|Voltage Probe|001.10MinReadable indicates the smallest value of the measured property that can be read by the NumericSensor.ResolutionTenths of MilliVoltsMIF.DMTF|Voltage Probe|001.17Resolution indicates the ability of the Sensor to resolve differences in the measured property. This value may vary depending on whether the Device is linear over its dynamic range.ToleranceMIF.DMTF|Voltage Probe|001.18Indicates the tolerance of the Sensor for the measured property. Tolerance, along with Resolution and Accuracy, is used to calculate the actual value of the measured physical property. Tolerance may vary depending on whether the Device is linear over its dynamic range.AccuracyMIF.DMTF|Voltage Probe|001.19Indicates the accuracy of the Sensor for the measured property. Its value is recorded as plus/minus hundredths of a percent. Accuracy, along with Resolution and Tolerance, is used to calculate the actual value of the measured physical property. Accuracy may vary depending on whether the Device is linear over its dynamic range.Hundredths of PercentLowerThresholdNonCriticalMIF.DMTF|Voltage Probe|001.11The Sensor's threshold values specify the ranges (min and max values) for determining whether the Sensor is operating under Normal, NonCritical, Critical or Fatal conditions. If CurrentReading is between LowerThresholdNonCritical and UpperThresholdNonCritical, then the Sensor is reporting a normal value. If CurrentReading is between LowerThresholdNonCritical and LowerThresholdCritical, then the CurrentState is NonCritical.UpperThresholdNonCriticalMIF.DMTF|Voltage Probe|001.12The Sensor's threshold values specify the ranges (min and max values) for determining whether the Sensor is operating under Normal, NonCritical, Critical or Fatal conditions. If the CurrentReading is between LowerThresholdNonCritical and UpperThresholdNonCritical, then the Sensor is reporting a normal value. If the CurrentReading is between UpperThresholdNonCritical and UpperThresholdCritical, then the CurrentState is NonCritical.LowerThresholdCriticalMIF.DMTF|Voltage Probe|001.13The Sensor's threshold values specify the ranges (min and max values) for determining whether the Sensor is operating under Normal, NonCritical, Critical or Fatal conditions. If the CurrentReading is between LowerThresholdCritical and LowerThresholdFatal, then the CurrentState is Critical.UpperThresholdCriticalMIF.DMTF|Voltage Probe|001.14The Sensor's threshold values specify the ranges (min and max values) for determining whether the Sensor is operating under Normal, NonCritical, Critical or Fatal conditions. If the CurrentReading is between UpperThresholdCritical and UpperThresholdFatal, then the CurrentState is Critical.LowerThresholdFatalMIF.DMTF|Voltage Probe|001.15The Sensor's threshold values specify the ranges (min and max values) for determining whether the Sensor is operating under Normal, NonCritical, Critical or Fatal conditions. If the CurrentReading is below LowerThresholdFatal, then the CurrentState is Fatal.UpperThresholdFatalMIF.DMTF|Voltage Probe|001.16The Sensor's threshold values specify the ranges (min and max values) for determining whether the Sensor is operating under Normal, NonCritical, Critical or Fatal conditions. If the CurrentReading is above UpperThresholdFatal, then the CurrentState is Fatal. 2.6.0This class exists for backward compatibility to earlier CIM Schema definitions. With additions to Sensor and NumericSensor in V2.2, it is no longer necessary. A Tachometer can be defined by setting the SensorType property. inherited from Sensor, to 5 ("Tachometer"). Other properties of this class are hard-coded to constant values to correspond to definitions in the Sensor hierarchy.SensorTypeThe Type of the Sensor, e.g. Voltage or Temperature Sensor. If the type is set to "Other", then the OtherSensorTypeDescription can be used to further identify the type, or if the Sensor has numeric readings, then the type of the Sensor can be implicitly determined by the Units. A description of the different Sensor types is as follows: A Temperature Sensor measures the environmental temperature. Voltage and Current Sensors measure electrical voltage and current readings. A Tachometer measures speed/revolutions of a Device. For example, a Fan Device can have an associated Tachometer which measures its speed. A Counter is a general purpose Sensor that measures some numerical property of a Device. A Counter value can be cleared, but it never decreases. A Switch Sensor has states like Open/Close, On/Off, or Up/Down. A Lock has states of Locked/Unlocked. Humidity, Smoke Detection and Air Flow Sensors measure the equivalent environmental characteristics. A Presence Sensor detects the presence of a PhysicalElement.0123456789101112UnknownOtherTemperatureVoltageCurrentTachometerCounterSwitchLockHumiditySmoke DetectionPresenceAir FlowCIM_Sensor.OtherSensorTypeDescription5BaseUnitsThe base unit of the values returned by this Sensor. All the values returned by this Sensor are represented in the units obtained by (BaseUnits * 10 raised to the power of the UnitModifier). For example, if BaseUnits is Volts and the UnitModifier is -6, then the units of the values returned are MicroVolts. However, if the RateUnits property is set to a value other than "None", then the units are further qualified as rate units. In the above example, if RateUnits is set to "Per Second", then the values returned by the Sensor are in MicroVolts/Second. The units apply to all numeric properties of the Sensor, unless explicitly overridden by the Units qualifier.01234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465UnknownOtherDegrees CDegrees FDegrees KVoltsAmpsWattsJoulesCoulombsVANitsLumensLuxCandelaskPaPSINewtonsCFMRPMHertzSecondsMinutesHoursDaysWeeksMilsInchesFeetCubic InchesCubic FeetMetersCubic CentimetersCubic MetersLitersFluid OuncesRadiansSteradiansRevolutionsCyclesGravitiesOuncesPoundsFoot-PoundsOunce-InchesGaussGilbertsHenriesFaradsOhmsSiemensMolesBecquerelsPPM (parts/million)DecibelsDbADbCGraysSievertsColor Temperature Degrees KBitsBytesWords (data)DoubleWordsQuadWordsPercentageCIM_NumericSensor.UnitModifierCIM_NumericSensor.RateUnits38UnitModifierThe unit multiplier for the values returned by this Sensor. All the values returned by this Sensor are represented in the units obtained by (BaseUnits * 10 raised to the power of the UnitModifier). For example, if BaseUnits is Volts and the UnitModifier is -6, then the units of the values returned are MicroVolts. However, if the RateUnits property is set to a value other than "None", then the units are further qualified as rate units. In the above example, if RateUnits is set to "Per Second", then the values returned by the Sensor are in MicroVolts/Second. The units apply to all numeric properties of the Sensor, unless explicitly overridden by the Units qualifier.CIM_NumericSensor.BaseUnitsCIM_NumericSensor.RateUnits1RateUnitsSpecifies if the units returned by this Sensor are rate units. All the values returned by this Sensor are represented in the units obtained by (BaseUnits * 10 raised to the power of the UnitModifier). This is true unless this property (RateUnits) has a value different than "None". For example, if BaseUnits is Volts and the UnitModifier is -6, then the units of the values returned are MicroVolts. But, if the RateUnits property is set to a value other than "None", then the units are further qualified as rate units. In the above example, if RateUnits is set to "Per Second", then the values returned by the Sensor are in MicroVolts/Second. The units apply to all numeric properties of the Sensor, unless explicitly overridden by the Units qualifier. Any implementation of CurrentReading should be qualified with either a Counter or a Gauge qualifier, depending on the characteristics of the sensor being modeled.0123456789NonePer MicroSecondPer MilliSecondPer SecondPer MinutePer HourPer DayPer WeekPer MonthPer YearCIM_NumericSensor.UnitModifierCIM_NumericSensor.BaseUnits4ResolutionTenths of Revolutions per MinuteResolution indicates the ability of the Sensor to resolve differences in the measured property. This value may vary depending on whether the Device is linear over its dynamic range. 2.6.0A PowerSupply may have an associated VoltageSensor, monitoring its input voltage. This is described by this association.trueThe VoltageSensor.AntecedenttrueThe PowerSupply associated with the VoltageSensor.DependenttrueIndicates the PowerSupply's input voltage range measured by the associated sensor. Range 1, 2 or both can be specified using the values 2, 3 or 4, respectively.01234UnknownOtherRange 1Range 2Both Range 1 and 2 2.6.0A PowerSupply may have an associated CurrentSensor, monitoring its input frequency. This is described by this association.trueThe CurrentSensor.AntecedenttrueThe PowerSupply associated with the CurrentSensor.DependenttrueIndicates the PowerSupply's input frequency range measured by the associated sensor. Range 1, 2 or both can be specified using the values 2, 3 or 4, respectively.01234UnknownOtherRange 1Range 2Both Range 1 and 2 2.7.0CIM_PackageDependencyOften, a TemperatureSensor is installed in a Package such as a Chassis or a Rack, not to measure any particular Device, but the Package's environment in general. The use of this association has been deprecated. Instead, use PackageDependency to describe this relationship.trueCIM_PackageDependency.AntecedentThe TemperatureSensor for the Package.AntecedenttrueCIM_PackageDependency.DependentThe PhysicalPackage whose environment is monitored.Dependenttrue 2.6.0An AlarmDevice is a type of Device that emits audible or visible indications related to a problem situation.Boolean indicating that the Alarm is audible.Boolean indicating that the Alarm is visible.Boolean indicating that the Alarm causes motion of the Device.Urgency is an enumerated value that indicates the relative frequency at which the Alarm flashes, vibrates and/or emits audible tones.0123456UnknownOtherNot SupportedInformationalNon-CriticalCriticalUnrecoverableThe current state of the alarm.0123UnknownOffSteadyAlternatingTrue indicates that the audio of an AlarmState indicator has been disabled (i.e. muted). A disabled state here does not imply that the AlarmState is off.True indicates that the visual of an AlarmState indicator has been disabled (i.e. dimmed). A disabled state here does not imply that the AlarmState is off.True indicates that the motion of an AlarmState indicator has been disabled (i.e. stopped). A disabled state here does not imply that the AlarmState is off.SetAlarmState is a method for defining the current state of the Alarm. Its input parameter, RequestedAlarmState, is specified using the Values list of AlarmDevice's AlarmState property. SetAlarmState returns 0 if the request is successfully implemented, 1 if the specified RequestedAlarmState is not supported, and some other value if any other error occurred. In a subclass, the set of possible return codes should be specified using a ValueMap qualifier on the method. The strings to which the ValueMap contents are 'translated' should be specified as a Values array qualifier.true0123UnknownOffSteadyAlternatingSetAlarmIndicator is a method for enabling or disabling the indicator of the AlarmState function, without changing the current AlarmState. It has 3 input parameters, AudioIndicator, VisualIndicator and MotionIndicator. For all of the input parameters, a value of 0 indicates no change to the AlarmState indicator, 1 indicates Disable, and 2 indicates Enable. The method returns 0 if the request is successfully implemented, 1 if the specified request is not supported, and some other value if any other error occurred. In a subclass, the set of possible return codes should be specified using a ValueMap qualifier on the method. The strings to which the ValueMap contents are 'translated' should be specified as a Values array qualifier.true012No ChangeDisableEnabletrue012No ChangeDisableEnabletrue012No ChangeDisableEnableSetUrgency is a method for defining the desired urgency level for the Alarm. Its input parameter, RequestedUrgency, is specified using the Values list of AlarmDevice's Urgency property. SetUrgency returns 0 if the request is successfully implemented, 1 if the specified Urgency level is not supported, and some other value if any other error occurred. In a subclass, the set of possible return codes should be specified using a ValueMap qualifier on the method. The strings to which the ValueMap contents are 'translated' should be specified as a Values array qualifier.true13456OtherInformationalNon-CriticalCriticalUnrecoverable 2.6.0LogicalDevices may have one or more AlarmDevices associated with them, in order to indicate problem situations. This relationship is indicated by the AssociatedAlarm dependency.trueAntecedentThe AlarmDevice.trueDependentThe LogicalDevice that is alarmed.true 2.7.0CIM_PackageDependencyOften, an AlarmDevice is installed as part of a Package, not to indicate issues with any particular LogicalDevice or PhysicalComponent, but with the Package's environment in general, its security state or its overall health. The use of this association has been deprecated. Instead, use PackageDependency to describe this relationship.trueCIM_PackageDependency.AntecedentThe AlarmDevice for the Package.AntecedenttrueCIM_PackageDependency.DependentThe PhysicalPackage whose health, security, environment, etc. is alarmed.Dependenttrue 2.6.0The management characterisitics of a USB Device.Indicates the latest USB Version supported by the USB Device. The property is expressed as a Binary-Coded Decimal (BCD) where a decimal point is implied between the 2nd and 3rd digits. For example, a value of 0x201 indicates that version 2.01 is supported.Indicates the USB class code.Indicates the USB subclass code.Indicates the USB protocol code.Number of device configurations that are defined for the Device.Indicates the configuration currently selected for the Device. If this value is zero, the Device is unconfigured.CIM_USBDevice.CurrentAlternateSettingsAn array of USB 'alternate settings' for each interface in the currently selected configuration (indicated by the CurrentConfigValue property). This array has one entry for each interface in the configuration. If the property, CurrentConfigValue, is zero (indicating the Device is not configured), the array is undefined. To understand how to parse this octet string, refer to the USB Specification.CIM_USBDevice.CurrentConfigValueThis method returns the USBDevice Descriptor as specified by the input parameters. Each parameter is briefly described here with more detail in its Qualifier list. RequestType is an input parameter that defines whether the request is for standard, class or vendor-specific information, as well as specifying the recipient. RequestValue is also an input parameter and defines the USB Descriptor Type and Index. RequestIndex is an input parameter which describes the language used to return a string Descriptor. RequestLength is both an input and output parameter. It specifies the length of the Descriptor that should be returned (on input) and what is actually returned in the Buffer parameter (on output). Buffer is an output parameter, containing the Descriptor data. The GetDescriptor method returns an integer value of 0 if the USB Descriptor is successfully returned, 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.trueRequestType is bit-mapped and identifies the type of Descriptor request and the recipient. The type of request may be 'standard', 'class' or 'vendor-specific'. The recipient may be 'device', 'interface', 'endpoint' or 'other'. Refer to the USB Specification for the appropriate values for each bit.trueRequestValue contains the Descriptor Type in the high byte and the Descriptor Index (for example, index or offset into the Descriptor array) in the low byte. Refer to the USB Specification for more information.trueRequestIndex defines the 2 byte Language ID code used by the USBDevice when returning string Descriptor data. The parameter is typically 0 for non-string Descriptors. Refer to the USB Specification for more information.truetrueOn input, RequestLength is the length (in octets) of the Descriptor that should be returned. If this value is less than the actual length of the Descriptor, only the requested length will be returned. If it is more than the actual length, the actual length is returned. On output, this parameter is the length, in octets, of the Buffer being returned. If the requested Descriptor does not exist, the contents of this parameter are undefined.falsetrueBuffer returns the requested Descriptor information. If the Descriptor does not exist, the contents of the Buffer are undefined. 2.6.0USB Hub Device.Indicates whether power to the Hub Ports is individually or gang-switched. If this value is FALSE, power is switched individually for each Port. If this value is TRUE, power is switched to all Ports on the Hub at once.Number of downstream Ports on the Hub, including those embedded in the Hub's silicon. Individual USBPorts are associated with the Hub using the USBPortOnHub association. 2.6.0A Port on a USBHub.SpeedUSB Port Speed in bits per second. This speed is determined and set by the attached Device. The 'attached Device' is indicated using the USBConnection association. At this time, only several Port speeds are valid. These are: 1.5Mbps and 12Mbps. The value 0 can also be specified to indicate that the current speed is 'unknown' or 1 to indicate that the speed is 'other' than 1.5 or 12Mbps.01150000012000000Bits per SecondStatusInfoIndicates whether the Port is currently enabled.234UnknownEnabledDisabledMIF.DMTF|Operational State|006.4AvailabilityIndicates whether the Port is currently Powered.237UnknownRunning/Full PowerPower OffMIF.DMTF|Operational State|006.5MIB.IETF|HOST-RESOURCES-MIB.hrDeviceStatusMIF.DMTF|Host Device|001.5CIM_LogicalDevice.AdditionalAvailabilityThe USB Port's power capability. The current specification defines that 1 or 5 loads can be supported (values 2 or 3 would be specified, respectively).0123UnknownOther1 Unit Load5 Unit LoadsIndicates whether the Port is currently Suspended.Indicates whether the Port is disabled due to an overcurrent event. 2.6.0USBPortOnHub associates a USBPort or connection point with the USBHub that includes it.true11The Hub that includes the USBPort.Antecedenttrue1The Port on the USBHub.Dependenttrue 2.6.0USBControllerHasHub defines the Hub(s) that are downstream of the USBController.true11The USBController.Antecedenttrue1The USBHub that is associated with the Controller.Dependenttrue 2.6.0USBConnection associates a Device with the USBPort to which it is connected.true1The USBPort.Antecedenttrue1The USBDevice that is connected to the Port.Dependenttrue 2.6.0A DiskGroup is a named collection of DiskDrives and the StorageExtent(s) accessed via those Drives. The collection is used to limit the BasedOn relationships of the Extents in the DiskGroup. Extents in the Group can NOT be BasedOn storage accessed from Drives outside of the Group. For example, a SoftwareVolume created 'within the DiskGroup' is restricted to be completely accessed using Drives in the Group. Actions such as 'replicate' or 'migrate' on an Extent must operate within the scope of the Extents present in the DiskGroup.CollectionIDtrue256The identification of the Collection object. When subclassed, the CollectionID property can be overridden to be a Key property. 2.6.0CIM_DriveInDiskGroup defines the DiskDrive(s) that participate in the Group.truetrue1The DiskGroup. A Drive is a member of at most one DiskGroup.CollectiontruetrueThe DiskDrive in the Group.Membertrue 2.6.0CIM_ExtentInDiskGroup defines the StorageExtent(s) that are located within and restricted by the Group.truetrue1The DiskGroup. An Extent is defined within at most one DiskGroup.CollectiontruetrueThe StorageExtent restricted by and participating in the Group.Membertrue 2.6.0CIM_GroupInDiskGroup describes that a DiskGroup may be divided into smaller named Collections.truetrueCollection1The DiskGroup that is subsetted into smaller Collections.truetrueCollectionInCollectionThe DiskGroup that is a subset of the larger Group.true true2.6.0PRS_ExchangeElement is an abstract base class for all classes in the Solution and Service Incident object model. As an abstract class it is never instantiated. PRS_ExchangeElement exists to provide a single anchor point for associations that may be made to any Solution or Service Incident object. For example, Administrative or Attachment instances may be associated with any object derived from PRS_ExchangeElement. To support this generic association capability, the PRS_AdminAssociation and PRS_Attached associations both derive from the CIM_Dependency association and override the Antecedent property of that class to be a PRS_ExchangeElement REF.trueThe PRSUniqueName property is a Globally Unique IDentifier (GUID) also known as a Universally Unique IDentifier (UUID). This property allows Solution and Service Incident objects to be used by multiple Solutions or Service Incidents without duplication. In addition, all Solution or Service Incidents containing a unique object are updated when the object is updated.0123CleanNewModifiedDeletedThe DirtyFlag is used by the SISService Start Transaction method to determine whether an ExchangeElement has been created, modified or deleted since the last Transaction. Any object not marked 'Clean' is included in the next Transaction. It is the responsibility of the entity creating, modifying or deleting the object derived from ExchangeElement to set this property appropriately. This property value is set to 'Clean' by an invocation of the Transaction Complete method with a Status parameter of zero (0). 2.6.0PRS_Solution is the root class of a set of associated classes used to describe a single Solution. If a Solution is associated with multiple Problems or Resolutions, all of the Problems described are related to all of the Resolutions described. The reverse is also true. All of the Resolutions described are related to all of the Problems described in the Solution. PRS_Solution is directly associated to one or more of the following classes: PRS_Reference PRS_Problem PRS_ResolutionThe Solution title.A brief description of the Solution.012254255ReferenceDiagnosticHow ToOtherUnknownThe SolutionType suggests the type of knowledge contained in the Solution. Depending on the type, the Solution may or may not include particular objects. For example, a 'Reference' Solution describes non-diagnostic technical or general information using PRS_Statement objects. A 'Diagnostic' Solution includes one or more PRS_Problem and PRS_Resolution objects. A 'How To' Solution describes how to solve a particular Problem described by a PRS_Problem in a series of sequential steps within a PRS_Resolution. true2.6.0PRS_SolutionElement is an abstract base class for non-Category objects that are associated with a Solution. This includes: PRS_Reference PRS_Problem PRS_Resolution PRS_SolutionElement provides a common reference for these objects to be associated with PRS_Expression objects through the SolutionExpression association. In addition, all of the derived objects may be retrieved with a single query for the common super-class. 2.6.0PRS_Reference is a placeholder to support links between PRS_Expression objects and a PRS_Solution. It does not have any properties. A 'Reference' Solution uses PRS_Statement objects to describe general, non-diagnostic knowledge and may not include any PRS_Problem and PRS_Resolution instances. 2.6.0PRS_Problem is the root object of a set of associated objects that describe a Problem. One or more Problems may be associated with a Solution. The Problem is described by PRS_Statement and PRS_Product instances indirectly associated to the PRS_Problem through a PRS_Expression.The Likelihood describes the potential for the Problem to occur. The value of this property shall be an integer value in the range of 0 to 100, inclusive.0100The Impact describes the severity of the problem. The value of this property shall be an integer value in the range of 0 to 100, inclusive.0100 2.6.0PRS_Resolution is the root object of a set of associated objects that describe a the resolution to a Problem. One or more Resolutions may be associated with a Solution. The Resolution is described by PRS_Statement and PRS_Product instances indirectly associated to the PRS_Resolution through a PRS_Expression.The Confidence describes the potential for the Resolution to correct the Problem or Problems associated with the PRS_Solution. The value of this property shall be an integer value in the range of 0 to 100, inclusive.0100 truetrue2.6.0PRS_SolutionHasElement is an abstract base class for associating PRS_Solution with objects derived from PRS_SolutionElement. This association class allows all PRS_Reference, PRS_Problem and PRS_Resolution objects to be retrieved with a single query.trueAntecedenttrue1The PRS_Solution root object of the Solution.trueDependentThe PRS_Reference, PRS_Problem or PRS_Resolution aggregated into the Solution by this association.true 2.6.0PRS_SolutionReference aggregates a Reference into a Solution.truetrue1The PRS_Solution root object of the Solution.AntecedenttruetrueThe PRS_Reference aggregated into the Solution.Dependenttrue 2.6.0PRS_SolutionProblem aggregates a Problem into a Solution.truetrue1The PRS_Solution root object of the Solution.AntecedenttruetrueThe PRS_Problem aggregated into the Solution.Dependenttrue 2.6.0PRS_SolutionResolution aggregates a Resolution into a Solution.truetrue1The PRS_Solution root object of the Solution.AntecedenttruetrueThe PRS_Solution aggregated into the Solution.Dependenttrue 2.6.0PRS_Category is used to classify the components of a Solution. Hierarchical classifications are created by associating PRS_CategoryParentChild with multiple PRS_Category instances.The specific value for the category. For example, 'HP Laserjet' would be a value for a category containing printer names.The type of category. Used to give additional semantics to the category. For example, a Category of Type 'Printers' would qualify the list of category values for a list of printers. Note: the relationship of Category Type to Category Value expresses no intrinsic hierarchy. If a tree of relationships exists to define categories and sub-categories, this should be defined using CategoryParentChild associations. 2.6.0PRS_SolutionCategory associates PRS_Solution with a PRS_Category for classification purposes.trueAntecedent1The PRS_Solution being classified.trueDependentThe specific PRS_Category being used to classify the Solution.true 2.6.0PRS_Categorization associates PRS_Reference, PRS_Problem or PRS_Resolution with a PRS_Category for classification purposes. For example, a Category named 'Printing Issues' can be defined for a Problem using the Categorization association between a PRS_Problem and a PRS_Category.trueAntecedentThe PRS_Category used for classification.trueDependent1The specific PRS_Reference, PRS_Problem or PRS_Resolution classified by this association.true 2.6.0PRS_CategoryParentChild is used to define classification hierarchies.trueAntecedentThe parent PRS_Category used for classification.trueDependentThe child PRS_Category used for classification.true true2.6.0PRS_ExpressionElement is an abstract base class for PRS_Products and PRS_Statements. It provides a common association point for objects associated with PRS_Expressions. 2.6.0PRS_Expression defines a specific relationship between PRS_ExpressionElements associated with PRS_SolutionElements.The operator to be used with the associated PRS_ExpressionElements. The 'AND', 'OR' and 'NOT' operators are the only operators currently defined by the standard. (They must be used as uppercase strings.) Note that this is a vendor-extensible property - so that additional operators can be defined and used in implementations. 2.6.0PRS_Product is used to describe a single product to associate with a PRS_Expression.The vendor of the product.The make and or model of the product.The version of the product.The order of relevance of this product to an associated PRS_SolutionElement (which includes PRS_Reference, PRS_Problem or PRS_Resolution). 2.6.0PRS_Statement contains the text describing a problem, any relevant background information, and its resolution. Statements are units of text ranging from brief sentences or phrases to paragraphs or pages. There is no limit to the number of PRS_Statements within a Solution, as long as they support the intent and focus of their root class. Root classes include: PRS_Reference, PRS_Problem or PRS_Resolution. PRS_Statements may be grouped together to build compound 'sentences'. For example, StatementA = Printer output is blotchy. StatementB = Print jobs per day are less than 50. ExpressionA = StatementA AND StatementB.01234567891011254255DescriptionSymptomError_MessageObjectiveEvidenceCauseWork_AroundFixAnswerKeywordChangesTitleOtherUnknownStatementRole describes how the PRS_Statement relates to the larger context. For example, is the PRS_Statement describing a Fix or a Symptom? 'Description' is generic text without a specific diagnostic application. 'Symptom' describes initial observable incident or behavior that the user reports. 'Error_Message' is a specific type of symptom that the user reports, describing the specific error condition. 'Objective' is what the user wants to accomplish, often expressed as a positive condition. FOr example, how to print on a network. 'Evidence' is information that is collected to diagnose the problem after the symptom is reported. 'Cause' is a description of the underlying facts or factors that engender or relate this behavior. 'Work_around' is information that lets the user work, but does not correct the problem completely. 'Fix' is information that fixes the problem completely. 'Answer' is the information given to the user such as steps to perform, wording to support their environment and understanding. 'Keyword' is a specific classification using defined words or phrases. 'Changes' describe recent changes in the environment which could affect the problem or resolution. 'Title is the title applying to associated PRS_Statements (usually associated via an 'and' expression.The descriptive text used for the PRS_Statement.When the PRS_Adminstrative object indicates Level 2 compliance, StatementOperator describes the relationship between an associated PRS_Feature and the FeatureValue property. This property is ignored if there is no PRS_Feature associated with this PRS_Statement.When the PRS_Adminstrative object indicates Level 2 compliance, FeatureValue is the specific value selected from the associated PRS_Feature. This property is ignored if there is no PRS_Feature associated with this PRS_Statement.Order is used to sequence PRS_Statements associated with a single PRS_Expression to allow a Consumer to process the information in the order desired by the Producer.Importance of this Statement. The value of this property shall be an integer value in the range of 0 to 100, inclusive.0100 2.6.0PRS_Feature is used for structured diagnostic data, including specific data values like steps or conditions. For example, consider a PRS_Statement with a Text property value of: Print jobs per day are less than 50 This could be described using a PRS_Feature as follows: Description: 'Print jobs per day' Prompt: 'How many print jobs per day?' ValidValues: '10' '50' '100' DataType: 'Integer' The associated PRS_Statement would contain: Operator: '<' FeatureValue: '50' Prompt presented through user interface.Valid values for this PRS_Feature.012345254255StringIntegerFloatDate/TimeBooleanBinaryOtherUnknownData type used for PRS_Statement FeatureValue property. 2.6.0Each PRS_Resolution may have an associated cost of implementation. This cost may have several components such as time, material costs, labor cost, etc. To capture these costs, a PRS_Resouce is associated with a PRS_Resolution. For Service Incidents, one or more PRS_Resource objects may be associated with an Activity.A string describing the type of resource.Number of units of resource used.Unit of measure for this resource. true2.6.0Associates a PRS_Expression with PRS_ExpressionElements such as PRS_Expression, PRS_Product, and PRS_Statement.truetrueAntecedent1The parent PRS_Expression.trueDependent1The child PRS_ExpressionElement, either a PRS_Expression, PRS_Product or PRS_Statement.true true2.6.0Products may exist in a hierarchy of relationships with related Products. If a Producer deems these hierarchy relationships are relevant to the current Problem or Resolution, then the position of the Product in a hierarchy can be implied using one of two types of relationships: 'is a' and 'has a'. An 'is a' relationship implies a classification, such as versioning or typing. A 'has a' relationship implies that one product contains another. The PRS_ProductParentChild association is used to imply an 'is a' hierarchy. Use the ProductComponent association to imply 'has a' relationships.truetrueAntecedentThe parent PRS_Product.trueDependentThe child PRS_Product.true true2.6.0PRS_ProductComponent is used to describe 'has a' relationships between Products and their components parts. See PRS_ProductParentChild for 'is a' relationships.truetrueAntecedentThe PRS_Product which contains the component.trueDependentThe component PRS_Product.true 2.6.0PRS_ProductAsset is used to provide specific information about a PRS_Product. PRS_ProductAsset associates this information to a PRS_Product using one or more Statements associated to a PRS_Expression.trueAntecedentThe product.trueDependentThe expression.true 2.6.0Associates PRS_Statement with PRS_Feature.trueAntecedentThe PRS_Statement.trueDependentThe PRS_Feature.true 2.6.0Associates PRS_Feature with PRS_Resource. This is used to track labor and costs associated with specific tasks defined in a Feature object.trueAntecedentThe PRS_Feature.trueDependentThe PRS_Resource.true 2.6.0Associates PRS_Resolution with PRS_Resource.trueAntecedentThe PRS_Resource.trueDependentThe PRS_Resolution.true true2.6.0Associates PRS_SolutionElements (PRS_Reference, PRS_Problem or PRS_Resolution) with PRS_Expressions.truetrueAntecedent1The PRS_SolutionElement.trueDependent1The PRS_Expression.true 2.6.0PRS_Administrative defines administrative information about associated objects. There must be at least one PRS_Administrative instance associated with a PRS_Solution. Administrative information is inherited from a parent object. If the administrative information among objects within a Solution is not the same, additional PRS_Administrative instances may be associated with other objects within the Solution. All instances under a specific parent inherit their administrative information unless there is an PRS_Administrative instance associated with that instance. For example, if there is a PRS_Administrative instance associated with a PRS_Problem instance, all of the PRS_Statement and PRS_Product instances within the Problem use the same Administrative information as the PRS_Problem instance.012Level 0 means all information within a Reference, Problem or Resolution is conveyed by a single PRS_Statement. Level 1 means there may be multiple PRS_Statement instances within a Reference, Problem or Resolution. Level 2 means that a PRS_Statement may be associated with a PRS_Feature instance within a Reference, Problem or Resolution.012254255DraftReviewedPublishedOtherUnknownEditorial status of the document. If 'Draft', information is complete, but unedited. If 'Reviewed', an editorial review has been completed. If 'Published', information has been reviewed and approved for distribution.0123254255ProprietaryInternalPartnerPublicOtherUnknownIntended distribution audience for the associated information. If 'Proprietary', information contains proprietary information and is not to be released externally. If 'Internal', information is for internal use only. If 'Partner', information is only available to contracted partners. If 'Public', information is available to anyone.Language used in the associated information.Copyright for the associated information.Disclaimers about the associated information.Usage rights for the associated information. 2.6.0Associates PRS_Administrative data with any object derived from PRS_ExchangeElement.trueAntecedent1The PRS_ExchangeElement.trueDependentThe PRS_Administrative object.true 2.6.0PRS_Revision records changes to the content.The date of this revision.012254255CreateUpdateDeleteOtherUnknownThe name of the specific revision being made.012254255TechnicalEditorialAdministrativeOtherUnknownType of revision activity. 'Technical' refers to a change in content. 'Editorial' refers to a change in language or style. 'Administrative' refers to information about the object.0123254255OpenNot ReviewedReviewedApprovedOtherUnknownThe current state of technical review. 'Open' means created but not necessarily completed or resolved. 'Not Reviewed' means contents have to be reviewed for accuracy and consistency with other content. 'Reviewed' means review has been completed. 'Approved' means formally approval to certify the solution given the specific status of the contents.0123254255In_ProgressDraftReviewedPublishedOtherUnknownThe current state of editorial review. 'In Progress' means the content is in the process of being developed. 'Draft' means the content is complete but unedited. 'Reviewed' means the review has been completed. 'Published' means the contents have been released.DescriptionText description of what was done in this revision. true2.6.0Associates PRS_Administrative with PRS_Revision.truetrueAntecedent11The PRS_Administrative.trueDependentThe PRS_Revision.true 2.6.0PRS_Contact is used to anchor associations to PRS_Person and PRS_Orgnaization. PRS_Contact is also used to anchor associations to PRS_Revision and PRS_Resolution, as well as PRS_ServiceIncident. true2.6.0PRS_ContactItem is the abstract root class for PRS_Person and PRS_Organization. It provides a common anchor point for the PRS_ContactContactItem association. true2.6.0Associates PRS_Administrative and PRS_Contact.truetrueAntecedent1The PRS_Administrative instance.trueDependent1The PRS_Contact.true true2.6.0Associates PRS_Revision and PRS_Contact.truetrueAntecedentThe PRS_Revision.trueDependent1The PRS_Contact.true 2.6.0PRS_Organization describes a PRS_Contact's organization name and business.The name of the organization.Description of organization's primary business. 2.6.0Information about a personal contact.Contact's first name.Contact's last name.How the contact is addressed, i.e. Dr., Mr., Ms., Mrs., etc.Contact's business title.Description of the contact. For example, they may have responsibilities not apparent from their title.01234254255Primary_VoiceAlternate_VoiceFaxEmailURLOtherUnknownContact's preferred communication method. See the PRS_Location.LocationType property. true2.6.0Abstract root class to associate PRS_Person or PRS_Organization and PRS_Contact.trueAntecedent1The PRS_Contact.trueDependent1The PRS_ContactItem, either PRS_Person or PRS_Organization. There is always at least one PRS_ContactItem, however it may be either a PRS_Person or PRS_Organization. For that reason, there is a minimum cardinality of one for this property, but a minimum cardinality of zero in the classes derived from this class.true 2.6.0Associates PRS_Contact and PRS_Organization.true1The PRS_Contact.Antecedenttrue1The PRS_Organization.Dependenttrue 2.6.0Associates PRS_Contact and PRS_Person.true1The PRS_Contact.Antecedenttrue1The PRS_Person.Dependenttrue 2.6.0Provides address information for PRS_ContactItem.0123254255PrimaryShippingBillingServiceOtherUnknownThe type of address.First line of address information.Second line of address information.Third line of address information.Fourth line of address information.The city.The specific region, such as state or province.The country's postal code for the address.The time zone of the address.The country code, based on ISO/IEC 3166. 2.6.0Associates PRS_ContactItem with PRS_Address.trueAntecedent1The PRS_ContactItem.trueDependentThe PRS_Address.true 2.6.0PRS_Location describes the location of a PRS_Address.01234254255Primary_VoiceAlternate_VoiceFaxEmailURLOtherUnknownThe type of location.The specific location. 2.6.0Associates PRS_Address and PRS_Location.trueAntecedent1The PRS_Address.trueDependentThe PRS_Location.true 2.6.0PRS_Attachment describes file attachments. A PRS_Attachment may be associated to any object derived from PRS_ExchangeElement. PRS_Attachment is used to attach objects of any type including binary files, ASCII documents, or URLs. Only one object may be attached per PRS_Attachment. The actual attachment carried by the Attachment object is included by one of two methods: by reference or by value as embedded data. A 'by reference' approach links indirectly to the attachment through the use of a string identifier, e.g. a file name. An 'embedded data' approach means the actual binary data is included in PRS_Attachment.If the attachment is not embedded, where the attachment is located.Protocol required to read the attachment (e.g., http).The file format of the attachment.The size of the attachment in bytes.The attachment itself, if embedded.012254255InstructionsBackgroundLogUnknownUndefinedThe purpose of the attachment, as related to the diagnosis. 'Instructions' are compilable code. 'Background' is descriptive information. 'Log' is information captured in a log file.The displayable attachment identifier. Used to define what will appear as the name of the attachment, as opposed to the specific attachment file name or URL. 2.6.0Associates PRS_Attachment with PRS_ExchangeElement.trueAntecedentThe PRS_Attachment.trueDependent1The PRS_ExchangeElement.true 2.6.0PRS_ServiceIncident contains the fundamental information related to a specific incident: its identity, status, priority, etc. The actual incident data, including specific transactions and resolution information, is contained in the objects associated with PRS_ServiceIncident. These include specific Problem, Resolution and Activity related objects accrued through the Transaction workflow.The unique identifier for this incident assigned by the Requester.The unique identifier for this incident assigned by the Provider.01234567254255Beginning_StateNot_EntitledEntitledProblem_SubmittedOpen_RequesterOpen_ProviderClosed_Pending_ConfirmationClosedOtherUnknownThe state of the incident within the Service Incident Exchange Standard transaction model.12345The severity of the incident as defined by the Requester. One is the most severe and five is the least severe.12345The priority of the incident as defined by the Requester. One is the highest priority and five is the lowest priority.The explicit time the Requester expects a response.Status of the incident according to the workflow.Additional general information about the incident.01254255YesNoOtherUnknownIs the Requester entitled to service or not?01254255YesNoOtherUnknownWas the last transaction was accepted or rejected?PRS_ServiceIncident.LastTransactionThe use of the TransactionName property is deprecated. New Service Incidents should use the LastTransaction property and set this property to NULL.01234567891011254255Service_RequestEntitlementProblem_SubmittalAccept_ProblemProblem_ResolutionRequest_Problem_InformationProvide_Problem_InformationProvide_Admin_InformationQuery_IncidentConfirm_CloseReject_ResolutionRequest_ClosureOtherUnknownThe name of the last transaction which was acknowledged. 2.6.0PRS_ServiceRequester associates a PRS_ServiceIncident with a PRS_Contact representing the entity requesting service. Note that the Contact class is used for both Requesters and Providers, the context is determined by which association exists.trueAntecedentThe PRS_ServiceIncident.trueDependent11The PRS_Contact.true 2.6.0Associates PRS_ServiceIncident to PRS_Contact to describe the Service Provider.trueAntecedentThe PRS_ServiceIncident.trueDependent11The PRS_Contact.true 2.6.0Associates PRS_ServiceIncident to PRS_Problem to describe the Problem being submitted to the Service Provider.trueAntecedent1The PRS_ServiceIncident.trueDependent1The PRS_Problem.true true2.6.0Associates PRS_ServiceIncident to PRS_Solution to describe the Resolutions proposed by the Service Provider.trueAntecedenttrueThe PRS_ServiceIncident.trueDependentThe PRS_Solution. PRS_Solution must be associated with at least one Resolution.true 2.6.0The agreement or contract referenced for entitlement to service.The identifier for the contract between the Request and the Provider. This property is set by the Requester prior to submitting a Service Request.A brief description of the contract. 2.6.0Associates PRS_ServiceIncident to PRS_Agreement.trueAntecedentThe PRS_ServiceIncident.trueDependent11The PRS_Agreement.true 2.6.0Describes the date of each transaction and the objects involved.PRS_Activity.NewKeysPRS_Activity.DeletedPRS_Activity.ModifiedThe key fields for the objects in the associated Transaction. The use of this property is deprecated. The PRS_SISService StartSISTransaction method uses the New, Modified and Deleted properties instead of this field. This field is set to NULL by the StartSISTransaction method if the other properties are used.The key fields for the objects added in the associated Transaction. This property is set by the PRS_SISService StartSISTransaction method.The key fields for objects deleted in the associated Transaction. This property is set by the PRS_SISService StartSISTransaction method.The key fields for objects modified in the associated Transaction. This property is set by the PRS_SISService StartSISTransaction method.The date of the Activity. This property is set by the PRS_SISService StartSISTranasaction method.Description of the activity performed. 2.6.0PRS_Transaction represents a single transaction of the Service Incident workflow. A PRS_Transaction instance is created by the PRS_SISService StartSISTransaction method.01234567891011254255Service_RequestEntitlementProblem_SubmittalAccept_ProblemProblem_ResolutionRequest_Problem_InformationProvide_Problem_InformationProvide_Admin_InformationQuery_IncidentConfirm_CloseReject_ResolutionRequest_ClosureOtherUnknownThe specific SIS transaction represented by this PRS_Transaction instance.0123OpenWorkingClosedNotification_PendingThe current state of this transaction. This value is manipulated by the PRS_SISService:StartSISTransaction and SetSISCompletionStatus method implementations. This property is not intended to be written by management applications.The status of the transaction after it has reached the 'Closed' state. A CompletionStatus of zero (0) means the tranasaction completed successfully. A non-zero CompletionStatus indicates the transaction did not complete successfully. Non-zero values are implementation-specific. While the transaction is 'Open' or 'Working' the CompletionStatus property shall be zero (0). See the description for PRS_SISService for the definition of the contents of this property. 2.6.0The PRS_SISService is used as a class factory for PRS_Transactions.When invoked on a local system, this method validates the objects in the local repository, to determine if they are sufficient for the indicated (input parameter) TransactionType. If not, an error is returned and no additional processing is performed. If the repository is successfully validated, this method creates a PRS_Transaction instance for return to the caller. The method also reviews the repository looking for new, modified or deleted objects. As these objects are located, their keys are appended to the related strings in the PRS_Activity instance referenced by another parameter of this method. After all the appropriate new, modified or deleted objects have been located, this method invokes the PRS_SISService's StartSISTransaction method on the remote system specified by the objects related to the Service Incident, associated with the PRS_Activity instance specified as a method parameter. The TransactionType and PRS_Activity REF is forwarded to the remote system as method parameters as well as the PRS_Transaction REF for the instance created by this method. The remote system creates a child namespace using the PRS_Transaction REF for the name. The local system then transfers all of the new, modified and deleted objects to the namespace on the remote system. Once all objects have been successfully transferred, the PRS_SISService's EndSISTransaction method is invoked on the remote system with a Status value of zero to indicate that the remote system should attempt to commit the transaction to the remote repository. The remote system passes the results of the remote commit back to the originating system by invoking the PRS_SISService's SetSISCompletionStatus method on the system that originated the SIS transaction. The CompletionStatus method parameter indicates whether the remote commit was successful. If the CompletionStatis is zero, the remote commit was successful. If it was unsuccessful, the objects were not applied to the remote repository and the CompletionStatus is non-zero, indicating the error. The local invocation of the SetSISCompletionStatus method updates the specified PRS_Transaction's TransactionState to Closed and CompletionStatus to the value provided by the remote system in the CompletionStatus method parameter. In order to promote extensibility, the uint32 return values for PRS_SISService's methods and Status-related parameters are mapped into three sections. The first describes the type of value being reported. It indicates Error versus Notification, and Standard versus Vendor-Specific. The second section describes the source of the value. It indicates Method, Operating System, Repository, or Transport. In addition, this section indicates whether the value was created locally or remotely. The third section is the specific return value. If all 32 bits of the return value are reset, the method completed successfully. Any other value indicates an error condition or notification. If D31 is set, the method did not complete successfully. If D31 is reset, but the rest of the return value is non-zero, this is a Notification that the operation did complete successfully, but that there is a conditon of which the caller should be aware. If D30 is set, the return value is vendor specific. If D30 is reset, the return value is defined by the standard. If D29 is set, the return value was generated by a remote system. If D29 is reset, the return value was generated locally. The bit is always set or reset by the local system. The local system sets the bit if it receives a non-zero return value from a remote method invocation. Bit D28 is reserved for future use and shall be reset on all return values. When there is an error or notification, D24 through D27 indicate its source. The following sources are currently defined (D24 is the least significant bit below): 0000 Method 0001 Operating System 0010 Repository 0011 Transport All remaining values are reserved. Bits D16 through D23 are reserved for future use and shall be reset to zero. Bits D0 through D15 indicate the specific return value. If zero, all other bits in the return value must be zero, indicating successful completion of the method (or Transaction).true01234567891011254255Service_RequestEntitlementProblem_SubmittalAccept_ProblemProblem_ResolutionRequest_Problem_InformationProvide_Problem_InformationProvide_Admin_InformationQuery_IncidentConfirm_CloseReject_ResolutionRequest_ClosureOtherUnknowntruetruetrueThe EndSISTransaction method is used to handle committing or aborting a transaction. For commit, the method is invoked by a remote system when all of the objects associated with the transaction have been placed in the child namespace created by StartSISTransaction. For abort, the method cleans up the child namespace and closes the specified PRS_Transaction, setting the Transaction's CompletionStatus to the method parameter of the same name.trueStatus indicates whether the transaction is to be committed or aborted. If Status is zero, the transaction is to be committed. If Status is non-zero, it indicates the transaction is to be aborted. If the transaction is being aborted, the Status field is passed back to the originating system as the CompletionStatus parameter for the PRS_SISService SetSISCompletionStatus method. See the description for PRS_SISService.StartSISTransaction for the definition of the contents of this property.trueTransactionRef identifies the PRS_Transaction to commit or abort. If this property is NULL or does not identify an 'Open' transaction, this method returns an error.SetSISCompletionStatus is used to signal the system that originated a PRS_Transaction that the remote system has completed processing of the transaction. If the processing was successful, as indicated by the CompletionStatus parameter, the local system resets the DirtyFlag for all of the objects identified in the PRS_Activity instance associated with the PRS_Transaction.trueThis parameter is used to set the CompletionStatus field of the specified PRS_Transaction. If zero, the Transaction was completed successfully. If non-zero, an error occurred and the objects provided in StartSISTransaction were not submitted to the remote repository. See the description for PRS_SISService.StartSISTransaction for the definition of the contents of this property.trueTransactionRef identifies the PRS_Transaction that has completed. If this property is NULL or does not identify an 'Open' transaction, this method returns an error. true2.6.0Associates PRS_ServiceIncident to PRS_Activity.truetrueAntecedent11The PRS_ServiceIncident.trueDependentThe PRS_Activity.true 2.6.0Associates PRS_Activity with PRS_Contact.trueAntecedentThe PRS_Activity.trueDependent1The PRS_Contact.true true2.6.0Associates PRS_Activity with PRS_Resource.truetrueAntecedent11The PRS_Activity.trueDependentThe PRS_Resource.true 2.6.0Associates PRS_Activity with PRS_Transaction.trueAntecedent11The PRS_Activity.trueDependent11The PRS_Transaction.true