X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;ds=sidebyside;f=vswitchd%2Fvswitch.xml;h=b74c55c8c7bea197cca76b13d36d82980befb687;hb=033419e81cac78924359f375e4ca558380f094c4;hp=a02ea53435982dc9d48a014c10b9b4f4d822d3dd;hpb=0b3e7a8b717b8c50c24244f7054079ede61742f2;p=openvswitch
diff --git a/vswitchd/vswitch.xml b/vswitchd/vswitch.xml
index a02ea534..b74c55c8 100644
--- a/vswitchd/vswitch.xml
+++ b/vswitchd/vswitch.xml
@@ -1,15 +1,20 @@
A database with this schema holds the configuration for one Open
- vSwitch daemon. The root of the configuration for the daemon is
- the table, which must have exactly one
+
+ A database with this schema holds the configuration for one Open
+ vSwitch daemon. The top-level configuration for the daemon is the
+ table, which must have exactly one
record. Records in other tables are significant only when they
- can be reached directly or indirectly from the
- table.
A port that has more than one interface is a ``bonded port.'' Bonding - allows for load balancing and fail-over. Open vSwitch supports - ``source load balancing'' (SLB) and "active backup" bonding. SLB - bonding assigns flows to slaves based on source MAC address and output - VLAN, with periodic rebalancing as traffic patterns change. Active - backup bonding assigns all flows to one slave, failing over to a backup - slave when the active slave is disabled. Neither form of bonding - require 802.3ad or other special support from the upstream switch to - which the slave devices are connected.
+ allows for load balancing and fail-over. Some kinds of bonding will + work with any kind of upstream switch: + +balance-slb
active-backup
+ The following mode requires the upstream switch to support 802.3ad with
+ successful LACP negotiation. If LACP negotiation fails then
+ balance-slb
mode is used as a fallback:
+
balance-tcp
These columns apply only to bonded ports. Their values are otherwise ignored.
The type of bonding used for a bonded port. Currently supported
- values are balance-slb
and active-backup
.
- Defaults to SLB if unset.
The type of bonding used for a bonded port. Defaults to
+ balance-slb
if unset.
+
Configures LACP on this port. LACP allows directly connected
+ switches to negotiate which links may be bonded. LACP may be enabled
+ on non-bonded ports for the benefit of any switches they may be
+ connected to. 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.
miimon
to detect failures. lacp-system-priority
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.remote_ip
and
local_ip
. If two ports are defined that are the same
except one includes local_ip
and the other does not,
@@ -999,8 +1036,10 @@
- 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.
+ This column will be empty for an interface that does not + have an MTU as, for example, some kinds of tunnels do not. +
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 @@ -1728,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.
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 @@ -1857,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
VOID
(connection is disabled),
BACKOFF
(attempting to reconnect at an increasing
- period), CONNECT_IN_PROGRESS
(attempting to connect),
+ period), CONNECTING
(attempting to connect),
ACTIVE
(connected, remote host responsive), and
- IDLE
(remote host unresponsive, disconnecting). These
+ IDLE
(remote host idle, sending keep-alive). These
values may change in the future. They are provided only for human
consumption.time_in_state
state
key changed.sec_since_connect
sec_since_disconnect