perfSONAR User Q&A and Other Discussion

[Aaron Brown <>]

Hello Amjad,

If the receiving side isn’t running bwctl, you can add the “-E” parameter to the bwping command, and it will run anyway.

Cheers,

Aaron

On Apr 21, 2014, at 11:57 PM, Md. Amjad Hossain <> wrote:

I am using bwping command as follow:

[root@kahuku ~]# bwping -s 198.129.254.58 -c 128.125.88.69

bwping: Using tool: ping

bwping: 29 seconds until test results available

SENDER START

bwctl: start_endpoint: 3607124799.332979

bwctl: run_endpoint: receiver: 128.125.88.69

bwctl: run_endpoint: sender: 198.129.254.58

bwctl: exec_line: ping -c 10 -i 1.000000 -W 1 -I 198.129.254.58 128.125.88.69

bwctl: run_tool: tester: ping

bwctl: run_tool: receiver: 128.125.88.69

bwctl: run_tool: sender: 198.129.254.58

bwctl: start_tool: 3607124814.473718

PING 128.125.88.69 (128.125.88.69) from 198.129.254.58 : 56(84) bytes of data.

64 bytes from 128.125.88.69: icmp_seq=1 ttl=60 time=8.29 ms

64 bytes from 128.125.88.69: icmp_seq=2 ttl=60 time=8.23 ms

64 bytes from 128.125.88.69: icmp_seq=3 ttl=60 time=8.28 ms

64 bytes from 128.125.88.69: icmp_seq=4 ttl=60 time=8.23 ms

64 bytes from 128.125.88.69: icmp_seq=5 ttl=60 time=8.24 ms

64 bytes from 128.125.88.69: icmp_seq=6 ttl=60 time=8.27 ms

64 bytes from 128.125.88.69: icmp_seq=7 ttl=60 time=8.23 ms

64 bytes from 128.125.88.69: icmp_seq=8 ttl=60 time=8.22 ms

64 bytes from 128.125.88.69: icmp_seq=9 ttl=60 time=8.23 ms

64 bytes from 128.125.88.69: icmp_seq=10 ttl=60 time=8.24 ms

--- 128.125.88.69 ping statistics ---

10 packets transmitted, 10 received, 0% packet loss, time 9020ms

rtt min/avg/max/mdev = 8.220/8.251/8.295/0.102 ms

bwctl: stop_tool: 3607124823.495001

bwctl: stop_endpoint: 3607124823.495136

SENDER END

/////////////////////////////////////////// ok so far///////////////////////////////////////////////////////////

Now if I change the receive host in the above command with another IP where no bwctl running, get error:

[root@kahuku ~]# bwping -s 198.129.254.58 -c 180.211.191.42

bwping: Unable to connect to 180.211.191.42

Regards

Amjad

On Mon, Apr 21, 2014 at 11:48 PM, Brian Tierney <> wrote:

Can you send the exact command you are using?

On Mon, Apr 21, 2014 at 8:20 PM, Md. Amjad Hossain <> wrote:
> But I am getting error if one of the hosts does have bwctl installed. Its
> says can't connect to "  receive machine ".
>
>
> On Mon, Apr 21, 2014 at 10:42 PM, Brian Tierney <> wrote:
>>
>> You need bwctl installed on the sending side.
>>
>>
>> On Mon, Apr 21, 2014 at 7:08 PM, Md. Amjad Hossain <>
>> wrote:
>> > Hi,
>> >
>> > Does bwping work between any two arbitrary machines with public IPs? or
>> > The
>> > hosts must have perfsonar running?
>> >
>> > I can't remember whether I was successful that time to ping between
>> > non-perfsonar machines. Now Its not working. Only I can ping between two
>> > remote machine where is perfsonar running.
>> >
>> > Regards
>> > Amjad
>> >
>> >
>> > On Sun, Mar 16, 2014 at 9:41 PM, Brian Tierney <> wrote:
>> >>
>> >> Not currently, but in the next release there will be (hopefully in
>> >> May).
>> >>
>> >>
>> >> On Sun, Mar 16, 2014 at 4:13 PM, Md. Amjad Hossain <>
>> >> wrote:
>> >> > Thank you very much.
>> >> >
>> >> > Is there any way to schedule these tests in perfsonar?
>> >> >
>> >> > -Amjad
>> >> >
>> >> >
>> >> > On Sun, Mar 16, 2014 at 12:55 PM, Brian Tierney <>
>> >> > wrote:
>> >> >>
>> >> >> The newest version of bwctl includes the tool bwping which supports
>> >> >> this.
>> >> >>
>> >> >> See:
>> >> >>
>> >> >>
>> >> >> http://fasterdata.es.net/performance-testing/network-troubleshooting-tools/bwctl/
>> >> >>
>> >> >>
>> >> >>
>> >> >> On Fri, Mar 14, 2014 at 8:23 PM,  <> wrote:
>> >> >> > Hi,
>> >> >> >
>> >> >> > Is there any way in perfsonar to run ping between two remote
>> >> >> > hosts? I
>> >> >> > mean How
>> >> >> > can I run ping or traceroute command/or perfsonar test from point
>> >> >> > C
>> >> >> > between
>> >> >> > point A and B. Perfsonar running in point C.
>> >> >> >
>> >> >> > Thanks
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Brian Tierney, http://www.es.net/tierney
>> >> >>
>> >> >> Energy Sciences Network (ESnet), Berkeley National Lab
>> >> >>
>> >> >> http://fasterdata.es.net
>> >> >
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Brian Tierney, http://www.es.net/tierney
>> >>
>> >> Energy Sciences Network (ESnet), Berkeley National Lab
>> >>
>> >> http://fasterdata.es.net
>> >
>> >
>>
>>
>>
>> --
>> Brian Tierney, http://www.es.net/tierney
>>
>> Energy Sciences Network (ESnet), Berkeley National Lab
>>
>> http://fasterdata.es.net
>
>



--
Brian Tierney, http://www.es.net/tierney

Energy Sciences Network (ESnet), Berkeley National Lab

http://fasterdata.es.net