[80031] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Getting a BGP table in to a lab

daemon@ATHENA.MIT.EDU (Arnold Nipper)
Thu Apr 21 17:09:11 2005

Date: Thu, 21 Apr 2005 23:08:38 +0200
From: Arnold Nipper <arnold@nipper.de>
To: "Reeves, Rob" <rreeves@arbinet.com>
Cc: nanog@merit.edu
In-Reply-To: <CC74E7E10A8A054798B6611BD1FEF4D30791D70F@vamail01.thexchange.com>
Errors-To: owner-nanog@merit.edu


On 21.04.2005 17:17 Reeves, Rob wrote

> 
> Quagga is great for smaller implementations, but it doesn't scale very
> well.  It eats up a lot of CPU, so once you hit a certain number of BGP
> peers, it may start intermittently flapping BGP sessions, or even just
> crash the bgpd process entirely. 

For what numbers? I've two quaggas, ~150 peers each, doing as-path and 
*full* prefix filtering for each peer (Config is around 9MB). CPU is 
idle 99.x% mostly ...





Arnold
-- 
Arnold Nipper, AN45

home help back first fref pref prev next nref lref last post