[AUDIO LOGO]
So now, we're going to take a look
at redistributing into RIP or Routing Information Protocol.
Now, this is, of course, not one of our main topics
from a service provider perspective.
We're generally not going to run into RIP very often,
at least I certainly hope not.
But it's still good to be familiar with it
in case you do run into a customer running RIP, maybe
as their CE-PE protocol.
Although, I doubt the service provider would support that.
But if you do support customers in a more direct fashion,
then you may, in fact, run into one that's running RIP.
So it's not going to hurt us just
to take a quick few minutes to take
a look at some of the caveats of redistributing into RIP.
And honestly, there's really only one caveat,
and that is that the default metric is infinite,
which means we have to set a metric when
we do the redistribution.
The only other thing to really note as we go through this
is that a bit like IS-IS, RIP also has no tracking mechanism
to know that this route came from an external source.
Internal and external routes are treated exactly the same way
in RIP.
So that said, we're going to look at the topology
real quickly.
We're just doing one redistribution on one router.
But let's just take a look where that is.
And then we'll jump into the command line real quick
and do that one redistribution.
So this is just going to be a quick one, but just so you're
at least familiar with being able to redistribute into RIP.
So again, this is going to be a very easy one we only
have one environment running RIP up here between router 6
and router 10.
So what we're going to be configuring
is simply router 6 to redistribute IS-IS into RIP.
And of course, we'll be looking at router 10
to see if those routes are showing up as they should.
So let's go ahead and jump into the command line.
We'll start on router 10 just to see its current routing table.
So let's do a show IP route RIP here on router 10.
And we can see that it's literally only learning
one route from RIP right now coming from router 6.
So let's go ahead and configure that redistribution now
on router 6.
So all we have to do is go into router RIP.
Say redistribute and choose our protocol.
So isis 1.
And we'll notice with RIP, there's not
a whole lot of choices here.
We can choose which ISIS routes to pull from.
So we can choose level 1, level 1-2, or 2.
We can, of course, specify the metric,
or we could use a route map, which would either be used
to filter or set the metric.
But let's just go ahead and hit Enter.
Do a simple redistribution.
And what we're going to find is if we go back to router 10,
we do our show ip route rip again,
we still don't have anything.
And if we were to do a debug ip rip,
let's just wait for an update to come in from router 6.
They're sending an update.
And there, we receive the update.
We see that that's the only route we're receiving.
This is, of course, because as we said before,
RIP uses infinite or infinity as its default metric.
Therefore, it doesn't even send the updates.
So we do have to specify a metric.
Let's go back over to router 6 and do that.
So back on router 6, we'll simply specify a metric.
Of course, it could be anything from 0 to 16.
But of course, depending on the size of your environment,
you probably want to go somewhere towards the middle,
like maybe a 5 or a 6.
So we'll go ahead and put that in there.
And then let's go back over to router 10.
So back here on router 10, let's go ahead and look at our routes
again.
And notice that we still don't have anything.
This is actually a caveat of IS-IS.
We have to tell RIP which level to pull the routes from.
Just like redistributing into IS-IS,
we're going to have to tell it where to get the routes from,
and the default is level 2.
So we're going to have to say we could either just
say level 1 here, or we could say
level 1-2 to get everything.
And now that we're doing that, now
let's see if we have routes on router 10.
So now, we can see those routes from the whole rest
of the environment coming in here on router 10.
And just to pick on one, we'll pick on this very bottom one,
the 192.168.78.0/24.
Few things to note-- number 1, there is no indicator
that it's external.
And notice that it has that metric of 5 on there,
which is the one we told it to put on
during the redistribution.
And once again, just since we have some mutual redistribution
going on, let's try some connectivity.
So we could trace, say, to that 88 address
we've been using before.
So as you can see, we have reachability
here to say the 88 network.
So generally speaking, our connectivity
appears to be working.
In this video, we saw how to do redistribution into RIP.
And the main thing, of course, to keep in mind is with RIP,
the default seed metric is infinite.
And of course, that's going to prevent it from sending routes.
So we need to specify a seed metric.
Also, in the case of redistributing from IS-IS,
don't forget we also need to specify
which level routes we wish to pull into the other protocol.
So all of that said, we now have just one more protocol to do--
EIGRP.
And that's exactly what we're going to be doing next.
Until then.
I hope this has been informative for you,
and I'd like to thank you for viewing.