Skip to Content.
Sympa Menu

perfsonar-user - [perfsonar-user] pscheduler throughput task failing on multihomed test host.

Subject: perfSONAR User Q&A and Other Discussion

List archive

[perfsonar-user] pscheduler throughput task failing on multihomed test host.


Chronological Thread 
  • From: "Uhl, George D. (GSFC-423.0)[SGT INC]" <>
  • To: "" <>
  • Subject: [perfsonar-user] pscheduler throughput task failing on multihomed test host.
  • Date: Wed, 28 Aug 2019 15:24:22 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nasa.gov; dmarc=pass action=none header.from=nasa.gov; dkim=pass header.d=nasa.gov; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=4/lWe5eZ+dPek3UF5LZesAUrPDSTHvWPyH6TtsHIPOw=; b=a7f1DAFga2wAm0yWZYmhmkDDo2oQCx6PF8OjNcOOOfGp/RrtrD5+NmDvs17LCuHMsmGFRPDAmefU7Zwldle/RGIck3+z3lXmbP/PIjzFdtiRIy4SndUTJTiiiAd3xhhtLe4o3f/UFKj/jwGK6UaccSQs6ls/DXgNwTF/chtjRB4Jr91kcKSC1xK7i7+I2H5dGfEc//OCyNWKWZGaPba9asUWTIG0qWni7PYZf/2ArTvgBvUOz2aJZk3aWuCd9U2RuIMH+xdwtaxJ/FHtTjlMWVm9+QhIfIae6zBD0m2PF4SQ5+Frjv3nPCqog4tR3vINimuxybuZ2LdGB032BAgJww==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=KD36FOEHSFHn7IBld4EYhsYdW4z6T2SEKV+jqcSAKumv2HaWujbcFCFWAGrJrzYs/uW7uLvzveOwo3tOt4uFm867hZZ4hTZkNegfbWUYBWJAKDsLtX8OBINtgP34zd4oTbWHupKIP7GCElKEWM6+h8q//XlH0TG2C7/jibnKTXY9jg91XRJ8kZCIbCpy8g3cr8zNxcz8Jqt5eJaXlgVIPlsJdznU83C/Si2hB2YRx/PIcUEYp2fznTfVe2duhPsPvN6h5fZPweUk9uxa33teNepEEf0lRVqb70Vq7aBhtVARyZtBD7NO51GfC5MVAt7XhRInLWy0BlruJDDdGH7jrg==
  • Dkim-filter: OpenDKIM Filter v2.11.0 ndjsvnpf103.ndc.nasa.gov 4545240FF60F

Hi,

 

I’m having problems sourcing throughput tests on a test host with two interfaces.  I’ve configured the host to operate using multiple interfaces including running the mod_interface_route script for both interfaces.  Sourcing traffic over the correct interface works EXCEPT when I run pscheduler throughput task.  In this case the following error:

 

# pscheduler task throughput --source xxx.xxx.8.206 --dest xxx.xxx.197.28 -B xxx.xxx.8.206

Submitting task...

Failed to post task: Error getting tools from xxx.xxx.197.28: Failed connect to xxx.xxx.197.28:443; Connection refused

 

The 'pscheduler troubleshoot' command may be of use in problem

diagnosis. 'pscheduler troubleshoot --help' for more information.

 

When I run a trace task from the same source/dest pair it is successful.  Traceroutes reveal that the wrong interface is used for throughput tasks despite binding the test to the desired interface’s IP address.  Trace tasks use the proper interface indicating that the proper ip rule is getting invoked and using the local interface route.  When I run other applications and bind them to one of the source IP, they are successful and they use the correct interface.  The pscheduler throughput task is successful only after I put a route for the destination in the Linux default routing table.

 

# route add -host xxx.xxx.197.28 gw xxx.xxx.8.193

[root@epsosgs-pt1g-01 ~]# pscheduler task throughput --source xxx.xxx.8.206 --dest xxx.xxx.197.28

Submitting task...

Task URL:

https:// xxx.xxx.8.206/pscheduler/tasks/8255b181-c58c-42bf-9ba8-439ace11157d

Running with tool 'iperf3'

Fetching first run...

 

Next scheduled run:

https:// xxx.xxx.8.206/pscheduler/tasks/8255b181-c58c-42bf-9ba8-439ace11157d/runs/6ef62abd-8364-4af0-b6e3-1269164d62c5

Starts 2019-08-28T14:58:25Z (~19 seconds)

Ends   2019-08-28T14:58:44Z (~18 seconds)

Waiting for result...

 

* Stream ID 5

Interval       Throughput     Retransmits    Current Window 

0.0 - 1.0      18.32 Mbps     0              430.06 KBytes  

1.0 - 2.0      197.08 Mbps    183            1.89 MBytes    

2.0 - 3.0      94.36 Mbps     7              946.99 KBytes  

3.0 - 4.0      52.44 Mbps     0              957.13 KBytes  

4.0 - 5.0      52.43 Mbps     0              1.05 MBytes    

5.0 - 6.0      52.42 Mbps     0              1.26 MBytes    

6.0 - 7.0      83.89 Mbps     0              1.62 MBytes    

7.0 - 8.0      94.37 Mbps     0              2.10 MBytes    

8.0 - 9.0      125.83 Mbps    0              2.72 MBytes    

9.0 - 10.0     157.28 Mbps    0              3.53 MBytes    

 

Summary

Interval       Throughput     Retransmits    

0.0 - 10.0     92.84 Mbps     190

 

No further runs scheduled.

 

IP address binding for throughput tasks was working in the 4.1.2 perfsonar release.

 

Thanks,

George




Archive powered by MHonArc 2.6.19.

Top of Page