So here are the lab tasks and let's go ahead and do this walk through together.
So here's our lab environment.
Let me go ahead and double click on the topology to make sure on the right
sheet of music or the same sheet of music.
Fantastic.
And we'll go ahead and double click here on server one to get console access to
each of our devices.
Fantastic.
Let me just scooch this over a little bit over here and I'll bring our topology
down here a little bit.
In fact, I'll make it a little bit smaller and just check that down in the
bottom right hand corner.
All right, that'll do.
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
So let's do a spot check real quick on our two, which is our rendezvous point.
It should already be configured.
Let's do a show IP Emroute and sure enough, it has a couple of groups that
knows about no sources yet specified.
And we show IP PIM interface.
Fantastic.
We do a show IP, I GMP interface also fantastic.
There's all our interfaces.
So again, we'll bring up the show IP Emroute and we have no custom groups yet
because we haven't actually sent multicast traffic as if we were a multicast
server.
So let's go to R4 and let's begin the configuration. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So let's go to R4 and let's begin the configuration.
We'll go into configuration mode first and we'll do IP multicast routing
spelled multicast dash routing and we're off to the races.
Then while we're here in global config, that's specified the rendezvous point
and that's going to be IP PIM, RP dash address and that is 2.2.2.2.
Let's also verify we can reach that address with a ping to 2.2.2.2.
And sure enough, that is our two loop back acting as a rendezvous point.
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
The tunnel at the moment is down but that's because we don't yet have any PIM
enabled interfaces.
So we'll go into interface configuration mode for the three interfaces here on
R4.
So inter-page range would do the trick for us for gig 1 slash 0 comma gig 2
slash 0 comma F A 4 slash 1.
And then we use the command IP PIM and a space question mark and we want to put
them into sparse mode.
So go ahead and use the sparse mode option right there.
Right click and paste that in and we are done.
So we have a couple of neighborships that came up.
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
Also our tunnel came up, our tunnel over from us to the rendezvous point.
So now if we do a show IPM around here, we shouldn't show any custom groups
because we haven't sent any traffic to custom groups.
So these are by default what are being used by Cisco router, part of which is
being used for auto RP.
But we know who our RP is already because we hard coded it.
We know show IP PIM, base question mark, RP, base question mark.
That would be enough.
And there's our RP of 222.
So let's go ahead and source some traffic.
So based on the lab tasks.
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
So here in the lab tasks is asking us to join the interface gig 2 0 to the
multicast group that we're going to create the content for and then generate
that traffic by doing a ping.
And I think it'd be wise just for a moment to do a ping first.
Look at the rendezvous point and look at its m route table just to verify that
it does not yet have or won't have any outgoing interface for that new group of
2 24 6 7 8 3.
Until we actually join that group on our one.
So let's do the ping first and then we'll join the group.
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
So when our four is to a ping to the multicast group of two 24 that 67.8.3 and
we'll source it from interface and that's going to be interface gig 2 0.
So that's going to create our multicast stream.
So if we go back to our two if we hit the up arrow key now to show IP em route.
It's now going to show that it knows about that s comma g that source comma
group information for that multicast stream, but the outgoing interface list is
null.
That's until we have somebody who needs it.
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
So let's go to our four next and let's join that group on its gig 2 0 interface
.
So we'll go to configuration mode interface gig 2 slash 0 and we'll type in IP
I GMP join group.
And we want to join that same group to 24 67.8.3 and we'll press enter.
And now if we go back to our two who is our rendezvous point previously it had
null for the outgoing interface list and now based on our topology, which will
bring up just a little bit here.
I think we could bigger.
It should now have interface gig 1 0 as inclusion in the outgoing interface
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
list because our one made a request for that multicast group and as a result
gig 1 0 on our two should now be forwarding it.
Now the request from our one to our two regarding that group is via PIM.
So a client making requests for a group to join a group would be via I GMP and
whatever software that client is using like a VLC player or something similar.
So let's go back to our two and let the up arrow key the same show IP em route.
So this time for that same s comma g the source address comma and the group
address and check it out.
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
And now here it's still showing us no I wonder if it just timed out.
Let me go back to router four and let's go ahead.
Oh, and I joined it on the wrong stinking router.
I joined it here.
That won't harm anything, but I do want to join the group over on R1.
I want to generate the traffic from R4, but I want to join that group on R1.
So if you didn't join the group that'd be a reason why the outgoing interface
list wasn't populated.
So we'll go to interface gig two slash zero.
I'm going to go to my topology make sure it's the right one here.
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
So router one gig two slash zero and was an IP, I GMP join and we'll join the
group 224.67.8.3.
And now that we've joined that crew, let's go ahead and go back to R2, which a
moment ago didn't have any outgoing interface list.
And we'll go ahead and do a show IP em route and look at that same group and it
.
Now it's timed out.
So let's go back to our four and generate that stream of traffic again.
So we'll go ahead and do a ping.
Now we have that flow of traffic.
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
Now if we go back to R2 and we have the up arrow key into a show IP em route
and we go down to that entry.
Here's our source, group information and we have our outgoing interface list.
And as a result of R1 joining that we should be getting responses here at R4
from that ping.
So if we do that ping again, we should get responses coming back from both R4
locally because it has joined the group and also from R1.
We've got R1 reflected right here.
So if we went back to R4 and went into interface gig two slash zero, let's do a
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
do show run interface gig two slash zero and it has joined that group.
Let's go ahead and do a no and I'm going to unjoin that group.
So now if we do a ping to that same multi cast group again, we should only be
getting responses coming back from 10 dot 10 dot zero dot one, which is our one
.
The reason we're not getting a response back from R4 is our four is no longer a
member of that group.
So thanks for joining me in this set of videos regarding multi cast concepts
and also for this lab regarding hands on working with multi cast, which
included accidentally a little bit of troubleshooting because I joined at one WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
included accidentally a little bit of troubleshooting because I joined at one
point, the wrong router's interface to the group.
So that troubleshooting is just a little cherry on the top.
So hopefully this set of videos is a good introduction to some of the concepts
regarding multi cast and multi cast routing and we'll go further into multi
cast in other courses and in other sets of videos.
So once again, thanks for joining me in this set of videos and in the skill.
I hope this has been informative and I'd like to thank you for viewing.