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

Multi-Service IronWare Switching Configuration Guide 125
53-1003036-02
Deploying a LAG
5
The short keyword configures the port for the short timeout mode—3 seconds. In the short timeout
configuration, an LACPDU is sent every second. If no response comes from its partner after 3
LACPDUs are sent, a timeout event occurs, and the LACP state machine transitions to the
appropriate state based on its current state.
If you specify neither long nor short, the state machine operates based on the standard IEEE
specification as its default behavior. The original IEEE specification says that the state machine
starts with short the timeout and moves to the long timeout after the LAG is established. However,
sometimes a vendor’s implementation always uses either the short timeout or the long timeout
without changing the timeout. Brocade provides this command so that you can configure Brocade
devices to interoperate with other vendor’s devices.
NOTE
This configuration is applicable to the configuration of dynamic or keep-alive LAGs only.
Deploying a LAG
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 LAG is formed. If there is only one
port in the LAG, a single port LAG is formed. For a dynamic LAG, LACP is started for each LAG port.
For a keep-alive LAG, no LAG is formed and LACP is started on the LAG port.
You can deploy a LAG as shown in the following for the “blue” LAG.
Brocade(config)# lag blue static
Brocade(config-lag-blue)# deploy
Syntax: [no] deploy [ forced | passive ]
When the deploy command is executed:
For a static and dynamic LAGs, the current LAG veto mechanism is invoked to make sure the LAG
can be formed. If the LAG is not vetoed, a LAG is formed with all the ports in the LAG.
For dynamic LAGs, by default all LAG ports will be on the active mode and LACP is activated on all
LAG ports. If you specify passive mode, the LACP ports do not initiate the aggregation aggressively
and ports will respond to LACP packets only when it receives LACP PDUs.
For a keep-alive LAGs, no LAG is formed, and LACP is started on the LAG port.
Once the deploy command is issued, all LAG ports will behave like a single port.
If the no deploy command is executed, the LAG is removed. For dynamic LAGs, LACP is de-activated
on all of the LAG ports.
If the no deploy command is issued and more than 1 LAG port is not disabled the command is
aborted and the following error message is displayed: “Error 2 or more ports in the LAG are not
disabled, un-deploy this LAG may form a loop - aborted.” Using the forced keyword with the no
deploy command in the previous situation, the un-deployment of the LAG is executed.