On 10 Sep 2024, at 13:07, John Depp via discuss wrote:
> Hi! > > I'm using OVS in virtual environment for testing purposes. > Sometimes I'd like to test different network configurations, including LACP > > So, I'd like to have LACP bonded interfaces in my VM, backed by LACP on > OVS, not using any hardware switch Both sides of the link need to run LACP. So how is your VM configured to support LACP? If you are running linux on the VM you need to do something like this: # modprobe bonding miimon=100 mode=4 lacp_rate=1 # ip link add name bond10 type bond # ifenslave bond10 p1p1 p1p2 # ip link set dev bond10 up # ifenslave bond10 p1p1 p1p2 And then you can do “cat /proc/net/bonding/bond10” to see the status. Same on the OVS side, you can do “ovs-appctl bond/show <bond_name>” and “ovs-appctl lacp/show <bond name>”. > I've tried bonding virtual ports on OVS side like > > ovs-vsctl add-bond vmbr0 lacptest tap133561i1 tap133561i2 > > but LACP never goes up > > Moving virtual interfaces to intermediate OVS bridges and then bonding > these bridges does not work also - it seems OVS can't nest bridges. > > Are there any way to make hardware-independed LACP with OVS? > _______________________________________________ > discuss mailing list > disc...@openvswitch.org > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss _______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
