bgp scanner cpu usage == number of neighbors * number of routes in table lots of neighbors would cause this, for longer periods. If running SUP1A/MSFC this could be worse than with MSFC2 (slightly more CPU power), and much worse than SUP2 I'm guessing. 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...