BGP (or any other dynamic routing protocol) won't withdraw an announcement
unless it doesn't know where to send traffic for a given network. If
you're nailing down the routes via a static route to a loopback interface,
the router will always "think" it knows where the traffic for that network
should go, and will continue announcing the block.
hth,
brian
On Wed, 28 Mar 2001, Michael K. Smith wrote:
:Hello All:
:
:I am facing two issues that appear to have two different solutions. I hope
:I am missing something basic in my config that will solve both issues at the
:same time.
:
:My present config uses a combination of the network statement and the
:aggregate-address summary statement. Whenever the networks associated with
:the network statement becomes unreachable by the router on which the
:statements are present, that router withdraws its routes from its BGP peers.
:However, because I am announcing the routes using the aggregate summary
:address, they are showing up as Incomplete instead of Locally Originated in
:the global routing tables.
:
:So, I would like to use the network statements and the usual tie-down routes
:in the static routing table, but I would also like to have the BGP edge
:router withdraw its announcements automatically if a select set of
:locally-originated routes become unreachable by the router. Does anyone
:have a config snippet that would do this?
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:33 EDT