[f-nsp] [MLX-16] CAM lookup very slow

[Jan Pedersen]

It's safe (Unlike some of the mac debug commands).

You might need to redirect the debug messages to the telnet or ssh session you are using if you are not directly connected on the console port.


Best regards

Jan Pedersen
Senior Network Specialist
D: +45 7730 2932
M: +45 2550 7321

-----Original Message-----
From: foundry-nsp-bounces at puck.nether.net [mailto:foundry-nsp-bounces at puck.nether.net] On Behalf Of Youssef Ghorbal
Sent: 4. oktober 2010 15:04
To: foundry-nsp
Subject: Re: [f-nsp] [MLX-16] CAM lookup very slow

On Mon, Oct 4, 2010 at 1:50 PM, Niels Bakker
<niels=foundry-nsp at bakker.net> wrote:
> * youssef.ghorbal at gmail.com (Youssef Ghorbal) [Mon 04 Oct 2010, 13:16 CEST]:
>>
>> On Mon, Oct 4, 2010 at 12:02 PM, Niels Bakker
>> <niels=foundry-nsp at bakker.net> wrote:
>>>
>>> Yes, IronWare is quite monolithic.  Try looking at what packets are
>>> traversing this linecard's CPU.
>>
>> How can I "look" at what packets are traversion this Linecard's CPU ?
>
> debug packet capture

I was'nt aware of this command. Is it "safe" to run it on loaded
equipement ? or is it as a simple "tcpdump" on an *NIX machine ?
I was always looking for a packet capture facility...

Youssef Ghorbal

_______________________________________________
foundry-nsp mailing list
foundry-nsp at puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp