bgp neighbor max-prefix makes this a lot easier to do now. As soon as you
go over 75% of the threshold set, the router sends messages to syslog. And
it will optionally tear the peering down once you hit the threshold you
set. I know a lot of folks monitor syslog for strange events, so adding a
monitor for the BGP threshold would be easy enough to do. Better than cron
logging into the router every 5/15/60 minutes...
philip
--At 08:52 03/07/2001 +0530, R S Mani wrote: >Hi! Alan > >You can write a simple script to scan for "sh ip bgp summ". >and take out the number of prefixes sent by the per.. You can then apply >your filtering rules so that it generates an alarm.. > >Iyer >----- Original Message ----- >From: "Alan Halachmi" <alan@halachmi.net> >To: <cisco-nsp@puck.nether.net> >Sent: Tuesday, July 03, 2001 12:10 AM >Subject: [nsp] Monitoring BGP routes... > > > > Greetings! > > > > Can anyone recommend a program that checks to ensure that a BGP > > peer is sending a sane number of BGP routes? I use rtrmon to check for >BGP > > sessions, just my ISP unintentionally change me from a full-route >connection > > to a default-route-only and it would have been nice to have gotten > > notification that I only had 1 route against that peer. > > > > TIA! > > Alan > > > > -- > > Alan Halachmi > > Wide Area Network Specialist > > Ingram Entertainment Network Services > > mailto:alan@halachmi.net > > http://www.ingramentertainment.com > > > >
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:43 EDT