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 switch, 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 switch was the same as that of another switch. This caused the LSP to be updated continuously.

Procedure

Run the display history-command command to check whether the reset isis all command is run on the local switch 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.
Run the display isis lsdb command to continuously check whether the LSP sequence number of the local switch 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.
Run the display current-configuration command to check whether there is another switch whose system ID or virtual system ID is the same as that of the local switch on the network.
- If so, go to Step 4.
- If not, go to Step 5.
Enter the IS-IS view of the local switch or another switch whose system ID is the same as the system ID or the virtual System ID of the local switch. 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 switch. 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.
Collect the trap information, log information, and configuration of the switch, and contact technical support personnel.
End.

Related Information

None