I drew a diagram by myself, simulated in dynamips. I ve connected virtual machines, and running a tiny software for sending and receiving multicast. Diagram is attached.
There is no route redistribution between routing protocols. When I run this in dense mode, all fine, both receivers do receive mcast trafic generated by source.
Maybe that happens due to a lack knowledge of mine here, but here is how I configure Auto RP
ip pim send-rp-announce s0/0 scope 5
ip pim send-rp-announce s0/1 scope 5
ip pim send-rp-discovery s0/0 scope 5
ip pim send-rp-discovery s0/0 scope 5
Then I receive the following in R1
PIM-6-INVALID_RP_JOIN: Received (*, 184.108.40.206) Join from 172.16.8.250 for invalid RP 172.16.8.249 but after some time sh ip pim rp in 8.250 shows that RP is set for that group. But that error goes on prompting.
I start sending mcast traffic from mcast source connected to R1 to group 220.127.116.11. As I start, following appears in R1 debugs
Mar 1 00:38:50.331: PIM(0): Check RP 172.16.8.253 into the (*, 18.104.22.168) entry
*Mar 1 00:38:50.335: MRT(0): Create (*,22.214.171.124), RPF /0.0.0.0
*Mar 1 00:38:50.339: MRT(0): (192.168.1.4,126.96.36.199), RPF install from /0.0.0.0 to Ethernet0/0/0.0.0.0
*Mar 1 00:38:50.343: MRT(0): Reset the z-flag for (192.168.1.4, 188.8.131.52)
*Mar 1 00:38:50.347: MRT(0): Create (192.168.1.4,184.108.40.206), RPF Ethernet0/0/0.0.0.0
*Mar 1 00:38:57.223: PIM(0): Received v2 Join/Prune on Serial1/0 from 172.16.8.250, to us
*Mar 1 00:38:57.227: PIM(0): Join-list: (*, 220.127.116.11),, ignored, invalid RP 172.16.8.249 from 172.16.8.250
sh ip mroute output in R1 is as I want to see
(192.168.1.4, 18.104.22.168), 00:01:24/00:02:51, flags: PT
Incoming interface: Ethernet0/0, RPF nbr 0.0.0.0
Outgoing interface list: Null
Now showtime. I start receiver in mcast destination 1, then I get the following logs
*Mar 1 00:41:34.195: IGMP(0): Received v2 Report on Ethernet1/0 from 172.16.5.2 for 22.214.171.124
*Mar 1 00:41:34.199: IGMP(0): Received Group record for group 126.96.36.199, mode 2 from 172.16.5.2 for 0 sources
*Mar 1 00:41:34.203: IGMP(0): WAVL Insert group: 188.8.131.52 interface: Ethernet1/0Successful
*Mar 1 00:41:34.207: IGMP(0): Switching to EXCLUDE mode for 184.108.40.206 on Ethernet1/0
*Mar 1 00:41:34.207: IGMP(0): Updating EXCLUDE group timer for 220.127.116.11
*Mar 1 00:41:34.211: IGMP(0): MRT Add/Update Ethernet1/0 for (*,18.104.22.168) by 0
*Mar 1 00:41:34.215: PIM(0): Check RP 172.16.8.249 into the (*, 22.214.171.124) entry
*Mar 1 00:41:34.219: MRT(0): (*,126.96.36.199), RPF change from /0.0.0.0 to Serial0/0/172.16.8.249
*Mar 1 00:41:34.219: MRT(0): Create (*,188.8.131.52), RPF Serial0/0/172.16.8.249
*Mar 1 00:41:34.223: MRT(0): WAVL Insert interface: Ethernet1/0 in (* ,184.108.40.206) Successful
and the following mroute table in R2
(*, 220.127.116.11), 00:00:58/00:02:31, RP 172.16.8.249, flags: SJC
Incoming interface: Serial0/0, RPF nbr 172.16.8.249
Outgoing interface list:
Ethernet1/0, Forward/Sparse, 00:00:58/00:02:31
sh ip pim rp
Group: 18.104.22.168, RP: 172.16.8.249, v2, v1, uptime 00:13:50, expires 00:02:17
Following from R1
*Mar 1 00:41:52.811: %PIM-6-INVALID_RP_JOIN: Received (*, 22.214.171.124) Join from 172.16.8.250 for invalid RP 172.16.8.249
Same above happens when I join mcast destination 2.
I am so sure that I am missing a very basic concept here, I hope you will shed light on this one.
R1 will use either the address of s0/0 or s0/1 as the RP address, not both. If you do a "sh ip pim rp map" on R1, you will see that 172.16.8.253 is selected, hence PIM join sent to 172.16.8.249 being considered invalid.
You should use the looback interface address as the RP address to solve this issue.
ip address 172.16.8.xx
ip pim sparse-mode
no ip pim send-rp-announce s0/0
no ip pim send-rp-announce s0/1
ip pim send-rp-announce loopback0 scope 5
You will also need to advertise the loopback address in both ospf and eigrp.