Snmpengineidornone; Entity Mib Objects - HP StorageWorks MSA 2/8 - SAN Switch Reference Manual

Entity MIB Objects

Table 7: Possible values for PhysicalClass (Continued)
module (9)
port (10)
stack (11)

SnmpEngineIdOrNone

Status
Description
Syntax
Entity MIB Objects
The entityMib objects are divided into the following groups:
168
Values
The physical entity class is a self-contained sub-system (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 may be realized by a
virtual cable, a real interconnect cable attached to multiple
chassis, or may be comprised of multiple interconnect cables. A
stack should not be modeled within any other physical entities, but
a stack may be contained within another stack. Only chassis
entities should be contained within a stack.
Current
A specially formatted SnmpEngineID string for use with the
Entity MIB.
If an instance of an object with syntax SnmpEngineIdOrNone
has a non-zero length, then the object encoding and semantics
are defined by the SnmpEngineID textual convention (see
RFC 2571 [RFC2571]).
If an instance of an object with syntax SnmpEngineIdOrNone
contains a zero-length string, then no appropriate
SnmpEngineID is associated with the logical entity (that is,
SNMPv3 not supported).
OCTET STRING (SIZE(0..32)) Empty string or
SnmpEngineID
The Physical Entity Group
The Logical Entity Group
Description
MIB Version 3.1.x/4.1.x Reference Guide