enhanced-hash-key profile1/profile2
Syntax
enhanced-hash-key profile1/profile2 profile-fields
Hierarchy Level
[edit forwarding-options]
Description
Enable or disable profile fields for an enhanced-hash-key load balancing profile (profile1 or profile2).
On EVO platforms, users can disable or enable enhanced-hash-key fields for load balancing by configuring "set forwarding-options enhanced-hash-key". However, this enhanced-hash-key config change is chassis-wide, and will be applied to any route. Committing a change on any particular enhanced-hash-key field will affect load balance of all applicable traffic.
Therefore, users can configure two load balance profiles (profile1 and profile2) with different sets of enhanced-hash-key configurations. Users will be able to apply a load balance profile to a specific route, not affecting other routes on the chassis, adding flexibility for load balance management.
The following are the profile fields that can be used for enhanced-hash-key profile1 and profile2:
| Settings | enhanced-hash-key profile field | Description |
|---|---|---|
|
Interface |
no-in-interface |
Inner inteface fields |
|
no-interface |
Interface fields |
|
|
Flexbytes |
no-in-flexbytes |
Inner L3/L4 flexbytes fields |
|
no-flexbytes |
L3/L4 flexbytes fields |
|
|
Tunnel |
no-tunnel |
Tunnel header fields |
|
no-in-tunnel |
Inner tunnel header fields |
|
|
Traffic Class |
no-in-layer3-pri |
Inner L3 dscp/dp fields |
|
no-layer3-pri |
L3 dscp/dp fields |
|
|
Layer 2 |
no-in-layer2 |
Inner layer2 fields |
|
no-layer2 |
DMAC, SMAC and VLAN fields |
|
|
Layer 3 |
no-in-layer3-proto |
Inner L3 protocol fields |
|
no-layer3-proto |
L3 protocol fields |
|
|
no-layer3-source-address |
L3 source address fields |
|
|
no-layer3-destination-address |
L3 destination address fields |
|
|
no-in-layer3 |
Inner layer3 fields |
|
|
Layer 4 |
no-layer4-source-port |
L4 source port fields |
|
no-layer4-destination-port |
L4 destination port fields |
|
|
no-in-layer4 |
Inner layer4 fields |
Profile fields are enabled by default and are only disabled if explicitly set.
As an example, if load-balancing profile profile1 has been
set for a route, interface fields are enabled by default in profile1, unless
explicitly disabled with the set forwarding-options
enhnaced-hash-key profile1 no-interface configuration
command.
Default
Default profile - The default profile or global profile is applied internally when neither profile1 or profile2 is applied to a route. You cannot use "default" as a profile name.
The final hash result is determined from an AND operation between hash fields of default profile and hash fields of profile1/profile2.
| Default profile hash field enabled/disabled (1/0) | profile1/profile2 hash field enabled/disabled (1/0) | Final hash result |
|---|---|---|
|
1 |
1 |
1 |
|
1 |
0 |
0 |
|
0 |
1 |
0 |
|
0 |
0 |
0 |
As an example, no-destination-port and
no-source-port enhanced-hash-key fields (disabled by
default) are part of the default profile. Their equivalent profile fields in
profile1/profile2 are no-layer4-source-port and
no-layer4-destination-port (enabled by default). To
enable no-destination-port and
no-source-port enhanced-hash-key fields of the
default profile, the following global CLI can be used:
set forwarding-options enhanced-hash-key family inet no-destination-port; set forwarding-options enhanced-hash-key family inet no-source-port;
The following table shows the final hash computation when
no-destination-port and
no-source-port is enabled globally. Note that you can
use show forwarding-options enhanced-hash-key
profile1/profile2 to view the final
hash computation results.
| Default profile no-destination-port and no-source-port enhanced-hash-key fields enabled/disabled (1/0) | profile1/profile2 no-layer4-source-port and no-layer4-destination-port profile fields enabled/disabled (1/0) | Final hash result |
|---|---|---|
|
1 |
1 |
1 |
To disable no-destination-port and
no-source-port hashing only for a specific route
while enabling no-destination-port and
no-source-port hashing on all other routes, user can
configure a profile for the route as follows.
set forwarding-options enhanced-hash-key profile1 no-layer4-source-port
set forwarding-options enhanced-hash-key profile1 no-layer4-destination-port
set policy-options policy-statement lb term 1 from route-filter 10.0.0.0/16 orlonger
set policy-options policy-statement lb term 1 then load-balance profile1
set policy-options policy-statement lb term 1 then accept
set policy-options policy-statement lb then accept
set routing-options forwarding-table export lb
The final hash result for no-destination-port and
no-source-port hashing for route 10.0.0.0/16 would be
"0" or disabled as indicated in the following table.
no-destination-port and
no-source-port hashing is still enabled for all other
routes on the chassis.
| Default profile no-destination-port and no-source-port enhanced-hash-key fields enabled/disabled (1/0) | profile1 no-layer4-source-port and no-layer4-destination-port profile fields enabled/disabled (1/0) | Final hash result |
|---|---|---|
|
1 |
0 |
0 |
Options
-
profile1
-
profile2
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 23.2