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. All the secodary ports should have the same IP directed-broadcast configuration as the primary port. 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.

device(config)# lag blue static
device(config-lag-blue)# deploy

Syntax: [no] deploy [ passive ]

When the deploy command is executed:

For dynamic LAGs, LACP is activated on all LAG ports. When activating LACP, use active mode if passive is not specified; otherwise, use passive mode.

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. All the secondary ports are disabled automatically and there will be no changes to the primary port.