Configuring the primary port for a lag, Configuring load sharing type – Brocade Multi-Service IronWare Switching Configuration Guide (Supporting R05.6.00) User Manual
Page 152
122
Multi-Service IronWare Switching Configuration Guide
53-1003036-02
Configuring a LAG
5
Ports can be added to an undeployed LAG or to currently deployed LAG using the commands
described. For special considerations when adding ports to or deleting ports from a currently
deployed LAG, refer to the following sections:
“Adding a Port to Currently Deployed LAG”
“Deleting a Port from a Currently Deployed LAG”
Disabling the Detection of Remote LACP Configuration Removal
The lacp-cfg-det-dis command is a global command and is used to disable detecting remote end
LACP configuration removal. By default, this feature this is enabled. To disable this feature, enter a
command such as the following:
Brocade(config)# lacp-cfg-det-dis
Syntax: lacp-cfg-det-dis
NOTE
When you have interoperability with another vendor’s device, you will need to disable this feature as
other vendors devices will remove the fiber.
Configuring the primary port for a LAG
In previous versions of the Multi-Service IronWare software, the lowest number port was assigned
as the primary port in a LAG or LACP configuration. In version 03.7.00 and later, the primary port
must be explicitly assigned using the primary-port command.
To designate the primary port for the static LAG “blue”, use the following command.
Brocade(config)# lag blue static
Brocade(config-lag-blue)# primary-port 3/2
Syntax: [no] primary-port slot/port
Once a primary port has been configured for a LAG, all configurations that apply to the primary port
are applied to the other ports in the LAG.
NOTE
This configuration is only applicable for configuration of a static or dynamic LAGs.
Configuring load sharing type
Individual LAGs can be configured to perform load sharing over the ports in the LAG using either a
hash based or per packet method, as shown in the following.
Brocade(config)# lag blue static
Brocade(config-lag-blue)# trunk-type hash-based
Syntax: [no] trunk-type hash-based | per-packet
NOTE
This configuration is only applicable for configuration of a static or dynamic LAGs.