Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated:
1
00:00:06,000 --> 00:00:11,400
Okay so in this lab we need to configure static ruts to enable IP connectivity between hosts on the
2
00:00:11,400 --> 00:00:15,220
left and hosts on the right as an example.
3
00:00:15,220 --> 00:00:24,450
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
4
00:00:24,520 --> 00:00:34,450
the destination is unreachable IP config slash all shows us that this P.C. has this IP address configured
5
00:00:35,350 --> 00:00:47,220
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
6
00:00:47,220 --> 00:00:57,650
can verify that by using the command show IP interface brief notice of the IP address on gigabyte 0
7
00:00:57,640 --> 00:01:04,400
0 0 now in this topology IP addresses are not shown.
8
00:01:04,460 --> 00:01:12,720
So I'm going to add IP addresses to the topology to make it easier to configure the study grants.
9
00:01:12,800 --> 00:01:20,790
We can see that as this interface is configured to with this IP address show IP run it will also show
10
00:01:20,790 --> 00:01:28,110
us some early information including of the subnet mosques used on interfaces as an example we can see
11
00:01:28,110 --> 00:01:31,780
that a slash 24 network is used on gigabit.
12
00:01:31,830 --> 00:01:33,410
0 0 0.
13
00:01:33,720 --> 00:01:41,460
As shown here and this is the IP address configured on that interface you could simply use a show run
14
00:01:42,060 --> 00:01:44,300
to see that information as well.
15
00:01:44,320 --> 00:01:51,280
Notice this IP address is configured on gigabit 0 0 0 and this IP address is configured on gigabit 0
16
00:01:51,280 --> 00:02:02,460
0 1 so 1 9 2 1 6 8 2 that one is configured on that interface again as shown here.
17
00:02:02,580 --> 00:02:05,840
Don't always rely on show run.
18
00:02:05,940 --> 00:02:14,310
Learn to use other commands such as Show ip route and learn to interpret the output of the commands
19
00:02:15,290 --> 00:02:19,090
we can see that the surround is directly connected to gigabit.
20
00:02:19,130 --> 00:02:22,270
0 0 1 as shown there.
21
00:02:22,370 --> 00:02:25,970
This is the IP address configured on that interface.
22
00:02:25,970 --> 00:02:31,910
Notice also that no static runs or any other rots except to connected and local routes are displayed
23
00:02:32,240 --> 00:02:41,670
in the routing table show IP protocol shows us that no routing protocols are enabled on Route 1.
24
00:02:41,920 --> 00:02:44,350
We can do something similar on brought it to
25
00:02:48,340 --> 00:02:49,820
show IP interface brief.
26
00:02:49,960 --> 00:02:54,460
Shows us the IP addresses configured on interfaces.
27
00:02:54,460 --> 00:02:58,580
Show ip route shows us the routing table.
28
00:02:58,870 --> 00:03:05,960
No static routes are configured on the router no IP routing protocols or enabled.
29
00:03:06,030 --> 00:03:09,940
We only see connected and local roots in the routing table.
30
00:03:10,140 --> 00:03:15,540
So show ip route once again we can see that this IP address is configured on gigabit.
31
00:03:15,580 --> 00:03:28,740
0 0 0 so 1 9 2 1 6 8 2 or 2 is configured on that interface as shown here.
32
00:03:28,770 --> 00:03:32,830
There's the IP address there's the mask used.
33
00:03:33,010 --> 00:03:41,740
This is derived from the IP address configured on the interface so that this IP address is configured
34
00:03:42,040 --> 00:03:42,700
on gigabit.
35
00:03:42,700 --> 00:03:46,380
0 0 0 slash 24 mosque.
36
00:03:46,780 --> 00:03:52,690
So hence in the IP routing table we see this as a connected route.
37
00:03:52,870 --> 00:03:57,010
This is the actual IP address configured on that interface.
38
00:03:57,250 --> 00:04:06,930
Same as shown here we can see the actual IP address and the subnet mask used on this interface so 1
39
00:04:06,930 --> 00:04:16,860
9 2 1 6 8 3 dot 1 slash 24 is the IP address configured on that interface and to confirm that when we
40
00:04:16,860 --> 00:04:25,520
type show run we can see the IP address and subnet mask on the interface let's have a look at what a
41
00:04:25,520 --> 00:04:38,310
3 interfaces have come up on broader 3 show IP interface brief we can see that this IP address is configured
42
00:04:38,760 --> 00:04:47,070
on gigabit 0 0 0 that's already shown in the topology diagram of this IP address is configured on this
43
00:04:47,070 --> 00:04:56,340
interface show ip route confirms that this IP address is configured on this interface that's the subnet
44
00:04:56,340 --> 00:05:07,480
mosque so 1 9 2 1 6 8 3 dot to slash 24 is configured on this interface OK so looking at the routing
45
00:05:07,480 --> 00:05:17,410
tables once again a one only knows about directly connected routes it doesn't know about this network
46
00:05:17,740 --> 00:05:26,990
or this network notice of the server is in the same subnet as a broader 3 Cisco dot com
47
00:05:30,130 --> 00:05:34,570
is also using an IP address in that subnet.
48
00:05:34,570 --> 00:05:41,350
So this is most likely configured as a layer to switch even though it says call to hear when I type
49
00:05:41,350 --> 00:05:51,490
show run we can see that no configuration is configured on the switch apart from an IP address which
50
00:05:51,490 --> 00:05:56,410
is actually incorrect for this lab but one effect of what we trying to accomplish here.
51
00:05:58,210 --> 00:06:07,200
So wrought one only has direct connected and local roots in the routing table.
52
00:06:07,240 --> 00:06:12,490
The same is true for Roddick too as well as Roger three.
53
00:06:12,500 --> 00:06:17,430
We only have connected and local roots in the routing table.
54
00:06:17,560 --> 00:06:22,130
So en route to one we need to configure a static route for every network.
55
00:06:22,130 --> 00:06:24,650
That's not directly connected.
56
00:06:24,650 --> 00:06:30,170
In other words we need to create a static grant for this network as well as this network.
57
00:06:30,170 --> 00:06:36,430
So ip route 1 9 2 1 6 8 3 0 subnet mask will be this.
58
00:06:36,440 --> 00:06:43,960
We've already determined that when we look to add to the IP addresses and routes on the routers.
59
00:06:44,360 --> 00:06:51,810
But once again show ip route shows us the route on rather three.
60
00:06:51,900 --> 00:06:56,130
Now what is the next hop or outgoing interface.
61
00:06:56,130 --> 00:07:00,480
We've been told to use next top IP addresses.
62
00:07:00,480 --> 00:07:09,090
So rather than using the local outgoing interface we going to specify the next top which is 1 9 2 1
63
00:07:09,090 --> 00:07:15,370
6 8 2 to 2 from right one's perspective to get to this network.
64
00:07:15,390 --> 00:07:23,130
It needs to center the traffic to product 2 so as traffic is sent out of this interface the next IP
65
00:07:23,130 --> 00:07:27,690
address that it's going to hit is this IP address.
66
00:07:27,690 --> 00:07:30,300
That's the next hop IP address.
67
00:07:31,020 --> 00:07:33,250
Now we could have specified minister of distance.
68
00:07:33,750 --> 00:07:35,930
We are not asked to do that in this lab.
69
00:07:36,400 --> 00:07:40,800
So I'm not going to configure an admin distance.
70
00:07:40,800 --> 00:07:44,610
Notice how the routing table has been updated.
71
00:07:44,610 --> 00:07:47,880
This round has been added to the routing table.
72
00:07:47,940 --> 00:07:49,090
It's a static round.
73
00:07:49,560 --> 00:07:54,930
This network is available via this next hop broader administer.
74
00:07:54,930 --> 00:07:56,750
Distance is one.
75
00:07:56,910 --> 00:08:04,500
The cost to get there is zero static grants to next top IP addresses have an admin distance or administrative
76
00:08:04,500 --> 00:08:14,490
distance of one such as this point I should be able to ping this IP address on Rider 2 which I can but
77
00:08:14,490 --> 00:08:22,110
I won't be able to ping this IP address because Rider 3 doesn't know how to send the traffic back to
78
00:08:22,110 --> 00:08:35,040
write a one right 2 can reply because of this network is directly connected router to knows about this
79
00:08:35,040 --> 00:08:46,580
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
80
00:08:46,710 --> 00:08:50,690
the outgoing interface as the source IP address.
81
00:08:50,910 --> 00:08:56,430
In other words this will be the source IP address for traffic sent from router 1 to run it to and brought
82
00:08:56,430 --> 00:09:04,070
it to knows how to get back to the site the address so pings succeed but they don't succeed.
83
00:09:04,100 --> 00:09:09,480
Two broader three because router 3 doesn't know how to get back to this IP address.
84
00:09:11,370 --> 00:09:13,560
OK so show ip route on Route 1.
85
00:09:13,560 --> 00:09:15,320
We've got one static right configured.
86
00:09:15,330 --> 00:09:18,330
We still need to configure the static route
87
00:09:21,110 --> 00:09:23,300
170 16 1.0 0.
88
00:09:23,310 --> 00:09:25,400
In other words the segment.
89
00:09:25,480 --> 00:09:35,700
Now to get to that a network which once again we can see on router 3 this network 170 is 16 1.0 slash
90
00:09:35,720 --> 00:09:36,940
24.
91
00:09:37,000 --> 00:09:45,160
We need to center the traffic to write to Roger to install our next hop Roorda to get to that destination
92
00:09:45,160 --> 00:09:53,230
network traffic sent from of 1 to any device in the subnet will firstly be sent to Roger 2.
93
00:09:53,260 --> 00:09:57,730
This is the next top IP address to show IP right.
94
00:09:57,730 --> 00:10:05,230
We now have two static routs in the IP routing table of router 1.
95
00:10:05,410 --> 00:10:09,450
I'll save of that configuration now and write it too.
96
00:10:09,460 --> 00:10:15,250
We need to do something similar at the moment or they are only connected and local runs in the running
97
00:10:15,250 --> 00:10:25,810
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
98
00:10:25,810 --> 00:10:31,330
of view to get to this network the Next Hop is right of 1.
99
00:10:31,330 --> 00:10:38,210
So 1 9 2 1 6 8 2 1 from router two's point of view to get to this network.
100
00:10:38,440 --> 00:10:41,920
The next stop is this IP address.
101
00:10:41,920 --> 00:10:52,260
Once again we only have 1 1 2 1 6 8 2.0 and 3.0 in the writing table.
102
00:10:52,290 --> 00:11:01,030
We have to add to this network via a static rot and we have to add this network via a static raft.
103
00:11:01,100 --> 00:11:10,850
So IP right 170 sixteen 1.0 slash 24 Mosque Next Top will be 1 9 2 1 6 8 3 dot 2
104
00:11:14,580 --> 00:11:16,130
show IP ranch.
105
00:11:16,290 --> 00:11:23,020
This right now has 2 static ruts in the writing table and at this point should be able to paying 1 9
106
00:11:23,020 --> 00:11:31,620
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
107
00:11:31,620 --> 00:11:41,730
point it should be able to ping the DNS server the DNS server is configured with Rider 3 as its default
108
00:11:41,730 --> 00:11:47,830
gateway so traffic from here can get to here to there and back again.
109
00:11:48,000 --> 00:11:56,190
But notice on Route 1 we still can't ping 170 16 one or two because Rider 3 doesn't know how to send
110
00:11:56,310 --> 00:12:03,660
the traffic back to write a 1 if we did a trace ranch to that IP address.
111
00:12:03,740 --> 00:12:10,100
Notice the traffic it gets to write it too and then we have a timeout because router 3 doesn't know
112
00:12:10,100 --> 00:12:16,100
how to reply back to write a 1 traffic is not being returned to write a 1.
113
00:12:16,610 --> 00:12:20,960
So the last step is to update the writing table of router 3.
12351
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.
Afrikaans
Albanian
Amharic
Arabic
Armenian
Azerbaijani
Basque
Belarusian
Bengali
Bosnian
Bulgarian
Catalan
Cebuano
Chichewa
Chinese (Simplified)
Chinese (Traditional)
Corsican
Croatian
Czech
Danish
Dutch
English
Esperanto
Estonian
Finnish
French
Frisian
Galician
Georgian
German
Greek
Gujarati
Haitian Creole
Hawaiian
Hungarian
Icelandic
Indonesian
Irish
Italian
Japanese
Kazakh
Khmer
Korean
Kurdish (Kurmanji)
Kyrgyz
Lao
Latvian
Lithuanian
Luxembourgish
Macedonian
Malagasy
Malay
Maltese
Maori
Mongolian
Myanmar (Burmese)
Nepali
Norwegian
Pashto
Polish
Romanian
Russian
Samoan
Serbian
Sesotho
Shona
Sinhala
Slovak
Slovenian
Somali
Spanish
Swahili
Swedish
Tajik
Thai
Turkish
Ukrainian
Urdu
Uzbek
Vietnamese
