You might see this error when using VXLAN on Juniper kit after you set an interface to be a member of “all” VLANs. This is because “all” includes VLAN 1. Per this documentation, you can’t actually use VLAN 1 with VXLAN but you must map it to a VNI. For example:
/* You need to map VLAN 1 to a VNI else you can't use `vlan members all` on interfaces - DO NOT USE THIS VLAN */
VLAN001 {
vlan-id 1;
vxlan {
vni 1;
}
}
VLAN001 {
vlan-id 1;
vxlan {
vni 1;
}
}
Set syntax is:
set vlans VLAN001 vlan-id 1 vxlan vni 1
Hi Phil,
Thank you for good information. I tried it but the same error was displayed, I found EVPN-VXLAN with MC-LAG is not supported. I’ll look it up about EVPN multihoming active-active mode.
Multichassis link aggregation groups (MC-LAGs) are not supported with VXLAN.
NOTE In an EVPN-VXLAN environment, EVPN multihoming active-active mode is used instead of MC-LAG for redundant connectivity between hosts and leaf devices.
https://www.juniper.net/documentation/en_US/junos/topics/concept/vxlan-constraints-qfx-series.html
Right – EVPN multihoming is the correct way to do HA in an EVPN+VXLAN setup. The config for it is pretty simple, it’s just a single port LACP LAG with a common ESI ID between the two switches