Management IP shared with vNet VLAN?

[WisperCA]

I have a problem with SDN. Here is my problem:

Requirements:

My Switch does not recognize a default VLAN. A VLAN MUST be specified.,
I must use SDN vNETs for VLANS so they will have a name. My admins can't memorize 2000 VLAN IDs.

Work Performed:
Created Linux VLAN vmbr0.950 for Basic (Management) VLAN and assigned Proxmox Management Address. This works. I can access the GUI and do stuff.

More Work Performed:
Assigned VLAN950 directly to a VM host to communicate on the same LAN. This works. However, I need to do this using a VNET so the VLANS will have a name (like VMWARE)

Problem:
When I create a vNET for any other VLAN (not 950) - it works fine.

But when I create a new vNET for 950 - so that Virtual machines can share the VLAN - It UNBINDS the management IP. In linux, the IP address no longer can be bound, even if I try to ifconfig it manually. The Proxmox GUI becomes unavailable - and the only solution is to go into linux and comment out the SDN product, so I can log in to the GUI again.

Interestingly, the VMs using that vNET can communicate on that VNet during the outage. It's just the Management IP that no longer works.


What I am trying to accomplish is to have an SDN VNet for guests configured for the same VLAN as the Management IP. Is this not possible?

 

[shanreich]

Usually this happens when you're using a non VLAN-aware bridge and configure the management IP on the physical interface (e.g.eth1.950) itself.

To check, can you post the network configuration of your host + VM configuration?

cat /etc/network/interfaces
cat /etc/network/interfaces.d/sdn
cat /etc/pve/sdn/zones.cfg
cat /etc/pve/sdn/vnets.cfg

 

[WisperCA]

Hello,

The config at this moment is working by avoiding assigning any vNets/VMs to that vlan. The test VM I have is just sitting there.

If I add a vNet for 950, I lose management access and won't be able to copy/paste configs to you. Sometimes, it lets me add it, but then when I actually assign the vNet to a VM and apply, that's when the GUI hangs and the IP drops. Ironically, the VM then starts bridging (working) on the vlan as expected.


This is a brand-new Install, and a minimal config - I am willing to set it up any way you tell me to - just tell me how it should be done.


RE: Usually this happens when you're using a non VLAN-aware bridge

I've tried both, but VLAN Virtual machines can bridge through it successfully, even when the Management IP drops.

RE: configure the management IP on the physical interface (e.g.eth1.950) itself.

It's assigned to a Linux VLAN I created in the GUI. How else can I set the Management VLAN?



This system has 2 physical interfaces. Eventually I would like to bond them. So eventually, I need everything to go through ONE bonded interface, including the Mngmt IP.

 

[shanreich]

It should work if you configure the IP address for the management VNet on the VNet instead of the bridge directly - so:

auto <vnet>
iface <vnet> inet static
        address 203.0.113.100/24

You should be able to configure this manually in /etc/network/interfaces without applying - then creating the respective VNet in the SDN configuration and apply everything at once (normal network configuration gets applied when applying SDN config as well).

 

[WisperCA]

Wow.

What a procedure... it worked.

So, to RECAP:
The card spawns initially in the INTERFACES file with the IP (which now shows up in the GUI as an UNKNOWN device), then it loads REENTRANTLY in the SDN file where the remaining Proxmox SDN parameters are assigned.


By extension, I'm coming to the conclusion that the SDN product's "ephermeral" non-IP-version of vmbr0.950 (which I noticed in configures in the SDN file) was squishing the previous vmbr0.950 I had created in the GUI that had the IP address assigned.


In any case, it worked, and I was able to set up the linux bond as well.


Thank you very much.