Reference Guide

Property Description
CreationClassName
Indicates the name of the class or the subclass used in the creation
of an instance. When used with the other key properties of this
class, this property allows all instances of this class and its
subclasses to be uniquely identied.
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 sub-
classed 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.
Number
The Number property indicates the physical slot number, which can
be used as an index into a system slot table, whether or not that
slot is physically occupied.
SupportsHotPlug
Boolean indicating whether the Slot supports hot-plug of adapter
Cards.
Tag
An arbitrary string that uniquely identies the Physical Element and
serves as the key of the Element. The Tag property can contain
information such as asset tag or serial number data. The key for
PhysicalElement is placed very high in the object hierarchy to
independently identify the hardware or entity, regardless of physical
placement in or on Cabinets, Adapters, and so on. For example, a
hotswappable or removable component can be taken from its
containing (scoping) Package and be temporarily unused. The
object still continues to exist and can even be inserted into a
dierent scoping container. Therefore, the key for Physical Element
is an arbitrary string and is dened independently of any placement
or location-oriented hierarchy.
VendorCompatibilityStrings
An array of strings that identify the components that are
compatible and can be inserted in a slot. This allows vendors to
provide clues to the system administrators by providing sucient
information to request the appropriate hardware that can populate
the slot. To ensure uniqueness within the NameSpace, each value
dened by the vendor for use in the VendorCompatibilityStrings
property SHOULD be constructed using the following 'preferred'
algorithm: : Where and are separated by a colon ':', and where
MUST include a copyrighted, trademarked or otherwise unique
name that is owned by the business entity creating/dening the
InstanceID, or is a registered ID that is assigned to the business
entity by a recognized global authority (This is similar to the _
structure of Schema class names.) In addition, to ensure uniqueness
MUST NOT contain a colon ':'. When using this algorithm, the rst
colon to appear in InstanceID MUST appear between and . is
chosen by the business entity and SHOULD not be re-used to
identify dierent underlying (real-world) elements.
Dell Command | Monitor10.1.0 classes and properties 75