Yes, R3 has the joins and I can not ping them from R3.
The are no other connections between the routers.
After pinging from R1 - here are R2 and R3's ip mroute.
R2
(*, 224.24.24.24), 00:10:22/stopped, RP 2.2.2.2, flags: S
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/0, 150.1.123.3, Forward/Sparse, 00:10:22/00:02:59
(1.1.1.1, 224.24.24.24), 00:01:08/00:02:28, flags: T
Incoming interface: Serial0/0, RPF nbr 150.1.123.1
Outgoing interface list:
Serial0/0, 150.1.123.3, Forward/Sparse, 00:01:08/00:03:21
(3.3.3.3, 224.24.24.24), 00:00:11/00:02:48, flags: PT
Incoming interface: Serial0/0, RPF nbr 150.1.123.3
Outgoing interface list: Null
(*, 224.32.32.32), 00:10:23/00:02:56, RP 2.2.2.2, flags: S
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/0, 150.1.123.3, Forward/Sparse, 00:10:23/00:02:56
(*, 224.0.1.39), 00:53:34/stopped, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/0, Forward/Sparse, 00:53:20/00:00:00
Loopback0, Forward/Sparse, 00:53:20/00:00:00
(2.2.2.2, 224.0.1.39), 00:53:34/00:02:25, flags: LT
Incoming interface: Loopback0, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/0, Prune/Sparse, 00:00:33/00:03:00
(*, 224.0.1.40), 00:55:09/stopped, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/0, Forward/Sparse, 00:48:41/00:00:00
Loopback0, Forward/Sparse, 00:55:10/00:00:00
(2.2.2.2, 224.0.1.40), 00:52:35/00:02:03, flags: LT
Incoming interface: Loopback0, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/0, Forward/Sparse, 00:48:42/00:00:00
r3
(*, 224.24.24.24), 00:10:32/stopped, RP 2.2.2.2, flags: SJCLF
Incoming interface: Serial0/0, RPF nbr 150.1.123.2
Outgoing interface list:
FastEthernet0/1, Forward/Sparse, 00:10:32/00:02:06
(1.1.1.1, 224.24.24.24), 00:01:17/00:01:43, flags: LJT
Incoming interface: Serial0/0, RPF nbr 150.1.123.2
Outgoing interface list:
FastEthernet0/1, Forward/Sparse, 00:01:17/00:02:06
(3.3.3.3, 224.24.24.24), 00:00:21/00:02:38, flags: LJT
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/1, Forward/Sparse, 00:00:21/00:02:38, A
(*, 224.32.32.32), 00:10:33/00:02:01, RP 2.2.2.2, flags: SJCL
Incoming interface: Serial0/0, RPF nbr 150.1.123.2
Outgoing interface list:
FastEthernet0/1, Forward/Sparse, 00:10:33/00:02:01
(*, 224.0.1.39), 00:48:48/stopped, RP 0.0.0.0, flags: DC
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/0, Forward/Sparse, 00:48:48/00:00:00
(2.2.2.2, 224.0.1.39), 00:02:43/00:00:16, flags: PTX
Incoming interface: Serial0/0, RPF nbr 150.1.123.2
Outgoing interface list: Null
(*, 224.0.1.40), 00:59:59/stopped, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/0, Forward/Sparse, 00:48:50/00:00:00
(2.2.2.2, 224.0.1.40), 00:48:44/00:02:55, flags: PLTX
Incoming interface: Serial0/0, RPF nbr 150.1.123.2
Outgoing interface list: Null
r1(config-if)#do ping 224.24.24.24
Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 224.24.24.24, timeout is 2 seconds:
Reply to request 0 from 150.1.123.3, 188 ms
r2(config-if)# do ping 224.24.24.24
Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 224.24.24.24, timeout is 2 seconds:
Reply to request 0 from 150.1.123.3, 61 ms
Reply to request 0 from 150.1.123.3, 153 ms
r2(config-if)#
r3(config-if)# do ping 224.24.24.24
Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 224.24.24.24, timeout is 2 seconds:
.
r3(config-if)#
r1 mroute
(*, 224.24.24.24), 00:03:04/stopped, RP 2.2.2.2, flags: SP
Incoming interface: Serial0/0.123, RPF nbr 150.1.123.2
Outgoing interface list: Null
(1.1.1.1, 224.24.24.24), 00:03:04/00:02:39, flags: T
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/0.123, Forward/Sparse, 00:02:05/00:03:21
(150.1.123.2, 224.24.24.24), 00:00:57/00:02:09, flags: PT
Incoming interface: Serial0/0.123, RPF nbr 150.1.123.2
Outgoing interface list: Null
(*, 224.0.1.39), 00:46:27/stopped, RP 0.0.0.0, flags: DC
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/0.123, Forward/Sparse, 00:46:27/00:00:00
(2.2.2.2, 224.0.1.39), 00:02:30/00:00:29, flags: PT
Incoming interface: Serial0/0.123, RPF nbr 150.1.123.2
Outgoing interface list: Null
(*, 224.0.1.40), 00:46:29/stopped, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0/0.123, Forward/Sparse, 00:46:29/00:00:00
(2.2.2.2, 224.0.1.40), 00:45:36/00:02:08, flags: PLT
Incoming interface: Serial0/0.123, RPF nbr 150.1.123.2
Outgoing interface list: Null
On Wed, Aug 19, 2009 at 5:08 PM, Bryan Bartik <[email protected]> wrote:
> Mark,
>
> R3 is the one that has the joins, but you say R3 cannot ping the groups? Is
> this correct? Or did you mean R1?
>
> Also, are they any other connections between these routers?
>
> What does show ip pim mroute look like on R2 and R3 after trying to ping
> from R1?
>
> On Wed, Aug 19, 2009 at 1:54 PM, Mark Matters <[email protected]> wrote:
>
>> I have an rpf issue I am trying to resolve.
>>
>> I have 3 routers ip multicast routing, ip pim sparse, Autorp and ip pim
>> autorp listener configured.
>>
>> I can ping the igmp groups from r1 and r2 but I can not ping the groups
>> from r3. The groups are configured on r3. Looking at it again I sometimes
>> the pings will work from R1 and sometimes they do not. r3 f0/1 was saying
>> it's not an rfp interface. I added a mroute ong r3 pointing to r2 and it did
>> not do anything. I added an mroute pointing to f0/1 on r3 and it did not do
>> anything. Ip v4 pings to all interfaces work fine, so no unicast routing
>> issues.
>>
>>
>> r1, r2 and r3 and connected to each other via frame-relay. The fast
>> ethernets all go to different vlans.
>>
>>
>> r1 -
>> ip pim autorp listener
>>
>> f0/0
>> ip pim sparse mode
>> ip pim dr-priority 0
>>
>> f0/1
>> ip pim sparse mode
>> ip pim dr-priority 0
>>
>> s0/0 (fr physical)
>> ip pim sparse mode
>> ip pim dr-priority 0
>>
>>
>> r2 - hub
>> ip pim autorp listener
>>
>> f0/0
>> ip pim sparse mode
>> ip pim dr-priority 255
>>
>> loop0
>> ip pim sparse mode
>>
>> s0/0 fr hub - physical int
>> ip pim dr-priority 255
>> ip pim nbma
>> ip pim sparse mode
>>
>> ip pim send-rp-announce Loopback0 scope 16 group-list 1
>> ip pim send-rp-discovery Loopback0 scope 16
>>
>> Standard IP access list 1
>> 10 permit 224.24.24.24
>> 20 permit 224.32.32.32
>>
>>
>> r3
>> ip pim autorp listener
>>
>> f0/0
>> ip pim sparse mode
>> ip pim dr-priority 0
>>
>> f0/1
>> ip pim dr-priority 0
>> ip pim sparse mode
>> igmp join 224.24.24.24
>> igmp join 224.32.32.32
>>
>> s0/0 (fr multipoint)
>> ip pim sparse mode
>> ip pim dr-priority 0
>>
>>
>> Any idea's?
>>
>> _______________________________________________
>> For more information regarding industry leading CCIE Lab training, please
>> visit www.ipexpert.com
>>
>>
>
>
> --
> Bryan Bartik
> CCIE #23707 (R&S), CCNP
> Sr. Support Engineer - IPexpert, Inc.
> URL: http://www.IPexpert.com
>
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit
www.ipexpert.com
