WEBVTT

1
00:00.000 --> 00:01.700
So for this hands-on lab,

2
00:01.700 --> 00:05.300
we have R1, R2, and R3 that are already configured and ready to go.

3
00:05.300 --> 00:10.240
That way we can focus our attention on R4 to enable multi-cast routing,

4
00:10.240 --> 00:13.000
to specify who the rendezvous point is,

5
00:13.000 --> 00:15.300
which we're going to use R2 as the rendezvous point.

6
00:15.300 --> 00:16.540
So I'll make a note here,

7
00:16.540 --> 00:20.780
R2 at 2.2.2.2 is the rendezvous point.

8
00:20.780 --> 00:23.980
Also, I'll put the helpful and useful commands regarding

9
00:23.980 --> 00:26.500
this lab in the text as part of the skills.

10
00:26.500 --> 00:27.700
If you want to refer to them there,

11
00:27.700 --> 00:29.060
you can see them there as well.

12
00:29.060 --> 00:31.260
Then once you've enabled multi-cast routing,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

12
00:29.060 --> 00:31.260
Then once you've enabled multi-cast routing,

13
00:31.260 --> 00:35.020
you've enabled the interfaces for PIM and you specify the rendezvous point,

14
00:35.020 --> 00:40.740
I'd then like you to go to R1 and join the multi-cast group of 224.67.83

15
00:40.740 --> 00:42.460
on its gig two zero interface.

16
00:42.460 --> 00:45.700
So see interface is 10.10.0.1.

17
00:45.700 --> 00:49.510
Then once you've joined that group, I like you to go to R4 and then PING that

18
00:49.510 --> 00:50.220
group address.

19
00:50.220 --> 00:53.020
That traffic should be forwarded over to R2,

20
00:53.020 --> 00:55.660
who's the rendezvous point, and then down the tree,

21
00:55.660 --> 00:58.140
down to R1, who will receive the PING request

22
00:58.140 --> 00:59.620
and should be able to respond.

23
00:59.620 --> 01:03.620
Now the responses are simply going to be unicast back to the source.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

23
00:59.620 --> 01:03.620
Now the responses are simply going to be unicast back to the source.

24
01:03.620 --> 01:06.500
And then we sourced it from gig two zero on R4,

25
01:06.500 --> 01:09.340
which is 23.1.2.4.

26
01:09.340 --> 01:14.780
That reply traffic from R1 to R4 is going to go based on the normal IPv4

27
01:14.780 --> 01:15.980
unicast routing table.

28
01:15.980 --> 01:18.020
But the initial flow for the PING request

29
01:18.020 --> 01:20.380
are going to be going down the multi-cast tree.

30
01:20.380 --> 01:22.140
And then once you have that configured and working,

31
01:22.140 --> 01:25.980
I would invite you to play around with some show commands like show IPPMRP,

32
01:25.980 --> 01:30.540
show IPPM interface, show IPigMP interface, and show IPM route.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

32
01:25.980 --> 01:30.540
show IPPM interface, show IPigMP interface, and show IPM route.

33
01:30.540 --> 01:32.660
So have some fun with this hands on lab.

34
01:32.660 --> 01:35.580
And when you are done, join me in the walkthrough video,

35
01:35.580 --> 01:36.860
which is coming up next.