On 10/13/23 12:55, Xuo Guoto wrote: > > ------- Original Message ------- > On Friday, October 13th, 2023 at 3:51 PM, Ilya Maximets <i.maxim...@ovn.org> > wrote: > > Thanks again for taking time to answer my questions! > > >> Here is your problem. The bond is in active-backup mode. This mode doesn't >> support LACP. You need to switch to the balanced mode, e.g. by adding >> 'bond_mode=balance-tcp' to the bond creation command. Or you may set it after >> the fact with: >> >> ovs-vsctl set port bond0 bond_mode=balance-tcp > > After some trial and error I got this command from Redhat bugzilla BZ#1267291 > > ovs-vsctl set port bond0 bond_mode=balance-tcp lacp=active > other-config:lacp-fallback-ab=true other-config:lacp-time=fast > > Now the output is > > ovs-appctl bond/show bond0 > ---- bond0 ---- > bond_mode: balance-tcp > bond may use recirculation: no, Recirc-ID : -1 > bond-hash-basis: 0 > lb_output action: disabled, bond-id: -1 > updelay: 0 ms > downdelay: 0 ms > lacp_status: configured > lacp_fallback_ab: true > active-backup primary: <none> > active member mac: fe:54:00:79:8e:a0(vnet77) > > member vnet74: enabled > may_enable: true > > member vnet75: enabled > may_enable: true > > member vnet76: enabled > may_enable: true > > member vnet77: enabled > active member > may_enable: true > > member vnet78: enabled > may_enable: true > > member vnet79: enabled > may_enable: true > > I can see that all member interfaces are enabled now, and I get an active > member mac. But still there is no ping between two devices in the switch. > Also in linux I can see this error bond0: Warning: No 802.3ad response from > the link partner for any adapters in the bond > > Could lb_output action: disabled, bond-id: -1 be the reason the bond0 is not > getting up?
No, it's just an optimization and kernel datapath doesn't support it. So, should not affect the actual traffic. You have an 'lacp_status: configured', meaning the negotiation with the other side didn't work out. It should be in 'negotiated' state if everything is working. I'd suggest you disable the lacp-fallback-ab, so the bond doesn't fall back to active-backup mode on failures. At least while you're troubleshooting. And you probably better use slow lacp-time as well. Also, how does the flow table look like? i.e. what's in the output of 'ovs-ofctl dump-flows ovsbr-lacp0' ? In case there are rules that would drop LACP traffic. Best regards, Ilya Maximets. _______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
