1
00:00:02,468 --> 00:00:05,051
(gentle music)

2
00:00:08,872 --> 00:00:11,070
- Let's go into a little bit
more detail now about OSPF

3
00:00:11,070 --> 00:00:14,231
by looking at the different
kinds of OSPF packets,

4
00:00:14,231 --> 00:00:17,564
what they're used for and their purpose.

5
00:00:18,856 --> 00:00:20,748
So like EIGRP...

6
00:00:20,748 --> 00:00:22,946
how EIGRP had specific packets

7
00:00:22,946 --> 00:00:26,296
do certain things like
the Hello, the Update,

8
00:00:26,296 --> 00:00:28,249
the Query, and the Reply,

9
00:00:28,249 --> 00:00:30,761
OSPF also has specific packet types.

10
00:00:30,761 --> 00:00:32,672
We have the OSPF Hello,

11
00:00:32,672 --> 00:00:34,747
and just like you could
guess that's used to

12
00:00:34,747 --> 00:00:37,053
dynamically discover OSPF neighbors,

13
00:00:37,053 --> 00:00:40,328
and to maintain OSPF
neighbor relationships,

14
00:00:40,328 --> 00:00:42,316
what we call adjacencies.

15
00:00:42,316 --> 00:00:43,631
Then we also have these other packets,

16
00:00:43,631 --> 00:00:45,094
which are used in the process

17
00:00:45,094 --> 00:00:46,692
of building a neighbor relationship:

18
00:00:46,692 --> 00:00:50,868
the Database Descriptor
and the Link State Request.

19
00:00:50,868 --> 00:00:52,834
So the Database Descriptor
and the Link State Request,

20
00:00:52,834 --> 00:00:54,913
you will only see those when a

21
00:00:54,913 --> 00:00:58,513
neighbor relationship is
very first being built.

22
00:00:58,513 --> 00:01:02,002
After that neighbor relationship
is up and maintained,

23
00:01:02,002 --> 00:01:03,803
you won't see those again.

24
00:01:03,803 --> 00:01:06,219
And then you also have
the Link State Update,

25
00:01:06,219 --> 00:01:08,478
and the Link State Acknowledgement packet.

26
00:01:08,478 --> 00:01:12,737
And the vast majority of
those are sent as multicasts.

27
00:01:12,737 --> 00:01:14,585
So I'm going to come back
to those in just a moment,

28
00:01:14,585 --> 00:01:16,265
to talk about how they are used,

29
00:01:16,265 --> 00:01:18,805
and during what process they're used.

30
00:01:18,805 --> 00:01:20,472
We will get to that.

31
00:01:22,192 --> 00:01:24,270
So just like with EIGRP,

32
00:01:24,270 --> 00:01:25,832
how there were certain things during the

33
00:01:25,832 --> 00:01:29,598
Hello packet exchange that
had to match with EIGRP,

34
00:01:29,598 --> 00:01:31,446
here you can see there
are also certain things

35
00:01:31,446 --> 00:01:35,502
that need to match for an
OSPF adjacency to fully form.

36
00:01:35,502 --> 00:01:37,183
So number one, the timers,

37
00:01:37,183 --> 00:01:38,915
the Hello and the dead interval,

38
00:01:38,915 --> 00:01:40,266
they have to match.

39
00:01:40,266 --> 00:01:42,222
This is different than EIGRP.

40
00:01:42,222 --> 00:01:45,227
In EIGRP, we could exchange Hello packets,

41
00:01:45,227 --> 00:01:47,363
and my Hello packet to you might say,

42
00:01:47,363 --> 00:01:50,396
hey, if you don't hear from
me within five minutes,

43
00:01:50,396 --> 00:01:52,311
declare me to be dead.

44
00:01:52,311 --> 00:01:54,102
And your Hello packet to me might be,

45
00:01:54,102 --> 00:01:56,475
hey Keith, if you don't
hear from within 30 seconds,

46
00:01:56,475 --> 00:01:58,300
declare me to be dead.

47
00:01:58,300 --> 00:01:59,133
That would be fine.

48
00:01:59,133 --> 00:02:01,368
As long as we set our
expectations appropriately,

49
00:02:01,368 --> 00:02:02,799
we'd be okay.

50
00:02:02,799 --> 00:02:06,466
With OSPF, those timers
have to be the same.

51
00:02:07,505 --> 00:02:10,123
Authentication, which as I
mentioned in an earlier video,

52
00:02:10,123 --> 00:02:11,290
is optional.

53
00:02:11,290 --> 00:02:13,043
But if you are doing authentication,

54
00:02:13,043 --> 00:02:15,755
the type of authentication
has to be the same

55
00:02:15,755 --> 00:02:17,113
because you and I could either

56
00:02:17,113 --> 00:02:18,729
exchange clear text passwords,

57
00:02:18,729 --> 00:02:21,412
or we could exchange
passwords that are hashed

58
00:02:21,412 --> 00:02:24,038
with a message digest formula.

59
00:02:24,038 --> 00:02:25,984
So, the type has to be the same,

60
00:02:25,984 --> 00:02:28,330
and clearly whatever the password is,

61
00:02:28,330 --> 00:02:30,609
has to be the same as well.

62
00:02:30,609 --> 00:02:31,864
The Area - ID.

63
00:02:31,864 --> 00:02:34,987
So you and I share this common
link, this common cable.

64
00:02:34,987 --> 00:02:37,995
If in my network statement
that covers this cable,

65
00:02:37,995 --> 00:02:40,307
I believe this is an area one,

66
00:02:40,307 --> 00:02:43,219
you also need to believe
this is an area one.

67
00:02:43,219 --> 00:02:45,575
If I get a Hello packet from you,

68
00:02:45,575 --> 00:02:48,586
indicating that you think
this link is an area 50,

69
00:02:48,586 --> 00:02:50,107
and I think it's an area one,

70
00:02:50,107 --> 00:02:51,757
that's going to be a problem.

71
00:02:51,757 --> 00:02:55,621
We will not form a neighbor
relationship in that case.

72
00:02:55,621 --> 00:02:57,101
The Prefix-length.

73
00:02:57,101 --> 00:02:59,637
So this is also a little
bit different than EIGRP.

74
00:02:59,637 --> 00:03:04,386
So in EIGRP, let's say I send
you an EIGRP Hello packet,

75
00:03:04,386 --> 00:03:05,219
and...

76
00:03:06,249 --> 00:03:08,666
let's say it was like this...

77
00:03:12,000 --> 00:03:15,250
So here comes in an EIGRP Hello packet.

78
00:03:17,175 --> 00:03:18,175
EIGRP Hello.

79
00:03:23,110 --> 00:03:26,610
And let's say the source of that packet...

80
00:03:27,560 --> 00:03:28,393
Was...

81
00:03:32,538 --> 00:03:33,371
1.1.1.1.

82
00:03:36,513 --> 00:03:39,305
Okay, that was a source IP address.

83
00:03:39,305 --> 00:03:40,631
And the router that's receiving

84
00:03:40,631 --> 00:03:43,891
that packet on this interface,

85
00:03:43,891 --> 00:03:46,974
his address is 1.1.1.9/...

86
00:03:54,051 --> 00:03:54,884
29.

87
00:03:57,643 --> 00:04:01,810
Would he say this source is in
the same network as himself?

88
00:04:04,834 --> 00:04:08,551
Hopefully, your answer
was no because 1.1.1.9,

89
00:04:08,551 --> 00:04:10,100
that's a host address.

90
00:04:10,100 --> 00:04:12,063
Because if we're doing the /29,

91
00:04:12,063 --> 00:04:13,576
that means this is a host,

92
00:04:13,576 --> 00:04:15,576
and the 1.1.1.8 network.

93
00:04:17,218 --> 00:04:20,684
1.1.1.8 and 1.1.1.9 is the
very first host address.

94
00:04:20,684 --> 00:04:24,520
And 1.1.1.1, that's not
in the same network.

95
00:04:24,520 --> 00:04:28,448
So, this router here, router X, would say,

96
00:04:28,448 --> 00:04:30,675
neighbor not on common sub-net.

97
00:04:30,675 --> 00:04:32,094
I'm receiving an EIGRP Hello,

98
00:04:32,094 --> 00:04:33,888
but the neighbor is not
on the common sub-net.

99
00:04:33,888 --> 00:04:35,559
But what about over here?

100
00:04:35,559 --> 00:04:37,226
What about router Z?

101
00:04:38,527 --> 00:04:41,194
What if his address was 1.1.1.1,

102
00:04:43,792 --> 00:04:46,242
cause that's the source he's using...

103
00:04:46,242 --> 00:04:47,492
/24?

104
00:04:49,005 --> 00:04:53,172
And here he receives a Hello
packet sourced from 1.1.1.9.

105
00:04:59,861 --> 00:05:03,473
Is router Z going to
have a problem with that?

106
00:05:03,473 --> 00:05:04,760
No!

107
00:05:04,760 --> 00:05:05,690
Router Z is going to say,

108
00:05:05,690 --> 00:05:08,540
oh, well I'm in the 1.1.1.1 network,

109
00:05:08,540 --> 00:05:11,761
this source is also in
the 1.1.1.1 network,

110
00:05:11,761 --> 00:05:13,796
so he looks good.

111
00:05:13,796 --> 00:05:15,001
So now we're going to have a problem here

112
00:05:15,001 --> 00:05:16,227
because router Z is going to say,

113
00:05:16,227 --> 00:05:17,696
hey router X, you look good.

114
00:05:17,696 --> 00:05:18,915
We're good to go.

115
00:05:18,915 --> 00:05:21,443
Router X is going to
say I can't talk to you.

116
00:05:21,443 --> 00:05:23,463
You're not on the same sub-net as me.

117
00:05:23,463 --> 00:05:27,608
So, only router X was able to
figure out this was a problem.

118
00:05:27,608 --> 00:05:30,179
Router Z did not know this is a problem.

119
00:05:30,179 --> 00:05:33,747
In OSPF, this would be
a problem for both sides

120
00:05:33,747 --> 00:05:35,696
because in their Hello packets,

121
00:05:35,696 --> 00:05:40,476
they actually include what
their sub-net mask is.

122
00:05:40,476 --> 00:05:41,779
And both sides would see that the

123
00:05:41,779 --> 00:05:44,425
other side had a different sub-net mask.

124
00:05:44,425 --> 00:05:45,901
Router Z would say, wait a second,

125
00:05:45,901 --> 00:05:48,492
you're telling me your
sub-net mask is a /29.

126
00:05:48,492 --> 00:05:49,899
That doesn't match me.

127
00:05:49,899 --> 00:05:51,452
I'm a /24.

128
00:05:51,452 --> 00:05:53,410
And so in OSPF, that's why we say the

129
00:05:53,410 --> 00:05:56,514
Prefix-length has to be the same.

130
00:05:56,514 --> 00:05:59,532
So it's a bit better at discovering

131
00:05:59,532 --> 00:06:02,699
these types of problems than EIGRP is.

132
00:06:04,009 --> 00:06:05,153
And then the last thing that has to

133
00:06:05,153 --> 00:06:08,592
be the same is something
called a stub area flag.

134
00:06:08,592 --> 00:06:12,768
You don't really get into
that in the world of CCNA.

135
00:06:12,768 --> 00:06:14,863
But a stub area is basically an area,

136
00:06:14,863 --> 00:06:16,095
a collection of routers,

137
00:06:16,095 --> 00:06:19,382
where there is only one
way in and one way out.

138
00:06:19,382 --> 00:06:21,360
There is just one area border router,

139
00:06:21,360 --> 00:06:23,045
and that's the only way out of the area,

140
00:06:23,045 --> 00:06:24,758
and the only way into the area.

141
00:06:24,758 --> 00:06:26,243
In that particular case,

142
00:06:26,243 --> 00:06:28,505
you can take all of the
routers in that area,

143
00:06:28,505 --> 00:06:30,892
and configure a special
command on there saying,

144
00:06:30,892 --> 00:06:33,195
you are all part of a stub area.

145
00:06:33,195 --> 00:06:34,751
And the actual benefit of that,

146
00:06:34,751 --> 00:06:38,530
is that area will not have
to learn about everything.

147
00:06:38,530 --> 00:06:40,839
You can reduce the size of the OSPF tables

148
00:06:40,839 --> 00:06:41,916
when it's a stub area,

149
00:06:41,916 --> 00:06:42,785
but if you do that,

150
00:06:42,785 --> 00:06:45,325
all of the routers when they're
exchanging their Hellos,

151
00:06:45,325 --> 00:06:47,146
have to have a little flag raised saying,

152
00:06:47,146 --> 00:06:49,224
I believe this area is a stub area.

153
00:06:49,224 --> 00:06:51,474
They have to agree on that.

154
00:06:52,394 --> 00:06:53,453
Okay, so let's go back to these

155
00:06:53,453 --> 00:06:56,120
different types of OSPF packets,

156
00:06:57,552 --> 00:06:59,302
and how they're used.

157
00:07:00,160 --> 00:07:01,405
So first thing, step number one,

158
00:07:01,405 --> 00:07:03,457
is we have to exchange Hello packets.

159
00:07:03,457 --> 00:07:05,596
And those things that we
saw in the previous slide,

160
00:07:05,596 --> 00:07:07,454
have to match.

161
00:07:07,454 --> 00:07:09,541
So let's say that that is the case.

162
00:07:09,541 --> 00:07:12,353
So you and I exchange Hello packets.

163
00:07:12,353 --> 00:07:13,963
So...

164
00:07:13,963 --> 00:07:16,097
inside the Hello packet,

165
00:07:16,097 --> 00:07:18,304
if I was actually to draw a Hello packet,

166
00:07:18,304 --> 00:07:20,717
so let's say here's a Hello packet.

167
00:07:20,717 --> 00:07:24,800
There's a field in here
where you list neighbors.

168
00:07:29,644 --> 00:07:31,969
Which means when I send
you a Hello packet,

169
00:07:31,969 --> 00:07:33,031
I'm telling you,

170
00:07:33,031 --> 00:07:35,920
here's all the neighbors
I know about on this link.

171
00:07:35,920 --> 00:07:39,072
On this link that you and I
share, here's all the neighbors.

172
00:07:39,072 --> 00:07:39,905
Now you might be saying,

173
00:07:39,905 --> 00:07:42,445
well wait a second, it's
just you and me, right?

174
00:07:42,445 --> 00:07:43,546
Why do that?

175
00:07:43,546 --> 00:07:45,443
Well because there might
be more than one neighbor.

176
00:07:45,443 --> 00:07:47,961
Imagine this link was
connected to a switch,

177
00:07:47,961 --> 00:07:49,438
or a hub in between us,

178
00:07:49,438 --> 00:07:52,868
and there were five or six
routers all on the same VLAN,

179
00:07:52,868 --> 00:07:54,267
all on the same sub-net.

180
00:07:54,267 --> 00:07:56,541
Well, my Hello packet would list all of

181
00:07:56,541 --> 00:07:57,969
the routers that I know about,

182
00:07:57,969 --> 00:08:00,637
that I'm neighbors with on this link.

183
00:08:00,637 --> 00:08:02,422
So what's that have to do with this?

184
00:08:02,422 --> 00:08:06,589
Well, when you type the
command show IP OSPF neighbor,

185
00:08:07,630 --> 00:08:09,425
show IP OSPF neighbor,

186
00:08:09,425 --> 00:08:11,488
you'll see if you've got any neighbors,

187
00:08:11,488 --> 00:08:13,879
and what state you're in.

188
00:08:13,879 --> 00:08:15,503
You see, in EIGRP,

189
00:08:15,503 --> 00:08:16,987
it's pretty much all or nothing.

190
00:08:16,987 --> 00:08:18,944
When you did show IP EIGRP neighbor,

191
00:08:18,944 --> 00:08:21,578
you either saw a neighbor or you didn't.

192
00:08:21,578 --> 00:08:24,068
There was like no intermediate steps.

193
00:08:24,068 --> 00:08:26,085
But in OSPF, there are,

194
00:08:26,085 --> 00:08:27,592
and you need to know what those steps are

195
00:08:27,592 --> 00:08:30,230
in building a neighbor relationship.

196
00:08:30,230 --> 00:08:31,813
So step number one.

197
00:08:32,783 --> 00:08:34,616
Here comes in a Hello.

198
00:08:38,408 --> 00:08:39,806
And...

199
00:08:39,806 --> 00:08:41,788
router one is getting that Hello.

200
00:08:41,788 --> 00:08:45,272
And the Hello says it's
coming from router two.

201
00:08:45,272 --> 00:08:47,164
But in the Hello packet itself,

202
00:08:47,164 --> 00:08:48,179
router one says,

203
00:08:48,179 --> 00:08:51,770
huh, okay I see there's a
router two here on this link.

204
00:08:51,770 --> 00:08:52,763
He and I match.

205
00:08:52,763 --> 00:08:53,835
Everything looks good.

206
00:08:53,835 --> 00:08:54,871
But...

207
00:08:54,871 --> 00:08:56,606
he doesn't recognize me.

208
00:08:56,606 --> 00:08:58,461
In other words, in his Hello packet,

209
00:08:58,461 --> 00:09:00,505
I don't see my own name.

210
00:09:00,505 --> 00:09:03,326
So I don't even know if
he's gotten my Hello yet.

211
00:09:03,326 --> 00:09:05,559
All I know is that he exists.

212
00:09:05,559 --> 00:09:07,583
So in this way...

213
00:09:07,583 --> 00:09:10,383
router two would be in
what's called the 2-way...

214
00:09:10,383 --> 00:09:11,883
in the INIT state.

215
00:09:15,420 --> 00:09:17,465
INIT, or the initial,

216
00:09:17,465 --> 00:09:18,976
it's called the initial state.

217
00:09:18,976 --> 00:09:22,297
So if he did show IP OSPF
neighbor on router one,

218
00:09:22,297 --> 00:09:23,812
you would see a neighbor of R2,

219
00:09:23,812 --> 00:09:26,353
and the state would be
INIT, meaning initial.

220
00:09:26,353 --> 00:09:28,146
I received his initial Hello,

221
00:09:28,146 --> 00:09:32,821
but I don't know if he
is even aware of me yet.

222
00:09:32,821 --> 00:09:35,956
Now let's say Hello comes in...

223
00:09:35,956 --> 00:09:37,456
from router two...

224
00:09:39,117 --> 00:09:40,117
That says...

225
00:09:41,005 --> 00:09:42,503
I...

226
00:09:42,503 --> 00:09:43,336
see...

227
00:09:45,562 --> 00:09:46,395
R1.

228
00:09:48,607 --> 00:09:52,645
So now, my neighbor
relationship would change

229
00:09:52,645 --> 00:09:55,395
to what's called the 2-way state.

230
00:09:56,587 --> 00:09:57,420
Router one would say,

231
00:09:57,420 --> 00:10:00,003
okay, I see him and he sees me.

232
00:10:00,981 --> 00:10:03,242
He's actually got my name, my router ID,

233
00:10:03,242 --> 00:10:04,630
inside of his Hello packet.

234
00:10:04,630 --> 00:10:07,106
So that means he must've
received my Hello packet.

235
00:10:07,106 --> 00:10:08,472
We see each other.

236
00:10:08,472 --> 00:10:11,018
Now we're at the 2-way state.

237
00:10:11,018 --> 00:10:14,534
So at this point, now the
routers recognize each other,

238
00:10:14,534 --> 00:10:15,842
and things have matched.

239
00:10:15,842 --> 00:10:18,601
Now it's time to progress
to the next level.

240
00:10:18,601 --> 00:10:21,854
Now the next step is, you and I,

241
00:10:21,854 --> 00:10:23,879
router one and router two get to say,

242
00:10:23,879 --> 00:10:26,302
what's your LSA Database look like?

243
00:10:26,302 --> 00:10:28,173
Do you have the same LSA's as me?

244
00:10:28,173 --> 00:10:30,819
Because if you don't,
we need to synchronize.

245
00:10:30,819 --> 00:10:32,673
So that's going to be the next step.

246
00:10:32,673 --> 00:10:33,549
So, you might want to...

247
00:10:33,549 --> 00:10:35,566
I'm about to...

248
00:10:35,566 --> 00:10:37,628
erase these right here,

249
00:10:37,628 --> 00:10:41,795
so you might want to write
these down before I do.

250
00:10:46,582 --> 00:10:47,415
Let's see here.

251
00:10:47,415 --> 00:10:48,248
Maybe I can fit a little bit more

252
00:10:48,248 --> 00:10:50,915
on the screen before I erase it.

253
00:10:52,142 --> 00:10:54,968
Okay, so the next thing is...

254
00:10:54,968 --> 00:10:59,391
router one and router two
will both send each other,

255
00:10:59,391 --> 00:11:01,170
another type of OSPF packet that

256
00:11:01,170 --> 00:11:02,915
we looked at real briefly,

257
00:11:02,915 --> 00:11:05,498
called the Database Descriptor.

258
00:11:13,778 --> 00:11:15,099
So the primary purpose of

259
00:11:15,099 --> 00:11:16,934
exchanging these Database Descriptors,

260
00:11:16,934 --> 00:11:18,488
is to determine...

261
00:11:18,488 --> 00:11:21,758
does your LSA database look like mine?

262
00:11:21,758 --> 00:11:23,269
And these are going to be
exchanged back and forth.

263
00:11:23,269 --> 00:11:25,077
They give us sort of like a view

264
00:11:25,077 --> 00:11:26,685
of what my database looks like,

265
00:11:26,685 --> 00:11:28,269
what your database looks like.

266
00:11:28,269 --> 00:11:31,593
And so now, as we're exchanging
Database Descriptors,

267
00:11:31,593 --> 00:11:34,941
we're going to move through
two additional states.

268
00:11:34,941 --> 00:11:38,941
We're going to move through
the Exstart state...

269
00:11:41,169 --> 00:11:43,086
and the Exchange state.

270
00:11:48,435 --> 00:11:49,268
Exchange...

271
00:11:49,268 --> 00:11:52,351
sorry for my sloppy handwriting here.

272
00:11:57,677 --> 00:12:00,064
So we started out at INIT,

273
00:12:00,064 --> 00:12:01,135
then we went into 2-way...

274
00:12:01,135 --> 00:12:03,893
and remember, if I'm
doing show IP OSPF data,

275
00:12:03,893 --> 00:12:06,505
show IP OSPF neighbor,

276
00:12:06,505 --> 00:12:08,803
I'm going to see these
various states in the output

277
00:12:08,803 --> 00:12:11,092
if I keep doing that
command over and over again.

278
00:12:11,092 --> 00:12:13,964
So Exstart and Exchange means,

279
00:12:13,964 --> 00:12:16,077
we're exchanging these
Database Descriptors,

280
00:12:16,077 --> 00:12:19,432
trying to discover if our
databases are the same or not.

281
00:12:19,432 --> 00:12:22,374
And they probably will not be the same.

282
00:12:22,374 --> 00:12:25,254
So now I have to erase some
stuff to make some room.

283
00:12:25,254 --> 00:12:29,734
So after the Database
Descriptors are exchanged,

284
00:12:29,734 --> 00:12:32,753
and we discover that
we're missing some stuff,

285
00:12:32,753 --> 00:12:36,503
that your database is
not the same as mine...

286
00:12:38,641 --> 00:12:40,861
then at that point...

287
00:12:40,861 --> 00:12:41,694
I'm going to say,

288
00:12:41,694 --> 00:12:44,899
Okay, you've got some Hello packets,

289
00:12:44,899 --> 00:12:48,470
you've got some link state
advertisements that I don't have.

290
00:12:48,470 --> 00:12:50,976
I would like to have them.

291
00:12:50,976 --> 00:12:52,662
And so, each router might send

292
00:12:52,662 --> 00:12:55,829
each other link state request packets,

293
00:13:00,485 --> 00:13:01,971
saying hey, you've got a link state

294
00:13:01,971 --> 00:13:03,082
advertisement I don't have.

295
00:13:03,082 --> 00:13:04,245
Please give it to me.

296
00:13:04,245 --> 00:13:08,412
And that will be followed by
a link state update packet.

297
00:13:11,401 --> 00:13:12,234
So now they're in the process of

298
00:13:12,234 --> 00:13:15,157
actually making their databases in sync.

299
00:13:15,157 --> 00:13:15,990
Synchronized by,

300
00:13:15,990 --> 00:13:18,638
You send me some request
of what you don't have.

301
00:13:18,638 --> 00:13:20,896
I send you back some updates.

302
00:13:20,896 --> 00:13:23,282
I send you some requests
of what I don't have.

303
00:13:23,282 --> 00:13:25,387
You send me back some updates.

304
00:13:25,387 --> 00:13:28,673
So now, we're going to move
into a different state,

305
00:13:28,673 --> 00:13:30,923
which is the Loading state.

306
00:13:33,467 --> 00:13:36,178
So if you issued the command
show IP OSPF neighbor,

307
00:13:36,178 --> 00:13:38,843
and it says loading,
that's what's going on.

308
00:13:38,843 --> 00:13:43,055
They're requesting LSA's and
updating each other with LSA's.

309
00:13:43,055 --> 00:13:45,052
And then finally, we're
going to eventually

310
00:13:45,052 --> 00:13:46,403
reach a point where we realize,

311
00:13:46,403 --> 00:13:48,154
hey, we're the same.

312
00:13:48,154 --> 00:13:51,559
My database has exactly the
same stuff as your database.

313
00:13:51,559 --> 00:13:52,796
Now, all we have to do is go back to

314
00:13:52,796 --> 00:13:56,569
exchanging periodic Hello
packets and that's it.

315
00:13:56,569 --> 00:14:00,736
And now you'll finally be in
what's called the Full state.

316
00:14:01,987 --> 00:14:04,040
Which means we are fully adjacent,

317
00:14:04,040 --> 00:14:05,134
we are fully loaded,

318
00:14:05,134 --> 00:14:07,931
everything is fully synchronized.

319
00:14:07,931 --> 00:14:10,667
So that's the series of
steps that two routers,

320
00:14:10,667 --> 00:14:12,222
or two OSPF devices,

321
00:14:12,222 --> 00:14:16,168
will move through to finally
become fully adjacent.

322
00:14:16,168 --> 00:14:20,335
INIT, 2-way, Exstart,
Exchange, Loading, and Full.

323
00:14:23,686 --> 00:14:26,283
And so now we've talked
about where those various

324
00:14:26,283 --> 00:14:29,356
packet types are used in the process

325
00:14:29,356 --> 00:14:32,106
of building an OSPF relationship.

326
00:14:33,083 --> 00:14:35,666
(gentle music)

