Technical Tip: Reducing BGP convergence delay and packet loss during HA failover using route-ttl and stale routes
| Description | This article describes an issue where significant packet loss and delayed BGP convergence occur during FortiGate HA failover, and how to mitigate it using HA route-ttl and BGP stale route retention (graceful restart). |
| Scope | FortiGate. |
| Solution | In HA failover scenarios involving BGP, the following behavior can commonly be observed, especially in environments using overlay VPNs:
Failover process: During failover, The primary unit goes down and Secondary unit takes over, BGP sessions are re-established and routes are relearned. If the Traffic is dropped until BGP reconvergence is completed, then the below config changes will resolve the issue. See Technical Tip: Controlling how HA synchronizes routing table updates.
Step 1: Configure HA route-ttl. The route-ttl parameter allows FortiGate to retain routes temporarily after failover.
Configuration:
config system ha set route-ttl 210 end
Step 2: Enable BGP graceful restart and stale routes.
To further improve convergence, enable stale route retention on BGP neighbors.
Global configuration:
config router bgp set graceful-restart enable set graceful-restart enable set graceful-restart-time 120 set stale-route enable end
Per-neighbor configuration:
config router bgp config neighbor edit <neighbor-ip> set capability-graceful-restart enable next end end
Notes:
Related articles: |
