WEBVTT 1 00:00.000 --> 00:05.000 So here are the lab tasks and let's go ahead and do this walk through together. 2 00:05.000 --> 00:06.400 So here's our lab environment. 3 00:06.400 --> 00:09.500 Let me go ahead and double click on the topology to make sure on the right 4 00:09.500 --> 00:11.600 sheet of music or the same sheet of music. 5 00:11.600 --> 00:12.400 Fantastic. 6 00:12.400 --> 00:16.280 And we'll go ahead and double click here on server one to get console access to 7 00:16.280 --> 00:17.600 each of our devices. 8 00:17.600 --> 00:18.600 Fantastic. 9 00:18.600 --> 00:22.510 Let me just scooch this over a little bit over here and I'll bring our topology 10 00:22.510 --> 00:23.600 down here a little bit. 11 00:23.600 --> 00:26.470 In fact, I'll make it a little bit smaller and just check that down in the 12 00:26.470 --> 00:27.800 bottom right hand corner. 13 00:27.800 --> 00:28.800 All right, that'll do. 14 00:28.800 --> 00:32.800 So let's do a spot check real quick on our two, which is our rendezvous point. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 14 00:28.800 --> 00:32.800 So let's do a spot check real quick on our two, which is our rendezvous point. 15 00:32.800 --> 00:34.000 It should already be configured. 16 00:34.000 --> 00:39.080 Let's do a show IP Emroute and sure enough, it has a couple of groups that 17 00:39.080 --> 00:41.400 knows about no sources yet specified. 18 00:41.400 --> 00:44.200 And we show IP PIM interface. 19 00:44.200 --> 00:45.200 Fantastic. 20 00:45.200 --> 00:49.000 We do a show IP, I GMP interface also fantastic. 21 00:49.000 --> 00:50.200 There's all our interfaces. 22 00:50.200 --> 00:54.820 So again, we'll bring up the show IP Emroute and we have no custom groups yet 23 00:54.820 --> 00:58.060 because we haven't actually sent multicast traffic as if we were a multicast 24 00:58.060 --> 00:58.400 server. 25 00:58.400 --> 01:01.400 So let's go to R4 and let's begin the configuration. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 25 00:58.400 --> 01:01.400 So let's go to R4 and let's begin the configuration. 26 01:01.400 --> 01:06.000 We'll go into configuration mode first and we'll do IP multicast routing 27 01:06.000 --> 01:09.600 spelled multicast dash routing and we're off to the races. 28 01:09.600 --> 01:12.790 Then while we're here in global config, that's specified the rendezvous point 29 01:12.790 --> 01:17.800 and that's going to be IP PIM, RP dash address and that is 2.2.2.2. 30 01:17.800 --> 01:22.800 Let's also verify we can reach that address with a ping to 2.2.2.2. 31 01:22.800 --> 01:26.400 And sure enough, that is our two loop back acting as a rendezvous point. 32 01:26.400 --> 01:30.250 The tunnel at the moment is down but that's because we don't yet have any PIM WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 32 01:26.400 --> 01:30.250 The tunnel at the moment is down but that's because we don't yet have any PIM 33 01:30.250 --> 01:31.400 enabled interfaces. 34 01:31.400 --> 01:34.920 So we'll go into interface configuration mode for the three interfaces here on 35 01:34.920 --> 01:35.400 R4. 36 01:35.400 --> 01:41.710 So inter-page range would do the trick for us for gig 1 slash 0 comma gig 2 37 01:41.710 --> 01:45.400 slash 0 comma F A 4 slash 1. 38 01:45.400 --> 01:50.230 And then we use the command IP PIM and a space question mark and we want to put 39 01:50.230 --> 01:51.400 them into sparse mode. 40 01:51.400 --> 01:53.400 So go ahead and use the sparse mode option right there. 41 01:53.400 --> 01:57.400 Right click and paste that in and we are done. 42 01:57.400 --> 01:59.400 So we have a couple of neighborships that came up. 43 01:59.400 --> 02:03.400 Also our tunnel came up, our tunnel over from us to the rendezvous point. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 43 01:59.400 --> 02:03.400 Also our tunnel came up, our tunnel over from us to the rendezvous point. 44 02:03.400 --> 02:07.540 So now if we do a show IPM around here, we shouldn't show any custom groups 45 02:07.540 --> 02:09.400 because we haven't sent any traffic to custom groups. 46 02:09.400 --> 02:13.290 So these are by default what are being used by Cisco router, part of which is 47 02:13.290 --> 02:14.400 being used for auto RP. 48 02:14.400 --> 02:17.400 But we know who our RP is already because we hard coded it. 49 02:17.400 --> 02:22.400 We know show IP PIM, base question mark, RP, base question mark. 50 02:22.400 --> 02:23.400 That would be enough. 51 02:23.400 --> 02:24.400 And there's our RP of 222. 52 02:24.400 --> 02:26.400 So let's go ahead and source some traffic. 53 02:26.400 --> 02:28.400 So based on the lab tasks. 54 02:28.400 --> 02:31.650 So here in the lab tasks is asking us to join the interface gig 2 0 to the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 54 02:28.400 --> 02:31.650 So here in the lab tasks is asking us to join the interface gig 2 0 to the 55 02:31.650 --> 02:35.860 multicast group that we're going to create the content for and then generate 56 02:35.860 --> 02:37.400 that traffic by doing a ping. 57 02:37.400 --> 02:41.400 And I think it'd be wise just for a moment to do a ping first. 58 02:41.400 --> 02:45.310 Look at the rendezvous point and look at its m route table just to verify that 59 02:45.310 --> 02:49.660 it does not yet have or won't have any outgoing interface for that new group of 60 02:49.660 --> 02:51.400 2 24 6 7 8 3. 61 02:51.400 --> 02:55.400 Until we actually join that group on our one. 62 02:55.400 --> 02:57.400 So let's do the ping first and then we'll join the group. 63 02:57.400 --> 03:03.660 So when our four is to a ping to the multicast group of two 24 that 67.8.3 and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 63 02:57.400 --> 03:03.660 So when our four is to a ping to the multicast group of two 24 that 67.8.3 and 64 03:03.660 --> 03:09.400 we'll source it from interface and that's going to be interface gig 2 0. 65 03:09.400 --> 03:11.400 So that's going to create our multicast stream. 66 03:11.400 --> 03:22.400 So if we go back to our two if we hit the up arrow key now to show IP em route. 67 03:22.400 --> 03:22.830 It's now going to show that it knows about that s comma g that source comma 68 03:22.830 --> 03:24.990 group information for that multicast stream, but the outgoing interface list is 69 03:24.990 --> 03:25.400 null. 70 03:25.400 --> 03:27.400 That's until we have somebody who needs it. 71 03:27.400 --> 03:32.090 So let's go to our four next and let's join that group on its gig 2 0 interface WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 71 03:27.400 --> 03:32.090 So let's go to our four next and let's join that group on its gig 2 0 interface 72 03:32.090 --> 03:32.400 . 73 03:32.400 --> 03:37.940 So we'll go to configuration mode interface gig 2 slash 0 and we'll type in IP 74 03:37.940 --> 03:39.400 I GMP join group. 75 03:39.400 --> 03:43.400 And we want to join that same group to 24 67.8.3 and we'll press enter. 76 03:43.400 --> 03:47.660 And now if we go back to our two who is our rendezvous point previously it had 77 03:47.660 --> 03:51.880 null for the outgoing interface list and now based on our topology, which will 78 03:51.880 --> 03:53.400 bring up just a little bit here. 79 03:53.400 --> 03:54.400 I think we could bigger. 80 03:54.400 --> 03:58.650 It should now have interface gig 1 0 as inclusion in the outgoing interface 81 03:58.650 --> 04:02.730 list because our one made a request for that multicast group and as a result WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 81 03:58.650 --> 04:02.730 list because our one made a request for that multicast group and as a result 82 04:02.730 --> 04:05.400 gig 1 0 on our two should now be forwarding it. 83 04:05.400 --> 04:10.400 Now the request from our one to our two regarding that group is via PIM. 84 04:10.400 --> 04:14.090 So a client making requests for a group to join a group would be via I GMP and 85 04:14.090 --> 04:18.400 whatever software that client is using like a VLC player or something similar. 86 04:18.400 --> 04:22.400 So let's go back to our two and let the up arrow key the same show IP em route. 87 04:22.400 --> 04:26.000 So this time for that same s comma g the source address comma and the group 88 04:26.000 --> 04:27.400 address and check it out. 89 04:27.400 --> 04:30.400 And now here it's still showing us no I wonder if it just timed out. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 89 04:27.400 --> 04:30.400 And now here it's still showing us no I wonder if it just timed out. 90 04:30.400 --> 04:34.400 Let me go back to router four and let's go ahead. 91 04:34.400 --> 04:36.400 Oh, and I joined it on the wrong stinking router. 92 04:36.400 --> 04:37.400 I joined it here. 93 04:37.400 --> 04:42.400 That won't harm anything, but I do want to join the group over on R1. 94 04:42.400 --> 04:46.400 I want to generate the traffic from R4, but I want to join that group on R1. 95 04:46.400 --> 04:49.290 So if you didn't join the group that'd be a reason why the outgoing interface 96 04:49.290 --> 04:50.400 list wasn't populated. 97 04:50.400 --> 04:53.400 So we'll go to interface gig two slash zero. 98 04:53.400 --> 04:56.400 I'm going to go to my topology make sure it's the right one here. 99 04:56.400 --> 05:02.140 So router one gig two slash zero and was an IP, I GMP join and we'll join the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 99 04:56.400 --> 05:02.140 So router one gig two slash zero and was an IP, I GMP join and we'll join the 100 05:02.140 --> 05:04.400 group 224.67.8.3. 101 05:04.400 --> 05:09.960 And now that we've joined that crew, let's go ahead and go back to R2, which a 102 05:09.960 --> 05:12.400 moment ago didn't have any outgoing interface list. 103 05:12.400 --> 05:16.400 And we'll go ahead and do a show IP em route and look at that same group and it 104 05:16.400 --> 05:16.400 . 105 05:16.400 --> 05:18.400 Now it's timed out. 106 05:18.400 --> 05:22.400 So let's go back to our four and generate that stream of traffic again. 107 05:22.400 --> 05:24.400 So we'll go ahead and do a ping. 108 05:24.400 --> 05:26.400 Now we have that flow of traffic. 109 05:26.400 --> 05:30.440 Now if we go back to R2 and we have the up arrow key into a show IP em route WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 109 05:26.400 --> 05:30.440 Now if we go back to R2 and we have the up arrow key into a show IP em route 110 05:30.440 --> 05:32.400 and we go down to that entry. 111 05:32.400 --> 05:37.400 Here's our source, group information and we have our outgoing interface list. 112 05:37.400 --> 05:42.210 And as a result of R1 joining that we should be getting responses here at R4 113 05:42.210 --> 05:43.400 from that ping. 114 05:43.400 --> 05:49.100 So if we do that ping again, we should get responses coming back from both R4 115 05:49.100 --> 05:52.400 locally because it has joined the group and also from R1. 116 05:52.400 --> 05:54.400 We've got R1 reflected right here. 117 05:54.400 --> 05:58.960 So if we went back to R4 and went into interface gig two slash zero, let's do a 118 05:58.960 --> 06:03.400 do show run interface gig two slash zero and it has joined that group. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 118 05:58.960 --> 06:03.400 do show run interface gig two slash zero and it has joined that group. 119 06:03.400 --> 06:06.400 Let's go ahead and do a no and I'm going to unjoin that group. 120 06:06.400 --> 06:12.340 So now if we do a ping to that same multi cast group again, we should only be 121 06:12.340 --> 06:17.280 getting responses coming back from 10 dot 10 dot zero dot one, which is our one 122 06:17.280 --> 06:17.400 . 123 06:17.400 --> 06:21.110 The reason we're not getting a response back from R4 is our four is no longer a 124 06:21.110 --> 06:22.400 member of that group. 125 06:22.400 --> 06:26.040 So thanks for joining me in this set of videos regarding multi cast concepts 126 06:26.040 --> 06:29.780 and also for this lab regarding hands on working with multi cast, which 127 06:29.780 --> 06:35.000 included accidentally a little bit of troubleshooting because I joined at one WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 127 06:29.780 --> 06:35.000 included accidentally a little bit of troubleshooting because I joined at one 128 06:35.000 --> 06:37.400 point, the wrong router's interface to the group. 129 06:37.400 --> 06:39.400 So that troubleshooting is just a little cherry on the top. 130 06:39.400 --> 06:43.430 So hopefully this set of videos is a good introduction to some of the concepts 131 06:43.430 --> 06:47.420 regarding multi cast and multi cast routing and we'll go further into multi 132 06:47.420 --> 06:50.400 cast in other courses and in other sets of videos. 133 06:50.400 --> 06:54.400 So once again, thanks for joining me in this set of videos and in the skill. 134 06:54.400 --> 06:58.400 I hope this has been informative and I'd like to thank you for viewing.