This topic is to discuss the following lesson:
Rene,
Based on the below entry:
"Above you can see that R2 is receiving the RP announcement traffic from R1. Let’s check R3:
R3#show ip mroute | begin 224
(*, 224.0.1.39), 00:05:28/00:01:57, RP 0.0.0.0, flags: DC
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
GigabitEthernet0/2, Forward/Sparse, 00:05:28/00:01:57
(*, 224.0.1.40), 00:27:34/stopped, RP 0.0.0.0, flags: DPL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list: Null
(2.2.2.2, 224.0.1.40), 00:04:29/00:02:29, flags: PLT
<strong>Incoming interface: GigabitEthernet0/2</strong>, RPF nbr 192.168.23.2
Outgoing interface list: Null
"
If I am not wrong, the incoming interface should be Gi0/1, which is the interface connected towards the RP mapping agent (2.2.2.2). Gi0/2 is the interface connected to GI0/4.
Let me know if I am missing something.
Thanks,
Jose
Hi Jose,
I accidently mixed the interface numbers in the topology picture. Just fixed them so it should make more sense now 
Thanks for letting me know!
Rene
Why would R2 send it to R3 ? SHouldn’t R3 have sent a PIM join to start recieving the traffic ?
Hi Suman,
Do you mean in the configuration example?
By default, all routers are listening to 224.0.1.40 once you enable PIM. They’ll listen for messages from a mapping agent.
The mapping agent will automatically send messages on its directly connected PIM enabled interfaces.
Rene
So, is this a property of mapping agent ? I will tell you where I am confused. As soon as we configure PIM on routers, they automatically have a **, 224.0.1.40) entry in their MRT. In order for them to generate PIM joins in sparse mode, some host needs to generate traffic. But in our example, we do not have any hosts which send an IGMP join to R3 and yet R2 sends the information about RP to it. Is this specific Mapping agent behaviour ?
Hi Suman,
Normally, we need a PIM join before a router will forward multicast traffic for a certain multicast group. With the mapping agent, it’s a bit different. The mapping agent will start advertising RP mapping information right away, no PIM join is needed to forward this information.
You can see this behavior when you try a “debug ip pim” on a mapping agent. It will advertise its messages on any PIM enabled interface right away.
Rene
Hi Renee,
Does autoRP provides RP redundancy? It seems that if the mapping agent dies, the RP is gone too.
Best regards,
Hans de Roode.
Hi rene, I am looking at aprod config and have a doubt
on one of Access Layer switch I see :-
-
under some VLANs “ip pim passive” and “ip cgmp” —> what do you make out of this config ?
-
under some interfaces : “ip pim sparse-dense mode” and under global “ip pim autorp listener”
why someone would configure both “ip pim sparse-dense mode” and “ip pim autorp listener” ?
Thanks in adv
Hi rene, I am looking at a prod config and have a doubt
on one of Access Layer switch I see :-
-
under some VLANs “ip pim passive” and “ip cgmp” —> what do you make out of this config ?
-
under some interfaces : “ip pim sparse-dense mode” and under global “ip pim autorp listener”
why someone would configure both “ip pim sparse-dense mode” and “ip pim autorp listener” ?
Thanks in adv
@Hans redundancy is no problem but you should configure multiple RPs AND multiple mapping agents. Otherwise a single mapping agent is your single point of failure.
@Abhishek CGMP is pretty old so it’s possible that this command is not even needed in your network. It’s used for within your L2 domain:
https://networklessons.com/cisco/ccie-routing-switching/cisco-group-management-protocol-cgmp/
The ip pim passive command means that the switch/router won’t send any PIM messages on its interface, it will also not accept any PIM messages from other devices. It forces your switch/router to become the DR. If you need PIM and you are the only PIM-enabled device, you can use this. Otherwise you should disable it.
Adding ip pim autorp listener only makes sense if you use sparse mode, not dense or sparse-dense mode.
Awesome Thanks Rene !
How come R3/R4 are mapping agents chosen in ethernet segment? What makes them mapping agent? Without PIM being configured or statically configured ??
Hello Parajuli
Although Rene doesn’t go into details in the lesson, a router is configured as a mapping agent using the following command:
ip pim send-rp-discovery
You can find out more about this command at this Cisco Command Reference Documentation (search for ip pim send-rp-discovery.
It is possible to configure two or more mapping agents within a network. Each will function independently. Engineers often misunderstand how multiple mapping agents interact and often believe that there is more complexity to such a configuration than there really is. Receiving mapping data from two or more mapping agents is not a problem because both transmit identical mapping information, so there are never any conflicts.
Conversely, the command ip pim send-rp-announce configures a router as an RP.
I hope this has been helpful!
Laz
2 Likes
If R3 has to be statically configured as MP beforehand, may be R4 can be done as well!
Regardless, in this topo, why is R4 not announcing itself as RP then?
Or this is for brevity; only for clarifying the technology?
Hello Deep
Routers will only play the role of a RP or an MA if they are statically configured as such. Specifically, to configure a router as a candidate RP and thus to have it announce itself as such, the following command must be present:
ip pim send-rp-announce
To configure a router as an MA the following command must be present:
ip pim send-rp-discovery
The above are configured on R1 and R2 respectively. R4 is not configured to announce itself as an RP so it will not do so. R4 does however recieve the information from the mapping agent because of the following command that is found on R3
ip pim autorp listener
This command allows the multicast traffic that reaches R3 to be flooded with dense mode, thus it will flood those packets to R4.
I hope this has been helpful!
Laz
Between Auto-RP and BSR, which one provides better fault tolerance? Both can have backup RP IPs.
Hello Chris
It really depends on what you want. A good explanation is given in this Cisco Community post:
The link to the white paper in the post is out of date. The following is the whitepaper related to this issue:
I hope this has been helpful!
Laz
It seems Cisco officially recommend to use sparse-dense mode rather than auto-rp listener, and dummy rp’s for the groups which don’t exist.
Which frankly makes little sense to me, as listener requires way less config!
1 Like
Hi All,
when I run a show ip pim rp to find out where the RP is on a network i get the following response:
(*, 239.0.78.141), 1w3s/00:02:54, RP 0.0.0.0
This entry is repeated for all multicast groups that transit the L3 switch. My question is, what does the 0.0.0.0 output mean? Is it saying this L3 device is the RP?
thanks
Mike