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?
Solved! Go to Solution.
You do not need to.
It will come back on its own when the monitor determines the conditions are correct.
What if the monitoring IP's are not within the source interface subnet range? Say for instance I monitor public dns servers like 220.127.116.11/18.104.22.168 from my source ISP interface which has a public /30. Do I need to have a seperate static routes for destination 22.214.171.124/126.96.36.199 pointing to that ISP interface next-hop?
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 Live Community as a whole!
The Live Community thanks you for your participation!