I have never tried this, but can't you provide a VLAN ID while creating
the L2 network?
And you mention VNI, that's VXLAN specific. But I assume you use VLANs?
Wido
Op 24/09/2024 om 13:53 schreef Jeroen Kleijer:
Hi all,
I've got the situation where my hypervisor has a network interface called
eth0. I created a VLAN interface on top of it (eth0.252 for VLAN 252) and
assigned the IP address of the hypervisor to it.
I'm running ACS 4.19.1.1 and would like to deploy VMs in VLAN 252 so I
thought I could set my guest traffic to go over eth0.252 so that it's
automatically tagged and that I'd only need to create a guest network on
top of it of type DefaultL2NetworkOfferingConfigDrive (without the VLAN)
thinking it would then simply create a bridge on top of eth0.252 and attach
my VM's to it.
Unfortunately, it just creates a new interface and randomly selects a VLAN
ID from the VLAN/VNI range I gave during the setup of the whole zone. (I
gave it the range between 500-700) Now my VM's attached to a bridge that's
on top of an interface that does tagging (VLAN 655 apparently) which is on
top of an interface that already does tagging (VLAN 252) which won't work.
Is the setup that I'd like to have possible and if so, how? What would I
need to do to configure it so that ACS doesn't create a new VLAN tagged
interface, but just creates a new bridge interface on top of the tagged
VLAN interface and let it work that way? (if such a thing is even possible)
Kind regards,
Jeroen Kleijer
