perfSONAR User Q&A and Other Discussion

["Curtis, Bruce" <>]

> On May 30, 2017, at 11:22 AM, Curtis, Bruce 
> <>
>  wrote:
> 
> 
>> On May 30, 2017, at 11:15 AM, Curtis, Bruce 
>> <>
>>  wrote:
>> 
>> 
>>> On May 30, 2017, at 8:45 AM, Charley Kneifel 
>>> <>
>>>  wrote:
>>> 
>>> Hello Andy,
>>> 
>>> I have setup hosts with both AAAA and A records as well as hosts with 
>>> only AAAA records or A records and hosts that just have v6 addresses in 
>>> the local network.
>>> 
>>> I am unable to get any of the tests to run when I select only the IPv6 
>>> checkbox and when I select both checkboxes then only the IPv4 tests run.  
>>> I think I did both bandwidth and ping based tests but will confirm.
>> 
>> I still see this also.  The problem we experienced that graphs were not 
>> created for IPv4 connections when a host had a AAAA record seems to be 
>> resolved but we also still get no graph when clicking on the IPv6 check 
>> box.
>> 
>> However IPv6 does work in at least one case.
>> 
>> 
>> http://ps-border1-pt.lbl.gov/perfsonar-graphs/?source=2620:83:8000:ff22::a&dest=2620:0:2b30:b::2&url=http%3A%2F%2Fps-border1-pt.lbl.gov%2Fesmond%2Fperfsonar%2Farchive%2F#start=1495555855&end=1496160655&summaryWindow=3600&timeframe=1w
>> 
>> http://ps-border1-pt.lbl.gov/perfsonar-graphs/?source=2620:83:8000:ff22::a&dest=2620:0:210:1::23&url=http%3A%2F%2Fps-border1-pt.lbl.gov%2Fesmond%2Fperfsonar%2Farchive%2F#start=1495556041&end=1496160841&summaryWindow=3600&timeframe=1w
>> 
>> I see that in the LBL cases the remote host is specified by IPv6 number 
>> rather than hostname.  I have not tested configuring a test with IPv6 
>> number rather than hostname since the problem with AAAA records affecting 
>> IPv4 tests has been resolved.
> 
> 
> 
> Hmm.
> 
> Here is a case where host names are used and IPv6 graphs are generated.  
> Not sure what the differences are between these hosts and mine.  They all 
> seem to be running CentOS 6.9 and the same version of personar and the 
> personar toolkit.
> 
> 
> http://perfsonar.ornl.gov/perfsonar-graphs/?source=2620:0:2b30:b::2&dest=2620:0:210:1::23&url=http%3A%2F%2Fperfsonar.ornl.gov%2Fesmond%2Fperfsonar%2Farchive%2F#start=1495556302&end=1496161102&summaryWindow=3600&timeframe=1w
> 
> 

Also strange.

I didn’t seem to be able to manually schedule a test from the command line.  
I used a command I saved in my notes but now I just get "never scheduled a 
run for the task.”

And the tasks did not show up in /var/log/pscheduler/pscheduler.log.

I also noticed that one of my personar hosts stopped doing throughput 
transfers in one direction about May 21.


[curtis@perfsonar ~]$ pscheduler task throughput --ip-version 6 --source 
perfsonar.ndsu.nodak.edu --dest perfsonar2.ndsu.nodak.edu --duration PT30S
Submitting task...
Task URL:
https://perfsonar.ndsu.nodak.edu/pscheduler/tasks/aa115f36-f70f-4024-9776-1a8dc3f7ab71
Running with tool 'iperf3'
Fetching first run...
perfsonar.ndsu.nodak.edu never scheduled a run for the task.
[curtis@perfsonar ~]$ 
[curtis@perfsonar ~]$ pscheduler task throughput --ip-version 4 --source 
perfsonar.ndsu.nodak.edu --dest perfsonar2.ndsu.nodak.edu --duration PT30S
Submitting task...
Task URL:
https://perfsonar.ndsu.nodak.edu/pscheduler/tasks/90124831-22e2-404c-9381-484adeebf992
Running with tool 'iperf3'
Fetching first run...
perfsonar.ndsu.nodak.edu never scheduled a run for the task.
[curtis@perfsonar ~]$ 
[curtis@perfsonar ~]$ 
[curtis@perfsonar ~]$ pscheduler task throughput  --source 
perfsonar.ndsu.nodak.edu --dest ps-border1-pt.lbl.gov --duration PT20S
Submitting task...
Task URL:
https://perfsonar.ndsu.nodak.edu/pscheduler/tasks/3dd3d605-5e18-46b1-81a0-72ec492980c0
Running with tool 'iperf3'
Fetching first run...
perfsonar.ndsu.nodak.edu never scheduled a run for the task.
[curtis@perfsonar ~]$ 


Then after a reboot I could schedule a test manually.

[curtis@perfsonar ~]$ pscheduler task throughput --ip-version 6 --source 
perfsonar.ndsu.nodak.edu --dest perfsonar2.ndsu.nodak.edu --duration PT10S
Submitting task...
Task URL:
https://perfsonar.ndsu.nodak.edu/pscheduler/tasks/c3390a56-8d44-47f9-a5ee-423e7b585fe9
Running with tool 'iperf3'
Fetching first run...

Next scheduled run:
https://perfsonar.ndsu.nodak.edu/pscheduler/tasks/c3390a56-8d44-47f9-a5ee-423e7b585fe9/runs/4923b786-9551-470f-b9c1-675ffc886186
Starts 2017-05-30T11:56:07-05:00 (~9 seconds)
Ends   2017-05-30T11:56:26-05:00 (~18 seconds)
Waiting for result...

* Stream ID 4
Interval       Throughput     Retransmits    Current Window 
0.0 - 1.0      937.43 Mbps    0              551.21 KBytes  
1.0 - 2.0      929.97 Mbps    0              554.06 KBytes  
2.0 - 3.0      929.46 Mbps    0              554.06 KBytes  
3.0 - 4.0      925.34 Mbps    0              554.06 KBytes  
4.0 - 5.0      929.97 Mbps    0              554.06 KBytes  
5.0 - 6.0      929.98 Mbps    0              554.06 KBytes  
6.0 - 7.0      925.34 Mbps    0              555.49 KBytes  
7.0 - 8.0      929.98 Mbps    0              555.49 KBytes  
8.0 - 9.0      929.97 Mbps    0              555.49 KBytes  
9.0 - 10.0     925.34 Mbps    0              556.92 KBytes  

Summary
Interval       Throughput     Retransmits    
0.0 - 10.0     929.28 Mbps    0

No further runs scheduled.


[curtis@perfsonar ~]$ pscheduler task throughput --ip-version 4 --source 
perfsonar.ndsu.nodak.edu --dest perfsonar2.ndsu.nodak.edu --duration PT10S
Submitting task...
Task URL:
https://perfsonar.ndsu.nodak.edu/pscheduler/tasks/347cd452-e70a-41d9-8d42-060ea97981b5
Running with tool 'iperf3'
Fetching first run...

Next scheduled run:
https://perfsonar.ndsu.nodak.edu/pscheduler/tasks/347cd452-e70a-41d9-8d42-060ea97981b5/runs/e7b31133-7f45-49f8-89b1-f38876144b9c
Starts 2017-05-30T11:53:00-05:00 (~46 seconds)
Ends   2017-05-30T11:53:19-05:00 (~18 seconds)
Waiting for result...

* Stream ID 4
Interval       Throughput     Retransmits    Current Window 
0.0 - 1.0      952.46 Mbps    0              558.93 KBytes  
1.0 - 2.0      942.47 Mbps    0              563.27 KBytes  
2.0 - 3.0      938.31 Mbps    0              563.27 KBytes  
3.0 - 4.0      942.99 Mbps    0              563.27 KBytes  
4.0 - 5.0      943.00 Mbps    0              563.27 KBytes  
5.0 - 6.0      938.30 Mbps    0              563.27 KBytes  
6.0 - 7.0      943.00 Mbps    0              563.27 KBytes  
7.0 - 8.0      942.99 Mbps    0              563.27 KBytes  
8.0 - 9.0      938.31 Mbps    0              563.27 KBytes  
9.0 - 10.0     942.99 Mbps    0              563.27 KBytes  

Summary
Interval       Throughput     Retransmits    
0.0 - 10.0     942.48 Mbps    0

No further runs scheduled.
[curtis@perfsonar ~]$ 


> 
>> 
>>> 
>>> I am running a fully patched/updated version of the 4.0 release with 
>>> auto-applied updates.
>>> 
>>> Charley
>>> 
>>> From: Andrew Lake 
>>> [mailto:]
>>>  
>>> Sent: Tuesday, May 30, 2017 9:40 AM
>>> To: 
>>> ;
>>>  Bill Owens 
>>> <>;
>>>  Charley Kneifel 
>>> <>
>>> Subject: Re: [perfsonar-user] Re: Lookup Service CentOS 7
>>> 
>>> Hi,
>>> 
>>> What type of tests are you trying to run? There is a known issue with rtt 
>>> tests and two hostnames that only have AAAA records detailed here: 
>>> https://github.com/perfsonar/pscheduler/issues/431
>>> 
>>> We also just pushed out 1.0.0.3 of pscheduler a couple weeks ago with 
>>> some IPv6-related fixes for throughput tests so may be good to make sure 
>>> you are running those. 
>>> 
>>> Thanks,
>>> Andy
>>> 
>>> 
>>> 
>>> On May 30, 2017 at 8:12:12 AM, Bill Owens 
>>> ()
>>>  wrote:
>>> 
>>> I believe this is a known bug that was closed last fall without being 
>>> resolved:https://github.com/perfsonar/pscheduler/issues/233
>>> 
>>> I’ve tried to get some attention to it but haven’t had time to dig into 
>>> it.
>>> 
>>> Bill.
>>> 
>>> From: 
>>> <>
>>>  on behalf of Charley Kneifel 
>>> <>
>>> Date: Saturday, May 27, 2017 at 8:31 PM
>>> To: 
>>> ""
>>>  
>>> <>
>>> Subject: [perfsonar-user] Re: Lookup Service CentOS 7
>>> 
>>> Is there anything special I need to do to get IPv6 working?
>>> 
>>> 
>>> 
>>> I have a privately IP'ed host that I can ping6 to IPv6 addresses such as:
>>> 
>>> 
>>> 
>>> perf-lax.sinet.ad.jp
>>> 
>>> 
>>> 
>>> or
>>> 
>>> 
>>> 
>>> nersc-pt1-v6.es.net
>>> 
>>> 
>>> 
>>> but I don't get any test results when I add them.
>>> 
>>> 
>>> 
>>> If I add perf-lax.sinet.ad.jp and check the IPv4 and IPv6 check boxes, 
>>> then I get:
>>> 
>>> 
>>> 
>>> May 27 19:04:21 ps-node-a runner INFO     673928: With ping: rtt --count 
>>> 10 --dest perf-lax.sinet.ad.jp --interval PT1S --ip-version 4 --source 
>>> 192.168.202.151 --length 1000 --ttl 255
>>> 
>>> 
>>> 
>>> in my /var/log/messages file but nothing with an --ip-version 6 and 
>>> nothing when it's just IPv6 checked.  I have several other hosts that I 
>>> am trying to check via direct IPv6 addresses including two on the local 
>>> network.
>>> 
>>> 
>>> 
>>> The PS node hosts show the v6 addresses in ifconfig and in the PS 
>>> dashboard
>>> 
>>> 
>>> 
>>> What am I missing?
>>> 
>>> 
>>> 
>>> Charley
>>> 
>> 
>> ---
>> Bruce Curtis                         
>> 
>> Certified NetAnalyst II                701-231-8527
>> North Dakota State University        
>> 
> 
> ---
> Bruce Curtis                         
> 
> Certified NetAnalyst II                701-231-8527
> North Dakota State University        
> 

---
Bruce Curtis                         

Certified NetAnalyst II                701-231-8527
North Dakota State University