Configure HASH KEY of Load Balance Profile
After creating one load balance profile successfully and entering the profile configuration mode, you can configure the HASH KEY value of the load balance profile.
-
The default profile of the system “default” will be configured with a default HASHKEY, and users can also modify its configuration according to actual needs.
- The default configuration of the “default” profile is: L2:src-mac, dst-mac; Ip:src-ip, dst-ip; mpls: src-ip, dst-ip.
-
After creating one user customized profile, the new profile is not configured with any HASH KEY value by default, and the user needs to configure HASH KEY correctly so that the profile can be bound by the service.
Configuration Conditions
None
Configure HASH KEY of Load Balance Profile
Table 1-5 Configure HASH KEY of the load balance profile
|
Step
|
Command
|
Description
|
| Enter the global configuration mode. |
configure terminal |
|
| Enter the load balance profile configuration mode |
load-balance profile { profile-name | default }
|
Mandatory
The same as the command of creating one load balance profile
|
|
Configure HASH KEY used by L2 known unicast packet load
|
l2 { [ dst-mac ] [ src-mac ] [ src-interface ] [ vlan ] }
|
Mandatory
You can configure one or more HASH KEY.
|
|
Configure HASH KEY used by L3 known unicast packet load
|
ip { [ dst-ip ] [ l4-src-port ] [ l4-dst-port ] [ protocol ] [ src-interface ] [ src-ip ] [ flow-label ]}
|
Mandatory
You can configure one or more HASH KEY.
|
|
Configure the HASH KEY used by the mpls packet load
|
Mpls {[src-ip] [dst-ip] [top- lable] [2nd -lable] [3rd- lable]}
|
Mandatory
You can configure one or multiple HASHKEY combinations.
|
|
Activate the current HASH KEY configuration
|
active configuration pending
|
Mandatory
|
|
Cancel the current HASH KEY configuration
|
abort configuration pending
|
Mandatory
|
-
The HASH KEY value configured by the l2 or ip command is in the pending state, and will not take effect immediately. It can take effect only after you execute the command active configuration pending.
- The HASH KEY value configured by the l2 or ip command is in the pending state, and will not take effect immediately. The user can cancel the current configuration via the command abort configuration pending.
- When configuring new HASH KEY, it will not cover the original HASH KEY. After activating via the command active, the result is the communication of the original HASH KEY and the new HASH KEY.
- When the HASH KEY in the pending state is cancelled via the abort command, it will modify the original HASH KEY.
- When failed to activate, it will clear the HASH KEY in the pending state. Usually, the activating failure is because the configured HASH KEY does not meet the requirement.
- You can configure any HASH KEY for the load balance profile customized by the user. When aggregation binds the profile, L2 and L3 cannot be empty at the same time. When mpls binds the service, HASH KEY of mpls cannot be empty.
- The requirement of the “default” profile: HASH KEYs of L2 and L3 cannot be empty at the same time.
Switch
.png){kind=icon}
.png){kind=logo}
