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


To have a better experience, please upgrade your IE browser.


S12700 V200R013C00 Log Reference

This document provides the explanations, causes, and recommended actions of logs 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).




LLDP/4/BAD_PACKET:[ULONG] invalid packets were received after latest notification. The last invalid packet came from interface [STRING].


The ULONG field specifies the number of invalid LLDP packets received by a device. The STRING field indicates the name of the interface from which the last invalid LLDP packet is received.

When a device receives invalid LLDP packets for the first time, it will print this log and set the counter of invalid LLDP packets to 1. Within the following 30 seconds:
  • If the device receives invalid LLDP packets, the counter will increase by one. This log will be printed again after 30 seconds.
  • If the device does not receive invalid LLDP packets, it will not print the log and clear the counter.


Parameter Name Parameter Meaning
ULONG Indicates the number of received invalid LLDP packets.
STRING Indicates the interface from which the last LLDP packet is received.

Possible Causes

The device received invalid LLDP packets.


  1. Obtain the interface that prints this log, and run the display interface interface-type interface-number command to check the interface status. If the field Line protocol current state is displayed as Up, the interface is in Up state.

    • If the interface is in Up state, go to step 3.
    • If the interface is not in Up state, go to step 2.

  2. Check whether the interface is properly connected.

    • If so, go to step 4.
    • If not, go to step 3.

  3. Check whether an invalid connection exists.

    • If so, remove the connection, and go to step 5.
    • If not, go to step 4.

  4. Run the capture-packet interface interface-type interface-number destination terminal command in the system view to capture packets received by the interface STRING. Check whether the captured LLDP packets are sent from the same source MAC address.

    • If so, run the mac-address blackhole mac-address command in the system view to set this MAC address as a blackhole MAC address, and go to step 5.
    • If not, go to step 6.

  5. Check whether the device prints this log again after 30 seconds.

    • If so, go to step 6.
    • If not, no further action is required.

  6. Check whether the LLDP function needs to be enabled on the interface.

    • If so, go to step 7.
    • If not, run the undo lldp enable command on the interface to disable the LLDP function. The problem will be resolved.

  7. Collect log information and configuration information, and then contact technical support personnel. You can collect diagnostic information using the display diagnostic-information command.



LLDP/4/TOOMANYCDPNBRS:No enough resources to save CDP neighbors


The number of CDP neighbors reached the maximum value.


Parameter Name Parameter Meaning
None None

Possible Causes

Generally, the number of CDP neighbors on a switch cannot reach the maximum value. If the number exceeds the maximum value, the possible causes are:

  1. Transparent transmission of CDP packets has been enabled on the device directly connected to the switch. As a result, a large number of devices that are not directly connected to the switch become CDP neighbors of the switch logically.
  2. The switch receives a large number of manually created CDP packets. As a result, the number of CDP neighbors reaches the maximum value.


  1. Run the cdp clear neighbor [ interface interface-type interface-number ] command in the user view of the switch to clear CDP neighbors globally or on a specified interface.
  2. Run the undo lldp compliance cdp receive command on the interface that does not need to receive CDP packets to disable CDP-compatible LLDP on the interface. The interface then does not establish a CDP neighbor relationship with the remote device when receiving a CDP packet.
  3. If the number of CDP neighbors on the switch reach the maximum value due to manually created CDP packets, eliminate the attack source on the network.



LLDP/4/TOOMANYNEIGHBORS:No enough resources to save LLDP neighbors


The number of LLDP neighbor entries at the remote end exceeds the maximum value


Parameter Name Parameter Meaning
None None

Possible Causes

In general, the topology does not generate the event that the number of LLDP neighbors exceeds the maximum value (the maximum number of global LLDP neighbors is 4096, and the maximum number of LLDP neighbors under a port is 256). The event happens because the peer device connected to the current device enables the LLDP transparent transmission function so that a large number of non-direct connection devices become the LLDP neighbors of the current device.


  1. Disable the LLDP function on the ports whose topology information is less important (in the view of the ports, run the undo lldp enable command) to release space for new neighbors.
Updated: 2019-04-09

Document ID: EDOC1100065665

Views: 5531

Downloads: 15

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