Revision history [back]

Hi,

ovsdb is probably not configured to listen to that pipe. In most cases, ovsdb listens to :6640. You may set the following in your neutron-ovs-agent.conf:

[ovs] ovsdb_connection = "tcp:127.0.0.1:6640"

Ensure that ovsdb listens to that port by issuing the following: ovs-appctl -t ovsdb-server ovsdb-server/add-remote ptcp:6640:127.0.0.1

Alternatively, you may use the following if you want to stick to unix sockets (ovs is using named pipes on Windows behind the scenes as Unix sockets are relatively new on Windows): ovs-appctl -t ovsdb-server ovsdb-server/add-remote punix:C:\ProgramData\openvswitch\db.sock

Regards, Lucian

Hi,

ovsdb is probably not configured to listen to that pipe. In most cases, ovsdb listens to :6640. You may set the following in your neutron-ovs-agent.conf:

[ovs] ovsdb_connection = "tcp:127.0.0.1:6640""tcp:127.0.0.1:6640"

Ensure that ovsdb listens to that port by issuing the ~~following:~~ following:

ovs-appctl -t ovsdb-server ovsdb-server/add-remote ptcp:6640:127.0.0.1ptcp:6640:127.0.0.1

Alternatively, you may use the following if you want to stick to unix sockets (ovs is using named pipes on Windows behind the scenes as Unix sockets are relatively new on ~~Windows):~~ Windows):

ovs-appctl -t ovsdb-server ovsdb-server/add-remote punix:C:\ProgramData\openvswitch\db.sockpunix:C:\ProgramData\openvswitch\db.sock

Regards, Lucian