[c-nsp] Cisco 2851 bug ?

2008-07-11 Thread Teller, Robert
Is anyone aware of a bug or configuration that could cause a sudden spike in IP input? uptime is 26 weeks, 3 days, 10 hours, 54 minutes System returned to ROM by reload at 01:40:08 PST Tue Jan 8 2008 System restarted at 01:41:34 PST Tue Jan 8 2008 System image file is "flash:c2800nm-ipbasek9-mz.12

Re: [c-nsp] Cisco 2851 bug ?

2008-07-14 Thread Pavel Skovajsa
Hi, IP Input spike is usually caused by abnormal 'IP input' traffic that gets punted into the RP from CEF for whatever reason. A very common cause is broadcast storm. You can see what what packet is holding the CPU with 'show buffers input interface fa0/1'. However you need to do this command durin

Re: [c-nsp] Cisco 2851 bug ?

2008-07-15 Thread Rodney Dunn
Or you could load the new 12.4(20)T and set up a packet capture on the punt path. ;) rtp-rodunn-871#monitor capture point ip process-switched test in ? rtp-rodunn-871#monitor capture point ip process-switched rodney in rtp-rodunn-871#mon rtp-rodunn-871#monitor cap rtp-rodunn-871#monitor captur

Re: [c-nsp] Cisco 2851 bug ?

2008-07-15 Thread Paul Cosgrove
Hi Rodney, Is that safe to do even if the traffic rate and/or cpu is high? Looks like a nice feature. Paul. Rodney Dunn wrote: Or you could load the new 12.4(20)T and set up a packet capture on the punt path. ;) rtp-rodunn-871#monitor capture point ip process-switched test in ? rtp-rodun

Re: [c-nsp] Cisco 2851 bug ?

2008-07-16 Thread Rodney Dunn
Yep. Done in CEF path. Rodney On Tue, Jul 15, 2008 at 05:34:21PM +0100, Paul Cosgrove wrote: > Hi Rodney, > > Is that safe to do even if the traffic rate and/or cpu is high? > > Looks like a nice feature. > > Paul. > > Rodney Dunn wrote: > >Or you could load the new 12.4(20)T and set up a pac