Purpose
If the outbound traffic across equal-cost next hops is not well balanced after you have load balancing configured, you can configure the hash key to provide additional information to further identify traffic flows and balance traffic more evenly. The hash key is configured at the
[edit forwarding-options]hierarchy level on ingress and transit routers, depending on your network configuration.Within the hash key, you can configure the IPv4 address family (INET) or the MPLS protocol family. Typically for the best results, you configure the INET on the ingress router and the MPLS protocol family on the transit router. If a router happens to be both an ingress and transit router, you can configure both the INET and the MPLS protocol family. However, the INET will only be used when the router is acting as an ingress router and the MPLS protocol family will only be used when the router is acting as a transit router. You can configure only the INET on the ingress router, and check that the results are what is intended. Similarly, you can configure only MPLS labels on the transit router, and check the results.
In addition, the MPLS protocol family is most useful in configurations with aggregated interfaces, although it can be used on transit routers with regular (non-aggregated) interfaces.
Steps To Take
To use the hash key to load-balance LSP traffic, follow these steps: