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-S, AR110-S, AR120-S, AR150-S, AR160-S, AR200-S, AR1200-S, AR2200-S, and AR3200-S V200R009

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.3.37.2.0.8 isisSequenceNumberSkip

ISIS_1.3.6.1.3.37.2.0.8 isisSequenceNumberSkip

Description

ISIS/2/SEQNUM_SKIP:OID [oid] ISIS received a self-originated LSP with a greater sequence number. (sysInstance=[integer], sysInstanceofLevel=[integer], sysLevel=[integer], sysInstanceofCircIfIndex=[integer], circIndex=[integer], ifIndex=[integer], circIfIndex=[integer], pduLspId=[opaque], ifName=[string])

The sequence number of the local IS-IS LSP irregularly increases.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.3.37.2.0.8

Major

other(1)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

sysInstance

Indicates the ID of the IS-IS process.

sysInstanceofLevel

Indicates the ID of the IS-IS process.

sysLevel

Indicates the IS-IS level:
  • 1: Level-1

  • 2: Level-2

sysInstanceofCircIfIndex

Indicates the ID of the IS-IS process.

circIndex

Indicates the index of the interface.

ifIndex

Indicates the index of the interface.

circIfIndex

Indicates the IF index of the interface.

pduLspId

Indicates the ID of the LSP.

ifName

Indicates the name of the interface.

Impact on the System

1. You can ignore the trap caused by the restart of the local router, and services will not be affected.

2. If the trap is triggered by the incorrect configuration, routes will flap frequently.

Possible Causes

1. After the IS-IS process was restarted, IS-IS received the LSP with the greater sequence number and the same LSP ID from the neighbor.

2. The system ID of the local router was the same as that of another router. This caused the LSP to be updated continuously.

Procedure

  1. Run the display history-command command to check whether the reset isis all command is run on the local router to restart the IS-IS process.

    • If so, it indicates that this trap message is informational only, and no action is required, go to Step 6.

    • If not, go to Step 2.

  2. Run the display isis lsdb command to continuously check whether the LSP sequence number of the local router increases rapidly, that is, to check whether the actual LSP refresh period is shorter than the value configured through the timer lsp-refresh command.

    • If so, go to Step 3.

    • If not, go to Step 5.

  3. Run the display current-configuration command to check whether there is another router whose system ID or virtual system ID is the same as that of the local router on the network.

    • If so, go to Step 4.

    • If not, go to Step 5.

  4. Enter the IS-IS view of the local router or another router whose system ID is the same as the system ID or the virtual System ID of the local router. Then run the undo network-entity command or the undo virtual-system command to delete the repeated system ID or virtual system ID and the network-entity command or the virtual-system command to configure a different system ID or virtual system ID for the router. Check whether the trap is cleared. If the undo network-entity or undo virtual-system command is run, the conflicting system ID or virtual system ID becomes unavailable. Therefore, make sure that the system ID or virtual system ID conflict exists before you run the undo network-entity or undo virtual-system command.

    • If so, go to Step 6.

    • If not, go to Step 5.

  5. Collect the trap information, log information, and configuration of the router, and contact technical support personnel.
  6. End.

Related Information

None

Translation
Download
Updated: 2019-05-06

Document ID: EDOC1000174085

Views: 118922

Downloads: 20

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