1
00:00:00,000 --> 00:00:03,318
[AUDIO LOGO]

2
00:00:03,318 --> 00:00:07,120

3
00:00:07,120 --> 00:00:10,780
So next, let's jump in
and look at our new type

4
00:00:10,780 --> 00:00:13,330
8 and type 9 LSAs.

5
00:00:13,330 --> 00:00:16,510
Now, as we go through, we'll
talk about what the type

6
00:00:16,510 --> 00:00:18,700
8 and type 9 are actually for--

7
00:00:18,700 --> 00:00:21,580
however, when we get
into the command line

8
00:00:21,580 --> 00:00:23,470
to look at these
in the database,

9
00:00:23,470 --> 00:00:26,560
we'll actually go ahead and
take a look at the differences

10
00:00:26,560 --> 00:00:29,090
in the other LSA types as well.

11
00:00:29,090 --> 00:00:32,119
So that's what our goal is
going to be in this video.

12
00:00:32,119 --> 00:00:34,780
Let's jump in and start
talking about those new type

13
00:00:34,780 --> 00:00:39,280
8 and type 9 LSAs and
what they're actually for.

14
00:00:39,280 --> 00:00:44,380
So as we mentioned, one of our
new LSA types is the type 8.

15
00:00:44,380 --> 00:00:49,300
Now, the type 8 is actually
a very interesting LSA type.

16
00:00:49,300 --> 00:00:54,790
The reason for that is it
carries link local information.

17
00:00:54,790 --> 00:00:57,930
The key word here being local.

18
00:00:57,930 --> 00:00:59,680
We're going to see how
this affects things

19
00:00:59,680 --> 00:01:02,440
in just a moment,
but keep in mind

20
00:01:02,440 --> 00:01:05,960
that this is local
information for a router.

21
00:01:05,960 --> 00:01:09,730
Now, these are called link LSAs,
just from a naming convention

22
00:01:09,730 --> 00:01:10,790
perspective.

23
00:01:10,790 --> 00:01:14,110
Now, the reason we need
these is as we mentioned

24
00:01:14,110 --> 00:01:18,250
in our previous video,
everything in IPv6

25
00:01:18,250 --> 00:01:21,100
uses link local addressing.

26
00:01:21,100 --> 00:01:24,850
If we're going to be using link
local addresses as our next hop

27
00:01:24,850 --> 00:01:28,060
and things like this in our
routing, well, then clearly,

28
00:01:28,060 --> 00:01:33,230
we have to know the link local
addresses of our neighbors.

29
00:01:33,230 --> 00:01:38,560
Now, the interesting part here
is since it's, again, local

30
00:01:38,560 --> 00:01:43,640
it only includes directly
connected neighbors.

31
00:01:43,640 --> 00:01:47,750
Now, this definitely brings
up an interesting situation,

32
00:01:47,750 --> 00:01:49,120
what situation?

33
00:01:49,120 --> 00:01:55,120
Well, doesn't that mean that
the type 8 is, in fact, breaking

34
00:01:55,120 --> 00:02:00,640
the normal OSPF rule that
databases must match.

35
00:02:00,640 --> 00:02:02,860
How can these databases match?

36
00:02:02,860 --> 00:02:06,220
If they only include
connected information.

37
00:02:06,220 --> 00:02:07,780
Every router is
going to be connected

38
00:02:07,780 --> 00:02:09,220
to different neighbors.

39
00:02:09,220 --> 00:02:13,930
Therefore, every router will
have different type 8 LSAs

40
00:02:13,930 --> 00:02:15,070
in its database.

41
00:02:15,070 --> 00:02:18,560
Therefore, the
databases cannot match.

42
00:02:18,560 --> 00:02:20,680
Now, just so we're
very clear here,

43
00:02:20,680 --> 00:02:24,640
the type 8 is the
exception to the rule, OK?

44
00:02:24,640 --> 00:02:26,740
Generally speaking,
yes, the database

45
00:02:26,740 --> 00:02:31,720
is still have to match for
all of our other LSA types.

46
00:02:31,720 --> 00:02:34,510
It's fun to point out that
it's breaking the rule,

47
00:02:34,510 --> 00:02:37,060
but at the end of the day,
it's breaking the rule

48
00:02:37,060 --> 00:02:38,990
because that's
what's needed here.

49
00:02:38,990 --> 00:02:42,130
But the rest of OSPF,
again, still works

50
00:02:42,130 --> 00:02:45,370
as normal and every
router in the area

51
00:02:45,370 --> 00:02:48,170
must have the same
matching database.

52
00:02:48,170 --> 00:02:51,490
So yes, it's an exception,
but we're not fundamentally

53
00:02:51,490 --> 00:02:55,210
changing that rule
in OSPF version 3.

54
00:02:55,210 --> 00:03:01,990
Now, the type 9 LSAs are used
to carry the prefixes that are

55
00:03:01,990 --> 00:03:04,570
available on each router ID.

56
00:03:04,570 --> 00:03:10,165
Remember that the type 1s
and type 2s in OSPF version

57
00:03:10,165 --> 00:03:14,140
3 only carry
topology information.

58
00:03:14,140 --> 00:03:18,050
That would be what router ID
is connected to what router ID.

59
00:03:18,050 --> 00:03:20,710
So for example, maybe we have
a couple of routers here.

60
00:03:20,710 --> 00:03:23,540
They're, of course, connected
together in some fashion.

61
00:03:23,540 --> 00:03:25,660
And we'll just say for
the sake of argument

62
00:03:25,660 --> 00:03:30,190
and to keep it simple, maybe
this is router ID 1.1.1.1,

63
00:03:30,190 --> 00:03:37,340
this one is 2.2.2.2,
and this one is 3.3.3.3.

64
00:03:37,340 --> 00:03:38,980
We'll just keep it simple.

65
00:03:38,980 --> 00:03:42,760
Well, again through the
type 1 and type 2 LSAs,

66
00:03:42,760 --> 00:03:46,420
we're going to learn which
router IDs are connected

67
00:03:46,420 --> 00:03:48,400
to which other router IDs.

68
00:03:48,400 --> 00:03:50,260
So what I just sort
of drew here would

69
00:03:50,260 --> 00:03:53,350
be what we would learn from
the type 1s and type 2s.

70
00:03:53,350 --> 00:03:58,750
What the type 9 is going to
tell us is, oh, by the way,

71
00:03:58,750 --> 00:04:09,580
3.3.3.3 over here has the
prefixes 2001:DB8:3::3/64

72
00:04:09,580 --> 00:04:19,120
and maybe it has a
2001:DB8:100::3/128,

73
00:04:19,120 --> 00:04:21,063
maybe that's its
loopback address.

74
00:04:21,063 --> 00:04:22,480
But what we're
doing with the type

75
00:04:22,480 --> 00:04:28,720
9 LSAs is we are mapping these
prefixes to this router ID.

76
00:04:28,720 --> 00:04:31,570
Those two pieces of
information together

77
00:04:31,570 --> 00:04:34,120
allow us to fill out
our routing tables

78
00:04:34,120 --> 00:04:37,360
to know which prefixes are
available through which

79
00:04:37,360 --> 00:04:38,500
router ID.

80
00:04:38,500 --> 00:04:41,620
And again, simply from
a naming perspective,

81
00:04:41,620 --> 00:04:46,030
these are called
intra-area prefix LSAs

82
00:04:46,030 --> 00:04:51,050
because they're dealing with
the prefixes inside of an area.

83
00:04:51,050 --> 00:04:53,680
So just like type
1s and type 2s,

84
00:04:53,680 --> 00:04:57,128
these will not go
into other OSPF areas.

85
00:04:57,128 --> 00:04:59,170
So let's go ahead and
clean that up a little bit.

86
00:04:59,170 --> 00:05:01,840
Just as a reminder
here, remember

87
00:05:01,840 --> 00:05:06,130
that the type has been
renamed to inter -area.

88
00:05:06,130 --> 00:05:09,880
This is, of course, the LSA
that goes between areas,

89
00:05:09,880 --> 00:05:16,360
and the type 4 has been
renamed to inter-area router.

90
00:05:16,360 --> 00:05:21,340
This, of course, is to
advertise ASPRs in other areas.

91
00:05:21,340 --> 00:05:23,810
We talked about this
in the previous video.

92
00:05:23,810 --> 00:05:26,170
This is just here as
a reminder before we

93
00:05:26,170 --> 00:05:29,200
take a look at the database.

94
00:05:29,200 --> 00:05:33,520
One other thing to be aware
of, OSPF version 3 does

95
00:05:33,520 --> 00:05:38,230
have different options that
will be on the various LSAs.

96
00:05:38,230 --> 00:05:40,630
We don't need to sit here
and go through every entry

97
00:05:40,630 --> 00:05:41,920
on the table here.

98
00:05:41,920 --> 00:05:43,865
I just put it here
for your reference.

99
00:05:43,865 --> 00:05:45,490
so as we're going
through the database,

100
00:05:45,490 --> 00:05:47,950
if you're not sure what
one of these options are,

101
00:05:47,950 --> 00:05:50,480
you can come back here and
reference to this table

102
00:05:50,480 --> 00:05:52,420
so you'll understand
what it's for.

103
00:05:52,420 --> 00:05:55,270
That said, let's take
a look at our topology

104
00:05:55,270 --> 00:05:58,120
real quick so we know which
routers we're going to look at

105
00:05:58,120 --> 00:06:00,100
and what's going on
as far as what entries

106
00:06:00,100 --> 00:06:03,100
we should see in our database.

107
00:06:03,100 --> 00:06:06,600
So we'll be using
OSPFv3 topology 1,

108
00:06:06,600 --> 00:06:08,850
and the main thing we
want to discuss here

109
00:06:08,850 --> 00:06:12,510
is since we've not actually
gotten to our configuration

110
00:06:12,510 --> 00:06:20,400
yet in this skill, routers 6,
1, and 2 are not yet configured.

111
00:06:20,400 --> 00:06:22,350
So what that really
means as we go

112
00:06:22,350 --> 00:06:26,260
through this video
is as of right now,

113
00:06:26,260 --> 00:06:28,500
we're only going
to see information

114
00:06:28,500 --> 00:06:31,470
on this part of the network
down here at the bottom.

115
00:06:31,470 --> 00:06:34,050
As such, we'll be
looking at the database

116
00:06:34,050 --> 00:06:37,500
mostly from the
perspective of router 8

117
00:06:37,500 --> 00:06:39,870
and a little bit on router 7.

118
00:06:39,870 --> 00:06:42,240
But we will see some
entries because we

119
00:06:42,240 --> 00:06:45,730
do have some routers in
area 100 and, of course,

120
00:06:45,730 --> 00:06:47,470
some routers in our own area.

121
00:06:47,470 --> 00:06:49,830
So let's go ahead and
jump in and take a look

122
00:06:49,830 --> 00:06:52,230
at the database.

123
00:06:52,230 --> 00:06:59,110
So here on router 8, let's
do a show OSPFv3 database.

124
00:06:59,110 --> 00:07:02,190
And we'll start by looking
at the type 1 LSAs.

125
00:07:02,190 --> 00:07:04,230
So let's look at the router LSA.

126
00:07:04,230 --> 00:07:06,930
We'll just scroll to the
bottom here and pick on one.

127
00:07:06,930 --> 00:07:08,850
The main thing we're
trying to see here

128
00:07:08,850 --> 00:07:13,630
is notice that it has entries
such as the advertising router.

129
00:07:13,630 --> 00:07:16,200
We can see that it's
connected to another router

130
00:07:16,200 --> 00:07:17,910
as a point-to-point link.

131
00:07:17,910 --> 00:07:20,910
We see that neighboring
router's router ID,

132
00:07:20,910 --> 00:07:23,490
but notice there's no prefix.

133
00:07:23,490 --> 00:07:26,610
There's no IPv6 prefix here.

134
00:07:26,610 --> 00:07:29,370
This is just
topology information.

135
00:07:29,370 --> 00:07:31,930
What router is connected
to what other router.

136
00:07:31,930 --> 00:07:33,930
And of course, if we were
to scroll through here

137
00:07:33,930 --> 00:07:35,805
and look at other ones,
they're all the same.

138
00:07:35,805 --> 00:07:39,060
If we look at the type 3s,
we simply take off router.

139
00:07:39,060 --> 00:07:42,310
Remember, these are
now called inter-area.

140
00:07:42,310 --> 00:07:45,420
And again, there's two choices
here, either the prefix

141
00:07:45,420 --> 00:07:46,410
or the router.

142
00:07:46,410 --> 00:07:49,440
Prefix would be the old type 3s.

143
00:07:49,440 --> 00:07:53,250
So these are going to be
entries from other areas.

144
00:07:53,250 --> 00:07:56,130
Once again, we'll scroll to the
bottom and take a look at one,

145
00:07:56,130 --> 00:07:57,900
and notice what we see here.

146
00:07:57,900 --> 00:08:01,740
This is now being
advertised by our ABR,

147
00:08:01,740 --> 00:08:03,030
in this case, router 3.

148
00:08:03,030 --> 00:08:07,930
And we see that this actually
does include the prefix.

149
00:08:07,930 --> 00:08:10,800
So this last entry
here happens to be

150
00:08:10,800 --> 00:08:15,780
looks like router 4's actual
loopback interface just based

151
00:08:15,780 --> 00:08:18,000
on the address and
the prefix length.

152
00:08:18,000 --> 00:08:21,030
But you can see that this
is actually advertising

153
00:08:21,030 --> 00:08:23,790
the same way we did a type 3.

154
00:08:23,790 --> 00:08:28,600
Now, we do not have any ASPRs
just yet in our topology.

155
00:08:28,600 --> 00:08:31,650
So if we were to
right now say router,

156
00:08:31,650 --> 00:08:33,850
there actually won't
be any entries.

157
00:08:33,850 --> 00:08:37,150
So we'll look at this one
again in a future video.

158
00:08:37,150 --> 00:08:39,480
Let's take a look at the
routing table just briefly.

159
00:08:39,480 --> 00:08:44,790
If we do a show IPv6 route
and we'll filter by OSPF,

160
00:08:44,790 --> 00:08:49,530
notice that all of
the next hop addresses

161
00:08:49,530 --> 00:08:54,270
are the link local
address of router 7, which

162
00:08:54,270 --> 00:08:56,200
it's a little difficult
to highlight here.

163
00:08:56,200 --> 00:08:57,720
I just highlighted
a few of them.

164
00:08:57,720 --> 00:09:01,320
But it's the FE80::7.

165
00:09:01,320 --> 00:09:02,850
By the way, another
good command we

166
00:09:02,850 --> 00:09:05,640
have while we're here just
taking a look at this,

167
00:09:05,640 --> 00:09:08,610
show IPv6 interface brief.

168
00:09:08,610 --> 00:09:11,140
Just like we have show
IP interface brief,

169
00:09:11,140 --> 00:09:14,110
and we can see all
these addresses.

170
00:09:14,110 --> 00:09:17,220
We can also see here our
link local addresses.

171
00:09:17,220 --> 00:09:21,060
Notice by the way, that my
gigabit ethernet interface

172
00:09:21,060 --> 00:09:24,420
and my loopback 0 interface
both have the same link

173
00:09:24,420 --> 00:09:25,530
local address.

174
00:09:25,530 --> 00:09:28,770
This is actually fine
because, well, they're local,

175
00:09:28,770 --> 00:09:31,170
they're not routable,
so you can actually

176
00:09:31,170 --> 00:09:35,620
use the same link local address
on every interface on a router.

177
00:09:35,620 --> 00:09:37,180
It's not a problem at all.

178
00:09:37,180 --> 00:09:40,680
So now let's take a look
at some of those new LSAs.

179
00:09:40,680 --> 00:09:43,170
Let's start with the type 8.

180
00:09:43,170 --> 00:09:45,360
So we'll go back to
our database command

181
00:09:45,360 --> 00:09:47,130
and, again, these are
called link locals,

182
00:09:47,130 --> 00:09:48,570
so we'll just say link.

183
00:09:48,570 --> 00:09:51,630
And here we see a type 8.

184
00:09:51,630 --> 00:09:54,330
Notice that what
it's showing us here

185
00:09:54,330 --> 00:09:58,360
is the link local
address of our neighbors.

186
00:09:58,360 --> 00:10:01,440
So for example, I'm on
router 8, my neighbor

187
00:10:01,440 --> 00:10:03,120
is router 7, so
let's look up here

188
00:10:03,120 --> 00:10:08,190
at the top at the advertising
router is 10.7.7.7,

189
00:10:08,190 --> 00:10:09,960
and look what it's telling me.

190
00:10:09,960 --> 00:10:15,300
It's telling me that the link
local address is FE80::7.

191
00:10:15,300 --> 00:10:19,230
Now, it also happens to
include the prefix address

192
00:10:19,230 --> 00:10:25,860
that's on that link, so
the 2001:DB8:78::/64.

193
00:10:25,860 --> 00:10:27,670
It lists that as well.

194
00:10:27,670 --> 00:10:31,800
But the main purpose of this is
to get that link local address.

195
00:10:31,800 --> 00:10:33,900
The bottom entry
here is, of course,

196
00:10:33,900 --> 00:10:37,210
me advertising my own
into the database.

197
00:10:37,210 --> 00:10:41,920
So here on router 8, we have
entries for 7 and 8 itself.

198
00:10:41,920 --> 00:10:46,650
But if we were to go do this
exact same command on router 7,

199
00:10:46,650 --> 00:10:49,590
this one has entries for
7 and 8, that's itself

200
00:10:49,590 --> 00:10:51,720
and rounder 8, of
course, is the neighbor.

201
00:10:51,720 --> 00:10:56,820
But notice it also has an entry
here for router 3 out gigabit 2

202
00:10:56,820 --> 00:11:02,970
advertising its link local
address of FE80::3, which,

203
00:11:02,970 --> 00:11:05,770
of course, 8 knew nothing about.

204
00:11:05,770 --> 00:11:09,180
So this is simply showing
that again, as we mentioned,

205
00:11:09,180 --> 00:11:15,190
the LSA type 8s do not have to
be identical through the area.

206
00:11:15,190 --> 00:11:16,770
In fact, they will not be.

207
00:11:16,770 --> 00:11:21,280
It's all about local information
about your local neighbors.

208
00:11:21,280 --> 00:11:23,880
So let's jump back over to
router 8 again, and let's

209
00:11:23,880 --> 00:11:26,220
take a look at the type 9s.

210
00:11:26,220 --> 00:11:29,050
So instead of link,
we say prefix.

211
00:11:29,050 --> 00:11:30,840
Now, notice what we're doing.

212
00:11:30,840 --> 00:11:33,570
These are entries
for the whole area.

213
00:11:33,570 --> 00:11:37,770
Notice, for example, this
top entry is from router 3.

214
00:11:37,770 --> 00:11:40,740
And it's telling us
about the three prefixes

215
00:11:40,740 --> 00:11:42,600
that are connected to router.

216
00:11:42,600 --> 00:11:45,480
We have our entry from router
7 and if we scroll down

217
00:11:45,480 --> 00:11:48,690
a little bit and then back up
so we can see the whole thing,

218
00:11:48,690 --> 00:11:51,570
we can now see that
it's router 7 telling us

219
00:11:51,570 --> 00:11:54,160
about its 4 prefixes.

220
00:11:54,160 --> 00:11:57,660
So this is, again, the
equivalent of the information

221
00:11:57,660 --> 00:12:01,140
that we used to get in
type 1 and type 2 LSAs

222
00:12:01,140 --> 00:12:03,450
in OSPF version 2.

223
00:12:03,450 --> 00:12:09,490
This information would be
the same in the whole area.

224
00:12:09,490 --> 00:12:14,700
In this video, we took a look
at the new LSA types, type 8

225
00:12:14,700 --> 00:12:17,970
and 9, that are used
to advertise the link

226
00:12:17,970 --> 00:12:20,190
local information
for our neighbors

227
00:12:20,190 --> 00:12:23,440
in the case of the
type 8 and, of course,

228
00:12:23,440 --> 00:12:27,660
all of the prefixes in the
area tied to the router

229
00:12:27,660 --> 00:12:31,430
ID in the case of the type 9.

230
00:12:31,430 --> 00:12:33,320
We also jumped into
the command line,

231
00:12:33,320 --> 00:12:36,200
took a look at some of these
in the actual database,

232
00:12:36,200 --> 00:12:38,930
including the changes
to the type 1.

233
00:12:38,930 --> 00:12:41,780
We saw that although
renamed, the type 3

234
00:12:41,780 --> 00:12:45,380
was pretty much the same as
it was in OSPF version 2,

235
00:12:45,380 --> 00:12:47,060
just again renamed.

236
00:12:47,060 --> 00:12:51,440
And then we also took a look
at the type 8 and the type 9s

237
00:12:51,440 --> 00:12:54,050
and we saw how the
type 8s actually

238
00:12:54,050 --> 00:12:57,290
don't have to be the
same in the entire area,

239
00:12:57,290 --> 00:13:00,480
and in fact, as we
saw, they won't be.

240
00:13:00,480 --> 00:13:02,510
I hope this has been
informative for you.

241
00:13:02,510 --> 00:13:05,590
And I'd like to thank
you for viewing.

242
00:13:05,590 --> 00:13:09,000