Use 'pktt' on the filer to collect a packet trace. It's in tcpdump format. You can use ethereal (www.ethereal.org) to read the trace. From that you should be able to find the culprit.
You can use pktt as such: (my comments are in {})
pktt start e0 { this starts tracing e0 } pktt dump { this causes a file to be created with the content of the dump} pktt stop e0 { stops capturing packets on e0 }
THe interface name can be changed to 'all'. There are some other options to pktt. -d <dir> /* Specifies the directory to put trace in */ -b <buffersize> /* How big a buffer to use to capture packets... don't make this too large... never more than 1m */ -i <ipaddr> /* Self explanitory */
There are some other options. You can search for 'pktt' on NOW to get more info.
Aaron
-----Original Message----- From: BrianH@dice.com [mailto:BrianH@dice.com] Sent: Tuesday, January 09, 2001 10:07 PM To: toasters@mathworks.com Subject: Net Stats, where from?
Does anyone know a nice easy way to tell where network traffic is coming from? Something like nfssat -l where you can see that x% of your traffic comes from xxx.xxx.xxx.xxx or something like that? I have tons and tons of writes happending on my 740, which is killing the CPU. The problem is it just started the other day and it is killing the overall performance of the filer. nfsstat -l shows me the number of NFS ops, and none of them seem out of line at all.
Ideas?
--Brian