Enabling BGP Max Route (Prefix) threshold monitoring

Network Protocol Manager for BGP monitors syslog messages from Cisco and Juniper devices to determine when the BGP Max Route (Prefix) threshold is exceeded. When Network Protocol Manager for BGP detects the threshold has been exceeded, the BGP application generates a PrefixThresholdCrossed notification for that BGP session and correlates it to the BGPsession “Down” notification.

Juniper syslog messages are not parsed for Facility-Mnemonic. Juniper syslog messages are processed based on the source device information in the message.

To receive the PrefixThresholdCrossed notification in the Notification Log Console, use sm_edit to modify the dxa-bgp.conf file available in the Service Assurance Manager deployment. Add the following lines:

sev BGPSession PrefixThresholdCrossed Operational 2
sub BGPSession::.*::PrefixThresholdCrossed/e

For example:

./sm_edit conf/ics/dxa-bgp.conf
22 sev BGPSession              Disconnected Operational 3
23 sev BGPSession              Flapping Operational 3
24 sev BGPSessionGroup                 Impacted Impacted 3
25 sev BGPSession PrefixThresholdCrossed      Operational 2
.
.
.
56 # Send events List Subscription
     57 sub     .*::.*::.*/p
     58 sub     BGPSession::.*:Disconnected/e
     59 sub     BGPSession::.*::Flapping/e
     60 sub     BGPSessionGroup::.*::Impacted/e
     61 sub     RedundancyGroup::.*::.*/e
     62 sub     BGPSession::.*:PrefixThresholdCrossed/e
     63 #COMPUTER SYSTEMS

The PrefixThresholdCrossed notification clears after a configured time interval, SysCleanTime, is reached. SysCleanTime default value is 86,400 seconds (24 hours). SysCleanTime is specified in <BASEDIR>/conf/bgp/bgp.conf and the value may be changed in the Domain Manager Administration Console.