Hi Jayakumar,

To the best of my knowledge, there is one bond interface per bridge. You can interconnect bridges to transit traffic to a different bond interface but it would be better to design bridges and VM NICs in such a way that the traffic always exits via the bond on the local bridge. Meaning two NICs on the VM, for example. NIC1 is connected to bridge br0 with bond0 and the other NIC2 is connected to bridge br1 with the bond1.

Let me know please if that answers your question.

Hi Alona,

    Thanks for your reply.Yes! Even I too think the same what you have mentioned.But When I checked this link https://portal.nutanix.com/page/documents/details/?targetId=AHV-Admin-Guide-v510%3Aahv-acr-nw-mgmt-c.html. There is a topic called Configuring an Open vSwitch Bond with Desired Interfaces which says creating a bond in the bridge. As per my knowledge when we create a bridge say br0 it will automatically create a bond bro-up, then why we need  create a bond manually. Also here they say the default bond name is bond0, but i think the default bond name is br0-up. So here I got confused.

-Jai

Jayakumar,

You can have only one bond inside a bridge. This bond is created by default during the imaging process. If you want to edit the bond members using manage_ovs after it’s already created, it deletes the bond, then creates it with the desired name and desired members. That’s why you need to specify the name. You can choose any name you like, but please use br0-up.

Bonds in br0 used to be named bond0 in older versions of code, but now we name the bond br0-up.