WEBVTT

1
00:00.000 --> 00:02.560
So in this walkthrough, we're going to walk through the lab tasks.

2
00:02.560 --> 00:07.680
We should involve setting up OSPFV3 for the address family for IPv6 as shown in

3
00:07.680 --> 00:08.560
the topology.

4
00:08.560 --> 00:12.960
And then once we verify that, we'll configure area two as a totally stubby area

5
00:12.960 --> 00:12.960
.

6
00:12.960 --> 00:14.640
It will also set up a summary.

7
00:14.640 --> 00:18.320
So any routes that begin with those first 48 bits and will make one summary

8
00:18.320 --> 00:19.520
that will advertise

9
00:19.520 --> 00:22.990
up into area zero. And that's going to get happened on R3 because that's the

10
00:22.990 --> 00:24.000
area border router

11
00:24.000 --> 00:28.300
between area one and the backbone area. So with that in mind, I have reset my

12
00:28.300 --> 00:29.120
lab environment.

13
00:29.120 --> 00:32.480
Let's go to it right now and let's do this walkthrough together.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

13
00:29.120 --> 00:32.480
Let's go to it right now and let's do this walkthrough together.

14
00:32.480 --> 00:35.890
So a few moments ago, I just clicked on reset and it'll take just a moment or

15
00:35.890 --> 00:36.720
two for this to fully

16
00:36.720 --> 00:41.020
initialize. And when it's done, we'll go ahead and start the walkthrough. All

17
00:41.020 --> 00:42.720
right, so here we go.

18
00:42.720 --> 00:47.020
Let's go ahead and open up the stupology diagram on the desktop of server one -

19
00:47.020 --> 00:48.560
nug that looks good

20
00:48.560 --> 00:52.100
and we use that for our reference. This same topology is also included as part

21
00:52.100 --> 00:52.560
of the skill.

22
00:52.560 --> 00:56.390
So if you want to put that on a separate screen or print it for reference, that

23
00:56.390 --> 00:57.440
's going to be helpful as well.

24
00:57.440 --> 01:00.650
And then let's go ahead and we'll double click here on server one nug to open
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

24
00:57.440 --> 01:00.650
And then let's go ahead and we'll double click here on server one nug to open

25
01:00.650 --> 01:01.360
that up

26
01:01.360 --> 01:03.980
because that's how we're going to get to our console access for each of the

27
01:03.980 --> 01:04.400
routers.

28
01:04.400 --> 01:08.220
Is VS server one nug? All right, and here it comes. Fantastic. And then we also

29
01:08.220 --> 01:08.480
have in the

30
01:08.480 --> 01:12.700
background the OSPF configs doc should we want to use that as well. So what I'm

31
01:12.700 --> 01:13.440
going to do is because

32
01:13.440 --> 01:18.270
we've already done this a couple times. I'm going to scroll down to the IPv6 OS

33
01:18.270 --> 01:19.280
PF section as part of

34
01:19.280 --> 01:24.910
this configuration file. And here it is. OSPF version three with IPv4 and IPv6.

35
01:24.910 --> 01:26.080
And let's go ahead and

36
01:26.080 --> 01:30.600
start with r1. Now in this lab environment, I'm not asking you to do IPv4. So I
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

36
01:26.080 --> 01:30.600
start with r1. Now in this lab environment, I'm not asking you to do IPv4. So I

37
01:30.600 --> 01:31.680
'm not going to even bother

38
01:31.680 --> 01:36.480
doing the IPv4 portions for that address family. We're focused just on IPv6. So

39
01:36.480 --> 01:36.640
in the

40
01:36.640 --> 01:40.690
instant of time, I'm going to use this notepad document, take those configs,

41
01:40.690 --> 01:41.760
copy them, and put them

42
01:41.760 --> 01:47.060
on to r1. Then I repeat that process for r2. So in r2, I'll take the config for

43
01:47.060 --> 01:48.240
r2. I'll remove the

44
01:48.240 --> 01:52.250
enablement of the address family for IPv4 on the interfaces. And then once that

45
01:52.250 --> 01:53.280
's done, I'll take the

46
01:53.280 --> 01:56.860
config for r2. Copy that. And all of its interfaces are going to be an area

47
01:56.860 --> 01:58.320
zero. So we'll copy that,

48
01:58.320 --> 02:01.810
then go to the right tab for r2 and paste it in. And then I'm going to repeat
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

48
01:58.320 --> 02:01.810
then go to the right tab for r2 and paste it in. And then I'm going to repeat

49
02:01.810 --> 02:03.040
that for r3,

50
02:03.040 --> 02:09.280
r4, r5, r6, r7, and r8. All right. So OSPF B3 process ID1 has been configured

51
02:09.280 --> 02:10.080
on all eight

52
02:10.080 --> 02:13.650
routers. And if we want to verify some basic routing, we do a show IP. Of

53
02:13.650 --> 02:16.160
course, I have a show IPv6

54
02:16.160 --> 02:20.310
route for OSPF learned routes, press center. And at the moment, we don't have

55
02:20.310 --> 02:21.280
any yet because I'm

56
02:21.280 --> 02:26.060
still waiting on a membership, I think, with r6. So if we look at our topology,

57
02:26.060 --> 02:26.800
that should be coming

58
02:26.800 --> 02:30.640
in shortly. And once we get that notification of the console here, we'll then
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

58
02:26.800 --> 02:30.640
in shortly. And once we get that notification of the console here, we'll then

59
02:30.640 --> 02:31.680
take a look at our

60
02:31.680 --> 02:38.280
routing table. And there's our JsonC right there. And what? What? What? I'm

61
02:38.280 --> 02:40.080
joking because what I

62
02:40.080 --> 02:43.780
also did, I just paste it in the IPv4 enablement as well. So we actually have

63
02:43.780 --> 02:44.880
two of JsonC's, one for

64
02:44.880 --> 02:48.970
address family IPv4. And based on what the lab was asking for, also one here

65
02:48.970 --> 02:50.240
for IPv6. So if we do

66
02:50.240 --> 02:56.190
a show OSPF B3 IPv6 neighbor, it should just the neighbor ships for IPv6. And

67
02:56.190 --> 02:57.280
there's our full

68
02:57.280 --> 03:01.240
of JsonC up with r6. So now if we get the upper key a couple of times to show
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

68
02:57.280 --> 03:01.240
of JsonC up with r6. So now if we get the upper key a couple of times to show

69
03:01.240 --> 03:02.480
IPv6 route that we're

70
03:02.480 --> 03:06.250
learning via OSPF, we should have all the routes in our routing table. So there

71
03:06.250 --> 03:07.200
's the seven network

72
03:07.200 --> 03:12.170
right there. This is to a trace. So let's go ahead and copy that and let's do a

73
03:12.170 --> 03:13.120
trace. And we'll

74
03:13.120 --> 03:17.910
paste that in. And r7's last octet is seven there, press center. And there we

75
03:17.910 --> 03:18.720
have the trace

76
03:18.720 --> 03:22.120
all the way from r8 all the way to r7. And then as you do the lab also feel

77
03:22.120 --> 03:23.280
free to practice with

78
03:23.280 --> 03:27.200
many of the show commands that we've issued up to this point. For example, show

79
03:27.200 --> 03:30.320
IPv6 protocols show IPv6
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

79
03:27.200 --> 03:30.320
IPv6 protocols show IPv6

80
03:30.320 --> 03:35.370
interface brief just to verify what addresses are there. Show OSPF version

81
03:35.370 --> 03:36.800
three interface brief

82
03:36.800 --> 03:45.090
and show OSPF B3. And I'm going to go ahead and say just for IPv6. So here's

83
03:45.090 --> 03:46.240
the OSPF B3

84
03:46.240 --> 03:50.520
information regarding process one for address family IPv6. There's the router

85
03:50.520 --> 03:51.520
ID. There's our reference

86
03:51.520 --> 03:56.740
bandwidth that we set to a thousand. There is the one normal area because this

87
03:56.740 --> 03:58.160
is r8. It is in area

88
03:58.160 --> 04:01.370
two. And it's not yet a stub because we haven't configured that yet. But it
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

88
03:58.160 --> 04:01.370
two. And it's not yet a stub because we haven't configured that yet. But it

89
04:01.370 --> 04:02.400
will be once we configured

90
04:02.400 --> 04:07.230
as a stub in fact, let's take that next step right now and configure area two

91
04:07.230 --> 04:08.720
as a stub. So to do that

92
04:08.720 --> 04:13.340
we need to go to r4, r6, and r8 to do that. So let's go ahead and use this

93
04:13.340 --> 04:14.800
option right here.

94
04:14.800 --> 04:18.100
Still carriage return icon. And what we'll do is we'll go into configuration

95
04:18.100 --> 04:18.720
mode for each of our

96
04:18.720 --> 04:24.760
routers and type in router. OSPF B3, process ID1. And then we'll say area two

97
04:24.760 --> 04:27.600
stub. Now if we did area two

98
04:27.600 --> 04:33.920
stub, no summary on a router such as r6 or r8, it wouldn't matter because they
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

98
04:27.600 --> 04:33.920
stub, no summary on a router such as r6 or r8, it wouldn't matter because they

99
04:33.920 --> 04:34.960
are not area border

100
04:34.960 --> 04:38.500
routers. The only router that's going to care about not advertising the lc type

101
04:38.500 --> 04:39.520
three is it's going to be

102
04:39.520 --> 04:42.870
an area border router. So we could, if we wanted to, we could get away with

103
04:42.870 --> 04:44.240
this. If we go back to

104
04:44.720 --> 04:49.330
the multi tab putty here, we could say no summary right there. And then end.

105
04:49.330 --> 04:50.800
And that would make it

106
04:50.800 --> 04:55.100
a totally stubby area. And r6 and r8 would know its area two stub and the no

107
04:55.100 --> 04:56.880
summary part wouldn't matter

108
04:56.880 --> 05:00.210
to them. It's only applicable to the area border router. So I'm going to go
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

108
04:56.880 --> 05:00.210
to them. It's only applicable to the area border router. So I'm going to go

109
05:00.210 --> 05:01.600
ahead and send that to r8,

110
05:01.600 --> 05:08.500
r6, and r4, click on send script. And we should be set. So let's go double

111
05:08.500 --> 05:10.240
check here on r4,

112
05:10.240 --> 05:14.270
the show OSPF B3. So this is showing us that we have one normal area. That's

113
05:14.270 --> 05:15.680
the backbone area

114
05:15.680 --> 05:20.350
and one stub area. That's area two. And it's also reinforcing that right here

115
05:20.350 --> 05:21.520
under area two. It says

116
05:21.520 --> 05:26.160
it is a stub area. So if we went down to r8 and down on r8 where a moment ago

117
05:26.160 --> 05:27.280
if we scroll up,

118
05:27.280 --> 05:32.160
we had a whole bunch of inter area routes as shown right here from earlier a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

118
05:27.280 --> 05:32.160
we had a whole bunch of inter area routes as shown right here from earlier a

119
05:32.160 --> 05:33.840
few minutes ago. Now if

120
05:33.840 --> 05:38.630
we had the rq a few times and do a show ipv6 route, ospf, impress enter. Now we

121
05:38.630 --> 05:40.000
have our default route.

122
05:40.000 --> 05:44.550
That we learned courtesy of r4 that's our area border router. And we have one

123
05:44.550 --> 05:45.840
intra area route here

124
05:45.840 --> 05:53.140
of 2001 db678346. But we have none of the other lsa type 3s. However, we still

125
05:53.140 --> 05:54.000
have access

126
05:54.000 --> 05:56.920
to reach those other networks because we have our default route. So if we did a

127
05:56.920 --> 05:58.000
trace route again,

128
05:58.000 --> 06:01.380
I'll let the up arrow key till we find that. There it is. If we trace route
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

128
05:58.000 --> 06:01.380
I'll let the up arrow key till we find that. There it is. If we trace route

129
06:01.380 --> 06:02.960
over to our sevens gig

130
06:02.960 --> 06:05.940
zero zero address, impress enter. It can go ahead and verify for us that we

131
06:05.940 --> 06:07.280
have full connectivity

132
06:07.280 --> 06:11.690
from r8 all the way around the horn down to r7. So let's check our tasks and

133
06:11.690 --> 06:12.800
verify we did it. We

134
06:12.800 --> 06:17.310
set up ospf v3. We verified basic connectivity. We configured area two as a

135
06:17.310 --> 06:18.800
totally stub area.

136
06:18.800 --> 06:23.250
And we verified connectivity. Oh, I almost forgot. We need to summarize the

137
06:23.250 --> 06:24.160
routes beginning with

138
06:24.160 --> 06:30.080
2001 db67834 those first 48 bits and create a summary route from area one as we
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

138
06:24.160 --> 06:30.080
2001 db67834 those first 48 bits and create a summary route from area one as we

139
06:30.080 --> 06:30.800
advertise those

140
06:30.800 --> 06:34.250
into area zero. And again, we're going to do that on r3 because that's the area

141
06:34.250 --> 06:35.120
border router between

142
06:35.120 --> 06:39.910
area one and the backbone area. So let's head over to r3 and we'll set up that

143
06:39.910 --> 06:41.360
range configuration

144
06:41.360 --> 06:45.480
inside of ospf. Let's go ahead and show the configuration for our routing with

145
06:45.480 --> 06:47.040
show run section

146
06:47.040 --> 06:50.800
router. And let's go into configuration mode. And from configuration mode, we

147
06:50.800 --> 06:52.560
'll go into router ospf v3

148
06:52.560 --> 06:55.970
for process id1 by typing that in. And then further, we'll go in the address

149
06:55.970 --> 06:57.200
family for ipv6

150
06:57.200 --> 07:00.570
unit cast because that's what we want to do the summary for. And then here we
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

150
06:57.200 --> 07:00.570
unit cast because that's what we want to do the summary for. And then here we

151
07:00.570 --> 07:01.360
're going to type

152
07:01.360 --> 07:05.340
in area. And then the area we want to summarize routes for which is area one.

153
07:05.340 --> 07:06.720
And we want to do 2001

154
07:06.720 --> 07:14.180
db8 colon 678 3 colon colon slash 48. And we press enter. Oh, I put 49. Oh, and

155
07:14.180 --> 07:15.120
I put 49. And I also

156
07:15.120 --> 07:19.320
forgot to put the range command. So let's go ahead and fix that. So area one

157
07:19.320 --> 07:20.240
range. And that is the

158
07:20.240 --> 07:26.270
same command, the range word, whether we're in ipv4 or ipv6. So area one range,

159
07:26.270 --> 07:26.960
the summary we want

160
07:26.960 --> 07:31.420
to do. And I want a 48 bit summary, not a 49 bit summary, although that 49th
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

160
07:26.960 --> 07:31.420
to do. And I want a 48 bit summary, not a 49 bit summary, although that 49th

161
07:31.420 --> 07:32.400
bit would also be a

162
07:32.400 --> 07:36.000
0. So that probably work. But we press enter here. And now with that range in

163
07:36.000 --> 07:37.200
place, we'll go ahead

164
07:37.200 --> 07:41.670
up to r1. And here on r1, if you do a show ipv6 route, and we'll tag on ospf

165
07:41.670 --> 07:42.640
just for ospf

166
07:42.640 --> 07:46.400
learned routes in press center. Here we have our 48 bit route. But what isn't

167
07:46.400 --> 07:47.680
showing up are those

168
07:47.680 --> 07:51.550
other detailed routes. So what I mean by those other detailed routes, I'm

169
07:51.550 --> 07:54.080
referring to the 35 subnet

170
07:54.080 --> 07:58.170
and the 57 subnet and the 7 subnet because they're being suppressed. And

171
07:58.170 --> 07:59.440
instead of advertising all

172
07:59.440 --> 08:03.700
those lc type 3s for those individual routes, it's advertising this one summary
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

172
07:59.440 --> 08:03.700
those lc type 3s for those individual routes, it's advertising this one summary

173
08:03.700 --> 08:06.160
of 2001 db868348.

174
08:06.160 --> 08:10.230
So if we want to verify full connectivity, we can go back to r8. We can hit the

175
08:10.230 --> 08:10.960
up arrow key and do

176
08:10.960 --> 08:15.050
a trace route all the way through the network down to r7. And that's just still

177
08:15.050 --> 08:16.000
function because

178
08:16.000 --> 08:19.320
everybody every single route in our topology has some type of routing

179
08:19.320 --> 08:20.640
information, including

180
08:20.640 --> 08:24.190
default routes or more specific routes to forward the packets in the right

181
08:24.190 --> 08:24.960
direction.

182
08:24.960 --> 08:28.640
So thanks for joining me in this set of videos and into skill regarding working

183
08:28.640 --> 08:30.640
with ospf version 3
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

183
08:28.640 --> 08:30.640
with ospf version 3

184
08:30.640 --> 08:35.040
for the address family for ipv6 and idlc4dcingu my friend in another set of

185
08:35.040 --> 08:36.960
videos very very soon.

186
08:36.960 --> 08:41.780
Until then, I hope this has been informative and I'd like to thank you for

187
08:41.780 --> 08:42.240
viewing.