Options for hash based load sharing – Brocade Multi-Service IronWare Switching Configuration Guide (Supporting R05.6.00) User Manual

Page 145

Advertising
background image

Multi-Service IronWare Switching Configuration Guide

115

53-1003036-02

LAG load sharing

5

NOTE

TCP or UDP Destination and Source port is used under the following conditions:
– Packet is non-fragmented and without option, and packet is a TCP or UDP packet
– or, the load-balance force-l4-hashing command is configured.

IPv6 tunnel encapsulated IPv6 traffic: source MAC address and destination MAC address,
IPv6 source and destination address, TCP or UDP source port and TCP or UDP destination
port, and IPv6 next header. and VLAN-ID.

NOTE

TCP or UDP Destination and Source port is used under the following conditions:
– Packet is a TCP or UDP packet
– or, the load-balance force-l4-hashing command is configured.
For 6over4 encapsulated packets, inner IPv6 destination address and inner IPv6 source
address are used if there is at least one GRE or IPv6 tunnel configured.

For MPLS Switching, the hash index is based on the following:

L2VPN traffic: outer source MAC address and outer destination MAC address, up to two
MPLS Labels, VLAN ID, inner source MAC address and inner destination MAC address, If
packet payload is an IPv4 or v6 packet: IPv4v6 source and destination address, IPv4
Protocol Number or IPv6 Next Header ID of the payload are used.

L3VPN traffic or IP shortcut traffic: outer source MAC address and outer destination MAC
address, VLAN ID, inner source IPv4v6 address and inner destination IPv4v6 address,
IPv4 Protocol Number or IPv6 Next Header ID, TCP source port and TCP destination port,
UDP source port and UDP destination port, and up to two MPLS Labels.

MPLS packets with 3 labels: outer source MAC address and outer destination MAC
address, VLAN ID, and all 3 MPLS Labels.

NOTE

For transit LSR’s please note the following:
The load-balance speculate-mpls-ip command must be active. It is on by default.
If the load-balance speculate-mpls-ip command has been configured to be inactive, and the
load-balance speculate-mpls-enet command is active, the packet will be processed like
anL2VPN packet.
If both commands are configured to be inactive, no inner Layer-2 or Layer-3 headers are
considered but up to 3 MPLS labels are used for hashing.

Options for hash based load sharing

The following options can be used to refine the hash calculations used for LAGs:

Speculate UDP or TCP Headers

Mask Layer-4 Source and Destination Port Information

Hash Diversification

Each of these options when configured apply to both IP Load Sharing and LAG Load sharing. They
are described in detail in Configuring IP Chapter.

Advertising