< Home

(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. To prevent this situation, set the timeout interval for sending LACPDUs. If a local member interface does not receive any LACPDU within the configured timeout interval, it considers that the remote end is reachable. Then the local member interface becomes Down immediately and no longer forwards data.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface eth-trunk trunk-id

    The Eth-Trunk interface view is displayed.

  3. 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 modes of the timeout interval at the two ends. However, to facilitate maintenance, you are advised to use the same mode at both ends.

    • Each member interface in an Eth-Trunk processes a maximum of 20 LACPDUs every second; a switch processes a maximum of 100 LACPDUs every second. Extra LACPDUs are dropped.

Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >