Enabling Ecmp Multicast Load Splitting Based On Source Group And Next-Hop Address - Cisco Nexus 7000 Series Configuration Manual

Enabling ECMP Multicast Load Splitting Based on Source Group and Next-Hop Address

Step 2
Step 3
Enabling ECMP Multicast Load Splitting Based on Source Group and Next-Hop
Address
Perform this task to enable ECMP multicast load splitting of multicast traffic based on source, group, and
next-hop address (using the next-hop-based S-G-hash algorithm) to take advantage of multiple paths through
the network. The next-hop-based S-G-hash algorithm is predictable because no randomization is used in
calculating the hash value. Unlike the S-hash and basic S-G-hash algorithms, the hash mechanism used by
the next-hop-based S-G-hash algorithm is not subject to polarization.
The next-hop-based S-G-hash algorithm provides more flexible support for ECMP multicast load splitting
than S-hash algorithm and eliminates the polarization problem. Using the next-hop-based S-G-hash algorithm
for ECMP multicast load splitting enables multicast traffic from devices that send many streams to groups or
that broadcast many channels, such as IPTV servers or MPEG video servers, to be more effectively load split
across equal-cost paths.
Procedure
Step 1
Step 2
Cisco Nexus 7000 Series NX-OS Multicast Routing Configuration Guide
104
Command or Action
ip multicast multipath none
Example:
switch(config)# ip multicast multipath
none
clear ip mroute * vrf vrf-name
Example:
switch(config)# clear ip mroute *
Command or Action
configure terminal
Example:
switch# configure terminal
ip multicast multipath s-g-hash
next-hop-based
Example:
switch(config)# ip multicast multipath
s-g-hash next-hop-based
Configuring PIM and PIM6
Purpose
Disables multicast multipath.
Clears multipath routes and activates multicast
multipath suppression.
Purpose
Enters global configuration mode.
Enables ECMP multicast load splitting based
on source, group, and next-hop-address using
the next-hop-based S-G-hash algorithm.
• Because this command changes the way
an RPF neighbor is selected, it must be
configured consistently on all routers in a
redundant topology to avoid looping.