ISP Redundancy and Pushing Policy when Failed over to a Secondary ISP

[PhoneBoy]

I know this question has been brought up in the past on the community and figured, since @Tomer_Noy mentioned internally, I'd share it here.

Starting from R81.20 and in R81.10 JHF 79 and above, an enhancement was added so that for gateways with ISP redundancy, the Management will try to use the secondary interface (and IP) in policy installation if the primary IP is unreachable.
Here is the exact reference:

This doesn’t cover all Management capabilities (such as monitoring and more), but for the “mission critical” policy installation it can be very helpful.

This doesn’t require changing the object’s IP or using DAIP.

[D_TK]

Yep, and to add on to that, it works great.  Organically we find ourselves on the secondary links often, and pushing policy has worked since that RFE was done years ago.  It would really be great to get monitoring / status to work as well as sometimes we can be on the secondary link for weeks if the fiber outage is unreachable (like under a freeway).  I requested this on the RFE page earlier this year, haven't received a response yet.

[PhoneBoy]

Under a freeway?
That might make it tough to fix, especially if they didn't provide a way to actually get at it in case of a fault.

Understand the issue with monitoring status.

[D_TK]

Yep, it was about a month long outage, and thankfully the secondary link performed perfected.  In southern cal, at&t actually had to shut down the 405 south to do the repair..

[the_rock]

I laughed a little when I read that, cause I heard funny stories about both 405 and AT&T even 10+ years ago. Luckily, I only experienced 405, was nice 🙂

[the_rock]

Tx for that!