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

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/ISIS_RCV_OWN_PURGED_LSP

ISIS/6/ISIS_RCV_OWN_PURGED_LSP

Message

ISIS/6/ISIS_RCV_OWN_PURGED_LSP:ISIS [ProcessId] received an own purged LSP. (Level=[Level], PduLspId=[PduLspId], Interface=[Interface], NbrSystem=[NbrSystem], SrcSystem=[SrcSystem], SrcDynName=[SrcDynName], SrcNbrSystem=[SrcNbrSystem])

Description

The IS-IS system received an LSP with Remaining Time 0 (purged LSP) from another system, and the LSP was locally generated.

Parameters

Parameter Name Parameter Meaning

ProcessId

Indicates the IS-IS process ID.

Level

Indicates the IS-IS level.

PduLspId

Indicates the ID of the purged LSP.

Interface

Indicates the interface that receives the purged LSP.

NbrSystem

Indicates the system ID of a neighbor.

SrcSystem

Indicates the system ID of the device that sends the purged LSP.

SrcDynName

Indicates the dynamic hostname of the device that sends the purged LSP.

SrcNbrSystem

Indicates the neighbor system ID of the device that sends the purged LSP.

Possible Causes

  • Cause 1: The local device did not update local LSPs in time. As a result, a locally generated LSP aged and was flooded back.

  • Cause 2: The LSP was modified because of a failure, such as a transmission failure. As a result, the LSP became a purged LSP.

  • Cause 3: The local device restarted, or the IS-IS process was reset. As a result, the local device received the purged LSP that was locally generated.

Procedure

  1. Check whether the device restarted.

    • If the device restarted, this log message is informational only and no action is required.
    • If the device did not restart, go to Step 2.

  2. Check whether SrcSystem is available in the log.

    • If SrcSystem is available, check the system ID of the device that sends the purged LSP and go to Step 4.
    • If SrcSystem is unavailable, go to Step 3.

  3. Check NbrSystem in the log, download the log from the neighbor, and check whether the purged LSP was sent by the neighbor.

    • If the purged LPS was sent by the neighbor, go to Step 4.
    • If the purged LPS was not sent by the neighbor, go to Step 5.

  4. Check whether the purged LSP has been deleted from the device that sent it.

    • If the purged LSP has been deleted from the device that sent it, this log message is informational only and no action is required.
    • If the purged LSP has not been deleted from the device that sent it, go to Step 5.

  5. Locate the device that sends the purged LSP and go to Step 4.
  6. Contact technical support personnel technical support personnel.
  7. End.
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100039602

Views: 118955

Downloads: 85

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