[ovs-discuss] Using --ovs with ovn-sbctl lflow-list

[Ankur Sharma]

Hi Ben,

Got it, thanks a lot for pointing out.
Do we have some documentation indicating how to start tcp server  that switch would listen to?

Appreciate your help

Regards,
Ankur


-----Original Message-----
From: Ben Pfaff [mailto:blp at ovn.org] 
Sent: Wednesday, May 9, 2018 8:31 AM
To: Ankur Sharma <ankur.sharma at nutanix.com>
Cc: ovs-discuss at openvswitch.org
Subject: Re: [ovs-discuss] Using --ovs with ovn-sbctl lflow-list

On Tue, May 08, 2018 at 11:44:44PM +0000, Ankur Sharma wrote:
> Hi,
> 
> We are trying to use "--ovs" option with ovn-sbctl  lflow-list command 
> (https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openv
> switch_ovs_commit_c2f4c39be4e288e7a08974aea53b18627a1ef9ef&d=DwIBAg&c=
> s883GpUCOChKOHiocYtGcg&r=mZwX9gFQgeJHzTg-68aCJgsODyUEVsHGFOfL90J6MJY&m
> =x0l3zFaEXEIKMYIEKQslilS0ifJUN_CD16qSs2wQD64&s=0fZZp6JkZJLQJE20wvPcFce
> xCAaSuBEvKY6R5qc3LYo&e=) Running it on remote controller always fails 
> with connection refused error.
> 
> Do we have to start something on vswitch side?
> Please feel free to point out if we are missing something basic.
> 
> Example:
> ovn-sbctl --ovs=tcp:HYPERVISOR_IP dump-flows
> 
> 2018-05-08T23:43:16Z|00001|stream|WARN|The default OpenFlow port 
> number has changed from 6633 to 6653
> 2018-05-08T23:43:16Z|00002|sbctl|WARN|tcp:10.15.17.211: connection 
> failed (Connection refused)

Is the switch listening for tcp connections?  It doesn't by default.