< draft-moats-dmtf-physical-ldap-00.txt   draft-moats-dmtf-physical-ldap-01.txt >
Internet-Draft Ryan Moats Internet-Draft Ryan Moats
draft-moats-dmtf-physical-ldap-00.txt Gerald Maziarski draft-moats-dmtf-physical-ldap-01.txt Gerald Maziarski
Expires in six months AT&T Expires in six months AT&T
John Strassner John Strassner
cisco Systems cisco Systems
October 1999 December 1999
LDAP Schema for the DMTF Physical CIM Model LDAP Schema for the DMTF Physical CIM v2.2 Model
Filename: draft-moats-dmtf-physical-ldap-00.txt Filename: draft-moats-dmtf-physical-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 43 skipping to change at page 1, line 43
This draft presents a LDAP schema for the DMTF CIM Physical model This draft presents a LDAP schema for the DMTF CIM Physical model
version 2.2 [4]. version 2.2 [4].
1. Introduction 1. Introduction
This draft presents a LDAPv3 [1,2] schema for the DMTF CIM Physical This draft presents a LDAPv3 [1,2] schema for the DMTF CIM Physical
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. Where auxiliary classes are used,
name form and DIT content rules are specified. name form and DIT content rules are specified.
2. Class Definitions This document is not a product of the DMTF, and represents the view
of the authors.
INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
1999
2. LDAP Mapping Considerations
There are several special considerations in mapping the physical
model from CIM to LDAP. They are discussed in this section.
2.1 Modifications to cimAssociationInstance
The core mapping [5] defined cimAssociationInstance as a helper
class. To support the auxiliary classes, the following classes
should be added to cimAssociationInstance's content rule:
cim22PhysicalElementLocationAuxClass
cim22ElementCapacityAuxClass
cim22ParticipatesInSetAuxClass
cim22ContainerAuxClass
cim22ChassisInRackAuxClass
cim22PackageInChassisAuxClass
cim22DockedAuxClass
cim22CardOnCardAuxClass
cim22DeviceServicesLocationAuxClass
cim22PackagedComponentAuxClass
cim22MemoryOnCardAuxClass
cim22MemoryWithMediaAuxClass
cim22PhysicalMediaInLocationAuxClass
cim22ElementsLinkedAuxClass
cim22ConnectedToAuxClass
cim22SlotInSlotAuxClass
cim22AdjacentSlotsAuxClass
cim22PackageInConnectorAuxClass
cim22PackageInSlotAuxClass
cim22CardInSlotAuxClass
cim22LinkHasConnectorAuxClass
cim22ConnectorOnPackageAuxClass
cim22AdapterActiveConnectionAuxClass
cim22ComputerSystemPackageAuxClass
cim22LibraryPackageAuxClass
cim22PackageCoolingAuxClass
cim22PackageTempSensorAuxClass
cim22PackageAlarmAuxClass
Also, the following structure rules defined here need to be added to
the structure rule for cimAssociationInstance: <sr12>, <sr13>,
<sr14>, <sr15>, <sr16>, <sr17>, <sr18>, <sr19>, and <sr20>.
2.2 cimServicePhilosophyInstance
The class cimPhysicalFrame defines two linked indexed arrays:
ServicePhilosophy and ServiceDescription. In the LDAP mapping, these
INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
1999
are replaced with separate instances of cimServicePhilosophyInstance,
DIT contained by cimPhysicalFrame.
( <oid-at98> NAME 'cimServicePhilosophy'
DESC 'ServicePhilosophy is an enumerated, integer value that
indicates whether the Frame is serviced from the top
(value=2), front (3), back (4) or side (5), whether it has
sliding trays (6) or removable sides (7), and/or whether
the Frame is moveable (8), for example, having rollers.'
SYNTAX integer SINGLE-VALUE
)
( <oid-at99> NAME 'cimServiceDescriptions'n
DESC 'A free-form strings providing more detailed explanations
for this entries.
SYNTAX string SINGLE-VALUE
)
( <oid-oc92> NAME 'cimServicePhilosophyInstance'
DESC 'helper class to tie ServicePhilosophy and
ServiceDescriptions in PhysicalFrame together'
SUP top
MUST (arrayIndex)
MAY (cimServicePhilosophy $ cimServiceDescription)
)
( <oid-nf21> NAME 'cimServicePhilosophyInstanceNameForm'
OC cimServicePhilosophyInstance
MUST (arrayIndex)
)
( <sr21> NAME 'cimServicePhilosophyInstanceStructureRule'
FORM cimServicePhilosophyInstanceNameForm
SUP <sr17>
)
2.3 cimChassisTypeInstance
The class cimChassis defines two linked indexed arrays: ChassisTypes
and TypeDescriptions. In the LDAP mapping, these are replaced with
separate instances of cimChassisTypeInstance, DIT contained by
cimChassis.
( <oid-at111> NAME 'cimChassisTypes'
DESC 'An enumerated, integer value indicating the type of
Chassis.'
SYNTAX integer SINGLE-VALUE
)
INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
1999
( <oid-at112> NAME 'cimTypeDescriptions'
DESC 'A free-form strings providing more information on the
ChassisTypes array entries.'
SYNTAX string SINGLE-VALUE
)
( <oid-oc93> NAME 'cimChassisTypeInstance'
DESC 'helper class to tie ChassisType and
TypeDescriptions in Chassis together'
SUP top
MUST (arrayIndex)
MAY (cimChassisType $ cimTypeDescription)
)
( <oid-nf22> NAME 'cimChassisTypeInstanceNameForm'
OC cimChassisTypeInstance
MUST (arrayIndex)
)
( <sr22> NAME 'cimChassisTypeInstanceStructureRule'
FORM cimChassisTypeInstanceNameForm
SUP <sr18>
)
2.4 cimMediaTypesSupportedInstance
The class cimStorageMediaLocation defines two linked indexed arrays:
MediaTypesSupported and MediaSizesSupported. In the LDAP mapping,
these are replaced with separate instances of
cimMediaTypeSupportedInstance, DIT contained by
cimStorageMediaLocation.
( <oid-at125> NAME 'cimMediaTypesSupported'
DESC 'Certain StorageMediaLocations may only be able to accept a
limited set of PhysicalMedia MediaTypes. This property defines
the types of Media that are acceptable for placement in the
Location.
SYNTAX integer SINGLE-VALUE
)
( <oid-at126> NAME 'cimMediaSizesSupported'
DESC 'The size (in inches) of the particular MediaTypes that may
be placed in the Location.'
SUP cim22Float32 SINGLE-VALUE
)
( <oid-oc94> NAME 'cimMediaTypesSupportedInstance'
DESC 'helper class to tie MediaTypesSupported and
INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
1999
MediaSizesSupported in StorageMediaLocation together'
SUP top
MUST (arrayIndex)
MAY (cimMediaTypesSupported $ cimMediaSizesSupported)
)
( <oid-nf23> NAME 'cimMediaTypesSupportedInstanceNameForm'
OC cimMediaTypesSupportedInstance
MUST (arrayIndex)
)
( <sr23> NAME 'cimMediaTypesSupportedInstanceStructureRule'
FORM cimMediaTypesSupportedInstanceNameForm
SUP <sr19>
)
2.5 cimPhysicalLabelsInstance
The class cimPhysicalMedia defines three linked indexed arrays:
PhysicalLabels, LabelStates, and LabelFormats. In the LDAP mapping,
these are replaced with separate instances of
cimPhysicalLabelsInstance, DIT contained by
cimPhysicalMedia.
( <oid-at143> NAME 'cimPhysicalLabels'
DESC '"labels" on the PhysicalMedia. The format of the labels and
their state (readable, unreadable, upside-down) are
indicated in LabelFormats and LabelStates properties.'
SYNTAX string SINGLE-VALUE
)
( <oid-at144> NAME 'cimLabelStates'
DESC 'An enumerated integer describing the state of a label on a
PhysicalMedia. The Label is listed in the PhysicalLabels
property.'
SYNTAX integer SINGLE-VALUE
)
( <oid-at145> NAME 'cimLabelFormats'
DESC 'An enumerated integer describing the format of a label on
a PhysicalMedia. The Labels is listed in the PhysicalLabels
property.'
SYNTAX integer SINGLE-VALUE
)
( <oid-oc95> NAME 'cimPhysicalLabelsInstance'
DESC 'helper class to tie PhysicalLabels, LabelStates, and
LabelFormats in PhsyicalMedia together'
INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
1999
SUP top
MUST (arrayIndex)
MAY (cimPhysicalLabels $ cimLabelStates $ cimLabelFormats)
)
( <oid-nf24> NAME 'cimPhysicalLabelsInstanceNameForm'
OC cimPhysicalLabelsInstance
MUST (arrayIndex)
)
( <sr24> NAME 'cimPhysicalLabelsInstanceStructureRule'
FORM cimPhysicalLabelsInstanceNameForm
SUP <sr20>
)
2.6 Floating point attributes: cimFloat32 and cimFloat64
Several attributes in this schema inherit from the attributes
cimFloat32 and cimFloat64, defined in [6]. Interested readers are
directed there for information about these attribute definition.
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.
This approach minimizes the number of DN pointers stored in the This approach minimizes the number of DN pointers stored in the
schema, but some pointer dereferencing is necessary. While not schema, but some pointer dereferencing is necessary. While not
explicitly stated in the definitions below, we assume that all explicitly stated in the definitions below, we assume that all
attributes with DN support the matching rule defined in [3]. attributes with DN support the matching rule defined in [3].
Attribute names for DN pointers also follow the convention that a Attribute names for DN pointers also follow the convention that a
single pointer's name ends in "Ref", while an array of pointers' name single pointer's name ends in "Ref", while an array of pointers' name
ends in "Refs". ends in "Refs".
Note: all OIDs are place holders, and OIDs in definitions have been Note: all attribute, object class, and name form OIDs are place
replaced by names for clarity. holders, and syntax OIDs in definitions have been replaced by names
for clarity.
There are some classes that aren't included in this mapping: Since There are some classes that aren't included in this mapping: Since
MediaTransferDevice isn't included in the device model, MediaTransferDevice isn't included in the device model,
DeviceServiceLocation isn't included here. MediaPhysicalStatInfo DeviceServiceLocation isn't included here. MediaPhysicalStatInfo
isn't included here because it is filled with nothing but counters. isn't included here because it is filled with nothing but counters.
Without StorageExtents, the associations RealizesExtent, Without StorageExtents, the associations RealizesExtent,
RealizesPExtent, RealizesDiskPartition, RealizesAggregatePExtent, and RealizesPExtent, RealizesDiskPartition, RealizesAggregatePExtent, and
RealizesTapePartition do not make sense to include here. Finally, RealizesTapePartition do not make sense to include here. Finally,
the PackageTempSensor association is not included because there are the PackageTempSensor association is not included because there are
INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
1999
no TemperatureSensors in the schema. no TemperatureSensors in the schema.
2.1 dmtfLocation 3.1 cim22Location
Locations are the position and address of a PhysicalElement. This Locations are the position and address of a PhysicalElement.
class reuses the name attribute and defines the attributes
physicalPosition and address.
( <oid-at462> NAME 'physicalPosition' ( <oid-at76> NAME 'cimPhysicalPosition'
DESC 'Position is a free-form string indicating the placement of DESC 'Position is a free-form string indicating the placement of
a PhysicalElement. It can specify slot information on a PhysicalElement. It can specify slot information on a
HostingBoard, mounting site in a Cabinet, or latitude and HostingBoard, mounting site in a Cabinet, or latitude and
longitude information, for example, from a GPS. May be used longitude information, for example, from a GPS. It is part
as an RDN.' of the key of the Location object.'
SYNTAX string{256} SINGLE-VALUE SYNTAX string{256} SINGLE-VALUE
) )
( <oid-at463> NAME 'address' ( <oid-at77> NAME 'cimAddress'
DESC 'Address is a free-form string indicating a street, building DESC 'Address is a free-form string indicating a street, building
or other type of address for the PhysicalElement's Location.' or other type of address for the PhysicalElement's
Location.'
SYNTAX string{1024} SINGLE-VALUE SYNTAX string{1024} SINGLE-VALUE
) )
( <oid-oc185> NAME 'dmtfLocation' ( <oid-oc46> NAME 'cim22Location'
DESC 'specifies the position and address of a PhysicalElement.' DESC 'The Location class specifies the position and address of a
PhysicalElement.'
SUP top SUP top
MUST (name $ physicalPosition $ address) MUST (orderedCimModelPath $ cimName $ cimPhysicalPosition)
MAY (cimAddress)
)
( <oid-nf12> NAME 'cim22LocationNameForm'
OC cim22Location
MUST (orderedCimModelPath)
) )
2.2 dmtfPhysicalElementLocationAuxClass ( <sr12> NAME 'cim22LocationStructureRule'
FORM cim22LocationNameForm
)
This class associates a physical element with a dmtfLocation object. The following content rule specifies the auxiliary classes that may
It defines the attributes dmtfPhysicalElementRefs and be attached to cim22Location.
dmtfLocationRef.
( <oid-at464> NAME 'dmtfPhysicalElementRefs' ( <oid-oc46> NAME 'cim22LocationContentRule'
DESC 'The PhysicalElement whose Location is specified. May be DESC 'The auxiliary classes that may be attached to cim22Location'
used as an RDN.' AUX (cim22PhysicalElementLocationAuxClass)
SYNTAX DN
) )
( <oid-at465> NAME 'dmtfLocationRef' INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
DESC 'The Physical Element's Location. May be used as an RDN.' 1999
SYNTAX DN SINGLE-VALUE
3.2 cim22PhysicalElementLocationAuxClass
This class associates a physical element with a cim22Location object.
( <oid-at78> NAME 'cimPhysicalLocationRef'
DESC 'The PhysicalElement's Location.'
SYNTAX DN
) )
( <oid-oc186> NAME 'dmtfPhysicalElementLocationAuxClass' ( <oid-oc47> NAME 'cim22PhysicalElementLocationAuxClass'
DESC 'associates a PhysicalElement with a Location object for DESC 'PhysicalElementLocation associates a PhysicalElement with a
inventory or replacement purposes.' Location object for inventory or replacement
purposes. Attribute cimElementRef points to
cim22PhysicalElement and attribute cimPhysicalLocationRef
points
to cim22Location. '
SUP top AUXILIARY SUP top AUXILIARY
MUST (dmtfPhysicalElementRefs $ dmtfLocationRef) MAY (cimElementRef $ cimPhysicalLocationRef)
) )
2.3 dmtfPhysicalCapacity 3.3 cim22PhysicalCapacity
This class describes a physical element's requirements. It reuses This class describes a physical element's requirements.
the attributes name, caption, and description.
( <oid-oc187> NAME 'dmtfPhysicalCapacity' ( <oid-oc48> NAME 'cim22PhysicalCapacity'
DESC 'abstract class describing a PhysicalElement's DESC 'PhysicalCapacity is an abstract class describing a
minimum/maximum requirements and ability to support PhysicalElement's minimum/maximum requirements and
different types of hardware.' ability to support different types of hardware. For
example, minimum and maximum memory requirements can be
modeled as a subclass of cim22PhysicalCapacity.'
SUP top ABSTRACT SUP top ABSTRACT
MUST (name $ caption $ description) MAY (cimName $ cimCaption $ cimDescription)
) )
2.4 dmtfElementCapacityAuxClass 3.4 cim22ElementCapacityAuxClass
This class associates a dmtfPhysicalCapacity object with one or more This class associates a cim22PhysicalCapacity object with one or more
dmtfPhysicalElements. It defines the attributes cim22PhysicalElements.
dmtfPhysicalCapacityRefs and dmtfPhysicalElementRefs.
( <oid-at466> NAME 'dmtfPhysicalCapacityRefs' ( <oid-at79> NAME 'cimCapacityRef'
DESC 'PhysicalCapacity describes the minimum and maximum DESC 'PhysicalCapacity describes the minimum and maximum
requirements, and ability to support different types of requirements, and ability to support different types of
hardware for a PhysicalElement. May be used as an RDN.' hardware for a PhysicalElement.'
SYNTAX DN SYNTAX DN
) )
( <oid-at467> NAME 'dmtfPhysicalElementRefs' ( <oid-oc49> NAME 'cim22ElementCapacityAuxClass'
DESC 'The PhysicalElement being described. May be used as an DESC 'ElementCapacity associates a PhysicalCapacity object with
RDN.' one or more PhysicalElements. It serves to associate a
SYNTAX DN
)
( <oid-oc188> NAME 'dmtfElementCapacityAuxClass' INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
DESC 'associates a PhysicalCapacity object with one or more 1999
PhysicalElements.'
description of min/max hardware requirements or
capabilities (stored as a kind of PhysicalCapacity), with
the PhysicalElements being described. Attribute
cimCapacityRef points to cim22PhysicalCapacity. Attribute
cimElementRef points to cim22PhysicalElement.'
SUP top AUXILIARY SUP top AUXILIARY
MUST (dmtfPhysicalCapacityRefs $ dmtfPhysicalElementRefs) MAY (cimCapacityRef $ cimElementRef)
) )
2.5 dmtfMemoryCapacity 3.5 cim22MemoryCapacity
Physical elements are limited in what memory can be installed. Physical elements are limited in what memory can be installed.
Instances of this class store information on what memory is currently Instances of this class store information on what memory is currently
installed. It defines the attributes memoryType, installed.
minimumMemoryCapacity, and maximumMemoryCapacity.
( <oid-at468> NAME 'memoryType' ( <oid-at80> NAME 'cimMemoryType'
DESC 'The type of memory. This is a part of the object DESC 'The type of memory. This is a part of the object
key. Values correspond to the list of possible memory types key. Values correspond to the list of possible memory types
in the PhysicalMemory class. May be used as an RDN. in the PhysicalMemory class.'
Allowed values are: "Unknown", "Other", "DRAM",
"Synchronous DRAM", "Cache DRAM", "EDO", "EDRAM", "VRAM",
"SRAM", "RAM", "ROM", "Flash", "EEPROM", "FEPROM", "EPROM",
"CDRAM", "3DRAM", "SDRAM", "SGRAM", "RDRAM".'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at469> NAME 'minimumMemoryCapacity' ( <oid-at81> NAME 'cimMinimumMemoryCapacity'
DESC 'Minimum amount of memory, in Kbytes, that is needed for the DESC 'Minimum amount of memory, in Kbytes, that is needed for
associated PhysicalElement to operate correctly.' the associated PhysicalElement to operate correctly.
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at470> NAME 'maximumMemoryCapacity' ( <oid-at82> NAME 'cimMaximumMemoryCapacity'
DESC 'Maximum amount of memory, in Kbytes, that can be supported DESC 'Maximum amount of memory, in Kbytes, that can be supported
by the associated PhysicalElement.' by the associated PhysicalElement.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-oc189> NAME 'dmtfMemoryCapacity' ( <oid-oc50> NAME 'cim22MemoryCapacity'
DESC 'describes the type of Memory that can be installed on a DESC 'MemoryCapacity describes the type of Memory that can be
PhysicalElement and its minimum/maximum configurations.' installed on a PhysicalElement and its minimum/maximum
SUP dmtfPhysicalCapacity configurations. Information on what memory is currently
MUST (memoryType $ minimumMemoryCapacity $ maximumMemoryCapacity) "installed", versus an Element's min/max requirements, is
located in instances of the PhysicalMemory class.'
SUP cim22PhysicalCapacity
MUST (orderedCimModelPath $ cimMemoryType)
MAY (cimMinimumMemoryCapacity $ cimMaximumMemoryCapacity)
) )
2.6 dmtfConfigurationCapacity ( <oid-nf13> NAME 'cim22MemoryCapacityNameForm'
OC cim22MemoryCapacity
MUST (orderedCimModelPath)
INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
1999
)
( <sr13> NAME 'cim22MemoryCapacityStructureRule'
FORM cim22MemoryCapacityNameForm
)
3.6 cim22ConfigurationCapacity
Capacity includes the number of power supplies, fans, disk drives, Capacity includes the number of power supplies, fans, disk drives,
etc. that can be connected to or placed on/into a physical element etc. that can be connected to or placed on/into a physical element
(and the number that must be connected/added/removed at a time). (and the number that must be connected/added/removed at a time).
DmtfElementCapacityAuxClass indentifies the physical element whose cim22ElementCapacityAuxClass identifies the physical element whose
configuration is described. The attribute objectType identifies the configuration is described.
object (ie, the power supply or fan) whose capacities are described.
This class does NOT represent the tradeoffs required of one resource This class does NOT represent the tradeoffs required of one resource
for another. It simply represents capacities. For a StorageLibrary, for another. It simply represents capacities. For a StorageLibrary,
there are only 2 valid configurations - 9 TapeDrives with 88 Slots, there are only 2 valid configurations - 9 TapeDrives with 88 Slots,
or 3 TapeDrives with 264 Slots. it only conveys that 'up to' 9 Drives or 3 TapeDrives with 264 Slots. it only conveys that 'up to' 9 Drives
and 'up to' 264 slots are available and supported. it reuses the and 'up to' 264 slots are available and supported.
attribute otherTypeDescription and defines objectType,
minimumCapacity, maximumCapacity, and increment.
( <oid-at471> NAME 'objectType' ( <oid-at83> NAME 'cimObjectType'
DESC 'The type of object (power supply, fan, disk drive, ..) DESC 'The type of object (power supply, fan, disk drive, ...)
whose capacities are shown. May be used as an RDN.' whose capacities are indicated. This information is part of
the class' key.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at472> NAME 'minimumCapacity' ( <oid-at84> NAME 'cimOtherTypeDescription'
DESC 'A string describing the object type - used when the
ObjectType property is set to 0
("Other"). OtherTypeDescription should be set to NULL when
ObjectType is any value other than 0.'
SYNTAX string{64} SINGLE-VALUE
)
( <oid-at85> NAME 'cimMinimumCapacity'
DESC 'Minimum number of Elements of type, ObjectType, that must DESC 'Minimum number of Elements of type, ObjectType, that must
be installed.' be installed.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at473> NAME 'maximumCapacity' ( <oid-at86> NAME 'cimMaximumCapacity'
DESC 'Maximum number of Elements of type, ObjectType, that may be DESC 'Maximum number of Elements of type, ObjectType, that may be
installed.' installed.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at474> NAME 'increment' ( <oid-at87> NAME 'cimIncrement'
INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
1999
DESC 'Increment in which Elements must be added or removed.' DESC 'Increment in which Elements must be added or removed.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-oc190> NAME 'dmtfConfigurationCapacity' ( <oid-oc51> NAME 'cim22ConfigurationCapacity'
DESC 'ConfigurationCapacity provides information on the minimum DESC 'ConfigurationCapacity provides information on the minimum
and maximum numbers of power supplies, fans, disk drives, and maximum numbers of power supplies, fans, disk drives,
etc. that can be connected to or placed on/into a etc. that can be connected to or placed on/into a
PhysicalElement (and the number that must be PhysicalElement (and the number that must be
connected/added/removed at a time).' connected/added/removed at a time). The PhysicalElement
SUP dmtfPhysicalCapacity whose configuration is described is identified using the
MUST (objectType $ otherTypeDescription $ minimumCapacity $ ElementCapacity association, inherited from
maximumCapacity $ increment) PhysicalCapacity. The object whose capacities are indicated
(ie, the power supply or fan) is identified in the
ObjectType property of this class. Since the same min/max
configurations can apply to multiple instances, this class
is not defined as "weak". Examples of the use of the
ConfigurationCapacity class are to describe that a "control
unit" Chassis may be connected to (at most) 4 other I/O
chassis, or to describe what a StorageLibrary's cabinet may
contain. Continuing the latter example, a particular
StorageLibrary's cabinet might hold a minimum of 3 and a
maximum of 9 TapeDrives, and a minimum of 88 and a maximum
of 264 StorageMediaLocations ("Slots"). This information
would be described in two instances of
ConfigurationCapacity, both associated to the
StorageLibrary's PhysicalPackage. This class does NOT
represent the tradeoffs that are likely to be required of
one resource for another. It simply represents
capacities. In the case of the StorageLibrary, there may be
only 2 valid configurations - 9 TapeDrives with 88 Slots,
or 3 TapeDrives with 264 Slots. This class only conveys
that "up to" 9 Drives and "up to" 264 slots may be
available and are supported.'
SUP cim22PhysicalCapacity
MUST (orderedCimModelPath $ cimObjectType)
MAY (cimOtherTypeDescription $ cimMinimumCapacity $
cimMaximumCapacity $ cimIncrement)
) )
2.7 dmtfReplacementSet ( <oid-nf14> NAME 'cim22ConfigurationCapacityNameForm'
OC cim22ConfigurationCapacity
MUST (orderedCimModelPath)
)
( <sr14> NAME 'cim22ConfigurationCapacityStructureRule'
FORM cim22ConfigurationCapacityNameForm
)
INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
1999
3.7 cim22ReplacementSet
A replacement set is a group of physical elements that must be A replacement set is a group of physical elements that must be
replaced or FRUed together. For example, when replacing a memory replaced or FRUed together. For example, when replacing a memory
card, the component memory chips could be removed and replaced as card, the component memory chips could be removed and replaced as
well. It reuses the attributes name and description. well.
( <oid-oc191> NAME 'dmtfReplacementSet' ( <oid-oc52> NAME 'cim22ReplacementSet'
DESC 'The ReplacementSet class aggregates PhysicalElements that DESC 'The ReplacementSet class aggregates PhysicalElements that
must be "replaced" or "FRUed" together.' must be "replaced" or "FRUed" together. For example, when
replacing a memory card, the component memory chips could
be removed and replaced as well. Or, a set of memory chips
may be specified to be replaced or upgraded together using
this association.'
SUP top SUP top
MUST (name $ description) MUST (cimName $ orderedCimModelPath)
MAY (cimDescription)
) )
2.8 dmtfParticipatesInSetAuxClass ( <oid-nf15> NAME 'cim22ReplacementSetNameForm'
OC cim22ReplacementSet
This class shows which physical elements should be replaced together. MUST (orderedCimModelPath)
It defines the attributes dmtfReplacementSetRefs and )
dmtfPhysicalElementRefs.
( <oid-at475> NAME 'dmtfReplacementSetRefs' ( <sr15> NAME 'cim22ReplacementSetStructureRule'
DESC 'The ReplacementSet.' FORM cim22ReplacementSetNameForm
SYNTAX DN
) )
( <oid-at476> NAME 'dmtfPhysicalElementRefs' The following content rule specifies the auxiliary classes that may
DESC 'The PhysicalElement that should be replaced with other be attached to cim22ReplacementSet.
Elements, as a Set.'
SYNTAX DN ( <oid-oc52> NAME 'cim22ReplacementSetContentRule'
DESC 'The auxiliary classes that may be attached to
cim22ReplacementSet'
AUX (cim22ParticipatesInSetAuxClass)
) )
( <oid-oc192> NAME 'dmtfParticipatesInSetAuxClass' 3.8 cim22ParticipatesInSetAuxClass
DESC 'shows which PhysicalElements should be replaced
together.' This class shows which physical elements should be replaced together.
( <oid-oc53> NAME 'cim22ParticipatesInSetAuxClass'
DESC 'ParticipatesInSet indicates which PhysicalElements should
be replaced together. Attribute cimSetRef points to
cim22ReplacementSet and attribute cimElementRef points to
cim22PhysicalElement.'
SUP top AUXILIARY SUP top AUXILIARY
MUST (dmtfReplacementSetRefs $ dmtfPhysicalElementRefs) MAY (cimSetRef $ cimElementRef)
INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
1999
) )
2.9 dmtfPhysicalPackage 3.9 cim22PhysicalPackage
A physical package contains or hosts components. Examples are a rack A physical package contains or hosts components. Examples are a rack
enclosure or an adapter Card. enclosure or an adapter Card.
( <oid-at477> NAME 'removable' ( <oid-at89> NAME 'cimRemovable'
DESC 'An object is Removable if it is designed to be taken in and DESC 'A PhysicalPackage is Removable if it is designed to be
out of the physical container in which it is normally taken in and out of the physical container in which it is
found, without impairing the function of the overall normally found, without impairing the function of the
packaging. A Component can still be Removable if power must overall packaging. A Package can still be Removable if
be "off" to perform the removal. If power can be power must be "off" in order to perform the removal. If
"on" and the Component removed, then the Element is both power can be "on" and the Package removed, then the Element
Removable and HotSwappable. For example, an upgradeable is both Removable and HotSwappable. For example, an extra
Processor chip is Removable.' battery in a laptop is Removable, as is a disk drive
Package inserted using SCA connectors. However, the latter
is also HotSwappable. A laptop's display is not Removable,
nor is a non-redundant power supply. Removing these
components would impact the function of the overall
packaging or is impossible due to the tight integration of
the Package.'
SYNTAX boolean SINGLE-VALUE SYNTAX boolean SINGLE-VALUE
) )
( <oid-at478> NAME 'replaceable' ( <oid-at90> NAME 'cimReplaceable'
DESC 'An object is Replaceable if it is possible to replace (FRU DESC 'A PhysicalPackage is Replaceable if it is possible to
or upgrade) the Element with a physically different replace (FRU or upgrade) the Element with a physically
one. For example, some ComputerSystems allow the main different one. For example, some ComputerSystems allow the
Processor chip to be upgraded to one of a higher clock main Processor chip to be upgraded to one of a higher clock
rating. Here, the Processor is said to be rating. In this case, the Processor is said to be
Replaceable. All Removable Components are inherently Replaceable. Another example is a power supply Package
Replaceable.' mounted on sliding rails. All Removable packages are
inherently Replaceable.'
SYNTAX boolean SINGLE-VALUE SYNTAX boolean SINGLE-VALUE
) )
( <oid-at479> NAME 'hotSwappable' ( <oid-at91> NAME 'cimHotSwappable'
DESC 'An object is HotSwappable if it is possible to replace the DESC 'A PhysicalPackage is HotSwappable if it is possible to
Element with a physically different but equivalent one replace the Element with a physically different but
while the containing Package is "on". For example, a fan equivalent one while the containing Package has power
Component may be designed to be HotSwappable. All applied to it (ie, is "on"). For example, a disk drive
HotSwappable Components are inherently Removable and Package inserted using SCA connectors is both Removable and
Replaceable.' HotSwappable. All HotSwappable packages are inherently
Removable and Replaceable.'
SYNTAX boolean SINGLE-VALUE SYNTAX boolean SINGLE-VALUE
) )
( <oid-at480> NAME 'height' INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
DESC 'The height of the object.' 1999
SYNTAX binary SINGLE-VALUE
( <oid-at92> NAME 'cimHeight'
DESC 'The height of the PhysicalPackage in inches.'
SUP CimFloat32 SINGLE-VALUE
) )
( <oid-at481> NAME 'depth' ( <oid-at93> NAME 'cimDepth'
DESC 'The depth of the object.' DESC 'The depth of the PhysicalPackage in inches.'
SYNTAX binary SINGLE-VALUE SUP CimFloat32 SINGLE-VALUE
) )
( <oid-at482> NAME 'width' ( <oid-at94> NAME 'cimWidth'
DESC 'The width of the object.' DESC 'The width of the PhysicalPackage in inches.'
SYNTAX binary SINGLE-VALUE SUp CimFloat32 SINGLE-VALUE
) )
( <oid-at483> NAME 'weight' ( <oid-at95> NAME 'cimWeight'
DESC 'The weight of the object.' DESC 'The weight of the PhysicalPackage in pounds.'
SYNTAX binary SINGLE-VALUE SUP CimFloat32 SINGLE-VALUE
) )
( <oid-oc193> NAME 'dmtfPhysicalPackage' ( <oid-oc54> NAME 'cim22PhysicalPackage'
DESC 'The PhysicalPackage class represents PhysicalElements that DESC 'The PhysicalPackage class represents PhysicalElements that
contain or host other components.' contain or host other components. Examples are a Rack
SUP dmtfPhysicalElement enclosure or an adapter Card.'
MUST (removable $ replaceable $ hotSwappable $ height $ depth $ SUP cim22PhysicalElement
width $ weight) MAY (cimRemovable $ cimReplaceable $ cimHotSwappable $
cimHeight $ cimDepth $ cimWidth $ cimWeight)
) )
2.10 dmtfContainerAuxClass ( <oid-nf16> NAME 'cim22PhysicalPackageNameForm'
OC cim22PhysicalPackage
MUST (orderedCimModelPath)
)
This class represents the relationship between a contained and a ( <sr16> NAME 'cim22PhysicalPackageStructureRule'
containing PhysicalElement. In it, groupComponentRef must point to a FORM cim22PhysicalPackageNameForm
dmtfPhysicalPackageObject and partComponentRefs must point to a )
dmtfPhysicalElementObject. Further, it defines the attribute
locationWithinContainer.
( <oid-at484> NAME 'groupComponentRef' The following content rule specifies the auxiliary classes that may
DESC 'The PhysicalPackage that contains other PhysicalElements, be attached to cim22PhysicalPackage.
including other Packages.'
SYNTAX DN SINGLE-VALUE ( <oid-oc54> NAME 'cim22PhysicalPackageContentRule'
DESC 'The auxiliary classes that may be attached to
cim22PhysicalPackage'
AUX (cim22ContainerAuxClass $ cim22PackageInChassisAuxClass $
cim22PackagedComponentAuxClass $
cim22PackageInConnectorAuxClass $
cim22PackageInSlotAuxClass $ cim22ConnectorOnPackageAuxClass $
INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
1999
cim22ComputerSystemPackageAuxClass $
cim22LibraryPackageAuxClass $ cim22PackageCoolingAuxClass $
cim22PackageTempSensorAuxClass $ cim22PackageAlarmAuxClass $
cim22ProductPhysicalElementsAuxClass $
cim22FRUPhysicalElementsAuxClass $
cim22PhysicalElementLocationAuxClass $
cim22ElementCapacityAuxClass $
cim22ParticipatesInSetAuxClass $ cim22ElementsLinkedAuxClass $
cim22CollectedMSEsAuxClass $
cim22ElementConfigurationAuxClass $
cim22ElementSettingAuxClass $ cim22DependencyAuxClass $
cim22ProvidesServiceToElementAuxClass $
cim22ComponentAuxClass $ cim22SystemComponentAuxClass)
) )
( <oid-at485> NAME 'locationWithinContainer' 3.10 cim22ContainerAuxClass
This class represents the relationship between a contained and a
containing PhysicalElement.
( <oid-at96> NAME 'cimLocationWithinContainer'
DESC 'A free-form string representing the positioning of the DESC 'A free-form string representing the positioning of the
PhysicalElement within the PhysicalPackage. This string PhysicalElement within the PhysicalPackage. This string
could supplement or be used in place of instantiating the could supplement or be used in place of instantiating the
dmtfLocation object.' cimLocation object.'
SYNTAX string SINGLE-VALUE SYNTAX string SINGLE-VALUE
) )
( <oid-oc194> NAME 'dmtfContainerAuxClass' ( <oid-oc55> NAME 'cim22ContainerAuxClass'
DESC 'The Container association represents the relationship DESC 'The Container association represents the relationship
between a contained and a containing PhysicalElement.' between a contained and a containing PhysicalElement. A
SUP dmtfComponentAuxClass AUXILIARY containing object must be a PhysicalPackage. Attribute
MUST (groupComponentRef $ locationWithinContainer) cimGroupComponentRef points to cim22PhysicalPackage and
attribute cimPartComponentRef points to
cim22PhysicalElement.'
SUP cim22ComponentAuxClass AUXILIARY
MAY (cimGroupComponentRef $ cimPartComponentRef $
cimLocationWithinContainer)
) )
2.11 dmtfPhysicalFrame 3.11 cim22PhysicalFrame
A physical frame is a generic frame enclosure. A physical frame is a generic frame enclosure.
( <oid-at486> NAME 'cableManagementStrategy' ( <oid-at97> NAME 'cimCableManagementStrategy'
DESC 'CableManagementStrategy is a free-form string that contains DESC 'CableManagementStrategy is a free-form string that contains
information on how the various cables are connected and information on how the various cables are connected and
bundled for the Frame. With many networking, bundled for the Frame. With many networking,
storage-related and power cables, cable management can be a
complex and challenging task. This string property INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
contains information to aid in assembly and service of the 1999
Frame.'
storage-related and power cables, cable management can be a
complex and challenging endeavor. This string property
contains information to aid in assembly and service of the
Frame.'
SYNTAX string SINGLE-VALUE SYNTAX string SINGLE-VALUE
) )
( <oid-at487> NAME 'servicePhilosophy' ( <oid-at100> NAME 'cimLockPresent'
DESC 'ServicePhilosophy is an enumerated, integer-valued array DESC 'Boolean indicating whether the Frame is protected with a
that shows whether the Frame is serviced from the top lock.'
(value=2), front (3), back (4) or side (5), whether it has SYNTAX boolean SINGLE-VALUE
sliding trays (6) or removable sides (7), and/or whether
the Frame is moveable (8), for example, having rollers.
Allowed values are: "Unknown", "Other", "Service From Top"
"Service From Front", "Service From Back", "Service From
Side", "Sliding Trays", "Removable Sides", "Moveable".'
SYNTAX integer
) )
( <oid-at488> NAME 'serviceDescriptions' ( <oid-at101> NAME 'cimAudibleAlarm'
DESC 'An array of free-form strings providing more detailed DESC 'Boolean indicating whether the Frame is equipped with an
explanations for any of the entries in the audible alarm.'
ServicePhilosophy array.' SYNTAX boolean SINGLE-VALUE
SYNTAX string
) )
( <oid-at489> NAME 'lockPresent' ( <oid-at102> NAME 'cimVisibleAlarm'
DESC 'Boolean indicating whether the Frame is protected with a DESC 'Boolean indicating that the equipment includes a visible
lock.' alarm.'
SYNTAX boolean SINGLE-VALUE SYNTAX boolean SINGLE-VALUE
) )
( <oid-at490> NAME 'securityBreach' ( <oid-at103> NAME 'cimSecurityBreach'
DESC 'SecurityBreach is an enumerated, integer-valued property DESC 'SecurityBreach is an enumerated, integer-valued property
indicating whether a physical breach of the Frame was indicating whether a physical breach of the Frame was
attempted but unsuccessful (value=4) or attempted and attempted but unsuccessful (value=4) or attempted and
successful (5). Also, the values, "Unknown" or "No Breach".' successful (5). Also, the values, "Unknown", "Other" or
"No Breach", can be specified.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at491> NAME 'breachDescription'
( <oid-at104> NAME 'cimBreachDescription'
DESC 'BreachDescription is a free-form string providing more DESC 'BreachDescription is a free-form string providing more
information if the SecurityBreach property shows that a information if the SecurityBreach property indicates that a
breach or some other security-related event occurred.' breach or some other security-related event occurred.'
SYNTAX string SINGLE-VALUE SYNTAX string SINGLE-VALUE
) )
( <oid-oc195> NAME 'dmtfPhysicalFrame' ( <oid-at105> NAME 'cimIsLocked'
DESC 'PhysicalFrame is a superclass of Rack, Chassis and other DESC 'Boolean indicating that the Frame is currently locked.'
frame enclosures, as they are defined in extension SYNTAX boolean SINGLE-VALUE
classes.'
SUP dmtfPhysicalPackage
MUST (cableManagementStrategy $ servicePhilosophy $
serviceDescriptions $ lockPresent $ audibleAlarm $
visibleAlarm $ securityBreach $ breachDescription $
isLocked)
) )
2.12 dmtfRack ( <oid-oc56> NAME 'cim22PhysicalFrame'
SUP cim22PhysicalPackage
INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
1999
MAY (cimCableManagementStrategy $ cimLockPresent $
cimAudibleAlarm $ cimVisibleAlarm $ cimSecurityBreach $
cimBreachDescription $ cimIsLocked)
)
( <oid-nf17> NAME 'cim22PhysicalFrameNameForm'
OC cim22PhysicalFrame
MUST (orderedCimModelPath)
)
( <sr17> NAME 'cim22PhysicalFrameStructureRule'
FORM cim22PhysicalFrameNameForm
)
3.12 cim22Rack
Racks are enclosures in which chassis are placed. Typically they are Racks are enclosures in which chassis are placed. Typically they are
nothing more than the enclosure, and the chassis packages all nothing more than the enclosure, and the chassis packages all
functioning componentry. This class reuses the attribute height and functioning componentry.
defines the attributes typeOfRack and countryDesignation.
( <oid-at492> NAME 'typeOfRack' ( <oid-at106> NAME 'cimTypeOfRack'
DESC 'Enumeration indicating the type of Rack. Specifies DESC 'Enumeration indicating the type of Rack. Information such
information such as "Telco" or 19 inch rack (1). as "Telco" rack (value=2) or standard 19 inch rack (1) can
Allowed values are: "Unknown", "Standard 19 Inch", "Telco", be specified. The country for which the Rack is
"Equipment Shelf", "Non-Standard".' manufactured is defined in the the CountryDesignation
property.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at493> NAME 'countryDesignation' ( <oid-at107> NAME 'cimCountryDesignation'
DESC 'Country for which the Rack is designed. ISO/IEC 3166 DESC 'Designation of the country for which the Rack is
defines country code strings.' designed. Country code strings are as defined by ISO/IEC
3166. The rack type is specified in the TypeOfRack
property.'
SYNTAX string SINGLE-VALUE SYNTAX string SINGLE-VALUE
) )
( <oid-oc196> NAME 'dmtfRack' ( <oid-oc57> NAME 'cim22Rack'
DESC 'A Rack is a PhysicalFrame that represents an enclosure in DESC 'A Rack is a PhysicalFrame that represents an enclosure in
which Chassis are placed.' which Chassis are placed. Typically a Rack is nothing more
SUP dmtfPhysicalFrame than the enclosure, and all the functioning componentry is
MUST (height $ typeOfRack $ countryDesignation) packaged in the Chassis, loaded in the Rack.'
SUP cim22PhysicalFrame
MAY (cimTypeOfRack $ cimCountryDesignation)
) )
2.13 dmtfChassis The following content rule specifies the auxiliary classes that may
be attached to cim22Rack.
INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
1999
( <oid-oc57> NAME 'cim22RackContentRule'
DESC 'The auxiliary classes that may be attached to cim22Rack'
AUX (cim22ChassisInRackAuxClass)
)
3.13 cim22Chassis
Chassis enclose other elements and provide definable functionality. Chassis enclose other elements and provide definable functionality.
( <oid-at494> NAME 'numberOfPowerCords' ( <oid-at108> NAME 'cimNumberOfPowerCords'
DESC 'Integer indicating the number of power cords that must be DESC 'Integer indicating the number of power cords which must be
connected to the Chassis, for all the componentry to connected to the Chassis, for all the componentry to
operate.' operate.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at495> NAME 'currentRequiredOrProduced' ( <oid-at109> NAME 'cimCurrentRequiredOrProduced'
DESC 'Current required by the Chassis at 120V. If power is DESC 'Current required by the Chassis at 120V. If power is
provided by the Chassis (as for a UPS), this property may provided by the Chassis (as in the case of a UPS), this
be the amperage produced, as a negative number.' property may indicate the amperage produced, as a negative
SYNTAX binary SINGLE-VALUE number.'
SYNTAX integer SINGLE-VALUE
) )
( <oid-at496> NAME 'heatGeneration' ( <oid-at110> NAME 'cimHeatGeneration'
DESC 'Amount of heat generated by the Chassis in BTU/hour.' DESC 'Amount of heat generated by the Chassis in BTU/hour.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at497> NAME 'chassisTypes' ( <oid-oc58> NAME 'cim22Chassis'
DESC 'An enumerated, integer-valued array indicating the type of DESC 'The Chassis class represents the PhysicalElements that
Chassis.' enclose other Elements and provide definable functionality,
SYNTAX integer such as a desktop, processing node, UPS, disk or tape
storage, or a combination of these.'
SUP cim22PhysicalFrame
MAY (cimNumberOfPowerCords $ cimCurrentRequiredOrProduced $
cimHeatGeneration)
) )
( <oid-at498> NAME 'typeDescriptions' ( <oid-nf18> NAME 'cim22ChassisNameForm'
DESC 'An array of free-form strings providing more information on OC cim22Chassis
the ChassisTypes array entries.' MUST (orderedCimModelPath)
SYNTAX string
) )
( <oid-oc197> NAME 'dmtfChassis' ( <sr18> NAME 'cim22ChassisStructureRule'
DESC 'The Chassis class represents the PhysicalElements that FORM cim22ChassisNameForm
enclose other Elements and provide definable functionality,
such as a desktop, processing node, UPS, disk or tape
storage, or a combination of these.'
SUP dmtfPhysicalFrame
MUST (numberOfPowerCords $ currentRequiredOrProduced $
heatGeneration $ chassisTypes $ typeDescriptions)
) )
2.14 dmtfChassisInRackAuxClass INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
1999
The following content rule specifies the auxiliary classes that may
be attached to cim22Chassis.
( <oid-oc58> NAME 'cim22ChassisContentRule'
DESC 'The auxiliary classes that may be attached to cim22Chassis'
AUX (cim22ChassisInRackAuxClass $ cim22PackageInChassisAuxClass $
cim22DockedAuxClass)
)
3.14 cim22ChassisInRackAuxClass
This class makes explicit the 'containing' relationship between the This class makes explicit the 'containing' relationship between the
Rack and the Chassis. In it, groupComponentRef points to a single Rack and the Chassis.
dmtfRack object while partComponentRefs point to dmtfChassis object.
The attribute bottomU is also defined.
( <oid-at499> NAME 'bottomU' ( <oid-at113> NAME 'cimBottomU'
DESC 'An integer indicating the lowest or 'bottom' U in which the DESC 'An integer indicating the lowest or "bottom" U in which the
Chassis is mounted. A 'U' is a standard unit of measure for Chassis is mounted. A "U" is a standard unit of measure for
the height of a Rack or rack-mountable component. It is the height of a Rack or rack-mountable component. It is
equal to 1.75 inches or 4.445 cm.' equal to 1.75 inches or 4.445 cm.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-oc198> NAME 'dmtfChassisInRackAuxClass' ( <oid-oc59> NAME 'cim22ChassisInRackAuxClass'
DESC 'makes explicit the "containing" relationship between the DESC 'Racks, as simple enclosures, contain Chassis that provide
Rack and the Chassis.' the physical componentry realizing processing nodes,
SUP dmtfContainerAuxClass AUXILIARY storage devices, UPSs, etc. The ChassisInRack association
MUST (bottomU) makes explicit the "containing" relationship between the
Rack and the Chassis.Attribute cimGroupComponentRef points
to cim22Rack and attribute cimPartComponentRef points to
cim22Chassis.'
SUP cim22ContainerAuxClass AUXILIARY
MAY (cimGroupComponentRef $ cimPartComponentRef $
cimLocationWithinContainer $ cimBottomU)
) )
2.15 dmtfPackageInChassisAuxClass 3.15 cim22PackageInChassisAuxClass
This class makes the containment relationship between a chassis and This class makes the containment relationship between a chassis and
other packages explicit. In it, groupComponentRef must point to a other packages explicit.
dmtfChassis object and partComponentRefs must point to
dmtfPhysicalPackage objects.
( <oid-oc199> NAME 'dmtfPackageInChassisAuxClass' ( <oid-oc60> NAME 'cim22PackageInChassisAuxClass'
DESC 'A Chassis can contain other Packages, such as other Chassis DESC 'A Chassis can contain other Packages, such as other Chassis
and Cards. The PackageInChassis association makes explicit and Cards. The PackageInChassis association makes explicit
this relationship.' this relationship. Attribute cimGroupComponentRef points to
SUP dmtfContainerAuxClass AUXILIARY cim22Chassis and attribute cimPartComponentRef points to
cim22PhysicalPackage.'
SUP cim22ContainerAuxClass AUXILIARY
MAY (cimGroupComponentRef $ cimPartComponentRef $
INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
1999
cimLocationWithinContainer)
) )
2.16 dmtfDockedAuxClass 3.16 cim22DockedAuxClass
This class makes explicit the relationship between a laptop, a type This class makes explicit the relationship between a laptop, a type
of chassis, which docks in another type of chassis, a docking of chassis, which docks in another type of chassis, a docking
station. In it, antecedentRef and dependentRef point to only one station.
dmtfChassis object.
( <oid-at500> NAME 'antecedentRef'
DESC 'A single object that is dependend on.'
SYNTAX DN SINGLE-VALUE
)
( <oid-at501> NAME 'dependentRef'
DESC 'A single dependent object.'
SYNTAX DN SINGLE-VALUE
)
( <oid-oc200> NAME 'dmtfDockedAuxClass' ( <oid-oc61> NAME 'cim22DockedAuxClass'
DESC 'A laptop, a type of Chassis, may be docked in another type DESC 'A laptop, a type of Chassis, may be docked in another type
of Chassis, a Docking Station.' of Chassis, a Docking Station. This is the relationship
SUP dmtfDependencyAuxClass AUXILIARY represented by the Docked association. Because this is such
MUST (antecedentRef $ dependentRef) a typical relationship, it is explicitly described. Both
attributes point to cim22Chassis objects.'
SUP cim22DependencyAuxClass AUXILIARY
MAY (cimAntecedentRef $ cimDependentRef)
) )
2.17 dmtfCard 3.17 cim22Card
This class represents a type of physical container that can be This class represents a type of physical container that can be
plugged into another Card or HostingBoard, or is itself a plugged into another Card or HostingBoard, or is itself a
HostingBoard/Motherboard in a Chassis. It includes any package HostingBoard/Motherboard in a Chassis. It includes any package
capable of carrying signals and providing a mounting point for capable of carrying signals and providing a mounting point for
PhysicalComponents, such as Chips, or other PhysicalPackages, such as PhysicalComponents, such as Chips, or other PhysicalPackages, such as
other Cards. it defines the attributes hostingBoard, slotLayout, other Cards.
requiresDaughterBoard, specialRequirements, requirementsDescription,
and operatingVoltages.
( <oid-at502> NAME 'hostingBoard' ( <oid-at114> NAME 'cimHostingBoard'
DESC 'Boolean indicating that this Card is a Motherboard or, more DESC 'Boolean indicating that this Card is a Motherboard or, more
generically, a baseboard in a Chassis.' generically, a baseboard in a Chassis.'
SYNTAX boolean SINGLE-VALUE SYNTAX boolean SINGLE-VALUE
) )
( <oid-at503> NAME 'slotLayout' ( <oid-at115> NAME 'cimSlotLayout'
DESC 'SlotLayout is a free-form string that describes the slot DESC 'SlotLayout is a free-form string that describes the slot
positioning, typical usage, restrictions, individual slot positioning, typical usage, restrictions, individual slot
spacings or any other pertinent information for the slots spacings or any other pertinent information for the slots
on a Card.' on a Card.'
SYNTAX string SINGLE-VALUE SYNTAX string SINGLE-VALUE
) )
( <oid-at504> NAME 'requiresDaughterBoard' ( <oid-at116> NAME 'cimRequiresDaughterBoard'
DESC 'Boolean indicating that at least one daughterboard or DESC 'Boolean indicating that at least one daughterboard or
auxiliary Card is required to function properly.' auxiliary Card is required in order to function properly.'
SYNTAX boolean SINGLE-VALUE SYNTAX boolean SINGLE-VALUE
) )
( <oid-at505> NAME 'specialRequirements' INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
DESC 'Boolean indicating that this Card is physically unique from 1999
other Cards of the same type and therefore requires a special
Slot.'
SYNTAX boolean SINGLE-VALUE
( <oid-at117> NAME 'cimSpecialRequirements'
DESC 'Boolean indicating that this Card is physically unique
from other Cards of the same type and therefore requires a
special Slot. For example, a double-wide Card requires two
Slots. Another example is where a certain Card may be used
for the same general function as other Cards but requires a
special Slot (e.g., extra long), whereas the other Cards
can be placed in any available Slot. If set to TRUE, then
the corresponding property, RequirementsDescription, should
specify the nature of the uniqueness or purpose of the
Card.'
SYNTAX boolean SINGLE-VALUE
) )
( <oid-at506> NAME 'requirementsDescription' ( <oid-at118> NAME 'cimRequirementsDescription'
DESC 'A free-form string describing the way(s) in which this Card DESC 'A free-form string describing the way(s) in which this Card
is physically unique from other Cards. This property only is physically unique from other Cards. This property only
has meaning when the corresponding boolean property, has meaning when the corresponding boolean property,
SpecialRequirements, is set to TRUE.' SpecialRequirements, is set to TRUE.'
SYNTAX string SINGLE-VALUE SYNTAX string SINGLE-VALUE
) )
( <oid-at507> NAME 'operatingVoltages' ( <oid-at119> NAME 'cimOperatingVoltages'
DESC 'Operating voltages required by the Card.' DESC 'Operating voltages required by the Card.'
SYNTAX binary SYNTAX
) )
( <oid-oc201> NAME 'dmtfCard' ( <oid-oc62> NAME 'cim22Card'
DESC 'The Card class represents a type of physical container that DESC 'The Card class represents a type of physical container that
can be plugged into another Card or HostingBoard, or is can be plugged into another Card or HostingBoard, or is
itself a HostingBoard/Motherboard in a Chassis.' itself a HostingBoard/Motherboard in a Chassis. The
SUP dmtfPhysicalPackage cim22Card class includes any package capable of carrying
MUST (hostingBoard $ slotLayout $ requiresDaughterBoard $ signals and providing a mounting point for
specialRequirements $ requirementsDescription $ PhysicalComponents, such as Chips, or other
operatingVoltages) PhysicalPackages, such as other Cards.'
SUP cim22PhysicalPackage
MAY (cimHostingBoard $ cimSlotLayout $ cimRequiresDaughterBoard $
cimSpecialRequirements $ cimRequirementsDescription $
cimOperatingVoltages)
) )
2.18 dmtfSystemBusCard The following content rule specifies the auxiliary classes that may
be attached to cim22Card.
( <oid-oc62> NAME 'cim22CardContentRule'
DESC 'The auxiliary classes that may be attached to cim22Card'
AUX (cim22CardOnCardAuxClass $ cim22MemoryOnCardAuxClass $
cim22CardInSlotAuxClass)
INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
1999
)
3.18 cim22SystemBusCard
System bus cards require additional attributes, detailing the card's bus System bus cards require additional attributes, detailing the card's bus
type and data width, which dictate the type of slot into which the card type and data width, which dictate the type of slot into which the card
can be inserted. For example, attributes can define that a card is a can be inserted. For example, attributes can define that a card is a
PCI, 64 bit adapter. PCI, 64 bit adapter.
( <oid-at508> NAME 'busType' ( <oid-at120> NAME 'cimBusType'
DESC 'An enumerated integer describing the System bus type for DESC 'An enumerated integer describing the System bus type for
this Card. It shows the type of Slot into which the this Card. It indicates the type of Slot into which the
Card can plug. The list of permissible values aligns with Card can plug.'
the System bus types in CIM_PhysicalConnector.ConnectorType.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at509> NAME 'busWidth' ( <oid-at121> NAME 'cimBusWidth'
DESC 'System bus width (in bits) required by this Card. If DESC 'System bus width (in bits) required by this Card. If
"unknown", enter 0. If "other" than the values, 8, 16, 32, "unknown", enter 0. If "other" than the values, 8, 16, 32,
64 or 128, enter 1.' 64 or 128, enter 1.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-oc202> NAME 'dmtfSystemBusCard' ( <oid-oc63> NAME 'cim22SystemBusCard'
DESC 'The SystemBusCard class represents additional information DESC 'The SystemBusCard class represents additional information
for a Card, detailing the Card's bus type and data width.' for a cimCard, detailing the Card's bus type and data
SUP dmtfCard width. These properties dictate the type of Slot into which
MUST (busType $ busWidth) the Card can be inserted. For example, using the properties
of this class, one can define that a Card is a PCI, 64 bit
adapter.'
SUP cim22Card
MAY (cimBusType $ cimBusWidth)
) )
2.19 dmtfCardOnCardAuxClass 3.19 cim22CardOnCardAuxClass
Cards may be plugged into Motherboards/baseboards, are daughtercards Cards may be plugged into Motherboards/baseboards, are daughtercards
of an adapter, or support special Card-like modules. This auxiliary of an adapter, or support special Card-like modules. This auxiliary
class describes these relationships and defines the class describes these relationships.
mountOrSlotDescription attribute. In it groupComponentRef points to
a single dmtfCard object while partComponentRefs also point to
dmtfCard objects.
( <oid-at510> NAME 'mountOrSlotDescription' ( <oid-at122> NAME 'cimMountOrSlotDescription'
DESC 'A string describing and identifying how the Card is mounted DESC 'A string describing and identifying how the Card is mounted
on or plugged into the "other" Card. This attribute could on or plugged into the "other" Card. Slot information could
store slot information, which may be enough for certain be included in this field and may be sufficient for certain
management purposes. If so, this avoids creating management purposes. If so, this avoids creating
instantiations of Connector/Slot objects just to model the instantiations of Connector/Slot objects just to model the
relationship of Cards to HostingBoards or other relationship of Cards to HostingBoards or other
adapters. On the other hand, if Slot and Connector adapters. On the other hand, if Slot and Connector
information is available, this field could be used to
provide more detailed mounting or slot insertion data.' INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
1999
information is available, this field could be used to
provide more detailed mounting or slot insertion data.'
SYNTAX string SINGLE-VALUE SYNTAX string SINGLE-VALUE
) )
( <oid-oc203> NAME 'dmtfCardOnCardAuxClass' ( <oid-oc64> NAME 'cim22CardOnCardAuxClass'
DESC 'Cards may be plugged into Motherboards/baseboards, are DESC 'Cards may be plugged into Motherboards/baseboards, are
daughtercards of an adapter, or support special Card-like daughtercards of an adapter, or support special Card-like
modules.' modules. These relationships are described by the
SUP dmtfContainerAuxClass AUXILIARY CardOnCard association. Both reference attributes point to
MUST (mountOrSlotDescription) cim22Card objects.'
SUP cim22ContainerAuxClass AUXILIARY
MAY (cimGroupComponentRef $ cimPartComponentRef $
cimLocationWithinContainer $ cimMountOrSlotDescription)
) )
2.20 dmtfStorageMediaLocation 3.20 cim22StorageMediaLocation
A storage media location holds media and goes beyond being just a A storage media location holds media and goes beyond being just a
location used by a storage library. location used by a storage library.
( <oid-at511> NAME 'locationType' ( <oid-at123> NAME 'cimLocationType'
DESC 'The type of Location. For example, whether this is an DESC 'The type of Location. For example, whether this is an
individual Media "Slot" or a "Magazine"property. Allowed individual Media "Slot" (value=2), a MediaAccessDevice
values are: "Unknown", "Other", "Slot", "Magazine", (value=4) or a "Magazine" (value=3) is indicated in this
"MediaAccessDevice", "InterLibrary Port", "Limited Access property.'
Port", "Door", "Shelf", "Vault".'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at512> NAME 'locationCoordinates' ( <oid-at124> NAME 'cimLocationCoordinates'
DESC 'LocationCoordinates represent the physical location of the DESC 'LocationCoordinates represent the physical location of the
the StorageMediaLocation instance. The property is defined the StorageMediaLocation instance. The property is defined
as a free-form string to allow the location information to as a free-form string to allow the location information to
be described in vendor-unique terminology.' be described in vendor-unique terminology.'
SYNTAX string SINGLE-VALUE SYNTAX string SINGLE-VALUE
) )
( <oid-at513> NAME 'mediaTypesSupported' ( <oid-at127> NAME 'cimMediaCapacity'
DESC 'Certain StorageMediaLocations may only be able to accept a DESC 'A StorageMediaLocation may hold more than one PhysicalMedia
limited set of PhysicalMedia MediaTypes.' - for example, a Magazine. This property indicates the
SYNTAX integer PhysicalMedia capacity of the Location.'
SYNTAX integer SINGLE-VALUE
) )
( <oid-at514> NAME 'mediaSizesSupported' ( <oid-oc65> NAME 'cim22StorageMediaLocation'
DESC 'The sizes (in inches) of the particular MediaTypes that may DESC 'StorageMediaLocation is a PhysicalElement where
be placed in the Location' PhysicalMedia may be placed. This class describes an entity
SYNTAX binary that holds Media and is not just a "place" (as is conveyed
INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
1999
by the cim22Location object). This class is typically used
in the context of a StorageLibrary. Examples of
StorageMediaLocations are MediaAccessDevices,
InterLibraryPorts or "slots" in a Library panel.'
SUP cim22PhysicalPackage
MAY (cimLocationType $ cimLocationCoordinates $ cimMediaCapacity)
) )
( <oid-at515> NAME 'mediaCapacity' ( <oid-nf19> NAME 'cim22StorageMediaLocationNameForm'
DESC 'A StorageMediaLocation may hold more than one PhysicalMedia OC cim22StorageMediaLocation
- for example, a Magazine. This property shows the MUST (orderedCimModelPath)
PhysicalMedia capacity of the Location.'
SYNTAX integer SINGLE-VALUE
) )
( <oid-oc204> NAME 'dmtfStorageMediaLocation' ( <sr19> NAME 'cim22StorageMediaLocationStructureRule'
DESC 'a PhysicalElement where PhysicalMedia may be placed.' FORM cim22StorageMediaLocationNameForm
SUP dmtfPhysicalPackage
MUST (locationType $ locationCoordinates $ mediaTypesSupported $
mediaSizesSupported $ mediaCapacity)
) )
2.21 dmtfPhysicalComponent The following content rule specifies the auxiliary classes that may
be attached to cim22StorageMediaLocation.
( <oid-oc65> NAME 'cim22StorageMediaLocationContentRule'
DESC 'The auxiliary classes that may be attached to
cim22StorageMediaLocation'
AUX (cim22DeviceServicesLocationAuxClass $
cim22PhysicalMediaInLocationAuxClass)
)
3.21 cim22PhysicalComponent
A physical component either can not or does not need to be decomposed A physical component either can not or does not need to be decomposed
into its constituent parts. For example, an ASIC can not be further into its constituent parts. For example, an ASIC can not be further
decomposed and a tape for data storage does not need to be decomposed and a tape for data storage does not need to be
decomposed. Any element that is not a link, connector, or package is decomposed. Any element that is not a link, connector, or package is
subclassed from this class. subclassed from this class.
( <oid-oc205> NAME 'dmtfPhysicalComponent' ( <oid-oc66> NAME 'cim22PhysicalComponent'
DESC 'represents any low-level or basic Component within a DESC 'The PhysicalComponent class represents any low-level or
Package.' basic Component within a Package. A Component object either
SUP dmtfPhysicalElement can not or does not need to be decomposed into its
MUST (removable $ replaceable $ hotSwappable) constituent parts. For example, an ASIC (or Chip) can not
be further decomposed. A tape for data storage
(PhysicalMedia) does not need to be decomposed. Any
PhysicalElement that is not a Link, Connector, or Package
is a descendent (or member) of this class. For example, the
UART chipset on an internal modem Card would be a subclass
(if additional properties or associations are defined) or
an instance of PhysicalComponent.'
SUP cim22PhysicalElement
INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
1999
MAY (cimRemovable $ cimReplaceable $ cimHotSwappable)
) )
2.22 dmtfPackagedComponentAuxClass The following content rule specifies the auxiliary classes that may
be attached to cim22PhysicalComponent.
( <oid-oc66> NAME 'cim22PhysicalComponentContentRule'
DESC 'The auxiliary classes that may be attached to
cim22PhysicalComponent'
AUX (cim22PackagedComponentAuxClass $ cim22RealizesAuxClass $
cim22ProductPhysicalElementsAuxClass $
cim22FRUPhysicalElementsAuxClass $
cim22PhysicalElementLocationAuxClass $
cim22ElementCapacityAuxClass $
cim22ParticipatesInSetAuxClass $ cim22ContainerAuxClass $
cim22ElementsLinkedAuxClass $ cim22CollectedMSEsAuxClass $
cim22ElementConfigurationAuxClass $
cim22ElementSettingAuxClass $ cim22DependencyAuxClass $
cim22ProvidesServiceToElementAuxClass $
cim22ComponentAuxClass $ cim22SystemComponentAuxClass)
)
3.22 cim22PackagedComponentAuxClass
As a physical package typically contains a component, this class As a physical package typically contains a component, this class
makes this relationship explicit. The word, 'typically', is used makes this relationship explicit. The word, 'typically', is used
because a Component may be removed from, or not yet inserted into, because a Component may be removed from, or not yet inserted into,
its containing Package (ie, the Removable boolean is TRUE). its containing Package (ie, the Removable boolean is TRUE).
Therefore, a Component may not always be associated with a container. Therefore, a Component may not always be associated with a container.
In it, groupComponentRef points to a dmtfPhysicalPackage object and
partComponentRefs point to dmtfPhysicalComponent objects.
( <oid-oc206> NAME 'dmtfPackagedComponentAuxClass' ( <oid-oc67> NAME 'cim22PackagedComponentAuxClass'
DESC 'A Component is typically contained by a PhysicalPackage, DESC 'A Component is typically contained by a PhysicalPackage,
such as a Chassis or Card.' such as a Chassis or Card. The PackagedComponent
SUP dmtfContainerAuxClass AUXILIARY association makes this relationship explicit. In the first
sentence, the word, "typically", is used. This is because a
Component may be removed from, or not yet inserted into,
its containing Package (ie, the Removable boolean is
TRUE). Therefore, a Component may not always be associated
with a container. Attribute cimGroupComponentRef points to
cim22PhysicalPackage and attribute cimPartComponentRef points
to cim22PhysicalComponent.'
SUP cim22ContainerAuxClass AUXILIARY
MAY (cimGroupComponentRef $ cimPartComponentRef $
cimLocationWithinContainer)
) )
2.23 dmtfChip INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
1999
3.23 cim22Chip
A chip is of IC hardware, including ASICs, processors, and memory A chip is of IC hardware, including ASICs, processors, and memory
chips. chips.
( <oid-at516> NAME 'formFactor' ( <oid-at128> NAME 'cimFormFactor'
DESC 'The implementation form factor for the Chip.For example, DESC 'The implementation form factor for the Chip. For example,
values such as SIMM (7), TSOP (9) or PGA (10) can be values such as SIMM (7), TSOP (9) or PGA (10) can be
specified. Allowed values are: "Unknown", "Other", "SIP", specified.'
"DIP", "ZIP", "SOJ", "Proprietary", "SIMM", "DIMM", "TSOP",
"PGA", "RIMM", "SODIMM", "SRIMM", "SMD", "SSMP", "QFP",
"TQFP", "SOIC", "LCC", "PLCC", "BGA", "FPBGA", "LGA".'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-oc207> NAME 'dmtfChip' ( <oid-oc68> NAME 'cim22Chip'
DESC 'represents any type of integrated circuit hardware, DESC 'The Chip class represents any type of integrated circuit
including ASICs, processors, memory chips, etc.' hardware, including ASICs, processors, memory chips, etc.'
SUP dmtfPhysicalComponent SUP cim22PhysicalComponent
MUST (formFactor) MAY (cimFormFactor)
) )
2.24 dmtfPhysicalMemory 3.24 cim22PhysicalMemory
Physical memory are low level memory devices. Physical memory are low level memory devices.
( <oid-at517> NAME 'totalWidth' ( <oid-at129> NAME 'cimTotalWidth'
DESC 'Total width, in bits, of the PhysicalMemory, including DESC 'Total width, in bits, of the PhysicalMemory, including
check or error correction bits. If there are no error check or error correction bits. If there are no error
correction bits, the value in this property should match correction bits, the value in this property should match
that specified for DataWidth.' that specified for DataWidth.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at518> NAME 'capacity' ( <oid-at130> NAME 'cimDataWidth'
DESC 'Data width of the PhysicalMemory, in bits. A data width of
0 and a TotalWidth of 8 would indicate that the Memory is
solely used to provide error correction bits.'
SYNTAX integer SINGLE-VALUE
)
( <oid-at131> NAME 'cimSpeed'
DESC 'The speed of the PhysicalMemory, in nanoseconds.'
SYNTAX integer SINGLE-VALUE
)
( <oid-at132> NAME 'cimCapacity'
DESC 'The total capacity of this PhysicalMemory, in bytes.' DESC 'The total capacity of this PhysicalMemory, in bytes.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at519> NAME 'bankLabel' INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
1999
( <oid-at133> NAME 'cimBankLabel'
DESC 'A string identifying the physically labeled bank where the DESC 'A string identifying the physically labeled bank where the
Memory is located' Memory is located - for example, "Bank 0" or "Bank A".'
SYNTAX string{64} SINGLE-VALUE SYNTAX string{64} SINGLE-VALUE
) )
( <oid-at520> NAME 'positionInRow' ( <oid-at134> NAME 'cimPositionInRow'
DESC 'Specifies the position of the PhysicalMemory in a DESC 'Specifies the position of the PhysicalMemory in a
"row". For example, if it takes two 8-bit memory devices to "row". For example, if it takes two 8-bit memory devices to
form a 16-bit row, then a value of "2" means that this form a 16-bit row, then a value of "2"means that this
Memory is the second device.' Memory is the second device. 0 is an invalid value for this
property.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at521> NAME 'interleavePosition' ( <oid-at135> NAME 'cimInterleavePosition'
DESC 'The position of this PhysicalMemory in an interleave. 0 DESC 'The position of this PhysicalMemory in an interleave. 0
for non-interleaved. 1 for the first position, indicates non-interleaved. 1 indicates the first position,
2 for the second position and so on.' 2 the second position and so on. For example, in a 2:1
interleave, a value of "1" would indicate that the Memory
is in the "even" position.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-oc208> NAME 'dmtfPhysicalMemory' ( <oid-oc69> NAME 'cim22PhysicalMemory'
DESC 'subclass representing low level memory devices - SIMMS, DESC 'PhysicalMemory is a subclass of cim22Chip, representing low
DIMMs, raw memory chips, etc.' level memory devices - SIMMS, DIMMs, raw memory chips,
SUP dmtfChip etc.'
MUST (formFactor $ memoryType $ totalWidth $ dataWidth $ speed $ SUP cim22Chip
capacity $ bankLabel $ positionInRow $ interleavePosition) MAY (cimFormFactor $ cimMemoryType $ cimTotalWidth $
cimDataWidth $ cimSpeed $ cimCapacity $ cimBankLabel $
cimPositionInRow $ cimInterleavePosition)
) )
2.25 dmtfMemoryOnCardAuxClass The following content rule specifies the auxiliary classes that may
be attached to cim22PhysicalMemory.
( <oid-oc69> NAME 'cim22PhysicalMemoryContentRule'
DESC 'The auxiliary classes that may be attached to
cim22PhysicalMemory'
AUX (cim22MemoryOnCardAuxClass $ cim22MemoryWithMediaAuxClass)
)
3.25 cim22MemoryOnCardAuxClass
Hosting boards, adapter Cards, etc., can hold physical memory. Hosting boards, adapter Cards, etc., can hold physical memory.
Therefore, this class represents that relationship. In it, Therefore, this class represents that relationship.
groupComponentRef points to a dmtfCard object while partComponentRefs
point to dmtfPhysicalMemory objects.
( <oid-oc209> NAME 'dmtfMemoryOnCardAuxClass' INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
DESC 'Explicitly defines the relationship of cards containing 1999
memory.'
SUP dmtfPackagedComponentAuxClass AUXILIARY ( <oid-oc70> NAME 'cim22MemoryOnCardAuxClass'
DESC 'PhysicalMemory can be located on HostingBoards, adapter
Cards, etc. This association explicitly defines this
relationship of Memory to Cards. Attribute
cimGroupComponentRef points to cim22Card. Attribute
cimPartComponentRef points to cim22PhysicalMemory.'
SUP cim22PackagedComponentAuxClass
MAY (cimGroupComponentRef $ cimPartComponentRef $
cimLocationWithinContainer)
) )
2.26 dmtfPhysicalMedia 3.26 cim22PhysicalMedia
Physical media are any type of documentation or storage medium, Physical media are any type of documentation or storage medium,
typically removable media. However, this class can also model typically removable media. However, this class can also model
'sealed' media where dmtfPackagedComponentAuxClass associates the 'sealed' media where dmtfPackagedComponentAuxClass associates the
media with the physical package. media with the physical package.
( <oid-at522> NAME 'mediaType' ( <oid-at136> NAME 'cimMediaType'
DESC 'Specifies the type of the PhysicalMedia, as an enumerated DESC 'Specifies the type of the PhysicalMedia, as an enumerated
integer.' integer. The MediaDescription property is used to provide
more explicit definition of the Media type, whether it is
pre-formatted, compatability features, etc.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at523> NAME 'mediaDescription' ( <oid-at137> NAME 'cimMediaDescription'
DESC 'Additional detail related to the MediaType enumeration.' DESC 'Additional detail related to the MediaType enumeration. For
example, if value 3 ("QIC Cartridge") is specified, this
property could indicate whether the tape is wide or 1/4
inch, whether it is pre-formatted, whether it is Travan
compatible, etc.'
SYNTAX string SINGLE-VALUE SYNTAX string SINGLE-VALUE
) )
( <oid-at524> NAME 'writeProtectOn' ( <oid-at138> NAME 'cimWriteProtectOn'
DESC 'Boolean specifying whether the Media is currently write DESC 'Boolean specifying whether the Media is currently write
protected by some physical mechanism, such as a protect tab protected by some kind of physical mechanism, such as a
on a floppy diskette.' protect tab on a floppy diskette.'
SYNTAX boolean SINGLE-VALUE SYNTAX boolean SINGLE-VALUE
) )
( <oid-at525> NAME 'cleanerMedia' ( <oid-at139> NAME 'cimCleanerMedia'
DESC 'Boolean indicating that the PhysicalMedia is used for DESC 'Boolean indicating that the PhysicalMedia is used for
cleaning purposes and not data storage.' cleaning purposes and not data storage.'
SYNTAX boolean SINGLE-VALUE SYNTAX boolean SINGLE-VALUE
) )
( <oid-at526> NAME 'mediaSize' INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
DESC 'Size of the Media in inches.' 1999
SYNTAX binary SINGLE-VALUE
( <oid-at140> NAME 'cimMediaSize'
DESC 'Size of the Media in inches. For example, "3.5" would be
entered for a 3.5 inch disk, or "12" would be entered for a
12 inch optical disk. On the other hand, "0.5" would be
defined for a 1/2 inch tape.'
SUP cim22Float32 SINGLE-VALUE
) )
( <oid-at527> NAME 'maxMounts' ( <oid-at141> NAME 'cimMaxMounts'
DESC 'For removable Media, the maximum number of times that the DESC 'For removable Media, the maximum number of times that the
Media can be mounted before it should be retired. For Media can be mounted before it should be retired. For
cleaner Media, this is the maximum number of Drive cleans cleaner Media, this is the maximum number of Drive cleans
that can be performed. For nonremovable Media, such as hard that can be performed. For nonremovable Media, such as hard
disks, this property is not applicable and should be set to disks, this property is not applicable and should be set to
0.' 0.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at528> NAME 'dualSided' ( <oid-at142> NAME 'cimDualSided'
DESC 'Boolean indicating that the Media has two recording sides DESC 'Boolean indicating that the Media has two recording sides
(TRUE) or only a single side (FALSE). Examples of dual (TRUE) or only a single side (FALSE). Examples of dual
sided Media include DVD-ROM and some optical sided Media include DVD-ROM and some optical
disks. Examples of single sided Media are tapes and CD-ROM.' disks. Examples of single sided Media are tapes and
CD-ROM.'
SYNTAX boolean SINGLE-VALUE SYNTAX boolean SINGLE-VALUE
) )
( <oid-at529> NAME 'physicalLabels' ( <oid-oc71> NAME 'cim22PhysicalMedia'
DESC 'One or more strings on 'labels' on the PhysicalMedia. The DESC 'The PhysicalMedia class represents any type of
format of the labels and their state (readable, unreadable, documentation or storage medium, such as tapes, CDROMs,
upside-down) are shown in the LabelFormats and etc. This class is typically used to locate and manage
LabelStates array properties.' Removable Media (versus Media sealed with the
SYNTAX string MediaAccessDevice, as a single Package, as is the case with
hard disks). However, "sealed" Media can also be modeled
using this class, where the Media would then be associated
with the PhysicalPackage using the PackagedComponent
relationship.'
SUP cim22PhysicalComponent
MAY (cimCapacity $ cimMediaType $ cimMediaDescription $
cimWriteProtectOn $ cimCleanerMedia $ cimMediaSize $
cimMaxMounts $ cimDualSided $ cimPhysicalLabels $
cimLabelStates $ cimLabelFormats)
) )
( <oid-at530> NAME 'labelStates' ( <oid-nf20> NAME 'cim22PhysicalMemoryNameForm'
DESC 'An array of enumerated integers describing the states of OC cim22PhysicalMemory
each of the labels on a PhysicalMedia. The Labels MUST (orderedCimModelPath)
themselves are listed in the PhysicalLabels property.'
SYNTAX integer
) )
( <oid-at531> NAME 'labelFormats' INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
DESC 'An array of enumerated integers describing the formats of 1999
each of the labels on a PhysicalMedia. The Labels
themselves are listed in the PhysicalLabels property.' ( <sr20> NAME 'cim22PhysicalMemoryStructureRule'
SYNTAX integer FORM cim22PhysicalMemoryNameForm
) )
( <oid-oc210> NAME 'dmtfPhysicalMedia' The following content rule specifies the auxiliary classes that may
DESC 'represents any type of documentation or storage medium, be attached to cim22PhysicalMedia.
such as tapes, CDROMs, etc.'
SUP dmtfPhysicalComponent ( <oid-oc71> NAME 'cim22PhysicalMediaContentRule'
MUST (capacity $ mediaType $ mediaDescription $ writeProtectOn $ DESC 'The auxiliary classes that may be attached to
cleanerMedia $ mediaSize $ maxMounts $ cim22PhysicalMedia'
dualSided $ physicalLabels $ labelStates $ labelFormats) AUX (cim22MemoryWithMediaAuxClass $
cim22PhysicalMediaInLocationAuxClass)
) )
2.27 dmtfMemoryWithMediaAuxClass 3.27 cim22MemoryWithMediaAuxClass
This class shows that memory is associated with a physical media and This class shows that memory is associated with a physical media and
its cartridge and provides identification and also stores user- its cartridge and provides identification and also stores user-
specific data. In it, antecedentRefs point to dmtfPhysicalMemory specific data.
objects and dependentRefs point to dmtfPhysicalMedia objects.
( <oid-oc211> NAME 'dmtfMemoryWithMediaAuxClass' ( <oid-oc72> NAME 'cim22MemoryWithMediaAuxClass'
DESC 'shows that Memory is associated with a PhysicalMedia DESC 'MemoryWithMedia indicates that Memory is associated with a
and its cartridge.' PhysicalMedia and its cartridge. The Memory provides media
SUP dmtfDependencyAuxClass AUXILIARY identification and also stores user-specific
data. Attribute cimAntecedentRef points to
cim22PhysicalMemory and attribute cimDependentRef points to
cim22PhysicalMedia.'
SUP cim22DependencyAuxClass AUXILIARY
MAY (cimAntecedentRef $ cimDependentRef)
) )
2.28 dmtfPhysicalMediaInLocationAuxClass 3.28 cim22PhysicalMediaInLocationAuxClass
Within a storage library, all media should be accounted for, and be Within a storage library, all media should be accounted for, and be
present in some storage location. In addition, one can determine if present in some storage location. In addition, one can determine if
a location is empty or full based on whether this `auxiliary class is a location is empty or full based on whether this auxiliary class is
attached to a dmtfStorageMediaLocation object. In this class, attached to a cim22StorageMediaLocation object.
antecedentRef points to a single dmtfStorageMediaLocation object and
dependentRefs point to dmtfPhysicalMedia objects.
( <oid-oc212> NAME 'dmtfPhysicalMediaInLocationAuxClass' ( <oid-oc73> NAME 'cim22PhysicalMediaInLocationAuxClass'
DESC 'Within a StorageLibrary, all Media should be accounted for, DESC 'Within a StorageLibrary, all Media should be accounted for,
and be present in some Storage Location. This relationship and be present in some Storage Location. This relationship
is made explicit here' is made explicit by the PhysicalMediaInLocation
SUP dmtfDependencyAuxClass AUXILIARY association. In addition, one can determine if a Location is
MUST (antecedentRef) empty or full based on whether this association exists for
the StorageMediaLocation. Attribute cimAntecedentRef points
to cim22StorageMediaLocation and attribute cimDependentRef
points to cim22PhysicalMedia.'
SUP cim22DependencyAuxClass AUXILIARY
INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
1999
MAY (cimAntecedentRef $ cimDependentRef)
) )
2.29 dmtfPhysicalTape 3.29 cim22PhysicalTape
This class represents data for a tape Media, including information on This class represents data for a tape Media, including information on
the length and whether it must be unloaded from BOT. the length and whether it must be unloaded from BOT.
( <oid-at532> NAME 'tapeLength' ( <oid-at146> NAME 'cimTapeLength'
DESC 'The physical length of the Tape in feet.' DESC 'The physical length of the Tape in feet.'
SYNTAX binary SINGLE-VALUE SUP cim22Float32 SINGLE-VALUE
) )
( <oid-at533> NAME 'unloadAnywhere' ( <oid-at147> NAME 'cimUnloadAnywhere'
DESC 'Boolean set to TRUE if the Tape can be unloaded at any DESC 'Boolean set to TRUE if the Tape can be unloaded at any
position on the Media. It is set to FALSE if the tape must position on the Media. It is set to FALSE if the tape must
be at a certain position for unload - such as at the be at a certain position for unload - such as at the
beginning of tape (BOT) area, or at mid-tape point for beginning of tape (BOT) area, or at mid-tape point for
TapeDrives with mid-tape load.' TapeDrives with mid-tape load.'
SYNTAX boolean SINGLE-VALUE SYNTAX boolean SINGLE-VALUE
) )
( <oid-oc213> NAME 'dmtfPhysicalTape' ( <oid-oc74> NAME 'cim22PhysicalTape'
DESC 'represents additional data for a Tape Media.' DESC 'The PhysicalTape class represents additional data for a
SUP dmtfPhysicalMedia Tape Media. Information on the tape length and whether it
MUST (tapeLength $ unloadAnywhere) must be unloaded from BOT are properties of this class.'
SUP cim22PhysicalMedia
MAY (cimTapeLength $ cimUnloadAnywhere)
) )
2.30 dmtfPhysicalLink 3.30 cim22PhysicalLink
Physical links are the cabling together of physical elements, Physical links are the cabling together of physical elements,
including cables and links. Rather than model the numerous physical including cables and links. Rather than model the numerous physical
cables within a physical package or network, this class is intended cables within a physical package or network, this class is intended
for those cases where the cables or links are either critical for those cases where the cables or links are either critical
components or important assets. components or important assets.
( <oid-at534> NAME 'maxLength' ( <oid-at149> NAME 'cimMaxLength'
DESC 'The maximum length of the PhysicalLink in feet.' DESC 'The maximum length of the PhysicalLink in feet.'
SYNTAX binary SINGLE-VALUE SUP cim22Float64 SINGLE-VALUE
) )
( <oid-at535> NAME 'length' ( <oid-at150> NAME 'cimLength'
DESC 'The current length of the PhysicalLink in feet.' DESC 'The current length of the PhysicalLink in feet. For some
SYNTAX binary SINGLE-VALUE connections, especially wireless technologies, this
property may not be applicable and should be left
uninitialized.'
INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
1999
SUP cim22Float64 SINGLE-VALUE
) )
( <oid-at536> NAME 'wired' ( <oid-at151> NAME 'cimWired'
DESC 'Boolean indicating whether the PhysicalLink is a DESC 'Boolean indicating whether the PhysicalLink is an actual
cable (TRUE) or a wireless connection (FALSE).' cable (TRUE) or a wireless connection (FALSE).'
SYNTAX boolean SINGLE-VALUE SYNTAX boolean SINGLE-VALUE
) )
( <oid-oc214> NAME 'dmtfPhysicalLink' ( <oid-oc75> NAME 'cim22PhysicalLink'
DESC 'The PhysicalLink class represents the cabling of DESC 'The PhysicalLink class represents the cabling of
PhysicalElements together.' PhysicalElements together. For example, serial or Ethernet
SUP dmtfPhysicalElement cables, and infrared Links would be subclasses (if
MUST (maxLength $ length $ wired $ mediaType) additional properties or associations are defined) or
instances of PhysicalLink. In many cases, the numerous
physical cables within a PhysicalPackage or Network will
not be modeled. However, where these cables or Links are
critical components, or are tagged assets of the company,
these objects can be instantiated using this class or one
of its descendent classes.'
SUP cim22PhysicalElement
MAY (cimMaxLength $ cimLength $ cimWired $ cimMediaType)
) )
2.31 dmtfElementsLinkedAuxClass The following content rule specifies the auxiliary classes that may
be attached to cim22PhysicalLink.
( <oid-oc75> NAME 'cim22PhysicalLinkContentRule'
DESC 'The auxiliary classes that may be attached to
cim22PhysicalLink'
AUX (cim22ElementsLinkedAuxClass $
cim22LinkHasConnectorAuxClass $ cim22RealizesAuxClass $
cim22ProductPhysicalElementsAuxClass $
cim22FRUPhysicalElementsAuxClass $
cim22PhysicalElementLocationAuxClass $
cim22ElementCapacityAuxClass $
cim22ParticipatesInSetAuxClass $ cim22ContainerAuxClass $
cim22CollectedMSEsAuxClass $
cim22ElementConfigurationAuxClass $
cim22ElementSettingAuxClass $ cim22DependencyAuxClass $
cim22ProvidesServiceToElementAuxClass $
cim22ComponentAuxClass $ cim22SystemComponentAuxClass)
)
INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
1999
3.31 cim22ElementsLinkedAuxClass
This class shows which physical elements are cabled together by a This class shows which physical elements are cabled together by a
physical link. In it, antecedentRefs point to dmtfPhysicalLink physical link.
objects and dependentRefs point to dmtfPhysicalElement objects.
( <oid-oc215> NAME 'dmtfElementsLinkedAuxClass' ( <oid-oc76> NAME 'cim22ElementsLinkedAuxClass'
DESC 'shows which PhysicalElements are cabled together by a DESC 'The ElementsLinked association indicates which
PhysicalLink.' PhysicalElements are cabled together by a
SUP dmtfDependencyAuxClass AUXILIARY PhysicalLink. Attribute cimAntecedentRef points to
cim22PhysicalLink and attribute cimDependentRef points to
cim22PhysicalElement.'
SUP cim22DependencyAuxClass AUXILIARY
MAY (cimAntecedentRef $ cimDependentRef)
) )
2.32 dmtfPhysicalConnector 3.32 cim22PhysicalConnector
This class represents any physical element that is used to connect to This class represents any physical element that is used to connect to
other elements. Any object that can be used to connect and transmit other elements. Any object that can be used to connect and transmit
signals or power between two or more physical elements is a signals or power between two or more physical elements is a
descendant of this class. For example, slots and D-shell connectors descendant of this class. For example, slots and D-shell connectors
are types of physical connectors. This class uses two attributes: are types of physical connectors.
connectorPinout and connectorType.
( <oid-at537> NAME 'connectorPinout' ( <oid-at152> NAME 'cimConnectorPinout'
DESC 'A free-form string describing the pin configuration and DESC 'A free-form string describing the pin configuration and
signal usage of a PhysicalConnector.' signal usage of a PhysicalConnector.'
SYNTAX string SINGLE-VALUE SYNTAX string SINGLE-VALUE
) )
( <oid-at538> NAME 'connectorType' ( <oid-at153> NAME 'cimConnectorType'
DESC 'An array of integers defining the type of DESC 'An array of integers defining the type of
PhysicalConnector.' PhysicalConnector. An array is specified to allow the
description of "combinations" of Connector information. For
example, one array entry could specify RS-232 (value=25),
another DB-25 (value=23) and a third entry define the
Connector as "Male" (value=2).'
SYNTAX integer SYNTAX integer
) )
( <oid-oc216> NAME 'dmtfPhysicalConnector' ( <oid-oc77> NAME 'cim22PhysicalConnector'
DESC 'The PhysicalConnector class represents any PhysicalElement DESC 'The PhysicalConnector class represents any PhysicalElement
that is used to connect to other Elements.' that is used to connect to other Elements. Any object that
SUP dmtfPhysicalElement can be used to connect and transmit signals or power
MUST (connectorPinout $ connectorType) between two or more PhysicalElements is a descendant (or
member) of this class. For example, Slots and D-shell
connectors are types of PhysicalConnectors.'
SUP cim22PhysicalElement
MAY (cimConnectorPinout $ cimConnectorType)
INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
1999
) )
2.33 dmtfConnectedToAuxClass The following content rule specifies the auxiliary classes that may
be attached to cim22PhysicalConnector.
( <oid-oc77> NAME 'cim22PhysicalConnectorContentRule'
DESC 'The auxiliary classes that may be attached to
cim22PhysicalConnector'
AUX (cim22ConnectedToAuxClass $ cim22PackageInConnectorAuxClass $
cim22LinkHasConnectorAuxClass $
cim22ConnectorOnPackageAuxClass $
cim22AdapterActiveConnectionAuxClass $ cim22RealizesAuxClass $
cim22ProductPhysicalElementsAuxClass $
cim22FRUPhysicalElementsAuxClass $
cim22PhysicalElementLocationAuxClass $
cim22ElementCapacityAuxClass $
cim22ParticipatesInSetAuxClass $ cim22ContainerAuxClass $
cim22ElementsLinkedAuxClass $ cim22CollectedMSEsAuxClass $
cim22ElementConfigurationAuxClass $
cim22ElementSettingAuxClass $ cim22DependencyAuxClass $
cim22ProvidesServiceToElementAuxClass $
cim22ComponentAuxClass $ cim22SystemComponentAuxClass)
)
3.33 cim22ConnectedToAuxClass
This class shows that two or more physical connectors are connected. This class shows that two or more physical connectors are connected.
In it, both antecedentRefs and dependentRefs point to
dmtfPhysicalConnector objects.
( <oid-oc217> NAME 'dmtfConnectedToAuxClass' ( <oid-oc78> NAME 'cim22ConnectedToAuxClass'
DESC 'shows that two or more PhysicalConnectors are connected DESC 'The ConnectedTo association indicates that two or more
together.' PhysicalConnectors are connected together. Both attributes
SUP dmtfDependencyAuxClass AUXILIARY point to cim22PhysicalConnector objects.'
SUP cim22DependencyAuxClass AUXILIARY
MAY (cimAntecedentRef $ cimDependentRef)
) )
2.34 dmtfSlot 3.34 cim22Slot
A slot represents connectors into which packages are inserted. For A slot represents connectors into which packages are inserted. For
example, a physical package that is a disk drive may be inserted into example, a physical package that is a disk drive may be inserted into
a SCA slot. As another example, a card may be inserted into a 16-, a SCA slot. As another example, a card may be inserted into a 16-,
32-, or 64-bit expansion slot on a hosting board. 32-, or 64-bit expansion slot on a hosting board.
( <oid-at539> NAME 'supportsHotPlug' ( <oid-at154> NAME 'cimSupportsHotPlug'
DESC 'Boolean indicating whether the Slot supports hot-plug of DESC 'Boolean indicating whether the Slot supports hot-plug of
adapter Cards.' adapter Cards.'
SYNTAX boolean SINGLE-VALUE SYNTAX boolean SINGLE-VALUE
) )
( <oid-at540> NAME 'heightAllowed'
INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
1999
( <oid-at155> NAME 'cimHeightAllowed'
DESC 'Maximum height of an adapter Card that can be inserted into DESC 'Maximum height of an adapter Card that can be inserted into
the Slot, in inches.' the Slot, in inches./
SYNTAX binary SINGLE-VALUE SUP cim22Float32 SINGLE-VALUE
) )
( <oid-at541> NAME 'lengthAllowed' ( <oid-at156> NAME 'cimLengthAllowed'
DESC 'Maximum length of an adapter Card that can be inserted into DESC 'Maximum length of an adapter Card that can be inserted into
the Slot, in inches.' the Slot, in inches.'
SYNTAX binary SINGLE-VALUE SUP cim22Float32 SINGLE-VALUE
) )
( <oid-at542> NAME 'vccMixedVoltageSupport' ( <oid-at157> NAME 'cimMaxDataWidth'
DESC 'Maximum bus width of adapter Cards that can be inserted
into this Slot, in bits. If the value is "unknown", enter
0. If the value is other than 8, 16, 32, 64 or 128, enter
1.'
SYNTAX integer SINGLE-VALUE
)
( <oid-at158> NAME 'cimVccMixedVoltageSupport'
DESC 'An array of enumerated integers indicating the Vcc voltage DESC 'An array of enumerated integers indicating the Vcc voltage
supported by this Slot.' supported by this Slot.'
SYNTAX integer SYNTAX integer
) )
( <oid-at543> NAME 'vppMixedVoltageSupport' ( <oid-at159> NAME 'cimVppMixedVoltageSupport'
DESC 'An array of enumerated integers indicating the Vpp voltage DESC 'An array of enumerated integers indicating the Vpp voltage
supported by this Slot.' supported by this Slot.'
SYNTAX integer SYNTAX integer
) )
( <oid-at544> NAME 'thermalRating' ( <oid-at160> NAME 'cimThermalRating'
DESC 'Maximum thermal dissipation of the Slot in milliwatts.' DESC 'Maximum thermal dissipation of the Slot in milliwatts.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at545> NAME 'specialPurpose' ( <oid-at161> NAME 'cimSpecialPurpose'
DESC 'Boolean indicating that this Slot is physically unique and DESC 'Boolean indicating that this Slot is physically unique and
may hold special types of hardware, e.g. a graphics may hold special types of hardware, e.g. a graphics
processor slot. If set to TRUE, then the property, processor slot. If set to TRUE, then the property,
SpecialPurposeDescription (a string), should specify the SpecialPurposeDescription (a string), should specify the
nature of the uniqueness or purpose of the Slot.' nature of the uniqueness or purpose of the Slot.'
SYNTAX boolean SINGLE-VALUE SYNTAX boolean SINGLE-VALUE
) )
( <oid-at546> NAME 'number' ( <oid-at162> NAME 'cimPurposeDescription'
DESC 'A free-form string describing that this Slot is physically
INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
1999
unique and may hold special types of hardware. This
property only has meaning when the corresponding boolean
property, SpecialPurpose, is set to TRUE.'
SYNTAX string SINGLE-VALUE
)
( <oid-at163> NAME 'cimNumber'
DESC 'The Number property indicates the physical slot number, DESC 'The Number property indicates the physical slot number,
which can be used as an index into a system slot table, which can be used as an index into a system slot table,
whether that slot is physically occupied.' whether or not that slot is physically occupied.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-oc218> NAME 'dmtfSlot' ( <oid-oc79> NAME 'cim22Slot'
DESC 'The Slot class represents Connectors into which Packages DESC 'The Slot class represents Connectors into which Packages
are inserted.' are inserted. For example, a PhysicalPackage that is a
DiskDrive may be inserted into an SCA "Slot". As another
example, a Card (subclass of PhysicalPackage) may be
inserted into a 16-, 32-, or 64-bit expansion "Slot" on a
HostingBoard. PCI or PCMCIA Type III Slots are examples of
the latter.'
SUP cim22PhysicalConnector
MAY (cimSupportsHotPlug $ cimHeightAllowed $ cimLengthAllowed $
cimMaxDataWidth $ cimThermalRating $
cimVccMixedVoltageSupport $ cimVppMixedVoltageSupport $
cimSpecialPurpose $ cimPurposeDescription $ cimNumber)
)
SUP dmtfPhysicalConnector The following content rule specifies the auxiliary classes that may
MUST (connectorType $ supportsHotPlug $ heightAllowed $ be attached to cim22Slot.
lengthAllowed $ maxDataWidth $ vccMixedVoltageSupport $
vppMixedVoltageSupport $ thermalRating $ specialPurpose $ ( <oid-oc79> NAME 'cim22SlotContentRule'
purposeDescription $ number) DESC 'The auxiliary classes that may be attached to cim22Slot'
AUX (cim22SlotInSlotAuxClass $ cim22AdjacentSlotsAuxClass $
cim22PackageInSlotAuxClass $ cim22CardInSlotAuxClass)
) )
2.35 dmtfSlotInSlotAuxClass 3.35 cim22SlotInSlotAuxClass
This class represents the ability of an adapter to extend a slot This class represents the ability of an adapter to extend a slot
structure, which enables the slot to support cards that would structure, which enables the slot to support cards that would
otherwise be incompatible by interfacing to the slot provided by the otherwise be incompatible by interfacing to the slot provided by the
adapter. This has many practical uses. In this class, antecedentRefs adapter. This has many practical uses.
point to dmtfSlot objects and dependentRef points to a dmtfSlot
objects.
( <oid-oc219> NAME 'dmtfSlotInSlotAuxClass' ( <oid-oc80> NAME 'cim22SlotInSlotAuxClass'
DESC 'represents the ability of a special adapter to extend the DESC 'Slots are special types of Connectors into which adapter
existing Slot structure to enable otherwise incompatible Cards are typically inserted. The SlotInSlot relationship
Cards to be plugged into a Frame or HostingBoard.' represents the ability of a special adapter to extend the
SUP dmtfConnectedToAuxClass AUXILIARY
MUST (dependentRef) INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
1999
existing Slot structure to enable otherwise incompatible
Cards to be plugged into a Frame or HostingBoard. The
adapter effectively creates a new Slot and can be thought
of (conceptually) as a Slot in a Slot. This enables Cards
that would otherwise be physically and/or electrically
incompatible with the existing Slots to be supported, by
interfacing to the Slot provided by the adapter. This has
many practical uses. For example, networking boards are
very expensive. As new hardware becomes available, Chassis
and even Card configurations change. To protect the
investment of their customers, networking vendors will
manufacture special adapters that enable old Cards to fit
into new Chassis or HostingBoards and/or new Cards to fit
into old. This is done using a special adapter that fits
over one or more existing Slots and presents a new Slot
into which the Card can plug. Both attributes point to
cim22Slot objects.'
SUP cim22ConnectedToAuxClass AUXILIARY
MAY (cimAntecedentRef $ cimDependentRef)
) )
2.36 dmtfAdjacentSlotsAuxClass 3.36 cim22AdjacentSlotsAuxClass
This class describes the layout of slots on a hosting board or This class describes the layout of slots on a hosting board or
adapter card and includes the distance between the slots and whether adapter card and includes the distance between the slots and whether
they are 'shared'. In it, slotARef and slotBRef both point to they are 'shared'.
dmtfCard objects.
( <oid-at547> NAME 'slotARef' ( <oid-at164> NAME 'cimSlotARef'
DESC 'an adjacent Slots.' DESC 'One of the adjacent Slots.'
SYNTAX DN SINGLE-VALUE SYNTAX DN
) )
( <oid-at548> NAME 'slotBRef' ( <oid-at165> NAME 'cimSlotBRef'
DESC 'The 'other' adjacent Slot.' DESC 'The "other" adjacent Slot.'
SYNTAX DN SINGLE-VALUE SYNTAX DN
) )
( <oid-at549> NAME 'distanceBetweenSlots' ( <oid-at166> NAME 'cimDistanceBetweenSlots'
DESC 'The distance, in inches, between adjacent Slots.' DESC 'The distance, in inches, between adjacent Slots.'
SYNTAX binary SINGLE-VALUE SUP cim22Float32 SINGLE-VALUE
) )
( <oid-at550> NAME 'sharedSlots' ( <oid-at167> NAME 'cimSharedSlots'
DESC 'Slots can be located near to each other on HostingBoards or DESC 'Slots can be located in close proximity on Hosting Boards
other Cards, such that if one of these Slots is populated or other Cards, such that if one of these Slots is
by an adapter Card, the other Slot must be left empty. This populated by an adapter Card, the other Slot must be left
relationship is shown by the SharedSlots boolean set to empty. This relationship is indicated by the SharedSlots
TRUE.' boolean set to TRUE.'
INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
1999
SYNTAX boolean SINGLE-VALUE SYNTAX boolean SINGLE-VALUE
) )
( <oid-oc220> NAME 'dmtfAdjacentSlotsAuxClass' ( <oid-oc81> NAME 'cim22AdjacentSlotsAuxClass'
DESC 'AdjacentSlots describes the layout of Slots on a DESC 'AdjacentSlots describes the layout of Slots on a
HostingBoard or adapter Card. Information like the distance HostingBoard or adapter Card. Information like the distance
between the Slots and whether they are 'shared' (if one is between the Slots and whether they are "shared" (if one is
populated, then the other Slot can not be used), is populated, then the other Slot can not be used), is
conveyed as properties of the association.' conveyed as properties of the association. Both reference
attributes point to cim22Slot objects.'
SUP top AUXILIARY SUP top AUXILIARY
MUST (slotARef $ slotBRef $ distanceBetweenSlots $ MAY (cimSlotARef $ cimSlotBRef $ cimDistanceBetweenSlots $
sharedSlots) cimSharedSlots)
) )
2.37 dmtfPackageInConnectorAuxClass 3.37 cim22PackageInConnectorAuxClass
This class represents the relationship between cards that are into This class represents the relationship between cards that are into
system connectors for power and/or to transfer data. For example, it system connectors for power and/or to transfer data. For example, it
would be used to describe the insertion of a daughter card onto would be used to describe the insertion of a daughter card onto
another card. another card.
In this class antecedentRefs point to dmtfPhysicalConnector objects ( <oid-oc82> NAME 'cim22PackageInConnectorAuxClass'
and dependentRef points to a dmtfPhysicalPackage object. DESC 'Adapter cards and other "packaging" are plugged into System
Connectors for power and/or to transfer data. This
( <oid-oc221> NAME 'dmtfPackageInConnectorAuxClass' relationship is defined by PackageInConnector. For example,
DESC 'Represents adapter being plugged into System Connectors for it would be used to describe the insertion of a
power and/or to transfer data.' daughtercard onto another Card. Various subclasses of
SUP dmtfDependencyAuxClass AUXILIARY PackageInConnector are also defined. PackageInSlot and its
MUST (dependentRef) subclass, CardInSlot, are two examples of
subclasses. Attribute cimAntecedentRef points to
cim22PhysicalConnector and attribute cimDependentRef points
to cim22PhysicalPackage.'
SUP cim22DependencyAuxClass AUXILIARY
MAY (cimAntecedentRef $ cimDependentRef)
) )
2.38 dmtfPackageInSlotAuxClass 3.38 cim22PackageInSlotAuxClass
Complex networking devices often are based on chassis, which allow Complex networking devices often are based on chassis, which allow
for enhancement and/or augmentation of their base functionality for enhancement and/or augmentation of their base functionality
adding new chassis devices, similar to adding cards. This auxiliary adding new chassis devices, similar to adding cards. This auxiliary
class models this capability and in it, antecedentRefs point to class models this capability.
dmtfSlot objects.
( <oid-oc222> NAME 'dmtfPackageInSlotAuxClass' ( <oid-oc83> NAME 'cim22PackageInSlotAuxClass'
DESC 'Complex networking devices often are Chassis-based. These DESC 'Complex networking devices often are Chassis-based. These
Chassis allow for enhancement and/or augmentation of their Chassis allow for enhancement and/or augmentation of their
base functionality by accepting additional Chassis devices, base functionality by accepting additional Chassis devices,
similar to accepting functionality by adding Cards. This
class models this capability.' INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
SUP dmtfPackageInConnectorAuxClass AUXILIARY 1999
similar to accepting functionality in the form of adding
Cards. This association models this capability.. Attribute
cimAntecedentRef points to cim22Slot and attribute
cimDependentRef points to cim22PhysicalPackage.'
SUP cim22PackageInConnectorAuxClass AUXILIARY
MAY (cimAntecedentRef $ cimDependentRef)
) )
2.39 dmtfCardInSlotAuxClass 3.39 cim22CardInSlotAuxClass
Slots are special types of connectors into which cards are inserted. Slots are special types of connectors into which cards are inserted.
This relationship of a Card in a Slot is made explicit using this This relationship of a Card in a Slot is made explicit using this
class, where dependentRef points to a dmtfCard object. class.
( <oid-oc223> NAME 'dmtfCardInSlotAuxClass' ( <oid-oc84> NAME 'cim22CardInSlotAuxClass'
DESC 'Slots are special types of Connectors into which adapter DESC 'Slots are special types of Connectors into which adapter
Cards are inserted. This relationship of a Card in a Slot Cards are inserted. This relationship of a Card in a Slot
is made explicit here' is made explicit using the CardInSlot
SUP dmtfPackageInSlotAuxClass AUXILIARY association. Attribute cimAntecedentRef points to cim22Slot
and attribute cimDependentRef points to cim22Card.'
SUP cim22PackageInSlotAuxClass AUXILIARY
MAY (cimAntecedentRef $ cimDependentRef)
) )
2.40 dmtfLinkHasConnectorAuxClass 3.40 cim22LinkHasConnectorAuxClass
Cables and links use physical connectors to connect physical Cables and links use physical connectors to connect physical
elements, which this class explicitly defines. In it, elements, which this class explicitly defines.
groupComponentRef points to a dmtfPhysicalLink object and
partComponentRefs point to dmtfPhysicalConnector objects.
( <oid-oc224> NAME 'dmtfLinkHasConnectorAuxClass' ( <oid-oc85> NAME 'cim22LinkHasConnectorAuxClass'
DESC 'Cables and Links utilize PhysicalConnectors to actually DESC 'Cables and Links utilize PhysicalConnectors to actually
"connect" PhysicalElements. This association explicitly "connect" PhysicalElements. This association explicitly
defines this relationship of Connectors for PhysicalLinks.' defines this relationship of Connectors for
SUP dmtfComponentAuxClass AUXILIARY PhysicalLinks. Attribute cimGroupComponentRef points to
cim22PhysicalLink and attribute cimPartComponentRef points to
cim22PhysicalConnector.'
SUP cim22ComponentAuxClass AUXILIARY
MAY (cimGroupComponentRef $ cimPartComponentRef)
) )
2.41 dmtfConnectorOnPackageAuxClass 3.41 cim22ConnectorOnPackageAuxClass
Physical packages contain connectors and other physical elements, Physical packages contain connectors and other physical elements,
which this class makes explicit. In it, groupComponentRef points to which this class makes explicit.
a dmtfPhysicalPackage object and partComponentRefs point to
dmtfPhysicalConnector objects.
( <oid-oc225> NAME 'dmtfConnectorOnPackageAuxClass' ( <oid-oc86> NAME 'cim22ConnectorOnPackageAuxClass'
DESC 'PhysicalPackages contain Connectors as well as other DESC 'PhysicalPackages contain Connectors as well as other
PhysicalElements. This class makes explicit the containment PhysicalElements. The ConnectorOnPackage association makes
relationship between Connectors and Packages.'
SUP dmtfContainerAuxClass AUXILIARY INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
1999
explicit the containment relationship between Connectors
and Packages. Attribute cimGroupComponentRef points to
cim22PhysicalPackage and attribute cimPartComponentRef points
to cim22PhysicalConnector.'
SUP cim22ContainerAuxClass AUXILIARY
MAY (cimGroupComponentRef $ cimPartComponentRef $
cimLocationWithinContainer)
) )
2.42 dmtfAdapterActiveConnectionAuxClass 3.42 cim22AdapterActiveConnectionAuxClass
This class shows that a network adapter uses a physical connector for This class shows that a network adapter uses a physical connector for
output to the network. This relationship is important when the output to the network. This relationship is important when the
adapter can choose from one of several connectors. In this class, adapter can choose from one of several connectors.
antecedentRefs point to dmtfPhysicalConnector objects and
dependentRefs point to dmtfNetworkAdapter objects.
( <oid-oc226> NAME 'dmtfAdapterActiveConnectionAuxClass' ( <oid-oc87> NAME 'cim22AdapterActiveConnectionAuxClass'
DESC 'shows that a NetworkAdapter is using the referenced DESC 'The AdapterActiveConnection relationship indicates that a
PhysicalConnector to output to the network.' NetworkAdapter is using the referenced PhysicalConnector to
SUP dmtfDependencyAuxClass AUXILIARY output to the network. This relationship is important when
the Adapter can choose to output from one of several
Connectors. The Connectors may be associated with the
NetworkAdapter in a Realizes relationship - but this is not
required. This association provides additional information
(i.e., "in use for communication") different than
Realizes. Attribute cimAntecedentRef points to
cim22PhysicalConnector and attribute cimDependentRef points
to cim22NetworkAdapter.'
SUP cim22DependencyAuxClass AUXILIARY
MAY (cimAntecedentRef $ cimDependentRef)
) )
2.43 dmtfComputerSystemPackageAuxClass 3.43 cim22ComputerSystemPackageAuxClass
Similar to the way that physical element 'realize' logical devices, Similar to the way that physical element 'realize' logical devices,
physical packages 'realize' unitary computer systems. This class physical packages 'realize' unitary computer systems. This class
explicitly defines this relationship. In it, antecedentRefs point to explicitly defines this relationship.
dmtfPhysicalPackage objects and dependentRefs point to
dmtfUnitaryComputerSystem objects.
( <oid-at551> NAME 'platformGUID' ( <oid-at168> NAME 'cimPlatformGUID'
DESC 'A Gloabally Unique Identifier for the System's Package.' DESC 'A Gloabally Unique Identifier for the System's Package.'
SYNTAX string SINGLE-VALUE SYNTAX string SINGLE-VALUE
) )
( <oid-oc227> NAME 'dmtfComputerSystemPackageAuxClass' ( <oid-oc88> NAME 'cim22ComputerSystemPackageAuxClass'
DESC 'Similar to the way that LogicalDevices are "Realized" by DESC 'Similar to the way that LogicalDevices are "Realized" by
PhysicalElements, UnitaryComputerSystems are realized in PhysicalElements, UnitaryComputerSystems are realized in
one or more PhysicalPackages. The ComputerSystemPackage one or more PhysicalPackages. The ComputerSystemPackage
association explicitly defines this relationship.' association explicitly defines this relationship. Attribute
SUP dmtfDependencyAuxClass AUXILIARY cimAntecedentRef points to cim22PhysicalPackage and attribute
MUST (platformGUID)
INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
1999
cimDependentRef points to cim22UnitaryComputerSystem.'
SUP cim22DependencyAuxClass AUXILIARY
MAY (cimAntecedentRef $ cimDependentRef $ cimPlatformGUID)
) )
2.44 dmtfLibraryPackageAuxClass 3.44 cim22LibraryPackageAuxClass
Similar to the way that physical element 'realize' logical devices, Similar to the way that physical element 'realize' logical devices,
physical packages 'realize' storage libraries. This class explicitly physical packages 'realize' storage libraries. This class explicitly
defines this relationship, in which antecedentRefs point to defines this relationship.
dmtfPhysicalPackage objects and dependentRefs point to
dmtfStorageLibrary objects.
( <oid-oc228> NAME 'dmtfLibraryPackageAuxClass' ( <oid-oc89> NAME 'cim22LibraryPackageAuxClass'
DESC 'Similar to the way that LogicalDevices are "Realized" by DESC 'Similar to the way that LogicalDevices are "Realized" by
PhysicalElements, a StorageLibrary can be realized in one PhysicalElements, a StorageLibrary can be realized in one
or more PhysicalPackages. This class explicitly defines or more PhysicalPackages. The LibraryPackage association
this relationship.' explicitly defines this relationship. Attribute
SUP dmtfDependencyAuxClass AUXILIARY cimAntecedentRef points to cim22PhysicalPackage and attribute
cimDependentRef points to cim22StorageLibrary.'
SUP cim22DependencyAuxClass AUXILIARY
MAY (cimAntecedentRef $ cimDependentRef)
) )
2.45 dmtfPackageCoolingAuxClass 3.45 cim22PackageCoolingAuxClass
Often, a package includes a cooling device to assist in the cooling Often, a package includes a cooling device to assist in the cooling
of the Package in general. This relationship is described by this of the Package in general. This relationship is described by this
class, in which antecedentRefs point to dmtfCoolingDevice objects and class.
dependentRefs point to dmtfPhysicalPackage objects.
( <oid-oc229> NAME 'dmtfPackageCoolingAuxClass' ( <oid-oc90> NAME 'cim22PackageCoolingAuxClass'
DESC 'Often, a CoolingDevice is installed in a Package such as a DESC 'Often, a CoolingDevice is installed in a Package such as a
Chassis or a Rack, not for a specific Device, but to assist Chassis or a Rack, not for a specific Device, but to assist
in the cooling of the Package in general. This relationship in the cooling of the Package in general. This relationship
is described by this class.' is described by the PackageCooling association. Attribute
SUP dmtfDependencyAuxClass AUXILIARY cimAntecedentRef points to cim22CoolingDevice. Attribute
cimDependentRef points to cim22PhysicalPackage.'
SUP cim22DependencyAuxClass AUXILIARY
MAY (cimAntecedentRef $ cimDependentRef)
) )
2.46 dmtfPackageAlarmAuxClass 3.46 cim22PackageAlarmAuxClass
Often, an alarm device is installed as part of a package, not to Often, an alarm device is installed as part of a package, not to
track any particular logical device or physical component, but the track any particular logical device or physical component, but the
package itself. This relationship is described by this class, where package itself. This relationship is described by this class.
antecedentRefs point to dmtfAlarmDevice objects and dependentRefs
point to dmtfPhysicalPackage objects.
( <oid-oc230> NAME 'dmtfPackageAlarmAuxClass'
DESC 'Often, an AlarmDevice is installed as part of a Package, not
to show issues with any particular LogicalDevice or
PhysicalComponent, but with the Package's environment in
general, its security state or its overall health. This
relationship is described by this class.'
SUP dmtfDependencyAuxClass AUXILIARY
)
3. DIT Content Rules
The following DIT Content Rules apply to objects in this schema.
These content rules reference not only classes in this
draft but classes from other DMTF CIM models [5, 6, 7, 8, 9]
( <oid-oc185> NAME 'dmtfLocationContentRule'
DESC 'shows what auxiliary classes may go with the dmtfLocation
class'
AUX (dmtfPhysicalElementLocationAuxClass)
)
( <oid-oc187> NAME 'dmtfPhysicalCapacityContentRule'
DESC 'shows what auxiliary classes may go with the
dmtfPhysicalCapacity class'
AUX (dmtfElementCapacityAuxClass)
)
( <oid-oc191> NAME 'dmtfReplacementSetContentRule'
DESC 'shows what auxiliary classes may go with the
dmtfReplacementSet class'
AUX (dmtfParticipatesInSetAuxClass)
)
( <oid-oc193> NAME 'dmtfPhysicalPackageContentRule'
DESC 'shows what auxiliary classes may go with the
dmtfPhysicalPackage class'
AUX (dmtfContainerAuxClass $ dmtfPackageInChassisAuxClass $
dmtfPackagedComponentAuxClass $
dmtfPackageInConnectorAuxClass $ dmtfPackageInSlotAuxClass $
dmtfConnectorOnPackageAuxClass $
dmtfComputerSystemPackageAuxClass $
dmtfLibraryPackageAuxClass $ dmtfPackageCoolingAuxClass $
dmtfPackageAlarmAuxClass)
)
( <oid-oc196> NAME 'dmtfRackContentRule'
DESC 'shows what auxiliary classes may go with the dmtfRack
class'
AUX (dmtfChassisInRackAuxClass)
)
( <oid-oc197> NAME 'dmtfChassisContentRule'
DESC 'shows what auxiliary classes may go with the dmtfChassis
class'
AUX (dmtfChassisInRackAuxClass $ dmtfPackageInChassisAuxClass $
dmtfDockedAuxClass)
)
( <oid-oc201> NAME 'dmtfCardContentRule'
DESC 'shows what auxiliary classes may go with the dmtfCard
class'
AUX (dmtfCardOnCardAuxClass $ dmtfMemoryOnCardAuxClass $
dmtfCardInSlotAuxClass)
)
( <oid-oc204> NAME 'dmtfStorageMediaLocationContentRule'
DESC 'shows what auxiliary classes may go with the
dmtfStorageMediaLocation class'
AUX (dmtfPhysicalMediaInLocationAuxClass)
)
( <oid-oc205> NAME 'dmtfPhysicalComponentContentRule'
DESC 'shows what auxiliary classes may go with the
dmtfPhysicalComponent class'
AUX (dmtfPackagedComponentAuxClass)
)
( <oid-oc208> NAME 'dmtfPhysicalMemoryContentRule'
DESC 'shows what auxiliary classes may go with the
dmtfPhysicalMemory class'
AUX (dmtfMemoryOnCardAuxClass $ dmtfMemoryWithMediaAuxClass)
)
( <oid-oc210> NAME 'dmtfPhysicalMediaContentRule'
DESC 'shows what auxiliary classes may go with the
dmtfPhysicalMedia class'
AUX (dmtfMemoryWithMediaAuxClass $
dmtfPhysicalMediaInLocationAuxClass)
)
( <oid-oc214> NAME 'dmtfPhysicalLinkContentRule' ( <oid-oc91> NAME 'cim22PackageAlarmAuxClass'
DESC 'shows what auxiliary classes may go with the DESC 'Often, an AlarmDevice is installed as part of a Package,
dmtfPhysicalLink class' not to indicate issues with any particular LogicalDevice or
AUX (dmtfElementsLinkedAuxClass $ dmtfLinkHasConnectorAuxClass)
)
( <oid-oc216> NAME 'dmtfPhysicalConnectorContentRule' INTERNET DRAFTLDAP Schema for the DMTF Physical CIM v2.2 ModelDecember
DESC 'shows what auxiliary classes may go with the 1999
dmtfPhysicalConnector class'
AUX (dmtfConnectedToAuxClass $ dmtfConnectedToAuxClass $
dmtfPackageInConnectorAuxClass $
dmtfLinkHasConnectorAuxClass $
dmtfConnectorOnPackageAuxClass $
dmtfAdapterActiveConnectionAuxClass $
dmtfAdapterActiveConnectionAuxClass)
)
( <oid-oc218> NAME 'dmtfSlotContentRule' PhysicalComponent, but with the Package's environment in
DESC 'shows what auxiliary classes may go with the dmtfSlot general, its security state or its overall health. This
class' relationship is described by the PackageAlarm
AUX (dmtfSlotInSlotAuxClass $ dmtfAdjacentSlotsAuxClass $ association. Attribute cimAntecedentRef points to
dmtfPackageInSlotAuxClass $ dmtfCardInSlotAuxClass) cim22AlarmDevice and attribute cimDependentRef points to
cim22PhysicalPackage.'
SUP cim22DependencyAuxClass AUXILIARY
MAY (cimAntecedentRef $ cimDependentRef)
) )
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, Decemeber 1997.
[2] M. Wahl, A. Coulbeck, T. Howes, S. Kille, "Lightweight
Directory Access Protocol (v3): Attribute Syntax 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 Physcial 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 Core CIM Model", September 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] DMTF, "CIM Physcial Model, v2.2".
for the DMTF Network CIM Model", October 1999.
[8] Ryan Moats, Gerald Maziarski, John Strassner, "LDAP Schema [5] Ryan Moats, Gerald Maziarski, John Strassner, "LDAP
for the DMTF System CIM Model", October 1999. Schema for the DMTF Core CIM v2.2 Model", Internet
Draft (work in progress), December 1999.
[9] Ryan Moats, Gerald Maziarski, John Strassner, "LDAP Schema [6] Doug Wood, "Directory string representation for
for the DMTF Application CIM Model", October 1999. floating point values", Internet Draft (work in
progress), December 1999.
5. Author's Addresses 5. Author's Addresses
Ryan Moats Jerry Maziarski John Strassner Ryan Moats Jerry Maziarski John Strassner
15621 Drexel Circle Room C3-3Z01 Cisco Systems, Bldg 1 15621 Drexel Circle Room C3-3Z01 Cisco Systems, Bldg 1
Omaha, NE 68135 200 S. Laurel Ave. 170 West Tasman Drive Omaha, NE 68135 200 S. Laurel Ave. 170 West Tasman Drive
USA Middletown, NJ 07748 San Jose, CA 95134 USA Middletown, NJ 07748 San Jose, CA 95134
E-mail: jayhawk@att.com USA E-mail: E-mail: jayhawk@att.com USA E-mail:
johns@cisco.com johns@cisco.com
E-mail: gfm@qsun.att.com E-mail: gfm@qsun.att.com
 End of changes. 307 change blocks. 
839 lines changed or deleted 1480 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/