From: Bob Sinclair (bsin@cox.net)
Date: Fri May 07 2004 - 22:15:57 GMT-3
Hi Mike,
Sounds like an interesting problem. I have to think that the failure of R2
to respond to the pings from R5 is a config or IOS issue. Can you start an
extended ping to the group address on R5, then run a sh ip mroute on R2?
You should see a "C" flag on the *,G indicating a connected member.
I have found that I can pretty reliably get sparse mode to work through the
hub with nbma mode on the hub. In other words, I have seen successful pings
from spoke to spoke.
Are you doing auto-rp? You could simplify by making sure mapping agent and
candidate are both on R5, or you could do static to R5. BTW, on recent IOS
I find that the static rp statement must also be on the RP itself.
HTH,
Bob Sinclair
CCIE #10427, CISSP, MCSE
www.netmasterclass.net
----- Original Message -----
From: "MMoniz" <ccie2002@tampabay.rr.com>
To: "Bob Sinclair" <bsin@cox.net>; "Yasser Aly" <blackyeyes00@hotmail.com>;
<sejimenez@its.co.cr>; <ccielab@groupstudy.com>
Sent: Friday, May 07, 2004 8:42 PM
Subject: RE: IP Multicast over FR!!!
> Bob, you seem very knowledgeable in mcast... can you help with this
scenario
> I posted but got no response..
>
>
> Thanks,
>
> Mike
>
>
>
> Here is the scenario. R5 is the hub and connects to R2, R3, R4 via MP
frame.
> R5 also connects to R6 via PTP frame.
>
> Running PIM sparse on the MP link with nbma mode as well. Running SD to
R6.
> R5 is the RP and MA for all groups.
>
> R2 also has a PPP link to R1, running SD on that link.
>
> On ether int's on all routers I did join mcast group 224.64.64.10.
>
> When I ping the group from R5 all routers respond except R2. After trying
> and trying I decide to put R2 on it's own frame ptp link to R5. Still the
> same results. R2 doesn't respond. R1 that is connected to R2 responds no
> problem. When I ping from R2 I get response from R5 and R1.
>
> Also, when I ping from any Rtr connected to R5, like R3, R4, etc. I only
get
> response from R5. Is this normal mcast
> behavior?
>
> Any ideas??
>
> mike
>
> R5#ping 224.64.64.10
>
> Type escape sequence to abort.
> Sending 1, 100-byte ICMP Echos to 224.64.64.10, timeout is 2 seconds:
>
> Reply to request 0 from 133.5.55.5, 8 ms
> Reply to request 0 from 133.5.12.1, 20 ms
> Reply to request 0 from 133.5.12.1, 20 ms
> Reply to request 0 from 133.5.56.6, 12 ms
> Reply to request 0 from 133.5.235.4, 12 ms
> Reply to request 0 from 133.5.235.3, 8 ms
> Reply to request 0 from 133.5.5.5, 8 ms
> R5#
>
> R6#ping 224.64.64.10
>
> Type escape sequence to abort.
> Sending 1, 100-byte ICMP Echos to 224.64.64.10, timeout is 2 seconds:
>
> Reply to request 0 from 133.5.66.6, 4 ms
> Reply to request 0 from 133.5.56.5, 24 ms
> Reply to request 0 from 133.5.6.6, 4 ms
> R6#
This archive was generated by hypermail 2.1.4 : Wed Jun 02 2004 - 11:12:06 GMT-3