ISP Redundancy R75.20 and cpisp_update

[jimbul]

Dear all,

I'm trying to configure ISP redundancy in a lab in primary/backup config on R75.20 splat's.

As far as i see it everything is configured correctly according to the documentation from CP, my question is, there is a lot of reference to cpisp_update scripts, which i can see on both gateways with ISP redundancy configured, but i am not clear on whether or not there is anything i need to configure within this script in order to make the redundancy work off the bat. I've read the comments, and the pdf's from CP but cannot see how it relates to a basic configuration such as the one i'm looking at.

The documentation specifies in order for this to work:

a)The script "cpisp_update" must be present (it is)

b) The gateway must be configured for dynamic IP resolution (not sure what they mean here? is this only required if you are dealing with dns for incoming service requests http, mail etc)

c) In a Primary/Backup configuration, the interface connected to the primary ISP must be defined as the Primary IP. (it is)


So far i've tested by disconnecting the primary connection, and internet access does not failover, there is a message in the tracker on the affected gateway that the link is down, but the default route appears not to be changed.

Before i troubleshoot in more depth - would be great if someone can clarify the above re cpisp_update.

Thanks for any guidance - and if you need any further info please let me know.

Cheers,

Jim

[jimbul]

I am something of a bozo: sk61692 "Troubleshooting ISP Redundancy" helped me here, should have seen it sooner.

1. there seems to be no need to fiddle with cpisp_update unless you are using site to site VPN's were you need to rearrange NAT after a failover, or other more complex scenarios (i am doing this but have yet to tackle that aspect).

2. My issue was with the hosts i was using to monitor if the links were down in the gateway object in the policy:.

Specifically:

4. ISP link > Advanced (On each link)

*Do NOT define the same object on both links.
[Doing so will cause failover to not occur.]


Thanks for reading regardless.