X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;ds=sidebyside;f=vswitchd%2Fvswitch.xml;h=48315fa9c1a68e2231106b33b2ca2bebbd068a8a;hb=ebca7787e50327716e2c2ea4a7cc2656fd4e9fd5;hp=4cc29da03b7f975bc86c6cf27f0feadacf6e3a17;hpb=e16a28b5854823e2d67099d49f7690235162b555;p=openvswitch
diff --git a/vswitchd/vswitch.xml b/vswitchd/vswitch.xml
index 4cc29da0..48315fa9 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) bonding, which - assigns flows to slaves based on source MAC address and output VLAN, - with periodic rebalancing as traffic patterns change. This form of - bonding does not require 802.3ad or other special support from the - upstream switch to which the slave devices are connected.
+A port that has more than one interface is a ``bonded port.'' Bonding + 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 modes require the upstream switch to support 802.3ad with
+ successful LACP negotiation. If LACP negotiation fails then
+ balance-slb
style flow hashing is used as a fallback:
+
balance-tcp
stable
Attempts to always assign a given flow to the same slave
+ consistently. In an effort to maintain stability, no load
+ balancing is done. Uses a similar hashing strategy to
+ balance-tcp
, falling back to balance-slb
+ style hashing when LACP negotiations are unsuccessful.
Slave selection decisions are made based on LACP port ID when LACP + negotiations are successful, falling back to openflow port number + when unsuccessful. Thus, decisions are consistent across all + ovs-vswitchd instances with equivalent port IDs.
+These columns apply only to bonded ports. Their values are otherwise ignored.
+The type of bonding used for a bonded port. Defaults to
+ balance-slb
if unset.
+
For a bonded port, the number of milliseconds for which carrier must stay up on an interface before the interface is considered to be up. @@ -538,6 +574,18 @@ name of the port. Use only for compatibility with legacy software that requires this.
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.
xx:xx:xx:xx:xx:xx
.bond-rebalance-interval
bond-detect-mode
carrier
and miimon
. Defaults
+ to carrier
which uses each interface's carrier to detect
+ failures. When set to miimon
, will check for failures
+ by polling each interface's MII. bond-miimon-interval
miimon
to detect failures. bond-hash-basis
lacp-system-id
lacp-system-priority
lacp-time
The LACP timing which should be used on this
+ . Possible values are fast
,
+ slow
and a positive number of milliseconds. By
+ default slow
is used. When configured to be
+ fast
LACP heartbeats are requested at a rate of once
+ per second causing connectivity problems to be detected more
+ quickly. In slow
mode, heartbeats are requested at
+ a rate of once every 30 seconds.
Users may manually set a heartbeat transmission rate to increase
+ the fault detection speed further. When manually set, OVS
+ expects the partner switch to be configured with the same
+ transmission rate. Manually setting lacp-time
to
+ something other than fast
or slow
is
+ not supported by the LACP specification.
lacp-strict
true
, configures this to
+ require successful LACP negotiations to enable any slaves.
+ Defaults to false
which safely allows LACP to be used
+ with switches that do not support the protocol.lacp-force-aggregatable
true
, forces all slaves managed by this
+ to advertise themselves as aggregatable even if
+ they normally wouldn't. Defaults to false
.ipsec_gre
gre
) must be uniquely identified by the
- combination of remote_ip
and
- local_ip
. Note that if two ports are defined
- that are the same except one has an optional identifier and
- the other does not, the more specific one is matched first.
- The following options may be specified in the
- column:
+ gre
) must be uniquely identified by the
+ combination of remote_ip
and
+ local_ip
. Note that if two ports are defined
+ that are the same except one has an optional identifier and
+ the other does not, the more specific one is matched first.
+ An authentication method of peer_cert
or
+ psk
must be defined. The following options may
+ be specified in the column:
remote_ip
ipsec_psk
peer_cert
certificate
option.certificate
private_key
certificate
. If certificate
+ contains the private key, this option may be omitted.psk
in_key
remote_ip
and
local_ip
. If two ports are defined that are the same
except one includes local_ip
and the other does not,
@@ -935,6 +1055,8 @@
null
+ Status information about interfaces attached to bridges, updated every + 5 seconds. Not all interfaces have all of these properties; virtual + interfaces don't have a link speed, for example. Non-applicable + columns will have empty values. +
++ The administrative state of the physical network link. +
++ 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. +
++ The negotiated speed of the physical network link. + Valid values are positive integers greater than 0. +
++ The duplex mode of the physical network link. +
++ The MTU (maximum transmission unit); i.e. the largest + amount of data that can fit into a single Ethernet frame. + The standard Ethernet MTU is 1500 bytes. Some physical media + and many kinds of virtual interfaces can be configured with + higher MTUs. +
++ This column will be empty for an interface that does not + have an MTU as, for example, some kinds of tunnels do not. +
+
Key-value pairs that report port status. Supported status
- values are type
-dependent.
+ values are type
-dependent; some interfaces may not have
+ a valid driver_name
, for example.
The only currently defined key-value pair is:
+The currently defined key-value pairs are:
+driver_name
driver_version
firmware_version
source_ip
gre
or capwap
. Not
- supported by all implementations.gre
or capwap
.
+ tunnel_egress_iface
remote_ip
.
+ This could be an internal interface such as a bridge port.lacp-port-id
lacp-port-priority
lacp-aggregation-key
linux-htb
are:
min-rate
max-rate
linux-hfsc
are:
min-rate
max-rate
+ To be selected for mirroring, a given packet must enter or leave the + bridge through a selected port and it must also be in one of the + selected VLANs. +
++ These columns are mutually exclusive. Exactly one of them must be + nonempty. +
+Output port for selected packets, if nonempty. Mutually exclusive - with .
+Output port for selected packets, if nonempty.
Specifying a port for mirror output reserves that port exclusively for mirroring. No frames other than those selected for mirroring will be forwarded to the port, and any frames received on the port @@ -1407,8 +1625,7 @@
Output VLAN for selected packets, if nonempty. Mutually exclusive - with .
+Output VLAN for selected packets, if nonempty.
The frames will be sent out all ports that trunk , as well as any ports with implicit VLAN . When a mirrored frame is sent out a @@ -1539,23 +1756,6 @@
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 @@ -1615,10 +1815,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 @@ -1731,6 +1905,60 @@ unique. No common key-value pairs are currently defined.
true
if currently connected to this controller,
+ false
otherwise.
+ The level of authority this controller has on the associated + bridge. Possible values are:
+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
Key-value pairs that report controller status.
+last_error
strerror(errno)
. This key
+ will exist only if an error has occurred.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