[86475] in North American Network Operators' Group
Re: BGP terminology question
daemon@ATHENA.MIT.EDU (Blaine Christian)
Mon Nov 7 10:58:25 2005
In-Reply-To: <p0623094dbf9507e16096@[192.168.0.2]>
Cc: nanog@merit.edu
From: Blaine Christian <blaine@blaines.net>
Date: Mon, 7 Nov 2005 10:57:57 -0500
To: "Howard C. Berkowitz" <hcb@gettcomm.com>
Errors-To: owner-nanog@merit.edu
On Nov 7, 2005, at 8:32 AM, Howard C. Berkowitz wrote:
>
> At 9:44 AM -1000 11/6/05, Randy Bush wrote:
>> > A peer should never announce a route it has already announced
>> unless
>>> that route is withdrawn.
>>
>> one of many counterexamples: change in igp will cause change in
>> med. any attribute changes, and announcement is required.
>>
>> e.g., an internal igp oscillation could cause what the op
>> describes.
>
> For the OP, http://www.ietf.org/rfc/rfc3345.txt
I give good odds this is not the oscillation issue. More likely a
flapping IGP link and a lack of pull-up use (or pull-ups not
installed such that link flaps would be non external impacting) etc...
I like pull-ups on all core devices personally...
