I'm trying to monitor the availability of one tunnel, to re-route the same destination traffic into a second tunnel. The other side can't do routing protocols right now--which would solve this easily. I hoped to find a non-manual way to fail over. I read in a discussion that the SOURCE IP and destination IP have to be in a single network. The documentation didn't mention this. If that is true, essentially this is designed to test a basic /30 circuit or a "can I see my default gateway?" test. And really nothing more. Calling a zero-hop distance (same broadcast domain) a "path" monitor is stretching the word path. Routing Gateway Monitor is more appropriate. Also the documentation (copied below) says you can have eight destinations. Having that many without being able to go beyond the gateway... really limits this to ... testing my two ISPs, or three ISPs and there are so many other ways that gets accomplished in the real world. Obviously none of the REMOTE IPs of a typical VPN between corporations are going to be in the same local subnet as any IP I can assign to my firewall. Cisco's DMVPN is structured to simulate a subnet between all the ipsec endpoints. So I'm not sure if there is anything in the PA's features that would let me manipulate routes without a routing protocol. I have a second route with a lower admin cost. But it doesn't work like Cisco where a route pointed to an interface(the tunnel) becomes invalid when the interface is down. Add a monitored destination by Name. You can add up to eight monitored destinations per static route. For Source IP , select the IP address that the firewall uses in the ICMP ping to the monitored destination: If you select an interface, the firewall uses the first IP address assigned to the interface by default. If the interface has multiple IP addresses, select one. If you select D HCP (Use DHCP Client address) , the firewall uses the address that DHCP assigned to the interface.
... View more