From: Scott Smith (hioctane@gmail.com)
Date: Thu Jan 26 2006 - 00:54:15 GMT-3
Thanks for the reply.
I've actually tried that config and it didn't work for me. The join is
never sent up to R2 (verified with debug). Thus far I've found three
configs that work:
1) Enable PIM on the HDLC link between R2 and R3 (preferred path from R3 to R2)
2) Place a static route (not mroute) on R3 to force traffic to R2 out
the frame int
3) Advertise R2's loopback into OSPF instead of EIGRP (side effect is
this hoses R6 but the join works <g>)
My understanding of a static mroute is: you're telling the router it
is ok to receive this source on an interface that isn't the same
interface you would use to forward traffic to this source. Right, I
hope?
-Scott
On 1/25/06, ggombas@hotmail.com <ggombas@hotmail.com> wrote:
> Hello Scott,
>
> I had the same issue a few weeks back.
> The solution is to add a 0.0.0.0 0.0.0.0 mroute on R3 pointing to the IP of R2 frame relay interface and also enable PIM NBNA mode on R3's frame relay interface.
>
> Here is the relevant config:
>
> R3
> ip multicast-routing
>
> int ser1/0
> ip pim sparse-mode
> ip pim nbma-mode
>
> ip pim rp-address 150.1.2.2
> ip mroute 0.0.0.0 0.0.0.0 132.1.0.2
>
> Although I still don't completely understand why this works Scott Morris suggested that the mroute allows R3 to send the join out the frame interface.
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Wed Feb 01 2006 - 07:45:50 GMT-3