Symptom

show port-channel load-balance forwarding-path interface Pox src-interface ethernet 1/Y src-mac dst-mac src-ip dst-ip predicts an Egress port that MAY be different from actually selected by the IP multicast traffic given a set of parameters that match the actual load-balancing configuration.

Conditions

traffic with multicast Destination IP load-balancing configuration: 'source-dest-ip' or 'source-dest-port'

Workaround

Further Problem Description

For 3548/3548X/XL platform * the the hash calculation for multicast flows is different from unicast flows. * Multicast IP traffic load-balancing algorithm is the same whether 'source-dest-ip' or 'source-dest-port' is configured. For both load-balancing types, L4 port information will be used for hashing if a valid L4 header is present in the packet. If L4 header is present, CLI should be used with L2 Dest MAC, L3 source and destination IP, L4 source and destination ports. else (no L4 header) CLI should be used with L2 Dest MAC, L3 source and destination IP. * L2-only load-balancing should only be used for non-IP traffic (source-mac, dest-mac, source-dest-mac) Not supported for IP traffic