Steve Bertrand wrote:
> My problem is the noticeable delay for switchover when the fibre happens
> to go down (God forbid).
>
> I would like to know if BGP timer adjustment is the way to adjust this,
> or if there is a better/different way. It's fair to say that the fibre
> doesn't 'flap'. Based
* Danny McPherson:
> On May 25, 2009, at 11:33 AM, Florian Weimer wrote:
>
>> * Iljitsch van Beijnum:
>>
>>> 30 60 isn't a good choice because that means that after 30.1
>>> seconds a
>>> keepalive comes in and then after 60.0 seconds the session will
>>> expire
>>> while the second one would be t
Cc: nanog@nanog.org
Subject: Re: IXP BGP timers (was: Multi-homed clients and BGP timers)
Hi Chris,
.-- My secret spy satellite informs me that at Mon, 25 May 2009, Chris Caputo
wrote:
> Would going below 60-180 without first discussing it with your peers, tend
> to piss them off?
Hi Chris,
.-- My secret spy satellite informs me that at Mon, 25 May 2009, Chris Caputo
wrote:
> Would going below 60-180 without first discussing it with your peers, tend
> to piss them off?
60-180 is fairly conservative. 60-180 is the Cisco default I believe, however
Junipers defaults are 30
On May 25, 2009, at 11:33 AM, Florian Weimer wrote:
* Iljitsch van Beijnum:
30 60 isn't a good choice because that means that after 30.1
seconds a
keepalive comes in and then after 60.0 seconds the session will
expire
while the second one would be there in 60.1 seconds.
Wouldn't the und
What's the BCP for BGP timers at exchange points?
I imagine if everyone did something low like 5-15 rather than the default
60-180, CPU usage increase could be significant given a high number peers.
Keeping in mind that "bgp fast-external-failover" is of no use at an
exchange since the fabric i
* Iljitsch van Beijnum:
> 30 60 isn't a good choice because that means that after 30.1 seconds a
> keepalive comes in and then after 60.0 seconds the session will expire
> while the second one would be there in 60.1 seconds.
Wouldn't the underlying TCP retry sooner than that?
We have customers in the same way you do. We only use Cisco (both pop
routers and managed cpe) and use
neighbor xxx.xxx.xxx.xxx timers 5 15
on the pop routers with great success. We haven't found any drawback so far.
// OK
On Sat, May 23, 2009 at 12:45 AM, Steve Bertrand wrote:
> Hi all,
>
> I
7;Steve Bertrand'; 'Jack Bates'
Cc: 'NANOG list'
Subject: RE: Multi-homed clients and BGP timers
For BFD to work, you need:
* ISR + 12.4(15)T (or later)
* 7200 with 12.4T or 12.2SRx
* 7600/6500/GSR + 12.2SRB (or later)
* ASR
A complete list is at the bottom of this docum
To: "nanog list"
Sent: Friday, May 22, 2009 3:45:20 PM GMT -08:00 US/Canada Pacific
Subject: Multi-homed clients and BGP timers
Hi all,
I've got numerous single-site 100Mb fibre clients who have backup SDSL
links to my PoP. The two services terminate on separate
distribut
> If you want to converge a little fast than BGP holdtimes here
> and the fiber link is directly between the routers, you might
> look at something akin to Cisco's "bgp
> fast-external-fallover", which immediately resets the session
> if the link layer is reset or lost.
For fast external fallo
For BFD to work, you need:
* ISR + 12.4(15)T (or later)
* 7200 with 12.4T or 12.2SRx
* 7600/6500/GSR + 12.2SRB (or later)
* ASR
A complete list is at the bottom of this document:
http://www.cisco.com/en/US/docs/ios/12_0s/feature/guide/fs_bfd.html
You'll find some more BFD details and usage gui
Jack Bates wrote:
> Steve Bertrand wrote:
>> Well, unfortunately, the local PUC owns the fibre, and they have a
>> switch aggregating all of their fibre in a star pattern. They then trunk
>> the VLANs to me across two redundant pair. I'm in the process of
>> persuading them to allow me to put my ow
Steve Bertrand wrote:
Well, unfortunately, the local PUC owns the fibre, and they have a
switch aggregating all of their fibre in a star pattern. They then trunk
the VLANs to me across two redundant pair. I'm in the process of
persuading them to allow me to put my own gear in their location so I
Danny McPherson wrote:
>
> On May 22, 2009, at 5:15 PM, Steve Bertrand wrote:
>>>
>>> neighbor xxx.xx.xx.x timers 30 60
>>>
>>> Make sure that this is communicated to your peer as well so that
>>> their timer setting are reflected the same.
>>
>> Thankfully at this point, we manage all CPE of any
> If you want to converge a little fast than BGP holdtimes here
> and the fiber link is directly between the routers, you might
> look at something akin to Cisco's "bgp fast-external-fallover",
> which immediately resets the session if the link layer is
> reset or lost.
>
Also things to consider:
On May 22, 2009, at 5:15 PM, Steve Bertrand wrote:
neighbor xxx.xx.xx.x timers 30 60
Make sure that this is communicated to your peer as well so that
their timer setting are reflected the same.
Thankfully at this point, we manage all CPE of any clients who peer
with
us, and so far, the
Zaid Ali wrote:
> From experience I found that you need to keep all the timers in sync with all
> your peers. Something like this for every peer in your bgp config.
>
> neighbor xxx.xx.xx.x timers 30 60
>
> Make sure that this is communicated to your peer as well so that their timer
> setting a
e same.
Zaid
- Original Message -
From: "Steve Bertrand"
To: "nanog list"
Sent: Friday, May 22, 2009 3:45:20 PM GMT -08:00 US/Canada Pacific
Subject: Multi-homed clients and BGP timers
Hi all,
I've got numerous single-site 100Mb fibre clients who have backup SDSL
li
Hi all,
I've got numerous single-site 100Mb fibre clients who have backup SDSL
links to my PoP. The two services terminate on separate
distribution/access routers.
The CPE that peers to my fibre router sets a community, and my end sets
the pref to 150 based on it. The CPE also sets a higher pref
20 matches
Mail list logo
