[j-nsp] Problems with Link Aggregation

[Ivan Ivanov]

Hi,

http://kb.juniper.net/InfoCenter/index?page=content&id=KB10926&actp=search&viewlocale=en_US&searchid=1366618122228

Here is written that it uses layer 2,3 and 4 for load balancing hash
algorithm. And yes, the "forwarding-options hash" is not configurable on
EX-series.

HTH,
Ivan,


On Sun, Apr 21, 2013 at 6:11 PM, Mark Tinka <mark.tinka at seacom.mu> wrote:

> On Wednesday, March 06, 2013 04:15:45 PM Filippo Cugini
> wrote:
>
> > However, when we send traffic on the aggregated link,
> > just one ge works, and we experience packet loss when we
> > exceed the throughput of 1000mbps. Indeed, the
> > statistics of all interfaces show that only the
> > ge-0/0/12 is utilized to forward the data traffic, while
> > the other two interfaces send and receive only signaling
> > packets.
>
> We've seen this when flows are non-IP, i.e., in our case,
> the flows were MPLS-based.
>
> TAC came back to say the system won't load share if the
> flows aren't direct IP (unlike Cisco switches, it can't look
> beyond the MPLS frames to reveal the IP packets and hash on
> that).
>
> Not sure if this was your traffic type.
>
> We saw the issue on the EX4200's.
>
> Mark.
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>



-- 
Best Regards!

Ivan Ivanov