Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated:
1
00:00:01,040 --> 00:00:07,139
Welcome to Jeremy’s IT Lab. This is a free,\n
2
00:00:07,139 --> 00:00:12,099
these videos, please subscribe to follow along\n
3
00:00:12,099 --> 00:00:16,589
a comment, and share the video to help spread\n
4
00:00:18,469 --> 00:00:23,929
Today we will finish our studies of OSPF for\n
5
00:00:23,929 --> 00:00:30,589
in much greater depth than RIP and EIGRP.\n
6
00:00:30,589 --> 00:00:36,299
CCIE level, you’ll see that there is much,\n
7
00:00:36,299 --> 00:00:42,359
purpose of this CCNA course we’ll finish\n
8
00:00:42,359 --> 00:00:48,100
here is exam topic 3.4, which covers OSPF.\n
9
00:00:48,100 --> 00:00:55,439
ready to take on OSPF questions on the CCNA\n
10
00:00:55,439 --> 00:01:01,309
First let’s look at what we’ll cover in\n
11
00:01:01,310 --> 00:01:05,969
These refer to the different kinds of connections\n
12
00:01:05,969 --> 00:01:13,420
influence OSPF’s behavior. Next up we will\n
13
00:01:13,420 --> 00:01:18,129
In day 2 we covered the process routers use\n
14
00:01:18,129 --> 00:01:23,298
actually look at the requirements for a successful\n
15
00:01:23,299 --> 00:01:28,850
at a few of the LSA, Link State Advertisement,\n
16
00:01:28,849 --> 00:01:34,339
be aware of a few for the CCNA. Make sure\n
17
00:01:34,340 --> 00:01:41,689
for a bonus question from Boson ExSim for\n
18
00:01:41,689 --> 00:01:45,868
Before we get into those topics I want to\n
19
00:01:45,868 --> 00:01:51,379
a little bit. In previous videos I’ve mentioned\n
20
00:01:51,379 --> 00:01:57,709
them in the past few lab videos, but let me\n
21
00:01:57,709 --> 00:02:03,780
is a virtual interface in the router. You\n
22
00:02:03,780 --> 00:02:09,669
you manually shut it down). So, this means\n
23
00:02:09,669 --> 00:02:15,238
dependent on a physical interface. Physical\n
24
00:02:15,239 --> 00:02:21,049
fail, however that can’t happen to a loopback\n
25
00:02:21,049 --> 00:02:28,079
So, it provides a consistent IP address that\n
26
00:02:28,079 --> 00:02:33,968
Sometimes you need to send traffic directly\n
27
00:02:33,968 --> 00:02:41,310
interface at the moment, and R4 receives a\n
28
00:02:41,310 --> 00:02:47,609
address of its G1/0 interface. It might forward\n
29
00:02:47,609 --> 00:02:53,260
What if R1’s G1/0 interface goes down for\n
30
00:02:53,259 --> 00:03:00,329
for R1 at 10.0.13.1, it will not be able to\n
31
00:03:00,330 --> 00:03:07,309
How about if R1 has a loopback interface,\n
32
00:03:07,308 --> 00:03:14,598
of 10.0.13.1? Even if a physical interface\n
33
00:03:14,598 --> 00:03:20,988
for R1’s loopback interface it will still\n
34
00:03:20,989 --> 00:03:25,838
why it’s a good idea to configure a loopback\n
35
00:03:25,838 --> 00:03:30,829
with an IP address that is always up, and\n
36
00:03:33,079 --> 00:03:38,340
Now let’s move on to look at the different\n
37
00:03:38,340 --> 00:03:44,088
refers to the type of connection between OSPF\n
38
00:03:44,088 --> 00:03:49,718
behaves in some ways. The most common type\n
39
00:03:49,718 --> 00:03:56,579
of course. There are three main OSPF network\n
40
00:03:56,579 --> 00:04:04,748
type, which is enabled by default on Ethernet\n
41
00:04:04,748 --> 00:04:09,019
and you don’t need to spend time learning\n
42
00:04:09,019 --> 00:04:13,799
flashcards for OSPF network types, you might\n
43
00:04:13,799 --> 00:04:21,879
the exam, that the OSPF broadcast network\n
44
00:04:21,879 --> 00:04:28,350
network type, which is enabled by default\n
45
00:04:28,350 --> 00:04:34,270
to learn PPP and HDLC in depth for the current\n
46
00:04:34,269 --> 00:04:40,909
later in this video. The last main network\n
47
00:04:40,910 --> 00:04:46,950
on Frame Relay and X.25 interfaces. Again,\n
48
00:04:46,949 --> 00:04:51,310
types for the exam, but I will include them\n
49
00:04:51,310 --> 00:04:59,180
OSPF network types. Take a look at the OSPF\n
50
00:04:59,180 --> 00:05:05,790
network type, and 3.4c mentions the Broadcast\n
51
00:05:07,490 --> 00:05:14,060
First up, the broadcast network type. As I\n
52
00:05:14,060 --> 00:05:21,189
on Ethernet and FDDI interfaces by default.\n
53
00:05:21,189 --> 00:05:25,399
and in the previous videos all of the OSPF\n
54
00:05:25,399 --> 00:05:31,019
Broadcast network type, because they are all\n
55
00:05:31,019 --> 00:05:36,389
above, these are all Ethernet connections,\n
56
00:05:36,389 --> 00:05:39,959
and therefore these connections between the\n
57
00:05:39,959 --> 00:05:46,700
type. Now let’s cover a few characteristics\n
58
00:05:46,701 --> 00:05:51,950
dynamically discover neighbors by sending\n
59
00:05:51,949 --> 00:05:58,889
the multicast address 224.0.0.5. You already\n
60
00:05:58,889 --> 00:06:04,699
you how OSPF routers become neighbors. However,\n
61
00:06:04,699 --> 00:06:09,719
neighbors like this. We won’t cover this\n
62
00:06:09,720 --> 00:06:17,990
network type you must manually configure neighbors.\n
63
00:06:17,990 --> 00:06:24,780
and BDR, backup designated router, must be\n
64
00:06:24,779 --> 00:06:32,189
the G1/0 interface of R1, R3, R4, and R5 where\n
65
00:06:32,189 --> 00:06:39,899
a DR, no BDR. Routers which aren’t the DR\n
66
00:06:39,899 --> 00:06:45,900
I’ve heard a few ways to pronounce that,\n
67
00:06:45,901 --> 00:06:53,329
at the network above. Each subnet needs a\n
68
00:06:53,329 --> 00:07:00,669
neighbors so each router becomes the DR for\n
69
00:07:00,670 --> 00:07:07,430
between R1 and R2? In the next slide I’ll\n
70
00:07:07,430 --> 00:07:17,470
say R2 is the DR. So, R1 becomes the BDR for\n
71
00:07:17,470 --> 00:07:27,180
subnet that R2, R3, R4, and R5 connect to?\n
72
00:07:27,180 --> 00:07:33,740
and then R2 and R3 become DROthers. You’re\n
73
00:07:33,740 --> 00:07:38,990
and what the purpose of the DR and BDR is.\n
74
00:07:38,990 --> 00:07:46,329
So, here’s how the DR and BDR are elected.\n
75
00:07:46,329 --> 00:07:51,969
router with the highest OSPF interface priority\n
76
00:07:51,970 --> 00:07:57,150
However, all interfaces have the same priority\n
77
00:07:57,149 --> 00:08:04,509
OSPF router IDs. The router with the highest\n
78
00:08:04,509 --> 00:08:10,430
the election becomes the DR for the subnet,\n
79
00:08:10,430 --> 00:08:16,949
default OSPF interface priority is 1 on all\n
80
00:08:16,949 --> 00:08:21,360
with the highest router ID will become the\nDR for the segment.
81
00:08:21,360 --> 00:08:29,710
Here’s some partial output from SHOW IP\n
82
00:08:29,709 --> 00:08:35,568
ID. I configured a loopback interface on each\n
83
00:08:35,568 --> 00:08:43,399
interface became the router ID. State DR,\n
84
00:08:43,399 --> 00:08:50,089
the highest router ID of the routers connected\n
85
00:08:50,089 --> 00:08:58,100
the DR. Down here the DR, R5 itself, and BDR,\n
86
00:08:58,100 --> 00:09:03,379
their router IDs and the interface IP address\nin the subnet.
87
00:09:03,379 --> 00:09:08,009
And here’s the same output for R2. The main\n
88
00:09:08,009 --> 00:09:14,990
of DROTHER. Now, what if I want to make R2\n
89
00:09:14,990 --> 00:09:19,068
see how to change the OSPF interface priority.
90
00:09:19,068 --> 00:09:24,610
The command to change the OSPF priority of\n
91
00:09:24,610 --> 00:09:33,681
by the priority, with a range of 0 to 255.\n
92
00:09:33,681 --> 00:09:40,490
a side note, if you set the OSPF interface\n
93
00:09:40,490 --> 00:09:46,720
for the subnet, no matter what. So, let’s\n
94
00:09:46,720 --> 00:09:53,800
That’s strange. R2’s state is still DROTHER,\n
95
00:09:53,799 --> 00:09:59,899
is that? It’s because the DR/BDR election\n
96
00:09:59,909 --> 00:10:05,558
about ‘preemption’ in Day 29 when we learn\n
97
00:10:05,558 --> 00:10:11,100
what ‘non-preemptive’ means is that once\n
98
00:10:11,100 --> 00:10:18,800
role until OSPF is reset, the interface fails/is\n
99
00:10:18,799 --> 00:10:24,609
idea to do in a live network, I’ll go reset\n
100
00:10:26,000 --> 00:10:33,740
So, I reset the OSPF process on R5, and you\n
101
00:10:33,740 --> 00:10:39,539
Then R2 and R4 returned to the FULL state,\n
102
00:10:39,539 --> 00:10:45,549
for that, you’ll learn soon. Then I used\n
103
00:10:45,549 --> 00:10:50,919
the neighbor state of R5’s neighbors. Look\n
104
00:10:50,919 --> 00:10:59,219
OSPF we can learn by analyzing this section.\n
105
00:10:59,220 --> 00:11:06,430
the BDR. What can we learn from that? We can\n
106
00:11:06,429 --> 00:11:14,308
becomes the new DR. Then an election is held\n
107
00:11:14,308 --> 00:11:19,299
stepped up to be the new DR, and then an election\n
108
00:11:19,299 --> 00:11:28,958
next BDR. R2 has the highest priority, 255,\n
109
00:11:28,958 --> 00:11:36,879
is a DROther, and is stable in the 2-way state.\n
110
00:11:36,879 --> 00:11:42,419
can we learn from this? We can learn that\n
111
00:11:42,419 --> 00:11:49,690
with the DR and BDR of the subnet. The neighbor\n
112
00:11:49,691 --> 00:11:55,339
gives us a hint to the purpose of the DR and\n
113
00:11:55,339 --> 00:12:01,410
But remember these two points, that the BDR\n
114
00:12:01,409 --> 00:12:06,999
even if it doesn’t have the highest priority.\n
115
00:12:06,999 --> 00:12:12,040
with other DROthers, they remain in the 2-way\nstate.
116
00:12:12,039 --> 00:12:17,778
To repeat, in the broadcast network type,\n
117
00:12:17,778 --> 00:12:24,720
with the DR and BDR of the segment. Therefore,\n
118
00:12:24,720 --> 00:12:32,500
BDR. DROthers will not exchange LSAs with\n
119
00:12:32,500 --> 00:12:37,110
routers haven’t shared LSAs with each other\n
120
00:12:37,110 --> 00:12:43,159
LSDB, but this reduces the amount of LSAs\n
121
00:12:43,159 --> 00:12:49,350
If 6 routers are connected to the same segment\n
122
00:12:49,350 --> 00:12:55,139
will end up like this. A whole lot of LSAs\n
123
00:12:58,828 --> 00:13:04,028
If routers only exchange LSAs with the DR\n
124
00:13:04,028 --> 00:13:09,639
flooding around the network is reduced. To\n
125
00:13:09,639 --> 00:13:15,610
not a big deal in most cases, but it still\n
126
00:13:15,610 --> 00:13:20,839
By the way, when routers need to send messages\n
127
00:13:20,839 --> 00:13:29,059
224.0.0.6. This is different than the OSPF\n
128
00:13:29,058 --> 00:13:36,129
Here’s a quick review of the OSPF neighbor\n
129
00:13:36,129 --> 00:13:41,188
steps involve becoming neighbors? So, when\n
130
00:13:41,188 --> 00:13:47,698
are OSPF neighbors. Connections between two\n
131
00:13:47,698 --> 00:13:54,328
only continue on to exchange LSAs and form\n
132
00:13:54,328 --> 00:14:00,000
So, to summarize, this means that the DR and\n
133
00:14:00,000 --> 00:14:06,000
in the subnet, including the DROthers. And\n
134
00:14:07,860 --> 00:14:15,690
I showed you this command, SHOW IP OSPF INTERFACE\n
135
00:14:15,690 --> 00:14:23,079
is a DROther. Notice the neighbor count on\n
136
00:14:23,078 --> 00:14:31,319
of full adjacencies, and C indicates the total\n
137
00:14:31,320 --> 00:14:39,050
with R2 and R4. But it has three total neighbors,\nR2, R4 and R5.
138
00:14:39,049 --> 00:14:46,169
For more detail, here is SHOW IP OSPF INTERFACE\n
139
00:14:46,169 --> 00:14:52,639
here, ‘Neighbor Count is 3’, that’s\n
140
00:14:52,639 --> 00:14:58,470
neighbor count is 2’, those are the neighbors\n
141
00:14:58,470 --> 00:15:06,290
it, its two adjacent neighbors are listed.\n
142
00:15:06,289 --> 00:15:09,519
enough for the Broadcast network type for\nnow, let’s move on.
143
00:15:09,519 --> 00:15:15,539
Now let’s take a look at the ‘point-to-point’\n
144
00:15:15,539 --> 00:15:22,129
between R1 and R2 to a ‘serial’ connection.\n
145
00:15:22,129 --> 00:15:26,188
connections in the next slide, but first let\n
146
00:15:26,188 --> 00:15:34,349
connection type. This network type is enabled\n
147
00:15:34,350 --> 00:15:41,629
encapsulations by default. PPP and HDLC are\n
148
00:15:41,629 --> 00:15:47,010
except they are used on serial connections.\n
149
00:15:47,010 --> 00:15:53,129
dynamically discover neighbors by sending/listening\n
150
00:15:53,129 --> 00:16:02,589
224.0.0.5. However, here’s a difference.\n
151
00:16:02,589 --> 00:16:07,420
As the network type name implies, these encapsulations\n
152
00:16:07,419 --> 00:16:14,599
between two routers. Therefore there is no\n
153
00:16:14,600 --> 00:16:19,670
will form a Full adjacency with each other,\n
154
00:16:19,669 --> 00:16:25,948
Okay, let me give a very brief overview of\n
155
00:16:25,948 --> 00:16:31,548
serial connections are an old technology which\n
156
00:16:31,548 --> 00:16:36,169
but Ethernet is much more dominant. In fact,\n
157
00:16:36,169 --> 00:16:42,539
the exam topics except for the OSPF ‘point-to-point’\n
158
00:16:42,539 --> 00:16:48,738
tested directly on knowledge of serial interfaces,\n
159
00:16:48,739 --> 00:16:53,449
This photo shows some serial interfaces and\n
160
00:16:53,448 --> 00:16:57,289
cables are different than Ethernet cables.
161
00:16:57,289 --> 00:17:03,238
To explain serial connections, I’ll show\n
162
00:17:03,239 --> 00:17:07,430
You don’t need a deep understanding of this\n
163
00:17:07,430 --> 00:17:14,828
here. First up, one side of a serial connection\n
164
00:17:14,828 --> 00:17:20,919
Equipment. The other side functions as DTE,\n
165
00:17:20,920 --> 00:17:29,039
Why is this significant? Well, on serial connections,\n
166
00:17:29,039 --> 00:17:35,389
which is the speed, of the connection. So,\n
167
00:17:35,390 --> 00:17:40,540
and therefore needs to tell R2 what speed\n
168
00:17:40,539 --> 00:17:45,310
is ‘clock rate’, and then you can see\n
169
00:17:45,310 --> 00:17:51,009
of these are in bits per second, by the way.\n
170
00:17:51,009 --> 00:17:58,710
second, aka 64 kilobits per second, added\n
171
00:17:58,710 --> 00:18:04,440
an important point. Ethernet interfaces use\n
172
00:18:04,440 --> 00:18:09,340
operating speed. Serial interfaces use the\nCLOCK RATE command.
173
00:18:09,339 --> 00:18:17,080
Let’s continue. I checked the interface\n
174
00:18:17,080 --> 00:18:24,209
encapsulation is HDLC. On Cisco routers, the\n
175
00:18:24,210 --> 00:18:32,360
is HDLC. Actually, it’s Cisco’s own version\n
176
00:18:32,359 --> 00:18:39,209
as just ‘HDLC’ in the CLI. Once again,\n
177
00:18:39,210 --> 00:18:45,190
except it’s used on serial connections.\n
178
00:18:45,190 --> 00:18:49,740
from Wikipedia. You don’t need to learn\n
179
00:18:49,740 --> 00:18:55,849
a look. One thing to note is that there is\n
180
00:18:55,849 --> 00:19:01,560
aren’t used. I mentioned the PPP encapsulation\n
181
00:19:01,560 --> 00:19:10,109
to use that encapsulation instead. Simply\n
182
00:19:10,109 --> 00:19:14,189
Note that if you change the encapsulation,\n
183
00:19:14,190 --> 00:19:19,490
will go down. If they use two different encapsulations\n
184
00:19:19,490 --> 00:19:26,460
languages, they won’t be able to communicate.\n
185
00:19:26,460 --> 00:19:32,690
see the encapsulation has changed to PPP.\n
186
00:19:34,269 --> 00:19:41,000
Here’s the configuration I did on R1. The\n
187
00:19:41,000 --> 00:19:47,230
default, so I only configured the clock rate,\n
188
00:19:47,230 --> 00:19:53,460
is on R2, with no CLOCK RATE command because\nit is the DTE end.
189
00:19:53,460 --> 00:19:57,920
Now you’re probably wondering, how can I\n
190
00:19:57,920 --> 00:20:05,450
to show you I had to recreate this connection\n
191
00:20:05,450 --> 00:20:10,160
these lectures, doesn’t handle physical,\n
192
00:20:10,160 --> 00:20:17,029
display as DCE. Anyway, the command to view\n
193
00:20:17,029 --> 00:20:26,170
ID. As you can see R1 is the DCE side, and\n
194
00:20:26,170 --> 00:20:31,750
I used the same command on R2, and you can\n
195
00:20:31,750 --> 00:20:36,309
the Tx, transmit, and Rx, receive clocks from\nR1.
196
00:20:36,309 --> 00:20:42,609
So, that’s a very basic overview of serial\n
197
00:20:42,609 --> 00:20:49,299
should know. The default encapsulation on\n
198
00:20:49,299 --> 00:20:56,169
them to use PPP encapsulation instead with\n
199
00:20:56,170 --> 00:21:01,650
the encapsulation on one side, remember to\n
200
00:21:01,650 --> 00:21:08,430
connection is DCE and the other is DTE. You\n
201
00:21:08,430 --> 00:21:15,460
DTE with this command: SHOW CONTROLLERS, followed\n
202
00:21:15,460 --> 00:21:20,950
configure the clock rate, the speed of the\n
203
00:21:20,950 --> 00:21:24,420
CLOCK RATE, followed by the clock rate in\nbits per second.
204
00:21:24,420 --> 00:21:30,170
Let’s return to the OSPF point-to-point\n
205
00:21:30,170 --> 00:21:38,000
IP OSPF NEIGHBOR on R2. Notice that R2 has\n
206
00:21:38,000 --> 00:21:43,759
BDR, or DROTHER, a dash is displayed. This\n
207
00:21:43,759 --> 00:21:48,559
doesn’t use DRs or BDRs, as I mentioned\nbefore.
208
00:21:48,559 --> 00:21:53,769
Final point on this topic, you can manually\n
209
00:21:53,769 --> 00:22:00,029
The command is IP OSPF NETWORK, followed by\n
210
00:22:00,029 --> 00:22:05,279
type that I haven’t mentioned, that is the\n
211
00:22:05,279 --> 00:22:10,000
more of a ‘sub-type’. You don’t need\n
212
00:22:10,000 --> 00:22:15,039
to do a Google search if you’re curious.\n
213
00:22:15,039 --> 00:22:20,109
type? For example, if two routers are directly\n
214
00:22:20,109 --> 00:22:26,149
diagram below, there is no need for a DR/BDR.\n
215
00:22:26,150 --> 00:22:31,460
type in this case, although you don’t have\n
216
00:22:31,460 --> 00:22:37,341
all link types. For example, a serial link\n
217
00:22:37,340 --> 00:22:42,039
is because serial links don’t support Layer\n
218
00:22:43,930 --> 00:22:50,549
Okay here’s a chart for quick review. One\n
219
00:22:50,549 --> 00:22:56,049
is that point-to-point networks use the same\n
220
00:22:56,049 --> 00:23:01,589
default Hello timer is 10 seconds and the\n
221
00:23:01,589 --> 00:23:05,490
have to learn this network type, but just\n
222
00:23:05,490 --> 00:23:12,089
type uses a default Hello timer of 30 seconds\n
223
00:23:14,450 --> 00:23:20,170
Now let’s move on to look at some requirements\n
224
00:23:20,170 --> 00:23:24,220
will become OSPF neighbors without issue,\n
225
00:23:24,220 --> 00:23:30,710
that can occur. I already mentioned some of\n
226
00:23:30,710 --> 00:23:36,090
First requirement, the area number must match\n
227
00:23:36,089 --> 00:23:43,119
We’ll use this small topology of two routers\n
228
00:23:43,119 --> 00:23:52,069
OSPF is enabled on G0/0 in area 0. However,\n
229
00:23:52,069 --> 00:23:59,269
IP OSPF NEIGHBOR on both devices, they have\n
230
00:23:59,269 --> 00:24:04,529
I changed the network command on R2 to use\n
231
00:24:06,349 --> 00:24:12,250
So, that’s the first rule. For two routers\n
232
00:24:12,250 --> 00:24:18,809
the same area. But we already covered that\n
233
00:24:18,809 --> 00:24:24,460
in the same subnet to become OSPF neighbors.\n
234
00:24:27,480 --> 00:24:33,700
Notice that R1 and R2’s G0/0 interfaces\n
235
00:24:33,700 --> 00:24:41,019
OSPF on both of the interfaces. But when I\n
236
00:24:41,019 --> 00:24:45,740
I once again configured R2’s interface in\n
237
00:24:45,750 --> 00:24:52,490
to edit the network command so that OSPF is\n
238
00:24:55,640 --> 00:25:01,620
Next up, here’s one we haven’t covered\n
239
00:25:01,619 --> 00:25:06,959
You can actually ‘shutdown’ the OSPF process\n
240
00:25:06,960 --> 00:25:12,660
OSPF operation, without removing the OSPF\n
241
00:25:12,660 --> 00:25:20,150
Here’s how to do it. From OSPF configuration\n
242
00:25:20,150 --> 00:25:25,509
a message is displayed indicating that its\n
243
00:25:25,509 --> 00:25:32,109
no neighbors are displayed in SHOW IP OSPF\n
244
00:25:32,109 --> 00:25:36,990
SHUTDOWN, A message indicates the neighbor\n
245
00:25:39,819 --> 00:25:44,490
That one won’t be a problem unless you manually\n
246
00:25:44,490 --> 00:25:50,000
not a problem. Next requirement, the OSPF\n
247
00:25:50,000 --> 00:25:56,869
Let’s see how that works. I haven’t configured\n
248
00:25:56,869 --> 00:26:01,939
configured any loopback interfaces, so each\n
249
00:26:01,940 --> 00:26:13,650
its router ID, 192.168.1.1 for R1 and 192.168.1.2\n
250
00:26:13,650 --> 00:26:18,690
router ID, the same as R1’s. As I have shown\n
251
00:26:18,690 --> 00:26:27,009
or use CLEAR IP OSPF PROCESS for the new router\n
252
00:26:27,009 --> 00:26:32,579
PROCESS. Immediately the neighbor goes down\n
253
00:26:32,579 --> 00:26:37,909
instead of the neighbor coming back up, this\n
254
00:26:37,910 --> 00:26:46,340
router-id 192.168.1.1 from 192.168.1.1 on\n
255
00:26:46,339 --> 00:26:52,549
neighbor stays down. So, let’s fix this.\n
256
00:26:52,549 --> 00:26:58,109
with NO ROUTER-ID. Note that you don’t actually\n
257
00:26:58,109 --> 00:27:06,199
the command. NO ROUTER-ID has the same effect\n
258
00:27:06,200 --> 00:27:12,930
command. This time, without having to reset\n
259
00:27:12,930 --> 00:27:21,130
to 192.168.1.2 and the neighbor comes up again.\n
260
00:27:21,130 --> 00:27:26,760
I actually didn’t expect this, but I realized\n
261
00:27:26,759 --> 00:27:31,710
at the time, so the router was free to change\n
262
00:27:33,980 --> 00:27:40,900
So, watch out for duplicate router IDs. Next\n
263
00:27:40,900 --> 00:27:46,860
match. In both of the network types we looked\n
264
00:27:46,859 --> 00:27:52,869
defaults are 10 seconds and 40 seconds. But\n
265
00:27:52,869 --> 00:27:57,259
The Hello and Dead timers are configured directly\n
266
00:27:57,259 --> 00:28:05,169
the Hello timer. IP OSPF HELLO-INTERVAL, followed\n
267
00:28:05,169 --> 00:28:12,361
Then the Dead timer. IP OSPF DEAD-INTERVAL,\n
268
00:28:12,361 --> 00:28:18,370
then goes down. Note that I changed both values,\n
269
00:28:18,369 --> 00:28:24,869
if you only change one the neighbor will still\n
270
00:28:24,869 --> 00:28:32,109
OSPF HELLO-INTERVAL and NO IP OSPF DEAD-INTERVAL\n
271
00:28:32,109 --> 00:28:35,609
Notice the method I used to return them to\n
272
00:28:35,609 --> 00:28:42,629
router ID. I didn’t have to actually specify\n
273
00:28:42,630 --> 00:28:48,290
20 to remove the commands. Anyway, now that\n
274
00:28:49,869 --> 00:28:56,750
So, remember to check the Hello and Dead intervals\n
275
00:28:56,750 --> 00:29:02,140
Next up, authentication settings must match.\n
276
00:29:02,140 --> 00:29:06,509
an OSPF password, and then the router will\n
277
00:29:06,509 --> 00:29:11,589
a matching OSPF password. Let’s take a look.
278
00:29:11,589 --> 00:29:18,990
The OSPF password is configured directly on\n
279
00:29:18,990 --> 00:29:24,130
followed by a password of ‘jeremy’. Note\n
280
00:29:24,130 --> 00:29:29,750
on the interface. The password is configured,\n
281
00:29:29,750 --> 00:29:36,559
So, I used IP OSPF AUTHENTICATION to enable\n
282
00:29:36,559 --> 00:29:42,690
down, because R1 isn’t providing R2 a matching\n
283
00:29:42,690 --> 00:29:49,269
OSPF authentication on R1 yet, so it’s not\n
284
00:29:49,269 --> 00:29:53,920
fix this we could either configure the same\n
285
00:29:53,920 --> 00:30:01,259
authentication from R2. I removed them from\n
286
00:30:01,259 --> 00:30:07,940
Okay, there are two more things to mention.\n
287
00:30:07,940 --> 00:30:14,110
interfaces must match. The IP MTU is the maximum\n
288
00:30:14,109 --> 00:30:21,000
of the interface. The default is usually 1500\n
289
00:30:21,000 --> 00:30:25,940
this requirement and the next one are special,\n
290
00:30:25,940 --> 00:30:32,980
can become OSPF neighbors, but OSPF won’t\n
291
00:30:32,980 --> 00:30:39,110
You can configure the IP MTU of an interface\n
292
00:30:39,109 --> 00:30:46,259
MTU in bytes. I changed it to 1400 on R2’s\n
293
00:30:46,259 --> 00:30:53,490
1500 on R1’s G0/0. I waited a minute and\n
294
00:30:53,490 --> 00:31:00,490
actually remained neighbors. Then I reset\n
295
00:31:00,490 --> 00:31:04,970
but no message came indicating that the neighbors\n
296
00:31:04,970 --> 00:31:11,110
neighbor table again, and it was stuck in\n
297
00:31:11,109 --> 00:31:15,949
a few more messages were displayed, and these\n
298
00:31:15,950 --> 00:31:22,830
OSPF isn’t functioning properly. I used\n
299
00:31:22,829 --> 00:31:27,220
value, and then finally R1 and R2 reached\nthe FULL state.
300
00:31:27,220 --> 00:31:32,250
So, if your OSPF neighbors are having trouble\n
301
00:31:32,250 --> 00:31:38,579
the MTU settings. Okay, last one. The OSPF\n
302
00:31:40,190 --> 00:31:45,860
So, to demonstrate this problem I configured\n
303
00:31:45,859 --> 00:31:51,529
and advertised it to R1. Then I changed the\n
304
00:31:51,529 --> 00:31:59,019
R1’s G0/0 is still using the default broadcast\n
305
00:31:59,019 --> 00:32:04,269
the neighbor went down, but then it went right\n
306
00:32:04,269 --> 00:32:10,369
FULL in SHOW IP OSPF NEIGHBOR. So what’s\n
307
00:32:10,369 --> 00:32:17,369
Here’s R1. R2 appears in the neighbor table\n
308
00:32:17,369 --> 00:32:23,459
is working fine. But look at the routing table.\n
309
00:32:23,460 --> 00:32:29,380
routing table, but it’s not. This is what\n
310
00:32:29,380 --> 00:32:33,690
match. It can be tricky to troubleshoot because\n
311
00:32:33,690 --> 00:32:37,670
like everything is working fine. Make sure\n
312
00:32:38,670 --> 00:32:44,601
Okay, I’ll leave it there. There is of course\n
313
00:32:44,601 --> 00:32:50,260
plenty for the CCNA. Make sure to remember\n
314
00:32:50,259 --> 00:32:54,700
them as a list, but make sure that if you\n
315
00:32:58,160 --> 00:33:03,190
The final topic for today’s video is LSA\n
316
00:33:03,190 --> 00:33:07,090
the exam topics list, so I’m just going\n
317
00:33:07,089 --> 00:33:12,689
overview of some basic LSA types. To do so,\n
318
00:33:12,690 --> 00:33:18,940
modified it, adding an Internet link on R4.\n
319
00:33:18,940 --> 00:33:23,779
I use DEFAULT-INFORMATION ORIGINATE to make\n
320
00:33:23,779 --> 00:33:31,910
let’s talk about LSAs. As you already know,\n
321
00:33:31,910 --> 00:33:38,680
in the same OSPF area share the same LSDB.\n
322
00:33:38,680 --> 00:33:46,070
3 you should know for the CCNA. Those are\n
323
00:33:46,069 --> 00:33:52,250
‘network LSA’. And type 5, the ‘AS external\n
324
00:33:54,130 --> 00:34:00,180
First up is type 1, the router LSA. Every\n
325
00:34:00,180 --> 00:34:07,110
LSA. The router LSA identifies the router\n
326
00:34:07,109 --> 00:34:14,398
networks attached to the router’s OSPF-activated\n
327
00:34:14,398 --> 00:34:22,009
LSA. It is generated by the DR of each ‘multi-access’\n
328
00:34:22,010 --> 00:34:28,230
is an Ethernet network using the broadcast\n
329
00:34:28,230 --> 00:34:35,570
which are attached to the multi-access network.\n
330
00:34:35,570 --> 00:34:42,429
LSA. This type of LSA is generated by ASBRs\n
331
00:34:42,429 --> 00:34:45,690
of the autonomous system, the OSPF domain.
332
00:34:45,690 --> 00:34:53,530
Here’s a look at the LSDB on R1, using the\n
333
00:34:53,530 --> 00:34:57,570
doesn’t actually matter which router I use\n
334
00:34:57,570 --> 00:35:03,360
because all routers in the area have the same\n
335
00:35:03,360 --> 00:35:10,619
a Type 1 Router LSA identifying itself. This\n
336
00:35:10,619 --> 00:35:15,250
but each of these router LSAs contains information\n
337
00:35:15,250 --> 00:35:23,869
to. Notice that there is only one Type 2 Network\n
338
00:35:23,869 --> 00:35:31,690
subnet. Even though R1, R3, and R5 are DRs\n
339
00:35:31,690 --> 00:35:37,610
are connected to the interfaces so no Type\n
340
00:35:37,610 --> 00:35:44,050
Type 5 AS-External LSA is generated by R4.\n
341
00:35:44,050 --> 00:35:49,769
with the other routers. Okay, that’s all\n
342
00:35:49,769 --> 00:35:54,119
stated in the exam topics list, but I just\n
343
00:35:54,119 --> 00:35:57,710
some of the basic LSA types you will encounter.
344
00:35:57,710 --> 00:36:04,230
I told you we were going to cover OSPF in\n
345
00:36:04,230 --> 00:36:10,240
these past three days we definitely did that.\n
346
00:36:10,239 --> 00:36:14,589
sure you understand the material in these\n
347
00:36:14,590 --> 00:36:19,240
to, and feel free to ask questions in the\n
348
00:36:19,239 --> 00:36:25,429
covered in today’s video and then move on\n
349
00:36:25,429 --> 00:36:32,179
types, focusing on the two you need to know\n
350
00:36:32,179 --> 00:36:36,109
Because Ethernet connections are dominant\n
351
00:36:36,110 --> 00:36:41,309
be using the Broadcast network type. But also\n
352
00:36:41,309 --> 00:36:46,469
and the basics of serial interfaces that I\n
353
00:36:46,469 --> 00:36:52,659
some requirements for OSPF neighbors and adjacencies.\n
354
00:36:52,659 --> 00:36:58,230
but make sure you can identify them all and\n
355
00:36:58,230 --> 00:37:05,969
the three most basic OSPF LSA types. Type\n
356
00:37:05,969 --> 00:37:11,759
And Type 5, the AS-External LSA. Make sure\n
357
00:37:11,760 --> 00:37:18,820
question from Boson ExSim for CCNA, my favorite\n
358
00:37:22,110 --> 00:37:26,990
Which option states a characteristic of the\n
359
00:37:26,989 --> 00:37:35,739
than the OSPF broadcast network type? A, DR\n
360
00:37:35,739 --> 00:37:42,929
elections are not held. C, Neighbors are dynamically\n
361
00:37:42,929 --> 00:37:50,279
discovered. Pause the video to think about\nyour answer.
362
00:37:50,280 --> 00:37:56,390
The answer is B. In the OSPF point-to-point\n
363
00:37:56,389 --> 00:38:01,969
held. C, neighbors are dynamically discovered,\n
364
00:38:01,969 --> 00:38:06,669
network type, but it is also true about the\n
365
00:38:10,670 --> 00:38:17,360
There is an OSPF broadcast network with 5\n
366
00:38:17,360 --> 00:38:25,200
interface. How many FULL OSPF adjacencies\n
367
00:38:25,199 --> 00:38:35,159
BDR. B, 2 with the DR and BDR. C, 4 with all\n
368
00:38:35,159 --> 00:38:43,000
to the segment. Pause the video to think about\nyour answer.
369
00:38:43,000 --> 00:38:48,090
The answer is C. The DR forms a FULL adjacency\n
370
00:38:48,090 --> 00:38:53,690
segment, so C is correct. It doesn’t form\n
371
00:38:53,690 --> 00:39:00,309
so B and D are incorrect. A is incorrect because\n
372
00:39:00,309 --> 00:39:06,429
neighbors, not all four. Let’s go to question\n3.
373
00:39:06,429 --> 00:39:11,960
Which of the following are requirements for\n
374
00:39:11,960 --> 00:39:21,800
A, Hello and Dead timers must match. B, OSPF\n
375
00:39:21,800 --> 00:39:31,310
must match. D, Interfaces must be in the same\n
376
00:39:31,309 --> 00:39:37,500
Or F, interfaces must be in different subnets.\n
377
00:39:42,349 --> 00:39:48,279
The answers are A and D. For two routers to\n
378
00:39:48,280 --> 00:39:54,630
timers on their interfaces must match. They\n
379
00:39:54,630 --> 00:39:59,539
here are the requirements for OSPF neighbors\n
380
00:40:02,989 --> 00:40:08,789
Which of the following OSPF LSA types is generated\n
381
00:40:08,789 --> 00:40:19,039
such as the broadcast network type? A, type\n
382
00:40:19,039 --> 00:40:25,230
the video to think about your answer.
383
00:40:25,230 --> 00:40:32,500
The answer is B, type 2. Type 2 is the ‘Network’\n
384
00:40:32,500 --> 00:40:38,710
network. It lists the routers which are attached\n
385
00:40:38,710 --> 00:40:46,731
the Router LSA type. D, Type 5, is the AS-External\n
386
00:40:46,731 --> 00:40:51,880
in this video. It’s called the ‘Summary’\n
387
00:40:53,329 --> 00:41:01,500
R1 is connected to an OSPF Broadcast network\n
388
00:41:01,500 --> 00:41:08,659
segment and R3 is the BDR. All routers on\n
389
00:41:08,659 --> 00:41:15,500
You issue the ip ospf priority 100 command\n
390
00:41:15,500 --> 00:41:20,000
the following statements are true about the\n
391
00:41:20,000 --> 00:41:30,389
two. A, R1 is the DR. B, R1 is the BDR. C,\n
392
00:41:30,389 --> 00:41:37,839
isn’t high enough. D, if you issue the clear\n
393
00:41:37,840 --> 00:41:45,480
the BDR. E, if you issue the clear ip ospf\n
394
00:41:45,480 --> 00:41:52,750
DR. And F, the DR and BDR of the network are\n
395
00:41:58,630 --> 00:42:04,970
The answers are D and F. The default OSPF\n
396
00:42:04,969 --> 00:42:11,059
entering the command R1’s G0/0 interface\n
397
00:42:11,059 --> 00:42:17,509
It’s still a DROther, but priority isn’t\n
398
00:42:17,510 --> 00:42:24,070
give up their positions, so R1 will not become\n
399
00:42:24,070 --> 00:42:31,170
and F is correct. If you issue the CLEAR IP\n
400
00:42:31,170 --> 00:42:37,869
R3, will automatically become the DR, not\n
401
00:42:37,869 --> 00:42:44,019
you issue that command, when R3 becomes the\n
402
00:42:44,019 --> 00:42:49,590
Since R1 has the highest priority, it will\n
403
00:42:49,590 --> 00:42:54,410
correct. That’s all for the quiz. Let’s\n
404
00:42:57,019 --> 00:43:05,090
Okay, here's today's Boson ExSim practice\n
405
00:43:05,090 --> 00:43:10,670
FASTETHERNET 0/1 command on Router1 and receive\n
406
00:43:10,670 --> 00:43:15,691
the command, and here's the question. Which\n
407
00:43:15,690 --> 00:43:21,299
the best answer. Okay, pause the video now.\n
408
00:43:27,380 --> 00:43:33,980
Okay, let's check. So, I believe the correct\n
409
00:43:33,989 --> 00:43:40,279
options and then I'll go on to D. First up,\n
410
00:43:40,280 --> 00:43:49,230
Well it says right here, Router1's state is\n
411
00:43:49,230 --> 00:43:55,780
connected to a point-to-multipoint network.\n
412
00:43:55,780 --> 00:44:02,960
so that's incorrect. C, Router1 is configured\n
413
00:44:02,960 --> 00:44:09,389
the timers here, they are the defaults. Also,\n
414
00:44:09,389 --> 00:44:15,259
think there is any problem with Router1's\n
415
00:44:15,260 --> 00:44:22,980
higher than 50. You can see here that Router1's\n
416
00:44:22,980 --> 00:44:28,539
BDR doesn't necessarily have a priority higher\n
417
00:44:28,539 --> 00:44:39,250
Router1, 50, but a higher router ID. So E\n
418
00:44:39,250 --> 00:44:45,760
The key to this question is knowing the difference\n
419
00:44:45,760 --> 00:44:50,220
those words are used to mean the same thing,\n
420
00:44:50,219 --> 00:44:58,919
different. Look here in the output. Neighbor\n
421
00:44:58,920 --> 00:45:05,920
So, although Router1 has 5 OSPF neighbors,\n
422
00:45:05,920 --> 00:45:13,659
in the OSPF FULL neighbor state. This number\n
423
00:45:13,659 --> 00:45:21,589
the DR and BDR, but also Router1's DROTHER\n
424
00:45:21,590 --> 00:45:28,789
the 2-way state with another DROTHER. So,\n
425
00:45:28,789 --> 00:45:35,369
OSPF broadcast network. And DROTHERs can only\n
426
00:45:35,369 --> 00:45:40,970
2 routers. So, I chose this question because\n
427
00:45:40,969 --> 00:45:49,329
between a neighbor and a full OSPF adjacency.\n
428
00:45:49,329 --> 00:45:56,599
is correct. Okay, pause the video now if you\n
429
00:45:56,599 --> 00:46:01,920
notice that it includes a reference to some\n
430
00:46:01,920 --> 00:46:07,829
INTERFACE command. And this Cisco documentation,\n
431
00:46:07,829 --> 00:46:14,170
and it's another great study resource. Okay,\n
432
00:46:14,170 --> 00:46:18,740
please follow the link in the video description.\n
433
00:46:18,739 --> 00:46:24,480
exams I used when studying for both my CCNA\n
434
00:46:24,481 --> 00:46:28,990
once again, follow that link in the video\ndescription.
435
00:46:28,989 --> 00:46:33,969
There are supplementary materials for this\n
436
00:46:33,969 --> 00:46:38,419
the software ‘Anki’. There will also be\n
437
00:46:38,420 --> 00:46:43,690
some hands-on practice. That will be in the\n
438
00:46:43,690 --> 00:46:47,349
the link in the description, and I’ll send\n
439
00:46:50,699 --> 00:46:55,790
Before finishing today’s video I want to\n
440
00:46:55,791 --> 00:46:59,289
I’ve noticed an increase in the number of\n
441
00:46:59,289 --> 00:47:05,800
all of you, both JCNA and JCNP-level members.\n
442
00:47:05,800 --> 00:47:10,300
JCNP-level members one by one, but the list\n
443
00:47:10,300 --> 00:47:16,050
list up here. Your support helps me keep making\n
444
00:47:16,050 --> 00:47:20,869
I’m really grateful for your support. This\n
445
00:47:20,869 --> 00:47:26,358
of recording by the way, August 23rd 2020,\n
446
00:47:26,358 --> 00:47:31,880
on here don’t worry, you’ll be in future\nvideos.
447
00:47:31,880 --> 00:47:36,750
Thank you for watching. Please subscribe to\n
448
00:47:36,750 --> 00:47:41,639
and share the video with anyone else studying\n
449
00:47:41,639 --> 00:47:47,440
check the links in the description. I'm also\n
450
00:47:47,440 --> 00:47:52,019
or Basic Attention Token, tips via the Brave\n
36972
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.