From: Chris Lewis (chrlewiscsco@yahoo.com)
Date: Sat Nov 12 2005 - 12:00:24 GMT-3
I tihnk you'll have to post your configs. ip mulicast routing is not required for R1 to respond to pings to 229.10.10.10 from R2, in my setup I can enable just a join on the interface on R1 facing R2, then R2 is able to ping 229.10.10.10, the only config on R2 is to enable multicast routing and put pim dende on the interface going towards R1
Chris
"Loi, Choon Ho" <ChoonHo.Loi@getronics.com> wrote:
For this scenario:
R1(join 229.10.10.10)-----------(pim dense)R2(pim
dense)----------------(pim dense)R3
With the setup, R2 can't ping 229.10.10.10
What is the possible solution for this, if R1 can not enable ip
multicast-routing.
Following is the debug from R2:
Nov 12 05:01:24.330: IGMP(0): Received v2 Report on FastEthernet0/0 from
172.16.80.1 for 229.10.10.10
*Nov 12 05:01:24.330: IGMP(0): Received Group record for group
229.10.10.10, mode 2 from 172.16.80.1 for 0 sources
*Nov 12 05:01:24.330: IGMP(0): Updating EXCLUDE group timer for
229.10.10.10
*Nov 12 05:01:24.330: IGMP(0): MRT Add/Update FastEthernet0/0 for
(*,229.10.10.10) by 0
Sh ip mroute from R2:
(*, 229.10.10.10), 00:05:37/stopped, RP 0.0.0.0, flags: DC
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/0, Forward/Dense, 00:05:37/00:00:00
(172.16.80.2, 229.10.10.10), 00:04:58/00:01:03, flags: PT
Incoming interface: FastEthernet0/0, RPF nbr 0.0.0.0
Outgoing interface list: Null
(*, 224.0.1.40), 00:06:32/00:02:21, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/0, Forward/Dense, 00:06:32/00:00:00
This archive was generated by hypermail 2.1.4 : Thu Dec 01 2005 - 09:12:06 GMT-3