[SOLVED] Help needed in assigning VM on the same Management VLAN as Proxmox

[dubfunkle]

I'm having issues assigning a VM on the same VLAN as the Proxmox Management interface. I'm able to assign a VM on any other VLAN so as soon as I change the VLAN tag and renew lease I get an IP on that VLAN.

My problem is that as soon as I change the VLAN tag to that of the Management VLAN (VLAN4), I lose connectivity to my Proxmox UI and the only way to get back access it to reset the Proxmox network service from CLI. Any help is appreciated. Thanks!

Config below:

auto lo
iface lo inet loopback

auto eno1
iface eno1 inet manual

auto eno2
iface eno2 inet manual

auto bond0
iface bond0 inet manual
bond-slaves eno1 eno2
bond-miimon 100
bond-mode 802.3ad
bond-xmit-hash-policy layer3+4
bond-downdelay 200
bond-updelay 200
bond-lacp-rate 1

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

auto vmbr0.4
iface vmbr0.4 inet static
address 10.9.4.5/24
gateway 10.9.4.1

 

[vesalius]

Are you using vmbr0 or vmbr0.4 with the VM’s/lxc?

 

[dubfunkle]

Are you using vmbr0 or vmbr0.4 with the VM’s/lxc?

I believe I could only select vmbr0 from the UI. You are referring to the Network device config on the VM itself correct? I can try to manually input vmbr0.4 tomorrow and let you know. Thanks.

 

[dubfunkle]

I believe I could only select vmbr0 from the UI. You are referring to the Network device config on the VM itself correct? I can try to manually input vmbr0.4 tomorrow and let you know. Thanks.

Confirmed that I can only choose vmbr0. It seems like as soon as I tag VLAN4 on any of my VM, I lose my routing for VLAN4. I did a quick test where I a pinged a VM configured on VLAN10, changed another VM to VLAN4, lost management but the VM on VLAN10 was still reachable. What's strange is that this happens as soon as I apply the tag and click OK, it's not like I add the tag and then get try and get an IP. There is no request happening to the DHCP server at this time.

 

[dubfunkle]

Any help?!

 

[vesalius]

Not sure why this doesn’t work for you. Maybe try a different approach and use Linux bridge which is not vlan-aware and specifically define the vlans on the bond as the example below and see if that works for you.

Example: Use VLAN 5 with bond0 for the Proxmox VE management IP with traditional Linux bridge

 

[dubfunkle]

Sorry for the late reply but many thanks for sharing that page. Managed to fix my issue using the Linux Bridge by adding and modifying some config on the bridge interface.

Something else I noticed, not really related with this issue but was previously preventing my trunked VLANs to reach my VM's was that when enabling the "VLAN-Aware" parameter from the UI, on the configuration file the line config was being done as "bridge-vlan-aware yes", which for me was not working. Changing the line config to "bridge-vlan-aware true" made this work.
Anyways all is working great for me now. Thanks again for your input.
Final Config:

auto lo
iface lo inet loopback

auto eno1
iface eno1 inet manual

auto eno2
iface eno2 inet manual

auto bond0
iface bond0 inet manual
bond-slaves eno1 eno2
bond-miimon 100
bond-mode 802.3ad
bond-xmit-hash-policy layer3+4
bond-downdelay 200
bond-updelay 200
bond-lacp-rate 1

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

auto vmbr0v4
iface vmbr0v4 inet static
address 10.9.4.5/24
gateway 10.9.4.1
bridge_ports bond0.4
bridge_stp off
bridge-fd 0