Configuring Resilient Trunk Hashing

Starting from Netvisor ONE release 6.1.0, the resilient hash mode can be configured on trunks to help prevent unnecessary traffic disruption when the number of trunk member ports changes.

Note: Resilient hashing is supported on all platforms except:

• Dell Z9100-ON, S5048F, Z9264-ON
• Freedom F9532L-C/Edgecore AS7712-32X
• Freedom F9532-C/Edgecore AS7716-32X
• Freedom F9572L-V/Edgecore AS7312-54XS
• Freedom F9572-V/Edgecore AS7316-54XS
• Freedom F9532C-XL-R/Edgecore AS7716-32X
• Freedom F9664-C/Edgecore AS7816-64X.

Due to a hardware restriction, this feature cannot be changed on the fly and needs to be configured during trunk creation like so:

CLI (network-admin@switch) > trunk-create name trunk2 hash-mode resilient ports 5,6,7

CLI (network-admin@switch) > trunk-show format name,trunk-id,ports,hash-mode,status

name                 trunk-id ports hash-mode status

-------------------- -------- ----- --------- ----------------------------------------

trunk1               272      65-68 l3        up,PN-switch,PN-cluster,multicast-router

trunk2               273      5,6,7 resilient up,PN-switch

vxlan-loopback-trunk 397      13-16 enhanced  up,stp-edge-port

If you then try to dynamically modify resilient mode (for example to revert back to the default enhanced mode), you get an error message:

CLI (network-admin@switch) > trunk-modify trunk-id 273 hash-mode enhanced

trunk-modify: Trunk is configured with resilient hash. Delete and create trunk to change hash mode

So you need to delete the trunk first and then recreate it if modification of resilient mode is required.