Bonding and VLAN

[markusbernhard]

Hi.
I have the following network config, where vlan 250-251 are for storage, and 254 is for migration. Would it be ok to set the vlan-raw-device to enp65s0f0 for vlan 250 and enp65s0f1 for vlan251, in order to use both network cards for storage, or are there any disadvantages?

auto enp65s0f0
iface enp65s0f0 inet manual

auto enp65s0f1
iface enp65s0f1 inet manual

auto bond0
iface bond0 inet manual
bond-slaves enp65s0f0 enp65s0f1
bond-miimon 100
bond-mode active-backup
bond-primary enp65s0f0

auto vmbr1
iface vmbr1 inet manual
bridge-ports bond0
bridge-stp off
bridge-fd 0
bridge-vlan-aware yes
bridge-vids 2-4094

auto vlan250
iface vlan250 inet static
address 10.0.0.108/24
vlan-raw-device vmbr1

auto vlan251
iface vlan251 inet static
address 10.1.10.108/24
vlan-raw-device vmbr1

auto vlan254
iface vlan254 inet static
address 10.2.10.108/24
vlan-raw-device vmbr1

auto vlan1055
iface vlan1055 inet static
address 10.3.10.108/24
gateway 10.3.10.0
vlan-raw-device vmbr1

 

[Pifouney]

Using 2 card in your bond is a good failover option. But, did you know that you wanna do ? Or are you testing ?

 

[markusbernhard]

Sorry, I'll try to be more clear.
I had an idea that I maybe could tag vlans directly on the physical interfaces, instead of using the bond, in order to be able to utilize both NICs for multipahted shared storage. At the same time, I'd like to keep the bond for redundancy of the network connections for vm's.
So, basically I'm trying to avoid going LACP.

 

[Pifouney]

oh ok. But i cannot help you anymore, no idea for your final config ^^