[42550] in North American Network Operators' Group
Re: What Worked - What Didn't
daemon@ATHENA.MIT.EDU (Mike Lewinski)
Mon Sep 17 18:13:58 2001
Message-ID: <003201c13fc5$ec4c11c0$8f65bccc@domain.com>
From: "Mike Lewinski" <mike@rockynet.com>
To: "Mike Rae" <mrae@wcom.ca>, <nanog@merit.edu>
Date: Mon, 17 Sep 2001 16:13:00 -0600
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Errors-To: owner-nanog-outgoing@merit.edu
> Are you aware of any "downside" to implementing this command ?
I opted against using it on our network, after considering the
consequences of having an eBGP link go down for a few seconds repeatedly
(which has actually happened here twice in my memory). Under this
circumstance the fast-external-fallover would probably have caused our
routes to be dampened.
Other than that, I think it's probably a bonus that a single very brief
failure on an eBGP link doesn't require the tables to be reset.
Mike
> ----- Original Message -----
> From: "Mike Lewinski" <mike@rockynet.com>
> To: <nanog@merit.edu>
> Sent: Monday, September 17, 2001 3:38 PM
> Subject: Re: What Worked - What Didn't
>
>
> >
> > > But speaking of BGP: what concerns me is the very long timeouts.
When
> > a
> > > BGP router loses power, it takes minutes for the peer on the other
> > side of
> > > the connection to notice something is wrong and reroute the
traffic.
> >
> > This IOS command should remedy that under most circumstances:
> >
> > bgp fast-external-fallover
> >
> >
> > Mike
> >
>
>
