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

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 traffic shaping parameters of queues are set correctly.

    Run the display this command in the interface view to check whether the qos queue shaping command is used.
    • If traffic shaping parameters of queues are set incorrectly or not set, run the qos queue shaping command to set the parameters correctly.

    • If traffic shaping parameters of queues are set and the CIR value for traffic shaping on an interface is set by using the qos lr outbound command, go to step 2.
    • If traffic shaping parameters of queues are set but the CIR value for traffic shaping on an interface is not set, go to step 3.

  2. Check whether the CIR value for traffic shaping on an interface is greater than the sum of CIR values for traffic shaping in queues on the interface.

    Compare the CIR value for interface-based traffic shaping with the sum of CIR values of traffic shaping in queues on the interface:

    • If the CIR value of traffic shaping on an interface is smaller than the sum of CIR values of traffic shaping in queues on the interface, the bandwidth required by queues on the interface cannot be guaranteed. The traffic shaping result may be incorrect. In this case, run the qos lr outbound and qos queue shaping commands to modify related parameters so that the CIR value of traffic shaping on an interface is greater than the sum of CIR values of traffic shaping in queues on the interface.

    • If the CIR value for traffic shaping on an interface is greater than the sum of CIR values for traffic shaping in queues on the interface, go to step 3.

  3. Check whether traffic policing affecting queue shaping is configured.
    1. Check whether interface-based traffic policing is configured on the inbound interface.

      If interface-based traffic policing is configured on the inbound interface and its CIR value is smaller than the specified CIR value for queue shaping, queue shaping uses the CIR value for interface-based traffic policing.

      Run the display this command in the inbound interface view to check whether the qos car inbound command is run on the inbound interface and whether its CIR value is smaller than the CIR value for queue shaping.

      • If the qos car inbound command is used and the CIR value is smaller than the CIR value for queue shaping, disable interface-based traffic policing or modify the configuration so that the CIR value for interface-based traffic policing is greater than the CIR value for queue shaping.
      • If the qos lr inbound command is not run or this command is run but the CIR value of the inbound interface is greater than the CIR value for queue shaping, go to step b.

    2. Check whether class-based traffic policing is configured on the device.

      If class-based traffic policing is configured on the device, its CIR value is smaller than the CIR for queue shaping, and traffic in queues matches the traffic classifier, the CIR for class-based traffic policing is used as the actual CIR value of queue shaping.

      Run the display this command in the system view, inbound interface view, and VLAN view to check whether the traffic-policy command is used:

      • If the traffic-policy command is run, run the display traffic policy command to check whether a CIR value is defined in the traffic policy and whether the CIR value is smaller than the CIR value for queue shaping.

        • If the CIR value is set, run the display traffic policy command to check whether traffic in queues matches the traffic classifier in the configured traffic policy. If traffic in queues matches the traffic classifier, delete the CIR value defined in the traffic policy or modify the configuration so that the CIR value in the traffic policy is greater than the CIR value for queue shaping. If traffic in queues does not match the traffic classifier, go to step 4.
        • If no CIR value is set, go to step 4.
      • If the traffic-policy command is not run, go to step 4.

  4. Check whether packets enter traffic shaping queues.

    Run the display qos queue statistics interface interface-type interface-number command to view the packet statistics on each queue on the interface.

    • If packets do not enter traffic shaping queues, locate the fault according to Packets Enter Incorrect Queues.

    • If packets enter traffic shaping queues and many packets enter PQ queues, go to step 5.

    • If packets enter traffic shaping queues and many packets do not enter PQ queues, go to step 6.

  5. Check whether queues on the interface use the combined scheduling mode.

    Run the display this command in the interface view to check the scheduling mode used by each queue on the interface.

    For CloudEngine 12800E, 8800, 7800, 6800, and 5800 series switches excluding the CE6870EI and CE6875EI:
    • If qos pq and qos wrr or qos drr are configured in each queue, the queue uses the combined scheduling mode.

      In combined scheduling mode, if no bandwidth limit is configured for PQ queues, traffic shaping of WRR or DRR queues is affected when PQ queues contain a large number of packets. This is because queue shaping is configured on WRR or DRR queues. Run the qos { pq | drr | wrr }, qos queue queue-index wrr weight weight, or qos queue queue-index drr weight weight command to reconfigure the scheduling mode and parameters of each queue, reducing packets entering PQ queues.

    • If each queue uses the scheduling mode of qos pq or qos wrr/drr, go to step 6.
    For the CE12800 series switches, CE6875EI and CE6870EI:
    • If qos pq and qos wfq are configured in each queue, the queue uses the combined scheduling mode.

      In combined scheduling mode, if no bandwidth limit is configured for PQ queues, traffic shaping of WFQ queues is affected when PQ queues contain a large number of packets. This is because queue shaping is configured on WFQ queues. Run the qos { pq | wfq } or qos queue queue-index wfq weight weight command to reconfigure the scheduling mode and parameters of each queue, reducing packets entering PQ queues.

    • If each queue uses the scheduling mode of qos pq or qos wfq, 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: 604711

Downloads: 2938

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next