From: Dino Costantini (dino.costantini@gmail.com)
Date: Thu Jun 12 2008 - 11:20:00 ART
Hello,
I don't think it is the problem as it works perfectly in sparse mode.
I mean if you take the configuration and remove from all the routers
"ip pim bidir-enable" and replace "ip pim send-rp-announce Loopback0
scope 16 bidir" with "ip pim send-rp-announce Loopback0 scope 16" (I
removed the bidir in the end) on R1 it works fine and all the listener
can receive all the traffic.
I think it may be a problem related to bidirectional PIM but I am not
sure as I wasn't able to find too much information.
I assume that R3 is in the R1 OIList as you can see from the output of
my original message:
R1#sh ip mroute
[omitting output]
(*, 226.2.2.2), 00:12:22/00:02:55, RP 1.1.1.1, flags: BC
Bidir-Upstream: Null, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet2/0, Forward/Sparse, 00:00:07/00:02:55
Serial1/0, 10.1.1.3, Forward/Sparse, 00:12:03/00:02:45
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
As you can see S1/0 is there and the ip address of R3 is listed
because of the PIM being in NBMA mode on S1/0 on R1 (it is in NBMA
mode on all routers anyway).
The only thing I am suspicious about is this debug output, but I can't
understand it:
*Jun 11 23:51:33.427: IP(0): s=10.192.169.2 (Serial1/0) d=226.2.2.2
(FastEthernet2/0) id=0, ttl=48, prot=17, len=284(284), mforward
*Jun 11 23:51:33.915: MRT(0): Update Serial1/0/10.1.1.3 in the olist
of (*, 226.2.2.2), Forward state - MAC not built
Look at the second line: "Forward state - MAC not built" I don't
understand what does it mean and I didn't find anything on the Cisco
website.
Do you have any ideas?
Thanks,
Dino
On Thu, Jun 12, 2008 at 2:28 PM, Sadiq Yakasai <sadiqtanko@gmail.com> wrote:
> Hi Dino,
>
> So I have been thinking about the scenario and I have read somewhere in the
> past where if you have OSPF NBMA mode on the FR network, which is emulating
> a multiaccess network, all PIM Join messages that R3 (Spoke) sends towards
> R1 (Hub), will be dropped by R1 because R1 thinks R3 is on the same
> multiaccess network as the source of the mcast traffic (R1).
>
> Try debugging "ip pim" and see if you actually see the PIM Join from R3
> being dropped by R1. If that actually happens, then try and change the
> network type to point-to-multipoint and see if the behaviour changes!
>
> Keep me posted please.
>
> HTH
> Sadiq
This archive was generated by hypermail 2.1.4 : Tue Jul 01 2008 - 06:23:21 ART