(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 will still be load balanced among the 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.
Procedure
- Run:
system-viewThe 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.
The timeout interval for receiving LACPDUs is three times the interval for sending LACPDUs. 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 timeout intervals at both ends. However, to facilitate maintenance, you are advised to use the same timeout interval at both ends.
Each member interface in an Eth-Trunk processes a maximum of 20 LACPDUs every second; a card on a switch processes a maximum of 50 LACPDUs every second. Extra LACPDUs are discarded.