[190308] in North American Network Operators' Group
Re: 1GE L3 aggregation
daemon@ATHENA.MIT.EDU (Mark Tinka)
Thu Jun 23 01:54:32 2016
X-Original-To: nanog@nanog.org
To: David Charlebois <dcharlebois@gmail.com>, nanog@nanog.org
From: Mark Tinka <mark.tinka@seacom.mu>
Date: Thu, 23 Jun 2016 07:54:24 +0200
In-Reply-To: <CAOT81N9jd4ppkYPvBj9GHvH+3icLaR86YA6cB79wKytSmV8j2A@mail.gmail.com>
Errors-To: nanog-bounces@nanog.org
On 22/Jun/16 22:04, David Charlebois wrote:
> Hello
> I'm curious about the overall recommendation when selecting a small class
> BGP router for IPv6 (with 1gig ports). We can see the current IPv4 routing
> table is around 615k routes and the IPv6 routing table is sitting around
> ~31k routes.
>
> In our case, we advertise a single /24 from our head office to 2 upstream
> providers. The routing is %100 for redundancy.
>
> Somebody mentioned that the Brocade CER-RT was once a best seller. Brocade
> are now offering the CER 4X-RT version at 256K IPv6 routes supported (1.5M
> IPv4 routes). We don't have immediate plans for IPv6, but I do foresee this
> in a few year. Question is - is 256k IPv6 routes suitable?
The CER/CES NetIron boxes from Brocade are reasonable.
That said, BGP-SD implementations apply both to IPv4 and IPv6. So in a
Metro-E Access deployment scenario, the number of IPv6 routes would not
matter, as we only download into FIB the minimum necessary to keep the
box alive.
Mark.
