HP StorageWorks 1606 Brocade Fabric OS MIB Reference v6.3.0 (53-1001339-01, Ju - Page 128

4 Textual conventions Textual conventions PhysicalIndex Syntax Arbitrary value that uniquely identifies the physical entity. Value should be a small positive integer; index values for different physical entities are not necessarily contiguous. Integer (1... 2147483647) PhysicalClass An enumerated value that provides an indication of the general hardware type of a particular physical entity. There are no restrictions as to the number of entPhysicalEntries of each entPhysicalClass, which must be instantiated by an agent. Syntax Integer TABLE 10 Values Possible values for PhysicalClass Description other (1) unknown (2) chassis (3) backplane (4) container (5) powerSupply (6) fan (7) sensor (8) module (9) The physical entity class is known but does not match any of the supported values. The physical entity class is unknown to the agent. The physical entity class is an overall container for networking equipment. Any class of physical entity except a stack can be contained within a chassis, and a chassis might be contained only within a stack. The physical entity class is a device for aggregating and forwarding networking traffic, such as a shared backplane in a modular Ethernet switch. Note that an agent might model a backplane as a single physical entity, which is actually implemented as multiple discrete physical components (within a chassis or stack). The physical entity class is capable of containing one ore more removable physical entities, possibly of different types (such as a chassis slot or daughter-card holder). For example, each (empty or full) slot in a chassis is modeled as a container. Note that all removable physical entities should be modeled within a container entity, such as field-replaceable modules, fans, or power supplies. Note that all known containers, including empty containers, should be modeled by the agent. The physical entity class is a power-supplying component. The physical entity class is a fan or other heat-reduction component. The physical entity class is a sensor, such as a temperature sensor within a router chassis. The physical entity class is a self-contained subsystem (such as a plug-in card or daughter-card). If it is removable, then it should be modeled within a container entity; otherwise, it should be modeled directly within another physical entity (for example, a chassis or another module). 110 Fabric OS MIB Reference 53-1001339-01