perfSONAR User Q&A and Other Discussion

[Brian Candler <>]

Update on previous report.

> Problem 1: clicking on either of the two "Details" links shows the 
> same graph. The graph headers say
>
>          Source                       Destination
> cov-client-1.snipped              cov-perf-1.snipped
> X.X.X.X, XXXX:XXXX:XXXX:XXXX Y.Y.Y.Y,YYYY:YYYY:YYYY:YYYY
>
> Previously, I could get different graphs for the v4 and v6. Now I can 
> only get one, and it's not even clear which it's showing.
>
> Clicking "link to this chart" gives a URL which contains
> graphWidget.cgi?source=cov-client-1.snipped&dest=cov-perf-1.snipped
>
> whereas before it would have given either the IPv4 or IPv6 addresses.
This has been fixed: I now get graphs separately for IPv4 and IPv6, and 
the link URLs include the actual v4 or v6 IP addresses rather than the 
hostname. Thank you!


> (2) From the time of the upgrade, I get red dots showing:
>
> "04:57:41 10/01/2015
> Error from bwctl/traceroute:
> Problem parsing traceroute output: Can't find hop number in output: 
> traceroute6 to XXXX:XXXX:0:2::254 (XXXX:XXXX:0:2::254) from 
> XXXX:XXXX:1:64::252, 64 hops max, 12 byte packets at 
> /usr/share/perl5/vendor_perl/Net/Traceroute.pm line 624.
> 04:57:41 10/01/2015"
>
> This might also explain why there is no "traceroute" link in the "test 
> results" section for the IPv6 addresses.
This problem still exists. There is a big solid red line for all the 
errors, and hovering over one of the red dots shows:

15:52:00 11/03/2015
Error from bwctl/traceroute:
Problem parsing traceroute output: Can't find hop number in output: 
traceroute6 to xxxx:xxxx:0:2::254 (xxxx:xxxx:0:2::254) from 
xxxx:xxxx:1:64::252, 64 hops max, 12 byte packets at 
/usr/share/perl5/vendor_perl/Net/Traceroute.pm line 624.
15:52:00 11/03/2015

And there is still no "Traceroute" link by the IPv6 source/destination 
pair, only "Details"

> (3) From the time of the upgrade, ping tests have stopped working (the 
> dotted yellow line for "reverse ping" has just stopped)
>
> But Configuration > Tests still shows the section (which I called 
> "Local ping test"), and I can see the test is still there.
This problem still exists. No new ping tests are shown, on either v4 or 
v6. But if I look back in history I can see ping tests were working up 
until 30th September, when the node updated to perfsonar 3.5. So this is 
a problem of data collection, not graph rendering.

ping tests would still be useful for basic connectivity checks to 
devices where owampd is not available.

Regards,

Brian Candler.