search

sudonym1 / iperf

Automatically exported from code.google.com/p/iperf
Other
0 stars 0 forks source link

Feature: SNMP statistics of a router connected to ISP #137

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Explanation of new feature:
I have added SNMP support to iperf which enables you to measure bandwidth on a 
router of a location for which you are making a TCP throughput test.
You give IP address of a router that goes from location to ISP and SNMP 
community as additional input settings and iperf reads 32-bit and 64-bit 
counters of all interfaces before and after the traffic is generated. Besides 
that it also reads CPU utilization of a router.

Justification of new feature:
Enables you to measure bandwidth when there is more cross traffic present from 
one to other locations.

Example of output:
================================================================================
=====
[TCP Sender  ] 0.00-2.02 sec  3.25 MBytes  13.5 Mbits/sec
[TCP Receiver] 0.00-2.02 sec  3.12 MBytes  13.0 Mbits/sec
--------------------------------------------------------------------------------
-----
SNMP Results - Max Traffic Seen & CPU Utilization
Time taken: 2.009 seconds
Time price: 1st request=8 ms, 2nd request=19 ms, 3rd request=6 ms

        32-bit counters: 13.79 Mbps on  FastEthernet0
                         13.18 Mbps on  Tunnel1
        64-bit counters: 13.78 Mbps on  FastEthernet0
                         13.17 Mbps on  Tunnel1

CPU last 5 sec utilization: 8 %
================================================================================
=====

Would does be useful for anyboday? I can add this...

Original issue reported on code.google.com by mark...@gmail.com on 27 Jan 2014 at 10:19

GoogleCodeExporter commented 9 years ago 
Hrm.  My first reaction is that this seems to be a little outside the scope of 
what iperf3 is designed to do.  Is there a specific use case where having this 
functionality inside iperf3 itself is useful?

Original comment by bmah@es.net on 30 Jan 2014 at 9:22

GoogleCodeExporter commented 9 years ago 
From jdugan@es.net (reposted with permission):

> I agree, I think this is outside the scope of iperf.  I can see a few cases 
where
> this would be handy but 99% of the time you don't know the SNMP community 
string for 
> the router and so you can't use it.
> 
> While I appreciate the effort I don't think we want to include this.

Apologies, but I'm going to close this as WontFix.

Original comment by bmah@es.net on 3 Feb 2014 at 10:57