From: steveaggie@gmail.com
Date: Wed Dec 26 2007 - 16:10:14 ART
Sorry, I forgot to say that I have "ip autorp listener" enabled on all of
the routers and R2 is the RP.
From: George Goglidze [mailto:goglidze@gmail.com]
Sent: Wednesday, December 26, 2007 1:08 PM
To: steveaggie@gmail.com
Subject: Re: IEWB Lab 4 Task 5.3
Hi There,
You've got sparse-mode PIM enabled, and I did not see any RP's.
Sparse-mode does not work without RP.
Regards,
On Dec 26, 2007 7:18 PM, < steveaggie@gmail.com
<mailto:steveaggie@gmail.com> > wrote:
Can someone help me understand why multicast is not working correctly on the
following network:
R1------R2-----R3
-Frame Relay hub and spoke. R2 is the hub.
-R1 & R3 connect using P2P sub-interfaces (s1/0.1)
-R2 uses the physical interface (s1/0)
-R3 has a static IGMP join to 225.25.25.25 on its e0/0 interface
-I try to ping 225.25.25.25 from the e0/0 interface on R1
-A few replies are received and then nothing
-From the debugs it appears R3 is trying to join the SPT to R1 and for some
reason R2 sends R3 a Register-Stop message.
R1:
interface Serial1/0.1 point-to-point
ip address 141.1.123.1 255.255.255.0
ip pim sparse-mode
ip ospf network non-broadcast
ip ospf priority 0
frame-relay interface-dlci 102
R2:
interface Serial1/0
ip address 141.1.123.2 255.255.255.0 <http://255.255.255.0>
ip pim dr-priority 100
ip pim nbma-mode
ip pim sparse-mode
encapsulation frame-relay
serial restart-delay 0
frame-relay map ip 141.1.123.1 201 broadcast
frame-relay map ip 141.1.123.3 203 broadcast
no frame-relay inverse-arp
frame-relay lmi-type ansi
R3:
interface Serial1/0.1 point-to-point
ip address 141.1.123.3 255.255.255.0
ip pim sparse-mode
ip ospf network non-broadcast
ip ospf priority 0
frame-relay interface-dlci 302
Debugs from R3:
Rack1R3#
*Mar 1 03:49:12.219: PIM(0): Insert (141.1.123.1, <http://225.25.25.25>
225.25.25.25) sgr prune in
nbr 141.1.123.2's queue
*Mar 1 03:49:12.223: PIM(0): Send v2 Register to 150.1.2.2 for 141.1.123.1,
group 225.25.25.25
*Mar 1 03:49:12.235: PIM(0): Insert ( 192.10.1.1 <http://192.10.1.1>
,225.25.25.25) join in nbr
141.1.123.2's queue
*Mar 1 03:49:12.243: PIM(0): Building Join/Prune packet for nbr 141.1.123.2
*Mar 1 03:49:12.247: PIM(0): Adding v2 (192.10.1.1/32, 225.25.25.25), S-bit
Join
*Mar 1 03:49:12.251: PIM(0): Adding v2 (141.1.123.1/32, 225.25.25.25),
RPT-bit, S-bit Prune
*Mar 1 03:49:12.255: PIM(0): Send v2 join/prune to 141.1.123.2
(Serial1/0.1)
Rack1R3#
*Mar 1 03:49:12.271: PIM(0): Received v2 Register-Stop on Serial1/0.1 from
150.1.2.2
*Mar 1 03:49:12.271: PIM(0): for source 141.1.123.1, group 225.25.25.25
*Mar 1 03:49:12.275: PIM(0): Clear Registering flag to 150.1.2.2 for
(141.1.123.1/32, 225.25.25.25)
Rack1R3#
*Mar 1 03:49:15.639: PIM(0): Received v2 Join/Prune on Ethernet0/0 from
141.1.37.7, to us
*Mar 1 03:49:15.643: PIM(0): Join-list: ( 141.1.123.1/32, 225.25.25.25),
S-bit set
*Mar 1 03:49:15.647: PIM(0): Update Ethernet0/0/141.1.37.7 to ( 141.1.123.1
<http://141.1.123.1> ,
225.25.25.25), Forward state, by PIM SG Join
*Mar 1 03:49:15.651: PIM(0): Join-list: (192.10.1.1/32
<http://192.10.1.1/32> , 225.25.25.25),
S-bit set
*Mar 1 03:49:15.655: PIM(0): Update Ethernet0/0/141.1.37.7 to (192.10.1.1,
225.25.25.25), Forward state, by PIM SG Join
Rack1R3#
*Mar 1 03:49:19.691: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit)
Prune message for 225.25.25.25 <http://225.25.25.25>
*Mar 1 03:49:19.695: PIM(0): Insert (*,225.25.25.25) join in nbr
141.1.123.2's queue
*Mar 1 03:49: 19.695: PIM(0): Insert (141.1.123.1,225.25.25.25) sgr prune
in
nbr 141.1.123.2 <http://141.1.123.2> 's queue
*Mar 1 03:49:19.703: PIM(0): Building Join/Prune packet for nbr 141.1.123.2
*Mar 1 03:49:19.707: PIM(0): Adding v2 ( 150.1.2.2/32 <http://150.1.2.2/32>
, 225.25.25.25),
WC-bit, RPT-bit, S-bit Join
*Mar 1 03:49:19.711: PIM(0): Adding v2 (141.1.123.1/32
<http://141.1.123.1/32> , 225.25.25.25),
RPT-bit, S-bit Prune
*Mar 1 03:49:19.715: PIM(0): Send v2 join/prune to 141.1.123.2
(Serial1/0.1)
This archive was generated by hypermail 2.1.4 : Tue Jan 01 2008 - 12:04:32 ARST