perfSONAR User Q&A and Other Discussion

[Vytenis Gadliauskas <>]

Hello,

I am Vytenis Gadliauskas from Lithuanian Academy of Music and Theatre and I am participating in GEANT GN4-3 WP6 T1 project which is developing network monitoring for low latency audiovisual streaming applications. As one of the options, we use perfSONAR for it's versatility and availability. We started with perfSONAR version 4.1.6-1.el7 and made a lot of tests with it. These tests include generating 400-450 Mbps bandwith with packet size of ~1000 bytes, around 50000pps. In order have this test running without issues, we had to change bandwidth.limits file from 20MB to 0. Everything was working fine. However, when we started using perfSONAR 4.2.2-1.el7 and now 4.2.3-1.el7 on newer machines (fresh install), there are some issues with pscheduler task latency tests (bandwidth.limits file is 0 by default).

For example, using command "pscheduler task latency -p 1008 -i 0.00002 -c 5000000 --source machine1 --dest machine2" between perfSONAR 4.1.6-1.el7 machines, produces output, attached in file output1.txt. If the same command is used between perfSONAR 4.2.2-1.el7 or 4.2.3-1.el7, result comes with an error, attached in file output2.txt

Could you please tell what should be changed/edited in perfSONAR 4.1.6-1.el7 for these commands to work again?

Thank you.

--

Best regards,

Vytenis Gadliauskas

Garso režisierius

Muzikos inovacijų ir studijų centras

Lietuvos muzikos ir teatro akademija

+37068207816

[machine1@localhost ~]$ pscheduler task latency -p 1008 -i 0.00002 -c 500000 
-source machine1 --dest machine2
Submitting task...
Task URL:
https://machine1/pscheduler/tasks/775ffc77-2449-40dd-9f61-9938af0c1150
Running with tool 'owping'
Fetching first run...

Next scheduled run:
https://machine1/pscheduler/tasks/775ffc77-2449-40dd-9f61-9938af0c1150/runs/9f0e055b-5910-40fd-a236-eb38b0bfd8db
Starts 2020-03-03T13:34:20Z (~8 seconds)
Ends   2020-03-03T13:34:41Z (~20 seconds)
Waiting for result...

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

One-way Latency Statistics
--------------------------
Delay Median ......... -2.45 ms
Delay Minimum ........ -2.45 ms
Delay Maximum ........ -1.92 ms
Delay Mean ........... -2.45 ms
Delay Mode ........... -2.45 ms
Delay 25th Percentile ... -2.45 ms
Delay 75th Percentile ... -2.44 ms
Delay 95th Percentile ... -2.44 ms
Max Clock Error ...... 0.61 ms
Common Jitter Measurements:
    P95 - P50 ........ 0.01 ms
    P75 - P25 ........ 0.01 ms
    Variance ......... 0.00 ms
    Std Deviation .... 0.01 ms
Histogram:
    -2.45 ms: 299715 packets
    -2.44 ms: 184999 packets
    -2.43 ms: 11673 packets
    -2.42 ms: 866 packets
    -2.41 ms: 567 packets
    -2.40 ms: 330 packets
    -2.39 ms: 184 packets
    -2.38 ms: 257 packets
    -2.37 ms: 375 packets
    -2.36 ms: 268 packets
    -2.35 ms: 194 packets
    -2.34 ms: 99 packets
    -2.33 ms: 71 packets
    -2.32 ms: 51 packets
    -2.31 ms: 45 packets
    -2.30 ms: 39 packets
    -2.29 ms: 27 packets
    -2.28 ms: 27 packets
    -2.27 ms: 18 packets
    -2.26 ms: 13 packets
    -2.25 ms: 12 packets
    -2.24 ms: 10 packets
    -2.23 ms: 5 packets
    -2.22 ms: 4 packets
    -2.21 ms: 9 packets
    -2.20 ms: 9 packets
    -2.18 ms: 5 packets
    -2.17 ms: 2 packets
    -2.15 ms: 1 packets
    -2.12 ms: 3 packets
    -2.11 ms: 7 packets
    -2.10 ms: 6 packets
    -2.09 ms: 5 packets
    -2.08 ms: 7 packets
    -2.07 ms: 13 packets
    -2.06 ms: 4 packets
    -2.05 ms: 8 packets
    -2.04 ms: 5 packets
    -2.03 ms: 5 packets
    -2.02 ms: 7 packets
    -2.01 ms: 3 packets
    -2.00 ms: 3 packets
    -1.99 ms: 6 packets
    -1.98 ms: 9 packets
    -1.97 ms: 6 packets
    -1.96 ms: 7 packets
    -1.95 ms: 6 packets
    -1.94 ms: 5 packets
    -1.93 ms: 7 packets
    -1.92 ms: 3 packets

TTL Statistics
--------------
TTL Median ........... 255.00
TTL Minimum .......... 255.00
TTL Maximum .......... 255.00
TTL Mean ............. 255.00
TTL Mode ............. 255.00
TTL 25th Percentile ... 255.00
TTL 75th Percentile ... 255.00
TTL 95th Percentile ... 255.00
Histogram:
    255: 500000 packets

No further runs scheduled.[machine3@localhost ~]$ pscheduler task latency -p 1008 -i 0.00002 -c 5000000 
--source machine3 --dest machine4
Submitting task...
Task URL:
https://machine3/pscheduler/tasks/137a0e98-2a2c-4693-9156-62738af59b9a
Running with tool 'owping'
Fetching first run...

Next scheduled run:
https://machine3/pscheduler/tasks/137a0e98-2a2c-4693-9156-62738af59b9a/runs/1bd57bc6-f701-4be7-b135-a98213199f12
Starts 2020-03-03T13:42:41Z (~2 seconds)
Ends   2020-03-03T13:44:32Z (~110 seconds)
Waiting for result...

Run did not complete: Failed

Limit system diagnostics for this run:

  Hints:
    requester: machine3
    server: machine3
  Identified as everybody, local-interfaces
  Classified as default, friendlies
  Application: Hosts we trust to do everything
    Group 1: Limit 'always' passed
    Group 1: Want all, 1/1 passed, 0/1 failed: PASS
    Application PASSES
  Application: Defaults applied to non-friendly hosts
    Group 1: Limit 'innocuous-tests' passed
    Group 1: Limit 'throughput-default-time' failed: Test is not 'throughput'
    Group 1: Limit 'throughput-default-udp' failed: Test is not 'throughput'
    Group 1: Limit 'idleex-default' failed: Test is not 'idleex'
    Group 1: Want any, 1/4 passed, 3/4 failed: PASS
    Application PASSES
  Proposal meets limits
  Priority set at 0:
    Initial priority  (Set to 0)


Diagnostics from machine3:
  No diagnostics.

Error from machine3:
  owping returned an error: owping: FILE=capi.c, LINE=881, Server denied 
test: 193.219.48.252;owping: FILE=owping.c, LINE=235, Session Failed!

No further runs scheduled.