[ovs-discuss] is this a bug?

[Ashok Chippa]

After fixing the "ovs-vsctl set-controller..."  command (with tcp:
127.0.0.1:6789 instead of just 127.0.0.1:6789), I can now get the
openvswitch connecting to my controller...

However, it seems (but I could be wrong) that the switch seems to be
repeatedly connecting with the controller:
ashok-vb$ python dispatcher.py
_dispatcher_init()
listening on socket: 127:0.0.1:6789
Connected with 127.0.0.1:39548
Connected with 127.0.0.1:39549
Connected with 127.0.0.1:39550
Connected with 127.0.0.1:39551
Connected with 127.0.0.1:39552
Connected with 127.0.0.1:39553
Connected with 127.0.0.1:39554
Connected with 127.0.0.1:39555
Connected with 127.0.0.1:39556
Connected with 127.0.0.1:39557
Connected with 127.0.0.1:39558
Connected with 127.0.0.1:39559
Connected with 127.0.0.1:39560
Connected with 127.0.0.1:39561
...

Any clues from openvswitch + socket experts out there as to why this may be
happening? Appreciate it.

Thanks,
Ashok


On Fri, Dec 26, 2014 at 2:55 PM, Ashok Chippa <a.n.chippa at gmail.com> wrote:

> Thank you Ansis, appreciate your response. If that's the case, I assume
> the openvswitch should be punting to whatever it shows as the controller in
> the output of "ovs-ofctl get-controller ...".. right?
>
> How do I capture the packets that the openvswitch datapath is punting? My
> epoll event is not getting triggered in my controller.
>
> When I reboot my controller, does the controller have to do anything else
> (other than listening on the right tcp port) for the openvswitch to try and
> connect to the controller? Or does the openvswitch periodically tries to
> connect to the controller (as long as it knows which controller(s) to
> connect to)? I would think the latter, but would be good to know from the
> horse's mouth :(
>
> I am sure this is documented somewhere, but at the moment I do not have
> the luxury to pour through documentation... :(   Sorry for the noise,
> appreciate your help.
>
> Thanks,
> Ashok
>
>
> On Fri, Dec 26, 2014 at 2:14 PM, Ansis Atteka <aatteka at vmware.com> wrote:
>
>>      Hello,
>>
>>  1. I set the controller and check it:
>> root at ashok-vb:/home/achippa/firewall# ovs-vsctl get-controller br-int
>> 127.0.0.1:8888
>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__127.0.0.1-3A8888&d=AwMFaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=AseqGobniu17eZwiefRxV_Xyfy_6IbJC3cK8jL-bARY&m=ATViXTnW2UrPM3LJ4S7etR-a7L7p677l-U5Tm5g7z5M&s=8HbXgkG7qkLu8r8ikv3bp2fNB8h0oSTlzMCF9i9v9g4&e=>
>>
>>  2. I add a flow with actions set to controller:
>> root at ashok-vb:/home/achippa/firewall# ovs-ofctl add-flow br-int
>> table=0,priority=0,actions=controller
>>
>>  3. I dump the flows:
>> root at ashok-vb:/home/achippa/firewall# ovs-ofctl dump-flows br-int
>> NXST_FLOW reply (xid=0x4):
>>  cookie=0x0, duration=8.967s, table=0, n_packets=0, n_bytes=0,
>> idle_age=8, priority=0 actions=CONTROLLER:65535
>>
>>  Even though controller was set to 127.0.0.1:8888
>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__127.0.0.1-3A8888&d=AwMFaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=AseqGobniu17eZwiefRxV_Xyfy_6IbJC3cK8jL-bARY&m=ATViXTnW2UrPM3LJ4S7etR-a7L7p677l-U5Tm5g7z5M&s=8HbXgkG7qkLu8r8ikv3bp2fNB8h0oSTlzMCF9i9v9g4&e=>
>> why does it still default to 65535?
>>
>>  What am I missing? Appreciate your help.
>>
>> [Ansis]: ​65535 is *not TCP port number* but instead *how many bytes of
>> the packet you want to be sent to the controller*. Answer to your
>> question can be found in "man ovs-ofctl".
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20141226/4fe8804d/attachment-0002.html>