Reference Guide

Table 20. Slot (continued)
Property Description
● 118 = LC
● 119 = HSSC
● 120 = VHDCI Shielded (68 pins)
● 121 = InfiniBand
● 122 = AGP8X
For example, one array entry could specify RS-232 (value =
25), another DB-25 (value = 23) and a third entry define
the Connector as Male (value = 2). This single property
is being deprecated instead of using separate properties to
describe the various aspects of the connector. The separation
allows for a more generic means of describing the connectors.
Obsolete connectors were intentionally removed from the new
list.
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 identified.
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 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 identifies 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 different
scoping container. Therefore, the key for Physical Element
is an arbitrary string and is defined 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 sufficient information to request the appropriate
hardware that can populate the slot. To ensure uniqueness
within the NameSpace, each value defined 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
Dell Command | Monitor 10.5 classes and properties 71