X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=vswitchd%2Fvswitch.xml;h=2af04bd1d21daf8f2a57b8c2dee34265c6d08fef;hb=485e2766d816a18e1a51ddf5e12e55f38aeedf89;hp=06edb767539ebb50f4f409b3a951f98bb8962eb2;hpb=8bddb894d90d84b642b9fd4fa83abf2af0074fba;p=sliver-openvswitch.git
diff --git a/vswitchd/vswitch.xml b/vswitchd/vswitch.xml
index 06edb7675..2af04bd1d 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.
@@ -432,6 +439,12 @@ value. May not be all-zero. +switch3 in room 3120
.
+ true
, disable in-band control on the bridge
@@ -446,6 +459,12 @@
QoS configured, or if the port does not have a queue with the specified
ID, the default queue is used instead.
OpenFlow10
will be used if this column is empty.
+ true
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
+ The maximum number of MAC addresses to learn. The default is + currently 2048. The value, if specified, is forced into a reasonable + range, currently 10 to 1,000,000. +
+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
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
- balance-tcp
, always taking into account L3 and L4
- fields even if LACP negotiations are unsuccessful.
Slave selection decisions are made based on if set. Otherwise,
- OpenFlow port number is used. Decisions are consistent across all
- ovs-vswitchd
instances with equivalent
-
- values.
These columns apply only to bonded ports. Their values are
@@ -843,7 +902,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
The LACP timing which should be used on this .
- Possible values are
- 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 0
to enable the interface immediately.
0
to disable the interface immediately.
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.
- 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.
Ethernet address to set for this interface. If unset then the default MAC address is used:
@@ -1123,6 +1167,20 @@ port number for the OpenFlow ``local port''). If the interface cannot be added then Open vSwitch sets this column to -1. +When is not set, Open vSwitch picks + an appropriate value for this column and then tries to keep the value + constant across restarts.
+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.
gre
ipsec_gre
capwap
gre64
ipsec_gre64
vxlan
+ An Ethernet tunnel over the experimental, UDP-based VXLAN
+ protocol described at
+ http://tools.ietf.org/html/draft-mahalingam-dutt-dcops-vxlan-03
.
+ VXLAN is currently supported only with the Linux kernel datapath
+ with kernel version 2.6.26 or later.
+
+ As an experimental protocol, VXLAN has no officially assigned UDP + port. Open vSwitch currently uses UDP destination port 8472. + The source port used for VXLAN traffic varies on a per-flow basis + and is in the ephemeral port range. +
+lisp
null
These options apply to interfaces with of
- gre
, ipsec_gre
, and capwap
.
+ gre
, ipsec_gre
, gre64
,
+ ipsec_gre64
, vxlan
, and lisp
.
@@ -1203,22 +1291,12 @@
- 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. -
+ Required. The tunnel endpoint. Only unicast endpoints are supported.flow
. The tunnel accepts packets with any
@@ -1257,8 +1336,9 @@
key="out_key"/> at all.
flow
. Packets sent through the tunnel will
@@ -1277,7 +1357,8 @@
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.
@@ -1290,48 +1371,13 @@
system default, typically 64). Default is the system default TTL.
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.
- false
to disable.
+ Optional. If enabled, the Don't Fragment bit will be set on tunnel
+ outer headers to allow path MTU discovery. Default is enabled; set
+ to false
to disable.
- Only 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.
-
Only
+ When operating over tunnels which have no When in extended mode, indicates the operational state of the
+ remote endpoint as either
+ 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.gre
and ipsec_gre
interfaces support
@@ -1491,15 +1537,15 @@
gre
or capwap
.
+ gre
.
in_key
, or an
+ in_key
of flow
. CFM will only accept CCMs
+ with a tunnel key of zero.
+ ovs-appctl
command.
up
or down
. See
+ .
+ random
in which
+ case each CCM will be tagged with a different randomly generated VLAN.
stable
bond mode to make slave
- selection decisions. Allocating values consistently across interfaces
- participating in a bond will guarantee consistent slave selection
- decisions across ovs-vswitchd
instances when using
- stable
bonding mode.
-
+ 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.
+ There is one exception: some hypervisors support ``migration'' from a
+ given hypervisor to itself (most often for test purposes). During
+ such a ``migration,'' two instances of a single might both be briefly marked
+ active
on a single hypervisor.
+
+ 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. +
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 .)
@@ -2243,36 +2373,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,
@@ -2649,11 +2755,33 @@
+
+ Additional configuration for a connection between the controller
+ and the Open vSwitch.
+
+ Additional configuration for a connection between the manager
+ and the Open vSwitch Database.
+ Common
Columns
at the beginning of this document.
Common
Columns
at the beginning of this document.