Textual Conventions; Physicalindex; Physicalclass; Possible Values For Entphysicalclass - HP StorageWorks 2/64 - Core Switch Reference Manual

Textual conventions

PhysicalIndex

Status
Description
Syntax

PhysicalClass

Status
Description
Syntax
Table 9

Possible values for entPhysicalClass

Value
other (1)
unknown (2)
chassis (3)
backplane (4)
container (5)
powerSupply (6)
fan (7)
sensor (8)
module (9)
port (10)
stack (11)
114 Entity MIB objects
Current
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)
Current
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 (see
Integer
Description
The physical entity class that is known but does not match any of the supported
values.
The physical entity class that 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. 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).
The physical entity class is a networking port, capable of receiving or transmitting
networking traffic.
The physical entity class is a super-container (possibly virtual), intended to group
together multiple chassis entities (such as a stack of multiple chassis entities). A stack
might be realized by a virtual cable or a real interconnect cable attached to multiple
chassis, or it can comprise multiple interconnect cables. A stack should not be
modeled within any other physical entities, but a stack might be contained within
another stack. Only chassis entities should be contained within a stack.
Table 9).