On 10/13/23 14:22, Xuo Guoto via discuss wrote: > ------- Original Message ------- > On Friday, October 13th, 2023 at 4:51 PM, Ilya Maximets <i.maxim...@ovn.org> > wrote: > >> 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. > > Executed > > # ovs-vsctl set port bond0 bond_mode=balance-tcp lacp=active > other-config:lacp-fallback-ab=false other-config:lacp-time=slow > > Now all the interfaces are disabled
This is expected. They were enabled before, because of ab fallback. > > ---- bond0 ---- > bond_mode: balance-tcp > bond may use recirculation: yes, Recirc-ID : 1 > bond-hash-basis: 0 > lb_output action: disabled, bond-id: -1 > updelay: 0 ms > downdelay: 0 ms > next rebalance: 9560 ms > lacp_status: configured > lacp_fallback_ab: false > active-backup primary: <none> > active member mac: 00:00:00:00:00:00(none) > > member vnet74: disabled > may_enable: false > > member vnet75: disabled > may_enable: false > > member vnet76: disabled > may_enable: false > > member vnet77: disabled > may_enable: false > > member vnet78: disabled > may_enable: false > > member vnet79: disabled > may_enable: false > > >> 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. > > # ovs-ofctl dump-flows ovsbr-lacp0 > cookie=0x0, duration=103674.235s, table=0, n_packets=6798, n_bytes=2111314, > priority=0 actions=NORMAL > > I guess this is fine. Yep. Looks fine. > > I did some more digging and when running tcpdump on both the ovs and on > Ubuntu I get this packet repeatedly at both interfaces: > > 12:23:17.081894 LACPv1, length 110 > Actor Information TLV (0x01), length 20 > System a6:a0:01:43:3a:41, System Priority 65534, Key 15, Port 17, > Port Priority 65535 > State Flags [Activity, Aggregation, Collecting, Distributing, > Default] > Partner Information TLV (0x02), length 20 > System 00:00:00:00:00:00, System Priority 0, Key 0, Port 0, Port > Priority 0 > State Flags [none] > Collector Information TLV (0x03), length 16 > Max Delay 0 > Terminator TLV (0x00), length 0 > > I am assuming this is a packet originated from a6:a0:01:43:3a:41 which > happens to be the MAC of ovsbr-lacp0 > > # ovs-vsctl -f table --columns=name,mac_in_use list interface | grep > a6:a0:01:43:3a:41 > ovsbr-lacp0 "a6:a0:01:43:3a:41" > > Am I correct in assuming that ovs is sending LACP packets correctly while > Ubuntu is not responding and not sending its own LACP packets? Yes, looks like it. I'm not an expert in configuring native linux bonds, so I'm not sure how to troubleshoot that. Are the ports including the bond port UP in the guest? Best regards, Ilya Maximets. _______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
