NOTIFICATION-LOG-MIB :: nlmLogEngineTAddress

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › NOTIFICATION-LOG-MIB › nlmLogEngineTAddress

nlmLogEngineTAddress

Module: NOTIFICATION-LOG-MIB

OID (symbolic): NOTIFICATION-LOG-MIB::nlmLogEngineTAddress

OID (numeric): 1.3.6.1.2.1.92.1.3.1.1.5

Node type: OBJECT-TYPE

Type: TAddress

Access: read-only

Description: The transport service address of the SNMP engine from which the Notification was received, formatted according to the corresponding value of nlmLogEngineTDomain. This is used to identify the source of an SNMPv1 trap, since an nlmLogEngineId cannot be extracted from the SNMPv1 trap pdu.

This object MUST always be instantiated, even if the log can contain Notifications from only one engine.

Please be aware that the nlmLogEngineTAddress may not uniquely identify the SNMP engine from which the Notification was received. For example, if an SNMP engine uses DHCP or NAT to obtain ip addresses, the address it uses may be shared with other network devices, and hence will not uniquely identify the SNMP engine.

What is nlmLogEngineTAddress?

The transport address of the SNMP engine that sent this notification, encoded per nlmLogEngineTDomain; this is always populated and is the only way to identify the source of an SNMPv1 trap (which carries no engine ID). Note it may not uniquely identify the sender if that engine's address is shared via DHCP or NAT.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.92.1.3.1.1.5
snmpwalk -v2c -c public <target> NOTIFICATION-LOG-MIB::nlmLogEngineTAddress

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.92.1.3.1.1.5.1
snmpget -v2c -c public <target> NOTIFICATION-LOG-MIB::nlmLogEngineTAddress.1

Start monitoring Vendor-neutral IETF standard (any SNMP-capable device, trap/inform logging) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the NOTIFICATION-LOG-MIB::nlmLogEngineTAddress OID value, configure state conditions and alerts, and monitor any Vendor-neutral IETF standard (any SNMP-capable device, trap/inform logging) from a single console.

OID Breakdown

Upper-level ancestors (6 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.2mgmtAPERTUS-NPG-MIB
1.3.6.1.2.1mib_2AXON-MIB
Numeric OIDNameModule
1.3.6.1.2.1.92notificationLogMIBNOTIFICATION-LOG-MIB
1.3.6.1.2.1.92.1notificationLogMIBObjectsNOTIFICATION-LOG-MIB
1.3.6.1.2.1.92.1.3nlmLogNOTIFICATION-LOG-MIB
1.3.6.1.2.1.92.1.3.1nlmLogTableNOTIFICATION-LOG-MIB
1.3.6.1.2.1.92.1.3.1.1nlmLogEntryNOTIFICATION-LOG-MIB
1.3.6.1.2.1.92.1.3.1.1.5nlmLogEngineTAddressNOTIFICATION-LOG-MIB