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

AR100, AR120, AR160, AR1200, AR2200, AR3200, and AR3600 V300R003

This document provides the trap description, attributes, parameters, impact on the system, possible causes, procedures, and references. This document provides a complete set of traps, through which intended readers are kept of the running status of the device so as to locate faults.
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).
ISIS-STD_1.3.6.1.2.1.138.0.3 isisCorruptedLSPDetected

ISIS-STD_1.3.6.1.2.1.138.0.3 isisCorruptedLSPDetected

Description

ISIS-STD/3/CORRUPT_LSP:OID [oid] The checksum of LSP is wrong. (NotificationSysLevelIndex=[integer], PduLspId=[opaque])

When an IS-IS router sent LSP packets, LSP checksum authentication failed.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.2.1.138.0.3

Minor

other(1)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

NotificationSysLevelIndex

IS-IS level of a device that sends the trap

PduLspId

LSP ID

Impact on the System

Relevant IS-IS services may be interrupted.

Possible Causes

Cause 1: During the LSP refreshment period, a memory fault caused the LSPs to be changed.

Cause 2: LSPs with non-zero checksum did not pass checksum authentication in the local LSDB.

Procedure

  1. Run the display memory-usage command to check whether the memory usage exceeds the upper threshold (around 80%).

    • If the memory usage has reached the upper threshold, go to Step 3.

    • If the memory usage has not reached the upper threshold, go to Step 2.

  2. Run the reset isis all command to restart the IS-IS process, and then check whether the trap is cleared.

    • If the trap is cleared, go to Step 4.

    • If the trap is not cleared, go to Step 3.

  3. Collect alarm information and configuration information, and then contact technical support personnel.
  4. End.

Related Information

None

Translation
Download
Updated: 2019-03-06

Document ID: EDOC1100041475

Views: 81616

Downloads: 49

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