perfSONAR User Q&A and Other Discussion

[Charley Kneifel <>]

Hi Ivan,

 

It’s a 4.0 that was upgraded from 3.5 – it’s not a 3.5 system anymore.

 

Charley

 

From: Garnizov, Ivan (RRZE) [mailto:]
Sent: Friday, June 30, 2017 9:57 AM
To: Charley Kneifel <>;
Subject: RE: perfSONAR v4 and IPv6

 

Hi Charlie,

 

I am surprised you have found a problem with pS 3.5 on IPv6. It had been heavily used and tested in the past.

Do these servers participate in other tests, or are you testing only in between?

If you are testing (seeing problems) only in tests between these 2 servers, then it would make sense to diagnose a problem with backward compatibility.

                Please tell if you are able to run tests on the direction from pS 3.5 to pS 4.0.

If you are reporting here about problems with these 2 servers separately, I suggest you open 2 tracks, it might get very messy otherwise.

 

Please check the conf, where the tests get described and scheduled from.

For pS 3.5 /etc/perfsonar/regulartesting.conf

For pS 4.0 /etc/perfsonar/meshconfig-agent-tasks.conf

 

Both should have blocks that define your IPv6 tests, if these are missing, then nothing will be scheduled / executed as tests.

 

For the pS 4.0 here is the doc for running tests: http://docs.perfsonar.net/pscheduler_client_tasks.html

Example (please mind source and destination): pscheduler task --debug throughput --duration PT10S --source sdsc-pt1-v6.es.net --ip-version6 --dest ps-node-c --parallel 1

 

 

Regards,

Ivan Garnizov

 

GEANT SA1T2: pS deployments GN Operations

GEANT SA2T3: pS development team

GEANT SA3T5: eduPERT team

 

 

 

 

From: Charley Kneifel []
Sent: Freitag, 30. Juni 2017 14:40
To: Garnizov, Ivan (RRZE);
Subject: RE: perfSONAR v4 and IPv6

 

Hello Ivan

 

See below -

 

From: Garnizov, Ivan (RRZE) []
Sent: Friday, June 30, 2017 4:07 AM
To: Charley Kneifel <>;
Subject: RE: perfSONAR v4 and IPv6

 

Hi Charley,

 

Could you please clarify:

-          Which bundle do you use?

 

I have two builds – one based on the 4.X ISO (Centos 7) and another based on an upgrade 3.5 build (Centos 6.9) both have the same problem.

 

-          Do you have IPv4 tests working?

 

Yes –

 

-          How did you configure IPv6 tests (where)?

 

GUI – add a host with an IPv6 name and check the [] IPv6 checkbox and un-check the v4 checkbox.

  I have also directly used the IPv6 address.

 

-          Did you run command line tests for verification? Do you have results  you can share?

 

Can you send me an example – I have only run a command link ping test.

 

-          Any log events, that you find related and suspicious ?

 

Nothing that I noticed – but if there are particular places to look, please let me know.

 

 

Regards,

Ivan Garnizov

 

GEANT SA1T2: pS deployments GN Operations

GEANT SA2T3: pS development team

GEANT SA3T5: eduPERT team

 

 

From: [] On Behalf Of Charley Kneifel
Sent: Freitag, 30. Juni 2017 03:13
To:
Subject: [perfsonar-user] perfSONAR v4 and IPv6

 

Hello All,

 

I am unable to get IPv6 tests to work.

 

I can ping a remote IPv6 node:

 

ping6 sdsc-pt1-v6.es.net
PING sdsc-pt1-v6.es.net(sdsc-pt1-v6.es.net) 56 data bytes
64 bytes from sdsc-pt1-v6.es.net: icmp_seq=1 ttl=48 time=107 ms
64 bytes from sdsc-pt1-v6.es.net: icmp_seq=2 ttl=48 time=106 ms
64 bytes from sdsc-pt1-v6.es.net: icmp_seq=3 ttl=48 time=105 ms
64 bytes from sdsc-pt1-v6.es.net: icmp_seq=4 ttl=48 time=104 ms
^C
--- sdsc-pt1-v6.es.net ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3726ms
rtt min/avg/max/mdev = 104.495/105.886/107.681/1.283 ms

name services are resolving properly

[root@ps-node-c pscheduler]# nslookup -type=aaaa sdsc-pt1-v6.es.net
Server:         192.168.202.5
Address:        192.168.202.5#53

Non-authoritative answer:
sdsc-pt1-v6.es.net      has AAAA address 2001:400:1101:1150::3

 

I have added an IPv6 host to a PS4 node and confirmed that it is set for IPv6

 

I see no tests with the hostname (sdsc-pt1-v6) in the pscheduler logs and no tests with --ip-version=6 in the logs either.

 

I do have a private v4 address, but have a public V6 address that is exposed for icmpv6.

 

Anyone have any suggestions?

 

Charley