I have 2 Cisco 1760 routers with 2 WIC-ENET interfaces each connected back to back to simulate 2 WAN connections b/w 2 remote sites. I'm running Cisco 12.4(12) IOS on them. I configured reliable static routing using Object tracking on them. When one of the interfaces fail, the other picks up like it's supposed to do. The issue I have is that if both interfaces fail, the routers start tracking on the Primary interface only if the Secondary interface comes up so even though the primary link comes up, the secondary one has to come up before it passes data on the primary link I need urgent help with this. Configuration is as on the Cisco site
ip address 172.16.x.2 255.255.0.0
ip address 144.32.x.2 255.255.0.0
ip local policy route-map MYMAP
ip route 0.0.0.0 0.0.0.0 172.16.12.1 track 123
ip route 0.0.0.0 0.0.0.x.32.8.1 254
access-list 101 permit icmp any host 184.108.40.206 echo
route-map MYMAP permit 10
match ip address 101
set ip next-hop 172.16.12.1
set interface Null0
ip sla monitor 1
type echo protocol ipIcmpEcho 220.127.116.11
ip sla monitor schedule 1 life forever start-time now
I have never tested taking both interfaces down myself, but I think it is acting the way it should, or should I say I don't think you configured it improperly. The problem is once the track goes down on primary the default route is out the secondary, the router won't know when the primary is back up.
You also have to consider that if you allow the ping reply from the secondary interface, if both interfaces are down and only secondary comes back up, the ping will succeed and the primary route will be reinstated even though the interface may still be down.
Ah, I got, create an acl denying ping reply from secondary connection, then create a static route to 18.104.22.168 towards 172.16.12.1. This will force the track ping always out primary. Make sense?
If both are down, route will be out secondary, track ping will continue to use primary route for ping, when primary comes back, the track will come back up and primary route will take over.
Are you routing to 22.214.171.124 via 126.96.36.199? Can you add a static route to 188.8.131.52 via 172.16.12.1 and post the results.
The problem appears to be routing issue. Router should install the floating static route when the tracked IP is unreachable via the primary interface. When the connectivity is restored via the primary interface the tracked route should be re-installed irrespective of whether the secondary interface is up or not. Also, ensure the tracked IP is never learnt or routed via the secondary interface under any circumstance.
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 ...