| OID | 1.3.6.1.2.1.92.1.3.1.1.5 |
| Module | NOTIFICATION-LOG-MIB (CISCO) |
| Nom | nlmLogEngineTAddress |
| Acces | readonly |
| Status | current |
| 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. |
| Syntaxe | TAddress (SNMPv2-TC) |
| Module | NOTIFICATION-LOG-MIB (ietf) |
| Nom | nlmLogEngineTAddress |
| Acces | readonly |
| Status | current |
| 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. |
| Syntaxe | TAddress (SNMPv2-TC) |