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


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


Alarm Handling

AR100, AR120, AR160, AR1200, AR2200, AR3200, and AR3600 V300R003

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

ISIS-STD_1. isisOwnLSPPurge


ISIS-STD/2/OWNLSP_PURGE:OID [oid] ISIS received a self-originated LSP with the age being 0. (NotificationSysLevelIndex=[integer], CircuitIfIndex=[integer], PduLspId=[opaque])

IS-IS received an LSP with the same system ID as that of the device and the lifetime of 0.


Alarm ID Alarm Severity Alarm Type




Name Meaning


Indicates the MIB object ID of the alarm.


IS-IS level of a device that sends the trap


Interface index



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 generated frequently, IS-IS routes will be affected and traffic forwarding may fail.

Possible Causes

Cause 1: The local router did not refresh LSPs in time. As a result, purge packets were generated after these LSPs aged out and flooded to the local router.

Cause 2: Packets were changed due to a transmission failure and purge packets were generated.

Cause 3: After the local router restarted, it received an LSP with the same system ID as that of the local router the lifetime of 0.


  1. Check whether the local router restarts.

    • If the local router restarts, this trap message is informational only, and no action is required, go to Step 4.

    • If the local router does not restart, go to Step 2.

  2. Check whether the IS-IS authentication configuration is changed on the router.

    • If the IS-IS authentication configuration is changed, this trap message is informational only, and no action is required, go to Step 4.

    • If the IS-IS authentication configuration is not changed, go to Step 3.

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

Related Information


Updated: 2019-03-06

Document ID: EDOC1100041475

Views: 100773

Downloads: 61

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next