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 (CloudEngine 16800, 12800, and 12800E Series Switches)

Troubleshooting Procedure (CloudEngine 16800, 12800, and 12800E Series Switches)

Context

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 WRED drop profile is configured on an interface or in a queue on the interface.

    Run the display this command in the interface view to check whether the qos queue wred command is used.

    • If not, run the qos queue wred command to configure a WRED drop profile in a queue.

    • If so, go to step 2.

  2. Check whether parameters are set correctly in the WRED drop profile.

    Run the display drop-profile command to check whether parameters are set correctly in the WRED drop profile.

    • If parameters are not set, run the color command to set parameters.
    • If parameters are set and the qos queue wred command is used on the interface, go to step 3.

  3. Check whether packets enter the queue configured with the WRED drop profile.

    Run the display qos queue statistics command to check whether there are packet statistics about the queue configured with the WRED drop profile.

    • If there are packet statistics about the queue configured with the WRED drop profile, go to step 4.
    • If there are no packet statistics about the queue configured with the WRED drop profile, packets do not enter the queue configured with the WRED drop profile. Locate the fault according to Packets Enter Incorrect Queues.

  4. Check whether packets are colored by using priority mapping or a traffic action on an interface.

    Run the display this command in the interface view to check whether the traffic-policy command is used. If the traffic-policy command is used, run the display traffic policy command to view the actions in the traffic policy. Check whether car with service-class specified or remark local-precedence is configured.

    • If car is configured but service-class is not specified, run the car command with service-class specified in the traffic behavior view.
    • If remark local-precedence is configured but color is not specified, run the remark local-precedence command with color specified.
    • If car or remark local-precedence is configured and relevant coloring parameters are configured, the system colors packets according to the configuration. Go to step 5.
    • If the action and relevant parameters are not configured, go to step 5.

  5. Check whether packets are colored by using priority mapping or a traffic action in a VLAN.

    Run the display this command in the VLAN view to check whether the following configurations are performed in the VLAN.

    1. Check whether the dei enable command is used in the VLAN.

      • If so, verify that the system correctly marks packets with colors based on the CFI field (if the CFI field is 1, packets are colored yellow; if the CFI field is 0, packets are colored green). Then, go to step 5.
      • If not, go to step b.

    2. Check whether the trust upstream command is used in the VLAN.

      If the trust upstream command is used in the VLAN, the system colors packets according to the mapping from packet priorities to colors in the DiffServ domain. If the trust upstream command is not used on the interface, the system trusts the DiffServ domain default by default, and colors packets according to the mapping from packet priorities to colors in the DiffServ domain default. Run the display diffserv domain ds-domain-name command to check whether the mapping from packet priorities to colors is correct.

      • If the mapping is incorrect, run the 8021p-inbound, mpls-exp inbound, or ip-dscp-inbound command to modify the mapping from packet priorities to colors.
      • If the mapping is correct, go to step 6.

  6. Collect the following information and contact technical support personnel:

    • Results of the preceding troubleshooting procedure
    • Configuration file, logs, and alarms of the device

Translation
Download
Updated: 2020-01-07

Document ID: EDOC1000060766

Views: 617109

Downloads: 2967

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next