Re: [j-nsp] MPLS LSP Load Balance

2011-02-03 Thread Jonathan Woolley
the label 112233 on interfaces X,Y > > and > > > Z , every single packet will be routed using the same interface ex: X > and > > > never will use Y or Z > > > > > > We already have configured the forwarding-option hash algorith but is > not > >

Re: [j-nsp] MPLS LSP Load Balance

2011-02-03 Thread Thedin Guruge
gt; > never will use Y or Z > > > > We already have configured the forwarding-option hash algorith but is not > > working > > > > Txs > > Ezequiel > > > > -- > > *From*: Matthew Tighe > > *To*: Telmo Di Leva > > *Cc*: juniper-nsp@pu

Re: [j-nsp] MPLS LSP Load Balance

2011-02-03 Thread Matthew Tighe
the forwarding-option hash algorith but is not > working > > Txs > Ezequiel > > -- > *From*: Matthew Tighe > *To*: Telmo Di Leva > *Cc*: juniper-nsp@puck.nether.net ; Ezequiel > Carson; Andres Arturo Diaz Montes > *Sent*: Thu Feb 03 10:47:27 2

Re: [j-nsp] MPLS LSP Load Balance

2011-02-03 Thread Matthew Tighe
Do you have multiple LSPs defined (one for each path you want to load balance over)? On Tue, Feb 1, 2011 at 6:46 PM, Telmo Di Leva wrote: > Dear JNSP, in this oportunity we are contacting you because we have the > following trouble: > Our core plataform is based on M20 and M160. > For some reaso

[j-nsp] MPLS LSP Load Balance

2011-02-01 Thread Telmo Di Leva
Dear JNSP, in this oportunity we are contacting you because we have the following trouble: Our core plataform is based on M20 and M160. For some reason, we cant balance mpls traffic thru multiples oc3. We have this links explaining our limitation whit M series: http://www.juniper.net/techpubs/en_U