[186124] in North American Network Operators' Group
Re: route converge time
daemon@ATHENA.MIT.EDU (William Herrin)
Sat Nov 28 23:01:58 2015
X-Original-To: nanog@nanog.org
X-Really-To: <nanog@nanog.org>
In-Reply-To: <c15ef829639944ce873f5d2c39c07aa6@anx-i-dag02.anx.local>
From: William Herrin <bill@herrin.us>
Date: Sat, 28 Nov 2015 23:01:24 -0500
To: =?UTF-8?Q?J=C3=BCrgen_Jaritsch?= <jj@anexia.at>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
On Sat, Nov 28, 2015 at 10:45 PM, J=C3=BCrgen Jaritsch <jj@anexia.at> wrote=
:
>> From: Matthew Petach [mpetach@netflight.com]
>>
>> Or, better yet, apply a REJECT-ALL type policy
>> on the neighbor to deny all inbound/outbound
>> prefixes; that way, you can keep the session
>> up as long as possible, but gracefully bleed
>> traffic off ahead of your work.
> Route update via new policy could be more cpu intensive than dropping pre=
fixes caused by session shutdown.
Of course. But operable routes remain throughout.
However, you don't want to reject the routes you want to depreference
them, both received and sent. And depreference them on the router
whose link will stay up first, so that it starts sending traffic via
its link before the router you're taking down changes its routes. Once
the preference change moves all routes to the other router, then you
want to drop the BGP session to deal with the residual routes. Then
once traffic drops to zero on the link, you take down the link.
If your customers are really that sensitive to downtime during a
reasonable off-hours maintenance window.
Regards,
Bill Herrin
--=20
William Herrin ................ herrin@dirtside.com bill@herrin.us
Owner, Dirtside Systems ......... Web: <http://www.dirtside.com/>
