LACP/4/LACP_STATE_DOWN: The LACP state is down. (PortName=[PortName], TrunkName=[TrunkName], LastReceivePacketTime=[ReceivePacketTime], Reason=[Reason])
| Parameter Name | Parameter Meaning |
|---|---|
|
PortName |
Interface name |
|
TrunkName |
Trunk interface name |
|
ReceivePacketTime |
Time when an LACPDU was received last time |
|
Reason |
Reason why LACP went Down on an interface |
Cause 1: The remote interface was not selected. Please check the remote interface's status and configurations. (The remote interface was not selected. 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. (The interface went down. Check the interface status.)
Cause 3: No LACPDUs were received when the timer expired. Please check link connections or remote interface's status. (LACPDU timeout. Check the connection or the remote interface 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. (The remote system MAC address in the received LACPDU was the same as the local system MAC address. Check the system MAC address of the peer device or check whether the loopback function is enabled on the interface.)
Cause 5: The interface bandwidth was invalid. Please replace this interface. (The interface bandwidth was invalid. 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. (The bandwidth or duplex mode of the member interface was different from that of other member interfaces. 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. (The number of active links was less than the configured minimum number of active links. Check the configuration for the minimum number of active links.)
Cause 8: The number of local active interfaces was greater than max active-linknumber. Please check the local max active-linknumber configuration. (The number of active links was greater than the configured maximum number of active links. Check the configuration for the maximum number of active links.)
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. (The remote portkey in the LACPDU received by this interface was different from that received by other interfaces. Check the remote member interface's bandwidth, duplex mode, and Eth-Trunk ID.)
Cause 10: The remote system MAC address in the LACPDU received from this interface was different from other members. Please check link connections. (The remote system MAC address in the LACPDU received by this interface was different from that received by other member interfaces. 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. (The remote system priority in the LACPDU received by this interface is different from that received by other member interfaces. Check link connections.)
Cause 12: The E-Trunk's Eth-Trunk worked in the backup mode. Please check the Eth-Trunk's status. (The E-Trunk's Eth-Trunk worked in the backup mode. Check the Eth-Trunk status.)
Cause 13: The number of local active bandwidth was less than least active-bandwidth. Please check the local min active-bandwidth configuration. (The local active bandwidth was less than the minimum active bandwidth. Check the local minimum active-bandwidth configuration.)
Cause 15: The partner informations in received LACPDU are not matched with local informations. Please check the remote interface's status and configurations. (The partner information in the received LACPDU is different from that in the local information. Check the remote interface's status and configuration.)