Quantcast
Channel: SRX Services Gateway topics
Viewing all articles
Browse latest Browse all 3959

RPM probes and IP-monitoring

$
0
0

I'm having a problem with RPM probes and IP-monitoring. I have 2 ISPs and one is primary and one is my backup (separate interfaces)

 

Next hop of primary ISP: 37.66.21.3

Next hop of secondary ISP: 62.72.129.2

 

When there is an issue with the first ISP, I install a secondary default route. Initially I just had this working with one probe (I would monitor the next hop of my primary ISP) This works perfectly fine (it fails over and fails back without any issues) The problem with this setup is there could be an upstream issue in the ISP network so traffic can be black-holed. What I am trying to do to alleviate this problem is monitor 3 IPs (next-hop of ISP, Google DNS & Cloudflare)  I have read that the RPM probe config works as AND statements. E.g. if next-hop of ISP AND Google DNS AND Cloudflare are down, only then does the probe fail. This appears to be true when it comes to failing over (when all 3 of them are down, it switches to the backup ISP)

The problem is when it comes to failing back, it seems that the RPM probes work as OR statements. If any of the 3 IPs are reachable, then it fails back to the primary ISP. 

 

Below is my config, any tips appreciated.

 

 

 

set routing-options static route 0.0.0.0/0 next-hop 37.66.21.3

set services ip-monitoring policy monitor match rpm-probe isp-failover
set services ip-monitoring policy monitor then preferred-route route 0.0.0.0/0 next-hop 62.72.129.2

set services rpm probe isp-failover test probe-1-next-hop probe-type icmp-ping
set services rpm probe isp-failover test probe-1-next-hop target address 37.66.21.3
set services rpm probe isp-failover test probe-1-next-hop probe-count 15
set services rpm probe isp-failover test probe-1-next-hop probe-interval 1
set services rpm probe isp-failover test probe-1-next-hop test-interval 5
set services rpm probe isp-failover test probe-1-next-hop thresholds total-loss 15
set services rpm probe isp-failover test probe-1-next-hop next-hop 37.66.21.3

set services rpm probe isp-failover test probe-2-google probe-type icmp-ping
set services rpm probe isp-failover test probe-2-google target address 8.8.8.8
set services rpm probe isp-failover test probe-2-google probe-count 15
set services rpm probe isp-failover test probe-2-google probe-interval 1
set services rpm probe isp-failover test probe-2-google test-interval 5
set services rpm probe isp-failover test probe-2-google thresholds total-loss 15
set services rpm probe isp-failover test probe-2-google next-hop 37.66.21.3

set services rpm probe isp-failover test probe-3-cloudflare probe-type icmp-ping
set services rpm probe isp-failover test probe-3-cloudflare target address 1.1.1.1
set services rpm probe isp-failover test probe-3-cloudflare probe-count 15
set services rpm probe isp-failover test probe-3-cloudflare probe-interval 1
set services rpm probe isp-failover test probe-3-cloudflare test-interval 5
set services rpm probe isp-failover test probe-3-cloudflare thresholds total-loss 15
set services rpm probe isp-failover test probe-3-cloudflare next-hop 37.66.21.3

 


Viewing all articles
Browse latest Browse all 3959

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>