Deploying A Lag - Dell PowerConnect B-RX Configuration Manual

Configuring LACP port priority
In a dynamic or keep alive LAG, the port priority determines the active and standby links. The other
ports (with lower priorities) become standby ports in the trunk group.
BigIron RX(config)# lag blue dynamic
BigIron RX(config-lag-blue)# lacp-port-priority 100000
Syntax: [no] lacp-port-priority <slot/port> <number>
For a port specified by the <slot/port> variable, you can specify a priority in the <number> variable
from 0 – 65535. A higher value indicates a lower priority. The default is 1.
NOTE
This configuration is only applicable for configuration of a dynamic or keep-alive LAGs.
Configuring an LACP timeout
In a dynamic or keep-alive LAG, a port's timeout can be configured as short or long. Once a port is
configured with a timeout option, it will remain in that timeout mode whether it's up or down, or
part of a trunk or not.
All the ports in a trunk should have the same timeout mode. This is checked when the LAG is
enabled on ports. To configure a port for a short LACP timeout use the following command.
BigIron RX(config)# lag blue dynamic
BigIron RX(config-lag-blue)# lacp-timeout short
Syntax: [no] lacp-timeout [long | short]
The long parameter configures the port for the long timeout mode.
The short parameter configures the port for the short timeout mode.
NOTE
This configuration is only applicable for configuration of a dynamic or keep-alive LAGs.

Deploying a LAG

After configuring a LAG, you must explicitly enable it before it takes begins aggregating traffic. This
is accomplished using the deploy command within the LAG configuration. Once the deploy
command is executed, 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. Once a non keep-alive LAG is deployed, a trunk is formed. If there is only one
port in the LAG, a single port trunk is formed. For a dynamic LAG, LACP is stared for each LAG port.
For a keep-alive LAG, no trunk is formed and LACP is started on the LAG port.
You can deploy a LAG as shown in the following for the "blue" LAG.
BigIron RX(config)# lag blue static
BigIron RX(config-lag-blue)# deploy
Syntax: [no] deploy [ forced | passive ]
BigIron RX Series Configuration Guide
53-1001810-01
8
Deploying a LAG
237