Dell POWEREDGE M1000E - Manual (Page 132)

112 Fabric OS MIB Reference
53-1002750-01
Physical entity group
5
entPhysicalParentRelPos
1.3.6.1.2.1.47.1.1.1.1.6 Read only An indication of the relative position of this child component among all
its sibling components. Sibling components are defined as
entPhysicalEntries that share the same instance values of each of the
entPhysicalContainedIn and entPhysicalClass objects.
For chassis entry, this value is -1; for containers, it is the sequential
number of the container from the first one; for all FRUs, it is always 1.
An NMS can use this object to identify the relative ordering for all
sibling components of a particular parent (identified by the
entPhysicalContainedIn instance in each sibling entry).
This value should match any external labeling of the physical
component if possible. For example, for a container (such as a card
slot) labeled slot #3, entPhysicalParentRelPos should have the value 3.
Note that the entPhysicalEntry for the module plugged into slot 3
should have an entPhysicalParentRelPos value of 1.
If the physical position of this component does not match any external
numbering or clearly visible ordering, then user documentation or other
external reference material should be used to determine the
parent-relative position. If this is not possible, then the agent should
assign a consistent (but possibly arbitrary) ordering to a given set of
sibling components, perhaps based on internal representation of the
components.
entPhysicalParentRelPos
1.3.6.1.2.1.47.1.1.1.1.6
(continued) Read only If the agent cannot determine the parent-relative position for some
reason, or if the associated value of entPhysicalContainedIn is 0, then
the value -1 is returned; otherwise, a non-negative integer is returned,
indicating the parent-relative position of this physical entity.
Parent-relative ordering normally starts from 1 and continues to n,
where n represents the highest-positioned child entity. However, if the
physical entities (for example, slots) are labeled from a starting
position of zero, then the first sibling should be associated with an
entPhysicalParentRelPos value of 0. Note that this ordering might be
sparse or dense, depending on agent implementation.
The actual values returned are not globally meaningful, as each parent
component might use different numbering algorithms. The ordering is
meaningful only among siblings of the same parent component.
The agent should retain parent-relative position values across reboots,
either through algorithmic assignment or use of nonvolatile storage.
entPhysicalName
1.3.6.1.2.1.47.1.1.1.1.7 Read only The textual name of the physical entity (physical name of the entity
such as chassis, blade, port, and so on). The value of this object should
be the name of the component as assigned by the local device and
should be suitable for use in commands entered at the device’s
“console.” This might be a text name, such as “console,” or a simple
component number (for example, port or module number) such as 1,
depending on the physical component naming syntax of the device.
If there is no local name, or this object is otherwise not applicable, then
this object contains a zero-length string.
Note that the value of entPhysicalName for two physical entities is the
same in the event that the console interface does not distinguish
between them (for example, slot 1 and the card in slot 1).
The name provides the type of the entry and its number (for example,
slot 1, power supply, and so on). The description gives the textual
description of the type of the entry (for example, power supply, module,
and so on).
TABLE 39
Object and OID Access Description