No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Log Reference

CloudEngine 8800, 7800, 6800, and 5800 V200R005C00

This document provides the explanations, causes, and recommended actions of logs on the product.
Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
LACP/2/hwLacpNegotiateFailed_active

LACP/2/hwLacpNegotiateFailed_active

Message

LACP/2/hwLacpNegotiateFailed_active: The member of LAG negotiation failed. (TrunkIndex=[TrunkIndex], PortIfIndex=[PortIfIndex], TrunkId=[TrunkId], TrunkName=[TrunkName], PortName=[PortName], Reason=[Reason])

Description

Negotiations over member links failed.

Parameters

Parameter Name Parameter Meaning

TrunkIndex

Indicates the index of a Trunk.

PortIfIndex

Indicates the index of a member interface.

TrunkId

Indicates the ID of a Trunk interface.

TrunkName

Indicates the name of a Trunk interface.

PortName

Indicates the name of a member interface.

Reason

Indicates the cause of the alarm.

Possible Causes

Cause 1: Interface physical link is down.

Cause 2: No LACP packet was received from the remote end when the timer expired.

Procedure

  1. Check whether the interface is Down.

    • If so, go to Step 2.
    • If not, go to Step 4.

  2. Run the undo shutdown command to check whether the alarm is cleared.

    • If so, go to Step 8.
    • If not, go to Step 3.

  3. Check whether the physical link is faulty.

    • If so, go to Step 6.
    • If not, go to Step 4.

  4. Check whether there is an interface on the local or remote end of the link leaving the LAG.

    • If so, go to Step 5.
    • If not, go to Step 7.

  5. Check whether the interface leaves the LAG normally.

    • If so, go to Step 8.
    • If not, go to Step 7.

  6. Repair the physical link and then check whether the alarm is cleared.

    • If so, go to Step 8.
    • If not, go to Step 4.

  7. Collect information about configurations, trap messages, and log messages, and then contact technical support personnel.
  8. End.
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100039602

Views: 115341

Downloads: 85

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next