[f-nsp] Debugging CPU usage on XMR

[Jeroen Wunnink | Atrato IP Networks]

Try disabling icmp redirects globally and/or no ip redirect on ve's


On 3/30/12 5:51 PM, Adam Davenport wrote:
> You can rconsole the MP (and/or LP's) and run the "debug packet 
> capture" command.  This will show you packets hitting the CPU on the 
> module.  The default output is 25 packets.  Running a "show cpu lp" 
> will also show CPU usage on the individual LP's which may make it 
> easier to single out the source of the CPU increase.
>
> Adam Davenport / adam at choopa.com
>
>
> On 3/30/2012 3:19 AM, Remco Bressers wrote:
>> Hi list,
>>
>> We are running a few XMR's in our network where one of them is showing
>> increased CPU usage on ip_rx. The box is not doing enormous amounts of
>> traffic (<10Gig) and a similar configuration on a different part of the
>> network isn't showing any CPU usage problems.
>> What is the best way to debug CPU issues like this and how can i get a
>> better insight in the way an XMR uses CPU cycles? A "show cpu" and "show
>> tasks" shows me what i already know and now i find it very hard to 
>> debug.
>>
>> Any ideas?
>>
>> Regards,
>>
>> Remco Bressers
>> Signet BV
>> _______________________________________________
>> foundry-nsp mailing list
>> foundry-nsp at puck.nether.net
>> http://puck.nether.net/mailman/listinfo/foundry-nsp
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp


-- 

Jeroen Wunnink
Network Engineer
Atrato IP Networks
jeroen.wunnink at atrato-ip.com
Phone: +31 20 82 00 623