From: Alexei Monastyrnyi (alexeim@orcsoftware.com)
Date: Thu Mar 23 2006 - 05:46:07 GMT-3
Hi.
You have to add mroute on the router with multicast receivers, next hop
should point through your PIM upstream interface.
A.
on 23/03/2006 02:26 Victor Cappuccio wrote:
> Hello List, is there any way to know which is the next hop for ip
> mroute in a multi-access media??
>
> I have a multicast topology like this
>
> 228.22.22.22 |==E0= R2 -S0---------S0-R5 -S1 ----S0-- R1 =E0 ==== E0
> = R3-- |
>
> All the interfaces are running ip pim sparse-dense-mode, and the
> problem is that the RPF Fails, because there is a ppp link between R2
> and R3 and the unicast routing prefers that link to reach destinations
> in R3/R2, so where do you put the ip mroute 0.0.0.0 255.255.255.255
> (on R2 or R3?) and which is the next hop required?
>
>
> Rack1R3#show ip pim interface
>
> Address Interface Ver/ Nbr Query DR DR
> Mode Count Intvl Prior
> 136.1.3.3 Ethernet0/0 v2/SD 0 30 1
> 136.1.3.3
> 136.1.136.3 Ethernet0/1 v2/D 1 30 1
> 136.1.136.3
>
> ====
> Rack1R1#ping 228.22.22.22 source 136.1.136.1 (this is the network
> where R3 also is)
>
> Type escape sequence to abort.
> Sending 1, 100-byte ICMP Echos to 228.22.22.22, timeout is 2 seconds:
> Packet sent with a source address of 136.1.136.1
> .
> Rack1R1# Rack1R1#ping 228.22.22.22
> Type escape sequence to abort.
> Sending 1, 100-byte ICMP Echos to 228.22.22.22, timeout is 2 seconds:
>
> Reply to request 0 from 136.1.245.2, 176 ms
> Rack1R1#
> ====
>
> Rack1R1#show ip pim neighbor
> PIM Neighbor Table
> Neighbor Interface Uptime/Expires Ver DR
> Address
> Prio/Mode
> 136.1.136.3 FastEthernet0/0 01:22:25/00:01:29 v2 1 /
> DR S
> 136.1.15.5 Serial0/0 03:31:31/00:01:25 v2 1 /
> DR S
>
>
>
>
> Thanks
> Victor.
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sat Apr 01 2006 - 10:07:39 GMT-3