tmnxIsisProtoSuppMismatch

TIMETRA-ISIS-NG-MIB · .1.3.6.1.4.1.6527.3.1.3.88.0.16

Object

notification

[CAUSE] The tmnxIsisProtoSuppMismatch notification is sent when a
non-pseudonode segment 0 LSP is received that has no matching
protocols supported.
          
This may be because the system does not generate the field, or because
there are no common elements.
          
The list of protocols supported should be included in the
notification: it may be empty if the TLV is not supported, or if the
TLV is empty.
          
This should be an edge-triggered notification. We should not send a
second notification about PDUs received from the same source.
          
[EFFECT] No effect.
          
[RECOVERY] No recovery is necessary.

Context

MIB: TIMETRA-ISIS-NG-MIB
OID: .1.3.6.1.4.1.6527.3.1.3.88.0.16
Type: notification
Status: current
Parent: tmnxIsisNotifications
Groups: 1

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-ISIS-NG-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'TIMETRA-ISIS-NG-MIB::tmnxIsisProtoSuppMismatch'

More examples

Translate to a numeric OID

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

Syntax

No syntax metadata recorded.

Values & Constraints

No enumerated values or constraints recorded.