[179638] in North American Network Operators' Group
RE: Euro-IX quagga stable download and implementation
daemon@ATHENA.MIT.EDU (=?iso-8859-2?Q?Goran_Slavi=E6?=)
Sat Apr 25 19:42:47 2015
X-Original-To: nanog@nanog.org
From: =?iso-8859-2?Q?Goran_Slavi=E6?= <gslavic@sox.rs>
To: "'Andy Davidson'" <andy@nosignal.org>
In-Reply-To: <54BC7947-5766-447F-B1A2-7BB137411F98@nosignal.org>
Date: Sat, 25 Apr 2015 22:06:11 +0200
Cc: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
Andy,
=09
Believe me when I say: I would never have the idea to think about
attempting to try to test my ability to generate configurations for this =
"2
route servers/ 2 different programs that run them" solution without the =
IXP
Manager :-)
I am familiar with the work INEX has been doing with IXP Manager and
have for some time attempted to find time from regular SOX operation to
implement it in our IX. This migration gives me the excellent =
opportunity
and arguments to finally allocate time, resources and manpower for
installation and implementation of IXP Manager as the route server
configuration generator at SOX.
=09
Regards
G.Slavic
-----Original Message-----
From: Andy Davidson [mailto:andy@nosignal.org]=20
Sent: Saturday, 25 April 2015 21:34
To: Goran Slavi=E6
Cc: nanog@nanog.org
Subject: Re: Euro-IX quagga stable download and implementation
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
consistency 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, maintained 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-server
hygiene.
There's also a historic perl-script that does this on my personal =
github.
Both of these solutions allow you to filter route-server participants =
based
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't link to it as you should really =
use
IXP Manager. :-)
Andy=3D
