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.4 isisAttemptToExceedMaxSequence

ISIS-STD_1.3.6.1.2.1.138.0.4 isisAttemptToExceedMaxSequence

Description

ISIS-STD/3/MAXSEQ_EXCEED:OID [oid] The LSP sequence number almost reaches the maximum value. (NotificationSysLevelIndex=[integer], PduLspId=[opaque])

The IS-IS LSP sequence number almost reached the maximum value.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.2.1.138.0.4

Minor

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

PduLspId

LSP ID

Impact on the System

After the LSP sequence number of an LSP reaches 0xFFFFFFFF, the IS-IS process will stop running for a period of time (the period equal the sum of the maximum lifetime of an LSP and the aging time of an LSP), causing IS-IS services to be interrupted.

Possible Causes

The sequence number of a locally generated LSP reached 0xFFFFFFFF.

Procedure

  1. If the trap is automatically cleared, no action is required. If the trap persists, after the sequence number of an LSP reaches 0xFFFFFFFF (it equals the maximum lifetime plus 60s, and the default maximum lifetime is 1200s), the sequence number of the LSP begins from 0 again. Run the display isis lsdb local command to view the sequence number of an LSP generated by the local router,

    • If the sequence number matches the configured update time, go to Step 5.

    • If the sequence number increases quickly, go to Step 2.

  2. Check whether the system IDs of other router devices in the domain are the same as the system ID or virtual system ID of the local router.

    • If the system IDs of other router devices in the domain are the same as the system ID or virtual system ID of the local router, go to Step 3.

    • If the system IDs of other router devices in the domain are different from the system ID or virtual system ID of the local router, go to Step 4.

  3. 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 trap is cleared, go to Step 5.

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

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

Related Information

None

Translation
Download
Updated: 2019-08-12

Document ID: EDOC1100034065

Views: 151255

Downloads: 42

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