North American Network Operators Group
Date Prev | Date Next |
Date Index |
Thread Index |
Author Index |
Historical
AW: Getting a BGP table in to a lab
- From: John van Oppen
- Date: Thu Apr 21 17:26:08 2005
I agree... I have around 75 peers on a box that actually does the routing running quagga, and there appears to be no problem. My only issues have been with version upgrades having bugs in them, but those problems are due to my inadequate testing. I also utilize supervise scripts (daemontools)to keep all the
The best feature is being able to use the same route maps I use on my cisco boxes.
John :)
-----Ursprüngliche Nachricht-----
Von: Arnold Nipper [mailto:arnold@nipper.de]
Gesendet: Thursday, April 21, 2005 2:09 PM
An: Reeves, Rob
Cc: nanog@merit.edu
Betreff: Re: Getting a BGP table in to a lab
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
|
