RIP2 and Default Gateways

[dennylester]

I am following the example in the "Cisco-Configuring a Gateway of Last Resort Using IP Commands" document, but am not having much luck.

I have RIP2 working and distributing routes for the locally connected subnets but I cannot get the host to distribute it's default gateway to my remote.

Before anyone asks why I am using RIP2, I have some legacy devices out there that don't support anything else all that well..

I set the ip default-network on the host router and the show ip route command lists the proper gateway of last resort, but it never makes it to the remote.

I am sure I'm missing something simple, but can't seem to nail it down.

At the moment I don't have the host and remote in the live network. They are connected via a T1 crossover cable and a pc is attached to an Ethernet port on each router.

Any suggestions would be appreciated.

Denny

[attrgautam]

Could you remove the default-netowrk (if it is there) in the host router (retain only the 0.0.0.0 Route) and check ? Can you show the RIP debug and the routing table in the remote router

[ruwhite]

"RIPv2 is supposed to redistribute default routes automatically."

Not in later versions of code.... I'm not certain when it changed, but sometime around when the RIP database went in. You must redistribute all routes, including the default, for RIP to redistribute it.

Russ.W

[dennylester]

Hello,

I've tried

Redistribute Static (on the host)

Default-information originate (on the host)

IP Default-network (on the remote)

The IP Default-Network on the remote did work, but should the default gateway ever change on the host then I would have to go in and reconfigure all of those remotes with the new IP Default-Network.

The Default-information originate with a route map setup on the host router looked like it was working. While running debug ip rip I could see 0.0.0.0 being built, but the debug ip rip on the remote never showed it coming across.

I've been fighting with this for two weeks, so I am throwing in the towel and opening a ticket with the TAC.

Thank you all for your suggestions..

Denny

[Richard Burts]

Denny

When you tried to do redistribute static did you have a default metric configured? A valid default metric is generally essential to successful redistribution.

HTH

Rick

[dennylester]

I didn't, but that was the first thing the TAC suggested I try.

Unfortunately that didn't work either..

[Richard Burts]

Denny

I do not want to replicate what the TAC is doing. But perhaps you could post the configs with the static default and the redistribute static for us to look at.

HTH

Rick

[dennylester]

The TAC was able to figure it out.

He was able to duplicate my problem in his lab and duplicated my problem.

The one command that fixed it

"NO AUTO-SUMMARY" on both routers under the Router Rip section.

Thank you all for you suggestions and help with this problem.

Now I can move on to DDR backups using floating static routes..

[Richard Burts]

Denny

Thanks for closing the loop and letting us know what the resolution of the problem was. It is very helpful in the forum when we can associate the solution with the problem that we have been looking at.

I will admit that I am surprised that no auto-summary was the solution. I will have to think a bit about why auto-summary would interfere with redistribution of the default route.

HTH

Rick

[lh]

Hi our there

I have had this problem with RIP and defaul-information originate

I tried the no-autosummary - and it didn't work :(

Though, I found a way to get it work :)

It seems that typing the command "default-information originate" does not put the 0.0.0.0/0 in the RIP database :) - sh ip rip database

if I make a "clear ip route *" the 0.0.0.0/0 get into the RIP database, and everything does function.

This was tested on ver.12.2(30) (jk8s-mz version)

Why the clear ip route is needed, I don't understand - A bug in the IOS :)

Lennart