Brocade Communications Systems 8, Справочное руководство

Страница: 144 / 382

126 Fabric OS MIB Reference
53-1001768-01
entPhysicalParentRelPos 1.3.6.1.2.1.47.1.1.1.1.6
4
•
Chassis: One entry (one row)
•
Container: One entry for each FRU slot (one switch blade, two power supplies, three fans)
•
Module: One entry for switch blade, up to two entries for power supplies, and up to three
entries for fans
Brocade 7500 and 7600 switches can have the following hierarchy of physical objects:
•
Chassis: One entry (one row)
•
Container: One entry for each FRU slot (one switch blade, two power supplies, three fans)
•
Module: One entry for switch blade, up to two entries for power supplies, and up to three
entries for fans
Brocade 8000 switch can have the following hierarchy of physical objects:
•
Chassis: One entry (one row)
•
Container: One entry for each FRU slot (one switch blade, two power supplies, three fans)
•
Module: One entry for switch blade, up to two entries for power supplies, and up to three
entries for fans
Brocade 7800 Extension Switch can have the following hierarchy of physical objects:
•
Chassis: One entry (one row)
•
Container: One entry for each FRU slot (one switch blade, two power supplies, two fans)
•
Module: One entry for switch blade, up to two entries for power supplies, and up to two
entries for fans
entPhysicalParentRelPos 1.3.6.1.2.1.47.1.1.1.1.6
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.
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.