nlmLogEngineTAddress

NOTIFICATION-LOG-MIB · .1.3.6.1.2.1.92.1.3.1.1.5
Commands MIB view Table view

Object

column SNMPv2-TCTAddress 
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.

Context

MIB
NOTIFICATION-LOG-MIB
OID
.1.3.6.1.2.1.92.1.3.1.1.5
Type
column
Access
readonly
Status
current
Parent
nlmLogEntry
Groups
1

Net-SNMP examples

How SNMP and these commands work

Walk the column to discover its indexed instances, or supply every index to read one instance.

Walk the column
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'NOTIFICATION-LOG-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'NOTIFICATION-LOG-MIB::nlmLogEngineTAddress'
More examples
Read one indexed instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'NOTIFICATION-LOG-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'NOTIFICATION-LOG-MIB::nlmLogEngineTAddress.<nlmLogName>.<nlmLogIndex>'
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'NOTIFICATION-LOG-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'NOTIFICATION-LOG-MIB::nlmLogEngineTAddress'

Syntax

SNMPv2-TCTAddress
Source
SNMPv2-TCTAddress
Base type
OctetString
Type Description
Denotes a transport service address.
          
A TAddress value is always interpreted within the context of a
TDomain value.  Thus, each definition of a TDomain value must
be accompanied by a definition of a textual convention for use
with that TDomain.  Some possible textual conventions, such as
SnmpUDPAddress for snmpUDPDomain, are defined in the SNMPv2-TM
MIB module.  Other possible textual conventions are defined in
other MIB modules.

Values & Constraints

Type Constraints
range: 1..255

Conformance

Member of
notificationLogLogGroup