Reference Guide

Property Description
• 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.
21