- [Voiceover] In order to perform static routing
as we've discussed, you must have a good network map.
And it has to be accurate.
By using CDP, verify your drawing.
In this case here, let's run out to the corp router
and San Francisco router and configure static routing.
In the corp router, we have the F0/0 interface,
the LAN which is 10.10.10.0
and then we have the directly connected 172.16.10
on San Francisco and corp.
Don't have to ever type that in,
we're directly connected.
On the San Francisco router, we have two LANs though,
one a logical one for 192 and 68.40
and the physical LAN, 192.68.10.
So what is the corp router not directly connected to?
That's your question.
And what you're gonna type in then,
is how to get to 192.168.40
and 192.168.10.
Let's take a look.
All right, I'm logged in to corp router,
I can do do show IP route again.
And verify what I'm directly connected to
and don't type a route to something you see in here.
Okay, so I see 172.16.10
but I'm not directly connected
to 192.168.40.0.
Using this remote mask, and how do I get there?
Well, there's a couple of different ways.
My next hop is 172.16.10.2
or I can go out my X interface, serial 0.1.1.
Either way, so I'm gonna go to,
I'll just use my next hop.
10.2, I'm 10.1.
Now watch what happens if I type 10.1, which is me.
It's gonna come back and say, hey it's me,
so fix that, okay.
So I'll just up arrow, make it my next guy.
And I'm glad it fixed that.
But wait, there's more.
So I'm gonna go ahead and add a number at the end,
and this is the administrative distance I've discussed,
the trustworthiness of the route.
So I've made it less trustworthy,
which will become important when we get to dynamic routing.
So that's how I get to 40.
And then, I'm just gonna up arrow,
I'm gonna use the same thing.
I am gonna type it out, I was gonna up arrow,
but the reason why
is just getting to 10.0, let me show you.
I'm gonna use my X interface,
and then show you the difference.
Serial 0.1.1.
It tells me right here,
172.16.10.0/30, directly connected off of
serial 0.1.1, that's my X interface then, right?
So, that's not my next hop, that's my X interface,
my interface.
I want to say, which is in my interface.
Do show IP route.
And we're gonna see now, I have my static routes,
notice the 10 network, which I used my X interface with,
shows directly connected.
The 40 network, the logical one over there,
which I used my next hop now.
They both show up as static,
but this doesn't show up as directly connected.
It says oh, you can get there by going through
your buddy 172.16.10.2.
Remember, routing is the process of just
pawning off packets to who you're directly connected
neighbor, as fast as possible.
Notice the 150/0 means I'm directly connected,
but it's a administrative distance of 150.
Let's run out to the San Francisco router.
And log in.
And let's take a look at our routing table.
Okay, and so we can see our directly connected networks
and really, I just want to get to the 10.10.10 network
at this point.
So I'm gonna say, config T.
IP route, 10.10.10.0, which uses this mask.
I can send it out my next hop interface,
which is serial, if we look at the top here,
my WAN connection to the corp,
is 172.16.10.0/30.
Directly connected off of serial 0.1.1.
Use the X interface, doesn't matter,
or my next hop.
Now again, they showed up different in the routing table.
We can see our static route up here on top,
as going to get to 10.10.10.0 network,
send it to 172.16.10.1.
We notice, when we use the X interface,
that it showed up as directly connected,
but functionally, they're gonna act the same.
I could have done a due ping.
Okay, now I got to 10.10.10.1 now.
Let's X out of here, and from the corp router,
I should be able to ping to 192.168.40.1,
which is a logical interface and then the 10.1.
Okay, looking one more time at the routing table,
all right, so at the corp router,
I just need to put in a couple more routes
to get to L.A.
IP route, 192.168., they're due's in 30 network.
And, now if we look at it,
we're going to 10.40, now I have two links to choose from.
Serial 0.0.1 or serial 1.0.
So I'll say serial 0.0.1.
Doesn't matter, or my next hop.
And the other one is 20, I'll just use the next,
my X interface on both.
And, that looks right.
Show IP route.
Okay, and now I can see 10.20.30.40,
which if I jump back out to my figure real quick,
we can see that the corp router now can get to
10 and 40 off of San Francisco,
and 30 and 20 off L.A.
Just got to run out to L.A.,
I'll go run out there and put a route to the 10 network
and to the San Francisco router, and we'll be set.
Okay, so that's how we configure the corp router,
can get to both and then to verify with a Show IP Route.
Very simple, in a small network.
Extremely hard in a larger network.