On 10/13/23 07:22, Xuo Guoto via discuss wrote:
> ------- Original Message -------
> On Thursday, October 12th, 2023 at 9:03 PM, Ilya Maximets
> <i.maxim...@ovn.org> wrote:
>
> Thanks again for the detailed reply!
>
>> If you want to preserve these, you'll need to re-add them manually.
>> Potentially as part of the same transaction, by adding more commands,
>> i.e.
>>
>> ovs-vsctl \
>> del-port vnet75 \
>> -- del-port vnet78 \
>
> I had followed your advice and used the following command to create the bond
>
> ovs-vsctl \
> del-port vnet75 \
> -- del-port vnet78 \
> -- del-port vnet79 \
> -- del-port vnet77 \
> -- del-port vnet74 \
> -- del-port vnet76 \
> -- add-bond ovsbr-lacp0 bond0 vnet75 vnet78 vnet79 vnet77 vnet74 vnet76
> lacp=active \
> -- set Interface vnet75 \
> external_ids='{attached-mac="52:54:00:0d:61:fc", iface-id="",
> iface-status=active, vm-id=""}' \
> -- set Interface vnet78 \
> external_ids='{attached-mac="52:54:00:24:36:a7", iface-id="",
> iface-status=active, vm-id=""}' \
> -- set Interface vnet79 \
> external_ids='{attached-mac="52:54:00:c7:90:3c", iface-id="",
> iface-status=active, vm-id=""}' \
> -- set Interface vnet77 \
> external_ids='{attached-mac="52:54:00:79:8e:a0", iface-id="",
> iface-status=active, vm-id=""}' \
> -- set Interface vnet74 \
> external_ids='{attached-mac="52:54:00:aa:fb:bb", iface-id="",
> iface-status=active, vm-id=""}' \
> -- set Interface vnet76 \
> external_ids='{attached-mac="52:54:00:d4:cc:88", iface-id="",
> iface-status=active, vm-id=""}'
>
> Note: iface-id and vm-id values have been removed for brevity.
>
> Now the command was successful and I could see the bond0 port with the
> specified interfaces
>
> Bridge ovsbr-lacp0
> Port bond0
> Interface vnet78
> Interface vnet75
> Interface vnet79
> Interface vnet74
> Interface vnet77
> Interface vnet76
> Port ovsbr-lacp0
> Interface ovsbr-lacp0
> type: internal
> Port vnet72
> Interface vnet72
>
> But the bonding is not working correctly
>
> $ sudo ovs-appctl bond/show bond0
> ---- bond0 ----
> bond_mode: active-backup
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
Best regards, Ilya Maximets.
> 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: 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
>
> I have configured bonding on an Ubuntu 22.04 at the other end with following
> configuration:
>
> bonds:
> bond0:
> addresses: [192.168.201.141/24]
> interfaces:
> - enp2s0
> - enp3s0
> - enp4s0
> - enp5s0
> - enp6s0
> - enp7s0
> parameters:
> mode: 802.3ad
> mii-monitor-interval: 100
>
> And I get this error in dmesg: bond0: Warning: No 802.3ad response from the
> link partner for any adapters in the bond
>
> In Ubuntu the bond mode is 802.3ad, while in ovs its shows as active-backup
> could that be the reason for bond not getting online?
>
> I am kind of stuck here!
You can see the
_______________________________________________
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
