X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=vswitchd%2Fvswitch.xml;h=fb41196369802a16a17a2a1141fa546da1f6745b;hb=b063d9f06e6bb005193a219bcb9f0a74dfdf7882;hp=608225647cf16e4fcc2140d3b8d0affb1366482e;hpb=0fa0fcdc5a3ab75b5e3846229ccb4aef96866ce7;p=openvswitch diff --git a/vswitchd/vswitch.xml b/vswitchd/vswitch.xml index 60822564..fb411963 100644 --- a/vswitchd/vswitch.xml +++ b/vswitchd/vswitch.xml @@ -463,13 +463,13 @@
forward-bpdu
true
to enable.
+ 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.
active
ports are allowed to initiate LACP
negotiations. passive
ports are allowed to participate
in LACP negotiations initiated by a remote switch, but not allowed to
- initiate such negotiations themselves. If unset Open vSwitch will
- choose a reasonable default.
+ initiate such negotiations themselves. Defaults to off
+ if unset.
@@ -1085,6 +1085,32 @@
(otherwise it will be the system default, typically 64).
Default is the system default TTL.
+ in_key
flow
. If
+ flow
is specified then any key will be accepted
+ and the key will be placed in the tun_id
field
+ for matching in the flow table. The ovs-ofctl manual page
+ contains additional information about matching fields in
+ OpenFlow flows. Default is no key.out_key
flow
. If
+ flow
is specified then the key may be set using
+ the set_tunnel
Nicira OpenFlow vendor extension (0
+ is used in the absence of an action). The ovs-ofctl manual
+ page contains additional information about the Nicira OpenFlow
+ vendor extensions. Default is no key.key
in_key
and
+ out_key
at the same time.df_inherit
+ According to the 802.1ag specification, each Maintenance Point should + be configured out-of-band with a list of Remote Maintenance Points it + should have connectivity to. Open vSwitch differs from the + specification in this area. It simply assumes the link is faulted if + no Remote Maintenance Points are reachable, and considers it not + faulted otherwise. +
++ Indicates a connectivity fault triggered by an inability to receive + heartbeats from any remote endpoint. When a fault is triggered on + s participating in bonds, they will be + disabled. +
++ Faults can be triggered for several reasons. Most importantly they + are triggered when no CCMs are received for a period of 3.5 times the + transmission interval. Faults are also triggered when any CCMs + indicate that a Remote Maintenance Point is not receiving CCMs but + able to send them. Finally, a fault is triggered if a CCM is + received which indicates unexpected configuration. Notably, this + case arises when a CCM is received which advertises the local MPID. +
cfm_extended
cfm_interval
configuration parameter by breaking
+ wire compatibility with 802.1ag compliant implementations.
+ Defaults to false.bond-stable-id
stable
bond mode to
make slave selection decisions. Allocating