X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=vswitchd%2Fvswitch.xml;h=c12fd8fc31c2bc788a47bfb1d423cbc52b127e19;hb=a5ae88ff8a276e86c842ac102145432662bf711a;hp=21bcbc2e5d92f2276eb7d785868fc83db122dbb1;hpb=798e1352d09bc48d1eecb6ecf1b2c21d9b1ba2a5;p=sliver-openvswitch.git
diff --git a/vswitchd/vswitch.xml b/vswitchd/vswitch.xml
index 21bcbc2e5..c12fd8fc3 100644
--- a/vswitchd/vswitch.xml
+++ b/vswitchd/vswitch.xml
@@ -71,6 +71,109 @@
The Citrix XenServer universally unique identifier for the physical
host as displayed by
+ When
+ This option allows for improvement. When
+ Thus, with this option, the procedure for a hot-upgrade of
+
+ The
+ A number of flows as a nonnegative integer. This sets number of
+ flows at which eviction from the datapath flow table will be
+ triggered. If there are a large number of flows then increasing this
+ value to around the number of flows present can result in reduced CPU
+ usage and packet loss.
+
+ The default is 2500. Values below 100 will be rounded up to 100.
+
+ Specifies userspace behaviour for handling flow misses. This takes
+ precedence over flow-eviction-threshold.
+
+ xe host-list
.
+
+ ovs-vswitchd
starts up, it has an empty flow table
+ and therefore it handles all arriving packets in its default fashion
+ according to its configuration, by dropping them or sending them to
+ an OpenFlow controller or switching them as a standalone switch.
+ This behavior is ordinarily desirable. However, if
+ ovs-vswitchd
is restarting as part of a ``hot-upgrade,''
+ then this leads to a relatively long period during which packets are
+ mishandled.
+ ovs-vswitchd
+ starts with this value set as true
, it will neither
+ flush or expire previously set datapath flows nor will it send and
+ receive any packets to or from the datapath. When this value is
+ later set to false
, ovs-vswitchd
will
+ start receiving packets from the datapath and re-setup the flows.
+ ovs-vswitchd
becomes roughly the following:
+
+
+ ovs-vswitchd
.
+ true
.
+ ovs-vswitchd
.
+ ovs-ofctl
(or some other program, such as an
+ OpenFlow controller) to restore the OpenFlow flow table
+ to the desired state.
+ false
(or remove it entirely from the database).
+ ovs-ctl
's ``restart'' and ``force-reload-kmod''
+ functions use the above config option during hot upgrades.
+
+
+ auto
with-facets
without-facets
+ Specifies the number of threads for software datapaths to use for + handling new flows. The default is two less than the number of + online CPU cores (but at least 1). +
+
+ This configuration is per datapath. If you have more than one
+ software datapath (e.g. some system
bridges and some
+ netdev
bridges), then the total number of threads is
+ n-handler-threads
times the number of software
+ datapaths.
+
- A number of flows as a nonnegative integer. This sets number of - flows at which eviction from the kernel flow table will be triggered. - If there are a large number of flows then increasing this value to - around the number of flows present can result in reduced CPU usage - and packet loss. -
-- The default is 1000. Values below 100 will be rounded up to 100. -
-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. + Open vSwitch uses UDP destination port 4789. The source port used for + VXLAN traffic varies on a per-flow basis and is in the ephemeral port + range.
lisp
patch
Required. The remote tunnel endpoint, one of:
+ +192.168.0.123
.
+ Only unicast endpoints are supported.
+ flow
. The tunnel accepts packets from any
+ remote tunnel endpoint. To process only packets from a specific
+ remote tunnel endpoint, the flow entries may match on the
+ tun_src
field. When sending packets to a
+ remote_ip=flow
tunnel, the flow actions must
+ explicitly set the tun_dst
field to the IP address of
+ the desired remote tunnel endpoint, e.g. with a
+ set_field
action.
+
+ The remote tunnel endpoint for any packet received from a tunnel
+ is available in the tun_src
field for matching in the
+ flow table.
+
+ Optional. The tunnel destination IP that received packets must + match. Default is to match all addresses. If specified, may be one + of: +
+ +192.168.12.3
.
+ flow
. The tunnel accepts packets sent to any
+ of the local IP addresses of the system running OVS. To process
+ only packets sent to a specific IP address, the flow entries may
+ match on the tun_dst
field. When sending packets to a
+ local_ip=flow
tunnel, the flow actions may
+ explicitly set the tun_src
field to the desired IP
+ address, e.g. with a set_field
action. However, while
+ routing the tunneled packet out, the local system may override the
+ specified address with the local IP address configured for the
+ outgoing system interface.
+
+
+ This option is valid only for tunnels also configured with the
+ remote_ip=flow
option.
+
+ The tunnel destination IP address for any packet received from a
+ tunnel is available in the tun_dst
field for matching in
+ the flow table.
+
+ BFD, defined in RFC 5880 and RFC 5881, allows point to point + detection of connectivity failures by occasional transmission of + BFD control messages. It is implemented in Open vSwitch to serve + as a more popular and standards compliant alternative to CFM. +
+ ++ BFD operates by regularly transmitting BFD control messages at a + rate negotiated independently in each direction. Each endpoint + specifies the rate at which it expects to receive control messages, + and the rate at which it's willing to transmit them. Open vSwitch + uses a detection multiplier of three, meaning that an endpoint + which fails to receive BFD control messages for a period of three + times the expected reception rate, will signal a connectivity + fault. In the case of a unidirectional connectivity issue, the + system not receiving BFD control messages will signal the problem + to its peer in the messages it transmits. +
+ ++ The Open vSwitch implementation of BFD aims to comply faithfully + with the requirements put forth in RFC 5880. Currently, the only + known omission is ``Demand Mode'', which we hope to include in + future. Open vSwitch does not implement the optional + Authentication or ``Echo Mode'' features. +
+ +true
BFD is enabled on this
+ , otherwise it's disabled. Defaults to
+ false
.
+ 1000
.
+ 100
.
+ decay_min_rx
is used to set the min_rx
,
+ when there is no obvious incoming data traffic at the interface.
+ It cannot be set less than the min_rx
. The decay feature
+ is disabled by setting the decay_min_rx
to 0. And the
+ feature is reset everytime itself or min_rx
is
+ reconfigured.
+ forwarding_if_rx
is true the interface will be
+ considered capable of packet I/O as long as there is packet
+ received at interface. This is important in that when link becomes
+ temporarily conjested, consecutive BFD control packets can be lost.
+ And the forwarding_if_rx
can prevent link failover by
+ detecting non-control packets received at interface.
+ cpath_down
to
+ true
which may cause the remote BFD session not to
+ forward traffic to this . Defaults to
+ false
.
+ in_key
of zero. Defaults to
+ false
.
+ 00:23:20:00:00:01
is used.
+ UP
.
+ UP
, and the remote system isn't signaling a
+ problem such as concatenated path down.
+
802.1ag Connectivity Fault Management (CFM) allows a group of
@@ -1850,6 +2125,44 @@
compatibility with 802.1ag compliant implementations. Defaults to
+ When
+ Demand mode has a couple of caveats:
+ false
.
+
+ true
, and
+ is true, the CFM
+ module operates in demand mode. When in demand mode, traffic
+ received on the is used to indicate
+ liveness. CCMs are still transmitted and received, but if the
+ is receiving traffic, their absence does not
+ cause a connectivity fault.
+
+
+
down
, the CFM module marks all CCMs it generates as
@@ -2503,18 +2816,27 @@
ssl:ip
[:port
]The specified SSL port (default: 6633) on the host at - the given ip, which must be expressed as an IP address - (not a DNS name). The - column in the table must point to a - valid SSL configuration when this form is used.
+The specified SSL port on the host at the + given ip, which must be expressed as an IP + address (not a DNS name). The column in the + table must point to a valid SSL configuration when this form + is used.
+If port is not specified, it currently + defaults to 6633. In the future, the default will change to + 6653, which is the IANA-defined value.
SSL support is an optional feature that is not always built as part of Open vSwitch.
tcp:ip
[:port
]The specified TCP port on the host at the + given ip, which must be expressed as an IP + address (not a DNS name).
+If port is not specified, it currently + defaults to 6633. In the future, the default will change to + 6653, which is the IANA-defined value.
+The following connection methods are currently supported for service @@ -2523,26 +2845,29 @@
pssl:
[port][:ip
]- Listens for SSL connections on the specified TCP port - (default: 6633). If ip, which must be expressed as an - IP address (not a DNS name), is specified, then connections are - restricted to the specified local IP address. -
-- The column in the table must point to a valid SSL - configuration when this form is used. -
+Listens for SSL connections on the specified TCP + port. If ip, which must be expressed + as an IP address (not a DNS name), is specified, then + connections are restricted to the specified local IP + address. The + column in the table must point + to a valid SSL configuration when this form is used.
+If port is not specified, it currently + defaults to 6633. In the future, the default will change to + 6653, which is the IANA-defined value.
SSL support is an optional feature that is not always built as part of Open vSwitch.
ptcp:
[port][:ip
]Listens for connections on the specified TCP + port. If ip, which must be expressed + as an IP address (not a DNS name), is specified, then + connections are restricted to the specified local IP + address.
+If port is not specified, it currently + defaults to 6633. In the future, the default will change to + 6653, which is the IANA-defined value.
When multiple controllers are configured for a single bridge, the @@ -2814,39 +3139,55 @@
ssl:ip
[:port
]- The specified SSL port (default: 6632) on the host at - the given ip, which must be expressed as an IP address - (not a DNS name). The - column in the table must point to a - valid SSL configuration when this form is used. + The specified SSL port on the host at the given + ip, which must be expressed as an IP address + (not a DNS name). The column in the + table must point to a valid SSL configuration when this + form is used.
- SSL support is an optional feature that is not always built as - part of Open vSwitch. + If port is not specified, it currently defaults + to 6632. In the future, the default will change to 6640, + which is the IANA-defined value. +
++ SSL support is an optional feature that is not always + built as part of Open vSwitch.
tcp:ip
[:port
]+ The specified TCP port on the host at the given + ip, which must be expressed as an IP address + (not a DNS name). +
++ If port is not specified, it currently defaults + to 6632. In the future, the default will change to 6640, + which is the IANA-defined value. +
pssl:
[port][:ip
]- Listens for SSL connections on the specified TCP port - (default: 6632). Specify 0 for port to have the - kernel automatically choose an available port. If ip, - which must be expressed as an IP address (not a DNS name), is - specified, then connections are restricted to the specified local - IP address. -
-- The column in the port. Specify 0 for port to have + the kernel automatically choose an available port. If + ip, which must be expressed as an IP address + (not a DNS name), is specified, then connections are + restricted to the specified local IP address. The column in the table must point to a valid SSL configuration when this form is used.
++ If port is not specified, it currently defaults + to 6632. In the future, the default will change to 6640, + which is the IANA-defined value. +
SSL support is an optional feature that is not always built as part of Open vSwitch. @@ -2854,11 +3195,19 @@
ptcp:
[port][:ip
]+ Listens for connections on the specified TCP + port. Specify 0 for port to have + the kernel automatically choose an available port. If + ip, which must be expressed as an IP address + (not a DNS name), is specified, then connections are + restricted to the specified local IP address. +
++ If port is not specified, it currently defaults + to 6632. In the future, the default will change to 6640, + which is the IANA-defined value. +
When multiple managers are configured, the @@ -3129,8 +3478,8 @@