ISIS_1.3.6.1.3.37.2.0.4 isisAttemptToExceedMaxSequence

Trap Buffer Description

The LSP sequence number has reached the maximum value. (SysInstance=[isisSysInstance], SysLevel=[isisSysLevelIndex], LspId=[isisPduLspId])

The LSP sequence number exceeds the maximum value. After the sequence number of an IS-IS LSP exceeds the upper threshold of 0xFFFFFFFF, this alarm is generated. After the sequence number of an IS-IS LSP falls below the upper threshold, this alarm is cleared.

Trap Attributes

Trap Attribute Description

Alarm or Event

Alarm

Trap Severity

Alert

Mnemonic Code

isisLspSeqMaxReach

Trap OID

1.3.6.1.3.37.2.0.4

MIB

ISIS-MIB

Alarm ID

0x00F10096

Alarm Name

isisLspSeqMaxReach

Alarm Type

communicationsAlarm

Raise or Clear

Raise

Match trap

ISIS_1.3.6.1.4.1.2011.5.25.24.2.4.16 hwIsisAttemptToExceedMaxSequenceClear

Trap Buffer Parameters

Parameter Description

isisSysInstance

Indicates the IS-IS process ID.

isisSysLevelIndex

Indicates the IS-IS level:

  • 1: Level-1
  • 2: Level-2

isisPduLspId

Indicates the LSP ID.

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.10.1.1.1

isisPduLspId

isisSysInstance

Impact on the System

If the LSP sequence number exceeds the upper threshold of 0xFFFFFFFF for more than three times, the IS-IS instance system enters the sleep mode and stops sending or receiving IS-IS packets.

Possible Causes

The sequence number of the LSP generated locally reached the maximum value 0xFFFFFFFF.

Procedure

1. After the LSP with the sequence number being 0xFFFFFFFF ages, the sequence number of the LSP starts from 1 again. You can run the display isis lsdb local command to view the sequence number of the LSP generated by the local device. Field.

  • If the sequence number matches the configured update time, this log message is informational only, and no action is required.
  • If the sequence number increases quickly, go to step 2.

2. Check whether the system ID of another device in the domain is the same as the system ID or virtual system ID of the local device.

  • If yes, go to step 3.
  • If no, go to Step 4.

3. (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. Run the undo network-entity or undo virtual-system command to delete the duplicate system ID or virtual system ID, run the network-entity or undo virtual-system command to configure a different system ID or virtual system ID for the device.Check whether the alarm is cleared.

  • If yes, go to step 5.
  • If no, go to Step 4.

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

5. End.

Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >