From: Rich Collins (nilsi2002@gmail.com)
Date: Fri Jun 13 2008 - 15:22:21 ART
Hi Dino,
I tried your setup and couldn't get it to work either. I scouted around and
always saw reference to broadcast or point-to-point links. I would deduce
that bidir just doesn't work for a point-to-multipoint frame-relay
interface.
If you change your hub to 2 pt-to-pt subinterfaces then it will work.
-Rich
On Thu, Jun 12, 2008 at 8:34 PM, Dino Costantini <dino.costantini@gmail.com>
wrote:
> Hello,
>
> This is the output of the debug on R1 (the hub) and R2 (the spoke with the
> receiver).
>
> R1:
> *Jun 13 01:14:45.371: PIM(0): Received v2 Join/Prune on Serial1/0 from
> 10.1.1.3, to us
> *Jun 13 01:14:45.375: PIM(0): Join-list: (*, 226.2.2.2), RPT-bit set,
> WC-bit set, S-bit set
> *Jun 13 01:14:45.383: PIM(0): Add Serial1/0/10.1.1.3 to (*, 226.2.2.2),
> Forward state, by PIM *G Join
> *Jun 13 01:14:47.643: PIM(0): Building Periodic Join/Prune message for
> 226.2.2.2
>
> R1#sh ip mroute
> IP Multicast Routing Table
> Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C -
> Connected,
> L - Local, P - Pruned, R - RP-bit set, F - Register flag,
> T - SPT-bit set, J - Join SPT, M - MSDP created entry,
> X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
> U - URD, I - Received Source Specific Host Report,
> Z - Multicast Tunnel, z - MDT-data group sender,
> Y - Joined MDT-data group, y - Sending to MDT-data group
> Outgoing interface flags: H - Hardware switched, A - Assert winner
> Timers: Uptime/Expires
> Interface state: Interface, Next-Hop or VCD, State/Mode
>
> (*, 226.2.2.2), 00:04:26/00:02:58, RP 1.1.1.1, flags: B
> Bidir-Upstream: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Serial1/0, 10.1.1.3, Forward/Sparse, 00:00:31/00:02:58
>
> (*, 224.0.1.39), 01:00:41/stopped, RP 0.0.0.0, flags: DCL
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Serial1/0, Forward/Sparse, 01:00:41/00:00:00
> Loopback0, Forward/Sparse, 01:00:41/00:00:00
> FastEthernet2/0, Forward/Sparse, 01:00:41/00:00:00
>
> (1.1.1.1, 224.0.1.39), 01:00:40/00:02:49, flags: LT
> Incoming interface: Loopback0, RPF nbr 0.0.0.0
> Outgoing interface list:
> Serial1/0, Forward/Sparse, 00:00:03/00:00:00
> FastEthernet2/0, Forward/Sparse, 01:00:40/00:00:00
>
> (*, 224.0.1.40), 01:00:48/00:01:56, RP 0.0.0.0, flags: DCL
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Serial1/0, Forward/Sparse, 01:00:17/00:00:00
> Loopback0, Forward/Sparse, 01:00:48/00:00:00
>
> *Jun 13 01:15:17.767: PIM(0): Received v2 Join/Prune on Serial1/0 from
> 10.1.1.3, to us
> *Jun 13 01:15:17.771: PIM(0): Join-list: (*, 226.2.2.2), RPT-bit set,
> WC-bit set, S-bit set
> *Jun 13 01:15:17.775: PIM(0): Update Serial1/0/10.1.1.3 to (*, 226.2.2.2),
> Forward state, by PIM *G Join
> *Jun 13 01:15:21.151: PIM(0): Send RP-reachability for 226.2.2.2 on
> Serial1/0
> *Jun 13 01:15:36.363: PIM(0): check pim_rp_announce 1
> *Jun 13 01:15:36.363: PIM(0): send rp announce
> *Jun 13 01:15:36.439: PIM(0): Received v2 Join/Prune on Serial1/0 from
> 10.1.1.3, to us
> *Jun 13 01:15:36.443: PIM(0): Prune-list: (1.1.1.1/32, 224.0.1.39)
> *Jun 13 01:15:36.447: PIM(0): Add Serial1/0/10.1.1.3 to (1.1.1.1,
> 224.0.1.39), Prune state, by PIM SG Prune
> *Jun 13 01:15:36.479: PIM(0): Received v2 Join/Prune on Serial1/0 from
> 10.1.1.2, to us
> *Jun 13 01:15:36.479: PIM(0): Prune-list: (1.1.1.1/32, 224.0.1.39)
> *Jun 13 01:15:36.483: PIM(0): Add Serial1/0/10.1.1.2 to (1.1.1.1,
> 224.0.1.39), Prune state, by PIM SG Prune
> *Jun 13 01:15:38.583: PIM(0): Received v2 Join/Prune on Serial1/0 from
> 10.1.1.2, to us
> *Jun 13 01:15:38.587: PIM(0): Prune-list: (1.1.1.1/32, 224.0.1.39)
> *Jun 13 01:15:38.591: PIM(0): Add Serial1/0/10.1.1.2 to (1.1.1.1,
> 224.0.1.39), Prune state, by PIM SG Prune
> *Jun 13 01:15:43.679: PIM(0): Received v2 Join/Prune on Serial1/0 from
> 10.1.1.3, to us
> *Jun 13 01:15:43.683: PIM(0): Prune-list: (1.1.1.1/32, 224.0.1.39)
> *Jun 13 01:15:43.683: PIM(0): Add Serial1/0/10.1.1.3 to (1.1.1.1,
> 224.0.1.39), Prune state, by PIM SG Prune
> *Jun 13 01:15:46.359: PIM(0): Building Periodic Join/Prune message for
> 226.2.2.2
> *Jun 13 01:16:16.687: PIM(0): Received v2 Join/Prune on Serial1/0 from
> 10.1.1.3, to us
> *Jun 13 01:16:16.691: PIM(0): Join-list: (*, 226.2.2.2), RPT-bit set,
> WC-bit set, S-bit set
> *Jun 13 01:16:16.695: PIM(0): Update Serial1/0/10.1.1.3 to (*, 226.2.2.2),
> Forward state, by PIM *G Join
>
> R3:
> *Jun 13 01:14:47.407: PIM(0): Building Triggered Join/Prune message for
> 226.2.2.2
> *Jun 13 01:14:47.407: PIM(0): Insert (*,226.2.2.2) join in nbr 10.1.1.1's
> queue
> *Jun 13 01:14:47.415: PIM(0): Building Join/Prune packet for nbr 10.1.1.1
> *Jun 13 01:14:47.419: PIM(0): Adding v2 (1.1.1.1/32, 226.2.2.2), WC-bit,
> RPT-bit, S-bit Join
> *Jun 13 01:14:47.423: PIM(0): Send v2 join/prune to 10.1.1.1 (Serial1/0)
> *Jun 13 01:15:17.215: PIM(0): Received v2 DF on Serial1/0 from 10.1.1.1
> *Jun 13 01:15:19.791: PIM(0): Building Periodic Join/Prune message for
> 226.2.2.2
> *Jun 13 01:15:19.795: PIM(0): Insert (*,226.2.2.2) join in nbr 10.1.1.1's
> queue
> *Jun 13 01:15:19.799: PIM(0): Building Join/Prune packet for nbr 10.1.1.1
> *Jun 13 01:15:19.799: PIM(0): Adding v2 (1.1.1.1/32, 226.2.2.2), WC-bit,
> RPT-bit, S-bit Join
> *Jun 13 01:15:19.799: PIM(0): Send v2 join/prune to 10.1.1.1 (Serial1/0)
> *Jun 13 01:15:23.187: PIM(0): Received RP-Reachable on Serial1/0 from
> 1.1.1.1
> *Jun 13 01:15:23.191: PIM(0): Received RP-Reachable on Serial1/0 from
> 1.1.1.1
> *Jun 13 01:15:23.191: for group 226.2.2.2
> *Jun 13 01:15:23.195: PIM(0): Update RP expiration timer (270 sec) for
> 226.2.2.2
> R3#sh ip mroute
> IP Multicast Routing Table
> Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C -
> Connected,
> L - Local, P - Pruned, R - RP-bit set, F - Register flag,
> T - SPT-bit set, J - Join SPT, M - MSDP created entry,
> X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
> U - URD, I - Received Source Specific Host Report,
> Z - Multicast Tunnel, z - MDT-data group sender,
> Y - Joined MDT-data group, y - Sending to MDT-data group
> Outgoing interface flags: H - Hardware switched, A - Assert winner
> Timers: Uptime/Expires
> Interface state: Interface, Next-Hop or VCD, State/Mode
>
> (*, 226.2.2.2), 00:04:11/00:02:17, RP 1.1.1.1, flags: BC
> Bidir-Upstream: Serial1/0, RPF nbr 10.1.1.1
> Outgoing interface list:
> FastEthernet2/0, Forward/Sparse, 00:00:47/00:02:17
> Serial1/0, 226.2.2.2, Bidir-Upstream/Sparse, 00:04:11/00:00:00
>
> (*, 224.0.1.39), 01:00:15/00:02:48, RP 0.0.0.0, flags: DC
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Serial1/0, Forward/Sparse, 01:00:15/00:00:00
>
> (*, 224.0.1.40), 01:00:38/stopped, RP 0.0.0.0, flags: DCL
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Serial1/0, Forward/Sparse, 01:00:26/00:00:00
> Loopback0, Forward/Sparse, 01:00:38/00:00:00
>
> (10.1.1.1, 224.0.1.40), 00:59:55/00:02:42, flags: LT
> Incoming interface: Serial1/0, RPF nbr 0.0.0.0
> Outgoing interface list:
> Loopback0, Forward/Sparse, 00:59:56/00:00:00
>
> R3#
> *Jun 13 01:15:38.479: PIM(0): Insert (1.1.1.1,224.0.1.39) prune in nbr
> 10.1.1.1's queue
> *Jun 13 01:15:38.483: PIM(0): Building Join/Prune packet for nbr 10.1.1.1
> *Jun 13 01:15:38.487: PIM(0): Adding v2 (1.1.1.1/32, 224.0.1.39) Prune
> *Jun 13 01:15:38.491: PIM(0): Send v2 join/prune to 10.1.1.1 (Serial1/0)
>
>
> The group 266.2.2.2 multicast packets don't reach R3.
>
> I also tried to change the OSPF network type to point-to-multipoint on all
> the nodes, it didn't change anything. Do you have any other ideas?
>
> I can't do any other experiment now as it is 1.30AM.
>
> Thanks for your support! Together we can defeat Bidirectional PIM! :)
>
> Dino
>
>
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Tue Jul 01 2008 - 06:23:21 ART