vRtrLdpInstanceStateChange

TIMETRA-LDP-MIB · .1.3.6.1.4.1.6527.3.1.3.8.0.2

Object

notification obsolete

[CAUSE] The vRtrLdpInstanceStateChange notification may be triggered
for the following reasons:
          
1) The LDP instance changes state operationally.
2) vRtrLdpGenOperState remains 'inService' but internal event described
by vRtrLdpGenOperDownReason has changed.  New notification will not be
generated if multiple internal event change occurs during 10 minute
interval.
          
[EFFECT] Based on the vRtrLdpGenOperDownReason reason code, system may
not be able to accept new request from peers.
          
[RECOVERY] Based on the vRtrLdpGenOperDownReason reason code,
appropriate configuration changes in LDP may be required.
          
This notification was obsoleted in release 13.0.

Context

MIB: TIMETRA-LDP-MIB
OID: .1.3.6.1.4.1.6527.3.1.3.8.0.2
Type: notification
Status: obsolete
Parent: tmnxLdpNotifications
Groups: 2

Net-SNMP examples

How SNMP and these commands work

Notifications are emitted by an agent; they cannot be read with snmpget or walked.

Inspect the notification definition

/usr/bin/snmptranslate -Pud -Ir -Td -m 'TIMETRA-LDP-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'TIMETRA-LDP-MIB::vRtrLdpInstanceStateChange'

More examples

Translate to a numeric OID

/usr/bin/snmptranslate -Pud -Ir -On -m 'TIMETRA-LDP-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'TIMETRA-LDP-MIB::vRtrLdpInstanceStateChange'

Syntax

No syntax metadata recorded.

Values & Constraints

No enumerated values or constraints recorded.