[179635] in North American Network Operators' Group
Re: Euro-IX quagga stable download and implementation
daemon@ATHENA.MIT.EDU (Andy Davidson)
Sat Apr 25 15:34:22 2015
X-Original-To: nanog@nanog.org
From: Andy Davidson <andy@nosignal.org>
To: =?windows-1250?Q?Goran_Slavi=E6?= <gslavic@sox.rs>
Date: Sat, 25 Apr 2015 19:34:17 +0000
In-Reply-To: <002101d07f8c$67f67b20$37e37160$@rs>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
On 25 Apr 2015, at 15:16, Goran Slavi=E6 <gslavic@sox.rs> wrote:
> Considering what I have learned in your posts (and on other places
> that I have informed myself) I will definitely suggest to SOX management =
to
> go the way similar to what LINX did (1 Bird + 1 Quagga as route servers) =
for
> the simple reason that 2 different solution provides more security in
> context of "new program update->new bugs" problems and incidents and
> prevents other potential problems.
Goran - glad to have helped.
One last piece of advice which might be useful - to help to guarantee consi=
stency of performance between the two route-servers, you should consider a =
configuration generator so that your route-server configs are in sync. The=
best way to implement this at your exchange is to use IXP Manager, maintai=
ned by the awesome folks at the Irish exchange point, INEX. https://github=
.com/inex/IXP-Manager
IXP Manager will get you lots of other features as well as good route-serve=
r hygiene.
There=92s also a historic perl-script that does this on my personal github.=
Both of these solutions allow you to filter route-server participants bas=
ed on IRR data, which has proved to be a life-saver at all of the exchanges=
I help to operate. Having my horrible historic thing is maybe better than=
no thing at all, but I deliberately won=92t link to it as you should reall=
y use IXP Manager. :-)
Andy=
