Skip to main content
fortiwei1
Staff
Staff
April 7, 2026

Troubleshooting Tip: BGP session flapping in ADVPN hub FortiGate with SD-WAN embedded measured health enabled

  • April 7, 2026
  • 0 replies
  • 338 views
Description
This article describes the cause and resolution of BGP session flapping on an ADVPN hub FortiGate when SD-WAN embedded SLA is enabled. The BGP peering is established over IPsec tunnels between the hub and spokes.
Scope FortiGate (Tested with v7.4).
Solution

When BGP passive mode is disabled on the ADVPN hub FortiGate, SD-WAN health-check events can trigger repeated BGP session resets.

 

When a health check exceeds the configured Service Level Agreement thresholds, the hub resets the BGP session. Check from the hub side with the following commands:

 

diagnose system sdwan health-check remote get router info bgp summary

 

Snipaste_2026-04-03_11-24-53.png

 

After the health check recovers and returns to an acceptable state, the hub resets the BGP session again, which results in visible BGP flapping.

 

Snipaste_2026-04-03_11-26-53.png

 

This behavior occurs only when BGP passive mode is disabled on the ADVPN hub.

To resolve this issue, verify that BGP passive mode is enabled on the hub neighbor group.

 

On the hub FortiGate:

 

config router bgp     config neighbor-group         edit <group-name>             set passive enable <--- (default: enable)         next     end end
 
Additionally, review the SD-WAN health-check configuration on both the hub and spoke FortiGate devices. Ensure that recovery time and SLA thresholds, such as latency, jitter, and packet loss, are aligned with application tolerance levels in order to avoid unnecessary traffic failover between SD-WAN members.
 

HUB FortiGate:

 

config system sdwan     config health-check         edit <Healthcheck-name>             set recoverytime 4 <---                 config sla                     edit <id>                         set latency-threshold 20 <-----                         set jitter-threshold 20 <-----                         set packetloss-threshold 2 <-----                     next                 end             next   end end

 

Related articles: