perfSONAR User Q&A and Other Discussion

[Roberto Carna <>]

Dear Mark, what do you mean with "You'd need to take that up with them" ???

Do you want to say that I have to permit traffic from Internet to my
pscheduler TCP/443 port from my perfsonar server ??? Or what ???

Here are my tests:

1) RTT:

root@perfsonar:~#  pscheduler task rtt --dest nettest.lbl.gov
Submitting task...
Task URL:
https://localhost/pscheduler/tasks/59e4cbf0-d176-4100-9032-9d89f55e43dd
Running with tool 'ping'
Fetching first run...

Next scheduled run:
https://localhost/pscheduler/tasks/59e4cbf0-d176-4100-9032-9d89f55e43dd/runs/0033db54-d3ad-418f-8676-825ad948b82c
Starts 2018-09-06T12:42:38-03:00 (~7 seconds)
Ends   2018-09-06T12:42:49-03:00 (~10 seconds)
Waiting for result...

1       nettest.lbl.gov (131.243.24.11)  64 Bytes  TTL 44  RTT 224.0000 ms
2       nettest.lbl.gov (131.243.24.11)  64 Bytes  TTL 44  RTT 214.0000 ms
3       nettest.lbl.gov (131.243.24.11)  64 Bytes  TTL 44  RTT 212.0000 ms
4       nettest.lbl.gov (131.243.24.11)  64 Bytes  TTL 44  RTT 223.0000 ms
5       nettest.lbl.gov (131.243.24.11)  64 Bytes  TTL 44  RTT 217.0000 ms

0% Packet Loss  RTT Min/Mean/Max/StdDev =
212.013000/218.212000/224.259000/4.823000 ms

No further runs scheduled.

2) LATENCY:

root@perfsonar:~# pscheduler task latency --dest nettest.lbl.gov
Submitting task...
Task URL:
https://localhost/pscheduler/tasks/13f20266-27e3-4b92-8055-40c9df7bf9ff
Running with tool 'owping'
Fetching first run...

Next scheduled run:
https://localhost/pscheduler/tasks/13f20266-27e3-4b92-8055-40c9df7bf9ff/runs/ddfcb9a8-bfea-4311-80d3-d7a89b3d67b4
Starts 2018-09-06T12:43:28-03:00 (~5 seconds)
Ends   2018-09-06T12:43:49-03:00 (~20 seconds)
Waiting for result...


Packet Statistics
-----------------
Packets Sent ......... 100 packets
Packets Received ..... 0 packets
Packets Lost ......... 100 packets
Packets Duplicated ... 0 packets
Packets Reordered .... 0 packets

One-way Latency Statistics
--------------------------
Delay Median ......... Not Reported
Delay Minimum ........ Not Reported
Delay Maximum ........ Not Reported
Delay Mean ........... Not Reported
Delay Mode ...........
Delay 25th Percentile ... Not Reported
Delay 75th Percentile ... Not Reported
Delay 95th Percentile ... Not Reported
Max Clock Error ...... Not Reported ms
Common Jitter Measurements:
    Variance ......... Not Reported
    Std Deviation .... Not Reported
Histogram:

TTL Statistics
--------------
TTL Median ........... Not Reported
TTL Minimum .......... Not Reported
TTL Maximum .......... Not Reported
TTL Mean ............. Not Reported
TTL Mode .............
TTL 25th Percentile ... Not Reported
TTL 75th Percentile ... Not Reported
TTL 95th Percentile ... Not Reported
Histogram:

No further runs scheduled.

3) THROUGHPUT:

root@perfsonar:~# pscheduler task throughput --dest nettest.lbl.gov
Submitting task...
Task URL:
https://localhost/pscheduler/tasks/a69dee59-828b-4a6b-a1a6-e6c9f1dd098c
Running with tool 'iperf3'
Fetching first run...

Next scheduled run:
https://localhost/pscheduler/tasks/a69dee59-828b-4a6b-a1a6-e6c9f1dd098c/runs/186da212-9a93-4500-8e97-fd64cc3529d1
Starts 2018-09-06T12:47:56-03:00 (~5 seconds)
Ends   2018-09-06T12:48:15-03:00 (~18 seconds)
Waiting for result...

* Stream ID 5
Interval       Throughput     Retransmits    Current Window
0.0 - 1.0      3.40 Mbps      0              108.07 KBytes
1.0 - 2.0      16.83 Mbps     0              712.73 KBytes
2.0 - 3.0      37.94 Mbps     0              2.08 MBytes
3.0 - 4.0      178.28 Mbps    0              8.56 MBytes
4.0 - 5.0      534.79 Mbps    0              25.21 MBytes
5.0 - 6.0      387.05 Mbps    0              26.07 MBytes
6.0 - 7.0      346.85 Mbps    0              26.92 MBytes
7.0 - 8.0      366.99 Mbps    0              27.53 MBytes
8.0 - 9.0      387.98 Mbps    0              28.45 MBytes
9.0 - 10.0     293.54 Mbps    9              14.39 MBytes

Summary
Interval       Throughput     Retransmits
0.0 - 10.0     255.37 Mbps    9

Sorry for my new question, regards...
El jue., 6 sept. 2018 a las 12:34, Mark Feit 
(<>)
 escribió:
>
> Roberto Carna writes:
>
>     ameslab-owamp.es.net:
>
>       Checking path MTU... Unsafe or unknown: Error: Process took too long 
> to run.
>
> This looks like the trace is being stymied by a firewall.  The timeout for 
> this is artificially low.
>
>       Checking for pScheduler... OK.
>       Checking clock... OK.
>       Idle test... Failed.
>     Unable to post task: Task forbidden by limits:
>     Hints:
>       requester: 179.0.151.2
>       server: 198.124.238.138
>     Identified as everybody
>     Classified as default
>     Application: Reject otherwise uncategorized hosts
>       Group 1: Limit 'never' failed: Forced failure
>       Group 1: Want all, 0/1 passed, 1/1 failed: FAIL
>       Group 1: Failed; stopping here.
>       Application FAILS
>     Proposal does not meet limits
>
>     Can you explain me what can be wrong ?
>
> ESNet has configured pScheduler on that host to prevent your system from 
> running tests.  You'd need to take that up with them.
>
> --Mark
>
>