diff options
| author | Oleksandr Kuchmystyi <o.kuchmystyi@vyos.io> | 2026-06-26 10:23:54 +0300 |
|---|---|---|
| committer | Oleksandr Kuchmystyi <o.kuchmystyi@vyos.io> | 2026-06-26 10:28:05 +0300 |
| commit | 4e11adfb927c22e2f977c897d56a4d243860e877 (patch) | |
| tree | 18123b28269b111c135b7488f0055081e27f5726 /src/migration-scripts/https/1-to-2 | |
| parent | 477b1b9137ef42407e18b68684485ae623834456 (diff) | |
| download | vyos-1x-4e11adfb927c22e2f977c897d56a4d243860e877.tar.gz vyos-1x-4e11adfb927c22e2f977c897d56a4d243860e877.zip | |
bgp: T8865: Reject `vni` sub-block in VRF l2vpn-evpn when `advertise-all-vni` is globally active
When `advertise-all-vni` is configured in the global/default BGP instance,
VyOS generated a `vni <id>` sub-block under each VRF BGP `address-family
l2vpn evpn` context. This conflicts with advertise-all-vni: FRR already
owns all kernel VNIs and returns `% Failed to create VNI` when frr-reload.py
attempts to apply the VRF-level vni sub-block. FRR then performs an early
exit from config processing, silently dropping the entire l2vpn evpn
address-family for all subsequent VRF BGP instances.
Diffstat (limited to 'src/migration-scripts/https/1-to-2')
0 files changed, 0 insertions, 0 deletions