X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=vswitchd%2Fvswitch.xml;h=1128db945f7e75c0d49f085d7d02bb1a103c17d9;hb=a65084987b743fbeaf9a5376ea0fe99454912186;hp=cd50f556de0619410992e090ebbab22bad112cb8;hpb=2c999774c1758ebdb138bb73e89e8de01f134d26;p=openvswitch diff --git a/vswitchd/vswitch.xml b/vswitchd/vswitch.xml index cd50f556..1128db94 100644 --- a/vswitchd/vswitch.xml +++ b/vswitchd/vswitch.xml @@ -233,8 +233,6 @@ The Open vSwitch version number, e.g. 1.1.0. - If Open vSwitch was configured with a build number, then it is - also included, e.g. 1.1.0+build6579. @@ -1728,6 +1726,37 @@ an ovs-appctl command. + + Indicates a CFM fault was triggered due to the reception of a CCM + frame having an invalid interval. + + + + Indicates a CFM fault was triggered because the CFM module received + a CCM frame with a sequence number that it was not expecting. + + + +

+ Indicates the health of the interface as a percentage of CCM frames + received over 21 s. + The health of an interface is undefined if it is communicating with + more than one . It reduces if + healthy heartbeats are not received at the expected rate, and + gradually improves as healthy heartbeats are received at the desired + rate. Every 21 s, the + health of the interface is refreshed. +

+

+ As mentioned above, the faults can be triggered for several reasons. + The link health will deteriorate even if heartbeats are received but + they are reported to be unhealthy. An unhealthy heartbeat in this + context is a heartbeat for which either some fault is set or is out + of sequence. The interface health can be 100 only on receiving + healthy heartbeats at the desired rate. +

+
+ When CFM is properly configured, Open vSwitch will occasionally receive CCM broadcasts. These broadcasts contain the MPID of the @@ -1768,7 +1797,8 @@ When set, the CFM module will apply a VLAN tag to all CCMs it generates - with the given value. + with the given value. May be the string random in which + case each CCM will be tagged with a different randomly generated VLAN. + + The VM to which this interface belongs. On XenServer, this will be the + same as . + + The VM to which this interface belongs. @@ -1921,6 +1956,12 @@ VLAN splinters increase kernel and userspace memory overhead, so do not use them unless they are needed.

+ +

+ VLAN splinters do not support 802.1p priority tags. Received + priorities will appear to be 0, regardless of their actual values, + and priorities on transmitted packets will also be cleared to 0. +

@@ -2061,9 +2102,11 @@

Queue 0 is the ``default queue.'' It is used by OpenFlow output - actions when no specific queue has been set. Ordinarily should include a configuration for queue 0. When no - configuration for queue 0 is present, a default configuration is used. + actions when no specific queue has been set. When no configuration for + queue 0 is present, it is automatically configured as if a record with empty + and columns had been + specified. (Before version 1.6, Open vSwitch would leave queue 0 unconfigured in this case. With some queuing disciplines, this dropped all packets destined for the default queue.) @@ -2647,11 +2690,34 @@ + +

+ Additional configuration for a connection between the controller + and the Open vSwitch. +

+ + + The Differentiated Service Code Point (DSCP) is specified in the IP + header. They are specified using 6 bits in the Type of Service (TOS) + field in the IP header. DSCP provides a mechanism to classify the + network traffic and provide the Quality of Service (QoS) on IP + networks. + The DSCP value passed is used when establishing the connection between + the controller and the Open vSwitch. The connection must be reset + for the new DSCP values to take effect. If no value is + specified, a default value of 192 is chosen for connection + establishment. Valid DSCP values must have their lower 2 bits set to 0. + + + + The overall purpose of these columns is described under Common Columns at the beginning of this document. + @@ -2871,11 +2937,33 @@
+ +

+ Additional configuration for a connection between the manager + and the Open vSwitch Database. +

+ + + The Differentiated Service Code Point (DSCP) is specified in the IP + header. They are specified using 6 bits in the Type of Service (TOS) + field in the IP header. DSCP provides a mechanism to classify the + network traffic and provide the Quality of Service (QoS) on IP + networks. + The DSCP value passed when establishing the connection between + the manager and the Open vSwitch Database. The connection must be + reset for the new DSCP values to take effect. If no value is + specified, a default value of 192 is chosen for connection + establishment. Valid DSCP values must have their lower 2 bits set to 0. + +
+ The overall purpose of these columns is described under Common Columns at the beginning of this document. +