ISIS/2/isisLspSeqThresholdExceed_active

Message

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

Description

The LSP sequence number exceeds the specified upper threshold. After the sequence number of an IS-IS LSP exceeds a specified upper threshold, this alarm is generated. After the sequence number of an IS-IS LSP falls below a specified upper threshold, this alarm is cleared.

Parameters

Parameter Name	Parameter Meaning
isisSysInstance	Indicates the IS-IS process ID.
isisSysLevelIndex	Indicates the IS-IS level.
isisPduLspId	Indicates the LSP ID.
thresholdVal	The upper threshold value of LSP sequence Number

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 number of the LSP generated by the local device.

If the sequence number increases normally, this log message is informational only, and no action is required.
If the sequence number increases too fast, go to step 2.

2. Run the timer lsp-refresh command in the IS-IS view to increase the value of the LSP refresh timer, and then run the display isis lsdb command to view the sequence number of the LSP generated by the local device.

If the sequence number increases normally, go to step 5.
If the sequence number still increases too fast, go to step 3.

3. Check whether there is a device whose system ID conflicts with the local system ID in the domain.

If so, change the system ID of one of the conflicting devices.
If no, go to Step 4.

4. Collect alarm and configuration information, and contact technical support personnel.

5. End.