North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

RE: Survey on IBGP persistent route oscillation problem

  • From: Yu Ning
  • Date: Thu Mar 21 04:03:40 2002


We have a similar situation (RR + always-compare-MED off), and the BGP table
version keeps changing at 1K/min ( I
suspect some
route meet the criteria of IDR-oscillation draft. But in real world, it's
very hard to pick
 up the pattern depicted in the draft from a huge log of debug bgp output.

After several sample from the huge bgp log, I have the following questions:

1.  How many time do our operator really find and affected by the problem
     in  draft-ietf-idr-route-oscillation-01.txt   

2. From my experience, most flapping seems to be oscillation route which
escaped the
     eBGP damping protection. And for this, we need adjust damping
parameters from
     RIPE 220 to make up.

3.   Anyone see oscillation been magnified when injected into RR (cluster
structure) ?

4. What's the typical bgp table change rate within your network ? From my
observation at
   the major global looking glass, should be  below 0.5K/min with some
accidental surge.


Yu Ning

(Mr.) Yu Ning, Chief Engineer
ChinaNET (AS4134) Senior Support
Internet Dep. DCBU, China Telecom
Beijing, P.R.China +86-10-62072357
Personal Page->

|-----Original Message-----
|From: [email protected] [mailto:[email protected]]On
|Behalf Of Susan Hares
|Sent: Wednesday, March 20, 2002 8:23 PM
|To: [email protected]
|Subject: Survey on IBGP persistent route oscillation problem
|IBGP and Persistent Route Oscillation
|The Draft BGP Persistent Route Oscillation draft describes route
|oscillation occurring in networks today.   This draft can be obtained at:
|In order to evaluate how significant a problem the route oscillation is, I
|would like to get input from network operators.   If you could take a few
|moments and fill out this survey, it would help in determining the
|of the problems.   Any information solicited by this survey will remain
|private.   Summaries of this information will be sent to this list and the
|IDR working list.
|Sue Hares
|IDR co-chair