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 whether the TRILL neighbor relationship is established.

    Run the display trill peer [ interface interface-type interface-number ] [ verbose ] command to check whether the TRILL neighbor relationship is established.

  2. Check whether the authentication configurations at the two ends are the same.

    Run the display current-configuration configuration trill | include area-authentication-mode command on each end to check the authentication configurations.

    • If the authentication modes at the two ends are different, run the area-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 area-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 3.

  3. Check whether nicknames conflict on the network.

    Run the display trill nickname command to check whether nicknames conflict on the network.

    • If nicknames conflict on the network (S/S or S/D is displayed in State), run the nickname nicknamevalue [ priority priorityvalue ] [ root-priority rootpriorityvalue ] command in the TRILL view on the device whose nickname has been suppressed to modify the nickname so that there are no nickname conflicts on the network.

    • If there are no nickname conflicts on the network, go to Step 4.

  4. Check whether the CE VLAN is configured.

    Run the display current-configuration configuration trill | include ce-vlan command to check whether the CE VLAN is configured.

    • If the CE VLAN is not configured, run the ce-vlan { vlan-id1 [ to vlan-id2 ] } & <1-10> command in the TRILL view to configure it.

    • If the CE VLAN has been configured, run the display vlan command to check whether the configured CE VLAN is established. If the configured CE VLAN is not established, run the vlan command to establish the VLAN. If the configured CE VLAN is already established, go to Step 5.

  5. Check whether the interface that is added to the CE VLAN is Up.

    Run the display interface [ interface-type interface-number ] command to check Line protocol current state of the interface that is added to the CE VLAN.

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

    • If Line protocol current state is Up, go to Step 6.

  6. Check whether TRILL LSDBs are synchronous on the network.

    Run the display trill lsdb command on each device to check whether TRILL LSDBs are synchronous on the network.

    • If TRILL LSDBs are asynchronous on the network, run the reset trill all command to reset TRILL.

    • If TRILL LSDBs are synchronous on the network, go to Step 7.

  7. 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: 609104

Downloads: 2951

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next