From: Tony H. (aamercado31@xxxxxxxxx)
Date: Fri Aug 02 2002 - 14:28:54 GMT-3
Hi
Design wise R2 should be hosting the 2 groups and you
will find all things pingable
However with r1 hosting the 2 groups, r2 will prune
back the multicast route to r3. This is normal
behavior for Sparse mode as to decrease multicast
traffic. If you were to add some clients off r3, then
r2 will go from prune to active (join) and r3 should
be able to ping r1
--- Szeto Jeff <jytszeto@hotmail.com> wrote:
> Hi,
>
> I am practising multicast and cannot do a simple
> config.
>
>
>
--e0--R1--s0-------HDLC------s1-R2-S0------HDLC-----s1-R3
>
> R1 ethernet joined two groups:224.1.1.1 and
> 224.2.1.1
> I use sparse-dense-mode, auto-rp
> The problem is R3 cannot ping both multicast groups
> while
> R2 does.
>
> Please help, the related config is at the end,
>
> Thank you.
>
> Regards,
>
> Jeff
>
> R1
> ip multicast-routing
>
> interface Ethernet0
> ip address 172.16.20.2 255.255.255.0
> ip pim sparse-dense-mode
> ip igmp join-group 224.1.1.1
> ip igmp join-group 224.2.1.1
>
> interface Serial0
> ip address 172.16.12.2 255.255.255.0
> ip pim sparse-dense-mode
> ip pim send-rp-announce Ethernet1 scope 15
> ip pim send-rp-discovery scope 15
>
>
> R2
> ip multicast-routing
> interface Serial0
> ip address 172.16.14.1 255.255.255.0
> ip pim sparse-dense-mode
>
> interface Serial1
> ip address 172.16.12.1 255.255.255.0
> ip pim sparse-dense-mode
>
> R3
>
> ip multicast-routing
> interface Serial1
> ip address 172.16.14.4 255.255.255.0
> no ip directed-broadcast
> ip pim sparse-dense-mode
>
>
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:48:14 GMT-3