Reference Guide

Property Description
InstanceID
Within the scope of the instantiating Namespace, InstanceID opaquely and uniquely
identifies an instance of this class. To ensure uniqueness within the NameSpace, the value
of InstanceID should be constructed using the following preferred algorithm:
<OrgID> : <LocalID>
Where <OrgID> and <LocalID> are separated by a colon (:), and where <OrgID> must
include a copyrighted, trademarked, or otherwise unique name that is owned by the
business entity that is creating or defining the InstanceID or that is a registered ID assigned
to the business entity by a recognized global authority. (This requirement is similar to the
<Schema Name>_<Class Name> structure of Schema class names.) In addition, to ensure
uniqueness, <OrgID> must not contain a colon (:). When using this algorithm, the first colon
to appear in InstanceID must appear between <OrgID> and <LocalID> . <LocalID> is chosen
by the business entity and should not be reused to identify different underlying (real-world)
elements. If the above preferred algorithm is not used, the defining entity must assure that
the resulting InstanceID is not reused across any InstanceIDs produced by this or other
providers for the NameSpace of this instance. For DMTF-defined instances, the preferred
algorithm must be used with the <OrgID>set to CIM.
DCIM_RedundancySet
Table 88. RedundancySet
Property Description
ElementName
ElementName A user-friendly name for the object. This property allows each instance to
define a user-friendly name in addition to its key properties, identity data, and description
information.
NOTE: The Name property of ManagedSystemElement is also defined as a
user-friendly name. But, it is often subclassed to be a Key. It is not reasonable
that the same property can convey both identity and a user-friendly name,
without inconsistencies. Where Name exists and is not a Key (such as for
instances of LogicalDevice), the same information can be present in both the
Name and ElementName properties.
InstanceID
Within the scope of the instantiating Namespace, InstanceID opaquely and uniquely
identifies an instance of this class. To ensure uniqueness within the NameSpace, the value
of InstanceID should be constructed using the following preferred algorithm:
<OrgID> : <LocalID>
Where <OrgID> and <LocalID> are separated by a colon (:), and where <OrgID> must
include a copyrighted, trademarked, or otherwise unique name that is owned by the
business entity that is creating or defining the InstanceID or that is a registered ID assigned
to the business entity by a recognized global authority. (This requirement is similar to the
<Schema Name>_<Class Name> structure of Schema class names.) In addition, to ensure
uniqueness, <OrgID> must not contain a colon (:). When using this algorithm, the first colon
to appear in InstanceID must appear between <OrgID> and <LocalID> . <LocalID> is chosen
by the business entity and should not be reused to identify different underlying (real-world)
elements. If the above preferred algorithm is not used, the defining entity must assure that
the resulting InstanceID is not reused across any InstanceIDs produced by this or other
providers for the NameSpace of this instance. For DMTF-defined instances, the preferred
algorithm must be used with the <OrgID>set to CIM.
MinNumberNeeded
MinNumberNeeded indicates the smallest number of elements that MUST be operational in
order to function. For example, in an N+1 redundancy relationship, the MinNumberNeeded
property is set equal to N. In a 'LimitedSparing' environment, this property is meaningless
and SHOULD be set to zero.
RedundancyStatus
RedundancyStatus provides information on the state of the RedundancyGroup.
Possible values are:
214 Dell Command | Monitor 10.3 classes and properties