Professional Documents
Culture Documents
Hashing Algorithm
Default configuration
Hashing algorithm
Default
Configuration/Current
Behaviour
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.
SRCIP-DSTIP
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
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.
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
eiction
LB configuration,It's
based on
the around
type of for
packet
results are wrong),the
"work
the egressing on the port-channel.)
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
Hash Criteria
L4SRCPORT+L4DDSTPORT+SIP+DIP+VLAN
SMAC+DMAC+VLAN+Ethertype
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.