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.
|
Manufacturer
|
The name of the organization responsible for producing
the PhysicalElement. This organization may be the entity from whom
the Element is purchased, but it is not necessarily true. The latter
information is contained in the Vendor property of CIM_Product.
|
Model
|
The name by which the PhysicalElement is 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 (e.g., 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.
|