PBF - Best practices for Target IP Address

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

PBF - Best practices for Target IP Address

Not applicable

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,

1 REPLY 1

L4 Transporter

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

  • 1762 Views
  • 1 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!