[j-nsp] Vlan 111 on EVPN-VXLAN

[Cristian Cardoso]

Hi

I had a strange behavior in my environment where I use qfx5120-48y-8c
switches, in spine/leaf topology with EVPN-VXLAN configured.

I transport the VLANs via VXLAN between the servers that are below the
leafs, to my mx routers that are above the spines. To make my life easier,
I use the configuration of groups in the leafs, to "standardize" the
aggregation interfaces with the servers in the environment and apply the
VLANs on all the servers that are below the leafs at the same time.

I use the group config like this:

> show configuration groups VLANS
interfaces {
    <ae*> {
        mtu 9216;
        unit 0 {
            family ethernet-switching {
                vlan {
                    members [ VNI830 VNI2925 VNI1819 VNI2819 VNI2829
VNI2853 VNI4018 VNI650 VNI680 VNI682 VNI750 VNI780 VNI782 VNI810 VNI815
VNI816 VNI821 VNI822 VNI826 VNI827 VNI828 VNI852 VNI854 VNI887 VNI910
VNI915 VNI916 VNI921 VNI922 VNI927 VNI928 VNI930 VNI952 VNI954 VNI987
VNI2953 VNI222 ];
                }
            }
        }
    }
}

> show configuration interfaces
apply-groups VLANS;

I just don't apply the VLANS group on the communication interfaces between
the leafs and the spines, on the other ports where the servers are
connected, the group is applied.

I have some VMs running OSPF with my MX routers on VLAN VNI2819, the
problem that occurred was when I tried to insert the VLAN VNI111, where the
vlan-id is 111 and the vni is 111 in the VLANS group, when applying the
configuration, the communication automatically OSPF on VNI2819 dropped
instantly, only coming back after I removed VLAN 111.

Does anyone happen to know if there is any limitation on Juniper equipment,
where VLAN or VNI 111 is reserved internally in the system, I looked for
documentation and I didn't find anything about it.