LAG/MLAG
LAG (Link Aggregation Group) and MLAG (Multi-Chassis Link Aggregation) are configured in the Control Plane section of the task page. They combine multiple physical links into one logical link to increase throughput and provide resiliency during testing.
LAG defines an aggregate on one chassis. MLAG defines a coordinated aggregate across two chassis, typically a leaf/spine or top-of-rack switch pair. In the task, configure the group and its members first, and then use the logical LAG interface wherever the testbed expects an aggregated link.
Table — Basic LAG/MLAG Parameters
| Name | Description | Value |
|---|---|---|
| Name / Instance ID | Aggregate identifier | Must be unique; available as a logical interface |
| Mode | Static LAG or LACP | Must match the DUT |
| Members | Agent physical ports | A port normally belongs to only one LAG |
| Min/Max active links | Limits on the number of active links | Follow the testbed policy |
| System priority / System ID | LACP actor parameters | Priority and MAC address |
| MLAG peer | Peer parameters for the second chassis | Used in multi-chassis scenarios |
| Hash / load-balance | Flow-distribution policy | When available in the UI |
The related Access Plane protocol is LACP, which emulates an LACP actor in access scenarios. Use this section for Control Plane aggregation.
After starting, check the number of active links, LACP PDU state, and whether traffic becomes pinned to a single member. If the links do not aggregate, compare the interface names, LACP timeout (short/long), and System ID with the DUT configuration.