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

Troubleshooting Guide

CloudEngine 16800, 12800, 12800E, 8800, 7800, 6800, and 5800 Series Switches

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).
Troubleshooting Procedure

Troubleshooting Procedure

After commands are configured to troubleshoot faults, pay attention to the configuration validation mode to ensure that the configurations take effect. Unless otherwise specified, this manual defaults to the two-phase validation mode.

  • In immediate validation mode, the configuration takes effect immediately after you run a command and press Enter.
  • In two-phase validation mode, you must run the commit command after commands are configured to commit the configuration.

Save the results of each troubleshooting step, so you can provide related information to Huawei technical support if your troubleshooting fails.

Procedure

  1. Check the TRILL interface state.

    Run the display trill interface [ interface-type interface-number ] command to check State of the TRILL interface.

    • If Mtu:Up/Lnk:Dn is displayed, go to Step 2.

    • If Mtu:Dn/Lnk:Up is displayed, go to Step 2.

    • If Mtu:Up/Lnk:Up is displayed, run the display trill interface verbose command to check Circuit State of the interface.
      • If Down (CarrierVlan:Dn / Bandwidth:UP / TrillEnable:UP / MAC:Up) is displayed, run the display current-configuration configuration trill command to check whether a carrier VLAN is configured. If no carrier VLAN is configured, configure one and run the display trill interface verbose command to check whether Circuit State is Up. If Circuit State is not Up, go to Step 8.
      • If Down (CarrierVlan:UP / Bandwidth:Dn / TrillEnable:UP / MAC:Up) is displayed, go to Step 2.
      • If Down (CarrierVlan:UP / Bandwidth:Up / TrillEnable:Dn / MAC:Up) is displayed, check whether TRILL is enabled on the interface. If TRILL is not enabled on the interface, run the trill enable command to enable it. If TRILL is enabled, go to Step 8.
      • If Down (CarrierVlan:UP / Bandwidth:Up / TrillEnable:Up / MAC:Dn) is displayed, go to Step 2.
    • If UP is displayed, go to Step 3.

  2. Check whether the interface is Up physically.

    Run the display interface [ interface-type [ interface-number ] ] command to check the interface state.

    • If Line protocol current state is not Up, diagnose the fault so that it is Up.

    • If UP is displayed, go to Step 3.

  3. Check whether TRILL receives and sends Hello packets properly.

    Run the display trill statistics packet [ interface interface-type interface-number ] command to check whether TRILL receives and sends Hello packets properly.

    By default, Hello packets are sent at an interval of 10s. Run the command each 10s and check whether the packet statistics increase.

    • If the statistics about received and sent packets remain unchanged, check whether there are discarded TRILL packets. Run the debugging trill adjacency [ interface interface-type interface-number ] command to check whether the interface receives and sends packets properly.
      • If TRILL-ADJ: Sending Lan Level-1 IIH. (IfName=XXXX, LocalSnpa=XXXX) is displayed, the interface sends packets properly. If TRILL-ADJ: Sending Lan Level-1 IIH. (IfName=XXXX, LocalSnpa=XXXX) is not displayed, go to Step 8.
      • If TRILL-ADJ: Received Lan Level-1 IIH. (IfName=XXXX, RemoteSnpa=XXXX) is displayed, the interface receives packets properly. If TRILL-ADJ: Received Lan Level-1 IIH. (IfName=XXXX, RemoteSnpa=XXXX) is not displayed, go to Step 8.
    • If the interface receives Hello packets properly, go to Step 4.

  4. Check whether the carrier VLANs at the two ends of the link are the same.

    Run the display current-configuration configuration trill command at both ends to check whether the carrier VLANs at the two ends are the same.

    • If the carrier VLANs at the two ends are different, run the carrier-vlan carrier-vlanid command to modify either carrier VLAN so that the carrier VLANs at the two ends are the same.

    • If the carrier VLANs at the two ends are the same, go to Step 5.

  5. Check whether the types of the TRILL interfaces at the two ends of the link are the same.

    Run the display trill interface interface-type interface-number command at both ends to check whether Port Type values at the two ends are the same.

    If access, hybrid, or trunk is displayed at one end and P2P is displayed at the other end, the neighbor relationship cannot be established. A TRILL neighbor relationship can be established only when the interfaces at the two ends are both P2P or non-P2P interfaces.

    • If the types of the interfaces at the two ends are different, run the trill enable port-mode { access | hybrid | P2P | trunk } command to modify the type of either interface so that the types of the interfaces at the two ends are the same.

    • If the types of the interfaces at the two ends are the same, go to Step 6.

  6. Check whether the authentication configurations at the two ends of the link are the same.

    Run the display current-configuration interface interface-type interface-number | include "trill authentication-mode" command on each end to check the authentication configurations.

    • If the authentication modes at the two ends are different, run the trill authentication-mode command in the TRILL interface view to modify the authentication mode of either end so that the authentication modes at the two ends are the same.

    • If the authentication passwords at the two ends are different, run the trill authentication-mode command in the TRILL interface view to modify the authentication password of either end so that the authentication passwords at the two ends are the same.

    • If the authentication configurations at the two ends of the link are the same, go to Step 7.

  7. Check whether designated VLANs of the TRILL interfaces at the two ends of the link are the same.

    Run the display trill interface [ interface-type interface-number ] command to check the designated VLAN of the interface at each end. If the types of interfaces at the two ends are both P2P, the designated VLANs at the two ends must be the same. If the types of interfaces at the two ends are not P2P, the designated VLAN of the DRB must be configured as a carrier VLAN at the other end.

    • If designated VLANs at the two ends of the link are different, run the trill designated-vlan vlan-id command to modify either designated VLAN so that designated VLANs at the two ends of the link are the same.
    • If the types of interfaces at the two ends are not P2P and the designated VLAN of the DRB is not configured as a carrier VLAN at the other end, run the carrier-vlan carrier-vlanid command in the TRILL view on the other end to configure the designated VLAN of the DRB as a carrier VLAN.
    • If designated VLANs of the TRILL interfaces at the two ends of the link are the same but the neighbor relationship still cannot be established, go to Step 8.
  8. Collect the following information and contact technical support personnel.

    • Results of the preceding troubleshooting procedure
    • Configuration files, logs, and alarms of the devices

Translation
Download
Updated: 2020-01-07

Document ID: EDOC1000060766

Views: 617085

Downloads: 2967

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next