PR that fixes behavior and introduces validation: https://github.com/vyos/vyos-1x/pull/5297

@o.kuchmystyi I confirm that works, thanks.

@ssasso you can verify it by deleting 'address-family l2vpn-evpn vni <id>':

I have found the root cause of this issue:

• VyOS generates a vni <id> block inside router bgp <asn> vrf <name> / address-family l2vpn evpn for each VRF:

Here you go:

@ssasso, I would be grateful if you provide the output of the following command:

• sudo /usr/lib/frr/frr-reload.py --reload --debug --stdout /run/frr/config/vyos.frr.conf

@o.kuchmystyi just tested with 2026.05.30-0046-rolling and I still have the issue.

@ssasso I have tested your setup using 2026.05.28-0044-rolling and I couldn't reproduce this behavior. Could you check it again?

https://github.com/vyos/vyos-1x/pull/5216

This is a duplicate which has been fixed in 1.5.0 LTS and also rolling. A subsequent fix will be present in the next stream release, too.

PR https://github.com/vyos/vyos-vpp-patches/pull/35