L3/L4 header-based hashing for NP7-offloaded GRE tunnels

You can use the following command to configure the algorithm that controls how NP7-offloaded GRE tunnel sessions are load balanced by LAGs. Depending on your traffic profile, you can adjust the algorithm to optimize performance and throughput. The command allows you to use L3 and L4 GRE headers when calculating load balancing hashing.

config system npu

set lag-hash-gre {disable | gre_inner_l3 | gre_inner_l4 | gre_inner_l3l4}

end

disable (the default) disable using GRE inner headers as hash input.

gre_inner_l3 use GRE inner L3 header information as hash input.

gre_inner_l4 use GRE inner L4 header information as hash input.

gre_inner_l3l4 use GRE inner L3 and L4 header information as hash input.

Once you have configured the lag-hash-gre option, you can configure a LAG to use the configuring hashing, by setting the algorithm option of the LAG configuration to NPU-GRE:

config system interface

edit example-lag

set type aggregate

set algorithm NPU-GRE

end

NPU-GRE use L4 and GRE inner header information for calculating load balance hashing for GRE tunnels passing through this LAG. The NPU-GRE option is only available if you have configured lag-hash-gre.