Mammoth-Platform-PC-LB-Direction Of Traffic Flowknown Unicast TrafficUnknown Unicast and Multicast TrafficHashing AlgorithmDefault configuration Hashing algorithmDefault Configuration/Current BehaviourTowards Uplink port-channels or Server port-channels.Based on the Load Balance configuration,It could be srcip-dstip,srcmac-dstmac etc Based on Src-IP DstIP,For L2 Packets Based on the following packet header fields:L2SA,L2DA For L3 Packets : L2SA,L2DA,SRCIP and DSTIP,Srcport and DstportWith Hardware multicast hw-hash disabled, the algorith based on the Incoming src Interface, and VOQ number. With "Hardware multicast hw-hash" enabled, its based on the Load balancing configuration. By Default "hardware multicast hw-hash" disabled, hashing is based on the incoming interface and VOQ number. VOQ number is based on vlan id.Network ----->Host ,HIF port-channelsBased on the Load Balance configuration, it could be any of the following srcipdstip, srcmac-dstmac etc, please go through the documentation for more.SRCIP-DSTIP.No Load Balancing across the member portsNo traffic Load Balance across the member ports.all the traffic goes over the same member port.Host ------>Network, NIF port channelsBased on the load balance configuration SRCIP-DSTIPBased on server eth interfaces.Traffic generated from different eth interfaces on the server goes over different NIF ports.

Mammoth-Platform-PC-LB-R

Ingress InterfaceVlanIdsrcMac -AddressdstMacAddresssrcIP DstIPOutGoingInterfaceEth1/30111000:25:b5:20:00:2401:00:00:01:01:c910.1.0.120.0.0.21/20Eg1110-1111Incr : 7 Incr :7 1/20EgEth1/29111000:00:04:00:05:0001:00:00:01:01:c91.1.1.12.1.1.21/17Eg1110-1111Incr-7Incr-71/17 EgEnable Hardware multicast-hw-has111000:00:04:00:05:0001:00:00:01:01:c91.1.1.12.1.1.2Egr:1/17 01:00:00:01:01:cAEgr:1/20 01:00:00:01:01:CB :CBEgr:1/20 01:00:00:01:01:CC Egr:1/18 01:00:00:01:01:CD Egr:1/18 01:00:00:01:01:CE Egr:1/19 01:00:00:01:01:CF Egr:1/19 01:00:00:01:01:D0 Egr:1/18 01:00:00:01:01:D1 Egr:1/18 01:00:00:01:01:D2 Egr:1/19 01:00:00:01:01:D3 Egr:1/19 01:00:00:01:01:D4 Egr:1/17With Hardware Multicats hw-hash enabled, varying the header fields results to the different destinations

MiniUCS-Pltfrm-PC-LBThe Traffic Distribution behaviour for the Unicast Traffic and Multicast Traffic on the Miniucs Platform.

1.Unicast Traffic.For Unicast Traffic, PC Load Balancing works on the Load Balancing algorithm configured on the port-channel.please refer the miniucs documents for understanding the PC LB Algorithm.From UCSM by default its configured with source-dest-ip, In the current releases Its not configurable from the UCSM.

2.Multicast Traffic For Multicast Traffic, the LB Alogorithm configuration won't apply(means It won't form the key to calculate the hash value based on the LB configuration,It's based on the type of packet egressing on the port-channel.)The current LB prediction show command from the nxos cli, won't work as per the expectation for the multicast traffic(means the prediction results are wrong),the "work around for the show command" in the last coloumn below explains the work around to get the correct prediction result for the show command.Egress Traffic on PCHeader Fields(For deriving the LB hash key)Work Around for the show command to get the proper Info1NON IP MCAST TRAFFIC (NO IP HEADER)L2SA,L2DA and EtherTypeEtherType is not provided as a input parameter in the show command, there is a no work around exists.2IP MCAST TRAFFIC(NO L4 HEADERSRCIP,DSTIPChange the load balance algorithm to srcip-dstip, then execute the show command to get the expected result.(default configuration is srcip-dstip from UCSM.)3IPMCAST TRAFFIC with L4 Header(TCP/UDP)SRCIP,DSTIP,SRCPORT,DSTPORTChange the load balance algorithm to source-dest-portUse the following command to change the load balance algorithm,mini03-A(config)(nx-os)# port-channel load-balance ethernetdestination-ip source-dest-ip source-dest-port source-macdestination-mac source-dest-ip-only source-dest-port-only source-portdestination-port source-dest-mac source-ip

For Non IP MCAST TRAFFICmini03-A(config)(nx-os)# port-channel load-balance Ethernet source-dest-ipmini03-A(config)(nx-os)# show port-channel load-balance forwarding-path interface port-channel 1 vlan 300 src-mac 00:00:04:00:00:00 dst-mac 01:00:04:00:01:02 src-ip 1.1.1.1 dst-ip 224.1.1.10

For IPMCAST Traffic with L4 headermini03-A(config)(nx-os)# port-channel load-balance Ethernet source-dest-portshow port-channel load-balance forwarding-path interface port-channel 1 vlan 300 src-mac 00:00:04:00:00:00 dst-mac 01:00:04:00:01:02 src-ip 1.1.1.1 dst-ip 224.1.1.25 l4-src-port 600 l4-dst-port 620

3gFI-Platform-PC-LB

packet-typeHash CriteriaIP PacketsL4SRCPORT+L4DDSTPORT+SIP+DIP+VLANNon-Ip PacketsSMAC+DMAC+VLAN+EthertypeNote: Ip refers to both ipv4 & ipv4 packetsSame hash criteria applied to unicast & multicast traffic"show port-channel load-balance forwarding"Following aspects need to be considered while using show commad to get hash results1. Src-interafce need to be provided; however any random port can be picked. It does not really matter where the traffic is coming in.2. Ethertype needs to be provided to get the correct results. If ethertype is IPv4 or IPv6; hash results will be based on L4SRCPORT+L4DDSTPORT+SIP+DIP+VLANOtherwise hashing will be based on SMAC+DMAC+VLAN+Ethertype3. The VLAN information needs to be provided even for untagged packets. The VLAN information corresponds to the packet classification at ingress. Hence for L2 ingress ports this should correspond to the access/native VLAN configuration of that port.