[j-nsp] QFX5100 issues with IPv6 hashing

[Anton Yurchenko]

Hi,

Under that inet6 stanza you can only turn off certain fields to be used 
for hashing. I tried playing with them with no visible effect.

Asking on this list cause I almost feel this kind of issue would not go 
unnoticed for so long and that maybe my test setup is wrong.

Thanks for your reply!

On 4/18/15 02:58, Karsten Thomann wrote:
>
> Hi,
>
> not tested, but have you tried to configure under enhanced-hash-key 
> the inet6 hashing like documented here?
>
> http://www.juniper.net/documentation/en_US/junos13.2/topics/reference/configuration-statement/enhanced-hash-key-edit-forwarding-options-ex-series.html
>
> Kind regards
>
> Karsten
>
> Am Freitag, 17. April 2015, 17:26:10 schrieb Anton Yurchenko:
>
> > Hi All,
>
> >
>
> > I am seeing issues with QFX5100, hashing of IPv6 traffic over ECMP paths
>
> > is very bad.
>
> > In my case I have an ECMP over 3x40Gig links, and sending 180x10Mbit
>
> > UDPv6 flows over them. First 40G gets ~300mbit, second ~600 and 
> third ~900.
>
> > IPv4 hashing is fine ~5% variance in traffic levels.
>
> >
>
> > I have enabled hashing on L3/L4 and layer2-payload but no avail.
>
> >
>
> > It seems that protocol/ports are not taken into account at all. If I
>
> > start traffic from just one IP with 30 flows, they will all end up on a
>
> > single link.
>
> >
>
> > Seeing this on 13.2X51-D35.3 and 14.1X53-D25.2 releases.
>
> >
>
> > Here is my hashing config:
>
> >
>
> > load-balance {
>
> > indexed-load-balance;
>
> > }
>
> > hash-key {
>
> > family inet {
>
> > layer-3;
>
> > layer-4;
>
> > }
>
> > }
>
> > enhanced-hash-key {
>
> > hash-mode {
>
> > layer2-payload;
>
> > }
>
> > }
>
> >
>
> > Wondering if anybody have seen something similar or have seen it working
>
> > properly.
>
> >
>
> > Thanks!
>
> > _______________________________________________
>
> > juniper-nsp mailing list juniper-nsp at puck.nether.net
>
> > https://puck.nether.net/mailman/listinfo/juniper-nsp
>