Meraki advise .When a route is configured as active while the next hop responds to ping, or active while a host responds to ping, the MX tracks the route. If the MX stops receiving ping responses for a period of time, the route will be removed from the routing table. The route is re-added when responses are received again.
I have a specific requirement where a static route is providing a route via a 2nd L3 device connected to a LAN port.
As such next hop testing will not detect if a L3 path failure occurs towards a destination using the static.
Will 'while a host responds' provide route availability and detection for a distant host that sits behind a few hops?
Specifically here I am using the static 0.0.0.0/0 via next hop on a LAN port so as to use a next hop L3 device to route to the Internet. However if that device looses internet connectivity I need the 0.0.0.0/0 static removing to allow a dynamic 0.0.0.0/0 via the MX WAN interface.
Philip a good pointer. I tried adding a static to 220.127.116.11/32 via my next hop 192.168.2.1 via LAN 3 port and testing availability to host 18.104.22.168
I then added a 2nd static route to 0.0.0.0/0 via my next hop 192.168.2.1
I checked that the static route was active via the Fortinet Firewall 192.168.2.1 and it was.
I then failed the WAN on the Fortinet to fail the 22.214.171.124 host test and the default route did not change it remained active on the Fortinet.
Not giving up but using your logic, I added a 2nd availability test onto the 0.0.0.0/0 static also to ping host 126.96.36.199
This worked when the 188.8.131.52 host test was associated with the Default static. When I failed the WAN interface on the next hop firewall the route then disappeared.
Now for the interesting bit.
So we have a static default via a 3rd party firewall and have the ability to remove the route if the test ping to 184.108.40.206 fails.
My monitored pings to 220.127.116.11 and 18.104.22.168 both failed when the static default route disappears, however Internet connectivity is maintained by my test PC plugged into MX port 3 on a separate VLAN.
So the failover for Internet connectivity via the MX WAN port instead of the next hop worked 🙂 but the CMD pings stopped. I tired an additional CMD ping to a different destination 22.214.171.124 and that responded via the route MX WAN 1 however the original pings still showed Request Timed Out and again I still have internet connectivity.
So in my mind something is not timing out on the MX ARP around 126.96.36.199 / 188.8.131.52
I rebooted MX to see if pings would return and they did.
So were 99% there but I am a little confused what is happening re the original test pings failing. p.s If I re enable the WAN port on the Fortinet the Static route becomes active again and the pings return.
Strange. What do we think is going on here is it the arp cache on the MX that's not timing out within my observation window?
Below is a test I have just performed pinging the 3 destinations. The original two that failed and the new destination to OpenDNS. The picture below is what just happened after I disconnected the Fortigate WAN. Notice the OPenDNS ping remains but the only the original destinations which were established when the Static route was active fail.
Got to be something in my mind to do with arp caches 🙂