X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=vswitchd%2Fvswitch.xml;h=602e68713db4e052646122d3aad71020d5bdf93f;hb=05a9d485c061495d0ba83bff7e26d6eb077688aa;hp=7739793cfb13709a1272296c5a39d4dd6669e115;hpb=c473936b9af693ad88907e739013f34d9c70860d;p=openvswitch
diff --git a/vswitchd/vswitch.xml b/vswitchd/vswitch.xml
index 7739793c..602e6871 100644
--- a/vswitchd/vswitch.xml
+++ b/vswitchd/vswitch.xml
@@ -233,8 +233,6 @@
1.1.0
.
- If Open vSwitch was configured with a build number, then it is
- also included, e.g. 1.1.0+build6579
.
If this value is unset, the default is implementation-specific.
+
+ The default is standalone
if the value is unset, but
+ future versions of Open vSwitch may change the default.
+
+ The standalone
mode can create forwarding loops on a
+ bridge that has more than one uplink port unless STP is enabled. To
+ avoid loops on such a bridge, configure secure
mode or
+ enable STP (see ).
+
When more than one controller is configured, is considered only when none of the configured controllers can be contacted.
@@ -549,6 +556,46 @@ and if Open vSwitch node does not run STP, then this option should be enabled. Default is disabled, set totrue
to enable.
+
+ The following destination MAC addresss will not be forwarded when this
+ option is enabled.
+ 01:80:c2:00:00:00
01:80:c2:00:00:01
01:80:c2:00:00:0x
00:e0:2b:00:00:00
00:e0:2b:00:00:04
and 00:e0:2b:00:00:06
+ 01:00:0c:cc:cc:cc
01:00:0c:cc:cc:cd
01:00:0c:cd:cd:cd
01:00:0c:00:00:00
01:00:0c:cc:cc:cx
A port that has more than one interface is a ``bonded port.'' Bonding - allows for load balancing and fail-over. Some kinds of bonding will - work with any kind of upstream switch:
+ allows for load balancing and fail-over. + ++ The following types of bonding will work with any kind of upstream + switch. On the upstream switch, do not configure the interfaces as a + bond: +
balance-slb
active-backup
stable
Deprecated and slated for removal in February 2013.
Attempts to always assign a given flow to the same slave
consistently. In an effort to maintain stability, no load
balancing is done. Uses a similar hashing strategy to
@@ -843,7 +897,7 @@
- The number of milliseconds for which carrier must stay up on an
+ The number of milliseconds for which the link must stay up on an
interface before the interface is considered to be up. Specify
0
to enable the interface immediately.
0
to disable the interface immediately.
The LACP timing which should be used on this .
- Possible values are fast
, slow
and a
- positive number of milliseconds. By default slow
is
- used. When configured to be fast
LACP heartbeats are
- requested at a rate of once per second causing connectivity
- problems to be detected more quickly. In slow
mode,
- heartbeats are requested at a rate of once every 30 seconds.
-
- Users may manually set a heartbeat transmission rate to increase
- the fault detection speed further. When manually set, OVS expects
- the partner switch to be configured with the same transmission
- rate. Manually setting lacp-time
to something other
- than fast
or slow
is not supported by the
- LACP specification.
+ By default slow
is used. When configured to be
+ fast
LACP heartbeats are requested at a rate of once
+ per second causing connectivity problems to be detected more
+ quickly. In slow
mode, heartbeats are requested at a
+ rate of once every 30 seconds.
false
.
-
These settings control behavior when a bond is in
- balance-slb
mode, regardless of whether the bond was
- intentionally configured in SLB mode or it fell back to SLB mode
- because LACP negotiation failed.
+ balance-slb
or balance-tcp
mode.
Requested OpenFlow port number for this interface. The port + number must be between 1 and 65279, inclusive. Some datapaths + cannot satisfy all requests for particular port numbers. When + this column is empty or the request cannot be fulfilled, the + system will choose a free port. The + column reports the assigned OpenFlow port number.
+The port number must be requested in the same transaction + that creates the port.
+gre64
ipsec_gre64
capwap
patch
null
These options apply to interfaces with of
- gre
, ipsec_gre
, and capwap
.
+ gre
, ipsec_gre
, gre64
,
+ ipsec_gre64
, and capwap
.
@@ -1277,7 +1343,8 @@
Only inherit
, in which case
+ packet. ToS is interpreted as DSCP and ECN bits, ECN part must be
+ zero. It may also be the word inherit
, in which case
the ToS will be copied from the inner packet if it is IPv4 or IPv6
(otherwise it will be 0). The ECN fields are always inherited.
Default is 0.
@@ -1313,23 +1380,14 @@
of the tunnel headers. Note that this option causes behavior that is
typically reserved for routers and therefore is not entirely in
compliance with the IEEE 802.1D specification for bridges. Default is
- enabled; set to false
to disable.
+ disabled; set to true
to enable. This feature is
+ deprecated and will be removed soon.
gre
interfaces support these options.
iptables
) and it may be useful to disable it if these
- features are required or as a debugging measure. Default is enabled,
- set to false
to disable.
-
+ When operating over tunnels which have no in_key
, or an
+ in_key
of flow
. CFM will only accept CCMs
+ with a tunnel key of zero.
+
ovs-appctl
command.
When in extended mode, indicates the operational state of the
+ remote endpoint as either up
or down
. See
+ .
+
+ Indicates the health of the interface as a percentage of CCM frames + received over 21 s. + The health of an interface is undefined if it is communicating with + more than one . It reduces if + healthy heartbeats are not received at the expected rate, and + gradually improves as healthy heartbeats are received at the desired + rate. Every 21 s, the + health of the interface is refreshed. +
++ As mentioned above, the faults can be triggered for several reasons. + The link health will deteriorate even if heartbeats are received but + they are reported to be unhealthy. An unhealthy heartbeat in this + context is a heartbeat for which either some fault is set or is out + of sequence. The interface health can be 100 only on receiving + healthy heartbeats at the desired rate. +
++ The interval, in milliseconds, between transmissions of CFM + heartbeats. Three missed heartbeat receptions indicate a + connectivity fault. +
+ ++ In standard operation only intervals of 3, 10, 100, 1,000, 10,000, + 60,000, or 600,000 ms are supported. Other values will be rounded + down to the nearest value on the list. Extended mode (see ) supports any interval up + to 65,535 ms. In either mode, the default is 1000 ms. +
+ +We do not recommend using intervals less than 100 ms.
random
in which
+ case each CCM will be tagged with a different randomly generated VLAN.
+ Hypervisors may sometimes have more than one interface associated
+ with a given , only one of
+ which is actually in use at a given time. For example, in some
+ circumstances XenServer has both a ``tap'' and a ``vif'' interface
+ for a single , but only
+ uses one of them at a time. A hypervisor that behaves this way must
+ mark the currently in use interface active
and the
+ others inactive
. A hypervisor that never has more than
+ one interface for a given
+ may mark that interface active
or omit entirely.
+
+ During VM migration, a given might transiently be marked active
on
+ two different hypervisors. That is, active
means that
+ this is the active
+ instance within a single hypervisor, not in a broader scope.
+
The eviction process only considers flows that have an idle timeout or a hard timeout. That is, eviction never deletes permanent flows. - (Permanent flows do count against . + (Permanent flows do count against .)
@@ -2254,36 +2390,12 @@ sent out an implicit VLAN port, the frame will not be tagged. This type of mirroring is sometimes called RSPAN.
- The following destination MAC addresses will not be mirrored to a - VLAN to avoid confusing switches that interpret the protocols that - they represent: + See the documentation for + in the + table for a list of destination MAC + addresses which will not be mirrored to a VLAN to avoid confusing + switches that interpret the protocols that they represent.
-01:80:c2:00:00:00
01:80:c2:00:00:01
01:80:c2:00:00:0x
01:00:0c:cc:cc:cc
01:00:0c:cc:cc:cd
01:00:0c:cd:cd:cd
01:00:0c:00:00:00
Please note: Mirroring to a VLAN can disrupt a network that contains unmanaged switches. Consider an unmanaged physical switch with two ports: port 1, connected to an end host, and port 2, @@ -2660,11 +2772,33 @@
+ Additional configuration for a connection between the controller + and the Open vSwitch. +
+ +Common
Columns
at the beginning of this document.
+ Additional configuration for a connection between the manager + and the Open vSwitch Database. +
+ +Common
Columns
at the beginning of this document.