|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
Date: Mon, 13 Oct 2003 17:54:44 -0400 From: Richard A Steenbergen <ras@e-gerbil.net> To: "Tom (UnitedLayer)" <tom@unitedlayer.com> Cc: sthaug@nethelp.no, nanog@merit.edu In-Reply-To: <20031013141249.X38950-100000@smtp.unitedlayer.com> Errors-To: owner-nanog-outgoing@merit.edu On Mon, Oct 13, 2003 at 02:15:59PM -0700, Tom (UnitedLayer) wrote: > > On Mon, 13 Oct 2003 sthaug@nethelp.no wrote: > > Maybe you could expand on the BGP scanner problems - we haven't seen > > them all the time we've been running 6500 native with full routes (about > > 1.5 years now). > > BGP Scanner taking up close to 100% of CPU on a box periodically. > GSR doesn't seem to do it, but a buncha other cisco boxes do. > Its more irritating than anything else, especially when customers complain > that when they traceroute they see ~200ms latency to the router... On the GSR, dCEF is turned on by default, and the GRP does the bgp processing while the linecards continue to forward packets without interruption (well at least until an update comes in and dCEF starts pointing the packets out the wrong interface at any rate). :P -- Richard A Steenbergen <ras@e-gerbil.net> http://www.e-gerbil.net/ras GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)
|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |