Hi DPDK users, I met a bond issue with dpdk bond mode 4.
ENV: DPDK 20.11.7 EAL parameters: --file-prefix node-1 --log-level pmd.net.bond:8 --vdev net_bonding0,mode=4,slave=d8:00.0,slave=d9:00.0 --vdev net_bonding1,mode=4,slave=d8:00.1,slave=d9:00.1 Here we only forcus on net_bonding0, which has two slave ports(1,3) in this bonding, and I set a bond mac 11:22:33:44:55:66 in app. The bond link is lost while shutdown one slave port. The reason seems the actor system id is changed while shutdown port 0. It cause port 3 to renegotiate and link down in this senario. I compared this with a linux bond behavior, the difference is that linux bonding device do not change system id while I shutdown one port. Do you have any idea for the issue ? Is this a dpdk bug ? I search the email list, and I found @Viktor Vasiliev<mailto:[email protected]> met a slimilar issue "bond mode 8023ad LACP system id changes when link goes down<http://patchwork.dpdk.org/project/dpdk/patch/[email protected]/>", I use your patch and it fix bonding status issue but no user pkts could send out while I shutdown one port ... so it's still not valid for me. Do you have any progress on your issue ? Thanks in advance. Sorry to cc you, dpdk experts, I notice you all fix some bond related issues, may you could help, thanks you so much! Br, Christian
