Reference Guide

Property Description
Name
The Name property defines 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 Specific
When the value 2 Static is specified, no modification 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 specified, the instance of CIM_Role may be modified by a
client. The modification may include changing the scope of the role or rights granted. When
the value 3 Opaque is specified, 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 specified, the rights granted by the instance of CIM_Role
is explicitly modeled through aggregation of instances of CIM_Privilege.
DCIM_IndicationSettingCollection
Table 90. IndicationSettingCollection
Property Description
ElementName
Human user oriented identifier for this instance.
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.
Name
The name of the product-defined event sources.
OccurrencesCount
Defines TXT state in MCH for vPro brand (on/off).
216 Dell Command | Monitor 10.3 classes and properties