Dell BigIron RX Series, Руководство по настройке

Страница: 320 / 1458

244 BigIron RX Series Configuration Guide
53-1002253-01
Deploying a LAG
8
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 ]
When the deploy command is executed:
For a static and dynamic LAGs, the current trunk veto mechanism is invoked to make sure the trunk
can be formed. If the trunk is not vetoed, a trunk is formed with all the ports in the LAG.
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 trunk 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 trunk 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.
Commands available under LAG once it is deployed
Once a LAG has been deployed, the following configurations can be performed on the deployed
LAG:
•
Configuring ACL-based Mirroring
•
Disabling Ports within a LAG
•
Enabling Ports within a LAG
•
Monitoring and Individual LAG Port
•
Assigning a name to a port within a LAG
•
Enabling sFlow Forwarding on a port within a LAG
•
Setting the sFlow Sampling Rate for a port within a LAG