Brocade Multi-Service IronWare Switching Configuration Guide (Supporting R05.6.00) - Manual (Page 636)

606 Multi-Service IronWare Switching Configuration Guide
53-1003036-02
About Multi-Chassis Trunk (MCT)
18
The ID parameter is optional. The value of the ID parameter that you can enter is from 1 to
256. If you do not enter a LAG ID, the system will generate one automatically. Once the LAG ID
is generated the system will save it in the configuration file along with the LAG name, therefore
the value will stay the same across system reload.
NOTE
The LAG id parameter is for static and dynamic LAGs only. No explicit configuration of a LAG id
is allowed on keepalive LAGs.
The static parameter specifies that the LAG with the name specified by the <lag-name>
variable will be configured as a static LAG.
The dynamic option specifies that the LAG with the name specified by the <lag-name> variable
will be configured as a dynamic LAG.
2. Define the ports the LAG will be using as shown in the following.
Brocade(config-lag-1)# ports ethernet 1/1 to 1/2
Syntax: [no] ports ethernet [slot/port] | to |[slot/port]
Use the appropriate [slot/port] variable to specify a Ethernet port within the LAG that you want
to enable.
3. The primary port must be explicitly assigned using the primary-port command. To designate
the primary port for the static LAG “1”, use the following command.
Brocade(config-lag-1)# primary-port 1/1
Syntax: [no] primary-port<slot/port>
Once a primary port has been configured for a LAG, all configurations that apply to the primary
port are applied to the other ports in the LAG.
NOTE
This configuration is only applicable for configuration of a static or dynamic LAGs
4. After configuring a LAG, you must explicitly enable it before it begins aggregating traffic. This
task is accomplished by executing 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 will no longer display
deployed LAG ports other than the primary port.
To deploy a LAG, at least one port must be in the LAG and the primary port must be specified
for non keep-alive LAGs. After a non keep-alive LAG is deployed, a trunk is formed. If there is
only one port in the LAG, a single port is formed. For a dynamic LAG, LACP is stared for each
LAG port.
Use a command such as the following to deploy LAG 1
Brocade(config-lag-1)# deploy
Syntax: [no] deploy [forced | passive]
When the deploy command is executed:
• For a static and dynamic LAGs, the current veto mechanism is invoked to make sure the
LAG can be formed. If the LAG is not vetoed, a no is formed with all the ports in the LAG.