From: Dino Costantini (dino.costantini@gmail.com)
Date: Thu Jun 12 2008 - 04:11:16 ART
Hello all,
I already posted this message to the online board but I didn't see in
the mail archive, so I assume it wasn't sent to the mailing list. If
this is a duplicate I apologize for the error.
I am studying multicast at the moment and I am having some issues with
bidirectional PIM.
I have a frame-relay hub and spoke topology, the hub R1 is also the
auto-rp mapping agent and the RP.
To the fastethernet interface of R1 there is a host configured as a receiver.
The sender is behing one of the spoke (R2) and behind the other spoke
(R3) there is another host listening to multicast.
I am flooding the auto-rp information through "ip pim autorp listener"
configured on all routers.
If I configure the routers to use PIM sparse-mode it works perfectly.
If I configure the routers to use Bidirectional PIM the host behing
the hub can receive all the multicast packets, the host behind the
second spoke doesn't receive anything although the spoke is on R1
oilist:
[I attach the whole output as maybe someone may find some errors in my config]
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: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
(*, 224.0.1.39), 00:12:23/stopped, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet2/0, Forward/Sparse, 00:12:23/00:00:00
Loopback0, Forward/Sparse, 00:12:23/00:00:00
Serial1/0, Forward/Sparse, 00:12:23/00:00:00
(1.1.1.1, 224.0.1.39), 00:11:46/00:02:43, flags: LT
Incoming interface: Loopback0, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet2/0, Forward/Sparse, 00:11:46/00:00:00
Serial1/0, Prune/Sparse, 00:11:46/00:00:45
(*, 224.0.1.40), 00:12:24/00:02:34, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Loopback0, Forward/Sparse, 00:12:24/00:00:00
Serial1/0, Forward/Sparse, 00:12:24/00:00:00
The multicast group is 226.2.2.2, 1.1.1.1 if the RP (R1) loopback
address. R2 loopback is 2.2.2.2 and R3 loopback is 3.3.3.3.
R2 and R3 are in the neighbor list of R1:
R1#sh ip pim neighbor
PIM Neighbor Table
Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority,
S - State Refresh Capable
Neighbor Interface Uptime/Expires Ver DR
Address Prio/Mode
10.1.1.2 Serial1/0 03:06:08/00:01:36 v2 1 / B S
10.1.1.3 Serial1/0 03:06:08/00:01:40 v2 1 / B S
This is (relevant part of) the configuration of R1:
ip multicast-routing
ip pim bidir-enable
ip pim rp-address 1.1.1.1
ip pim autorp listener
ip pim send-rp-announce Loopback0 scope 16 bidir
ip pim send-rp-discovery scope 10
interface Serial1/0
ip address 10.1.1.1 255.255.255.0
ip pim dr-priority 200
ip pim nbma-mode
ip pim sparse-mode
encapsulation frame-relay
no ip mroute-cache
ip ospf priority 255
serial restart-delay 0
frame-relay map ip 10.1.1.2 120 broadcast
frame-relay map ip 10.1.1.3 130 broadcast
frame-relay interface-dlci 120
frame-relay interface-dlci 130
frame-relay interface-dlci 140
frame-relay lmi-type ansi
interface FastEthernet2/0
ip address 192.168.200.200 255.255.255.0
ip pim sparse-mode
ip igmp version 3
duplex auto
speed auto
This is the R2 configuration:
ip pim bidir-enable
ip pim autorp listener
interface Serial1/0
ip address 10.1.1.2 255.255.255.0
ip pim nbma-mode
ip pim sparse-mode
encapsulation frame-relay
ip ospf priority 0
serial restart-delay 0
frame-relay map ip 10.1.1.3 110 broadcast
frame-relay map ip 10.1.1.1 110 broadcast
frame-relay interface-dlci 110
frame-relay lmi-type ansi
interface FastEthernet2/0
ip address 10.192.169.1 255.255.255.0
ip pim sparse-mode
ip igmp version 3
duplex auto
speed auto
And the R3 configuration:
ip pim bidir-enable
ip pim spt-threshold infinity !used when in sparse-mode
interface Serial1/0
ip address 10.1.1.3 255.255.255.0
ip pim nbma-mode
ip pim sparse-mode
encapsulation frame-relay
ip ospf priority 0
serial restart-delay 0
frame-relay map ip 10.1.1.1 110
frame-relay map ip 10.1.1.4 110 broadcast
frame-relay map ip 10.1.1.2 110 broadcast
frame-relay interface-dlci 110
frame-relay lmi-type ansi
interface FastEthernet2/0
ip address 10.192.168.1 255.255.255.0
ip pim sparse-mode
ip igmp version 3
duplex auto
speed auto
Consider that removing all the commands relative to bidirectional PIM
(ip pim bidir-enable) and restoring the sparse mode (ip pim
send-rp-announce Loopback0 scope 16, without the bidir in the end) the
configuration works perfectly
Finally the output of a debug ip mpacket and debug ip mroute on R1:
*Jun 11 23:51:24.855: 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
R1#
*Jun 11 23:51:27.779: 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
R1#
*Jun 11 23:51:30.591: 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
R1#
*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
^^^^^^^^^^^
Does this on top look wrong to any of you?
It then continues:
*Jun 11 23:51:36.319: 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:36.539: MRT(0): Update Serial1/0/224.0.1.39 in the olist
of (1.1.1.1, 224.0.1.39), Prune state - MAC not built
*Jun 11 23:51:36.547: MRT(0): Add Serial1/0/224.0.1.39 to the olist of
(1.1.1.1, 224.0.1.39), Prune state - MAC not built
R1#
*Jun 11 23:51:39.095: 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
I know this is quite long for a first post but I looked for a solution
in google/cisco/CCIE colleagues but I didn't find any answer, and I
wanted to give all the information which are relevant in my opinion.
Can anyone help me with this? If you are in Dublin I can repay with a
beer or a coffee! :)
Thanks.
Dino Costantini
PS
Let me know if some information is missing and I will provide the
information needed as soon as I can.
This archive was generated by hypermail 2.1.4 : Tue Jul 01 2008 - 06:23:21 ART