This is expected behaviour: https://documentation.meraki.com/MX/Firewall_and_Traffic_Shaping/Connection_Monitoring_for_WAN_Failover If you are operating with MX to MX AutoVPN tunnels then you can use SD-WAN policies to shuffle important tunnelled sessions across to the secondary WAN link very quickly (seconds). https://documentation.meraki.com/MX/Firewall_and_Traffic_Shaping/SD-WAN_and_Traffic_Shaping#SD-WAN_policies For Internet-bound traffic, you can use SD-Internet policies to ensure that new flows are generated, originating from the secondary WAN link, more quickly (c. 30 seconds after the primary fails ) https://documentation.meraki.com/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practice_Design_-_MX_Security_and_SD-WAN/SD-WAN_Internet_Policies_(SD-Internet) The SD-WAN+ MX license is required for this feature (required for all MXs in the Dashboard Organization) Remember that untunnelled traffic flows are NATed to the outside address of the MX. This session must therefore change source IP address to use the secondary WAN, so must be entirely re-initiated - thus seamless failover is not an option, regardless of configuration.
... View more
