Not to skin a dead horse...
http://now.netapp.com/NOW/download/tools/ntaptop/
Display Top NFS Clients (netapp-top.pl) Note: This tool is unsupported - NetApp offers no support for it
If you would like to see a per-client summary of NFS activity on a NetApp filer, this Unix Perl script utility will help.
Here's some sample output:
NFS/s total NFS/s = 708 | interval = 60 ------ ---------------------------------------- 323 mercury.netapp.com 156 venus.netapp.com 113 earth.netapp.com 61 mars.netapp.com 48 jupiter.netapp.com 3 saturn.netapp.com 3 uranus.netapp.com 1 neptune.netapp.com
HTH
-john
John Witham MCSE, MCP+i, A+ Senior Systems Engineer Takeda Pharmaceuticals America, Inc. V://847.383.3304 F://847.383.3205 mailto://jwitham@takedapharm.com
-----Original Message----- From: Collins, Brian [mailto:brian.collins@netapp.com] Sent: Wednesday, January 10, 2001 7:51 AM To: 'Martin Hannigan'; BrianH@dice.com; toasters@mathworks.com Subject: RE: Net Stats, where from?
You might want to look at http://now.netapp.com/NOW/download/tools/filer-mrtg/ as well.
bc
-----Original Message----- From: Martin Hannigan [mailto:hannigan@fugawi.net] Sent: Wednesday, January 10, 2001 7:54 AM To: BrianH@dice.com; toasters@mathworks.com Subject: Re: Net Stats, where from?
Try MRTG. Do a google search. It's an SNMP tool that allows you to script "things" reported by SNMP.
At the minimum, run it against the filer and the switch for the office, if it's SNMP'able, and you should be able to see the port it's coming from..at a minimum.
But also, using stats on the filter to track down the file set is useful. I haven't had to do this in awhile, so I can't help you there.
-M
At 09:06 PM 1/9/2001 -0600, BrianH@dice.com wrote:
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