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

Multi-Service IronWare Switching Configuration Guide 127
53-1003036-02
Deploying a LAG
5
Brocade(config)# lag blue static
Brocade(config-lag-blue)# deploy
Brocade(config-lag-blue)# disable ethernet 3/1
Syntax: [no] disable ethernet [slot/port] | named [name]
Use the ethernet option with the appropriate [slot/port] variable to specify a Ethernet port within
the LAG that you want to disable.
Use the named option with the appropriate [slot/port] variable to specify a named port within the
LAG that you want to disable.
Enabling ports within a LAG
You can enable an individual port within a LAG using the enable command within the LAG
configuration as shown in the following.
Brocade(config)# lag blue static
Brocade(config-lag-blue)# deploy
Brocade(config-lag-blue)# enable ethernet 3/1
Syntax: [no] enable ethernet [slot/port] | named [name]
Use the ethernet option with the appropriate [slot/port] variable to specify a Ethernet port within
the LAG that you want to enable.
Use the named option with the appropriate [slot/port] variable to specify a named port within the
LAG that you want to enable.
Adding a Port to Currently Deployed LAG
Ports can be added to a currently deployed LAG. Adding a port to a deployed LAG uses the same
procedures as described in
“Adding Ports to a LAG or Deleting Ports from a LAG” . When you add
ports to a deployed LAG, the MAC address of the port being added is changed to that of the primary
port of the LAG to which it is being added.
When adding a port to a currently deployed static LAG the LACP BPDU Forwarding configuration
must be the same as the LAG. Follow the procedure on
“Enabling and Disabling LACP BPDU
Forwarding on a Port” .
Deleting a Port from a Currently Deployed LAG
Ports can be deleted from a currently deployed LAG. Deleting a port in a currently deployed LAG
uses the same procedures as described in
“Adding Ports to a LAG or Deleting Ports from a LAG” .
However, when deleting ports from a currently deployed LAG you must consider the following:
• The primary port cannot be removed.
• If removal of a port will result in the trunk threshold value becoming greater than the number
of ports in the LAG, the port deletion will be rejected.
• The port being deleted must be in the “disabled” state or you must use the forced option (as
described in the following command syntax) when deleting it from a currently deployed LAG.
Otherwise, the deletion request will be denied and the following error message will be
displayed: “Error: ports to be deleted from the deployed LAG are not disabled, deleting these
ports from the LAG may form a loop – aborted.”