- [Instructor] Now that we have RIP running
on our internetwork,
it is extremely important that you can verify RIP routing.
Configuring RIP is very simple,
as you know, as I showed you.
But you have to be able to verify it.
So, I'm going to log into corp router.
Now I don't have to be in privilege mode to verify,
but I'm going to go ahead and do it.
First thing I'm going to do is show ip route.
And let's talk about this some more in detail now.
Down here at the bottom I see my RIP injected routes,
as I've already explained I have two routes to network 20,
which is off the LA router.
But first, let's take a look at this first line.
Rip, 192, 168, 10, zero.
The administrative distance is 120.
And slash, that's the metric,
so administrative distance slash metric.
120 means I'm not very trustworthy, really.
And then slash one means I'm one hop away.
Cause RIP uses a metric of hops.
So, it's saying hey, to get to network 10,
which is one hop away,
go out, my next neighbor is 172, 16, 10, two, right?
We know that's for a fact, the San Francisco router.
Which is out by serial zero one one, my exit interface.
So, I list both my next hop
and my x interface in the routing table in this case.
Under network 20 we can get there, two outs,
via 172, 16, 10, 10, and 10 six.
That's kinda cool, isn't it?
Make sure you get this up,
cause this is kinda fun.
192, 168, 20, administrative distance of 120,
each are one hop away.
And now if they weren't the same bandwidth
you wouldn't wanna use both.
But in this case RIP is seeing that
they're both only one hop away from network 20,
so, they're going to load balance.
And notice they have different exit interfaces,
different next hop, different exit interfaces.
The next command that's very important
for your studies for your ccna, show ip protocols.
I already showed you this before,
but, in this case here let's spend
a little bit more time here, it's very important.
You go back to the top here,
routing protocol is RIP,
the filters here are used if we can put
what's called a distribute list,
which is an access list that you put on your routing table
to either stop routes from coming in,
or stop them from going out.
Sending updates every 30 seconds, right?
That's what RIP does.
It sends its complete routing table out
all active interfaces every 30 seconds.
We've got our invalid, we've got out hold down
and flush timers.
And now your troubleshooting spot right here
is right underneath the redistributing RIP
default version control, send version two,
receive version two.
Notice that this is a troubleshooting spot.
Make sure all your routers are running version two.
Also, if you don't see something in your routing table
do show ip protocols
and verify all your interfaces are participating
in the RIP process.
Okay, and then we have
automatic network summarization is not in effect,
that means because I did the no auto summary
because we have a dis-contiguous network.
Maximum paths of four is awesome,
that means that I will load balance
across what RIP thinks is,
or RIP will load balance across
what it thinks is equal cause paths
up to four, out of full.
And if I don't see all my interfaces listed above that,
I'm gonna come down here to routing for networks,
and make sure my directly connected networks
are typed in correctly right there.
Notice, as a trouble shooting spot,
that my passive interface in this case
is fast ethernet zero zero.
It wasn't default, right, I just chose the one,
it was a lot less work to do it this way.
And then my next hops here.
Let's do one more command that's a lot of fun,
it really shows us a lot about RIP.
This is debug ip RIP,
this shows RIP packets as they cross the cpu.
So, let's go ahead and take a look,
now we can see some updates from LA, from 10, 10.
And then that we're sending updates.
And, this might go a little faster
for me to just be able to talk about it.
So, we have a lot of traffic this is gonna show.
We have only three routers,
so it's not gonna be a huge flood,
but it's definitely gonna give us overhead, right?
I'm gonna turn that off, and then let's go through this.
So, receive version two update from 172, 16, 10, 10
on serial zero, one, zero, that is from the LA router
saying hey, 172, 16, 10, 4 slash 30 is over here in one hop.
You can get there in one hop.
As well as 192, 168, 20.
Notice the slash notations, this is vlsm,
we're running version two.
If we were running version one this would say
172, 16, zero, zero is over here.
And that would be a problem.
Because as we've discussed,
we have dis-contiguous networking.
So, by doing this we can see
that it's advertising with this slash notation.
Now, the next line is sending version two update
to two two four zero zero nine.
That is the multi-cast address for RIP version two.
So, it's sending out my serials zero zero one,
which is 10 dot five, to San Francisco,
and we can see that hey, 10 10 10 is over here,
172, 16, 10 dot zero, 10 dot eight,
and 192, 168, 10, zero is all over here.
You can get there through me if you're getting this
its a cut and cost you one
and then to get to 192, 168, 10, zero
is a hop of two from here.
And the same thing, we're sending out
all our other serial interfaces.
Hey, so, to configure to verify RIP routing
your show ip route is pretty important
in understanding the routing table.
But show ip protocols is your ceasing objective.
Just to summarize this again,
verify your interfaces are all there,
make sure you didn't put the wrong ones
into a passive interface,
or the wrong ones are going to be under there
and that's what you have to find.
And that you're routing for the correct networks.
And you have the correct version configured on all routers.
So, that is how you troubleshoot RIP.