[Xorp-users] PIM IGMP troubleshooting

Fri Mar 5 12:02:13 PST 2010

Mark, 

I appreciate your assistance in this matter.  I will do what you said,
however I've found some intriguing info in the xorp logs.  Below is the
extent of IGMP related messages.  It looks like all IGMP activity is
strictly prohibited to the vif on em0.  Shouldn't I be seeing membership
reports from 10.9.8.2?  If so this could be the source of my problem.

[ 2010/03/05 14:28:49 TRACE xorp_igmp MLD6IGMP ] TX
IGMP_MEMBERSHIP_QUERY from 10.9.8.1 to 224.0.0.1
[ 2010/03/05 14:28:49 TRACE xorp_igmp MLD6IGMP ] RX
IGMP_MEMBERSHIP_QUERY from 10.9.8.1 to 224.0.0.1 on vif em0
[ 2010/03/05 14:28:50 TRACE xorp_igmp MLD6IGMP ] RX
IGMP_V2_MEMBERSHIP_REPORT from 10.9.8.1 to 224.0.0.22 on vif em0
[ 2010/03/05 14:28:56 TRACE xorp_igmp MLD6IGMP ] RX
IGMP_V2_MEMBERSHIP_REPORT from 10.9.8.1 to 224.0.0.2 on vif em0

On Fri, 2010-03-05 at 10:44 -0800, Williams, Mark wrote:
> If the tcpdump is showing that the client is issuing the IGMP join, but there is no PIM join/prune, then I would suspect there is a problem with the RP config. Get into xorpsh and issue 'show pim rps'. Also, run xorp_rtrmgr in interactive mode (not as a daemon) and watch output to console when the PC joins 239.255.255.250. 
> 
> -Mark Williams
> 
> -----Original Message-----
> From: Bernard J Hughes [mailto:bhughes at totalrecallcorp.com] 
> Sent: Friday, March 05, 2010 10:10
> To: Williams, Mark; xorp-users at xorp.org
> Subject: RE: [Xorp-users] PIM IGMP troubleshooting
> 
> I ran tcpdump ip multicast on both interfaces.  It appears that 10.8.9.2
> is indeed specifying group 239.255.255.250.  10.0.90.2 does not appear
> to be sending a PIM Join.  I also do not see the group doing a show igmp
> groups in xorp.
> 
> TCPDUMP OUTPUT
> em0:
> 11:15:27.523739 IP 10.9.8.1 > 224.0.0.1: igmp query v2
> 11:15:32.516834 IP 10.9.8.1 > 224.0.0.2: igmp v2 report 224.0.0.2
> 11:15:34.260355 IP 10.9.8.2 > 239.255.255.250: igmp v2 report
> 239.255.255.250
> 11:15:36.938512 IP 10.9.8.1 > 224.0.0.22: igmp v2 report 224.0.0.22
> 11:17:32.525481 IP 10.9.8.1 > 224.0.0.1: igmp query v2
> 11:17:37.441454 IP 10.9.8.2 > 239.255.255.250: igmp v2 report
> 239.255.255.250
> 11:17:40.946331 IP 10.9.8.1 > 224.0.0.2: igmp v2 report 224.0.0.2
> 11:17:42.554211 IP 10.9.8.1 > 224.0.0.22: igmp v2 report 224.0.0.22
> 11:19:37.527237 IP 10.9.8.1 > 224.0.0.1: igmp query v2
> 11:19:37.718683 IP 10.9.8.1 > 224.0.0.2: igmp v2 report 224.0.0.2
> 11:19:38.321655 IP 10.9.8.1 > 224.0.0.22: igmp v2 report 224.0.0.22
> 11:19:46.128847 IP 10.9.8.2 > 239.255.255.250: igmp v2 report
> 239.255.255.250
> 
> rl0:
> 
> 11:15:19.543353 IP 10.0.90.1 > 224.0.0.13: PIMv2, Hello, length 34
> 11:15:33.932209 IP 10.0.90.2 > 224.0.0.13: PIMv2, Hello, length 34
> 11:15:49.306859 IP 10.0.90.1 > 224.0.0.13: PIMv2, Hello, length 34
> 11:16:03.934213 IP 10.0.90.2 > 224.0.0.13: PIMv2, Hello, length 34
> 11:16:04.116646 IP 10.0.90.1 > 224.0.0.1: igmp query v2
> 11:16:10.101054 IP 10.0.90.2 > 224.0.0.13: igmp v2 report 224.0.0.13
> 11:16:18.626251 IP 10.0.90.1 > 224.0.0.13: PIMv2, Hello, length 34
> 11:16:33.934835 IP 10.0.90.2 > 224.0.0.13: PIMv2, Hello, length 34
> 11:16:48.105253 IP 10.0.90.1 > 224.0.0.13: PIMv2, Hello, length 34
> 11:17:03.937579 IP 10.0.90.2 > 224.0.0.13: PIMv2, Hello, length 34
> 11:17:04.517132 IP 10.0.90.1 > 224.0.0.1: igmp query v2
> 11:17:11.803492 IP 10.0.90.2 > 224.0.0.13: igmp v2 report 224.0.0.13
> 11:17:17.483155 IP 10.0.90.1 > 224.0.0.13: PIMv2, Hello, length 34
> 11:17:33.939360 IP 10.0.90.2 > 224.0.0.13: PIMv2, Hello, length 34
> 11:17:47.305961 IP 10.0.90.1 > 224.0.0.13: PIMv2, Hello, length 34
> 11:18:03.942143 IP 10.0.90.2 > 224.0.0.13: PIMv2, Hello, length 34
> 11:18:04.919607 IP 10.0.90.1 > 224.0.0.1: igmp query v2
> 11:18:10.692132 IP 10.0.90.2 > 224.0.0.13: igmp v2 report 224.0.0.13
> 11:18:16.835023 IP 10.0.90.1 > 224.0.0.13: PIMv2, Hello, length 34
> 11:18:33.944923 IP 10.0.90.2 > 224.0.0.13: PIMv2, Hello, length 34
> 11:18:46.137962 IP 10.0.90.1 > 224.0.0.13: PIMv2, Hello, length 34
> 11:19:03.946704 IP 10.0.90.2 > 224.0.0.13: PIMv2, Hello, length 34
> 11:19:05.318138 IP 10.0.90.1 > 224.0.0.1: igmp query v2
> 11:19:10.384714 IP 10.0.90.2 > 224.0.0.13: igmp v2 report 224.0.0.13
> 11:19:15.868244 IP 10.0.90.1 > 224.0.0.13: PIMv2, Hello, length 34
> 11:19:33.949480 IP 10.0.90.2 > 224.0.0.13: PIMv2, Hello, length 34
> 11:19:45.229482 IP 10.0.90.1 > 224.0.0.13: PIMv2, Hello, length 34
> 11:20:03.951266 IP 10.0.90.2 > 224.0.0.13: PIMv2, Hello, length 34
> 11:20:05.718605 IP 10.0.90.1 > 224.0.0.1: igmp query v2
> 11:20:13.896014 IP 10.0.90.2 > 224.0.0.13: igmp v2 report 224.0.0.13
> 11:20:14.557250 IP 10.0.90.1 > 224.0.0.13: PIMv2, Hello, length 34
> 
> On Thu, 2010-03-04 at 14:25 -0800, Williams, Mark wrote:
> > I would start by removing the static mrib-routes in the XORP config. Then try doing tcpdumps on em0 to see if the IGMP join is coming in, then on rl0 to see if the PIM join/prune is being sent to the RP after the IGMP join. 
> > 
> > -Mark Williams
> > 
> > -----Original Message-----
> > From: xorp-users-bounces at xorp.org [mailto:xorp-users-bounces at xorp.org] On Behalf Of Bernard J Hughes
> > Sent: Thursday, March 04, 2010 14:07
> > To: xorp-users at xorp.org
> > Subject: [Xorp-users] PIM IGMP troubleshooting
> > 
> > Below is a diagram of my current setup:
> > 
> 