perfSONAR User Q&A and Other Discussion

[Dan Doyle <>]

Hi Tomy,

iperf and iperf3 are started and stopped on demand via pScheduler, not run as persistent daemons. As a result, you likely won't see them in the output of something like netstat unless you happen to run it during a test run.

If your interest is in using the UI to do everything and you installed the perfsonar toolkit package, the firewall should already be configured correctly. You can test this either by setting up a test in the UI and then waiting for it to run and examining the results, or by running a test off the command line with pscheduler directly.

Dan Doyle

Network Data Collection and Analysis

1-812-856-3892

On Sep 10, 2018, at 12:31 PM, Tom Yard <> wrote:

Dear people, I have installed perfSONAR 4.1 toolkit in a Debian 9 box, via repositories. 

I'm testing some initial configurations.

I have configured /etc/pscheduler/tool/iperf/iperf2.conf and /etc/pscheduler/tool/iperf3.iperf3.conf in order to put them UP, but I'm seeing that ports TCP/5001 (iperf) and TCP/5201 (iperf3) aren't listening. 

How can I put UP both iperf and iperf3 ports through pScheduler?

My objective is to use the web interface to define and view all the latency, loss and throughput tasks.

Thanks a lot.

Tomy

--
To unsubscribe from this list: https://lists.internet2.edu/sympa/signoff/perfsonar-user

Attachment: smime.p7s
Description: S/MIME cryptographic signature