[j-nsp] Multicast configuration

[Leonard Giuliano]

I think Harry may be right, that the dense-groups may be only needed for
sparse-dense mode.  But the explicit config for the auto-RP may be
overriding the defaults.  I agree that the best start is to either config
the whole range or delete it altogether.  Then try a "show pim join
extensive" as well as a "show multicast route extensive" and see what that
says.

-Lenny

On Wed, 22 Sep 2004, Harry Reynolds wrote:

-) I thought dense-groups was only needed only when operating in sparse-dense
-) mode.  Based on Leonard's feedback, and the config snippets, I would either
-) open the dense-group range as suggested, or loose it all together and test
-) again; the docs do not indicate it is needed for basic dense mode. If it is
-) needed then we should file a doc PR. Please let me know.
-)
-) Right now the dense groups you have defined only support auto-RP...
-)
-) HTHs
-)
-)
-)
-) > -----Original Message-----
-) > From: juniper-nsp-bounces at puck.nether.net
-) > [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of
-) > Leonard Giuliano
-) > Sent: Wednesday, September 22, 2004 8:42 AM
-) > To: Christian Malo
-) > Cc: juniper-nsp at puck.nether.net
-) > Subject: Re: [j-nsp] Multicast configuration
-) >
-) >
-) > Config is very simple.  Only special thing to remember is
-) > that you need to explicitly state what the dense group range
-) > is.  This is a feature that prevents groups from accidentally
-) > falling into dense mode, if say, RP mapping is lost.
-) >
-) > pim {
-) >     dense-groups {
-) >         224.0.0.0/4;
-) >     }
-) >     interface all {
-) >         mode dense;
-) >     }
-) > }
-) >
-) > No need for tunnel pics.  They are only needed to encap/decap
-) > PIM-SM register messages.
-) >
-) > -Lenny
-) >
-) > On Wed, 22 Sep 2004, Christian Malo wrote:
-) >
-) > -) Hi list,
-) > -)
-) > -) I have to start doing some multicast on my backbone. As a
-) > 1st step I want
-) > -) to do a basic setup using PIM-DM.
-) > -)
-) > -) I currently have:
-) > -)
-) > -) stream-server <-> 6509 <-> Juniper <-> 6509 <-> PC
-) > -)
-) > -) it's the same 6509 on 2 different vlans and IGMP is
-) > enabled on the 6509.
-) > -)
-) > -)
-) > -) I tried to do some basic igmp/pim configuration and it
-) > still doesn't work.
-) > -) I know that the streaming via multicast works because when
-) > I put my pc on
-) > -) the same vlan I get the streaming fine via the multicast feed.
-) > -)
-) > -) I was just wondering if any of you guys had a simple
-) > config for that kind
-) > -) of setup.
-) > -)
-) > -) I'm also wondering if I need a TS PIC. From what I read, I
-) > will only need
-) > -) it when I start doing PIM-SM.
-) > -)
-) > -)
-) > -) The router is receiving:
-) > -)
-) > -) Sep 22 11:23:58 IGMP RECV *.*.*.* -> 224.123.123.102 V2
-) > Membership Report: group 224.123.123.102 length 8
-) > -)
-) > -) but nothing happens afterwards.
-) > -)
-) > -)
-) > -) -chris
-) > -) _______________________________________________
-) > -) juniper-nsp mailing list juniper-nsp at puck.nether.net
-) > -) http://puck.nether.net/mailman/listinfo/juniper-nsp
-) > -)
-) > _______________________________________________
-) > juniper-nsp mailing list juniper-nsp at puck.nether.net
-) > http://puck.nether.net/mailman/listinfo/juniper-nsp
-) >
-)
-) _______________________________________________
-) juniper-nsp mailing list juniper-nsp at puck.nether.net
-) http://puck.nether.net/mailman/listinfo/juniper-nsp
-)