[Xorp-users] Mcast issues

[Garry Peirce]

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. 

 

 

 

 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20110916/6ddb7223/attachment.html