When primary line on a router fails, dialer watch causes backup to dial out. But: when there is no traffic on the line, the backup line will go eventually down (idle-timeout kicks in) - immediately after the backup line goes down dialer watch brings it up again. This will happen continuously until there is traffic or the primary line goes up. Is there way to avoid this?
But does not "connect delay" increase time without any connectivity at all? When I set connect delay to say, 120 secs, these 120 secs there will be no connectivity. And in fact, both solutions only mitigate the problem, they do not solve it.
One has to think why the dialer watch doesn't work just like "backup interface" - it is putting the backup interface to "standby mode" and only enabling it in time specified routes are not seen in routing table. Then you could use either dynamic protocol to keep the line up, or even OSPF demand circuit, to dial it only when necessary.
I've seen this problem with certain versions of code. Dialer-watch is supposed to check for the existence of the route(s) being watched if the idle-timeout is reached, and if the route is still missing the call remains up for another idle-time period.
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...