nanog mailing list archives
Re: BGP Routing problem
From: Alan Barrett <apb () iafrica com>
Date: Fri, 6 Jun 1997 09:32:43 +0200 (GMT+0200)
Anthony Walker said that the following was seen while the BGP session between AS6180 and AS3741 was down:
MAE-East Looking Glass Results Query: bgp Addr: 196.25.203.0 BGP routing table entry for 196.25.203.0/24, version 5006458 Paths: (1 available, no best path, advertised over IBGP) 1673 1239 4005 3741 6180, (received-only) 192.41.177.141 from 192.41.177.141 (140.223.57.217) Origin IGP, external
AFAIK, "received-only" means that DIGEX heard that route from AS1673 but did not install it, presumably because it failed to pass a filter. The question is, why did that route not get withdrawn properly when the BGP session between AS6189 and AS3741 was terminated? This looks very much like the cisco bug that bit Sprint during the AS7007 incident a month or so ago. Hey, Ravi, I thought you fixed that bug? Perhaps AS4005 is not running the fixed code. Perhaps there's another bug. --apb (Alan Barrett)
Current thread:
- BGP Routing problem Anthony Walker (Jun 05)
- Re: BGP Routing problem Bil Herd (Jun 05)
- Re: BGP Routing problem Alan Barrett (Jun 06)
- <Possible follow-ups>
- Re: BGP Routing problem Danny McPherson (Jun 05)
- Re: BGP Routing problem Danny McPherson (Jun 06)
- Re: BGP Routing problem Alan Barrett (Jun 06)
- Re: BGP Routing problem John (Jun 06)
- Re: BGP Routing problem Alex.Bligh (Jun 06)
- Re: BGP Routing problem Ed Kern (Jun 06)
- Re: BGP Routing problem John (Jun 06)
- Re: BGP Routing problem Alan Barrett (Jun 06)
- Re: BGP Routing problem Marc Slemko (Jun 06)