Reference Guide

Dell OpenManage Client Instrumentation Reference Guide
file:///T|/htdocs/SOFTWARE/smcliins/cli80/EN/refgd/index.htm[10/19/2012 9:56:27 AM]
107 - Out of CPU Cycles
108 - Software Environment Problem
109 - Software Download Failure
110 - Element Reinitialized
111 - Timeout
112 - Logging Problems
113 - Leak Detected
114 - Protection Mechanism Failure
115 - Protecting Resource Failure
116 - Database Inconsistency
117 - Authentication Failure
118 - Breach of Confidentiality
119 - Cable Tamper
120 - Delayed Information
121 - Duplicate Information
122 - Information Missing
123 - Information Modification
124 - Information Out of Sequence
125 - Key Expired
126 - Non-Repudiation Failure
127 - Out of Hours Activity
128 - Out of Service
129 - Procedural Error
130 - Unexpected Information
ProviderName The name of the Provider generating this Indication.
SystemCreationClassName The scoping System's CreationClassName for the Provider generating this Indication.
SystemName The scoping System's Name for the Provider generating this Indication.
Trending
Provides information on trending - trending up, down, or no change.
Possible values are:
0 - Unknown
1 - Not Applicable
2 - Trending Up
3 - Trending Down
4 - No Change
DCIM_Card
CanBeFRUed Boolean that indicates whether this PhysicalElement can be FRUed (TRUE) or not (FALSE).
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 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.
HostingBoard Boolean indicating that this Card is a Motherboard or, more generically, a baseboard in a Chassis.
ManufactureDate The date that this PhysicalElement was manufactured.
Manufacturer
The name of the organization responsible for producing the PhysicalElement. This organization may be the entity from whom the Element is
purchased, but this is not necessarily true. The latter information is contained in the Vendor property of CIM_Product.
Model The name by which the PhysicalElement is generally known.
PackageType
Enumeration defining the type of the PhysicalPackage.
Possible values are:
0 - Unknown - Indicates that the package type is not known.
1 - Other - The package type does not correspond to an existing enumerated value. The value is specified using the OtherPackageType property.
2 - Rack
3 - Chassis/Frame
4 - Cross Connect/Backplane
5 - Container/Frame Slot
6 - Power Supply
7 - Fan
8 - Sensor
9 - Module/Card
10 - Port/Connector
11 - Battery
12 - Processor
13 - Memory
14 - Power Source/Generator
15 - Storage Media Package (for example, Disk or Tape Drive)
16 - Blade
17 - Blade Expansion
Note: This enumeration expands on the list in the Entity MIB (the attribute, entPhysicalClass). The numeric values are consistent with CIM's
enum numbering guidelines, but are slightly different than the MIB's values.
The values "Rack" through "Port/Connector" are defined per the Entity-MIB (where the semantics of rack are equivalent to the MIB's 'stack'
value). The other values (for battery, processor, memory, power source/generator and storage media package) are self-explanatory.
A value of "Blade" should be used when the PhysicalPackage contains the operational hardware aspects of a ComputerSystem, without the
supporting mechanicals such as power and cooling. For example, a Blade Server includes processor(s) and memory, and relies on the containing
chassis to supply power and cooling. In many respects, a Blade can be considered a "Module/Card". However, it is tracked differently by
inventory systems and differs in terms of service philosophy. For example, a Blade is intended to be hot-plugged into a hosting enclosure without
requiring additional cabling, and does not require a cover to be removed from the enclosure for installation. Similarly, a "Blade Expansion" has
characteristics of a "Blade" and a "Module/Card". However, it is distinct from both due to inventory tracking and service philosophy, and because
of its hardware dependence on a Blade. A Blade Expansion must be attached to a Blade prior to inserting the resultant assembly into an
enclosure.
PartNumber The part number assigned by the organization that is responsible for producing or manufacturing the PhysicalElement.
SKU The stock-keeping unit number for this PhysicalElement.
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.
DCIM_Chassis