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


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


Alarm Handling

S9300, S9300E, and S9300X V200R010C00

This document provides the explanations, causes, and recommended actions of alarms 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_1. hwLacpNegotiateFailed

LACP_1. hwLacpNegotiateFailed


LACP/2/MNCD:OID [oid] The member of LAG neither can take over PDU nor transmit PDUs. (TrunkIndex=[INTEGER], PortIfIndex=[INTEGER], TrunkId=[INTEGER], TrunkName=[OCTET], PortName=[OCTET])

Negotiations over member links failed.


Alarm ID Alarm Severity Alarm Type Major operationalViolation(8)


Name Meaning


Indicates the MIB object ID of the alarm.


Indicates the index of a Trunk.


Indicates the index of a member interface.


Indicates the ID of a Trunk interface.


Indicates the name of a Trunk interface.


Indicates the name of a member interface.

Impact on the System

The link cannot transmit services.

Possible Causes


An MNCD trap was generated when the link became Down.


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


A member interface left the LAG.


The interface received the LACP packet sent from the interfaces on the same device.


  1. Run the display this interface command on the corresponding interface to 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 the alarm is cleared, go to Step 8.

    • If the alarm is not cleared, 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. Run the display eth-trunk command to 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 the alarm is cleared, go to Step 8.

    • If the alarm is not cleared, go to Step 4.

  7. Collect alarm information and configuration information, and then contact technical support personnel.
  8. End.

Related Information


Updated: 2019-08-21

Document ID: EDOC1000142054

Views: 184603

Downloads: 44

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