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
> >
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
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
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
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
5 matches
Mail list logo