Symptom

show port-channel loadbalance forwarding path shows incorrect interface for multicast traffic. It does not match with the egress port which is actually selected for forwarding. Actual loadbalancing works fine. Please keep in mind no matter what loadbalancing algorithm you choose for multicast traffic load balancing algorithm will always fall back to src-dst ip ( for multicast traffic without l4 port info) and src dst ip/l4 ports for packets with l4 info. http://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/5_x/nx-os/interfaces/configuration/guide/if_cli/if_portchannel.html

Conditions

F3,F2E,M3 cards are impacted. Not seen with M2 line card

Workaround

contact TAC, using ELAM we can determine the RBH (result bundle hash) and figure out the egress port taken by the traffic.

Further Problem Description