tBgpMaxNgPrefixThreshReached

TIMETRA-BGP-MIB · .1.3.6.1.4.1.6527.3.1.3.14.0.12

Object

notification obsolete

[CAUSE] A tBgpMaxNgPrefixThreshReached notification is generated when
the number of routes learned from the peer has exceeded
tBgpPeerNgMaxPrefixThreshold percent of the configured maximum
(tBgpPeerNgMaxPrefix). tBgpMaxNgPrefixThreshReached replaces
notification object tBgpMaxNgPrefix90 as the latter limits the
threshold to 90 percent.
          
[EFFECT] No direct effect but if the peer continues to advertise more
routes then the number of routes may exceed the configured maximum
(tBgpPeerNgMaxPrefix). in that case the peer would just be disabled.
          
[RECOVERY] Increase the max-prefix for this peer.
          
This notification is obsoleted in release 13.0.

Context

MIB: TIMETRA-BGP-MIB
OID: .1.3.6.1.4.1.6527.3.1.3.14.0.12
Type: notification
Status: obsolete
Parent: tBgpNotifications
Groups: 3

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

More examples

Translate to a numeric OID

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

Syntax

No syntax metadata recorded.

Values & Constraints

No enumerated values or constraints recorded.