NTllect:I have no idea why and how it has worked for me: I have RP mappings on all devices, all interfaces are in PIM sparse mode as per requirements,
without configuring '
ip pim autorp listner' on any router. Hardly confused.
This is what i noticed, i assume your C-RP are using R5 E0/1 and R1 F0/0 for the C-RP announcement like what SG answers is showing.
I saw the effects of this 'ip pim autorp listner'. Initially i was Loopback for the C-RP announcemnt for both R5 an R1.
Without using the 'ip pim autorp listner', SW2 M-agent is only able to learn the group from R5, which means R3 is learning only M group 232.0.0.0 only.
Rack1SW2#sh ip pim rp map
PIM Group-to-RP Mappings
This system is an RP-mapping agent
Group(s) 232.0.0.0/5
RP 150.1.5.5 (?), v2v1
Info source: 150.1.5.5 (?), elected via Auto-RP
Uptime: 00:04:28, expires: 00:02:30
Rack1SW2#
I revisited my IE notes, it mentioned Auto-RP announcement subject to RP check. I used a static mroute on R1 to point to SW2, but SW2 still didnt manage
to learn the M-group from R1.
Once i started to put 'ip pim autorp listner', SW2 M-agent is able to know the groups from both R5 & R1
Rack1SW2#sh ip pim rp map
PIM Group-to-RP Mappings
This system is an RP-mapping agent
Group(s) 224.0.0.0/5
RP 150.1.1.1 (?), v2v1
Info source: 150.1.1.1 (?), elected via Auto-RP
Uptime: 00:00:06, expires: 00:02:51
Group(s) 232.0.0.0/5
RP 150.1.5.5 (?), v2v1
Info source: 150.1.5.5 (?), elected via Auto-RP
Uptime: 00:04:28, expires: 00:02:30
Rack1SW2#
Also, any idea why isnt SG using loopback on C-RP for announcement?