X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=vswitchd%2Fvswitch.xml;h=6565b9582e6ab898b5b914ac9e679d6dcb599f73;hb=ea7bd5973fb426f3a6ea66b0953c6000980e77ec;hp=4aa46494877cad63074eec97cea349293dca5a1a;hpb=3c52fa7b69609ca8fcfc8de7426f7ebbcba493eb;p=openvswitch
diff --git a/vswitchd/vswitch.xml b/vswitchd/vswitch.xml
index 4aa46494..6565b958 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.5.0-24648p
on XenServer 5.5.0 build 24648.
+
+ 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. 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.
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.
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. @@ -583,12 +591,22 @@
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. + 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. +
+
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.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