Access-internal RPM probe

Perform Access-internal route failover when ISPs (next-hop address) use dynamic addresses as well.

In order to perform ISP failover in a scenario where both ISPs push an access-internal route and use dynamic addresses as well (dynamic next-hop) consider using RPM with IP monitoring to perform the route failover without having to specify the next hop address in the IP monitoring policy, the following is a configuration sample:

set services rpm probe WAN test INTERNET target address 8.8.8.8

set services rpm probe WAN test INTERNET probe-count 5

set services rpm probe WAN test INTERNET probe-interval 2

set services rpm probe WAN test INTERNET test-interval 1

set services rpm probe WAN test INTERNET routing-instance <routing-instance name> <--If any

set services rpm probe WAN test INTERNET thresholds successive-loss 10

set services rpm probe WAN test INTERNET thresholds total-loss 5

set services rpm probe WAN test INTERNET destination-interface <destination-interface>

set services ip-monitoring policy WAN1 match rpm-probe WAN

set services ip-monitoring policy WAN1 then interface <interface_facing_primary_isp> disable

-----

In this case if both access-internal routes are in the same routing instance when we disable the interface of the primary ISP the other access-internal route (backup ISP) should take over.