We are still on the same LAB scenario as per the previous one. Everything is the same, but I have wiped all configuration that we have done on multicast.
What I would like to do is to make R1 as BSR and also the RP candidate. Then R2 will receive the BSR message from R1 which will include that R1 is the RP, and we will see whether R2 will be able to receive the multicast from the VLC Streaming Server and send it down to the VLC client PC.
First let me show that we do not have any configuration R1 for PIM:
Same if we look to R2 as below:
[mepr-show rules=”319″ unauth=”message”]
Remember, OSPF is still running and of course we do have the IP addresses already configured. Also, the VLC server has the route created on the Windows PC.
Let’s start adding the interfaces on R1 to work on PIM and IGMP:
I have added Ether1, I will add now Ether2:
Now Ether1 and Ether2 of R1 have been added as you see below:
You need to do the same on R2 (I will not show the steps again), so the result on R2 will be as following:
Now we need to make R1 the RP. Let’s do that directly:
Now R1 is the RP.
Before we used to go to R2 and say that R1 is the RP of the multicast group 188.8.131.52.
This time, I am going to use BSR and RP candidate, so R2 will receive a BSR message from R1 saying that R1 is the RP, then R2 will learn from the BSR that R1 is the RP of the multicast group 184.108.40.206.
To do this, we need to configure BSR Candidate and RP Candidate on R1.
Let me show you how to do that. We start with the BSR Candidate:
This makes R1 to become the BSR. I have used the complete multicast address and the BSR messages will be sent out of Ether2.
Now we need to make also R1 as an RP Candidate because he is the router that should the RP. Let me show you how you can do that:
I have created a new RP candidate and said that R1 is going to be the RP for the multicast group of 220.127.116.11. Now, when R1 sends BSR messages to other multicast-enabled routers (in our case only R2) then it mentions in the message that R1 is the RP of the multicast group 18.104.22.168
We are done on R1, let go now to R2 and see what is the result that we have.
As per above, you see that R2 has seen the BSR which is R1, and this is clearly shown on the BSR address which is the IP of R1.
What about the RP? Do you think that R2 has learned now that R1 is the RP? Let’s have a look:
Wonderful!!!! It has seen that R1 is the RP and this is clearly shown on the picture above that R1 which has the IP of 192.168.12.1 is the RP for the multicast group 22.214.171.124. If you double click on this entry, you will see it has learned about the RP from the “bootstrap” which is the BSR:
Everything up to now is working perfectly.
Let’s run now the multicast traffic to see if the VLC client will receive the multicast streaming. I will open the video on the background now and see if this is going to work on the VLC client:
Hurrayyyyy!!!! It is working ????
The last thing I want to do is to check the Rx Multicast on Ether2 of R2 to see if it is receiving the multicast traffic and if it is increasing:
I see the Rx Multicast is increasing on the Ether2 interface of R2, so the multicast traffic is flowing without any issue.
This is the end of this chapter; I hope that you have enjoyed it and I see you in the upcoming one.