X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=vswitchd%2Fvswitch.xml;h=7d9bb0b1dfd1ed0f7a7690a0f387b8ed5ddc1345;hb=109b8459218973f7fba72fc606bcdbbb306592de;hp=b8aa813c954b4daeab0c749d5982b79a0031f9d2;hpb=6c2d2a9f8318fea11250a7624144cb06436f91a4;p=openvswitch diff --git a/vswitchd/vswitch.xml b/vswitchd/vswitch.xml index b8aa813c..7d9bb0b1 100644 --- a/vswitchd/vswitch.xml +++ b/vswitchd/vswitch.xml @@ -461,6 +461,16 @@
forward-bpdu
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.
@@ -670,9 +680,6 @@
Key-value pairs for configuring rarely used port features. The
currently defined key-value pairs are:
hwaddr
xx:xx:xx:xx:xx:xx
.bond-rebalance-interval
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