ISIS/6/ISIS_LSP_SEQ_SKIP

Message

ISIS/6/ISIS_LSP_SEQ_SKIP:ISIS modifid self-originated LSP sequence number with received [STRING]. (ProcessId=[USHORT], Level=[USHORT], LspId=[STRING], LocalSeqnum=[ULONG], ReceivedSeqNum=[ULONG], NewSeqNum=[ULONG])

Description

IS-IS modified the sequence number of a self-originated LSP after it received a [UDP]. (ProcessId=[USHORT],Level=[USHORT],LspId=[STRING],LocalSeqnum=[ULONG],ReceivedSeqNum=[ULONG],NewSeqNum=[ULONG])

Parameters

Parameter Name	Parameter Meaning
PDU	Received packet
ProcessId	ID of an IS-IS process
Level	Level of an LSP
LspId	ID of the LSP
LocalSeqnum	Sequence number of the local LSP
ReceivedSeqNum	Sequence number of the received packet
NewSeqNum	New sequence number of the LSP

Possible Causes

1. After the IS-IS process restarted, the sequence number increased from one. IS-IS received an LSP whose ID was the same as that of a local LSP, but the sequence number of the received LSP was larger than that of the local one.

2. A system ID conflict existed on the network. As a result, LSPs were updated frequently.

Procedure

Run the display history-command command to check whether the IS-IS process was restarted on the local switch using the reset isis all command.
- If the IS-IS process was restarted, this log message is informational only, and no action is required.
- If the IS-IS process was not restarted, go to Step 2.
Run the display isis lsdb command repeatedly to check whether the sequence numbers of LSPs on the local switch increase abnormally fast. Specifically, check whether the LSP update interval is less than that configured using the timer lsp-refresh command.
- If the LSP update interval is less than the configured one, go to Step 3.
- If the LSP update interval is not less than the configured one, go to Step 5.
Run the display current-configuration command to check whether another switch has the same system ID or virtual system ID as that of the local switch.
- If a system ID or virtual system ID conflict exists, go to Step 4.
- If no system ID or virtual system ID conflict exists, go to Step 5.
Enter the IS-IS view of the local switch or the switch whose system ID or virtual system ID is the same as that of the local switch, run the undo network-entity command to delete the conflicting system ID or run the undo virtual-system command to delete the conflicting virtual system ID, and then run the network-entity command to configure a different system ID or run the virtual-system command to configure a different virtual system ID. Then, check whether the problem is resolved. 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 the problem is resolved, go to Step 6.
- If the problem persists, go to Step 5.
Collect log information and configuration information, and then contact technical support personnel.
End.