WAN Failover/Failback: Graceful/Immediate

[rhbirkelund]

It might just be me, but has anyone else noticed this? Didn't it just show up within the last few days?

The documentation was updated two days ago, Nov. 21.

https://documentation.meraki.com/MX/Firewall_and_Traffic_Shaping/Connection_Monitoring_for_WAN_Failo...

[alemabrahao]

Nope, what version are you running?

[ww]

Yes i noticed yesterday. Previous  it was only available at the local status page

[Ryan_Miles]

The feature went live 11/16/22. Requires MX17 firmware. And only works in non-templated networks.

[sprahlad]

when will the template have those options?

[Mloraditch]

Is it just me or does anyone else want immediate failover but graceful failback? That seems like the ideal scenario. 

[Jeizzen]

Yeah......a VoIP flow that has dead air because the expiry time has not ended and it is still on the failed WAN 1 (in Graceful Mode failover), waiting for something to happen for 300 seconds ??

[TheAlchemist]

And what is expiry time? and how long ? 5 minutes? so if preferred uplink fails still all existing traffic will use it i.e. no connection to internet till "expiry" i.e. no internet connectivity for 5 minutes? 

[mansamusa]

Did you ever find an answer to this? I want to know what the expiry time is as well.

[Jeizzen]

Here's an answer from meraki:

In case the link goes down, the failover would be immediate.

But a soft failure occurs when the link is still up, but there is no connectivity over it.

All flows going over the Non-Preferred link will continue to be bound to the Non-Preferred link until 300 seconds pass without seeing any relevant frame or if TCP ended the session related to the flow on the Non-Preferred link.

In this scenario, there is a chance that you'll have an active flow that will remain active on the Non-Preferred link after hours since the recovery of the preferred link.

[TheAlchemist]

Is there a way in Meraki events to know whether the failover was hard or soft?