Step 1: Configure ICL and LAGs for client devices

You can configure a static or dynamic LAG. Static LAG groups are manually configured aggregate links containing multiple ports. Dynamic LAGs use Link Aggregation Control Protocol (LACP) to maintain aggregate links over multiple port. LACP PDUs are exchanged between ports on each device to determine if the connection is still active. The LAG then shuts down any port whose connection is no longer active. You can configure static or dynamic LAGs for cluster clients. Static LAGs are manually configured aggregate links containing multiple ports. Dynamic LAGs use Link Aggregation Control Protocol (LACP) to maintain aggregate links over multiple ports. LACP PDUs are exchanged between ports on each device to determine if the connection is still active. The LAG then shuts down any port whose connection is no longer active.
NOTE
ICL LAGs support only static trunks.

Syntax: [no] lag lag-name [ { static | dynamic } [ id number ] ]

To configure an ICL static LAG, enter the following commands.

device-1(config)# lag MCT_lag1 static id 2
Brocade-1(config-lag-MCT_lag1)# ports ethernet 1/1/7 to 1/1/8
Brocade-1(config-lag-MCT_lag1)# primary-port 1/1/7
Brocade-1(config-lag-MCT_lag1)# deploy

To configure a dynamic LAG for a client device, enter the following commands for each MCT cluster device.

device-1(config)# lag client_lag2 dynamic id 5
Brocade-1(config-lag-client_lag2)# ports ethernet 1/2/11
Brocade-1(config-lag-client_lag2)# primary-port 1/2/11
Brocade-1(config-lag-client_lag2)# deploy