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

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.

Procedure

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.
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.
Check whether the physical link is faulty.
- If so, go to Step 6.
- If not, go to Step 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.
Check whether the interface leaves the LAG normally.
- If so, go to Step 8.
- If not, go to Step 7.
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.
Collect alarm information and configuration information, and then contact technical support personnel.
End.

Related Information

None.