Lag load sharing, Hash based load sharing – Brocade Multi-Service IronWare Switching Configuration Guide (Supporting R05.6.00) User Manual

Page 143

Advertising
background image

Multi-Service IronWare Switching Configuration Guide

113

53-1003036-02

LAG load sharing

5

FIGURE 5

Examples of multi-slot, multi-port LAG

LAG load sharing

Brocade devices can be configured for load sharing over a LAG by either of the following methods:

Hash Based Load Sharing

Per Packet Load Sharing

Each of these methods, that are described in the following sections, are configured per LAG using
the trunk-type command as described in

“Configuring load sharing type”

.

Hash based load sharing

The Brocade device shares the traffic load evenly across the ports in LAG group, while ensuring
that packets in the flow are not reordered. Individual flows are assigned a LAG index to identify
them. Beginning with version 03.8.00, an improved hash based load sharing algorithm was
introduced with the following enhancements:

Better Distribution

Support for 32-port LAGs

An increased number of fields in the packet header that can be used for load balancing

Enhanced load sharing in configurations of ECMP with LAGs.

Traffic from each flow is then distributed across the ports in the LAG group using a hash index as
follows:

NOTE

The following description of the hash index contains all of the fields available beginning with version
3.8.00. If you are using a version prior to 3.8.00 and want to know which fields are included in the
hash algorithm, consult the configuration guide for the version you are using.

For Layer 2 switching, the hash index is based on the following:

IPv4 or IPv6 traffic: source MAC address and destination MAC address, IPv4v6 source and
destination address, VLAN-ID, IPv4 protocol number or IPv6 next header and TCP or UDP
source port and TCP or UDP destination port.

Advertising