Any way to perform probing on a logical address to drive a route change?

[BigRic]

Good afternoon. I have a client who just installed a 1GB L2 connection between two offices. The firewall which routes between sites cannot keep up with the rate of the circuit so we want to make the switch the default gateway on each end and use it to route over the 1GB interface, but have a backup path to the firewall/VPN should the L2 go down. As far as I can tell, the route will only fail if the port physically drops (not logically) and I would like to be able to probe the other side of the L2 connection using IP and change the next hop to be the firewall instead, should that link drop. Cisco has a "track" feature to do this, is there an equivalent EXOS feature?

[Luke_French]

Configure flow-redirect and enable health-check for ping.

This article provides a flow redirect config and you will need to add the ping health check
https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-configure-flow-redirect

[BigRic]

Got it - thank you!

[Luke_French]

flow redirect is similar to a route map and would monitor the next hop to which traffic is sent and if it does not reply to ping it wold send it to the other next hop.

[BigRic]

Thanks. I'm not sure I understand the logic (or how to use health check on ping . Traffic is coming into the switch destined for the remote hop on the L2. If that address is not reachable, then the next hop changes to the firewall locally on the LAN (same subnet as original source).