[189056] in North American Network Operators' Group
Re: BGP peering strategies for smaller routers
daemon@ATHENA.MIT.EDU (Richard Hicks)
Mon May 2 18:12:19 2016
X-Original-To: nanog@nanog.org
In-Reply-To: <5727A554.1090202@tiedyenetworks.com>
Date: Mon, 2 May 2016 13:32:14 -0700
From: Richard Hicks <richard.hicks@gmail.com>
To: Mike <mike-nanog@tiedyenetworks.com>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
Careful with the ASR1000 and full tables at 4GB.
http://www.gossamer-threads.com/lists/cisco/nsp/180710
I recommend adding some third party RAM to get 16GB.
On Mon, May 2, 2016 at 12:07 PM, Mike <mike-nanog@tiedyenetworks.com> wrote:
> Hello,
>
> I have an ASR1000 router with 4gb of ram. The specs say I can get '1
> million routes' on it, but as far as I have been advised, a full table of
> internet routes numbers more than 530k by itself, so taking 2 full tables
> seems to be out of the question (?).
>
> I am looking to connect to a second ip transit provider and I'm
> looking for any advice or strategies that would allow me to take advantage
> and make good forwarding decisions while not breaking the bank on bgp
> memory consumption. I simply don't understand how this would likely play
> out and what memory consumption mitigation steps may be necessary here. Im
> open to ideas... a pair of route reflectors? selective bgp download? static
> route filter maps?
>
> Thank you.
>
> Mike-
>
>
