Troubleshooting Tip: Route shows inactive when SD-WAN Performance SLA Configured

[qyah]

Description	This article describes that the route shows inactive when SD-WAN Performance SLA is Configured.
Scope	FortiGate v7.4.X.
Solution	From the output of the command, 'get router info routing-table details 0.0.0.0' the static route has been configured and is showing inactive at port2: A configured Performance SLA still runs even if all SD-WAN rules referencing the interface have an interface selection method that does not rely on SLA. In this example, the 'Manual' strategy is used, but port2 is still not selected to forward the traffic. When an SD‑WAN Performance SLA is assigned to an interface, FortiGate monitors its health. If the health check fails (no response to probes within timeout), and 'Update static route' is enabled, the system automatically removes or marks inactive the associated static route in the routing table. This behavior ensures traffic doesn’t route over unhealthy links, and so it is the default configuration for Performance SLA. If a route is being inactivated and that behavior is not desired, follow one or more of the following: Disable 'Update static route' in the Performance SLA configuration. Remove SD-WAN members from any Performance SLA that does not apply to them. Troubleshoot why the health check probes are failing, see the article Troubleshooting Tip: First steps to troubleshoot connectivity problems to or through a FortiGate wit... The same troubleshooting method can be done on for IPsec tunnels which are SD-WAN members. In many environments, configuring a source IP address for an IPsec tunnel to use with a Performance SLA is required, see Technical Tip: How to configure source IP for Secure SD-WAN Performance SLA A route will also show inactive if there is no valid gateway or next-hop in the routing table, see the KB article Technical Tip: SD-WAN is not in Active Routing Table