Op 03-02-2026 om 07:31 schreef Jan Vöhringer via users:
Hi Júlíus,
thank you for your message.
i’ve created again a new zone (new DB from scratch) and do following traffic
tags:
Physical Network 1, Isolation Method: VXLAN
*
GUEST (without Label)
*
MANAGEMENT (brcsmm1)
*
PUBLIC (without Label)
*
STORAGE (brdrbd1)
log show: Error: argument "brvxlan1028-1096" is wrong: "name" not a valid
ifname Failed to create br: brvxlan1028-1096
Failed to create vnet 1096: Error: argument "brvxlan1028-1096" is wrong: "name" not a
valid ifname/usr/share/cloudstack-common/scripts/vm/network/vnet/modifyvlan.sh: line 59:
/proc/sys/net/ipv6/conf/brvxlan1028-1096/disable_ipv6: No such file or directoryCannot find device
"brvxlan1028-1096"Failed to create br: brvxlan1028-1096
This confuses me for a couple of reasons:
- modifyvlan.sh and not modifyvXlan.sh, what is the broadcast domain of
the network? This should be vxlan://1028 for example
- Did you provide a VLAN range? Like 1028-1096?
I have a feeling CloudStack is configured in VLAN mode and not VXLAN.
Wido
brvxlan1028-1096 - don’t know why this is used or created, brvxlan1028 is
brcsmm1 with subinterface vxlan1028
1096 is my public guest Network, but i didn’t used it in the wizard.
and i can’t explain why still modifyvlan instead of modifyvxlan is used.
Maybe if NO Traffic Label is set, it uses modifyvlan?
Best Regards,
Jan
Von: Júlíus Þór Bess <[email protected]>
Datum: Montag, 2. Februar 2026 um 18:10
An: [email protected] <[email protected]>
Betreff: Re: VXLAN-EVPN Bridge Name and Traffic Labels
Hi Jan,
Max ifname length is 15 characters, so yes. The ifname of
brvxlan1028-1096 is too long.
Did you replace the modify-vxlan.sh with the EVPN-VXLAN version?
Otherwise you're using the multicast version.
I also notice that the modifyvlan.sh (notice vlan, not vxlan) is
executing and trying to create a VLAN on a traditional bridge... That's
probably not what you want. What should happen is that modifyvxlan.sh
should have created another bridge named brvx1096 which should have a
bridge slave of vxlan1096. Names might not be entirely correct but you
probably get what I mean.
On 2/2/26 4:56 PM, Jan V�hringer via users wrote:
Hi Cloudstack Community,
i have trouble with the Zone/Welcome Wizard in Cloudstack - the System
VMs are in a deployment/reboot loop.
Maybe because of the wrong or too long Bridge Name for VXLAN with EVPN.
*
Setup modify sh for VXLAN with EVPN
*
The Hosts have two physical NICs:
o
eno1 = Transfer LAN-1 OSPF 172.16.11.2/30
o
eno2 = Transfer LAN-2 OSPF 172.16.12.2/30
o
lo = Loopback for BGP with EVPN 10.1.0.1/32
o
brdrbd1 = Bridge for DRBD / Linstor Traffic 10.10.26.101 /24
+
vxlan1026 as Subinterface, added by NMCLI
o
brcsmm1 = Bridge for Cloudstack Management Traffic
10.10.28.101 /24
+
vxlan1028 as Subinterface, added by NMCLI
i’m looking for „normal“ VXLAN Bridges like brvxlan2001 for example
customer1...
After the Wizard completes, the Systems VMs are permanently
rebooted/deployed. And the Wizard create following Interfaces: cloud0
and vxlan1028.1096@vxlan1028
Log Show (1096 should be the public VXLAN):
"“result”:“false”,“details”:“Failed to create vnet 1096: Error:
argument \"brvxlan1028-1096\" is wrong: \"name\" not a valid ifname...
Cannot find device \"brvxlan1028-1096\" Failed to create br:
brvxlan1028-1096”
Failed to create vnet 1096: Error: argument "brvxlan1028-1096" is
wrong: "name" not a valid
ifname/usr/share/cloudstack-common/scripts/vm/network/vnet/modifyvlan.sh:
line 59: /proc/sys/net/
ipv6/conf/brvxlan1028-1096/disable_ipv6: No such file or
directoryCannot find device "brvxlan1028-1096"Failed to create br:
brvxlan1028-1096
i’ve following setups without success:
SCR-20260129-kvah.png
and
image.png
have someone a idea how to create the Interfaces and Traffic Types?
Best Regards,
Jan
