cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1336
Views
0
Helpful
4
Replies

Problems to track default routes on IP SLA

In my router, there is a default route with the administrative distance 1 with track 1 This route is used for an internet link. 
  0.0.0.0 0.0.0.0 172.19.4.10 

I also have 2 dialers to redundancy with the administrative distance 20 and 30 respectively. 

ip route 0.0.0.0 0.0.0.0 dialer1 20 
ip route 0.0.0.0 0.0.0.0 Dialer2 30 

When I set up a route with track and give a shutdown on subinterface, the route takes the dialer. 

But when I give a no shutdown on the port, which is the route with the track becomes more specific, but the same does not appear in the routing table.

I'm using two routes, one with and one without track the track to the same destination:

 

RTR(config)#do sh run | i ip route
ip route 0.0.0.0 0.0.0.0 172.19.4.10  track 1
ip route 0.0.0.0 0.0.0.0 Dialer1 20
ip route 0.0.0.0 0.0.0.0 Dialer2 30


RTR(config)#interface gi0/0.303
RTR(config-subif)#shut
RTR(config-subif)#do ping 8.8.8.8
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 8.8.8.8, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
RTR(config-subif)#do sh ip route
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
       ia - IS-IS inter area, * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route, + - replicated route

Gateway of last resort is 0.0.0.0 to network 0.0.0.0

S*    0.0.0.0/0 is directly connected, Dialer1

RTR(config-subif)#no shut
RTR(config-subif)#do ping 8.8.8.8

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 8.8.8.8, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
RTR(config-subif)#do sh ip route
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
       ia - IS-IS inter area, * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route, + - replicated route

Gateway of last resort is 0.0.0.0 to network 0.0.0.0

S*    0.0.0.0/0 is directly connected, Dialer1
 

RTR(config-subif)#ip route 0.0.0.0 0.0.0.0 172.19.4.10
RTR(config)#do ping 8.8.8.8

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 8.8.8.8, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 84/87/88 ms
RTR(config)#do sh run | i ip route
ip route 0.0.0.0 0.0.0.0 172.19.4.10  track 1
ip route 0.0.0.0 0.0.0.0 172.19.4.10
ip route 0.0.0.0 0.0.0.0 Dialer1 20
ip route 0.0.0.0 0.0.0.0 Dialer2 30
 

Anyone know what I have to do to solve the problem?

1 Accepted Solution

Accepted Solutions

david-swope
Level 1
Level 1

With the default route up (172.19.4.10), test connectivity to "Dialer1" and "Dialer2". These need to be reachable for obvious reasons, once we lose our tracked route and Dialer1 is placed into the routing table, it's no use if we don't have connectivity to backup route/s.

I would also recommend using higher metrics for "floating" statics. I'd personally do

ip route 0.0.0.0 0.0.0.0 172.19.4.10 track 1

ip route 0.0.0.0 0.0.0.0 Dialer1 249

ip route 0.0.0.0 0.0.0.0 Dialer2 250

 

Better practice for when you have dynamic routing protocols in place etc. Again, your floating static is doing it's job so that's not an issue, it's more of an issue as to why your device cannot reach Dialer1 or Dialer2

 

 

 

 

View solution in original post

4 Replies 4

feltinsilije
Level 1
Level 1

Hi, 

 

Please can you display configuration concern IP SLA ??

Hello, 

I'm testing the gateway Internet link of the carrier.

Below is the configuration of IP SLA:

ip sla 303 
 icmp-echo 189.40.251.174 
ip sla schedule 303 life forever start-time now
track 1 ip sla 303 

david-swope
Level 1
Level 1

With the default route up (172.19.4.10), test connectivity to "Dialer1" and "Dialer2". These need to be reachable for obvious reasons, once we lose our tracked route and Dialer1 is placed into the routing table, it's no use if we don't have connectivity to backup route/s.

I would also recommend using higher metrics for "floating" statics. I'd personally do

ip route 0.0.0.0 0.0.0.0 172.19.4.10 track 1

ip route 0.0.0.0 0.0.0.0 Dialer1 249

ip route 0.0.0.0 0.0.0.0 Dialer2 250

 

Better practice for when you have dynamic routing protocols in place etc. Again, your floating static is doing it's job so that's not an issue, it's more of an issue as to why your device cannot reach Dialer1 or Dialer2

 

 

 

 

Hello,

My dialers are not good, but would fix them at another time. My goal now is to monitor my primary internet link. 

I removed the two routes of Dialers, but the problem persists:

 

RTR#show run | i ip route
ip route 0.0.0.0 0.0.0.0 172.19.4.10 track 1
ip route 0.0.0.0 0.0.0.0 172.19.4.10
RTR#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
RTR(config)#no ip route 0.0.0.0 0.0.0.0 172.19.4.10
RTR(config)#do ping 8.8.8.8

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 8.8.8.8, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
RTR(config)#ip route 0.0.0.0 0.0.0.0 172.19.4.10
RTR(config)#do ping 8.8.8.8

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 8.8.8.8, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 8/11/16 ms

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Innovations in Cisco Full Stack Observability - A new webinar from Cisco