sh proc cpu | exclude 0.00 CPU utilization for five seconds: 88%/63%; one minute: 89%; five minutes: 89% PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process 4 6029 389 15498 1.11% 0.16% 0.12% 0 Check heaps
9 2883 5699 505 0.15% 0.06% 0.07% 0 ARP Input * 51 40119 129588 309 0.63% 1.22% 1.27% 0 Fifo Error Detec* 67 2973 78578 37 0.15% 0.10% 0.08% 0 HLFM address ret 81 16566 41729 396 0.79% 0.43% 0.43% 0 hpm main process *115 190582 60871 3130 6.86% 6.03% 6.01% 0 Hulc LED Process* 123 5054 576 8774 0.31% 0.19% 0.16% 0 HQM Stack Proces 136 25648 2746 9340 1.27% 0.77% 0.74% 0 PI MATM Aging Pr 1*68 308273 1603815 192 9.10% 9.49% 9.82% 0 IP Input * * * *Cisco doc reads the HULC LED is a possible link flapping yet nothing in logs indicate.* * * On Fri, Apr 24, 2009 at 5:12 AM, Chris Lane <[email protected]> wrote: > sh ip cef switching statistics feature > IPv4 CEF input features: > Feature Drop Consume Punt Punt2Host Gave > route > Total 0 0 0 0 > 0 > > IPv4 CEF output features: > Feature Drop Consume Punt Punt2Host New > i/f > Total 0 0 0 0 > 0 > > IPv4 CEF post-encap features: > Feature Drop Consume Punt Punt2Host New > i/f > Total 0 0 0 0 > 0 > > IPv4 CEF for us features: > Feature Drop Consume Punt Punt2Host New > i/f > Total 0 0 0 0 > 0 > > > > On Fri, Apr 24, 2009 at 2:31 AM, Peter Rathlev <[email protected]> wrote: > >> On Thu, 2009-04-23 at 19:09 -0400, Chris Lane wrote: >> > sh platform tcam utilization >> > >> > CAM Utilization for ASIC# 0 Max Used >> ... >> >> Hm... nothing there (unless the other ASICs show dissimilar results). If >> the problem is punted traffic, maybe "show ip cef switching statistics >> feature" can tell you what it is. >> >> It could also be traffic directed at the switch itself of course. >> >> Regards, >> Peter >> >> >> >> > > > -- > //CL > -- //CL _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
