API Guide

IPV4 Load Balancing : Enabled
IPV6 Load Balancing : Enabled
MAC Load Balancing : Enabled
TCP-UDP Load Balancing : Enabled
Ingress Port Load Balancing : Disabled
IPV4 FIELDS : source-ip destination-ip protocol vlan-id l4-destination-port l4-
source-port
IPV6 FIELDS : source-ip destination-ip protocol vlan-id l4-destination-port l4-
source-port
MAC FIELDS : source-mac destination-mac ethertype vlan-id
TCP-UDP FIELDS: l4-destination-port l4-source-port
● The second part generates from the static physical configuration such as the ingress and egress port numbers.
To generate load balancing based on any parameters, change the hash field using the load-balance command. The example
shows how to enable the ingress port to generate load balancing based on the ingress parameter.
OS10(config)# load-balancing ingress-port enable
OS10(config)# do show load-balance
Load-Balancing Configuration For LAG and ECMP:
----------------------------------------------
IPV4 Load Balancing : Enabled
IPV6 Load Balancing : Enabled
MAC Load Balancing : Enabled
TCP-UDP Load Balancing : Enabled
Ingress Port Load Balancing : Enabled
IPV4 FIELDS : source-ip destination-ip protocol vlan-id l4-destination-port l4-source-
port
IPV6 FIELDS : source-ip destination-ip protocol vlan-id l4-destination-port l4-source-
port
MAC FIELDS : source-mac destination-mac ethertype vlan-id
TCP-UDP FIELDS: l4-destination-port l4-source-port
Resilient hashing
To increase bandwidth and for load balancing, traffic distributes across the next hops of an ECMP group or member ports of a
port channel. OS10 uses a hash algorithm to determine a hash key. The egress port in a port channel or the next hop in an
ECMP group is selected based on the hash key modulo the number of ports in a port channel or next hops in an ECMP group,
respectively. When a member link goes down or a new member link is added, the traffic flows remap based on the new hash
result.
In this section, the term, "member link" refers to either a member physical port, in the case of port channels or next hop in the
case of ECMP groups.
With resilient hashing, when a member link goes down, the existing flows are not affected; they do not remap. Resilient hashing
reassigns the traffic from the failed link to another member link without remapping the other existing flows. However, minimal
re-mapping occurs when a new member link is added.
Resilient hashing is supported both for Port Channels and Equal Cost MultiPath Groups (ECMP). Resilient hashing is a global
configuration. You can configure resilient hashing for both port channels and ECMP independently.
NOTE:
● Resilient hashing is not supported on the S4200-ON and Z9332F-ON platforms.
● The flow-map table always has an even number of entries.
To enable resilient hashing for Port Channels or ECMP groups, use the following commands in CONFIGURATION mode:
OS10(config)# enhanced-hashing resilient-hashing ecmp
OS10(config)# enhanced-hashing resilient-hashing lag
Supported platforms
The following table lists the platforms that support resilient hashing.
652
Layer 3