X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=vswitchd%2Fvswitch.xml;h=7d02e50305cd33d28119554ce786b6fb1c4b382a;hb=2bcf7df6f7a87d8940deff6fbbc359b0a310a74a;hp=560d22240b3600971a25ab8346d50a2892771d88;hpb=86dc65011b820698dab5f1e4cb5083d20f14aad4;p=openvswitch diff --git a/vswitchd/vswitch.xml b/vswitchd/vswitch.xml index 560d2224..7d02e503 100644 --- a/vswitchd/vswitch.xml +++ b/vswitchd/vswitch.xml @@ -104,14 +104,16 @@ omitted.
-true
to enable populating the
column or to false
to explicitly disable it.
Number of CPU processors, threads, or cores currently online and
available to the operating system on which Open vSwitch is running,
@@ -370,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.
+
A number of flows as a nonnegative integer. This sets number of
flows at which eviction from the kernel flow table will be triggered.
@@ -471,13 +541,45 @@
+ 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.
+ true
, disable in-band control on the bridge
regardless of controller and manager settings.
forwarding
, in seconds. By default, the
+ forwarding delay is 15 seconds.
+ true
to enable.
+ true
to enable.
+ stp-system-id
and stp-priority
keys
+ of the other_config
section earlier.
+
@@ -537,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.
@@ -605,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 @@ -672,15 +810,16 @@ detects link failure.
-carrier
and miimon
. Defaults to
+ carrier
which uses each interface's carrier to detect
failures. When set to miimon
, will check for failures
by polling each interface's MII.
miimon
.
@@ -732,10 +871,11 @@
nonzero MAC address.
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.
@@ -922,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. +
true
to
enable.
df_inherit
option is not set, or if
the encapsulated packet is not IP. Default is enabled; set to
false
to disable.
gre
interfaces support these options.
-
Optional. Compute GRE checksums on outgoing packets. Default is
disabled, set to true
to enable. Checksums present on
@@ -1169,6 +1409,13 @@
+ The number of times Open vSwitch has observed the + of this change. +
+The negotiated speed of the physical network link. @@ -1235,10 +1482,10 @@ internal interface such as a bridge port.
down
and
- up
.
+ true
, the CFM module operates in extended mode. This
causes it to use a nonstandard destination address to avoid conflicting
with compliant implementations which may be running concurrently on the
@@ -1447,7 +1696,8 @@
compatibility with 802.1ag compliant implementations. Defaults to
false
.
down
, the CFM module marks all CCMs it generates as
operationally down without triggering a fault. This allows remote
maintenance points to choose not to forward traffic to the
@@ -1457,11 +1707,19 @@
OpenFlow action. This setting is ignored when CFM is not in extended
mode. Defaults to up
.
stable
bond mode to make slave
+ stable
bond mode to make slave
selection decisions. Allocating values consistently across interfaces
participating in a bond will guarantee consistent slave selection
@@ -1469,25 +1727,25 @@
stable
bonding mode.
+ 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.
@@ -1580,7 +1910,7 @@
the following key-value pair:
-
These key-value pairs are defined for of min-rate
.
linux-htb
.
- linux-htb
implementation require a minimum burst size, so
a too-small burst
will be silently ignored.
priority
will receive all the excess
- bandwidth that it can use before a queue with a larger value receives
- any. Specific priority values are unimportant; only relative ordering
- matters.
+ priority
will receive all the
+ excess bandwidth that it can use before a queue with a larger value
+ receives any. Specific priority values are unimportant; only relative
+ ordering matters. Defaults to 0 if unspecified.
linux-hfsc
.
-