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


To have a better experience, please upgrade your IE browser.


Log Reference

CloudEngine 8800, 7800, 6800, and 5800 V200R005C00

This document provides the explanations, causes, and recommended actions of logs 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/2/ISIS_SEQUENCE_NUMBER_SKIP: ISIS received a self-originated LSP with a greater sequence number. (isisSysInstance=[isisSysInstance], isisSysLevelIndex=[isisSysLevelIndex], isisCircIndex=[isisCircIndex], isisCircIfIndex=[isisCircIfIndex], isisPduLspId=[isisPduLspId], ifIndex=[ifIndex], IfName=[IfName])


When local LSPs were refreshed, the sequence number increased irregularly.


Parameter Name Parameter Meaning


ID of an IS-IS process


IS-IS level


Circuit index of an interface


Circuit IfIndex of an interface




IfIndex of an interface


Interface name

Possible Causes

Cause 1: After an IS-IS process restarted, the sequence number increased from 1, and IS-IS received an LSP with a larger sequence number but the same LSP ID from the neighbor.

Cause 2: The system ID of the local was the same as that of another , causing the LSPs to be frequently refreshed.


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

    • If so, go to Step 5. In this case, this log message is informational only, and no action is required.

    • If not, go to Step 2.

  2. Run the display isis lsdb command on the local to check whether the LSP sequence number increases rapidly, that is, whether the actual refreshing period is smaller than that set by using the timer lsp-refresh command.

    • If so, go to Step 3.

    • If not, go to Step 4.

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

    • If so, go to Step 4.

    • If not, go to Step 5.

  4. Exercise caution when running the undo network-entity or undo virtual-system command. Run the undo network-entity or undo virtual-system command in the IS-IS view of the local or the that has the same system ID or virtual system ID to delete the system ID or virtual system ID. Run the network-entity or virtual-system command to configure a different system ID or virtual system ID on the . Check whether the fault is rectified.

    • If so, go to Step 6.

    • If not, go to Step 5.

  5. Contact technical support personnel technical support personnel.
  6. End.
Updated: 2019-04-20

Document ID: EDOC1100039602

Views: 179820

Downloads: 112

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next