The announcing router must have an exact match entry in the local FIB in
order to announce the route. The one exception is when creating aggregates,
in which case, only a prefix-match must be made. If an 'internal' or local
path is not available, the prefix will be withdrawn, thus causing
route-flapping. Most get around this by routing their static announcements
to null0 with a high distance. Some applications require you to set this
distance to something less than 200, some not.
chris
> -----Original Message-----
> From: Tatsuya Kawasaki [mailto:tatsuya@kivex.com]
> Sent: Friday, July 21, 2000 2:56 PM
> To: cisco-nsp@iagnet.net
> Subject: [nsp] Question about BGP routing damping
>
>
>
> Hello,
>
> I have a simple bgp question.
>
> In the BGP statement, we defined the network.
>
> I thought network statement in the bgp statement is
> independent of internal routing protocol.
> Even if we lost the connectivity to a network,
> which does not cause BGP routing damping or does it?
>
> Only time that BGP routing damping occurs when you lose the connection
> to peer provided that we do not change any configuration change?
>
> Or am I missing something?
>
>
> Tatsuya
>
>
> /_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
> Tatsuya Kawasaki
> Allegiance Telecom
> Unlock the Power of the Internet
> http://www.kivex.com
> Phone 301.215.6777 Fa 301.215.5991
> Affiliation given for identification not representation
> /_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
>
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:14 EDT