ISIS-STD_1.3.6.1.2.1.138.0.8 isisSequenceNumberSkip

Description

ISIS-STD/2/SEQNUM_SKIP:OID [oid] ISIS received a self-originated LSP with a greater sequence number. (NotificationSysLevelIndex=[integer], CircIfIndex=[integer], PduLspId=[opaque])

When local LSPs were refreshed, the sequence numbers of the LSPs increased irregularly.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.2.1.138.0.8

Major

other(1)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

NotificationSysLevelIndex

IS-IS level of a device that sends the trap

CircIfIndex

Interface index

PduLspId

LSP ID

Impact on the System

1. If the trap is triggered by the restart of the wireless access controller, services will not be affected.

2. If the trap is triggered by incorrect configurations, route flapping will occur frequently.

Possible Causes

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

Cause 2: The system ID of the local wireless access controller was the same as that of another wireless access controller, causing the LSPs to be frequently refreshed.

Procedure

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

    • If the reset isis all command is run to restart an IS-IS process, go to Step 6.

    • If the reset isis all command is not run to restart an IS-IS process, go to Step 2.

  2. Run the display isis lsdb command on the local wireless access controller to continuously check whether the LSP sequence number increases rapidly, that is, whether the actual LSP refreshing period is smaller than that set using the timer lsp-refresh command.

    • If the LSP sequence number increases rapidly, go to Step 3.

    • If the LSP sequence number does not increase rapidly, go to Step 5.

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

    • If the system ID or virtual system ID of another wireless access controller is the same as that of the local wireless access controller, go to Step 4.

    • If the system ID or virtual system ID of another wireless access controller is different from that of the local wireless access controller, go to Step 5.

  4. Run the undo network-entity or undo virtual-system command in the IS-IS view of the local wireless access controller or other wireless access controller devices that have the same system ID or virtual system ID with the local wireless access controller to delete the system ID or virtual system ID. Run the network-entity or virtual-system command to configure a new system ID or virtual system ID for the wireless access controller. 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 the trap is cleared, go to Step 6.

    • If the trap is not cleared, go to Step 5.

  5. Collect alarm information and configuration information, and then contact technical support personnel.
  6. End.

Related Information

None

Parent Topic: ISIS
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >