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

Reminder

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

upgrade

Alarm Handling

S600-E V200R010C00

This document provides the explanations, causes, and recommended actions of alarms 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_1.3.6.1.4.1.2011.5.25.134.2.7 hwLldpRateExcessive

LLDP_1.3.6.1.4.1.2011.5.25.134.2.7 hwLldpRateExcessive

Description

LLDP/4/RATEEXCESSIVE: OID [oid] The rate of received PDUs exceeded the threshold. (IfName=[STRING])

The LLDP packets received by an interface exceeded five in one second.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.134.2.7 Warning equipmentAlarm(6)

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
IfName Indicates the interface name.

Impact on the System

If the interface is attacked by LLDP packets, it may not receive LLDP packets sent by a neighbor device. As a result, the judgment of the network topology for the NMS will be affected.

Possible Causes

  • The interface had more than five LLDP neighbors, and all neighbors sent LLDP packets to it simultaneously.
  • The interface was attacked by LLDP packets.

Procedure

  1. Run the display lldp neighbor interface interface-type interface-number command in any view to check the number of LLDP neighbors on the interface found in the alarm. The n in "STRING has n neighbor(s)" displayed in the first line is the number.

    • If n ranges from 0 to 5, the interface is attacked by LLDP packets. Go to step 2.
    • If n is greater than 5, the alarm cause cannot be determined. Go to step 2.

  2. Run the capture-packet interface interface-type interface-number destination terminal command in the system view to capture packets received by the STRING interface. Check whether two or more captured LLDP packets have 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 4.
    • If not, go to step 3.

  3. Check whether the current LLDP neighbor relationships on this interface are needed.

    • If so, this alarm is informational only, and no action is required.
    • If not, go to step 4.

  4. Disconnect unnecessary LLDP neighbor relationships. If the neighbor relationships can be disconnected, run the undo lldp enable command on the neighbor's interface that establishes a neighbor relationship with the local device to disable the LLDP function, or run the undo l2protocol-tunnel lldp enable command to disable transparent transmission for LLDP packets on the intermediate device's interface that connects to the LLDP neighbor device.
  5. If the alarm persists, collect alarm information and configuration information, and then contact technical support personnel.

Related Information

None

Translation
Download
Updated: 2019-04-18

Document ID: EDOC1000141873

Views: 127833

Downloads: 14

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