Mlt With Lacp Configuration Considerations - Avaya 8600 Configuration Manual

Link aggregation fundamentals
• LACP parameters configuration considerations
• Link aggregation and scaling

MLT with LACP configuration considerations

When you configure MLT with LACP, you must enable the aggregation parameter. After you
enable the aggregation parameter, the LACP aggregator maps one-to-one to the specified
MultiLink trunk.
The following lists the steps that are involved when you configure MLT with LACP:
1. Assign a numeric key to the ports you want to include in the LAG.
2. Configure the LAG for aggregation.
3. Enable LACP on the port.
4. Create an MultiLink trunk and assign the same key as in step 1 to it.
The newly created MultiLink trunk with LACP adopts the VLAN membership of its member
ports when the first port is attached to the aggregator associated with this LAG. When a port
detaches from an aggregator, the associated LAG port deletes the member from its list.
Prior to Release 7.1.3, you could not add or remove a VLAN from an active LACP-enabled
MLT without first disabling LACP on the MLT. Starting with Release 7.1.3, this restriction is
removed, namely a VLAN can be added (adding all port members) to or removed (removing
all port members) from an LACP-enabled MLT. The CLI, ACLI, and EDM commands to
configure this feature are shown below.
In the CLI, use either of the following commands to add a VLAN to an active LACP-enabled
MLT:
• config mlt <mlt-id> add vlan <vid>
• config vlan <vid> add-mlt <mlt-id>
In the CLI, use the following command to remove a VLAN from an active LACP-enabled MLT:
• config mlt <mlt-id> remove vlan <vid>
In the ACLI Global Configuration Mode, use either of the following commands to add a VLAN
to an active LACP-enabled MLT:
• mlt <mlt-id> vlan <vid>
• vlan mlt <vid> <mlt-id>
50 Configuration — Link Aggregation, MLT, and SMLT
The MultiLink trunk with LACP only aggregates ports whose key matches its own.
Comments? infodev@avaya.com
on page 54
on page 55
January 2012