perfSONAR User Q&A and Other Discussion

["Uhl, George D. (GSFC-423.0)[Arctic Slope Technical Services, Inc.]" <>]

Forward to pS user list.

 

From: "George.D.Uhl" <>
Date: Friday, December 6, 2019 at 10:40 AM
To: "" <>
Subject: Dual stack throughput test failures

 

Hi,

 

I run a mesh with a dual stack local host that is failing to run ipv4 throughput tests to any non-agent dual stack remote host when the remote host shares a single hostname for IPv4 and IPv6.  I’ve attached some test cases showing conditions when tests work vs. when they fail.

 

Specifying ip-version as IPv4 in the pscheduler command line doesn’t seem to make a difference.  The local test node has an advanced configuration which includes multiple test interfaces, policy routing and a non-test interface that is used by the main routing table as the default path.  The issue appears that the non-agent remote host prefers using it’s IPv6 address when it translates the “--destination hostname” given to it by the local pscheduler during test setup/tool negotiation.  Thus the ip-version parameter is used to specify the protocol for testing only and isn’t used as part of the test setup.  Would it be possible to support a new feature that specidies the preferred protocol during test setup?

 

Thanks,

George

SCENARIO - two dual-stack perfsonar test nodes running ipv4 throughput tests. 
 The local test node has an advanced configuration which includes multiple 
test interfaces, policy routing and anon-test interface that is used to by 
the host's main routing table as the default path.


CASE 1 - specify an ipv4 test only using hostnames

# pscheduler task --lead-bind enpl-pt2-10g.eos.nasa.gov throughput --source 
enpl-pt2-10g.eos.nasa.gov --dest uhmanoa-tp.ps.uhnet.net --ip-version=4
Submitting task...
Failed to post task: Error getting tools from uhmanoa-tp.ps.uhnet.net: Could 
not resolve host: enpl-pt2-10g.eos.nasa.gov; Unknown error

The 'pscheduler troubleshoot' command may be of use in problem
diagnosis. 'pscheduler troubleshoot --help' for more information.


CASE 2 - specify an IPv4 test using hostnames except for the destination 
which is an IPv4 address literal

# pscheduler task --lead-bind enpl-pt2-10g.eos.nasa.gov throughput --source 
enpl-pt2-10g.eos.nasa.gov --dest 132.160.6.178 --ip-version=4
Submitting task...
Task URL:
https://enpl-pt2-10g.eos.nasa.gov/pscheduler/tasks/d9727824-d2ec-4543-afc0-a72a5eabcd22
Running with tool 'iperf3'
Fetching first run...

Next scheduled run:
https://enpl-pt2-10g.eos.nasa.gov/pscheduler/tasks/d9727824-d2ec-4543-afc0-a72a5eabcd22/runs/3917927e-7c5d-4e72-b27c-974ee90bf19d
Starts 2019-12-06T07:59:50-05 (~36 seconds)
Ends   2019-12-06T08:00:09-05 (~18 seconds)
Waiting for result...

* Stream ID 5
Interval       Throughput     Retransmits    Current Window 
0.0 - 1.0      187.57 Mbps    0              1.13 MBytes    
1.0 - 2.0      922.80 Mbps    0              65.71 MBytes   
2.0 - 3.0      1.53 Gbps      0              65.71 MBytes   
3.0 - 4.0      1.52 Gbps      0              65.71 MBytes   
4.0 - 5.0      1.54 Gbps      0              65.71 MBytes   
5.0 - 6.0      1.51 Gbps      0              65.71 MBytes   
6.0 - 7.0      1.54 Gbps      0              65.71 MBytes   
7.0 - 8.0      1.52 Gbps      0              65.71 MBytes   
8.0 - 9.0      1.53 Gbps      0              65.71 MBytes   
9.0 - 10.0     1.53 Gbps      0              65.71 MBytes   

Summary
Interval       Throughput     Retransmits    
0.0 - 10.0     1.33 Gbps      0

No further runs scheduled.


CASE 3 - specify an ipv4 test using an IPv4 address literal as the lead-bind 
and with hostnames for the remaining parameters

# pscheduler task --lead-bind 169.154.197.28 throughput --source 
enpl-pt2-10g.eos.nasa.gov --dest uhmanoa-tp.ps.uhnet.net --ip-version=4
Submitting task...
Failed to post task: Error getting tools from uhmanoa-tp.ps.uhnet.net: bind 
failed with errno 22: Invalid argument

The 'pscheduler troubleshoot' command may be of use in problem
diagnosis. 'pscheduler troubleshoot --help' for more information.