The lacp timeout command configures the timeout interval for an Eth-Trunk in LACP mode to receive LACPDUs.
The undo lacp timeout command restores the default timeout interval.
By default, the timeout interval for an Eth-Trunk to receive LACPDUs is 90s.
| Parameter | Description | Value |
|---|---|---|
| fast | Indicates that the timeout interval for an Eth-Trunk
in LACP mode to receive LACPDUs is 3 seconds. If fast is specified, the remote device sends an LACPDU every 1 second. In this mode, the local device can quickly respond to LACPDUs from the remote device but consumes more system resources compared with the slow mode. |
- |
| user-defined user-defined | Specifies the timeout interval for an Eth-Trunk to receive LACPDUs when fast is specified. |
The value is an integer that ranges from 3 to 90, in seconds. |
| slow | Indicates that the timeout interval for an Eth-Trunk
in LACP mode to receive LACPDUs is 90 seconds. If slow is specified, the remote device sends an LACPDU every 30 seconds. In this mode, the local device responds to LACPDUs from the remote device slowly but consumes fewer system resources compared with the fast mode. The timeout interval on the two ends can be different. To facilitate maintenance, you are advised to set the same timeout interval at both ends. |
- |
Usage Scenario
If two devices are connected through three GE interfaces at each end and the three GE interfaces are bundled into an Eth-Trunk, you can run the mode lacp command to configure the Eth-Trunk to work in LACP mode and run the least active-linknumber link-number command to set the lower threshold for the number of active interfaces to 2.
If the Eth-Trunk on the local device cannot detect a self-loop or fault that occurred on a member interface in the LAG on the remote device, the local Eth-Trunk still has three member interfaces in Up state and the three member interfaces still load balance data, causing packet loss. To ensure reliable data transmission, run the lacp timeout command to set the timeout interval for the Eth-Trunk to receive LACPDUs. If a local member interface does not receive any LACPDU within the configured timeout interval, it becomes Down immediately and no longer forwards data.
The number of Up member interfaces does not fall below the configured lower threshold for the number of active interfaces, so the Eth-Trunk is still Up. In this case, data is load balanced between the two member interfaces in Up state and reliably transmitted to the remote end.
Prerequisites
The Eth-Trunk has been configured to work in LACP mode using the mode lacp command in the Eth-Trunk interface view.
Precautions
After the timeout interval is successfully configured, pay attention to the following points:
The timeout interval configured on an Eth-Trunk takes effect on all its member interfaces.