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

Alarm Handling

S600-E 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.3.6.1.4.1.2011.5.25.41.3.2 hwLacpNegotiateFailed

LACP_1.3.6.1.4.1.2011.5.25.41.3.2 hwLacpNegotiateFailed

Description

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.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.41.3.2 Major operationalViolation(8)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

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.

Impact on the System

The link cannot transmit services.

Possible Causes

1.

An MNCD trap was generated when the link became Down.

2.

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

3.

A member interface left the LAG.

4.

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

Procedure

  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

None.

Translation
Download
Updated: 2019-09-24

Document ID: EDOC1000141873

Views: 155097

Downloads: 15

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