From: Fred Ingham (fingham@xxxxxxx)
Date: Sun Aug 25 2002 - 19:27:59 GMT-3
!!!
!!
!
Jin: I agree with the other post that both frame interfaces have to be
point-to-point for this to work. If one interface is a multipoint there
will be no outgoing interface on the middle router and the pings will be
dropped. Output when both interfaces are point-to-point:
On my middle router mroute table (your r2):
(172.16.123.3, 224.100.100.100), 00:11:03/00:03:23, flags: FT
Incoming interface: Serial0/0.124, RPF nbr 172.16.123.3
Outgoing interface list:
Serial0/0.14, Forward/Sparse-Dense, 00:11:03/00:03:12
where s0/0.124 is the p-t-p interface to the ping source
172.16.123.3 is the ping source (your r3)
s0/0.14 is the p-t-p interface to the RP/MA and the ethernet interface in
group 224.100.100.100 (your r1)
and pings to 224.100.100.100 from the end router (your r3):
Reply to request 29 from 172.16.14.4, 220 ms
Reply to request 30 from 172.16.14.4, 232 ms
Reply to request 31 from 172.16.14.4, 332 ms
. (14.4 is the serial interface on
the RP/MA).
.
Reply to request 51 from 172.16.14.4, 172 ms
HTH, Fred
----- Original Message -----
From: "jin" <jin10101010@hotmail.com>
To: <ccielab@groupstudy.com>
Sent: Sunday, August 25, 2002 5:06 AM
Subject: Multicasting ! Go to the Hell!
> It's so difficult. And I can't understand.
> I have read so many book. But I'm still confused.
>
> Network is below like the one that we already have been discussed with it
during several months.
>
> ether-r1--r2--r3-ether. All router links are F/R and 2 ethernet of r1 and
r3.
> R2 is not a hub router. r1-r1 and r2-r3 is different network.
>
> Now this is the problem.
> If r1 has a igmp join group like 224.100.100.100, and r1 is a Auto-RP and
MA, r2 can ping to the 224.100.100.100 but r3 can't.
> I checked pim rp mapping and rpf table.
> When I check the mroute table after pinging to the 224.100.100.100 on the
r3, mroute table show that ping's next hop is ethernet of r3.
> And there is no outgoing interface, saying NULL. But 'sh ip pim rp
mapping' show me the next hop of the 224.100.100.100 is r1's loopback,which
is set by ip pim send-rp-announce <intf> scope.
> I don't understand what's wrong.
>
> Is there something mistaken?
> Please let me know.
>
> PS.
> routing table is good. I know multicast rpf first check the igp table. And
I'm sure my igp table is almost complete.
>
> I saw this discussion this year early. But also there was no solution.
> And please let me doing basic command, like that 'do not use the ip pim
nbma with sparse-dense mode'..
> If I don't know about it basically, I won't post this discussion.
>
> Thanks Group.
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:48:37 GMT-3