X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;ds=sidebyside;f=vswitchd%2Fvswitch.xml;h=b74c55c8c7bea197cca76b13d36d82980befb687;hb=1c2e2d2fc87c9435b6fe33112b0ddaab59f507c5;hp=b084884cda8886c8d332875404ae5fb1b203d2e6;hpb=5eda645e36a9b5dd72c275b7e400dfefcba281d3;p=openvswitch diff --git a/vswitchd/vswitch.xml b/vswitchd/vswitch.xml index b084884c..b74c55c8 100644 --- a/vswitchd/vswitch.xml +++ b/vswitchd/vswitch.xml @@ -637,6 +637,13 @@ LACP negotiations, link status decisions are made by the system with the numerically lower priority. Must be a number between 1 and 65535. +
lacp-time
fast
and
+ slow
. By default slow
is used. When
+ configured to be fast
more frequent LACP heartbeats
+ will be requested causing connectivity problems to be detected more
+ quickly.- The observed state of the physical network link; - i.e. whether a carrier is detected by the interface. + The observed state of the physical network link. This is ordinarily + the link's carrier status. If the interface's is + a bond configured for miimon monitoring, it is instead the network + link's miimon status.
linux-htb
are:
min-rate
max-rate
linux-hfsc
are:
min-rate
max-rate
discover
Enables controller discovery.
-In controller discovery mode, Open vSwitch broadcasts a DHCP
- request with vendor class identifier OpenFlow
across
- all of the bridge's network devices. It will accept any valid
- DHCP reply that has the same vendor class identifier and includes
- a vendor-specific option with code 1 whose contents are a string
- specifying the location of the controller in the same format as
- .
The DHCP reply may also, optionally, include a vendor-specific
- option with code 2 whose contents are a string specifying the URI
- to the base of the OpenFlow PKI
- (e.g. http://192.168.0.1/openflow/pki
). This URI is
- used only for bootstrapping the OpenFlow PKI at initial switch
- setup; ovs-vswitchd
does not use it at all.
The following connection methods are currently supported for service @@ -1768,10 +1744,7 @@
If not specified, the default is implementation-specific. If
- is discover
, the connection mode
- is always treated as in-band
regardless of the actual
- setting.
If not specified, the default is implementation-specific.
@@ -1821,33 +1794,9 @@ -These values are considered only when
- is discover
.
^
. If not specified, the default
- is implementation-specific.
- /etc/resolv.conf
when the
- controller is discovered. If not specified, the default
- is implementation-specific. Open vSwitch will only modify
- /etc/resolv.conf
if the DHCP response that it receives
- specifies one or more DNS servers.
- These values are considered only in in-band control mode (see
- ) and only when
- is not discover
. (For controller discovery, the network
- configuration obtained via DHCP is used instead.)
When multiple controllers are configured on a single bridge, there should be only one set of unique values in these columns. If different @@ -1897,15 +1846,11 @@
other
master
other
, except that there may be at
most one master controller at a time. When a controller configures
itself as master
, any existing master is demoted to
the slave
role.slave
strerror(errno)
. This key
will exist only if an error has occurred.state
VOID
, BACKOFF
,
- CONNECTING
, ACTIVE
, and
- IDLE
.time_in_state
VOID
(connection is disabled),
+ BACKOFF
(attempting to reconnect at an increasing
+ period), CONNECTING
(attempting to connect),
+ ACTIVE
(connected, remote host responsive), and
+ IDLE
(remote host idle, sending keep-alive). These
+ values may change in the future. They are provided only for human
+ consumption.
+ sec_since_connect
sec_since_disconnect