X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=vswitchd%2Fvswitch.xml;h=7d02e50305cd33d28119554ce786b6fb1c4b382a;hb=2bcf7df6f7a87d8940deff6fbbc359b0a310a74a;hp=611f47dba49cca63610c944a0748d3813d514e54;hpb=dae57238bc0ae2527b7d6f95482c5f17cba2e16e;p=openvswitch
diff --git a/vswitchd/vswitch.xml b/vswitchd/vswitch.xml
index 611f47db..7d02e503 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.
+
+ Status information about bridges.
+
+ The bridge-id (in hex) used in spanning tree advertisements.
+ Configuring the bridge-id is described in the
+
+ The designated root (in hex) for this spanning tree.
+
+ The path cost of reaching the designated bridge. A lower
+ number is better.
+ forwarding
, in seconds. By default, the
+ forwarding delay is 15 seconds.
+ true
to enable.
+ Option to allow forwarding of BPDU frames when NORMAL action is
+ invoked. Frames with reserved Ethernet addresses (e.g. STP
+ BPDU) will be forwarded when this option is enabled and the
+ switch is not providing that functionality. If STP is enabled
+ on the port, STP BPDUs will never be forwarded. If the Open
+ vSwitch bridge is used to connect different Ethernet networks,
+ and if Open vSwitch node does not run STP, then this option
+ should be enabled. Default is disabled, set to
+ true
to enable.
+ stp-system-id
and stp-priority
keys
+ of the other_config
section earlier.
+
@@ -543,14 +638,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.
@@ -611,6 +706,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
@@ -774,13 +906,6 @@
when this mode is in use. The default if not specified is
false
.
-
-
false
spanning tree is disabled on the
+ port.
+ + Status information about ports attached to bridges. +
+
+ The port-id (in hex) used in spanning tree advertisements for
+ this port. Configuring the port-id is described in the
+ stp-port-num
and stp-port-priority
+ keys of the other_config
section earlier.
+
+ STP state of the port. +
++ The amount of time (in seconds) port has been in the current + STP state. +
++ STP role of the port. +
++ Key-value pairs that report port statistics. +
+Common
Columns
at the beginning of this document.
@@ -933,7 +1151,7 @@
not support GRE. Only the tunneling component of the protocol is
implemented. UDP ports 58881 and 58882 are used as the source and
destination ports respectively. CAPWAP is currently supported only
- with the Linux kernel datapath with kernel version 2.6.25 or later.
+ with the Linux kernel datapath with kernel version 2.6.26 or later.
patch
+ Required. The tunnel endpoint. Unicast and multicast endpoints are + both supported. +
+ ++ When a multicast endpoint is specified, a routing table lookup occurs + only when the tunnel is created. Following a routing change, delete + and then re-create the tunnel to force a new routing table lookup. +
+ The number of times Open vSwitch has observed the + of this change. +
+
The negotiated speed of the physical network link.
@@ -1472,6 +1707,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. +
+Common
Columns
at the beginning of this document.
@@ -1618,6 +1932,15 @@
Service (QoS) features. May be referenced by column in table.
+ These key-value pairs are defined for -