[c-nsp] High CPU Utilisation

[Rodney Dunn]

That's incorrect. If you have CEF on globally that enables it
for every interface in the box that is capable of doing CEF.
You should NEVER modify the per interface fastswitching/CEF flags
via the "ip route-cache <blah>" commands unless you do it just
as a SHORT TERM workaround for a switching path bug.

Rodney

On Mon, Jun 20, 2005 at 06:12:23AM -0400, Alex Rubenstein wrote:
> 
> 
> simply having 'ip cef' may not actually enable CEF on your interfaces.
> 
> Make sure you have at the least a 'ip route-cache', and, 'ip route-cache 
> cef' on your interface configs..
> 
> 
> 
> 
> On Mon, 20 Jun 2005, Gangasagar Amula wrote:
> 
> > Dear Saku,
> >
> > We have already used CEF....
> >
> > Any other Sugestions...
> >
> > Regs...Sagar.
> >
> >
> > On Mon, 20 Jun 2005 Saku Ytti wrote :
> >> conf term
> >> ip cef
> >> end
> >> write
> >>
> >>  If that doesn't help (you're already running CEF perhaps), you need
> >> to find what packets you're receiving for processing. Try looking
> >> at 'show buffers assigned packet', if there is something you shouldn't
> >> be receiving and either stop the sender sending them or put ACL before
> >> the box.
> >>
> >> --
> >>   ++ytti
> > _______________________________________________
> > cisco-nsp mailing list  cisco-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
> >
> 
> -- 
> Alex Rubenstein, AR97, K2AHR, alex at nac.net, latency, Al Reuben
> Net Access Corporation, 800-NET-ME-36, http://www.nac.net
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/