X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=vswitchd%2Fvswitch.xml;h=c80e8cdb5428fc840228f4b392c27d5c31d2a106;hb=88db6b82715ef5188d56ae2404614d6d6ff4db3f;hp=f78a579455e7fa161f7c97101a973fa5aaba98af;hpb=4c2fa71d662cde318940c4cd555aacd687538510;p=openvswitch
diff --git a/vswitchd/vswitch.xml b/vswitchd/vswitch.xml
index f78a5794..c80e8cdb 100644
--- a/vswitchd/vswitch.xml
+++ b/vswitchd/vswitch.xml
@@ -197,21 +197,21 @@
- These columns report the types and versions of the hardware and
- software running Open vSwitch. We recommend in general that software
- should test whether specific features are supported instead of relying
- on version number checks. These values are primarily intended for
- reporting to human administrators.
+ These columns report the types and versions of the hardware and
+ software running Open vSwitch. We recommend in general that software
+ should test whether specific features are supported instead of relying
+ on version number checks. These values are primarily intended for
+ reporting to human administrators.
+
The database schema version number in the form
- An identifier for the type of system on top of which Open vSwitch
- runs, e.g.
- System integrators are responsible for choosing and setting an
- appropriate value for this column.
-
+ System integrators are responsible for choosing and setting an
+ appropriate value for this column.
+
- The version of the system identified by ,
- e.g.
- System integrators are responsible for choosing and setting an
- appropriate value for this column.
- 1.1.0pre2
.
- If Open vSwitch was configured with a build number, then it is
- also included, e.g. 1.1.0pre2+build4948
.
+ The Open vSwitch version number, e.g. 1.1.0pre2
.
+ If Open vSwitch was configured with a build number, then it is
+ also included, e.g. 1.1.0pre2+build4948
.
major.minor.tweak
,
e.g. 1.2.3
. Whenever the database schema is changed in
@@ -232,26 +232,26 @@
XenServer
or KVM
.
- XenServer
or KVM
.
+ 5.5.0-24648p
on XenServer 5.5.0 build 24648.
- 5.6.100-39265p
on XenServer 5.6.100 build 39265.
+
+ System integrators are responsible for choosing and setting an + appropriate value for this column. +
+ +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 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. 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 +569,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. lacp-system-priority
false
to disable. If IPsec is enabled through the
- parameters, header caching will be
- automatically disabled.
+ false
to disable.
+
+
+ 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.
+ An authentication method of peer_cert
or
+ psk
must be defined. The following options may
+ be specified in the column:
+ remote_ip
local_ip
peer_cert
certificate
option.certificate
private_key
certificate
. If certificate
+ contains the private key, this option may be omitted.psk
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.tos
inherit
, in which case the ToS will be copied from
+ the inner packet if it is IPv4 or IPv6 (otherwise it will be
+ 0). Note that the ECN fields are always inherited. Default is
+ 0.ttl
inherit
, in which case the
+ TTL will be copied from the inner packet if it is IPv4 or IPv6
+ (otherwise it will be the system default, typically 64).
+ Default is the system default TTL.csum
true
to enable.pmtud
false
to disable.capwap
+ 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; + i.e. whether a carrier is detected by the interface. +
++ 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.openvswitch-ipsec
package for
- Debian. The currently defined key-value pair is:
+ Key-value pairs for rarely used interface features.
ipsec_psk
gre
.lacp-port-priority
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
, BACKOFF
,
+ CONNECTING
, ACTIVE
, and
+ IDLE
.time_in_state