FALSE FALSE FALSE Bag FALSE FALSE FALSE FALSE FALSE FALSE FALSE FALSE FALSE TRUE FALSE FALSE FALSE FALSE 0 FALSE FALSE CurrentContext TRUE FALSE .5 FALSE FALSE V2.5 FALSE FALSE TRUE 2.6.0 ManagedElement is an abstract class that provides a common superclass (or top of the inheritance tree) for the non-association classes in the CIM Schema. 64 The Caption property is a short textual description (one-line string) of the object. The Description property provides a textual description of the object. TRUE TRUE 2.6.0 CIM_Dependency is a generic association used to establish dependency relationships between ManagedElements. TRUE Antecedent represents the independent object in this association. TRUE Dependent represents the object dependent on the Antecedent. TRUE 2.6.0 CIM_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.5 256 The Name property defines the label by which the object is known. When subclassed, the Name property can be overridden to be a Key property. 10 A string indicating the current status of the object. Various operational and non-operational statuses are defined. Operational statuses are "OK", "Degraded", "Stressed" and "Pred Fail". "Stressed" indicates that the Element is functioning, but needs attention. Examples of "Stressed" states are overload, overheated, etc. The condition "Pred Fail" (failure predicted) indicates that an Element is functioning properly but predicting a failure in the near future. An example is a SMART-enabled hard drive. \n Non-operational statuses can also be specified. These are "Error", "NonRecover", "Starting", "Stopping", "Stopped", "Service", "No Contact" and "Lost Comm". "NonRecover" indicates that a non-recoverable error has occurred. "Service" describes an Element being configured, maintained, cleaned, or otherwise administered. This status could apply during mirror-resilvering of a disk, reload of a user permissions list, or other administrative task. Not all such work is on-line, yet the Element is neither "OK" nor in one of the other states. "No Contact" indicates that the current instance of the monitoring system has knowledge of this Element but has never been able to establish communications with it. "Lost Comm" indicates that the ManagedSystemElement is known to exist and has been contacted successfully in the past, but is currently unreachable. "Stopped" indicates that the ManagedSystemElement is known to exist, it is not operational (i.e. it is unable to provide service to users), but it has not failed. It has purposely been made non-operational. The Element may have never been "OK", the Element may have initiated its own stop, or a management system may have initiated the stop. OK Error Degraded Unknown Pred Fail Starting Stopping Service Stressed NonRecover No Contact Lost Comm Stopped TRUE TRUE TRUE 2.6.0 CIM_Component is a generic association used to establish 'part of' relationships between Managed System Elements. For example, the SystemComponent association defines parts of a System. TRUE TRUE The parent element in the association. TRUE The child element in the association. TRUE 2.6.0 Subclasses 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. TRUE 256 An 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. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. 256 The name of the organization responsible for producing the PhysicalElement. This may be the entity from whom the Element is purchased, but this is not necessarily true. The latter information is contained in the Vendor property of CIM_Product. 64 The name by which the PhysicalElement is generally known. 64 The stock keeping unit number for this PhysicalElement. 64 A manufacturer-allocated number used to identify the PhysicalElement. 64 A string indicating the version of the PhysicalElement. 256 The part number assigned by the organization responsible for producing or manufacturing the PhysicalElement. OtherIdentifyingInfo 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. Boolean indicating that the PhysicalElement is powered on (TRUE), or is currently off (FALSE). Date that this PhysicalElement was manufactured. TRUE 2.6.0 CIM_LogicalElement is a base class for all the components of a System that represent abstract system components, such as Files, Processes, or LogicalDevices. TRUE TRUE 2.6.0 CIM_LogicalIdentity is an abstract and generic association, indicating that two LogicalElements represent different aspects of the same underlying entity. This relationship conveys what could be defined with multiple inheritance. It is restricted to the 'logical' aspects of a ManagedSystemElement. In most scenarios, the Identity relationship is determined by the equivalence of Keys or some other identifying properties of the related Elements. The association should only be used in well understood scenarios. This is why the association is abstract - allowing more concrete definition and clarification in subclasses. One of the scenarios where this relationship is reasonable is to represent that a Device is both a 'bus' entity and a 'functional' entity. For example, a Device could be both a USB (bus) and a Keyboard (functional) entity. TRUE SystemElement represents one aspect of the LogicalElement. TRUE SameElement represents an alternate aspect of the System entity. TRUE 2.6.0 Indicates 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. TRUE SystemElement represents one LogicalElement that is synchronized with the entity referenced as SyncedElement. TRUE SyncedElement 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. TRUE 2.6.0 An abstraction or emulation of a hardware entity, that may or may not be Realized in physical hardware. Any characteristics of a LogicalDevice that are used to manage its operation or configuration are contained in, or associated with, the LogicalDevice object. Examples of the operational properties of a Printer would be paper sizes supported, or detected errors. Examples of the configuration properties of a Sensor Device would be threshold settings. Various configurations could exist for a LogicalDevice. These configurations could be contained in Setting objects and associated with the LogicalDevice. CIM_System.CreationClassName TRUE 256 The scoping System's CreationClassName. CIM_System.Name TRUE 256 The scoping System's Name. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE 64 An address or other identifying information to uniquely name the LogicalDevice. Boolean indicating that the Device can be power managed - ie, put into a power save state. This boolean does not indicate that power management features are currently enabled, or if enabled, what features are supported. Refer to the PowerManagementCapabilities array for this information. If this boolean is false, the integer value 1, for the string, "Not Supported", should be the only entry in the PowerManagementCapabilities array. Indicates the specific power-related capabilities of a LogicalDevice. The array values, 0="Unknown", 1="Not Supported" and 2="Disabled" are self-explanatory. The value, 3="Enabled" indicates that the power management features are currently enabled but the exact feature set is unknown or the information is unavailable. "Power Saving Modes Entered Automatically" (4) describes that a Device can change its power state based on usage or other criteria. "Power State Settable" (5) indicates that the SetPowerState method is supported. "Power Cycling Supported" (6) indicates that the SetPowerState method can be invoked with the PowerState input variable set to 5 ("Power Cycle"). "Timed Power On Supported" (7) indicates that the SetPowerState method can be invoked with the PowerState input variable set to 5 ("Power Cycle") and the Time parameter set to a specific date and time, or interval, for power-on. 0 1 2 3 4 5 6 7 Unknown Not Supported Disabled Enabled Power Saving Modes Entered Automatically Power State Settable Power Cycling Supported Timed Power On Supported The 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. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 Other Unknown Running/Full Power Warning In Test Not Applicable Power Off Off Line Off Duty Degraded Not Installed Install Error Power Save - Unknown Power Save - Low Power Mode Power Save - Standby Power Cycle Power Save - Warning Paused Not Ready Not Configured Quiesced MIF.DMTF|Operational State|006 MIB.IETF|HOST-RESOURCES-MIB.hrDeviceStatus MIF.DMTF|Host Device|001.5 CIM_LogicalDevice.AdditionalAvailability 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. 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 cannot be communicated with until a load of a driver, a load of a configuration file or some other "enabling" activity has occurred. 1 2 3 4 5 Other Unknown Enabled Disabled Not Applicable MIF.DMTF|Operational State|006 LastErrorCode 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. 256 Indexed OtherIdentifyingInfo 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.IdentifyingDescriptions The number of consecutive hours that this Device has been powered, since its last power cycle. Hours TRUE The total number of hours that this Device has been powered. Hours TRUE Indexed An array of free-form strings providing explanations and details behind the entries in the OtherIdentifyingInfo array. Note, each entry of this array is related to the entry in OtherIdentifyingInfo that is located at the same index. CIM_LogicalDevice.OtherIdentifyingInfo Additional availability and status of the Device, beyond that specified in the Availability property. The Availability property denotes the primary status and availability of the Device. In some cases, this will not be sufficient to denote the complete status of the Device. In those cases, the AdditionalAvailability property can be used to provide further information. For example, a Device's primary Availability may be "Off line" (value=8), but it may also be in a low power state (AdditonalAvailability value=14), or the Device could be running Diagnostics (AdditionalAvailability value=5, "In Test"). 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 Other Unknown Running/Full Power Warning In Test Not Applicable Power Off Off Line Off Duty Degraded Not Installed Install Error Power Save - Unknown Power Save - Low Power Mode Power Save - Standby Power Cycle Power Save - Warning Paused Not Ready Not Configured Quiesced CIM_LogicalDevice.Availability Maximum time in milliseconds, that a Device can run in a "Quiesced" state. A Device's state is defined in its Availability and AdditionalAvailability properties, where "Quiesced" is conveyed by the value 21. What occurs at the end of the time limit is device-specific. The Device may unquiesce, may offline or take other action. A value of 0 indicates that a Device can remain quiesced indefinitely. MilliSeconds FALSE 1 2 3 4 5 6 Full Power Power Save - Low Power Mode Power Save - Standby Power Save - Other Power Cycle Power Off FALSE Requests a reset of the LogicalDevice. The return value should be 0 if the request was successfully executed, 1 if the request is not supported and some other value if an error occurred. In a subclass, the set of possible return codes could be specified, using a ValueMap qualifier on the method. The strings to which the ValueMap contents are 'translated' may also be specified in the subclass as a Values array qualifier. FALSE FALSE FALSE Requests that the Device capture its current configuration, setup and/or state information in a backing store. The goal would be to use this information at a later time (via the RestoreProperties method), to return a Device to its present "condition". This method may not be supported by all Devices. The method should return 0 if successful, 1 if the request is not supported, and some other value if any other error occurred. In a subclass, the set of possible return codes could be specified, using a ValueMap qualifier on the method. The strings to which the ValueMap contents are 'translated' may also be specified in the subclass as a Values array qualifier. Requests that the Device re-establish its configuration, setup and/or state information from a backing store. The intent is to capture this information at an earlier time (via the SaveProperties method), and use it to return a Device to this earlier "condition". This method may not be supported by all Devices. The method should return 0 if successful, 1 if the request is not supported, and some other value if any other error occurred. In a subclass, the set of possible return codes could be specified, using a ValueMap qualifier on the method. The strings to which the ValueMap contents are 'translated' may also be specified in the subclass as a Values array qualifier. TRUE 2.6.0 CIM_Realizes is the association that defines the mapping between LogicalDevices and the PhysicalElements that implement them. Antecedent The physical component that implements the Device. Dependent The LogicalDevice. TRUE 2.6.0 A 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.CreationClassName TRUE 256 The scoping System's CreationClassName. CIM_System.Name TRUE 256 The scoping System's Name. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. Name TRUE 256 The 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. 10 StartMode is a string value indicating whether the Service is automatically started by a System, Operating System, etc. or only started upon request. Automatic Manual Started is a boolean indicating whether the Service has been started (TRUE), or stopped (FALSE). The StartService method places the Service in the started state. It 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. It 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. TRUE 2.6.0 CIM_ProvidesServiceToElement is used to describe that ManagedElements may be dependent on the functionality of one or more Services. An example is that a Processor and an Enclosure (PhysicalElement) are dependent on AlertOnLAN Services to signal an incomplete or erroneous boot, and hardware-related errors. Antecedent The Service provided. Dependent The ManagedElement dependent on the Service. TRUE 2.6.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 BIOS Disk and initialization Services. In the case of the initialization Services, the Boot Service is simply dependent on the init Services completing. For the Disk Services, Boot Services may actually utilize the SAPs of this Service. This usage dependency is modeled via the CIM_ServiceSAPDependency association. Antecedent The required Service. Dependent The Service that is dependent on an underlying Service. The 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. 0 1 2 3 4 Unknown Other Service Must Have Completed Service Must Be Started Service Must Not Be Started this property describes that the antecedent service must be restarted after the dependent operation is complete. TRUE TRUE 2.6.0 The ServiceComponent aggregation models a set of subordinate Services that are aggregated together to form a higher-level service. GroupComponent TRUE The parent Service. PartComponent The component Service. TRUE 2.6.0 CIM_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.CreationClassName TRUE 256 The scoping System's CreationClassName. CIM_System.Name TRUE 256 The scoping System's Name. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. Name TRUE 256 The Name property uniquely identifies the ServiceAccessPoint and provides an indication of the functionality that is managed. This functionality is described in more detail in the object's Description property. TRUE 2.6.0 CIM_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. Antecedent The required ServiceAccessPoint. Dependent The Service that is dependent on an underlying SAP. TRUE 2.6.0 CIM_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. Antecedent The required ServiceAccessPoint. Dependent The ServiceAccessPoint that is dependent on an underlying SAP. TRUE 2.6.0 CIM_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. Antecedent The Service. Dependent An Access Point for a Service. Access points are dependent in this relationship since they have no function without a corresponding Service. TRUE 2.6.0 A CIM_System is a LogicalElement that aggregates an enumerable set of Managed System Elements. The aggregation operates as a functional whole. Within any particular subclass of System, there is a well-defined list of Managed System Element classes whose instances must be aggregated. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE 256 Name The inherited Name serves as key of a System instance in an enterprise environment. 64 The 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. 64 The name of the primary system owner. MIF.DMTF|General Information|001.3 256 A string that provides information on how the primary system owner can be reached (e.g. phone number, email address, ...). MIF.DMTF|General Information|001.4 An array (bag) of strings that specify the roles this System plays in the IT-environment. Subclasses of System may override this property to define explicit Roles values. Alternately, a Working Group may describe the heuristics, conventions and guidelines for specifying Roles. For example, for an instance of a networking system, the Roles property might contain the string, 'Switch' or 'Bridge'. TRUE 2.6.0 CIM_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. Antecedent 1 1 The hosting System. Dependent TRUE The Service hosted on the System. TRUE 2.6.0 CIM_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. Antecedent 1 1 The hosting System. Dependent TRUE The SAP(s) that are hosted on this System. TRUE TRUE 2.6.0 CIM_SystemComponent is a specialization of the CIM_Component association that establishes 'part of' relationships between a System and the Managed System Elements of which it is composed. GroupComponent TRUE The parent System in the Association. PartComponent The child element that is a component of a System. TRUE TRUE 2.6.0 LogicalDevices may be aggregated by a System. This relationship is made explicit by the SystemDevice association. GroupComponent TRUE 1 1 The parent system in the Association. PartComponent TRUE The LogicalDevice that is a component of a System. TRUE 2.6.0 A 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). NameFormat The ComputerSystem 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 is defined to create the ComputerSystem Name to attempt to always generate the same Name, independent of discovery protocol. This prevents inventory and management problems where the same asset or entity is discovered multiple times, but cannot be resolved to a single object. Use of the heuristic is optional, but recommended. \n The NameFormat property identifies how the ComputerSystem Name is generated, using a heuristic. The heuristic is outlined, in detail, 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 ComputerSystem Name. Several rules do map to the same Value. \n Note that the ComputerSystem Name calculated using the heuristic is the System's key value. Other names can be assigned and used for the ComputerSystem, that better suit a business, using Aliases. Other IP Dial HID NWA HWA X25 ISDN IPX DCC ICD E.164 SNA OID/OSI 256 Indexed OtherIdentifyingInfo 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.IdentifyingDescriptions Indexed An array of free-form strings providing explanations and details behind the entries in the OtherIdentifyingInfo array. Note, each entry of this array is related to the entry in OtherIdentifyingInfo that is located at the same index. 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). 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 Not Dedicated Unknown Other Storage Router Switch Layer 3 Switch Central Office Switch Hub Access Server Firewall Print I/O Web Caching Management If enabled (value = 4), the UnitaryComputerSystem 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). 1 2 3 4 5 Other Unknown Disabled Enabled Not Implemented MIF.DMTF|System Hardware Security|001.4 Indicates the specific power-related capabilities of a ComputerSystem and its associated running OperatingSystem. The values, 0="Unknown", 1="Not Supported", and 2="Disabled" are self-explanatory. The value, 3="Enabled" indicates that the power management features are currently enabled but the exact feature set is unknown or the information is unavailable. "Power Saving Modes Entered Automatically" (4) describes that a system can change its power state based on usage or other criteria. "Power State Settable" (5) indicates that the SetPowerState method is supported. "Power Cycling Supported" (6) indicates that the SetPowerState method can be invoked with the PowerState input variable set to 5 ("Power Cycle"). "Timed Power On Supported" (7) indicates that the SetPowerState method can be invoked with the PowerState input variable set to 5 ("Power Cycle") and the Time parameter set to a specific date and time, or interval, for power-on. 0 1 2 3 4 5 6 7 Unknown Not Supported Disabled Enabled Power Saving Modes Entered Automatically Power State Settable Power Cycling Supported Timed Power On Supported MIF.DMTF|System Power Controls|001.2 FALSE 1 2 3 4 5 6 7 8 Full Power Power Save - Low Power Mode Power Save - Standby Power Save - Other Power Cycle Power Off Hibernate Soft Off FALSE 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. \n NameFormat The 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. Other AS NAP NOC POP RNP IP IPX SNA Dial WAN LAN ISDN Frame Relay ATM E.164 IB FC Policy Repository Other Autonomous System Network Access Provider Network Operations Center Point of Presence Regional Network Provider IP IPX SNA Dial WAN LAN ISDN Frame Relay ATM E.164 Infiniband Fibre Channel Policy Repository TRUE TRUE 2.6.0 A relationship that aggregates one or more lower-level AdminDomain instances into a higher-level AdminDomain. GroupComponent TRUE An AdminDomain that aggregates other AdminDomains. PartComponent An AdminDomain aggregated by another AdminDomain. 2.6.0 CIM_Product is a concrete class that is a collection of PhysicalElements, SoftwareFeatures and/or other Products, 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. TRUE 256 Commonly used Product name. MIF.DMTF|ComponentID|001.2 TRUE 64 Product 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.4 TRUE 256 The 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. MIF.DMTF|ComponentID|001.1 TRUE 64 Product version information. Corresponds to the Version property in the Product object in the DMTF Solution Exchange Standard. MIF.DMTF|ComponentID|001.3 64 Product SKU (stock keeping unit) information. If this Product is under warranty, the start date of the warranty. CIM_Product.WarrantyDuration MIF.DMTF|FRU|002.9 If this Product is under warranty, the duration of the warranty in days. Days CIM_Product.WarrantyStartDate MIF.DMTF|FRU|002.10 TRUE TRUE 2.6.0 The CIM_ProductParentChild association defines a parent child hierarchy among Products. For example, a Product may come bundled with other Products. TRUE TRUE The parent Product in the association. TRUE The child Product in the association. TRUE 2.6.0 CIM_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, ... TRUE The Product for which compatible offerings are defined. TRUE The compatible Product. CompatibilityDescription is a free-form string defining how the two referenced Products interoperate or are compatible, any limitations to compatibility, etc. TRUE 2.6.0 CIM_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. TRUE The required Product. TRUE The 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. 0 1 2 3 Unknown Other Product Must Be Installed Product Must Not Be Installed 2.6.0 The CIM_SupportAccess association defines how to obtain assistance for a Product. Description A textual description of the type of Support provided. MIF.DMTF|Support|001.3 TRUE 256 SupportAccessID 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. CommunicationInfo 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.11 MIF.DMTF|FRU|002.12 CommunicationMode defines the form of communication in order to obtain support. For example, phone communication (value=2), fax (3) or email (8) can be specified. 1 2 3 4 5 6 7 8 Other Phone Fax BBS Online Service Web Page FTP E-mail MIF.DMTF|Support|001.5 64 Locale defines the geographic region and/or language dialect to which this Support resource pertains. MIF.DMTF|Support|001.2 TRUE 2.6.0 CIM_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. TRUE The Product. TRUE Support for the Product. 2.6.0 The 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'. Description A textual description of the FRU. MIF.DMTF|FRU|002.3 TRUE 64 FRU ordering information. MIF.DMTF|FRU|002.6 TRUE 64 FRU identification such as a serial number on software or a die number on a hardware chip. MIF.DMTF|FRU|002.7 TRUE 256 The name of the FRU's supplier. MIF.DMTF|FRU|002.4 FRU name. 256 64 The FRU's revision level. MIF.DMTF|FRU|002.8 Indicates whether the FRU is customer replaceable. TRUE 2.6.0 CIM_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. 1 TRUE The Product to which the FRU is applied. TRUE The FRU. TRUE 2.6.0 ReplaceableProductFRU 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. 1 TRUE The Product to which the FRU is applied. TRUE The FRU. TRUE TRUE 2.6.0 Indicates the PhysicalElements that make up a Product. 1 TRUE TRUE The Product. TRUE The PhysicalElement which is a part of the Product. TRUE TRUE 2.6.0 Indicates the PhysicalElements that make up a FRU. 1 TRUE TRUE The FRU. TRUE The PhysicalElement which is a part of the FRU. TRUE TRUE 2.6.0 Indicates that a FRU may be composed of other Product(s). 1 TRUE TRUE The FRU. TRUE The Product which is a part of the FRU. TRUE 2.6.0 Collection is an abstract class that provides a common superclass for data elements that represent collections of ManagedElements and its subclasses. TRUE TRUE 2.6.0 CIM_MemberOfCollection is an aggregation used to establish membership of ManagedElements in a Collection. TRUE TRUE The Collection that aggregates members. TRUE The aggregated member of the Collection. TRUE 2.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). \n 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. 256 The identification of the Collection object. When subclassed, the CollectionID property can be overridden to be a Key property. TRUE TRUE 2.6.0 CIM_CollectedCollections is an aggregation association representing that a CollectionOfMSEs may itself be contained in a CollectionOfMSEs. TRUE TRUE The 'higher level' or parent element in the aggregation. TRUE The 'collected' Collection. TRUE TRUE 2.6.0 CIM_CollectedMSEs is a generic association used to establish the members of the grouping object, CollectionOfMSEs. TRUE Collection The grouping or 'bag' object that represents the Collection. Member The members of the Collection. TRUE 2.6.0 CIM_StatisticalInformation is a root class for any arbitrary collection of statistical data and/or metrics applicable to one or more ManagedSystemElements. 256 The Name property defines the label by which the statistic or metric is known. When subclassed, the property can be overridden to be a Key property. TRUE 2.6.0 CIM_Statistics is an association that relates ManagedElements to the StatisticalGroup(s) that apply to them. TRUE The statistic information/object. TRUE The ManagedElement for which statistical or metric data is defined. TRUE 2.6.0 CIM_RelatedStatistics is an association that defines hierarchies and/or dependencies of related CIM_StatisticalInformation classes. TRUE The statistic information/object. TRUE The related statistics or metrics. 2.6.0 Statistical information associated with a System object or one of its subclasses. CIM_System.CreationClassName TRUE 256 The scoping System's CreationClassName. CIM_System.Name TRUE 256 The scoping System's Name. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE 256 Name The Name property, inherited from StatisticalInformation, serves as part of the object key. TRUE 2.6.0 SystemStatistics relates the SystemStatisticalInformation class to the System to which it applies. Stats TRUE The statistical object. Element 1 1 The System to which the statistics apply. 2.6.0 Statistical information associated with a Service object or one of its subclasses. CIM_Service.SystemCreationClassName TRUE 256 The scoping System's CreationClassName. CIM_Service.SystemName TRUE 256 The scoping System's Name. CIM_Service.CreationClassName TRUE 256 The scoping Service's CreationClassName. CIM_Service.Name TRUE 256 The scoping Service's Name. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE 256 Name The Name property, inherited from StatisticalInformation, serves as part of the object key. TRUE 2.6.0 ServiceStatistics relates the ServiceStatisticalInformation class to the Service to which it applies. Stats TRUE The statistical object. Element 1 1 The Service to which the statistics apply. 2.6.0 Statistical information associated with a ServiceAccessPoint object or one of its subclasses. CIM_ServiceAccessPoint.SystemCreationClassName TRUE 256 The scoping System's CreationClassName. CIM_ServiceAccessPoint.SystemName TRUE 256 The scoping System's Name. CIM_ServiceAccessPoint.CreationClassName TRUE 256 The scoping SAP's CreationClassName. CIM_ServiceAccessPoint.Name TRUE 256 The scoping SAP's Name. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE 256 Name The Name property, inherited from StatisticalInformation, serves as part of the object key. TRUE 2.6.0 SAPStatistics relates the SAPStatisticalInformation class to the ServiceAccessPoint to which it applies. Stats TRUE The statistical object. Element 1 1 The ServiceAccessPoint to which the statistics apply. 2.6.0 Statistical information associated with a LogicalDevice or one of its subclasses. CIM_LogicalDevice.SystemCreationClassName TRUE 256 The scoping System's CreationClassName. CIM_LogicalDevice.SystemName TRUE 256 The scoping System's Name. CIM_LogicalDevice.CreationClassName TRUE 256 The scoping Device's CreationClassName. CIM_LogicalDevice.DeviceID TRUE 64 The scoping Device's ID. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE 256 Name The Name property, inherited from StatisticalInformation, serves as part of the object key. TRUE 2.6.0 DeviceStatistics relates the DeviceStatisticalInformation class to the LogicalDevice to which it applies. Stats TRUE The statistical object. Element 1 1 The Device to which the statistics apply. 2.6.0 Statistical information associated with a PhysicalElement or one of its subclasses. CIM_PhysicalElement.CreationClassName TRUE 256 The scoping Element's CreationClassName. CIM_PhysicalElement.Tag TRUE 256 The scoping Element's identifying Tag. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE 256 Name The Name property, inherited from StatisticalInformation, serves as part of the object key. TRUE 2.6.0 PhysicalStatistics relates the PhysicalStatisticalInformation class to the PhysicalElement to which it applies. Stats TRUE The statistical object. Element 1 1 The PhysicalElement to which the statistics apply. TRUE 2.6.0 The Setting class represents configuration-related and operational parameters for one or more ManagedSystemElement(s). A ManagedSystemElement 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. 256 The identifier by which the Setting object is known. FALSE FALSE FALSE FALSE FALSE FALSE FALSE FALSE FALSE FALSE TRUE FALSE FALSE FALSE FALSE FALSE TRUE FALSE FALSE FALSE FALSE FALSE FALSE FALSE FALSE FALSE FALSE FALSE FALSE FALSE TRUE FALSE FALSE FALSE FALSE FALSE FALSE TRUE TRUE 2.6.0 ElementSetting represents the association between ManagedSystemElements and the Setting class(es) defined for them. TRUE The ManagedSystemElement. TRUE The Setting object associated with the ManagedSystemElement. TRUE 2.6.0 DefaultSetting represents the association between a ManagedSystemElement and the single Setting class that is defined to be the default setting for this Element. Setting 1 The Setting object which is the default. TRUE 2.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. \n 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. 256 The identifier by which the MethodParameters object is known. FALSE TRUE 2.6.0 ParameterValueSources represents the association between a MethodParameters instance and the ManagedElement instances which contain properties to be used to create values for the MethodParameters properties. TRUE The MethodParameters instance whose property values are to be set. TRUE The ManagedElement which contains properties to be used to populate the values of the properties of the MethodParameters instance. TRUE 2.6.0 ParametersForMethod 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. TRUE The MethodParameters instance which may be used by the ParametersForMethod's method invocation. TRUE The ManagedElement which has a method that may use this instance of MethodParameters. TRUE 64 The name of the method that may use the referenced instance of MethodParameters during its invocation. TRUE 2.6.0 CIM_SystemSetting represents the general concept of a CIM_Setting which is scoped by/weak to a System. CIM_System.CreationClassName TRUE 256 The scoping System's CreationClassName. CIM_System.Name TRUE 256 The scoping System's Name. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. SettingID TRUE 256 TRUE 2.6.0 CIM_SettingForSystem defines a Setting in the context of the System on which it resides. Antecedent 1 1 The hosting System. Dependent TRUE The Setting defined for the System. 2.6.0 The Configuration object allows the grouping of sets of parameters (defined in Setting objects) and dependencies for one or more ManagedSystemElements. The Configuration object represents a certain behavior, or a desired functional state for the ManagedSystemElements. The desired functional state 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. TRUE 256 The label by which the Configuration object is known. TRUE TRUE 2.6.0 ConfigurationComponent 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. TRUE TRUE The Configuration that aggregates additional Configurations. TRUE A Configuration that is part of a 'higher-level' Configuration. TRUE 2.6.0 This 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. TRUE The ManagedSystemElement. TRUE The Configuration object that groups the Settings and dependencies associated with the ManagedSystemElement. TRUE 2.6.0 This 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. TRUE The CollectionOfMSEs. TRUE The Configuration object that groups the Settings and dependencies associated with the Collection. TRUE TRUE 2.6.0 This 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. TRUE TRUE The Configuration object that aggregates the Dependency. TRUE An aggregated Dependency. TRUE TRUE 2.6.0 This 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. TRUE TRUE The Configuration object that aggregates the Setting. TRUE An aggregated Setting. TRUE 2.6.0 CollectionSetting represents the association between a CollectionOfMSEs class and the Setting class(es) defined for them. TRUE The CollectionOfMSEs. TRUE The Setting object associated with the Collection. 2.6.0 CIM_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.CreationClassName TRUE 256 The scoping System's CreationClassName. CIM_System.Name TRUE 256 The scoping System's Name. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE 256 The label by which the Configuration object is known. TRUE 2.6.0 CIM_ConfigurationForSystem defines a Configuration in the context of the System on which it resides. Antecedent 1 1 The hosting System. Dependent TRUE The Configuration defined for the System. TRUE TRUE 2.6.0 This relationship associates System-specific Configuration objects with System-specific Setting objects, similar to the SettingContext association. TRUE TRUE The Configuration object that aggregates the Setting. TRUE An aggregated Setting. TRUE TRUE 2.6.0 CIM_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. \n\nTo 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. The 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. TRUE TRUE 2.6.0 CIM_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. TRUE TRUE The 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. TRUE 2.6.0 CIM_ClassCreation notifies when a new class is defined in the schema. TRUE 2.6.0 CIM_ClassDeletion notifies when a class is deleted from the schema. TRUE 2.6.0 CIM_ClassModification notifies when a class definition in the schema is modified. TRUE TRUE A 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). TRUE TRUE 2.6.0 CIM_InstIndication is an abstract superclass describing changes to instances. Subclasses represent specific types of change notifications, such as instance creation, deletion and modification. TRUE TRUE A 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. TRUE 2.6.0 CIM_InstCreation notifies when a new instance is created. TRUE 2.6.0 CIM_InstDeletion notifies when an existing instance is deleted. TRUE 2.6.0 CIM_InstModification notifies when an instance is modified. TRUE TRUE A 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. TRUE 2.6.0 CIM_InstMethodCall notifies when an instance's method is invoked. TRUE The name of the method invoked. TRUE The 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.PreCall TRUE Boolean 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. TRUE 2.6.0 CIM_InstRead notifies when an instance is read but not modified. TRUE TRUE 2.6.0 An 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.0 A 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. Type of object generating the trap. PDU.IETF|RFC1157-TRAP-PDU.enterprise Address of the object generating the trap. PDU.IETF|RFC1157-TRAP-PDU.agent-addr An enumerated value that describes the generic trap type: \n- 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. \n- 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. \n- 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. \n- 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. \n- 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. \n- 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. \n- 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 Start Warm Start Link Down Link Up Authentication Failure EGP Neighbor Loss Enterprise Specific PDU.IETF|RFC1157-TRAP-PDU.generic-trap Specific trap code. PDU.IETF|RFC1157-TRAP-PDU.specific-trap Time elapsed between the last (re)intialization of the managed entity and the generation of the trap. PDU.IETF|RFC1157-TRAP-PDU.time-stamp Object 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. Indexed CIM_SNMPTrapIndication.VarBindSyntaxes CIM_SNMPTrapIndication.VarBindValues PDU.IETF|RFC1157-TRAP-PDU.variable-bindings Object 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. Indexed 1 2 3 4 5 6 7 8 Integer OctetString ObjectIdentifier NetworkAddress Counter Gauge TimeTicks Opaque CIM_SNMPTrapIndication.VarBindNames CIM_SNMPTrapIndication.VarBindValues PDU.IETF|RFC1157-TRAP-PDU.variable-bindings An 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. Indexed TRUE CIM_SNMPTrapIndication.VarBindNames CIM_SNMPTrapIndication.VarBindSyntaxes PDU.IETF|RFC1157-TRAP-PDU.variable-bindings TRUE 2.6.0 A 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. A short description of the Indication. Recommendation.ITU|X733.Additional text The 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. TRUE Primary classification of the Indication. The following values are defined: \n1 - 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. \n2 - 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. \n3 - 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. \n4 - Processing Error. An Indication of this type is principally associated with a software or processing fault. \n5 - Device Alert. An Indication of this type is principally associated with an equipment or hardware fault. \n6 - 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. \n7 - 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. \n8 - Security Alert. An Indication of this type is associated with security violations, detection of viruses, and similar issues. 1 2 3 4 5 6 7 8 Other Communications Alert Quality of Service Alert Processing Error Device Alert Environmental Alert Model Change Security Alert Recommendation.ITU|X733.Event type A string describing the Alert type - used when the AlertType property is set to 1, "Other State Change". CIM_AlertIndication.AlertType TRUE An enumerated value that describes the severity of the AlertIndication from the notifier's point of view: \n1 - Other, by CIM convention, is used to indicate that the Severity's value can be found in the OtherSeverity property. \n3 - Degraded/Warning should be used when its appropriate to let the user decide if action is needed. \n4 - Minor should be used to indicate action is needed, but the situation is not serious at this time. \n5 - Major should be used to indicate action is needed NOW. \n6 - 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). \n7 - Fatal/NonRecoverable should be used to indicate an error occurred, but it's too late to take remedial action. \n2 and 0 - Information and Unknown (respectively) follow common usage. Literally, the AlertIndication is purely informational or its severity is simply unknown. Unknown Other Information Degraded/Warning Minor Major Critical Fatal/NonRecoverable Recommendation.ITU|X733.Perceived severity Holds the value of the user defined severity value when 'Severity' is 1 ("Other"). CIM_AlertIndication.PerceivedSeverity TRUE An enumerated value that describes the probable cause of the situation which resulted in the AlertIndication. Unknown Other Adapter Error Application Subsystem Failure Bandwidth Reduced Connection Establishment Error Communications Protocol Error Communications Subsystem Failure Configuration/Customization Error Congestion Corrupt Data CPU Cycles Limit Exceeded Dataset/Modem Error Degraded Signal DTE-DCE Interface Error Enclosure Door Open Equipment Malfunction Excessive Vibration File Format Error Fire Detected Flood Detected Framing Error HVAC Problem Humidity Unacceptable I/O Device Error Input Device Error LAN Error Non-Toxic Leak Detected Local Node Transmission Error Loss of Frame Loss of Signal Material Supply Exhausted Multiplexer Problem Out of Memory Output Device Error Performance Degraded Power Problem Pressure Unacceptable Processor Problem (Internal Machine Error) Pump Failure Queue Size Exceeded Receive Failure Receiver Failure Remote Node Transmission Error Resource at or Nearing Capacity Response Time Excessive Retransmission Rate Excessive Software Error Software Program Abnormally Terminated Software Program Error (Incorrect Results) Storage Capacity Problem Temperature Unacceptable Threshold Crossed Timing Problem Toxic Leak Detected Transmit Failure Transmitter Failure Underlying Resource Unavailable Version MisMatch Previous Alert Cleared Login Attempts Failed Software Virus Detected Hardware Security Breached Denial of Service Detected Security Credential MisMatch Invalid Access of Data Detected Recommendation.ITU|X733.Probable cause Provides additional information related to the ProbableCause. Provides information on trending - trending up, down or no change. Unknown Not Applicable Trending Up Trending Down No Change Recommendation.ITU|X733.TrendIndication An identifier for the AlertIndication. This property is similar to a key value in that it can be used for identification, when correlating AlertIndications (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 AlertIndications will reference it in their CorrelatedIndications array. Recommendation.ITU|X733.Notification identifier A list of IndicationIdentifiers whose notifications are correlated with (related to) this one. Recommendation.ITU|X733.Correlated notifications Free form descriptions of the recommended actions to take to resolve the cause of the notification. Recommendation.ITU|X733.Proposed repair actions TRUE 2.6.0 A 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". A 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 information A 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 information A 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 TRUE 2.6.0 A subclass of CIM_AlertIndication that embeds a CIM_InstIndication. It is used when adding AlertIndication data to a LifeCycle Indication. AlertType The 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'. 7 TRUE TRUE Embeds the InstIndication that is part of this AlertIndication. Only the properties selected by the IndicationFilter's Query are included. 2.6.0 CIM_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. TRUE 256 A 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. TRUE 256 A 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. TRUE 256 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, it allows all instances of this class and its subclasses to be uniquely identified. TRUE The name of the filter. The path to a local namespace where the Indications originate. If NULL, the namespace of the Filter registration is assumed. TRUE A 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.QueryLanguage TRUE The language in which the query is expressed. TRUE 2.6.0 CIM_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. TRUE 256 A 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. TRUE 256 A 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. TRUE 256 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, it allows all instances of this class and its subclasses to be uniquely identified. TRUE 256 Indicates the name of this Handler. The name of the entity that created and/or maintains this Handler. 2.6.0 CIM_IndicationHandlerCIMXML describes the destination for Indications to be delivered via CIM-XML. TRUE The destination URL to which CIM-XML Indication messages are to be delivered. The scheme prefix is implied and is not required, but must be 'http:' if specified. TRUE 2.6.0 CIM_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. TRUE The Filter that defines the criteria and data of the possible Indications of this subscription. TRUE The Handler addressing delivery of the possible Indications of this subscription. 2.6.0 The 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. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE 1024 The 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. 128 The BusinessCategory property may be used to describe the kind of business activity performed by the members of the group. TRUE 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. 2.6.0 The 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. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE 1024 The 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. 128 The 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. 1024 The 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.6.0 The 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. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE 1024 The 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. 128 This 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. TRUE 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. 2.6.0 The 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. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE 1024 The 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. 128 This 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. 1024 The 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. 128 This property is used for the role occupants' telegram service. The role occupants' facsimile telephone number. 16 The role occupants' International ISDN number. The name of an organizational unit related to the role. 128 The 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. 40 The 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. 40 The 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. 128 The 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. 32 The 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. 15 An X.121 address for the role occupants. TRUE 2.6.0 OrganizationalEntity is an abstract class from which classes that fit into an organizational structure are derived. 2.6.0 The 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. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE 1024 The 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. 128 This 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. TRUE The 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. 40 The 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. 32 The Telephone Number property specifies a telephone number of the organization, e.g. + 44 582 10101). 2.6.0 The 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. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE 1024 The 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. 128 This property describes the kind of business performed by an organization. 1024 The 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. 128 This property is used for the organization's telegram service. The organization's facsimile telephone number. 16 The 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. 128 The 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. 40 The 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. 40 The 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. 128 The 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. 32 The 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. TRUE An 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. TRUE In 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. 15 An X.121 address for the organization. 2.6.0 The 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. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE 1024 The 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. 128 This 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. TRUE The 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. 40 The 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. 32 The Telephone Number property specifies a telephone number of the organizational unit, e.g. + 44 582 10101). 2.6.0 The 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. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE 1024 The 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. 128 This property describes the kind of business performed by an organizational unit. 1024 The 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. 128 This property is used for the organizational unit's telegram service. The organizational unit's facsimile telephone number. 16 The 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. 128 The 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. 40 The 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. 40 The 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. 128 The 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. 32 The 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. TRUE In 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. 15 An X.121 address for the organization. TRUE 2.6.0 UserEntity is an abstract class that represents users. 2.6.0 The 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. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE 1024 The 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. 128 This property describes the kind of business performed by an organization. TRUE 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. 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. 32 Based 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. 32 Based 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. 32 Based 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. 40 The 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. TRUE 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. 32 The 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. 2.6.0 The 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. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE 1024 The 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. TRUE The Audio property may be used to store an audio clip of the person. 128 This property describes the kind of business performed by an organization. 128 The 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). 1024 The 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. 128 This 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. 32 Based 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. 16 The 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. 32 Based on RFC1274, the Mobile Phone property specifies a mobile telephone number for the person, e.g. + 44 582 10101). TRUE The 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. 32 Based 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. TRUE Based 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. 128 The 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. 40 The 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. 40 The 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. 128 The 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. 32 The 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. TRUE A small image of the person's organization logo. TRUE A 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. TRUE Based on inetOrgPerson and for directory compatibility, the User Certificate property may be used to specify a public key certificate for the person. TRUE In 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. TRUE Based 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. TRUE Based 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. 15 An X.121 address for the organization. TRUE An X.500 specified unique identifier that may be assigned in an environment to differentiate between uses of a given named person object instance. 2.6.0 The 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. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE 256 The Name property defines the label by which the object is known. TRUE The 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. 0 1 2 3 4 5 6 7 8 N/A Other Facial Retina Mark Finger Voice DNA-RNA EEG 2.6.0 CIM_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.CreationClassName TRUE 256 The scoping System's CCN. CIM_System.Name TRUE 256 The scoping System's Name. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE Name 1024 The 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. 256 UserID 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. 1024 The 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. TRUE The 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. TRUE Based on inetOrgPerson and for directory compatibility, the User Certificate property may be used to specify a public key certificate for the person. TRUE In 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. TRUE 2.6.0 A service providing security functionaity. 2.6.0 CIM_AccountManagementService creates, manages, and if necessary destroys Accounts on behalf of other SecuritySerices. 2.6.0 CIM_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.0 CIM_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.0 CIM_CredentialManagementService issues credentials and manages the credential lifecycle. 2.6.0 CIM_CredentialManagementSAP represents the ability to utilize or invoke a CredentialManagementService. The URL for the access point. 2.6.0 A 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. A 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. TRUE 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). TRUE The frequency, expressed in hours, at which the CA will update its Certificate Revocation List. Zero implies that the refresh frequency is unknown. Hours The maximum number of certificates in a certificate chain permitted for credentials issued by this certificate authority or it's subordinate CAs. \nThe 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.0 The Kerberos KDC. Name The Realm served by this KDC. The version of Kerberos supported by this service. 0 1 2 3 V4 V5 DCE MS 2.6.0 CIM_Notary is an AuthenticationService (credential management service) which compares the biometric characteristics of a person with the known characteristics of an 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. 0 1 2 3 4 5 6 7 8 N/A Other Facial Retina Mark Finger Voice DNA-RNA EEG The 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.0 CIM_LocalCredentialManagementService is a credential management service that provides local system management of credentials used by the local system. 2.6.0 CIM_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. 256 The Algorithm used to convey the shared secret, such as HMAC-MD5,or PLAINTEXT. The Protocol supported by the SharedSecretService. 2.6.0 CIM_PublicKeyManagementService is a credential management service that provides local system management of public keys used by the local system. TRUE 2.6.0 Subclasses 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. 2.6.0 A 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.SystemCreationClassName TRUE 256 The scoping System's CCN. CIM_CertificateAuthority.SystemName TRUE 256 The scoping System's Name. CIM_CertificateAuthority.CreationClassName TRUE 256 The scoping Service's CCN. CIM_CertificateAuthority.Name TRUE 256 The scoping Service's Name. TRUE 256 Certificate subject identifier. 256 Alternate subject identifier for the Certificate. The DER-encoded raw public key. TRUE 2.6.0 A 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.SystemCreationClassName TRUE 256 The scoping System's CCN. CIM_PublicKeyManagementService.SystemName TRUE 256 The scoping System's Name. CIM_PublicKeyManagementService.CreationClassName TRUE 256 The scoping Service's CCN. CIM_PublicKeyManagementService.Name TRUE 256 The scoping Service's Name. TRUE 256 The 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.PeerIdentityType PeerIdentityType is used to describe the type of the PeerIdentity. The currently defined values are used for IKE identities. 0 1 2 3 4 5 6 7 8 9 10 11 Other IPV4_ADDR FQDN USER_FQDN IPV4_ADDR_SUBNET IPV6_ADDR IPV6_ADDR_SUBNET IPV4_ADDR_RANGE IPV6_ADDR_RANGE DER_ASN1_DN DER_ASN1_GN KEY_ID CIM_PublicKeyManagementService.PeerIdentity The DER-encoded raw public key. TRUE 2.6.0 A 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.SystemCreationClassName TRUE 256 The scoping System's CCN. CIM_KerberosKeyDistributionCenter.SystemName TRUE 256 The scoping System's Name. CIM_KerberosKeyDistributionCenter.CreationClassName TRUE 256 The scoping Service's CCN. CIM_KerberosKeyDistributionCenter.Name TRUE 256 The 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. TRUE 256 The name of the service for which this ticket is used. TRUE 256 RemoteID 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"). 0 1 Session TicketGranting 2.6.0 CIM_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.SystemCreationClassName TRUE 256 The scoping System's CCN. CIM_SharedSecretService.SystemName TRUE 256 The scoping System's Name. CIM_SharedSecretService.CreationClassName TRUE 256 The scoping Service's CCN. CIM_SharedSecretService.Name TRUE 256 The scoping Service's Name. TRUE 256 RemoteID 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.0 CIM_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.SystemCreationClassName TRUE 256 The scoping System's CCN. CIM_SharedSecretService.SystemName TRUE 256 The scoping System's Name. CIM_SharedSecretService.CreationClassName TRUE 256 The scoping Service's CCN. CIM_SharedSecretService.Name TRUE 256 The scoping Service's Name. TRUE 256 The local Identity with whom the direct trust relationship exists. CIM_NamedSharedIKESecret.LocalIdentityType TRUE LocalIdentityType is used to describe the type of the LocalIdentity. 1 2 3 4 5 6 7 8 9 10 11 IPV4_ADDR FQDN USER_FQDN IPV4_ADDR_SUBNET IPV6_ADDR IPV6_ADDR_SUBNET IPV4_ADDR_RANGE IPV6_ADDR_RANGE DER_ASN1_DN DER_ASN1_GN KEY_ID CIM_NamedSharedIKESecret.LocalIdentity TRUE 256 The peer identity with whom the direct trust relationship exists. CIM_NamedSharedIKESecret.PeerIdentityType TRUE PeerIdentityType is used to describe the type of the PeerIdentity. 1 2 3 4 5 6 7 8 9 10 11 IPV4_ADDR FQDN USER_FQDN IPV4_ADDR_SUBNET IPV6_ADDR IPV6_ADDR_SUBNET IPV4_ADDR_RANGE IPV6_ADDR_RANGE DER_ASN1_DN DER_ASN1_GN KEY_ID CIM_NamedSharedIKESecret.PeerIdentity SharedSecretName 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.0 CIM_AuthorizationService determines whether a user, by association with an Account used by the AuthorizationService, is permitted access a resource or set of resources. 2.6.0 CIM_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.CreationClassName TRUE 256 Hosting system creation class name. CIM_System.Name TRUE 256 Hosting system name. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE 256 Name The 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.0 CIM_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.CreationClassName TRUE 256 Hosting system creation class name. CIM_System.Name TRUE 256 Hosting system name. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE 256 Name The 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.AccessQualifier CIM_AccessControlInformation.Permission The 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.AccessType CIM_AccessControlInformation.Permission The 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. Unknown Allow Deny Manage CIM_AccessControlInformation.AccessType CIM_AccessControlInformation.AccessQualifier TRUE TRUE 2.6.0 CIM_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. Collection TRUE Member A MemberPrincipal may be identifed in several ways that may be either direct or indirect membership in the collection. \n - A 'UsersAccess' membership directly identifies the user by the UsersAccess object instance. \n - An 'Account' membership directly identifies the user by the Account object class instance. \n - 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. 1 2 3 4 UsersAccess Account UsingElement CredentialManagementService TRUE TRUE 2.6.0 A system (e.g., ApplicationSystem, ComputerSystem, AdminDomain) aggregates Accounts and scopes the uniqueness of the Account names (i.e., userids). GroupComponent 1 1 TRUE The aggregating system also provides name scoping for the Account. PartComponent TRUE The subordinate Account. TRUE TRUE 2.6.0 CIM_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. TRUE 1 TRUE The organizational parent in this association. TRUE The organizational child in this association, i.e., the sub-unit or other owned object instance. TRUE TRUE 2.6.0 CIM_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. TRUE 1 TRUE The parent organization responsible for the collection. TRUE The collection. TRUE TRUE 2.6.0 CIM_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. TRUE 1 TRUE The parent system responsible for the collection. TRUE The collection. TRUE 2.6.0 CIM_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. 1 1 Antecedent The ManagedElement that has UsersAccess. Dependent The 'owned' UsersAccess. TRUE 2.6.0 CIM_MoreOrganizationInfo is an association used to extend the information in a CIM_Organization class instance. 1 Antecedent The Organization which has more information. 0 1 Dependent Additional data concerning the Organization. TRUE 2.6.0 CIM_MoreOrgUnitInfo is an association used to extend the information in an CIM_OrgUnit class instance. 1 Antecedent The OrgUnit which has more information. 0 1 Dependent Additional data concerning the OrgUnit. TRUE 2.6.0 CIM_MoreGroupInfo is an association used to extend the information in a CIM_Group class instance. 1 Antecedent The Group which has more information. 0 1 Dependent Additional data concerning the Group. TRUE 2.6.0 CIM_MoreRoleInfo is an association used to extend the information in a CIM_Role class instance. 1 Antecedent The Role which has more information. 0 1 Dependent Additional data concerning the Role. TRUE 2.6.0 CIM_MorePersonInfo is an association used to extend the information in a CIM_Person class instance. 1 Antecedent The Person which has more information. 0 1 Dependent Additional data concerning the Person. TRUE 2.6.0 CIM_SystemAdministrator is an association used to identify the UserEntity as a system administrator of a CIM_System. Antecedent The administered system. Dependent The UserEntity that provides the admininstrative function for the associated system. TRUE 2.6.0 CIM_SystemAdministratorGroup is an association used to identify a Group that has system administrator responsibilities for a CIM_System. Antecedent The administered system. Dependent The Group of administrators. TRUE 2.6.0 CIM_SystemAdministratorRole is an association used to identify a system administrator Role for a CIM_System. Antecedent The administered system. Dependent The system administration role. TRUE 2.6.0 This relationship associates UsersAccess with the Accounts with which they're able to interact. Antecedent The user's Account. Dependent The User as identified by their UsersAccess instance. TRUE 2.6.0 This 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. Antecedent An Account. Dependent A related Account. TRUE 2.6.0 This relationship associates SecurityService instances to the Accounts they use in the course of their work. Antecedent Dependent TRUE 2.6.0 This relationship associates the AccountManagement security service to the Accounts for which it is responsible. Antecedent Dependent TRUE 2.6.0 This relationship associates a Service with the SecurityServices that it uses. Antecedent Dependent TRUE 2.6.0 The CIM_SecurityServiceForSystem provides the association between a System and a SecurityService that provides services for that system. Antecedent The SecurityService that provides services for the system. Dependent The system that is dependent on the security service. TRUE 2.6.0 The CIM_ManagesAccountOnSystem provides the association between a System and the AccountManagementService that manages accounts for that system. Antecedent An AccountManagementService that manages accounts for the system. Dependent The system that is dependent on the AccountManagementService. TRUE 2.6.0 CIM_TrustHierarchy is an association between two CredentialManagementService instances that establishes the trust hierarchy between them. Antecedent 1 The superior CredentialManagementService from which the dependent service gets its authority. Dependent The subordinate CredentialManagementService. TRUE 2.6.0 CIM_UsersCredential is an association used to establish the credentials that may be used for a UsersAccess to a system or set of systems. Antecedent The issued credential that may be used. Dependent The UsersAccess that has use of a credential. TRUE 2.6.0 This 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. Antecedent Dependent The Certificate may be used for signature only or for confidentiality as well as signature 0 1 SignOnly ConfidentialityOrSignature The repository in which the certificate is backed up. TRUE 2.6.0 A 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. 1 Antecedent The Certificate used by the CA. Dependent The CA that uses a Certificate. TRUE 2.6.0 This relationship associates a CredentialManagementService with the Credential it manages. Antecedent 1 1 The credential management service. Dependent The managed credential. TRUE 2.6.0 This relationship associates a CertificateAuthority with the certificates it signs. Antecedent 1 1 The CA which signed the certificate. Dependent TRUE The certificate issued by the CA. TRUE TRUE 2.6.0 CIM_LocallyManagedPublicKey association provides the relationship between a PublicKeyManagementService and an UnsignedPublicKey. Antecedent 1 1 The PublicKeyManagementService that manages an unsigned public key. Dependent TRUE An unsigned public key. TRUE 2.6.0 This relationship associates a SharedSecretService with the SecretKey it verifies. Antecedent 1 1 The credential management service. Dependent TRUE The managed credential. TRUE 2.6.0 CIM_IKESecretIsNamed association provides the relationship between a SharedSecretService and a NamedSharedIKESecret. Antecedent 1 1 The SharedSecretService that manages a NamedSharedIKESecret. Dependent TRUE The managed NamedSharedIKESecret. TRUE 2.6.0 The KDC issues and owns Kerberos tickets. This association captures the relationship between the KDC and its issued tickets. Antecedent 1 1 The issuing KDC. Dependent TRUE The managed credential. TRUE 2.6.0 This relationship associates a Notary service with the Users Access whose biometric information is verified. Antecedent The Notary service that verifies biometric information. Dependent The UsersAccess that represents a person using biometric information for authentication. TRUE 2.6.0 CIM_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. 1 1 Antecedent The hosting system. Dependent TRUE The hosted AuthenticationRequirement. TRUE 2.6.0 CIM_AuthenticateForUse is an association used to provide an AuthenticationService with the AuthenticationRequirement it needs to do its job. Antecedent AuthenticationRequirement for use. Dependent AuthenticationService that uses the requirements. TRUE 2.6.0 CIM_RequireCredentialsFrom is an association used to require that credentials are issued by particular Credential Management Services in order to authenticate a user. Antecedent CredentialManagementService from which credentials are accepted for the associated AuthenticationRequirement. Dependent AuthenticationRequirement that limit acceptable credentials. TRUE 2.6.0 CIM_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. Antecedent AuthenticationRequirement that apply to specific resources. Dependent Target resources that may be in a Collection or an individual ManagedElement. These resources are protected by the AuthenticationRequirement. TRUE 2.6.0 CIM_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. 1 1 Antecedent The hosting system. Dependent TRUE The hosted AccessControlInformation. TRUE 2.6.0 CIM_AuthorizedUse is an association used to provide an AuthorizationService with the AccessControlInformation it needs to do its job. Antecedent Access Control Information. Dependent AuthorizationService that uses an ACI. TRUE 2.6.0 CIM_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. Antecedent AccessControlInformation that applies to a subject set. Dependent The subject set may be specified as a collection or as a set of associations to ManagedElements that represent users. TRUE 2.6.0 CIM_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. Antecedent AccessControlInformation that applies to the target set. Dependent The target set of resources may be specified as a collection or as a set of associations to ManagedElements that represent target resources. TRUE 2.6.0 An abstract class defining the common properties of the policy managed elements derived from CIM_Policy. The subclasses are used to create rules and groups of rules that work together to form a coherent set of policies within an administrative domain or set of domains. 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: \n- Keywords defined in this and other MOFs, or in DMTFwhite papers. These keywords provide a vendor-independent, installation-independent way of characterizing policy objects. \n- Installation-dependent keywords for characterizing policy objects. Examples include 'Engineering', 'Billing', and 'Review in December 2000'. \nThis 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. TRUE 2.6.0 PolicySet 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. 1 FirstMatching The PolicyRoles property represents the roles and role combinations 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). \n\nEach value represents one role or role combination. Since this is a multi-valued property, more than one role or combination can be associated with a single PolicySet. Each value is a string of the form: \n <RoleName>[&&<RoleName>]* \nwhere the individual role names appear in alphabetical order (according to the collating sequence for UCS-2). 2.6.0 An 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.CreationClassName TRUE 256 The scoping System's CreationClassName. CIM_System.Name TRUE 256 The scoping System's Name. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE 256 A user-friendly name of this PolicyGroup. 2.6.0 The 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. \n\nThe 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. \n\nA 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 PolicyRuleValidityPeriod aggregation that provides this linkage. \n\nThe PolicyRule class uses the property ConditionListType, to indicate whether the conditions for the rule are in DNF or CNF. 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. \n\nSuppose we have a PolicyRule that aggregates five PolicyConditions C1 through C5, with the following values in the properties of the five PolicyConditionInPolicyRule associations: \n C1: GroupNumber = 1, ConditionNegated = FALSE \n C2: GroupNumber = 1, ConditionNegated = TRUE \n C3: GroupNumber = 1, ConditionNegated = FALSE \n C4: GroupNumber = 2, ConditionNegated = FALSE \n C5: GroupNumber = 2, ConditionNegated = FALSE \n\nIf ConditionListType = DNF, then the overall condition for the PolicyRule is: \n (C1 AND (NOT C2) AND C3) OR (C4 AND C5) \n\nOn the other hand, if ConditionListType = CNF, then the overall condition for the PolicyRule is: \n (C1 OR (NOT C2) OR C3) AND (C4 OR C5) \n\nIn 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. \n\nPolicyRule 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.CreationClassName TRUE 256 The scoping System's CreationClassName. CIM_System.Name TRUE 256 The scoping System's Name. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE 256 A user-friendly name of this PolicyRule. Indicates whether this PolicyRule is administratively enabled, administratively disabled, or enabled for debug. When the property has the value 3 ("enabledForDebug"), the entity evaluating the PolicyConditions is instructed to evaluate the conditions for the Rule, but not to perform the actions if the PolicyConditions evaluate to TRUE. This serves as a debug vehicle when attempting to determine what policies would execute in a particular scenario, without taking any actions to change state during the debugging. The default value is 1 ("Enabled"). 1 2 3 Enabled Disabled EnabledForDebug Indicates whether the list of PolicyConditions associated with this PolicyRule is in disjunctive normal form (DNF) or conjunctive normal form (CNF).The default value is 1 ("DNF"). 1 2 DNF CNF A free-form string that can be used to provide guidelines on how this PolicyRule should be used. CIM_PolicySetComponent.Priority PolicyRule.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. \n\nA non-negative integer for prioritizing this PolicyRule relative to other Rules. A larger value indicates a higher priority. The default value is 0. A 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: \n o mandatory(1): Do the actions in the indicated order, or don't do them at all. \n 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. \n o dontCare(3): Do them -- I don't care about the order. \nThe default value is 3 ("DontCare"). 1 2 3 Mandatory Recommended DontCare ExecutionStrategy defines the strategy to be used in executing the sequenced actions aggregated by this PolicyRule. There are three execution strategies: \n\nDo Until Success - execute actions according to predefined \n order, until successful execution of a \n single action. \nDo All - execute ALL actions which are part of \n the modeled set, according to their \n predefined order. Continue doing this, \n even if one or more of the actions fails. \nDo Until Failure - execute actions according to predefined \n order, until the first failure in \n execution of an action instance. 1 2 3 Do Until Success Do All Do Until Failure 2.6.0 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 unique association for containing policy elements. \n\nAn instance of this class uses the NameFormat value"ReusablePolicyContainer". CIM_ReusablePolicyContainer 2.6.0 The 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. \n\nA 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. \n\nAn instance of this class uses the NameFormat value"PolicyRepository". TRUE 2.6.0 A 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. TRUE 256 The name of the class or the subclass used in the creation of the System object in whose scope this PolicyCondition is defined. \n\nThis 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. \n\nNote 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. TRUE 256 The name of the System object in whose scope this PolicyCondition is defined. \n\nThis 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. TRUE 256 For 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. TRUE 256 For 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. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE 256 A user-friendly name of this PolicyCondition. 2.6.0 This class provides a means of representing the time periods during which a PolicyRule is valid, i.e., active. At all times that fall outside these time periods, the PolicyRule has no effect. A Rule is treated as valid at ALL times, if it does not specify a PolicyTimePeriodCondition. \n\nIn some cases a Policy Consumer may need to perform certain setup / cleanup actions when a PolicyRule becomes active / inactive. For example, sessions that were established while a Rule was active might need to be taken down when the Rule becomes inactive. In other cases, however, such sessions might be left up. In this case, the effect of deactivating the PolicyRule would just be to prevent the establishment of new sessions. \n\nSetup / 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_PolicyRule, 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. \n\nPolicyTimePeriodCondition 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. \n\nInstances 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: \n Friday, March 5, 2000, from 0800 through 1600; \n Friday, March 12, 2000, from 0800 through 1600; \n Friday, March 19, 2000, from 0800 through 1600; \n Friday, March 26, 2000, from 0800 through 1600; \n Friday, April 2, 2000, from 0800 through 1600; \n Friday, April 9, 2000, from 0800 through 1600; \n Friday, April 16, 2000, from 0800 through 1600; \n Friday, April 23, 2000, from 0800 through 1600; \n Friday, April 30, 2000, from 0800 through 1600. \n\nProperties 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 PolicyRule 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 PolicyRule 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: \n 20000101T080000/20000131T120000 defines \n January 1, 2000, 0800 through January 31, 2000, noon \n\nThere are also two special cases in which one of the date/time strings is replaced with a special string defined in RFC 2445. \n o If the first date/time is replaced with the string 'THISANDPRIOR', then the property indicates that a PolicyRule is valid [from now] until the date/time that appears after the '/'. \n o If the second date/time is replaced with the string 'THISANDFUTURE', then the property indicates that a PolicyRule becomes valid on the date/time that appears before the '/', and remains valid from that point on. CIM_PolicyTimePeriodCondition.MonthOfYearMask CIM_PolicyTimePeriodCondition.DayOfMonthMask CIM_PolicyTimePeriodCondition.DayOfWeekMask CIM_PolicyTimePeriodCondition.TimeOfDayMask CIM_PolicyTimePeriodCondition.LocalOrUtcTime TRUE The 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 PolicyRule is valid. These properties work together, with the TimePeriod used to specify the overall time period in which the PolicyRule is valid, and the MonthOfYearMask used to pick out the months during which the Rule is valid. \n\nThis property is formatted as an octet string, structured as follows: \n o a 4-octet length field, indicating the length of the entire octet string; this field is always set to 0x00000006 for this property; \n 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. \n\nThe value 0x000000060830, for example, indicates that a PolicyRule is valid only in the months May, November, and December. \n\nIf a value for this property is not provided, then the PolicyRule is treated as valid for all twelve months, and only restricted by its TimePeriod property value and the other Mask properties. CIM_PolicyTimePeriodCondition.TimePeriod CIM_PolicyTimePeriodCondition.LocalOrUtcTime TRUE The 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 PolicyRule is valid. These properties work together, with the TimePeriod used to specify the overall time period in which the PolicyRule is valid, and the DayOfMonthMask used to pick out the days of the month during which the Rule is valid. \n\n This property is formatted as an octet string, structured as follows: \n o a 4-octet length field, indicating the length of the entire octet string; this field is always set to 0x0000000C for this property; \n 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 policy is valid for that day, and the value '0' indicates that it is not valid. \n\nThe value 0x0000000C8000000100000000, for example, indicates that a PolicyRule is valid on the first and last days of the month. \n\n For months with fewer than 31 days, the digits corresponding to days that the months do not have (counting in both directions) are ignored. \n\nIf a value for this property is not provided, then the PolicyRule 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.TimePeriod CIM_PolicyTimePeriodCondition.LocalOrUtcTime TRUE The 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 PolicyRule is valid. These properties work together, with the TimePeriod used to specify the overall time period in which the PolicyRule is valid, and the DayOfWeekMask used to pick out the days of the week during which the Rule is valid. \n\n This property is formatted as an octet string, structured as follows: \n o a 4-octet length field, indicating the length of the entire octet string; this field is always set to 0x00000005 for this property; \n 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 policy is valid for that day, and the value '0' indicates that it is not valid. \n\nThe value 0x000000057C, for example, indicates that a PolicyRule is valid Monday through Friday. \n\nIf a value for this property is not provided, then the PolicyRule 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.TimePeriod CIM_PolicyTimePeriodCondition.LocalOrUtcTime The 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 PolicyRule is valid. These properties work together, with the TimePeriod used to specify the overall time period in which the PolicyRule is valid, and the TimeOfDayMask used to pick out the range of time periods in a given day of during which the Rule is valid. \n\nThis 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'. \n\nThe 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. \n\nWhen 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 policy 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 policy is active during the following three intervals: \n From midnight Sunday until 0800 Monday; \n From 2100 Monday until 0800 Tuesday; \n From 2100 Tuesday until 23:59:59 Tuesday. \n\nIf a value for this property is not provided, then the PolicyRule 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.TimePeriod CIM_PolicyTimePeriodCondition.LocalOrUtcTime This 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. 1 2 LocalTime UTCTime CIM_PolicyTimePeriodCondition.TimePeriod CIM_PolicyTimePeriodCondition.MonthOfYearMask CIM_PolicyTimePeriodCondition.DayOfMonthMask CIM_PolicyTimePeriodCondition.DayOfWeekMask CIM_PolicyTimePeriodCondition.TimeOfDayMask 2.6.0 A 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. \n\nAs 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. TRUE This 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.ConstraintEncoding An OID encoded as a string, identifying the format and semantics for this instance's Constraint property. CIM_VendorPolicyCondition.Constraint TRUE 2.6.0 A 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. TRUE 256 The name of the class or the subclass used in the creation of the System object in whose scope this PolicyAction is defined. \n\nThis 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. \n\nNote 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. TRUE 256 The name of the System object in whose scope this PolicyAction is defined. \n\nThis 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. TRUE 256 For a rule-specific PolicyAction, the CreationClassName of the PolicyRule object with which this Action is associated. For a reusable PolicyAction, a special value, 'NO RULE', should be used to indicate that this Action is reusable and not associated with a single PolicyRule. TRUE 256 For a rule-specific PolicyAction, the name of the PolicyRule object with which this Action is associated. For a reusable PolicyAction, a special value, 'NO RULE', should be used to indicate that this Action is reusable and not associated with a single PolicyRule. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE 256 A user-friendly name of this PolicyAction. 2.6.0 A 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. \n\nAs 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. TRUE This 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.ActionEncoding An OID encoded as a string, identifying the format and semantics for this instance's ActionData property. CIM_VendorPolicyAction.ActionData 2.6.0 CompoundPolicyAction 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: \n o mandatory(1): Do the actions in the indicated order, or don't do them at all. \n 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. \n o dontCare(3): Do them -- I don't care about the order. \nThe default value is 3 ("DontCare"). 1 2 3 Mandatory Recommended DontCare ExecutionStrategy defines the strategy to be used in executing the sequenced actions aggregated by this CompoundPolicyAction. There are three execution strategies: \n\nDo Until Success - execute actions according to predefined \n order, until successful execution of a \n single action. \nDo All - execute ALL actions which are part of \n the modeled set, according to their \n predefined order. Continue doing this, \n even if one or more of the actions fails. \nDo Until Failure - execute actions according to predefined \n order, until the first failure in \n execution of an action instance. \nThe default value is 2 ("Do All"). 1 2 3 Do Until Success Do All Do Until Failure TRUE TRUE TRUE 2.6.0 CIM_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. TRUE TRUE The parent Policy in the association. TRUE The child/part Policy in the association. TRUE TRUE 2.6.0 CIM_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. \n\nCardinality 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. Antecedent 1 The hosting System. Dependent The hosted Policy. TRUE TRUE 2.6.0 PolicySetInSystem 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. Antecedent 1 1 The System in whose scope a PolicySet is defined. Dependent A PolicySet named within the scope of a System. The 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. TRUE 2.6.0 An association that links a PolicyGroup to the System in whose scope the Group is defined. Antecedent 1 1 The System in whose scope a PolicyGroup is defined. Dependent TRUE A PolicyGroup named within the scope of a System. TRUE 2.6.0 An association that links a PolicyRule to the System in whose scope the Rule is defined. Antecedent 1 1 The System in whose scope a PolicyRule is defined. Dependent TRUE A PolicyRule named within the scope of a System. TRUE TRUE 2.6.0 PolicySetComponent is a concrete aggregation class that collects instances of PolicySet subclasses (PolicyGroups and PolicyRules) into coherent sets of policies that have the same decision strategy and are prioritized within the set. GroupComponent TRUE A PolicySet that aggregates other PolicySet instances. PartComponent A PolicySet aggregated into a PolicySet. A non-negative integer for prioritizing this PolicySetcomponent relative to components of the same PolicySet. A larger value indicates a higher priority. TRUE TRUE CIM_PolicySetComponent 2.6.0 PolicySetComponent 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. \n\nA relationship that aggregates one or more lower-level PolicyGroups into a higher-level Group. A PolicyGroup may aggregate PolicyRules and/or other PolicyGroups. GroupComponent TRUE A PolicyGroup that aggregates other Groups. PartComponent A PolicyGroup aggregated by another Group. TRUE TRUE CIM_PolicySetComponent 2.6.0 PolicySetComponent 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. \n\nA relationship that aggregates one or more PolicyRules into a PolicyGroup. A PolicyGroup may aggregate PolicyRules and/or other PolicyGroups. GroupComponent TRUE A PolicyGroup that aggregates one or more PolicyRules. PartComponent A PolicyRule aggregated by a PolicyGroup. TRUE TRUE 2.6.0 A 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 entered into a PolicyRepository or being defined for a System. Note that a PolicyRule should have no effect until it is valid. \n\nThe Conditions aggregated by a PolicyRule 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. \n\nIn either case, PolicyConditions are used to determine whether to perform the PolicyActions associated with the PolicyRule. \n\nOne or more PolicyTimePeriodConditions may be among the conditions associated with a PolicyRule via the PolicyConditionInPolicyRule association. In this case, the time periods are simply additional Conditions to be evaluated along with any others that are specified for the Rule. GroupComponent TRUE This property represents the PolicyRule that contains one or more PolicyConditions. PartComponent This property holds the name of a PolicyCondition contained by one or more PolicyRules. Unsigned integer indicating the group to which the PolicyCondition identified by the ContainedCondition property belongs. This integer segments the Conditions into the ANDed sets (when the ConditionListType is "DNF") or similarly the ORed sets (when the ConditionListType is "CNF") that are then evaluated. Indication of whether the Condition identified by the ContainedCondition property is negated. TRUE indicates that the PolicyCondition IS negated, FALSE indicates that it IS NOT negated. TRUE TRUE 2.6.0 The 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). GroupComponent TRUE This property contains the name of a PolicyRule that contains one or more PolicyTimePeriodConditions. PartComponent This property contains the name of a PolicyTimePeriodCondition defining the valid time periods for one or more PolicyRules. TRUE TRUE TRUE 2.6.0 PolicyActions may be aggregated into rules and into compound actions. PolicyActionStructure is the abstract aggregation class for the structuring of policy actions. GroupComponent TRUE PolicyAction instances may be aggregated into either PolicyRule instances or CompoundPolicyAction instances. PartComponent A PolicyAction aggregated by a PolicyRule or CompoundPolicyAction. ActionOrder 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. \n\nA series of examples will make ordering of PolicyActions clearer: \n o If all actions have the same sequence number, \n regardless of whether it is '0' or non-zero, any \n order is acceptable. \n o The values: \n 1:ACTION A \n 2:ACTION B \n 1:ACTION C \n 3:ACTION D \n indicate two acceptable orders: A,C,B,D or C,A,B,D, \n since A and C can be performed in either order, but \n only at the '1' position. \n o The values: \n 0:ACTION A \n 2:ACTION B \n 3:ACTION C \n 3:ACTION D \n require that B,C, and D occur either as B,C,D or as \n B,D,C. Action A may appear at any point relative to \n B, C, and D. Thus the complete set of acceptable \n orders is: A,B,C,D; B,A,C,D; B,C,A,D; B,C,D,A; \n A,B,D,C; B,A,D,C; B,D,A,C; B,D,C,A. \n\nNote that the non-zero sequence numbers need not start with '1', and they need not be consecutive. All that matters is their relative magnitude. TRUE TRUE 2.6.0 A 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. \n\nThe 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. \n\nThis 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. GroupComponent TRUE This property represents the PolicyRule that contains one or more PolicyActions. PartComponent This property holds the name of a PolicyAction contained by one or more PolicyRules. TRUE TRUE 2.6.0 PolicyActionInPolicyAction is used to represent the compounding of policy actions into a higher-level policy action. GroupComponent TRUE This property represents the CompoundPolicyAction that contains one or more PolicyActions. PartComponent This property holds the name of a PolicyAction contained by one or more CompoundPolicyActions. TRUE TRUE 2.6.0 A relationship that aggregates one or more lower-level ReusablePolicyContainer instances into a higher-level ReusablePolicyContainer. GroupComponent TRUE A ReusablePolicyContainer that aggregates other ReusablePolicyContainers. PartComponent A ReusablePolicyContainer aggregated by another ReusablePolicyContainer. TRUE TRUE CIM_PolicyContainerInPolicyContainer 2.6.0 The 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. \n\nA relationship that aggregates one or more lower-level PolicyRepositories into a higher-level Repository. GroupComponent TRUE A PolicyRepository that aggregates other Repositories. PartComponent A PolicyRepository aggregated by another Repository. TRUE 2.6.0 The ReusablePolicy association provides for the reuse of any subclass of Policy in a ReusablePolicyContainer. Antecedent 1 This property identifies a ReusablePolicyContainer that provides the administrative scope for the reuse of the referenced policy element. Dependent A reusable policy element. TRUE CIM_ReusablePolicy 2.6.0 The ReusablePolicy association is a more general relationship that incorporates both Conditions and Actions as well as any other policy subclass. \n\nA class representing the hosting of reusable PolicyConditions by a PolicyRepository. A reusable PolicyCondition is always related to a single PolicyRepository, via this association. \n\nNote, 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. Antecedent 1 This 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. Dependent This property holds the name of a PolicyConditionhosted in the PolicyRepository. TRUE CIM_ReusablePolicy 2.6.0 The ReusablePolicy association is a more general relationship that incorporates both Conditions and Actions as well as any other policy subclass. \n\nA class representing the hosting of reusable PolicyActions by a PolicyRepository. A reusable PolicyAction is always related to a single PolicyRepository, via this association. \n\nNote, 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. Antecedent 1 This 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. Dependent This property holds the name of a PolicyActionhosted in the PolicyRepository. 2.6.0 The 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.6.0 The 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. TRUE 256 Name The name used to identify this SoftwareElement. TRUE 64 Software Version should be in the form <Major>.<Minor>.<Revision> or <Major>.<Minor><letter><revision>. MIF.DMTF|SubComponent Software |001.4 TRUE The SoftwareElementState is defined in this model to identify various states of a SoftwareElement's life cycle. \n - 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). \n - 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). \n - 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). \n - A SoftwareElement in the running state describes the details necessary to manage the started element. 0 1 2 3 Deployable Installable Executable Running TRUE 256 This 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. TRUE MIF.DMTF|SubComponent Software|001.8 The 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. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 Unknown Other MACOS ATTUNIX DGUX DECNT Digital Unix OpenVMS HPUX AIX MVS OS400 OS/2 JavaVM MSDOS WIN3x WIN95 WIN98 WINNT WINCE NCR3000 NetWare OSF DC/OS Reliant UNIX SCO UnixWare SCO OpenServer Sequent IRIX Solaris SunOS U6000 ASERIES TandemNSK TandemNT BS2000 LINUX Lynx XENIX VM/ESA Interactive UNIX BSDUNIX FreeBSD NetBSD GNU Hurd OS9 MACH Kernel Inferno QNX EPOC IxWorks VxWorks MiNT BeOS HP MPE NextStep PalmPilot Rhapsody Windows 2000 Dedicated OS/390 VSE TPF Windows (R) Me Caldera Open UNIX OpenBSD Not Applicable CIM_OperatingSystem.OSType The 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. 64 CIM_OperatingSystem.OtherTypeDescription 256 MIF.DMTF|SubComponent Software|001.3 Manufacturer of this SoftwareElement. 64 MIF.DMTF|Software Component Information|002.4 The internal identifier for this compilation of SoftwareElement. 64 MIF.DMTF|ComponentID|001.4 The assigned serial number of this SoftwareElement. 64 The 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. 64 MIF.DMTF|SubComponent Software|001.6 The manufacturer's identifier for this SoftwareElement. Often this will be a stock keeping unit (SKU) or a part number. 32 MIF.DMTF|SubComponent Software|001.7 The 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. \n 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.IdentifyingNumber TRUE 64 The scoping Product's identification. CIM_Product.Name TRUE 256 The scoping Product's commonly used name. CIM_Product.Vendor TRUE 256 The scoping Product's supplier. CIM_Product.Version TRUE 64 The scoping Product's version. TRUE Name 256 The 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. TRUE 2.6.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. \n 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.Name TRUE 256 The name used to identify the SoftwareElement that is being checked. CIM_SoftwareElement.Version TRUE 64 The version of the SoftwareElement being checked. CIM_SoftwareElement.SoftwareElementState TRUE The SoftwareElementState of the SoftwareElement being checked. 0 1 2 3 Deployable Installable Executable Running CIM_SoftwareElement.SoftwareElementID TRUE 256 This is an identifier for the SoftwareElement being checked. CIM_SoftwareElement.TargetOperatingSystem TRUE The Target Operating System of the SoftwareElement being checked. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 Unknown Other MACOS ATTUNIX DGUX DECNT Digital Unix OpenVMS HPUX AIX MVS OS400 OS/2 JavaVM MSDOS WIN3x WIN95 WIN98 WINNT WINCE NCR3000 NetWare OSF DC/OS Reliant UNIX SCO UnixWare SCO OpenServer Sequent IRIX Solaris SunOS U6000 ASERIES TandemNSK TandemNT BS2000 LINUX Lynx XENIX VM/ESA Interactive UNIX BSDUNIX FreeBSD NetBSD GNU Hurd OS9 MACH Kernel Inferno QNX EPOC IxWorks VxWorks MiNT BeOS HP MPE NextStep PalmPilot Rhapsody Windows 2000 Dedicated OS/390 VSE TPF Windows (R) Me Caldera Open UNIX OpenBSD Not Applicable TRUE 256 An 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. \n 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. FALSE 2.6.0 The 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. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 Product base directory Product executable directory Product library directory Product configuration directory Product include directory Product working directory Product log directory Shared base directory Shared executable directory Shared library directory Shared include directory System base directory System executable directory System library directory System configuration directory System include directory System log directory Other MIF.DMTF|Location|001.2 1024 The 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.6.0 ArchitectureCheck 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. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 48 49 50 51 52 53 54 55 64 65 66 67 68 69 80 81 82 83 84 85 86 87 88 96 97 98 99 100 101 112 120 121 128 130 144 145 146 147 148 149 150 160 176 177 178 179 180 181 190 200 201 202 250 251 260 261 280 281 300 301 302 320 350 500 Other Unknown 8086 80286 80386 80486 8087 80287 80387 80487 Pentium(R) brand Pentium(R) Pro Pentium(R) II Pentium(R) processor with MMX(TM) technology Celeron(TM) Pentium(R) II Xeon(TM) Pentium(R) III M1 Family M2 Family K5 Family K6 Family K6-2 K6-3 AMD Athlon(TM) Processor Family AMD(R) Duron(TM) Processor AMD29000 Family K6-2+ Power PC Family Power PC 601 Power PC 603 Power PC 603+ Power PC 604 Power PC 620 Power PC X704 Power PC 750 Alpha Family Alpha 21064 Alpha 21066 Alpha 21164 Alpha 21164PC Alpha 21164a Alpha 21264 Alpha 21364 MIPS Family MIPS R4000 MIPS R4200 MIPS R4400 MIPS R4600 MIPS R10000 SPARC Family SuperSPARC microSPARC II microSPARC IIep UltraSPARC UltraSPARC II UltraSPARC IIi UltraSPARC III UltraSPARC IIIi 68040 68xxx Family 68000 68010 68020 68030 Hobbit Family Crusoe(TM) TM5000 Family Crusoe(TM) TM3000 Family Weitek Itanium(TM) Processor PA-RISC Family PA-RISC 8500 PA-RISC 8000 PA-RISC 7300LC PA-RISC 7200 PA-RISC 7100LC PA-RISC 7100 V30 Family Pentium(R) III Xeon(TM) Pentium(R) III Processor with Intel(R) SpeedStep(TM) Technology Pentium(R) 4 Intel(R) Xeon(TM) AS400 Family Intel(R) Xeon(TM) processor MP K7 IBM390 Family G4 G5 i860 i960 SH-3 SH-4 ARM StrongARM 6x86 MediaGX MII WinChip DSP Video Processor MIF.DMTF|Processor|004.3 CIM_Processor.Family 2.6.0 MemoryCheck 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. KiloBytes CIM_OperatingSystem.FreePhysicalMemory 2.6.0 DiskSpaceCheck 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. KiloBytes The AvailableDiskSpace property specifies the minimum amount of disk space that needs to be available on the target system. CIM_FileSystem.AvailableSpace 2.6.0 SwapSpaceCheck 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. KiloBytes The 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. \n 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. \n 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. 64 Minimum version of the required operating system. The value is encoded as <major>.<minor>.<revision> or <major>.<minor><letter revision>. CIM_OperatingSystem.Version 64 Maximum version of the required operating system. The value is encoded as <major>.<minor>.<revision> or <major>.<minor><letter revision>. CIM_OperatingSystem.Version 2.6.0 SoftwareElementVersionCheck 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. 256 The name of the SoftwareElement being checked. CIM_SoftwareElement.Name 64 The minimum version of the SoftwareElement being checked. CIM_SoftwareElement.Version 64 The maximum version of the SoftwareElement being checked. CIM_SoftwareElement.Version The state of the SoftwareElement being checked. 0 1 2 3 Deployable Installable Executable Running CIM_SoftwareElement.SoftwareElementState 64 The target operating system of the SoftwareElement being checked. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 Unknown Other MACOS ATTUNIX DGUX DECNT Digital Unix OpenVMS HPUX AIX MVS OS400 OS/2 JavaVM MSDOS WIN3x WIN95 WIN98 WINNT WINCE NCR3000 NetWare OSF DC/OS Reliant UNIX SCO UnixWare SCO OpenServer Sequent IRIX Solaris SunOS U6000 ASERIES TandemNSK TandemNT BS2000 LINUX Lynx XENIX VM/ESA Interactive UNIX BSDUNIX FreeBSD NetBSD GNU Hurd OS9 MACH Kernel Inferno QNX EPOC IxWorks VxWorks MiNT BeOS HP MPE NextStep PalmPilot Rhapsody Windows 2000 Dedicated OS/390 VSE TPF Windows (R) Me Caldera Open UNIX OpenBSD Not Applicable CIM_SoftwareElement.TargetOperatingSystem 2.6.0 FileSpecification 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. 1024 Either the name of the file or the name of the file with a directory prefix. The creation date and time of the file. KiloBytes A checksum calculated as the 16-bit sum of the first 32 bytes of the file. MIF.DMTF|Software Signature|002.4 The CRC1 property is the CRC value calculated using the middle 512K bytes of the file. MIF.DMTF|Software Signature|002.5 The CRC2 property is the CRC value for the middle 512K bytes of the file, modulo 3. MIF.DMTF|Software Signature|002.6 32 The 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.0 The 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.0 This 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. 256 Key or label for the section of the file containing the settings to be checked. 256 Name of the setting entry to be checked. Value to be compared for the named entry. CheckType specifies how the setting value should be compared. 0 1 Matches Contains 1024 File name of the 'setting' file to be checked. TRUE 2.6.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.Name TRUE 256 The name used to identify the SoftwareElement that is being acted upon. CIM_SoftwareElement.Version TRUE 64 The version of the SoftwareElement being acted upon. CIM_SoftwareElement.SoftwareElementState TRUE The SoftwareElementState of the SoftwareElement being acted upon. 0 1 2 3 Deployable Installable Executable Running CIM_SoftwareElement.SoftwareElementID TRUE 256 This is an identifier for the SoftwareElement being acted upon. CIM_SoftwareElement.TargetOperatingSystem TRUE The Target Operating System of the SoftwareElement being acted upon. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 Unknown Other MACOS ATTUNIX DGUX DECNT Digital Unix OpenVMS HPUX AIX MVS OS400 OS/2 JavaVM MSDOS WIN3x WIN95 WIN98 WINNT WINCE NCR3000 NetWare OSF DC/OS Reliant UNIX SCO UnixWare SCO OpenServer Sequent IRIX Solaris SunOS U6000 ASERIES TandemNSK TandemNT BS2000 LINUX Lynx XENIX VM/ESA Interactive UNIX BSDUNIX FreeBSD NetBSD GNU Hurd OS9 MACH Kernel Inferno QNX EPOC IxWorks VxWorks MiNT BeOS HP MPE NextStep PalmPilot Rhapsody Windows 2000 Dedicated OS/390 VSE TPF Windows (R) Me Caldera Open UNIX OpenBSD Not Applicable TRUE 256 The 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"). 0 1 Install Uninstall 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. \n 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. FALSE TRUE 2.6.0 DirectoryAction is an abstract class used to manage directories. The creation of directories is handled by CreateDirectoryAction and removal is handled by RemoveDirectoryAction. 1024 The name of the directory being managed. 2.6.0 CreateDirectoryAction creates empty directories for SoftwareElements to be installed locally. 2.6.0 RemoveDirectoryAction 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. TRUE 2.6.0 FileAction 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.0 CopyFileAction 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). 1024 The source directory. 1024 The destination directory. Boolean indicating that the file should be deleted after being copied. 2.6.0 The RemoveFileAction uninstalls files. 1024 The file to be removed. 2.6.0 RebootAction causes a reboot of the computer system that defines the Action's environment. 2.6.0 ExecuteProgram causes programs to be executed on the computer system that defines the Action's environment. 1024 The 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.0 This 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. 256 This is the key or label of the section of the file to be modified. 256 Name of setting entry to be modified. This is the value to add, append, or replace the specified setting. 1024 File name of the 'setting' file. Type of Action to be performed on the specified setting entry. \n0=Create - Creates the specified entry. \n1=Delete - Deletes the specified entry. \n2=Append - Appends to the end of the specified entry. \n3=Remove - Removes the value from the specified entry. 0 1 2 3 Create Delete Append Remove TRUE TRUE 2.6.0 This 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. TRUE 1 1 TRUE TRUE TRUE The Phase property indicates whether the referenced Check is an in-state or a next-state Check. 0 1 In-State Next-State TRUE 2.6.0 The CIM_DirectorySpecificationFile association identifies the directory that contains the file being checked in the CIM_FileSpecification class. TRUE 1 The directory to be checked. TRUE The file to be checked. TRUE 2.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. \n 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. TRUE 1 The next Action in the sequence. TRUE 1 The previous Action in the sequence. TRUE TRUE 2.6.0 This association identifies the Actions for a SoftwareElement. TRUE 1 1 TRUE The element that scopes the Action. TRUE TRUE The software Action to move or uninstall a SoftwareElement. TRUE TRUE 2.6.0 SoftwareFeatureSoftwareElements identifies the SoftwareElements that make up a particular SoftwareFeature. TRUE GroupComponent The SoftwareFeature that groups the SoftwareElement. PartComponent The SoftwareElement that makes up the Feature. TRUE TRUE 2.6.0 The ProductSoftwareFeatures association identifies the SoftwareFeatures for a particular Product. TRUE 1 1 TRUE The Product that scopes the SoftwareFeatures. TRUE TRUE The SoftwareFeature in a Product. TRUE 2.6.0 The 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. TRUE 1 The destination directory of the Action. TRUE The Action against the directory. TRUE 2.6.0 The 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. TRUE 1 The source directory of the Action. TRUE The Action against the directory. TRUE 2.6.0 The 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. TRUE 1 The destination directory of the Action. TRUE The Action against the directory. TRUE 2.6.0 The 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. TRUE 1 The source directory of the Action. TRUE The Action against the directory. TRUE 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. \n 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. Antecedent The SoftwareFeature implementing the Service. Dependent The 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. \n 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. Antecedent The SoftwareFeature implementing the SAP. Dependent The AccessPoint being implemented. TRUE TRUE 2.6.0 The ApplicationSystemSoftwareFeature association identifies the Features that make up a particular ApplicationSystem. The SoftwareFeatures can be scoped by different Products. GroupComponent TRUE The ApplicationSystem that aggregates the Features. PartComponent The Features in an ApplicationSystem. TRUE 2.6.0 The InstalledSoftwareElement association allows the identification of the ComputerSystem on which a particular SoftwareElement is installed. TRUE Reference to the Software Element that is installed. TRUE 1 Reference to the ComputerSystem hosting a particular SoftwareElement. TRUE TRUE 2.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: \n(1) Is the physical package of the FRU compatible with the slots or equivalent packaging of the hardware? \n(2) Are there any physical constraints (such as power consumption) that prevent the FRU from being installed? \n(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? \n 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. TRUE 1 TRUE The field replaceable unit. TRUE The SoftwareFeature which is included in the FRU and whoseSoftwareElements should be evaluated. TRUE 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. \n 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. \n 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. \n 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. \n 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. Antecedent The executable SoftwareElement implementing the Service. Dependent The 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. \n 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. \n 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. \n 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. \n 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. Antecedent The executable SoftwareElement implementing the SAP. Dependent The ServiceAccessPoint implemented by the SoftwareElement. TRUE TRUE 2.6.0 The 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. GroupComponent TRUE The parent SoftwareFeature. PartComponent The component SoftwareFeature. 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. \n 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.IdentifyingNumber TRUE 64 The scoping Product's identification. CIM_Product.Name TRUE 256 The scoping Product's commonly used name. CIM_Product.Vendor TRUE 256 The scoping Product's name. CIM_Product.Version TRUE 64 The scoping Product's version information. TRUE 256 The 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. TRUE 256 The identification of the InstalledProduct object. This key can be used to differentiate between Product installations and could include the installation location. 256 The 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. TRUE 2.6.0 InstalledProductImage identifies the collection of SoftwareFeatures and SoftwareElements that are the result of the installation of the referenced Product. TRUE 1 1 TRUE The product that has been installed. TRUE TRUE The collection containing the set of SoftwareFeatures and SoftwareElements that are the result of installing the Product. TRUE TRUE 2.6.0 CollectedSoftwareElements defines the SoftwareElements that are collected by InstalledProduct (ie, the installed image of a Product). TRUE Collection The collection representing the installed image of a Product. Member A SoftwareElement that is a member of the InstalledProduct collection. TRUE TRUE 2.6.0 CollectedSoftwareFeatures defines the SoftwareFeatures that are collected by InstalledProduct (ie, the installed image of a Product). TRUE Collection The collection representing the installed image of a Product. Member The SoftwareFeature that is a member of the InstalledProduct collection. TRUE TRUE 2.6.0 A 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'.\n\nWhen 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. GroupComponent TRUE The ComputerSystem that contains and/or aggregates other Systems. PartComponent The contained (Sub)ComputerSystem. 2.6.0 A 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). 0 1 2 3 4 Unknown Other Automatic Cleaning Manual Operation Front Panel Lockable Boolean 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. Seconds Boolean 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. FALSE 2.6.0 A 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.hrSystemInitialLoadDevice MIB.IETF|HOST-RESOURCES-MIB.hrSystemInitialLoadParameters MIF.DMTF|Host System|001.3 Boolean indicating that the ComputerSystem, with its running OperatingSystem, supports power management. This boolean does not indicate that power management features are currently enabled, or if enabled, what features are supported. Refer to the PowerManagementCapabilities array for this information. If this boolean is false, the integer value 1 for the string, "Not Supported", should be the only entry in the PowerManagementCapabilities array. 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. 0 1 2 3 4 5 6 7 8 9 Unknown Full Power Power Save - Low Power Mode Power Save - Standby Power Save - Unknown Power Cycle Power Off Power Save - Warning Power Save - Hibernate Power Save - Soft Off The event that caused the System to power up. This information is available in SMBIOS, in the Type 1 structure, the Wake Up Type attribute. 0 1 2 3 4 5 6 7 8 Reserved Other Unknown APM Timer Modem Ring LAN Remote Power Switch PCI PME# A/C Power Restored TRUE TRUE 2.6.0 A 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. GroupComponent TRUE 1 The 'underlying' ComputerSystem that hosts a Partition. PartComponent The System Partition. 2.6.0 A 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. TRUE 2.6.0 A VirtualComputerSystem is hosted on another ComputerSystem. This association makes that relationship explicit. Antecedent 1 The hosting ComputerSystem. Dependent The VirtualComputerSystem. 2.6.0 A 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. 0 1 2 3 4 5 6 Unknown Other Failover Performance Distributed OS Node Grouping SysPlex Indicates 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). 0 1 2 3 4 5 Unknown Other On-line Off-line Degraded Unavailable TRUE 2.6.0 A Cluster is composed of two or more ComputerSystems, operating together. A ComputerSystem may participate in multiple Clusters. \n\nWhen 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). Antecedent 1 The ComputerSystem which participates in the Cluster. Dependent The Cluster. StateOfNode indicates the condition of the participating ComputerSystem in the Cluster. For example, one value is "Joining" (2). 0 1 2 3 4 5 6 Unknown Other Joining Paused Available Unavailable Degraded RoleOfNode 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). 0 1 2 3 4 5 6 7 Unknown Other Peer Primary Secondary Standby Base Plex Enhanced Plex 2.6.0 ClusteringService represents the functionality provided by a Cluster. For example, failover functionality may be modeled as a Service of a failover Cluster. FALSE FALSE 2.6.0 A representation of the access points of a ClusteringService. TRUE 2.6.0 ClusterServiceAccessBySAP is the relationship between a ClusteringService and its access points. Antecedent The ClusteringService. Dependent An access point for the ClusteringService. TRUE 2.6.0 HostedClusterService 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. Antecedent 1 1 The Cluster. Dependent The ClusteringService that is hosted on the Cluster. TRUE 2.6.0 HostedClusterSAP 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. Antecedent 1 1 The ComputerSystem. Dependent The ClusteringSAP that is hosted on the ComputerSystem. 2.6.0 BootService represents the functionality provided by a Device, software or via a Network to load an Operating System on a UnitaryComputerSystem. 2.6.0 A representation of the access points of a BootService. TRUE 2.6.0 BootServiceAccessBySAP is the relationship between a BootService and its access points. Antecedent The BootService. Dependent An access point for the BootService. TRUE 2.6.0 HostedBootService 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. Dependent The BootService hosted on the System. TRUE 2.6.0 HostedBootSAP 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. Antecedent 1 1 The UnitaryComputerSystem. Dependent The BootSAP hosted on the UnitaryComputerSystem. 2.6.0 A file or dataset store local to a ComputerSystem or remotely mounted from a file server. CIM_ComputerSystem.CreationClassName TRUE 256 The scoping ComputerSystem's CreationClassName. CIM_ComputerSystem.Name TRUE 256 The scoping ComputerSystem's Name. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. Name TRUE 256 The 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.hrFSMountPoint MIF.DMTF|Host File System|001.2 FileSystems 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. Bytes The FileSystemSize property stores the total size of the FileSystem in bytes. If unknown, enter 0. Bytes MIF.DMTF|Host File System|001.13 TRUE AvailableSpace indicates the total amount of free space for the FileSystem, in bytes. If unknown, enter 0. Bytes MIF.DMTF|Host File System|001.14 MIF.DMTF|Partition|002.4 Indicates that the FileSystem is designated as read only. MIB.IETF|HOST-RESOURCES-MIB.hrFSAccess MIF.DMTF|Host File System|001.5 A 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.8 A 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.7 Indicates 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. 0 1 2 3 4 5 6 7 8 Unknown Other ASCII Unicode ISO2022 ISO8859 Extended UNIX Code UTF-8 UCS-2 Integer 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.6 MIF.DMTF|Host File System|001.4 2.6.0 A 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.0 A 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.0 A 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.\nIf 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.\nIf 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.\nIf 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 Seconds Read buffer size in bytes. Bytes Write buffer size in bytes. Bytes The remote ComputerSystem's (ie, the NFS File 'Server's) UDP port number. If set to true: Control attribute caching is enabled.\nIf set to false: Control attribute caching is disabled. Minimum number of seconds that cached attributes are held after file modification. Seconds Maximum number of seconds that cached attributes are held after file modification. Seconds Minimum number of seconds that cached attributes are held after directory update. Seconds Maximum number of seconds that cached attributes are held after directory update. Seconds 2.6.0 A 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.CSCreationClassName TRUE 256 The scoping ComputerSystem's CreationClassName. CIM_FileSystem.CSName TRUE 256 The scoping ComputerSystem's Name. CIM_FileSystem.CreationClassName TRUE 256 The scoping FileSystem's CreationClassName. CIM_FileSystem.Name TRUE 256 The scoping FileSystem's Name. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. Name TRUE 1024 The 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. TRUE Size of the File in bytes. Bytes File'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. TRUE Integer indicating the number of 'file opens' that are currently active against the File. 2.6.0 DataFile is a type of LogicalFile that is a named collection of data or executable code. 2.6.0 Directory is a type of File that logically groups Files 'contained' in it, and provides path information for the grouped Files. 2.6.0 DeviceFile 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.0 FIFOPipeFile 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.0 This 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. TRUE The target file of the symbolic link. TRUE 2.6.0 Specifies the LogicalDevice that is associated with, and accessed using the referenced DeviceFile. Antecedent The DeviceFile. Dependent 1 The Device that is accessed using the DeviceFile. TRUE TRUE 2.6.0 Specifies the hierarchical arrangement of LogicalFiles in a Directory. GroupComponent TRUE 1 The Directory. PartComponent The LogicalFile 'contained within' the Directory. TRUE 2.6.0 An 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. Antecedent 1 The Directory mounted. Dependent The FileSystem the Directory is mounted on. TRUE 2.6.0 An 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. TRUE 1 The LocalFileSystem. TRUE The Directory exported for mount. Name under which the Directory is exported. TRUE TRUE 2.6.0 A link between the ComputerSystem and the FileSystem(s) hosted on this ComputerSystem. GroupComponent TRUE 1 1 The ComputerSystem. PartComponent TRUE The FileSystem owned by the ComputerSystem. TRUE TRUE 2.6.0 A link between the FileSystem and the LogicalFile(s) addressed through this FileSystem. GroupComponent TRUE 1 1 The FileSystem. PartComponent TRUE The LogicalFile stored in the context of the FileSystem. 2.6.0 An 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.CreationClassName TRUE 256 The scoping ComputerSystem's CreationClassName. CIM_ComputerSystem.Name TRUE 256 The scoping ComputerSystem's Name. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. Name TRUE 256 The inherited Name serves as key of an OperatingSystem instance within a ComputerSystem. MIF.DMTF|Operating System|001.2 A integer indicating the type of OperatingSystem. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 Unknown Other MACOS ATTUNIX DGUX DECNT Digital Unix OpenVMS HPUX AIX MVS OS400 OS/2 JavaVM MSDOS WIN3x WIN95 WIN98 WINNT WINCE NCR3000 NetWare OSF DC/OS Reliant UNIX SCO UnixWare SCO OpenServer Sequent IRIX Solaris SunOS U6000 ASERIES TandemNSK TandemNT BS2000 LINUX Lynx XENIX VM/ESA Interactive UNIX BSDUNIX FreeBSD NetBSD GNU Hurd OS9 MACH Kernel Inferno QNX EPOC IxWorks VxWorks MiNT BeOS HP MPE NextStep PalmPilot Rhapsody Windows 2000 Dedicated OS/390 VSE TPF Windows (R) Me Caldera Open UNIX OpenBSD Not Applicable CIM_OperatingSystem.OtherTypeDescription A 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. 64 CIM_OperatingSystem.OSType A 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.3 Time when the OperatingSystem was last booted. MIF.DMTF|General Information|001.5 OperatingSystem's notion of the local date and time of day. MIB.IETF|HOST-RESOURCES-MIB.hrSystemDate MIF.DMTF|General Information|001.6 CurrentTimeZone indicates the number of minutes the OperatingSystem is offset from Greenwich Mean Time. Either the number is positive, negative or zero. Minutes Number of user licenses for the OperatingSystem. If unlimited, enter 0. Number of user sessions for which the OperatingSystem is currently storing state information. TRUE MIF.DMTF|Host System|001.4 MIB.IETF|HOST-RESOURCES-MIB.hrSystemNumUsers Number of process contexts currently loaded or running on the OperatingSystem. TRUE MIF.DMTF|Host System|001.5 MIB.IETF|HOST-RESOURCES-MIB.hrSystemProcesses Maximum 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.6 MIB.IETF|HOST-RESOURCES-MIB.hrSystemMaxProcesses Total 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. KiloBytes Number 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. KiloBytes MIF.DMTF|System Memory Settings|001.5 TRUE Number 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). KiloBytes MIF.DMTF|System Memory Settings|001.6 TRUE Number of Kbytes of physical memory currently unused and available. KiloBytes MIF.DMTF|System Memory Settings|001.2 MIF.UNIX|Host Physical Memory|6.1 The 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. KiloBytes The total number of KBytes that can be stored in the OperatingSystem's paging files. 0 indicates that there are no paging files. KiloBytes MIF.DMTF|System Memory Settings|001.3 TRUE The 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. KiloBytes MIF.DMTF|System Memory Settings|001.4 Maximum 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. KiloBytes Boolean 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. TRUE TRUE 2.6.0 A 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. GroupComponent TRUE 1 1 The ComputerSystem. PartComponent TRUE The OperatingSystem installed on the ComputerSystem. Boolean indicating that the OperatingSystem is the default OS for the ComputerSystem. MIF.DMTF|Operating System|001.4 TRUE 2.6.0 RunningOS 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. Antecedent 1 The OperatingSystem currently running on the ComputerSystem. Dependent 1 The ComputerSystem. TRUE TRUE 2.6.0 Indicates the SoftwareFeatures that make up the OperatingSystem. The SoftwareFeatures can be part of different Products. GroupComponent TRUE The OperatingSystem. PartComponent The SoftwareFeatures that make up the OperatingSystem. TRUE 2.6.0 A 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. Antecedent The FileSystem from which the OperatingSystem is loaded. Dependent The OperatingSystem. 2.6.0 BIOSFeature 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. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 160 Other Unknown Undefined ISA Support MCA Support EISA Support PCI Support PCMCIA Support PnP Support APM Support Upgradeable BIOS BIOS Shadowing Allowed VL VESA Support ESCD Support LS-120 Boot Support ACPI Support I2O Boot Support USB Legacy Support AGP Support PC Card IR 1394 I2C Smart Battery ATAPI ZIP Drive Boot Support 1394 Boot Support Boot from CD Selectable Boot BIOS ROM is Socketed Boot from PCMCIA EDD Specification Support PC-98 MIF.DMTF|BIOS Characteristic|004.3 Indexed CIM_BIOSFeature.CharacteristicDescriptions An 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. Indexed MIF.DMTF|BIOS Characteristic|004.4 CIM_BIOSFeature.Characteristics 2.6.0 BIOSElement represents the low-level software that is loaded into non-volatile storage and used to bring up and configure a ComputerSystem. Version MIF.DMTF|System BIOS|001.3 Manufacturer MIF.DMTF|System BIOS|001.2 If true, this is the primary BIOS of the ComputerSystem. MIF.DMTF|System BIOS|001.9 A 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.ListOfLanguages The starting address of the memory which this BIOS occupies. MIF.DMTF|System BIOS|001.5 The ending address of the memory which this BIOS occupies. MIF.DMTF|System BIOS|001.6 64 A 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.7 Date that this BIOS was released. MIF.DMTF|System BIOS|001.8 TRUE TRUE 2.6.0 A link between BIOSFeature and its aggregated BIOSElements. GroupComponent TRUE The BIOSFeature. PartComponent The BIOSElement that implements the capabilities described by BIOSFeature. TRUE TRUE 2.6.0 SystemBIOS associates a UnitaryComputerSystem's BIOS with the System itself. GroupComponent 1 TRUE The UnitaryComputerSystem that boots from the BIOS. PartComponent The System's BIOS. 2.6.0 Each 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.CSCreationClassName TRUE 256 The scoping ComputerSystem's CreationClassName. CIM_OperatingSystem.CSName TRUE 256 The scoping ComputerSystem's Name. CIM_OperatingSystem.CreationClassName TRUE 256 The scoping OperatingSystem's CreationClassName. CIM_OperatingSystem.Name TRUE 256 The scoping OperatingSystem's Name. Name The name of the process. MIF.DMTF|Process Information|001.6 TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE 256 A string used to identify the Process. A Process ID is a kind of Process Handle. MIF.DMTF|Process Information|001.1 Priority 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.10 Indicates the current operating condition of the Process. Values include ready (2), running (3), and blocked (4), among others. 0 1 2 3 4 5 6 7 8 9 Unknown Other Ready Running Blocked Suspended Blocked Suspended Ready Terminated Stopped Growing MIF.DMTF|Process Information|001.9 MIF.UNIX|Process Information|13.9 A 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, a value of 0 should be used. MilliSeconds MIF.DMTF|Process Information|001.13 Time in user mode, in milliseconds. If this information is not available, a value of 0 should be used. MilliSeconds MIF.DMTF|Process Information|001.14 TRUE The 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 TRUE TRUE 2.6.0 A link between the OperatingSystem and Process(es) running in the context of this OperatingSystem. GroupComponent TRUE 1 1 The OperatingSystem. PartComponent TRUE The Process running in the context of the OperatingSystem TRUE 2.6.0 A link between a Process and a DataFile indicating that the File participates in the execution of the Process. Antecedent The DataFile participating in the execution of the Process. Dependent The Process. TRUE 2.6.0 CIM_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. TRUE The Service whose Process is described by this association. TRUE The 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. 0 1 2 3 Unknown Other Executes in Existing Process Executes as Independent Process 2.6.0 Threads 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.CSCreationClassName TRUE 256 The scoping ComputerSystem's CreationClassName. CIM_Process.CSName TRUE 256 The scoping ComputerSystem's Name. CIM_Process.OSCreationClassName TRUE 256 The scoping OperatingSystem's CreationClassName. CIM_Process.OSName TRUE 256 The scoping OperatingSystem's Name. CIM_Process.CreationClassName TRUE 256 The scoping Process' CreationClassName. CIM_Process.Handle TRUE 256 The scoping Process' Handle. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allow all instances of this class and its subclasses to be uniquely identified. TRUE 256 A 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. 0 1 2 3 4 5 6 Unknown Other Ready Running Blocked Suspended Blocked Suspended Ready Time in kernel mode, in milliseconds. If this information is not available, a value of 0 should be used. MilliSeconds Time in user mode, in milliseconds. If this information is not available, a value of 0 should be used. MilliSeconds TRUE TRUE 2.6.0 A link between a Process and the Thread(s) running in the context of this Process. GroupComponent TRUE 1 1 The Process. PartComponent TRUE The Thread running in the context of the Process. TRUE 2.6.0 A Job is a LogicalElement representing a unit of work for a System, such as a print job. A Job is distinct from a Process in that a Job can be scheduled. A free form string representing the Job's status. Time that the Job was submitted. Time that the Job was begun. Length of time that the Job has been executing. Time after which the Job is invalid or should be stopped. User to be notified upon Job completion or failure. User that submitted the Job. Indicates the urgency or importance of execution of a Job. 2.6.0 JobDestination is a LogicalElement 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. CIM_System.CreationClassName TRUE 256 The scoping System's CreationClassName. CIM_System.Name TRUE 256 The scoping System's Name. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. Name TRUE 256 The inherited Name serves as key of a JobDestination instance in a System. TRUE 2.6.0 An 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. Antecedent 1 1 The hosting System. Dependent TRUE The JobDestination hosted on the System. TRUE 2.6.0 An association describing where a Job is submitted for processing, ie to which JobDestination. Antecedent 1 The JobDestination, possibly a queue. Dependent The Job that is in the Job queue/Destination. 2.6.0 Specific 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.\nData 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. TRUE 256 SettingID The 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).\n 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. TRUE 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. 0 1 2 3 No Warnings Missing Resources Testing Impacts All Warnings TRUE When 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. TRUE When 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. TRUE When this flag is true, the test will halt after finding the first error. TRUE When 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. TRUE 0 100 Requests 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. \nThis 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.Characteristics Percent 2.6.0 When 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.\nFor every running of DiagnosticTest, a new instance of DiagnosticResult, or one of it's subclasses should be created. CIM_DiagnosticTest.CreationClassName TRUE 256 The scoping Test's CreationClassName. CIM_DiagnosticTest.Name TRUE 256 The scoping Test's Name. CIM_DiagnosticTest.SystemCreationClassName TRUE 256 The scoping Test's SystemCreationClassName. CIM_DiagnosticTest.SystemName TRUE 256 The scoping Test's SystemName. TRUE 1024 The Unique identifier for an instance of DiagnosticResults. The date and time the result was last updated. If 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). 0 1 2 3 4 5 Unknown Other Passed Failed In Progress Stopped CIM_DiagnosticResult.OtherStateDescription When "Other" (value=1) is entered in the TestState property, OtherStateDescription can be used to describe the test's state. CIM_DiagnosticResult.TestState Seconds Estimated 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.EstimatedTimeOfPerforming TestResults stores one or more textual results from the execution of the DiagnosticTest(s) referenced by the DiagnosticCreationClassName and DiagnosticName properties. One entry is considered a cell location in the array. Each entry is time stamped and contains the following information, in the following format: \n yyymmddhhttssoutc|DiagnosticName|Textual message \nWhere: \n yyy = year, e.g. 2000 \n mm = month (01 - 12) \n dd = day (01 - 31) \n hh = hour (00 - 24) \n tt = minute (00-59) \n ss = second (00-59) \n o = "+" or "-" indicating the sign of the UTC correction field \n utc = offset from UTC (Universal Coordinated Time) in minutes \n DiagnosticName = string reference to the DiagnosticTest object which was executed\n Textual message = free form string that is the 'test result'. Ordered Percent 0 100 The 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). TRUE 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. 0 1 2 3 No Warnings Missing Resources Testing Impacts All Warnings TRUE When 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. TRUE When 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. TRUE When this flag is true, the test will halt after finding the first error. TRUE When 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. TRUE 0 100 Requests 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. \nThis 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.Characteristics Percent 2.6.0 The CIM_DiagnosticTest class represents the ability to execute a test. Specific diagnostic tests may be defined by subclassing and/or instantiating this object. To provide more detail for a type of test (i.e, additional properties and methods), subclassing is appropriate. To indicatae that a test exists and may be applied to a specific ManagedSystemElement, instantiation of the DiagnosticTest class may suffice. The descriptions for each Characteristic are below:\n \n* "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. \n\n* If "Is Interactive" (value=3) is set, then the diagnostic displays a message either before, during or after testing. \n\n* Set "Is Destructive" (value=4) if the diagnostic will destroy data, or reconfigure the Element that is being tested. \n\n* "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. \n\n* If "Is Package" (value=6) is set, this test is actually a set of lower level diagnostics, that are 'packaged' together. \n\n"Supports PercentOfTestCoverage" (value=7) indicates that a request for reduced test coverage can be specified using the PercentOfTestCoverage property of Diagnostic Setting. \n\nAlso, 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. 0 1 2 3 4 5 6 7 Unknown Other Is Exclusive Is Interactive Is Destructive Is Risky Is Package Supports PercentOfTestCoverage CIM_DiagnosticTest.OtherCharacteristicDescription Provides additional information for the Characteristic when its value is set to 1 ("Other"). CIM_DiagnotistTest.Characteristics If 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. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 CPU Memory Hard Disk CDROM Floppy PCI Bus USB Bus 1394 Bus SCSI Bus IDE Bus Network ISA Bus EISA Bus VESA Bus PCMCIA Bus CardBus Access.bus NuBus AGP VME Bus Sbus IEEE 1396-1993 MCA Bus GIO Bus XIO Bus HIO Bus PMC Bus SIO Bus FALSE FALSE FALSE TRUE FALSE FALSE TRUE FALSE FALSE FALSE TRUE TRUE 2.6.0 This is an association class relating diagnostic test results to the ManagedSystemElement that is/was tested. TRUE The diagnostic result. TRUE The ManagedSystemElement to which the diagnostic result applies. TRUE 2.6.0 This is an association class to relate the results of a test to the test itself. TRUE 1 1 TRUE The result object. TRUE 1 1 The test that generated the result object. TRUE 2.6.0 This 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. Antecedent The test that may be run against a ManagedSystemElement. Dependent The ManagedSystemElement that can be tested. Seconds Estimated 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.\nA CIM Consumer can compare this value with the value inDiagnosticResult to get an idea of what impact theirsettings have on test execution. CIM_DiagnosticResult.EstimatedTimeOfPerforming If 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. TRUE TRUE 2.6.0 This 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. GroupComponent TRUE The DiagnosticTest object that acts as the container for all the tests of the package. PartComponent The DiagnosticTest object that is one of the elements of the package. TRUE TRUE 2.6.0 This 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. TRUE TRUE The DiagnosticResult object that acts as the container for all the results of the package. TRUE The DiagnosticResult object that is one of the elements of the package. TRUE 2.6.0 This is an association class relating DiagnosticTest to the SoftwareElements that provide this test. SoftwareElement describes vendor/version information and other deployment data. Antecedent Vendor/version and other information about the software that runs as the DiagnosticTest. Dependent The DiagnosticTest whose software is described. TRUE 2.6.0 This is an association class to relate test settings with diagnostic tests. Element The Test that can use the Setting object. Setting The Setting that can be applied to the execution of the DiagnosticTest. 2.6.0 A TimeZone is a presentation of the properties used to describe a time zone. These properties include the concepts of daylight saving time. TRUE Time zone identifier. TimeZoneId MAY be expressed as the form 'area name/city name' (e.g. America/New_York) instead of a time zone name depending on a date (e.g. EST or EDT). TRUE The date and time at which this time zone definition takes effect. Specify it in UTC. Full name of the time zone (e.g. U.S. East Standard Time) of the standard time name in a format suitable for presentation to the user in the default locale. Short name of the time zone (e.g. EST) of the standard time name in a format suitable for presentation to the user in the default locale. The 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. Minutes The month in which daylight saving time ends. Specify 0 for January, 1 for February, and so on. 0 1 2 3 4 5 6 7 8 9 10 11 January February March April May June July August September October November December CIM_TimeZone.StandardDay -31 31 The day-in-month on which daylight saving time ends, if StandardDayOfWeek is 0. Specify a positive or negative integer to indicate whether the StandardDay should be calculated from the beginning of the month 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. \n\nThe day-in-month from which the StandardDayOfWeek is calculated, if StandardDayOfWeek is not 0. If StandardDay is 15 and StandardDayOfWeek is Saturday, then this indicates the first Saturday on or after the 15th day in the StandardMonth (i.e. third Saturday in the StandardMonth). 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.StandardDayOfWeek Positive or negative integer used in conjunction with StandardDay to indicate the day of the week on which daylight saving time ends. Set StandardDayOfWeek 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 StandardDay. Negative integer (-Sunday, -Monday, ..., -Saturday) means that the day of week is found on or before StandardDay. -7 -6 -5 -4 -3 -2 -1 0 1 2 3 4 5 6 7 -Saturday -Friday -Thursday -Wednesday -Tuesday -Monday -Sunday ExactDayOfMonth Sunday Monday Tuesday Wednesday Thursday Friday Saturday CIM_TimeZone.StandardDay The time interval after midnight when daylight saving time ends. For example: \n 00000000020000.000000:000 indicates \n daylight saving time ends at two o'clock in \n the local time (usually, daylight saving time). Full name of the time zone (e.g. U.S. East Daylight Saving Time) of the daylight saving time name in a format suitable for presentation to the user in the default locale. Short name of the time zone (e.g. EDT) of the daylight saving time name in a format suitable for presentation to the user in the default locale. The 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. Minutes The month in which daylight saving time starts. Specify 0 for January, 1 for February, and so on. 0 1 2 3 4 5 6 7 8 9 10 11 January February March April May June July August September October November December CIM_TimeZone.DaylightDay -31 31 The day-in-month on which daylight saving time starts, if DaylightDayOfWeek is 0. Specify a positive or negative integer to indicate whether the DaylightDay should be calculated from the beginning of the month 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. \n\nThe day-in-month from which the DaylightDayOfWeek is calculated, if DaylightDayOfWeek is not 0. If DaylightDay is 15 and DaylightDayOfWeek is Saturday, then this indicates the first Saturday on or after the 15th day in the DaylightMonth (i.e. third Saturday in the DaylightMonth). 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 DaylightMonth. CIM_TimeZone.DaylightDayOfWeek Positive 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 -1 0 1 2 3 4 5 6 7 -Saturday -Friday -Thursday -Wednesday -Tuesday -Monday -Sunday ExactDayOfMonth Sunday Monday Tuesday Wednesday Thursday Friday Saturday CIM_TimeZone.DaylightDay The time interval after midnight when daylight saving time starts. For example: \n 00000000020000.000000:000 indicates \n daylight saving time starts at two o'clock in \n the local time (usually, standard time). 2.6.0 A 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.12 CIM_UnixLocalFileSystem.TotalSlots The total number of inodes available in the file system. A value of zero for TotalSlots indicates that this file system does not have a preset limit. MIF.DMTF|Host File System|001.11 The reserve data capacity of the file system in bytes. MIF.DMTF|Host File System|001.15 Bytes 2.6.0 Each 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. TRUE The parent process ID of this executing process. MIF.DMTF|Process Information|001.2 TRUE The Real User ID of this currently executing process. MIF.DMTF|Process Information|001.4 TRUE The Group ID of this currently executing process. MIF.DMTF|Process Information|001.2 If 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.5 The executing process's command path. MIF.DMTF|Process Information|001.7 The operating system parameters provided to the executing process. These are the argv[] values. MIF.DMTF|Process Information|001.8 The process's 'nice' value. Used to compute its priority. MIF.DMTF|Process Information|001.11 A 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.0 The statistics associated with a Unix process. CIM_Process.CSCreationClassName TRUE 256 The scoping Process's ComputerSystem CreationClassName. CIM_Process.CSName TRUE 256 The scoping Process's ComputerSystem Name. CIM_Process.OSCreationClassName TRUE 256 The scoping Process's OperatingSystem CreationClassName. CIM_Process.OSName TRUE 256 The scoping Process's OperatingSystem Name. CIM_Process.Handle TRUE 256 The scoping Process's Handle. CIM_Process.CreationClassName TRUE 256 The scoping Process's CreationClassName. TRUE 256 Name A 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.12 Percent The number of KiloBytes of real text space used by the process. MIF.DMTF|Process Information|001.15 KiloBytes The number of KiloBytes of real data space used by the process. MIF.DMTF|Process Information|001.16 KiloBytes The number of KiloBytes of real stack space used by the process. MIF.DMTF|Process Information|001.17 KiloBytes The number of KiloBytes of virtual text space used by the process. MIF.DMTF|Process Information|001.18 KiloBytes The number of KiloBytes of virtual data space used by the process. MIF.DMTF|Process Information|001.19 KiloBytes The number of KiloBytes of virtual stack space used by the process. MIF.DMTF|Process Information|001.20 KiloBytes The number of KiloBytes of virtual space used for memory mapped files by the process. MIF.DMTF|Process Information|001.22 KiloBytes The number of KiloBytes of shared memory used by theprocess. MIF.DMTF|Process Information|001.21 KiloBytes CPU time of terminated child processes in clock ticks Clock Ticks TRUE System time of terminated child processes in clock ticks Clock Ticks TRUE TRUE 2.6.0 CIM_UnixProcessStatistics is an association that relates a CIM_UnixProcess to its StatisticalInformation. TRUE Element 1 1 The Process for which statistical or metric data is defined. TRUE Stats TRUE The UNIX Process statistical information/object. 2.6.0 Threads 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. 0 1 2 3 Unknown Other SCHED_FIFO SCHED_RR CIM_UnixThread.OtherSchedPolicy Indicates the thread's scheduling policy when SchedPolicy is set to "Other". CIM_UnixThread.SchedPolicy Indicates the size of the guard area for a created thread's stack. Indicates the creation state of the thread. 0 2 3 Unknown PTHREAD_CREATE_DETACHED PTHREAD_CREATE_JOINABLE Indicates how the scheduling attributes are to be set. 0 2 3 Unknown PTHREAD_INHERIT_SCHED PTHREAD_EXPLICIT_SCHED Indicates the contention scope of the thread. 0 2 3 Unknown PTHREAD_SCOPE_SYSTEM PTHREAD_SCOPE_PROCESS Indicates the size of storage to be used for the thread's stack. Indicates the thread's concurrency level. Indicates the thread's cancelability state. 0 2 3 Unknown PTHREAD_CANCEL_ENABLE PTHREAD_CANCEL_DISABLE Indicates the thread's cancelability type. 0 2 3 Unknown PTHREAD_CANCEL_DEFERRED PTHREAD_CANCEL_ASYNCHRONOUS 2.6.0 The 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.CSCreationClassName TRUE 256 The scoping ComputerSystem's CreationClassName. CIM_LogicalFile.CSName TRUE 256 The scoping ComputerSystem's Name. CIM_LogicalFile.FSCreationClassName TRUE 256 The scoping FileSystem's CreationClassName. CIM_LogicalFile.FSName TRUE 256 The scoping FileSystem's Name. CIM_LogicalFile.CreationClassName TRUE 256 The scoping LogicalFile's CreationClassName. CIM_LogicalFile.Name TRUE 1024 The scoping LogicalFile's Name. TRUE An Identifer that uniquely describes the owner of this file. TRUE An 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. TRUE File Inode number, as printed by "ls -i". UNIX.TOG|ls -i Indicates 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. 8 POSIX.TOG|pathconf|_PC_LINK_MAX Maximum number of bytes in a filename, not including terminating null. 14 Bytes POSIX.TOG|pathconf|_POSIX_NAME_MAX Maximum number of bytes in a pathname, including the terminating null character. 255 Bytes POSIX.TOG|pathconf|_POSIX_PATH_MAX The 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_RESTRICTED Indicates whether pathname components longer than NameMax generate an error. CIM_UnixFile.NameMax POSIX.TOG|pathconf|_PC_NO_TRUNC Indicates whether asynchronous input or output operations may be performed for the associated file. POSIX.TOG|pathconf|_PC_ASYNC_IO Indicates whether prioritized input or output operations may be performed for the associated file. POSIX.TOG|pathconf|_PC_PRIO_IO Indicates whether synchronised input or output operations may be performed for the associated file. POSIX.TOG|pathconf|_PC_SYNC_IO TRUE 2.6.0 CIM_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. SystemElement 1 1 The Logical File. SameElement TRUE 1 SameElement represents the additional aspects of the Unix/Linux Logical file. 2.6.0 UnixDirectory 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. 32 Bits POSIX.TOG|pathconf|_PC_FILESIZEBITS 2.6.0 DeviceFile 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 file. 0 1 2 3 Unknown Other Block Character CIM_UnixDeviceFile.OtherTypeDescription Additional information when the Type property is set to "Other". CIM_UnixDeviceFile.Type TRUE The 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". TRUE The Device's Major Id. TRUE The Device's Minor Id. TRUE 2.6.0 The DeviceConnection relationship indicates that two or more Device are connected together. Antecedent A LogicalDevice. Dependent A second LogicalDevice connected to the Antecedent Device. When 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 Second MIF.DMTF|Bus Port Association|001.2 When 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. Bits MIF.DMTF|Bus Port Association|001.3 TRUE 2.6.0 CIM_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. SystemElement SystemElement represents one aspect of the Device. SameElement SameElement represents an alternate aspect of the System entity. TRUE 2.6.0 An 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. Antecedent The LogicalDevice. Dependent The Service implemented using the LogicalDevice. TRUE 2.6.0 An 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. Antecedent The LogicalDevice. Dependent The ServiceAccessPoint implemented using the LogicalDevice. 2.6.0 Capabilities and management of CoolingDevices. ActiveCooling is a boolean indicating that the CoolingDevice provides active (as opposed to passive) cooling. 2.6.0 Capabilities and management of a Refrigeration CoolingDevice. 2.6.0 Capabilities and management of a HeatPipe CoolingDevice. 2.6.0 Capabilities 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 Minute FALSE TRUE 2.6.0 Many 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. Antecedent The CoolingDevice. Dependent The LogicalDevice being cooled. 2.6.0 Capabilities 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. 1 2 3 4 5 6 7 8 9 10 11 Other Unknown Fully Charged Low Critical Charging Charging and High Charging and Low Charging and Critical Undefined Partially Charged MIF.DMTF|Portable Battery|003 TimeOnBattery 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'. Seconds EstimatedRunTime 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. Minutes MIF.DMTF|Portable Battery|003 TRUE An estimate of the percentage of full charge remaining. Percent An enumeration that describes the Battery's chemistry. 1 2 3 4 5 6 7 8 Other Unknown Lead Acid Nickel Cadmium Nickel Metal Hydride Lithium-ion Zinc air Lithium Polymer MIF.DMTF|Portable Battery|003 The design capacity of the battery in mWatt-hours. If this property is not supported, enter 0. MilliWattHours MIF.DMTF|Portable Battery|003 The 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. MilliWattHours MIF.DMTF|Portable Battery|003 The design voltage of the battery in mVolts. If this attribute is not supported, enter 0. MilliVolts MIF.DMTF|Portable Battery|003 64 The 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 The remaining time to charge the battery fully in minutes at the current charging rate and usage. Minutes MIF.DMTF|Portable Battery|003 Indicates 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. Minutes MaxRechargeTime 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 TRUE 2.6.0 A 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. Antecedent The Battery. Dependent The LogicalDevice needing or associated with the Battery. 2.6.0 Capabilities 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'. MilliVolts MIF.DMTF|Power Supply|004 The high voltage of Input Voltage Range 1 for this PowerSupply, in millivolts. A value of 0 denotes 'unknown'. MilliVolts MIF.DMTF|Power Supply|004 The frequency (in Hertz) at the low end of this PowerSupply's Input Frequency Range 1. A value of zero implies DC. Hertz MIF.DMTF|Power Supply|004 The frequency (in Hertz) at the high end of this PowerSupply's Input Frequency Range 1. A value of zero implies DC. Hertz MIF.DMTF|Power Supply|004 The low voltage of Input Voltage Range 2 for this PowerSupply, in millivolts. A value of 0 denotes 'unknown'. MilliVolts MIF.DMTF|Power Supply|004 The high voltage of Input Voltage Range 2 for this PowerSupply, in millivolts. A value of 0 denotes 'unknown'. MilliVolts MIF.DMTF|Power Supply|004 The frequency (in Hertz) at the low end of this PowerSupply's Input Frequency Range 2. A value of zero implies DC. Hertz MIF.DMTF|Power Supply|004 The frequency (in Hertz) at the high end of this PowerSupply's Input Frequency Range 2. A value of zero implies DC. Hertz MIF.DMTF|Power Supply|004 ActiveInputVoltage 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. 1 2 3 4 5 6 Other Unknown Range 1 Range 2 Both Neither MIF.DMTF|Power Supply|004 TypeOfRangeSwitching describes the kind of input voltage range switching implemented in this PowerSupply. For example, autoswitching can be specified (value=4). 1 2 3 4 5 6 Other Unknown Manual Autoswitch Wide Range Not Applicable MIF.DMTF|Power Supply|004 Represents the total output power of the PowerSupply in milliWatts. 0 denotes 'unknown'. MilliWatts MIF.DMTF|Power Supply|004 TRUE 2.6.0 The 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. Antecedent The Supply providing power. Dependent A LogicalDevice in the power domain of the Supply. 2.6.0 Capabilities 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. Range1InputVoltageLow If 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'. MilliVolts Range1InputVoltageHigh If 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'. MilliVolts Range2InputVoltageLow If 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'. MilliVolts Range2InputVoltageHigh If 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'. MilliVolts The 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). 1 2 3 4 Unknown Normal Low Depleted MIF.DMTF|UPS Battery|001.1 TimeOnBackup 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'. Seconds MIF.DMTF|UPS Battery|001.2 EstimatedRunTime 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. Minutes MIF.DMTF|UPS Battery|001.3 TRUE An estimate of the percentage of full charge remaining for a UPS (that uses battery technology). Percent MIF.DMTF|UPS Battery|001.4 TRUE 2.6.0 UserDevices 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.6.0 PointingDevice represents those Devices used to 'point' to regions of a Display. The type of the pointing device. 1 2 3 4 5 6 7 8 9 Other Unknown Mouse Track Ball Track Point Glide Point Touch Pad Touch Screen Mouse - Optical Sensor MIF.DMTF|Pointing Device|003 Number of buttons. If the PointingDevice has no buttons, enter 0. MIF.DMTF|Pointing Device|003 Integer 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. 0 1 2 3 Unknown Not Applicable Right Handed Operation Left Handed Operation Tracking resolution of the PointingDevice in Counts per Inch. Counts per Inch 2.6.0 Capabilities 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 An 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). 1 2 3 4 5 Other Unknown Disabled Enabled Not Implemented MIF.DMTF|System Hardware Security|001.2 TRUE 2.6.0 Display is a superclass for grouping the miscellaneous display devices that exist. 2.6.0 Capabilities 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. 0 1 2 3 4 5 Unknown Other Multiscan Color Multiscan Monochrome Fixed Frequency Color Fixed Frequency Monochrome Monitor's bandwidth in MHertz. If unknown, enter 0. MegaHertz The logical height of the Display in screen coordinates. The logical width of the Display in screen coordinates. 2.6.0 Capabilities and management of the FlatPanel LogicalDevice. FlatPanel's horizontal resolution in Pixels. Pixels FlatPanel's vertical resolution in Pixels. Pixels A FlatPanel's scan mode indicating either single (value=2) or dual scan (3). 0 1 2 3 Unknown Other Single Scan Dual Scan An integer enumeration describing the type of flat panel display. 0 1 2 3 4 5 6 7 8 Unknown Other Passive Matrix LCD Active Matrix LCD Cholesteric LCD Field Emission Display Electro Luminescent Display Gas Plasma LED A description of the display illumination type. For example, backlit (value=2) or reflective (4) can be specified. 0 1 2 3 4 Unknown Other Backlit Edgelit Reflective Boolean indicating whether the FlatPanel supports color display. 2.6.0 Capabilities and management of the Scanner LogicalDevice. 2.6.0 A 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. Seconds Date 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. 0 1 2 3 4 Unknown Other Host System Lockable Physical Key All Drives Dismounted Before Access TRUE 2.6.0 Doors provide access to PhysicalElements for hot swap, repair and similar activities. The entities accessed through a Door are indicated in this relationship. Antecedent The Door that provides access. Dependent The PhysicalElement that is accessed. TRUE 2.6.0 Doors 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. Antecedent The Door that provides access. Dependent The LogicalDevice that is accessed. TRUE 2.6.0 A 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. 0 1 2 3 4 5 6 7 8 9 10 11 12 Unknown Other Temperature Voltage Current Tachometer Counter Switch Lock Humidity Smoke Detection Presence Air Flow CIM_Sensor.OtherSensorTypeDescription 128 A string describing the Sensor type - used when the SensorType property is set to "Other". CIM_Sensor.SensorType 128 PossibleStates 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. 128 The 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 TRUE 2.6.0 Many Devices include Sensors or have Sensors installed nearby, in order to measure critical input and output properties. This association indicates that relationship. Antecedent The Sensor. Dependent The LogicalDevice for which information is measured by the Sensor. 2.6.0 A 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. 64 InterpretationOfTrue is a string indicating what a 'True' value from the BinarySensor means. This information could be displayed to a user. 64 InterpretationOfFalse is a string indicating what a 'False' value from the BinarySensor means. This information could be displayed to a user. 2.6.0 A Multi-StateSensor is a multi-member set of Sensors. TRUE TRUE 2.6.0 The CollectionOfSensors association indicates the Sensors that make up a MultiStateSensor. GroupComponent TRUE 1 The MultiStateSensor. PartComponent 2 A Sensor that is part of the MultiStateSensor. 2.6.0 A 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. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 Unknown Other Degrees C Degrees F Degrees K Volts Amps Watts Joules Coulombs VA Nits Lumens Lux Candelas kPa PSI Newtons CFM RPM Hertz Seconds Minutes Hours Days Weeks Mils Inches Feet Cubic Inches Cubic Feet Meters Cubic Centimeters Cubic Meters Liters Fluid Ounces Radians Steradians Revolutions Cycles Gravities Ounces Pounds Foot-Pounds Ounce-Inches Gauss Gilberts Henries Farads Ohms Siemens Moles Becquerels PPM (parts/million) Decibels DbA DbC Grays Sieverts Color Temperature Degrees K Bits Bytes Words (data) DoubleWords QuadWords Percentage CIM_NumericSensor.UnitModifier CIM_NumericSensor.RateUnits The 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.BaseUnits CIM_NumericSensor.RateUnits Specifies 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. 0 1 2 3 4 5 6 7 8 9 None Per MicroSecond Per MilliSecond Per Second Per Minute Per Hour Per Day Per Week Per Month Per Year CIM_NumericSensor.UnitModifier CIM_NumericSensor.BaseUnits The 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 Percent Indicates 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. 0 1 2 3 4 5 LowerThresholdNonCritical UpperThresholdNonCritical LowerThresholdCritical UpperThresholdCritical LowerThresholdFatal UpperThresholdFatal An array representing the thresholds that are currently enabled for this Sensor. 0 1 2 3 4 5 LowerThresholdNonCritical UpperThresholdNonCritical LowerThresholdCritical UpperThresholdCritical LowerThresholdFatal UpperThresholdFatal An array representing the writable thresholds supported by Sensor. 0 1 2 3 4 5 LowerThresholdNonCritical UpperThresholdNonCritical LowerThresholdCritical UpperThresholdCritical LowerThresholdFatal UpperThresholdFatal This 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. FALSE FALSE TRUE FALSE TRUE FALSE TRUE FALSE TRUE 2.6.0 A 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. \nGiven 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. 64 The current value indicated by the Sensor. 64 PossibleValues enumerates the string outputs that can be reported by the DiscreteSensor. 64 AcceptableValues details which of the PossibleValues strings are considered 'acceptable' (ie, 'not an error'). 2.6.0 This 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. SensorType 2 BaseUnits 2 UnitModifier -1 RateUnits 0 CurrentReading MIF.DMTF|Temperature Probe|002.5 NominalReading MIF.DMTF|Temperature Probe|002.6 NormalMax MIF.DMTF|Temperature Probe|002.7 NormalMin MIF.DMTF|Temperature Probe|002.8 MaxReadable MIF.DMTF|Temperature Probe|002.9 MinReadable MIF.DMTF|Temperature Probe|002.10 Resolution Hundredths of Degrees C MIF.DMTF|Temperature Probe|002.17 Tolerance MIF.DMTF|Temperature Probe|002.18 Accuracy MIF.DMTF|Temperature Probe|002.19 LowerThresholdNonCritical MIF.DMTF|Temperature Probe|002.11 UpperThresholdNonCritical MIF.DMTF|Temperature Probe|002.12 LowerThresholdCritical MIF.DMTF|Temperature Probe|002.13 UpperThresholdCritical MIF.DMTF|Temperature Probe|002.14 LowerThresholdFatal MIF.DMTF|Temperature Probe|002.15 UpperThresholdFatal MIF.DMTF|Temperature Probe|002.16 2.6.0 This 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. SensorType 4 BaseUnits 6 UnitModifier -3 RateUnits 0 CurrentReading MIF.DMTF|Electrical Current Probe|001.5 NominalReading MIF.DMTF|Electrical Current Probe|001.6 NormalMax MIF.DMTF|Electrical Current Probe|001.7 NormalMin MIF.DMTF|Electrical Current Probe|001.8 MaxReadable MIF.DMTF|Electrical Current Probe|001.9 MinReadable MIF.DMTF|Electrical Current Probe|001.10 Resolution Tenths of MilliAmps MIF.DMTF|Electrical Current Probe|001.17 Tolerance MIF.DMTF|Electrical Current Probe|001.18 Accuracy MIF.DMTF|Electrical Current Probe|001.19 LowerThresholdNonCritical MIF.DMTF|Electrical Current Probe|001.11 UpperThresholdNonCritical MIF.DMTF|Electrical Current Probe|001.12 LowerThresholdCritical MIF.DMTF|Electrical Current Probe|001.13 UpperThresholdCritical MIF.DMTF|Electrical Current Probe|001.14 LowerThresholdFatal MIF.DMTF|Electrical Current Probe|001.15 UpperThresholdFatal MIF.DMTF|Electrical Current Probe|001.16 2.6.0 This 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. SensorType 3 BaseUnits 5 UnitModifier -3 RateUnits 0 CurrentReading MIF.DMTF|Voltage Probe|001.5 NominalReading MIF.DMTF|Voltage Probe|001.6 NormalMax MIF.DMTF|Voltage Probe|001.7 NormalMin MIF.DMTF|Voltage Probe|001.8 MaxReadable MIF.DMTF|Voltage Probe|001.9 MinReadable MIF.DMTF|Voltage Probe|001.10 Resolution Tenths of MilliVolts MIF.DMTF|Voltage Probe|001.17 Tolerance MIF.DMTF|Voltage Probe|001.18 Accuracy MIF.DMTF|Voltage Probe|001.19 LowerThresholdNonCritical MIF.DMTF|Voltage Probe|001.11 UpperThresholdNonCritical MIF.DMTF|Voltage Probe|001.12 LowerThresholdCritical MIF.DMTF|Voltage Probe|001.13 UpperThresholdCritical MIF.DMTF|Voltage Probe|001.14 LowerThresholdFatal MIF.DMTF|Voltage Probe|001.15 UpperThresholdFatal MIF.DMTF|Voltage Probe|001.16 2.6.0 This 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. SensorType 5 BaseUnits 38 UnitModifier 1 RateUnits 4 Resolution Tenths of Revolutions per Minute TRUE 2.6.0 A PowerSupply may have an associated VoltageSensor, monitoring its input voltage. This is described by this association. Antecedent The VoltageSensor. Dependent The PowerSupply associated with the VoltageSensor. Indicates 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. 0 1 2 3 4 Unknown Other Range 1 Range 2 Both Range 1 and 2 TRUE 2.6.0 A PowerSupply may have an associated CurrentSensor, monitoring its input frequency. This is described by this association. Antecedent The CurrentSensor. Dependent The PowerSupply associated with the CurrentSensor. Indicates 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. 0 1 2 3 4 Unknown Other Range 1 Range 2 Both Range 1 and 2 2.6.0 CIM_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 re-arming the watchdog at periodic intervals. 0 1 2 3 4 5 6 7 8 Unknown Other Operating System Operating System Boot Process Operating System Shutdown Process Firmware Boot Process BIOS Boot Process Application Service Processor 256 A string describing more textual information about the monitored entity The timeout interval used by the watchdog, in MicroSeconds. MicroSeconds Resolution of the timer. For example, if this value is 100, then the timer can expire anytime between (TimeoutInterval-100) microseconds or (TimeoutInterval+100) microseconds. MicroSeconds The time of the last timer expiry. Monitored entity at the time of last timer expiry. 0 1 2 3 4 5 6 7 8 Unknown Other Operating System Operating System Boot Process Operating System Shutdown Process Firmware Boot Process BIOS Boot Process Application Service Processor The action that should happen upon the expiry of the watchdog. 0 1 2 3 4 5 None - Status Only System Reset System Power Off System Power Off then On Generate 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.6.0 Capabilities 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). 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 48 49 50 51 52 53 54 55 64 65 66 67 68 69 80 81 82 83 84 85 86 87 88 96 97 98 99 100 101 112 120 121 128 130 144 145 146 147 148 149 150 160 176 177 178 179 180 181 190 200 201 202 250 251 260 261 280 281 300 301 302 320 350 500 Other Unknown 8086 80286 80386 80486 8087 80287 80387 80487 Pentium(R) brand Pentium(R) Pro Pentium(R) II Pentium(R) processor with MMX(TM) technology Celeron(TM) Pentium(R) II Xeon(TM) Pentium(R) III M1 Family M2 Family K5 Family K6 Family K6-2 K6-3 AMD Athlon(TM) Processor Family AMD(R) Duron(TM) Processor AMD29000 Family K6-2+ Power PC Family Power PC 601 Power PC 603 Power PC 603+ Power PC 604 Power PC 620 Power PC X704 Power PC 750 Alpha Family Alpha 21064 Alpha 21066 Alpha 21164 Alpha 21164PC Alpha 21164a Alpha 21264 Alpha 21364 MIPS Family MIPS R4000 MIPS R4200 MIPS R4400 MIPS R4600 MIPS R10000 SPARC Family SuperSPARC microSPARC II microSPARC IIep UltraSPARC UltraSPARC II UltraSPARC IIi UltraSPARC III UltraSPARC IIIi 68040 68xxx Family 68000 68010 68020 68030 Hobbit Family Crusoe(TM) TM5000 Family Crusoe(TM) TM3000 Family Weitek Itanium(TM) Processor PA-RISC Family PA-RISC 8500 PA-RISC 8000 PA-RISC 7300LC PA-RISC 7200 PA-RISC 7100LC PA-RISC 7100 V30 Family Pentium(R) III Xeon(TM) Pentium(R) III Processor with Intel(R) SpeedStep(TM) Technology Pentium(R) 4 Intel(R) Xeon(TM) AS400 Family Intel(R) Xeon(TM) processor MP K7 IBM390 Family G4 G5 i860 i960 SH-3 SH-4 ARM StrongARM 6x86 MediaGX MII WinChip DSP Video Processor MIF.DMTF|Processor|013 CIM_Processor.OtherFamilyDescription 64 A 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.Family CPU socket information including data on how this Processor can be upgraded (if upgrades are supported). This property is an integer enumeration. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 Other Unknown Daughter Board ZIF Socket Replacement/Piggy Back None LIF Socket Slot 1 Slot 2 370 Pin Socket Slot A Slot M Socket 423 Socket A (Socket 462) MIF.DMTF|Processor|013 The maximum speed (in MHz) of this Processor. MegaHertz MIF.DMTF|Processor|013 The current speed (in MHz) of this Processor. MegaHertz MIF.DMTF|Processor|013 Processor data width in bits. Bits Processor address width in bits. Bits TRUE Loading of this Processor, averaged over the last minute, in Percent. Percent MIB.IETF|HOST-RESOURCES-MIB.hrProcessorLoad Stepping is a free-form string indicating the revision level of the Processor within the Processor.Family. CIM_Processor.Family A 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. 0 1 2 3 4 7 Unknown CPU Enabled CPU Disabled by User via BIOS Setup CPU Disabled By BIOS (POST Error) CPU Is Idle Other 2.6.0 An 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. 0 1 2 3 4 5 6 Unknown Other Not Supported Informational Non-Critical Critical Unrecoverable The current state of the alarm. 0 1 2 3 Unknown Off Steady Alternating True 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. FALSE 0 1 2 3 Unknown Off Steady Alternating FALSE 0 1 2 No Change Disable Enable FALSE 0 1 2 No Change Disable Enable FALSE 0 1 2 No Change Disable Enable FALSE 1 3 4 5 6 Other Informational Non-Critical Critical Unrecoverable TRUE 2.6.0 LogicalDevices may have one or more AlarmDevices associated with them, in order to indicate problem situations. This relationship is indicated by the AssociatedAlarm dependency. Antecedent The AlarmDevice. Dependent The LogicalDevice that is alarmed. TRUE TRUE 2.6.0 Association indicating the processor(s) of a UnitaryComputerSystem. At least one processor is required. Note that this relationship inherits from the SystemDevice association, and therefore, the System Processor is weak to the aggregating UnitaryComputerSystem. GroupComponent TRUE The UnitaryComputerSystem. PartComponent The Processor which is part of the UnitaryComputerSystem. TRUE 2.6.0 An entity managed by BIOS and/or an OperatingSystem which is available for use by software and/or LogicalDevices. Examples of Resources in the x86 environment are IRQs, DMA channels and memory mapped I/O. Boolean indicating whether the Resource can be shared. 2.6.0 Personal computer architecture IRQ. CIM_ComputerSystem.CreationClassName TRUE 256 The scoping ComputerSystem's CreationClassName. CIM_ComputerSystem.Name TRUE 256 The scoping ComputerSystem's Name. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE A part of the object's key value, IRQ Number. MIF.DMTF|IRQ|002.1 Availability of the IRQ. 1 2 3 4 5 Other Unknown Available In Use/Not Available In Use and Available/Shareable MIF.DMTF|IRQ|002.2 IRQ trigger type indicating whether edge (value=4) or level triggered (value=3) interrupts occur. Also, "Other" (1) and "Unknown" (2) may be defined. 1 2 3 4 Other Unknown Level Edge MIF.DMTF|IRQ|002.3 MIF.DMTF|System Resource IRQ Info|001.2 IRQ 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. 1 2 3 4 Other Unknown Active Low Active High MIF.DMTF|System Resource IRQ Info|001.3 Shareable Boolean indicating whether the IRQ can be shared. MIF.DMTF|IRQ|002.4 The 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.0 Personal 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.CreationClassName TRUE 256 The scoping ComputerSystem's CreationClassName. CIM_ComputerSystem.Name TRUE 256 The scoping ComputerSystem's Name. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE A part of the object's key value, the starting address of memory mapped I/O. MIF.DMTF|Memory Mapped I/O|001.1 Ending address of memory mapped I/O. MIF.DMTF|Memory Mapped I/O|001.2 Type 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. 0 1 2 3 Other Mapped Memory I/O Mapped to Memory Space I/O Mapped to Port Space 2.6.0 Since 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.0 Since 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.0 Personal computer architecture DMA. CIM_ComputerSystem.CreationClassName TRUE 256 The scoping ComputerSystem's CreationClassName. CIM_ComputerSystem.Name TRUE 256 The scoping ComputerSystem's Name. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE A part of the object's key value, the DMA Channel number. MIF.DMTF|DMA|001.1 Availability of the DMA. 1 2 3 4 5 Other Unknown Available In Use/Not Available In Use and Available/Shareable MIF.DMTF|DMA|001.2 Indication that the DMA Channel supports burst mode. MIF.DMTF|DMA|001.3 An 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. Bits 0 8 16 32 64 128 MIF.DMTF|System Resource DMA Info|001.2 An integer indicating the DMA Channel address size in bits. Permissible values are 8, 16, 32 or 64 bits. If unknown, enter 0. Bits 0 8 16 32 64 MIF.DMTF|System Resource DMA Info|001.3 The maximum number of bytes that can be transferred by this DMA Channel. If unknown, enter 0. Bytes MIF.DMTF|System Resource DMA Info|001.4 Indicates whether DMA may execute in 'count by byte' mode (value=4) or not (value=3). Also, "Other" (1) and "Unknown" (2) may be defined. 1 2 3 4 Other Unknown Not execute in 'count by byte' mode Execute in 'count by byte' mode MIF.DMTF|System Resource DMA Info|001.7 Indicates whether DMA may execute in 'count by word' mode (value=4) or not (value=3). Also, "Other" (1) and "Unknown" (2) may be defined. 1 2 3 4 Other Unknown Not execute in 'count by word' mode Execute in 'count by word' mode MIF.DMTF|System Resource DMA Info|001.8 DMA channel timing. For example, "Type A" (value =4) or "Type F" (6) could be specified. 1 2 3 4 5 6 Other Unknown ISA Compatible Type A Type B Type F MIF.DMTF|System Resource DMA Info|001.9 Indicates whether C type (burst) timing is supported (value=5) or not (value=4). Also, "Other" (1), "Unknown" (2) and "ISA Compatible" (3) are defined. 1 2 3 4 5 Other Unknown ISA Compatible Not Supported Supported MIF.DMTF|System Resource DMA Info|001.10 TRUE TRUE 2.6.0 An association between a ComputerSystem and the SystemResources available on it. GroupComponent TRUE 1 1 The ComputerSystem. PartComponent A SystemResource of the ComputerSystem. TRUE TRUE 2.6.0 An association between a ComputerSystem and the IRQs available on it. PartComponent TRUE An IRQ of the ComputerSystem. TRUE TRUE 2.6.0 An association between a ComputerSystem and the Memory Mapped I/O ports available on it. PartComponent TRUE A memory mapped I/O port of the ComputerSystem. TRUE TRUE 2.6.0 An association between a ComputerSystem and the DMA channels available on it. PartComponent TRUE A DMA channel of the ComputerSystem. TRUE 2.6.0 An association between LogicalDevices and SystemResources, indicating that the Resource is assigned to the Device. Antecedent The Resource. Dependent The LogicalDevice to which the Resource is assigned. TRUE 2.6.0 An association between a LogicalDevice and a DMA SystemResource indicating that the DMA Channel is assigned to the Device. Antecedent The DMA Channel. Boolean indicating whether the LogicalDevice can act as a bus master on the DMA Channel. MIF.DMTF|System Resource DMA Info|001.6 2.6.0 VideoBIOSFeature 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. 1 2 3 4 5 6 7 8 9 Other Unknown Undefined Standard Video BIOS VESA BIOS Extensions Supported VESA Power Management Supported VESA Display Data Channel Supported Video BIOS Shadowing Allowed Video BIOS Upgradeable Indexed MIF.DMTF|Video BIOS Characteristic|001.3 CIM_VideoBIOSFeature.CharacteristicDescriptions An 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. Indexed MIF.DMTF|Video BIOS Characteristic|001.4 CIM_VideoBIOSFeature.Characteristics 2.6.0 VideoBIOSElement 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. Version MIF.DMTF|Video BIOS|001.3 Manufacturer MIF.DMTF|Video BIOS|001.2 If true, indicates that the Video BIOS is shadowed. MIF.DMTF|Video BIOS|001.5 Date that this BIOS was released. MIF.DMTF|Video BIOS|001.4 TRUE TRUE 2.6.0 A link between VideoBIOSFeature and its aggregated VideoBIOSElements. GroupComponent TRUE The VideoBIOSFeature. PartComponent The VideoBIOSElement that implements the capabilities described by VideoBIOSFeature. TRUE 2.6.0 The DeviceSoftware relationship identifies any software that is associated with a Device - such as drivers, configuration or application software, or firmware. Antecedent The SoftwareElement. Dependent The LogicalDevice that requires or uses the software. An 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). 0 1 2 3 4 5 6 7 8 Unknown Other Driver Configuration Software Application Software Instrumentation Firmware BIOS Boot ROM CIM_DeviceSoftware.PurposeDescription MIF.DMTF|SubComponent Software|001.2 A free-form string to provide more information for the Purpose property, e.g. "Application Software". CIM_DeviceSoftware.Purpose Boolean 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.6.0 AGPSoftwareFeature 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. Indexed 0 1 2 3 4 5 6 Unknown Other OS support Hardware Acceleration Hardware Blit OpenGL Support Cache Coherency CIM_AGPSoftwareFeature.CharacteristicDescriptions An 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. Indexed CIM_AGPSoftwareFeature.Characteristics 2.6.0 DeviceErrorCounts 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). CIM_LogicalDevice.SystemCreationClassName TRUE 256 The scoping System's CreationClassName. CIM_LogicalDevice.SystemName TRUE 256 The scoping System's Name. CIM_LogicalDevice.CreationClassName TRUE 256 The scoping Device's CreationClassName. CIM_LogicalDevice.DeviceID TRUE 64 The scoping Device's ID. Name TRUE 256 The 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. TRUE Count of the critical errors. MIF.DMTF|Operational State|006 TRUE Count of the major errors. MIF.DMTF|Operational State|006 TRUE Count of the minor errors. TRUE Count of the warnings. MIF.DMTF|Operational State|006 TRUE FALSE 0 1 2 3 4 5 All Indeterminate Error Counter Critical Error Counter Major Error Counter Minor Error Counter Warning Counter TRUE 2.6.0 ErrorCountersForDevice relates the DeviceErrorCounts class to the LogicalDevice to which it applies. Stats TRUE The statistical object - in this case, the error counter class. Element 1 1 The Device to which the error counters apply. 2.6.0 Error and event counters specific to a Fibre Channel Adapter. The number of Abort sequence frames received. TRUE The number of Abort sequence frames sent. TRUE The number of frames busied by the Fabric. TRUE The number of frames busied by the receiving Node. TRUE The number of frames busied by the Adapter itself. TRUE The number of frames rejected by the Fabric. TRUE The number of frames rejected by the receiving Node. TRUE The number of frames rejected by the Adapter itself. TRUE The number of PRLI frames sent where the response was LS_RJT. TRUE The number of PRLO frames sent where the response was LS_RJT. TRUE The number of Abort sequence frames sent where the response was BA_RJT. TRUE FALSE 0 1 2 3 4 5 6 7 8 9 10 11 All ABTSFramesReceived ABTSFramesSent FBSYReceived PBSYReceived PBSYSent FRJTReceived PRJTReceived PRJTSent PRLIRejected PRLORejected ABTSFramesRejected 2.6.0 Error and event counters specific to a Fibre Channel Port (connection point). The number of login frames received. TRUE The number of login frames sent. TRUE Number of frames received containing 'EOF Abort'. TRUE Number of frames transmitted containing 'EOF Abort'. TRUE The number of logouts received from various targets. TRUE The number of logout frames sent. TRUE The number of PLOGI frames sent where the response was LS_RJT. TRUE The number of PLOGO frames sent where the response was LS_RJT. TRUE FALSE 0 1 2 3 4 5 6 7 8 All PLOGIsReceived PLOGIsSent EOFAbortsReceived EOFAbortsTransmitted PLOGOsReceived PLOGOsSent PLOGIsRejected PLOGOsRejected 2.6.0 Statistics for a LabelReader, related to read successes, failures and retries. The number of successful physical label scans. TRUE The number of failed physical label scans. TRUE The number of retried physical label scans. TRUE FALSE 0 1 2 3 All Scan Successes Scan Failures Scan Retries 2.6.0 Statistics 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). The number of attempted read operations. TRUE The number of unrecoverable read operations. TRUE The number of attempted write operations. TRUE The number of unrecoverable write operations. TRUE The number of recovered read operations. TRUE The number of recovered write operations. TRUE The number of recovered seek operations. TRUE The number of unrecoverable seek operations. TRUE FALSE 0 1 2 3 4 5 6 7 8 All Read Operations Unrecoverable Read Operations Write Operations Unrecoverable Write Operations Recovered Read Operations Recovered Write Operations Recovered Seeks Unrecoverable Seeks 2.6.0 Statistics for a PickerElement, related to pick/put successes, retries and failures. The number of successful picks. TRUE The number of failed picks. TRUE The number of retried picks. TRUE The number of successful puts. TRUE The number of failed puts. TRUE The number of retried puts. TRUE FALSE 0 1 2 3 4 5 6 All Pick Successes Pick Failures Pick Retries Put Successes Put Failures Put Retries TRUE 2.6.0 Controller 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 primarily for communication to, and control or reset of downstream (ControlledBy) Devices. Time of last reset of the Controller. The protocol used by the Controller to access 'controlled' Devices. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 Other Unknown EISA ISA PCI ATA/ATAPI Flexible Diskette 1496 SCSI Parallel Interface SCSI Fibre Channel Protocol SCSI Serial Bus Protocol SCSI Serial Bus Protocol-2 (1394) SCSI Serial Storage Architecture VESA PCMCIA Universal Serial Bus Parallel Protocol ESCON Diagnostic I2C Power HIPPI MultiBus VME IPI IEEE-488 RS232 IEEE 802.3 10BASE5 IEEE 802.3 10BASE2 IEEE 802.3 1BASE5 IEEE 802.3 10BROAD36 IEEE 802.3 100BASEVG IEEE 802.5 Token-Ring ANSI X3T9.5 FDDI MCA ESDI IDE CMD ST506 DSSI QIC2 Enhanced ATA/IDE AGP TWIRP (two-way infrared) FIR (fast infrared) SIR (serial infrared) IrBus MIF.DMTF|Bus Port|003 MIF.DMTF|Disks|003.3 CIM_Controller.ProtocolDescription Maximum 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|003 A free form string providing more information related to the ProtocolSupported by the Controller. CIM_Controller.ProtocolSupported MIF.DMTF|Bus Port|003 TRUE 2.6.0 The ControlledBy relationship indicates which Devices are commanded by or accessed through the Controller LogicalDevice. Antecedent The Controller. Dependent The controlled Device. The 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. 0 1 2 Unknown Active Inactive The 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. TRUE Number 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.0 Capabilities 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. Indexed 1 2 3 4 5 6 160 161 Other Unknown XT/AT Compatible 16450 Compatible 16550 Compatible 16550A Compatible 8251 Compatible 8251FIFO Compatible MIF.DMTF|Serial Ports|004.7 CIM_SerialController.CapabilityDescriptions An 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. Indexed CIM_SerialController.Capabilities Maximum baud rate in Bits per Second supported by the SerialController. Bits per Second MIF.DMTF|Serial Ports|004.6 An 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. 1 2 3 4 5 6 Other Unknown None External Interface Locked Out External Interface Enabled Boot Bypass MIF.DMTF|Serial Ports|004.9 TRUE 2.6.0 SerialInterface is a ControlledBy relationship indicating which Devices are accessed through the SerialController and the characteristics of this access. Antecedent The SerialController. NegotiatedDataWidth For the SerialInterface, NegotiatedDataWidth is the number of data bits to be transmitted, without stop bits or parity. Bits Number of stop bits to be transmitted. Bits Information on the parity setting for transmitted data. No parity (value=1), even (2) or odd (3) can be specified. 0 1 2 3 Unknown None Even Odd An integer enumeration indicating the flow control (Xon-Xoff and/or RTS/CTS) for transmitted data. 0 1 2 3 4 5 Unknown Not Supported None XonXoff RTS/CTS Both XonXoff and RTS/CTS 2.6.0 Capabilities and management of the SCSIController. An integer enumeration indicating whether or not the SCSIController provides redundancy or protection against device failures. 1 2 3 4 5 6 Other Unknown Unprotected Protected Protected through SCC (SCSI-3 Controller Command) Protected through SCC-2 (SCSI-3 Controller Command) MIF.DMTF|Storage Controller|001.3 Maximum data width (in bits) supported by the SCSIController. Bits MIF.DMTF|Bus Port|003 Maximum transfer rate (in Bits per Second) supported by the SCSIController. Bits per Second MIF.DMTF|Bus Port|003 Number of SCSIController timeouts that have occurred since the TimeOfLastReset. TRUE Signal 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. 1 2 3 4 5 6 Other Unknown Single Ended Differential Low Voltage Differential Optical CIM_SCSIInterface.SCSISignal TRUE 2.6.0 SCSIInterface is a ControlledBy relationship indicating which Devices are accessed through a SCSIController and the characteristics of this access. Antecedent The SCSIController. Number 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. TRUE Number 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. TRUE MIF.DMTF|Mass Storage Statistics|001.18 The SCSI Initiator ID. MIF.DMTF|Bus Port|003 The SCSI Target ID. MIF.DMTF|Bus Port|003 The SCSI Target LUN. MIF.DMTF|Storage Devices|001.4 SCSIReservation indicates the type of SCSI reservation that currently exists between the source and destination. 0 1 2 3 Unknown None Simple Persistent The SCSI signal characteristics being used for this connection. The value listed here must also be listed in the SCSIController's SignalCapabilities field. 1 2 3 4 5 6 Other Unknown Single Ended Differential Low Voltage Differential Optical MIF.DMTF|Bus Port|003 CIM_SCSIController.SignalCapabilities Maximum 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.0 Capabilities and management of the VideoController. Description MIF.DMTF|Video|004.18 A free-form string describing the video processor/Controller. An integer enumeration indicating the type of video memory. 1 2 3 4 5 6 7 8 9 10 11 12 13 Other Unknown VRAM DRAM SRAM WRAM EDO RAM Burst Synchronous DRAM Pipelined Burst SRAM CDRAM 3DRAM SDRAM SGRAM MIF.DMTF|Video|004.6 Number of video pages supported given the current resolutions and available memory. Maximum amount of memory supported in bytes. Bytes An array of integers indicating the graphics and 3D capabilities of the VideoController. 0 1 2 3 Unknown Other Graphics Accelerator 3D Accelerator CIM_VideoController.CapabilityDescriptions An 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. Indexed CIM_VideoController.AcceleratorCapabilities The number of bits used to display each pixel. Bits MIF.DMTF|Video|004.12 Current number of horizontal pixels. Pixels MIF.DMTF|Video|004.11 Current number of vertical pixels. Pixels MIF.DMTF|Video|004.10 Maximum refresh rate of the VideoController in Hertz. Hertz MIF.DMTF|Video|004.5 Minimum refresh rate of the Video Controller in Hertz. Hertz MIF.DMTF|Video|004.4 Current refresh rate in Hertz. Hertz MIF.DMTF|Video|004.15 Current scan mode. "Interlaced" (value=3) or "Non Interlaced" (4) can be defined using this property. 1 2 3 4 Other Unknown Interlaced Non Interlaced MIF.DMTF|Video|004.8 If in character mode, number of rows for this VideoController. Otherwise, enter 0. MIF.DMTF|Video|004.13 If in character mode, number of columns for this VideoController. Otherwise, enter 0. MIF.DMTF|Video|004.14 Number of colors supported at the current resolutions. 2.6.0 Capabilities and management of a PCVideoController, a subtype of VideoController. The video architecture. For example, VGA (value=5) or PC-98 (160) may be specified. 1 2 3 4 5 6 7 8 9 10 11 12 160 Other Unknown CGA EGA VGA SVGA MDA HGC MCGA 8514A XGA Linear Frame Buffer PC-98 MIF.DMTF|Video|004.2 Current video mode. MIF.DMTF|Video|004.3 Current number of color planes. If this value is not applicable for the current video configuration, enter 0. 2.6.0 Capabilities and management of an AGPVideoController. 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. Indexed 0 1 2 3 4 5 6 Unknown Other PCI Fast Write MultiMonitor Support PCI Mastering Second Monochrome Adapter Support Large Memory Address Support CIM_AGPVideoController.CapabilityDescriptions An array of free form strings providing more detailed explanations for any of the entries 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. Indexed CIM_AGPVideoController.Capabilities Size of the non-local video memory in KB. KiloBytes Width of the internal bus in the graphics Controller, in bits. Bits An 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. 0 1 2 3 4 Unknown Other Execute DMA Both An integer enumeration indicating the data transfer rate of the graphics Controller. 0 1 2 3 4 Unknown Other 1X 2X 4X An integer enumeration indicating the addressing mode of the graphics Controller. 0 1 2 3 Unknown Other Sideband Pipeline The 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. KiloBytes A string containing the AGP specification version to which this graphics Controller conforms. 2.6.0 Capabilities and management of the ParallelController. Set to true if the ParallelController supports DMA. MIF.DMTF|Parallel Ports|003.7 An integer enumeration indicating the capabilities of the ParallelController. Indexed 0 1 2 3 4 5 6 7 8 Unknown Other XT/AT Compatible PS/2 Compatible ECP EPP PC-98 PC-98-Hireso PC-H98 MIF.DMTF|Parallel Ports|003.8 CIM_ParallelController.CapabilityDescriptions An 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. Indexed CIM_ParallelController.Capabilities An 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. 1 2 3 4 5 6 Other Unknown None External Interface Locked Out External Interface Enabled Boot Bypass MIF.DMTF|Parallel Ports|003.10 2.6.0 Capabilities and management of an SSAController (Serial Storage Architecture). 2.6.0 Capabilities and managment of a ManagementController. An I2C microcontroller is a type of ManagementController. 2.6.0 Capabilities and management of an IDEController. 2.6.0 Capabilities and management of an InfraredController. 2.6.0 PCIController 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. Indexed 0 1 2 3 4 5 6 7 8 9 10 11 12 Unknown Other Supports 66MHz Supports User Definable Features Supports Fast Back-to-Back Transactions PCI-X Capable PCI Power Management Supported Message Signaled Interrupts Supported Parity Error Recovery Capable AGP Supported Vital Product Data Supported Provides Slot Identification Hot Swap Supported CIM_PCIController.CapabilityDescriptions An 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. Indexed CIM_PCIController.Capabilities The slowest device select timing for a target device. 0 1 2 3 4 5 Unknown Other Fast Medium Slow Reserved Register 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. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18..254 255 Pre 2.0 Mass Storage Network Display Multimedia Memory Bridge Simple Communications Base Peripheral Input Docking Station Processor Serial Bus Wireless Intelligent I/O Satellite Communication Encryption/Decryption Data Acquisition and Signal Processing PCI Reserved Other Specifies 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. DoubleWords Defines the minimum amount of time, in PCI clock cycles, that the bus master can retain ownership of the bus. PCI clock cycles Defines the PCI interrupt request pin (INTA# to INTD#) to which a PCI functional device is connected. 0 1 2 3 4 5 None INTA# INTB# INTC# INTD# Unknown Doubleword Expansion ROM base memory address. DoubleWords Reports 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.0 Capabilities 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 nanoseconds Register specifying how often the device needs access to the PCI bus in 250ns. A zero value indicates no requirement. 250 nanoseconds 2.6.0 Capabilities 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. 0 1 2 3 4 5 6 7 8 128 Host ISA EISA Micro Channel PCI PCMCIA NuBus CardBus RACEway Other The timeslice for the secondary interface when the bridge is acting as an initiator. A zero value indicates no requirement. PCI clock cycles The 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. 0 1 2 3 4 5 Unknown Other Fast Medium Slow Reserved End 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.6.0 Capabilities and management of a PCMCIAController. 2.6.0 Capabilities and management of an ESCONController. 2.6.0 Capabilities 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. 0 1 2 3 Unknown Other UHCI OHCI CIM_USBController.ControllerVersion Indicates 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.6.0 The abstraction of a port or connection point of a Device. This object should be instantiated when the Port has independent management characteristics from the Device that includes it. Examples are a Fibre Channel Port and a USB Port. This class would not be instantiated for an Ethernet Port which is not managed independently of the EthernetAdapter. The speed of the Port in Bits per Second. Bits per Second The max speed of the Port in Bits per Second. Bits per Second TRUE 2.6.0 PortOnDevice associates a Port or connection point with its Device. Antecedent The Device that includes the Port. Dependent The Port on the Device. TRUE 2.6.0 NetworkAdapter is an Abstract class defining general networking hardware concepts (for example, PermanentAddress or Speed of operation). NetworkAdapters are Devices with the ability to support multiple, higher level protocols and provide the implementation behind the Network Model's ProtocolEndpoint class. (This information is conveyed using the DeviceSAPImplementation association, defined in the Core Model.) NetworkAdapters and their Endpoints represent the potential for connectivity among peers. \nThe 'potential for connectivity' is very different than the master-slave/controller-controlled by relationships of CIM_Controller. Sometimes, however, a single Device is both a kind of NetworkAdapter and a Controller - for example, when a FibreChannelAdapater is operating as a ComputerSystem's SCSIController. In this case, there are aspects of the Device that are network oriented and others that are Controller oriented - and, both the Controller and Adapter classes should be instantiated. A DeviceIdentity relationship would also be created to tie together these differing aspects/abstractions of the Device. 64 PermanentAddress 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.2 64 An array of strings indicating the network addresses for an adapter. Indexed MIF.DMTF|Network Adapter 802 Port|001.3 An 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 Second MIB.IETF|RFC1213-MIB.ifSpeed MIF.DMTF|Network Adapter 802 Port|001.5 The maximum speed, in Bits per Second, for the NetworkAdapter. Bits per Second Boolean indicating that the Adapter is operating in full duplex mode. A boolean indicating whether the NetworkAdapter is capable of automatically determining the speed or other communications characteristics of the attached network media. The total number of octets transmitted, including framing characters. MIB.IETF|RFC1213-MIB.ifOutOctets MIF.DMTF|Network Adapter 802 Port|001.7 TRUE The total number of octets received, including framing characters. MIB.IETF|RFC1213-MIB.ifInOctets MIF.DMTF|Network Adapter 802 Port|001.9 TRUE 2.6.0 Capabilities and management of an EthernetAdapter. NetworkAddresses Ethernet/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.) Indexed The maximum size of the INFO (non-MAC) field that will be received or transmitted. MIB.IETF|BRIDGE-MIB.dot1dTpPortMaxInfo Capabilities 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. Indexed 0 1 2 3 4 5 Unknown Other AlertOnLan WakeOnLan FailOver LoadBalancing CIM_EthernetAdapter.CapabilityDescriptions An 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. Indexed CIM_EthernetAdapter.Capabilities Specifies which capabilities are enabled from the list of all supported ones, defined in the Capabilities array. 0 1 2 3 4 5 Unknown Other AlertOnLan WakeOnLan FailOver LoadBalancing CIM_EthernetAdapter.Capabilities The 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.dot3StatsSymbolErrors TRUE The total number of packets transmitted. MIF.DMTF|Network Adapter 802 Port|001.6 TRUE The total number of packets received. MIF.DMTF|Network Adapter 802 Port|001.8 TRUE A 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.dot3StatsAlignmentErrors TRUE A 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.dot3StatsFCSErrors TRUE A 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.dot3StatsSingleCollisionFrames TRUE A 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.dot3StatsMultipleCollisionFrames TRUE A 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.dot3StatsSQETestErrors TRUE A 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.dot3StatsDeferredTransmissions TRUE The 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.dot3StatsLateCollisions TRUE A count of frames for which transmission on a particular interface fails due to excessive collisions. MIB.IETF|EtherLike-MIB.dot3StatsExcessiveCollisions TRUE A 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.dot3StatsInternalMacTransmitErrors TRUE A 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.dot3StatsInternalMacReceiveErrors TRUE The 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.dot3StatsCarrierSenseErrors TRUE A 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 TRUE 2.6.0 Capabilities and management of a TokenRingAdapter. NetworkAddresses Token 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.) Indexed The maximum size of the INFO (non-MAC) field that will be received or transmitted. MIB.IETF|BRIDGE-MIB.dot1dTpPortMaxInfo Capabilities 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. Indexed 0 1 2 3 4 5 Unknown Other AlertOnLan WakeOnLan FailOver LoadBalancing CIM_TokenRingAdapter.CapabilityDescriptions An 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. Indexed CIM_TokenRingAdapter.Capabilities Specifies which of the capabilities from the "Capabilities" property are currently enabled. 0 1 2 3 4 5 Unknown Other AlertOnLan WakeOnLan FailOver LoadBalancing CIM_TokenRingAdapter.Capabilities The 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:\n0 = 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.dot5RingStatus The current Device state with respect to entering or leaving the ring. 0 1 2 3 4 5 Opened Closed Opening Closing Open Failure Ring Failure MIB.IETF|IEEE 802.5 Token Ring MIB.dot5RingState This property indicates the success, or the reason for failure, of the station's most recent attempt to enter the ring. 0 1 2 3 4 5 6 7 8 9 10 No Open Attempted Bad Parameter Lobe Failed Signal Loss Insertion Timeout Ring Failed Beaconing Duplicate MAC Request Failed Remove Received Last Open Successful MIB.IETF|IEEE 802.5 Token Ring MIB.dot5RingOpenStatus The ring's bandwidth. 0 1 2 3 4 Unknown Other One Megabit Four Megabit Sixteen Megabit MIB.IETF|IEEE 802.5 Token Ring MIB.dot5RingSpeed This 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.dot5StatsBurstErrors TRUE This 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.dot5StatsACErrors TRUE This counter is incremented when a station transmits an abort delimiter while transmitting data. MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsAbortTransErrors TRUE This counter is incremented when a station recognizes an internal error. MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsInternalErrors TRUE This 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.dot5StatsLostFrameErrors TRUE This 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.dot5StatsReceiveCongestions TRUE This 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.dot5StatsFrameCopiedErrors TRUE This 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.dot5StatsTokenErrors TRUE The 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.dot5StatsSoftErrors TRUE The 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.dot5StatsHardErrors TRUE The number of times this Device has detected the loss of signal condition from the ring. MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsSignalLoss TRUE The number of times this Device has transmitted a beacon frame. MIB.IETF|IEEE 802.5 Token Ring MIB.dot5StatsTransmitBeacons TRUE The 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.dot5StatsRecoverys TRUE The 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.dot5StatsLobeWires TRUE The 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.dot5StatsRemoves TRUE The 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.dot5StatsSingles TRUE The 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 TRUE 2.6.0 Capabilities and management of a Fibre Channel Adapter. The maximum frame size, in bytes, supported by the Adapter. Bytes The 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. 0 1 2 3 4 5 6 Unknown 1 2 3 4 6 F An 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. 0 1 4 5 8 9 17 18 19 21 22 23 25 26 27 28 32 34 36 64 80 81 82 88 96 255 Unknown Other ISO/IEC 8802 - 2 LLC IP over FC SCSI - FCP SCSI - GPP IPI - 3 Master IPI - 3 Slave IPI - 3 Peer CP IPI - 3 Master CP IPI - 3 Slave CP IPI - 3 Peer SBCCS Channel SBCCS Control Unit FC-SB-2 Channel FC-SB-2 Control Unit Fibre Channel Services (FC-GS FC-GS-2 FC-GS-3) FC-SW FC - SNMP HIPPI - FP BBL Control BBL FDDI Encapsulated LAN PDU BBL 802.3 Encapsulated LAN PDU FC - VI FC - AV Vendor Unique CIM_FibreChannelAdapter.FC4VendorUniqueTypes 240 255 When 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. An 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. 0 1 4 5 8 9 17 18 19 21 22 23 25 26 27 28 32 34 36 64 80 81 82 88 96 255 Unknown Other ISO/IEC 8802 - 2 LLC IP over FC SCSI - FCP SCSI - GPP IPI - 3 Master IPI - 3 Slave IPI - 3 Peer CP IPI - 3 Master CP IPI - 3 Slave CP IPI - 3 Peer SBCCS Channel SBCCS Control Unit FC-SB-2 Channel FC-SB-2 Control Unit Fibre Channel Services (FC-GS FC-GS-2 FC-GS-3) FC-SW FC - SNMP HIPPI - FP BBL Control BBL FDDI Encapsulated LAN PDU BBL 802.3 Encapsulated LAN PDU FC - VI FC - AV Vendor Unique CIM_FibreChannelAdapter.FC4TypesSupported CIM_FibreChannelAdapter.CurrentFC4VendorTypes 240 255 When 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.FC4VendorUniqueTypes A 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. Indexed 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Unknown Other Utilizes the Directory Server Utilizes the Time Server Utilizes the Management Server Utilizes the Alias Server Utilizes the Security Key Distribution Server Utilizes the Clock Synchronization Server Utilizes the Multicast Server Utilizes QoS Facilitator Utilizes Broadcast Services Supports Fabric Login Server Generates State Change Notifications Registers for State Change Notifications Responds to Read Connection Status Supports Third Party Process Logout An 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. Indexed CIM_FibreChannelAdapter.Capabilities The number of times that a frame was received but no buffer was available. TRUE The number of times that a frame was received but no end-to-end credit was available. TRUE A '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). MilliSeconds A 'short' timeout value (in milliseconds) for determining that an error has occurred. The default value is 10 seconds (10000 milliseconds). MilliSeconds Number of Class 1 sequences sent since last reset of the Device. TRUE Number of Class 2 sequences sent since last reset of the Device. TRUE Number of Class 3 sequences sent since last reset of the Device. TRUE Number of Class 4 sequences sent since last reset of the Device. TRUE Number of octets received by the Adapter when running Class 2 service. TRUE Number of octets transmitted by the Adapter when running Class 2 service. TRUE Number of frames received by the Adapter when running Class 2 service. TRUE Number of frames transmitted by the Adapter when running Class 2 service. TRUE Number of frames discarded by the Adapter when running Class 2 service. TRUE Number of octets received by the Adapter when running Class 3 service. TRUE Number of octets transmitted by the Adapter when running Class 3 service. TRUE Number of frames received by the Adapter when running Class 3 service. TRUE Number of frames transmitted by the Adapter when running Class 3 service. TRUE Number of frames discarded by the Adapter when running Class 3 service. TRUE Number of parity errors detected somewhere in the data path. TRUE Number of Class 1 or 2 frames that are not ACKed within the time indicated by ErrorDetectTimeout. TRUE Number of times that the Device has been without a buffer credit for a time longer than ErrorDetectTimeout. TRUE Number of times that the Device has been without an end credit for a time longer than ErrorDetectTimeout. TRUE Number of frames received out of order. TRUE 2.6.0 Capabilities and management of a Fibre Channel Port Device. An 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. An 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. \n\nA 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. Indexed 0 1 2 3 4 5 6 7 Unknown N NL-Private NL-Public E F FL B CIM_FibrePort.PortTypeVersions Version 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. Indexed CIM_FibrePort.SupportedPortTypes The specific modes currently enabled for the Port. The values are equal to, or a subset of the values in the SupportedPortTypes array. 0 1 2 3 4 5 6 7 Unknown N NL-Private NL-Public E F FL B CIM_FibrePort.SupportedPortTypes CIM_FibrePort.EnabledVersions Version 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. Indexed CIM_FibrePort.EnabledPortTypes The 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). 0 1 2 3 4 5 6 7 Unknown N NL-Private NL-Public E F FL B CIM_FibrePort.EnabledPortTypes CIM_FibrePort.CurrentVersion Version information for the CurrentPortType that is active. CIM_FibrePort.CurrentPortType One 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. Number of times that signal is lost on the Port since last reset of the Device. TRUE Number 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. TRUE Number of times that the CRC in a frame does not match the CRC computed by the receiver. TRUE The 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. TRUE The 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. TRUE The 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. TRUE The 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. TRUE The 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. TRUE Timeout value in milliseconds used to determine when loss of synchronization has occurred. The typical default is 100 msec. Milliseconds Indication 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". 0 1 2 3 Unknown Not Bypassed Bypassed Forced Insert The 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. 0 1 2 3 4 5 6 Unknown Other No Media Copper/Twinaxial Fiber-optic Fiber Single Mode Fiber Multimode TRUE 2.6.0 FibrePortOnFCAdapter associates a FibrePort with a FibreChannelAdapter. Cardinalities are defined as Max (1) to indicate the intent and usage of the model - that an Adapter is synonymous with its Port (connection point). Where you have a multi-Port Adapter and more than one Port may be active at a time, individual Adapters with individual operating data and characteristics really exist. If you have multiple connection points, but they exist only to provide multiple physical form factors (only one connection may be active at a time), then one FibreChannelAdapter and one FibrePort (the active one) exist. On the hardware side, the realizations of these entities in PhysicalElements may be as a CIM_Card (for example) with multiple CIM_PhysicalConnectors. Antecedent 1 The FibreChannelAdapter that includes the Port. Dependent 1 The FibrePort on the Adapter. TRUE 2.6.0 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. \nThe class' key is composed of the login originator's and responder's keys plus the Class Of Service. This combination is unique and prevents subclassing FibrePortActiveLogin from its reasonable superclass, DeviceConnection. TRUE The originator of the login. TRUE The responder to the login. TRUE The 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. 0 1 2 3 4 5 6 Unknown 1 2 3 4 6 F CIM_FibreChannelAdapter.SupportedCOS MIF.DMTF|Fibre Channel Bus Port Extensions|001.5 The Fibre Channel frame size, in bytes, that is currently negotiated between the two Ports. Bytes The 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 Second Acknowledgement model negotiated during Port login. For example, ACK-1 indicates that each frame should be acknowledged. 0 1 2 3 Unknown ACK-0 ACK-1 ACK-N MIF.DMTF|Fibre Channel Bus Port Extensions|001.6 The 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. 0 1 2 Unknown Regular Alternate OriginatorBufferCredit 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.3 ResponderBufferCredit 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.3 OriginatorEndCredit 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.2 ResponderEndCredit 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.6.0 The management characterisitics of a USB Device. These 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.CurrentAlternateSettings An 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.CurrentConfigValue FALSE RequestType 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. FALSE RequestValue 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. FALSE RequestIndex 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. FALSE TRUE On 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. FALSE TRUE Buffer returns the requested Descriptor information. If the Descriptor does not exist, the contents of the Buffer are undefined. 2.6.0 USB 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.0 A Port on a USBHub. Speed USB 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. 0 1 1500000 12000000 StatusInfo Indicates whether the Port is currently enabled. 2 3 4 Unknown Enabled Disabled Availability Indicates whether the Port is currently Powered. 2 3 7 Unknown Running/Full Power Power Off The 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). 0 1 2 3 Unknown Other 1 Unit Load 5 Unit Loads Indicates whether the Port is currently Suspended. Indicates whether the Port is disabled due to an overcurrent event. TRUE 2.6.0 USBPortOnHub associates a USBPort or connection point with the USBHub that includes it. Antecedent 1 1 The Hub that includes the USBPort. Dependent 1 The Port on the USBHub. TRUE 2.6.0 USBControllerHasHub defines the Hub(s) that are downstream of the USBController. Antecedent 1 1 The USBController. Dependent 1 The USBHub that is associated with the Controller. TRUE 2.6.0 USBConnection associates a Device with the USBPort to which it is connected. Antecedent 1 The USBPort. Dependent 1 The USBDevice that is connected to the Port. TRUE 2.6.0 CIM_Modem is the superclass for grouping the numerous types of Modems. TRUE 2.6.0 CIM_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.0 The DSLModem class represents the superclass for Digital Subscriber Line (DSL) Devices. Properties will be defined in a future release of the model. 2.6.0 The 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. 2.6.0 The 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.0 The 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.0 The 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 Decibels TRUE Measured 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 Decibels Status indicates the current state of the connection (line). The property holds a bitmap describing the possible conditions. For example, \n1) No Defect - There no defects on the line; \n2) Loss Of Framing - ATUR failure due to not receiving valid frame; \n4) Loss Of Signal - ATUR failure due to not receiving signal; \n8) Loss Of Power - ATUR failure due to loss of power; \n32) 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. 1 2 4 8 32 No Defect Loss Of Framing Loss Of Signal Loss Of Power Loss Of Signal Quality TRUE Measured total output power (in tenths of dB) transmitted by this Modem. Tenths of Decibels Indicates 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.0 The CableModem class represents a device for transmission across a cable infrastructure. TRUE 2.6.0 CIM_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. 0 1 2 3 4 5 6 7 8 9 Unknown Other No Compression MNP 5 V.42bis MNP 3 MNP 4 V.58 PEP HST CIM_CallBasedModem.OtherCompressionDescription Description 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.CompressionSupported Describes the current data compression characteristics of the Modem. 0 1 2 3 4 5 6 7 8 9 Unknown Other No Compression MNP 5 V.42bis MNP 3 MNP 4 V.58 PEP HST CIM_CallBasedModem.CompressionSupported CIM_CallBasedModem.OtherCompressionInfoDescription Description of the current compression type when "Other" (value=1) is specified in the CompressionInfo property. CIM_CallBasedModem.CompressionInfo An 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. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 Unknown Other Not Supported Bell 103 Bell 212A V.22bis V.32 V.32bis V.terbo V.FC V.34 V.34bis V.17 (G3 Fax Call) V.21 V.22 V.23 Constant Carrier (1200/75) V.23 Switched Carrier (Half Duplex) V.26bis V.26ter V.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.58 X2 K56FLEX V.Fast PEP HST CIM_CallBasedModem.OtherModulationDescription Description 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.ModulationSupported Describes the current modulation scheme of the Modem. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 Unknown Other Not Supported Bell 103 Bell 212A V.22bis V.32 V.32bis V.terbo V.FC V.34 V.34bis V.17 (G3 Fax Call) V.21 V.22 V.23 Constant Carrier (1200/75) V.23 Switched Carrier (Half Duplex) V.26bis V.26ter V.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.58 X2 K56FLEX V.Fast PEP HST CIM_CallBasedModem.ModulationSupported CIM_CallBasedModem.OtherSchemeDescription Description of the current modulation type when "Other" (value=1) is specified in the ModulationScheme property. CIM_CallBasedModem.ModulationScheme An 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. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 Unknown Other No Error Correction MNP 4 LAPM V.58 ECP Enhanced Cellular Protocol ETC Enhanced Throughput Cellular MNP 1 MNP 2 MNP 3 MNP10 PEP HST CIM_CallBasedModem.OtherErrorControlDescription Description 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.ErrorControlSupported Describes the current error correction characteristics of the Modem. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 Unknown Other No Error Correction MNP 4 LAPM V.58 ECP Enhanced Cellular Protocol ETC Enhanced Throughput Cellular MNP 1 MNP 2 MNP 3 MNP10 PEP HST CIM_CallBasedModem.ErrorControlSupported CIM_CallBasedModem.OtherErrorControlInfoDescription Description of the error control when "Other" (value=1) is defined as the value of the ErrorControlInfo property. CIM_CallBasedModem.ErrorControlInfo Time 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 Second Status 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. 0 1 2 3 4 5 6 7 8 9 10 Unknown Other Offline On Hook Dialing Waiting for Answer Ringing Modem Detected Negotiating Online Error Total 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. TRUE Total 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. TRUE Total 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. TRUE Total 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. TRUE Total 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. TRUE Total 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. TRUE Total 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. TRUE Length 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.0 The ISDNModem class, a kind of call-based Modem. Properties will be defined in a future release of the model. 2.6.0 The 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. Indexed 0 1 2 3 4 5 6 7 8 9 10 11 12 Unknown Other Distinctive Ring Caller ID Voice Fax Class 1 Fax Class 2 WakeOnRing Fax Group 3 GSM Support AMPS Support OOB Alerting Worldwide Country Support CIM_POTSModem.CapabilityDescriptions An 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. Indexed CIM_POTSModem.Capabilities Specifies which capabilities are enabled from the list of ones supported, defined in the Capabilities array. 0 1 2 3 4 5 6 7 8 9 10 11 12 Unknown Other Distinctive Ring Caller ID Voice Fax Class 1 Fax Class 2 WakeOnRing Fax Group 3 GSM Support AMPS Support OOB Alerting Worldwide Country Support CIM_POTSModem.Capabilities Defines the maximum settable communication speed to the COM Port for an external modem. Enter 0 if not applicable. Bits per Second Defines the maximum settable communication speed for accessing the phone system. Bits per Second Boolean 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. 0 1 2 Unknown Tone Pulse InactivityTimeout 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. Seconds Describes 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). 0 1 2 3 4 5 6 7 Unknown Other Not Supported High Medium Low Off Auto 64 CountriesSupported is an array of strings defining the countries in which the POTSModem operates. 64 CountrySelected 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. 24 CurrentPasswords 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. 0 1 2 3 4 5 Unknown Other Disabled Manual Answer Auto Answer Auto Answer with Call-Back The current equalization setting for the Modem. 0 1 2 3 Unknown Other Long Short List of black-listed numbers for the Modem. 2.6.0 Unimodem is a POTSModem that supports the Unimodem 1.0 Specification. Current call setup result code. 0 1 2 3 4 5 6 7 8 9 10 11 No Previous Call No Dial Tone Detected Reorder Signal Detected Network Busy Busy Signal Detected No Recognized Signal Detected Voice Detected Text Telephone Detected Data Answering Signal Detected Data Calling Signal Detected Fax Answering Signal Detected Fax Calling Signal Detected V.8bis Signal Detected Current multi-media mode of the Unimodem. 0 1 2 3 4 5 6 7 8 9 10 Data Only Fax Only Voice Only Voice View ASVD V.61 ASVD V.34Q DSVD Multi-Tech DSVD 1.2 DSVD V.70 Video Telephony H.324 Other V.80 Call Current DTE-DCE interface mode of the Unimodem, such as asynchronous, v.80 transparent or framed synchronous modes. 0 1 2 Async Data V.80 Transparent Synchronous Mode V.80 Framed Synchronous Mode The active transmit modulation scheme. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 .. V.17 (G3 Fax Call) V.21 V.22 V.22bis V.23 Constant Carrier (1200/75) V.23 Switched Carrier (Half Duplex) V.26bis V.26ter V.27ter (G3 Fax Call) V.29 HD (G3 Fax Call) V.32 V.32bis V.34 V.34 HD (G3 Fax Call) V.90 Issue 1 (Asymmetric) V.90 Issue 2 (Symmetric) Reserved (V.58) X2 K56FLEX V.FC V.32terbo Bell 212A Bell 103 Reserved for Mfgs The active receive modulation scheme. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 .. V.17 (G3 Fax Call) V.21 V.22 V.22bis V.23 Constant Carrier (1200/75) V.23 Switched Carrier (Half Duplex) V.26bis V.26ter V.27ter (G3 Fax Call) V.29 HD (G3 Fax Call) V.32 V.32bis V.34 V.34 HD (G3 Fax Call) V.90 Issue 1 (Asymmetric) V.90 Issue 2 (Symmetric) Reserved (V.58) X2 K56FLEX V.FC V.32terbo Bell 212A Bell 103 Reserved for Mfgs Initial transmit carrier data rate for the current or last call, in bits per second. Bits per Second Initial receive carrier data rate for the current or last call, in bits per second. Bits per Second The number of carrier retrains requested during the current or last call. TRUE The number of carrier retrains granted during the current or last call. TRUE Final transmit carrier data rate of the current or last call, in bits per second. Bits per Second Final receive carrier data rate of the current or last call, in bits per second. Bits per Second Cause of last call termination. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 Cause Unidentified No Previous Call Call Is Still in Progress Call Waiting Signal Detected Delayed NMS Initiated Dial Call NMS Initiated Leased Line Restoral NMS Initiated Redial NMS Initiated Dial Disconnect Power Loss Equipment Failure Front Panel Disconnect Requested Front Panel Leased Line Restoral Automatic Leased Line Restoral Inactivity Timer Expired cct116 Restoral Request cct108 Is Off Inhibits Dial cct108 Turned Off No Number Provided Blacklisted Number Call Attempts Limit Exceeded Extension Phone Off Hook Call Setup Fail Timer Expired Incoming Call Detected Loop Current Interrupted No Dial Tone Voice Detected Reorder Tone Sit Tone Engaged Tone Long Space Disconnect Carrier Lost Training Failed No Modulation in Common Retrain Failed Retrain Attempt Count Exceeded GSTN Cleardown Received Fax Detected In Test Mode Intrusive Self Test Initiated Any Key Abort DTE Hangup Command DTE Reset Command Frame Reject No Error Control Established Protocol Violation n400 Exceeded Negotiation Failed Disconnect Frame Received Sabme Frame Received Loss Of Synchronization Diagnostic Command Specification, Unimodem revision number. TRUE Estimated noise level for the last or current call in -dBm. Values are in the range of 0-100. -dBm Normalized mean squared error for the last or current call. Temporary carrier loss event count for the last or current call. TRUE Carrier Rate re-negotiation event count for the last or current call. TRUE Error Control frame size in bytes for the last or current call. Bytes Error control link timeouts in transmission for the last or current call. TRUE Error control link NAKs received for the last or current call. TRUE The flow control mechanism used in transmitting data. 0 1 2 3 Unknown Off DC1/DC3 V.24 ckt 106/133 The flow control mechanism used in receiving data. 0 1 2 3 Unknown Off DC1/DC3 V.24 ckt 106/133 Number 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. TRUE Number 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. TRUE Number 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. TRUE Number 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. TRUE Number 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. TRUE Number 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. TRUE Number 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. TRUE Number 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. TRUE Number of Call waiting events detected for the last or current call. TRUE 2.6.0 A 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. \nSeveral 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. Indexed 0 1 2 3 4 5 6 7 8 9 10 11 12 Unknown Other Sequential Access Random Access Supports Writing Encryption Compression Supports Removeable Media Manual Cleaning Automatic Cleaning SMART Notification Supports Dual Sided Media Predismount Eject Not Required MIF.DMTF|Storage Devices|001.9 MIF.DMTF|Storage Devices|001.11 MIF.DMTF|Storage Devices|001.12 MIF.DMTF|Disks|003.7 MIF.DMTF|Host Disk|001.2 MIF.DMTF|Host Disk|001.4 CIM_MediaAccessDevice.CapabilityDescriptions An 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. Indexed CIM_MediaAccessDevice.Capabilities ErrorMethodology 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.2 MIF.DMTF|Host Disk|001.5 Default block size, in bytes, for this Device. Bytes Maximum block size, in bytes, for media accessed by this Device. Bytes Minimum block size, in bytes, for media accessed by this Device. Bytes Boolean 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. 1 2 3 4 5 6 7 Other Unknown None Read Only Locked Out Boot Bypass Boot Bypass and Read Only MIF.DMTF|Disks|003.22 The 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.) MilliSeconds The 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 Second Time 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. MilliSeconds Time 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. MilliSeconds For 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. TRUE For 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.MaxUnitsBeforeCleaning CIM_MediaAccessDevice.UnitsUsed An 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.UnitsDescription An 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. TRUE CIM_MediaAccessDevice.UnitsDescription CIM_MediaAccessDevice.MaxUnitsBeforeCleaning FALSE 2.6.0 Capabilities and managment of a DiskDrive, a subtype of MediaAccessDevice. 2.6.0 Capabilities and managment of a DisketteDrive, a subtype of MediaAccessDevice. 2.6.0 Capabilities and managment of a CDROMDrive, a subtype of MediaAccessDevice. 2.6.0 Capabilities 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. 0 1 16 17 18 19 22 23 24 25 26 27 33 34 35 36 37 38 39 40 41 42 Unknown Other CD-ROM CD-ROM/XA CD-I CD Recordable DVD DVD-RW+ DVD-RAM DVD-ROM DVD-Video Divx CD-RW CD-DA CD+ DVD Recordable DVD-RW DVD-Audio DVD-5 DVD-9 DVD-10 DVD-18 CIM_PhysicalMedia.MediaType 2.6.0 Capabilities and managment of a WORMDrive, a subtype of MediaAccessDevice. 2.6.0 Capabilities and managment of a MagnetoOpticalDrive, a subtype of MediaAccessDevice. 2.6.0 Capabilities 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. Bytes Maximum partition count for the TapeDrive. Padding indicates the number of bytes inserted between blocks on a tape Media. Bytes Time in milliseconds to move from the most physically distant point on the tape to the beginning. MilliSeconds 2.6.0 A MediaTransferDevice represents hardware that moves PhysicalMedia. It is a superclass for Devices like PickerElement, ChangerDevice and InterLibraryPort. 2.6.0 PickerElements 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. Seconds The 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. Seconds String describing the location in the StorageLibrary where the Picker is currently positioned. 2.6.0 ChangerDevices 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. Seconds Boolean 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. A count of the number of audits performed by the Changer. TRUE TRUE 2.6.0 PickerForChanger 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. Antecedent The PickerElement that accesses StorageMediaLocations to deliver Media to the Changer. Dependent 1 The ChangerDevice. 2.6.0 LimitedAccessPorts 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. Seconds Date and time that the Port was last extended. TRUE The number of times that the LimitedAccessPort was used to move a PhysicalMedia into the System/StorageLibrary. TRUE The 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). 0 1 2 3 Unknown Import Export Both Import and Export 2.6.0 InterLibraryPorts 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. The number of times that the InterLibraryPort was used to move a PhysicalMedia into the System/StorageLibrary. TRUE The number of times that the InterLibraryPort was used to move a PhysicalMedia out of the System/StorageLibrary. TRUE 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). 0 1 2 3 Unknown Import Export Both Import and Export TRUE 2.6.0 LibraryExchange indicates that two StorageLibraries are connected through their InterLibraryPorts. Antecedent The InterLibraryPort of one StorageLibrary. Dependent The InterLibraryPort of the connected Library. Enumeration indicating whether the Antecedent (value=1), Dependent (value=2), or neither Library (value=3) currently has access to the Port. 0 1 2 3 Unknown Antecedent Dependent Neither 2.6.0 LabelReaders 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. 0 1 2 3 4 5 Barcode Radio Frequency Identification OCR (Optical Character Recognition) MICR (Magnetic Ink Character Recognition) 7 Character Barcode 9 Character Barcode CIM_PhysicalMedia.LabelFormats The 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. 0 1 2 3 4 5 6 Unknown Other Laser Infrared RF Camera Memory Reader TRUE 2.6.0 A LogicalDevice may use or require one or more LabelReaders, to scan barcodes or otherwise identify entities. This relationship is described by the AssociatedLabelReader dependency. Antecedent The LabelReader. Dependent The Device that is dependent on the Reader Device. TRUE 2.6.0 PickerLabelReader is used to indicate that one or more LabelReaders works in conjunction with PickerElements, to identify PhysicalMedia as they are being picked/placed. Dependent The PickerElement that is dependent on the Reader Device. TRUE 2.6.0 AccessLabelReader is used to indicate that one or more LabelReaders works in conjunction with MediaAccessDevices, to identify PhysicalMedia before read/write. Dependent The MediaAccessDevice that is dependent on the Reader Device. 2.6.0 StorageExtent 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. 0 1 2 3 4 Other Unknown Fixed Block Variable Block Count Key Data A free form string describing the media and/or its use. MIB.IETF|HOST-RESOURCES-MIB.hrStorageDescr Access 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. 0 1 2 3 4 Unknown Readable Writeable Read/Write Supported Write Once ErrorMethodology 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. Bytes MIF.DMTF|Host Storage|001.4 MIB.IETF|HOST-RESOURCES-MIB.hrStorageAllocationUnits MIF.DMTF|Storage Devices|001.5 Total 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.5 MIB.IETF|HOST-RESOURCES-MIB.hrStorageSize The 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. TRUE 2.6.0 An association between a FileSystem and the StorageExtent where it is located. Typically, a FileSystem ResidesOn a LogicalDisk. Antecedent The StorageExtent. Dependent The FileSystem that is located on the StorageExtent. TRUE 2.6.0 BasedOn 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. Antecedent The lower level StorageExtent. Dependent The higher level StorageExtent. StartingAddress 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. TRUE 2.6.0 Where a StorageExtent must be accessed through a MediaAccessDevice, this relationship is described by the MediaPresent association. MIF.DMTF|Storage Devices|001.8 Antecedent The MediaAccessDevice. Dependent The StorageExtent accessed using the MediaAccessDevice. Boolean indicating that the accessed StorageExtent is fixed in the MediaAccessDevice and can not be ejected. 2.6.0 StorageError 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.SystemCreationClassName TRUE 256 The scoping System's CreationClassName. CIM_StorageExtent.SystemName TRUE 256 The scoping System's Name. CIM_StorageExtent.CreationClassName TRUE 256 The scoping StorageExtent's CreationClassName. CIM_StorageExtent.DeviceID TRUE 64 The scoping StorageExtent's DeviceID. TRUE The starting address of the bytes in error. The ending address of the bytes in error. TRUE TRUE 2.6.0 The StorageDefect aggregation collects the StorageErrors for a StorageExtent. TRUE TRUE 1 1 The Extent reference defines the StorageExtent on which the errors occurred. TRUE TRUE Error references the Error object, defining the starting and ending addresses that are 'mapped out' of the StorageExtent. 2.6.0 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. BlockSize MIF.DMTF|Physical Extent|001.4 NumberOfBlocks MIF.DMTF|Physical Extent|001.3 Number of bytes of user data to skip before starting the check data interleave. Bytes MIF.DMTF|Physical Extent|001.6 Number of bytes to be reserved for check data. Bytes MIF.DMTF|Physical Extent|001.7 Number of bytes to be reserved for user data. Bytes MIF.DMTF|Physical Extent|001.8 2.6.0 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. BlockSize MIF.DMTF|Protected Space Extent|001.4 NumberOfBlocks The number of user data blocks contained in this Extent. MIF.DMTF|Protected Space Extent|001.3 For 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.) Bytes MIF.DMTF|Protected Space Extent|001.6 TRUE 2.6.0 ProtectedSpaceExtents are BasedOn a PhysicalExtent. This relationship is made explicit in this association. Antecedent The PhysicalExtent. Dependent The ProtectedSpaceExtent which is built on the PhysicalExtent. StartingAddress The starting logical block address of the PhysicalExtent from which this ProtectedSpaceExtent is derived. MIF.DMTF|Protected Space Extent|001.2 2.6.0 A 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.0 A VolumeSet is 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. NumberOfBlocks MIF.DMTF|Volume Set|001.3 Number 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.4 Number 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.5 VolumeSets in SCC have additional status information beyond that captured in the Availability and StatusInfo properties, inherited from ManagedSystemElement. This additional information (for example, "Protection Disabled", value=9) is captured in the VolumeStatus property. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 Other Unknown None/Not Applicable Broken Data Lost Dynamic Reconfig Exposed Fractionally Exposed Partially Exposed Protection Disabled Readying Rebuild Recalculate Spare in Use Verify In Progress TRUE 2.6.0 VolumeSets are BasedOn on one or more ProtectedSpaceExtents. This relationship is made explicit in this association. Antecedent 1 The ProtectedSpaceExtent. Dependent The VolumeSet which is built on the ProtectedSpaceExtent. True 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. 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. 2.6.0 A 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.SignatureState CIM_MediaPartition.SignatureAlgorithm A 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.Signature CIM_MediaPartition.SignatureState An 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. 0 1 2 3 4 5 Unknown Unimplemented Uninitialized Calculated by Operating System Calculated by a Media Manager Assigned by Owning Application CIM_MediaPartition.Signature CIM_MediaPartition.SignatureAlgorithm Boolean indicating that the Partition can be grown/extended without reformatting. 2.6.0 A 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. 0 1 2 3 Unknown Primary Extended Logical The '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. 0 1 2 3 4 5 6 7 8 9 10 11 12 14 15 16 17 18 20 22 23 27 28 33 35 36 38 49 51 52 53 54 55 60 64 65 66 67 80 81 82 83 84 85 86 97 99 100 101 102 103 104 105 113 115 116 117 118 119 120 121 128 129 130 131 132 134 135 147 148 161 163 164 165 166 177 179 180 182 183 184 193 196 198 199 216 219 225 227 228 229 230 239 240 241 242 243 244 246 254 255 65535 Empty | Microsoft DOS 12-bit FAT XENIX root XENIX usr DOS 16-bit FAT DOS Extended DOS 16-bit FAT (> 32MB) OS/2 HPFS | Win NTFS | QNX Ver 2 | Adv UNIX AIX Boot | OS /2 | Dell (Array) | Commodore DOS AIX Data Coherent OS/2 Boot Manager 32-bit FAT 32-bit FAT Microsoft 16-bit FAT Microsoft DOS Extended OPUS | OS/2 2.0 OS/2 (MOSS) Inactive Type 1 Compaq Diagnostics Partition | Microsoft OS/2 (MOSS) Inactive Type 4 OS/2 (MOSS) Inactive Type 6 OS/2 (MOSS) Inactive Type 7 OS/2 (MOSS) Inactive Type B OS/2 (MOSS) Inactive Type C Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft OS/2 Logical Volume Manager Microsoft OS/2 JFS Log PowerQuest VENIX 80286 | Series/1 Disk Personal RISC Boot Veritas Veritas OnTrack Disk Manager Read Only DOS OnTrack Disk Manager Read/Write DOS CPM | Microport System V/386 | OnTrack Disk Mgr | Microsoft OnTrack Disk Manager OnTrack Disk Manager Non-DOS Micro House EZ-Drive Non-DOS Golden Bow Vfeature | Microsoft Storage Dimensions SpeedStor | Microsoft UNIX - AT&T System V/386 | SCO UNIX Novell NetWare | Speedstore Novell NetWare Novell NetWare Novell Novell Novell Microsoft Microsoft Microsoft PC/IX IBM Microsoft QNX POSIX QNX POSIX (Secondary) QNX POSIX (Secondary) Minix (<=1.4a) | Linux | Microsoft Minix (>=1.4b) | Microsoft Linux Swap | Prime Linux Native | Apple System Hibernation for APM Microsoft HPFS FT mirror Amoeba | Microsoft Amoeba BBT | Microsoft Microsoft Microsoft Microsoft BSD/386 Microsoft Microsoft Microsoft Microsoft Microsoft BSDI fs | Microsoft BSDI Swap | Microsoft Microsoft Microsoft Microsoft Syrinx | HPFS FT Disabled Mirror CP/M 86 Digital Research CPM-86 | Concurrent DOS | OUTRIGGER SpeedStor 12-bit FAT Extended DOS Read-Only | Storage Dimensions SpeedStor 16-bit FAT Extended Microsoft Microsoft Intel OS/2 Raw Data Storage Dimensions DOS (Secondary) Microsoft SpeedStor Large | Storage Dimensions Microsoft Lan Step | SpeedStor | IBM PS/2 IML Bad Block Tables Unknown TRUE 2.6.0 DiskPartitions 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. Antecedent 1 The StorageVolume. Dependent The DiskPartition which is built on the Volume. 2.6.0 Capabilities 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 TRUE 2.6.0 TapePartitionOnSurface 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. Antecedent 1 The StorageExtent that represents the Tape's surface. Dependent The TapePartition which is built on the Extent. 2.6.0 A 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.) TRUE 2.6.0 LogicalDisks 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. Antecedent 1 The StorageExtent. Dependent The LogicalDisk which is built on the StorageExtent. TRUE 2.6.0 LogicalDisks 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. Antecedent 1 The StorageVolume. TRUE 2.6.0 LogicalDisks can be BasedOn a VolumeSet. This association is an optimization where software RAID doesn't exist and the LogicalDisk is built right on top of a VolumeSet presented by an SCC cabinet. However, this would be better modeled by a DiskPartition BasedOn the VolumeSet (described using the DiskPartitionBasedOnVolume association) and then basing the LogicalDisk on the DiskPartition (using the LogicalDiskBasedOnPartition association). Antecedent 1 The VolumeSet. TRUE 2.6.0 LogicalDisks 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. Antecedent 1 The DiskPartition. 2.6.0 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. NumberOfBlocks Total 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.2 The 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 2.6.0 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. NumberOfBlocks Total number of user data blocks that are contained in this Extent. MIF.DMTF|Aggregate Protected Space Extent|001.2 TRUE 2.6.0 AggregatePSExtents are BasedOn a single PhysicalExtent. This relationship is made explicit in this association. Antecedent 1 The PhysicalExtent. Dependent The AggregatePSExtent which is built on the PhysicalExtent. TRUE 2.6.0 AggregatePSExtents are BasedOn a single AggregatePExtent. This relationship is made explicit in this association. Antecedent 1 The AggregatePExtent. Dependent The AggregatePSExtent which is built on the AggregatePExtent. 2.6.0 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. \nSnapshot'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. \nWhen 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). True indicates that the snapshot is synced. The time stamp indicating when the sync occurred. TRUE 2.6.0 SnapshotOfExtent is an association between an Extent and its Snapshot. This relationship is made explicit in this association. Antecedent 1 The StorageExtent. Dependent The Snapshot. The type of snapshot. 0 1 2 3 4 Other Unknown Copy Before Delta After Delta 2.6.0 Capabilities and management of Memory-related LogicalDevices. ErrorMethodology ErrorMethodology 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.7 The 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. KiloBytes MIF.DMTF|Memory Array Mapped Addresses|001.3 MIF.DMTF|Memory Device Mapped Addresses|001.4 The 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. KiloBytes MIF.DMTF|Memory Array Mapped Addresses|001.4 MIF.DMTF|Memory Device Mapped Addresses|001.5 An 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. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 Other Unknown OK Bad Read Parity Error Single-Bit Error Double-Bit Error Multi-Bit Error Nibble Error Checksum Error CRC Error Undefined Undefined Undefined MIF.DMTF|Memory Device|005 MIF.DMTF|Physical Memory Array|001.8 CIM_Memory.OtherErrorDescription Free 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.ErrorInfo Boolean 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|Memory Device|005 MIF.DMTF|Physical Memory Array|001.8 The 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. 1 2 3 4 5 Other Unknown Read Write Partial Write MIF.DMTF|Memory Device|005 MIF.DMTF|Physical Memory Array|001.10 The 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. Bits MIF.DMTF|Memory Device|005 MIF.DMTF|Physical Memory Array|001.11 TRUE Data 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. Indexed MIF.DMTF|Memory Device|005 MIF.DMTF|Physical Memory Array|001.12 The 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. 0 1 2 Unknown Least Significant Byte First Most Significant Byte First Specifies 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 MIF.DMTF|Memory Device|005 MIF.DMTF|Physical Memory Array|001.14 Boolean 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. Bytes MIF.DMTF|Memory Device|005 MIF.DMTF|Physical Memory Array|001.15 TRUE An 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 MIF.DMTF|Physical Memory Array|001.13 TRUE 2.6.0 LogicalDevices may have Memory installed on them or otherwise associated with them - such as CacheMemory. This is made explicit in this association. Antecedent Memory installed on or associated with a Device. Dependent The LogicalDevice. TRUE TRUE 2.6.0 Association 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. GroupComponent TRUE The UnitaryComputerSystem. PartComponent The Memory StorageExtent which is part of the UnitaryComputerSystem. TRUE 2.6.0 Associates the Processor and system Memory, or a Processor's Cache. Dependent The Processor that accesses the Memory or uses the Cache. Speed of the bus, in MHertz, between the Processor and Memory. MegaHertz 2.6.0 Capabilities 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.ApplicationWriteable When 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. Bits CIM_NonVolatileStorage.ApplicationWriteable TRUE 2.6.0 A link between BIOSElement and NonVolatileStorage where the BIOS is loaded. Antecedent The non-volatile storage. Dependent The BIOS stored in the NonVolatile Extent. The 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.0 Capabilities and management of Volatile Storage. Indicates whether this Memory can be cached or not. MIF.DMTF|System Resource Memory Info|002 An 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". 1 2 3 4 5 Other Unknown Write-Back Write-Through Not Applicable MIF.DMTF|System Resource Memory Info|002 2.6.0 Capabilities 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). \nIf 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. 1 2 3 4 5 6 Other Unknown Primary Secondary Tertiary Not Applicable MIF.DMTF|System Cache|006 Defines 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. 1 2 3 4 5 6 Other Unknown Write Back Write Through Varies with Address Determination Per I/O MIF.DMTF|System Cache|006 Defines 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. 1 2 3 4 5 Other Unknown Instruction Data Unified MIF.DMTF|System Cache|006 Size, in bytes, of a single cache bucket or line. Bytes MIF.DMTF|System Cache|006 An integer enumeration describing the algorithm to determine which cache lines or buckets should be re-used. 1 2 3 4 5 6 7 8 Other Unknown Least Recently Used (LRU) First In First Out (FIFO) Last In First Out (LIFO) Least Frequently Used (LFU) Most Frequently Used (MFU) Data Dependent Multiple Algorithms MIF.DMTF|System Cache|006 Policy 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. 1 2 3 4 5 6 Other Unknown Read Read-Ahead Read and Read-Ahead Determination Per I/O MIF.DMTF|System Cache|006 Maximum 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. Seconds MIF.DMTF|System Cache|006 An integer enumeration defining the system cache associativity. For example, 6 indicates a fully associative cache. 1 2 3 4 5 6 7 8 Other Unknown Direct Mapped 2-way Set-Associative 4-way Set-Associative Fully Associative 8-way Set-Associative 16-way Set-Associative MIF.DMTF|System Cache|006 2.6.0 Capabilities 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). 1 2 3 4 5 6 7 Other Unknown Idle Printing Warmup Stopped Printing Offline MIB.IETF|Printer-MIB.hrPrinterStatus Printer error information. 0 1 2 3 4 5 6 7 8 9 10 11 Unknown Other No Error Low Paper No Paper Low Toner No Toner Door Open Jammed Offline Service Requested Output Bin Full CIM_Printer.ErrorInformation MIB.IETF|Printer-MIB.hrPrinterDetectedErrorState An array providing supplemental information for the current error state, indicated in DetectedErrorState. CIM_Printer.DetectedErrorState An integer array indicating the types of paper supported. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 Unknown Other A B C D E Letter Legal NA-10x13-Envelope NA-9x12-Envelope NA-Number-10-Envelope NA-7x9-Envelope NA-9x11-Envelope NA-10x14-Envelope NA-Number-9-Envelope NA-6x9-Envelope NA-10x15-Envelope A0 A1 A2 A3 A4 A5 A6 A7 A8 A9A10 B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 B10 C0 C1 C2C3 C4 C5 C6 C7 C8 ISO-Designated JIS B0 JIS B1 JIS B2 JIS B3 JIS B4 JIS B5 JIS B6 JIS B7 JIS B8 JIS B9 JIS B10 NA-Letter NA-Legal B4-Envelope B5-Envelope C3-Envelope C4-Envelope C5-Envelope C6-Envelope Designated-Long-Envelope Monarch-Envelope Executive Folio Invoice Ledger Quarto An 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. Indexed CIM_PrintJob.RequiredPaperType CIM_PrintService.PaperTypesAvailable MIB.IETF|Printer-MIB.prtInputMediaName Specifies 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.PaperTypesAvailable Specifies 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.PaperTypesAvailable An array indicating the print languages natively supported. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 Other Unknown PCL HPGL PJL PS PSPrinter IPDS PPDS EscapeP Epson DDIF Interpress ISO6429 Line Data MODCA REGIS SCS SPDL TEK4014 PDS IGP CodeV DSCDSE WPS LN03 CCITT QUIC CPAP DecPPL Simple Text NPAP DOC imPress Pinwriter NPDL NEC201PL Automatic Pages LIPS TIFF Diagnostic CaPSL EXCL LCDS XES MIME MIB.IETF|Printer-MIB.prtInterpreterLangFamily CIM_Printer.MimeTypesSupported CIM_PrintJob.Language CIM_PrintService.LanguagesSupported An 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.LanguagesSupported CIM_PrintJob.MimeTypes CIM_PrintService.MimeTypesSupported Indicates the current printer language being used. A language that is being used by the Printer should also be listed in LanguagesSupported. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 Other Unknown PCL HPGL PJL PS PSPrinter IPDS PPDS EscapeP Epson DDIF Interpress ISO6429 Line Data MODCA REGIS SCS SPDL TEK4014 PDS IGP CodeV DSCDSE WPS LN03 CCITT QUIC CPAP DecPPL Simple Text NPAP DOC imPress Pinwriter NPDL NEC201PL Automatic Pages LIPS TIFF Diagnostic CaPSL EXCL LCDS XES MIME CIM_Printer.LanguagesSupported CIM_Printer.CurrentMimeType Specifies 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.CurrentLanguage Indicates the default printer language. A language that is used as a default by the Printer should also be listed in LanguagesSupported. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 Other Unknown PCL HPGL PJL PS PSPrinter IPDS PPDS EscapeP Epson DDIF Interpress ISO6429 Line Data MODCA REGIS SCS SPDL TEK4014 PDS IGP CodeV DSCDSE WPS LN03 CCITT QUIC CPAP DecPPL Simple Text NPAP DOC imPress Pinwriter NPDL NEC201PL Automatic Pages LIPS TIFF Diagnostic CaPSL EXCL LCDS XES MIME CIM_Printer.LanguagesSupported CIM_Printer.DefaultMimeType Specifies 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.DefaultLanguage Printer jobs processed since last reset. These jobs may be processed from one or more PrintQueues. TRUE Time 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. Indexed 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 Unknown Other Color Printing Duplex Printing Copies Collation Stapling Transparency Printing Punch Cover Bind Black and White Printing One Sided Two Sided Long Edge Two Sided Short Edge Portrait Landscape Reverse Portrait Reverse Landscape Quality High Quality Normal Quality Low CIM_Printer.CapabilityDescriptions CIM_PrintJob.Finishing CIM_PrintService.Capabilities An 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. Indexed CIM_Printer.Capabilities Specifies 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. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 Unknown Other Color Printing Duplex Printing Copies Collation Stapling Transparency Printing Punch Cover Bind Black and White Printing One Sided Two Sided Long Edge Two Sided Short Edge Portrait Landscape Reverse Portrait Reverse Landscape Quality High Quality Normal Quality Low CIM_Printer.Capabilities Specifies 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. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 Unknown Other Color Printing Duplex Printing Copies Collation Stapling Transparency Printing Punch Cover Bind Black and White Printing One Sided Two Sided Long Edge Two Sided Short Edge Portrait Landscape Reverse Portrait Reverse Landscape Quality High Quality Normal Quality Low CIM_Printer.Capabilities The maximum number of copies that can be produced by the Printer from a single Job. CIM_PrintJob.Copies The 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.NumberUp The 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 Inch CIM_PrintJob.HorizontalResolution Printer's vertical resolution in Pixels per Inch. Pixels per Inch CIM_PrintJob.HorizontalResolution Identifies 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". Indexed CIM_PrintJob.CharSet MIB.IETF|Printer-MIB.prtLocalizationCharacterSet Specifies 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.CharSetsSupported Identifies 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. Indexed MIB.IETF|Printer-MIB.prtLocalizationLanguage CIM_PrintJob.NaturalLanguage Identifies 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.NaturalLanguagesSupported Specifies 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. KiloBytes CIM_PrintJob.JobSize Describes 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.RequiredJobSheets Specifies the marking technology used by the Printer. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 Other Unknown Electrophotographic LED Electrophotographic Laser Electrophotographic Other Impact Moving Head Dot Matrix 9pin Impact Moving Head Dot Matrix 24pin Impact Moving Head Dot Matrix Other Impact Moving Head Fully Formed Impact Band Impact Other Inkjet Aqueous Inkjet Solid Inkjet Other Pen Thermal Transfer Thermal Sensitive Thermal Diffusion Thermal Other Electroerosion Electrostatic Photographic Microfiche Photographic Imagesetter Photographic Other Ion Deposition eBeam Typesetter MIB.IETF|Printer-MIB.prtMarkerMarkTech 2.6.0 Capabilities 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. Indicates 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. When 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. The current number of Jobs on the Queue. TRUE Gives 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). 0 1 2 3 Other Unknown No Additional Status QueueSpoolAreaFull Provides 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. KiloBytes CIM_PrintJob.JobSize Specifies 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.JobPriorityHigh CIM_PrintQueue.JobPriorityLow Specifies 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.JobPriorityLow CIM_Job.Priority Specifies 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.JobPriorityHigh CIM_Job.Priority Specifies 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.6.0 Description 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.SystemCreationClassName TRUE 256 The scoping System's CreationClassName. CIM_PrintQueue.SystemName TRUE 256 The scoping System's Name. CIM_PrintQueue.CreationClassName TRUE 256 The scoping Queue's CreationClassName. CIM_PrintQueue.Name TRUE 256 The scoping Queue's Name. JobStatus The inherited JobStatus is used to provide additional information about the status of a PrintJob beyond that enumerated by PrintJobStatus. CIM_PrintJob.PrintJobStatus TRUE Uniquely 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. KiloBytes CIM_Printer.MaxSizeSupported CIM_PrintQueue.MaxJobSize Specifies the print language used by this Job. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 Other Unknown PCL HPGL PJL PS PSPrinter IPDS PPDS EscapeP Epson DDIF Interpress ISO6429 Line Data MODCA REGIS SCS SPDL TEK4014 PDS IGP CodeV DSCDSE WPS LN03 CCITT QUIC CPAP DecPPL Simple Text NPAP DOC imPress Pinwriter NPDL NEC201PL Automatic Pages LIPS TIFF Diagnostic CaPSL EXCL LCDS XES MIME Indexed MIB.IETF|Printer-MIB.prtInterpreterLangFamily CIM_Printer.LanguagesSupported CIM_PrintService.LanguagesSupported CIM_PrintJob.MimeTypes Specifies the mime types used by the PrintJob if Language is set to indicate a mime type is in use (value=47). CIM_PrintJob.Language CIM_Printer.MimeTypesSupported CIM_PrintService.MimeTypesSupported A 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.PaperTypesAvailable CIM_PrintService.PaperTypesAvailable An array of integers indicating the type of finishing required by this Job. It is equivalent to the Capabilities property provided by the Printer. Indexed 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 Unknown Other Color Printing Duplex Printing Copies Collation Stapling Transparency Printing Punch Cover Bind Black and White Printing One Sided Two Sided Long Edge Two Sided Short Edge Portrait Landscape Reverse Portrait Reverse Landscape Quality High Quality Normal Quality Low CIM_Printer.Capabilities CIM_PrintService.Capabilities The number of physical copies of the output that will be produced from this Job. CIM_Printer.MaxCopies The horizontal resolution in Pixels per Inch for the Job. Pixels per Inch CIM_Printer.HorizontalResolution The vertical resolution in Pixels per Inch for the Job. Pixels per Inch CIM_Printer.VerticalResolution Specifies 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.CharSetsSupported Identifies 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.NaturalLanguagesSupported The number of print-stream pages that should be rendered onto a single media sheet when the Printer outputs this PrintJob. CIM_Printer.MaxNumberUp Describes the current state of this Job with respect to the PrintQueue and the Printer. Additional information may be specified in JobStatus. 1 2 3 4 5 6 7 Other Unknown Pending Blocked Complete Completed With Error Printing CIM_PrintJob.TimeCompleted CIM_PrintJob.JobStatus Time 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.PrintJobStatus Describes the job sheets that should be used when this Job is output on the Printer. CIM_Printer.AvailableJobSheets Provides 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.0 The 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. Indexed 0 1 2 3 4 5 6 7 Unknown Other SMB BSD SYSV HPNP IPP Local CIM_PrintSAP.PrintProtocolInfo Provides 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. Indexed CIM_PrintSAP.PrintProtocol 2.6.0 The 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.PaperTypesAvailable CIM_PrintJob.RequiredPaperType An 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. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 Other Unknown PCL HPGL PJL PS PSPrinter IPDS PPDS EscapeP Epson DDIF Interpress ISO6429 Line Data MODCA REGIS SCS SPDL TEK4014 PDS IGP CodeV DSCDSE WPS LN03 CCITT QUIC CPAP DecPPL Simple Text NPAP DOC imPress Pinwriter NPDL NEC201PL Automatic Pages LIPS TIFF Diagnostic CaPSL EXCL LCDS XES MIME Indexed MIB.IETF|Printer-MIB.prtInterpreterLangFamily CIM_Printer.LanguagesSupported CIM_PrintJob.Language CIM_PrintService.MimeTypesSupported An 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.MimeTypesSupported CIM_PrintJob.MimeTypes CIM_PrintService.LanguagesSupported An 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. Indexed 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 Unknown Other Color Printing Duplex Printing Copies Collation Stapling Transparency Printing Punch Cover Bind Black and White Printing One Sided Two Sided Long Edge Two Sided Short Edge Portrait Landscape Reverse Portrait Reverse Landscape Quality High Quality Normal Quality Low CIM_Printer.Capabilities CIM_PrintJob.Finishing CIM_PrintService.CapabilityDescriptions An 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. Indexed CIM_PrintService.Capabilities Describes 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. TRUE 2.6.0 This association indicates that a Printer can be passed PrintJobs from a particular Queue. Antecedent A destination Printer for Jobs enqueued on the Dependent Queue. Dependent A Queue that is providing Jobs to the Printer. TRUE 2.6.0 This association indicates that a Printer is currently servicing a particular PrintJob. Antecedent The destination Printer for a PrintJob. Dependent The PrintJob. TRUE TRUE 2.6.0 This association indicates which files are associated with a PrintJob. GroupComponent TRUE The PrintJob that is based on one or more Files. PartComponent The File(s) that make up a PrintJob. TRUE 2.6.0 This association indicates that a PrintService utilizes a particular PrintQueue. Antecedent The PrintQueue that the Service utilizes. Dependent The PrintService that puts Jobs on the Queue. Indicates that the PrintService can accept Jobs and place them on the Queue. TRUE 2.6.0 This association indicates that the Jobs from a PrintQueue can be sent to the referenced PrintSAP, to be handled by the SAP's backing PrintService. Antecedent The PrintSAP for the PrintService. Dependent The PrintQueue that forwards Jobs to the SAP. TRUE 2.6.0 This 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". Antecedent 1 1 The PrintQueue on which the Job is held. Dependent TRUE The PrintJob. The 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). 2.6.0 This 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). 0 1 2 3 4 Unknown Other Pager TCP Port UDP Port CIM_OOBAlertService.OtherDestinationTypeDescription The description of the alert DestinationType. This is used when the DestinationType is set to "Other" (value=1). CIM_OOBAlertService.DestinationType The 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. 0 1 2 3 4 5 Unknown Other Numeric AlphaNumeric Free Form Text Platform Event Trap CIM_OOBAlertService.OtherMessageFormatDescription The description of the format of the alert message used by the Service when the AlertMessageFormat property is set to "Other" (value=1). CIM_OOBAlertService.MessageFormat If 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. Seconds FALSE If 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.0 WakeUpService 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. 0 1 2 3 4 Unknown Other Wake On LAN - Magic Packet Wake on LAN - Packet Filtering Wake On Ring CIM_WakeUpServcice.OtherWakeUpTypeDescription A description of the type of WakeUpService used when WakeUpType is set to "Other" (value=1). CIM_WakeUpService.WakeUpType The 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). 0 1 2 3 4 5 6 7 Unknown Other ARP Broadcast Neighbor Discovery Multicast IP Packet with Directed MAC Address IPX Diagnostic Responder NBT Name Query Binary Match CIM_WakeUpService.OtherFilterTypeDescription TRUE The 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 TRUE 2.6.0 OOBAlertServiceOnModem defines where the out of band alerting Service is implemented. The Service can either employ a Modem or NetworkAdapter to send alerts. Antecedent 1 The Modem which implements the alerting Service. Dependent The alerting Service provided on the Modem. TRUE 2.6.0 WakeUpServiceOnModem defines where the WakeUpService is implemented. The Service can either employ a Modem or NetworkAdapter to receive a wakeup signal. Antecedent 1 The Modem which implements the WakeUpService. Dependent The wakeup Service provided on the Modem. TRUE 2.6.0 OOBAlertServiceOnNetworkAdapter defines where the out of band alerting Service is implemented. Currently, the Service can either employ a Modem or a NetworkAdapter to send alerts. Antecedent 1 The NetworkAdapter which implements the Service. Dependent The alerting Service provided on the NetworkAdapter. TRUE 2.6.0 WakeUpServiceOnNetworkAdapter defines where the WakeUpService is implemented. Currently, the Service can either employ a Modem or a NetworkAdapter for wakeup. Antecedent 1 The NetworkAdapter which implements the Service. Dependent The wakeup Service provided on the NetworkAdapter. 2.6.0 FibreProtocolService 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.6.0 A 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. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. Name TRUE 256 The 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. 0 1 2 3 4 Unknown Other Fully Redundant Degraded Redundancy Redundancy Lost TRUE TRUE 2.6.0 A 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. GroupComponent TRUE The RedundancyComponent association indicates that 'this set of fans' or 'these physical extents' participate in a single RedundancyGroup. 2.6.0 A 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. FALSE FALSE TRUE 2.6.0 The 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. TRUE The SpareGroup TRUE A 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.6.0 A class derived from RedundancyGroup containing mass storage-related redundancy information. StorageRedundancyGroups are used to protect user data. They are made up of one or more PhysicalExtents, or one or more AggregatePExtents. StorageRedundancyGroups may overlap. However, the underlying Extents 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. 0 1 2 3 4 5 6 7 None Other Unknown Copy XOR P+Q S P+S MIF.DMTF|Redundancy Group|001.2 StorageRedundancy 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. 0 1 2 3 4 5 6 7 8 No Additional Status Reconfig In Progress Data Lost Not Currently Configured Protected Rebuild Redundancy Disabled Unprotected Rebuild Recalculating Verifying True 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.0 A 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. TRUE TRUE 2.6.0 CIM_NetworkAdapterRedundancyComponent indicates the role that a NetworkAdapter plays in a ExtraCapacityGroup, providing load balancing. GroupComponent TRUE The RedundancyGroup representing a set of load balanced NetworkAdapters. PartComponent The Network Adapter(s) belonging to the RedundancyGroup. Indicates 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). 0 1 2 3 Unknown Load Balancing - Transmit Only Load Balancing - Receive Only Full Load Balancing Boolean 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. 0 1 2 3 4 Unknown Original Primary Preferred Primary Both Not Applicable TRUE 2.6.0 NetworkVirtualAdapter describes that an instance of NetworkAdapter is actually the result of several Adapters participating in a load balanced RedundancyGroup. SystemElement The 'virtual' NetworkAdapter. SameElement The ExtraCapacity RedundancyGroup that describes the load balancing. The result of the load balancing is the 'virtual' Adapter. TRUE TRUE 2.6.0 Describes the StorageExtents participating in a StorageRedundancyGroup. GroupComponent TRUE The StorageRedundancyGroup. PartComponent The StorageExtent participating in the RedundancyGroup. TRUE TRUE 2.6.0 Describes the PhysicalExtents participating in a StorageRedundancyGroup. GroupComponent TRUE The StorageRedundancyGroup. PartComponent The PhysicalExtent participating in the RedundancyGroup. TRUE TRUE 2.6.0 Describes the AggregatePExtent in a StorageRedundancyGroup. GroupComponent TRUE The StorageRedundancyGroup. PartComponent The AggregatePExtent participating in the RedundancyGroup. 2.6.0 A 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. CollectionID TRUE TRUE TRUE 2.6.0 CIM_DriveInDiskGroup defines the DiskDrive(s) that participate in the Group. Collection TRUE 1 The DiskGroup. A Drive is a member of at most one DiskGroup. Member The DiskDrive in the Group. TRUE TRUE 2.6.0 CIM_ExtentInDiskGroup defines the StorageExtent(s) that are located within and restricted by the Group. Collection TRUE 1 The DiskGroup. An Extent is defined within at most one DiskGroup. Member The StorageExtent restricted by and participating in the Group. TRUE TRUE 2.6.0 CIM_GroupInDiskGroup describes that a DiskGroup may be divided into smaller named Collections. Collection TRUE 1 The DiskGroup that is subsetted into smaller Collections. CollectionInCollection The DiskGroup that is a subset of the larger Group. 2.6.0 MonitorResolution 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. SettingID TRUE 256 The inherited SettingID serves as part of the key for a MonitorResolution instance. Monitor's horizontal resolution in Pixels. Pixels CIM_VideoController.CurrentHorizontalResolution MIF.DMTF|Monitor Resolutions|002.2 Monitor's vertical resolution in Pixels. Pixels CIM_VideoController.CurrentVerticalResolution MIF.DMTF|Monitor Resolutions|002.3 Monitor'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. Hertz CIM_VideoController.CurrentRefreshRate MIF.DMTF|Monitor Resolutions|002.4 Monitor's minimum refresh rate in Hertz, when a range of rates is supported at the specified resolutions. Hertz CIM_VideoController.MinRefreshRate MIF.DMTF|Monitor Resolutions|002.6 Monitor's maximum refresh rate in Hertz, when a range of rates is supported at the specified resolutions. Hertz CIM_VideoController.MaxRefreshRate MIF.DMTF|Monitor Resolutions|002.7 Integer indicating whether the monitor operates in interlaced (value=5) or non-interlaced (4) mode. 1 2 3 4 5 Other Unknown Not Supported Non-Interlaced Operation Interlaced Operation CIM_VideoController.CurrentScanMode MIF.DMTF|Monitor Resolutions|002.5 TRUE 2.6.0 MonitorSetting associates the MonitorResolution Setting object with the DesktopMonitor to which it applies. Element The DesktopMonitor. Setting The MonitorResolution associated with the DesktopMonitor. 2.6.0 VideoControllerResolution 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. SettingID TRUE 256 The inherited SettingID serves as part of the key for a VideoControllerResolution instance. Controller's horizontal resolution in Pixels. Pixels CIM_VideoController.CurrentHorizontalResolution MIF.DMTF|Monitor Resolutions|002.2 Controller's vertical resolution in Pixels. Pixels CIM_VideoController.CurrentVerticalResolution MIF.DMTF|Monitor Resolutions|002.3 Refresh rate in Hertz. If a range of rates is supported, use the MinRefreshRate and MaxRefreshRate properties, and set RefreshRate (this property) to 0. Hertz CIM_VideoController.CurrentRefreshRate MIF.DMTF|Monitor Resolutions|002.4 Minimum refresh rate in Hertz, when a range of rates is supported at the specified resolutions. Hertz CIM_VideoController.MinRefreshRate MIF.DMTF|Monitor Resolutions|002.6 Maximum refresh rate in Hertz, when a range of rates is supported at the specified resolutions. Hertz CIM_VideoController.MaxRefreshRate MIF.DMTF|Monitor Resolutions|002.7 Integer indicating whether the Controller operates in interlaced (value=5) or non-interlaced (4) mode. 1 2 3 4 5 Other Unknown Not Supported Non-Interlaced Operation Interlaced Operation CIM_VideoController.CurrentScanMode MIF.DMTF|Monitor Resolutions|002.5 Number of colors supported at the current resolutions. CIM_VideoController.CurrentNumberOfColors TRUE 2.6.0 VideoSetting associates the VideoControllerResolution Setting with the Controller(s) to which it applies. Element The VideoController. Setting The resolutions, refresh rates, scan mode and number of colors that can be set for the Controller. 2.6.0 MessageLog 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. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. Name TRUE 256 The 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. Indexed 0 1 2 3 4 5 6 7 8 9 10 Unknown Other Write Record Supported Delete Record Supported Can Move Backward in Log Freeze Log Supported Clear Log Supported Supports Addressing by Ordinal Record Number Variable Length Records Supported Variable Formats for Records Can Flag Records for Overwrite CIM_MessageLog.CapabilitiesDescriptions An 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. Indexed CIM_MessageLog.Capabilities The maximum size, in bytes, to which the Log can grow. If there is no maximum, then MaxLogSize should be set to 0. Bytes The 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. Bytes If 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. Bytes The 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. Bytes If 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. TRUE An 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). \n\nSome of the property's possible values need further explanation:\n3="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. \n4="Overwrite Outdated When Needed" describes that Log entries (timestamped later than the date/time specified in the property, TimeWhenOutdated) can be overwritten. \n5="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. \n6="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". 0 1 2 3 4 5 6 7 Unknown Other Wraps When Full Clear When Near Full Overwrite Outdated When Needed Remove Outdated Records Overwrite Specific Records Never Overwrite CIM_MessageLog.OtherPolicyDescription CIM_MessageLog.TimeWhenOutdated CIM_MessageLog.PercentageNearFull When 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.OverwritePolicy If 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.OverwritePolicy If 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'. Percent CIM_MessageLog.OverwritePolicy An enumeration describing the last change to the MessageLog. 0 1 2 3 4 Unknown Add Delete Modify Log Cleared When 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). 0 1 2 3 4 5 6 7 8 9 10 11 Unknown Other ASCII Unicode ISO2022 ISO8859 Extended UNIX Code UTF-8 UCS-2 Bitmapped Data OctetString Defined by Individual Records Requests 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. \n\nNote: 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. FALSE TRUE FALSE TRUE FALSE Advancing 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. FALSE TRUE FALSE TRUE FALSE Boolean indicating that the IterationIdentifier should be advanced to the next record, after retrieving the current Log entry. FALSE TRUE FALSE TRUE FALSE TRUE FALSE Boolean 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. FALSE TRUE FALSE TRUE FALSE TRUE FALSE Boolean indicating that the IterationIdentifier should be advanced to the next record, after writing the Log entry. FALSE FALSE TRUE FALSE FALSE FALSE TRUE FALSE Boolean indicating that the IterationIdentifier should be advanced to the next record, after updating the current Log entry. FALSE TRUE 2.6.0 The 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. \nDefinitional formats for LogRecords could be specified by establishing a naming convention for the RecordID and MessageTimestamp key properties. CIM_MessageLog.CreationClassName TRUE 256 The scoping Log's CreationClassName. CIM_MessageLog.Name TRUE 256 The scoping Log's Name. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE 256 RecordID, 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. TRUE A LogRecord's key structure includes a timestamp for the entry. A free-form string describing the LogRecord's data structure. TRUE TRUE 2.6.0 RecordInLog describes the aggregation or location of Log entries within a MessageLog. TRUE TRUE 1 1 The Message Log. TRUE TRUE The Log entry contained within the MessageLog. TRUE 2.6.0 MessageLogs 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. Antecedent The I/O stream DeviceFile. Dependent The MessageLog outputting to the DeviceFile. TRUE 2.6.0 MessageLogs 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. Antecedent The DataFile. Dependent The MessageLog residing in the DataFile. TRUE 2.6.0 MessageLogs 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. Antecedent The StorageExtent. Dependent The MessageLog located within the Extent. StartingOffset indicates where in the Extent that the Log begins. TRUE 2.6.0 ManagedSystemElements 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. Antecedent The MessageLog. Dependent The ManagedSystemElement whose information is recorded in the MessageLog. A free-form string describing the use of the Log by the ManagedSystemElement. 2.6.0 The Location class specifies the position and address of a PhysicalElement. TRUE 256 Name is a free-form string defining a label for the Location. It is a part of the key for the object. TRUE 256 Position 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. 1024 Address is a free-form string indicating a street, building or other type of address for the PhysicalElement's Location. TRUE 2.6.0 PhysicalElementLocation associates a PhysicalElement with a Location object for inventory or replacement purposes. TRUE The PhysicalElement whose Location is specified. TRUE 1 The PhysicalElement's Location. 2.6.0 The 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. TRUE 256 Name is a free-form string defining a label for the ReplacementSet. It is the key for the object. TRUE TRUE 2.6.0 ParticipatesInSet indicates which PhysicalElements should be replaced together. TRUE TRUE The ReplacementSet. TRUE The PhysicalElement which should be replaced with other Elements, as a Set. 2.6.0 The 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). 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 Unknown Other Male Female Shielded Unshielded SCSI (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 BNC ATA 3-1/2 Inch (40 pins) ATA 2-1/2 Inch (44 pins) ATA-2 ATA-3 ATA/66 DB-9 DB-15 DB-25 DB-36 RS-232C RS-422 RS-423 RS-485 RS-449 V.35 X.21 IEEE-488 AUI UPT Category 3 UPT Category 4 UPT Category 5 BNC RJ11 RJ45 Fiber MIC Apple AUI Apple GeoPort PCI ISA EISA VESA PCMCIA PCMCIA Type I PCMCIA Type II PCMCIA Type III ZV Port CardBus USB IEEE 1394 HIPPI HSSDC (6 pins) GBIC DIN Mini-DIN Micro-DIN PS/2 Infrared HP-HIL Access.bus NuBus Centronics Mini-Centronics Mini-Centronics Type-14 Mini-Centronics Type-20 Mini-Centronics Type-26 Bus Mouse ADB AGP VME Bus VME64 Proprietary Proprietary Processor Card Slot Proprietary Memory Card Slot Proprietary I/O Riser Slot PCI-66MHZ AGP2X AGP4X PC-98 PC-98-Hireso PC-H98 PC-98Note PC-98Full SSA SCSI Circular On Board IDE Connector On Board Floppy Connector 9 Pin Dual Inline 25 Pin Dual Inline 50 Pin Dual Inline 68 Pin Dual Inline On Board Sound Connector Mini-jack PCI-X Sbus IEEE 1396-1993 32 bit Sbus IEEE 1396-1993 64 bit MCA GIO XIO HIO NGIO PMC MTRJ VF-45 Future I/O SC SG Electrical Optical Ribbon GLM 1x9 Mini SG LC HSSC VHDCI Shielded (68 pins) InfiniBand MIF.DMTF|Bus Port|003 and 12 CIM_PhysicalConnector.OtherTypeDescription A 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.ConnectorType MIF.DMTF|Bus Port|003 TRUE 2.6.0 The ConnectedTo association indicates that two or more PhysicalConnectors are connected together. Antecedent The Antecedent represents a PhysicalConnector that serves as one end of the connection. Dependent The Dependent represents another PhysicalConnector that serves as the other end of the connection. 2.6.0 The Slot class represents Connectors into which Packages are inserted. For example, a PhysicalPackage that is a DiskDrive may be inserted into an SCA 'Slot'. As another example, a Card (subclass of PhysicalPackage) may be inserted into a 16-, 32-, or 64-bit expansion 'Slot' on a HostingBoard. PCI or PCMCIA Type III Slots are examples of the latter. ConnectorType MIF.DMTF|System Slot|005.2 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. Inches Maximum length of an adapter Card that can be inserted into the Slot, in inches. Inches Maximum 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. Bits 0 1 8 16 32 64 128 MIF.DMTF|System Slot|005.3 An array of enumerated integers indicating the Vcc voltage supported by this Slot. 0 1 2 3 Unknown Other 3.3V 5V MIF.DMTF|System Slot|005.9 An array of enumerated integers indicating the Vpp voltage supported by this Slot. 0 1 2 3 4 Unknown Other 3.3V 5V 12V MIF.DMTF|System Slot|005.10 Maximum thermal dissipation of the Slot in milliwatts. MilliWatts MIF.DMTF|System Slot|005.11 Boolean 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.PurposeDescription A 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.SpecialPurpose The 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.1 A boolean indicating whether the Slot is currently powered (TRUE) or not (FALSE). MIF.DMTF|System Slot|005.13 A 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 TRUE 2.6.0 Slots 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. Antecedent The 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. Dependent 1 The new Slot provided by the adapter board. TRUE 2.6.0 AdjacentSlots 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. TRUE One of the adjacent Slots. TRUE The 'other' adjacent Slot. The distance, in inches, between adjacent Slots. Inches Slots 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.0 The 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. Inches The depth of the PhysicalPackage in inches. Inches The width of the PhysicalPackage in inches. Inches The weight of the PhysicalPackage in pounds. Pounds FALSE TRUE TRUE 2.6.0 The Container association represents the relationship between a contained and a containing PhysicalElement. A containing object must be a PhysicalPackage. GroupComponent TRUE 1 The PhysicalPackage that contains other PhysicalElements, including other Packages. PartComponent The PhysicalElement which is contained in the Package. A 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. 2.6.0 PhysicalFrame 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. Indexed 0 1 2 3 4 5 6 7 8 Unknown Other Service From TopService From Front Service From Back Service From Side Sliding Trays Removable Sides Moveable CIM_PhysicalFrame.ServiceDescriptions An 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. Indexed CIM_PhysicalFrame.ServicePhilosophy Boolean 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. 1 2 3 4 5 Other Unknown No Breach Breach Attempted Breach Successful MIF.DMTF|Physical Container Global Table|004 CIM_PhysicalFrame.BreachDescription BreachDescription 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.SecurityBreach Boolean indicating that the Frame is currently locked. 2.6.0 A 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. Height The 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. Us Enumeration 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. 0 1 2 3 4 Unknown Standard 19 Inch Telco Equipment Shelf Non-Standard CIM_Rack.CountryDesignation Designation 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.6.0 The 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 Volts Amount of heat generated by the Chassis in BTU/hour. BTU per Hour An enumerated, integer-valued array indicating the type of Chassis. Indexed 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 Other Unknown Desktop Low Profile Desktop Pizza Box Mini Tower Tower Portable LapTop Notebook Hand Held Docking Station All in One Sub Notebook Space-Saving Lunch Box Main System Chassis Expansion Chassis SubChassis Bus Expansion Chassis Peripheral Chassis Storage Chassis Rack Mount Chassis Sealed-Case PC MIF.DMTF|Physical Container Global Table|004 CIM_Chassis.TypeDescriptions An array of free-form strings providing more information on the ChassisTypes array entries. Note, each entry of this array is related to the entry in ChassisTypes that is located at the same index. Indexed CIM_Chassis.ChassisTypes TRUE TRUE 2.6.0 Racks, 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. GroupComponent TRUE 1 The Rack that contains the Chassis. PartComponent The Chassis which is mounted in the Rack. An 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 TRUE TRUE 2.6.0 A Chassis can contain other Packages, such as other Chassis and Cards. The PackageInChassis association makes explicit this relationship. GroupComponent TRUE 1 The Chassis that contains other PhysicalPackages. PartComponent The PhysicalPackage which is contained in the Chassis. TRUE 2.6.0 A 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.2 Antecedent 1 The Docking Station. Dependent 1 The Laptop that is 'Docked'. 2.6.0 The 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.RequirementsDescription A 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.SpecialRequirements Operating voltages required by the Card. MilliVolts FALSE FALSE 2.6.0 The 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. 43 44 45 46 47 48 49 50 52 64 65 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 98 99 100 101 102 103 104 105 106 109 110 PCI ISA EISA VESA PCMCIA PCMCIA Type I PCMCIA Type II PCMCIA Type III CardBus Access.bus NuBus AGP VME Bus VME64 Proprietary Proprietary Processor Card Slot Proprietary Memory Card Slot Proprietary I/O Riser Slot PCI-66MHZ AGP2X AGP4X PC-98 PC-98-Hireso PC-H98 PC-98Note PC-98Full PCI-X Sbus IEEE 1396-1993 32 bit Sbus IEEE 1396-1993 64 bit MCA GIO XIO HIO NGIO PMC Future I/O InfiniBand CIM_PhysicalConnector.ConnectorType System 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. Bits 0 1 8 16 32 64 128 CIM_Slot.MaxBusWidth TRUE TRUE 2.6.0 Cards 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. GroupComponent TRUE 1 The Card that hosts another Card. PartComponent The Card that is plugged into or otherwise mounted on another Card. A 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.0 StorageMediaLocation is a PhysicalElement 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. 0 1 2 3 4 5 6 7 8 9 Unknown Other Slot Magazine MediaAccessDevice InterLibrary Port Limited Access Port Door Shelf Vault LocationCoordinates 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. \n\n 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"). Indexed 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 Unknown Other Tape Cartridge QIC Cartridge AIT Cartridge DTF Cartridge DAT Cartridge 8mm Tape Cartridge 19mm Tape Cartridge DLT Cartridge Half-Inch Magnetic Tape Cartridge Cartridge Disk JAZ Disk ZIP Disk SyQuest Disk Winchester Removable Disk CD-ROM CD-ROM/XA CD-I CD Recordable WORM Magneto-Optical DVD DVD-RW+ DVD-RAM DVD-ROM DVD-Video Divx Floppy/Diskette Hard Disk Memory Card Hard Copy Clik Disk CD-RW CD-DA CD+ DVD Recordable DVD-RW DVD-Audio DVD-5 DVD-9 DVD-10 DVD-18 Magneto-Optical Rewriteable Magneto-Optical Write Once Magneto-Optical Rewriteable (LIMDOW) Phase Change Write Once Phase Change Rewriteable Phase Change Dual Rewriteable Ablative Write Once Near Field Recording MiniQic Travan 8mm Metal Particle 8mm Advanced Metal Evaporate NCTP LTO Ultrium LTO Accelis 9 Track Tape 18 Track Tape 36 Track Tape Magstar 3590 Magstar MP D2 Tape Tape - DST Small Tape - DST Medium Tape - DST Large CIM_PhysicalMedia.MediaType CIM_StorageMediaLocation.MediaSizesSupported The 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. Indexed Inches CIM_PhysicalMedia.MediaType CIM_StorageMediaLocation.MediaSizesSupported CIM_StorageMediaLocation.TypeDescriptions A 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. Indexed CIM_StorageMediaLocation.MediaTypesSupported 2.6.0 StorageMediaLocations 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. Indexed CIM_Magazine.LabelStates CIM_Magazine.LabelFormats An 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. Indexed 0 1 2 OK/Readable Unreadable Upside Down CIM_Magazine.PhysicalLabels An 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. Indexed 0 1 2 3 4 5 Barcode Radio Frequency Identification OCR (Optical Character Recognition) MICR (Magnetic Ink Character Recognition) 7 Character Barcode 9 Character Barcode CIM_Magazine.PhysicalLabels TRUE 2.6.0 Adapter 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. Antecedent The Connector into which the Package is inserted. Dependent 1 The Package in the Connector. TRUE 2.6.0 Complex 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. Antecedent The Slot into which the PhysicalPackage is inserted. Dependent 1 The Package in the Slot. TRUE 2.6.0 Slots 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.4 Antecedent The Slot into which the Card is inserted. Dependent 1 The Card in the Slot. TRUE TRUE 2.6.0 PhysicalPackages contain Connectors as well as other PhysicalElements. The ConnectorOnPackage association makes explicit the containment relationship between Connectors and Packages. GroupComponent TRUE 1 The PhysicalPackage that has a Connector. PartComponent The PhysicalConnector. 2.6.0 The 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. Feet The current length of the PhysicalLink in feet. For some connections, especially wireless technologies, this property may not be applicable and should be left uninitialized. Feet Boolean 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). 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 Unknown Other Cat1 Cat2 Cat3 Cat4 Cat5 50-ohm Coaxial 75-ohm Coaxial 100-ohm Coaxial Fiber-optic UTP STP Ribbon Cable Twinaxial Optical 9um Optical 50um Optical 62.5um MIF.DMTF|Fibre Channel Bus Port Extensions|001.4 TRUE 2.6.0 The ElementsLinked association indicates which PhysicalElements are cabled together by a PhysicalLink. Antecedent The PhysicalLink. Dependent The PhysicalElement that is linked. TRUE TRUE 2.6.0 Cables and Links utilize PhysicalConnectors to actually 'connect' PhysicalElements. This association explicitly defines this relationship of Connectors for PhysicalLinks. GroupComponent TRUE 1 The PhysicalLink that has a Connector. PartComponent The PhysicalConnector. 2.6.0 The 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. TRUE TRUE 2.6.0 A 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. GroupComponent TRUE 1 The PhysicalPackage that contains Component(s). PartComponent The PhysicalComponent which is contained in the Package. 2.6.0 The 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. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 Unknown Other SIP DIP ZIP SOJ Proprietary SIMM DIMM TSOP PGA RIMM SODIMM SRIMM SMD SSMP QFP TQFP SOIC LCC PLCC BGA FPBGA LGA 2.6.0 PhysicalMemory is a subclass of CIM_Chip, representing low level memory devices - SIMMS, DIMMs, raw memory chips, etc. FormFactor MIF.DMTF|Memory Device|005 The type of PhysicalMemory. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Unknown Other DRAM Synchronous DRAM Cache DRAM EDO EDRAM VRAM SRAM RAM ROM Flash EEPROM FEPROM EPROM CDRAM 3DRAM SDRAM SGRAM RDRAM DDR MIF.DMTF|Memory Device|005 Total 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. Bits MIF.DMTF|Memory Device|005 Data 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. Bits MIF.DMTF|Memory Device|005 The speed of the PhysicalMemory, in nanoseconds. NanoSeconds MIF.DMTF|Memory Device|005 The total capacity of this PhysicalMemory, in bytes. Bytes MIF.DMTF|Memory Device|005 A string identifying the physically labeled bank where the Memory is located - for example, 'Bank 0' or 'Bank A'. 64 MIF.DMTF|Memory Device|005 Specifies 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.6 The 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 TRUE TRUE 2.6.0 PhysicalMemory can be located on HostingBoards, adapter Cards, etc. This association explicitly defines this relationship of Memory to Cards. GroupComponent TRUE 1 The Card that includes or 'contains' Memory. PartComponent The PhysicalMemory which is located on the Card. 2.6.0 The 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. Bytes Specifies 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. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 Unknown Other Tape Cartridge QIC Cartridge AIT Cartridge DTF Cartridge DAT Cartridge 8mm Tape Cartridge 19mm Tape Cartridge DLT Cartridge Half-Inch Magnetic Tape Cartridge Cartridge Disk JAZ Disk ZIP Disk SyQuest Disk Winchester Removable Disk CD-ROM CD-ROM/XA CD-I CD Recordable WORM Magneto-Optical DVD DVD-RW+ DVD-RAM DVD-ROM DVD-Video Divx Floppy/Diskette Hard Disk Memory Card Hard Copy Clik Disk CD-RW CD-DA CD+ DVD Recordable DVD-RW DVD-Audio DVD-5 DVD-9 DVD-10 DVD-18 Magneto-Optical Rewriteable Magneto-Optical Write Once Magneto-Optical Rewriteable (LIMDOW) Phase Change Write Once Phase Change Rewriteable Phase Change Dual Rewriteable Ablative Write Once Near Field Recording MiniQic Travan 8mm Metal Particle 8mm Advanced Metal Evaporate NCTP LTO Ultrium LTO Accelis 9 Track Tape 18 Track Tape 36 Track Tape Magstar 3590 Magstar MP D2 Tape Tape - DST Small Tape - DST Medium Tape - DST Large CIM_PhysicalMedia.MediaDescription Additional 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.MediaType Boolean 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. Inches For 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. TRUE CIM_PhysicalMedia.MaxMounts Boolean 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. Indexed CIM_PhysicalMedia.LabelStates CIM_PhysicalMedia.LabelFormats An 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. Indexed 0 1 2 OK/Readable Unreadable Upside Down CIM_PhysicalMedia.PhysicalLabels An 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. Indexed 0 1 2 3 4 5 Barcode Radio Frequency Identification OCR (Optical Character Recognition) MICR (Magnetic Ink Character Recognition) 7 Character Barcode 9 Character Barcode CIM_PhysicalMedia.PhysicalLabels For 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. TRUE 2.6.0 MemoryWithMedia indicates that Memory is associated with a PhysicalMedia and its cartridge. The Memory provides media identification and also stores user-specific data. Antecedent The Memory associated with PhysicalMedia. Dependent The PhysicalMedia. TRUE 2.6.0 Within 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. Antecedent The StorageMediaLocation which holds the PhysicalMedia. 1 Dependent The Media in the Location. An 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. 0 1 2 3 4 5 Unknown Side 0 Side 1 Side A Side B Not Applicable The date and time that the Media was last placed into the referenced Location. 2.6.0 The 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. Feet Boolean 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. TRUE 2.6.0 PhysicalCapacity 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. 256 The 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. TRUE 2.6.0 ElementCapacity 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. TRUE PhysicalCapacity describes the minimum and maximum requirements, and ability to support different types of hardware for a PhysicalElement. TRUE 1 The PhysicalElement being described. 2.6.0 MemoryCapacity 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. Name TRUE The inherited Name serves as a part of the MemoryCapacity object key. TRUE The type of memory. This is a part of the object key. Values correspond to the list of possible memory types in the PhysicalMemory class. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Unknown Other DRAM Synchronous DRAM Cache DRAM EDO EDRAM VRAM SRAM RAM ROM Flash EEPROM FEPROM EPROM CDRAM 3DRAM SDRAM SGRAM RDRAM DDR CIM_PhysicalMemory.MemoryType Minimum amount of memory, in Kbytes, that is needed for the associated PhysicalElement to operate correctly. KiloBytes Maximum amount of memory, in Kbytes, that can be supported by the associated PhysicalElement. KiloBytes 2.6.0 ConfigurationCapacity 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'.\nExamples 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.\nThis 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. Name TRUE The inherited Name serves as a part of the ConfigurationCapacity object key. TRUE The type of object (power supply, fan, disk drive, ...) whose capacities are indicated. This information is part of the class' key. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 Other Processors Power Supplies Fans Batteries I/O Slots Memory Slots MediaAccessDevices (Drives) StorageMediaLocation Slots StorageMediaLocation Magazines StorageMediaLocation Panels StorageMediaLocation InterLibrary Ports StorageMediaLocation Limited Access Ports Doors MediaTransferDevice Pickers MediaTransferDevice Changers LabelReaders Contained Chassis Connected Chassis Connected Frames Front Side I/O Slots Back Side I/O Slots Cache Memory NVS Memory Volatile Memory CIM_ConfigurationCapacity.OtherTypeDescription A 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. 64 CIM_ConfigurationCapacity.ObjectType Minimum 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.6.0 Statistics 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). The number of successful physical label scans. TRUE The number of failed physical label scans. TRUE The number of retried physical label scans. TRUE The number of successful picks. TRUE The number of failed picks. TRUE The number of retried picks. TRUE The number of successful puts. TRUE The number of failed puts. TRUE The number of retried puts. TRUE FALSE 0 1 2 3 4 5 6 7 8 9 All Scan Successes Scan Failures Scan Retries Pick Successes Pick Failures Pick Retries Put Successes Put Failures Put Retries TRUE 2.6.0 Within 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. Antecedent The MediaTransferDevice that handles Media from the StorageMediaLocation. Dependent The MediaLocation that is serviced. Boolean 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. TRUE 2.6.0 StorageExtents 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. Antecedent The PhysicalComponent on which the Extent is realized. 1 Dependent The StorageExtent that is located on the Component. The 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. TRUE 2.6.0 PhysicalExtents are realized on a PhysicalMedia. This relationship is made explicit by the RealizesPExtent association. In addition, the StartingAddress of the PhysicalExtent on the PhysicalMedia is specified here. Antecedent The PhysicalMedia on which the Extent is realized. 1 Dependent The PhysicalExtent that is located on the Media. TRUE 2.6.0 DiskPartitions 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. Antecedent The PhysicalMedia on which the Extent is realized. 1 Dependent The DiskPartition that is located on the Media. TRUE 2.6.0 AggregatePExtents are realized on a PhysicalMedia. This relationship is made explicit by the RealizesAggregatePExtent association. Antecedent The PhysicalMedia on which the Extent is realized. 1 Dependent The AggregatePExtent that is located on the Media. TRUE 2.6.0 TapePartitions are realized on PhysicalTape. This relationship is made explicit by the RealizesTapePartition association. Antecedent The PhysicalTape on which the Partition is realized. 1 Dependent The TapePartition that is located on the Media. TRUE 2.6.0 Since 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. Antecedent 1 The PhysicalMedia on which the Extent is realized. An 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. 0 1 2 3 4 Unknown Side 0 Side 1 Side A Side B TRUE 2.6.0 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. Antecedent The PhysicalConnector. Dependent The NetworkAdapter that transmits using the Connector. TRUE 2.6.0 Similar to the way that LogicalDevices are 'Realized' by PhysicalElements, UnitaryComputerSystems are realized in one or more PhysicalPackages. The ComputerSystemPackage association explicitly defines this relationship. Antecedent The PhysicalPackage(s) that realize a UnitaryComputerSystem. Dependent The UnitaryComputerSystem. A Gloabally Unique Identifier for the System's Package. TRUE 2.6.0 Similar 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. Antecedent The PhysicalPackage(s) that realize a StorageLibrary. Dependent The StorageLibrary. TRUE 2.6.0 Often, 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. This relationship is described by the PackageCooling association. Antecedent The CoolingDevice for the Package. Dependent The PhysicalPackage whose environment is cooled. TRUE 2.6.0 Often, 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. This relationship is described by the PackageTempSensor association. Antecedent The TemperatureSensor for the Package. Dependent The PhysicalPackage whose environment is monitored. TRUE 2.6.0 Often, 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. This relationship is described by the PackageAlarm association. Antecedent The AlarmDevice for the Package. Dependent The PhysicalPackage whose health, security, environment, etc. is alarmed. TRUE 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.) Antecedent 1 The Location that is 'home' to a piece of PhysicalMedia. Dependent 1 The PhysicalMedia whose 'home' or default Location is defined. TRUE 2.6.0 This is an abstract base class, derived from the Service class. It serves as the root of the network service hierarchy. Network services represent generic functions that are available from the network that configure and/or modify the traffic being sent. For example, FTP is not a network service, as it simply passes data unchanged from source to destination. On the other hand, services that provide quality of service (e.g., DiffServ) and security (e.g., IPSec) do affect the traffic stream. Quality of service, IPSec, and other services are subclasses of this class. This class hierarchy enables developers to match services to users, groups, and other objects in the network. This is a free-form array of strings that provide descriptive words and phrases that can be used in queries to help locate and identify instances of this service. This is a URL that provides the protocol, network location, and other service-specific information required in order to access the service. This should be implemented as a LabeledURI, with syntax DirectoryString and a matching rule of CaseExactMatch, for directory implementors. This 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 is expected that subclasses will refine the inherited StartService() and StopService()methods to suit their own application-specific needs. This property is used to specify application-specific conditions needed by the refined StartService and StopServicemethods. This 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 is expected that subclasses will refine the inherited StartService() and StopService() methods to suit their own application-specific needs. This property is used to specify application-specific parameters needed by the refined StartService and StopService methods. TRUE 2.6.0 This association establishes the Dependency relationships that exist between an administrative domain and the NetworkServices that it hosts. This also has the semantics that the associated Services are commonly administered. \n This relationship could be viewed as a kind of HostedService. However, the latter carries the additional semantics of 'weak'ness (or naming) the NetworkService relative to the hosted System. NetworkServices are scoped/named by the network device that 'hosts' them, not by the AdminDomain in which they are administered. Therefore, this relationship is similar to HostedService, but not a subclass of it. Antecedent 1 The AdminDomain that hosts and administers the various network services. Dependent The network service that is hosted in the administrative domain. 2.6.0 This 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). \n\nForwardingService is different than RouteCalculationService in that it represents a way to forward traffic independent of calculating routing information (e.g., using static routing). Generally, the Endpoints among which a ForwardingService routes data are at the same protocol layer and are usually of similar types, or of the same type. This kind of service is used in the implementation of routers, switches and other network devices. This defines the type of protocol that is being forwarded. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 Unknown Other IPv4 IPv6 IPv4/IPv6 IPX AppleTalk DECnet SNA CONP CLNP VINES XNS ATM Frame Relay Ethernet TokenRing FDDI Infiniband Fibre Channel 32 This 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.0 An 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.\n\nThe 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. Whether a given AS is single-homed or not has important ramifications for BGP configuration. 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 BGP rule: a BGP router should not advertise destinations learned from internal BGP neighbors to external BGP destinations unless those destinations are also known via some internal gateway protocol. Otherwise, a BGP 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 into BGP. Statically injected routes are maintained by the routing table and are independent of the status of the networks that they refer to. This is done by defining static routes in the BGP routing table. Dynamically injected routes are of two types. Dynamic routes refer to distributing all of the IGP routes into BGP. Semi-dynamic routes define a set of specific IGP routes that will be injected into BGP. 0 1 2 3 Unknown Static Dynamic Semi-Dynamic Route 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., AS_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, however, that BGP4 is required to do this. \n\nThere 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. 0 1 2 3 4 Unknown None Aggregate Only Aggregate And All Specific Routes Aggregate Based on Subset of Specific Routes 2.6.0 A 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. CIM_AdminDomain.CreationClassName TRUE 256 The scoping AdminDomain's CreationClassName. CIM_AdminDomain.Name TRUE 256 The scoping AdminDomain's Name. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE 256 The Name property defines the label by which the object is known. Type is an enumeration that provides additional information that can be used to help categorize and classify different instances of this class. \n\nSubclasses 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. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 Unknown Other IPv4 IPv6 IPX AppleTalk DECnet SNA CONP CLNP VINES XNS ATM Frame Relay Ethernet TokenRing FDDI Infiniband Fibre Channel CIM_LogicalNetwork.OtherTypeDescription 64 A 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 TRUE 2.6.0 A LogicalNetworkService represents network services that either originate and/or terminate in a LogicalNetwork. This enables management applications to more easily identify services that are provided by particular network devices. TRUE The LogicalNetwork that contains the network service. TRUE The NetworkService that is running in the LogicalNetwork. An enumeration that explicitly defines this network service as originating, terminating, or residing in this LogicalNetwork. 0 1 2 3 Unknown Originates In Terminates In Resides In 2.6.0 An 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. The IP address of the entire subnet, formatted according to the appropriate convention as defined in the AddressType property of this class. \n\nNote that CIDR format is not supported for this release. This is because, without more formal methods like constraints, it is possible to create different instances of the same object that have different naming formats.\n\nIPv4-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. The mask for the starting IP address of the IPSubnet, formatted according to the appropriate convention as defined in the AddressType property of this class (e.g., '255.255.252.0'). An 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. 0 1 2 Unknown IPv4 IPv6 2.6.0 A communication point from which data may be sent or received. ProtocolEndpoints link router interfaces and switch ports to LogicalNetworks. Name 256 A string which identifies this ProtocolEndpoint with either a port or an interface on a device. To ensure uniqueness, the Name property should be prepended or appended with information from the Type or OtherTypeDescription properties. The method chosen is described in the NameFormat property of this class. 256 NameFormat 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. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 Unknown Other IPv4 IPv6 IPX AppleTalk DECnet SNA CONP CLNP VINES XNS ATM Frame Relay Ethernet TokenRing FDDI Infiniband Fibre Channel ISDN BRI Endpoint ISDN B Channel Endpoint ISDN D Channel Endpoint IPv4/v6 BGP OSPF MPLS UDP TCP CIM_ProtocolEndpoint.OtherTypeDescription 64 A 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 TRUE 2.6.0 This 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. Antecedent The ProtocolEndpoints that are used to forward the data Dependent The service that is forwarding the data TRUE 2.6.0 PortImplementsEndpoint associates a LogicalPort with one or more ProtocolEndpoints that are implemented on it. This class specializes the DeviceSAPImplementation association. It indicates that the referenced Endpoint is dependent on the operations of the Port Device. (In the cases where Ports are not currently defined for a protocol, for example for Ethernet, an Endpoint could be associated directly with an EthernetAdapter via the DeviceSAPImplementation relationship.) Antecedent The LogicalPort that represents the Device behind the ProtocolEndpoint. Dependent The ProtocolEndpoint implemented on the LogicalPort. 2.6.0 A communication endpoint which, when its associated interface device is connected to a LAN, may send and receive data frames. LANEndpoints link switch ports and host interfaces to LANs. A label or identifier for the LAN Segment. CIM_LANSegment.LANID An indication of the kind of technology used on the LAN. 0 1 2 3 4 Unknown Other Ethernet TokenRing FDDI CIM_LANSegment.LANType A free-form string that describes the type of technology used on the LAN when the value of the LANType property is equal to 1 (i.e., "Other"). This provides built-in extensibility. CIM_LANEndpoint.LANType 12 The principal unicast address used in communication with the LANEndpoint. The MAC address is formatted as twelve hexadecimal digits (e.g., "010203040506"), with each pair representing one of the six octets of the MAC address in "canonical" bit order according to RFC 2469. 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 2.6.0 A collection of LAN Endpoints of a particular type that are able to intercommunicate directly without the assistance of bridging or routing services. 64 A label or identifier for the LAN Segment. CIM_LANEndpoint.LANID An indication of the kind of technology used on the LAN. 0 1 2 3 4 Unknown Other Ethernet TokenRing FDDI CIM_LANEndpoint.LANType 64 A 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 TRUE TRUE 2.6.0 This association defines a ProtocolEndpoint as a member of a specific LogicalNetwork. Collection TRUE 1 The LogicalNetwork that groups the ProtocolEndpoint instances. Member The child ProtocolEndpoints that are components of the LogicalNetwork. TRUE TRUE 2.6.0 Defines a LANEndpoint as a member of a specific LANSegment. Collection TRUE 1 The LANSegment that groups the LANEndpoint instances. Member A child LANEndpoint that is a component of the LANSegment. TRUE 2.6.0 This association defines a connection that is currently carrying traffic between two ProtocolEndpoints. Antecedent A ProtocolEndpoint in active communication with the dependent ProtocolEndpoint. Dependent A second ProtocolEndpoint communicating with the Antecedent ProtocolEndpoint. The type of traffic that is carried over this connection. 0 1 2 3 4 5 Unknown Other Unicast Broadcast Multicast Anycast CIM_ActiveConnection.OtherTrafficDescription 64 A string describing the type of traffic that is being carried over this instance when its Type property 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 TrafficType property. This property should be set to NULL when the TrafficType property is any value other than 1. CIM_ActiveConnection.TrafficType TRUE means that this connection is uni-directional; FALSE means that this connection is bi-directional. TRUE 2.6.0 This represents a grouping of specific addresses, and provides additional semantics for this group if appropriate. 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). The 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). An enumeration that defines how to format the address and mask of the address range that defines this IPSubnet).\n\nWhenever 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. 0 1 2 Unknown IPv4 IPv6 This attribute defines the region that addresses can be allocated to. 0 1 2 3 4 5 6 7 8 Unknown Multiregional: 192.0.0.0 to 193.255.255.255 Europe: 194.0.0.0 to 195.255.255.255 Others: 196.0.0.0 to 197.255.255.255 North America: 198.0.0.0 to 199.255.255.255 Central & South America: 200.0.0.0 to 201.255.255.255 Pacific Rim: 202.0.0.0 to 203.255.255.255 Others: 204.0.0.0 to 205.255.255.255 Others: 206.0.0.0 to 207.255.255.255 2.6.0 A ProtocolEndpoint that is dedicated to running IP. The 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). The mask for the IP address of this ProtocolEndpoint, formatted according to the appropriate convention as defined in the AddressType property of this class (e.g., 255.255.252.0). An enumeration that describes the format of the address property. Whenever possible, IPv4-compatible addresses should be used instead of native 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. 0 1 2 Unknown IPv4 IPv6 It is not possible to tell from the address alone if a given IPProtocolEndpoint can support IPv4 and IPv6, or just one of these. This property explicitly defines the support for different versions of IP that this IPProtocolEndpoint has. 0 1 2 Unknown IPv4 Only IPv6 Only 2.6.0 A 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|RFC1657-MIB.bgpIdentifier This is the unique identifier of the peer BGP router. This is often the router ID (e.g., an IP address). MIB.IETF|RFC1657-MIB.bgpPeerIdentifier This defines the current connection state of the BGP Peer. 1 2 3 4 5 6 Idle Connect Active OpenSet OpenConfirm Established MIB.IETF|RFC1657-MIB.bgpPeerState This defines the desired state of the BGP connection. 1 2 Stop Start MIB.IETF|RFC1657-MIB.bgpPeerAdminStatus This defines the negotiated version of BGP that is running between the two peers. MIB.IETF|RFC1657- MIB.bgpPeerNegotiatedVersion This is the local IP address of this router's BGP connection. MIB.IETF|RFC1657-MIB.bgpPeerLocalAddr This is the local port number for the TCP connection of this router's BGP connection. MIB.IETF|RFC1657-MIB.bgpPeerLocalPort This is the remote IP address of this router's BGP connection. MIB.IETF|RFC1657-MIB.bgpPeerRemoteAddr This is the remote port number for the TCP connection of this router's BGP connection. MIB.IETF|RFC1657-MIB.bgpPeerRemotePort This is the remote AS number for this router's BGP connection. MIB.IETF|RFC1657-MIB.bgpPeerRemoteAs This 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 this 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. Seconds MIB.IETF|RFC1657-MIB.bgpPeerHoldTime This defines the time interval in seconds for the KeepAlive timer established with the peer. The value of this property is calculated by this 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. Seconds MIB.IETF|RFC1657-MIB.bgpPeerKeepAlive 2.6.0 An 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.6.0 A network or subnet that uses the IPX protocol. An IPX network number formatted as eight hexadecimal digits (e.g., "00112233"). TRUE 2.6.0 NextHopRouting 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. \n\nSubclasses of NextHopRouting provide specific protocol and Key information. For example, the IPRoute subclass contains an AddressType property as part of its key structure. This property is not required for next hop information defined for Infiniband. \n\nNextHopRoutes are dependent on at least one ForwardingService to execute them. This is conveyed by the CIM_NextHopForwardedByService association. The address which serves as the destination to be reached. The mask for the DestinationAddress. This contains either the address of the next-hop router, or the interface used to reach the destination. TRUE indicates that this is a static route, and FALSE indicates a dynamically-learned route. TRUE 2.6.0 This 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. Antecedent 1 Dependent This 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. PathMetric provides a numeric indication as to the preference of this route compared to other routes that reach the same destination. TRUE 2.6.0 An 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. \n\nSince 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. CIM_ForwardingService.SystemCreationClassName TRUE 256 The scoping ForwardingService's SystemCreationClassName. CIM_ForwardingService.SystemName TRUE 256 The scoping ForwardingService's SystemName. CIM_ForwardingService.CreationClassName TRUE 256 The scoping ForwardingService's CreationClassName. CIM_ForwardingService.Name TRUE 256 The scoping ForwardingService's Name. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE The 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. \n\nThis 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.DestinationAddress TRUE The mask for the destination IP address, formatted according to the appropriate convention as defined in the AddressType property of this class. \n\nThis 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.DestinationMask TRUE An 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. \n\nAddressType is part of the key so that an IPv4 and an IPv6 route to IP subnets with the same network number but different versions (v4/v6) can coexist 0 1 2 Unknown IPv4 IPv6 DestinationAddress CIM_IPRoute.IPDestinationAddress DestinationMask CIM_IPRoute.IPDestinationMask TRUE 2.6.0 This 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. Antecedent 1 1 Dependent TRUE TRUE 2.6.0 This association establishes a ServiceAccessPoint as a requestor of protocol services from a ProtocolEndpoint. Typically, this association runs between SAPs and endpoints on a single system. 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. Antecedent Dependent TRUE 2.6.0 This association makes explicit the dependency of a ProtocolEndpoint on some lower layer ProtocolEndpoint on the same system. Antecedent This describes the framing method for the upper layer protocol endpoint that is bound to a LANEndpoint. Note: "Raw802.3" is only known to be used with the IPX protocol. 0 1 2 3 4 Unknown Ethernet 802.2 SNAP Raw802.3 2.6.0 BGPIPRoute 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. 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. TRUE 2.6.0 This association defines a BGP route, and makes explicit the dependency between a BGPIPRoute and a BGPProtocolEndpoint. Antecedent 2 The BGPProtocolEndpoints that represent the source and destination (or at least the next hop) of the BGP route. Dependent 1 The routing table entry that represents a BGP route. TRUE 2.6.0 This 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 administered by the same network admin that administrates the domain. TRUE 1 1 The AdminDomain that hosts the various LogicalNetworks. TRUE TRUE The LogicalNetworks that are hosted by the AdminDomain. 2.6.0 The 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. \n\nThe 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. \n\nAn AS can have more than one route reflector. There can be more than one route reflector in a cluster, and there can be more than one cluster in an AS. TRUE If 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. TRUE TRUE 2.6.0 This aggregation establishes 'whole-part' relationships between a BGPCluster and the ComputerSystems (e.g., the routers) that it contains. At least three routers are required to form a cluster - a reflector and two clients. In addition, the routers that form a cluster share common configuration information, and are commonly administered. Collection TRUE 1 The Cluster that aggregates the routers belonging to it and administers them. Member 3 The routers that form the Cluster. TRUE TRUE 2.6.0 This aggregation establishes 'whole-part' relationships between an AutonomousSystem and the BGPClusters that it contains. In addition, the routers that form a cluster share common configuration information, and are commonly administered. TRUE TRUE 1 The AutonomousSystem that aggregates the Clusters belonging to it and administers them. TRUE The Clusters that are contained in the AS. TRUE TRUE 2.6.0 This 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. GroupComponent TRUE 1 The AutonomousSystem that aggregates the routers belonging to it and administers them. PartComponent The Routers that are contained in the AS. This 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. 0 1 2 3 4 5 6 7 Unknown Other Conventional BGP Speaker Route Reflector Router Reflector Client Route Reflector Non-Client Peer Group Member Confederation Member CIM_BGPService.OtherRoleDescription 64 A 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 TRUE 2.6.0 This association represents the endpoints that a network service provides to access it. Antecedent 1 The NetworkService that is being accessed by the ProtocolEndpoints. Dependent The ProtocolEndpoints that provide access to the NetworkService. TRUE TRUE 2.6.0 This aggregation defines the different router interfaces that are running BGP in the AutonomousSystem. GroupComponent TRUE 1 The AutonomousSystem that aggregates the router interfaces that are running BGP. PartComponent The router interfaces that are contained in the AS. TRUE TRUE 2.6.0 The 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. This 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. GroupComponent TRUE 1 The AutonomousSystem that contains the confederations. PartComponent The Confederation within the AutonomousSystem. A unique identifier of the AutonomousSystem that contains the confederations. A unique identifier of the Confederation within the AutonomousSystem. TRUE 2.6.0 This is an abstract base class, derived from NetworkService, that represents the route calculation aspects of a router. This class also addresses functions performed by the router when it exchanges routing information. \n\nNote that there are a large variety of additional routing protocols that are not enumerated below, or currently subclassed. These will be added as models are developed. 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. 0 1 2 3 4 5 6 7 8 Unknown RIPv1 RIPv2 OSPFv1 OSPFv2 BGPv1 BGPv2 BGPv3 BGPv4 TRUE 2.6.0 This assocation makes explicit the routes that are calculated by a specific RouteCalculationService. Thus, every RouteCalculationService can have its own unique set of calculated routes. Antecedent 1 Dependent TRUE 2.6.0 This is a specialization of CIM_HostedService, which is anassociation between a Service and the System on which the functionality resides. The ComputerSystem is made up of different routing services, which take the form of internal and external routing protocols. These are different NetworkServices, and are weak with respect to their hosting ComputerSystem. Antecedent 1 1 The hosting router. Dependent The Service hosted on the System. TRUE 2.6.0 This is a specialization of CIM_HostedService, which is anassociation between a Service and the System on which the functionality resides. The ComputerSystem is made up of different forwarding services, which take the form of internal and external routing protocols. These are different NetworkServices, and are weak with respect to their hosting ComputerSystem. Antecedent 1 1 The hosting router. Dependent The Service hosted on the System. TRUE 2.6.0 This is a specialization of ServiceServiceDependency, and captures the dependency that external gateway protocols (such as BGP) have on interior gateway protocols (such as OSPF). Antecedent The independent RouteCalculationService that provides routing information from the AS, for the EGP to use. Dependent The dependent RouteCalculationService (e.g., the RouteCalculationService that is functioning as an EGP. Sometimes 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. 1 2 3 None Partial Full 2.6.0 This 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|RFC1657-MIB.bgpVersion BGP 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. 0 1 2 3 4 5 6 None Message Header Error OPEN Message Error UPDATE Message Error Hold Timer Expired Finite State Machine Error Cease This defines the BGP error subcode for message header errors. If the ErrorCode property is any other value, then this property should be set to NULL. 0 1 2 3 None Connection Not Synchronized Bad Message Length Bad Message Type CIM_BGPService.ErrorCode This defines the BGP error subcode for OPEN message errors. If the ErrorCode property is any other value, then this property should be set to NULL. 0 1 2 3 4 5 6 None Unsupported Version Number Bad Peer AS Bad BGP Identifier Unsupported Optional Parameter Authentication Failure Unacceptable Hold Time CIM_BGPService.ErrorCode This defines the BGP error subcode for UPDATE message errors. If the ErrorCode property is any other value, then this property should be set to NULL. 0 1 2 3 4 5 6 7 8 9 10 11 None Malformed Attribute List Unrecognized Well-Known Attribute Missing Well-Known Attribute Attribute Flags Error Attribute Length Error Invalid Origin Attribute AS Routing Loop Invalid NEXT_HOP Attribute Optional Attribute Error Invalid Network Field Malformed AS_path CIM_BGPService.ErrorCode 2.6.0 A 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.\n\nA BGPPeerGroup is weak to the AutonomousSystem that contains it. Therefore, the keys from System must be propagated to it. CIM_AutonomousSystem.CreationClassName TRUE 256 The scoping AutonomousSystem's CreationClassName. CIM_AutonomousSystem.Name TRUE 256 The scoping AutonomousSystem's Name. TRUE The type of class that this instance is. 256 TRUE This is the name of the BGP Peer Group. This defines the time interval, in seconds, for the ConnectRetry timer. The suggested value is 120 seconds. Seconds MIB.IETF|RFC1657-MIB.bgpConnectRetryInterval This 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. This 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. Seconds MIB.IETF|RFC1657-MIB.bgpPeerHoldTimeConfigured This 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. Seconds MIB.IETF|RFC1657-MIB.bgpPeerKeepAliveConfigured This defines the time interval in seconds for the MinASOriginationInterval timer. The suggested value for this property is 15 seconds. Seconds MIB.IETF|RFC1657-MIB.bgpPeerMinASOriginationInterval This defines the time interval in seconds for the MinRouteAdvertisementInterval timer. The suggested value for this property is 30 seconds. Seconds MIB.IETF|RFC1657-MIB.bgpPeerMinRouteAdvertisementInterval TRUE 2.6.0 A BGPPeerGroup is weak to the AutonomousSystem that contains it. This association formalizes that relationship. Antecedent 1 1 The AutonomousSystem that scopes the BGP peer group. Dependent TRUE The BGP peer group defined in the context of the AutonomousSystem. TRUE 2.6.0 This association will serve as the base class for defining BGP routing policies for the reflector of this Cluster. Antecedent 1 The Cluster for which this policy is being defined. Dependent 1 The BGPService to which the policy will be applied in the Cluster. TRUE 2.6.0 This association will serve as the base class for defining BGP routing policies for clients of the reflector of this Cluster. Antecedent 1 The Cluster for which this policy is being defined. Dependent 1 The BGPService to which the policy will be applied in the Cluster. TRUE 2.6.0 This association will serve as the base class for defining BGP routing policies for the non-clients of the reflector of this Cluster. Antecedent 1 The Cluster for which this policy is being defined. Dependent The BGPService to which the policy will be applied in the Cluster. 2.6.0 FilterEntryBase is an abstract class to define the naming of all filter entries, and to allow their common aggregation into FilterLists. The FilterEntry subclass represents packet filtering. Other types of Entries are possible - for example, to filter security credentials. \n FilterEntryBase is weak to the network device (i.e., the ComputerSystem) that contains it. Hence, the ComputerSystem keys are propagated to this class. CIM_ComputerSystem.CreationClassName TRUE 256 The scoping ComputerSystem's CreationClassName. CIM_ComputerSystem.Name TRUE 256 The scoping ComputerSystem's Name. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE 256 The 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.6.0 A 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.\n\nThis class is oriented towards packet filtering. Other subclasses of FilterEntryBase can be defined to do other types of filtering. \n\nA 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. 0 1 2 3 4 Unknown IPv4 IPX IPv6 Any This 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. 1 2 3 4 5 6 7 8 9 10 11 12 13 Other Source Address and Mask Destination Address and Mask Source Port Source Port Range Destination Port Destination Port Range Protocol Type Protocol Type and Option DSCP ToS Value 802.1P Priority Value Any CIM_FilterEntry.OtherMatchConditionType If 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.MatchConditionType This 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. 1 2 Permit Deny This 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. CIM_NextService.TrafficClass 2.6.0 IPHeadersFilter 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: \nipv4(4): OctetString(SIZE (4)) \nipv6(6): OctetString(SIZE (16|20)), \ndepending on whether a scope identifier is present. \n\nIf 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. 4 6 IPv4 IPv6 CIM_IPHeadersFilter.HdrSrcAddress CIM_IPHeadersFilter.HdrSrcAddressEndOfRange CIM_IPHeadersFilter.HdrSrcMask CIM_IPHeadersFilter.HdrDestAddress CIM_IPHeadersFilter.HdrDestAddressEndOfRange CIM_IPHeadersFilter.HdrDestMask HdrSrcAddress 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. \n\nIf 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. TRUE CIM_IPHeadersFilter.HdrIPVersion HdrSrcAddressEndOfRange 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. \n\nIf 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. TRUE CIM_IPHeadersFilter.HdrIPVersion HdrSrcMask 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. \n\nIf 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. TRUE CIM_IPHeadersFilter.HdrIPVersion HdrDestAddress 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. \n\nIf 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. TRUE CIM_IPHeadersFilter.HdrIPVersion HdrDestAddressEndOfRange 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. \n\nIf 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. TRUE CIM_IPHeadersFilter.HdrIPVersion HdrDestMask 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. \n\nIf 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. TRUE CIM_IPHeadersFilter.HdrIPVersion HdrProtocolID is an 8-bit unsigned integer, representing an IP protocol type. This value is compared to the Protocol field in the IP header. \n\nIf 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. \n\nA 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. \n\nIf 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. \n\nA 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. \n\nIf 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. \n\nA 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. \n\nIf 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. \n\nA 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. \n\nIf 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. HdrDSCP 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. \n\nSince, 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. \n\nHdrDSCP 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. \n\nIf 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. 63 The 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'. \n\nIf 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. TRUE 2.6.0 A 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.\n\nA 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.CreationClassName TRUE 256 The scoping ComputerSystem's CreationClassName. CIM_ComputerSystem.Name TRUE 256 The scoping ComputerSystem's Name. TRUE The type of class that this instance is. TRUE 256 This 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. \n\n"Not Applicable" (0) is used when there is no direction applicable to the FilterList.\n"Input" (1) is used when the FilterList applies to packets that are inbound on the related interface.\n"Output" (2) is used when the FilterList applies to packets that are outbound on the related interface.\n"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.\n"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. 0 1 2 3 4 Not Applicable Input Output Both Mirrored TRUE TRUE 2.6.0 All filter entries (FilterEntryBase and its subclasses) can be used directly in the implementation of a network device such as a router, host or firewall, or they can be aggregated in a FilterList. Since both of these uses are possible, FilterEntryBase is defined as weak to the ComputerSystem (i.e., the network device) where it is used to identify and act on network traffic. GroupComponent TRUE 1 1 The ComputerSystem/network device that aggregates the FilterEntry, for identifying and acting on network traffic. PartComponent TRUE The FilterEntry used in the System's operation. TRUE TRUE 2.6.0 The purpose of this weak association is to model the use of a FilterList by a ComputerSystem (e.g., a router, firewall or host). One example of such a use is in the QoS Model, where a ClassifierService aggregates a set of FilterLists in order to build its services. GroupComponent TRUE 1 1 The ComputerSystem/network device that aggregates the FilterList and administers it. PartComponent TRUE The FilterList used in the System's operation. 2.6.0 This 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 BGP attributes in a consistent manner.\n\nA RoutingPolicy is weak to the network device (i.e., the ComputerSystem) that contains it. Hence, the ComputerSystem keys are propagated to this class. CIM_ComputerSystem.CreationClassName TRUE 256 The scoping ComputerSystem's CreationClassName. CIM_ComputerSystem.Name TRUE 256 The scoping ComputerSystem's Name. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE 256 This is the name of the Routing Policy. The Description property is a free-form string that provides a textual description of the routing policy. This defines the type of action that will be performed if the match conditions of this filter policy are met. There are essentially three choices: forward the traffic unmodified, forward the traffic, but modify either the BGP 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. 1 2 3 4 5 6 7 8 9 Accept As Is Accept With BGP Changes Accept and Remark Packet Accept With BGP and Remark Changes Accept With Other Actions Accept With BGP Changes and Other Actions Accept with Remark Changes and Other Actions Accept with BGP and Remark Changes and Other Actions Deny This defines one or more BGP attributes that should beused to modify this routing update. 1 2 3 4 5 6 7 8 9 10 Origin AS_Path NEXT_HOP Multi_Exit_Disc Local_Pref Atomic_Aggregate Aggregator Community Originator_ID Cluster_List The value for the corresponding BGPAction. This defines a remarking action for this traffic. 1 2 3 4 5 6 7 Change DSCP Change ToS Change 802.1Q Value Change CIR Change CBR Change ABR Change VBR The value for the corresponding RemarkAction. This defines other actions to be taken for this traffic. 1 2 3 4 5 6 7 Other Input Flow Policing Output Flow Policing Input Aggregate Policing Output Aggregate Policing PoliceByMarkingDown PoliceByDroppingDown If 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.ConditioningAction The value for the corresponding ConditioningAction. This controls whether BGP attribute values replace, get prepended, or get appended to their existing values. 1 2 3 Replace Prepend Append TRUE 2.6.0 A RoutingPolicy is weak to the network device (i.e., the ComputerSystem) that contains it. This association formalizes that relationship. Antecedent 1 1 The network device/computer system that scopes the RoutingPolicy. Dependent TRUE The routing policy defined in the context of the network device. TRUE TRUE 2.6.0 This 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. GroupComponent TRUE 1 The FilterList, which aggregates the set of FilterEntries. PartComponent Any subclass of FilterEntryBase which is a part of the FilterList. The order of the Entry relative to all others in the FilterList. A value of zero indicates that all the Entries should be ANDed together. Use of the Sequence property should be consistent across the List. It is not valid to define some Entries as ANDed in the FilterList (Sequence=0) while other Entries have a non-zero Sequence number. TRUE TRUE 2.6.0 This is a specialization of the CIM_Component aggregation which is used to define a set of FilterLists that are aggregated by a particular RoutingPolicy. GroupComponent TRUE The RoutingPolicy, which aggregates the set of FilterLists. PartComponent A FilterList, which is part-of the RoutingPolicy. The position of the FilterList relative to all other entries in the RoutingPolicy. TRUE 2.6.0 This is a specialization of the Dependency association, and defines the relationship between a BGPService and the RoutingPolicy that control it. Antecedent The BGP routing policy object. Dependent The BGPService that is controlled by the routing policy. TRUE 2.6.0 This defines the relationship between a BGPService and the BGP Peer Group that hosts it. Antecedent 1 1 The BGP Peer Group that hosts the BGP Service. Dependent The BGPService that is hosted in the BGP Peer Group. 2.6.0 Information 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.\n\nAdministrativeDistance, being a global object, is weak to the AdminDomain that contains it. Hence, the AdminDomain keys are propagated to this class. CIM_AdminDomain.CreationClassName TRUE 256 The scoping AdminDomain's CreationClassName. CIM_AdminDomain.Name TRUE 256 The scoping AdminDomain's Name. TRUE The type of class that this instance is. TRUE 256 This is the name of the AdministrativeDistance class. The distance for directly connected peers. It has a default value of 0. The distance for staticly connected peers. It has a default value of 1. The distance for peers using EBGP. It has a default value of 20. The distance for peers using internal EIGRP. It has a default value of 90. The distance for peers using IGRP. It has a default value of 100. The distance for peers using OSPF. It has a default value of 110. The distance for peers using ISIS. It has a default value of 115. The distance for peers using RIP. It has a default value of 120. The distance for peers using EGP. It has a default value of 140. The distance for peers using external EIGRP. It has a default value of 170. The distance for peers using IBGP. It has a default value of 200. The distance for peers using BGP locally. It has a default value of 200. The distance for peers using an unknown protocol. It has a default value of 255. TRUE 2.6.0 AdministrativeDistance, being a global object, is weak to the AdminDomain that contains it. This association formalizes that relationship. Antecedent 1 1 The AdminDomain that scopes the AdministrativeDistance. Dependent TRUE The table of (global) administrative distances that are defined in the context of the AdminDomain. TRUE 2.6.0 This is a specialization of the Dependency association, and defines the relationship between a BGPService and the Administrative Distances that it uses to control the (BGP) routing decisions that it makes. Antecedent 1 1 The table of (global) administrative distances that are used by all BGP services. Dependent The BGP service object, that makes BGP routing decisions. 2.6.0 A 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 (see accompanying white paper). \n\nRoute maps may use FilterLists to identify the route (again, see the accompanying white paper). \n\nA BGPRouteMap is specific to a given AutonomousSystem that contains it. Hence, the keys of the AutonomousSystem are propagated to this class. CIM_AutonomousSystem.CreationClassName TRUE 256 The scoping AutonomousSystem's CreationClassName. CIM_AutonomousSystem.Name TRUE 256 The scoping AutonomousSystem's Name. TRUE The type of class that this instance is. TRUE 256 This is the name of the RouteMap class. This defines whether this RouteMap is used for input, output, or both input and output filtering. 1 2 3 Input Output Both This defines whether the action should be to forward or deny traffic meeting the match condition specified in this RouteMap 1 2 Permit Deny This 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. 1 2 3 4 5 6 7 8 9 Other Source Address and Mask Destination Address and Mask Source Port Source Port Range Destination Port Destination Port Range Protocol Type Protocol Type and Option CIM_RouteMap.OtherMatchConditionType If 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.MatchConditionType This defines an additional action to take if the MatchCondition is satisfied. This definition is specifically limited to BGP filtering for now (e.g., its use is limited to setting a BGP attribute to a specific value), and will be upgraded in a subsequent release. The actual value of the metric is specified in the SetMetricValue property. 1 2 3 4 5 6 7 8 9 Origin AS_Path NEXT_HOP Multi_Exit_Disc Local_Pref Atomic_Aggregate Aggregator Community Originator_ID This is the value of the metric that is being set for the BGP attribute defined in the SetMetricType property. TRUE 2.6.0 A BGPRouteMap is weak to the AutonomousSystem that contains it. This association formalizes that relationship. Antecedent 1 1 The AutonomousSystem that scopes the BGP route map. Dependent TRUE The BGP route map defined in the context of the AutonomousSystem. TRUE TRUE 2.6.0 This aggregation defines the RouteMaps 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. GroupComponent TRUE The RoutingPolicy that aggregates the RouteMaps. PartComponent The RouteMaps that are used by the RoutingPolicy. This defines the position of this RouteMap instance relative to all other instances of the same RouteMap. TRUE TRUE 2.6.0 This 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. Collection TRUE The BGPPeerGroup that aggregates the RouteMaps. Member The RouteMaps that are used by the BGPPeerGroup. This defines the position of this RouteMap instance relative to all other instances of the same RouteMap. TRUE 2.6.0 RouteMaps do not have to use FilterLists, but if they do, this association defines which FilterList is used by a particular RouteMap. Antecedent The FilterList used by a RouteMap. Dependent The RouteMap using the FilterList. TRUE TRUE 2.6.0 This aggregation defines the specific routers (i.e., ComputerSystems) that participate in a PeerGroup. Collection TRUE 1 The PeerGroup that aggregates the routers. Member 2 The routers that comprise the PeerGroup. TRUE 2.6.0 This is a specialization of the ServiceSAPDependency association, indicating that the referenced ProtocolEndpoint is utilized by the RouteCalculationService to provide its functionality. Antecedent The required ProtocolEndpoint Dependent The RouteCalculationService, which is dependent on the underlying ProtocolEndpoint. TRUE indicates that this ProtocolEndpoint represents a static route, and FALSE means that it represents a dynamically-learned route. 2.6.0 This class defines all of the BGP Attributes, for a given version of the BGP protocol, that can be used to affect routing decisions. \n\nBGPAttributes are specific to a given AutonomousSystem that contains it. Hence, the keys of the AutonomousSystem are propagated to this class. CIM_AutonomousSystem.CreationClassName TRUE 256 The scoping AutonomousSystem's CreationClassName. CIM_AutonomousSystem.Name TRUE 256 The scoping AutonomousSystem's Name. TRUE This 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|RFC1657-MIB.bgp4PathAttrLocalPref This 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|RFC1657-MIB.bgp4PathAttrASPath This 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|RFC1657-MIB.bgp4PathAttrNextHop This 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|RFC1657-MIB.bgp4PathAttrMultiExitDisc This 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 attribute gets set 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. MIB.IETF|RFC1657- MIB.bgp4PathAttrAtomicAggregate This specifies the AS and IP address of the router that has generated an aggregate. MIB.IETF|RFC1657- MIB.bgp4PathAttrAggregatorAS This 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. 1 2 3 IGP EGP INCOMPLETE MIB.IETF|RFC1657-MIB.bgp4PathAttrOrigin This is the router ID for the ORIGIN attribute. TRUE 2.6.0 The class BGPAttributes is weak to the AutonomousSystem that contains it. This association formalizes that relationship. Antecedent 1 1 The AutonomousSystem that scopes the BGP attributes. Dependent TRUE The BGP attributes defined in the context of the AutonomousSystem. TRUE TRUE 2.6.0 This 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. GroupComponent TRUE The RoutingPolicy, which aggregates a set of BGP attributes. PartComponent A BGP attribute, which is part-of the RoutingPolicy. 2.6.0 This class defines the per-path information used to process specific BGP attribute information, as defined in the bgp4PathAttrTable of RFC 1657. This 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: \n <type, length, value>\n\nThe type is a 1-octet field which has two possible values: \n 1 = AS_SET \n 2 = AS_SEQUENCE \nAn 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. \n\nThe length is a 1-octet field containing the number of ASs in the value field. \n\nThe 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;\n\nThis 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. Indexed MIB.IETF|RFC1657-MIB.bgp4PathAttrASPathSegment TRUE 512 A 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. TRUE 32 This is the address of the border router that should be used for the destination network. MIB.IETF|RFC1657-MIB.bgp4PathAttrNextHop This 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. 1 2 3 IGP EGP INCOMPLETE MIB.IETF|RFC1657-MIB.bgp4PathAttrOrigin This 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|RFC1657- MIB.bgp4PathAttrMultiExitDisc This 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|RFC1657-MIB.bgp4PathAttrLocalPref This 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. 1 2 Less Specific Not Selected Less Specific Selected MIB.IETF|RFC1657- MIB.bgp4PathAttrAtomicAggregate This is the AS number of the last BGP4 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|RFC1657- MIB.bgp4PathAttrAggregatorAS This is the IP address of the last BGP4 speaker that performed route aggregation. A value of 0.0.0.0 indicates the absence of this attribute. MIB.IETF|RFC1657- MIB.bgp4PathAttrAggregatorAddr This is the degree of preference calculated by the receiving BGP4 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|RFC1657- MIB.bgp4PathAttrCalcLocalPref This is an indication of whether or not this route was chosen as the best BGP4 route. There are three possible values, 0 (Unknown), 1 (FALSE) and 2 (TRUE). 0 1 2 Unknown False True MIB.IETF|RFC1657-MIB.bgp4PathAttrBest This contains one or more path atributes not understood by this BGP4 speaker. The MIB variable is an OctetString, and contains a 1-octet length field and up to 254 additional octets of data. The length is placed in a separate attribute of this class, PathAttrUnknownNumber. CIM_BGPPathAttributes.PathAttrUnknownNumber MIB.IETF|RFC1657-MIB.bgp4PathAttrUnknown The MIB variable is an OctetString, and contains a 1-octet length field and up to 255 additional octets of data. The length is placed in this attribute. CIM_BGPPathAttributes.PathAttrUnknown MIB.IETF|RFC1657-MIB.bgp4PathAttrUnknown TRUE 2.6.0 This defines the attributes that are transmitted between BGP peers on a per-route basis. Antecedent 1 The BGPPathAttribute object that may be associated with a BGP route. Dependent 1 The BGPIPRoute that may have an associated set of per-peer attributes. This defines the IP address of the peer where the path information was learned. MIB.IETF|RFC1657-MIB.bgp4PathAttrPeer This defines the length in bits of the IP address prefix in the Network Layer Reachability information field. The range of this attribute is defined to be 0 to 32. MIB.IETF|RFC1657- MIB.bgp4PathAttrIpAddrPrefixLen An IP address prefix in the Network Layer Reachability Information field. This object is an IP address containing the prefix with length specified by the PathAttrIpAddrPrefixLen attribute. CIM_BGPPathAttributes.PathAttrIpAddrPrefixLen MIB.IETF|RFC1657- MIB.bgp4PathAttrIpAddrPrefix TRUE TRUE 2.6.0 This is a specialization of the Component aggregation. This aggregation defines the set of BGP Attributes that are transmitted in per-path UPDATE messages. GroupComponent TRUE 1 The BGPService that aggregates BGP attributes as part of its routing information. PartComponent 1 1 The BGP attribute, which are part-of the BGP UPDATE message. 2.6.0 Generic switch (bridging) service class. Additional switching functions are incorporated as subordinate services related to this class via ServiceComponent associations. 32 Address 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.BridgeAddressType MIB.IETF|RFC1493- MIB.dot1dBaseBridgeAddress The number of switch ports controlled by this switching service. MIB.IETF|RFC1493-MIB.dot1dBaseNumPorts Indicates what type of switching service can be performed. 1 2 3 4 Unknown Transparent-only SourceRoute-only SRT MIB.IETF|RFC1493-MIB.dot1dBaseType BridgeAddressType defines the type of addressing scheme used for this Bridge and its BridgeAddress property. 1 2 3 4 5 Other IPv4 IPv6 MAC MAC + Spanning Tree Priority CIM_SwitchingService.BridgeAddress 2.6.0 Switch Port from which frames are received and out which they are transmitted. Numeric identifier for a switch port. MIB.IETF|RFC1493-MIB.dot1dPort TRUE 2.6.0 A SwitchService switches frames between SwitchPorts. This association makes that relationship explicit. Antecedent The switch port. Dependent 1 The switching service. TRUE 2.6.0 A switch port has a LANEndpoint that is exposed via this relationship. Antecedent 1 The switch port. Dependent 1 The LAN endpoint. 2.6.0 This service class represents the learning/transparent bridging aspect of switch service. The timeout period in seconds for aging out dynamically learned forwarding information. 802.1D-1990 recommends a default of 300 seconds. Seconds MIB.IETF|RFC1493-MIB.dot1dTpAgingTime Filtering Database Identifier. Used by VLAN-aware switch having more than one filtering database. MIB.IETF|RFC????-MIB.dot1qFdbId 2.6.0 This 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. 1 2 3 Unknown DEC LB100 IEEE 802d MIB.IETF|RFC1493- MIB.dot1dStpProtocolSpecification The 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. \n\nA 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|RFC1493- MIB.dot1dStpPriority 16 The Bridge ID (Priority + MAC Address) of the root bridge.\n\nThe 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. 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|RFC1493-MIB.dot1dStpDesignatedRoot The cost of the path from the switch to the root. MIB.IETF|RFC1493-MIB.dot1dStpRootCost The port number of the port having the lowest cost path to the root bridge. MIB.IETF|RFC1493-MIB.dot1dStpRootPort The current value for the maximum age of Spanning Tree information before discard, as learned from the network. Hundredths of Seconds MIB.IETF|RFC1493-MIB.dot1dStpMaxAge The 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 Seconds MIB.IETF|RFC1493-MIB.dot1dStpHelloTime The minimum interval between transmission of bridge PDUs through a given port, as learned from the network. Hundredths of Seconds MIB.IETF|RFC1493-MIB.dot1dStpHoldTime The 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 Seconds MIB.IETF|RFC1493-MIB.dot1dStpForwardDelay The MaxAge parameter to be used by all switches in the network if this switch becomes the root. Hundredths of Seconds MIB.IETF|RFC1493-MIB.dot1dStpBridgeMaxAge The HelloTime parameter to be used by all switches in the network if this switch becomes the root. Hundredths of Seconds MIB.IETF|RFC1493-MIB.dot1dStpBridgeHelloTime The ForwardDelay parameter to be used by all switches in the network if this switch becomes the root. Hundredths of Seconds MIB.IETF|RFC1493- MIB.dot1dStpBridgeForwardDelay MAC 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. \n\nNote 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. TRUE 2.6.0 A 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. Antecedent The switch port. Dependent The spanning tree service. The 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|RFC1493-MIB.dot1dStpPortPriority The current state of the port as determined by the spanning tree protocol. 1 2 3 4 5 6 Disabled Blocking Listening Learning Forwarding Broken MIB.IETF|RFC1493-MIB.dot1dStpPortState The enabled/disabled status of the port. 1 2 Enabled Disabled MIB.IETF|RFC1493-MIB.dot1dStpPortEnable The contribution of this port to the path cost of paths towards the spanning tree root which include this port. MIB.IETF|RFC1493-MIB.dot1dStpPortPathCost The 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|RFC1493- MIB.dot1dStpPortDesignatedRoot The cost of the path to the root offered by the designated bridge for the segment. MIB.IETF|RFC1493- MIB.dot1dStpPortDesignatedCost The bridge identifier of the designated bridge for the segment to which the port is attached. MIB.IETF|RFC1493- MIB.dot1dStpPortDesignatedBridge The port identifier of the port on the designated bridge serving the segment to which the port is attached. MIB.IETF|RFC1493- MIB.dot1dStpPortDesignatedPort 2.6.0 A DynamicForwardingEntry represents an entry in the forwarding (filtering) database associated with the transparent bridging service. CIM_System.CreationClassName TRUE 256 The scoping System's CreationClassName. CIM_System.Name TRUE 256 The scoping System's Name. CIM_Service.CreationClassName TRUE 256 The scoping Service's CreationClassName. CIM_Service.Name TRUE 256 The scoping Service's Name. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE 6 Unicast MAC address for which the transparent bridging service has forwarding and/or filtering information. \n\nNote 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|RFC1493-MIB.dot1dTpFdbAddress The status of the entry. 1 2 3 4 5 Other Invalid Learned Self Mgmt MIB.IETF|RFC1493-MIB.dot1dTpFdbStatus TRUE 2.6.0 This association links an instance of the transparent bridging service to the entries of its forwarding database. The forwarding database is weak to the service. Antecedent 1 1 The transparent bridging service. Dependent TRUE Dynamic Forwarding Entry of forwarding database. TRUE 2.6.0 This association links a dynamic forwarding entry and the switch port to which the entry applies. Antecedent 1 1 The switch port. Dependent Dynamic Forwarding Entry of forwarding database. 2.6.0 A StaticForwardingEntry represents an entry in the static (destination-address filtering) database associated with the switch service. CIM_System.CreationClassName TRUE 256 The scoping System's CreationClassName. CIM_System.Name TRUE 256 The scoping System's Name. CIM_Service.CreationClassName TRUE 256 The scoping Service's CreationClassName. CIM_Service.Name TRUE 256 The scoping Service's Name. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE 6 Destination MAC address (unicast, multicast or broadcast) to which the filtering information applies. \n\nNote 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|RFC1493-MIB.dot1dStaticAddress The status of the entry. 1 2 3 4 5 Other Invalid Permanent DeleteOnReset DeleteOnTimeout MIB.IETF|RFC1493-MIB.dot1dStaticStatus The ports to which frames with the destination MAC address arriving on the port represented by the SwitchPortStaticForwarding association are allowed to be forwarded. TRUE 2.6.0 This association links an instance of the transparent bridging service to the entries of its static (destination-address filtering) database. Antecedent 1 1 The transparent bridging service. Dependent TRUE Static Forwarding Entry of forwarding database. TRUE 2.6.0 This association links a static database entry and the switch port to which the entry applies. Antecedent 1 The switch port. Dependent Static Forwarding Entry of static database. TRUE TRUE 2.6.0 An association linking SwitchService to a component TransparentBridgingService. The cardinality of the TransparentBridgingService is 0..1 for a VLAN-unaware switch. GroupComponent TRUE 1 The parent service. PartComponent The component service. TRUE TRUE 2.6.0 An association linking SwitchService to a component SpanningTreeService. The cardinality of the SpanningTreeService is 0..1 for a VLAN-unaware switch. GroupComponent TRUE 1 The parent service. PartComponent The component service. 2.6.0 SourceRoutingService 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. For this reason, it is not defined as a subclass of NetworkService. Instead, SourceRoutingService is aggregated into a higher level Network/Forwarding/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. 1 2 Mode3 Mode6 MIB.IETF|RFC1525-MIB.dot1dSrBridgeLfMode TRUE TRUE 2.6.0 An association linking SwitchService to a component SourceRoutingService. The cardinality of the SourceRoutingService is 0..1 for a VLAN-unaware switch. GroupComponent TRUE 1 The parent service. PartComponent The component service. TRUE 2.6.0 This association represents information regarding port pairings that is used by the SourceRoutingService of a switch. Antecedent 1 The lower numbered port. Dependent 1 The higher numbered port. A 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|RFC1525-MIB.dot1dPortPairBridgeNum The state of dot1dPortPairBridgeNum. Writing 'invalid(3)' to this property removes the association instance. 1 2 3 Enabled Disabled Invalid MIB.IETF|RFC1525-MIB.dot1dPortPairBridgeState TRUE 2.6.0 A switch capable of source routing maintains source-routing specific information about each port. This association represents that information. Antecedent The switch port. Dependent 1 The source routing service. The maximum number of routing descriptors allowed in an All Paths or Spanning Tree Explorer frames. MIB.IETF|RFC1525-MIB.dot1dSrPortHopCount The 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|RFC1525-MIB.dot1dSrPortLocalSegment A 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|RFC1525-MIB.dot1dSrPortBridgeNum The segment number that corresponds to the target segment this port is considered to be connected to by the switch. 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|RFC1525-MIB.dot1dSrPortTargetSegment Determines 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, this 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. 1 2 3 Auto-Span Disabled Forced MIB.IETF|RFC1525-MIB.dot1dSrPortSTESpanMod 2.6.0 An instance of VLAN represents a VLAN within a switch. In a particular switch, there should be an instance of VLAN for every VLAN available in the switch. 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.\n\nVLAN 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. It's irritating to see a list sorted 'VLAN 1, VLAN 10, VLAN 11, VLAN 2, VLAN 3...', when it could have been 'VLAN 0001, VLAN 0002, ..., VLAN 0010, VLAN 0011, ....'.) The numeric part of the name should be at least four digits wide since 802.1Q specifies 4095 VLANs.\n\nIt 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.\n\nAn 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 received on a port in 802.1Q VLAN 5 will be transmitted from a port in 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. \n\nIn 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 would be an attribute of the subclass. If it is desirable to representthe VLAN assignment predicate in a protocol-based VLAN switch, it will be necessary to subclass VLAN, InboundVLAN, or both. If the predicate applies to all ports in the switch, then only VLAN need be subclassed. 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. TRUE 2.6.0 The 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. Antecedent Dependent 1 1 TRUE 2.6.0 This association identifies the spanning tree in which a forwarding database (TransparentBridgingService) is nested. Antecedent Dependent 1 TRUE 2.6.0 This association makes explicit the operational dependencies of a SwitchPort when operating in a VLAN.\n\nIf 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 VLAN in question. Antecedent Dependent If 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 if 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.\n\nIf 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. \n\nNote 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 by default. For 802.1Q-compliant ports, the Default property should be true on the association instance connecting a SwitchPort to the CIM_VLAN corresponding to the port's PVID. Default should never be true if Tagged is true -- it applies only to untagged packets. TRUE 2.6.0 This association makes explicit the operational dependencies of a SwitchPort when operating in a VLAN. \n\nIf there is no instance of OutboundVLAN between a given SwitchPort and CIM_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. Antecedent Dependent If 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. TRUE 2.6.0 VLANService 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.\n\nVLANService must be subclassed so that instances can be distinguished by their class. If there is a name assigned to a set of VLAN-aware switches, e.g., the VTP domain name in Cisco Catalyst switches, use the Name attribute inherited from CIM_Service to store the name.\n\nA VLANService should be instantiated in a VLAN-aware switch even if there is no GVRP-like protocol. 2.6.0 If 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. TRUE TRUE 2.6.0 An association linking SwitchService to a component VLANService. GroupComponent TRUE 1 1 PartComponent TRUE 2.6.0 The VLAN Port used by the VLAN Service. Antecedent Dependent 1 2.6.0 Statistical information regarding the Transparent Bridging Service. TRUE The 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|RFC1493- MIB.dot1dTpLearnedEntryDiscards 2.6.0 Statistical information regarding the Spanning Tree Service. The time since the last topology change was detected by the switch. Hundredths of Seconds MIB.IETF|RFC1493- MIB.dot1dStpTimeSinceTopologyChange TRUE The total number of topology changes detected by the switch since the counter was last reset or initialized. MIB.IETF|RFC1493-MIB.dot1dStpTopChanges 2.6.0 Statistical information regarding a generic switch port, independent of the specific kind of switching done on frames arriving at the port. TRUE The number of frames discarded by this port due to excessive transit delay through the bridge. MIB.IETF|RFC1493- MIB.dot1dBasePortDelayExceededDiscards TRUE The number of frames discarded by this port due to an excessive size. MIB.IETF|RFC1493- MIB.dot1dBasePortMtuExceededDiscards 2.6.0 Statistical information regarding a switch port, at which transparent bridging is performed. TRUE The 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|RFC1493-MIB.dot1dTpPortInFrames TRUE The 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|RFC1493-MIB.dot1dTpPortOutFrames TRUE Count of valid frames received which were discarded (i.e., filtered) by the Forwarding Process. MIB.IETF|RFC1493-MIB.dot1dTpPortInDiscards 2.6.0 Statistical information regarding a switch port participating in the spanning tree. TRUE The number of times the port has transitioned from the Learning state to the Forwarding state. MIB.IETF|RFC1493- MIB.dot1dStpPortForwardTransitions 2.6.0 Statistical information regarding a switch port supporting source routing. TRUE The 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|RFC1525-MIB.dot1dSrPortSpecInFrames TRUE The number of Specifically Routed frames, also referred to as Source Routed Frames, that the port has transmitted on its segment. MIB.IETF|RFC1525-MIB.dot1dSrPortSpecOutFrames TRUE The 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|RFC1525-MIB.dot1dSrPortApeInFrames TRUE The 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|RFC1525-MIB.dot1dSrPortApeOutFrames TRUE The number of spanning tree explorer frames that have been received by the port from its segment. MIB.IETF|RFC1525-MIB.dot1dSrPortSteInFrames TRUE The number of spanning tree explorer frames that have been transmitted by the port on its segment. MIB.IETF|RFC1525-MIB.dot1dSrPortSteOutFrames TRUE The number of explorer frames that have been discarded by the port because the routing descriptor field contained an invalid adjacent segment value. MIB.IETF|RFC1525- MIB.dot1dSrPortSegmentMismatchDiscards TRUE The number of frames that have been discarded by the port because the routing descriptor field contained a duplicate segment identifier. MIB.IETF|RFC1525- MIB.dot1dSrPortDuplicateSegmentDiscards TRUE The 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|RFC1525- MIB.dot1dSrPortHopCountExceedsDiscards TRUE The number of duplicate LAN IDs or Tree errors. This helps in detection of problems in networks containing older IBM Source Routing Bridges. MIB.IETF|RFC1525- MIB.dot1dSrPortDupLanIdOrTreeErrors TRUE The 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|RFC1525- MIB.dot1dSrPortLanIdMismatches 2.6.0 This class contains statistical information for a Group sessions. TRUE This is the number of BGP UPDATE messages received on this router's BGP connection. This is a 32-bit counter. MIB.IETF|RFC1657-MIB.bgpPeerInUpdates TRUE This is the number of BGP UPDATE messages transmitted on this router's BGP connection. This is a 32-bit counter. MIB.IETF|RFC1657-MIB.bgpPeerOutUpdates TRUE This is the total number of BGP messages received on this router's BGP connection. This is a 32-bit counter. MIB.IETF|RFC1657-MIB.bgpPeerInTotalMessages TRUE This is the total number of BGP messages transmitted on this router's BGP connection. This is a 32-bit counter. MIB.IETF|RFC1657-MIB.bgpPeerOutTotalMessages This 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|RFC1657-MIB.bgpPeerLastError TRUE This 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|RFC1657-MIB.bgpPeerFsmEstablishedTransitions TRUE This 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. Seconds MIB.IETF|RFC1657-MIB.bgpPeerFsmEstablishedTime TRUE This 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. Seconds MIB.IETF|RFC1657-MIB.bgpPeerInUpdateElapsedTime TRUE 2.6.0 This association defines statistics collected for a BGP session. Stats 1 The statistics object for the BGP session. Element 1 1 The BGPService for which statistics are being gathered. TRUE 2.6.0 CIM_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. SystemElement SystemElement represents one aspect of the Endpoint. SameElement SameElement represents an alternate aspect of the Endpoint. 2.6.0 This 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. \n\nThis 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.\n\nFor example, Gold Service may be defined as a set of sub-services, where each of these sub-services perform one or more different functions required by the higher-level service. Continuing the example, Gold Service may be used to specify EF for one traffic stream along with different AF services for other different traffic streams. Each of these services are instances of the class QoSService, and each require a set of sub-services to be defined as part of their implementation. For example, one would expect to see different marking, dropping, and queuing sub-services to be defined for each of these services. TRUE TRUE 2.6.0 The 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. \n 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). GroupComponent TRUE 1 The higher level QoSService that is constructed by aggregating one or more lower-level QoSServices. PartComponent The more concrete QoSService that is used to provide the higher level Service. 2.6.0 This 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. \n\nThis 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, to devices that do support DiffServ, which use DSCPs. \n\nSince the PrecedenceService class is a specialization of QoSService, it can be related to higher-level QoS services as well as to lower-level sub-services (e.g., classification, metering, dropping, queuing, and others). This property is an 8-bit unsigned integer that defines the notion of precedence for different types of traffic. 2.6.0 DiffServService represents using standard or custom DiffServ services to implement a (higher-level) QoS service. Note that the DiffServService may be just one of a set of coordinated QoSSubServices that together implement a higher-level QoS service.\n\nDiffServService is modeled as a specialization of QoSService. This enables it to be related to a higher-level QoSService (via QoSSubService) as well as to specific ConditioningServices (e.g., classification, metering, dropping, queuing, and others). This 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. 2.6.0 This class represents a specialization to 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. \n\nThis 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. \n\nThe 8021PService class is modeled as a specialization of QoSService. This enables it to be related to a higher-level QoS service as well as to lower-level sub-services (e.g., classification, metering, dropping, queuing, and others). This property is an 8-bit unsigned integer that defines the notion of priority as specified in 802.1P implementations. 2.6.0 This 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.\n\nNote that this RFC defines 12 DSCPs that together implement the AF Per-Hop Behavior (PHB) group. Implementations are free to extend this (e.g., add more classes and/or drop precedences) and indeed do not have to implement the AF PHB to be considered compliant to DiffServ. However, implementations should use this set of DSCPs if they implement the AF PHB. \n\nThe AFService class is modeled as a specialization of DiffServService, which is in turn a specialization of QoSService. This enables it to be related to a higher-level QoS services as well as to lower-level sub-services (e.g., classification, metering, dropping, queuing, and others). This property is an 8-bit unsigned integer that defines the number of classes that this AF implementation uses. Implementations should define at least four classes. This property is an 8-bit unsigned integer that defines the number of drop precedence values that this AF implementation uses. The number of drop precedence values are PER AF CLASS. Implementations should define at least three drop precedence values per class. 2.6.0 This class represents a specialization to 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). \n\nThe EFService class is modeled as a specialization of DiffServService, which is in turn a specialization of QoSService. This enables it to be related to a higher-level QoS service as well as to lower-level sub-services (e.g., classification, metering, dropping, queuing, and others). \n\nThe 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. \n\nThe EF PHB is not a mandatory part of the DiffServ architecture (e.g., a node does not have to implement the EF PHB to be considered DiffServ-compliant. However, when a DiffServ-compliant node claims to implement the EF PHB, the implementation must conform to the specification given in RFC2598.\n\nRFC 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. TRUE 2.6.0 The 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. TRUE 1 The AFService with a lower drop precedence (ie, lower probability of dropping packets). TRUE An AFService at the same IP packet-forwarding class level, but at a higher drop precedence. 2.6.0 This class is a specialization of ForwardingService, and represents the ability to define how traffic will be conditioned in the data forwarding path of a device. The subclasses of ConditioningService define the particular type of conditioning that is done. Five fundamental types of functions are defined in this version (2.4) of the model. They are the services performed by a classifier, meter, marker, dropper, and queue. Note that other, more sophisticated, types of actions may be defined in the future. This 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. TRUE TRUE 2.6.0 A 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). GroupComponent TRUE 1 The QoSService that includes the ConditioningService. PartComponent The ConditioningService. TRUE 2.6.0 The 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. Antecedent 1 The ProtocolEndpoint through which traffic arrives at or leaves from a network device. Dependent The ConditioningService which begins or ends the traffic conditioning processing within a network device. Indicates whether a packet is incoming (value = 1, "Ingress") or out-going (value = 2, "Egress") at the ProtocolEndpoint, relative to the ConditioningService. 0 1 2 Unknown Ingress Egress TRUE 2.6.0 In processing or 'conditioning' a packet at a network device, that packet is handled by a variety of ConditioningServices (such as Classifiers, Meters, Droppers, etc.). The Services may feed one another directly, or be more discretely mapped to multiple 'next' Services (for example, queues) based on the characteristics of the packet. \n There is a need to indicate the sequence of Services when conditioning packets in a network device. This is accomplished via the NextService association. Both one-to-one and fan in/fan out relationships can be described. \n Note that this relationship is truly a Dependency association, but can not be modeled as such - since an additional key property is required. This key allows a ConditioningService to forward multiple traffic flows to the same 'next' Service but maintain their traffic 'identity'. This identity must be maintained to allow a later step in the conditioning process to 'fan out' from one to many 'next' Services. The TrafficClass key property uniquely distinguishes potentially multiple NextService instances between the same ConditioningServices. TRUE The preceeding ConditioningService, 'earlier' in the processing sequence for a packet. TRUE The 'next' or following ConditioningService. TRUE Traffic flows from the various ConditioningServices may be distinguished by their specific traffic class (information which is conveyed in the FilterEntry.TrafficClass property). There can be only one traffic 'class of service' per output from the ConditioningService (i.e., per instance of this association). CIM_FilterEntry.TrafficClass 2.6.0 This class represents a logical entity that resides in the data forwarding path of a network device. A classifier takes a single input traffic stream and sorts it into one or more output traffic streams. The sorting is done by a set of filters that select packets based on the packet contents (or possibly other attributes associated with the packet). Each output stream is the result of matching a particular filter (or not matching any filter). \n\nClassification is modeled as a QoSSubService that occurs as part of the conditioning that may be applied to a traffic stream. Thus, it is subclassed from ConditioningService. This property is an enumerated 16-bit unsigned integer that is used to define the specific type of classifier of this instance. The following types of classifiers are defined: \n\n 1 - Other; \n 2 - Behavior Aggregate; \n 3 - IPv4 Multi-Field-5; \n 4 - IPv6 Multi-Field-5; \n 5 - IPv4 Multi-Field-6; \n 6 - IPv6 Multi-Field-6; \n 7 - 802 MAC; \n 8 - IEEE Priority; \n 9 - IEEE VLAN; \n 10 - Free-form. \n\nHere, Multi-Field-5 defines a filter to match on source and destination IP address, source and destination port, and IP Protocol. Multi-Field-6 is the same, except that the DSCP value is also matched. 1 2 3 4 5 6 7 8 9 10 Other Behavior Aggregate IPv4 Multi-Field-5 IPv6 Multi-Field-5 IPv4 Multi-Field-6 IPv6 Multi-Field-6 802 MAC IEEE Priority IEEE VLAN Free-form CIM_ClassifierService.OtherClassifierType This is a vendor-specified string describing the type of classifier. It is used when the value of the ClassifierType attribute of this class is equal to 1. CIM_ClassifierService.ClassifierType This is a boolean attribute that, if TRUE, means that this Classifier has already processed at least one packet. TRUE 2.6.0 In 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. Antecedent 1 The FilterList aggregating FilterEntries, these in turn describe how traffic is identified and processed by the ClassifierService. Dependent The ClassifierService which uses the FilterList and its aggregated FilterEntries. The ordering of the FilterLists used in the classification and forwarding functions of the ClassifierService. 2.6.0 This class represents a logical entity that resides in the data forwarding path of a network device. It describes 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 traffic and non-conforming traffic. Non-conforming packets may be further conditioned (e.g., dropped or queued) by routing the packet to the appropriate conditioning element. \n\nThis class is the base class for defining different types of meters. As such, it contains common properties that all meter subclasses share. 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: \n\n 1: Other \n 2: AverageRateMeter \n 3: EWMAMeter \n 4: TokenBucketMeter.\n\nNote: 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. 1 2 3 4 Other AverageRateMeter EWMAMeter TokenBucketMeter CIM_MeterService.OtherMeterType This 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.MeterType An 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.6.0 This class represents a logical entity that resides in the data forwarding path of a network device. It describes the metering of network traffic using 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. \n\nThis is modeled as a subclass of ConditioningService and has the ability to invoke different ConditioningServices for conforming and non-conforming traffic. This property is a 32-bit real number that defines the rate that determines whether admitted packets are in conformance or not. KiloBits per Second This property is a 64-bit unsigned integer that defines the time period over which the average measurement should be taken. NanoSeconds 2.6.0 This class represents a logical entity that resides in the data forwarding path of a network device. It describes the metering of network traffic using an Exponentially Weighted Moving Average meter. This meter can be modeled as a simple IIR 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. \n\nThis is modeled as a subclass of ConditioningService and has the ability to invoke different ConditioningServices for conforming and non-conforming traffic. This property is a 32-bit real number 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. KiloBits Per Second This property is a 64-bit unsigned integer that defines the sampling interval used to measure the arrival rate in bytes. 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. NanoSeconds This property is a 32-bit real number that defines the time constant (e.g. frequency response) of what is essentially a simple IIR low-pass filter. 2.6.0 This class represents a logical entity that resides in the data forwarding path of a network device. It describes the metering of network traffic using a token bucket meter. Two types of token bucket meters are defined using this class - a simple, 2 parameter bucket meter, and a multi-stage meter.\n\nA simple token bucket usually has two parameters, an average token rate and a burst size. Quoting from the IETF Draft, 'A Conceptual Model for DiffServ Routers', "TB meters compare the arrival rate of packets to the average rate specified by the TB profile. Logically, tokens accumulate in a bucket at the average rate, up to a maximum credit which is the burst size. Packets of length L bytes are considered conforming if any tokens are available in the bucket at the time of packet arrival: up to L bytes may then be borrowed from future token allocations. Packets are allowed to exceed the average rate in bursts up to the burst size. Packets which arrive to find a bucket with no tokens in it are deemed non-conforming." This type of meter has only two conformance levels - conforming and non-conforming. \n\nThis class also defines an excess burst size, which enables the meter to have three conformance levels (basically, 'conforming', 'partially conforming', and 'non-conforming'). The difference is that packets that exceed the excess burst size are deemed non-conforming, while packets that exceed the smaller BurstSize but are less than the ExcessBurstSize are deemed partially conforming. \n\nThis is modeled as a subclass of ConditioningService and has the ability to invoke different ConditioningServices for conforming, partially conforming and non-conforming traffic. This property is a 32-bit real number that is used to define the committed rate of the meter. KiloBits per Second This attribute is a 32-bit real number that is used to define the peak rate of the meter. KiloBits per Second This property is a 32-bit real number that is used to define the maximum number of tokens available for the committed rate (specified by the AverageRate property). KiloBytes This property is a 32-bit real number that is used to define the maximum number of tokens available for the peak rate (specified by the PeakRate property). KiloBytes TRUE 2.6.0 Describes the 'next' ConditioningService for a packet, after processing by the MeterService. PreceedingService The MeterService. Information on the result of the metering. Traffic is distinguished as being in- or out-of-profile, or "Partially Conforming" for a 3 color Meter. This is captured through setting the property to the value 1, 3 or 2, respectively. 0 1 2 3 Unknown In-profile Partially Conforming Out-of-profile 2.6.0 This class represents a logical entity that resides in the data forwarding path of a network device. It describes the marking or re-marking (e.g., set or reset a particular field in a packet header) of network traffic. Markers may act either on unmarked packets or re-mark previously marked packets. Markers are usually invoked as a result of a preceding classifier match. \n\nThis is modeled as a QoSSubService that is part of a higher-level QoSService. It is a subclass of ConditioningService and has the ability to mark traffic and then invoke another ConditioningServices for further processing of the traffic. This property is a boolean attribute that, when TRUE, signifies that this Marker can remark the field value specified in the RemarkType property, with the value specified in the RemarkValue property. This change is made to unmarked packets or to re-mark a previously marked packet. This property is an enumerated 16-bit unsigned integer that defines what type of remarking will be done. Values are: \n\n 1: Other \n 2: Mark ToS Byte \n 3: Mark the DSCP \n 4: Mark the Priority Field 1 2 3 4 Other Mark ToS Byte Mark the DSCP Mark the Priority Field CIM_MarkerService.OtherRemarkType This property contains a vendor-specific value for the type of remarking that is done. It is used when the value of the RemarkType property is 1 (Other). CIM_MarkerService.RemarkType This property is a 16-bit unsigned integer that is the value to be applied to the field specified in the RemarkType attribute. 2.6.0 This class represents a logical entity that resides in the data forwarding path of a network device. It describes the ability to drop network traffic. As such, it is the base class for different types of droppers. These droppers are distinguished by the algorithm that they use to drop traffic. \n\nThis is modeled as a QoSSubService that is part of a higher-level QoSService. It is a subclass of ConditioningService and has the ability to drop traffic or invoke another ConditioningServices for further processing of the remaining traffic. This property is an enumerated 16-bit unsigned integer that defines the type of dropper. Values are: \n\n 1: Other \n 2: Head \n 3: Tail \n 4: RED \n 5: Weighted RED\n\nNote: 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 a Head or Tail Dropper in today's model). Therefore, DropperService can be instantiated directly and the Type property is needed. 1 2 3 4 5 Other Head Tail RED Weighted RED CIM_DropperService.OtherDropperType This 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.DropperType This property indicates whether the Dropper will always drop incoming packets (value=1) regardless of their type. 0 1 2 Unknown Always Drop Do Not Always Drop This 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: \n\n 1: Other \n 2: Queue Threshold \n 3: Arrival Rate 1 2 3 Other Queue Threshold Arrival Rate This 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: \n\n 1: Other \n 2: Queue Threshold \n 3: Arrival Rate 1 2 3 Other Queue Threshold Arrival Rate 2.6.0 This 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 Random Early Detection (RED) algorithm. The purpose of RED is to avoid congestion (as opposed to managing congestion). That is, instead of waiting for the queues to fill up and then dropping large numbers of packets, RED works by monitoring the average queue depth. When the queue depth exceeds a minimum threshold, packets are randomly discarded, asking only those connections to slow down. \n\nThis is modeled as a QoSSubService that is part of a higher-level QoSService. It is a subclass of ConditioningService and has the ability to drop traffic or invoke another ConditioningServices for further processing of the remaining traffic. This property is a 32-bit unsigned integer, and is used to define the minimum queue length at which packets are subject to being dropped according to the dropping algorithm being used. This property is a 32-bit unsigned integer, and is used to define the maximum queue length at which packets are subject to always being dropped regardless of the dropping algorithm being used. This property is a 32-bit real number, and is used in conjunction with the StopProbability attribute to define the slope of the drop probability function. The latter governs the rate at which packets are subject to being dropped, as a function of the queue length. 0 100 CIM_REDDropperService.StopProbability This property is a 32-bit real number, and is used in conjunction with the StartProbability attribute to define the slope of the drop probability function. The latter governs the rate at which packets are subject to being dropped, as a function of the queue length. 0 100 CIM_REDDropperService.StartProbability 2.6.0 This 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. \n\nThis is modeled as a QoSSubService that is part of a higher-level QoSService. It is a subclass of ConditioningService and has the ability to drop traffic or invoke another ConditioningServices for further processing of the remaining traffic. This property is an enumerated 16-bit unsigned integer, and defines the type of metric that is used to drop traffic. Values are: \n\n 1: Other \n 2: IP Precedence \n 3: DSCP Value \n 4: 802.1P Priority Value \n 5: RSVP Session \n 6: Queue Depth \n 7: Packet Arrival Rate 1 2 3 4 5 6 7 Other IP Precedence DSCP Value 802.1P Priority Value RSVP Session Queue Depth Packet Arrival Rate CIM_WeightedREDDropperService.OtherDropMetric This 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.DropMetric This is a 32-bit real number that represents the weighting factor used to determine which queues get more service. 0 100 2.6.0 This class represents a logical entity that resides in the data forwarding path of a network device. It describes the ability to queue network traffic and to specify the characteristics for determining long-term congestion. \n\nThis is modeled as a QoSSubService that is part of a higher-level QoSService. It is a subclass of ConditioningService and has the ability to queue traffic or invoke another ConditioningServices for further processing. This property is a 32-bit real number, and defines the degree to which each actual queue depth influences the averaged (smoothed) queue depth used for determining long-term congestion in RED-like droppers. This property is specified as the percentage/weight that each calculation of averaged queue depth influences the new value of average depth. 0 100 This property is a 32-bit unsigned integer, and defines the number of nano-seconds between each calculation of average queue depth. When this property is not specified, it implies that the calculation is performed every time a packet departs from the queue under normal operating conditions. In other words, if the queue is serviced intermittently, the calculations will be performed logically to simulate a consistent queue servicing interval. NanoSeconds This property is a boolean attribute that, if TRUE, enables the queue to be made available to other queue/scheduler instances. When true, the queue can be used to hold packets from other traffic classes than normally serviced. For example, assume that queues for Gold, Silver and Bronze traffic classes are defined. Further assume that the Silver queue is full and the others are empty. If this boolean is set for the Gold and Bronze queues, their capacity can be used to hold Silver traffic, as opposed to dropping it. TRUE 2.6.0 Describes 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. Antecedent The supporting queue(s) and its QueuingService. This Service can only support at most one, higher level QueuingService. Dependent 1 The QueuingService dependent on other, supporting QueuingServices. 2.6.0 This 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.\n\nIn 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. \n\nNote 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. TRUE CollectionID 256 This property is defined in the CollectionOfMSEs class, but is overridden here to serve as part of the (composite) key that identifies the BufferPool instance. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. 256 The 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. This 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. TRUE 2.6.0 Describes the reliance of a QueuingService on the availability of space in a BufferPool. Antecedent The BufferPool supporting packet storage for a QueuingService. Dependent The QueuingService dependent on the BufferPool for storage space. TRUE TRUE 2.6.0 CIM_CollectedBufferPool is an aggregation association representing that a Pool may itself be contained in a 'higher level' Pool. Collection TRUE The 'higher level' or parent Pool. Member The 'collected' Pool. 2.6.0 This 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 queue that the scheduler is servicing. One can describe that different schedulers support different queues, or that a scheduler supports several queues. \n\nPacketSchedulingService is modeled as a sibling service to ConditioningService. Both are derived from a common root, ForwardingService. This property is an enumerated 16-bit unsigned integer, and defines the type of scheduler. Values are: \n\n 1: Other \n 2: FIFO \n 3: Priority \n 4: Bandwidth \n 5: Priority Bandwidth \n 6: Round Robin Packet \n 7: Weighted Round Robin Packet. \n\nNote: The SchedulerType property and the SchedulerService subclasses provide similar information. This property is defined for query purposes and to not require a subclass for all types of SchedulerServices (for example, to describe a FIFO Scheduler in today's model). Therefore, SchedulerService can be instantiated directly and the Type property is needed. 1 2 3 4 5 6 7 Other FIFO Priority Bandwidth Priority Bandwidth Round Robin Packet Weighted Round Robin Packet CIM_PacketSchedulingService.SchedulerType This string property is used in conjunction with the SchedulerType property. When the value of SchedulerType is 1 (i.e., "Other"), then the type of metric to be used is defined in this attribute. CIM_ PacketSchedulingService.SchedulerType TRUE 2.6.0 In 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. Antecedent 1 1 The PacketSchedulingService which empties the QueuingService's queue. Dependent The queue and its QueuingService from which packets are emptied. 2.6.0 This class represents a simple priority scheduler, which is a process that schedules arriving packets into different priority queues. \n\nThis is modeled as a specialization of the PacketSchedulingService, which is a sibling service to ConditioningService. Both PacketSchedulingService and ConditioningService instances are derived from a common root, ForwardingService. This property is a 16-bit unsigned integer that defines the priority level of the queue that is being scheduled. 2.6.0 This class represents a priority scheduler that is extended to specify an upper limit on the bandwidth that can be sent on the priority queue, over some time interval.\n\nThis is modeled as a specialization of the PacketSchedulingService, which is a sibling service to ConditioningService. Both PacketSchedulingService and ConditioningService instances are derived from a common root, ForwardingService. This property is a 32-bit unsigned integer, and defines the number of bytes that can be delivered from a queue each cycle. Bytes This is a boolean property which, if TRUE, signifies that a temporary or short-term allocation of additional bandwidth in addition to the amount of bandwidth allocated through the BandwidthAllocation attribute is allowed. This property is a 32-bit unsigned integer, and specifies the amount of temporary or short-term bandwidth that can be allocated beyond the amount of bandwidth allocated through the BandwidthAllocation attribute. If the maximum actual bandwidth allocation were to be measured, it would be the sum of the BurstAllocation and the BandwidthAllocation properties. Bytes 2.6.0 This class represents a bandwidth scheduler, which is a process that reserves a portion of the bandwidth of a link for each selected traffic type. This is modeled as a specialization of the PacketSchedulingService, which is a sibling service to ConditioningService. Both PacketSchedulingService and ConditioningService instances are derived from a common root, ForwardingService. This property is a 32-bit unsigned integer, and defines the number of bytes that can be delivered from a queue each cycle. Bytes This is a boolean attribute which, if TRUE, signifies that a temporary or short-term allocation of additional bandwidth in addition to the amount of bandwidth allocated through the BandwidthAllocation attribute is allowed. This property is a 32-bit unsigned integer, and specifies the amount of temporary or short-term bandwidth that can be allocated beyond the amount of bandwidth allocated through the BandwidthAllocation attribute. If the maximum actual bandwidth allocation were to be measured, it would be the sum of the BurstAllocation and the BandwidthAllocation properties. Bytes This is a boolean attribute that, if TRUE, enables unused bandwidth from the associated queue to be allocated to queues that need additional resources. This is a boolean attribute that, if TRUE, prevents the scheduler from bursting traffic from the queue to which this instance of the scheduler is associated (via SchedulerUsed). When TRUE, this attribute also prevents bandwidth from other idle queues to be consumed by the associated queue, thereby preventing resource allocations above the assigned bandwidth. 2.6.0 This class represents a round robin packet scheduler, which is a process that guarantees that bandwidth will be allocated fairly at the packet level. With this type of scheduler, each associated queue is entitled to equal access to the output interface. This is modeled as a specialization of the PacketSchedulingService, which is a sibling service to ConditioningService. Both PacketSchedulingService and ConditioningService are derived from a common root, ForwardingService. 2.6.0 This class represents a weighted round robin packet scheduler, which is the same as a fair packet scheduler except that a per-traffic stream multiplier is applied to each stream. This is modeled as a specialization of the PacketSchedulingService, which is a sibling service to ConditioningService. Both PacketSchedulingService and ConditioningService are derived from a common root, ForwardingService. This property is a real 32-bit number, which is used to define the weighting factor that will be used to offer some queues a higher probability of being serviced than other queues. This property represents this probability. 0 100 This property is a 16-bit unsigned integer, which specifies a tie breaker in the event that two or more queues achieve an equal weighting. While this condition may not occur in some implementations of a weighted round robin scheduler, there are many implementations that require a priority to resolve this condition. However, in instances where this behavior is not necessary or is undesirable, this property may be left unspecified. TRUE 2.6.0 PRS_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. \n\nPRS_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. TRUE The 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. 0 1 2 3 Clean New Modified Deleted The 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. \n\nIt is the responsibility of the entity creating, modifying or deleting the object derived from ExchangeElement to set this property appropriately. \n\nThis property value is set to 'Clean' by an invocation of the Transaction Complete method with a Status parameter of zero (0). 2.6.0 PRS_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. \n\nPRS_Solution is directly associated to one or more of the following classes: \n PRS_Reference \n PRS_Problem \n PRS_Resolution The Solution title. A brief description of the Solution. 0 1 2 254 255 Reference Diagnostic How To Other Unknown The 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. TRUE 2.6.0 PRS_SolutionElement is an abstract base class for non-Category objects that are associated with a Solution. This includes: \n PRS_Reference \n PRS_Problem \n PRS_Resolution \n\nPRS_SolutionElement provides a common reference for these objects to be associated with PRS_Expression objects through the SolutionExpression association. \n\nIn addition, all of the derived objects may be retrieved with a single query for the common super-class. 2.6.0 PRS_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.0 PRS_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. \n\nThe 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. 0 100 The 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. 0 100 2.6.0 PRS_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. \n\nThe 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. 0 100 TRUE TRUE TRUE 2.6.0 PRS_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. Antecedent TRUE 1 The PRS_Solution root object of the Solution. Dependent The PRS_Reference, PRS_Problem or PRS_Resolution aggregated into the Solution by this association. TRUE TRUE 2.6.0 PRS_SolutionReference aggregates a Reference into a Solution. Dependent The PRS_Reference aggregated into the Solution. TRUE TRUE 2.6.0 PRS_SolutionProblem aggregates a Problem into a Solution. Dependent The PRS_Problem aggregated into the Solution. TRUE TRUE 2.6.0 PRS_SolutionResolution aggregates a Resolution into a Solution. Dependent The PRS_Solution aggregated into the Solution. 2.6.0 PRS_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. \n\nNote: 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. TRUE 2.6.0 PRS_SolutionCategory associates PRS_Solution with a PRS_Category for classification purposes. Antecedent 1 The PRS_Solution being classified. Dependent The specific PRS_Category being used to classify the Solution. TRUE 2.6.0 PRS_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. Antecedent The PRS_Category used for classification. Dependent 1 The specific PRS_Reference, PRS_Problem or PRS_Resolution classified by this association. TRUE 2.6.0 PRS_CategoryParentChild is used to define classification hierarchies. Antecedent The parent PRS_Category used for classification. Dependent The child PRS_Category used for classification. TRUE 2.6.0 PRS_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.0 PRS_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.0 PRS_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.0 PRS_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. \n\nPRS_Statements may be grouped together to build compound 'sentences'. For example, \n StatementA = Printer output is blotchy. \n StatementB = Print jobs per day are less than 50. \n ExpressionA = StatementA AND StatementB. 0 1 2 3 4 5 6 7 8 9 10 11 254 255 Description Symptom Error_Message Objective Evidence Cause Work_Around Fix Answer Keyword Changes Title Other Unknown StatementRole 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. 0 100 2.6.0 PRS_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: \n Print jobs per day are less than 50\n\nThis could be described using a PRS_Feature as follows: \n Description: 'Print jobs per day' \n Prompt: 'How many print jobs per day?' \n ValidValues: '10' '50' '100' \n DataType: 'Integer' \n\nThe associated PRS_Statement would contain: \n Operator: '<' \n FeatureValue: '50' \n Prompt presented through user interface. Valid values for this PRS_Feature. 0 1 2 3 4 5 254 255 String Integer Float Date/Time Boolean Binary Other Unknown Data type used for PRS_Statement FeatureValue property. 2.6.0 Each 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. TRUE TRUE 2.6.0 Associates a PRS_Expression with PRS_ExpressionElements such as PRS_Expression, PRS_Product, and PRS_Statement. TRUE Antecedent 1 The parent PRS_Expression. Dependent 1 The child PRS_ExpressionElement, either a PRS_Expression, PRS_Product or PRS_Statement. TRUE TRUE 2.6.0 Products 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. TRUE Antecedent The parent PRS_Product. Dependent The child PRS_Product. TRUE TRUE 2.6.0 PRS_ProductComponent is used to describe 'has a' relationships between Products and their components parts. See PRS_ProductParentChild for 'is a' relationships. TRUE Antecedent The PRS_Product which contains the component. Dependent The component PRS_Product. TRUE 2.6.0 PRS_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. Antecedent The product. Dependent The expression. TRUE 2.6.0 Associates PRS_Statement with PRS_Feature. Antecedent The PRS_Statement. Dependent The PRS_Feature. TRUE 2.6.0 Associates PRS_Feature with PRS_Resource. This is used to track labor and costs associated with specific tasks defined in a Feature object. Antecedent The PRS_Feature. Dependent The PRS_Resource. TRUE 2.6.0 Associates PRS_Resolution with PRS_Resource. Antecedent The PRS_Resource. Dependent The PRS_Resolution. TRUE TRUE 2.6.0 Associates PRS_SolutionElements (PRS_Reference, PRS_Problem or PRS_Resolution) with PRS_Expressions. TRUE Antecedent 1 The PRS_SolutionElement. Dependent 1 The PRS_Expression. 2.6.0 PRS_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. \n\nIf 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.\n\nFor 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. 0 1 2 Level 0 means all information within a Reference, Problem or Resolution is conveyed by a single PRS_Statement. \n\nLevel 1 means there may be multiple PRS_Statement instances within a Reference, Problem or Resolution. \n\nLevel 2 means that a PRS_Statement may be associated with a PRS_Feature instance within a Reference, Problem or Resolution. 0 1 2 254 255 Draft Reviewed Published Other Unknown Editorial 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. 0 1 2 3 254 255 Proprietary Internal Partner Public Other Unknown Intended 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. TRUE 2.6.0 Associates PRS_Administrative data with any object derived from PRS_ExchangeElement. Antecedent 1 The PRS_ExchangeElement. Dependent The PRS_Administrative object. 2.6.0 PRS_Revision records changes to the content. The date of this revision. 0 1 2 254 255 Create Update Delete Other Unknown The name of the specific revision being made. 0 1 2 254 255 Technical Editorial Administrative Other Unknown Type 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. 0 1 2 3 254 255 Open Not Reviewed Reviewed Approved Other Unknown The 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. 0 1 2 3 254 255 In_Progress Draft Reviewed Published Other Unknown The 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. Description Text description of what was done in this revision. TRUE TRUE 2.6.0 Associates PRS_Administrative with PRS_Revision. TRUE Antecedent 1 1 The PRS_Administrative. Dependent The PRS_Revision. 2.6.0 PRS_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. TRUE 2.6.0 PRS_ContactItem is the abstract root class for PRS_Person and PRS_Organization. It provides a common anchor point for the PRS_ContactContactItem association. TRUE TRUE 2.6.0 Associates PRS_Administrative and PRS_Contact. TRUE Antecedent 1 The PRS_Administrative instance. Dependent 1 The PRS_Contact. TRUE TRUE 2.6.0 Associates PRS_Revision and PRS_Contact. TRUE Antecedent The PRS_Revision. Dependent 1 The PRS_Contact. 2.6.0 PRS_Organization describes a PRS_Contact's organization name and business. The name of the organization. Description of organization's primary business. 2.6.0 Information 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. 0 1 2 3 4 254 255 Primary_Voice Alternate_Voice Fax Email URL Other Unknown Contact's preferred communication method. See the PRS_Location.LocationType property. TRUE TRUE 2.6.0 Abstract root class to associate PRS_Person or PRS_Organization and PRS_Contact. Antecedent 1 The PRS_Contact. Dependent 1 The 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.0 Associates PRS_Contact and PRS_Organization. Dependent The PRS_Organization. TRUE 2.6.0 Associates PRS_Contact and PRS_Person. Dependent The PRS_Person. 2.6.0 Provides address information for PRS_ContactItem. 0 1 2 3 254 255 Primary Shipping Billing Service Other Unknown The 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. TRUE 2.6.0 Associates PRS_ContactItem with PRS_Address. Antecedent 1 The PRS_ContactItem. Dependent The PRS_Address. 2.6.0 PRS_Location describes the location of a PRS_Address. 0 1 2 3 4 254 255 Primary_Voice Alternate_Voice Fax Email URL Other Unknown The type of location. The specific location. TRUE 2.6.0 Associates PRS_Address and PRS_Location. Antecedent 1 The PRS_Address. Dependent The PRS_Location 2.6.0 PRS_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. \n\nThe 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. 0 1 2 254 255 Instructions Background Log Unknown Undefined The 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. TRUE 2.6.0 Associates PRS_Attachment with PRS_ExchangeElement. Antecedent The PRS_Attachment. Dependent 1 The PRS_ExchangeElement. 2.6.0 PRS_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. 0 1 2 3 4 5 6 7 254 255 Beginning_State Not_Entitled Entitled Problem_Submitted Open_Requester Open_Provider Closed_Pending_Confirmation Closed Other Unknown The state of the incident within the Service Incident Exchange Standard transaction model. 1 2 3 4 5 The severity of the incident as defined by the Requester. One is the most severe and five is the least severe. 1 2 3 4 5 The 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. 0 1 254 255 Yes No Other Unknown Is the Requester entitled to service or not? 0 1 254 255 Yes No Other Unknown Was the last transaction was accepted or rejected? PRS_ServiceIncident.LastTransaction The use of the TransactionName property is deprecated. New Service Incidents should use the LastTransaction property and set this property to NULL. 0 1 2 3 4 5 6 7 8 9 10 11 254 255 Service_Request Entitlement Problem_Submittal Accept_Problem Problem_Resolution Request_Problem_Information Provide_Problem_Information Provide_Admin_Information Query_Incident Confirm_Close Reject_Resolution Request_Closure Other Unknown The name of the last transaction which was acknowledged. TRUE 2.6.0 PRS_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. Antecedent The PRS_ServiceIncident. Dependent 1 1 The PRS_Contact. TRUE 2.6.0 Associates PRS_ServiceIncident to PRS_Contact to describe the Service Provider. Antecedent The PRS_ServiceIncident. Dependent 1 1 The PRS_Contact. TRUE 2.6.0 Associates PRS_ServiceIncident to PRS_Problem to describe the Problem being submitted to the Service Provider. Antecedent 1 The PRS_ServiceIncident. Dependent 1 The PRS_Problem. TRUE TRUE 2.6.0 Associates PRS_ServiceIncident to PRS_Solution to describe the Resolutions proposed by the Service Provider. Antecedent TRUE The PRS_ServiceIncident. Dependent The PRS_Solution. PRS_Solution must be associated with at least one Resolution. 2.6.0 The 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. TRUE 2.6.0 Associates PRS_ServiceIncident to PRS_Agreement. Antecedent The PRS_ServiceIncident. Dependent 1 1 The PRS_Agreement. 2.6.0 Describes the date of each transaction and the objects involved. PRS_Activity.NewKeys PRS_Activity.Deleted PRS_Activity.Modified The 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.0 PRS_Transaction represents a single transaction of the Service Incident workflow. A PRS_Transaction instance is created by the PRS_SISService StartSISTransaction method. 0 1 2 3 4 5 6 7 8 9 10 11 254 255 Service_Request Entitlement Problem_Submittal Accept_Problem Problem_Resolution Request_Problem_Information Provide_Problem_Information Provide_Admin_Information Query_Incident Confirm_Close Reject_Resolution Request_Closure Other Unknown The specific SIS transaction represented by this PRS_Transaction instance. 0 1 2 3 Open Working Closed Notification_Pending The 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.0 The PRS_SISService is used as a class factory for PRS_Transactions. FALSE 0 1 2 3 4 5 6 7 8 9 10 11 254 255 Service_Request Entitlement Problem_Submittal Accept_Problem Problem_Resolution Request_Problem_Information Provide_Problem_Information Provide_Admin_Information Query_Incident Confirm_Close Reject_Resolution Request_Closure Other Unknown FALSE FALSE TRUE FALSE Status 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. FALSE TransactionRef 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. FALSE This 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. FALSE TransactionRef identifies the PRS_Transaction that has completed. If this property is NULL or does not identify an 'Open' transaction, this method returns an error. TRUE TRUE 2.6.0 Associates PRS_ServiceIncident to PRS_Activity. TRUE Antecedent 1 1 The PRS_ServiceIncident. Dependent The PRS_Activity. TRUE 2.6.0 Associates PRS_Activity with PRS_Contact. Antecedent The PRS_Activity. Dependent 1 The PRS_Contact. TRUE TRUE 2.6.0 Associates PRS_Activity with PRS_Resource. TRUE Antecedent 1 1 The PRS_Activity. Dependent The PRS_Resource. TRUE 2.6.0 Associates PRS_Activity with PRS_Transaction. Antecedent 1 1 The PRS_Activity. Dependent 1 1 The PRS_Transaction. TRUE 2.6.0 An 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.6.0 A 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. 2.6.0 The 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. TRUE CommunicationMechanism 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 - "CIM-XML". If this is supported by an ObjectManager, the specified string should be indicated. Other 'standard' strings may be defined. In addition, a vendor specific encoding/protocol string may be used. 0 1 2 Unknown Other CIM-XML A free-form string providing a description of the supported protocols when 1, "Other", is specified in the CommunicationMechanism. CIM_ObjectManagerCommunicationMechanism.CommunicationMechanism TRUE Enumerated array describing the types of operations supported by the ObjectManager, using this encoding/protocol. The enumeration is based on the Functional Profiles defined for conformance in the DMTF document, Specification for CIM Operations over HTTP. 0 1 2 3 4 5 6 7 8 9 Unknown Other Basic Read Basic Write Schema Manipulation Instance Manipulation Association Traversal Query Execution Qualifier Declaration Indications A free-form string providing a description of the supported operations when 1, "Other", is specified in the ProfilesSupported array. CIM_ObjectManagerCommunicationMechanism.ProfilesSupported TRUE Boolean indicating whether the ObjectManager supports multiple operation requests (TRUE) or only simple requests (FALSE). TRUE Enumerated array describing the types of authentication supported by the ObjectManager, using this encoding/protocol. The defined values represent the authentication defined in the DMTF document, Specification for CIM Operations over HTTP. 0 1 2 3 4 Unknown Other None Basic Digest A free-form string providing a description of the supported mechanism when 1, "Other", is specified in the AuthenticationMechanismsSupported array. CIM_ObjectManagerCommunicationMechanism.AuthenticationMechanismsSupported 2.6.0 This class specializes ObjectManagerCommunicationMechanism, adding properties specific to the CIM-XML protocol (XML encoding and CIM Operations). CommunicationMechanism TRUE 2 TRUE Enumeration describing the CIM-XML protocol version supported by the ObjectManager. 0 1 Unknown 1.0 TRUE Describes whether the CIM Server is strictly validating (validates the XML document against the DTD) or not (loosely validating). TRUE 2.6.0 CommMechanismForManager 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. Antecedent 1 1 The specific ObjectManager whose communication mechanism is described. Dependent 1 The encoding/protocol/set of operations that may be used to communicate with the referenced ObjectManager. 2.6.0 Namespace 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.SystemCreationClassName TRUE 256 The scoping System's CreationClassName. CIM_ObjectManager.SystemName TRUE 256 The scoping System's Name. CIM_ObjectManager.CreationClassName TRUE 256 The scoping ObjectManager's CreationClassName. CIM_ObjectManager.Name TRUE 256 The scoping ObjectManager's Name. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE 256 A string to uniquely identify the Namespace within the ObjectManager. TRUE TRUE Enumeration indicating the organization/schema of the Namespace's objects. For example, they may be instances of classes of a specific CIM version. 0 1 2 3 4 5 6 7 8 9 200 201 202 Unknown Other CIM 1.0 CIM 2.0 CIM 2.1 CIM 2.2 CIM 2.3 CIM 2.4 CIM 2.5 CIM 2.6 DMI Recast SNMP Recast CMIP Recast CIM_Namespace.DescriptionOfClassInfo TRUE A string providing more detail (beyond the general classification in ClassInfo) for the object hierarchy of the Namespace. CIM_Namespace.ClassInfo 2.6.0 A 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.SystemCreationClassName TRUE 256 The scoping System's CreationClassName. CIM_Namespace.SystemName TRUE 256 The scoping System's Name. CIM_Namespace.ObjectManagerCreationClassName TRUE 256 The scoping ObjectManager's CreationClassName. CIM_Namespace.ObjectManagerName TRUE 256 The scoping ObjectManager's Name. CIM_Namespace.CreationClassName TRUE 256 The scoping Namespace's CreationClassName. CIM_Namespace.Name TRUE 256 The scoping Namespace's Name. TRUE 256 CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified. TRUE 256 A string uniquely identifying the name of the system represented in the Namespace. TRUE TRUE Enumeration indicating the format of the system identification and/or addressing information. 0 1 2 3 4 5 6 7 8 9 10 11 Unknown Other Short DNS Name Fully qualified DNS Name Windows Domain Name NetWare Server Name Unix Hostname Globally Unique System Identifier IP Address Modem Dialup String MAC Address IPMI Address Indexed CIM_SystemIdentification.IdentificationData CIM_SystemIdentification.FormatDescription TRUE Strings further describing the format of the system identification information. Indexed CIM_SystemIdentification.IdentificationFormat CIM_SystemIdentification.IdentificationData Strings containing the system identification information. The format is described by the corresponding array item in IdentificationFormats. Indexed CIM_SystemIdentification.IdentificationFormat CIM_SystemIdentification.FormatDescription TRUE 2.6.0 NamespaceInManager is an association describing the Namespaces hosted by a CIM ObjectManager. Antecedent 1 1 TRUE The ObjectManager containing a Namespace. Dependent TRUE The Namespace in an ObjectManager. TRUE 2.6.0 SystemInNamespace is an association that allows enumeration of the system(s) represented in a Namespace. TRUE 1 1 The Namespace containing management objects from one or more systems. TRUE TRUE Identification information for systems in the Namespace. TRUE TRUE A 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. Indexed 0 1 2 3 4 Unknown Other Local System Data Data Aggregated from Multiple Systems Proxied Data CIM_SystemInNamespace.DescriptionOfContainedData TRUE An 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. Indexed CIM_SystemInNamespace.ScopeOfContainedData TRUE 2.6.0 IdentificationOfManagedSystem is an association that links the SystemIdentification object to the CIM_System(s) that are being identified and represented in the Namespace. Antecedent 1 The System which is identified. Dependent 1 The SystemIdentification information.