LACP
LACP/3/LAG_DOWN_REASON_EVENT
Message
LACP/3/LAG_DOWN_REASON_EVENT: The member of the LACP mode Eth-Trunk interface went down. (TrunkName=[STRING], PortName=[STRING], Reason=[STRING])
Parameters
Parameter Name | Parameter Meaning |
---|---|
TrunkName |
Name of an Eth-Trunk interface in static LACP mode |
PortName |
Name of the member interface of an Eth-Trunk interface in static LACP mode |
Reason |
Reason why the member interface of an Eth-Trunk interface in static LACP mode went Down |
Possible Causes
- Cause 1: The lower limit on the number of Eth-Trunk member links was not met.
- Cause 2: The upper limit on the number of Eth-Trunk member links was not met.
- Cause 3: The local member or Eth-Trunk interface was shut down.
- Cause 4: The local member interface's rate changed.
- Cause 5: The local member interface's simplex/duplex mode was changed.
- Cause 6: Bit errors were detected on the local member interface.
- Cause 7: The preemption delay timed out.
- Cause 8: The receive timer expired.
- Cause 9: The local Eth-Trunk interface's aggregation flag was set to false.
- Cause 10: The E-Trunk went to the slave state.
- Cause 11: The E-Trunk's IP address changed.
- Cause 12: The remote and local system IDs were set to the same value.
- Cause 13: The lower limit on the bandwidth of Eth-Trunk member links was not met.
Procedure
- Troubleshoot the fault based on the reasons listed in the log, as well as the LACP state and parameters of the local Eth-Trunk interface's member interfaces. For details, see the section "Checking the Configurations" in Configuration Guide - Configuring an Eth-Trunk Interface to Work in Static LACP Mode of the product document.
- Collect log information and configuration information, and then contact technical support personnel.
LACP/3/LAG_DOWN_REASON_PDU
Message
LACP/3/LAG_DOWN_REASON_PDU: The member of the LACP mode Eth-Trunk interface went down because the local device received changed LACP PDU from partner. (TrunkName=[STRING], PortName=[STRING], Reason=[STRING], OldParam=[STRING], NewParam=[STRING])
Description
The member interface of an Eth-Trunk interface in static LACP mode went Down because the LACPDUs sent by the remote end changed.
Parameters
Parameter Name | Parameter Meaning |
---|---|
TrunkName | Name of an Eth-Trunk interface in static LACP mode |
PortName | Name of the member interface of an Eth-Trunk interface in static LACP mode |
Reason | Reason why the member interface of an Eth-Trunk interface in static LACP mode went Down |
OldParam | Original parameter |
NewParam | New parameter |
LACP/3/LAG_DOWN_REASON_SYS
Message
LACP/3/LAG_DOWN_REASON_SYS: Members of the LACP mode Eth-Trunk interface went down. (TrunkName=[STRING], Reason=[STRING])
Parameters
Parameter Name | Parameter Meaning |
---|---|
TrunkName | Name of an Eth-Trunk interface in static LACP mode |
Reason | Reason why the member interface of an Eth-Trunk interface in static LACP mode went Down |
LACP/3/OPTICAL_FIBER_MISCONNECT
Message
LACP/3/OPTICAL_FIBER_MISCONNECT: The member of the LACP mode Eth-Trunk interface received an abnormal LACPDU, which may be caused by optical fiber misconnection. (TrunkName=[STRING], PortName=[STRING], LocalParam=[STRING], PDUParam=[STRING])
Description
The member of an Eth-Trunk interface in static LACP mode received an abnormal LACPDU, which may be caused by the optical fiber misconnection.
Parameters
Parameter Name | Parameter Meaning |
---|---|
TrunkName | Name of an Eth-Trunk interface in static LACP mode |
PortName | Name of the member interface of the Eth-Trunk interface in static LACP mode |
LocalParam | Local parameters |
PDUParam | Local parameters received using LACPDUs |
Possible Causes
The optical fiber connection was incorrect, or packets were invalid.
During an LACP negotiation between a Huawei device and a non-Huawei device, if the non-Huawei device implementation does not completely comply with the LACP protocol standard, the log may be reported on the Huawei device.
Procedure
- Check whether the members of the Eth-Trunk interface in
static LACP mode have optical fibers incorrectly connected based on LocalParam and PDUParam in the log.
- If optical fibers were connected incorrectly, go to Step 2.
- If optical fibers were connected correctly, go to Step 3.
- Connect the optical fibers correctly.
- Collect log information and configuration information, and then contact technical support personnel.