Correct, however, the LAG doesn't get assigned an OpenFlow port number, so the controller can't direct flows out it without using some mechanism like the "normal" action.
--Justin On Oct 15, 2013, at 11:01 AM, Vasu Dasari <[email protected]> wrote: > You will be using LACP mechanism just to create a LAG interfaces. You can > accomplish that using OVS. You can create traffic flows to go over these > LAG(like that on any other interfaces in the system) using openflow, using > openflow controllers. > > > On Tue, Oct 15, 2013 at 12:52 PM, ZhengLingyun <[email protected]> wrote: > Thanks Ben. > I can avoid using ovs-controller. > But I don't find document specifing if I can use LACP and openflow > simultaneously. > The remote controller has no openflow way to get the LACP configuration I > think, so > the flow table will mass up, is that right? > > > > > > At 2013-10-15 23:55:30,"Ben Pfaff" <[email protected] > > wrote: > >On Tue, Oct 15, 2013 at 04:07:39PM +0800, ZhengLingyun wrote: > >> I just enable the LACP function in OVS and connect the OVS to its > >> ovs-controller, it seems I will get a loop. > > > >Don't use ovs-controller. > > > > > _______________________________________________ > discuss mailing list > [email protected] > http://openvswitch.org/mailman/listinfo/discuss > > > _______________________________________________ > discuss mailing list > [email protected] > http://openvswitch.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
