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).
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

The LSP sequence number has exceeded the upper threshold value. (SysInstance=[isisSysInstance], SysLevel=[isisSysLevelIndex], LspId=[isisPduLspId], ThresholdValue=0x[thresholdVal])

The LSP sequence number exceeded the upper alarm threshold.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

hwIsisSeqThresholdExceed

Trap OID

1.3.6.1.4.1.2011.5.25.24.2.4.14

Alarm ID

0x00F10097

Alarm Type

communicationsAlarm

Raise or Clear

Raise

Match trap

ISIS_1.3.6.1.4.1.2011.5.25.24.2.4.15 hwIsisSeqNumExceedThresholdClear

Parameters

Parameter Description

SysInstance

ID of an IS-IS process

SysLevel

IS-IS level

LspId

LSP ID

ThresholdValue

Upper alarm threshold

VB

VB OID

VB Name

VB Index

1.3.6.1.3.37.1.1.1.1.1

isisSysInstance

isisSysInstance

1.3.6.1.3.37.1.2.1.1.1

isisSysLevelIndex

isisSysInstance;

isisSysLevelIndex

1.3.6.1.3.37.1.10.1.1.1

isisPduLspId

isisSysInstance

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 the relevant information and contact technical support personnel technical support personnel.
  5. End.
Translation
Download
Updated: 2019-04-02

Document ID: EDOC1100074754

Views: 22450

Downloads: 30

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