ovn: Fix example for use of `ovs-ofctl` command

The charms configure briges with the OpenFlow 1.3 and newer
protocols which require a different syntax when issuing the
ovs-ofctl command.

Change-Id: I80d24db7fc52a885508029e89a3d7f51ce9b8b84
This commit is contained in:
Frode Nordahl 2020-05-13 12:07:59 +02:00
parent b4cec4df1b
commit c062135f1c
No known key found for this signature in database
GPG Key ID: 6A5D59A3BA48373F
1 changed files with 11 additions and 1 deletions

View File

@ -592,7 +592,7 @@ SSH into one of the chassis units to get access to various diagnostic tools:
sudo ovs-vsctl show
sudo ovs-ofctl dump-flows br-int
sudo ovs-ofctl -O OpenFlow13 dump-flows br-int
sudo ovs-appctl -t ovs-vswitchd \
ofproto/trace br-provider \
@ -611,6 +611,16 @@ SSH into one of the chassis units to get access to various diagnostic tools:
icmp4.type==8 && \
ip.ttl == 64'
.. note::
OVN makes use of OpenFlow 1.3 or newer and as such the charm configures
bridges to use these protocols. To be able to successfully use the
:command:`ovs-ofctl` command you must specify the OpenFlow version as shown
in the example above.
You may issue the :command:`ovs-vsctl list bridge` command to show what
protocols are enabled on the bridges.
.. LINKS
.. _Vault: app-vault
.. _Certificate Lifecycle Management: app-certificate-management