Hello again, this is your host Habib Korea and in this topic we will be discussing sparse mode with auto Rp. In this lab it is going to be somewhat practical and someone needed in today's infrastructures. So auto RP became very important. But before we go into the lab three let's first go back into why do we need auto RP and how did it emerge into the networking world. First of all, this is a Cisco proprietary solution. As most of the organizations moved from dense mode to sparse mode, there needed to be some something else added to enhance the role of these routes.

Automatically. So auto discovery or to announcement of the rendezvous point routers became a necessity especially for large organizations. That's when Cisco introduced auto Rp. So, basically as you have seen in the previous lab configuring static RP in each routers will consume time in large companies to resolve this issue or to RP was introduced by Cisco to make this work there are steps to be followed and in this lab we will cover that. So, once you basically establish a total convergence using any of the IGP interior gateway protocols like OSPF eigrp Rip version two and you have full convergence in your network you will start to basically choose one of the main routers to announce itself as or as a rendezvous point. And in that role, we will have to add a command known as auto RP announce.

That's what we will see in our lab. The announcement of that router will actually carried out through the multicast address which is two to four dot zero dot one dot three nine this this this role is also now known as candidate RP role and this router, this announcement will go to another router or even to the same router that is a that's a rendezvous point and You will add the second role which is the auto RP discovery or the mapping agent. The router will be a mapping agent for the rest of the routers on the network and this router will announce the location of the rendezvous point using the multicast address two to four dot zero dot one dot 40 this node will is known as the mapping agent obviously and other routers will be getting this information from the brand new from the discovery from the mapping agent and they will basically create an RP map for the RP address depending on what the mapping agent is telling them.

Now on all the other routes They need a mechanism to discover this information and to to learn from the mapping agent and for that all the routers need to have another command known as auto RP listener. And basically this will be applied to all the routers including the mapping mapping age and including the the rendezvous point. router. Basically, we are moving on to lab three sparse mode with auto RP there are tasks to be completed. Number one is to implement and verify Pim sparse mode operation and Jason C's. Task number two is implement and verify the rendezvous point r1 should be the RP r four would be the mapping agent Just test the solution.

So, this is similar to the previous lab that we did this is dmvpn network with four sites and basically r1 which is the one in the on the top is the is the main hub of the network r two r three and r four are the spokes. So the configuration of dmvpn is is already done. What we will do is basically configure the loopback addresses which I think the loopback addresses are already added, but we will we will implement the IP multicast configuration on all the routers first and make sure that there's adjacency formed across the across the network. Okay, so let's start I will bring up The router one console and move on to all the other routers. Okay, so I have the console for router one. So the first thing I would like to do is look at the interfaces on router one.

So show IP interface interface brief. And as you can see I have three interfaces one is Fast Ethernet zero slash 01 is the loopback address zero and one is the tunnel one. And so basically first thing we need to do is really add the IP multicast routing in and apply that to router one. So let's start that. So that's the first step that You need to do in any router that will be participating in IP multicast network. The other thing that we need to do is we need to add IP Pim sparse mode into the interfaces that will be participating in the IP multicast network.

So we will select interface loopback zero and first thing we will do is I add the protocol IP Pim sparse mode. So that's completed and the other interface that we will we will add in the IP multicast network will be the tunnel one. So, so if I go to interface, channel one, I'll do the same thing IP Pim sparse mode. So so far I think we are comfortable in doing this and doing it for all the routers. So let's save the the change in the configuration and router one and let me bring up route to choose console. Okay, so similarly I have the router to console here.

So if I do show IP interface brief, I'll see the interfaces and so the first thing that I need to do is IP multicast routing should be added to the router and and I'm going to basically add loopback zero and tunnel one to the Pim sparse mode. Okay, so interface loopback zero IP Pim sparse mode and interface tunnel one IP Pim sparse mode. Let me save that. Okay so I will I will bring the router three console. So we have the console here for router three. So let me just do show IP interface brief come t IP multicast routing.

If you don't add IP multicast routing and you start going into the interface and typing IP Pim sparse mode, the router will give you a message saying that You need to really add IP multicast routing into global mode so just remember that so now we'll do the same thing interface to pack zero IP Pim sparse mode and interface. tunnel one IP Pim sparse mode. I'll bring the console for router three. I mean router four. So let's do the same thing show IP interface brief. We do have the interfaces again, we have to do coffee.

T IP multicast routing and let me go to interface loopback zero IP Pim sparse mode and then interface tunnel one. IP Pim sparse mode. So the configuration of the Pim sparse mode is now completed. What we will do next is to find the neighboring relationship between the routers, and we'll continue. Let me bring the console for r1 to verify the neighbor relationship Here's the console for r1. So the command to verify Pim neighbor, ship relationships in in, in a router is his show IP Pim neighbor, if I do show IP, Pim m neighbor and as you can see, I can see all the three neighboring routers, which is basically the tunnel interfaces and it's showing me the uptime and and it's showing me the relationship mode.

So basically S stands for sparse mode. Dr. Means are four is acting as the DR router and that's how you verify if there is a Pim neighbor ship relationship. stablished. If for some reason you don't see all the problems, From your hub or from the main router, that means one of these interfaces still need to have Pim sparse mode configuration completed. And that will be the only reason and you can see basically from the, from the changes as we added the Pim sparse mode, you could see that the neighbors neighbor ship was getting stablished on the tunnel interfaces. I hope that is clear.

So we completed now, task one and now we are moving into task number two, which is implemented verify the rendezvous point. And so what we will do is for our one, we will actually choose loopback zero to be our to be our rendezvous point for this network. So the way we can do it is basically go into the global config mode. And we will add the command which is IP, Pim and Rp. And now loopback zero scope. scope is basically the number of hops for this announcement to reach and we don't have more than 10.

So I usually choose 10. That should be enough. And the other command I would like to do is Choose one of the other routers which is let's say our four to be our mapping agent. So let me bring up the console for our for our forests here and let's go to the global config mode and and this is the command for the mapping agent, IP Pim send RP discovery loopback zero scope. So that is completed now. Now, what we will do is in most of these routers we have to add in all of the all of these routers we have to add the RP listener command Okay, so here what we will do is we will add IP Pim auto Rp.

Similarly if I bring if I bring up other routers so let me go back to our to and I'll do the same thing called T. IP, auto auto RP listener. Let me bring our three and our four So, the IP Pim auto RP listener is is configured. The next step is to choose one of the loopback addresses as basically as a receiver. And what we will do is let me choose Yeah, let's, let's basically test this solution. So let me go to our four and basically choose choose the interface loopback zero and make it so it can join ip igmp join a group. So loopback zero is going to join a group of multicast address two to four dot 10 dot 10 dot 10.

So I'm assuming that this loopback address is basically a streaming device and from from the receiver and which is going to be our two, I'm going to ping to four dot 10 dot 10 10 and let's see what happens. Okay, so I was looking at why the reply didn't come but it finally came. And the reason for that delay was basically because the location of our for in a dmvpn environment is it's difficult I mean our four is located in behind dmvpn tunnel. My recommendation always when it comes to this design is really make the the announcer and the mapping agent to be in To be in the hub or the main router, and that is much better because in hub and spoke topology, most of the spokes are any way talking to the hub router. Unless you implement dmvpn in phase three mode, which is basically multipoint GRP tunnel where all the spokes can talk to each other.

But in most of the cases in many of the companies I've seen dmvpn is implemented in phase two situation. And basically phase three is in is in open progress mode for some of the organizations I worked with, and because it really requires a lot of work to complete phase three But anyway, we are successful in our lab. As you can see, we have added the auto Rp. And successfully we have in summary, we have made all the routers to have auto RP listener command. So they're all listening to all the routers and to the to the, to the to the discovered to the mapping agent. So if somebody asked you well how do you check the multicast router routing table it's very simple.

So show IP route is the command and you will be able to see all the the routing table for this and you can see actually the so yeah, this is the group that we were pinging. And these are all the groups that you can see that are making the announcements. So as I said, I mean, two to four dot zero dot one dot 39 is actually the announcer group. And it's it has asterik on its source. So basically announcing this multicast group to to this guy which is the which is the multicast mapping agent route and two to four dot zero dot one dot 40 is basically the person or the router responsible to announce the rendezvous point on the network. And with this lab, I conclude today's this topic and I hope to see you in the next topic which is going to be basically an open standard of auto Rp.

Auto RP, as you know is a Cisco proprietary proprietary and and bootstrap is basically an open standard and it's almost similar to auto Rp. Thank you