Skip to main content
kriyapedo
kriyapedo
New Member
January 2, 2026
Question

7.4.8 SDWAN with Fabric Overlay Orchestrator

  • January 2, 2026
  • 3 replies
  • 231 views

Been witnessing an issue where spoke to internet traffic via hub would see excessive latency via Tunnel 1 (WAN 1) despite the rule failing over to Tunnel 2 (WAN 2) based on SLA metrics.

Traffic between spoke and internal subnets behind the hub is fine as those do switch to Tunnel 2.

Traffic from spoke to local WAN 1 internet break out is also fine.

Anyone familiar with this issue?

3 replies

Jean-Philippe_P
Staff & Editor
Jean-Philippe_P
Staff & Editor
January 5, 2026

Hello kriyapedo, 

 

Thank you for using the Community Forum. I will seek to get you an answer or help. We will reply to this thread with an update as soon as possible. 

Jean-Philippe - Fortinet Community Team
Daniel__
Daniel__
New Member
January 5, 2026

Hi, 

 

You are not really giving a complete picture, how are routes added, bgp or static, is the internet part of the sd-wan overlay etc? 


A few thoughts. 

 

diagnose sys sdwan health-check on the hub

- Confirms that the health‑check for WAN 1 is actually failing.

 

diagnose sys sdwan neighbor on the hub

get router info routing-table static and bgp on the hub

get router info routing-table bgp on the spoke

 

    iamakk
    iamakk
    Explorer
    February 16, 2026

    Could you please share the output for this : get router info routing-table all

    Terms & ConditionsAccessibility statement