Brocade BigIron RX Series Configuration Guide - Manual (Page 612)

534 BigIron RX Series Configuration Guide
53-1002484-04
Configuring MCT
20
Syntax: [no] lag <name> [static | dynamic] [id <number>]
The static option specifies that the LAG with the name specified by the lag <name> parameter
is configured as a static LAG.
The dynamic option specifies that the LAG with the name specified by the lag <name>
parameter is configured as a dynamic LAG.
The id <number> parameter is optional. The id <number> parameter can take values from 1
through 256. If you do not specify a LAG ID, the system automatically generates a LAG ID and
saves it in the configuration file along with the LAG name, and the value remains the same
across the system reload.
The id <number> parameter is only applicable for the static and dynamic LAGs. Explicit
configuration of a LAG ID is not allowed on the keepalive LAGs.
2. Define the ports to be used by LAG 1 by entering the following command.
BigIron RX(config-lag-1)# ports ethernet 1/1 to 1/2
Syntax: [no] ports ethernet <slot/port> to <slot/port>
The ethernet [slot/port] specifies the Ethernet port within the LAG that you want to enable.
3. Assign the primary port explicitly using the primary-port command. Designate the primary port
for the static LAG 1 by entering the following command.
BigIron RX(config-lag-1)# primary-port 1/1
Syntax: [no] primary-port <slot/port>
After a primary port has been configured for LAG 1, all the configurations that apply to the
primary port are applied to the other ports in LAG 1.
4. After configuring a LAG, you must explicitly enable the LAG before it begins aggregating traffic
by using the deploy command within the LAG configuration. After the deploy command runs,
the LAG is in the aggregating mode. Only the primary port within the LAG is available at the
individual interface level. Any configuration performed on the primary port applies to all ports
within the LAG. The running configuration no longer displays the deployed LAG ports other than
the primary port.
To deploy the LAG, at least one port must be configured in that LAG and the primary port must
be specified for the non-keepalive LAGs. After the non-keepalive LAG is deployed, a trunk is
formed.
Deploy LAG 1 by entering the following command.
BigIron RX(config-lag-1)# deploy
Syntax: [no] deploy [forced | passive]
When the deploy command is executed:
• For the static and dynamic LAGs, the current veto mechanism is invoked to make sure the
LAG is formed.
• For dynamic LAGs, LACP is activated on all the LAG ports. When activating LACP, use active
mode, unless the passive option is not specified.
• For the keepalive LAGs, a LAG is formed and LACP is started on the LAG ports.
After the deploy command is issued, all the LAG ports behave like a single port.