- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
08-30-2018 08:40 AM
I've configured static route path monitoring on primary ISP. When it if fails secondary ISP comes up. Do I need to configure static route path monitoring on secondary ISP for primary to come back when the circuit recovers?
Thank you
08-30-2018 11:44 AM
Hello,
You do not need to.
It will come back on its own when the monitor determines the conditions are correct.
Regards,
08-30-2018 11:44 AM
Hello,
You do not need to.
It will come back on its own when the monitor determines the conditions are correct.
Regards,
08-30-2018 11:46 AM
Thanks for the quick response.
03-11-2019 09:06 AM
What if the monitoring IP's are not within the source interface subnet range? Say for instance I monitor public dns servers like 8.8.8.8/4.2.2.2 from my source ISP interface which has a public /30. Do I need to have a seperate static routes for destination 8.8.8.8/4.2.2.2 pointing to that ISP interface next-hop?
03-11-2019 09:20 AM
Hello,
Typically, the default route handles this, but if you do not have one, then yes you will need additional static routes. The monitor IP's can be anything as long as they are reachable.
Hope that clarifies things.
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!