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

Multi-Service IronWare Switching Configuration Guide 119
53-1003036-02
Configuring a LAG
5
You can either assign a LAG ID explicitly or it will be automatically generated by the system. The LAG
ID stays the same across system reload and hitless upgrade.
The command to configure LAGs allows explicit configuration of the LAG ID for static and dynamic
LAGs.
To create a LAG with the LAG ID option, enter a command such as the following.
Brocade(config)# lag blue static
Brocade(config-lag-blue)#
Syntax: [no] lag name [static | dynamic] [id number]
The ID parameter is optional. The value of the ID parameter that you can enter is from 1 to 256. If
you do not enter a LAG ID, the system will generate one automatically. Once the LAG ID is generated
the system will save it in the configuration file along with the LAG name, therefore the value will
stay the same across system reload.
NOTE
The LAG ID parameter is for static and dynamic LAGs only. No explicit configuration of a LAG ID is
allowed on keepalive LAGs.
The static parameter specifies that the LAG with the name specified by the lag-name variable will
be configured as a static LAG.
The dynamic option specifies that the LAG with the name specified by the lag-name variable will be
configured as a dynamic LAG.
Configuration considerations
LAG IDs are unique for each LAG in the system. The same LAG ID cannot be assigned to two or
more different LAGs. If a LAG ID is already used, the CLI will reject the new LAG configuration and
display an error message that suggests the next available LAG ID that can be used.
Example
Brocade(config)#lag lag3 static id 123
Error: LAG id 123 is already used. The next available LAG id is 2.
NOTE
If you upgrade from an earlier version to a version with the LAG ID configuration feature, the old
configuration file will be parsed correctly and each LAG configured will get a LAG ID automatically.
However, afterwards you will not be able to downgrade to any pre 4.0 version because the new
configuration cannot be parsed correctly. 4.0 patch release 4.0.0c and later versions support the
downgrade of LAG ID feature so the user can load 4.0.01 or later versions of the configuration files
without problem. However, the LAG ID configured (both explicitly and implicitly) will be removed and
discarded for backward compatibility.
Example : LAG configured with LAG id 124.
!
lag "lag1" static id 124
ports ethernet 1/2 to 1/3
primary-port 1/3
deploy
!