[ovs-discuss] OVS 2.6.0 - Ovs-ofctl can not get flows

[Justin Pettit]

> On Nov 18, 2016, at 2:14 AM, zhi <changzhi1990 at gmail.com> wrote:
> 
> hi, all
> 
> I downloaded the OVS 2.6.0 and installed it following by here[1]. But I met a strange problem, please let me show you:
> 
> root at devstack:~# ovs-vsctl show
> 6e695086-6663-4fd0-b713-5a12605c92cb
>     Bridge br-int
>         Port br-int
>             Interface br-int
>                 type: internal
>     Bridge br-ex
>         Port br-ex
>             Interface br-ex
>                 type: internal
>     ovs_version: "2.6.0"
> root at devstack:~# ovs-ofctl dump-flows br-int
> ovs-ofctl: br-int is not a bridge or a socket
> root at devstack:~# ovs-vsctl add-br br00
> root at devstack:~# ovs-ofctl dump-flows br00
> ovs-ofctl: br00 is not a bridge or a socket
> 
> To be brief, ovs-ofctl tool can not get any bridges anymore. Bridge " br-int " and " br-ex " were read from ovsdb. Error happens when I create a new bridge and try to dump its flows.
> 
> I can use ovs-vsctl tool to see all bridges and using ovs-ofctl tool can not dump any flows, why?
> 
> I setup ovs services like this:
> 
> root at devstack:~# ps -ef|grep ovs
> root     22238     1  0 17:48 ?        00:00:00 ovsdb-server --remote=punix:/usr/var/run/openvswitch/db.sock --private-key=db:Open_vSwitch,SSL,private_key --certificate=db:Open_vSwitch,SSL,certificate --bootstrap-ca-cert=db:Open_vSwitch,SSL,ca_cert --pidfile --detach
> root     22242     1  0 17:48 ?        00:00:02 ovs-vswitchd --pidfile --detach unix:/usr/var/run/openvswitch/db.sock
> root     23031 22899  0 18:13 pts/6    00:00:00 grep --color=auto ovs
> 
> Could someone give me some advice?

ovs-vsctl communicates with ovsdb-server, and ovs-ofctl communicates with ovs-vswitchd.  I'd make sure that ovs-vsctl is using the right path to ovsdb-server and that ovs-ofctl is using the right path to ovs-vswitchd.  I'd also turn on logging for both daemons and check the logs.

> [1]: https://github.com/openvswitch/ovs/blob/master/INSTALL.rst


It appears that you started the daemons differently than those instructions, so, once again, I'd check to make sure that everything is using correct paths.

--Justin