diff options
| author | Abhinay Ramesh <rabhinay@vmware.com> | 2021-03-31 11:05:56 +0000 |
|---|---|---|
| committer | Abhinay Ramesh <rabhinay@vmware.com> | 2021-04-07 06:09:42 +0000 |
| commit | ef7c53e244d5d0cd7c0ba2536fc931abf28df656 (patch) | |
| tree | 1621b49aa404504baaddecdb41f57e4d273ecb53 /pceplib/test/pcep_utils_tests.c | |
| parent | f19d77a086d526171bb19f24c1a4ff9e77ab5b7a (diff) | |
bgpd: vrf route leaking, fix the bgp instance delete and re-add
Description:
FRR doesn't re-install the routes, imported from a tenant VRF,
when bgp instance for source vrf is deleted and re-added again.
When bgp instance is removed and re-added, when import statement is already there,
then route leaking stops between two VRFs.
Every 'router bgp' command should trigger re-export of all the routes
to the importing bgp vrf instances.
When a router bgp is configured, there could be bgp vrf instance(s) importing routes from
this newly configured bgp vrf instance.
We need to export routes from configured bgp vrf to VPN.
This can impact performance, whenever we are testing scale from vrf route-leaking perspective.
We should not trigger re-export for already existing bgp vrf instances.
Co-authored-by: Santosh P K <sapk@vmware.com>
Co-authored-by: Kantesh Mundaragi <kmundaragi@vmware.com>
Signed-off-by: Abhinay Ramesh <rabhinay@vmware.com>
Diffstat (limited to 'pceplib/test/pcep_utils_tests.c')
0 files changed, 0 insertions, 0 deletions