[ovs-dev] [PATCH] FAQ: Describe how bonded ports interact with OpenFlow.
blp at nicira.com
Mon Oct 1 20:18:35 UTC 2012
Signed-off-by: Ben Pfaff <blp at nicira.com>
FAQ | 21 +++++++++++++++++++++
1 files changed, 21 insertions(+), 0 deletions(-)
diff --git a/FAQ b/FAQ
index a98739c..b14bfa4 100644
@@ -747,6 +747,27 @@ A: ovs-dpctl queries a kernel datapath, not an OpenFlow switch. It
won't display the information that you want. You want to use
"ovs-ofctl dump-flows" instead.
+Q: It looks like each of the interfaces in my bonded port shows up
+ as an individual OpenFlow port. Is that right?
+A: Yes, Open vSwitch makes individual bond interfaces visible as
+ OpenFlow ports, rather than the bond as a whole. The interfaces
+ are treated together as a bond for only a few purposes:
+ - Sending a packet to the OFPP_NORMAL port. (When an OpenFlow
+ controller is not configured, this happens implicitly to
+ every packet.)
+ - The "autopath" Nicira extension action. However, "autopath"
+ is deprecated and scheduled for removal in February 2013.
+ - Mirrors configured for output to a bonded port.
+ It would make a lot of sense for Open vSwitch to present a bond as
+ a single OpenFlow port. If you want to contribute an
+ implementation of such a feature, please bring it up on the Open
+ vSwitch development mailing list at dev at openvswitch.org.
More information about the dev