[Xorp-users] Mcast issues

Fri Sep 16 09:12:21 PDT 2011

On 09/16/2011 07:44 AM, Patricio Latini wrote:
> Garry, thanks for your response, I changed the groups to all of them in the 239.x.x.x range however the behaivior is the same. Do you know any useful command to
> troubleshoot this?

There are definitely bugs in 1.8.3, so please make sure you try the 1.8.4
or compile from latest github source tree (which is 1.8.4).

We've been testing ipv4 multicast lately and it works for us.  We are
having troubles with IPv6, but not sure if it's xorp related
yet...

As always, make sure your generator has TTL high enough..it's
usually 1 by default which will not route.

Thanks,
Ben

>
> Patricio
>
> xorp at dns> show pim mfc
>
> Group Source RP
>
> 229.255.0.1 172.16.4.254 0.0.0.0
>
> Incoming interface : vlan30
>
> Outgoing interfaces: ............O
>
> 239.1.0.1 172.16.4.254 172.16.1.9
>
> Incoming interface : vlan30
>
> Outgoing interfaces: .............
>
> 239.2.0.1 172.16.4.14 172.16.1.9
>
> Incoming interface : vlan30
>
> Outgoing interfaces: .............
>
> 239.3.0.1 172.16.4.10 172.16.1.9
>
> Incoming interface : vlan30
>
> Outgoing interfaces: ...........O.
>
> xorp at dns> show pim mfc
>
> Group Source RP
>
> 229.255.0.1 172.16.4.254 0.0.0.0
>
> Incoming interface : vlan30
>
> Outgoing interfaces: ............O
>
> 239.1.0.1 172.16.4.254 172.16.1.9
>
> Incoming interface : vlan30
>
> Outgoing interfaces: .............
>
> 239.2.0.1 172.16.4.14 172.16.1.9
>
> Incoming interface : vlan30
>
> Outgoing interfaces: .............
>
> 239.3.0.1 172.16.4.10 172.16.1.9
>
> Incoming interface : vlan30
>
> Outgoing interfaces: ...........O.
>
> xorp at dns> show igmp group
>
> Interface Group Source LastReported Timeout V State
>
> vlan12 224.0.0.2 0.0.0.0 172.16.1.9 28 2 E
>
> vlan12 224.0.0.5 0.0.0.0 172.16.1.9 20 2 E
>
> vlan12 224.0.0.6 0.0.0.0 172.16.1.9 19 2 E
>
> vlan12 224.0.0.13 0.0.0.0 172.16.1.9 28 2 E
>
> vlan12 224.0.0.22 0.0.0.0 172.16.1.9 27 2 E
>
> vlan12 224.0.0.251 0.0.0.0 172.16.1.9 28 2 E
>
> vlan15 224.0.0.2 0.0.0.0 172.16.1.21 29 2 E
>
> vlan15 224.0.0.5 0.0.0.0 172.16.1.21 25 2 E
>
> vlan15 224.0.0.6 0.0.0.0 172.16.1.21 26 2 E
>
> vlan15 224.0.0.22 0.0.0.0 172.16.1.21 24 2 E
>
> vlan15 224.0.0.251 0.0.0.0 172.16.1.21 26 2 E
>
> vlan15 239.3.0.1 0.0.0.0 172.16.1.22 23 2 E
>
> vlan30 224.0.0.2 0.0.0.0 172.16.4.1 28 3 E
>
> vlan30 224.0.0.13 0.0.0.0 172.16.4.1 28 3 E
>
> vlan30 224.0.0.22 0.0.0.0 172.16.4.1 28 3 E
>
> vlan30 224.0.0.251 0.0.0.0 172.16.4.1 28 3 E
>
> vlan31 224.0.0.2 0.0.0.0 172.16.5.1 25 2 E
>
> vlan31 224.0.0.13 0.0.0.0 172.16.5.1 29 2 E
>
> vlan31 224.0.0.22 0.0.0.0 172.16.5.1 23 2 E
>
> vlan31 224.0.0.251 0.0.0.0 172.16.5.1 27 2 E
>
> vlan31 239.3.0.1 0.0.0.0 172.16.5.2 21 2 E
>
> xorp at dns> show igmp interface
>
> Interface State Querier Timeout Version Groups
>
> eth0 DISABLED 0.0.0.0 None 2 0
>
> vlan10 DISABLED 172.16.1.1 None 2 0
>
> vlan11 DISABLED 172.16.1.5 None 2 0
>
> vlan12 UP 172.16.1.9 None 2 6
>
> vlan13 DISABLED 172.16.1.13 None 2 0
>
> vlan14 DISABLED 172.16.1.17 None 2 0
>
> vlan15 UP 172.16.1.21 None 2 6
>
> vlan18 DISABLED 0.0.0.0 None 2 0
>
> vlan19 DISABLED 0.0.0.0 None 2 0
>
> vlan20 DISABLED 172.16.3.1 None 2 0
>
> vlan30 UP 172.16.4.1 None 3 4
>
> vlan31 UP 172.16.5.1 None 2 5
>
> *From:*xorp-users-bounces at xorp.org [mailto:xorp-users-bounces at xorp.org] *On Behalf Of *Garry Peirce
> *Sent:* Friday, September 16, 2011 11:13 AM
> *To:* xorp-users at xorp.org
> *Subject:* Re: [Xorp-users] Mcast issues
>
> Just a general comment/suggestion re: mcast issues.
>
> If you are experiencing mcast issues it is very difficult for anyone to provide insight when the entire picture is not supplied.
>
> Help others help you - provide your XORP config (anonymize addressing consistently if you need to) , the entire relevant topology, and IGMP/PIM/MFEA state.
>
> Otherwise it can result in numerous back/forth messages to try and get the full picture and those assisting may become disinterested or available in continuing
> to help solve your issue. I suppose this holds true for any type of problem, but mcast is enough of a different bird that it certainly helps to provide as much
> info as possible.
>
> Oren: perhaps your routers have some PIM adjacency/RP/mapping issue so traffic cannot reach the RP.
>
> [ 2011/09/15 14:28:14.465824 WARNING xorp_pimsm4 PIM ] JoinDesired(S,G) = false: upstream neighbor for source 10.0.0.1 and group 224.5.6.7: not found
>
> Patricio: you show some IGMP info but nothing of PIM state. I’d change your addressing to avoid 32:1 overlap. The addresses you chose to use for two different
> services will end up using the same L2 address which may make other troubleshooting more difficult as well as pass both streams to all participating NICs only
> to be dropped. Sensing your addressing did not actually have SSM/GLOP needs, you might move these, for example, into the 239.x.x.x block.
>
>
>
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users

-- 
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com