Users Guide

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.
Table 42. Supported platforms for resilient hashing feature
Platform Resilient hashing on ECMP Resilient hashing on Port Channels
S6000-ON, S6010-ON, S4048T-ON,
S4100-ON Series, S5200F-ON Series
Y Y
Z9100-ON Series, Z9200-ON Series Y N
MX Series Y N
S3000-ON, S4200-ON Series N N
Examples
Normal traffic flow without resilient hashing
Traffic flow with resilient hashing enabled
When you enable resilient hashing for ECMP groups, the flow-map table is created with 64 paths (the OS10 default maximum number of
ECMP paths) and traffic is equally distributed. In the following example, traffic 1 maps to next hop 'A'; traffic 2 maps to next hop 'C'; and
traffic 3 maps to next hop 'B.'
Layer 3
577