[44200] in North American Network Operators' Group
Re: Strange BGP phantom announce remaining
daemon@ATHENA.MIT.EDU (Chrisy Luke)
Mon Nov 12 11:04:58 2001
Date: Mon, 12 Nov 2001 16:03:00 +0000
From: Chrisy Luke <chrisy@flix.net>
To: Stephane Bortzmeyer <bortzmeyer@gitoyen.net>
Cc: nanog@merit.edu, zebra@zebra.org
Message-ID: <20011112160300.N73502@flix.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20011112151614.A15319@internatif.org>; from bortzmeyer@gitoyen.net on Mon, Nov 12, 2001 at 03:16:14PM +0100
Errors-To: owner-nanog-outgoing@merit.edu
Stephane Bortzmeyer wrote (on Nov 12):
> Does you have any idea why routers at Colt still see the old announce?
> People at Colt have no idea. Abovenet checked on its side and sees
> only the good prefix.
Dodgy Cisco-ism probably. Use looking glasses and NOC's to find the one
router where the phantom prefix appears in a BGP table and (have someone)
drop the BGP session associated with it.
Failing that, re-advertise the prefix for a period of time (minutes
not seconds) and then withdraw it.
I have found IOS sometimes unable to "keep up" when it is faced with
a prefix that is withdrawn too quickly. Because "soft" configuration
maintains the same state the BGP engine sees, a soft clear doesn't solve
the problem. You have top dump all state for that session, ergo, drop
the BGP session or renew the phantom prefix.
Just my experience, and it's always been with other networks routers,
not mine.
Chris.
--
== chris@easynet.net T: +44 845 333 0122
== Global IP Network Engineering, Easynet Group PLC F: +44 845 333 0122
