Original subtitles

Okay so in this lab we need to configure static ruts to enable IP connectivity between hosts on the

left and hosts on the right as an example.

If I open up a console on P.S. 1 and try and paying 170 16 wandered to the DNS server I'm told that

the destination is unreachable IP config slash all shows us that this P.C. has this IP address configured

and it's a DCP server and a default gateway 0 1 9 2 1 6 8 1 2 5 4 if that device is right of 1 and we

can verify that by using the command show IP interface brief notice of the IP address on gigabyte 0

0 0 now in this topology IP addresses are not shown.

So I'm going to add IP addresses to the topology to make it easier to configure the study grants.

We can see that as this interface is configured to with this IP address show IP run it will also show

us some early information including of the subnet mosques used on interfaces as an example we can see

that a slash 24 network is used on gigabit.

0 0 0.

As shown here and this is the IP address configured on that interface you could simply use a show run

to see that information as well.

Notice this IP address is configured on gigabit 0 0 0 and this IP address is configured on gigabit 0

0 1 so 1 9 2 1 6 8 2 that one is configured on that interface again as shown here.

Don't always rely on show run.

Learn to use other commands such as Show ip route and learn to interpret the output of the commands

we can see that the surround is directly connected to gigabit.

0 0 1 as shown there.

This is the IP address configured on that interface.

Notice also that no static runs or any other rots except to connected and local routes are displayed

in the routing table show IP protocol shows us that no routing protocols are enabled on Route 1.

We can do something similar on brought it to

show IP interface brief.

Shows us the IP addresses configured on interfaces.

Show ip route shows us the routing table.

No static routes are configured on the router no IP routing protocols or enabled.

We only see connected and local roots in the routing table.

So show ip route once again we can see that this IP address is configured on gigabit.

0 0 0 so 1 9 2 1 6 8 2 or 2 is configured on that interface as shown here.

There's the IP address there's the mask used.

This is derived from the IP address configured on the interface so that this IP address is configured

on gigabit.

0 0 0 slash 24 mosque.

So hence in the IP routing table we see this as a connected route.

This is the actual IP address configured on that interface.

Same as shown here we can see the actual IP address and the subnet mask used on this interface so 1

9 2 1 6 8 3 dot 1 slash 24 is the IP address configured on that interface and to confirm that when we

type show run we can see the IP address and subnet mask on the interface let's have a look at what a

3 interfaces have come up on broader 3 show IP interface brief we can see that this IP address is configured

on gigabit 0 0 0 that's already shown in the topology diagram of this IP address is configured on this

interface show ip route confirms that this IP address is configured on this interface that's the subnet

mosque so 1 9 2 1 6 8 3 dot to slash 24 is configured on this interface OK so looking at the routing

tables once again a one only knows about directly connected routes it doesn't know about this network

or this network notice of the server is in the same subnet as a broader 3 Cisco dot com

is also using an IP address in that subnet.

So this is most likely configured as a layer to switch even though it says call to hear when I type

show run we can see that no configuration is configured on the switch apart from an IP address which

is actually incorrect for this lab but one effect of what we trying to accomplish here.

So wrought one only has direct connected and local roots in the routing table.

The same is true for Roddick too as well as Roger three.

We only have connected and local roots in the routing table.

So en route to one we need to configure a static route for every network.

That's not directly connected.

In other words we need to create a static grant for this network as well as this network.

So ip route 1 9 2 1 6 8 3 0 subnet mask will be this.

We've already determined that when we look to add to the IP addresses and routes on the routers.

But once again show ip route shows us the route on rather three.

Now what is the next hop or outgoing interface.

We've been told to use next top IP addresses.

So rather than using the local outgoing interface we going to specify the next top which is 1 9 2 1

6 8 2 to 2 from right one's perspective to get to this network.

It needs to center the traffic to product 2 so as traffic is sent out of this interface the next IP

address that it's going to hit is this IP address.

That's the next hop IP address.

Now we could have specified minister of distance.

We are not asked to do that in this lab.

So I'm not going to configure an admin distance.

Notice how the routing table has been updated.

This round has been added to the routing table.

It's a static round.

This network is available via this next hop broader administer.

Distance is one.

The cost to get there is zero static grants to next top IP addresses have an admin distance or administrative

distance of one such as this point I should be able to ping this IP address on Rider 2 which I can but

I won't be able to ping this IP address because Rider 3 doesn't know how to send the traffic back to

write a one right 2 can reply because of this network is directly connected router to knows about this

network so it can reply back to pings sent from our one when our 1 pings 1 9 2 1 6 8 3 dot 1 it uses

the outgoing interface as the source IP address.

In other words this will be the source IP address for traffic sent from router 1 to run it to and brought

it to knows how to get back to the site the address so pings succeed but they don't succeed.

Two broader three because router 3 doesn't know how to get back to this IP address.

OK so show ip route on Route 1.

We've got one static right configured.

We still need to configure the static route

170 16 1.0 0.

In other words the segment.

Now to get to that a network which once again we can see on router 3 this network 170 is 16 1.0 slash

24.

We need to center the traffic to write to Roger to install our next hop Roorda to get to that destination

network traffic sent from of 1 to any device in the subnet will firstly be sent to Roger 2.

This is the next top IP address to show IP right.

We now have two static routs in the IP routing table of router 1.

I'll save of that configuration now and write it too.

We need to do something similar at the moment or they are only connected and local runs in the running

table so IP brought 1 9 2 1 6 8 1 0 subnet mosque is a select 24 subnet mask from right at 2s point

of view to get to this network the Next Hop is right of 1.

So 1 9 2 1 6 8 2 1 from router two's point of view to get to this network.

The next stop is this IP address.

Once again we only have 1 1 2 1 6 8 2.0 and 3.0 in the writing table.

We have to add to this network via a static rot and we have to add this network via a static raft.

So IP right 170 sixteen 1.0 slash 24 Mosque Next Top will be 1 9 2 1 6 8 3 dot 2

show IP ranch.

This right now has 2 static ruts in the writing table and at this point should be able to paying 1 9

2 1 6 8 wandered 1 which it can it should be able to being 170 16 wandered 1 which it can and at this

point it should be able to ping the DNS server the DNS server is configured with Rider 3 as its default

gateway so traffic from here can get to here to there and back again.

But notice on Route 1 we still can't ping 170 16 one or two because Rider 3 doesn't know how to send

the traffic back to write a 1 if we did a trace ranch to that IP address.

Notice the traffic it gets to write it too and then we have a timeout because router 3 doesn't know

how to reply back to write a 1 traffic is not being returned to write a 1.

So the last step is to update the writing table of router 3.