perfsonar-user - [perfsonar-user] Psconfig to run iperf2 tests
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: Sal Ghani <>
- To: "" <>
- Subject: [perfsonar-user] Psconfig to run iperf2 tests
- Date: Tue, 6 Jul 2021 13:26:17 +0000
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=tx-learn.net; dmarc=pass action=none header.from=tx-learn.net; dkim=pass header.d=tx-learn.net; 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=BB1/jHz2lTMR611M2To13bYJDbBPuht25/5JQ6BI8b8=; b=FJEKjgET/x1fLqZ6ZarYntFpsMe9QpQOvst9+rRmDnJ5fL644laTuFEFpOygfxiwUni9IFQRqwGh5W70zw+tXDQUTVSigopvGfgOTPxnmX0a/ANZzBbs42FRReEJGC0fr/HIU/ICrr3R0pHQCcocJQJZXIQJcPQ+gjhMJliGM2I/lEBz4PE6YBFL7Ohn0ZiZebzp9Pq9tI51EXXbbCg0BduI2oIxvhDoGaklIRm4Zwyqh+COUTraQiJGsdbUdaqkP/xXB9RvcEn8mwrKwhcgQGEfRHTejhVg/ueU0LpZs+pnFgSfImAsewMca1upQFaDPfN4zVZn8s5f0F/yzWGleQ==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=GXOCbblZaKUMgvxUPb3W4NGXL93FXk6hEibqWFHxBbAE4X1XIhRh8XJK7szhGjYcna3wBgJEp/GxxTAiKAmWpBM9YbLDhnIaNlExiI0lIIj7veNEd5YFsEs7f1Z9Aws2TCvuBvKcew8s7Hk+FSSynM1W9VE78H85g3cV53X5LQJV8YsC044Fu91z19tqT5cXOCPA9G1NSRCQp7cicAiCIkuF4yNuUZ6BcgJv47YzloKHqnkExHvv9yuf/Hpmv42H9DvX+Aqnul9oMxIXlX5YHpguSojh3bjGcFFCWq5x9ELtgw00fylD1pXyG9xl3s6x+keyBvIEyQVL49Pl7CK8tg==
Hello all, I’m running a mesh with a number of perfSONAR nodes on which I’d like to run throughput tests using iperf2. My truncated config file looks like this:
Test: "throughput_test": { "type":"throughput", "spec": { "source":"{% address[0] %}", "dest":"{% address[1] %}", "duration":"PT30S", "omit":"PT5S" } }
And corresponding Task: "Throughput Task": { "_meta":{"display-name":" Throughput"}, "group":"GroupName", "test":"throughput_test", "tools": ["iperf2"], "schedule":"PT4H", "archives": ["esmond_archive"] }
There are also latencybg and trace tests and task configured for the same set of hosts within this config. The latencybg and trace tests are running fine but the throughput tests are not reporting back to the measurement archive. Note that without the “tools”:[“iperf2”] entry, default iperf3 throughput results were being posted without issue.
I’ve checked some of the nodes and I am noticing entries similar to this in their psconfig-pscheduler-agent.log files: WARN pid=20171 prog=perfSONAR_PS::PSConfig::PScheduler::Agent::_run_end line=231 guid=6FFF77C4-DDB6-11EB-A3F0-965CEB9615E8 msg=Problem adding test throughput(<IP Address of node 1>-><IP Address of node 2>), continuing with rest of config: UNPROCESSABLE ENTITY: Unable to complete request: No tool in common among the participants: <IP address of node 1> offered iperf3, ethr; < IP address of node 2> offered iperf3, ethr.
Manually running pscheduler task --tool iperf2 throughput -d <IP address> against the same nodes produces test results as expected. Not quite sure what I’m doing wrong in the psconfig or why the nodes report that there is no tool in common when the manual tests run without issue using the same tool.
As always, help provided is highly appreciated! Thanks!
|
- [perfsonar-user] Psconfig to run iperf2 tests, Sal Ghani, 07/06/2021
- Re: [perfsonar-user] Psconfig to run iperf2 tests, Mark Feit, 07/06/2021
- Re: [perfsonar-user] Psconfig to run iperf2 tests, Sal Ghani, 07/06/2021
- Re: [perfsonar-user] Psconfig to run iperf2 tests, Mark Feit, 07/06/2021
Archive powered by MHonArc 2.6.24.