HP StorageWorks 2/16V Brocade Fabric OS MIB Reference (53-1000241-01, November - Page 121

entPhysicalClass 1.3.6.1.2.1.47.1.1.1.1.5 4 entPhysicalClass 1.3.6.1.2.1.47.1.1.1.1.5 An indication of the general hardware type of the physical entity. An agent should set this object to the standard enumeration value that most accurately indicates the general class of the physical entity, or the primary class if there is more than one. If no appropriate standard registration identifier exists for this physical entity, then the value other(1) is returned. If the value is unknown by this agent, then the value unknown(2) is returned. SilkWorm 12000, 24000, and 48000 directors 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. SilkWorm 3900 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, six fans) • Module: One entry for switch blade, up to two entries for power supplies, and up to six entries for fans. SilkWorm 4100 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: 1 entry for switch blade, up to two entries for power supplies, and up to three 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. Fabric OS MIB Reference 4-9 Publication Number: 53-1000241-01