X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=vswitchd%2Fvswitch.xml;h=cee28a54291a43c6f00d1b24ed0bc2f47bee1914;hb=refs%2Fheads%2Fbranch-1.5;hp=bcb6b6fd5e5a821accf4f9e2c027c9f4ae6e9dee;hpb=b37e6334fd80a6460aabc95f05eb8ab68e5a82ed;p=sliver-openvswitch.git
diff --git a/vswitchd/vswitch.xml b/vswitchd/vswitch.xml
index bcb6b6fd5..cee28a542 100644
--- a/vswitchd/vswitch.xml
+++ b/vswitchd/vswitch.xml
@@ -372,8 +372,20 @@
+ OpenFlow controller set. If unset, then no OpenFlow controllers
+ will be used.
+
+ If there are primary controllers, removing all of them clears the
+ flow table. If there are no primary controllers, adding one also
+ clears the flow table. Other changes to the set of controllers, such
+ as adding or removing a service controller, adding another primary
+ controller to supplement an existing primary controller, or removing
+ only one of two primary controllers, have no effect on the flow
+ table.
+ When more than one controller is configured,
is considered only when none of the
configured controllers can be contacted.
+ Changing when no primary controllers are
+ configured clears the flow table.
+
+ The maximum number of seconds to retain a MAC learning entry for
+ which no packets have been seen. The default is currently 300
+ seconds (5 minutes). The value, if specified, is forced into a
+ reasonable range, currently 15 to 3600 seconds.
+
+ A short MAC aging time allows a network to more quickly detect that a
+ host is no longer connected to a switch port. However, it also makes
+ it more likely that packets will be flooded unnecessarily, when they
+ are addressed to a connected host that rarely transmits packets. To
+ reduce the incidence of unnecessary flooding, use a MAC aging time
+ longer than the maximum interval at which a host will ordinarily
+ transmit packets.
+ true
to enable.
@@ -623,14 +658,14 @@
An access port carries packets on exactly one VLAN specified in the - column. Packets ingressing and egressing on an - access port have no 802.1Q header. + column. Packets egressing on an access port + have no 802.1Q header.
- Any packet with an 802.1Q header that ingresses on an access port - is dropped, regardless of whether the VLAN ID in the header is the - access port's VLAN ID. + Any packet with an 802.1Q header with a nonzero VLAN ID that + ingresses on an access port is dropped, regardless of whether the + VLAN ID in the header is the access port's VLAN ID.
@@ -691,6 +726,34 @@ VLAN.
+ ++ An 802.1Q header contains two important pieces of information: a VLAN + ID and a priority. A frame with a zero VLAN ID, called a + ``priority-tagged'' frame, is supposed to be treated the same way as + a frame without an 802.1Q header at all (except for the priority). +
+ +
+ However, some network elements ignore any frame that has 802.1Q
+ header at all, even when the VLAN ID is zero. Therefore, by default
+ Open vSwitch does not output priority-tagged frames, instead omitting
+ the 802.1Q header entirely if the VLAN ID is zero. Set this key to
+ true
to enable priority-tagged frames on a port.
+
+ Regardless of this setting, Open vSwitch omits the 802.1Q header on + output if both the VLAN ID and priority would be zero. +
+ ++ All frames output to native-tagged ports have a nonzero VLAN ID, so + this setting is not meaningful on native-tagged ports. +
+active-backup
.
+
An important part of link bonding is detecting that links are down so
@@ -854,13 +926,6 @@
when this mode is in use. The default if not specified is
false
.
-
-
+ Key-value pairs that report port statistics. +
+Common
Columns
at the beginning of this document.
@@ -1642,6 +1727,13 @@
OpenFlow action. This setting is ignored when CFM is not in extended
mode. Defaults to up
.
+
+ + The ``VLAN splinters'' feature increases Open vSwitch compatibility + with buggy network drivers in old versions of Linux that do not + properly support VLANs when VLAN devices are not used, at some cost + in memory and performance. +
+ ++ When VLAN splinters are enabled on a particular interface, Open vSwitch + creates a VLAN device for each in-use VLAN. For sending traffic tagged + with a VLAN on the interface, it substitutes the VLAN device. Traffic + received on the VLAN device is treated as if it had been received on + the interface on the particular VLAN. +
+ ++ VLAN splinters consider a VLAN to be in use if: +
+ ++ The same set of in-use VLANs applies to every interface on which VLAN + splinters are enabled. That is, the set is not chosen separately for + each interface but selected once as the union of all in-use VLANs based + on the rules above. +
+ ++ It does not make sense to enable VLAN splinters on an interface for an + access port, or on an interface that is not a physical port. +
+ ++ VLAN splinters are deprecated. When broken device drivers are no + longer in widespread use, we will delete this feature. +
+ +
+ Set to true
to enable VLAN splinters on this interface.
+ Defaults to false
.
+
+ VLAN splinters increase kernel and userspace memory overhead, so do + not use them unless they are needed. +
+ ++ VLAN splinters do not support 802.1p priority tags. Received + priorities will appear to be 0, regardless of their actual values, + and priorities on transmitted packets will also be cleared to 0. +
+Common
Columns
at the beginning of this document.
@@ -1756,8 +1926,17 @@
supported range of queue numbers depend on . The
queue numbers are the same as the queue_id
used in
OpenFlow in struct ofp_action_enqueue
and other
- structures. Queue 0 is used by OpenFlow output actions that do not
- specify a specific queue.
+ structures.
+
+ + Queue 0 is the ``default queue.'' It is used by OpenFlow output + actions when no specific queue has been set. Ordinarily should include a configuration for queue 0. When no + configuration for queue 0 is present, a default configuration is used. + (Before version 1.6, Open vSwitch would leave queue 0 unconfigured in + this case. With some queuing disciplines, this dropped all packets + destined for the default queue.) +
These key-value pairs are defined for
- These key-value pairs are defined for of
- These key-value pairs are defined for of linux-htb
.
+
+ linux-htb
may use queue_id
s less than 61440.
+ It has the following key-value pairs defined.
linux-hfsc
.
+
+ linux-hfsc
may use queue_id
s less than 61440.
+ It has the following key-value pairs defined.