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.0.8802.1.1.2.0.0.1 lldpRemTablesChange

LLDP_1.0.8802.1.1.2.0.0.1 lldpRemTablesChange

Description

LLDP neighbor information was changed. (Added=[lldpStatsRemTablesInserts], Deleted=[lldpStatsRemTablesDeletes], Dropped=[lldpStatsRemTablesDrops], Aged=[lldpStatsRemTablesAgeouts])

Neighbor information is changed.

Attributes

Attribute

Description

Alarm or Event

Event

Trap Severity

Warning

Mnemonic Code

lldpRemTablesChange

Trap OID

1.0.8802.1.1.2.0.0.1

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

Parameter Description
LldpStatsRemTablesInserts Indicates the number of new neighbors.
LldpStatsRemTablesDeletes Indicates the number of neighbors that are deleted.
LldpStatsRemTablesDrops Indicates the number of neighbors that are discarded.
LldpStatsRemTablesAgeouts Indicates the number of neighbors that are aged.

VB

VB OID

VB Name

VB Index

1.0.8802.1.1.2.1.2.2

lldpStatsRemTablesInserts

None

1.0.8802.1.1.2.1.2.3

lldpStatsRemTablesDeletes

None

1.0.8802.1.1.2.1.2.4

lldpStatsRemTablesDrops

None

1.0.8802.1.1.2.1.2.5

lldpStatsRemTablesAgeouts

None

Impact on the System

None.

Possible Causes

  • Cause 1: A neighbor is found.

  • Cause 2: A neighbor is deleted.

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

  • Cause 4: A neighbor is aged.

Procedure

  • Cause 1: A neighbor is found.
    1. Check whether LLDP is enabled on the neighbor.

      • If LLDP is enabled, this log message is informational only, and no action is required.
      • LLDP is not enabled, go to Step 2.

    2. Collect information about configurations, trap messages, and log messages, and then contact technical support personnel.
  • Cause 2: A neighbor is deleted.
    1. Check whether LLDP is disabled on the neighbor.

      • If LLDP is disabled, run the lldp enable (system view) command on the neighbor.
      • If LLDP is not disabled, go to Step 2.

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

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

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

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

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

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

    2. Check whether the interfaces used to connect the neighbor to the 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 neighbor and local device is congested.

      • If the link is congested, stop unnecessary traffic to alleviate the 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: 24548

Downloads: 31

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