perfSONAR User Q&A and Other Discussion

[Brian Candler <>]

On 01/10/2015 15:53, Andrew Lake wrote:

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

Hmm that's strange, if you run the traceroute6 command in question by hand, anything of note about the output? The traceroute parsing hasn't changed in 3.5 as far as I can tell but it's a little tricky because we rely on the Net::Traceroute module to do the parsing. 

 

XXXX:XXXX:0:2::254 is the perfsonar node's own IP address, and XXXX:XXXX:1:64::252 is the remote address (actually a Mac Mini running OSX and bwctl from homebrew)

From the perfsonar node:

[admin@cov-perf-1 ~]$ traceroute6 XXXX:XXXX:1:64::252
traceroute to XXXX:XXXX:1:64::252 (XXXX:XXXX:1:64::252), 30 hops max, 80 byte packets
 1  XXXX:XXXX:0:2::1 (XXXX:XXXX:0:2::1)  0.786 ms  0.909 ms  1.034 ms
 2  cov-client-1.snipped (XXXX:XXXX:1:64::252)  0.621 ms  0.605 ms  0.601 ms

From the Mac mini:

$ traceroute6 XXXX:XXXX:0:2::254
traceroute6 to XXXX:XXXX:0:2::254 (XXXX:XXXX:0:2::254) from XXXX:XXXX:1:64::252, 64 hops max, 12 byte packets
 1  XXXX:XXXX:1:64::1  1.163 ms  0.898 ms  0.820 ms
 2  XXXX:XXXX:0:2::254  0.339 ms  0.296 ms  0.224 ms

Both those look fine to me. The regex in line 624 is:

        s/^ ?([0-9 ][0-9]) // || die "Can't find hop number in output: $_";

which matches, and on the perfsonar node it works if I do this:

perl -e 'use Net::Traceroute; $tr = Net::Traceroute->new(host=>"XXXX:XXXX:1:64::252", trace_program=>"traceroute6"); print $tr->hops;'
2

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

Do you have bwctl running on the hosts running the ping tests? Someone else reported a similar issue and they somehow had been getting results in 3.4 without bwctl enabled (which should not have been possible since we use bwping for all ping tests starting in 3.4).

bwctld is running on the target OSX host; periodic iperf tests to that host are working fine.

However if the 'ping' test now doesn't work without bwctl, that is a downer.  On another node we also use the ping test for monitoring non-perfsonar hosts; a sort of poor-mans' smokeping.

(Actually it would be a very good smokeping with a better GUI, since the esmond database stores the individual RTTs of each ping packet)

But in any case:

(1) this was all working fine with 3.4.2
(2) bwping at the command line works fine

[admin@cov-perf-1 ~]$ bwping -c cov-client-1.snipped
bwping: Using tool: ping
bwping: 20 seconds until test results available

SENDER START
PING XXXX:XXXX:1:64::252(XXXX:XXXX:1:64::252) from XXXX:XXXX:0:2::254 : 56 data bytes
64 bytes from XXXX:XXXX:1:64::252: icmp_seq=1 ttl=63 time=0.329 ms
64 bytes from XXXX:XXXX:1:64::252: icmp_seq=2 ttl=63 time=0.361 ms
64 bytes from XXXX:XXXX:1:64::252: icmp_seq=3 ttl=63 time=0.298 ms
64 bytes from XXXX:XXXX:1:64::252: icmp_seq=4 ttl=63 time=0.356 ms
64 bytes from XXXX:XXXX:1:64::252: icmp_seq=5 ttl=63 time=0.411 ms
64 bytes from XXXX:XXXX:1:64::252: icmp_seq=6 ttl=63 time=0.339 ms
64 bytes from XXXX:XXXX:1:64::252: icmp_seq=7 ttl=63 time=0.397 ms
64 bytes from XXXX:XXXX:1:64::252: icmp_seq=8 ttl=63 time=0.333 ms
64 bytes from XXXX:XXXX:1:64::252: icmp_seq=9 ttl=63 time=0.388 ms
64 bytes from XXXX:XXXX:1:64::252: icmp_seq=10 ttl=63 time=0.307 ms

--- XXXX:XXXX:1:64::252 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9000ms
rtt min/avg/max/mdev = 0.298/0.351/0.411/0.043 ms

SENDER END
[admin@cov-perf-1 ~]$ bwping -s cov-client-1.snipped
bwping: Using tool: ping
bwping: 20 seconds until test results available

SENDER START
PING6(56=40+8+8 bytes) XXXX:XXXX:1:64::252 --> XXXX:XXXX:0:2::254
16 bytes from XXXX:XXXX:0:2::254, icmp_seq=0 hlim=63 time=0.351 ms
16 bytes from XXXX:XXXX:0:2::254, icmp_seq=1 hlim=63 time=0.246 ms
16 bytes from XXXX:XXXX:0:2::254, icmp_seq=2 hlim=63 time=0.395 ms
16 bytes from XXXX:XXXX:0:2::254, icmp_seq=3 hlim=63 time=0.266 ms
16 bytes from XXXX:XXXX:0:2::254, icmp_seq=4 hlim=63 time=0.236 ms
16 bytes from XXXX:XXXX:0:2::254, icmp_seq=5 hlim=63 time=0.302 ms
16 bytes from XXXX:XXXX:0:2::254, icmp_seq=6 hlim=63 time=0.329 ms
16 bytes from XXXX:XXXX:0:2::254, icmp_seq=7 hlim=63 time=0.266 ms
16 bytes from XXXX:XXXX:0:2::254, icmp_seq=8 hlim=63 time=0.376 ms
16 bytes from XXXX:XXXX:0:2::254, icmp_seq=9 hlim=63 time=0.227 ms

--- XXXX:XXXX:0:2::254 ping6 statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 0.227/0.299/0.395/0.057 ms

SENDER END
[admin@cov-perf-1 ~]$

Regards,

Brian.