From: Tony Paterra (apaterra@gmail.com)
Date: Tue May 16 2006 - 01:10:11 ART
I was going through the multicast portion of the first lab and (being
a little fresh to mcast) have noticed some unexpected behaviors. R3
is supposed to announce it's loopback as the RP for all multicast
groups and R2 is supposed to announce it's loopback as the mapping
agent. I understand these pieces, the real question... Is that I'm
running debugs and seeing RPF check failures on R5 for (150.1.2.2,
224.0.1.40) because of the unicast routing table.
Is this the way this is supposed to operate? Are there any other ways
around this outside of static mroutes or enabling multicast on the
necessary interfaces to reach R5 on the proper (ethernet0/0)
interface? If R2 is the mapping agent, does it matter that it can't
pass around the multicast address for cisco-rp-discovery?
Thanks in advance,
-- Tony Paterra apaterra@gmail.com
This archive was generated by hypermail 2.1.4 : Thu Jun 01 2006 - 06:33:21 ART