[45086] in North American Network Operators' Group

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

Re: router startup behavior

daemon@ATHENA.MIT.EDU (Danny McPherson)
Tue Jan 15 23:41:08 2002

Message-Id: <200201160531.g0G5V4M06316@tcb.net>
To: "'nanog@merit.edu'" <nanog@merit.edu>
From: Danny McPherson <danny@tcb.net>
Reply-To: danny@tcb.net
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 15 Jan 2002 22:31:04 -0700
Errors-To: owner-nanog-outgoing@merit.edu


  
> 
> The routers in question run a BGP redistribution process every 
> 60 seconds and it just happened to run (quite often) just as 
> filters were being rewritten, resulting in "the gunk" not being 
> tagged as "keep internal" and therefore being advertised 
> externally.  A subsequent run of the BGP process realized a 
> policy was in place withdrew the routes.  

I should clarify here:

A subsequent run of the BGP resdistribution process with the 
newly rewritten policy in place resulted in the routes being 
tagged with the appropriate "keep internal" community and "re-
advertised".  Upon receipt of the now tagged routes, routers that
had previously announced the untagged routes withdrew them (per 
egress policy specification).

-danny


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