From: MICHAEL J. KILPATRICK (mjkilpat@xxxxxxxxxxx)
Date: Sun May 19 2002 - 22:33:06 GMT-3
It's been over an hour now... why won't this route age out?
R2-#show ip route 0.0.0.0
Routing entry for 0.0.0.0/0, supernet
Known via "rip", distance 120, metric 2, candidate default path
Redistributing via rip
Last update from 192.168.0.66 on Serial0.402, 01:09:09 ago
Routing Descriptor Blocks:
* 192.168.0.66, from 192.168.0.66, 01:09:09 ago, via Serial0.402
Route metric is 2, traffic share count is 1
>>> "Michael Kilpatrick" <mjkilpat@yahoo.com> 05/19/02 20:15 PM >>>
Can someone please explain why this default route on R2 never died....
R1 --- RIP --- R2 (default-information originate)
At first R1 was not seeing default route as expected. Then I noticed I had
split-horizon disabled on R1. This was causing the following:
R2-(config)#router rip
R2-(config-router)#default-information originate
Mar 1 03:30:11.791: %SYS-5-CONFIG_I: Configured from console by console
Mar 1 03:30:12.067: RIP: sending v1 flash update to 255.255.255.255 via
Serial0.402 (192.168.0.65)
Mar 1 03:30:12.067: RIP: build flash update entries
Mar 1 03:30:12.071: subnet 0.0.0.0 metric 1
Mar 1 03:30:12.223: RIP: received v1 update from 192.168.0.66 on Serial0.402
Mar 1 03:30:12.223: 192.168.0.64 in 1 hops
Mar 1 03:30:12.227: 0.0.0.0 in 2 hops
Mar 1 03:30:14.247: RIP: sending v1 update to 255.255.255.255 via Serial0.402
(192.168.0.65)
Mar 1 03:30:14.247: RIP: build update entries - suppressing null update
Notice that immediately after R2 advertises 0.0.0.0, it learns it back from R1
(remember split-horizin diabled on R1). Now R2 sees 0.0.0.0 coming from R1...
and because split-horizon is enabled on R2, it ceases the correct
avertisements to R1. R2 also puts an 0.0.0.0 entry pointing to R1 in its
routing table. The route evntually ages out on R1 however the R2 0.0.0.0
route never does. Even after I fixed the problem on R1...
R1-(config)#int s 4/0
R1-(config-if)#ip split-horizon
Even after 9 minutes. Why doesn't the route ever age out?
R2-#show ip route 0.0.0.0
Routing entry for 0.0.0.0/0, supernet
Known via "rip", distance 120, metric 2, candidate default path
Redistributing via rip
Last update from 192.168.0.66 on Serial0.402, 00:09:19 ago
Routing Descriptor Blocks:
* 192.168.0.66, from 192.168.0.66, 00:09:19 ago, via Serial0.402
Route metric is 2, traffic share count is 1
I did a clear ip route * on R2 on all is well... but shouldn't the bad
information age out on its own..... (I have the RIP timers set for 7 14 21
28, but I don't see how that would be causing this.)
Thanks. Mike
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:59:01 GMT-3