2501 and RIP problems

[trevorh13]

I am writing some course notes for a short introductory course on Cisco and have ran into a problem with RIP of all things!

I have 2 Cisco 2501's linked together via a V35 DTE and V35 DCE cable. I have my routers configured as follows:-

Router One

E0 192.36.10.1 255.255.255.0
S0 192.36.11.2 255.255.255.0

S0 is running a clock rate of 56000

I have enabled RIP routing as follows:-

Router rip
network 192.36.0.0

Router two

e0 192.36.12.1 255.255.255.0
s0 192.36.11.1 255.255.255.0

Router rip
network 192.36.0.0

EAch router will see its own directly connected networks and is able to ping them. I can also ping the remote serial interface but NOT the remote e0 interface.

I have checked for things like administratively down and interface status is up in terms of hardware and protocol. Running a debug ip rip gave no results. No routes to remote networks are present in either route table and I don't understand why.

Both routers are running IOS Version 11.2(23)Release Software (fc1). CAn anyone offer me any suggestions.

 

[wybnormal]

I'll bet it trying to summerize the two IPs

Use the command

router1#debug ip rip
router1#terminal monitor

and check to see what the updates are.

You should get something like this:

4w1d: RIP: sending v2 update to 224.0.0.9 via Ethernet0 (192.168.50.1)
4w1d: 0.0.0.0/0 -> 0.0.0.0, metric 1, tag 0
4w1d: RIP: sending v2 update to 224.0.0.9 via Ethernet0 (192.168.50.1)
4w1d: 0.0.0.0/0 -> 0.0.0.0, metric 1, tag 0
4w1d: RIP: sending v2 update to 224.0.0.9 via Ethernet0 (192.168.50.1)
4w1d: 0.0.0.0/0 -> 0.0.0.0, metric 1, tag 0

it wont be exactly like this as I did not have anything talking back to the RIP box. But you get the idea.

To turn of the debug,
router1#no debug all

Dont try this on a production router under a heavy load.. you will throw the CPU utilization way up and then you mya not be able to telnet to the router and keep the connection long enough to kill it Thats a general warning about debug.. useful but somewhat dangerous.. more so when asking it to watch packets.. like debug IP packets..

Mike S
"Diplomacy; the art of saying 'nice doggie' till you can find a rock" Wynn Catlin

 

[trevorh13]

I have tried that already and no RIP updates are being broadcast by either router. (Or at least they are not visible in the terminal window) I have tried sh ip protocol and RIP timers seem to be established and counting down so I am at a loss as to where the updates are going! I can only assume that they are not being broadcast for some reason and this is why routes aren't present to my remote ethernet networks.

I have not installed the IP feature pack and am running with the IOS version that shipped with the router. Is this likely to be the problem. I know the cables are OK as the network will work if I use static routing also as I said I can ping the remote serial interface.

Any advice would be welcome. Thankyou in advance.

 

[davidarndt]

You're telling RIP that the routers are both on the same class B segment with network 192.36.0.0, while you actually have them on two separate class C networks, 192.36.10.0 and 192.36.12.0, subnet mask 255.255.255.0.

If you change your Router RIP network commands to 192.36.10.0 and 192.36.12.0 you should be ready to fly.

 

[trevorh13]

I also needed to add a network for 192.36.11.0 on each router aswell. Still got there in the end! MAny thanks to both of you for your assitance.