X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=FAQ;h=86b48a2164607689c16e230d88ad33aa59446f2e;hb=e2f3178f0582eda302bdc5629189b6a56d9fbcdd;hp=27bd5b88f02217890e17d63d2fa645404c96be45;hpb=c37c03826ce05e0d8262180b102923574eea01eb;p=sliver-openvswitch.git diff --git a/FAQ b/FAQ index 27bd5b88f..86b48a216 100644 --- a/FAQ +++ b/FAQ @@ -148,7 +148,8 @@ A: The following table lists the Linux kernel versions against which the 1.10.x 2.6.18 to 3.8 1.11.x 2.6.18 to 3.8 2.0.x 2.6.32 to 3.10 - 2.1.x 2.6.32 to 3.12 + 2.1.x 2.6.32 to 3.11 + 2.2.x 2.6.32 to 3.14 Open vSwitch userspace should also work with the Linux kernel module built into Linux 3.3 and later. @@ -157,18 +158,22 @@ A: The following table lists the Linux kernel versions against which the It should build against almost any kernel, certainly against 2.6.32 and later. -Q: What Linux kernel versions does IPFIX flow monitoring work with? +Q: I get an error like this when I configure Open vSwitch: -A: IPFIX flow monitoring requires the Linux kernel module from Open - vSwitch version 1.10.90 or later. + configure: error: Linux kernel in is version , but + version newer than is not supported (please refer to the + FAQ for advice) -Q: Should userspace or kernel be upgraded first to minimize downtime? + What should I do? - In general, the Open vSwitch userspace should be used with the - kernel version included in the same release or with the version - from upstream Linux. However, when upgrading between two releases - of Open vSwitch it is best to migrate userspace first to reduce - the possibility of incompatibilities. +A: If there is a newer version of Open vSwitch, consider building that + one, because it may support the kernel that you are building + against. (To find out, consult the table in the previous answer.) + + Otherwise, use the Linux kernel module supplied with the kernel + that you are using. All versions of Open vSwitch userspace are + compatible with all versions of the Open vSwitch kernel module, so + this will also work. See also the following question. Q: What features are not available in the Open vSwitch kernel datapath that ships as part of the upstream Linux kernel? @@ -192,6 +197,19 @@ A: Tunnel virtual ports are not supported, as described in the actions. On Linux kernels before 2.6.39, maximum-sized VLAN packets may not be transmitted. +Q: What Linux kernel versions does IPFIX flow monitoring work with? + +A: IPFIX flow monitoring requires the Linux kernel module from Open + vSwitch version 1.10.90 or later. + +Q: Should userspace or kernel be upgraded first to minimize downtime? + + In general, the Open vSwitch userspace should be used with the + kernel version included in the same release or with the version + from upstream Linux. However, when upgrading between two releases + of Open vSwitch it is best to migrate userspace first to reduce + the possibility of incompatibilities. + Q: What happened to the bridge compatibility feature? A: Bridge compatibility was a feature of Open vSwitch 1.9 and earlier. @@ -1100,25 +1118,43 @@ A: The following table lists the versions of OpenFlow supported by 1.11 yes --- [*] [*] --- 2.0 yes [*] [*] [*] --- 2.1 yes [*] [*] [*] --- - 2.2 yes [*] [*] [*] [*] + 2.2 yes [*] [*] [*] [%] + 2.3 yes yes yes yes [%] [*] Supported, with one or more missing features. + [%] Support is unsafe: ovs-vswitchd will abort when certain + unimplemented features are tested. + + Open vSwitch 2.3 enables OpenFlow 1.0, 1.1, 1.2, and 1.3 by default + in ovs-vswitchd. In Open vSwitch 1.10 through 2.2, OpenFlow 1.1, + 1.2, and 1.3 must be enabled manually in ovs-vswitchd. Either way, + the user may override the default: - Because of missing features, OpenFlow 1.1, 1.2, 1.3, and 1.4 must - be enabled manually. The following command enables OpenFlow 1.0, - 1.1, 1.2, and 1.3 on bridge br0: + - To enable OpenFlow 1.0, 1.1, 1.2, and 1.3 on bridge br0: - ovs-vsctl set bridge br0 protocols=OpenFlow10,OpenFlow11,OpenFlow12,OpenFlow13 + ovs-vsctl set bridge br0 protocols=OpenFlow10,OpenFlow11,OpenFlow12,OpenFlow13 - Use the -O option to enable support for later versions of OpenFlow - in ovs-ofctl. For example: + - To enable only OpenFlow 1.0 on bridge br0: + + ovs-vsctl set bridge br0 protocols=OpenFlow10 + + All current versions of ovs-ofctl enable only OpenFlow 1.0 by + default. Use the -O option to enable support for later versions of + OpenFlow in ovs-ofctl. For example: ovs-ofctl -O OpenFlow13 dump-flows br0 + OpenFlow 1.4 is a special case, because it is not implemented + safely: ovs-vswitchd will abort when certain unimplemented features + are tested. Thus, for now it is suitable only for experimental + use. ovs-vswitchd will only allow OpenFlow 1.4 to be enabled + (which must be done in the same way described above) when it is + invoked with a special --enable-of14 command line option. + OPENFLOW-1.1+ in the Open vSwitch source tree tracks support for - OpenFlow 1.1 and later features. When support for a given OpenFlow - version is solidly implemented, Open vSwitch will enable that - version by default. + OpenFlow 1.1 and later features. When support for OpenFlow 1.4 is + solidly implemented, Open vSwitch will enable that version by + default. Q: Does Open vSwitch support MPLS?