Reference Guide

Property Description
ElementName
A user-friendly name for the object. This property allows each instance to dene a user-
friendly name in addition to its key properties, identity data, and description information.
NOTE: The Name property of ManagedSystemElement is also dened 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.
Name
The Name property denes the label by which the object is known. In the case of an LDAP-
derived instance, the Name property value may be set to the distinguished name of the
LDAP-accessed object instance.
RoleCharacteristics
RoleCharacteristics provides descriptive information about the intended usage of the Role.
Possible values are:
• 2 = Static
• 3 = Opaque
• .. = DMTF Reserved
• 32000..65535 = Vendor Specic
When the value 2 Static is specied, no modication to the role is allowed. Any requests by
client to change the privileges or the scope of the role by modifying the associated
instances of CIM_Privilege or referencing associations fails.
When the value 2 Static is not specied, the instance of CIM_Role may be modied by a
client. The modication may include changing the scope of the role or rights granted. When
the value 3 Opaque is specied, the rights granted by the CIM_Role instance is not explicitly
modeled through aggregation of instances of CIM_Privilege.
When the value 3 Opaque is not specied, the rights granted by the instance of CIM_Role
is explicitly modeled through aggregation of instances of CIM_Privilege.
DCIM_IndicationSettingCollection
Property
Description
ElementName
Human user oriented identier for this instance.
InstanceID
Within the scope of the instantiating Namespace, InstanceID opaquely and uniquely identies
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 dening 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 rst 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 dierent underlying (real-world)
elements. If the above preferred algorithm is not used, the dening 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-dened instances, the preferred
algorithm must be used with the <OrgID>set to CIM.
224 Dell Command | Monitor10.1.0 classes and properties