perfSONAR User Q&A and Other Discussion

[Jarvis Zhang <>]

Hi,

I set several tests on my host, but some tests only work unidirectionally. For throughput 

This problem is a little complicate. Here is my address: http://115.25.138.244/serviceTest/psGraph.cgi

The throughput test works on command line but fails on web interface.

The one-way delay test doesn’t work even on command line; I think maybe the problem has something to do with the port, but I have no idea where to start with.

The ping delay test never work.

Attachment is regular_testing.log. Here is more details:

1. For throughput test:
a) 115.25.138.244(my host) to 128.104.100.67(komatsu) stops working since I update from v3.3.2 to 3.4 yesterday. but the command line still works.

[zwzhang@jsi-inspur02 perfsonar]$ bwctl -c 128.104.100.67
bwctl: Using tool: iperf
bwctl: 27 seconds until test results available

RECEIVER START
bwctl: exec_line: iperf -B komatsu.chtc.wisc.edu -s -f b -m -p 5019 -t 10
bwctl: start_tool: 3624097458.082252
------------------------------------------------------------
Server listening on TCP port 5019
Binding to local address komatsu.chtc.wisc.edu
TCP window size: 87380 Byte (default)
------------------------------------------------------------
[ 14] local 128.104.100.67 port 5019 connected with 115.25.138.244 port 52456
[ ID] Interval       Transfer     Bandwidth
[ 14]  0.0-11.5 sec  36438016 Bytes  25453583 bits/sec
[ 14] MSS size 1436 bytes (MTU 1500 bytes, ethernet)
bwctl: stop_exec: 3624097473.816542

RECEIVER END

b) 2001:da8:203:d406:16da:e9ff:fef9:b68f(my host) to 2607:f388:107c:501:202:c9ff:fee8:85a0(komatsu) never works, but the command line still works, as above.

c) 159.226.15.235(cnic) to 115.25.138.244(my host) stops working since I update from v3.3.2 to 3.4 yesterday. so does the command line.

[zwzhang@jsi-inspur02 perfsonar]$ bwctl -s 159.226.15.235
bwctl: Using tool: iperf
bwctl: 20 seconds until test results available

RECEIVER START

bwctl: remote peer cancelled test

RECEIVER END

d) 2400:dd01:1011:1:92b1:1cff:fe0c:7c0a(cnic) to 2001:da8:203:d406:16da:e9ff:fef9:b68f(my host) stops working since I update from v3.3.2 to 3.4 yesterday. so does the command line, as above.

e) 115.25.138.244 to 137.110.119.113 works well bidirectionally.

2. For one-way latency

a) 128.104.100.67(komatsu) to 115.25.138.244(my host) doesn’t work, so does the command line.

--- owping statistics from [128.104.100.67]:8944 to [jsi-inspur02]:8841 ---
SID: 73198af4d8035c80a36f5244c1e63df9
first: 2014-11-04T22:09:06.866
last: 2014-11-04T22:09:17.026
100 sent, 100 lost (100.000%), 0 duplicates
one-way delay min/median/max = nan/nan/nan ms, (err=0.104 ms)
one-way jitter = nan ms (P95-P50)
TTL not reported
no reordering

b)159.226.15.235(cnic) to 115.25.138.244(my host) doesn’t work , so does the command line.

c) 137.110.119.113(murpa) doesn’t work bidirectionally.

d) Other ipv6 addresses work well.

3. All ping latency doesn’t work.

Any insights appreciated.

Thanks,

Jarvis

Attachment: regular_testing.log
Description: Binary data