< draft-moats-dmtf-system-ldap-00.txt   draft-moats-dmtf-system-ldap-01.txt >
Internet-Draft Ryan Moats Internet-Draft Ryan Moats
draft-moats-dmtf-system-ldap-00.txt Gerald Maziarski draft-moats-dmtf-system-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 System CIM Model LDAP Schema for the DMTF System CIM v2.2 Model
Filename: draft-moats-dmtf-system-ldap-00.txt Filename: draft-moats-dmtf-system-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 System model [5]. This draft presents a LDAP schema for the DMTF CIM System model [5].
1. Introduction 1. Introduction
This draft presents a LDAPv3 [1,2] schema for the DMTF CIM System This draft presents a LDAPv3 [1,2] schema for the DMTF CIM System
model. It builds on the core model presented in [3]. Associations model. It builds on the core model presented in [3]. Associations
are mapped using a combination of auxiliary classes and DIT structure are mapped using a combination of auxiliary classes and DIT structure
rules. Where auxiliary classes are used, name form and DIT content rules. Where auxiliary classes are used, name form and DIT content
rules are specified. rules are specified.
2. Class Definitions This document is not a product of the DMTF, and represents the view
of the authors.
For efficiency in the LDAP representation, associations are specified
as a combination of auxiliary classes and DIT structure rules.
Attribute definitions for each class are presented with the object
class. Other definitions are also provided when necessary.
This approach minimizes the number of DN pointers stored in the 2. LDAP Mapping Considerations
schema, but some pointer dereferencing is necessary. While not
explicitly stated in the definitions below, we assume that all
attributes with DN support the matching rule defined in [3].
Attribute names for DN pointers also follow the convention that a
single pointer's name ends in "Ref", while an array of pointers' name
ends in "Refs".
Note: all OIDs are placeholders, and OIDs in definitions have been 2.1 Differences Between this Mapping and the CIM System Model
replaced by names for clarity.
Several classes have attributes removed because they do not make Several classes have attributes removed because they do not make
sense for the directory to store: localDateTime, numberOfUsers, sense for the directory to store: LocalDateTime, NumberOfUsers,
numberOfProcesses, totalSwapSpaceSize, totalVirtualMemorySize, NumberOfProcesses, TotalSwapSpaceSize, TotalVirtualMemorySize,
freeVirtualMemory, freePhysicalMemory, totalVisibleMemorySize, FreeVirtualMemory, FreePhysicalMemory, TotalVisibleMemorySize,
sizeStoredInPagingFiles, freeSpaceInPagingFiles. Further, a SizeStoredInPagingFiles, and FreeSpaceInPagingFiles. Further, a
directory shouldn't store logicalfile information, including directory shouldn't store logicalfile information, including
datafiles, directories, and devices shouldn't be stored Therefore the datafiles, directories, and devices shouldn't be stored Therefore the
DeviceAccessedByFile, DirectoryContainsFile, Mount, Export, and DeviceAccessedByFile, DirectoryContainsFile, Mount, Export, and
FileStorage associations aren't included because referenced pieces FileStorage associations aren't included because referenced pieces
are missing. are missing.
A directory should not store either Process, Thread, Job, or A directory should not store either Process, Thread, Job, or
JobDestination objects. Therefore the associations OSProcess, JobDestination objects. Therefore the associations OSProcess,
ProcessThread, ProcessExecutable, HostedJobDestination, and ProcessThread, ProcessExecutable, HostedJobDestination, and
JobDestinationJobs aren't included either. JobDestinationJobs aren't included either.
2.1 dmtfComponentCSAuxClass 2.2 Changes to cimAssociationInstance
The core mapping [3] defined cimAssociationInstance as a helper
class. To support the auxiliary classes, the following classes
should be added to cimAssociationInstance's content rule:
cim22ComponentCSAuxClass
cim22SystemPartitionAuxClass
cim22HostingCSAuxClass
cim22ParticipatingCSAuxClass
cim22ClusterServiceAccessBySAPAuxClass
cim22BootServiceAccessBySAPAuxClass
cim22RunningOSAuxClass
cim22OperatingSystemSoftwareFeatureAuxClass
cim22BootOSFromFSAuxClass
cim22BIOSFeatureBIOSElementsAuxClass
cim22SystemBIOSAuxClass
Also, the following structure rules defined here need to be added to
the structure rule for cimAssociationInstance: <sr29>, <sr30>,
<sr31>.
2.3 cimCharacteristicsInstance
The class cimBIOSFeature defines two linked indexed arrays:
Characteristics and CharacteristicDescriptions. In the LDAP mapping,
these are replaced with separate instances of
cimCharacteristicsInstance, DIT contained by cimBIOSFeature.
( <oid-at284> NAME 'cimCharacteristics'
DESC 'An integer that specifies the feature supported by the
BIOS. For example, one can specify that PnP capabilities
are provided (value=9) or that infrared devices are
supported (21). Values specified in the enumeration are
taken from both DMI and SMBIOS (the Type 0 structure, the
BIOS Characteristics and BIOS Characteristics Extension
Bytes attributes.'
SYNTAX integer SINGLE-VALUE
)
( <oid-at285> NAME 'cimCharacteristicDescriptions'
DESC 'A free-form string providing more detailed explanations for
any BIOS feature'
SYNTAX string SINGLE-VALUE
)
( <oid-oc157> NAME 'cimCharacteristicsInstance'
DESC 'helper class to tie Characteristics and
CharacteristicDescriptions in BIOSFeature together'
SUP top
MUST (arrayIndex)
MAY (cimCharacteristic $ cimCharacteristicDescription)
)
( <oid-nf32> NAME 'cimCharacteristicsInstanceNameForm'
OC cimCharacteristicsInstance
MUST (arrayIndex)
)
( <sr32> NAME 'cimCharacteristicsInstanceStructureRule'
FORM cimCharacteristicsInstanceNameForm
SUP <sr31>
)
3. Class Definitions
For efficiency in the LDAP representation, associations are specified
as a combination of auxiliary classes and DIT structure rules.
Attribute definitions for each class are presented with the object
class. Other definitions are also provided when necessary.
This approach minimizes the number of DN pointers stored in the
schema, but some pointer dereferencing is necessary. While not
explicitly stated in the definitions below, we assume that all
attributes with DN support the matching rule defined in [4].
Attribute names for DN pointers also follow the convention that a
single pointer's name ends in "Ref", while an array of pointers' name
ends in "Refs".
Note: all attribute, object class, and name form OIDs are place
holders, and syntax OIDs in definitions have been replaced by names
for clarity.
3.1 cim22ComponentCSAuxClass
A ComputerSystem can aggregate another ComputerSystem. This A ComputerSystem can aggregate another ComputerSystem. This
association can be used to model MPP Systems with workstation association can be used to model MPP Systems with workstation
frontends, an I2O subsystem embedded in a UnitaryComputerSystem, or a frontends, an I2O subsystem embedded in a UnitaryComputerSystem, or a
System that splits functionality between two processors, potentially System that splits functionality between two processors, potentially
running different OperatingSystems. For example, if a CISC Processor running different OperatingSystems. For example, if a CISC Processor
and its associated OperatingSystem, are used for user interface and and its associated OperatingSystem, are used for user interface and
file support, and a RISC Processor and its OS are used for complex file support, and a RISC Processor and its OS are used for complex
mathematical operations, this could be modeled as two ComputerSystems mathematical operations, this could be modeled as two ComputerSystems
where one aggregates the other. Sometimes, this could be modeled as a where one aggregates the other. Sometimes, this could be modeled as a
skipping to change at page 3, line 9 skipping to change at page 4, line 34
still distinguishable entities and are only viewed as such. still distinguishable entities and are only viewed as such.
Alternately, with a Cluster, the ComputerSystems that participate in Alternately, with a Cluster, the ComputerSystems that participate in
it are inconsequential, when viewed through the 'Cluster System'. it are inconsequential, when viewed through the 'Cluster System'.
When instantiating or subclassing the ComponentCS relationship, care When instantiating or subclassing the ComponentCS relationship, care
should be taken that the component ComputerSystem meets the should be taken that the component ComputerSystem meets the
definitional requirements of a ComputerSystem - ie, a functional definitional requirements of a ComputerSystem - ie, a functional
whole that provides compute capabilities and aggregates System whole that provides compute capabilities and aggregates System
Devices, an OperatingSystem, etc. Devices, an OperatingSystem, etc.
Lastly, in this class both groupComponentRefs and partComponentRefs ( <oid-oc131> NAME 'cim22ComponentCSAuxClass'
point to dmtfComputerSystem objects. DESC 'A ComputerSystem can aggregate another ComputerSystem. This
association can be used to model MPP Systems with
( <oid-oc159> NAME 'dmtfComponentCSAuxClass' workstation frontends, an I2O subsystem embedded in a
DESC ' This association can be used to model MPP Systems with UnitaryComputerSystem, or a System that splits
workstation frontends, an I2O subsystem embedded in a functionality between two processors, potentially running
UnitaryComputerSystem, or a System that splits different OperatingSystems. For example, if a CISC
functionality between two processors, potentially running Processor and its associated OperatingSystem, are used for
different OperatingSystems.' user interface and file support, and a RISC Processor and
SUP dmtfSystemComponentAuxClass AUXILIARY its OS are used for complex mathematical operations, this
could be modeled as two ComputerSystems where one
aggregates the other. In some cases, this could be modeled
as a Cluster. The difference is the focus of the
relationship. ComponentCS represents that unique and
distinct ComputerSystems are aggregated by a higher level
CS object. However, each of the component CSs are still
distinguishable entities and are only viewed as
such. Alternately, with a Cluster, the ComputerSystems that
participate in it are inconsequential, when viewed through
the "Cluster System". When instantiating or subclassing
the ComponentCS relationship, care should be taken that the
component ComputerSystem meets the definitional
requirements of a ComputerSystem - ie, a functional whole
that provides compute capabilities and aggregates System
Devices, an OperatingSystem, etc. Both attributes
point to cim22ComputerSystem objects.'
SUP cim22SystemComponentAuxClass AUXILIARY
MAY (cimGroupComponentRef $ cimPartComponentRef)
) )
2.2 dmtfUnitaryComputerSystem 3.2 cim22UnitaryComputerSystem
A class derived from ComputerSystem that represents a Desktop, A class derived from ComputerSystem that represents a Desktop,
Mobile, NetPC, Server or other type of a single node Computer System. Mobile, NetPC, Server or other type of a single node Computer System.
This class reuses the attributes powerManagementSupported, ( <oid-at229> NAME 'cimInitialLoadInfo'
powerManagementCapabilities, and wakeUpType. It defines the
attributes initialLoadInfo, lastLoadInfo, resetCapability and
powerState.
( <oid-at410> NAME 'initialLoadInfo'
DESC 'This object contains the data needed to find either the DESC 'This object contains the data needed to find either the
initial load device (its key) or the boot service to initial load device (its key) or the boot service to
request the operating system to start up. In addition, the request the operating system to start up. In addition, the
load parameters (ie, a pathname and parameters) may also be load parameters (ie, a pathname and parameters) may also be
specified.' specified.'
SYNTAX string SYNTAX string
) )
( <oid-at411> NAME 'lastLoadInfo' ( <oid-at230> NAME 'cimLastLoadInfo'
DESC 'This object contains the data identifying either the DESC 'This object contains the data identifying either the
initial load device (its key) or the boot service that initial load device (its key) or the boot service that
requested the last operating system load. In addition, the requested the last operating system load. In addition, the
load parameters (ie, a pathname and parameters) may also be load parameters (ie, a pathname and parameters) may also be
specified.' specified.'
SYNTAX string SINGLE-VALUE SYNTAX string SINGLE-VALUE
) )
( <oid-at412> NAME 'resetCapability' ( <oid-at231> NAME 'cimResetCapability'
DESC 'If enabled (value = 4), the UnitaryComputerSystem can be DESC 'If enabled (value = 4), the UnitaryComputerSystem can be
reset via hardware (e.g. the power and reset buttons). If reset via hardware (e.g. the power and reset buttons). If
disabled (value = 3), hardware reset is not allowed. In disabled (value = 3), hardware reset is not allowed. In
addition to Enabled and Disabled, other Values for the addition to Enabled and Disabled, other Values for the
property are also defined - "Not Implemented""Other" (2).' property are also defined - "Not Implemented" (5), "Other"
(1) and "Unknown" (2).'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at413> NAME 'powerState' ( <oid-at232> NAME 'cimPowerState'
DESC 'Shows the current power state of the ComputerSystem and DESC 'Indicates the current power state of the ComputerSystem and
its associated OperatingSystem. Regarding the Power Save its associated OperatingSystem. Regarding the Power Save
states, these are defined as follows: Value 4 ("Power states, these are defined as follows: Value 4 ("Power Save
Save") shows that the System is known to be in a power - Unknown") indicates that the System is known to be in a
save mode, but its exact status in this mode is unknown; 2 power save mode, but its exact status in this mode is
("Power Save - Low Power Mode"the System is in a power save unknown; 2 ("Power Save - Low Power Mode") indicates that
state but still functioning, and may exhibit degraded the System is in a power save state but still functioning,
performance; 3 ("Power Save -") describes that the System and may exhibit degraded performance; 3 ("Power Save -
is not functioning but could be brought to full power Standby") describes that the System is not functioning but
'quickly'; value 7 ("Power Save") shows that the could be brought to full power "quickly"; value 7 ("Power
ComputerSystem is in a warning state, though also in a Save - Warning") indicates that the ComputerSystem is in a
power save mode; and, values 8 and 9 describe the ACPI warning state, though also in a power save mode; and,
"Hibernate" states. Allowed values are: "Unknown", "Full values 8 and 9 describe the ACPI "Hibernate" and "Soft Off"
Power", "Power Save - Low Power Mode", "Power Save - states.'
Standby", "Power Save - Unknown", "Power Cycle", "Power SYNTAX integer SINGLE-VALUE
Off", "Power Save - Warning", "Power Save - Hibernate",
"Power Save - Soft Off".'
SYNTAX integer SINGLE-VALUE
) )
( <oid-oc160> NAME 'dmtfUnitaryComputerSystem' ( <oid-at233> NAME 'cimWakeUpType'
DESC 'The event that caused the System to power up. This
information is available in SMBIOS, in the Type 1
structure, the Wake Up Type attribute.'
SYNTAX integer SINGLE-VALUE
)
( <oid-oc132> NAME 'cim22UnitaryComputerSystem'
DESC 'A class derived from ComputerSystem that represents a DESC 'A class derived from ComputerSystem that represents a
Desktop, Mobile, NetPC, Server or other type of a single Desktop, Mobile, NetPC, Server or other type of a single
node Computer System.' node Computer System.'
SUP dmtfComputerSystem SUP cim22ComputerSystem
MUST (initialLoadInfo $ lastLoadInfo $ resetCapability $ MAY (cimInitialLoadInfo $ cimLastLoadInfo $ cimResetCapability $
powerManagementSupported $ powerManagementCapabilities $ cimPowerManagementSupported $ cimPowerState $ cimWakeUpType $
powerState $ wakeUpType) cimPowerManagementCapabilities)
) )
2.3 dmtfSystemPartitionAuxClass The following content rule specifies the auxiliary classes that may
be attached to cim22UnitaryComputerSystem.
( <oid-oc132> NAME 'cim22UnitaryComputerSystemContentRule'
DESC 'The auxiliary classes that may be attached to
cim22UnitaryComputerSystem'
AUX (cim22SystemPartitionAuxClass $ cim22SystemBIOSAuxClass)
)
3.3 cim22SystemPartitionAuxClass
A Partition is an instance of a UnitaryComputerSystem (with its own A Partition is an instance of a UnitaryComputerSystem (with its own
OperatingSystem and Devices dedicated to the Partition) that is OperatingSystem and Devices dedicated to the Partition) that is
supported by underlying hardware and software. A Partition is not a supported by underlying hardware and software. A Partition is not a
virtualization of a ComputerSystem, but the segmentation of the virtualization of a ComputerSystem, but the segmentation of the
System's compute capabilities. Partitions can run independent copies System's compute capabilities. Partitions can run independent copies
of possibly different OperatingSystems and have dedicated Devices. of possibly different OperatingSystems and have dedicated Devices.
The 'real', underlying System (perhaps a Cluster or another The 'real', underlying System (perhaps a Cluster or another
UnitaryComputerSystem) aggregates its Partitions. These semantics are UnitaryComputerSystem) aggregates its Partitions. These semantics are
described by the SystemPartition association.' described by the SystemPartition association.'
In this class, groupComponentRefs point to dmtfComputerSystem objects
and partComponentRefs point to dmtfUnitaryComputerSystem objects.
( <oid-oc161> NAME 'dmtfSystemPartitionAuxClass' ( <oid-oc133> NAME 'cim22SystemPartitionAuxClass'
DESC 'A Partition is an instance of a UnitaryComputerSystem (with DESC 'A Partition is an instance of a UnitaryComputerSystem (with
its own OperatingSystem and Devices dedicated to the its own OperatingSystem and Devices dedicated to the
Partition) that is supported by underlying hardware and Partition) that is supported by underlying hardware and
software.' software. A Partition is not a virtualization of a
SUP dmtfComponentCSAuxClass AUXILIARY ComputerSystem, but the segmentation of the System's
compute capabilities. Partitions can run independent copies
of possibly different OperatingSystems and have dedicated
Devices. The "real", underlying System (perhaps a Cluster
or another UnitaryComputerSystem) aggregates its
Partitions. These semantics are described by the
SystemPartition association. Attribute cimGroupComponentRef
points to cim22ComputerSystem and attribute
cimPartComponentRef points to cim22UnitaryComputerSystem.'
SUP cim22ComponentCSAuxClass AUXILIARY
MAY (cimGroupComponentRef $ cimPartComponentRef)
) )
2.4 dmtfVirtualComputerSystem 3.4 cim22VirtualComputerSystem
A string describing the type of System or hardware platform that is A string describing the type of System or hardware platform that is
virtualized. OperatingSystem information is obtained via the virtualized. OperatingSystem information is obtained via the
RunningOS inherited from ComputerSystem. This class defines the RunningOS inherited from ComputerSystem.
attribute virtualSystem.
( <oid-at414> NAME 'virtualSystem' ( <oid-at234> NAME 'cimVirtualSystem'
DESC 'A string describing the type of System or hardware platform DESC 'A string describing the type of System or hardware platform
that is virtualized. OperatingSystem information is that is virtualized. OperatingSystem information is
obtained via the RunningOS inherited from ComputerSystem.' obtained via the RunningOS inherited from ComputerSystem.'
SYNTAX string SINGLE-VALUE SYNTAX string SINGLE-VALUE
) )
( <oid-oc162> NAME 'dmtfVirtualComputerSystem' ( <oid-oc134> NAME 'cim22VirtualComputerSystem'
DESC 'A class derived from ComputerSystem that represents the DESC 'A class derived from ComputerSystem that represents the
ability to virtualize or emulate another ComputerSystem.' ability to virtualize or emulate another ComputerSystem.'
SUP dmtfComputerSystem SUP cim22ComputerSystem
MUST (virtualSystem) MAY (cimVirtualSystem)
) )
2.5 dmtfHostingCSAuxClass The following content rule specifies the auxiliary classes that may
be attached to cim22VirtualComputerSystem.
( <oid-oc134> NAME 'cim22VirtualComputerSystemContentRule'
DESC 'The auxiliary classes that may be attached to
cim22VirtualComputerSystem'
AUX (cim22HostingCSAuxClass)
)
3.5 cim22HostingCSAuxClass
A VirtualComputerSystem is hosted on another ComputerSystem. This A VirtualComputerSystem is hosted on another ComputerSystem. This
association makes that relationship explicit. In this class, association makes that relationship explicit.
antecedentRefs point to dmtfComputerSystem objects and dependentRefs
point to dmtfVirtualComputerSystem objects.
( <oid-oc163> NAME 'dmtfHostingCSAuxClass' ( <oid-oc135> NAME 'cim22HostingCSAuxClass'
DESC 'This association makes the hosting relationship between a DESC 'A VirtualComputerSystem is hosted on another
computer system and a virtual computer system explicit.' ComputerSystem. This association makes that relationship
SUP dmtfDependencyAuxClass AUXILIARY explicit. Attribute cimAntecedentRef points to
cim22ComputerSystem and attribute cimDependentRef points to
cim22VirtualComputerSystem.'
SUP cim22DependencyAuxClass AUXILIARY
MAY (cimAntecedentRef $ cimDependentRef)
) )
2.6 dmtfCluster 3.6 cim22Cluster
A class derived from ComputerSystem that is made up of two or more A class derived from ComputerSystem that is made up of two or more
ComputerSystems that operate together as an atomic, functional whole ComputerSystems that operate together as an atomic, functional whole
to increase the performance, resources and/or RAS (Reliability, to increase the performance, resources and/or RAS (Reliability,
Availability and Serviceability) of the component ComputerSystems, Availability and Serviceability) of the component ComputerSystems,
related to some aspects of these ComputerSystems. related to some aspects of these ComputerSystems.
This class defines the attributes interconnect, interconnectAddress, ( <oid-at235> NAME 'cimInterconnect'
types, maxNumberOfNodes, and clusterState.
( <oid-at415> NAME 'interconnect'
DESC 'Interconnect is a free form string that describes the DESC 'Interconnect is a free form string that describes the
interconnection mechanism for the Cluster.' interconnection mechanism for the Cluster.'
SYNTAX string SINGLE-VALUE SYNTAX string SINGLE-VALUE
) )
( <oid-at416> NAME 'interconnectAddress' ( <oid-at236> NAME 'cimInterconnectAddress'
DESC 'InterconnectAddress shows the address of the Cluster DESC 'InterconnectAddress indicates the address of the Cluster
System, which is dependent on the interconnection System, which is dependent on the interconnection
scheme. If no address is available or applicable, a null scheme. If no address is available or applicable, a null
string should be used.' string should be used.'
SYNTAX string SINGLE-VALUE SYNTAX string SINGLE-VALUE
) )
( <oid-at417> NAME 'types' ( <oid-at237> NAME 'cimTypes'
DESC 'The cluster types. This specifies whether the cluster is DESC 'The cluster types. This specifies whether the cluster is
for failover (value=2), performance (3), etc. The values for failover (value=2), performance (3), etc. The values
which can be specified are not mutually exclusive. Thus, which can be specified are not mutually exclusive. Thus,
Types is an array. Allowed values are: "Unknown", "Other", Types is an array.'
"Failover", "Performance", "Distributed OS", "Node
Grouping", "SysPlex".'
SYNTAX integer SYNTAX integer
) )
( <oid-at238> NAME 'cimMaxNumberOfNodes'
( <oid-at418> NAME 'maxNumberOfNodes' DESC 'Indicates the maximum number of nodes that may participate
DESC 'Shows the maximum number of nodes that may participate in the Cluster. If unlimited, enter 0.'
in the Cluster. If unlimited, enter 0.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at419> NAME 'clusterState' ( <oid-at239> NAME 'cimClusterState'
DESC 'Shows the state of the Cluster. The cluster can be DESC 'Indicates the state of the Cluster. The cluster can be
defined to be on-line (value=2), off-line (3), in a defined to be on-line (value=2), off-line (3), in a
degraded mode of operation (4) or unavailable (5). Allowed degraded mode of operation (4) or unavailable (5).'
values are: "Unknown", "Other", "On-line", "Off-line",
"Degraded", "Unavailable".'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-oc164> NAME 'dmtfCluster' ( <oid-oc136> NAME 'cim22Cluster'
DESC 'A class derived from ComputerSystem that "is made up of" DESC 'A class derived from ComputerSystem that "is made up of"
two or more ComputerSystems that operate together as an two or more ComputerSystems which operate together as an
atomic, functional whole to increase the performance, atomic, functional whole to increase the performance,
resources and/or RAS (Reliability, Availability and resources and/or RAS (Reliability, Availability and
Serviceability) of the component ComputerSystems, related Serviceability) of the component ComputerSystems, related
to some aspects of these ComputerSystems.' to some aspects of these ComputerSystems.'
SUP dmtfComputerSystem SUP cim22ComputerSystem
MUST (interconnect $ interconnectAddress $ types $ MAY (cimInterconnect $ cimInterconnectAddress $ cimTypes $
maxNumberOfNodes $ clusterState) cimMaxNumberOfNodes $ cimClusterState)
) )
2.7 dmtfParticipatingCSAuxClass The following content rule specifies the auxiliary classes that may
be attached to cim22Cluster.
( <oid-oc136> NAME 'cim22ClusterContentRule'
DESC 'The auxiliary classes that may be attached to cim22Cluster'
AUX (cim22ParticipatingCSAuxClass)
)
3.7 cim22ParticipatingCSAuxClass
A Cluster is composed of two or more ComputerSystems, operating A Cluster is composed of two or more ComputerSystems, operating
together. A ComputerSystem may participate in multiple Clusters. together. A ComputerSystem may participate in multiple Clusters.
This class defines the attributes stateOfNode and roleOfNode. In ( <oid-at240> NAME 'cimStateOfNode'
addition, antecedentRefs point to dmtfComputerSystem objects and DESC 'StateOfNode indicates the condition of the participating
dependentRefs point to dmtfCluster objects. ComputerSystem in the Cluster. For example, one value is
"Joining" (2).'
( <oid-at420> NAME 'stateOfNode'
DESC 'StateOfNode shows the condition of the participating
ComputerSystem in the Cluster. For example, one value is
"Joining". Allowed values are: "Unknown", "Other",
"Joining", "Paused", "Available", "Unavailable",
"Degraded".'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at421> NAME 'roleOfNode' ( <oid-at241> NAME 'cimRoleOfNode'
DESC 'RoleOfNode shows whether the Cluster nodes are peers DESC 'RoleOfNode indicates whether the Cluster nodes are peers
(value = 2), connected in a master-slave/primary-secondary (value = 2), connected in a master-slave/primary-secondary
relationship (values = 3 for primary, 4 for secondary), relationship (values = 3 for primary, 4 for secondary),
available in a standby configuration (5) or of some other available in a standby configuration (5) or of some other
(1) or unknown (0) relationship. In a System/390 (1) or unknown (0) relationship. In a System/390
environment, the nodes are identified as "Base" (value=6) environment, the nodes are identified as "Base Plex"
or "Enhanced Plex". Allowed values are: "Unknown", (value=6) or "Enhanced Plex" (value=7).'
"Other", "Peer", "Primary", "Secondary", "Standby", "Base
Plex", "Enhanced Plex".'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-oc165> NAME 'dmtfParticipatingCSAuxClass' ( <oid-oc137> NAME 'cim22ParticipatingCSAuxClass'
DESC 'A Cluster is composed of two or more ComputerSystems, DESC 'A Cluster is composed of two or more ComputerSystems,
operating together.' operating together. A ComputerSystem may participate in
multiple Clusters. When first establishing or bringing up a
SUP dmtfDependencyAuxClass AUXILIARY Cluster, only one ComputerSystem may be defined as
MUST (stateOfNode $ roleOfNode) participating in it. Attribute cimAntecedentRef points to
cim22ComputerSystem and attribute cimDependentRef points to
cim22Cluster.'
SUP cim22DependencyAuxClass AUXILIARY
MAY (cimAntecedentRef $ cimDependentRef $ cimStateOfNode $
cimRoleOfNode)
) )
2.8 dmtfClusteringService 3.8 cim22ClusteringService
This class represents the functionality provided by a Cluster. For This class represents the functionality provided by a Cluster. For
example, failover functionality may be modeled as a Service of a example, failover functionality may be modeled as a Service of a
failover Cluster. failover Cluster.
( <oid-oc166> NAME 'dmtfClusteringService' ( <oid-oc138> NAME 'cim22ClusteringService'
DESC 'ClusteringService represents the functionality provided by DESC 'ClusteringService represents the functionality provided by
a Cluster.' a Cluster. For example, failover functionality may be
SUP dmtfService modeled as a Service of a failover Cluster.'
SUP cim22Service
) )
2.9 dmtfClusteringSAP The following content rule specifies the auxiliary classes that may
be attached to cim22ClusteringService.
( <oid-oc138> NAME 'cim22ClusteringServiceContentRule'
DESC 'The auxiliary classes that may be attached to
cim22ClusteringService'
AUX (cim22ClusterServiceAccessBySAPAuxClass)
)
3.9 cim22ClusteringSAP
This class is a representation of the access points of a clustering This class is a representation of the access points of a clustering
service. service.
( <oid-oc167> NAME 'dmtfClusteringSAP' ( <oid-oc139> NAME 'cim22ClusteringSAP'
DESC 'A representation of the access points of a DESC 'A representation of the access points of a
ClusteringService.' ClusteringService.'
SUP dmtfServiceAccessPoint SUP cim22ServiceAccessPoint
) )
2.10 dmtfClusterServiceAccessBySAPAuxClass The following content rule specifies the auxiliary classes that may
be attached to cim22ClusteringSAP.
( <oid-oc139> NAME 'cim22ClusteringSAPContentRule'
DESC 'The auxiliary classes that may be attached to
cim22ClusteringSAP'
AUX (cim22ClusterServiceAccessBySAPAuxClass)
)
3.10 cim22ClusterServiceAccessBySAPAuxClass
This class handles the relationship between a ClusteringService and This class handles the relationship between a ClusteringService and
its access points. In this class, antecedentRefs point to its access points.
dmtfClusteringService objects and dependentRefs point to
dmtfCusteringSAP objects.
( <oid-oc168> NAME 'dmtfClusterServiceAccessBySAPAuxClass' ( <oid-oc140> NAME 'cim22ClusterServiceAccessBySAPAuxClass'
DESC 'the relationship between a ClusteringService and its access DESC 'ClusterServiceAccessBySAP is the relationship between a
points.' ClusteringService and its access points. Attribute
SUP dmtfServiceAccessBySAPAuxClass AUXILIARY cimAntecedentRef points to cim22ClusteringService and
attribute cimDependentRef points to cim22ClusteringSAP.'
SUP cim22ServiceAccessBySAPAuxClass AUXILIARY
MAY (cimAntecedentRef $ cimDependentRef)
) )
2.11 dmtfBootService 3.11 cim22BootService
This class represents the functionality provided by a Device, This class represents the functionality provided by a Device,
software or via a Network to load an Operating System on a software or via a Network to load an Operating System on a
UnitaryComputerSystem. UnitaryComputerSystem.
( <oid-oc169> NAME 'dmtfBootService' ( <oid-oc141> NAME 'cim22BootService'
DESC 'represents the functionality provided by a Device, software DESC 'BootService represents the functionality provided by a
or via a Network to load an Operating System on a Device, software or via a Network to load an Operating
UnitaryComputerSystem.' System on a UnitaryComputerSystem.'
SUP dmtfService SUP cim22Service
) )
2.12 dmtfBootSAP The following content rule specifies the auxiliary classes that may
be attached to cim22BootService.
( <oid-oc141> NAME 'cim22BootServiceContentRule'
DESC 'The auxiliary classes that may be attached to
cim22BootService'
AUX (cim22BootServiceAccessBySAPAuxClass)
)
3.12 cim22BootSAP
This class represents the access points of a boot service. This class represents the access points of a boot service.
( <oid-oc170> NAME 'dmtfBootSAP' ( <oid-oc142> NAME 'cim22BootSAP'
DESC 'representation of the access points of a BootService.' DESC 'A representation of the access points of a BootService.'
SUP dmtfServiceAccessPoint SUP cim22ServiceAccessPoint
) )
2.13 dmtfBootServiceAccessBySAPAuxClass The following content rule specifies the auxiliary classes that may
be attached to cim22BootSAP.
( <oid-oc142> NAME 'cim22BootSAPContentRule'
DESC 'The auxiliary classes that may be attached to cim22BootSAP'
AUX (cim22BootServiceAccessBySAPAuxClass)
)
3.13 cim22BootServiceAccessBySAPAuxClass
This class describes the relationship between a BootService and its This class describes the relationship between a BootService and its
access points. In it, antecedentRefs point to dmtfBootService access points.
objects and dependentRefs point to dmtfBootSAP objects.
( <oid-oc171> NAME 'dmtfBootServiceAccessBySAPAuxClass' ( <oid-oc143> NAME 'cim22BootServiceAccessBySAPAuxClass'
DESC 'the relationship between a BootService and its access DESC 'BootServiceAccessBySAP is the relationship between a
points.' BootService and its access points. Attribute
SUP dmtfServiceAccessBySAPAuxClass AUXILIARY cimAntecedentRef points to cim22BootService and attribute
cimDependentRef points to cim22BootSAP.'
SUP cim22ServiceAccessBySAPAuxClass AUXILIARY
MAY (cimAntecedentRef $ cimDependentRef)
) )
2.14 dmtfStorageLibrary 3.14 cim22StorageLibrary
A StorageLibrary is a collection of ManagedSystemElements that A StorageLibrary is a collection of ManagedSystemElements that
operate together to provide cartridge library capabilities. This operate together to provide cartridge library capabilities. This
object serves as an aggregation point to group the following object serves as an aggregation point to group the following
elements: MediaTransferDevices, a LabelReader, a library Door, elements: MediaTransferDevices, a LabelReader, a library Door,
MediaAccessDevices, and other Library components. MediaAccessDevices, and other Library components.
This class reuses the attribute capabilities and defines the ( <oid-at242> NAME 'cimCapabilities'
attributes overfilled, auditNeeded, auditInProgress, maxAuditTime, DESC 'Capabilities of the StorageLibrary. For example, it can be
and automated. indicated that the Library can perform automatic cleaning
( <oid-at422> NAME 'overfilled' of the MediaAccessDevices contained in it (value=1) or that
the Library provides physical door access for an operator
(value=2).'
SYNTAX integer
)
( <oid-at243> NAME 'cimOverfilled'
DESC 'Boolean set to TRUE if there are more PhysicalMedia in a DESC 'Boolean set to TRUE if there are more PhysicalMedia in a
Library than there are StorageMediaLocations to contain Library than there are StorageMediaLocations to contain
them. For instance, if all MediaAccessDevices have a Media them. For instance, if all MediaAccessDevices have a Media
loaded in them, and all StorageMediaLocations are loaded by loaded in them, and all StorageMediaLocations are loaded by
an operator, then an Overfilled condition exists.' an operator, then an Overfilled condition exists.'
SYNTAX boolean SINGLE-VALUE SYNTAX boolean SINGLE-VALUE
) )
( <oid-at423> NAME 'auditNeeded' ( <oid-at244> NAME 'cimAuditNeeded'
DESC 'Boolean set to TRUE if the Library can not currently report DESC 'Boolean set to TRUE if the Library can not currently report
the correct state of each PhysicalMedia within its proper the correct state of each PhysicalMedia within its proper
StorageMediaLocation.' StorageMediaLocation.'
SYNTAX boolean SINGLE-VALUE SYNTAX boolean SINGLE-VALUE
) )
( <oid-at424> NAME 'auditInProgress' ( <oid-at245> NAME 'cimAuditInProgress'
DESC 'Boolean set to TRUE if an audit of the location of some or DESC 'Boolean set to TRUE if an audit of the location of some or
all the Library's PhysicalMedia is currently being all of the Library's PhysicalMedia is currently being
performed. That an individual Changer is currently doing an performed. That an individual Changer is currently doing an
audit is shown by a similar AuditInProgress boolean audit is indicated by a similar AuditInProgress boolean
property on the Changer object.' property on the Changer object.'
SYNTAX boolean SINGLE-VALUE SYNTAX boolean SINGLE-VALUE
) )
( <oid-at425> NAME 'maxAuditTime' ( <oid-at246> NAME 'cimMaxAuditTime'
DESC 'Maximum time in seconds that it takes for the DESC 'Maximum time in seconds that it takes for the
StorageLibrary to do a complete audit of each StorageLibrary to perform a complete audit of each
StorageMediaLocation, to determine the absence or presence StorageMediaLocation, to determine the absence or presence
of a PhysicalMedia. If automated support is not provided, of a PhysicalMedia. If automated support is not provided,
then this property's value is undefined.' then this property's value is undefined.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at426> NAME 'automated' ( <oid-at247> NAME 'cimAutomated'
DESC 'Boolean set to TRUE if the Library includes a robotics DESC 'Boolean set to TRUE if the Library includes a robotics
mechanism that can be controlled by a ComputerSystem, to mechanism that can be controlled by a ComputerSystem, to
automatically load and unload PhysicalMedia to/from automatically load and unload PhysicalMedia to/from
MediaAccessDevices and StorageMediaLocations. The property MediaAccessDevices and StorageMediaLocations. The property
is set to FALSE if the Library represents a repository of is set to FALSE if the Library represents a repository of
Media that are inaccessible to a MediaAccessDevice without Media that are inaccessible to a MediaAccessDevice without
human intervention. An example of a non-automated Library human intervention. An example of a non-automated Library
is a "shelf" or "vault" where PhysicalMedia are kept for is a "shelf" or "vault" where PhysicalMedia are kept for
extended periods of time.' extended periods of time.'
SYNTAX boolean SINGLE-VALUE SYNTAX boolean SINGLE-VALUE
) )
( <oid-oc144> NAME 'cim22StorageLibrary'
( <oid-oc172> NAME 'dmtfStorageLibrary'
DESC 'A StorageLibrary is a collection of ManagedSystemElements DESC 'A StorageLibrary is a collection of ManagedSystemElements
that operate together to provide cartridge library that operate together to provide cartridge library
capabilities.' capabilities. This object serves as an aggregation point to
SUP dmtfSystem group the following elements: MediaTransferDevices, a
MUST (capabilities $ overfilled $ auditNeeded $ auditInProgress $ LabelReader, a library Door, MediaAccessDevices, and other
maxAuditTime $ automated) Library components.'
SUP cim22System
MAY (cimCapabilities $ cimOverfilled $ cimAuditNeeded $
cimAuditInProgress $ cimMaxAuditTime $ cimAutomated)
) )
2.15 dmtfOperatingSystem 3.15 cim22OperatingSystem
An OperatingSystem is software/firmware that makes a ComputerSystem's An OperatingSystem is software/firmware that makes a ComputerSystem's
hardware usable, and implements and/or manages the resources, file hardware usable, and implements and/or manages the resources, file
systems, processes, user interfaces, and services available on the systems, processes, user interfaces, and services available on the
ComputerSystem.' ComputerSystem.
This class reuses the attributes cSCreationClassName, cSName, ( <oid-at248> NAME 'cimCSCreationClassName'
creationClassName, name, and version. Further, it defines the DESC 'The scoping ComputerSystem's CreationClassName.'
attributes oSType, otherTypeDescription, lastBootUpTime, SYNTAX string{256} SINGLE-VALUE
currentTimeZone, numberOfLicensedUsers, maxNumberOfProcesses,
maxProcessMemorySize, distributed, and primaryOS.
( <oid-at427> NAME 'oSType'
DESC 'A integer indicating the type of OperatingSystem. Allowed
values are: "Unknown", "Other", "MACOS", "ATTUNIX", "DGUX",
"DECNT", "Digital Unix", "OpenVMS", "HPUX", "AIX", "MVS",
"OS400", "OS/2", "JavaVM", "MSDOS", "WIN3x", "WIN95",
"WIN98", "WINNT", "WINCE", "NCR3000", "NetWare", "OSF",
"DC/OS", "Reliant UNIX", "SCO UnixWare", "SCO OpenServer",
"Sequent", "IRIX", "Solaris", "SunOS", "U6000", "ASERIES",
"TandemNSK", "TandemNT", "BS2000", "LINUX", "Lynx",
"XENIX", "VM/ESA", "Interactive UNIX", "BSDUNIX",
"FreeBSD", "NetBSD", "GNU Hurd", "OS9", "MACH Kernel",
"Inferno", "QNX", "EPOC", "IxWorks", "VxWorks", "MiNT",
"BeOS", "HP MPE", "NextStep", "PalmPilot", "Rhapsody",
"Windows 2000", "Dedicated", "OS/390", "VSE", "TPF".
SYNTAX integer SINGLE-VALUE
) )
( <oid-at428> NAME 'otherTypeDescription' ( <oid-at249> NAME 'cimCSName'
DESC 'A string describing the manufacturer and OperatingSystem DESC 'The scoping ComputerSystem's Name.'
type - used when the OperatingSystem property, OSType, is SYNTAX string{256} SINGLE-VALUE
set to 1 or 59 ("Other"). The format of the string inserted
in OtherTypeDescription should be similar in format to the
Values strings defined for OSType. OtherTypeDescription
should be set to NULL when OSType is any value other than 1
or 59.'
SYNTAX string{64} SINGLE-VALUE
) )
( <oid-at429> NAME 'lastBootUpTime' ( <oid-at250> NAME 'cimOSType'
DESC 'A integer indicating the type of OperatingSystem.'
SYNTAX integer SINGLE-VALUE
)
( <oid-at251> NAME 'cimLastBootUpTime'
DESC 'Time when the OperatingSystem was last booted.' DESC 'Time when the OperatingSystem was last booted.'
SYNTAX generalizedTime SINGLE-VALUE SYNTAX generalizedTime SINGLE-VALUE
) )
( <oid-at430> NAME 'currentTimeZone' ( <oid-at252> NAME 'cimCurrentTimeZone'
DESC 'CurrentTimeZone shows the number of minutes the DESC 'CurrentTimeZone indicates the number of minutes the
OperatingSystem is offset from Greenwich Mean Time. Either OperatingSystem is offset from Greenwich Mean Time. Either
the number is positive, negative or zero.' the number is positive, negative or zero.'
SYNTAX binary SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at431> NAME 'numberOfLicensedUsers' ( <oid-at253> NAME 'cimNumberOfLicensedUsers'
DESC 'Number of user licenses for the OperatingSystem. If DESC 'Number of user licenses for the OperatingSystem. If
unlimited, enter 0.' unlimited, enter 0.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at432> NAME 'maxNumberOfProcesses' ( <oid-at254> NAME 'cimMaxNumberOfProcesses'
DESC 'Maximum number of process contexts the OperatingSystem can DESC 'Maximum number of process contexts the OperatingSystem can
support. If there is no fixed maximum, the value should be support. If there is no fixed maximum, the value should be
0. On systems that have a fixed maximum, this object can 0. On systems that have a fixed maximum, this object can
help diagnose failures that occur when the maximum is help diagnose failures that occur when the maximum is
reached.' reached.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at433> NAME 'maxProcessMemorySize' ( <oid-at255> NAME 'cimMaxProcessMemorySize'
DESC 'Maximum number of Kbytes of memory that can be allocated to DESC 'Maximum number of Kbytes of memory that can be allocated to
a Process.' a Process. For Operating Systems with no virtual memory,
this value is typically equal to the total amount of
physical Memory minus memory used by the BIOS and OS. For
some Operating Systems, this value may be infinity - in
which case, 0 should be entered. In other cases, this value
could be a constant - for example, 2G or 4G.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at434> NAME 'distributed' ( <oid-at256> NAME 'cimDistributed'
DESC 'Boolean indicating whether the OperatingSystem is DESC 'Boolean indicating whether the OperatingSystem is
distributed across several ComputerSystem nodes. If so, distributed across several ComputerSystem nodes. If so,
these nodes should be grouped as a Cluster.' these nodes should be grouped as a Cluster.'
SYNTAX boolean SINGLE-VALUE SYNTAX boolean SINGLE-VALUE
) )
( <oid-at435> NAME 'primaryOS' ( <oid-at257> NAME 'cimPrimaryOS'
DESC 'Boolean indicating that the OperatingSystem is the default DESC 'Boolean indicating that the OperatingSystem is the default
OS for the ComputerSystem.' OS for the ComputerSystem.'
SYNTAX boolean SINGLE-VALUE SYNTAX boolean SINGLE-VALUE
) )
( <oid-oc173> NAME 'dmtfOperatingSystem' ( <oid-oc145> NAME 'cim22OperatingSystem'
DESC 'An OperatingSystem is software/firmware that makes a DESC 'An OperatingSystem is software/firmware that makes a
Computer Systems hardware usable.' ComputerSystem's hardware usable, and implements and/or
SUP dmtfLogicalElement manages the resources, file systems, processes, user
MUST (cSCreationClassName $ cSName $ creationClassName $ name $ interfaces, services, ... available on the ComputerSystem.'
oSType $ otherTypeDescription $ version $ lastBootUpTime $ SUP cim22LogicalElement
currentTimeZone $ numberOfLicensedUsers $ primaryOS $ MUST (cimCSCreationClassName $ cimCSName $ cimCreationClassName $
maxNumberOfProcesses $ maxProcessMemorySize $ distributed) cimName)
) MAY (cimOSType $ cimOtherTypeDescription $ cimVersion $
cimLastBootUpTime $ cimCurrentTimeZone $
Altough csCreationClassName and csName may be used as RDNs for this cimNumberOfLicensedUsers $ cimMaxNumberOfProcesses $
class, the solution used in the schema is to require that this class cimMaxProcessMemorySize $ cimDistributed $ cimPrimaryOS)
follow the containment and name form rules below.
( 22 NAME 'dmtfOperatingSystemStructureRule1'
FORM dmtfOperatingSystemNameForm1
SUP 24 25
)
( <oid-nf22> NAME 'dmtfOperatingSystemNameForm1'
OC dmtfOperatingSystem
MUST (creationClassName)
)
( 23 NAME 'dmtfOperatingSystemStructureRule2'
FORM dmtfOperatingSystemNameForm2
SUP 24 25
)
( <oid-nf23> NAME 'dmtfOperatingSystemNameForm2'
OC dmtfOperatingSystem
MUST (name)
) )
( 24 NAME 'dmtfComputerSystemStructureRule1' ( <oid-nf29> NAME 'cim22OperatingSystemNameForm'
FORM dmtfComputerSystemNameForm1 OC cim22OperatingSystem
MUST (orderedCimModelPath)
) )
( <oid-nf24> NAME 'dmtfComputerSystemNameForm1' ( <sr29> NAME 'cim22OperatingSystemStructureRule'
OC dmtfComputerSystem FORM cim22OperatingSystemNameForm
MUST (creationClassName) SUP <sr11>
) )
( 25 NAME 'dmtfComputerSystemStructureRule2' The following content rule specifies the auxiliary classes that may
FORM dmtfComputerSystemNameForm2 be attached to cim22OperatingSystem.
)
( <oid-nf25> NAME 'dmtfComputerSystemNameForm2' ( <oid-oc145> NAME 'cim22OperatingSystemContentRule'
OC dmtfComputerSystem DESC 'The auxiliary classes that may be attached to
MUST (name) cim22OperatingSystem'
AUX (cim22RunningOSAuxClass $
cim22OperatingSystemSoftwareFeatureAuxClass $
cim22BootOSFromFSAuxClass $ cim22LogicalIdentityAuxClass $
cim22CollectedMSEsAuxClass $
cim22ElementConfigurationAuxClass $
cim22ElementSettingAuxClass $ cim22DependencyAuxClass $
cim22ProvidesServiceToElementAuxClass $
cim22ComponentAuxClass $ cim22SystemComponentAuxClass)
) )
2.16 dmtfRunningOSAuxClass 3.16 cim22RunningOSAuxClass
This class shows the currently executing OperatingSystem. At most one This class shows the currently executing OperatingSystem. At most one
OperatingSystem can execute at any time on a ComputerSystem. 'At most OperatingSystem can execute at any time on a ComputerSystem. 'At most
one' is specified, since the ComputerSystem may not be currently one' is specified, since the ComputerSystem may not be currently
booted, or its OperatingSystem may be unknown. booted, or its OperatingSystem may be unknown.
In this class antecedentRefs point to dmtfOperatingSystem objects and ( <oid-oc146> NAME 'cim22RunningOSAuxClass'
dependentRefs point to dmtfComputerSystem objects. DESC 'RunningOS indicates the currently executing
OperatingSystem. At most one OperatingSystem can execute at
( <oid-oc174> NAME 'dmtfRunningOSAuxClass' any time on a ComputerSystem. "At most one" is specified,
DESC 'RunningOS shows the currently executing since the ComputerSystem may not be currently booted, or
OperatingSystem.' its OperatingSystem may be unknown. Attribute
SUP dmtfDependencyAuxClass AUXILIARY cimAntecedentRef points to cim22OperatingSystem and attribute
cimDependentRef points to cim22ComputerSystem.'
SUP cim22DependencyAuxClass AUXILIARY
MAY (cimAntecedentRef $ cimDependentRef)
) )
2.17 dmtfOperatingSystemSoftwareFeatureAuxClass 3.17 cim22OperatingSystemSoftwareFeatureAuxClass
Shows the SoftwareFeatures that make up the OperatingSystem. The Shows the SoftwareFeatures that make up the OperatingSystem. The
SoftwareFeatures can be part of different Products. SoftwareFeatures can be part of different Products.
In this class groupComponentRefs point to dmtfOperatingSystem objects ( <oid-oc147> NAME 'cim22OperatingSystemSoftwareFeatureAuxClass'
and partComponentRefs point to dmtfSoftwareFeature objects. DESC 'Indicates the SoftwareFeatures that make up the
OperatingSystem. The SoftwareFeatures can be part of
( <oid-oc175> NAME 'dmtfOperatingSystemSoftwareFeatureAuxClass' different Products. Attribute cimGroupComponentRef points
DESC 'Shows the SoftwareFeatures that make up the to cim22OperatingSystem and attribute cimPartComponentRef
OperatingSystem.' points to cim22SoftwareFeature.'
SUP dmtfComponentAuxClass AUXILIARY SUP cim22ComponentAuxClass AUXILIARY
MAY (cimGroupComponentRef $ cimPartComponentRef)
) )
2.18 dmtfFileSystem 3.18 cim22FileSystem
A file or dataset store local to a ComputerSystem or remotely mounted A file or dataset store local to a ComputerSystem or remotely mounted
from a file server. This class reuses the attributes from a file server.
cSCreationClassName, cSName, creationClassName, name, blockSize, and
compressionMethod, and defines the attributes root, fileSystemSize,
encryptionMethod, readOnly, caseSensitive, casePreserved, codeSet,
maxFileNameLength, clusterSize, and fileSystemType.
( <oid-at436> NAME 'root' ( <oid-at258> NAME 'cimRoot'
DESC 'Path name or other information defining the root of the DESC 'Path name or other information defining the root of the
FileSystem.' FileSystem.'
SYNTAX string SINGLE-VALUE SYNTAX string SINGLE-VALUE
) )
( <oid-at437> NAME 'fileSystemSize' ( <oid-at259> NAME 'cimBlockSize'
DESC 'FileSystems can read/write data in blocks which are defined
independently of the underlying StorageExtents. This
property captures the FileSystem's block size for data
storage and retrieval.'
SYNTAX integer SINGLE-VALUE
)
( <oid-at260> NAME 'cimFileSystemSize'
DESC 'The FileSystemSize property stores the total size of the DESC 'The FileSystemSize property stores the total size of the
FileSystem in bytes. If unknown, enter 0.' FileSystem in bytes. If unknown, enter 0.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at438> NAME 'readOnly' ( <oid-at261> NAME 'cimReadOnly'
DESC 'Shows that the FileSystem is designated as read only.' DESC 'Indicates that the FileSystem is designated as read only.'
SYNTAX boolean SINGLE-VALUE SYNTAX boolean SINGLE-VALUE
) )
( <oid-at439> NAME 'encryptionMethod'
( <oid-at262> NAME 'cimEncryptionMethod'
DESC 'A free form string indicating the algorithm or tool used to DESC 'A free form string indicating the algorithm or tool used to
encrypt the FileSystem. If it is not possible or not encrypt the FileSystem. If it is not possible or not
desired to describe the encryption scheme (perhaps for desired to describe the encryption scheme (perhaps for
security reasons), recommend using the following words: security reasons), recommend using the following words:
"Unknown" represent that it is not known whether the "Unknown" to represent that it is not known whether the
FileSystem is encrypted or not, "Encrypted" System is FileSystem is encrypted or not, "Encrypted" to represent
encrypted but either its encryption scheme is not known or that the FileSystem is encrypted but either its encryption
not disclosed, and "Not Encrypted"that the FileSystem is scheme is not known or not disclosed, and "Not Encrypted"
not encrypted.' to represent that the FileSystem is not encrypted.'
SYNTAX string SINGLE-VALUE SYNTAX string SINGLE-VALUE
) )
( <oid-at440> NAME 'caseSensitive' ( <oid-at263> NAME 'cimCompressionMethod'
DESC 'Shows that case sensitive file names are supported.' DESC 'A free form string indicating the algorithm or tool used to
compress the FileSystem. If it is not possible or not
desired to describe the compression scheme (perhaps because
it is not known), recommend using the following words:
"Unknown" to represent that it is not known whether the
FileSystem is compressed or not, "Compressed" to represent
that the FileSystem is compressed but either its
compression scheme is not known or not disclosed, and "Not
Compressed" to represent that the FileSystem is not
compressed.'
SYNTAX string SINGLE-VALUE
)
( <oid-at264> NAME 'cimCaseSensitive'
DESC 'Indicates that case sensitive file names are supported.'
SYNTAX boolean SINGLE-VALUE SYNTAX boolean SINGLE-VALUE
) )
( <oid-at441> NAME 'casePreserved' ( <oid-at265> NAME 'cimCasePreserved'
DESC 'Shows that the case of file names are preserved.' DESC 'Indicates that the case of file names are preserved.'
SYNTAX boolean SINGLE-VALUE SYNTAX boolean SINGLE-VALUE
) )
( <oid-at442> NAME 'codeSet' ( <oid-at266> NAME 'cimCodeSetMV'
DESC 'Array defining the character sets or encoding supported by DESC 'Array defining the character sets or encoding supported by
the FileSystem. Allowed values are: "Unknown", "Other", the FileSystem. For example, the values, "ASCII" (2) or
"ASCII", "Unicode", "ISO2022", "ISO8859", "Extended UNIX "ISO2022" (4), may be specified.'
Code", "UTF-8", "UCS-2".'
SYNTAX integer SYNTAX integer
) )
( <oid-at443> NAME 'maxFileNameLength' ( <oid-at267> NAME 'cimMaxFileNameLength'
DESC 'Integer indicating the maximum length of a file name within DESC 'Integer indicating the maximum length of a file name within
the FileSystem. 0 shows that there is no limit on file the FileSystem. 0 indicates that there is no limit on file
name length.' name length.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at268> NAME 'cimClusterSize'
( <oid-at444> NAME 'clusterSize'
DESC 'The minimum file allocation size (an integral number of DESC 'The minimum file allocation size (an integral number of
blocks), imposed by the FileSystem. (The size of a block is blocks), imposed by the FileSystem. (The size of a block is
specified in the BlockSize property for the FileSystem.) specified in the BlockSize property for the FileSystem.)
Minimum allocation size is the smallest amount of storage Minimum allocation size is the smallest amount of storage
allocated to a LogicalFile by the FileSystem. This is not a allocated to a LogicalFile by the FileSystem. This is not a
mandatory minimum allocation for all FileSystems. Under mandatory minimum allocation for all FileSystems. Under
stress conditions, some FileSystems may allocate storage in stress conditions, some FileSystems may allocate storage in
amounts smaller than the ClusterSize.' amounts smaller than the ClusterSize.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at445> NAME 'fileSystemType' ( <oid-at269> NAME 'cimFileSystemType'
DESC 'String describing the type of FileSystem and therefore, its DESC 'String describing the type of FileSystem and therefore, its
conventions. For example, "NTFS" may be listed as well as conventions. For example, "NTFS" or "S5" may be listed as
any additional information on the FileSystems well as any additional information on the FileSystem's
implementation. Since various flavors of FileSystems (like implementation. Since various flavors of FileSystems (like
S5) exist, this property is defined as a string.' S5) exist, this property is defined as a string.'
SYNTAX string SINGLE-VALUE SYNTAX string SINGLE-VALUE
) )
( <oid-oc176> NAME 'dmtfFileSystem' ( <oid-oc148> NAME 'cim22FileSystem'
DESC 'A file or dataset store local to a ComputerSystem or DESC 'A file or dataset store local to a ComputerSystem or
remotely mounted from a file server.' remotely mounted from a file server.'
SUP dmtfLogicalElement SUP cim22LogicalElement
MUST (cSCreationClassName $ cSName $ creationClassName $ name $ MUST (cimCSCreationClassName $ cimCSName $ cimCreationClassName $
root $ blockSize $ fileSystemSize $ readOnly $ cimName)
encryptionMethod $ compressionMethod $ caseSensitive $ MAY (cimRoot $ cimBlockSize $ cimFileSystemSize $ cimReadOnly $
casePreserved $ codeSet $ maxFileNameLength $ clusterSize $ cimEncryptionMethod $ cimCompressionMethod $
fileSystemType) cimCaseSensitive $ cimCasePreserved $ cimCodeSetMV $
cimMaxFileNameLength $ cimClusterSize $ cimFileSystemType)
) )
Even though csCreationClassName and cSName may be used as RDNs, the ( <oid-nf30> NAME 'cim22FileSystemNameForm'
preferred method is to use the following DIT structural rules. OC cim22FileSystem
MUST (orderedCimModelPath)
( 26 NAME 'dmtfFileSystemStructureRule1'
FORM dmtfFileSystemNameForm1
SUP 24 25
) )
( <oid-nf26> NAME 'dmtfFileSystemNameForm1' ( <sr30> NAME 'cim22FileSystemStructureRule'
OC dmtfFileSystem FORM cim22FileSystemNameForm
MUST (creationClassName) SUP <sr11>
) )
( 27 NAME 'dmtfFileSystemStructureRule2' The following content rule specifies the auxiliary classes that may
FORM dmtfFileSystemNameForm2 be attached to cim22FileSystem.
SUP 24 25
)
( <oid-nf27> NAME 'dmtfFileSystemNameForm2' ( <oid-oc148> NAME 'cim22FileSystemContentRule'
OC dmtfFileSystem DESC 'The auxiliary classes that may be attached to
MUST (name) cim22FileSystem'
AUX (cim22BootOSFromFSAuxClass $ cim22LogicalIdentityAuxClass $
cim22CollectedMSEsAuxClass $
cim22ElementConfigurationAuxClass $
cim22ElementSettingAuxClass $ cim22DependencyAuxClass $
cim22ProvidesServiceToElementAuxClass $
cim22ComponentAuxClass $ cim22SystemComponentAuxClass)
) )
2.19 dmtfLocalFileSystem 3.19 cim22LocalFileSystem
A class derived from dmtfFileSystem that represents the file store on A class derived from cim22FileSystem that represents the file store
a ComputerSystem's locally controlled media. on a ComputerSystem's locally controlled media.
( <oid-oc177> NAME 'dmtfLocalFileSystem' ( <oid-oc149> NAME 'cim22LocalFileSystem'
DESC 'A class derived from FileSystem that represents the file DESC 'A class derived from FileSystem that represents the file
store on a ComputerSystem's locally controlled media.' store on a ComputerSystem's locally controlled media.'
SUP dmtfFileSystem SUP cim22FileSystem
) )
2.20 dmtfRemoteFileSystem 3.20 cim22RemoteFileSystem
A class derived from FileSystem that represents access of the A class derived from FileSystem that represents access of the
FileSystem via a network-related service. For example, the file store FileSystem via a network-related service. For example, the file store
for a NFS FileSystem is NOT on a ComputerSystem's locally controlled for a NFS FileSystem is NOT on a ComputerSystem's locally controlled
media. media.
( <oid-oc178> NAME 'dmtfRemoteFileSystem' ( <oid-oc150> NAME 'cim22RemoteFileSystem'
DESC 'A class derived from FileSystem that represents access of DESC 'A class derived from FileSystem that represents access of
the FileSystem via a network-related service.' the FileSystem via a network-related service. For example,
SUP dmtfFileSystem the file store for an NFS FileSystem is NOT on a
ComputerSystem's locally controlled media.'
SUP cim22FileSystem
) )
2.21 dmtfNFS 3.21 cim22NFS
A class derived from RemoteFileSystem representing that the A class derived from RemoteFileSystem representing that the
FileSystem is mounted from another ComputerSystem. The properties of FileSystem is mounted from another ComputerSystem. The properties of
the NFS object deal with the operational aspects of the mount.' the NFS object deal with the operational aspects of the mount.'
This class defines the attributes hardMount, foregroundMount, ( <oid-at270> NAME 'cimHardMount'
interrupt, mountFailureRetries, retransmissionAttempts,
retransmissionTimeout, readBufferSize, writeBufferSize,
serverCommunicationPort, attributeCaching,
attributeCachingForRegularFilesMin,
attributeCachingForRegularFilesMax,
attributeCachingForDirectoriesMin, and
attributeCachingForDirectoriesMax.
( <oid-at446> NAME 'hardMount'
DESC 'If set to true: Once the FileSystem is mounted, NFS DESC 'If set to true: Once the FileSystem is mounted, NFS
requests are retried until the hosting System responds. If requests are retried until the hosting System responds. If
set to false: Once the FileSystem is mounted, an error is set to false: Once the FileSystem is mounted, an error is
returned if the hosting System does not respond.' returned if the hosting System does not respond. '
SYNTAX boolean SINGLE-VALUE SYNTAX boolean SINGLE-VALUE
) )
( <oid-at271> NAME 'cimForegroundMount'
( <oid-at447> NAME 'foregroundMount'
DESC 'If set to true: Retries are performed in the DESC 'If set to true: Retries are performed in the
foreground. If set to false: If the first mount attempt foreground. If set to false: If the first mount attempt
fails, retries are performed in the background.' fails, retries are performed in the background.'
SYNTAX boolean SINGLE-VALUE SYNTAX boolean SINGLE-VALUE
) )
( <oid-at448> NAME 'interrupt' ( <oid-at272> NAME 'cimInterrupt'
DESC 'If set to true: Interrupts are permitted for hard DESC 'If set to true: Interrupts are permitted for hard mounts.
mounts. If set to false: Interrupts are ignored for hard If set to false: Interrupts are ignored for hard mounts.'
mounts.'
SYNTAX boolean SINGLE-VALUE SYNTAX boolean SINGLE-VALUE
) )
( <oid-at449> NAME 'mountFailureRetries' ( <oid-at273> NAME 'cimMountFailureRetries'
DESC 'Maximum number of mount failure retries allowed.' DESC 'Maximum number of mount failure retries allowed.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at450> NAME 'retransmissionAttempts' ( <oid-at274> NAME 'cimRetransmissionAttempts'
DESC 'Maximum number of NFS retransmissions allowed.' DESC 'Maximum number of NFS retransmissions allowed.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at451> NAME 'retransmissionTimeout' ( <oid-at275> NAME 'cimRetransmissionTimeout'
DESC 'NFS timeout in tenths of a second.' DESC 'NFS timeout in tenths of a second.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at452> NAME 'readBufferSize' ( <oid-at276> NAME 'cimReadBufferSize'
DESC 'Read buffer size in bytes.' DESC 'Read buffer size in bytes.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at453> NAME 'writeBufferSize' ( <oid-at277> NAME 'cimWriteBufferSize'
DESC 'Write buffer size in bytes.' DESC 'Write buffer size in bytes.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at454> NAME 'serverCommunicationPort' ( <oid-at278> NAME 'cimServerCommunicationPort'
DESC 'The NFS File server UDP port number.' DESC 'The remote ComputerSystem's (ie, the NFS File "Server"s)
UDP port number.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at455> NAME 'attributeCaching' ( <oid-at279> NAME 'cimAttributeCaching'
DESC 'If set to true: Control attribute caching is enabled. If DESC 'If set to true: Control attribute caching is enabled. If
set to false: Control attribute caching is disabled.' set to false: Control attribute caching is disabled.'
SYNTAX boolean SINGLE-VALUE SYNTAX boolean SINGLE-VALUE
) )
( <oid-at456> NAME 'attributeCachingForRegularFilesMin'
( <oid-at280> NAME 'cimAttributeCachingForRegularFilesMin'
DESC 'Minimum number of seconds that cached attributes are held DESC 'Minimum number of seconds that cached attributes are held
after file modification.' after file modification.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at457> NAME 'attributeCachingForRegularFilesMax' ( <oid-at281> NAME 'cimAttributeCachingForRegularFilesMax'
DESC 'Maximum number of seconds that cached attributes are held DESC 'Maximum number of seconds that cached attributes are held
after file modification.' after file modification.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at458> NAME 'attributeCachingForDirectoriesMin' ( <oid-at282> NAME 'cimAttributeCachingForDirectoriesMin'
DESC 'Minimum number of seconds that cached attributes are held DESC 'Minimum number of seconds that cached attributes are held
after directory update.' after directory update.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-at459> NAME 'attributeCachingForDirectoriesMax' ( <oid-at283> NAME 'cimAttributeCachingForDirectoriesMax'
DESC 'Maximum number of seconds that cached attributes are held DESC 'Maximum number of seconds that cached attributes are held
after directory update.' after directory update.'
SYNTAX integer SINGLE-VALUE SYNTAX integer SINGLE-VALUE
) )
( <oid-oc179> NAME 'dmtfNFS' ( <oid-oc151> NAME 'cim22NFS'
DESC 'A class derived from RemoteFileSystem representing that the DESC 'A class derived from RemoteFileSystem representing that the
FileSystem is mounted from another ComputerSystem.' FileSystem is mounted from another ComputerSystem. The
SUP dmtfRemoteFileSystem properties of the NFS object deal with the operational
MUST (hardMount $ foregroundMount $ interrupt $ aspects of the mount.'
mountFailureRetries $ retransmissionAttempts $ SUP cim22RemoteFileSystem
retransmissionTimeout $ readBufferSize $ writeBufferSize $ MAY (cimHardMount $ cimForegroundMount $ cimInterrupt $
serverCommunicationPort $ attributeCaching $ cimMountFailureRetries $ cimRetransmissionAttempts $
attributeCachingForRegularFilesMin $ cimRetransmissionTimeout $ cimReadBufferSize $
attributeCachingForRegularFilesMax $ cimWriteBufferSize $ cimServerCommunicationPort $
attributeCachingForDirectoriesMin $ cimAttributeCaching $ cimAttributeCachingForRegularFilesMin $
attributeCachingForDirectoriesMax) cimAttributeCachingForRegularFilesMax $
cimAttributeCachingForDirectoriesMin $
cimAttributeCachingForDirectoriesMax)
) )
2.22 dmtfBootOSFromFSAuxClass 3.22 cim22BootOSFromFSAuxClass
The relationship between the OperatingSystem and the FileSystem(s) The relationship between the OperatingSystem and the FileSystem(s)
from which this OperatingSystem is loaded. The association is many- from which this OperatingSystem is loaded. The association is many-
to-many since a Distributed OS could depend on several FileSystems to to-many since a Distributed OS could depend on several FileSystems to
correctly and completely load. correctly and completely load.
In this class, antecedentRefs point to dmtfFileSystem objects and ( <oid-oc152> NAME 'cim22BootOSFromFSAuxClass'
dependentRefs point to dmtfOperatingSystem objects. DESC 'A link between the OperatingSystem and the FileSystem(s)
from which this OperatingSystem is loaded. The association
( <oid-oc180> NAME 'dmtfBootOSFromFSAuxClass' is many-to-many since a Distributed OS could depend on
DESC 'A link between the OperatingSystem and the FileSystem(s) from several FileSystems in order to correctly and completely
which this OperatingSystem is loaded.' load. Attribute cimAntecedentRef points to cim22FileSystem
SUP dmtfDependencyAuxClass AUXILIARY and attribute cimDependentRef points to
MUST (dmtfFileSystemRefs $ dmtfOperatingSystemRefs) cim22OperatingSystem.'
SUP cim22DependencyAuxClass AUXILIARY
MAY (cimAntecedentRef $ cimDependentRef)
) )
2.23 dmtfBIOSFeature 3.23 cim22BIOSFeature
This class represents the capabilities of the low-level software that This class represents the capabilities of the low-level software that
is used to bring up and configure a ComputerSystem. It reuses the is used to bring up and configure a ComputerSystem.
attributes characteristics and characteristicDescriptions.
( <oid-oc181> NAME 'dmtfBIOSFeature'
DESC 'represents the capabilities of the low-level software that
is used to bring up and configure a ComputerSystem.'
SUP dmtfSoftwareFeature
MUST (characteristics $ characteristicDescriptions)
)
2.24 dmtfBIOSElement
This class represents the low-level software that is loaded into non-
volatile storage and used to bring up and configure a ComputerSystem.
It reuses the attributes version, manufacturer and currentLanguage
and defines the attributes primaryBIOS and listOfLanguages.
( <oid-at460> NAME 'primaryBIOS' ( <oid-oc153> NAME 'cim22BIOSFeature'
DESC 'If true, this is the primary BIOS of the ComputerSystem.' DESC 'BIOSFeature represents the capabilities of the low-level
SYNTAX boolean SINGLE-VALUE software that is used to bring up and configure a
ComputerSystem.'
SUP cim22SoftwareFeature
) )
( <oid-at461> NAME 'listOfLanguages' ( <oid-nf31> NAME 'cim22BIOSFeatureNameForm'
DESC 'A list of installable languages for the BIOS. This OC cim22BIOSFeature
information can be obtained from SMBIOS, from the string MUST (orderedCimModelPath)
list that follows the Type 13 structure. An ISO 639
Language Name should be used to specify the BIOS
installable languages. The ISO 3166 Territory Name and the
encoding method may also be specified, following the
Language Name.'
SYNTAX string
) )
( <oid-at461a> NAME 'currentLanguageString' ( <sr31> NAME 'cim22BIOSFeatureStructureRule'
DESC 'Shows the current printer language being used.' FORM cim22BIOSFeatureNameForm
SYNTAX string SINGLE-VALUE
) )
( <oid-oc182> NAME 'dmtfBIOSElement'
DESC 'BIOSElement represents the low-level software that is
loaded into non-volatile storage and used to bring up and
configure a ComputerSystem.'
SUP dmtfSoftwareElement
MUST (version $ manufacturer $ primaryBIOS $ listOfLanguages $
currentLanguageString)
)
2.25 dmtfBIOSFeatureBIOSElementsAuxClass The following content rule specifies the auxiliary classes that may
be attached to cim22BIOSFeature.
This auxiliary class provides a link between BIOSFeature and its
aggregated BIOSElements. In this class, groupComponentRefs point to
dmtfBIOSFeature objects and partComponentRefs point to
dmtfBIOSElement objects.
( <oid-oc183> NAME 'dmtfBIOSFeatureBIOSElementsAuxClass' ( <oid-oc153>> NAME 'cim22BIOSFeatureContentRule'
DESC 'A link between BIOSFeature and its aggregated DESC 'The auxiliary classes that may be attached to
BIOSElements.' cim22BIOSFeature'
SUP dmtfSoftwareFeatureSoftwareElementsAuxClass AUXILIARY AUX (cim22BIOSFeatureBIOSElementsAuxClass)
) )
2.26 dmtfSystemBIOSAuxClass 3.24 cim22BIOSElement
This auxiliary class associates a UnitaryComputerSystem's BIOS with This class represents the low-level software that is loaded into
the System itself. In it, groupComponentRefs point to non-volatile storage and used to bring up and configure a
dmtfUnitaryComputerSystem objects and partComponentRefs point to ComputerSystem.
dmtfBIOSElementObjects.
( <oid-oc184> NAME 'dmtfSystemBIOSAuxClass' ( <oid-at286> NAME 'cimPrimaryBIOS'
DESC 'associates a UnitaryComputerSystem BIOS with the System DESC 'If true, this is the primary BIOS of the ComputerSystem.'
itself.' SYNTAX boolean SINGLE-VALUE
SUP dmtfSystemComponentAuxClass AUXILIARY
) )
3. DIT Content Rules ( <oid-at287> NAME 'cimListOfLanguages'
DESC 'A list of installable languages for the BIOS. This
The following DIT Content Rules apply to objects in this schema. information can be obtained from SMBIOS, from the string
These content rules referrence not only auxiliary classes in this list that follows the Type 13 structure. An ISO 639
draft but auxiliary classes from other DMTF CIM models [3, 6, 7, 8, Language Name should be used to specify the BIOS'
9] installable languages. The ISO 3166 Territory Name and the
encoding method may also be specified, following the
( <oid-oc160> NAME 'dmtfUnitaryComputerSystemContentRule' Language Name.'
DESC 'shows what auxiliary classes may go with the SYNTAX string
dmtfUnitaryComputerSystem class'
AUX (dmtfSystemPartitionAuxClass $ dmtfSystemBIOSAuxClass $
dmtfComputerSystemPackageAuxClass)
)
( <oid-oc162> NAME 'dmtfVirtualComputerSystemContentRule'
DESC 'shows what auxiliary classes may go with the
dmtfVirtualComputerSystem class'
AUX (dmtfHostingCSAuxClass)
) )
( <oid-oc164> NAME 'dmtfClusterContentRule' ( <oid-at288> NAME 'cimCurrentLanguage'
DESC 'shows what auxiliary classes may go with the dmtfCluster DESC 'The currently selected language for the BIOS. This
class' information can be obtained from SMBIOS, using the Current
AUX (dmtfParticipatingCSAuxClass) Language attribute of the Type 13 structure, to index into
the string list following the structure. The property is
formatted using the ISO 639 Language Name, and may be
followed by the ISO 3166 Territory Name and the encoding
method.'
SYNTAX string SINGLE-VALUE
) )
( <oid-oc166> NAME 'dmtfClusteringServiceContentRule' ( <oid-oc154> NAME 'cim22BIOSElement'
DESC 'shows what auxiliary classes may go with the DESC 'BIOSElement represents the low-level software that is
dmtfClusteringService class' loaded into non-volatile storage and used to bring up and
AUX (dmtfClusterServiceAccessBySAPAuxClass) configure a ComputerSystem.'
SUP cim22SoftwareElement
MAY (cimPrimaryBIOS $ cimListOfLanguages $ cimCurrentLanguage)
) )
( <oid-oc167> NAME 'dmtfClusteringSAPContentRule' The following content rule specifies the auxiliary classes that may
DESC 'shows what auxiliary classes may go with the be attached to cim22BIOSFeature.
dmtfClusteringSAP class'
AUX (dmtfClusterServiceAccessBySAPAuxClass)
)
( <oid-oc169> NAME 'dmtfBootServiceContentRule' ( <oid-oc154> NAME 'cim22BIOSElementContentRule'
DESC 'shows what auxiliary classes may go with the DESC 'The auxiliary classes that may be attached to
dmtfBootService class' cim22BIOSElement'
AUX (dmtfBootServiceAccessBySAPAuxClass) AUX (cim22BIOSFeatureBIOSElementsAuxClass $ cim22SystemBIOSAuxClass)
) )
( <oid-oc170> NAME 'dmtfBootSAPContentRule' 3.25 cim22BIOSFeatureBIOSElementsAuxClass
DESC 'shows what auxiliary classes may go with the dmtfBootSAP
class'
AUX (dmtfBootServiceAccessBySAPAuxClass)
)
( <oid-oc172> NAME 'dmtfStorageLibraryContentRule' This auxiliary class provides a link between BIOSFeature and its
DESC 'shows what auxiliary classes may go with the aggregated BIOSElements.
dmtfStorageLibrary class'
AUX (dmtfLibraryPackageAuxClass)
)
( <oid-oc173> NAME 'dmtfOperatingSystemContentRule' ( <oid-oc155> NAME 'cim22BIOSFeatureBIOSElementsAuxClass'
DESC 'shows what auxiliary classes may go with the DESC 'A link between BIOSFeature and its aggregated
dmtfOperatingSystem class' BIOSElements. Attribute cimGroupComponentRef points to
AUX (dmtfRunningOSAuxClass $ dmtfBootOSFromFSAuxClass $ cim22BIOSFeature and attribute cimPartComponentRef points to
dmtfOperatingSystemSoftwareFeatureAuxClass) cim22BIOSElement.'
) SUP cim22SoftwareFeatureSoftwareElementsAuxClass AUXILIARY
( <oid-oc176> NAME 'dmtfFileSystemContentRule' MAY (cimGroupComponentRef $ cimPartComponentRef)
DESC 'shows what auxiliary classes may go with the dmtfFileSystem
class'
AUX (dmtfBootOSFromFSAuxClass)
) )
( <oid-oc181> NAME 'dmtfBIOSFeatureContentRule' 3.26 cim22SystemBIOSAuxClass
DESC 'shows what auxiliary classes may go with the
dmtfBIOSFeature class'
AUX (dmtfBIOSFeatureBIOSElementsAuxClass)
)
( <oid-oc182> NAME 'dmtfBIOSElementContentRule' This auxiliary class associates a UnitaryComputerSystem's BIOS with
DESC 'shows what auxiliary classes may go with the the System itself.
dmtfBIOSElement class'
AUX (dmtfBIOSFeatureBIOSElementsAuxClass $ dmtfSystemBIOSAuxClass) ( <oid-oc156> NAME 'cim22SystemBIOSAuxClass'
DESC 'SystemBIOS associates a UnitaryComputerSystem's BIOS with
the System itself. Attribute cimGroupComponentRef points to
cim22UnitaryComputerSystem and attribute cimPartComponentRef
points to cim22BIOSElement.'
SUP cim22SystemComponentAuxClass AUXILIARY
MAY (cimGroupComponentRef $ cimPartComponentRef)
) )
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 Synatx Defini-
tions," RFC 2252, December 1997.
[3] Ryan Moats, Gerald Maziarski, John Strassner, "LDAP Schema
for the DMTF Core CIM Model," Internet Draft (work in
progress), September 1999.
[4] Ryan Moats, Gerald Maziarski, John Strassner, "Extensible
Match Rule to Dereference Pointers", Internet Draft (work in
progress), June 1999.
[5] DMTF, "CIM System Model, v2.2".
[6] Ryan Moats, Gerald Maziarski, John Strassner, "LDAP Schema [2] M. Wahl, A. Coulbeck, T. Howes, S. Kille, "Light-
for the DMTF Device CIM Model", September 1999. weight Directory Access Protocol (v3): Attribute
Synatx Definitions," RFC 2252, December 1997.
[7] Ryan Moats, Gerald Maziarski, John Strassner, "LDAP Schema [3] Ryan Moats, Gerald Maziarski, John Strassner, "LDAP
for the DMTF Network CIM Model", October 1999. Schema for the DMTF Core CIM v2.2 Model," Internet
Draft (work in progress), December 1999.
[8] Ryan Moats, Gerald Maziarski, John Strassner, "LDAP Schema [4] Ryan Moats, Gerald Maziarski, John Strassner,
for the DMTF Application CIM Model", October 1999. "Extensible Match Rule to Dereference Pointers",
Internet Draft (work in progress), June 1999.
[9] Ryan Moats, Gerald Maziarski, John Strassner, "LDAP Schema [5] DMTF, "CIM System Model, v2.2".
for the DMTF Physical CIM Model", October 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. 191 change blocks. 
636 lines changed or deleted 736 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/