perfSONAR User Q&A and Other Discussion

[<>]

Hello all,

We have a running and green maddash for several local systems. Problem occurs
when adding an external system(from a different campus). I can run traceroute
against other systems but not throughput and latency.(details posted below) I
can reproduce this issue if I test the other way around. Network and firewall
is proved not the issue. The external system works fine alone. During the test
the remote server did received similar packets as the good runs so I assume
the host requests to the remote server for the port but the server does not
properly open up the port. maybe privilege issue?  Appreciate any suggestions!

Note: for throughput test, it will run successfully if we manually open up
port 5201 on the remote server.

Thanks,
Shawn Wang,
Northwestern University

***********************************************************
throughput test error:
$pscheduler task --assist 10.244.23.13:9443 latency --source-node
10.244.23.13:9443 --dest 10.244.25.4 --dest-node 10.244.25.4:9443 --source
10.244.23.13
Run failed.
Limit system diagnostics:
  Hints:
    requester: 10.244.23.13
    server: 10.244.23.13
  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' failed: Passed but inverted
    Group 1: Limit 'throughput-default-time' passed
    Group 1: Limit 'idleex-default' failed: Test is not 'idleex'
    Group 1: Want any, 1/3 passed, 2/3 failed: PASS
    Application PASSES
  Proposal meets limits


Diagnostics from 10.244.23.13:9443:
    (No diagnostics)

Error from 10.244.23.13:9443:
    iperf3 returned an error: error - unable to connect to server: Connection
refused

Diagnostics from 10.244.25.4:9443:
    No result was produced

Error from 10.244.25.4:9443:
    No result was produced

No further runs scheduled.

***********************************************************
latency test:
$pscheduler task --assist 10.244.23.13:9443 throughput --source-node
10.244.23.13:9443 --dest 10.244.25.4 --dest-node 10.244.25.4:9443 --source
10.244.23.13
Packet Statistics
-----------------
Packets Sent ......... 0 packets
Packets Received ..... 0 packets
Packets Lost ......... 0 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.