Recommended Bond0 Config

Nov 25, 2023
21
5
8
I have two NICs that I wanted to use in a bond and support two VLANs while still being able to manage the device using the same bond. I realize that ideally I should have a separate physical interface to manage the device but for now this is what I have until I can add a second NIC.

I am also wondering what the benefits of the OVS bond over the traditional Linux Bond. Its what I have generally used in the past but open to other options.

In this example would I want to assign and IP address to the bridge or just the VLANs themselves?

Finally, I only have OOB management access to the device so I will be manually editing the interface config file.
 
Set up your bond, use it directly or through a bridge if you want VMs on it. And either set that bridge as VLAN Aware if you only need VLANs for VMs, or add a VLAN if you want to manage your node through it.. and a bridge on top of it if you also need VMs on that VLAN..

OVS has a few features that the linux bridge doesn't have (RTSP, VXLAN, …).. but adds a bit of overhead to handle them... For the bond itself, I doubt it's useful to switch..
 
Last edited:
  • Like
Reactions: Eduardo Taboada