| Description | This article describes how to resolve the issue with the SD-WAN rule that uses the route tag for dynamic destination. However, the rule is not working due to the 'Service disabled caused by no destination' error. |
| Scope | FortiGate. |
| Solution |
In the following scenario, the SD-WAN rule for the 4 dialup tunnels. Each with its route-tag for the dynamic destination.
However, if the SD-WAN logs are checked or if the CLI uses the command 'diag sys sdwan service', the error 'Service disabled caused by no destination' for SD-WAN rules 3 and 4.
Sample Logs in SD-WAN Events:
If looking at the BGP network and route-tag, the route is tagged from 10.20.20.2(Dialup_2_2) to 3 and the route from 10.20.10.2(Dialup_2_1) to 4.
So, if correcting the correct route-tag destination on the SD-WAN rule just like the following:
The results of 'diag sys sdwan service', show the results as expected now:
|
