From: Ian Blaney (ian.blaney@gmail.com)
Date: Mon Dec 11 2006 - 14:13:15 ART
Hi
I am pulling my hair out trying to get multicast to work over a frame-relay
hub and spoke. Any help would be
appreciated.
I have a hub (R1) and 2 spokes (R2 and R3). R3 has joined the group
224.3.3.3 and I am trying to
ping it form the other spoke R2. When I set the ospf network to
point-to-multipoint with ip pim nbma-mode
it works but when I set it to broadcast or non-broadcast the first pings
works but subsequent do not.
R2#p 224.3.3.3
Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 224.3.3.3, timeout is 2 seconds:
Reply to request 0 from 192.168.145.3, 976 ms
Reply to request 0 from 192.168.145.3, 976 ms
Reply to request 0 from 192.168.145.3, 976 ms
R2#p 224.3.3.3
Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 224.3.3.3, timeout is 2 seconds:
.
R2
If I do a repeated ping it seems to works after a certain amount of time for
a few pings.
R2#p 224.3.3.3 r 100
Type escape sequence to abort.
Sending 100, 100-byte ICMP Echos to 224.3.3.3, timeout is 2 seconds:
Reply to request 0 from 192.168.145.3, 540 ms
Reply to request 0 from 192.168.145.3, 636 ms
Reply to request 0 from 192.168.145.3, 588
ms.....................................................................
..........................
Reply to request 96 from 192.168.145.3, 448 ms
Reply to request 96 from 192.168.145.3, 544 ms
Reply to request 96 from 192.168.145.3, 452 ms...
Here is my config
HUB
R1#sh run int s1/0
Building configuration...
Current configuration : 327 bytes
!
interface Serial1/0
ip address 192.168.145.1 255.255.255.0
ip pim nbma-mode
ip pim sparse-mode
encapsulation frame-relay
ip ospf network broadcast
no ip mroute-cache
serial restart-delay 0
frame-relay map ip 192.168.145.2 102 broadcast
frame-relay map ip 192.168.145.3 103 broadcast
no frame-relay inverse-arp
end
Spokes
R2#sh run int s1/0
Building configuration...
Current configuration : 357 bytes
!
interface Serial1/0
ip address 192.168.145.2 255.255.255.0
ip pim sparse-mode
encapsulation frame-relay
ip ospf network broadcast
ip ospf priority 0
serial restart-delay 0
frame-relay map ip 192.168.145.1 201 broadcast
frame-relay map ip 192.168.145.3 201 broadcast
no frame-relay inverse-arp
end
R3#sh run int s1/0
Building configuration...
Current configuration : 309 bytes
!
interface Serial1/0
ip address 192.168.145.3 255.255.255.0
ip pim sparse-mode
encapsulation frame-relay
ip ospf network broadcast
ip ospf priority 0
serial restart-delay 0
frame-relay map ip 192.168.145.1 301 broadcast
frame-relay map ip 192.168.145.2 301 broadcast
no frame-relay inverse-arp
end
R1 is announcing itself as a RP and is also configured as
mapping agent
R1#sh run | i send-rp
ip pim send-rp-announce Loopback0 scope 16
ip pim send-rp-discovery Loopback0 scope 16
Both Spokes are seeing R1 as the RP
R2#sh ip pim rp map
PIM Group-to-RP Mappings
Group(s) 224.0.0.0/4
RP 150.1.1.1 (?), v2v1
Info source: 150.1.1.1 (?), elected via Auto-RP
Uptime: 01:32:53, expires: 00:02:27
R3#sh ip pim rp mapp
PIM Group-to-RP Mappings
Group(s) 224.0.0.0/4
RP 150.1.1.1 (?), v2v1
Info source: 150.1.1.1 (?), elected via Auto-RP
Uptime: 00:51:28, expires: 00:02:10
The ethernet interface on the spoke R3 is configured to join the group
224.3.3.3
R3#sh ip igmp gro 224.3.3.3
IGMP Connected Group Membership
Group Address Interface Uptime Expires Last
Reporter Group Accounted
224.3.3.3 Ethernet0/0 00:59:20 00:02:37 192.168.45.3
Pinging 224.3.3.3 from the other spoke works initially and then fails
R2#p 224.3.3.3
Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 224.3.3.3, timeout is 2 seconds:
Reply to request 0 from 192.168.145.3, 976 ms
Reply to request 0 from 192.168.145.3, 976 ms
Reply to request 0 from 192.168.145.3, 976 ms
R2#p 224.3.3.3
Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 224.3.3.3, timeout is 2 seconds:
.
R2
R2#p 224.3.3.3 r 100
Type escape sequence to abort.
Sending 100, 100-byte ICMP Echos to 224.3.3.3, timeout is 2 seconds:
Reply to request 0 from 192.168.145.3, 540 ms
Reply to request 0 from 192.168.145.3, 636 ms
Reply to request 0 from 192.168.145.3, 588
ms.....................................................................
..........................
Reply to request 96 from 192.168.145.3, 448 ms
Reply to request 96 from 192.168.145.3, 544 ms
Reply to request 96 from 192.168.145.3, 452 ms...
R1#sh ip mroute 224.3.3.3
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
(*, 224.3.3.3), 01:00:52/stopped, RP 150.1.1.1, flags: S
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Serial1/0, 192.168.145.3, Forward/Sparse, 01:00:43/00:02:55
(192.168.145.2, 224.3.3.3), 00:00:17/00:02:53, flags: PT
Incoming interface: Serial1/0, RPF nbr 0.0.0.0
Outgoing interface list: Null
debug ip pim
debug ip mrouting
*Mar 1 02:22:25.439: PIM(0): Received v2 Register on Serial1/0 from
192.168.145.3
*Mar 1 02:22:25.439: for 192.168.145.2, group 224.3.3.3
*Mar 1 02:22:25.447: PIM(0): Send v2 Register-Stop to 192.168.145.3 for
192.168.145.2, group 224.3.3.3
*Mar 1 02:22:25.459: PIM(0): Received v2 Join/Prune on Serial1/0 from
192.168.145.3, to us
*Mar 1 02:22:25.463: PIM(0): Prune-list: (192.168.145.2/32, 224.3.3.3)
RPT-bit set
*Mar 1 02:22:25.467: PIM(0): Prune Serial1/0/192.168.145.3 from (
192.168.145.2/32, 224.3.3.3)
*Mar 1 02:22:25.471: MRT(0): Delete Serial1/0/192.168.145.3 from the olist
of (192.168.145.2, 224.3.3.3) - deleted
R1#
*Mar 1 02:22:25.479: PIM(0): Received v2 Join/Prune on Serial1/0 from
192.168.145.3, to us
*Mar 1 02:22:25.479: PIM(0): Prune-list: (192.168.145.2/32, 224.3.3.3)
RPT-bit set
*Mar 1 02:22:25.483: PIM(0): Received v2 Register on Serial1/0 from
192.168.145.3
*Mar 1 02:22:25.487: for 192.168.145.2, group 224.3.3.3
*Mar 1 02:22:25.491: PIM(0): Send v2 Register-Stop to 192.168.145.3 for
192.168.145.2, group 224.3.3.3
*Mar 1 02:22:25.503: PIM(0): Received v2 Register on Serial1/0 from
192.168.145.3
*Mar 1 02:22:25.507: for 192.168.145.2, group 224.3.3.3
*Mar 1 02:22:25.511: PIM(0): Send v2 Register-Stop to 192.168.145.3 for
192.168.145.2, group 224.3.3.3
This archive was generated by hypermail 2.1.4 : Tue Jan 02 2007 - 07:50:37 ART