HP Insight Management WBEM Providers for HP integrated VMware ESXi 5.0 U1 June 2012 Profiles

10 Version 1.2.0
Note that this profile does not reference any other profiles nor does any other profile reference this profile.
Profile elements defined in this profile are intended to be optionally used by any managed element
defined within another profile to report location information and/or the location information of its
containment. Furthermore, this profile has no requirement to be registered in the interop namespace
using profile registration defined in P00100 and DSP1033 (see section 2.1)
7 Implementation Requirements
7.1 HP_Location
HP_Location adds 4 properties to more deterministically describe and report the location of the managed
elements.
7.1.1 Name (mandatory)
The name property is defined as a key and should be implemented as an opaque value used to
differentiate between instances unless another profile places restrictions on its use.
7.1.2 PhysicalPosition (mandatory)
The PhysicalPosition property is defined as a key and should be implemented as an opaque value used
to differentiate between instances unless another profile places restrictions on its use.
7.1.3 ElementLocationTagDesc (mandatory)
ElementLocationTagDesc shall contain one of the enumerated values contained in Table 2. These
values describe the semantic meaning of the value in the ElementLocationTag property. The
combination of ElementLocationTagDesc and ElementLocationTag provide a location tag for the
managed element associated to an instance of HP_Location.
ElementLocationTagDesc defined tag
values
Description of contents of
ElementLocationTag
Example of
ElementLocationTag
Contents
Hood Tag The Hood tag or silk screen ID that
identifies this managed element to the
user. Several systems shipped by HP
contain a diagram on the physical hood
that contains IDs identifying the location
of all replaceable items in the system.
“Fan 1”
Slot This tag shall be used to identify the
actual slot. This would typically be the
case when HP_Location is associated
with an instance of CIM_Slot or one of
its sub-classes. Typically clients would
have to query the slot type from the
instance of CIM_Slot (or subclass) to
determine what type of slot the tag is
referring to.
“4”
Socket
This tag is used to identify a socket.
“7”
Chassis
This tag is used to identify the actual
“3”