< draft-moats-dmtf-core-ldap-00.txt   draft-moats-dmtf-core-ldap-01.txt >
Internet-Draft Ryan Moats Internet-Draft Ryan Moats
draft-moats-dmtf-core-ldap-00.txt Gerald Maziarski draft-moats-dmtf-core-ldap-01.txt AT&T
Expires in six months AT&T Expires in six months December 1999
John Strassner
cisco Systems
September 1999
LDAP Schema for the DMTF Core CIM Model LDAP Schema for the DMTF Core CIM v2.2 Model
Filename: draft-moats-dmtf-core-ldap-00.txt Filename: draft-moats-dmtf-core-ldap-01.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. Internet-Drafts are working all provisions of Section 10 of RFC2026. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts. working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
skipping to change at page 1, line 36 skipping to change at page 1, line 33
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Abstract Abstract
This draft presents a LDAP core schema for the DMTF CIM Core model This draft presents a LDAP core schema for the DMTF CIM Core model
version 2.2 [4]. version 2.2 [4].
Table of Contents
1. Introduction 2
2. LDAP Mapping Considerations 3
2.1 Differences from the Core CIM Model 3
2.2 cimAssociationInstance 3
2.3 cimOtherIdentifyingInfoInstance 4
2.4 Naming considerations 5
2.5 Inheritance Assumptions 5
3 Class Definitions 6
3.1 cim22ManagedSystemElement 6
3.2 cim22CollectionOfMSEs 7
3.3 cim22CollectedMSEsAuxClass 9
3.4 cim22CollectedCollectionsAuxClass 9
3.5 cim22PhysicalElement 10
3.6 cim22LogicalElement 12
3.7 cim22LogicalIdentityAuxClass 12
3.8 cim22Configuration 13
3.9 cim22ConfigurationComponentAuxClass 14
3.10 cim22ElementConfigurationAuxClass 15
3.11 cim22CollectionConfigurationAuxClass 16
3.12 cim22Setting 16
3.13 cim22ElementSettingAuxClass 17
3.14 cim22DefaultSettingAuxClass 17
3.15 cim22SettingContextAuxClass 17
3.16 cim22CollectionSettingAuxClass 18
3.17 cim22System 18
3.18 cim22ComputerSystem 20
3.19 cim22LogicalDevice 21
3.20 cim22Service 24
3.21 cim22ServiceAccessPoint 25
3.22 cim22DependencyAuxClass 26
3.24 cim22ServiceAccessBySAPAuxClass 26
3.25 cim22ServiceServiceDependencyAuxClass 27
3.26 cim22ServiceSAPDependencyAuxClass 28
3.27 cim22SAPSAPDependencyAuxClass 28
3.28 cim22ProvidesServiceToElementAuxClass 28
3.29 cim22RealizesAuxClass 29
3.30 cim22ComponentAuxClass 29
3.31 cim22SystemComponentAuxClass 30
3.32 cim22ServiceComponentAuxClass 30
3.33 cim22Product 30
3.34 cim22ProductParentChildAuxClass 32
3.35 cim22CompatibleProductAuxClass 32
3.36 cim22ProductProductDependencyAuxClass 33
3.37 cim22SupportAccess 33
3.38 cim22ProductSupportAuxClass 35
3.39 cim22FRU 35
3.40 cim22ProductFRUAuxClass 36
3.41 cim22ProductPhysicalElementsAuxClass 37
3.42 cim22FRUPhysicalElementsAuxClass 37
3.43 cim22FRUIncludesProductAuxClass 37
4. References 38
5. Acknowledgement 38
6. Editor's Address 38
1. Introduction 1. Introduction
This draft presents a LDAPv3 [1,2] schema for the DMTF CIM Core This draft presents a LDAPv3 [1,2] schema for the DMTF CIM Core
model. Associations are mapped using a combination of auxiliary model. Associations are mapped using a combination of auxiliary
classes and DIT structure rules. Where auxiliary classes are used, classes and DIT structure rules. All attribute, object class, and
name form and DIT content rules are specified. name form OIDs are place holders, and syntax OIDs in definitions have
been replaced by names for clarity. Further, structure rule
identifiers are place holders and should be replaced as dictated by
local implementations.
2. Class Definitions This document is a product of the DMTF LDAP WG.
2. LDAP Mapping Considerations
2.1 Differences from the Core CIM Model
This mapping differs from the core CIM model in several ways. The
hierarchy of classes beginning with CIM_StatisticalInformation has
not been mapped. The CIM_DependencyContaxt association is not
mapped. Finally, the classes CIM_Service, CIM_System,
CIM_ServiceAccessPoint, and CIM_LogicalDevice have been mapped to
structural classes to support basic DIT containment rules.
2.2 cimAssociationInstance
This object class is used when attaching multiple association
auxiliary classes to a structural object class would lead to
attribute confusion or collision. Instead, the association auxiliary
classes attach to cimAssociationInstance classes that are DIT
contained by the original structural class.
( <oid-at74> NAME 'cimAssociationName'
DESC 'The associations' name'
SYNTAX string SINGLE-VALUE
)
( <oid-at75> NAME 'cimAssociationTypeName'
DESC 'The associations' type name. It can support storing extra
information about the association type'
SYNTAX string SINGLE-VALUE
)
( <oid-oc44> NAME 'cimAssociationInstance'
SUP top
MUST (orderedCimModelPath)
MAY (cimAssociationTypeName)
)
( <oid-nf9> NAME 'cimAssociationInstanceNameForm'
OC cimAssociationInstance
MUST (orderedCimModelPath)
)
( <sr9> NAME 'cimAssociationInstanceStructureRule'
FORM cimAssociationInstanceNameForm
SUP <sr1> <sr2> <sr3> <sr4> <sr5> <sr6> <sr7> <sr8>
)
The following content rule specifies the auxiliary classes that may
be attached to cimAssociationInstance.
( <oid-oc44> NAME 'cimAssociationInstanceContentRule'
DESC 'The auxiliary classes that may be attached to
cimAssociationInstance'
AUX (cim22CollectedMSEsAuxClass $ cim22CollectedCollectionsAuxClass
$
cim22LogicalIdentityAuxClass $
cim22ConfigurationComponentAuxClass $
cim22ElementConfigurationAuxClass $
cim22CollectionConfigurationAuxClass $
cim22ElementSettingAuxClass $ cim22DefaultSettingAuxClass $
cim22SettingContextAuxClass $ cim22CollectionSettingAuxClass $
cim22DependencyAuxClass $ cim22ServiceAccessBySAPAuxClass $
cim22ServiceServiceDependencyAuxClass $
cim22ServiceSAPDependencyAuxClass $
cim22SAPSAPDependencyAuxClass $
cim22ProvidesServiceToElementAuxClass $ cim22RealizesAuxClass $
cim22ComponentAuxClass $ cim22SystemComponentAuxClass $
cim22ServiceComponentAuxClass $ cim22ProductParentChildAuxClass
$
cim22CompatibleProductAuxClass $
cim22ProductProductDependencyAuxClass $
cim22ProductSupportAuxClass $ cim22ProductFRUAuxClass $
cim22ProductPhysicalElementsAuxClass $
cim22FRUPhysicalElementsAuxClass $
cim22FRUIncludesProductAuxClass)
)
2.3 cimOtherIdentifyingInfoInstance
CIM defines the concept of an ordered array, which LDAP does not
support. In the core model, indexed arrays are only used in two
cases to tie two properties together. In the LDAP mapping, these
attributes are replaced with separate instances of
cimOtherIdentifyingInfoInstance that each contain a single pair of
property values and are DIT contained by the parent class. The
attribute cimOtherIdentifyingInfo is already defined below and reused
here. The attribute arrayIndex is defined here as the RDN for this
class.
( <oid-at34> NAME 'arrayIndex'
DESC 'the index of this child'
SYNTAX integer
)
( <oid-at35> NAME 'cimIdentifyingDescriptions'
DESC 'A free-form string providing explanations and
details behind the entries in the OtherIdentifyingInfo
array.'
SYNTAX string
)
( <oid-oc45> NAME 'cimOtherIdentifyingInfoInstance'
DESC 'helper class to tie indexed arrays in core model together'
SUP top
MUST (arrayIndex)
MAY (cimOtherIdentifyingInfo $ cimIdentifyingDescriptions)
)
( <oid-nf10> NAME 'cimOtherIdentifyingInfoInstanceNameForm'
OC cimOtherIdentifyingInfoInstance
MUST (arrayIndex)
)
( <sr10> NAME 'cimOtherIdentifyingInfoInstanceStructureRule'
FORM cimOtherIdentifyingInfoInstanceNameForm
SUP <sr3> <sr11>
)
2.4 Naming considerations
To support naming in the LDAP mapping of the core schema, the
attribute orderedCimModelPath is defined. It is used to provide a
simple RDN for directory implementations. The name form rules that
follow show that this attribute should be used as the RDN for
structural classes.
( <oid-at1> NAME 'orderedCimModelPath'
DESC 'The model path for the instance. Used as an RDN'
SYNTAX string SINGLE-VALUE
)
The value of this attribute is constructed by ordering the CIM keys
of the object in the US-ASCII collation order of the property types.
To support an existing naming plan, an implementor may specify
additional/replacement nameform rules.
2.5 Inheritance Assumptions
This schema mapping is based on the assumption that name form rules
structural rules, and content rules are inherited by both auxiliary
and structural sub-classes. For implementations where this is not
the case, extra rules will need to be specified.
On the other hand, the attributes contained in auxiliary classes in
this mapping are based on the assumption that inheritance does not
occur between auxiliary classes (even though such inheritance is
shown in the auxiliary class definitions). For implementations that
do support this type of inheritance, the schema definitions will be
simpler.
3. Class Definitions
For efficiency in the LDAP representation, associations are specified For efficiency in the LDAP representation, associations are specified
as a combination of auxiliary classes and DIT structure rules. as a combination of auxiliary classes and DIT structure rules.
Attribute definitions for each class are presented with the object Attribute definitions for each class are presented with the object
class. Other definitions are also provided when necessary. class. Other definitions are also provided when necessary.
While this approach was chosen to minimize the number of DN pointers While this approach was chosen to minimize the number of DN pointers
stored in the schema, some pointer dereferencing is necessary. While stored in the schema, some pointer dereferencing is necessary. While
not explicitly stated, all DN pointers are assumed to support the not explicitly stated, all DN pointers are assumed to support the
extended matching rule defined in [3]. Attribute names for DN extended matching rule defined in [3].
pointers follow the convention that a single pointer to "foo" is
named "fooRef" while an array of pointers would be named "fooRefs."
Note: all OIDs are place holders, and OIDs in definitions have been
replaced by names for clarity.
2.1 dmtfManagedSystemElement Class 3.1 cim22ManagedSystemElement
This is the base class for the system element hierarchy. Any This is the base class for the system element hierarchy. Any
distinguishable component of a system is a candidate for inclusion in distinguishable component of a system is a candidate for inclusion in
this class. Examples of this are software components, such as files; this class. Examples of this are software components, such as files
and devices, such as disk drives and controllers, and physical and devices, such as disk drives and controllers, and physical
components such as chips and cards. components such as chips and cards.
The dmtfManagedSystemElement class supports five attributes: caption, ( <oid-at2> NAME 'cimCaption'
description, installDate, name and status. The caption attribute is DESC 'The Caption property is a short textual description
a short textual description (one-line string) of the object. The (one-line string) of the object.'
description attribute provides a textual description of the object.
The installDate attribute is a date-time value showing when the
object was installed. The name attribute defines the label by which
the object is known. In subclasses, this attribute can be used as a
RDN. The status attribute is a string showing the current status of
the object.
( <oid-at1> NAME 'caption'
DESC 'short textual description of the object'
SYNTAX string{64} SINGLE-VALUE SYNTAX string{64} SINGLE-VALUE
) )
( <oid-at2>NAME 'description' ( <oid-at3> NAME 'cimDescription'
DESC 'a textual description of the object' DESC 'The Description property provides a textual description of
the object.'
SYNTAX string SINGLE-VALUE SYNTAX string SINGLE-VALUE
) )
( <oid-at3> NAME 'installDate' ( <oid-at4> NAME 'cimInstallDate'
DESC 'A datetime value showing when the object was DESC 'A datetime value indicating when the object was
installed. A lack of a value does not show that the installed.'
object is not installed.'
SYNTAX generalizedTime SINGLE-VALUE SYNTAX generalizedTime SINGLE-VALUE
) )
( <oid-at4> NAME 'name' ( <oid-at5> NAME 'cimName'
DESC 'The Name property defines the label by which the object is DESC 'The Name property defines the label by which the object is
known. When subclassed, the Name property can be overridden known. When subclassed, the Name property can be overridden
to be a Key property.' to be a key property.'
SYNTAX string{256} SINGLE-VALUE SYNTAX string{256} SINGLE-VALUE
) )
( <oid-at5> NAME 'status' ( <oid-at6> NAME 'cimStatus'
DESC 'A string showing the current status of the DESC 'A string indicating the current status of the
object. Various operational and non-operational statuses object. Various operational and non-operational statuses
are defined.' are defined. Operational statuses are "OK", "Degraded",
"Stressed" and "Pred Fail". "Stressed" shows that the
Element is functioning, but needs attention. Examples of
"Stressed" states are overload, overheated, etc. The
condition "Pred Fail" (failure predicted) shows that
an Element is functioning properly but predicting a
failure soon. An example is a SMART-enabled hard
drive. Non-operational statuses can also be specified.
These are "Error", "NonRecover", "Starting",
"Stopping" and "Service". "NonRecover" shows that a
non-recoverable error has occurred. "Service" describes an
Element being configured, maintained or 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
another state.'
SYNTAX string{10} SINGLE-VALUE SYNTAX string{10} SINGLE-VALUE
) )
( <oid-oc1> NAME 'dmtfManagedSystemElement' ( <oid-oc1> NAME 'cim22ManagedSystemElement'
DESC 'the base class for the System Element hierarchy' DESC 'cim22ManagedSystemElement 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.'
SUP top ABSTRACT SUP top ABSTRACT
MUST (caption $ description $ installDate $ name $ status) MUST (orderedCimModelPath)
MAY (cimCaption $ cimDescription $ cimInstallDate $ cimName $
cimStatus)
) )
2.2 dmtfCollectionOfMSEs 3.2 cim22CollectionOfMSEs
This object allows the grouping of dmtfManagedSystemElement
objects for associating settings and
configurations. It is abstract to require further definition and
semantic refinement in subclasses. As this object does
not carry any state or status information, it only represents a
grouping or 'bag' of elements. So, it is incorrect to
subclass groups that have state/status from this class - an
example is dmtfRedundancyGroup (which is correctly subclassed from
dmtfLogicalElement).
Collections typically aggregate 'like' objects, and
represent an optimization. Without collections, one is forced to
define individual associations, to tie settings and configuration
objects to individual dmtfManagedSystemElements. There may be much
duplication in assigning the same setting to multiple objects. In
addition, using this 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 way, and then querying the
associations to determine if the collection set is completely
covered.
This class defines a new attribute collectionID and reuse the This object allows the grouping of cim22ManagedSystemElement objects
previously defined attributes description and caption. for associating settings and configurations. It is abstract to
require further definition and semantic refinement in subclasses. As
this object does not carry any state or status information, it only
represents a grouping or 'bag' of elements. So, it is incorrect to
subclass groups that have state/status from this class - an example
is cim22RedundancyGroup (which is correctly subclassed from
cim22LogicalElement).
( <oid-at6> NAME 'collectionID' Collections typically aggregate 'like' objects, and represent an
DESC 'The identification of the Collection object. optimization. Without collections, one is forced to define individual
associations, to tie settings and configuration objects to individual
cim22ManagedSystemElements. There may be much duplication in
assigning the same setting to multiple objects. In addition, using
this 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 way, and then querying the associations
to determine if the collection set is completely covered.
When subclassed, the CollectionID property can be ( <oid-at7> NAME 'cimCollectionID'
overridden to be a RDN' DESC 'The identification of the Collection object. When
subclassed, the CollectionID property can be overridden to
be a Key property.'
SYNTAX string{256} SINGLE-VALUE SYNTAX string{256} SINGLE-VALUE
) )
( <oid-oc2> NAME 'dmtfCollectionOfMSEs' ( <oid-oc2> NAME 'cim22CollectionOfMSEs'
DESC 'Parent class of collections of MSEs' DESC 'The CollectionOfMSEs object allows the grouping of
ManagedSystemElements for the purposes 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. Therefore, it is incorrect to
subclass groups that have state/status from
CollectionOfMSEs - an example is cim22RedundancyGroup (which
is correctly subclassed from LogicalElement). Collections
typically aggregate "like" objects, and represent an
optimization. Without Collections, one is forced to define
individual ElementSetting and ElementConfiguration
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 way, and then
querying the ElementSetting and ElementConfiguration
associations to determine if the Collection set is
completely covered.'
SUP top ABSTRACT SUP top ABSTRACT
MUST (collectionID $ caption $ description) MAY (cimCollectionID $ cimCaption $ cimDescription)
) )
2.3 dmtfCollectedMSEsAuxClass 3.3 cim22CollectedMSEsAuxClass
This auxiliary class represents a generic association used to This auxiliary class represents a generic association used to
establish the members of the grouping object, dmtfCollectionOfMSEs. establish the members of the grouping object, cim22CollectionOfMSEs.
It defines the attributes collectionRefs (which point to
dmtfCollectionOfMSEs) and memberRefs (which point to
dmtfManagedSystemElements).
( <oid-at7> NAME 'collectionRef' ( <oid-at8> NAME 'cimCollectionRef'
DESC 'The grouping or "bag" object that represents the DESC 'The grouping or "bag" object that represents the Collection.'
Collection. May be used as an RDN.' SYNTAX DN
SYNTAX DN SINGLE-VALUE
) )
( <oid-at8> NAME 'memberRefs' ( <oid-at9> NAME 'cimMemberRef'
DESC 'The members of the Collection. May be used as an RDN.' DESC 'The members of the Collection.'
SYNTAX DN SYNTAX DN
) )
( <oid-oc3> NAME 'dmtfCollectedMSEsAuxClass' ( <oid-oc3> NAME 'cim22CollectedMSEsAuxClass'
DESC 'generic association used to establish the members of the DESC 'cimCollectedMSEs is a generic association used to
grouping object, CollectionOfMSEs.' establish the members of the grouping object,
CollectionOfMSEs. Attribute cimCollectionRef points to
cim22CollectionOfMSEs and cimMemberRef points to
cim22ManagedSystemElement.'
SUP top AUXILIARY SUP top AUXILIARY
MUST (collectionRef $ memberRefs) MAY (cimCollectionRef $ cimMemberRef)
) )
2.4 dmtfCollectedCollectionsAuxClass 3.4 cim22CollectedCollectionsAuxClass
This association represents that a dmtfCollectionOfMSEs may itself be This association represents that a cim22CollectionOfMSEs may itself
contained in another dmtfCollectionOfMSEs object. It reuses be contained in another cim22CollectionOfMSEs object.
collectionRefs and defines and collectionInCollectionRefs.
( <oid-at9> NAME 'collectionInCollectionRefs' ( <oid-at10> NAME 'cimCollectionInCollectionRef'
DESC 'The "collected" collection. May be used as an RDN.' DESC 'The "collected" Collection.'
SYNTAX DN SYNTAX DN
) )
( <oid-oc4> NAME 'dmtfCollectedCollectionsAuxClass'
DESC 'aggregation association representing that a ( <oid-oc4> NAME 'cim22CollectedCollectionsAuxClass'
CollectionOfMSEs may itself be contained in a DESC 'cim22CollectedCollections is an aggregation association
CollectionOfMSEs.' representing that a CollectionOfMSEs may itself be
contained in a CollectionOfMSEs. Both attributes point to
cim22CollectionOfMSEs.'
SUP top AUXILIARY SUP top AUXILIARY
MUST (collectionRefs $ collectionInCollectionRefs) MAY (cimCollectionRef $ cimCollectionInCollectionRef)
) )
2.5 dmtfPhysicalElement class 3.5 cim22PhysicalElement
This class acts as the base class for any component of a system that This class acts as the base class for any component of a system that
has a distinct physical identity. Instances of this class can be has a distinct physical identity. Instances of this class can be
defined in terms of labels that can be physically attached to the defined in terms of labels that can be physically attached to the
object. All processes, files, and logical devices are considered not object. All processes, files, and logical devices are considered not
to be physical elements. For example, it is not possible to attach a to be physical elements. For example, it is not possible to attach a
label to a modem. It is only possible to attach a label to the card 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 that implements the modem. The same card could also implement a LAN
adapter. This is an example of a single physical element (the card) adapter. This is an example of a single physical element (the card)
hosting more than one logical device. hosting more than one logical device.
This class has the following attributes: creationClassName, ( <oid-at11> NAME 'cimCreationClassName'
manufacturer, model, sKU, serialNumber, tag, version, partNumber,
otherIdentifyingInfo and poweredOn. The creationClassName attribute
shows the name of the class or the subclass used in the creation of
an instance. The manufacturer attribute contains the name of the
organization responsible for producing this physical element and the
partNumber attribute stores that manufacturer's part number of the
physical element. The model, version and serialNumber attributes are
self-explanatory. The stock keeping unit number of the physical
element is contained in the sKU attribute. The tag attribute
provides an arbitrary string used to identify the physical element.
Other identifying information (beyond that stored in the tag
attribute) is stored in the otherIdentifyingInfo attribute. Finally,
the poweredOn attribute shows if the physical element is currently
powered on or not.
In this class, the attributes creationClassName and tag may be used
as a RDN.
( <oid-at10> NAME 'creationClassName'
DESC 'CreationClassName shows the name of the class or the DESC 'CreationClassName shows the name of the class or the
subclass used in the creation of an instance. When used subclass used in the creation of an instance. When used
with the other key properties of this class, this property with the other key properties of this class, this property
allows all instances of this class and its subclasses to be allows all instances of this class and its subclasses to be
uniquely identified. May be used as a RDN.' uniquely identified.'
SYNTAX string{256} SINGLE-VALUE SYNTAX string{256} SINGLE-VALUE
) )
( <oid-at11> NAME 'manufacturer'
( <oid-at12> NAME 'cimTag'
DESC '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
high in the object hierarchy 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 exists - 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.'
SYNTAX string{256} SINGLE-VALUE
)
( <oid-at13> NAME 'cimManufacturer'
DESC 'The name of the organization responsible for producing the DESC 'The name of the organization responsible for producing the
PhysicalElement.' 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
cim22Product.'
SYNTAX string{256} SINGLE-VALUE SYNTAX string{256} SINGLE-VALUE
) )
( <oid-at12> NAME 'model' ( <oid-at14> NAME 'cimModel'
DESC 'The name by which the PhysicalElement is generally known.' DESC 'The name by which the PhysicalElement is generally known.'
SYNTAX string{64} SINGLE-VALUE SYNTAX string{64} SINGLE-VALUE
) )
( <oid-at13> NAME 'sKU' ( <oid-at15> NAME 'cimSKU'
DESC 'The stock keeping unit number for this PhysicalElement.' DESC 'The stock keeping unit number for this PhysicalElement.'
SYNTAX string{64} SINGLE-VALUE SYNTAX string{64} SINGLE-VALUE
) )
( <oid-at14> NAME 'serialNumber' ( <oid-at16> NAME 'cimSerialNumber'
DESC 'A manufacturer-allocated number used to identify the DESC 'A manufacturer-allocated number used to identify the
PhysicalElement.' PhysicalElement.'
SYNTAX string{64} SINGLE-VALUE SYNTAX string{64} SINGLE-VALUE
) )
( <oid-at15> NAME 'tag' ( <oid-at17> NAME 'cimVersion'
DESC 'An arbitrary string that uniquely identifies the DESC 'A string indicating the version of the PhysicalElement.'
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
high in the object hierarchy to independently
identify the hardware/entity, regardless of physical
placement in or on Cabinets, Adapters, etc. May be used as
a RDN.'
SYNTAX string{256} SINGLE-VALUE
)
( <oid-at16> NAME 'version'
DESC 'A string showing the version of the PhysicalElement.'
SYNTAX string{64} SINGLE-VALUE SYNTAX string{64} SINGLE-VALUE
) )
( <oid-at17> NAME 'partNumber' ( <oid-at18> NAME 'cimPartNumber'
DESC 'The part number assigned by the organization responsible DESC 'The part number assigned by the organization responsible
for producing or manufacturing the PhysicalElement.' for producing or manufacturing the PhysicalElement.'
SYNTAX string{256} SINGLE-VALUE SYNTAX string{256} SINGLE-VALUE
) )
( <oid-at18> NAME 'otherIdentifyingInfo' ( <oid-at19> NAME 'cimOtherIdentifyingInfo'
DESC 'OtherIdentifyingInfo captures additional data, beyond asset DESC 'OtherIdentifyingInfo captures additional data, beyond asset
tag information, that could be used to identify a tag information, that could be used to identify a
PhysicalElement. One example is bar code data associated PhysicalElement. One example is bar code data associated
with an Element that also has an asset tag. Note that if with an Element that also has an asset tag. Note that if
only bar code data is available and is unique/able to be only bar code data is available and is unique/able to be
used as an Element key, this property would be NULL and the used as an Element key, this property would be NULL and the
bar code data used as the class key, in the Tag property.' bar code data used as the class key, in the Tag property.'
SYNTAX string SINGLE-VALUE SYNTAX string SINGLE-VALUE
) )
( <oid-at19> NAME 'poweredOn' ( <oid-at20> NAME 'cimPoweredOn'
DESC 'Boolean showing that the PhysicalElement is powered on DESC 'Boolean indicating that the PhysicalElement is powered on
(TRUE), or is currently off (FALSE).' (TRUE), or is currently off (FALSE).'
SYNTAX boolean SINGLE-VALUE SYNTAX boolean SINGLE-VALUE
) )
( <oid-oc5> NAME 'dmtfPhysicalElement' ( <oid-oc5> NAME 'cim22PhysicalElement'
DESC 'base class for any component of a system that has a DESC 'Subclasses of cim22PhysicalElement define any component of a
distinct physical identity' System that has a distinct physical identity. Instances of
SUP dmtfManagedSystemElement ABSTRACT this class can be defined in terms of labels that can be
MUST (creationClassName $ manufacturer $ model $ sKU $ physically attached to the object. All Processes, Files,
serialNumber $ tag $ version $ partNumber $ and LogicalDevices are considered not to be
otherIdentifyingInfo $ poweredOn) 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 Managed
System Elements (usually hardware items) that have a
physical manifestation of some sort. A Managed System
Element is not necessarily a discrete component. For
example, it is possible for a single Card (which is a type
of Physical Element) to host more than one Logical
Device. The card would be represented by a single Physical
Element associated with multiple Logical Devices.'
SUP cim22ManagedSystemElement ABSTRACT
MUST (cimTag $ cimCreationClassName)
MAY (cimManufacturer $ cimModel $ cimSKU $ cimSerialNumber $
cimVersion $ cimPartNumber $ cimOtherIdentifyingInfo $
cimPoweredOn)
) )
2.6 dmtfLogicalElement Class 3.6 cim22LogicalElement
This class is the base class for all the components of a system that This class is the base class for all the components of a system that
represent abstract system components, such as files, processes, or represent abstract system components, such as files, processes, or
system capabilities as logical devices. system capabilities as logical devices.
This class defines no additional attributes to those inherited from ( <oid-oc6> NAME 'cim22LogicalElement'
dmtfManagedSystemElement DESC 'cim22LogicalElement is a base class for all the components
of a System that represent abstract system components, such
( <oid-oc6> NAME 'dmtfLogicalElement' as Files, Processes, or system capabilities as Logical
DESC 'base class for all the components of a System that
represent abstract system components, such as Files,
Processes, or system capabilities as Logical
Devices.' Devices.'
SUP dmtfManagedSystemElement ABSTRACT SUP cim22ManagedSystemElement ABSTRACT
) )
2.7 dmtfLogicalIdentityAuxClass 3.7 cim22LogicalIdentityAuxClass
This auxiliary class represents an abstract and generic association, This auxiliary class represents an abstract and generic association,
showing that two dmtfLogicalElements represent different aspects of showing that two cim22LogicalElements represent different aspects of
the same underlying entity. This relationship conveys what could be the same underlying entity. This relationship conveys what could be
defined with multiple inheritance. It is restricted to the 'logical' defined with multiple inheritance. It is restricted to the 'logical'
aspects of a dmtfManagedSystemElement. In most scenarios, the aspects of a cim22ManagedSystemElement. In most scenarios, the
identity relationship is determined by the equivalence of keys or identity relationship is determined by the equivalence of keys or
some other identifying properties of the related elements. The some other identifying properties of the related elements. The
association should only be used in well understood scenarios. This is association should only be used in well understood scenarios. This is
why the association is abstract - allowing more concrete definition why the association is abstract - allowing more concrete definition
and clarification in subclasses. This class defines two attributes: and clarification in subclasses.
systemElementRefs and sameElementRefs.
( <at-21> NAME 'systemElementRefs' ( <oid-at21> NAME 'cimSystemElementRef'
DESC 'represents one aspect of the Logical Element' DESC 'SystemElement represents one aspect of the
SYNTAX DN LogicalElement.'
SYNTAX DN
) )
( <at-22> NAME 'sameElementRefs' ( <oid-at22> NAME 'cimSameElementRef'
DESC 'represents an alternate aspect of the System entity' DESC 'SameElement represents an alternate aspect of the System
entity.'
SYNTAX DN SYNTAX DN
) )
( <oid-oc7> NAME 'dmtfLogicalIdentityAuxClass' ( <oid-oc7> NAME 'cim22LogicalIdentityAuxClass'
DESC 'an abstract and generic association, showing that two DESC 'cim22LogicalIdentityAuxClass is an abstract and generic
LogicalElements represent different aspects of the same association,
underlying entity. ' 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 scenario 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. Both attributes point to
cim22LogicalElement objects.'
SUP top AUXILIARY SUP top AUXILIARY
MUST (systemElementRefs $ sameElementRefs) MAY (cimSystemElementRef $ cimSameElementRef)
) )
2.8 dmtfConfiguration Class 3.8 cim22Configpuration
This object allows the grouping of sets of parameters (defined in This object allows the grouping of sets of parameters (defined in
dmtfSetting objects) and dependencies for one or more managed system cim22Setting objects) and dependencies for one or more managed system
elements. The configuration object represents a certain behavior, or elements. The configuration object represents a certain behavior, or
a desired functional state for the managed system elements. The a desired functional state for the managed system elements. The
desired functional state is typically driven by external requirements desired functional state is typically driven by external requirements
such as time or location. For example, to connect to a Mail System 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 from 'home', a dependency on a modem exists, but a dependency on a
network adapter exists at 'work'. Settings for the pertinent logical network adapter exists at 'work'. Settings for the pertinent logical
devices can be defined and aggregated by the configuration. devices can be defined and aggregated by the configuration.
Therefore, two 'Connect to Mail' configurations may be defined Therefore, two 'Connect to Mail' configurations may be defined
grouping the relevant dependencies and setting objects. grouping the relevant dependencies and setting objects.
This class uses the following attributes: name, caption, and ( <oid-oc8> NAME 'cim22Configuration'
description. Name holds the label by which the object is known, and DESC 'The Configuration object allows the grouping of sets of
may be used as a RDN. Description holds the textual description of parameters (defined in Setting objects) and dependencies
the object, which is summarized in the caption attribute. for one or more ManagedSystemElements. The Configuration
object represents a certain behavior, or a desired
( <oid-oc8> NAME 'dmtfConfiguration' functional state for the ManagedSystemElements. The desired
DESC 'allows the grouping of sets of parameters and dependencies functional state is typically driven by external
for one or more dmtfManagedSystemElements.' 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.'
SUP top SUP top
MUST (name $ caption $ description) MUST (cimName $ orderedCimModelPath)
MAY (cimCaption $ cimDescription)
)
( <oid-nf1> NAME 'cim22ConfigurationNameForm'
OC cim22Configuration
MUST (orderedCimModelPath)
)
( <sr1> NAME 'cim22ConfigurationStructureRule'
FORM cim22ConfigurationNameForm
) )
2.9 dmtfConfigurationComponentAuxClass The following content rule specifies the auxiliary classes that may
be attached to cim22Configuration.
( <oid-oc8> NAME 'cim22ConfigurationContentRule'
DESC 'The auxiliary classes that may be attached to
cim22Configuration'
AUX (cim22ConfigurationComponentAuxClass $
cim22ElementConfigurationAuxClass $
cim22CollectionConfigurationAuxClass $
cim22SettingContextAuxClass)
)
3.9 cim22ConfigurationComponentAuxClass
This association aggregates 'lower-level' configuration objects into This association aggregates 'lower-level' configuration objects into
a 'high-level' configuration. This enables the assembly of complex a 'high-level' configuration. This enables the assembly of complex
configurations by grouping together simpler ones. configurations by grouping together simpler ones.
( <oid-at20> NAME 'configGroupRefs' ( <oid-at23> NAME 'cimConfigGroupRef'
DESC 'The Configuration that aggregates additional Configurations.
May be used as an RDN.'
SYNTAX DN SYNTAX DN
) )
( <oid-at24> NAME 'cimConfigComponentRef'
( <oid-at21> NAME 'configComponentRefs'
DESC 'A Configuration that is part of a "higher-level" DESC 'A Configuration that is part of a "higher-level"
Configuration. May be used as an RDN.' Configuration.'
SYNTAX DN SYNTAX DN
) )
( <oid-oc9> NAME 'dmtfConfigurationComponentAuxClass' ( <oid-oc9> NAME 'cim22ConfigurationComponentAuxClass'
DESC 'aggregates lower-level Configuration objects into a DESC 'ConfigurationComponent aggregates "lower-level"
high-level Configuration.' 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. Both attributes point to cim22Configuration
objects.'
SUP top AUXILIARY SUP top AUXILIARY
MUST (configGroupRefs $ configComponentRefs) MAY (cimConfigGroupRef $ cimConfigComponentRef)
) )
2.10 dmtfElementConfigurationAuxClass 3.10 cim22ElementConfigurationAuxClass
This association relates a configuration object to one or more This association relates a configuration object to one or more
managed system elements. The configuration object represents a managed system elements. The configuration object represents a
certain behavior, or a desired functional state for the associated certain behavior, or a desired functional state for the associated
managed system elements.' managed system elements.
Two attributes are defined by this class:
dmtfManagedSystemElementRefs and dmtfConfigurationRefs.
( <oid-at22> NAME 'elementRefs' ( <oid-at25> NAME 'cimElementRef'
DESC 'The ManagedSystemElements.' DESC 'The ManagedSystemElement.'
SYNTAX DN SYNTAX DN
) )
( <oid-at23> NAME 'configurationRefs' ( <oid-at26> NAME 'cimConfigurationRef'
DESC 'The Configuration objects that groups the Settings and DESC 'The Configuration object that groups the Settings and
dependencies associated with the ManagedSystemElement.' dependencies associated with the ManagedSystemElement.'
SYNTAX DN SYNTAX DN
) )
( <oid-oc10> NAME 'dmtfElementConfigurationAuxClass'
DESC 'association relating a Configuration object to one or ( <oid-oc10> NAME 'cim22ElementConfigurationAuxClass'
more ManagedSystemElements' DESC '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. Attribute
cimElementRef points to cim22ManagedSystemElement and
attribute
cimConfigurationRef points to cim22Configuration.'
SUP top AUXILIARY SUP top AUXILIARY
MUST (elementRefs $ configurationRefs) MAY (cimElementRef $ cimConfigurationRef)
) )
2.11 dmtfCollectionConfigurationAuxClass 3.11 cim22CollectionConfigurationAuxClass
This auxiliary class relates a dmtfConfiguration object to one or This auxiliary class relates a cim22Configuration object to one or
more dmtfCollectionOfMSEs objects. The dmtfConfiguration object more cim22CollectionOfMSEs objects. The cim22Configuration object
represents a certain behavior, or a desired functional state for the represents a certain behavior, or a desired functional state for the
associated collection. It reuses the collectionRefs and associated collection.
configurationRefs attributes.
( <oid-oc11> NAME 'dmtfCollectionConfigurationAuxClass' ( <oid-oc11> NAME 'cim22CollectionConfigurationAuxClass'
DESC 'This association relates a Configuration object to one or DESC 'This association relates a Configuration object to one or
more CollectionOfMSEs objects.' more CollectionOfMSEs objects. The Configuration object
represents a certain behavior, or a desired functional
state for the associated Collection. Attribute
cimCollectionRef points to cim22CollectionOfMSEs and
attribute cimConfigurationRef points to cim22Configuration.'
SUP top AUXILIARY SUP top AUXILIARY
MUST (collectionRefs $ configurationRefs) MAY (cimCollectionRef $ cimConfigurationRef)
) )
2.12 dmtfSetting Class 3.12 cim22Setting
This class represents configuration-related and operational This class represents configuration-related and operational
parameters for one or more managed system element(s). A managed parameters for one or more managed system element(s). A managed
system element may have multiple setting objects associated with it. system element may have multiple setting objects associated with it.
The current operational values for an element's parameters are The current operational values for an element's parameters are
reflected by properties in the element itself or by properties in its reflected by properties in the element itself or by properties in its
associations. These properties do not have to be the same values associations. These properties do not have to be the same values
present in the setting object. For example, a modem may have a 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. setting baud rate of 56Kb/sec but be operating at 19.2Kb/sec.
This class uses the description and caption attributes defined above ( <oid-at27> NAME 'cimSettingID'
and defines the attribute settingID, which is the identifier for the
setting object.
( <oid-at24> NAME 'settingID'
DESC 'The identifier by which the Setting object is known.' DESC 'The identifier by which the Setting object is known.'
SYNTAX string{256} SINGLE-VALUE SYNTAX string{256} SINGLE-VALUE
) )
( <oid-oc12> NAME 'dmtfSetting' ( <oid-oc12> NAME 'cim22Setting'
DESC 'configuration-related and operational parameters for one or DESC 'The Setting class represents configuration-related and
more ManagedSystemElement(s).' 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.'
SUP top ABSTRACT SUP top ABSTRACT
MUST (settingID $ caption $ description) MAY (cimSettingID $ cimCaption $ cimDescription)
) )
2.13 dmtfElementSettingAuxClass Association 3.13 cim22ElementSettingAuxClass
This auxiliary class represents the association between managed This auxiliary class represents the association between managed
system elements and the setting class(es) defined for them. It reuses system elements and the setting class(es) defined for them.
the elementRefs attribute and defines the attribute settingRefs.
( <oid-at25> NAME 'settingRefs' ( <oid-at28> NAME 'cimSettingRef'
DESC 'The setting objects associated with the managed system DESC 'The Setting object associated with the ManagedSystemElement.'
elements.'
SYNTAX DN SYNTAX DN
) )
( <oid-oc13> NAME 'dmtfElementSettingAuxClass' ( <oid-oc13> NAME 'cim22ElementSettingAuxClass'
DESC 'association between ManagedSystemElements and the Setting DESC 'ElementSetting represents the association between
class(es) defined for them.' ManagedSystemElements and the Setting class(es) defined for
them. Attribute cimElementRef points to
cim22ManagedSystemElement and attribute cimSettingRef points
to cim22Setting.'
SUP top AUXILIARY SUP top AUXILIARY
MUST (elementRefs $ settingRefs) MAY (cimElementRef $ cimSettingRef)
) )
2.14 dmtfDefaultSettingAuxClass 3.14 cim22DefaultSettingAuxClass
This auxiliary class represents the association between a This auxiliary class represents the association between a
dmtfManagedSystemElement and the single dmtfSetting class that is cim22ManagedSystemElement and the single cim22Setting class that is
defined to be the default setting for this element. defined to be the default setting for this element.
( <oid-at26> NAME 'defaultSettingRefs' ( <oid-oc14> NAME 'cim22DefaultSettingAuxClass'
DESC 'default setting to use for this class DESC 'DefaultSetting represents the association between a
SYNTAX DN ManagedSystemElement and the single Setting class that is
) defined to be the default setting for this
Element. Attribute cimElementRef points to
( <oid-oc14> NAME 'dmtfDefaultSettingAuxClass' cim22ManagedSystemElement and attribute cimSettingRef points
DESC 'represents the association between a ManagedSystemElement to cim22Setting.'
and the single Setting class that is defined to be the SUP cim22ElementSettingAuxClass AUXILIARY
default setting for this Element.' MAY (cimElementRef $ cimSettingRef)
SUP dmtfElementSettingAuxClass AUXILIARY
MUST (defaultSettingRefs)
) )
2.15 dmtfSettingContextAuxClass Association 3.15 cim22SettingContextAuxClass
This auxiliary class associates a setting with one or more This auxiliary class associates a setting with one or more
configuration objects. For example, a network adapter's settings configuration objects. For example, a network adapter's settings
could change based on the site/network to which its hosting computer could change based on the site/network to which its hosting computer
system is attached. This class uses the dmtfConfigurationRefs and system is attached.
dmtfSettingRefs attributes previously defined.
( <oid-at27> NAME 'contextRefs' ( <oid-at29> NAME 'cimContextRef'
DESC 'The configuration object that aggregates settings' DESC 'The Configuration object that aggregates the Setting.'
SYNTAX DN SYNTAX DN
) )
( <oid-oc15> NAME 'dmtfSettingContextAuxClass' ( <oid-oc15> NAME 'cim22SettingContextAuxClass'
DESC 'associates a Setting with one or more Configuration objects.' DESC '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. Here, 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. Attribute cimContextRef points to
cim22Configuration and attribute cimSettingRef points to
cim22Setting.'
SUP top AUXILIARY SUP top AUXILIARY
MUST (contextRefs $ settingRefs) MAY (cimContextRef $ cimSettingRef)
) )
2.16 dmtfCollectionSettingAuxClass 3.16 cim22CollectionSettingAuxClass
This auxiliary class represents the association between a This auxiliary class represents the association between a
dmtfCollectionOfMSEs class and the dmtfSetting class(es) defined for cim22CollectionOfMSEs class and the cim22Setting class(es) defined
them. It reuses the collectionRefs and settingRefs attributes. for them.
( <oid-oc16> NAME 'dmtfCollectionSettingAuxClass' ( <oid-oc16> NAME 'cim22CollectionSettingAuxClass'
DESC 'association between a CollectionOfMSEs class and the DESC 'CollectionSetting represents the association between a
Setting class(es) defined for them.' CollectionOfMSEs class and the Setting class(es) defined
for them. Attribute cimCollectionRef points to
cim22CollectionOfMSEs and attribute cimSettingRef points to
cim22Setting.'
SUP top AUXILIARY SUP top AUXILIARY
MUST (collectionRefs $ settingRefs) MAY (cimCollectionRef $ cimSettingRef)
) )
2.17 dmtfSystem Class 3.17 cim22System
This class is a logical element that aggregates an enumerable set of This class is a logical element that aggregates an enumerable set of
managed system elements and operates as a functional whole. Within managed system elements and operates as a functional whole. Within
any particular subclass of system, there is a well-defined list of any particular subclass of system, there is a well-defined list of
managed system element classes whose instances must be aggregated. managed system element classes whose instances must be aggregated.
This class uses the attributes creationClassName and name previously ( <oid-at30> NAME 'cimNameFormat'
defined and defines the attributes nameFormat, primaryOwnerContact, DESC 'The System object and its derivatives are Top Level Objects
primaryOwnerName, and roles. The nameFormat attribute identifies how of CIM. They provide the scope for numerous
the system name was generated. Primary owner information (name and components. Having unique System keys is required. A
contact) are stored in the primaryOwnerName and primaryOwnerContact heuristic can be defined in individual System subclasses to
information, respectively. The roles attributes is an array of attempt to always generate the same System Name Key. The
strings specifying the roles this system plays. NameFormat property identifies how the System name was
generated, using the subclass' heuristic.'
( <oid-at28> NAME 'nameFormat'
DESC 'identifies how the System name was generated, using the
subclass heuristic.'
SYNTAX string{64} SINGLE-VALUE SYNTAX string{64} SINGLE-VALUE
) )
( <oid-at29> NAME 'primaryOwnerContact' ( <oid-at31> NAME 'cimPrimaryOwnerContact'
DESC 'A string that provides information on how the primary DESC 'A string that provides information on how the primary
system owner can be reached (e.g. phone number, email system owner can be reached (e.g. phone number, email
address, ...' address, ...).'
SYNTAX string{256} SINGLE-VALUE SYNTAX string{256} SINGLE-VALUE
) )
( <oid-at30> NAME 'primaryOwnerName' ( <oid-at32> NAME 'cimPrimaryOwnerName'
DESC 'The name of the primary system owner.' DESC 'The name of the primary system owner.'
SYNTAX string{64} SINGLE-VALUE SYNTAX string{64} SINGLE-VALUE
) )
( <oid-at31> NAME 'roles' ( <oid-at33> NAME 'cimRoles'
DESC 'what roles this System plays in the IT-environment.' DESC '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".'
SYNTAX string SYNTAX string
) )
( <oid-oc17> NAME 'dmtfSystem' ( <oid-oc17> NAME 'cim22System'
DESC 'A Logical Element that aggregates an enumerable set of DESC 'A cim22System is a LogicalElement that aggregates an
Managed System Elements.' enumerable set of Managed System Elements. The aggregation
SUP dmtfLogicalElement ABSTRACT operates as a functional whole. Within any particular
MUST (creationClassName $ name $ nameFormat $ subclass of System, there is a well-defined list of Managed
primaryOwnerContact $ primaryOwnerName $ roles) System Element classes whose instances must be aggregated.'
SUP cim22LogicalElement
MUST (cimCreationClassName $ cimName)
MAY (cimNameFormat $ cimPrimaryOwnerContact $
cimPrimaryOwnerName $ cimRoles)
) )
2.18 dmtfComputerSystem Class ( <oid-nf2> NAME 'cim22SystemNameForm'
OC cim22System
MUST (orderedCimModelPath)
)
This class is derived from dmtfSystem and represents a special ( <sr2> NAME 'cim22SystemStructureRule'
FORM cim22SystemNameForm
)
The following content rule specifies the auxiliary classes that may
be attached to cim22System.
( <oid-oc17> NAME 'cim22SystemContentRule'
DESC 'The auxiliary classes that may be attached to cim22System'
AUX (cim22SystemComponentAuxClass $ cim22CollectedMSEsAuxClass $
cim22LogicalIdentityAuxClass $ cim22ElementSettingAuxClass $
cim22DependencyAuxClass $ cim22ComponentAuxClass $
cim22ElementConfigurationAuxClass $
cim22ProvidesServiceToElementAuxClass)
)
3.18 cim22ComputerSystem
This class is derived from cim22System and represents a special
collection of managed system elements that provide compute collection of managed system elements that provide compute
capabilities. Thus, it serves as aggregation point to associate one capabilities. Thus, it serves as aggregation point to associate one
or more of the following elements: file systems, operating systems, or more of the following elements: file systems, operating systems,
processors and memory (volatile and/or non-volatile storage). This processors and memory (volatile and/or non-volatile storage).
class overrides the nameFormat attribute to show the CIM V2 System
model heuristic for determining the computer system's name. It also
defines the attributes otherIdentifyingInfo, identifyingDescriptions,
and dedicated.
( <oid-at32> NAME 'otherIdentifyingInfo' ( <oid-at36> NAME 'cimDedicated'
DESC 'captures additional data, beyond system name information, DESC 'Enumeration indicating whether the ComputerSystem is a
that could be used to identify a computer system.' special-purpose System (ie, dedicated to a particular use),
SYNTAX string{256} 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).'
SYNTAX integer
) )
( <oid-at33> NAME 'identifyingDescriptions' ( <oid-oc18> NAME 'cim22ComputerSystem'
DESC 'An array of free-form strings providing explanations and DESC 'A class derived from System that is a special collection of
details behind the entries in the otherIdentifyingInfo ManagedSystemElements. This collection provides compute
array.' capabilities and serves as aggregation point to associate
SYNTAX string one or more of the following elements: FileSystem,
OperatingSystem, Processor and Memory (Volatile and/or
NonVolatile Storage).'
SUP cim22System
MAY (cimDedicated)
) )
( <oid-nf11> NAME 'cim22ComputerSystemNameForm'
( <oid-at34> NAME 'dedicated' OC cim22ComputerSystem
DESC 'Enumeration showing whether the ComputerSystem is a MUST (orderedCimModelPath)
special-purpose System (ie, dedicated to a particular use),
versus being "general purpose".'
SYNTAX integer
) )
( <oid-oc18> NAME 'dmtfComputerSystem' ( <sr11> NAME 'cim22ComputerSystemStructureRule'
DESC 'a special collection of ManagedSystemElements that provide FORM cim22ComputerSystemNameForm
compute capabilities'
SUP dmtfSystem ABSTRACT
MUST (otherIdentifyingInfo $ identifyingDescriptions $ dedicated)
) )
2.19 dmtfLogicalDevice Class 3.19 cim22LogicalDevice
This class represents an abstraction or emulation of a hardware This class represents an abstraction or emulation of a hardware
entity, that may or may not be realized in physical hardware. Any entity, that may or may not be realized in physical hardware. Any
characteristics of a logical device that are used to manage its characteristics of a logical device that are used to manage its
operation or configuration are contained in, or associated with, this operation or configuration are contained in, or associated with, this
object. object.
This object defines the attributes systemCreationClassName, ( <oid-at37> NAME 'cimSystemCreationClassName'
systemName, deviceID, powerManagementSupported, DESC 'The scoping System's CreationClassName.'
powerManagementCapabilities, availability, statusInfo, lastErrorCode,
errorDescription, errorCleared, powerOnHours, totalPowerOnHours and
also uses the previously defined creationClassName,
otherIdentifyingInfo and identifyingDescriptions. The
systemCreationClassName, systemName, lastErrorCode, errorCleared and
deviceID attributes are self explanatory and powerManagementSupportd
shows whether the device can be power managed. If the device can be
power managed, the capabilities for doing so are presented in the
powerManagementCapabilities attribute (an array of integers). Allowed
values for this attribute are: "Unknown", "Not Supported",
"Disabled", "Enabled", "Power Saving Modes Entered Automatically",
"Power State Settable", "Power Cycling Supported", and "Timed Power
On Supported". The availability attribute contains availability and
status of the Device, while statusInfo is an integer showing 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. ErrorDescirption is a free-form string supplying more
information about the error recorded in LastErrorCode, including
information on any corrective actions that may be taken.
( <oid-at35> NAME 'systemCreationClassName'
DESC 'The scoping System's CreationClassName. May be used as a
RDN.'
SYNTAX string{256} SINGLE-VALUE SYNTAX string{256} SINGLE-VALUE
) )
( <oid-at36> NAME 'systemName' ( <oid-at38> NAME 'cimSystemName'
DESC 'The scoping System's Name. May be used as a RDN.' DESC 'The scoping System's Name.'
SYNTAX string{256} SINGLE-VALUE SYNTAX string{256} SINGLE-VALUE
) )
( <oid-at37> NAME 'deviceID' ( <oid-at39> NAME 'cimDeviceID'
DESC 'An address or other identifying information to uniquely DESC 'An address or other identifying information to uniquely
name the LogicalDevice. May be used as a RDN.' name the LogicalDevice.'
SYNTAX string{64} SINGLE-VALUE SYNTAX string{64} SINGLE-VALUE
) )
( <oid-at38> NAME 'powerManagementSupported' ( <oid-at40> NAME 'cimPowerManagementSupported'
DESC 'shows if the Device can be power managed - ie, put into DESC 'Boolean indicating that the Device can be power managed -
a power save state.' ie, put into a power save state. This boolean does not
show 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.'
SYNTAX boolean SINGLE-VALUE SYNTAX boolean SINGLE-VALUE
) )
( <oid-at39> NAME 'powerManagementCapabilities' ( <oid-at41> NAME 'cimPowerManagementCapabilities'
DESC 'Indicates the specific power-related capabilities of a DESC 'Shows the specific power-related capabilities of a
LogicalDevice.' LogicalDevice. The array values, 0="Unknown", 1="Not
Supported" and 2="Disabled" are self-explanatory. The
value, 3="Enabled" shows 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) shows that the
SetPowerState method is supported. "Power Cycling
Supported" (6) shows that the SetPowerState method can
be invoked with the PowerState input variable set to 5
("Power Cycle"). "Timed Power On Supported" (7) shows
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.'
SYNTAX integer SYNTAX integer
) )
( <oid-at40> NAME 'availability' ( <oid-at42> NAME 'cimAvailability'
DESC 'The availability and status of the Device.' DESC 'The availability and status of the Device. For example, the
Availability property shows 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") shows 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") shows 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")
shows that the Device is in a warning state, though
also in a power save mode.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at41> NAME 'statusInfo' ( <oid-at43> NAME 'cimStatusInfo'
DESC 'logical device state' DESC 'StatusInfo is a string indicating 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.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at42> NAME 'lastErrorCode' ( <oid-at44> NAME 'cimLastErrorCode'
DESC 'the last error code reported by the LogicalDevice.' DESC 'LastErrorCode captures the last error code reported by the
LogicalDevice.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at43> NAME 'errorDescription' ( <oid-at45> NAME 'cimErrorDescription'
DESC 'more information about the error recorded in LastErrorCode' DESC '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.'
SYNTAX string SINGLE-VALUE SYNTAX string SINGLE-VALUE
) )
( <oid-at44> NAME 'errorCleared' ( <oid-at46> NAME 'cimErrorCleared'
DESC 'shows that the error reported in LastErrorCode is now DESC 'ErrorCleared is a boolean property indicating that the
cleared.' error reported in LastErrorCode is now cleared.'
SYNTAX boolean SINGLE-VALUE SYNTAX boolean SINGLE-VALUE
) )
( <oid-at45> NAME 'powerOnHours'
DESC 'The number of consecutive hours that this Device has been
powered, since its last power cycle.'
SYNTAX integer SINGLE-VALUE
)
( <oid-at46> NAME 'totalPowerOnHours'
DESC 'The total number of hours that this Device has been
powered.'
SYNTAX integer SINGLE-VALUE
)
( <oid-oc19> NAME 'dmtfLogicalDevice'
DESC 'An abstraction or emulation of a hardware entity'
SUP dmtfLogicalElement ABSTRACT
MUST (systemCreationClassName $ systemName $ creationClassName $
deviceID $ powerManagementSupported $
powerManagementCapabilities $ availability $ statusInfo $
lastErrorCode $ errorDescription $ errorCleared $
otherIdentifyingInfo $ powerOnHours $ totalPowerOnHours $
identifyingDescriptions)
)
Although systemCreationClassName and systemName may be used as RDNs
for this class, the solution taken in this schema is to require that
this class follow the containment and name form rules below.
( 1 NAME 'dmtfLogicalDeviceStructureRule2'
FORM dmtfLogicalDeviceNameForm1
SUP 3 4
)
( 2 NAME 'dmtfLogicalDeviceStructuralRule2'
FORM dmtfLogicalDeviceNameForm2
SUP 3 4
)
( <oid-nf1> NAME 'dmtfLogicalDeviceNameForm1'
OC dmtfLogicalDevice
MUST (creationClassName)
)
( <oid-nf2> NAME 'dmtfLogicalDeviceNameForm2' ( <oid-oc19> NAME 'cim22LogicalDevice'
OC dmtfLogicalDevice DESC 'An abstraction or emulation of a hardware entity, that may
MUST (deviceID) 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.'
SUP cim22LogicalElement
MUST (cimSystemCreationClassName $ cimSystemName $
cimCreationClassName $ cimDeviceID)
MAY (cimPowerManagementSupported $ cimAvailability $
cimPowerManagementCapabilities $ cimStatusInfo $
cimLastErrorCode $ cimErrorDescription $ cimErrorCleared)
) )
( <oid-nf3> NAME 'dmtfSystemNameForm1' ( <oid-nf3> NAME 'cim22LogicalDeviceNameForm'
OC dmtfSystem OC cim22LogicalDevice
MUST (creationClassName) MUST (orderedCimModelPath)
) )
( <oid-nf4> NAME 'dmtfSystemNameForm2' ( <sr3> NAME 'cim22LogicalDeviceStructureRule'
OC dmtfSystem FORM cim22LogicalDeviceNameForm
MUST (name) SUP <sr2>
) )
( 3 NAME 'dmtfSystemStructureRule1' The following content rule specifies the auxiliary classes that may
FORM dmtfSystemNameForm1 be attached to cim22LogicalDevice.
)
( 4 NAME 'dmtfSystemStructureRule2' ( <oid-oc19> NAME 'cim22LogicalDeviceContentRule'
FORM dmtfSystemNameForm1 DESC 'The auxiliary classes that may be attached to
cim22LogicalDevice'
AUX (cim22RealizesAuxClass $ cim22LogicalIdentityAuxClass $
cim22CollectedMSEsAuxClass $
cim22ElementConfigurationAuxClass $
cim22ElementSettingAuxClass $ cim22DependencyAuxClass $
cim22ProvidesServiceToElementAuxClass $
cim22ComponentAuxClass $ cim22SystemComponentAuxClass)
) )
2.20 dmtfService Class 3.20 cim22Service
This class represents a Logical Element that contains the information This class represents a Logical Element that contains the information
necessary to represent and manage the functionality provided by a necessary to represent and manage the functionality provided by a
device and/or software feature. A service is a general-purpose object device and/or software feature. A service is a general-purpose object
to configure and manage the implementation of functionality. It is to configure and manage the implementation of functionality. It is
not the functionality itself. not the functionality itself.
This class uses the systemCreationClassName, systemName, ( <oid-at47> NAME 'cimStartMode'
creationClassName and name attributes previously defined. It also DESC 'StartMode is a string value indicating whether the Service
defines the attributes startMode and started. The startMode is automatically started by a System, Operating System,
attribute shows whether a service is automatically started or only etc. or only started on request.'
started on request, while started shows if the service has been
started or stopped.
( <oid-at47> NAME 'startMode'
DESC 'shows whether the Service is automatically started by a
System, Operating System, etc. or only started on
request.'
SYNTAX string{10} SINGLE-VALUE SYNTAX string{10} SINGLE-VALUE
) )
( <oid-at48> NAME 'started' ( <oid-at48> NAME 'cimStarted'
DESC 'boolean showing whether the Service has been started DESC 'Started is a boolean indicating whether the Service has
(TRUE), or stopped (FALSE).' been started (TRUE), or stopped (FALSE).'
SYNTAX boolean SINGLE-VALUE SYNTAX boolean SINGLE-VALUE
) )
( <oid-oc20> NAME 'dmtfService' ( <oid-oc20> NAME 'cim22Service'
DESC 'information necessary to represent and manage the DESC 'A cim22Service is a Logical Element that contains the
functionality provided by a Device and/or SoftwareFeature.' information necessary to represent and manage the
functionality provided by a Device and/or
SUP dmtfLogicalElement ABSTRACT SoftwareFeature. A Service is a general-purpose object to
MUST (creationClassName $ name $ startMode $ started $ configure and manage the implementation of
systemCreationClassName $ systemName) functionality. It is not the functionality itself.'
SUP cim22LogicalElement
MUST (cimCreationClassName $ cimName $ cimSystemName $
cimSystemCreationClassName)
MAY (cimStartMode $ cimStarted)
) )
Although systemCreationClassName and systemName may be used as RDNs ( <oid-nf4> NAME 'cim22ServiceNameForm'
for this class, the solution taken in this schema is to require that OC cim22Service
this class follow the containment and name form rules below. MUST (orderedCimModelPath)
( 5 NAME 'dmtfServiceStructureRule1'
FORM dmtfServiceNameForm1
SUP 3 4
) )
( <oid-nf5> NAME 'dmtfServiceNameForm1' ( <sr4> NAME 'cim22ServiceStructureRule'
OC dmtfService FORM cim22ServiceNameForm
MUST (creationClassName) SUP <sr2>
) )
( 6 NAME 'dmtfServiceStructureRule2' The following content rule specifies the auxiliary classes that may
FORM dmtfServiceNameForm2 be attached to cim22Service.
SUP 3 4
)
( <oid-nf6> NAME 'dmtfServiceNameForm' ( <oid-oc20> NAME 'cim22ServiceContentRule'
OC dmtfService DESC 'The auxiliary classes that may be attached to cim22Service'
MUST (name) AUX (cim22ServiceAccessBySAPAuxClass $
cim22ServiceServiceDependencyAuxClass $
cim22ServiceSAPDependencyAuxClass $
cim22ProvidesServiceToElementAuxClass $
cim22ServiceComponentAuxClass $
cim22LogicalIdentityAuxClass $ cim22CollectedMSEsAuxClass $
cim22ElementConfigurationAuxClass $
cim22ElementSettingAuxClass $ cim22DependencyAuxClass $
cim22ComponentAuxClass $ cim22SystemComponentAuxClass)
) )
2.21 dmtfServiceAccessPoint Class This class represents the ability to 3.21 cim22ServiceAccessPoint
use or invoke a service. Access points represent that a service is made
available to other entities for use. This class uses the previously
defined attributes creationClassName, name, systemCreationClassName and
systemName.
( <oid-oc21> NAME 'dmtfServiceAccessPoint'
DESC 'representation of the ability to use or invoke a Service'
SUP dmtfLogicalElement ABSTRACT
MUST (creationClassName $ name $ systemCreationClassName $ systemName)
)
Although systemCreationClassName and systemName may be used as RDNs for This class represents the ability to use or invoke a service. Access
this class, the solution taken in this schema is to require that this points represent that a service is made available to other entities
class follow the containment and name form rules below. for use.
( 7 NAME 'dmtfServiceAccessPointStructureRule1' ( <oid-oc21> NAME 'cim22ServiceAccessPoint'
FORM dmtfServiceAccessPointNameForm1 DESC 'cim22ServiceAccessPoint represents the ability to use or
SUP 3 4 invoke a Service. Access points represent that a Service is
made available to other entities for use.'
SUP cim22LogicalElement
MUST (cimCreationClassName $ cimName $ cimSystemName $
cimSystemCreationClassName)
)
) ( <oid-nf5> NAME 'cim22ServiceAccessPointNameForm'
OC cim22ServiceAccessPoint
MUST (orderedCimModelPath)
)
( <oid-nf7> NAME 'dmtfServiceAccessPointNameForm1' ( <sr5> NAME 'cim22ServiceAccessPointStructureRule'
OC dmtfServiceAccessPoint FORM cim22ServiceAccessPointNameForm
MUST (creationClassName) SUP <sr2>
) )
( 8 NAME 'dmtfServiceAccessPointStructureRule2' The following content rule specifies the auxiliary classes that may
FORM dmtfServiceAccessPointNameForm2 be attached to cim22ServiceAccessPoint.
SUP 3 4
)
( <oid-nf8> NAME 'dmtfServiceAccessPointNameForm2' ( <oid-oc21> NAME 'cim22ServiceAccessPointContentRule'
OC dmtfServiceAccessPoint DESC 'The auxiliary classes that may be attached to
MUST (name) cim22ServiceAccessPoint'
) AUX (cim22ServiceAccessBySAPAuxClass $
cim22ServiceSAPDependencyAuxClass $
cim22SAPSAPDependencyAuxClass $
cim22LogicalIdentityAuxClass $ cim22CollectedMSEsAuxClass $
cim22ElementConfigurationAuxClass $
cim22ElementSettingAuxClass $ cim22DependencyAuxClass $
cim22ProvidesServiceToElementAuxClass $
cim22ComponentAuxClass $ cim22SystemComponentAuxClass)
)
2.22 dmtfDependencyAuxClass Association 3.22 cim22DependencyAuxClass
This class represents a generic association used to establish This class represents a generic association used to establish
dependency relationships between objects. It defines two attributes dependency relationships between objects.
antecedentRefs and dependentRefs, which must both point to
dmtfManagedSystemElement objects.
( <oid-at49> NAME 'antecedentRefs'
DESC 'the independent objects in this association.'
SYNTAX DN
)
( <oid-at50> NAME 'dependentRefs' ( <oid-at49> NAME 'cimAntecedentRef'
DESC 'the object dependent on the antecedent.' DESC 'Antecedent represents the independent object in this
association.'
SYNTAX DN SYNTAX DN
) )
( <oid-oc22> NAME 'dmtfDependencyAuxClass' ( <oid-at50> NAME 'cimDependentRef'
DESC 'generic association used to establish dependency DESC 'Dependent represents the object dependent on the
relationships between objects.' Antecedent.'
SUP top AUXILIARY
MUST (antecedentRefs $ dependentRefs)
)
2.23 dmtfDependencyContextAuxClass Association
This relationship associates a dependency with one or more
configuration objects. For example, a computer system's dependencies
could change based on the site/network to which the system is
attached.
This class reuses the contextRefs attribute defined previously and
defines the attribute dependencyRefs, which points to a set of
dmtfDependency objects.
( <oid-at51> NAME 'dependencyRefs'
DESC 'An aggregated Dependency.'
SYNTAX DN SYNTAX DN
) )
( <oid-oc23> NAME 'dmtfDependencyContextAuxClass' ( <oid-oc22> NAME 'cim22DependencyAuxClass'
DESC 'association of Dependency with one or more Configurations' DESC 'cimDependency is a generic association used to establish
dependency relationships between objects. Both attributes
point to cim22ManagedSystemElement objects.'
SUP top AUXILIARY SUP top AUXILIARY
MUST (dmtfConfigurationRefs $ dmtfDependencyRefs) MAY (cimAntecedentRef $ cimDependentRef)
) )
2.24 dmtfServiceAccessBySAPAuxClass Association 3.23 cim22ServiceAccessBySAPAuxClass
This association identifies the access points for a service. For This association identifies the access points for a service. For
example, a printer may be accessed by Netware, MacIntosh or Windows example, a printer may be accessed by Netware, MacIntosh or Windows
service access points, potentially hosted on different systems. In service access points, potentially hosted on different systems.
this association, antecedentRef points to dmtfService objects and
dependentRef points to dmtfServiceAccessPoint objects.
( <oid-oc24> NAME 'dmtfServiceAccessBySAPAuxClass' ( <oid-oc23> NAME 'cim22ServiceAccessBySAPAuxClass'
DESC 'identifies the access points for a service' DESC 'ServiceAccessBySAP is an association that identifies
SUP dmtfDependencyAuxClass AUXILIARY the access points for a Service. For example, a printer may
be accessed by Netware, MacIntosh or Windows
ServiceAccessPoints, potentially hosted on different
Systems. Attribute cimAntecedentRef points to cim22Service
and attribute cimDependentRef points to
cim22ServiceAccessPoint.'
SUP cim22DependencyAuxClass AUXILIARY
MAY (cimAntecedentRef $ cimDependentRef)
) )
2.25 dmtfServiceServiceDependencyAuxClass Association 3.24 cim22ServiceServiceDependencyAuxClass
This is an association between two services, showing that the latter This is an association between two services, showing that the latter
is required to be present, required to have completed, or must be is required to be present, required to have completed, or must be
absent for the former Service to provide its functionality. For absent for the former Service to provide its functionality. For
example, boot Services may be dependent on underlying BIOS disk and example, boot Services may be dependent on underlying BIOS disk and
initialization services. For initialization services, the boot initialization services. For initialization services, the boot
service is simply dependent on the initialization services service is simply dependent on the initialization services
completing. completing.
In this class, both antecedentRefs and dependentRefs point to ( <oid-at51> NAME 'cimTypeOfDependency'
dmtfService objects. In addition, this class stores the type of DESC 'The Service to Service dependency. This property describes
dependency in the typeOfDependency attribute. Allowed values for that the associated Service must have completed (value=2),
typeOfDepencency are: "Unknown", "Other", "Service Must Have must be started (3) or must not be started (4) in order for
Completed", "Service Must Be Started", and "Service Must Not Be the Service to function.'
Started".
( <oid-at52> NAME 'typeOfDependency'
DESC 'type of Service to Service dependency.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-oc25> NAME 'dmtfServiceServiceDependencyAuxClass' ( <oid-oc24> NAME 'cim22ServiceServiceDependencyAuxClass'
DESC 'association between two services' DESC 'ServiceServiceDependency is an association between a
SUP dmtfDependencyAuxClass AUXILIARY Service and another Service, indicating that the latter is
MUST (typeOfDependency) 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
on 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 use the
SAPs of this Service. This usage dependency is modeled via
the ServiceSAPDependency association. Both attributes
point to cim22Service objects.'
SUP cim22DependencyAuxClass AUXILIARY
MAY (cimAntecedentRef $ cimDependentRef $ cimTypeOfDependency)
) )
2.26 dmtfServiceSAPDependencyAuxClass Association 3.25 cim22ServiceSAPDependencyAuxClass
This class is an association between a service and a service access This class is an association between a service and a service access
point showing that the referenced SAP is used by the service to point showing that the referenced SAP is used by the service to
provide its functionality. For example, boot services may invoke BIOS provide its functionality. For example, boot services may invoke BIOS
disk services (interrupts) to function. disk services (interrupts) to function.
In this class, antecedentRefs point to dmtfServiceAccessPoint objects ( <oid-oc25> NAME 'cim22ServiceSAPDependencyAuxClass'
and dependentRefs point to dmtfService objects. DESC 'ServiceSAPDependency is an association between a
Service and a ServiceAccessPoint indicating that the
( <oid-oc26> NAME 'dmtfServiceSAPDependencyAuxClass' referenced SAP is used by the Service to provide its
DESC 'association between a Service and a ServiceAccessPoint' functionality. For example, Boot Services may invoke BIOS'
SUP dmtfDependencyAuxClass AUXILIARY Disk Services (interrupts) to function. Attribute
cimAntecedentRef points to cim22ServiceAccessPoint and
attribute cimDependentRef points to cim22Service.'
SUP cim22DependencyAuxClass AUXILIARY
MAY (cimAntecedentRef $ cimDependentRef)
) )
2.27 dmtfSAPSAPDependencyAuxClass Association 3.26 cim22SAPSAPDependencyAuxClass
This class is an association between two service access points This class is an association between two service access points
showing that the latter is required in order for the former to use or showing that the latter is required in order for the former to use or
connect with its service. For example, to print at a network printer, connect with its service. For example, to print at a network printer,
local print access points must use underlying network-related SAPs, local print access points must use underlying network-related SAPs,
or protocol endpoints, to send the print request. or protocol endpoints, to send the print request.
In this class, both antecedentRefs and dependentRefs point to ( <oid-oc26> NAME 'cim22SAPSAPDependencyAuxClass'
dmtfServiceAccessPoint objects. DESC 'SAPSAPDependency is an association between a
ServiceAccessPoint and another ServiceAccessPoint
( <oid-oc27> NAME 'dmtfSAPSAPDependencyAuxClass' indicating that the latter is required in order for the
DESC 'association between two ServiceAccessPoints' former ServiceAccessPoint to use or connect with its
SUP dmtfDependencyAuxClass AUXILIARY Service. For example, to print at a network printer, local
Print Access Points must use underlying network-related
SAPs, or ProtocolEndpoints, to send the print request.
Both attributes point to cim22ServiceAccessPoint objects.'
SUP cim22DependencyAuxClass AUXILIARY
MAY (cimAntecedentRef $ cimDependentRef)
) )
2.28 dmtfProvidesServiceToElementAuxClass 3.27 cim22ProvidesServiceToElementAuxClass
This association is used to describe that dmtfManagedSystemElements This association is used to describe that cim22ManagedSystemElements
may be dependent on the functionality of one or more Services. In may be dependent on the functionality of one or more Services.
this class antecedentRefs point to dmtfService objects and
dependentRefs point to dmtfManagedSystemElement objects.
( <oid-oc28> NAME 'dmtfProvidesServiceToElementAuxClass' ( <oid-oc27> NAME 'cim22ProvidesServiceToElementAuxClass'
DESC 'this association is used to describe that DESC 'ProvidesServiceToElement is used to describe that
ManagedSystemElements may be dependent on the functionality ManagedSystemElements may be dependent on the functionality
of one or more Services.' of one or more Services. An example is that a Processor and
SUP dmtfDependencyAuxClass AUXILIARY an Enclosure (PhysicalElement) are dependent on AlertOnLAN
Services to signal an incomplete or erroneous boot, and
hardware-related errors. Attribute cimAntecedentRef points
to cim22Service and attribute cimDependentRef points to
cim22ManagedSystemElement.'
SUP cim22DependencyAuxClass AUXILIARY
MAY (cimAntecedentRef $ cimDependentRef)
) )
2.29 dmtfRealizesAuxClass Association 3.28 cim22RealizesAuxClass
This association defines the mapping between a logical device and the This association defines the mapping between a logical device and the
physical component that implements the device. In this class, physical component that implements the device.
antecedentRefs points to dmtfPhysicalElement objects and
dependentRefs points to dmtfLogicalElement objects.
( <oid-oc29> NAME 'dmtfRealizesAuxClass' ( <oid-oc28> NAME 'cim22RealizesAuxClass'
DESC 'mapping between a Logical Device and the physical component DESC 'Realizes is the association that defines the mapping
that implements the Device.' between a Logical Device and the physical component that
SUP dmtfDependencyAuxClass AUXILIARY implements the Device. Attribute cimAntecedentRef points to
cim22PhysicalElement and attribute cimDependentRef points to
cim22LogicalDevice.'
SUP cim22DependencyAuxClass AUXILIARY
MAY (cimAntecedentRef $ cimDependentRef)
) )
2.30 dmtfComponentAuxClass Association 3.29 cim22ComponentAuxClass
This class is a generic association used to establish 'part of' This class is a generic association used to establish 'part of'
relationships between managed system elements. For example, the relationships between managed system elements. For example, the
system component association defines parts of a system. This class system component association defines parts of a system.
defines two attributes: groupRefs, which holds the parent elements of
the association and partRefs, which holds the children elements of
the association. In this class, both attributes point to
dmtfManagedSystemElement objects.
( <oid-at53> NAME 'groupRefs' ( <oid-at52> NAME 'cimGroupComponentRef'
DESC 'The parent elements in the association.' DESC 'The parent element in the association.'
SYNTAX DN SYNTAX DN
) )
( <oid-at54> NAME 'partRefs' ( <oid-at53> NAME 'cimPartComponentRef'
DESC 'The children elements in the association.' DESC 'The child element in the association.'
SYNTAX DN SYNTAX DN
) )
( <oid-oc30> NAME 'dmtfComponentAuxClass' ( <oid-oc29> NAME 'cim22ComponentAuxClass'
DESC 'generic association used to establish part of relationships DESC 'Component is a generic association used to establish
between managed system elements.' "part of" relationships between Managed System
Elements. For example, the SystemComponent association
defines parts of a System. Both attributes point to
cim22ManagedSystemElement objects.'
SUP top AUXILIARY SUP top AUXILIARY
MUST (groupRefs $ partRefs) MAY (cimGroupComponentRef $ cimPartComponentRef)
) )
2.31 dmtfSystemComponentAuxClass Association 3.30 cim22SystemComponentAuxClass
This class is a specialization of the dmtfComponentAuxClass This class is a specialization of the cim22ComponentAuxClass
association that establishes part of relationships between a system association that establishes part of relationships between a system
and the managed system elements of which it is composed. In this and the managed system elements of which it is composed.
class, groupRefs points to dmtfSystem objects while partRefs
continues to dmtfManagedSystemElement objects.
( <oid-oc31> NAME 'dmtfSystemComponentAuxClass' ( <oid-oc30> NAME 'cim22SystemComponentAuxClass'
DESC 'specialization of dmtfComponent handling relationships DESC 'SystemComponent is a specialization of the
between a System and the Managed System Elements of which Component association that establishes "part of"
it is composed.' relationships between a System and the Managed System
SUP dmtfComponentAuxClass AUXILIARY Elements of which it is composed. Attribute
cimGroupComponentRef points to cim22System and attribute
cimPartComponentRef points to cim22ManagedSystemElement.'
SUP cim22ComponentAuxClass AUXILIARY
MAY (cimGroupComponentRef $ cimPartComponentRef)
) )
2.32 dmtfServiceComponentAuxClass 3.31 cim22ServiceComponentAuxClass
This auxiliary class models a set of subordinate services that are This auxiliary class models a set of subordinate services that are
aggregated together to form a higher-level service. In it, both aggregated together to form a higher-level service.
groupRefs and partRefs both point to dmtfService objects.
( <oid-oc32> NAME 'dmtfServiceComponentAuxClass' ( <oid-oc31> NAME 'cim22ServiceComponentAuxClass'
DESC 'The ServiceComponent aggregation models a set of DESC 'The ServiceComponent aggregation models a set of
subordinate Services that are aggregated together to form a subordinate Services that are aggregated together to form a
higher-level service.' higher-level service. Both attributes point to cim22Service
SUP dmtfComponentAuxClass AUXILIARY objects.'
SUP cim22ComponentAuxClass AUXILIARY
MAY (cimGroupComponentRef $ cimPartComponentRef)
) )
2.33 dmtfProduct Class 3.32 cim22Product
This concrete class that is a collection of physical elements, This concrete class that is a collection of physical elements,
software features and/or other products, acquired as a unit. software features and/or other products, acquired as a unit.
Acquisition implies an agreement between supplier and consumer that Acquisition implies an agreement between supplier and consumer that
may have implications to product licensing, support and warranty. may have implications to product licensing, support and warranty.
This class uses the previously defined attributes caption, ( <oid-at54> NAME 'cimIdentifyingNumber'
description, name, sKU, and version and defines attributes DESC 'Product identification such as a serial number on software,
identifyingNumber and vendor. The identifyingNumber provides product a die number on a hardware chip, or (for non-commercial
identification, while vendor contains the name of the product's Products) a project number.'
supplier. Both of these attributes may be used as a RDN.
( <oid-at55> NAME 'identifyingNumber'
DESC 'Product identification such as a serial number on software
or a die number on a hardware chip.'
SYNTAX string{64} SINGLE-VALUE SYNTAX string{64} SINGLE-VALUE
) )
( <oid-at55> NAME 'cimVendor'
( <oid-at56> NAME 'vendor' DESC 'The name of the Product's supplier, or entity selling the
DESC 'The name of the supplier.' Product (the manufacturer, reseller, OEM, etc.).
Corresponds to the Vendor property in the Product object in
the CIM Solution Exchange Standard.'
SYNTAX string{256} SINGLE-VALUE SYNTAX string{256} SINGLE-VALUE
) )
( <oid-oc33> NAME 'dmtfProduct' ( <oid-at56> NAME 'cimSKUNumber'
DESC 'collection of PhysicalElements, SoftwareFeatures and/or DESC 'Product SKU (stock keeping unit) information.'
other Products, acquired as a unit.' SYNTAX string{64} SINGLE-VALUE
)
( <oid-oc32> NAME 'cim22Product'
DESC 'cim22Product 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 that 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 cim22Product.'
SUP top SUP top
MUST (caption $ description $ identifyingNumber $ name $ MUST (cimIdentifyingNumber $ cimName $ cimVendor $ cimVersion $
sKUNumber $ vendor $ version) orderedCimModelPath)
MAY (cimCaption $ cimDescription $ cimSKUNumber)
) )
2.34 dmtfProductParentChildAuxClass Association ( <oid-nf6> NAME 'cim22ProductNameForm'
OC cim22Product
MUST (orderedCimModelPath)
)
( <sr6> NAME 'cim22ProductStructureRule'
FORM cim22ProductNameForm
)
The following content rule specifies the auxiliary classes that may
be attached to cim22Product.
( <oid-oc32> NAME 'cim22ProductContentRule'
DESC 'The auxiliary classes that may be attached to cim22Product'
AUX (cim22ProductParentChildAuxClass $
cim22CompatibleProductAuxClass $
cim22ProductProductDependencyAuxClass $
cim22ProductSupportAuxClass $ cim22ProductFRUAuxClass $
cim22ProductPhysicalElementsAuxClass $
cim22FRUIncludesProductAuxClass)
)
3.33 cim22ProductParentChildAuxClass
The association defines a parent child hierarchy among products. For The association defines a parent child hierarchy among products. For
example, a product may come bundled with other products. This class example, a product may come bundled with other products.
defines two attributes: parentRefs (the parent of the association)
and childRefs (the children of the association). In this class, both
attributes point to dmtfProduct objects.
( <oid-at57> NAME 'parentRefs' ( <oid-at57> NAME 'cimParentRef'
DESC 'The parent Product in the association.' DESC 'The parent Product in the association.'
SYNTAX DN SYNTAX DN
) )
( <oid-at58> NAME 'childRefs' ( <oid-at58> NAME 'cimChildRef'
DESC 'The child Product in the association.' DESC 'The child Product in the association.'
SYNTAX DN SYNTAX DN
) )
( <oid-oc34> NAME 'dmtfProductParentChildAuxClass' ( <oid-oc33> NAME 'cim22ProductParentChildAuxClass'
DESC 'parent child hierarchy among Products' DESC 'The ProductParentChild association defines a parent
child hierarchy among Products. For example, a Product may
come bundled with other Products. Both attributes point to
cim22Product objects.'
SUP top AUXILIARY SUP top AUXILIARY
MUST (parentRefs $ childRefs) MAY (cimParentRef $ cimChildRef)
) )
2.35 dmtfCompatibleProductAuxClass Association 3.34 cim22CompatibleProductAuxClass Association
This association between products can show a wide variety of This association between products can show a wide variety of
information. For example, it can show that the two referenced information. For example, it can show that the two referenced
products interoperate, that they can be installed together, that one products interoperate, that they can be installed together, that one
can be the physical container for the other, etc. The string can be the physical container for the other, etc.
attribute compatibilityDescription, defines how the products
interoperate or are compatible. This class also defines attributes
productRefs and compatibleProductRefs, both of which point to
dmtfProduct objects.
( <oid-at59> NAME 'productRefs' ( <oid-at59> NAME 'cimProductRef'
DESC 'The Product for which compatible offerings are defined.' DESC 'The Product for which compatible offerings are defined.'
SYNTAX DN SYNTAX DN
) )
( <oid-at60> NAME 'compatibleProductRefs' ( <oid-at60> NAME 'cimCompatibleProductRef'
DESC 'The compatible Product.' DESC 'The compatible Product.'
SYNTAX DN SYNTAX DN
) )
( <oid-at61> NAME 'compatibilityDescription' ( <oid-at61> NAME 'cimCompatibilityDescription'
DESC 'free-form string defining how the two referenced product DESC 'CompatibilityDescription is a free-form string defining
interoperate' how the two referenced Products interoperate or are
compatible, any limitations to compatibility, etc.'
SYNTAX string SINGLE-VALUE SYNTAX string SINGLE-VALUE
) )
( <oid-oc34> NAME 'cim22CompatibleProductAuxClass'
( <oid-oc35> NAME 'dmtfCompatibleProductAuxClass' DESC 'CompatibleProduct is an association between Products
DESC 'an association between Products' that can show a wide variety of information. For
example, it can show 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, ... Both
reference attributes point to cim22Product objects.'
SUP top AUXILIARY SUP top AUXILIARY
MUST (productRefs $ compatibleProductRefs $ MAY (cimProductRef $ cimCompatibleProductRef $
compatibilityDescription) cimCompatibilityDescription)
) )
2.36 dmtfProductProductDependencyAuxClass Association 3.35 cim22ProductProductDependencyAuxClass
This association is between two products, showing that one must be This association is between two products, showing that one must be
installed, or must be absent, for the other to function. This is installed, or must be absent, for the other to function. This is
conceptually equivalent to the service to service dependency conceptually equivalent to the service to service dependency
association. association.
This class defines the attributes requiredProductRefs and ( <oid-at62> NAME 'cimRequiredProductRef'
dependentProductRefs, and uses the previously defined
typeOfDependency attribute. The reference attributes both point to
dmtfProduct objects.
( <oid-at62> NAME 'requiredProductRefs'
DESC 'The required Product.' DESC 'The required Product.'
SYNTAX DN SYNTAX DN
) )
( <oid-at63> NAME 'dependentProductRefs' ( <oid-at63> NAME 'cimDependentProductRef'
DESC 'The Product that is dependent on another Product.' DESC 'The Product that is dependent on another Product.'
SYNTAX DN SYNTAX DN
) )
( <oid-oc36> NAME 'dmtfProductProductDependencyAuxClass' ( <oid-oc35> NAME 'cim22ProductProductDependencyAuxClass'
DESC 'dependency association between two products' DESC '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.
Both reference attributes point to cim22Product objects.'
SUP top AUXILIARY SUP top AUXILIARY
MUST (requiredProductRefs $ dependentProductRefs $ typeOfDependency) MAY (cimRequiredProductRef $ cimDependentProductRef $
cimTypeOfDependency)
) )
2.37 dmtfSupportAccess Class 3.36 cim22SupportAccess
This class defines how to obtain help for a product. It defines This class defines how to obtain help for a product.
attributes communicationInfo (providing information about the
communicationMode), communicationMode (defines the form of
communication available), locale (defines the geographic region), and
supportAccessId (arbitrary, free form string that may be used as a
RDN). In addition, it uses the previously defined attribute
description.
( <oid-at64> NAME 'communicationInfo' ( <oid-at64> NAME 'cimSupportAccessId'
DESC 'provides the details of the CommunicationMode. For example, DESC 'SupportAccessID is an arbitrary, free form string defined
if the CommunicationMode is phone, CommunicationInfo by the Product Vendor or by the organization that deploys
specifies the phone number to be called.' the Product. This property, since it is a key, should be
unique throughout the enterprise.'
SYNTAX string{256} SINGLE-VALUE
)
( <oid-at65> NAME 'cimCommunicationInfo'
DESC 'CommunicationInfo provides the details of the
CommunicationMode. For example, if the CommunicationMode is
"Phone", CommunicationInfo specifies the phone number to be
called.'
SYNTAX string SINGLE-VALUE SYNTAX string SINGLE-VALUE
) )
( <oid-at65> NAME 'communicationMode' ( <oid-at66> NAME 'cimCommunicationMode'
DESC 'CommunicationMode defines the form of communication in DESC 'CommunicationMode defines the form of communication in
order to obtain support. For example, phone communication order to obtain support. For example, phone communication
(value=2), fax (3) or email (8) can be specified.' (value=2), fax (3) or email (8) can be specified.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at66> NAME 'locale' ( <oid-at67> NAME 'cimLocale'
DESC 'Locale defines the geographic region and/or language DESC 'Locale defines the geographic region and/or language
dialect to which this Support resource pertains.' dialect to which this Support resource pertains.'
SYNTAX string{64} SINGLE-VALUE SYNTAX string{64} SINGLE-VALUE
) )
( <oid-at67> NAME 'supportAccessId' ( <oid-oc36> NAME 'cim22SupportAccess'
DESC 'SupportAccessID is an arbitrary, free form string defined DESC 'The cim22SupportAccess association defines how to obtain
by the Product Vendor or by the organization that deploys help for a Product.'
the Product. This property, since it is a key, should be SUP top
unique throughout the enterprise. May be used as a RDN.' MUST (cimSupportAccessId $ orderedCimModelPath)
SYNTAX string{256} SINGLE-VALUE MAY (cimCommunicationInfo $ cimCommunicationMode $ cimLocale $
cimDescription)
) )
( <oid-oc37> NAME 'dmtfSupportAccess' ( <oid-nf7> NAME 'cim22SupportAccessNameForm'
DESC 'defines how to obtain help for a Product.' OC cim22SupportAccess
SUP top MUST (orderedCimModelPath)
MUST (communicationInfo $ communicationMode $ description $
locale $ supportAccessId)
) )
2.38 dmtfProductSupportAuxClass Association ( <sr7> NAME 'cim22SupportAccessStructureRule'
FORM cim22SupportAccessNameForm
)
The following content rule specifies the auxiliary classes that may
be attached to cim22SupportAccessProduct.
( <oid-oc36> NAME 'cim22SupportAccessContentRule'
DESC 'The auxiliary classes that may be attached to
cim22SupportAccess'
AUX (cim22ProductSupportAuxClass)
)
3.37 cim22ProductSupportAuxClass
This auxiliary class represents the association between products and This auxiliary class represents the association between products and
support access that conveys how support is obtained for the product. support access that conveys how support is obtained for the product.
This is a many-to-many relationship, implying that various types of This is a many-to-many relationship, implying that various types of
support are available for a product, and that the same support object support are available for a product, and that the same support object
can provide help for multiple products. This class defines two can provide help for multiple products. This class defines two
attributes that are self-explanatory. attributes that are self-explanatory.
( <oid-at68> NAME 'productRefs' ( <oid-at68> NAME 'cimSupportRef'
DESC 'The Product.'
SYNTAX DN
)
( <oid-at69> NAME 'supportRefs'
DESC 'Support for the Product.' DESC 'Support for the Product.'
SYNTAX DN SYNTAX DN
) )
( <oid-oc38> NAME 'dmtfProductSupportAuxClass' ( <oid-oc37> NAME 'cim22ProductSupportAuxClass'
DESC 'the association between Product and SupportAccess that DESC 'cimProductSupport is an association between Product and
conveys how support is obtained for the Product.' 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 help for
multiple Products. Attribute cimProductRef points to
cim22Product and attribute cimSupportRef points to
cim22SupportAccess.'
SUP top AUXILIARY SUP top AUXILIARY
MUST (productRefs $ supportRefs) MAY (cimProductRef $ cimSupportRef)
) )
2.39 dmtfFRU Class 3.38 cim22FRU
This class is a vendor-defined collection of products and/or physical This class is a vendor-defined collection of products and/or physical
elements that is associated with a product for supporting, elements that is associated with a product for supporting,
maintaining or upgrading that product at the customer's location. FRU maintaining or upgrading that product at the customer's location. FRU
is an acronym for 'field replaceable unit'. This class uses the is an acronym for 'field replaceable unit'.
previously defined caption, description, identifyingNumber, vendor,
and name attributes and defines the attributes fRUNumber (FRU
ordering information), and revisionLevel (FRU's revision level.)
( <oid-at70> NAME 'fRUNumber' ( <oid-at69> NAME 'cimFRUNumber'
DESC 'FRU ordering information. May be used as a RDN' DESC 'FRU ordering information.'
SYNTAX string{64} SINGLE-VALUE SYNTAX string{64} SINGLE-VALUE
) )
( <oid-at70> NAME 'cimRevisionLevel'
( <oid-at71> NAME 'revisionLevel'
DESC 'The FRU's revision level.' DESC 'The FRU's revision level.'
SYNTAX string{64} SINGLE-VALUE SYNTAX string{64} SINGLE-VALUE
) )
( <oid-oc39> NAME 'dmtfFRU' ( <oid-oc38> NAME 'cim22FRU'
DESC 'field replacible unit' DESC 'The cimFRU class is a vendor-defined collection of
Products and/or PhysicalElements that is associated with a
Product for supporting, maintaining or upgrading that
Product at the customer's location. FRU is an acronym for
"field replaceable unit". '
SUP top SUP top
MUST (caption $ description $ fRUNumber $ identifyingNumber $ MUST (cimFRUNumber $ cimIdentifyingNumber $ cimVendor $
name $ vendor $ revisionLevel) orderedCimModelPath)
MAY (cimCaption $ cimDescription $ cimName $ cimRevisionLevel)
) )
2.40 dmtfProductFRUAuxClass Association ( <oid-nf8> NAME 'cim22FRUNameForm'
OC cim22FRU
MUST (orderedCimModelPath)
)
( <sr8> NAME 'cim22FRUStructureRule'
FORM cim22FRUNameForm
)
The following content rule specifies the auxiliary classes that may
be attached to cim22FRU.
( <oid-oc38> NAME 'cim22FRUContentRule'
DESC 'The auxiliary classes that may be attached to cim22FRU'
AUX (cim22ProductFRUAuxClass $ cim22FRUPhysicalElementsAuxClass $
cim22FRUIncludesProductAuxClass)
)
3.39 cim22ProductFRUAuxClass
This auxiliary class provides information regarding what product This auxiliary class provides information regarding what product
components have been or are being replaced and uses the previously components have been or are being replaced and uses the previously
defined attribute dmtfProductRefs. It also defines the attribute defined attribute cimProductRefs.
fRURefs, which holds the FRU information.
( <oid-at72> NAME 'fRURefs' ( <oid-at71> NAME 'cimFRURef'
DESC 'The FRU.' DESC 'The FRU.'
SYNTAX DN SYNTAX DN
) )
( <oid-oc40> NAME 'dmtfProductFRUAuxClass' ( <oid-oc39> NAME 'cim22ProductFRUAuxClass'
DESC 'association between Product and FRU that provides DESC 'cimProductFRU is an association between Product and FRU
information about replacements' 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. Attribute cimProductRef points to
cim22Product and attribute cimFRURef points to cim22FRU.'
SUP top AUXILIARY SUP top AUXILIARY
MUST (productRefs $ fRURefs) MAY (cimProductRef $ cimFRURef)
) )
2.41 dmtfProductPhysicalElementsAuxClass Association 3.40 cim22ProductPhysicalElementsAuxClass
Indicates the physical elements that make up a product. It uses the Shows the physical elements that make up a product. It uses the
previously defined dmtfProductsRefs attribute and defines previously defined cimProductsRefs attribute and defines
dmtfPhysicalElementRefs. cimPhysicalElementRefs.
( <oid-at73> NAME 'componentRefs' ( <oid-at72> NAME 'cimComponentRef'
DESC 'The PhysicalElement that is a part of the Product.' DESC 'The PhysicalElement that is a part of the Product.'
SYNTAX DN SYNTAX DN
) )
( <oid-oc41> NAME 'dmtfProductPhysicalElementsAuxClass' ( <oid-oc40> NAME 'cim22ProductPhysicalElementsAuxClass'
DESC 'Indicates the PhysicalElements that make up a Product.' DESC 'Shows the PhysicalElements that make up a
Product. Attribute cimProductRef points to
cim22Product and attribute cimComponentRef points to
cim22PhysicalElement.'
SUP top AUXILIARY SUP top AUXILIARY
MUST (productRefs $ componentRefs) MAY (cimProductRef $ cimComponentRef)
) )
2.42 NAME 'dmtfFRUPhysicalElementsAuxClass' 3.41 cim22FRUPhysicalElementsAuxClass
This auxiliary class shows the physical elements that make up a FRU This auxiliary class shows the physical elements that make up a FRU
and uses previously defined attributes. and uses previously defined attributes.
( <oid-oc42> NAME 'dmtfFRUPhysicalElementsAuxClass' ( <oid-oc41> NAME 'cim22FRUPhysicalElementsAuxClass'
DESC 'Indicates the PhysicalElements that make up a FRU.' DESC 'Shows the PhysicalElements that make up a FRU. Attribute
cimFRURef points to cim22FRU and attribute cimComponentRef
points to cim22PhysicalElement.'
SUP top AUXILIARY SUP top AUXILIARY
MUST (dmtfFRURefs $ dmtfPhysicalElementRefs) MAY (cimFRURef $ cimComponentRef)
) )
2.43 dmtfFRUIncludesProductAuxClass Association 3.42 cim22FRUIncludesProductAuxClass
This auxiliary class shows that a FRU may be composed of other This auxiliary class shows that a FRU may be composed of other
product(s). It uses previously defined attributes. product(s). It uses previously defined attributes.
( <oid-oc43> NAME 'dmtfFRUIncludesProductAuxClass' ( <oid-oc42> NAME 'cim22FRUIncludesProductAuxClass'
DESC 'Indicates that a FRU may be composed of other Product(s).' DESC 'Shows that a FRU may be composed of other
SUP top AUXILIARY Product(s). Attribute cimFRURef points to cim22FRU and
MUST (dmtfFRURefs $ dmtfProductRefs) attribute cimComponentRef points to cim22Product.'
)
2.44 dmtfStatisticalInformation Class
This root class holds any arbitrary collection of statistical data
and/or metrics applicable to one or more managed system elements and
uses previously defined attributes.
( <oid-oc44> NAME 'dmtfStatisticalInformation'
DESC 'root class for any arbitrary collection of statistical data
and/or metrics applicable to one or more
ManagedSystemElements.'
SUP top ABSTRACT
MUST (name $ description $ caption)
)
2.45 dmtfStatisticsAuxClass Association
This auxiliary class relates managed system elements to the
statistical group(s) that apply to them. The attribute
dmtfStatisticalInformationRefs is defined by this class.
( <oid-at74> NAME 'statsRefs'
DESC 'The statistic information/object.'
SYNTAX DN
)
( <oid-oc45> NAME 'dmtfStatisticsAuxClass'
DESC 'association relating ManagedSystemElements to the
StatisticalGroup(s) that apply to them.'
SUP top AUXILIARY
MUST (statsRefs $ elementRefs)
)
2.46 dmtfRelatedStatisticsAuxClass Association
This auxiliary class defines hierarchies and/or dependencies of
related statistical information classes. It defines the attributes
statsRefs and relatedStatsRefs, both of which point to
dmtfStatisticalInformation objects.
( <oid-at75> NAME 'relatedStatsRefs'
DESC 'The related statistics or metrics.'
SYNTAX DN
)
( <oid-oc46> NAME 'dmtfRelatedStatisticsAuxClass'
DESC 'hierarchies and/or dependencies of related CIM_Statistical
Information classes'
SUP top AUXILIARY SUP top AUXILIARY
MUST (dmtfStatisticalInformationRefs $ MAY (cimFRURef $ cimComponentRef)
dmtfStatisticalInformationRefs)
)
2.47 dmtfSystemStatisticalInformation class
This class provides statistical information associated with a system
object or one of its subclasses. This class reuses the attributes
systemCreationClassName, systemName, creationClassName, and name.
( <oid-oc47> NAME 'dmtfSystemStatisticalInformation'
DESC 'Statistical information associated with a System object or
one of its subclasses.'
SUP dmtfStatisticalInformation
MUST (systemCreationClassName $ systemName $ creationClassName $
name)
)
Although systemCreationClassName and systemName may be used as RDNs
for this class, the solution taken in this schema is to require that
this class follow the containment and name form rules below.
( 9 NAME 'dmtfSystemStatisticsStructureRule1'
FORM dmtfSystemStatisticalInformationNameForm1
SUP 3 4
)
( <oid-nf9> NAME 'dmtfSystemStatisticalInformationNameForm1'
OC dmtfSystemStatisticalInformation
MUST (creationClassName)
)
( 10 NAME 'dmtfSystemStatisticsStructureRule2'
FORM dmtfSystemStatisticalInformationNameForm2
SUP 3 4
)
( <oid-nf10> NAME 'dmtfSystemStatisticalInformationNameForm2'
OC dmtfSystemStatisticalInformation
MUST (name)
)
2.48 dmtfServiceStatisticalInformation
Statistical information associated with a service object or one of
its subclasses. This class reuses the attributes
systemCreationClassName, systemName, creationClassName, and name. It
defines serviceCreationClassName and serviceName.
( <oid-at76> NAME 'serviceCreationClassName'
DESC 'The scoping Service's CreationClassName. May be used as
an RDN.'
SYNTAX string{256} SINGLE-VALUE
)
( <oid-at77> NAME 'serviceName'
DESC 'The scoping Service's Name. May be used as an RDN.'
SYNTAX string{256} SINGLE-VALUE
)
( <oid-oc48> NAME 'dmtfServiceStatisticalInformation'
DESC 'Statistical information associated with a Service object or
one of its subclasses.'
SUP dmtfStatisticalInformation
MUST (systemCreationClassName $ systemName $
serviceCreationClassName $ serviceName $
creationClassName $ name)
)
Although systemCreationClassName, serviceCreationClassName,
serviceName and systemName may be used as RDNs for this class, the
solution taken in this schema is to require that this class follow
the containment and name form rules below.
( 11 NAME 'dmtfServiceStatisticsStructureRule1'
FORM dmtfServiceStatisticalInformationNameForm1
SUP 5 6
)
( <oid-nf11> NAME 'dmtfServiceStatisticalInformationNameForm1'
OC dmtfServiceStatisticalInformation
MUST (creationClassName)
)
( 12 NAME 'dmtfServiceStatisticsStructureRule2'
FORM dmtfServiceStatisticalInformationNameForm2
SUP 5 6
)
( <oid-nf12> NAME 'dmtfServiceStatisticalInformationNameForm2'
OC dmtfServiceStatisticalInformation
MUST (name)
)
2.49 dmtfSAPStatisticalInformation
Statistical information associated with a service access point object
or one of its subclasses. This class reuses the attributes
systemCreationClassName, systemName, creationClassName, and name. It
further defines the attributes sAPCreationClassName and sAPName.
( <oid-at78> NAME 'sAPCreationClassName'
DESC 'The scoping SAP's CreationClassName. May be used as an
RDN.'
SYNTAX string{256} SINGLE-VALUE
)
( <oid-at79> NAME 'sAPName'
DESC 'The scoping SAP's Name. May be used as an RDN.'
SYNTAX string{256} SINGLE-VALUE
)
( <oid-oc49> NAME 'dmtfSAPStatisticalInformation'
DESC 'Statistical information associated with a
service access point object or one of its subclasses.'
SUP dmtfStatisticalInformation
MUST (systemCreationClassName $ systemName $
sAPCreationClassName $ sAPName $ creationClassName $ name)
)
Although systemCreationClassName, sAPCreationClassName, sAPName and
systemName may be used as RDNs for this class, the solution taken in
this schema is to require that this class follow the containment and
name form rules below.
( 13 NAME 'dmtfSAPStatisticsStructureRule1'
FORM dmtfSAPStatisticalInformationNameForm1
SUP 7 8
)
( <oid-nf13> NAME 'dmtfSAPStatisticalInformationNameForm1'
OC dmtfSAPStatisticalInformation
MUST (creationClassName)
)
( 14 NAME 'dmtfSAPStatisticsStructureRule2'
FORM dmtfSAPStatisticalInformationNameForm2
SUP 7 8
)
( <oid-nf14> NAME 'dmtfSAPStatisticalInformationNameForm2'
OC dmtfSAPStatisticalInformation
MUST (name)
)
2.50 dmtfDeviceStatisticalInformation
Statistical information associated with a logical device or one of
its subclasses. This class reuses the attributes
systemCreationClassName, systemName, deviceID, creationClassName,
name and defines the attribute deviceCreationClassName
( <oid-at80> NAME 'deviceCreationClassName'
DESC 'The scoping Device's CreationClassName. May be used as an
RDN.'
SYNTAX string{256} SINGLE-VALUE
)
( <oid-oc50> NAME 'dmtfDeviceStatisticalInformation'
DESC 'Statistical information associated with a LogicalDevice or
one of its subclasses.'
SUP dmtfStatisticalInformation
MUST (systemCreationClassName $ systemName $
deviceCreationClassName $ deviceID $ creationClassName $
name)
)
Although systemCreationClassName, deviceCreationClassName, deviceID
and systemName may be used as RDNs for this class, the solution taken
in this schema is to require that this class follow the containment
and name form rules below.
( 15 NAME 'dmtfDeviceStatisticsStructureRule1'
FORM dmtfDeviceStatisticalInformationNameForm1
SUP 1 2
)
( <oid-nf15> NAME 'dmtfDeviceStatisticalInformationNameForm1'
OC dmtfDeviceStatisticalInformation
MUST (name)
)
( 16 NAME 'dmtfDeviceStatisticsStructureRule2'
FORM dmtfDeviceStatisticalInformationNameForm2
SUP 1 2
)
( <oid-nf16> NAME 'dmtfDeviceStatisticalInformationNameForm2'
OC dmtfDeviceStatisticalInformation
MUST (creationClassName)
)
2.51 dmtfPhysicalStatisticalInformation
Statistical information associated with a physical element or one of
its subclasses. This class defines the attribute
physicalCreationClassName and reuses the attributes tag,
creationClassName, and name.
( <oid-at81> NAME 'physicalCreationClassName'
DESC 'The scoping Element's CreationClassName. May be used as an
RDN.'
SYNTAX string{256} SINGLE-VALUE
)
( <oid-oc51> NAME 'dmtfPhysicalStatisticalInformation'
DESC 'Statistical information associated with a PhysicalElement
or one of its subclasses.'
SUP dmtfStatisticalInformation
MUST (physicalCreationClassName $ tag $ creationClassName $ name)
)
Although physicalCreationClassName, and tag may be used as RDNs for
this class, the solution taken in this schema is to require that this
class follow the containment and name form rules below.
( 17 NAME 'dmtfPhysicalStatisticsStructureRule1'
FORM dmtfPhysicalStatisticalInformationNameForm1
SUP 19 20
)
( <oid-nf17> NAME 'dmtfPhysicalStatisticalInformationNameForm1'
OC dmtfPhysicalStatisticalInformation
MUST (name)
)
( 18 NAME 'dmtfPhysicalStatisticsStructureRule2'
FORM dmtfPhysicalStatisticalInformationNameForm2
SUP 19 20
)
( <oid-nf18> NAME 'dmtfPhysicalStatisticalInformationNameForm2'
OC dmtfPhysicalStatisticalInformation
MUST (creationClassName)
)
( 19 NAME 'dmtfPhysicalElementStructureRule1'
FORM dmtfPhysicalElementNameForm1
)
( <oid-nf19> NAME 'dmtfPhysicalElementNameForm1'
OC dmtfPhysicalElement
MUST (creationClassName)
)
( 20 NAME 'dmtfPhysicalElementStructureRule2'
FORM dmtfPhysicalElementNameForm2
)
( <oid-nf20> NAME 'dmtfPhysicalElementNameForm2'
OC dmtfPhysicalElement
MUST (tag)
)
3. DIT Content Rules
The following DIT Content Rules apply to objects in this schema.
These content rules reference not only auxiliary classes in this
draft but auxiliary classes from other DMTF CIM models [5, 6, 7, 8, 9].
( <oid-oc1> NAME 'dmtfManagedSystemElementContentRule'
DESC 'shows what auxiliary classes may go with the
dmtfManagedSystemElement class'
AUX (dmtfCollectedMSEsAuxClass $
dmtfProvidesServiceToElementAuxClass $
dmtfElementConfigurationAuxClass $
dmtfRedundancyComponentAuxClass $
dmtfElementSettingAuxClass $ dmtfDependencyAuxClass $
dmtfDependencyAuxClass $ dmtfComponentAuxClass $
dmtfComponentAuxClass $ dmtfSystemComponentAuxClass $
dmtfStatisticsAuxClass $ dmtfActsAsSpareAuxClass)
)
( <oid-oc2> NAME 'dmtfCollectionOfMSEsContentRule'
DESC 'shows what auxiliary classes may go with the
dmtfCollectionOfMSEs class'
AUX (dmtfCollectedMSEsAuxClass $
dmtfCollectedCollectionsAuxClass $
dmtfCollectionConfigurationAuxClass $
dmtfCollectionSettingAuxClass)
)
( <oid-oc5> NAME 'dmtfPhysicalElementContentRule'
DESC 'shows what auxiliary classes may go with the
dmtfPhysicalElement class'
AUX (dmtfRealizesAuxClass $ dmtfProductPhysicalElementsAuxClass $
dmtfFRUPhysicalElementsAuxClass $
dmtfDoorAccessToPhysicalElementAuxClass $
dmtfPhysicalElementLocationAuxClass $
dmtfElementCapacityAuxClass $
dmtfParticipatesInSetAuxClass $ dmtfContainerAuxClass $
dmtfElementsLinkedAuxClass)
)
( <oid-oc6> NAME 'dmtfLogicalElementContentRule'
DESC 'shows what auxiliary classes may go with the
dmtfLogicalElement class'
AUX (dmtfLogicalIdentityAuxClass)
)
( <oid-oc8> NAME 'dmtfConfigurationContentRule'
DESC 'shows what auxiliary classes may go with the
dmtfConfiguration class'
AUX (dmtfConfigurationComponentAuxClass $
dmtfElementConfigurationAuxClass $
dmtfCollectionConfigurationAuxClass $
dmtfSettingContextAuxClass $ dmtfDependencyContextAuxClass)
)
( <oid-oc12> NAME 'dmtfSettingContentRule'
DESC 'shows what auxiliary classes may go with the dmtfSetting
class'
AUX (dmtfElementSettingAuxClass $ dmtfDefaultSettingAuxClass $
dmtfSettingContextAuxClass $ dmtfCollectionSettingAuxClass)
)
( <oid-oc17> NAME 'dmtfSystemContentRule'
DESC 'shows what auxiliary classes may go with the dmtfSystem
class'
AUX (dmtfSystemComponentAuxClass)
)
( <oid-oc18> NAME 'dmtfComputerSystemContentRule'
DESC 'shows what auxiliary classes may go with the
dmtfComputerSystem class'
AUX (dmtfComputerSystemResourceAuxClass $
dmtfComponentCSAuxClass $ dmtfComponentCSAuxClass $
dmtfSystemPartitionAuxClass $ dmtfHostingCSAuxClass $
dmtfParticipatingCSAuxClass $
dmtfRunningOSAuxClass $
dmtfRoutersInBGPClusterAuxClass $ dmtfRoutersInASAuxClass $
dmtfInBGPPeerGroupAuxClass)
)
( <oid-oc19> NAME 'dmtfLogicalDeviceContentRule'
DESC 'shows what auxiliary classes may go with the
dmtfLogicalDevice class'
AUX (dmtfRealizesAuxClass $ dmtfDeviceConnectionAuxClass $
dmtfDeviceConnectionAuxClass $ dmtfAllocatedResourceAuxClass $
dmtfDeviceServiceImplementationAuxClass $
dmtfDeviceSAPImplementationAuxClass $
dmtfDeviceSoftwareAuxClass $ dmtfPortOnDeviceAuxClass $
dmtfAssociatedSensorAuxClass $
dmtfAssociatedCoolingAuxClass $ dmtfSuppliesPowerAuxClass $
dmtfAssociatedBatteryAuxClass $ dmtfControlledByAuxClass $
dmtfAssociatedAlarmAuxClass $
dmtfDoorAccessToDeviceAuxClass $
dmtfDeviceIdentityAuxClass)
)
( <oid-oc20> NAME 'dmtfServiceContentRule'
DESC 'shows what auxiliary classes may go with the dmtfService
class'
AUX (dmtfServiceAccessBySAPAuxClass $
dmtfProvidesServiceToElementAuxClass $
dmtfServiceServiceDependencyAuxClass $
dmtfServiceServiceDependencyAuxClass $
dmtfServiceSAPDependencyAuxClass $
dmtfServiceComponentAuxClass $
dmtfServiceComponentAuxClass $
dmtfDeviceServiceImplementationAuxClass $
dmtfSoftwareFeatureServiceImplementationAuxClass $
dmtfServiceComponentAuxClass $ dmtfServiceComponentAuxClass)
)
( <oid-oc21> NAME 'dmtfServiceAccessPointContentRule'
DESC 'shows what auxiliary classes may go with the
dmtfServiceAccessPoint class'
AUX (dmtfServiceAccessBySAPAuxClass $
dmtfServiceSAPDependencyAuxClass $
dmtfSAPSAPDependencyAuxClass $
dmtfSAPSAPDependencyAuxClass $
dmtfDeviceSAPImplementationAuxClass $
dmtfSoftwareFeatureSAPImplementationAuxClass $
dmtfBindsToAuxClass)
)
( <oid-oc33> NAME 'dmtfProductContentRule'
DESC 'shows what auxiliary classes may go with the dmtfProduct
class'
AUX (dmtfProductParentChildAuxClass $
dmtfProductParentChildAuxClass $
dmtfCompatibleProductAuxClass $
dmtfCompatibleProductAuxClass $
dmtfProductProductDependencyAuxClass $
dmtfProductProductDependencyAuxClass $
dmtfProductSupportAuxClass $ dmtfProductFRUAuxClass $
dmtfProductPhysicalElementsAuxClass $
dmtfFRUIncludesProductAuxClass)
)
( <oid-oc37> NAME 'dmtfSupportAccessContentRule'
DESC 'shows what auxiliary classes may go with the
dmtfSupportAccess class'
AUX (dmtfProductSupportAuxClass)
)
( <oid-oc39> NAME 'dmtfFRUContentRule'
DESC 'shows what auxiliary classes may go with the dmtfFRU class'
AUX (dmtfProductFRUAuxClass $ dmtfFRUPhysicalElementsAuxClass $
dmtfFRUIncludesProductAuxClass)
)
( <oid-oc44> NAME 'dmtfStatisticalInformationContentRule'
DESC 'shows what auxiliary classes may go with the
dmtfStatisticalInformation class'
AUX (dmtfStatisticsAuxClass $ dmtfRelatedStatisticsAuxClass $
dmtfRelatedStatisticsAuxClass)
) )
4. References 4. References
Request For Comments (RFC) and Internet Draft documents are available Request For Comments (RFC) and Internet Draft documents are available
from numerous mirror sites. from numerous mirror sites.
[1] M. Wahl, T. Howes, S. Kille, "Lightweight Directory Access [1] M. Wahl, T. Howes, S. Kille, "Lightweight Directory
Protocol (v3)," RFC 2251, Decemeber 1997. Access Protocol (v3)," RFC 2251, December 1997.
[2] M. Wahl, A. Coulbeck, T. Howes, S. Kille, "Lightweight
Directory Access Protocol (v3): Attribute Synatx Defini-
tions," RFC 2252, December 1997.
[3] Ryan Moats, Gerald Maziarski, John Strassner, "Extensible
Match Rule to Dereference Pointers", Internet Draft (work in
progress), June 1999.
[4] DMTF, "CIM Core Model, v2.2".
[5] Ryan Moats, Gerald Maziarski, John Strassner, "LDAP Schema [2] M. Wahl, A. Coulbeck, T. Howes, S. Kille, "Light-
for the DMTF Application CIM Model", October 1999. weight Directory Access Protocol (v3): Attribute
Syntax Definitions," RFC 2252, December 1997.
[6] Ryan Moats, Gerald Maziarski, John Strassner, "LDAP Schema [3] Ryan Moats, Gerald Maziarski, John Strassner,
for the DMTF Device CIM Model", September 1999. "Extensible Match Rule to Dereference Pointers",
Internet Draft (work in progress), June 1999.
[7] Ryan Moats, Gerald Maziarski, John Strassner, "LDAP Schema [4] CIM, "CIM Core Model, v2.2".
for the DMTF Network CIM Model", October 1999.
[8] Ryan Moats, Gerald Maziarski, John Strassner, "LDAP Schema 5. Acknowledgement
for the DMTF System CIM Model", October 1999.
[9] Ryan Moats, Gerald Maziarski, John Strassner, "LDAP Schema This work is a product of the DMTF LDAP Mapping Working Group and has
for the DMTF Physical CIM Model", October 1999. benefited from many comments and discussions during this groups meet-
ings.
5. Author's Addresses 6. Editor's Address
Ryan Moats Jerry Maziarski John Strassner Ryan Moats
15621 Drexel Circle Room C3-3Z01 Cisco Systems, Bldg 1 15621 Drexel Circle
Omaha, NE 68135 200 S. Laurel Ave. 170 West Tasman Drive Omaha, NE 68135
USA Middletown, NJ 07748 San Jose, CA 95134 USA
E-mail: jayhawk@att.com USA E-mail: E-mail: jayhawk@att.com
johns@cisco.com
E-mail: gfm@qsun.att.com
 End of changes. 252 change blocks. 
1218 lines changed or deleted 1180 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/