HP StorageWorks 2/16V Brocade Fabric OS MIB Reference - Supporting Fabric OS 5 - Page 115

SnmpEngineIdOrNone 4 TABLE 10 Values Possible Values for PhysicalClass (Continued) Description container (5) powerSupply (6) fan (7) sensor (8) module (9) port (10) 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. stack (11) 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. SnmpEngineIdOrNone 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). • For the Brocade 3016 or Brocade 4020 blades, the snmpEngineID takes the UUID value. For example, if the UUID value is A9914D56-1E5A-0E59-C51E-528802B06E4F, the snmpEngineID displays 80.00.06.34.B1.A9.91.4D.56.1E.5A.0E.59.C5.1E.52.88.02.B0.6E.4F (hex) • For other switches, the snmpEngineID takes the WWN. For example, if the WWN value is 10:00:00:05:1e:35:d5:ee, the snmpEngineID displays 80.00.06.34.B2.10.00.00.05.1E.35.D5.EE (hex) • If the WWN cannot be taken, the snmpEngineID takes the IP address + port number along with the private enterprise number and algorithm type used. An example of this type of snmpEngineID would be 00.00.06.34.00.00.00.A1.0A.20.93.CA (hex) Syntax OCTET STRING (SIZE(0..32)) Empty string or SnmpEngineID Fabric OS MIB Reference 99 53-1000439-01