Entlogicaltype 1.3.6.1.2.1.47.1.2.1.1.3, Entlogicalcommunity 1.3.6.1.2.1.47.1.2.1.1.4, Entlogicaltaddress 1.3.6.1.2.1.47.1.2.1.1.5 – Dell POWEREDGE M1000E User Manual

Page 149

Advertising
background image

Fabric OS MIB Reference

131

53-1001768-01

entLogicalType 1.3.6.1.2.1.47.1.2.1.1.3

4

entLogicalType 1.3.6.1.2.1.47.1.2.1.1.3

An indication of the type of logical entity. This is typically the Object Identifier name of the node in
the SMI’s naming hierarchy that represents the major MIB module, or the majority of the MIB
modules, supported by the logical entity.

A logical entity of a regular host/router -> mib-2

A logical entity of a 802.1d bridge -> dot1dBridge

A logical entity of a 802.3 repeater -> snmpDot3RptrMgmt

If an appropriate node in the SMI’s naming hierarchy cannot be identified, the value mib-2 should
be used.

entLogicalCommunity 1.3.6.1.2.1.47.1.2.1.1.4

An SNMPv1 or SNMPv2C community string, which can be used to access detailed management
information for this logical entity. The agent should allow read access with this community string (to
an appropriate subset of all managed objects) and might also return a community string based on
the privileges of the request used to read this object.

Note that an agent might return a community string with read-only privileges, even if this object is
accessed with a read-write community string. However, the agent must take care not to return a
community string that allows more privileges than the community string used to access this object.

A compliant SNMP agent might 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” might 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.
This object might 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 might return a zero-length string for this object or might
continue to return a community string (for example, tri-lingual agent support).

entLogicalTAddress 1.3.6.1.2.1.47.1.2.1.1.5

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 4 octets containing the IP-address in
network-byte order and the last 2 containing the UDP port in network-byte order. Refer to Transport
Mappings for Version 2 of the Simple Network Management Protocol
(RFC1906) for further
information on snmpUDPDomain.

Advertising