ISIS_1.3.6.1.3.37.2.0.8 isisSequenceNumberSkip

Trap Buffer Description

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])

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

Trap Attributes

Trap Attribute	Description
Alarm or Event	Event
Trap Severity	Critical
Mnemonic Code	ISIS_SEQUENCE_NUMBER_SKIP
Trap OID	1.3.6.1.3.37.2.0.8
MIB	ISIS-MIB
Alarm ID	This is an event trap and does not involve alarm ID.
Alarm Name	This is an event trap and does not involve alarm name.
Alarm Type	This is an event trap and does not involve alarm type.
Raise or Clear	This is an event trap and does not involve alarm generation or clearance.
Match trap	-

Trap Buffer Parameters

Parameter	Description
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.

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.3.37.1.1.1.1.1	isisSysInstance	isisSysInstance
1.3.6.1.3.37.1.2.1.1.1	isisSysLevelIndex	isisSysInstance isisSysLevelIndex
1.3.6.1.3.37.1.3.1.1.2	isisCircIfIndex	isisSysInstance isisCircIndex
1.3.6.1.3.37.1.10.1.1.1	isisPduLspId	isisSysInstance
1.3.6.1.2.1.31.1.1.1.1	ifName	ifIndex

Impact on the System

1. You can ignore the trap caused by the restart of the local device, and services will not be affected.

2. If the trap is triggered by the incorrect configuration, routes will flap frequently.

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.