WBEM Profiles Guide

16 Version 1.2.0
The second case is when the providers do not fully instantiate or implement the physical containment
hierarchy, but still need to report the location of a managed element within it. This requires augmenting
the ElementLocationTagDesc/ElementLocationTag properties with the
LocationInformationDesc/LocationInformation property arrays.
The following object diagrams show instances of each and how both cases can be supported by a single
set of providers in the same implementation namespace.
9.2 Object Diagrams
Figure 2 shows an instance of a system where the main chassis (chassis1) contains another chassis
(chassis2) directly, no slot has been modeled between the two. Chassis2 contains 2 slots capable of
holding another type of chassis, one of which has a chassis (chassis3) plugged into it. Chassis3 contains
1 fan slot (fanslot1) which contains a single fan module (fm1). Fm1 is associated with its logical side via a
CIM_Realizes association to a logical fan (fan3). Fan3 is a system device of the contained computer
system (system1).
This instance diagram shows an instance of an implementation that has fully instantiated the containment
hierarchy of the system. To this end, the providers utilize ElementLocationTagDesc and
ElementLocationTag to identify the location of each element in the hierarchy. All physical components
are modeled and supported and the containment of each component is explicitly instantiated. For
example, you can see explicitly that fan module fm1 is contained in slot fanslot1 and that chassis
chassis3 is contained in chassis slot chslt2. In this case, HP_Location is used to tag each physical
component to communicate to clients the label of the physical element and not the location inside its
contained component. The red arrow shows the path of traversal and client would follow when following
the algorithm defined in section 9.1. At the end of implementing this algorithm the client should have 2
corresponding lists:
Index
ElementLocationTag
ElementLocationTagDesc
0
“3”
Fan
1
“1”
Slot
2
“3”
Chassis
3
“2”
Slot
4
“2”
Chassis
Clients can use this information along with the semantics of the tags defined in ElementLocationTag as
well as the associations between each CIM_PhysicalElement to report the following string to the user has
the location for the instance of HP_Fan:
“Fan 3 is plugged into Slot 1 which is contained in Chassis 3 which is plugged into Slot 2 which is
contained in Chassis 2 which is contained in the Main System chassis.”