Configuration of a lag, Creating a link aggregation group (lag) – Brocade BigIron RX Series Configuration Guide User Manual
Page 319
![background image](/manuals/361694/319/background.png)
BigIron RX Series Configuration Guide
241
53-1002484-04
Configuration of a LAG
8
•
IPv4 UDP packets: source MAC address and destination MAC address, source IP address
and destination IP address, and UDP source port and UDP destination port.
•
IPv6 non-TCP/UDP packets: source MAC address and destination MAC address, source IP
address and destination IP address.
•
IPv6 TCP packets: source MAC address and destination MAC address, source IP address
and destination IP address and TCP source port and TCP destination port.
•
IPv6 UDP packets: source MAC address and destination MAC address, source IP address
and destination IP address, and UDP source port and UDP destination port.
The device uses the hash index in the following formula, using the modulo operator (written as “%”
in C programming language).
(hash index)% (Number of trunk ports in a trunk group) = selected trunk port
Configuration of a LAG
The following configuration procedures are used to configure a LAG. Depending upon whether you
are configuring a static, dynamic or keep-alive LAG, the configuration procedures may or may not
apply as described:
•
Creating a Link Aggregation Group – Required for all static, dynamic or keep alive LAGs.
•
Adding Ports to a LAG – Required for all static, dynamic, or keep alive LAGs. A keep alive LAG
contains only one port with static and dynamic LAGs can have 2 to 8 ports.
•
Configuring the Primary Port for a LAG – Required for all static and dynamic LAGs. Since a keep
alive LAG contains only one port, it is unnecessary to configure this parameter.
•
Specifying the Trunk Threshold for a Trunk Group – Optional for static and dynamic LAGs. Since
a keep alive LAG contains only one port, it is unnecessary to configure this parameter.
•
Configuring LACP Port Priority – Optional for dynamic and keep alive LAGs. Because static LAGs
do not support LACP, it is unnecessary to configure this parameter.
•
Configuring an LACP Timeout – Optional for dynamic and keep alive LAGs. Because static LAGs
do not support LACP, it is unnecessary to configure this parameter.
Creating a Link Aggregation Group (LAG)
Before setting-up ports or configuring any other aspects of a LAG, you must create it as shown in
the following.
BigIron RX(config)# lag blue static
BigIron RX(config-lag-blue)#
Syntax: [no] lag <lag-name> static | dynamic | keep-alive
“Allowable characters for LAG names”
on page 13 for guidelines on LAG naming
conventions.
The static option specifies that the LAG with the name specified by the <lag-name> variable will be
configured as a static LAG. The static LAG configuration is much the same as the Trunk feature .
The dynamic option specifies that the LAG with the name specified by the <lag-name> variable will
be configured as a dynamic LAG. The dynamic LAG configuration is much the same as the LACP
feature.