HP Brocade 8/12c Brocade Fabric OS MIB Reference Supporting Fabric OS v7.0.0 ( - Page 129

Physical entity group 5 Object and OID Access entPhysicalClass 1.3.6.1.2.1.47.1.1.1.1.5 (continued) Read only entPhysicalParentRelPos Read only 1.3.6.1.2.1.47.1.1.1.1.6 Description 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 Brocade 6510 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 Brocade DCX 8510-4 Backbone can have the following hierarchy of physical objects: • Chassis: One entry (one row) • Container: One entry for each FRU slot (four port blades, two CPs, two power supplies, two fans) • Module: Eight entries for port blades, two entries for CPs, four entries for power supplies, and three entries for fans Brocade DCX 8510-8 Backbone can have the following hierarchy of physical objects: • Chassis: One entry (one row) • Container: One entry for each FRU slot (eight port blades, two CPs, four power supplies, three fans) • Module: Eight entries for port blades, two entries for CPs, four entries for power supplies, and three entries for fans 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. Fabric OS MIB Reference 109 53-1002151-01