Commits on Feb 1, 2021

1. zebra: treat vrf add for existing vrf as update …

   Description: When we get a new vrf add and vrf with same name, but different vrf-id already
   exists in the database, we should treat vrf add as update.
   This happens mostly when there are lots of vrf and other configuration being replayed.
   There may be a stale vrf delete followed by new vrf add. This
   can cause timing race condition where vrf delete could be missed and
   further same vrf add would get rejected instead of treating last arrived
   vrf add as update.
   
   Treat vrf add for existing vrf as update.
   Implicitly disable this VRF to cleanup routes and other functions as part of vrf disable.
   Update vrf_id for the vrf and update vrf_id tree.
   Re-enable VRF so that all routes are freshly installed.
   
   Above 3 steps are mandatory since it can happen that with config reload
   stale routes which are installed in vrf-1 table might contain routes from
   older vrf-0 table which might have got deleted due to missing vrf-0 in new configuration.
   
   Signed-off-by: sudhanshukumar22 <sudhanshu.kumar@broadcom.com>

   

   sudhanshukumar22 committed Feb 1, 2021
   Configuration menu

   • View commit details
   • Copy full SHA for 75d26fb
   • Browse repository at this point

   Copy the full SHA

   75d26fb View commit details

   Browse the repository at this point in the history