hash-keys (Interfaces)
Syntax
hash-keys {
egress-key (source-ip | destination-ip);
ingress-key (source-ip | destination-ip);
ipv6-source-prefix-length ipv6-source-prefix-length;
}
Hierarchy Level
[edit interfaces unit unit-name load-balancing-options]
Description
Configure the hash keys used for load balancing in aggregated multiservices (AMS) for next-hop style services. The hash keys supported in the ingress and egress direction are the source IP address and destination IP address.
Hash keys are used to define the load-balancing behavior among
the various members in the AMS. For example, if hash-keys is configured as source-ip, then the hashing is performed
based on the source IP address of the packet, so that all packets
with the same source IP address land on the same member. When you
use ingress-key and egress-key, you must configure
hash keys to take the traffic direction into consideration. For example,
if you configure hash-keys as source-ip in the
ingress direction, then you must configure hash-keys as destination-ip in the egress direction. This is required to
ensure that the packets of the same flow reach the same member of
the AMS group.
If you are configuring an AMS interface used in a service set for DS-Lite,
The remaining statements are explained separately. See CLI Explorer.
Options
| egress-key destination-ip | Use the destination IP address of the flow to compute the hash used in load balancing. Configure the hash keys to be used in the egress flow direction. |
| egress-key source-ip | Use the source IP address of the flow to compute the hash used in load balancing. Configure the hash keys to be used in the egress flow direction. |
| ingress-key destination-ip | Use the destination IP address of the flow to compute the hash used in load balancing. Configure the hash keys to be used in the ingress flow direction. |
| ingress-key source-ip | Use the source IP address of the flow to compute the hash used in load balancing. Configure the hash keys to be used in the ingress flow direction. |
Required Privilege Level
interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Release 11.4.
ipv6-source-prefix-length option introduced in Junos OS Release 18.2R1.
Support
added in Junos OS Release 19.3R2 for Next Gen Services on MX Series
routers MX240, MX480 and MX960 with the MX-SPC3 services card. The ipv6-source-prefix-length option is not supported for Next
Gen Services.