BGP Routing problem
apb at iafrica.com
Fri Jun 6 07:32:43 UTC 1997
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: 184.108.40.206
> BGP routing table entry for 220.127.116.11/24, version 5006458
> Paths: (1 available, no best path, advertised over IBGP)
> 1673 1239 4005 3741 6180, (received-only)
> 18.104.22.168 from 22.214.171.124 (126.96.36.199)
> 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)
More information about the NANOG