[9886] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: BGP Routing problem

daemon@ATHENA.MIT.EDU (Jun (John) Wu)
Fri Jun 6 10:25:53 1997

From: Jun (John) Wu <jun@wolfox.gsl.net>
To: apb@iafrica.com (Alan Barrett)
Date: Fri, 6 Jun 1997 10:22:56 -0400 (EDT)
Cc: danny@genuity.net, nanog@merit.edu
In-Reply-To: <Pine.NEB.3.95.970606153225.190U-100000@apb.iafrica.com> from "Alan Barrett" at Jun 6, 97 03:49:29 pm
Reply-To: Jun John Wu <jun@wolfox.gsl.net>

===== Alan Barrett previously wrote: ====
> 
> That's independent of the issue I am talking about, which is that the BGP
> sesson between AS3741 and AS6180 had been shut down for several hours, the
> route in question was no longer present in AS3741, but the route still
> appeared (with path "1673 1239 4005 3741 6180") at DIGEX's MAE-East
> looking glass.  The route should have been withdrawn completely from the
> entire Internet when the BGP session between AS6180 and AS3741 was shut
> down, but the route was not properly withdrawn.  DIGEX should not have
> seen any trace of the route (except perhaps a history entry for flap
> damping purposes).
> 

It would not hurt to check a few other looking glasses. Such as,

route-views.oregon-ix.net  or
route-server.cerf.net

to see if the path is really there. We have found out that some of these
looking glasses sometimes keep the routes much longer,  at one time
several hours after we see routes disppeared in our routers.

Just one observation.


Jun

home help back first fref pref prev next nref lref last post