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_1.3.6.1.4.1.2011.5.25.24.2.4.14 hwIsisSeqNumExceedThreshold

ISIS_1.3.6.1.4.1.2011.5.25.24.2.4.14 hwIsisSeqNumExceedThreshold

Description

ISIS/2/ hwIsisSeqNumExceedThreshold:OID [oid] The LSP sequence number has exceeded the upper threshold value. (sysInstance=[sysInstance], sysInstanceofLevel=[sysInstanceofLevel], sysLevel=[sysLevelIndex], pduLspId=[pduLspId], ThresholdValue=[ThresholdValue])

The LSP sequence number exceeded the upper alarm threshold.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.24.2.4.14 Major communicationsAlarm(2)

Parameters

Name Meaning

OID

Indicates the MIB object ID of the alarm.

sysInstance

Indicates the IS-IS instance ID.

sysInstanceofLevel

Indicates the IS-IS System level.

SysLevel

Indicates the IS-IS level.

pduLspId

Indicates the IS-IS System ID.

ThresholdValue

Upper alarm threshold.

Impact on the System

If the sequence number of LSP has reached 0xFFFFFFFF more than 3 times, the IS-IS instance will directly enters the hibernation state.

Possible Causes

Cause 1: An attacker simulated a locally generated LSP, set its sequence number to a value that is greater than the upper alarm threshold, and sent the LSP to the local device.

Cause 2: Another device on the network had the same IS-IS System ID as the local one.

Procedure

  1. Run the display isis lsdb command to check the sequence numbers of locally generated LSPs.

    • If the sequence numbers increase as expected, no action is required.
    • If the sequence numbers increase too fast, go to Step 2.

  2. Run the timer lsp-refresh command in the IS-IS view to increase the LSP update interval and then run the display isis lsdb command to check the sequence numbers of locally generated LSPs.

    • If the sequence numbers increase as expected, go to Step 5.
    • If the sequence numbers increase too fast, go to Step 3.

  3. Check whether there is another device on the network with the local IS-IS System ID.

    • If such a device exists, change its system ID.
    • If no such a device exists, go to Step 4.

  4. Collect alarm information and configuration information, and then contact technical support personnel.
  5. End.
Translation
Download
Updated: 2019-03-06

Document ID: EDOC1100041475

Views: 69703

Downloads: 45

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