Yes and No.
You may want to add an aggregate statement,
followed with a corresponding static route.
ip route 198.32.64.0 255.255.255.0 fast 4/0
and maybe even
ip route 198.32.64.0 255.255.255.0 null 0 254
to re-enforce it.
(If fast 4/0 is experiencing intermittent but brief errors..
but still usable)
adding the aggregate network statement and summary only lines, will
result in the router
not so much announcing a local net and corresponding status, but more
proxy-aggregating it's own network. And as long as a route to that
network exists in the route-table, your router will *not* withdraw the
proxy aggregate route....
And one always will... The static route.
Voila, dampening.
(Ps. the null 0 ?will:should keep the route up even, when the interface
is dead... :(
But, that little trick is repairing the symptom. The cause is yet
undetermined.... I would re-check your counters on the FE again.
bmanning@ISI.EDU wrote:
>
> > That , or nail it up and insert the actual network into your BGP
> > tables.... Solid as rock then.
> > > >
> > > > router bgp 4555
> > > > no synchronization
> > > > bgp dampening
> > > > network 198.32.64.0
> > > > redistribute connected metric 50 weight 3500
> > >
> > > Isn't it better to nail up a static route for that network to null0, and
> > > redistribute static instead of connected?
>
> Er, the actual network is (or should be) inserted into the BGP table.
> Or at least thats what I thought the:
>
> network 198.32.64.0
>
> entry did...
>
> --
> --bill
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:13:13 EDT