(Optional) Setting the Timeout Interval for Receiving LACPDUs
Context
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, data on the local device is still load balanced among original active interfaces. As a result, data traffic on the faulty link is discarded.
After the timeout interval at which LACPDUs are received is set, if a local member interface does not receive any LACPDUs within the configured timeout interval, the local member interface becomes Down immediately and no longer forwards data.
Procedure
- Run system-view
The system view is displayed.
- Run interface eth-trunk trunk-id
The Eth-Trunk interface view is displayed.
- Run lacp timeout { fast [ user-defined user-defined ] | slow }
The timeout interval at which LACPDUs are received is set.
By default, the timeout interval at which an Eth-Trunk receives LACPDUs is 90 seconds.
-
After you run the lacp timeout command, the local end notifies the remote end of the timeout interval by sending LACPDUs. When fast is specified, the interval for sending LACPDUs is 1 second. When slow is specified, the interval for sending LACPDUs is 30 seconds.
-
When fast is specified, the timeout interval for receiving LACPDUs is 3 seconds. When slow is specified, the timeout interval for receiving LACPDUs is 90 seconds.
-
You can use different modes of the timeout interval at the two ends. However, to facilitate maintenance, you are advised to use the same mode at both ends.
-
- Run commit
The configuration is committed.