WEBVTT

1
00:00.000 --> 00:03.480
In this video, we get to take a look at the configuration and verification of

2
00:03.480 --> 00:08.800
summarization for the IPv4 address family using OSPF version 3.

3
00:08.800 --> 00:12.720
Now, as a reminder, the summarization that we're going to do uses the command

4
00:12.720 --> 00:13.400
range.

5
00:13.400 --> 00:17.840
That's true for traditional OSPF and also for OSPF version 3.

6
00:17.840 --> 00:22.170
And we're going to implement those summaries, those ranges here at our area

7
00:22.170 --> 00:23.280
border routers.

8
00:23.280 --> 00:28.480
So we could summarize networks from area 1 as they're being advertised up here

9
00:28.480 --> 00:29.280
in area 0.

10
00:29.280 --> 00:31.040
Meaning those LC type 3s.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

10
00:29.280 --> 00:31.040
Meaning those LC type 3s.

11
00:31.040 --> 00:35.680
We could summarize LC type 3s from area 0 as we're coming down here and same

12
00:35.680 --> 00:36.400
treatment over here.

13
00:36.400 --> 00:39.760
We could summarize from area 0 going down to area 2.

14
00:39.760 --> 00:42.720
We could summarize from area 2 going into area 0.

15
00:42.720 --> 00:47.730
So having said that, let's put a plan together for some specific summarization

16
00:47.730 --> 00:48.320
and then we'll

17
00:48.320 --> 00:50.560
implement it and test it to verify that it works.

18
00:50.560 --> 00:51.680
So here's what I propose we do.

19
00:51.680 --> 00:55.600
Let's use R3 as the area border router that's going to do the summarization and

20
00:55.600 --> 00:57.120
let's summarize

21
00:57.120 --> 00:58.960
the routes from area 0.

22
00:58.960 --> 01:03.500
In fact, let's go ahead and summarize anything that begins with 10, 0, anything
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

22
00:58.960 --> 01:03.500
In fact, let's go ahead and summarize anything that begins with 10, 0, anything

23
01:03.500 --> 01:03.680
.

24
01:03.680 --> 01:07.200
So we'll do the summary at 10, 0, 16 for area 0.

25
01:07.200 --> 01:11.590
And if we do that right here in R3, when R3 is advertising the LSA type 3s down

26
01:11.590 --> 01:12.720
into area 1,

27
01:12.720 --> 01:18.610
instead of sending all the individual LSA type 3s down, it will send the 10, 0,

28
01:18.610 --> 01:20.240
16 and it will hide

29
01:20.240 --> 01:24.400
or not advertise the LSA type 3s for any of the more detailed routes that fall

30
01:24.400 --> 01:25.280
under that summary.

31
01:25.280 --> 01:28.910
So with that in mind, let's go to our topology, we'll do a couple quick checks

32
01:28.910 --> 01:30.640
first and then we'll
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

32
01:28.910 --> 01:30.640
first and then we'll

33
01:30.640 --> 01:32.880
implement the summary and compare the differences.

34
01:32.880 --> 01:36.960
So to start off, let's go to R5 and just verify it can see the detailed routes

35
01:36.960 --> 01:40.320
for 10, 0, 13, 10, 0, 12, 10, 0, 24.

36
01:40.320 --> 01:42.400
So let's go down to R5.

37
01:42.400 --> 01:43.360
So we're at R5.

38
01:43.360 --> 01:49.380
We'll do a show IP route for OSPFB3 learned routes and sure enough, as far as

39
01:49.380 --> 01:50.880
routes to begin with 10, 0, we

40
01:50.880 --> 01:55.890
have those three and then we have these four and these external type twos,

41
01:55.890 --> 01:57.680
those are LSA type 5s.

42
01:57.680 --> 02:01.590
So if we do a summary with the range command, it's not going to catch those
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

42
01:57.680 --> 02:01.590
So if we do a summary with the range command, it's not going to catch those

43
02:01.590 --> 02:02.480
external routes.

44
02:02.480 --> 02:05.760
If we wanted to summarize those routes, we'd want to do that up at the

45
02:05.760 --> 02:06.720
autonomous system boundary

46
02:06.720 --> 02:12.390
route or R1 as it injected those into OSPF. So with the range command and the

47
02:12.390 --> 02:13.840
summary at the ABR,

48
02:13.840 --> 02:20.250
we're just summarizing the LSA type 3s, which is the 10, 0, 1, 2, 4 and 12, 13,

49
02:20.250 --> 02:21.760
24 and 34, that I'll

50
02:21.760 --> 02:25.720
begin with 10, 0 and our LSA type 3. So now that we've verified they exist, let

51
02:25.720 --> 02:27.280
's go up to R3

52
02:27.280 --> 02:30.850
and we'll look at our topology. R3 is our area border router between the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

52
02:27.280 --> 02:30.850
and we'll look at our topology. R3 is our area border router between the

53
02:30.850 --> 02:32.880
backbone area and area 1

54
02:32.880 --> 02:36.900
and let's set up our summary. So let's do a show run, pipe section router and

55
02:36.900 --> 02:37.120
then we'll go in

56
02:37.120 --> 02:42.590
a configuration mode. We'll go into router OSPFB3, process ID1 and then further

57
02:42.590 --> 02:43.520
more, we'll go into

58
02:43.520 --> 02:48.520
address family for IPv4 unicast and here under the address family for IPv4, we

59
02:48.520 --> 02:49.120
'll go ahead and use our

60
02:49.120 --> 02:52.840
range command. So we'll say area and then we want to summarize the routes

61
02:52.840 --> 02:54.320
coming from area 0. So we'll

62
02:54.320 --> 02:58.230
say area 0. That's the area where the routes for about to summarize are and let

63
02:58.230 --> 03:00.960
's go ahead and do 10.0.0.0
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

63
02:58.230 --> 03:00.960
's go ahead and do 10.0.0.0

64
03:00.960 --> 03:06.340
and then what do we say 16? Yeah, 16 bits. So we'll do 255.25.0.0. It'll do a

65
03:06.340 --> 03:07.360
space and question mark

66
03:07.360 --> 03:10.520
and it says Keith, it looks great. You said range probably but you didn't type

67
03:10.520 --> 03:12.240
it in. So area 0,

68
03:12.240 --> 03:16.510
range, space and then we'll go to the end and then we'll do a question mark and

69
03:16.510 --> 03:17.200
then we're going to

70
03:17.200 --> 03:21.790
give it a cost. We can't let's give it initial cost of about 10. Great. So that

71
03:21.790 --> 03:22.560
'll be the cost of

72
03:22.560 --> 03:27.120
that summary route. So a moment ago down on our five, if we go back to our five

73
03:27.120 --> 03:28.480
, it had a whole bunch

74
03:28.480 --> 03:33.990
of these 10.0 routes that were L.C. type 3s and now if we do a show IP route OS
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

74
03:28.480 --> 03:33.990
of these 10.0 routes that were L.C. type 3s and now if we do a show IP route OS

75
03:33.990 --> 03:35.520
PFB3 again, those

76
03:35.520 --> 03:39.590
inter area routes that started with 10.0, they are gone and they've been

77
03:39.590 --> 03:41.200
replaced with this one

78
03:41.200 --> 03:45.920
summary route as shown right here. So here in our five, if we did a show OSPFB3

79
03:45.920 --> 03:47.680
IPV4 database,

80
03:47.680 --> 03:53.240
press dinner, here's our L.C. type 1s, L.C. type 2s and here's our L.C. type 3s

81
03:53.240 --> 03:54.880
. You'll notice we have

82
03:54.880 --> 03:58.220
this one right here with a very short age, that's because we just made it and

83
03:58.220 --> 03:59.760
that is the summary address.

84
03:59.760 --> 04:05.360
So here in area 1 on our five, it no longer has the L.S.A.s for the individual
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

84
03:59.760 --> 04:05.360
So here in area 1 on our five, it no longer has the L.S.A.s for the individual

85
04:05.360 --> 04:06.240
detailed routes like

86
04:06.240 --> 04:12.300
the 10.0.12 or 13 or 24 or 34. They're all being suppressed and held back at

87
04:12.300 --> 04:12.880
the area border

88
04:12.880 --> 04:16.480
router because the summary is in place. So far five is going to ping for

89
04:16.480 --> 04:19.040
example 10.0.12.1,

90
04:19.040 --> 04:23.830
that's the IP address on gig 1.0 of R1, let's go ahead and verify which route

91
04:23.830 --> 04:24.880
it would use.

92
04:24.880 --> 04:30.410
So this show IP route for 10.0.12.1 and it is going to be using that summary
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

92
04:24.880 --> 04:30.410
So this show IP route for 10.0.12.1 and it is going to be using that summary

93
04:30.410 --> 04:31.520
route right there

94
04:31.520 --> 04:34.770
that was advertised by the ABR. So that'd be forwarded up to our three and then

95
04:34.770 --> 04:35.200
our three would make

96
04:35.200 --> 04:38.490
its own routing decision and then it forwards the packet to the final

97
04:38.490 --> 04:39.760
destination. And we're going to do

98
04:39.760 --> 04:46.940
a quick ping to 10.0.12.1 just to verify it works, that's a good sign too. So

99
04:46.940 --> 04:47.680
now that we've had the

100
04:47.680 --> 04:53.730
opportunity to do some configuration and verification with OSPF V3 for IPv4 in

101
04:53.730 --> 04:54.480
the next video,

102
04:54.480 --> 04:58.630
I like to present a hands-on lab for you to get your own practice doing exactly

103
04:58.630 --> 04:59.520
that. So when

104
04:59.520 --> 05:01.920
you're ready, I'll see you in the lab video in just a moment.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

104
04:59.520 --> 05:01.920
you're ready, I'll see you in the lab video in just a moment.