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/4/LACP_STATE_DOWN
Message
LACP/4/LACP_STATE_DOWN: The LACP state is down. (PortName=[PortName], TrunkName=[TrunkName], LastReceivePacketTime=[ReceivePacketTime], Reason=[Reason])
Parameters
| Parameter Name | Parameter Meaning |
|---|---|
| PortName | Interface name |
| TrunkName | Trunk interface name |
| LastReceivePacketTime | Time when an LACPDU was received last time |
| Reason | Reason why LACP went Down on an interface |
Possible Causes
- Cause 1: The remote interface was not selected. Please check the remote interface's status and configurations.
- Cause 2: The interface went down physically or flapped to down. Please check the interface's status, duplex mode, bandwidth, and so on.
- Cause 3: No LACPDUs were received when the timer expired. Please check link connections or remote interface's status.
- Cause 4: The remote system MAC address in the received LACPDU was the same as the local system MAC address. Please check remote system MAC address or the interface's loopback status.
- Cause 5: The interface bandwidth was invalid. Please replace this interface.
- Cause 6: The bandwidth or duplex mode of the interface was different from other members. Please check the interface's bandwidth and duplex mode.
- Cause 7: The number of local active interfaces was less than least active-linknumber. Please check the local min active-linknumber configuration.
- Cause 8: The number of local active interfaces was greater than max active-linknumber. Please check the local max active-linknumber configuration.
- Cause 9: The remote portkey in the LACPDU received from this interface was different from other members. Please check the remote members' bandwidths, duplex modes, or Eth-Trunk IDs.
- Cause 10: The remote system MAC address in the LACPDU received from this interface was different from other members. Please check link connections.
- Cause 11: The remote system priority in the LACPDU received from this interface is different from other members. Please check link connections.
- Cause 12: The E-Trunk's Eth-Trunk worked in the backup mode. Please check the Eth-Trunk's status.
- Cause 13: The number of local active bandwidth was less than least active-bandwidth. Please check the local min active-bandwidth configuration.
- Cause 14: The partner informations in received LACPDU are not matched with local informations. Please check the remote interface's status and configurations.
