RE: Whatta RIP!

From: Christopher M. Heffner (cheffner@xxxxxxxxxxxxxxxxxx)
Date: Thu Apr 11 2002 - 22:55:32 GMT-3


   
Leave the dubug rip turned on both routers then try to do a clear ip
route *

This will force the router to request routing updates via
255.255.255.255 and 224.0.0.9 addresses.

Make sure you see the requests going out the router and make sure you
see the other router sending the updates out.

You should then see the updates coming back to the first router.

Make sure both routers are sending and receiving the same verion of rip
either version 1 and/or version 2.

If using version 2 check to see if one of the two routers is doing
routing updates with authenication.

Take a look at the show ip protocols command for all this information.

You should also see the neighboring router listed as a gateway in the
show ip protocols command.

HTH

========================================================================
==========
Christopher M. Heffner
IMCR Course Director
Certified Cisco Systems Instructor
CCSI, CCIE, MCT, MCSE, MCNI, MCNE, CLI, PCLP, FCSE, ASE, CTT, A+
cheffner@certified-labs.net

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Jeffery S Kimes
Sent: Thursday, April 11, 2002 4:08 PM
To: ccielab@groupstudy.com
Subject: Whatta RIP!

I had an issue where I was supposed to be receiving RIP routes on a
backbone interface. I didn't believe that I was receiving them. I did
a
debug RIP and it didn't show anything coming in. Is there something
else
that I should have been looking for?

Jeff Kimes
Senior I/T Specialist
I/T Consulting & Implementation Services



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:58:06 GMT-3