[179236] in North American Network Operators' Group
Re: BGP offloading (fixing legacy router BGP scalability issues)
daemon@ATHENA.MIT.EDU (Baldur Norddahl)
Fri Apr 3 21:55:38 2015
X-Original-To: nanog@nanog.org
In-Reply-To: <FAC2AC34-C211-4FD8-BABE-B80621B954AA@gizmopartners.com>
Date: Sat, 4 Apr 2015 03:55:34 +0200
From: Baldur Norddahl <baldur.norddahl@gmail.com>
To: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
The SIR approach might not work if your switch does not support selective
installing routes. Also the switch might have a very slow CPU and be memory
constrained, making downloading a large number of routes impractical even
if you do not install all.
IX and transit providers are making this harder that it needs to be. Just
allow two IP and MAC addresses on the peering network. Then you can just
have a server running BIRD directly on the peering network using next hop
attribute to redirect traffic through the switch.
Actually I believe Cogent offers /29 on the peering link so you can do
exactly that.
Regards
Baldur
Den 03/04/2015 21.19 skrev "Chris Boyd" <cboyd@gizmopartners.com>:
> Can we please get back to the original topic?
>
> So far we have had one interesting and useful suggestion that I've seen --
> Paul S. mentioned SIR https://github.com/dbarrosop/sir
>
> Have I missed any other solutions other than the prefix length filtering?
>
> --Chris
>
>
