Reference Guide

The Reference Guide contains the
file:///T|/htdocs/SOFTWARE/smcliins/cli81/en/refgd/index.html[10/19/2012 10:01:19 AM]
84 = PC-98-Hireso
85 = PC-H98
86 = PC-98Note
87 = PC-98Full
88 = SSA SCSI
89 = Circular
90 = On Board IDE Connector
91 = On Board Floppy Connector
92 = 9 Pin Dual Inline
93 = 25 Pin Dual Inline
94 = 50 Pin Dual Inline
95 = 68 Pin Dual Inline
96 = On Board Sound Connector
97 = Mini-jack
98 = PCI-X
99 = Sbus IEEE 1396-1993 32 bit
100 = Sbus IEEE 1396-1993 64 bit
101 = MCA
102 = GIO
103 = XIO
104 = HIO
105 = NGIO
106 = PMC
107 = MTRJ
108 = VF-45
109 = Future I/O
110 = SC
111 = SG
112 = Electrical
113 = Optical
114 = Ribbon
115 = GLM
116 = 1x9
117 = Mini SG
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 include a copyrighted, trademarked or otherwise unique name that is owned by the business entity creating/defining 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 first colon to appear in InstanceID MUST appear between and . is chosen by the business entity and SHOULD not be re-used to identify different underlying (real-world) elements.
DCIM_SerialPort
BaseIOAddress An integer value that represents the base I/O address used by the serial port. Caption The Caption property is a short textual description (one- line string) of the object.
ConnectorType
ConnectorType is defined to force consistent naming of the 'connector type' property in subclasses and to guarantee unique enum values for all instances of SerialPort. When set to 1 ("Other"), related property
OtherConnectorType contains a string description of the type of port. A range of values, DMTF_Reserved, has been defined that allows subclasses to override and define their specific types of ports.
Possible values are:
0 = Unknown
1 = Other
2 = Not Applicable
3..15999 = DMTF Reserved
16003 = DB9Male
16004 = DB9Female
16005 = DB25Male1
16006 = DB25Female1
16007 = RJ11
16008 = RJ45
16009 = Proprietary
16010 = CircularDIN8Male
16011 = CircularDIN8Female
16160 = MiniCentronicsType14
16161 = MiniCentronicsType26
16162..65535 = Vendor Reserved
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.
DeviceID An address or other identifying information used to uniquely name the LogicalDevice.
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.