HP StorageWorks Fabric OS 5.0.0 MIB Reference Guide (AA-RW1QA-TE, May 2005)

128 Entity MIB objects
A compliant SNMP agent may want to conserve naming scopes by representing multiple
logical entities in a single default naming scope. This is possible when the logical entities
represented by the same value of entLogicalCommunity have no object instances in
common. For example, bridge1 and repeater1 may be part of the main naming scope,
but at least one additional community string is needed to represent bridge2 and
repeater2.
Logical entities bridge1 and repeater1 would be represented by sysOREntries associated
with the default naming scope.
For agents not accessible through SNMPvl or SNMPv2C, the value of this object is the
empty string. The object may also contain an empty string if a community string has not
yet been assigned by the agent, or no community string with suitable access rights can
be returned for a particular SNMP request.
Note that this object is deprecated. Agents that implement SNMPv3 access should use
the entLogicalContextEngineID and entLogicalContextName objects to identify the
context associated with each logical entity. SNMPv3 agents may return a zero-length
string for this object or may continue to return a community string (for example, tri-lingual
agent support).
entLogicalTAddress
OID 1.3.6.1.2.1.47.1.2.1.1.5
Description The transport service address by which the logical entity receives network management
traffic, formatted according to the corresponding value of entLogicalTDomain.
For snmpUDPDomain, a TAddress is 6 octets long, the initial four octets containing the
IP-address in network-byte order and the last two containing the UDP port in network-byte
order. Consult Transport Mappings for Version 2 of the Simple Network Management
Protocol (RFC1906) for further information on snmpUDPDomain.
entLogicalTDomain
OID 1.3.6.1.2.1.47.1.2.1.1.6
Description The kind of transport service by which the logical entity receives network management
traffic. Possible values for this object are currently found in the Transport Mappings for
SNMPv2 document (RFC1906).
entLogicalContextEngineID
OID 1.3.6.1.2.1.47.1.2.1.1.7
Description The authoritative contextEngineID that can be used to send an SNMP message
concerning information held by this logical entity to the address specified by the
associated entLogicalTAddress/entLogicalTDomain pair.
This object, together with the associated entLogicalContextName object, defines the
context associated with a particular logical entity; it allows access to SNMP engines
identified by a contextEngineId and contextName pair.
If no value has been configured by the agent, a zero-length string is returned, or the
agent may choose not to instantiate this object at all.