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).
TRILL/4/TRILL_ADJ_CHANGE

TRILL/4/TRILL_ADJ_CHANGE

Message

TRILL/4/TRILL_ADJ_CHANGE: TRILL-INFO: TRILL adjacency state change. (IfName=[IfName], AdjLevel=[AdjLevel], NbrSysId=[NbrSysId], AdjState=[AdjState], AddressFamily=[AddressFamily], Reason=[Reason])

Description

The TRILL neighbor status changed.

Parameters

Parameter Name Parameter Meaning

IfName

Name of the neighbor interface

AdjLevel

Level of the neighbor whose status changes

NbrSysId

System ID of the neighbor

AdjState

Status of the neighbor before change

AddressFamily

Address family of the neighbor

Reason

Possible causes of the neighbor status change

Possible Causes

Cause 1: The neighbor holdtime expired.

Cause 2: The neighbor interface went down.

Cause 3: A protocol error occurred.

Cause 4: Configurations changed.

Cause 5: An error occurred on the remote switch.

Procedure

  1. Check the hexadecimal value in the NbrSysId field. The value indicates the system ID of the source switch. Check whether the neighbor status at both ends is the same.

    • If the neighbor status at both ends is the same, go to step 12.

    • If the neighbor status at both ends is different, go to step 2.

  2. Check whether the interface went down and check whether it is the cause of the neighbor status change in the source switch logs.

    • If the interface going Down is the cause of the neighbor status change, go to step 3.

    • If the interface going Down is not the cause of the neighbor status change, go to step 9.

  3. Check the interface and MTU status on the local interface and ensure that the interface and MTU status at both ends are Up. Check whether the neighbor status at both ends is the same.

    • If the neighbor status at both ends is the same, go to step 12.

    • If the neighbor status at both ends is different, go to step 4.

  4. Check the system IDs and ensure that the system IDs at both ends are correct. If no system IDs are configured, check whether MAC addresses are correctly configured.

    • If the neighbor status at both ends is the same, go to step 12.

    • If the neighbor status at both ends is different, go to step 5.

  5. Check the Carrier VLANs at both ends are the same and ensure the designated VLANs at both ends are the same. Check whether the neighbor status at both ends is the same.

    • If the neighbor status at both ends is the same, go to step 12.

    • If the neighbor status at both ends is different, go to step 6.

  6. Check whether the TRILL interface types at both ends are the same, either P2P or Broadcast. Check whether the neighbor status at both ends is the same.

    • If the neighbor status at both ends is the same, go to step 12.

    • If the neighbor status at both ends is different, go to step 7.

  7. Check whether the authentication mode is configured at each end and ensure that the authentication mode and password at both ends are the same. If authentication is not necessary, disable it from both ends (disabling authentication degrades the system security). Check whether the neighbor status at both ends is the same.

    • If the neighbor status at both ends is the same, go to step 12.

    • If the neighbor status at both ends is different, go to step 8.

  8. Ensure interfaces at both ends can transmit Hello packets properly. Check whether the neighbor status at both ends is the same.

    • If the neighbor status at both ends is the same, go to step 12.

    • If the neighbor status at both ends is different, go to step 9.

  9. Run the display cpu command to check whether the CPU usage remains 100% within a period of time.

    • If the CPU usage remains 100% within a period of time, go to step 10.

    • If the CPU usage does not reach 100% within a period of time, go to step 11.

  10. Run the trill timer hello command in the interface view to set the interval at which the device sends Hello packets to a larger value, which increases by 10s each time. Prolonging the interval at which the device sends Hello packets slows down the network fault detection and route convergence. Check whether the neighbor status at both ends is the same.

    • If the neighbor status at both ends is the same, go to step 12.

    • If the neighbor status at both ends is different, go to step 11.

  11. Collect trap, log, and configuration information, and contact Huawei technical support personnel.
  12. End.
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100039602

Views: 119246

Downloads: 89

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