I am trying to configure Object tracking on an interface. Currently I am tracking IP SLA, and because the primary line is bouncing (loosing LMI, and constantly going up/down state) it?s not effective. I am looking in configuring a tracked list and threshold percentage. Any suggestions what would be the best option for me in a situation when my Primary line is bouncing?
I appreciate any help in this matter.
When a serial line does not wqorkfine as it must, the best way to troubleshoot the circuit is to perform loopback tests. Loopback tests allow you to isolate pieces of the circuit, and test them separately.Refer URL
You can increase the frequency and timeout value of the IP SLA if you want. Below you can find the link that explains how to do that:
Another option to consider is using dynamic routing. Since you have a serial your dyanmic routing protocol can failover between different route options withouth the need for tracking objects.
Let me know if you need further clarification,
Appreciate your rating,
Is this Router connected to ISP or Internal WAN? Can you give me some information about the topology? What type of encapsulation your are using on the Serial?
Waiting for your feedback,
The router is connected to a CSU and which is connected to an MPLS network. Below is the config:
ip sla 10
icmp-echo 184.108.40.206 source-interface FastEthernet0
history lives-kept 2
ip sla schedule 10 life forever start-time now
ip sla 20
icmp-echo 220.127.116.11 source-interface FastEthernet1
history lives-kept 2
ip sla schedule 20 life forever start-time now
chat-script DialAccess ABORT ERROR ABORT BUSY ABORT NO "" AT+MS=V34 OK AT+DS44=0 OK ATDT\T TIMEOUT 9
modemcap entry modem:MSC=S0=8
track 100 rtr 10 reachability.
tack 200 rtr 20 reachability
description Primary Connection
ip address 172.20.254.2 255.255.255.0
service-policy output PrimaryQoS
description Secondary Connection
ip address 18.104.22.168 255.255.255.0
crypto ipsec client ezvpn ToCorpHubSecondary
service-policy output SecondaryQoS
ip route 0.0.0.0 0.0.0.0 22.214.171.124 track 100
ip route 0.0.0.0 0.0.0.0 126.96.36.199 50 track 200
ip route 188.8.131.52 255.255.255.255 FastEthernet0 172.20.254.1 permanent
ip route 184.108.40.206 255.255.255.255 FastEthernet1 220.127.116.11 50 permanent
Thank you for your help in advance.
What you can do is run EIGRP on f0 the primary interface with the remote host. THe remote host should send you a default route. Therefore, you will get the default route from the remote host with Admin distance of 90.
Also, add another static default route for the secondary connection with admin distance 190.
In the above situation, when the primary link goes down you router will no more see the primary default route via EIGRP. Therefore, it will fall back to the static default route which has admin distance 190.
When the primary links goes back up, EIGRP session will be re-established and you will receive the dynamic default route via EIGRP and your router will shift back to use the primary link.
Hope this clarifies your question,
Let me know if you have other questions as well,
I am running OSPF, and it would require a design change to run EIGRP. I am using delay statements in track. I will update you with what I find.
Can you delay the reporting of the "down" state? That way, if it comes back "up" before the delay has expired, it will never get reported.
track 1 rtr 100 reachability