deploy

Deploys the LAG.
Syntax
deploy [ passive ]
no deploy [ passive ]
Command Default

The LAG is not deployed.

Parameters
passive
Configures Link Aggregation Control Protocol (LACP) as passive. This option is applicable only to dynamic LAGs and LACP is active by default.
Modes

LAG configuration mode

Usage Guidelines

A LAG must be created before being deployed. 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.

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.

When activating LACP, LACP is activated as active if the passive keyword is not specified. If you need to configure LACP as passive, use the passive keyword. Once the deploy command is issued, all LAG ports will behave like a single port. For dynamic LAGs, LACP is activated on all of the LAG ports.

The no form of the command undeploys the LAG. Once the LAG is undeployed, all the secondary ports are disabled automatically and there will be no changes to the primary port. Also, for dynamic LAGs, LACP is deactivated on all ports.

Examples

The following example shows how to deploy a LAG.

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

The following example shows how to deploy a dynamic LAG as passive.

device(config)# lag test2 dynamic
device(config-lag-test2)# deploy passive