WEBVTT

1
00:00.000 --> 00:04.560
And preparation for deploying OSPF version 3 for IPv6. Let's take a look at our

2
00:04.560 --> 00:05.200
topology.

3
00:05.200 --> 00:11.040
So this topology supports both IPv4 and IPv6. And this number here is here in

4
00:11.040 --> 00:12.560
red that is our

5
00:12.560 --> 00:16.640
subnet number. And what I'm circling there is for IPv4, but I'm also using the

6
00:16.640 --> 00:18.000
same exact subnet

7
00:18.000 --> 00:23.110
in the world of IPv6 as well. So all the prefixes for IPv6 begin with 2001, DBA

8
00:23.110 --> 00:23.280
,

9
00:23.280 --> 00:29.940
6 and 8, 3, colon X where X is that number. So here's the 12 network 13, 34, 24

10
00:29.940 --> 00:30.480
, and down here
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

10
00:29.940 --> 00:30.480
, and down here

11
00:30.480 --> 00:37.270
to the 35, 57, 48, 46, 68, and so forth. And then down here it would be subnet

12
00:37.270 --> 00:38.720
7, and over here

13
00:38.720 --> 00:45.200
it would be subnet 8 for IPv6. So all the IPv6 addressing is in place for this

14
00:45.200 --> 00:45.920
topology already,

15
00:45.920 --> 00:51.610
but what is not in place is the OSPF version 3 for the address family for IPv6.

16
00:51.610 --> 00:52.240
So let's do a quick

17
00:52.240 --> 00:56.250
review about some of the basics regarding IPv6. And if you haven't worked with

18
00:56.250 --> 00:57.200
IPv6 for a few minutes

19
00:57.200 --> 01:00.410
or a few hours or a few days or weeks or years, it might be a great refresher
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

19
00:57.200 --> 01:00.410
or a few hours or a few days or weeks or years, it might be a great refresher

20
01:00.410 --> 01:01.600
as well. So as far as

21
01:01.600 --> 01:09.120
addresses go, we have global addresses. And those begin with 2000 through 3FFF.

22
01:09.120 --> 01:09.760
So if we see an

23
01:09.760 --> 01:13.740
IPv6 address starting within that range, that represents a globally routable IP

24
01:13.740 --> 01:14.960
v6 address. Then we

25
01:14.960 --> 01:20.020
have link local addresses, which begin with FE80. So if you see that, that's a

26
01:20.020 --> 01:20.960
link local address

27
01:20.960 --> 01:24.110
that the router can use, but just for that local segment, and link local

28
01:24.110 --> 01:25.600
addresses are not globally

29
01:25.600 --> 01:30.450
routable. And then we have multicast addresses as well, which begin with FF.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

29
01:25.600 --> 01:30.450
routable. And then we have multicast addresses as well, which begin with FF.

30
01:30.450 --> 01:31.200
Now when configuring the

31
01:31.200 --> 01:34.230
SPF for IPv6 on these Cisco routers, there's a few options. We can use the

32
01:34.230 --> 01:35.680
legacy method, which is

33
01:35.680 --> 01:40.750
IPv6 router OSPF, and then a process ID number. And that would be the legacy

34
01:40.750 --> 01:42.160
way of doing it, but even if

35
01:42.160 --> 01:45.860
we configure it in the older method, this legacy method, and do a show IP

36
01:45.860 --> 01:46.720
protocols, it's still

37
01:46.720 --> 01:49.840
going to show that it's OSPF version 3, although this is the older way of

38
01:49.840 --> 01:51.120
implementing it. And what

39
01:51.120 --> 01:53.480
we're going to do in this set of videos is we're going to focus on the more

40
01:53.480 --> 01:54.480
current way of doing it.

41
01:54.480 --> 01:57.940
And that is with literally a routing process known as OSPF B3, which can

42
01:57.940 --> 02:00.080
support IPv6, and also
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

42
01:57.940 --> 02:00.080
support IPv6, and also

43
02:00.080 --> 02:04.480
support IPv4 at the same time. So for configuration, we're going to configure

44
02:04.480 --> 02:05.760
OSPF version 3, that

45
02:05.760 --> 02:10.480
flavor, the current flavor of it, with the address family for IPv6. Now with OS

46
02:10.480 --> 02:11.360
PF version 3,

47
02:11.360 --> 02:14.670
there are LSAs, link state advertisements that are used, and a lot of them are

48
02:14.670 --> 02:15.520
very similar as we

49
02:15.520 --> 02:21.940
had with IPv4 OSPF. So we have LSA type 1, which is a router LSA, generated by

50
02:21.940 --> 02:23.520
our routers. So that's

51
02:23.520 --> 02:30.020
very similar between IPv4 and IPv6. We also have LSA type 2, which is generated
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

51
02:23.520 --> 02:30.020
very similar between IPv4 and IPv6. We also have LSA type 2, which is generated

52
02:30.020 --> 02:31.040
by the designated router

53
02:31.040 --> 02:34.460
for a given segment. And actually, let me adjust these columns. And actually,

54
02:34.460 --> 02:34.960
let me go ahead and make

55
02:34.960 --> 02:38.880
another column here. I'll put the name of it, we're here on the name of the LSA

56
02:38.880 --> 02:39.520
, and then we'll go

57
02:39.520 --> 02:43.730
ahead and put who generates it to the right of it. So the LSA type 1 is the

58
02:43.730 --> 02:45.280
router LSA, and is generated

59
02:45.280 --> 02:50.490
by each of the routers respectively. And the LSA type 2 is the network LSA, and

60
02:50.490 --> 02:51.840
just like an IPv4,

61
02:51.840 --> 02:54.870
that's generated by the designated router for a given segment, where there are

62
02:54.870 --> 02:56.000
two or more OSPF

63
02:56.000 --> 03:00.930
speakers connected to that segment. Then we have LSA type 3, and in the world
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

63
02:56.000 --> 03:00.930
speakers connected to that segment. Then we have LSA type 3, and in the world

64
03:00.930 --> 03:02.640
of IPv6, the LSA type 3

65
03:02.640 --> 03:06.280
is very similar to the LSA type 3 in IPv4, but it's given a different name. It

66
03:06.280 --> 03:07.120
's called the

67
03:07.120 --> 03:12.730
interarea prefix LSA. And in IPv4, we called that a summary LSA, and that's

68
03:12.730 --> 03:14.720
generated by the ABRs.

69
03:14.720 --> 03:20.480
So for example, this network right here, the 2001 DB868312 network, which is in

70
03:20.480 --> 03:21.360
area 0, is that

71
03:21.360 --> 03:25.180
gets advertised down to area 1. That's going to be sent by the ABR here, as an

72
03:25.180 --> 03:26.720
LSA type 3, which in

73
03:26.720 --> 03:31.680
the past was called a summary LSA with IPv4, and now it's called an interarea L
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

73
03:26.720 --> 03:31.680
the past was called a summary LSA with IPv4, and now it's called an interarea L

74
03:31.680 --> 03:33.200
SA with IPv6.

75
03:33.200 --> 03:36.800
Still a type 3, still providing the same functionality. There's also the LSA

76
03:36.800 --> 03:38.480
types 4 and 5, which

77
03:38.480 --> 03:42.100
deal with external routes that have been redistributed into the OSPF routing

78
03:42.100 --> 03:43.280
domain. And there's also

79
03:43.280 --> 03:48.060
a very similar to how they did with OSPF for IPv4. So the type 4 describes how

80
03:48.060 --> 03:49.280
to reach the ASBR,

81
03:49.280 --> 03:52.150
the autonomous STEM boundary route that we talked about in the previous skill,

82
03:52.150 --> 03:53.120
and the LSA type 5 is

83
03:53.120 --> 03:56.620
the external route that we're advertising, meaning that route that was redist

84
03:56.620 --> 03:58.400
ributed into OSPF

85
03:58.400 --> 04:01.460
from some other source, from a static route or a different routing protocol.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

85
03:58.400 --> 04:01.460
from some other source, from a static route or a different routing protocol.

86
04:01.460 --> 04:02.080
And although there's

87
04:02.080 --> 04:06.580
a few additional LSA types, specifically for OSPF version 3, let me point out

88
04:06.580 --> 04:08.560
two more. That's an LSA

89
04:08.560 --> 04:14.240
type 8 and an LSA type 9. And these are unique to the IPv6 implementation of OS

90
04:14.240 --> 04:15.680
PF with OSPF version 3.

91
04:15.680 --> 04:19.920
The LSA type 8 is describing link local information and additional options that

92
04:19.920 --> 04:20.640
they may have regarding

93
04:20.640 --> 04:23.580
the individual links are connected to. So the link local addresses are the ones

94
04:23.580 --> 04:24.800
that begin with FE80,

95
04:24.800 --> 04:29.640
as we talked about earlier. And then an LSA type 9 is going to carry intra,

96
04:29.640 --> 04:30.800
meaning within the area,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

96
04:29.640 --> 04:30.800
meaning within the area,

97
04:30.800 --> 04:35.710
prefixes, which is a fancy way of saying the networks. So for example, here in

98
04:35.710 --> 04:37.280
area 1, with the 2001

99
04:37.280 --> 04:44.210
DB86M8335 network, and the 2001 DB86M8357 networks, there'd be LSA type 9s to

100
04:44.210 --> 04:45.280
describe those networks,

101
04:45.280 --> 04:49.330
and those in state in the area. As far as the router IDs, that's the same as it

102
04:49.330 --> 04:50.640
was for IPv4.

103
04:50.640 --> 04:55.530
The router ID is a 32-bit address, which looks a lot like an IPv4 address.

104
04:55.530 --> 04:56.720
However, it's just a 32-bit

105
04:56.720 --> 05:01.710
identifier for the router, and it's determined the same way it is with IPv4's
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

105
04:56.720 --> 05:01.710
identifier for the router, and it's determined the same way it is with IPv4's

106
05:01.710 --> 05:03.440
OSPF. If there's a hard-coded

107
05:03.440 --> 05:07.220
router ID that takes precedence, if there's no hard-coded router ID in the

108
05:07.220 --> 05:08.480
routing process, then it's

109
05:08.480 --> 05:12.710
going to use the highest IPv4 address on any loopback. And if you don't have

110
05:12.710 --> 05:14.080
any loopback interfaces with

111
05:14.080 --> 05:19.390
IPv4, when OSPF comes up, you'll then go ahead and use the highest IPv4 address

112
05:19.390 --> 05:21.040
on any other interface

113
05:21.040 --> 05:23.920
if you don't have any loopbacks with IPv4 addresses. So that process, we're

114
05:23.920 --> 05:24.960
going to how it picks the

115
05:24.960 --> 05:30.990
router ID is the same in every flavor of OSPF, for both IPv4 and IPv6. Also,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

115
05:24.960 --> 05:30.990
router ID is the same in every flavor of OSPF, for both IPv4 and IPv6. Also,

116
05:30.990 --> 05:32.320
the rules with OSPF

117
05:32.320 --> 05:36.720
version 3 for IPv6 regarding becoming a fully adjacent neighbor. Those are also

118
05:36.720 --> 05:38.000
extremely similar to

119
05:38.000 --> 05:41.760
IPv4. So a couple of skills ago, we talked about some of the basics regarding

120
05:41.760 --> 05:42.640
OSPF and neighbor

121
05:42.640 --> 05:50.210
jacencies, and we used the acronym of stamp, STTAMP. So among the things that

122
05:50.210 --> 05:51.360
would need to match

123
05:51.360 --> 05:55.080
between two routers for them to become adjacent, fully adjacent with OSPF

124
05:55.080 --> 05:56.400
version 3 for IPv6,

125
05:56.400 --> 06:00.470
they need to agree on the subnet that they're both connected to. They need to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

125
05:56.400 --> 06:00.470
they need to agree on the subnet that they're both connected to. They need to

126
06:00.470 --> 06:01.680
agree on the timers,

127
06:01.680 --> 06:05.270
including the hello and dead interval timers. They need to agree on the network

128
06:05.270 --> 06:06.240
type. For example,

129
06:06.240 --> 06:09.930
as a broadcast network, our point-to-point network. And most of the time, if we

130
06:09.930 --> 06:11.200
agree on the network type,

131
06:11.200 --> 06:14.300
that's also going to take care of our timers issue, unless we've tweaked those

132
06:14.300 --> 06:15.280
timers separately.

133
06:15.280 --> 06:18.420
It's also going to help in identifying whether or not we need a designated

134
06:18.420 --> 06:19.680
router for the segment.

135
06:19.680 --> 06:23.360
So in a point-to-point network, I care between our four and our six. It's a

136
06:23.360 --> 06:24.320
serial link, and the

137
06:24.320 --> 06:27.640
network type is going to be point-to-point, no DR needed. On the ethernet

138
06:27.640 --> 06:29.200
network here between our two

139
06:29.200 --> 06:33.040
and our four, because it's a broadcast-based network by default for ethernet,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

139
06:29.200 --> 06:33.040
and our four, because it's a broadcast-based network by default for ethernet,

140
06:33.040 --> 06:33.440
and they're both

141
06:33.440 --> 06:37.080
expecting there to be a DR. So when they show up on the network and there's one

142
06:37.080 --> 06:37.920
, they'll go ahead and

143
06:37.920 --> 06:40.780
decide who's going to be the DR. And then one of these two devices will be the

144
06:40.780 --> 06:41.600
designated router for

145
06:41.600 --> 06:44.850
this segment, and the other router will be the backup designated router. And a

146
06:44.850 --> 06:45.760
third router, if we

147
06:45.760 --> 06:50.680
add it there, would become the DR other. Another item that needs to be agreed

148
06:50.680 --> 06:52.160
to is the area, and not just

149
06:52.160 --> 06:57.220
the area number, but also the type of area. Is it a normal area, or is it a

150
06:57.220 --> 06:58.720
stub area? So the two

151
06:58.720 --> 07:03.060
neighbors need to agree on the area type and the area number. They also need to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

151
06:58.720 --> 07:03.060
neighbors need to agree on the area type and the area number. They also need to

152
07:03.060 --> 07:04.560
agree on the Mtu,

153
07:04.560 --> 07:08.220
the maximum transmission unit, and the p is to remind us of password, now what

154
07:08.220 --> 07:08.800
that really is,

155
07:08.800 --> 07:12.550
is authentication. So the two routers need to agree on the authentication, and

156
07:12.550 --> 07:13.200
what type of

157
07:13.200 --> 07:17.240
authentication we're using, and also the keys involved for that authentication.

158
07:17.240 --> 07:18.320
So in troubleshooting,

159
07:18.320 --> 07:23.030
just think of STT AMP as a reminder of those elements, which you need to match

160
07:23.030 --> 07:23.440
if we want to

161
07:23.440 --> 07:27.550
get full adjacencies. So just like with IPv4, R3, because it connected the

162
07:27.550 --> 07:29.200
backbone in area 1, it would be

163
07:29.200 --> 07:34.190
an ABR, once it's configured with interfaces in both areas, and over here on
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

163
07:29.200 --> 07:34.190
an ABR, once it's configured with interfaces in both areas, and over here on

164
07:34.190 --> 07:35.040
our four, once we

165
07:35.040 --> 07:40.380
configure it with interfaces in area zero and in area two, it would also act as

166
07:40.380 --> 07:41.360
an ABR. Now the

167
07:41.360 --> 07:45.440
cool thing with that is that we can do the same types of filtering and summar

168
07:45.440 --> 07:46.560
ization as we did with

169
07:46.560 --> 07:51.280
IPv4. So if we want to take all the routes, for example, from area zero, and

170
07:51.280 --> 07:52.560
summarize them as they're

171
07:52.560 --> 07:56.290
being advertised down to area one, we can do that here at this ABR, or if we

172
07:56.290 --> 07:57.200
want to take these

173
07:57.200 --> 08:01.470
routes in area two and summarize those into one or more summaries as we
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

173
07:57.200 --> 08:01.470
routes in area two and summarize those into one or more summaries as we

174
08:01.470 --> 08:03.280
advertise those as LSA type

175
08:03.280 --> 08:06.710
threes up here in area zero. Once again, at the ABR, we can do that summar

176
08:06.710 --> 08:07.920
ization. And we also have

177
08:07.920 --> 08:12.520
the option if we choose to to create stub or totally stubby areas, and that's

178
08:12.520 --> 08:13.680
again done by having

179
08:13.680 --> 08:17.460
all the routers in an area agree that it's a stub area, and for a totally stub

180
08:17.460 --> 08:18.160
by area where we're

181
08:18.160 --> 08:21.750
not advertising the LSA type threes down, we simply configure the area border

182
08:21.750 --> 08:22.720
router, simply use the

183
08:22.720 --> 08:27.460
option of no dash summary, which restricts the LSA type threes from being sent

184
08:27.460 --> 08:28.480
down into this area

185
08:28.480 --> 08:32.260
with the exception of the LSA type three, which is the default route, which it
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

185
08:28.480 --> 08:32.260
with the exception of the LSA type three, which is the default route, which it

186
08:32.260 --> 08:33.760
'll advertise by default,

187
08:33.760 --> 08:38.420
once we have this setup as a stub area. So with that overview in mind in our

188
08:38.420 --> 08:39.200
next video,

189
08:39.200 --> 08:45.560
let's begin to put in the configuration for IPv6 OSPFE3 based on this topology

190
08:45.560 --> 08:47.200
diagram and verify

191
08:47.200 --> 08:50.110
that it works. So we'll do that in the next video and I'll see you there in

192
08:50.110 --> 08:50.720
just a moment.