[135208] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Dual Homed BGP for failover

daemon@ATHENA.MIT.EDU (Jack Bates)
Tue Jan 18 14:16:38 2011

Date: Tue, 18 Jan 2011 13:12:18 -0600
From: Jack Bates <jbates@brightok.net>
To: William Herrin <bill@herrin.us>
In-Reply-To: <AANLkTimF=uTuuPPhE7ouuw8gOMK7qq7QhN18zP_prinG@mail.gmail.com>
Cc: Ahmed Yousuf <ayousuf0079@gmail.com>, nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org



On 1/18/2011 1:00 PM, William Herrin wrote:
> IMO, that would be a mistake. Taking significantly less than a full
> table severely limits your options for balancing traffic between the
> links.
>

It should also be noted that taking a full table, doesn't mean you have 
to use the full table. Apply filters to smaller routes or long ASPATHs 
that you don't want, and then assign preferences, communities, prepends, 
etc as necessary for the routes you actually accept.

This means your sync time is longer and you'll have more updates, but it 
will still keep the local routing table much lower.


Jack


home help back first fref pref prev next nref lref last post