Signed-off-by: Mauricio Vasquez B
---
FAQ.rst | 106 +-
INSTALL.DPDK.rst | 74 +--
INSTALL.Debian.rst| 10 ++---
INSTALL.Docker.rst| 38 +-
INSTALL.KVM.rst | 12 +++---
INSTALL.Windows.rst | 68
INSTALL.XenServer.rst | 16
INSTALL.userspace.rst | 6 +--
8 files changed, 165 insertions(+), 165 deletions(-)
diff --git a/FAQ.rst b/FAQ.rst
index 4ee4c2b..d250c28 100644
--- a/FAQ.rst
+++ b/FAQ.rst
@@ -276,7 +276,7 @@ Q: What DPDK version does each Open vSwitch release work
with?
2.6.x16.07
=
-Q: I get an error like this when I configure Open vSwitch:::
+Q: I get an error like this when I configure Open vSwitch::
configure: error: Linux kernel in is version , but
version newer than is not supported (please refer to the
@@ -479,7 +479,7 @@ Q: How do I configure a DPDK port as an access port?
startup when other_config:dpdk-init is set to 'true'.
Secondly, when adding a DPDK port, unlike a system port, the type for the
-interface must be specified. For example:::
+interface must be specified. For example::
$ ovs-vsctl add-br br0
$ ovs-vsctl add-port br0 dpdk0 -- set Interface dpdk0 type=dpdk
@@ -546,7 +546,7 @@ Q: How do I configure mirroring of all traffic to a GRE
tunnel?
A: The following commands configure br0 with eth0 and tap0 as trunk ports.
All traffic coming in or going out on eth0 or tap0 is also mirrored to
gre0, a GRE tunnel to the remote host 192.168.1.10; any traffic arriving on
-gre0 is dropped:::
+gre0 is dropped::
$ ovs-vsctl add-br br0
$ ovs-vsctl add-port br0 eth0
@@ -557,7 +557,7 @@ Q: How do I configure mirroring of all traffic to a GRE
tunnel?
-- --id=@m create mirror name=m0 select-all=true output-port=@p \
-- set bridge br0 mirrors=@m
-To later disable mirroring and destroy the GRE tunnel:::
+To later disable mirroring and destroy the GRE tunnel::
$ ovs-vsctl clear bridge br0 mirrors
$ ovs-vsctl del-port br0 gre0
@@ -720,7 +720,7 @@ Configuration Problems
--
Q: I created a bridge and added my Ethernet port to it, using commands like
-these:::
+these::
ovs-vsctl add-br br0
ovs-vsctl add-port br0 eth0
@@ -735,7 +735,7 @@ eth0. Help!
You can restore functionality by moving the IP address to an Open vSwitch
"internal" device, such as the network device named after the bridge
itself. For example, assuming that eth0's IP address is 192.168.128.5, you
-could run the commands below to fix up the situation:::
+could run the commands below to fix up the situation::
$ ifconfig eth0 0.0.0.0
$ ifconfig br0 192.168.128.5
@@ -763,7 +763,7 @@ eth0. Help!
applies to all network devices except Open vSwitch "internal" devices.
Q: I created a bridge and added a couple of Ethernet ports to it, using
-commands like these:::
+commands like these::
$ ovs-vsctl add-br br0
$ ovs-vsctl add-port br0 eth0
@@ -785,7 +785,7 @@ very high.
- If you added eth0 and eth1 to get higher bandwidth or higher reliability
between OVS and your physical Ethernet switch, use a bond. The following
- commands create br0 and then add eth0 and eth1 as a bond:::
+ commands create br0 and then add eth0 and eth1 as a bond::
$ ovs-vsctl add-br br0
$ ovs-vsctl add-bond br0 bond0 eth0 eth1
@@ -814,7 +814,7 @@ very high.
prevent loops, turn on spanning tree protocol (STP). The following
commands create br0, enable STP, and add eth0 and eth1 to the bridge.
The order is important because you don't want have to have a loop in your
- network even transiently:::
+ network even transiently::
$ ovs-vsctl add-br br0
$ ovs-vsctl set bridge br0 stp_enable=true
@@ -898,7 +898,7 @@ Q: Open vSwitch does not seem to obey my packet filter
rules.
Q: It seems that Open vSwitch does nothing when I removed a port and then
immediately put it back. For example, consider that p1 is a port of
-``type=internal``:::
+``type=internal``::
$ ovs-vsctl del-port br0 p1 -- \
add-port br0 p1 -- \
@@ -917,7 +917,7 @@ immediately put it back. For example, consider that p1 is
a port of
corresponding interface, you need to separate operations into multiple
OVSDB transactions and ensure that at least the first one does not have
``--no-wait``. In the following example, the first ovs-vsctl will block
-until Open vSwitch reloads the new configuration and removes the port:::
+until Open vSwitch reloads the new configuration and removes the port::
$ ovs-vsctl del-port br0 p1
$ ovs-vsctl add-port br0 p1 -- \
@@ -934,7 +934,7 @@ long (minutes or h
