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

CloudEngine 8800, 7800, 6800, and 5800 V200R005C10

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.6 hwLldpMdnRemTablesChange

LLDP_1.3.6.1.4.1.2011.5.25.134.2.6 hwLldpMdnRemTablesChange

Description

MDN Neighbor information was changed.

MDN neighbor information is changed.

Attributes

Attribute

Description

Alarm or Event

Event

Trap Severity

Warning

Mnemonic Code

hwLldpMdnRemTablesChange

Trap OID

1.3.6.1.4.1.2011.5.25.134.2.6

Alarm ID

This is an event trap and does not involve alarm ID.

Alarm Type

This is an event trap and does not involve alarm type.

Raise or Clear

This is an event trap and does not involve alarm generation or clearance.

Match trap

This is an event trap and does not involve the matching trap.

Parameters

None.

VB

VB OID

VB Name

VB Index

N/A

N/A

N/A

Impact on the System

None.

Possible Causes

  • Cause 1: An MDN neighbor is found.

  • Cause 2: An MDN neighbor is deleted.

  • Cause 3: An MDN neighbor is discarded because of insufficient space.

  • Cause 4: An MDN neighbor is aged.

Procedure

  • Cause 1: An MDN neighbor is found.
    1. Check whether a new MDN neighbor is found.

      • If a new MDN neighbor is found, this log message is informational only, and no action is required.
      • If no new MDN neighbor is found, go to Step 2.

    2. Collect information about configurations, trap messages, and log messages, and contact technical support personnel.
  • Cause 2: An MDN neighbor is deleted.
    1. Check whether an MDN neighbor has been deleted.

      • If an MDN neighbor has been deleted, this log message is informational only, and no action is required.
      • If no MDN neighbor has been deleted, go to Step 2.

    2. Check whether the link between the local device and its MDN neighbor is faulty.

      • If the link is fault, rectify the fault.
      • If the link is normal, go to Step 3.

    3. Collect information about configurations, trap messages, and log messages, and contact technical support personnel.
  • Cause 3: An MDN neighbor is discarded because of insufficient space.
    1. Check whether the number of MDN neighbors stored on the local device has reached the maximum limit.

      • If the number of MDN neighbors has reached the maximum limit, this log message is informational only, and no action is required.
      • If the number of MDN neighbors has not reached the maximum limit, go to Step 2.

    2. Collect information about configurations, trap messages, and log messages, and contact technical support personnel.
  • Cause 4: An MDN neighbor is aged.
    1. Check whether the MDN neighbor information stored on the local device has timed out.

      • If the MDN neighbor information has timed out, this log message is informational only, and no action is required.
      • If the MDN neighbor information has not timed out, go to Step 2.

    2. Check whether the interfaces used to connect the MDN neighbor and local device are shut down.

      • If an interface is shut down, run the undo shutdown command on this interface.
      • If no interface is shut down, go to Step 3.

    3. Check the usage of CPU resources to determine whether the link between the MDN neighbor and local device is congested.

      • If the link is congested, stop unnecessary traffic to alleviate link congestion.
      • If the link is not congested, go to Step 4.

    4. Collect information about configurations, trap messages, and log messages, and then contact technical support personnel.
Translation
Download
Updated: 2019-04-02

Document ID: EDOC1100074754

Views: 17681

Downloads: 25

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