The problem is that the fact that ISP1 is malfuncional is not triggering fa0 to go down. And as long as fa0 is not link down the router will still route via fa0 even if the ISP has i.e routing problems a few hops away.
Another way to solve my original problem (it has to do with multiple DMVPN clouds for redundancy) might be to configure the router to route all traffic out via ISP A/fa0 EXCEPT traffic destinated to IP 220.127.116.11(which is my secondary DMVPN cloud HUB).
This will not make outgoing internet traffic work when ISP A fails, but my main goal is actually to always reach one of my 2 DMVPN Hubs.
How will this be configured?
Lets say that fa0 is addressed 18.104.22.168 and fa1 22.214.171.124. I have a default route to 126.96.36.199.
Traffic to my primary DMVPN hub 188.8.131.52 is routed via default route and 184.108.40.206 but I want traffic destinated to my secondary DMVPN hub 220.127.116.11 to go via fa1 and 18.104.22.168.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...