diff options
| author | vivek <vivek@cumulusnetworks.com> | 2017-12-11 14:38:15 -0800 |
|---|---|---|
| committer | mitesh <mitesh@cumulusnetworks.com> | 2018-01-23 16:27:25 -0800 |
| commit | 9d97533e37d3614755ef94e75c41e70d0404218b (patch) | |
| tree | c279202ec189dabfa7a1ddbaaf356f422d98e493 /doc/manpages/conf.py | |
| parent | 5ee65f6f3e6e6e9911753cd3c8d70a39b649bed4 (diff) | |
zebra: Refine cleanup when a VRF with configuration gets deleted
When a VRF gets deleted - e.g., networking restart or ifdown of the VRF - but
has associated FRR configuration, additional cleanup of all dynamic data pertaining
to this VRF is necessary. This includes the routing tables, next hop tables,
temporary queues for this VRF etc. Only the FRR configuration for this VRF must
be retained.
Signed-off-by: Vivek Venkatraman <vivek@cumulusnetworks.com>
Reviewed-by: Don Slice <dslice@cumulusnetworks.com>
Reviewed-by: Mitesh Kanjariya <mitesh@cumulusnetworks.com>
Reviewed-by: Donald Sharp <sharpd@cumulusnetworks.com>
Ticket: CM-19148
Reviewed By: CCR-7030
Testing Done:
1. Manual testing - This scenario and EVPN configuration
2. Various smoke tests - vrf, bgp, pim, l3-smoke
Diffstat (limited to 'doc/manpages/conf.py')
0 files changed, 0 insertions, 0 deletions