perfSONAR User Q&A and Other Discussion

["Jeff W. Boote" <>]

On Nov 3, 2008, at 3:31 AM, Jason Zurawski wrote:

> Vicky;
>
> > Hi jason :
> > Thank you for your answer. I am work in client as follows:
> > USER@HOST2:~$
> >  bwctl -c HOST1
> > bwctl: 25 seconds until test results available
> > RECEIVER START
> > bwctl: thrulay_server: streams=1,win_size=4194304
> > bwctl: start_tool: 3434684143.053010
> > 11/03/2008 14:55:43 thrulayd started, listening on port 5003 with  
> > window
> > size 219136
> > 11/03/2008 14:55:49 connection from ::ffff: HOST_IP
> > bwctl: stop_exec: 3434684159.744133
> > 11/03/2008 14:55:59 TCP test duration = 10.015s, average throughput =
> > 94.078Mb/s, CPU user/sys time = 0.077/0.565s
> > RECEIVER END
> > Why the message didn't show " bwctl: Using tool: iperf" as you  
> > shown? Is my
> > message is right?  What's the the tool use of bwctl ?
>
>
> I used an older version of BWCTL (pre 1.3) for testing.  The older  
> versions only used iperf as a tool, and did not support the -T  
> option. By default thurlay is the testing tool on the new versions  
> (what ran above).  Here is the same test using a newer BWCTL and  
> choosing the iperf tool:

Just a minor correction.

Iperf is still the preferred tool for 1.3, if it is installed and  
found. Iperf needs to be in the 'path' of the process, or the full  
path explicitly configured in the bwctld.conf (if contacting a bwctld)  
or .bwctlrc file (if no bwctld is running, and the client is executing  
the test directly).

bwctl 1.3 looks at the tools available from both sides of the test and  
picks the first one that is common to both sides (if the -T is not  
specified). thrulay is in fact the tool of last resort since it is  
directly compiled in.

jeff

> Server:
>
> [zurawski@HOST1
>  ~]$ /usr/local/bin/bwctld -Zc /usr/local/etc
> bwctld[2065]: FILE=nuttcp.c, LINE=175, NuttcpAvailable(): We were  
> unable to verify that nuttcp is working. Likely you do not have it  
> installed. exit status: 1: output: exec(nuttcp): No such file or  
> directory
> bwctld[2065]: FILE=tools.c, LINE=255, Couldn't initialize tool  
> "nuttcp". Disabling it.
>
> Client using '-s' option:
>
> [zurawski@HOST2
>  ~]$ /usr/local/bin/bwctl -T iperf -s HOST1
> bwctl: Unable to contact a local bwctld: Spawning local tool  
> controller
> bwctl: NuttcpAvailable(): We were unable to verify that nuttcp is  
> working. Likely you do not have it installed. exit status: 1:  
> output: exec(nuttcp): No such file or directory
> bwctl: Couldn't initialize tool "nuttcp". Disabling it.
> bwctl: 27 seconds until test results available
>
> RECEIVER START
> bwctl: exec_line: iperf -B HOST2 -s -f b -m -p 5001 -t 10
> bwctl: start_tool: 3434696767.528693
> ------------------------------------------------------------
> Server listening on TCP port 5001
> Binding to local address HOST2
> TCP window size: 87380 Byte (default)
> ------------------------------------------------------------
> [ 12] local HOST2 port 5001 connected with HOST1 port 5001
> [ ID] Interval       Transfer     Bandwidth
> [ 12]  0.0-10.3 sec  58572800 Bytes  45358700 bits/sec
> [ 12] MSS size 1448 bytes (MTU 1500 bytes, ethernet)
> bwctl: stop_exec: 3434696787.817773
>
>
> Client using '-c' option:
>
> [zurawski@HOST2
>  ~]$ /usr/local/bin/bwctl -T iperf -c HOST1
> bwctl: Unable to contact a local bwctld: Spawning local tool  
> controller
> bwctl: NuttcpAvailable(): We were unable to verify that nuttcp is  
> working. Likely you do not have it installed. exit status: 1:  
> output: exec(nuttcp): No such file or directory
> bwctl: Couldn't initialize tool "nuttcp". Disabling it.
> bwctl: 28 seconds until test results available
>
> RECEIVER START
> bwctl: exec_line: iperf -B HOST1 -s -f b -m -p 5003 -t 10
> bwctl: start_tool: 3434696986.455201
> ------------------------------------------------------------
> Server listening on TCP port 5003
> Binding to local address HOST1
> TCP window size: 87380 Byte (default)
> ------------------------------------------------------------
> [ 15] local HOST1 port 5003 connected with HOST2 port 5003
> [ 15]  0.0-10.1 sec  56057856 Bytes  44403243 bits/sec
> [ 15] MSS size 1448 bytes (MTU 1500 bytes, ethernet)
> bwctl: stop_exec: 3434697007.023277
>
> RECEIVER END
>
>
> -jason
>
>
>
> > Thanks,
> > Vicky
> > -----Original Message-----
> > From: Jason Zurawski [mailto:] Sent: Friday,  
> > October 31, 2008 5:40 PM
> > To: 
> >
> > Cc: 
> > ;
> >  
> >
> > Subject: Re: [perfsonar-user] perfSONAR-BUOY BWCTL problem
> > Vicky;
> > > Hi all:
> > > I try to run the bwctl tool from the command line, I set the  
> > > "bwctl -T
> > iperf -s <server IP>" in client and set "bwctl -c" in server, but  
> > the client
> > window shown the message "bwctl: 25 seconds until test results  
> > available
> > > RECEIVER START
> > > bwctl: Remote 'sender' never initiated handshake - canceling
> > > RECEIVER END
> > > "
> > > What's the problem? How can I user bwctl's tool(iperf) to run in the
> > command line ?
> > Please read all of the instructions before proceeding, they  
> > describe the proper steps to take:
> > http://e2epi.internet2.edu/bwctl/#Build
> > Note that 'bwctl' is the client program, and 'bwctld' is the  
> > server. The server will be started as such (using the -Z option  
> > here to keep the server open in the terminal and the bwctld.conf  
> > file is installed in '/usr/local/etc'):
> > USER@HOST1:~$
> >  /usr/local/bin/bwctld -Zc /usr/local/etc
> > bwctld[22356]: FILE=bwctld.c, LINE=1573, The data_dir option has  
> > been depricated, ignoring...
> > bwctld[22356]: FILE=nuttcp.c, LINE=175, NuttcpAvailable(): We were  
> > unable to verify that nuttcp is working. Likely you do not have it  
> > installed. exit status: 1: output: exec(nuttcp): No such file or  
> > directory
> > And the client should work as such:
> > USER@HOST2:~$
> >  bwctl -c HOST1
> > bwctl: Using tool: iperf
> > bwctl: 22 seconds until test results available
> > RECEIVER START
> > bwctl: exec_line: iperf -B HOST1 -s -f b -m -p 5002 -t 10
> > bwctl: start_tool: 3434434010.222274
> > ------------------------------------------------------------
> > Server listening on TCP port 5002
> > Binding to local address HOST1
> > TCP window size: 87380 Byte (default)
> > ------------------------------------------------------------
> > [ 15] local HOST1 port 5002 connected with HOST2 port 5002
> > [ ID] Interval       Transfer     Bandwidth
> > [ 15]  0.0-10.1 sec  59973632 Bytes  47345214 bits/sec
> > [ 15] MSS size 1448 bytes (MTU 1500 bytes, ethernet)
> > bwctl: stop_exec: 3434434030.351189
> > or
> > USER@HOST2:~$
> >  bwctl -s HOST1
> > bwctl: Using tool: iperf
> > bwctl: 29 seconds until test results available
> > RECEIVER START
> > bwctl: exec_line: /usr/local/bin/iperf -B HOST2 -s -f b -m -p 5001 - 
> > t 10
> > bwctl: start_tool: 3434434168.196122
> > ------------------------------------------------------------
> > Server listening on TCP port 5001
> > Binding to local address HOST2
> > TCP window size: 87380 Byte (default)
> > ------------------------------------------------------------
> > [ 14] local HOST2 port 5001 connected with HOST1 port 5001
> > [ 14]  0.0-10.1 sec  58490880 Bytes  46450766 bits/sec
> > [ 14] MSS size 1448 bytes (MTU 1500 bytes, ethernet)
> > bwctl: stop_exec: 3434434188.695510
> > RECEIVER END
> > Thanks;
> > -jason