[j-nsp] egress balancing on J2350

[Chuck Anderson]

"load-balance per-packet" really means "distribute load per-flow based
on a hash of the traffic".  You should not expect exact balancing, and
you will never get it.

You can control which fields on the packet (MAC addresses, IP
addresses, ports) are used to hash the flows by changing the hash-key
settings:

edit forwarding-options hash-key family inet
set layer-3
set layer-4

I'm not sure whether J2350 supports these hash-keys or different ones.

On Sat, Nov 23, 2013 at 11:27:01PM -0800, Yucong Sun wrote:
> Hi,
> 
> I'm been trying to get egress load balancing on J2350 10.4R9 and it just
> does't work as expected, any one can shed some light on this?
> 
> Here is what  monitor interface traffic looks like
> 
> Interface    Link     Input bytes        (bps)      Output bytes
>  (bps) Description
>  ge-0/0/1      Up 706087502511390   (29248072)    27664195116364
> (78022952) link-3
>  ge-0/0/2      Up  30707284714253   (39000048)    27353978545943
> (38232088) link-2
>  ge-0/0/3      Up   8076879239425    (3346480)    27858475703889
> (35689368) link-1
> 
> Egress is 78/38/35 mbps , not balanced.
> 
> I have
> 
> route {
> forwarding-table {
>     export LOAD-BALANCE;
> }
> }
> 
> policy-options {
> policy-statement LOAD-BALANCE {
>     then {
>         load-balance per-packet;
>     }
> }
> }
> 
> I also confirmed route is installed correctly
> 
> Routing table: default.inet
> Internet:
> Destination        Type RtRef Next hop           Type Index NhRef Netif
> default            user     3                    ulst 262143     5
>                               0:c:db:fe:ed:0     ucst   909     3
> ge-0/0/1.992
>                               0:c:db:fe:ed:0     ucst   608     4
> ge-0/0/3.999
>                               0:c:db:fe:ed:0     ucst   892     3
> ge-0/0/2.991
> 
> 
> WHY my regress is still not balanced ?! :-(
> 
> Thanks.