We've been using SD-WAN to load balance across 4 internet connections on version 6.0.x no problem for a long time. We recently updated to 6.2.x and have seen nothing but problems that seem to be related to sessions hopping from one ISP to another too frequently. We have looked at the logs and the destination interface for the same source/destination IP pair jumps periodically. We have been using weighted volume based balancing until now.
It seems that for the kinds of applications that most of our people use, either source-destination or just source-based balancing may be the best fit to force the connections to stay on the same outbound connection and not break signed-on web application sessions and the like.
So the question for the group is, do others see problems like this with connections jumping around? In the real world, do you see better results by trying to create specific rules for the troublesome destination applications to make the connections more sticky? Or is it easier to just do the source based balancing for everything?
Did you read the information in the link I posted?
When no explicit SD-WAN rules are defined, or if none of the rules are matched, then the default implicit rule is used.
So when you build rules above the implicit these rules are execute outside of what you have configured in implicit. Another item if your on 6.4.x you can't even clone or edit that rule. It like what the document says is the implicit implied rule.
so all zones are impacted
fwhibTH081 # diag sys sdwan zone
Zone upg-zone-wan2 index=2
Zone virtual-wan-link index=1
Zone vpn index=3
members(2): 43(vpn1) 44(vpn2)
Zone vpn index=4
members(2): 47(vpn3) 48(vpn4)
Remember the SDWAN concept is advance PBR with load-balance and session persistence.
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.