we would like to know how the MX decides to failover from wan 1 to the WAN 2.
Considering in example that the primary wan is the WAN 1, can you explain us If these are the cases where the mx failover to WAN 2 :
- Wan 1 physically down;
- Wan 1 logically down, i.e. the link is up but for some reason internet is not reachable;
- Wan 1 affected by loss;
- Wan 1 affected by latency;
If some of the points above are part of the logic can you tell us what are the thresholds ?
Consider that the firewalls in the organization has just the SEC License (not sd-wan plus)
Are the parameters for the thresholds (again Loss, Latency etc.) configurable ?
In case there's a flow that force the outgoing traffic to go out from WAN 2 is the above parameters appliable as well and so in case of any problem the traffico goes out WAN 1 ?
hi @Dieghitoo77
You're looking at points 1 and 2 for WAN failover's to occur. Take a read through the below WAN failover document which highlights the steps the mx performs before deciding to failover.
The threshold parameters aren't configurable.
Only for sdwan(vpn) traffic. Based on %loss,jitter,latency
it is not clear when MX change the flow,. for us, it is clear that the thresholds are not configurable with our license.
we try to know when MX move the traffic flow from wan1 to wan2, what are the thresholds? how is it processed?
For vpn/sdwan traffic you should be able
You can define Flow preferences for your traffic types to send traffic out of WAN 1 or WAN 2:
The answer depends on whether you are talking about plain Internet traffic or SDWAN traffic. Which use case are you referring to?