I suppose that: -cef is enabled -no QoS are in place (including nbar...) -no ACL with 'log' keyword (matching packets would be cpu switched) -no "logging debug" and debugging commands are used (flood of syslog messages) -only necessary routing protocols are used (if you have a stub area, a default route is enough) -no heavy routing protocol (e.g BGP) -if the link is between 2 ciscos, you could use HDLC rather than PPP. (I saw it lighter from a cpu point of view)
You can always send us your configuration, removing all your passwords and replacing your public IP addresses by private ones. Christophe -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gideon le Grange Sent: Friday, November 14, 2008 4:23 PM To: [email protected] Subject: Re: [c-nsp] 2610 High CPU Load On 14 Nov 2008, at 3:07 PM, Varaillon Jean Christophe wrote: > A "sho proc cpu sorted" would display which process(es) is actually > eating > your resources. > > I know, but it doesn't show anything useful. Nothing seems to be taking a noticeable amount of CPU. G _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ __________ Information from ESET Smart Security, version of virus signature database 3614 (20081114) __________ The message was checked by ESET Smart Security. http://www.eset.com __________ Information from ESET Smart Security, version of virus signature database 3614 (20081114) __________ The message was checked by ESET Smart Security. http://www.eset.com _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
