excessive bgp withdraws

Wed Apr 16 15:53:55 UTC 1997

  this might be of interest to some.  we found a few weeks ago that 
we were suddenly on the "bad guys" list at merit, 
routing-problems at merit.edu.  we were consistantly making the top ten 
offenders of "largest sources of bgp instability".  we had upgraded 
to a new version of code in our peer router in san jose that had 
"lost" the fix to bgp to stop these excessive withdraws which had 
been discussed on nanog some time ago.  we got a new image with the 
fix rolled back in 2 days ago and will be deploying soon.

  i don't know what version everyone is running but if you're making 
this list consistantly you might check with your vendor to see if 
your version of code is lacking this fix.

  here is yesterday's list for those that don't subscribe to 
routing-problems:

Largest Sources of BGP Instability
----------------------------------
(announcements + withdraws = total)

1.  ANS (AS1673)       at Mae-East 7124 + 276413 = 283537 BGP prefix updates
2.  INSnetUSA (AS6660) at Mae-East 11 + 250384 = 250395 BGP prefix updates
3.  SPRINT (AS1239)    at Mae-East 170072 + 69258 = 239330 BGP prefix updates
4.  HLCnet (AS4565)    at Mae-West 14 + 229402 = 229416 BGP prefix updates
5.  GRIDNET (AS6113)   at Mae-East 647 + 220572 = 221219 BGP prefix updates
6.  GRIDNET (AS6113)   at PacBell  646 + 195514 = 196160 BGP prefix updates
7.  GRIDNET (AS6113)   at Mae-West 640 + 193955 = 194595 BGP prefix updates
8.  IconNet (AS3951)   at Mae-East 36 + 190158 = 190194 BGP prefix updates
9.  ANS (AS1673)       at Mae-West 7757 + 174053 = 181810 BGP prefix updates
10. Genuity (AS3847)   at Mae-West 1144 + 165556 = 166700 BGP prefix updates

-brett