nanog mailing list archives
RE: BGP peering strategies for smaller routers
From: Eric Sabotta <esabotta () whdh com>
Date: Tue, 3 May 2016 02:35:30 +0000
Mike, I just did this with a ASR1001. I had to upgrade it to 8gb of ram (I got the real Cisco stuff for ~ $500). Before the router would crash when loading the tables. Right now, I have full tables from two providers: router1#show ip bgp summary BGP router identifier 192.55.82.2, local AS number 4505 BGP table version is 11150622, main routing table version 11150622 582461 network entries using 144450328 bytes of memory 911730 path entries using 109407600 bytes of memory 148924/93298 BGP path/bestpath attribute entries using 36933152 bytes of memory 132977 BGP AS-PATH entries using 6043938 bytes of memory 0 BGP route-map cache entries using 0 bytes of memory 0 BGP filter-list cache entries using 0 bytes of memory BGP using 296835018 total bytes of memory BGP activity 962568/380103 prefixes, 5155645/4243915 paths, scan interval 60 secs Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd 192.55.82.3 4 4505 2532914 1634867 11150622 0 0 3w0d 330377 192.55.82.4 4 4505 672950 1634865 11150622 0 0 3w0d 1 209.117.103.33 4 2828 1837130 48052 11150557 0 0 2w1d 581351 router1#show ip cef summary IPv4 CEF is enabled for distributed and running VRF Default 582527 prefixes (582527/0 fwd/non-fwd) Table id 0x0 Database epoch: 2 (582527 entries at this epoch) -Eric -----Original Message----- From: NANOG [mailto:nanog-bounces () nanog org] On Behalf Of Mike Sent: Monday, May 2, 2016 3:07 PM To: NANOG list <nanog () nanog org> Subject: BGP peering strategies for smaller routers 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-
Current thread:
- Re: BGP peering strategies for smaller routers, (continued)
- Re: BGP peering strategies for smaller routers James Milko (May 02)
- Re: BGP peering strategies for smaller routers lincoln dale (May 02)
- Re: BGP peering strategies for smaller routers Mark Tinka (May 02)
- Re: BGP peering strategies for smaller routers Bob Evans (May 02)
- RE: BGP peering strategies for smaller routers Gustav Ulander (May 02)
- RE: BGP peering strategies for smaller routers Tony Wicks (May 02)
- Re: BGP peering strategies for smaller routers Blake Hudson (May 02)
- Re: BGP peering strategies for smaller routers Richard Hicks (May 02)
- Re: BGP peering strategies for smaller routers Mark Tinka (May 02)
- Re: BGP peering strategies for smaller routers William Herrin (May 03)
- RE: BGP peering strategies for smaller routers Eric Sabotta (May 03)
- Re: BGP peering strategies for smaller routers Mike (May 02)
- Re: BGP peering strategies for smaller routers Blake Hudson (May 03)
- Re: BGP peering strategies for smaller routers William Herrin (May 03)
- SV: BGP peering strategies for smaller routers Gustav Ulander (May 03)
- Re: BGP peering strategies for smaller routers William Herrin (May 03)
- Re: BGP peering strategies for smaller routers Nick Hilliard (May 03)
- Re: BGP peering strategies for smaller routers Ćukasz Bromirski (May 03)
- Re: BGP peering strategies for smaller routers William Herrin (May 03)
- Re: BGP peering strategies for smaller routers Nick Hilliard (May 03)
- Re: BGP peering strategies for smaller routers William Herrin (May 03)
- Re: BGP peering strategies for smaller routers Mike (May 02)
- Re: BGP peering strategies for smaller routers James Milko (May 02)