ISIS/2/ISIS_SEQUENCE_NUMBER_SKIP

Message

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],oldSeqNum=[oldSeqNum],newSeqNum=[newSeqNum])

Description

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

Parameters

Parameter Name	Parameter Meaning
isisSysInstance	ID of an IS-IS process
isisSysLevelIndex	IS-IS level
isisCircIndex	Interface index
isisCircIfIndex	Interface index
isisPduLspId	LSP ID
ifIndex	IfIndex of an interface
IfName	Interface name
oldSeqNum	Old sequence number
newSeqNum	New sequence number

Possible Causes

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

Cause 2: The system ID of the device was the same as that of another device on the network. As a result, the LSP was continuously refreshed.

Procedure

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

If yes, this log message is informational only, and no action is required.
If not, go to Step 2.

2. Run the display isis lsdb command to check whether the LSP sequence number of the local device increases rapidly. That is, the actual LSP refresh interval is smaller than the LSP refresh interval set using the timer lsp-refresh command.

If yes, go to Step 3.
If no, go to Step 4.

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

If yes, go to Step 4.
If no, go to Step 5.

4. (Exercise caution when running the undo network-entity or undo virtual-system command.) Enter the IS-IS view of the local device or another device that has the same system ID or virtual system ID as the local device and run the undo network-entity or undo virtual-system command to delete the duplicate system ID or virtual system ID. Then, run the network-entity or virtual-system command to configure a different system ID or virtual system ID for the device. Check whether the fault is rectified.

If yes, go to Step 6.
If no, go to Step 5.

5. Collect log and configuration information, and contact Huawei technical support personnel.

6. End.