Re: [c-nsp] C6500 C6KERRDETECT-SP-2-FIFOCRITLEVEL

2007-10-14 Thread John I
Hi sukumar Kevin, Thank you both for your replies. Regarding the error: %C6KERRDETECT-SP-2-FIFOCRITLEVEL: System detected unrecoverable resources error on active supervisor port-asic This seems to have gone after a reload of the switch. It's only been 12 hours, but, I haven't seen that

[c-nsp] pruned routes, memory still low on Cisco 7507

2007-10-14 Thread neal rauhauser
I have some 7507s under my care with RSP4s taking full routes from Sprint and McLeod. We were getting tight on memory so we stopped accepting all /24s except 192.0.0.0/7. The memory usage reported by sh ip bgp su dropped from about 57 meg to half of that, but show proc mem still appears to be

Re: [c-nsp] pruned routes, memory still low on Cisco 7507

2007-10-14 Thread Oliver Boehmer (oboehmer)
neal rauhauser wrote on Sunday, October 14, 2007 6:40 PM: I have some 7507s under my care with RSP4s taking full routes from Sprint and McLeod. We were getting tight on memory so we stopped accepting all /24s except 192.0.0.0/7. The memory usage reported by sh ip bgp su dropped from about

Re: [c-nsp] CEF CPUHOG on GSR 12.0(S)

2007-10-14 Thread Oliver Boehmer (oboehmer)
David Freedman wrote on Sunday, October 14, 2007 2:34 PM: Recently we've been seeing some messages in the log with regards to a CPUHOG event occuring on some engine 2 linecards we have running. It didn't seem to be traffic affecting, and looked a little like this: SLOT 6:Oct 12 03:17:41

Re: [c-nsp] pruned routes, memory still low on Cisco 7507

2007-10-14 Thread neal rauhauser
I cleared them soft when I made the changes. I'll try a hard clear next - thanks. On 10/14/07, Oliver Boehmer (oboehmer) [EMAIL PROTECTED] wrote: neal rauhauser wrote on Sunday, October 14, 2007 6:40 PM: I have some 7507s under my care with RSP4s taking full routes from Sprint and

Re: [c-nsp] CEF CPUHOG on GSR 12.0(S)

2007-10-14 Thread Serguei Bezverkhi
Hello Peter, Based on the information provided by show cef event command, I can tell that CEF CPU Hog was due to a flapping 128.0.0.0/1 prefix. When this prefix gets installed in a line card forwarding, it is installed almost in the root of the forwarding table. It is CPU intensive and older