Dell Command | Monitor Version 9.1 Reference Guide

PDF

DCIM_Slot

Property	Description
ConnectorLayout	Describes the type of packaging normally associated with this type of connector. Possible values are: 0 = Unknown 1 = Other 2 = RS232 3 = BNC 4 = RJ11 5 = RJ45 6 = DB9 7 = Slot 8 = SCSI High Density 9 = SCSI Low Density 10 = Ribbon 11 = AUI 12 = Fiber SC 13 = Fiber ST 14 = FDDI-MIC 15 = Fiber-RTMJ 16 = PCI — Describes the generic PCI connector layout. 17 = PCI-X — Describes the PCI Extended connector layout. 18 = PCI-E — Describes the PCI Express connector layout, where the actual layout with respect to the length is unknown. 19 = PCI-E x1 20 = PCI-E x2 21 = PCI-E x4 22 = PCI-E x8 23 = PCI-E x16 24 = PCI-E x32 25 = PCI-E x64 26..32567 = DMTF Reserved 32568..65535 = Vendor Reserved 19 — 25 (PCI-E xN) — Describes the PCI Express connector layout, where N is the lane count that appropriately describes the length of the PCI-E connector.
ConnectorType	An array of integers defining the type of PhysicalConnector. An array is specified to allow the description of combinations of Connector information. Possible values are: 0 = Unknown 1 = Other 2 = Male 3 = Female 4 = Shielded 5 = Unshielded 6 = SCSI (A) High-Density (50 pins) 7 = SCSI (A) Low-Density (50 pins) 8 = SCSI (P) High-Density (68 pins) 9 = SCSI SCA-I (80 pins) 10 = SCSI SCA-II (80 pins) 11 = Fibre Channel (DB-9, Copper) 12 = Fibre Channel (Optical Fibre) 13 = Fibre Channel SCA-II (40 pins) 14 = Fibre Channel SCA-II (20 pins) 15 = Fibre Channel BNC 16 = ATA 3-1/2 Inch (40 pins) 17 = ATA 2-1/2 Inch (44 pins) 18 = ATA-2 19 = ATA-3 20 = ATA/66 21 = DB-9 22 = DB-15 23 = DB-25 24 = DB-36 25 = RS-232C 26 = RS-422 27 = RS-423 28 = RS-485 29 = RS-449 30 = V.35 31 = X.21 32 = IEEE-488 33 = AUI 34 = UPT Category 3 35 = UPT Category 4 36 = UPT Category 5 37 = BNC 38 = RJ11 39 = RJ45 40 = Fiber MIC 41 = Apple AUI 42 = Apple GeoPort 43 = PCI 44 = ISA 45 = EISA 46 = VESA 47 = PCMCIA 48 = PCMCIA Type I 49 = PCMCIA Type II 50 = PCMCIA Type III 51 = ZV Port 52 = CardBus 53 = USB 54 = IEEE 1394 55 = HIPPI 56 = HSSDC (6 pins) 57 = GBIC 58 = DIN 59 = Mini-DIN 60 = Micro-DIN 61 = PS/2 62 = Infrared 63 = HP-HIL 64 = Access.bus 65 = NuBus 66 = Centronics 67 = Mini-Centronics 68 = Mini-Centronics Type-14 69 = Mini-Centronics Type-20 70 = Mini-Centronics Type-26 71 = Bus Mouse 72 = ADB 73 = AGP 74 = VME Bus 75 = VME64 76 = Proprietary 77 = Proprietary Processor Card Slot 78 = Proprietary Memory Card Slot 79 = Proprietary I/O Riser Slot 80 = PCI-66MHZ 81 = AGP2X 82 = AGP4X 83 = PC-98 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.