[c-nsp] GSR CPU Process is very HIGH 95%

Eninja eninja at gmail.com
Wed Oct 7 12:45:56 EDT 2009


Bharath,

Several things can cause RP (or LC) CPU spike at interrupt level. What  
does a 'sh align', 'sh int stat', 'sh ver' and 'sh diag summ' say? If  
they reveal no clues, you may have to profile the CPU.

Oli,

"Contact TAC" should probably be re-phrased to say "contact your  
maintenance service provider" - which may or may not be Cisco ;-)

Eninja


On Oct 7, 2009, at 3:22 PM, "Oliver Boehmer (oboehmer)" <oboehmer at cisco.com 
 > wrote:

> bharath kondi <mailto:bluffmaster4hearts at gmail.com> wrote on  
> Wednesday,
> October 07, 2009 15:10:
>>   are you switching traffic across the PRP/GRP's Management
> Ethernet
>>   ports? Those must only be used for management, i.e. traffic
> from/to
>>   the GSR ..
>>
>> Dear Oliver,
>>
>> No.
>
> hmm, your high interrupt load (the 71 in "CPU utilization for five
> seconds: 95%/71%") suggests that the RP's CPU switches traffic, which
> should not happen on a GSR as all traffic is switched by hardware..
> It requires a closer look at the config and linecards to see what  
> could
> cause this. I'd contact TAC..
>
>   oli
> _______________________________________________
> 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/



More information about the cisco-nsp mailing list