SRX

Hi Team,

I have two PPPoE connections from ISPs, and I've static IP addresses to establish VPN connectivity. I'm trying to implement a failover mechanism using RPM with IP monitoring specifically, to monitor reachability to an external IP (e.g., 8.8.8.8). If this IP becomes unreachable through the primary PPPoE interface, the default route should automatically switch to the secondary ISP.

I attempted multiple configurations to track the external IP through destination interface pp0.1,  but it doesn't work, in the ppoe connection my local ip shows (171.x.x.x) and remote static ip shows (122.x.x.x), for testing purpose i had applied static route for these two ip address but doesn't work, probe-result shows "internal error" and 100% loss however, when I test RPM with a local IP on the same subnet as the interface, it works fine. I tried pinging external ip with source ip specified in the RPM and it does work. 

Please refer to the configuration snippet below and advise if any modifications are needed or suggest an alternative approach to achieve reliable route failover based on internet reachability, i had tried qualified next hop to switchover on secondary isp however many time ppoe interfaces are up but due to other issues from isp end we couldn't have internet hence trying RPM method to have appropriate failover..

set services rpm probe failover test failoverto target address 8.8.8.8

set services rpm probe failover test failoverto probe-count 5

set services rpm probe failover test failoverto probe-interval 10

set services rpm probe failover test failoverto test-interval 10

set services rpm probe failover test failoverto thresholds successive-loss 10

set services rpm probe failover test failoverto destination-interface pp0.1 (doesn't work even if i removed this)

set services rpm probe failover test failoverto hardware-timestamp

set services rpm probe failover test failoverto next-hop 122.x.x.x (Tried with local ppoe ip, remote ip, external ip but doesn't work)

set services rpm probe failover test failoverto source-address 171.x.x.x (Tried with ppoe local & remote ip but doesn't work)

"I tried pinging external ip with source ip specified in the RPM and it does work. "   <---   Did you mean "doesn't"? If it works, why not use that?

In general, source-address should be the IP address of pp0.1, and when the connection is working normally, say "show route 8.8.8.8" and put whatever the active next-hop is into the RPM next-hop.

Hi Team,

I have two PPPoE connections from ISPs, and I've static IP addresses to establish VPN connectivity. I'm trying to implement a failover mechanism using RPM with IP monitoring specifically, to monitor reachability to an external IP (e.g., 8.8.8.8). If this IP becomes unreachable through the primary PPPoE interface, the default route should automatically switch to the secondary ISP.

I attempted multiple configurations to track the external IP through destination interface pp0.1,  but it doesn't work, in the ppoe connection my local ip shows (171.x.x.x) and remote static ip shows (122.x.x.x), for testing purpose i had applied static route for these two ip address but doesn't work, probe-result shows "internal error" and 100% loss however, when I test RPM with a local IP on the same subnet as the interface, it works fine. I tried pinging external ip with source ip specified in the RPM and it does work. 

Please refer to the configuration snippet below and advise if any modifications are needed or suggest an alternative approach to achieve reliable route failover based on internet reachability, i had tried qualified next hop to switchover on secondary isp however many time ppoe interfaces are up but due to other issues from isp end we couldn't have internet hence trying RPM method to have appropriate failover..

set services rpm probe failover test failoverto target address 8.8.8.8

set services rpm probe failover test failoverto probe-count 5

set services rpm probe failover test failoverto probe-interval 10

set services rpm probe failover test failoverto test-interval 10

set services rpm probe failover test failoverto thresholds successive-loss 10

set services rpm probe failover test failoverto destination-interface pp0.1 (doesn't work even if i removed this)

set services rpm probe failover test failoverto hardware-timestamp

set services rpm probe failover test failoverto next-hop 122.x.x.x (Tried with local ppoe ip, remote ip, external ip but doesn't work)

set services rpm probe failover test failoverto source-address 171.x.x.x (Tried with ppoe local & remote ip but doesn't work)

Many thank you for your assistance. After some troubleshooting, I found that removing the command delete services rpm probe failover test failoverto hardware-timestamp resolved the issue and the configuration started working.

"I tried pinging external ip with source ip specified in the RPM and it does work. "   <---   Did you mean "doesn't"? If it works, why not use that?

In general, source-address should be the IP address of pp0.1, and when the connection is working normally, say "show route 8.8.8.8" and put whatever the active next-hop is into the RPM next-hop.

Hi Team,

I have two PPPoE connections from ISPs, and I've static IP addresses to establish VPN connectivity. I'm trying to implement a failover mechanism using RPM with IP monitoring specifically, to monitor reachability to an external IP (e.g., 8.8.8.8). If this IP becomes unreachable through the primary PPPoE interface, the default route should automatically switch to the secondary ISP.

I attempted multiple configurations to track the external IP through destination interface pp0.1,  but it doesn't work, in the ppoe connection my local ip shows (171.x.x.x) and remote static ip shows (122.x.x.x), for testing purpose i had applied static route for these two ip address but doesn't work, probe-result shows "internal error" and 100% loss however, when I test RPM with a local IP on the same subnet as the interface, it works fine. I tried pinging external ip with source ip specified in the RPM and it does work. 

Please refer to the configuration snippet below and advise if any modifications are needed or suggest an alternative approach to achieve reliable route failover based on internet reachability, i had tried qualified next hop to switchover on secondary isp however many time ppoe interfaces are up but due to other issues from isp end we couldn't have internet hence trying RPM method to have appropriate failover..

set services rpm probe failover test failoverto target address 8.8.8.8

set services rpm probe failover test failoverto probe-count 5

set services rpm probe failover test failoverto probe-interval 10

set services rpm probe failover test failoverto test-interval 10

set services rpm probe failover test failoverto thresholds successive-loss 10

set services rpm probe failover test failoverto destination-interface pp0.1 (doesn't work even if i removed this)

set services rpm probe failover test failoverto hardware-timestamp

set services rpm probe failover test failoverto next-hop 122.x.x.x (Tried with local ppoe ip, remote ip, external ip but doesn't work)

set services rpm probe failover test failoverto source-address 171.x.x.x (Tried with ppoe local & remote ip but doesn't work)