From 15d63ed3ac3fe8c7d545a554220ba9d27b17d13b Mon Sep 17 00:00:00 2001 From: Ben Pfaff Date: Mon, 1 Oct 2012 13:22:35 -0700 Subject: [PATCH] FAQ: Describe how bonded ports interact with OpenFlow. Signed-off-by: Ben Pfaff Acked-by: Kyle Mestery Acked-by: Ethan Jackson --- FAQ | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/FAQ b/FAQ index a98739cb..b14bfa45 100644 --- a/FAQ +++ b/FAQ @@ -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@openvswitch.org. + Contact ------- -- 2.30.2