PBF - Best practices for Target IP Address

alliance — Tue, 15 Nov 2011 15:17:10 GMT

Hello all,

When you want to failover between 2 ISP with PBF features, what are the best practices for the choice of the target IP addresses?

If we use the default gw of ISP 1 (for ISP 1 tracking) and ISP2 (for ISP2 tracking), it's sometimes possible that the default GW of ISP is still UP (LAN interface of the ISP router) whereas the ISP line is down.

So the PBF rules will fail.

Do we have to chose a public IP address for the target IP address? In this case, do we have to add a static route for that host in the VR ? Is this the best practice or does it exist a better method ?

Thanks for your feedbacks

Regards,

Re: PBF - Best practices for Target IP Address

sjamaluddin — Thu, 17 Nov 2011 17:10:49 GMT

Hello

You can monitor a public address like 4.2.2.1 and since your policy / routing through the Untrust probably allows for traffic to the Internet you should not need a specific host route for that address.

Having an IP address on the Internet - that is different from your ISP gateway is the better way (as you said)

Thanks

topic PBF - Best practices for Target IP Address in General Topics

PBF - Best practices for Target IP Address

Re: PBF - Best practices for Target IP Address