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.


Log Reference

CloudEngine 8800, 7800, 6800, and 5800 V200R005C00

This document provides the explanations, causes, and recommended actions of logs on the product.

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/6/IS_PURGE_CALCULATE_DELAY_COUNT:ISIS-INFO: The statistics about the suppression times of the updated LSP of the IS that sent the non-pseudo node purge LSP with fragment number 0 were recorded. (InstanceId = [InstanceId], Level = [Level], SuppressedLocalPurgeCount = [LocalCount], SuppressedReceivePurgeCount = [RecCount], LogPeriod = [LogPeriod])


The number of times that purge LSP-triggered route calculations were delayed were recorded.


Parameter Name Parameter Meaning


ID of an IS-IS process


IS-IS Level


Number of times that local purge LSP-triggered route calculations are delayed


Number of times that received purge LSP-triggered route calculations are delayed


Interval at which logs are generated

Possible Causes

Purge LSP-triggered route calculations were delayed.


  1. Check whether either of the following inequalities is met:

    SuppressedLocalPurgeCount > 100

    SuppressedReceivePurgeCount > 100

    • If either of the preceding inequalities is met, go to Step 2.

    • If neither of the preceding inequalities is met, go to Step 4.

  2. Check whether a device or link failure exists on the network.

    • If a device or link failure exists, rectify the failure.

    • If no device or link failure exists, go to Step 3.

  3. Check whether the delay period configured using the timer purge-zero-lsp route-calculate-delay delay-interval command is too long. If it is too long, reduce it and check whether the problem is resolved.

    • If the problem persists, go to Step 5.

    • If the problem is resolved, go to Step 6.

  4. This log is informational only, and no action is required.
  5. Contact technical support personnel technical support personnel.
  6. End.
Updated: 2019-04-20

Document ID: EDOC1100039602

Views: 168854

Downloads: 110

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next