perfSONAR User Q&A and Other Discussion

["Curtis, Bruce" <>]

> 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.

>  
> 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