You are on page 1of 138

Direction Of Traffic Flow

known Unicast Traffic

Hashing Algorithm

Towards Uplink port-channels


or Server port-channels.

Based on the Load Balance


configuration,It could be srcipdstip,srcmac-dstmac etc

Network ----->Host ,HIF portchannels

Based on the Load Balance


configuration, it could be any
of the following srcipdstip,
srcmac-dstmac etc, please go
through the documentation
for more.

Host ------>Network, NIF port


channels

Based on the load balance


configuration

Unknown Unicast and Multicast Traffic

Default configuration

Hashing algorithm

Default
Configuration/Current
Behaviour

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 Dstport

With Hardware multicast hwhash disabled, the algorith


based on the Incoming src
Interface, and VOQ number.
With "Hardware multicast hwhash" 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.

SRCIP-DSTIP.

No Load Balancing across the


member ports

No traffic Load Balance


across the member
ports.all the traffic goes
over the same member
port.

SRCIP-DSTIP

Traffic generated from


different eth interfaces
on the server goes over
Based on server eth interfaces. different NIF ports.

Ingress Interface
Eth1/30

VlanId

srcMac -Address
1110 00:25:b5:20:00:24
1110-1111
Incr : 7

dstMacAddress
01:00:00:01:01:c9
Incr :7

Eth1/29

1110 00:00:04:00:05:00
1110-1111
Incr-7
Enable Hardware multicast-hw-has
1110 00:00:04:00:05:00

01:00:00:01:01:c9
Incr-7
01:00:00:01:01:c9
01:00:00:01:01:cA
01:00:00:01:01:CB
01:00:00:01:01:CC
01:00:00:01:01:CD
01:00:00:01:01:CE
01:00:00:01:01:CF
01:00:00:01:01:D0
01:00:00:01:01:D1
01:00:00:01:01:D2
01:00:00:01:01:D3
01:00:00:01:01:D4

With Hardware Multicats hw-hash enabled, varying the header fields results to the different destinatio

srcIP
10.1.0.1

DstIP
20.0.0.2

OutGoingInterface
1/20Eg
1/20Eg

1.1.1.1

2.1.1.2

1/17Eg
1/17 Eg

1.1.1.1

2.1.1.2

Egr:1/17
Egr:1/20
Egr:1/20
Egr:1/18
Egr:1/18
Egr:1/19
Egr:1/19
Egr:1/18
Egr:1/18
Egr:1/19
Egr:1/19
Egr:1/17

1:01:CB
1:01:CC
1:01:CD
1:01:CE
1:01:CF
1:01:D0
1:01:D1
1:01:D2
1:01:D3
1:01:D4

e different destinations

:CB

The Traffic Distribution behaviour for the Unicast Traffic and Multicast Traffic on t
1.Unicast Traffic.

For Unicast Traffic, PC Load Balancing works on the Load Balancing algorithm configured on the port-c
documents for understanding the PC LB Algorithm.From UCSM by default its configured with source-de
configurable from the UCSM.

2.Multicast Traffic

For Multicast
Traffic,
the LB
Alogorithm
configuration
won't
It per
won't
the key to
The
current LB
prediction
show
command
from the nxos
cli,apply(means
won't work as
theform
expectation
forcalcu
the
show command" in the last coloumn below explains the work around to get the correct prediction resu

Egress Traffic on PC

1 NON IP MCAST TRAFFIC (NO IP HEADER)

2 IP MCAST TRAFFIC(NO L4 HEADER


IPMCAST TRAFFIC with L4
3 Header(TCP/UDP)

Use the following command to change the load balance algorithm,


mini03-A(config)(nx-os)# port-channel load-balance ethernet
destination-ip
source-dest-ip
source-dest-port
source-mac
destination-mac
source-dest-ip-only
source-dest-port-only source-port
destination-port
source-dest-mac
source-ip

For Non IP MCAST TRAFFIC


mini03-A(config)(nx-os)# port-channel load-balance Ethernet source-dest-ip
mini03-A(config)(nx-os)# show port-channel load-balance forwarding-path interface port-channel 1 vla

For IPMCAST Traffic with L4 header


mini03-A(config)(nx-os)# port-channel load-balance Ethernet source-dest-port
show port-channel load-balance forwarding-path interface port-channel 1 vlan 300 src-mac 00:00:04:0

or the Unicast Traffic and Multicast Traffic on the Miniucs Platform.

on the Load Balancing algorithm configured on the port-channel.please refer the miniucs
orithm.From UCSM by default its configured with source-dest-ip, In the current releases Its not

guration
won't
It per
won't
the key to
the hash
value based
the LB configuration,It's
om
the nxos
cli,apply(means
won't work as
theform
expectation
forcalculate
the multicast
traffic(means
theon
prediction
results are wron
explains the work around to get the correct prediction result for the show command.

Header Fields(For deriving the


LB hash key)

Work Around for the show command


to get the proper Info

L2SA,L2DA and EtherType

EtherType is not provided as a input parameter


in the show command, there is a no work
around exists.

SRCIP,DSTIP
SRCIP,DSTIP,SRCPORT,DSTPORT

Change the load balance algorithm to srcipdstip, then execute the show command to get
the expected result.(default configuration is
srcip-dstip from UCSM.)
Change the load balance algorithm to sourcedest-port

oad balance algorithm,


balance ethernet
rce-dest-port
source-mac
source-dest-port-only source-port
ource-ip

balance Ethernet source-dest-ip


load-balance forwarding-path interface port-channel 1 vlan 300 src-mac 00:00:04:00:00:00 dst-mac 01:00:04:0

balance Ethernet source-dest-port


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

eiction
LB configuration,It's
based on
the around
type of for
packet
results are wrong),the
"work
the egressing on the port-channel.)

00 dst-mac 01:00:04:00:01:02 src-ip 1.1.1.1 dst-ip 224.1.1.10

1:02 src-ip 1.1.1.1 dst-ip 224.1.1.25 l4-src-port 600 l4-dst-port 620

packet-type
IP Packets
Non-Ip Packets
Note: Ip refers to both ipv4 & ipv4 packets
Same hash criteria applied to unicast & multicast traffic
"show port-channel load-balance forwarding"
Following aspects need to be considered while using show commad to

1. Src-interafce need to be provided; however any random port can be


2. Ethertype needs to be provided to get the correct results. If etherty
Otherwise hashing will be based on SMAC+DMAC+VLAN+Ethertype
3. The VLAN information needs to be provided even for untagged pack
Hence for L2 ingress ports this should correspond to the access/nativ

Hash Criteria
L4SRCPORT+L4DDSTPORT+SIP+DIP+VLAN
SMAC+DMAC+VLAN+Ethertype

both ipv4 & ipv4 packets


ia applied to unicast & multicast traffic

nnel load-balance forwarding"


s need to be considered while using show commad to get hash results

eed to be provided; however any random port can be picked. It does not really matter where the traffic is co
ds to be provided to get the correct results. If ethertype is IPv4 or IPv6; hash results will be based on L4SRC
g will be based on SMAC+DMAC+VLAN+Ethertype
mation needs to be provided even for untagged packets. The VLAN information corresponds to the packet cl
gress ports this should correspond to the access/native VLAN configuration of that port.

ly matter where the traffic is coming in.


h results will be based on L4SRCPORT+L4DDSTPORT+SIP+DIP+VLAN

on corresponds to the packet classification at ingress.


f that port.

You might also like