perfSONAR User Q&A and Other Discussion

[Aaron Brown <>]

Hey Roderick,

Could you specify the -v flag as well for bwping? Also, could you try running 
the following on perfsonar2.sanren.ac.za:

time owping perfsonar1.sanren.ac.za 

Cheers,
Aaron

On Jul 7, 2014, at 10:16 AM, Roderick Mooi 
<>
 wrote:

> Hey Aaron
> 
> Ok. This is the output:
> 
> [rmooi@perfsonar3
>  ~]$ bwping -T owamp -c perfsonar1.sanren.ac.za -s
> perfsonar2.sanren.ac.za -x
> bwping: Using tool: owamp
> bwping: 19 seconds until test results available
> 
> RECEIVER START
> owampd[57747]: WARNING: No limits specified.
> owampd[57748]: Connection to ([155.232.40.2]:5779) from
> ([155.232.40.26]:57128)
> owampd[57748]: ControlSession([155.232.40.2]:5779) accepted from
> userid(nil):([155.232.40.26]:57128)
> owampd[57747]: ResReq ALLOWED: default:request:bandwidth = 336 (result
> = 0, limit = 0)
> owampd[57747]: ResReq ALLOWED: default:request:disk = 450 (result = 0,
> limit = 0)
> owampd[57747]: owampd: exiting...
> owampd[57748]: OWPDQuery: Unable to contact parent
> owampd[57748]: OWPDQuery: Unable to contact parent
> owampd[57747]: owampd: exited.
> 
> bwctl: local tool did not complete in allocated time frame and was
> killed
> 
> RECEIVER END
> 
> SENDER START
> owping: FILE=protocol.c, LINE=2703, _OWPReadFetchAck: Unable to read
> from socket.
> owping: FILE=owping.c, LINE=1833, Unable to fetch data for
> sid(9be82802d76528d6e7949635444eae92)
> Approximately 13.2 seconds until results available
> 
> bwctl: local tool did not complete in allocated time frame and was
> killed
> 
> SENDER END
> 
> and the other way (swopping server and client)...
> 
> [rmooi@perfsonar3
>  ~]$ bwping -T owamp -s perfsonar1.sanren.ac.za -c
> perfsonar2.sanren.ac.za -x
> bwping: Using tool: owamp
> bwping: 30 seconds until test results available
> 
> RECEIVER START
> owampd[8290]: WARNING: No limits specified.
> owampd[8291]: Connection to ([155.232.40.26]:5782) from
> ([155.232.40.2]:56968)
> owampd[8291]: ControlSession([155.232.40.26]:5782) accepted from
> userid(nil):([155.232.40.2]:56968)
> owampd[8290]: ResReq ALLOWED: default:request:bandwidth = 336 (result =
> 0, limit = 0)
> owampd[8290]: ResReq ALLOWED: default:request:disk = 450 (result = 0,
> limit = 0)
> owampd[8290]: ResReq ALLOWED: default:release:disk = 16 (result = 0,
> limit = 0)
> owampd[8290]: ResReq ALLOWED: default:release:bandwidth = 336 (result =
> 0, limit = 0)
> owampd[8290]: owampd: exiting...
> owampd[8290]: owampd: exited.
> 
> RECEIVER END
> 
> SENDER START
> Approximately 13.2 seconds until results available
> 
> --- owping statistics from [155.232.40.2]:8922 to [155.232.40.26]:40790
> ---
> SID:    9be8281ad7652910d58f5254e8b94eea
> first:  2014-07-07T16:11:30.680
> last:   2014-07-07T16:11:37.000
> 10 sent, 10 lost (100.000%), 0 duplicates
> one-way delay min/median/max = nan/nan/nan ms, (err=0.127 ms)
> one-way jitter = nan ms (P95-P50)
> TTL not reported
> no reordering
> 
> 
> SENDER END
> 
> 
> Thanks,
> 
> Roderick
> 
>>>> On 2014-07-07 at 15:46, Aaron Brown 
>>>> <>
>>>>  wrote:
>> Hey Roderick,
>> 
>> Could you try running bwping with ‘-x’ so that it grabs the
> server side of 
>> the test as well?
>> 
>> Cheers,
>> Aaron
>> 
>> On Jul 4, 2014, at 5:02 AM, Roderick Mooi 
>> <>
>>  wrote:
>> 
>>> Hi Aaron
>>> 
>>> I added these lines to /etc/sysconfig/iptables and restarted the
>>> iptables service on perfsonar1 and perfsonar2:
>>> 
>>> # bwping OWAMP Control (Incoming)
>>> -A INPUT -m state --state NEW,ESTABLISHED -m tcp -p tcp --dport
>>> 4000:4100 -j ACCEPT
>>> 
>>> # bwping OWAMP Test (Incoming)
>>> -A INPUT -m udp -p udp --dport 4000:4100 -j ACCEPT
>>> 
>>> Now it connects (control session seems to be working) and starts but
> I
>>> get blank results / errors.
>>> 
>>> 10 sent, 10 lost (100.000%), 0 duplicates
>>> one-way delay min/median/max = nan/nan/nan ms, (err=0.228 ms)
>>> 
>>> OR
>>> 
>>> owping: FILE=protocol.c, LINE=2419, _OWPReadStopSessions: Unable to
>>> read final H                                                        
> 
>>>                                               MAC block
>>> owping: FILE=protocol.c, LINE=2453, _OWPReadStopSessions: Failed
>>> owping: FILE=owping.c, LINE=1772, Test session(s) Failed...
>>> 
>>> I tried updating the owamp ports to bwctld.conf by adding owamp_port
> 
>>> 5601-5900
>>> and restarting bwctld and adding those ports to IP tables.
>>> 
>>> # bwping OWAMP Control (Incoming)
>>> -A INPUT -m state --state NEW,ESTABLISHED -m tcp -p tcp --dport
>>> 4000:4100 -j ACCEPT
>>> -A INPUT -m state --state NEW,ESTABLISHED -m tcp -p tcp --dport
>>> 5601:5900 -j ACCEPT
>>> 
>>> # bwping OWAMP Test (Incoming)
>>> -A INPUT -m udp -p udp --dport 5601:5900 -j ACCEPT
>>> -A INPUT -m udp -p udp --dport 4000:4100 -j ACCEPT
>>> 
>>> Now I get either blank results
>>> 
>>> 10 sent, 10 lost (100.000%), 0 duplicates
>>> one-way delay min/median/max = nan/nan/nan ms, (err=0.228 ms)
>>> one-way jitter = nan ms (P95-P50)
>>> 
>>> OR
>>> 
>>> owping: FILE=protocol.c, LINE=2703, _OWPReadFetchAck: Unable to
> read
>>> from socket.
>>> owping: FILE=owping.c, LINE=1833, Unable to fetch data for
>>> sid(9be8281ad760e959ff6d2f472aebc34e)
>>> 
>>> I suspect the test ports aren't open but which ports are those?
>>> 
>>> Thanks!
>>> 
>>> Regards,
>>> 
>>> Roderick
>>> 
>>>>>> On 2014-07-03 at 16:14, Aaron Brown 
>>>>>> <>
>>>>>>  wrote:
>>>> Hey Roderick,
>>>> 
>>>> bwctl doesn’t reuse the owampd daemon (due to specifics of the
>>> owamp and 
>>>> bwctl protocols) so the owampd port range isn’t applicable. The
>>> ‘owamp test’ 
>>>> port range defaults to 4000-4100 if it’s unset. Is that port
> range
>>> open in the 
>>>> firewall on your host?
>>>> 
>>>> Cheers,
>>>> Aaron
>>>> 
>>>> On Jul 3, 2014, at 9:41 AM, Roderick Mooi 
>>>> <>
> wrote:
>>>> 
>>>>> Hi Aaron
>>>>> 
>>>>> [rmooi@perfsonar3
>>>>>  ~]$ bwping -T owamp -s perfsonar1.sanren.ac.za
> -c
>>>>> perfsonar2.sanren.ac.za
>>>>> bwping: Using tool: owamp
>>>>> bwping: 18 seconds until test results available
>>>>> 
>>>>> SENDER START
>>>>> owping: FILE=owping.c, LINE=1598, Unable to open control
> connection
>>> to
>>>>> [155.232.40.26]:4003.
>>>>> bwctl: local tool exited before expected with status=1
>>>>> 
>>>>> SENDER END
>>>>> 
>>>>> bwctl, bwping (ping) work fine. owampd and bwctld are running on
>>> both
>>>>> perfsonar1 and perfsonar2.
>>>>> 
>>>>> What do I have to do to get bwping -T owamp working?
>>>>> 
>>>>> Thanks!
>>>>> 
>>>>> Regards,
>>>>> 
>>>>> Roderick 
>>>>> 
>>>>>>>> On 2014-02-18 at 20:11, Aaron Brown 
>>>>>>>> <>
> wrote:
>>>>>> Hi all,
>>>>>> 
>>>>>> A new version of BWCTL is now available. BWCTL 1.5.1 is a major
>>>>> upgrade over 
>>>>>> the previously released version.
>>>>>> 
>>>>>> Notable additions in this release:
>>>>>> - Support for ping and owping (Run 'bwping -h' to see the
>>> available
>>>>> options)
>>>>>> - Support for traceroute and tracepath (Run 'bwtraceroute -h' to
>>> see
>>>>> the 
>>>>>> available options)
>>>>>> - Support for iperf3, and improved support for nuttcp
>>>>>> - Support for working behind a firewall for iperf3, ping,
>>> traceroute
>>>>> and 
>>>>>> tracepath (use the "--flip" flag when the receiver is behind the
>>>>> firewall)
>>>>>> - Handles NTP unsync a bit better (the daemon start, but will
> deny
>>>>> tests 
>>>>>> until NTP is synchronized)
>>>>>> 
>>>>>> Those who are using the perfSONAR Toolkit, or otherwise have the
>>>>> Internet2 
>>>>>> RPM repository enabled, can run 'yum update' to get the latest
>>>>> changes. For 
>>>>>> those who are installing from source or prefer to install the
> RPMs
>>>>> manually, 
>>>>>> the newest version can be downloaded from
>>>>> http://software.internet2.edu/ . 
>>>>>> After installation, you will need to restart bwctld to use the
> new
>>>>> features. 
>>>>>> You can do this by running “/etc/init.d/bwctld restart”.
>>>>>> 
>>>>>> Please let us know if you have any questions and we look forward
> to
>>> 
>>>>>> everyone's continued feedback and support!
>>>>>> 
>>>>>> Thank you,
>>>>>> The perfSONAR-PS Development Team
>>>>>> -- 
>>>>>> This message is subject to the CSIR's copyright terms and
>>> conditions,
>>>>> e-mail 
>>>>>> legal notice, and implemented Open Document Format (ODF)
> standard.
>>> 
>>>>>> The full disclaimer details can be found at 
>>>>>> http://www.csir.co.za/disclaimer.html.
>>>>>> 
>>>>>> This message has been scanned for viruses and dangerous content
> by
>>> 
>>>>>> MailScanner, 
>>>>>> and is believed to be clean.
>>>>>> 
>>>>>> Please consider the environment before printing this email.
>>>>> 
>>>>> -- 
>>>>> This message is subject to the CSIR's copyright terms and
>>> conditions, e-mail 
>>>> legal notice, and implemented Open Document Format (ODF) standard.
> 
>>>>> The full disclaimer details can be found at 
>>>> http://www.csir.co.za/disclaimer.html.
>>>>> 
>>>>> This message has been scanned for viruses and dangerous content by
> 
>>>> MailScanner, 
>>>>> and is believed to be clean.
>>>>> 
>>>>> Please consider the environment before printing this email.
>>>>> 
>>>> 
>>>> 
>>>> -- 
>>>> This message is subject to the CSIR's copyright terms and
> conditions,
>>> e-mail 
>>>> legal notice, and implemented Open Document Format (ODF) standard.
> 
>>>> The full disclaimer details can be found at 
>>>> http://www.csir.co.za/disclaimer.html.
>>>> 
>>>> This message has been scanned for viruses and dangerous content by
> 
>>>> MailScanner, 
>>>> and is believed to be clean.
>>>> 
>>>> Please consider the environment before printing this email.
>>> 
>>> -- 
>>> This message is subject to the CSIR's copyright terms and
> conditions, e-mail 
>> legal notice, and implemented Open Document Format (ODF) standard. 
>>> The full disclaimer details can be found at 
>> http://www.csir.co.za/disclaimer.html.
>>> 
>>> This message has been scanned for viruses and dangerous content by 
>> MailScanner, 
>>> and is believed to be clean.
>>> 
>>> Please consider the environment before printing this email.
>>> 
>> 
>> 
>> -- 
>> This message is subject to the CSIR's copyright terms and conditions,
> e-mail 
>> legal notice, and implemented Open Document Format (ODF) standard. 
>> The full disclaimer details can be found at 
>> http://www.csir.co.za/disclaimer.html.
>> 
>> This message has been scanned for viruses and dangerous content by 
>> MailScanner, 
>> and is believed to be clean.
>> 
>> Please consider the environment before printing this email.
> 
> -- 
> This message is subject to the CSIR's copyright terms and conditions, 
> e-mail legal notice, and implemented Open Document Format (ODF) standard. 
> The full disclaimer details can be found at 
> http://www.csir.co.za/disclaimer.html.
> 
> This message has been scanned for viruses and dangerous content by 
> MailScanner, 
> and is believed to be clean.
> 
> Please consider the environment before printing this email.
>