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/2/isisAdjacencyChange_active

ISIS/2/isisAdjacencyChange_active

Message

ISIS/2/isisAdjacencyChange_clear: ISIS adjacency state restore. (SysInstance=[IsisSysInstance], SysLevel=[IsisSysLevelIndex], CircIndex=[IsisCircIndex], CircIfIndex=[IsisCircIfIndex], LspId=[IsisPduLspId], AdjState=[IsisAdjState], IfIndex=[IfIndex], IfName=[IfName], Reason=[HwIsisAdjChgReason], SubReason=[HwIsisAdjChgSubReason])

Description

IS-IS neighbor relationship status changed.

Parameters

Parameter Name Parameter Meaning

SysInstance

IS-IS process ID

SysLevel

IS-IS neighbor type

CircIndex

IS-IS interface index

CircIfIndex

Interface index

LspId

System ID of the IS-IS neighbor

AdjState

Neighbor relationship status

IfIndex

Interface index

IfName

Interface name

Reason

Causes for the alarm

SubReason

Specific cause for the change in the IS-IS neighbor relationship

Possible Causes

Cause 1: The adjacency HoldTimer expired.

Cause 2: The physical interface went Down.

Cause 3: Protocol reason.

Cause 4: BFD detected that the neighbor went Down.

Cause 5: Configurations changed.

Cause 6: Peer router reason.

Cause 100: The alarm was cleared.

Procedure

  • Cause 1: The adjacency HoldTimer expired.
    1. Run the ping command to check whether two link ends are properly connected.

      • If the ping succeeds, go to Step 2.
      • If the ping fails, go to Step 4.

    2. Run the display this in the IS-IS view and in the interface view of the remote end to check whether IS-IS is correctly configured.

      • If IS-IS is correctly configured, go to Step 3.
      • If IS-IS is not correctly configured, go to Step 5.

    3. Run the display cpu command to check whether the CPU usage is too high.

      • If the CPU usage is too high, go to Step 5.
      • If the CPU usage is normal, go to Step 6.

    4. Run the display this command in the interface view to check whether the link between two ends is correctly configured. If the link is configured incorrectly, correct the configurations. Then run the display isis peer command to check whether the status of the IS-IS neighbor relationship between two ends is Up.

      • If IS-IS neighbor relationship status is Down, go to Step 5.
      • If IS-IS neighbor relationship status is Up, no action is required.

    5. Run the display current-configuration command in the system view to check configurations of two ends. If the two ends are incorrectly configured, correct the configurations. Then run the display isis peer command to check whether the status of the IS-IS neighbor relationship between two ends is Up.

      • If IS-IS neighbor relationship status is Down, go to Step 6.
      • If IS-IS neighbor relationship status is Up, no action is required.

    6. Collect log messages and contact technical support personnel technical support personnel.
  • Cause 2: The physical interface went Down.
    1. Run the display isis interface command or the display interface brief command to check whether interface status is Down.

      • If interface status remains Down, go to Step 2.
      • If interface status is Up, go to Step 3.

    2. Change configurations and then check whether interface status changes to Up.

      • If interface status is Up, go to Step 3.
      • If interface status remains Down, go to Step 4.

    3. Run the display isis peer command to check whether IS-IS neighbor relationship status is Up.

      • If IS-IS neighbor relationship status is Down, go to Step 4.
      • If IS-IS neighbor relationship status is Up, no action is required.

    4. Collect log messages and contact technical support personnel technical support personnel.
  • Cause 3: Protocol reason.
    1. Run the display memory command to check whether the CPU usage is too high.

      • If the CPU usage is normal, go to Step 2.
      • If the CPU usage is too high, no action is required.

    2. Collect log messages and contact technical support personnel technical support personnel.
  • Cause 4: BFD detected that the neighbor went Down.
    1. Run the ping command to check whether two link ends are properly connected.

      • If the ping succeeds, go to Step 3.
      • If the ping fails, go to Step 2.

    2. Run the display this command in the interface view to check whether the link between two ends is correctly configured. If the link is configured incorrectly, correct the configurations. Then run the display isis peer command to check whether the status of the IS-IS neighbor relationship between two ends is Up.

      • If IS-IS neighbor relationship status is Down, go to Step 3.
      • If IS-IS neighbor relationship status is Up, no action is required.

    3. Collect log messages and contact technical support personnel technical support personnel.
  • Cause 5: Configurations changed.
    1. Check whether some recently changed configurations affect the establishment of the IS-IS neighbor relationship.

      • If there are some configurations affecting the establishment of the IS-IS neighbor relationship, go to Step 2.
      • If there is no configuration affecting the establishment of the IS-IS neighbor relationship, go to Step 4.

    2. Check whether changed configurations meet users' requirements.

      • If the changed configurations meet users' requirements, no action is required.
      • If the changed configurations do not meet users' requirements, go to Step 3.

    3. Restore the original configurations and then check whether IS-IS neighbor relationship status is Up.

      • If IS-IS neighbor relationship status is Down, go to Step 4.
      • If IS-IS neighbor relationship status is Up, no action is required.

    4. Collect log messages and contact technical support personnel technical support personnel.
  • Cause 6: Peer router reason.
    1. Check whether the remote end is configured correctly.

      • If the configuration of the remote end is incorrect, go to Step 2.
      • If the configuration of the remote end is correct, go to Step 3.

    2. Correct the configuration of the remote end and then check whether IS-IS neighbor relationship status is Up.

      • If IS-IS neighbor relationship status is Down, go to Step 3.
      • If IS-IS neighbor relationship status is Up, no action is required.

    3. Collect log messages and contact technical support personnel technical support personnel.
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100039602

Views: 121575

Downloads: 90

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