So for this hands-on lab,
we have R1, R2, and R3 that are already configured and ready to go.
That way we can focus our attention on R4 to enable multi-cast routing,
to specify who the rendezvous point is,
which we're going to use R2 as the rendezvous point.
So I'll make a note here,
R2 at 2.2.2.2 is the rendezvous point.
Also, I'll put the helpful and useful commands regarding
this lab in the text as part of the skills.
If you want to refer to them there,
you can see them there as well.
Then once you've enabled multi-cast routing, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Then once you've enabled multi-cast routing,
you've enabled the interfaces for PIM and you specify the rendezvous point,
I'd then like you to go to R1 and join the multi-cast group of 224.67.83
on its gig two zero interface.
So see interface is 10.10.0.1.
Then once you've joined that group, I like you to go to R4 and then PING that
group address.
That traffic should be forwarded over to R2,
who's the rendezvous point, and then down the tree,
down to R1, who will receive the PING request
and should be able to respond.
Now the responses are simply going to be unicast back to the source. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Now the responses are simply going to be unicast back to the source.
And then we sourced it from gig two zero on R4,
which is 23.1.2.4.
That reply traffic from R1 to R4 is going to go based on the normal IPv4
unicast routing table.
But the initial flow for the PING request
are going to be going down the multi-cast tree.
And then once you have that configured and working,
I would invite you to play around with some show commands like show IPPMRP,
show IPPM interface, show IPigMP interface, and show IPM route. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
show IPPM interface, show IPigMP interface, and show IPM route.
So have some fun with this hands on lab.
And when you are done, join me in the walkthrough video,
which is coming up next.