From: tv (tvarriale@xxxxxxxxxxxx)
Date: Sun Jan 21 2001 - 13:13:07 GMT-3
I think you are not telling r2 to join anything. Recommendations:
Try to make a loopback on r1 the rp.
Have r2 join the multicast address.
do a show ip mroute on r2 before you ping.
Let us know how it works.
tv
----- Original Message -----
From: "Steve Clubb" <sclubb@cattech.com>
To: <ccielab@groupstudy.com>
Sent: Sunday, January 21, 2001 2:15 AM
Subject: ip multicasting and ping
> For all you multi-cast wizards out there, I have 2 routers configured as
> such:
>
> r2 cannot ping multicast 224.2.2.2-4 on r1's e0.
>
> Any reasons why?
>
> Thanks,
>
> Steve
>
>
> r1#
> ip multicast-routing
> ip dvmrp route-limit 20000
> !
> interface Ethernet0
> ip address 137.20.10.1 255.255.255.0
> ip pim sparse-mode
> ip igmp join-group 224.2.2.2
> !
> interface Serial0.2 point-to-point
> ip address 137.20.12.1 255.255.255.0
> ip pim nbma-mode
> ip pim sparse-mode
>
> r2#
> ip multicast-routing
> ip dvmrp route-limit 20000
> !
> interface Serial0
> ip address 137.20.12.2 255.255.255.0
> ip pim nbma-mode
> ip pim sparse-mode
> !
> interface TokenRing0
> ip address 137.20.22.1 255.255.255.240
> ip multicast use-functional
> ip pim sparse-mode
> !
> ip pim rp-address 137.20.12.1
>
>
> r2#ping 224.2.2.2
>
> Type escape sequence to abort.
> Sending 1, 100-byte ICMP Echos to 224.2.2.2, timeout is 2 seconds:
> ..
> r2#
>
>
>
>
>
>
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:27:37 GMT-3