No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Alarm Handling

AR100, AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R010

This document provides the trap description, attributes, parameters, impact on the system, possible causes, procedures, and references. This document provides a complete set of traps, through which intended readers are kept of the running status of the device so as to locate faults.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
ISIS-STD_1.3.6.1.2.1.138.0.8 isisSequenceNumberSkip

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 router, 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 router was the same as that of another router, 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 router 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 router 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 router is the same as that of the local router.

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

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

  4. Run the undo network-entity or undo virtual-system command in the IS-IS view of the local router or other router devices that have the same system ID or virtual system ID with the local router 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 router. 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

Translation
Download
Updated: 2019-05-07

Document ID: EDOC1100034065

Views: 131725

Downloads: 40

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next