[j-nsp] Multicast configuration
Harry Reynolds
harry at juniper.net
Wed Sep 22 12:50:58 EDT 2004
I might me mistaken here, but I seem to recall that static joins in JUNOS
software would generate S,G state, but would not actually flood traffic out
the associated interface unless a real join was received. IOW, the
downstream interface for the static join may be pruned.
What app are you using on the PC, and can it generate a real join? We use
wsend/wlisten in classes.
HTHs again.
> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net
> [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of
> Christian Malo
> Sent: Wednesday, September 22, 2004 9:28 AM
> To: juniper-nsp at puck.nether.net
> Subject: RE: [j-nsp] Multicast configuration
>
> yeah it didn't make sense. By mistake I removed the fe-0/0/0
> interface from the output. (wanted to edit out fe-0/0/3)
>
>
> On Wed, 22 Sep 2004, Harry Reynolds wrote:
>
> > Also, it strikes me that the static joins are on the wrong
> interface.
> > The joins should point to the PC, which you identify as being on
> > fe-0/0/0. Joins are not needed for the sender.....
> >
> >
> >
> > > -----Original Message-----
> > > From: Christian Malo [mailto:chris at fiberpimp.net]
> > > Sent: Wednesday, September 22, 2004 8:41 AM
> > > To: Harry Reynolds
> > > Cc: juniper-nsp at puck.nether.net
> > > Subject: RE: [j-nsp] Multicast configuration
> > >
> > >
> > >
> > > Instance: PIM.master
> > >
> > > Name Stat Mode IP V State Count DR address
> > > fe-0/0/3.11 Up Dense 4 2 NotDR 1 *.*.*.*
> > > ge-0/1/0.991 Up Dense 4 2 DR 0 *.*.*.*
> > > lo0.0 Up Dense 4 2 DR 0 *.*.*.*
> > >
> > > ge-0/1/0.991 is the streaming server.
> > >
> > > fe-0/0/0 is the PC.
> > >
> > > traceoptions {
> > > file pim size 500k files 4;
> > > flag hello detail;
> > > flag rp detail;
> > > }
> > > dense-groups {
> > > 224.0.1.39/32;
> > > 224.0.1.40/32;
> > > }
> > > interface lo0.0 {
> > > mode dense;
> > > version 2;
> > > }
> > > interface ge-0/1/0.991 {
> > > mode dense;
> > > version 2;
> > > }
> > > interface fe-0/0/0.0 {
> > > mode dense;
> > > version 2;
> > > }
> > > interface fxp0.0 {
> > > disable;
> > > }
> > >
> > > [edit protocols]
> > > chris at core1.mtl1# show igmp
> > > traceoptions {
> > > file igmp;
> > > flag leave detail;
> > > flag report detail;
> > > flag query detail;
> > > flag state detail;
> > > flag normal detail;
> > > }
> > > query-response-interval 5;
> > > interface ge-0/1/0.991 {
> > > version 3;
> > > static {
> > > group 224.123.123.100;
> > > group 224.123.123.101;
> > > group 224.123.123.102;
> > > group 224.123.123.103;
> > > group 224.123.123.104;
> > > }
> > > }
> > >
> > >
> > > On Wed, 22 Sep 2004, Harry Reynolds wrote:
> > >
> > > > You are correct. A TS PIC is not needed for PIM DM.
> > > >
> > > > Perhaps some configuration snips from the Juniper and the
> > > OP of show
> > > > pim interfaces commands would get things rolling?
> > > >
> > > > Regards
> > > >
> > > >
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: juniper-nsp-bounces at puck.nether.net
> > > > > [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of
> > > Christian
> > > > > Malo
> > > > > Sent: Wednesday, September 22, 2004 8:27 AM
> > > > > To: juniper-nsp at puck.nether.net
> > > > > Subject: [j-nsp] Multicast configuration
> > > > >
> > > > > 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
>
More information about the juniper-nsp
mailing list