perfSONAR User Q&A and Other Discussion

[Brian Tierney <>]

I'm not aware of anything that might explain that. Can you try iperf3 and nuttcp to see if they behave the same?

On Mon, Jan 26, 2015 at 12:22 PM, Trey Dockendorf <> wrote:

Right now most of the endpoints I'm testing against seem to not work with bwctl so to help some colleagues I've been trying to just use iperf by itself.  From my perfsonar boxes the iperf tests seem to do nothing while a non-perfsonar host with iperf installed from EPEL gives expected output.  The results are below.  I've removed the remote information as these were not against a perfsonar box but a remote site's cluster login node.

Is there something about iperf on a PS host that could cause this issue?  The 2 systems below are on same network and same core switch.

PERFSONAR:

# iperf -c <REMOTE HOST> -p 50100 -t 20 -i 1

------------------------------------------------------------

Client connecting to <REMOTE HOST>, TCP port 50100

TCP window size: 92.6 KByte (default)

------------------------------------------------------------

[  3] local 165.91.55.6 port 33135 connected with <REMOTE IP> port 50100

[ ID] Interval       Transfer     Bandwidth

[  3]  0.0- 1.0 sec   175 KBytes  1.43 Mbits/sec

[  3]  1.0- 2.0 sec  0.00 Bytes  0.00 bits/sec

[  3]  2.0- 3.0 sec  0.00 Bytes  0.00 bits/sec

<Repeated 100s of times with 0.00 bits/sec>

[  3] 931.0-932.0 sec  0.00 Bytes  0.00 bits/sec

NON-PERFSONAR:

$ iperf -c <REMOTE HOST> -p 50100 -t 20 -i 1

------------------------------------------------------------

Client connecting to <REMOTE HOST>, TCP port 50100

TCP window size: 92.6 KByte (default)

------------------------------------------------------------

[  3] local 165.91.55.28 port 51252 connected with <REMOTE IP> port 50100

[ ID] Interval       Transfer     Bandwidth

[  3]  0.0- 1.0 sec  60.5 MBytes   508 Mbits/sec

[  3]  1.0- 2.0 sec  30.5 MBytes   256 Mbits/sec

[  3]  2.0- 3.0 sec  32.9 MBytes   276 Mbits/sec

[  3]  3.0- 4.0 sec  36.2 MBytes   304 Mbits/sec

[  3]  4.0- 5.0 sec  36.6 MBytes   307 Mbits/sec

[  3]  5.0- 6.0 sec  25.1 MBytes   211 Mbits/sec

[  3]  6.0- 7.0 sec  27.2 MBytes   229 Mbits/sec

[  3]  7.0- 8.0 sec  33.5 MBytes   281 Mbits/sec

[  3]  8.0- 9.0 sec  32.2 MBytes   271 Mbits/sec

[  3]  9.0-10.0 sec  31.9 MBytes   267 Mbits/sec

[  3] 10.0-11.0 sec  24.9 MBytes   209 Mbits/sec

[  3] 11.0-12.0 sec  29.9 MBytes   251 Mbits/sec

[  3] 12.0-13.0 sec  36.8 MBytes   308 Mbits/sec

[  3] 13.0-14.0 sec  33.0 MBytes   277 Mbits/sec

[  3] 14.0-15.0 sec  21.6 MBytes   181 Mbits/sec

[  3] 15.0-16.0 sec  16.6 MBytes   139 Mbits/sec

[  3] 16.0-17.0 sec  22.0 MBytes   185 Mbits/sec

[  3] 17.0-18.0 sec  23.6 MBytes   198 Mbits/sec

[  3] 18.0-19.0 sec  23.5 MBytes   197 Mbits/sec

[  3] 19.0-20.0 sec  19.2 MBytes   161 Mbits/sec

[  3]  0.0-20.0 sec   598 MBytes   250 Mbits/sec

Thanks,

- Trey

=============================

Trey Dockendorf 

Systems Analyst I 

Texas A&M University 

Academy for Advanced Telecommunications and Learning Technologies 

Phone: (979)458-2396 

Email:  

Jabber:

--

Brian Tierney, http://www.es.net/tierney
Energy Sciences Network (ESnet), Berkeley National Lab
http://fasterdata.es.net