3.6 Reliable Static Routing with Enhanced Object Tracking


I believe I have configured task 3.6 correctly (my config matches up with the solution) but I am not seeing R4 fail over to the frame connection correctly when the tracked object stops responding.

I do see the static route pointing out the ethernet interface get removed and the static route with AD=2 pointing out the FR interface is installed into the routing table:


Rack1R4#debug ip routing


*Mar  1 06:25:19.606: %TRACKING-5-STATE: 1 rtr 1 state Up->Down


*Mar  1 06:25:19.606: RT: del via, static metric [1/0]

*Mar  1 06:25:19.610: RT: delete subnet route to

*Mar  1 06:25:19.614: RT: NET-RED

*Mar  1 06:25:19.618: RT: add via, static metric [2/0]

*Mar  1 06:25:19.622: RT: NET-RED

But at this point I can't ping R1's loopback even though I am supposed to be able to.

Rack1R4#debug ip packet

*Mar  1 06:29:30.578: IP: tableid=0, s= (local), d= (FastEthernet0/1), routed via FIB

*Mar  1 06:29:30.582: IP: s= (local), d= (FastEthernet0/1), len 100, sending.

So, even though it is sourcing the ping correctly from the serial interface's IP address, it is still trying to send it out the fa0/1 interface. Am I reading that right? Does anyone know why this is?


If I do a quick 'shut' and 'no shut' on the fa0/1 interface, that fixes it:

Rack1R4#debug ip pack

IP packet debugging is on


Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to, timeout is 2 seconds:


Success rate is 100 percent (5/5), round-trip min/avg/max = 20/32/40 ms


*Mar  1 06:31:16.634: IP: tableid=0, s= (local), d= (Serial0/0.1), routed via FIB

*Mar  1 06:31:16.638: IP: s= (local), d= (Serial0/0.1), len 100, sending

*Mar  1 06:31:16.666: IP: tableid=0, s= (Serial0/0.1), d= (Serial0/0.1), routed via RIB

*Mar  1 06:31:16.670: IP: s= (Serial0/0.1), d= (Serial0/0.1), len 100, rcvd 3



Sign In or Register to comment.