- [Narrator] Now that we have our
fundamentals down for dynamic
routing, RIP routing, we know
we don't type in remote networks
like we did with static
we type in our directly connected networks,
the completely opposite way to configure it.
So looking at our network drawing here,
really not even that important cause routing
is all about me, all about the router I'm on.
So let's run out, we're gonna configure RIP
I've already removed the static and default routing
that we used so we have no routing whatsoever
let's go ahead and get RIP version two
up and running real quick on our
little internetwork.
Logging into the corp router and show ip route
just to you really quick,
Always verify your routing table
now I have just directly connected networks.
Now, the nice thing about this, if I do
show ip route connected, now this shows you
only my directly connected routes and my links
or show ip int brief as you guys know,
and now I see my network so basically
if I look at this it says this is what
you want to type in under your routing protocol.
So I'm gonna say router rip and I'm gonna type
these network numbers I see right here under
show ip interface brief without the host names,
just the classful network addresses we've discussed.
So I've got 10.0.0.0 pretty simple, class A,
and the other one's network, 172.16.0.0.
Now, in some circumstances, I would be done here
because I'm running RIP version one, done and done,
now you can see why a lot of people used RIP routing,
it can't get any easier so,
even if you typed in network this,
if I typed in as 10.10.10.0,
it would change it to 10.0.0.0, so it would say
oh I know what you mean.
So what we wanna do is run version two,
and do, as we discussed, no auto summary.
That's it, right?
So much easier.
We're basically hiring someone.
Before, we went out there, and we
did the work ourselves.
Now we're hiring someone to go out,
hey, go find the subnets.
These are the ones I want you to advertise
for me, but go find someone else's subnets,
so let's go out to San Francisco,
and do the same thing.
So I'll log into San Francisco here,
and show ip route,
and we see our directly connected network,
show ip int brief,
I kinda like either one of these when
I'm doing my routing protocols.
Always have this on the screen whether you're typing
RIP, EIG, OSPF, ISIS, whatever,
if they're on your screen, it's harder to screw up.
Here we go, router RIP, network 192.168,
in this case it's class c, type in three octets,
it's class c.
For class b, I only type in the first two octets,
and that's all I'm directly connected to.
No auto summary, version 2.
Done and done, wow, this is gettin' fun.
Let's route out to LA
and we got helmet
and then enable CISCO
show IP route, let's take a look.
Kay, we see all our networks are still there,
that's awesome, show IP int brief.
Whichever commands work for you
to help you configure your routing protocol,
router RIP, and again
192.168.20.0, right?
And network 172.16.0.0
version 2, no auto, and notice
I didn't advertise my loopbacks,
I didn't really need them.
So, I'm just doing the physical,
real, interfaces on this routing protocol.
I want to do, notice that I did make a typo
on this, did ya see that?
Network 182.
So here's how you fix that.
And, I would have found this when
we went to our verification section next.
No network, 182.168.20.0.
You probably saw that.
Network 192.168.20.0.
Okay, so you just take out the bad statement,
put in the good.
So I'm gonna go back to,
let's go back to the corp,
take a look at what we've got here.
So, show ip route.
Now, I'm gonna do another section
on the verification, I just
wanna see that it's working.
10 and 20 in these are looking good,
and notice that I have two routes
number 20, don't I, the two
serial links, let's take a quick look at our drawing.
The two serial links between Corp and LA,
RIP found them both.
It found them, they were both one hop away,
so it said oh, they are equal cost links.
So I'm gonna Load Balance.
Every routing protocol will Load Balance
automatically for equal cost paths, including RIP.
Now, they might not be equal cost paths,
one might be T3, one might be a T1 or whatever,
but RIP will see them equal because
it only looks at, as you know, hop count.
But we'll do some more verification in a minute.
The one thing I'm gonna do is use that passive command.
The last thing I wanna do is, look at this,
I go into router rip,
enter your routing protocol,
almost done here guys,
passive interface, and I'm gonna say default.
I do not recommend this, but this is a
CCENT A Objective.
I just turned off RIP on all interfaces.
RIP is running a global config, but
the process is running but it's not advertising
or receiving on any interface.
Then I'm gonna say nope, this is
this is kind of a not a good way to do this,
let me up arrow, do control A, and do a no here,
because most of my interfaces I want to advertise
my serials, right, so I wanna go to and say
passive interface, let's do this,
and I'm gonna do it just on fastEthernet 0/0
that's my LAN, I don't want RIP being sent out
and received on my fastEthernet 0/0.
Alright, so now there's no other router out there
but my serial interfaces are not passive.
So let's run out to San Francisco
and let's do our passive interface as well.
Now I can do this cause it's an objective.
Router rip, and I want to show this to you,
passive interface default.
Now, no passive-interface
s0/1/1, I believe it is,
and now I'm sending and receiving on serial 0/1/1,
but not out all my interfaces which is just F00,
I don't recommend using passive interface default,
but you will see that on the objectives.
It turns everything off, and then you
specifically choose the interfaces you want it on.
Alright, now that we have that done,
we're gonna go through a verification section next.
Alright guys, that is how hard it is to configure
a route, right?
A few commands, and then we have the passive interfaces
if you want, not sending that data out,
your LAN interfaces where there's no other routers,
but we now have RIP running on our little internetwork,
and everything is up and running.