perfsonar-user - Re: [perfsonar-user] bwctl -T iperf3 using wrong test?
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: Brian Tierney <>
- To: Aaron Brown <>
- Cc: "" <>, "" <>
- Subject: Re: [perfsonar-user] bwctl -T iperf3 using wrong test?
- Date: Wed, 15 Oct 2014 06:50:44 -0700
Alex:
Try doing a yum update iperf3 to make sure you have the newest version,
and make sure you dont have an older version of iperf3 in /usr/local/bin or some other location.
Also, did you really mean to do a 1 second test? Or did you want "-i1", not "-t1"
On Wed, Oct 15, 2014 at 5:48 AM, Aaron Brown <> wrote:
Hey Alex,
If you look at the version info, it’s using iperf3: "iperf version 3.0.1 (10 January 2014)”. It’s just an older version of iperf3, which may be the problem.
Cheers,
Aaron
On Oct 15, 2014, at 8:27 AM, <> <> wrote:
> Hi all,
>
> I've recently done a fresh install of Toolkit 3.4, and when running bwctl tests via the commandline i'm finding that bwctl is NOT using iperf3 even when being expressly told to:
>
> [root@nettest2 ~]# bwctl -t1 -T iperf3 -s nettest3 -vv
> Messages being sent to syslog(user,err)
> bwctl[8469]: FILE=util.c, LINE=466, BWLDiscoverSourceAddr(): Looking up address: nettest3
> bwctl[8469]: FILE=util.c, LINE=501, BWLDiscoverSourceAddr(): Returning: 1.1.1.1
> bwctl[8469]: FILE=bwctl.c, LINE=2739, Resolving nettest3
> bwctl[8469]: FILE=bwctl.c, LINE=2751, Current session is remote, using nettest3 as the address for client.
> bwctl[8469]: FILE=util.c, LINE=466, BWLDiscoverSourceAddr(): Looking up address: nettest3
> bwctl[8469]: FILE=util.c, LINE=501, BWLDiscoverSourceAddr(): Returning: 1.1.1.1
> bwctl[8469]: FILE=bwctl.c, LINE=2739, Resolving 1.1.1.1
> bwctl[8469]: FILE=bwctl.c, LINE=2751, Current session is local, using 1.1.1.1 as the address for server.
> bwctl[8469]: FILE=bwctl.c, LINE=2796, Available in-common: iperf nuttcp iperf3
> bwctl[8469]: FILE=bwctl.c, LINE=2821, Using tool: iperf3
> bwctl[8469]: FILE=bwctl.c, LINE=2908, Requested Time: 1413375726.190032
> bwctl[8469]: FILE=bwctl.c, LINE=2910, Latest Acceptable Time: 1413376326.190032
> bwctl[8469]: FILE=bwctl.c, LINE=3078, Reservation(localhost): 1413375733.587332
> bwctl[8469]: FILE=bwctl.c, LINE=2947, Server 'localhost' accepted test request at time 1413375733.587332
> bwctl[8469]: FILE=bwctl.c, LINE=3078, Reservation(nettest3): 1413375733.587332
> bwctl[8469]: FILE=bwctl.c, LINE=2971, Client 'nettest3' accepted test request at time 1413375733.587332
> bwctl[8469]: FILE=bwctl.c, LINE=3283, 9 seconds until test results available
>
> RECEIVER START
> bwctl: start_endpoint: 3622364525.939829
> bwctl: run_endpoint: receiver: 1.1.1.1
> bwctl: run_endpoint: sender: 2.2.2.2
> bwctl: run_tool: tester: iperf3
> bwctl: run_tool: receiver: 1.1.1.1
> bwctl: run_tool: sender: 2.2.2.2
> bwctl: start_tool: 3622364530.263081
> iperf version 3.0.1 (10 January 2014)
> Linux nettest2.diamond.ac.uk 2.6.32-431.29.2.el6.aufs.web100.x86_64 #1 SMP Wed Sep 10 05:45:30 PDT 2014 x86_64 x86_64 x86_64 GNU/Linux
> -----------------------------------------------------------
> Server listening on 5019
> -----------------------------------------------------------
> Time: Wed, 15 Oct 2014 12:22:13 GMT
> Accepted connection from 2.2.2.2, port 52277
> Cookie: nettest3.diamond.ac.uk.1413375733.58
> TCP MSS: 1448 (default)
> [ 17] local 1.1.1.1 port 5019 connected to 2.2.2.2 port 40169
> Starting Test: protocol: TCP, 1 streams, 131072 byte blocks, omitting 0 seconds, 1 second test
> [ ID] Interval Transfer Bandwidth
> [ 17] 0.00-1.00 sec 1.11 GBytes 9.51 Gbits/sec
> [ 17] 1.00-1.04 sec 44.6 MBytes 9.89 Gbits/sec
> - - - - - - - - - - - - - - - - - - - - - - - - -
> Test Complete. Summary Results:
> [ ID] Interval Transfer Bandwidth Retr
> [ 17] 0.00-1.04 sec 1.16 GBytes 9.60 Gbits/sec 0 sender
> [ 17] 0.00-1.04 sec 1.15 GBytes 9.53 Gbits/sec receiver
> CPU Utilization: local/receiver 18.8% (0.3%u/18.7%s), remote/sender 29.6% (0.8%u/30.5%s)
> bwctl: stop_tool: 3622364534.863543
> bwctl: stop_endpoint: 3622364535.864037
>
> RECEIVER END
>
>
> I know this worked in previous versions - we were using the extra "retries" output from iperf3 to track down a problem.
>
> Note that i'm telling bwctl to use iperf3, iperf3 is amongst the available test tools, and bwctl says "Using tool: iperf3" - but then it seems to use standard iperf - and gives the output from standard iperf?
>
> Thanks,
> Alex White
> Diamond Light Source
>
>
>
> --
> This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
> Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
> Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
> Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
>
>
>
>
Brian Tierney, http://www.es.net/tierney
Energy Sciences Network (ESnet), Berkeley National Lab
http://fasterdata.es.net
- [perfsonar-user] bwctl -T iperf3 using wrong test?, alex.white, 10/15/2014
- Re: [perfsonar-user] bwctl -T iperf3 using wrong test?, Aaron Brown, 10/15/2014
- Re: [perfsonar-user] bwctl -T iperf3 using wrong test?, Brian Tierney, 10/15/2014
- RE: [perfsonar-user] bwctl -T iperf3 using wrong test?, alex.white, 10/15/2014
- Re: [perfsonar-user] bwctl -T iperf3 using wrong test?, Brian Tierney, 10/15/2014
- Re: [perfsonar-user] bwctl -T iperf3 using wrong test?, Aaron Brown, 10/15/2014
Archive powered by MHonArc 2.6.16.