Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

hash-key (Forwarding Options)

Syntax

Hierarchy Level

Description

Select which packet header data to use for per-flow load balancing.

The options are explained separately.

Note:

To modify the default hashing mechanism on Modular Port Concentrators (MPCs) and Type 5 FPCs, you need to configure the statements at the [edit forwarding-options enhanced-hash-key] hierarchy level. Statements at the [edit forwarding-options hash-key] hierarchy level do not support MPCs and Type 5 FPCs.
Note:

The following statements are not supported on T Series routers:

  • The symmetric-hash and the session-id statements at the [edit forwarding-options hash-key family inet] hierarchy level and all statements at the [edit forwarding-options hash-key family multiservice] hierarchy level.

  • The label-1 and label-2 statements, and the IP configuration at the [edit forwarding-options hash-key family multiservice] hierarchy level.
Note:

The following statements are not supported on QFX Series switches:

  • The symmetric-hash and the session-id statements at the [edit forwarding-options hash-key family inet] hierarchy level.
Note:

QFX 5000 Series switches with an EVPN Type 5 overlay must configure overlay-ecmp at the [edit forwarding-options vxlan-routing hierarchy.
Note:

QFX 10000 Series switches in an EVPN-VXLAN environment should configure the layer2 option with appropriate sub-option at the [edit forwarding-options enhanced-hash-key] hierarchy. This applies to the overlay fabric.

Addtionally, you should configure the family option with appropriate sub-option at the [edit forwarding-options enhanced-hash-key hierarchy. This applies to both EVPN-VXLAN underlay and overlay fabrics.
Note:

On PTX platforms, family inet/inet6 layer-3 traffic-class (dscp-v4/dscp-v6) is disabled by default.

PTX platforms running Junos OS Evolved require the enhanced-hash-key family setting for EVPN-VXLAN underlay and overlay fabrics.
Note:

EVPN-VXLAN configuration is required for underlay ECMP to work in ACX platforms on Junos EVO.

Note:

On ACX 7000 Series of routers, the following statements are not supported:

  • label-1, label-2, and payload statements at the [edit forwarding-options hash-key family multiservice] hierarchy level

  • bottom-label-1, bottom-label-2, bottom-label-3, label-1, label-2, label-3, no-labels, and no-label-1-exp at the [edit forwarding-options hash-key family mpls] hierarchy level

  • disable and port-data statements at the [edit forwarding-options hash-key family mpls payload ip] hierarchy level

  • destination-address, incoming-interface-index, next-header, source-address, traffic-class at the [edit forwarding-options hash-key family inet6 layer-3] hierarchy level

  • destination-port and source-port at the [edit forwarding-options hash-key family inet6 layer-4] hierarchy level

Note:

On ACX Series routers, configure the family (inet|inet6) option with appropriate sub-option at the [edit forwarding-options enhanced-hash-key hierarchy. This applies to both EVPN-VXLAN underlay and overlay fabrics.

Options

  • inet-IPv4 protocol family.

  • mpls-MPLS protocol family.

  • layer-3-Incorporate Layer 3 data into the hash key.

  • layer-4-Incorporate Layer 4 data into the hash key.

  • session-id-Incorporate session ID data into the hash key (SRX3000 and SRX5000 lines only). The session ID data has higher precedence than the Layer 3 or 4 information.

  • label-1-Incorporate the first MPLS label into the hash key.

  • label-2-Incorporate the second MPLS label into the hash key.

  • label-3-Incorporate the third MPLS label into the hash key.

  • no-labels-Include no MPLS labels into the hash key.

  • payload-Incorporate payload data into the hash key.

  • ip-Include the IP address of the IPv4 or IPv6 payload into the hash key.

  • layer-3–only-Include only Layer 3 IP information.

  • port-data-Include the source and destination port field information.

  • source-msb-Include the most significant byte of the source port.

  • source-lsb-Include the least significant byte of the source port.

  • destination-msb-Include the most significant byte of the destination port.

  • destination-lsb-Include the least significant byte of the destination port.

  • source-mac-Include source MAC address in hash key.

  • destination-mac-Include destination MAC address in hash key.

Required Privilege Level

interface—To view this statement in the configuration.

interface-control—To add this statement to the configuration.

Release Information

Statement introduced before Junos OS Release 7.4.

family multiservice and no-label-1-exp options introduced in Junos OS Release 8.0.

label-3 and no-labels options introduced in Junos OS Release 8.1.

ether-pseudowire statement introduced in Junos OS Release 9.1 (M320 and T Series routers only); support extended to M120 and MX Series routers in Junos OS Release 9.4.

ip, label-1, label-2, layer-3-only, and payload options for the family multiservice statement introduced in Junos OS Release 9.4 (M120 and M320 routers only). For MX Series routers, only the ip and payload statements apply.

layer-3, source-ip-only, destination-ip-only, and layer-4 statements introduced for the family multiservice statement in Junos OS Release 9.5. (MX Series routers only).

all-labels and payload ip disable statements introduced for the family mpls statement in Junos OS Release 12.1X48R2 PTX Series Packet Transport Routers only.

bottom-label statement introduced for the family mpls statement in Junos OS Release 14.1 for MX Series routers with DPCs (excluding M7i, M10i, and M120.)

zero-control-word option for the ether-pseudowire statement introduced in Junos OS Release 16.1 for the M Series, MX Series, and PTX Series.

Related Documentation