perfSONAR User Q&A and Other Discussion

[Mark Feit <>]

Tao Zhang writes:

 

The thoughput result also looks fine, however, I need to wait about 3 minutes for the result

 

bwctl -T iperf3 -s 198.165.161.174 -c 205.189.32.28 -t 30 -i 1 -f m -O 3

 

The use of bwctl as a command-line tool has been deprecated since we released 4.0 last April.  The system has provisions for backward compatibility to ease the transition to pScheduler, but those will be going away after we release 4.1.  Using the pScheduler CLI to test throughput between those hosts works just fine:

 

$ pscheduler task throughput --source 205.189.32.28 --dest 198.165.161.174

Submitting task...

Task URL:

https://205.189.32.28/pscheduler/tasks/4a94d7e0-2d38-4183-8008-4a2794896a93

Running with tool 'iperf3'

Fetching first run...

 

Next scheduled run:

https://205.189.32.28/pscheduler/tasks/4a94d7e0-2d38-4183-8008-4a2794896a93/runs/7f433f1f-3c63-442c-9f79-81f15f4ec633

Starts 2018-03-28T12:42:25Z (~6 seconds)

Ends   2018-03-28T12:42:44Z (~18 seconds)

Waiting for result...

 

* Stream ID 5

Interval       Throughput     Retransmits    Current Window

0.0 - 1.0      935.56 Mbps    0              8.56 MBytes   

1.0 - 2.0      943.74 Mbps    0              8.56 MBytes   

2.0 - 3.0      943.72 Mbps    0              8.56 MBytes   

3.0 - 4.0      943.60 Mbps    0              8.56 MBytes   

4.0 - 5.0      933.32 Mbps    0              8.56 MBytes   

5.0 - 6.0      943.74 Mbps    0              8.62 MBytes   

6.0 - 7.0      954.19 Mbps    0              9.06 MBytes   

7.0 - 8.0      943.72 Mbps    0              9.06 MBytes   

8.0 - 9.0      943.72 Mbps    0              9.06 MBytes   

9.0 - 10.0     933.21 Mbps    0              9.06 MBytes   

 

Summary

Interval       Throughput     Retransmits   

0.0 - 10.0     941.85 Mbps    0

 

No further runs scheduled.

 

ESNet has a good summary of how to use the pScheduler CLI and equivalent commands for old favorites:  https://fasterdata.es.net/performance-testing/network-troubleshooting-tools/pscheduler/

 

 

the owping test is more problematic.

1)      owping the box itself

 

owping 198.165.161.174

Approximately -232.8 seconds until results available

 

I just tried the same thing (which is fine because all perSONAR boxes run an OWAMP daemon) and owping seems to be getting caught up doing something DNS-related.  Trying to do any basic DNS lookups (dig, nslookup) on that host doesn’t go well, either, so the cause of that might be related to how that’s configured.  Owping to the other machine (205.189.32.28) works fine, so I suspect you have a network or DNS configuration problem.

 

--Mark