Hi
Smart switches can do that for you usually (if they're smart enought) so I would rather look here.
Greetings
_________________ Michael Bernardoff FSE@netapp +33 679 028 224
________________________________
De : Fox, Adam À : ggwalker@mindspring.com ; gtchen@yahoo-inc.com ; filip.sneppe@gmail.com ; toasters@mathworks.com Envoyé : Thu Sep 18 02:56:41 2008 Objet : Re: Identify traffic per IP address without using pktt
And there's a lun_top tool on the NOW Toolchest for SAN configs.
FYI
-- Adam Fox ------------------------ Typed with my thumbs on a very small keyboard.
----- Original Message ----- From: Glenn Walker ggwalker@mindspring.com To: George T Chen gtchen@yahoo-inc.com; Filip Sneppe filip.sneppe@gmail.com; Toasters toasters@mathworks.com Sent: Wed Sep 17 21:22:38 2008 Subject: RE: Identify traffic per IP address without using pktt
Similar is 'cifs top' if you have cifs.per_client_stats.enable set to 'on'. However, it gives you top talkers based on username (you'd have to use 'cifs sessions' to get the machine name\IP) and only for the last 3 second rolling average (though there are other options).
Not really a way to get what you're looking for, to my knowledge...
Glenn
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of George T Chen Sent: Wednesday, September 17, 2008 5:49 PM To: Filip Sneppe; Toasters Subject: RE: Identify traffic per IP address without using pktt
If the traffic is nfs, and you have nfs.per_client_stats.enable, then nfsstats -l gives the number of nfs requests per host.
-George
-----Original Message----- From: owner-toasters@mathworks.com
[mailto:owner-toasters@mathworks.com]
On Behalf Of Filip Sneppe Sent: Wednesday, September 17, 2008 2:21 PM To: Toasters Subject: Identify traffic per IP address without using pktt
Hi,
When using "sysstat" from the command line, it's very easy to get an idea of the network throughput that is currently being handled by the filer, and with commands like "vif stat" it's easy to get an idea on the interfaces that are transmitting or receiving this traffic.
However, I am wondering if is it possible to get an idea on the client IP addresses that are generating most of the network traffic without having to resort to pktt every time, then copying over the capture file and analyzing it afterwards ?
Are there any counters availble from a command that show how much
traffic
a particular IP address has sent/received ? I tried various commands (eg. netstat has a few interesting options) but couldn't find anything that solved my
problem.
At the moment, if I need to determine the hosts that are using most of
the
iSCSI or NFS bandwidth, I have to resort to pktt, and I am looking for a
easier
way to achieve what I want. Ideally, I'd like to get information on the protocols and ports involved too, but having IP addresses would already be very useful.
Best regards, Filip
sFlow will get this for you if your switches support it however you will need a sFlow collector too.
From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Bernardoff, Michael Sent: Thursday, 18 September 2008 3:59 PM To: Fox, Adam; ggwalker@mindspring.com; gtchen@yahoo-inc.com; filip.sneppe@gmail.com; toasters@mathworks.com Subject: Re: Identify traffic per IP address without using pktt
Hi
Smart switches can do that for you usually (if they're smart enought) so I would rather look here.
Greetings
_________________ Michael Bernardoff FSE@netapp +33 679 028 224
________________________________ De : Fox, Adam À : ggwalker@mindspring.com ; gtchen@yahoo-inc.com ; filip.sneppe@gmail.com ; toasters@mathworks.com Envoyé : Thu Sep 18 02:56:41 2008 Objet : Re: Identify traffic per IP address without using pktt
And there's a lun_top tool on the NOW Toolchest for SAN configs.
FYI
-- Adam Fox ------------------------ Typed with my thumbs on a very small keyboard.
----- Original Message ----- From: Glenn Walker ggwalker@mindspring.com To: George T Chen gtchen@yahoo-inc.com; Filip Sneppe filip.sneppe@gmail.com; Toasters toasters@mathworks.com Sent: Wed Sep 17 21:22:38 2008 Subject: RE: Identify traffic per IP address without using pktt
Similar is 'cifs top' if you have cifs.per_client_stats.enable set to 'on'. However, it gives you top talkers based on username (you'd have to use 'cifs sessions' to get the machine name\IP) and only for the last 3 second rolling average (though there are other options).
Not really a way to get what you're looking for, to my knowledge...
Glenn
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of George T Chen Sent: Wednesday, September 17, 2008 5:49 PM To: Filip Sneppe; Toasters Subject: RE: Identify traffic per IP address without using pktt
If the traffic is nfs, and you have nfs.per_client_stats.enable, then nfsstats -l gives the number of nfs requests per host.
-George
-----Original Message----- From: owner-toasters@mathworks.com
[mailto:owner-toasters@mathworks.com]
On Behalf Of Filip Sneppe Sent: Wednesday, September 17, 2008 2:21 PM To: Toasters Subject: Identify traffic per IP address without using pktt
Hi,
When using "sysstat" from the command line, it's very easy to get an idea of the network throughput that is currently being handled by the filer, and with commands like "vif stat" it's easy to get an idea on the interfaces that are transmitting or receiving this traffic.
However, I am wondering if is it possible to get an idea on the client IP addresses that are generating most of the network traffic without having to resort to pktt every time, then copying over the capture file and analyzing it afterwards ?
Are there any counters availble from a command that show how much
traffic
a particular IP address has sent/received ? I tried various commands (eg. netstat has a few interesting options) but couldn't find anything that solved my
problem.
At the moment, if I need to determine the hosts that are using most of
the
iSCSI or NFS bandwidth, I have to resort to pktt, and I am looking for a
easier
way to achieve what I want. Ideally, I'd like to get information on the protocols and ports involved too, but having IP addresses would already be very useful.
Best regards, Filip
************************************************************************************ This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses. ************************************************************************************