perfsonar-user - [perfsonar-user] Re: [perf-node-users] RE: BWCTL- remote peer cancelled test
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: Jason Zurawski <>
- To: Amit <>
- Cc: " Users" <>, , perfsonar-ps-users <>
- Subject: [perfsonar-user] Re: [perf-node-users] RE: BWCTL- remote peer cancelled test
- Date: Wed, 31 Jul 2013 10:29:44 -0400
Hi Amit;
To be clear, the scheduling will queue the tests on the various daemons on
your hosts so that you can run many tests eventually, but each daemon runs
only one test a time.
Thanks;
-jason
On Jul 31, 2013, at 10:26 AM, Amit
<>
wrote:
> Hi Jason,
>
> Agreed, but doing scheduled test should solve this purpose I think.
>
>
> --
> Thanks & Regards
>
> Amit Kumar
> Scientific Officer
> Operation and Routing Group
> M/O Communication and IT, NIC, A- Block, CGO Complex, New Delhi
> Ph. 24305091, NKN VoIP:5032
>
>
>
>
> -----Original Message-----
> From: Jason Zurawski
> [mailto:]
>
> Sent: Wednesday, July 31, 2013 7:46 PM
> To: Amit
> Cc:
>
> Users;
> ;
> perfsonar-ps-users
> Subject: Re: [perf-node-users] RE: BWCTL- remote peer cancelled test
>
> Amit;
>
> To answer the other question:
>
>>>> I have connected 6-7 perfsonar servers in my network. Now I would like
> to test the bandwidth of the link connecting these servers. So I planned to
> run scheduled test from server1 to other 5 servers.
>>>> But It doesn't seems to run. It shows error "remote peer cancelled
> test". Also I don't see any graph.
>>>> Please find attached logs
>>>>
>>>> Can't I ran more than one scheduled bandwidth test at a time?
>
> BWCTL is a serial tester, it only lets you test one test at a time.
>
> Thanks;
>
> -jason
>
> On Jul 31, 2013, at 10:12 AM, Aaron Brown
> <>
> wrote:
>
>> Hey Amit,
>>
>> Could you try adding the "-i 2" flag and seeing what the result is?
>>
>> Cheers,
>> Aaron
>>
>> On Jul 31, 2013, at 7:32 AM, Amit
>> <>
>> wrote:
>>
>>> Hi,
>>>
>>> I am not able to run any bwctl test from cli mode also and also from any
> of 6 servers.
>>> Please find below error:
>>>
>>> [root@localhost
>>> ~]# bwctl -c 14.139.5.201 -s 14.139.5.202
>>> bwctl: Using tool: iperf
>>> bwctl: 16 seconds until test results available
>>>
>>> RECEIVER START
>>> bwctl: exec_line: iperf -B 14.139.5.201 -s -f b -m -p 5103 -t 10
>>> bwctl: start_tool: 3584258840.361688
>>> ------------------------------------------------------------
>>> Server listening on TCP port 5103
>>> Binding to local address 14.139.5.201 TCP window size: 87380 Byte
>>> (default)
>>> ------------------------------------------------------------
>>> [ 15] local 14.139.5.201 port 5103 connected with 14.139.5.202 port
>>> 5103
>>> bwctl: stop_exec: 3584258854.896837
>>>
>>> RECEIVER END
>>>
>>>
>>> [root@localhost
>>> ~]# bwctl -c 14.139.5.206 -s 14.139.5.205
>>> bwctl: Using tool: iperf
>>> bwctl: 16 seconds until test results available
>>>
>>> RECEIVER START
>>> bwctl: exec_line: iperf -B 14.139.5.206 -s -f b -m -p 5018 -t 10
>>> bwctl: start_tool: 3584258952.610546
>>> ------------------------------------------------------------
>>> Server listening on TCP port 5018
>>> Binding to local address 14.139.5.206 TCP window size: 87380 Byte
>>> (default)
>>> ------------------------------------------------------------
>>> [ 15] local 14.139.5.206 port 5018 connected with 14.139.5.205 port
>>> 5018
>>> bwctl: local tool did not complete in allocated time frame and was
>>> killed
>>> bwctl: stop_exec: 3584258967.376065
>>>
>>> RECEIVER END
>>>
>>> Please help..
>>>
>>>
>>> --
>>> Thanks & Regards
>>>
>>> Amit Kumar
>>> Scientific Officer
>>> Operation and Routing Group
>>> M/O Communication and IT, NIC, A- Block, CGO Complex, New Delhi Ph.
>>> 24305091, NKN VoIP:5032
>>>
>>>
>>>
>>> From: Amit
>>> [mailto:]
>>> Sent: Tuesday, July 30, 2013 7:03 PM
>>> To:
>>>
>>> Subject: BWCTL- remote peer cancelled test
>>>
>>> Hi,
>>>
>>> I have connected 6-7 perfsonar servers in my network. Now I would like to
> test the bandwidth of the link connecting these servers. So I planned to run
> scheduled test from server1 to other 5 servers.
>>> But It doesn't seems to run. It shows error "remote peer cancelled test".
> Also I don't see any graph.
>>> Please find attached logs
>>>
>>> Can't I ran more than one scheduled bandwidth test at a time?
>>>
>>> Also find below output of ps auwx
>>>
>>> [root@localhost
>>> ~]# ps auwx | grep bwctl
>>> 499 22947 0.0 0.0 2816 916 ? S 15:07 0:00
> /usr/bin/bwctl -T iperf -e local5 -p -B 14.139.5.202 -q -I 600 -t 20 -d
> 14846829.IPV4/KNOPPIX/14_139_5_201 -s [14.139.5.201]:4823 -c 14.139.5.202
>>> 499 22948 0.0 0.0 2816 908 ? S 15:07 0:00
> /usr/bin/bwctl -T iperf -e local5 -p -B 14.139.5.202 -q -I 600 -t 20 -d
> 14846829.IPV4/KNOPPIX/14_139_5_203 -s [14.139.5.203]:4823 -c 14.139.5.202
>>> 499 22949 0.0 0.0 2816 912 ? S 15:07 0:00
> /usr/bin/bwctl -T iperf -e local5 -p -B 14.139.5.202 -q -I 600 -t 20 -d
> 14846829.IPV4/KNOPPIX/14_139_5_205 -s [14.139.5.205]:4823 -c 14.139.5.202
>>> 499 22950 0.0 0.0 2816 904 ? S 15:07 0:00
> /usr/bin/bwctl -T iperf -e local5 -p -B 14.139.5.202 -q -I 600 -t 20 -d
> 14846829.IPV4/KNOPPIX/14_139_5_206 -s [14.139.5.206]:4823 -c 14.139.5.202
>>> 499 22951 0.0 0.0 2816 904 ? S 15:07 0:00
> /usr/bin/bwctl -T iperf -e local5 -p -B 14.139.5.202 -q -I 600 -t 20 -d
> 14846829.IPV4/KNOPPIX/14_139_5_207 -s [14.139.5.207]:4823 -c 14.139.5.202
>>> 499 22952 0.0 0.0 2816 940 ? S 15:07 0:00
> /usr/bin/bwctl -T iperf -e local5 -p -B 14.139.5.202 -q -I 600 -t 20 -d
> 14846829.IPV4/14_139_5_201/KNOPPIX -s 14.139.5.202 -c [14.139.5.201]:4823
>>> 499 22953 0.0 0.0 2816 932 ? S 15:07 0:00
> /usr/bin/bwctl -T iperf -e local5 -p -B 14.139.5.202 -q -I 600 -t 20 -d
> 14846829.IPV4/14_139_5_203/KNOPPIX -s 14.139.5.202 -c [14.139.5.203]:4823
>>> 499 22954 0.0 0.0 2816 900 ? S 15:07 0:00
> /usr/bin/bwctl -T iperf -e local5 -p -B 14.139.5.202 -q -I 600 -t 20 -d
> 14846829.IPV4/14_139_5_205/KNOPPIX -s 14.139.5.202 -c [14.139.5.205]:4823
>>> 499 22956 0.0 0.0 2816 932 ? S 15:07 0:00
> /usr/bin/bwctl -T iperf -e local5 -p -B 14.139.5.202 -q -I 600 -t 20 -d
> 14846829.IPV4/14_139_5_206/KNOPPIX -s 14.139.5.202 -c [14.139.5.206]:4823
>>> 499 22959 0.0 0.0 2816 900 ? S 15:07 0:00
> /usr/bin/bwctl -T iperf -e local5 -p -B 14.139.5.202 -q -I 600 -t 20 -d
> 14846829.IPV4/14_139_5_207/KNOPPIX -s 14.139.5.202 -c [14.139.5.207]:4823
>>> bwctl 23058 0.0 0.0 2844 764 ? Ss 15:08 0:00
> /usr/bin/bwctld -c /etc/bwctld -R /var/run
>>> bwctl 23252 0.0 0.0 3064 780 ? S 15:17 0:00
> /usr/bin/bwctld -c /etc/bwctld -R /var/run
>>> bwctl 23253 0.0 0.0 3064 784 ? S 15:17 0:00
> /usr/bin/bwctld -c /etc/bwctld -R /var/run
>>> bwctl 23254 0.0 0.0 3064 784 ? S 15:17 0:00
> /usr/bin/bwctld -c /etc/bwctld -R /var/run
>>> bwctl 23255 0.0 0.0 3064 784 ? S 15:17 0:00
> /usr/bin/bwctld -c /etc/bwctld -R /var/run
>>> bwctl 23256 0.0 0.0 3064 784 ? S 15:17 0:00
> /usr/bin/bwctld -c /etc/bwctld -R /var/run
>>> bwctl 23257 0.0 0.0 3056 788 ? S 15:17 0:00
> /usr/bin/bwctld -c /etc/bwctld -R /var/run
>>> bwctl 23258 0.0 0.0 3056 788 ? S 15:17 0:00
> /usr/bin/bwctld -c /etc/bwctld -R /var/run
>>> bwctl 23259 0.0 0.0 3056 788 ? S 15:17 0:00
> /usr/bin/bwctld -c /etc/bwctld -R /var/run
>>> bwctl 23260 0.0 0.0 3064 788 ? S 15:17 0:00
> /usr/bin/bwctld -c /etc/bwctld -R /var/run
>>> bwctl 23261 0.0 0.0 3064 788 ? S 15:17 0:00
> /usr/bin/bwctld -c /etc/bwctld -R /var/run
>>> bwctl 23382 0.0 0.0 3064 588 ? S 15:27 0:00
> /usr/bin/bwctld -c /etc/bwctld -R /var/run
>>> bwctl 23383 0.0 0.0 3064 588 ? S 15:27 0:00
> /usr/bin/bwctld -c /etc/bwctld -R /var/run
>>> bwctl 23384 0.0 0.0 3064 548 ? S 15:27 0:00
> /usr/bin/bwctld -c /etc/bwctld -R /var/run
>>> bwctl 23386 0.0 0.0 3064 548 ? S 15:27 0:00
> /usr/bin/bwctld -c /etc/bwctld -R /var/run
>>> bwctl 23388 0.0 0.0 3064 548 ? S 15:27 0:00
> /usr/bin/bwctld -c /etc/bwctld -R /var/run
>>> bwctl 23390 0.0 0.0 3064 548 ? S 15:27 0:00
> /usr/bin/bwctld -c /etc/bwctld -R /var/run
>>> bwctl 23391 0.0 0.0 3064 548 ? S 15:27 0:00
> /usr/bin/bwctld -c /etc/bwctld -R /var/run
>>> bwctl 23392 0.0 0.0 3068 624 ? S 15:27 0:00
> /usr/bin/bwctld -c /etc/bwctld -R /var/run
>>> bwctl 23393 0.0 0.0 36188 888 ? Sl 15:27 0:00 iperf -B
> 14.139.5.202 -s -f b -m -p 5184 -t 20
>>> bwctl 23394 0.0 0.0 3068 616 ? S 15:27 0:00
> /usr/bin/bwctld -c /etc/bwctld -R /var/run
>>> bwctl 23395 0.0 0.0 3068 616 ? S 15:27 0:00
> /usr/bin/bwctld -c /etc/bwctld -R /var/run
>>> bwctl 23396 0.0 0.0 3068 616 ? S 15:27 0:00
> /usr/bin/bwctld -c /etc/bwctld -R /var/run
>>> bwctl 23397 0.0 0.0 3068 616 ? S 15:27 0:00
> /usr/bin/bwctld -c /etc/bwctld -R /var/run
>>> bwctl 23398 0.0 0.0 3068 616 ? S 15:27 0:00
> /usr/bin/bwctld -c /etc/bwctld -R /var/run
>>>
>>> Please Help, as very soon I am going to deploy perfsonar servers into my
> country wide network.
>>> --
>>> Thanks & Regards
>>>
>>> Amit Kumar
>>> Scientific Officer
>>> Operation and Routing Group
>>> M/O Communication and IT, NIC, A- Block, CGO Complex, New Delhi Ph.
>>> 24305091, NKN VoIP:5032
- [perfsonar-user] Re: [perf-node-users] RE: BWCTL- remote peer cancelled test, Aaron Brown, 07/31/2013
- [perfsonar-user] Re: [perf-node-users] RE: BWCTL- remote peer cancelled test, Jason Zurawski, 07/31/2013
- [perfsonar-user] RE: [perf-node-users] RE: BWCTL- remote peer cancelled test, Amit, 07/31/2013
- [perfsonar-user] Re: [perf-node-users] RE: BWCTL- remote peer cancelled test, Jason Zurawski, 07/31/2013
- [perfsonar-user] RE: [perf-node-users] RE: BWCTL- remote peer cancelled test, Amit, 07/31/2013
- [perfsonar-user] Re: [perf-node-users] RE: BWCTL- remote peer cancelled test, Jason Zurawski, 07/31/2013
Archive powered by MHonArc 2.6.16.