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

AR Router Troubleshooting Guide

This Product Documentation provides guidance for maintaining AR Enterprise Router, covering common information collection and fault diagnostic commands, typical fault troubleshooting guide, and troubleshooting.
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).
Queue-based Traffic Shaping Results Are Incorrect

Queue-based Traffic Shaping Results Are Incorrect

This section describes the troubleshooting flowchart and provides a step-by-step troubleshooting procedure to use when queue-based traffic shaping results are incorrect.

Common Causes

This fault is commonly caused by one of the following:
  • Traffic shaping parameters are set incorrectly.
  • The CIR value for interface-based traffic shaping is smaller than the sum of CIR values for traffic shaping in queues on the interface. As a result, the bandwidth required by queues cannot be ensured.
  • Packets do not enter queues configured with traffic shaping because the configuration is incorrect. For example, priority mapping is incorrect.
  • Each queue uses the combined scheduling mode and excess packets enter Priority Queuing (PQ) queues. As a result, other queues cannot obtain sufficient bandwidth.
    NOTE:
    In combined scheduling mode, if the bandwidth is insufficient, the CIR value of other queues cannot be reached. This is a correct traffic shaping result.

Troubleshooting Flowchart

Figure 21-6 shows the troubleshooting flowchart.
Figure 21-6 Troubleshooting flowchart for incorrect queue-based traffic shaping results

Troubleshooting Procedure

NOTE:

Saving the results of each troubleshooting step is recommended. If troubleshooting fails to correct the fault, you will have a record of your actions to provide Huawei technical support personnel.

Procedure

  1. Check that queue-based traffic shaping parameters are set correctly.

    Run the display this command in the interface view to check whether the qos queue-profile command is used.
    • If the qos queue-profile command is used, run the display qos queue-profile queue-profile-name command to check the queue profile configuration.

      • If the value of the GTS (CIR/CBS) field is -/-, queue-based traffic shaping is not configured in the queue profile. Run the queue gts command in the queue profile view to configure queue-based traffic shaping.
      • If the value of the GTS (CIR/CBS) field is not -/-, queue-based traffic shaping is configured in the queue profile. Record the index of the queue configured with traffic shaping and go to step 2.
    • If the qos queue-profile command is not used, run the qos queue-profile command to configure a queue profile.

  2. Check whether the interface is configured with interface-based traffic shaping.

    Check whether the qos gts command is used on the interface.
    • If yes, go to step 3.
    • If not, go to step 4.

  3. Check whether the CIR value for interface-based traffic shaping 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 for interface-based traffic shaping is smaller than the sum of CIR values for traffic shaping in queues on the interface, queues on the interface cannot obtain sufficient bandwidth. The traffic shaping result may be incorrect. Run the qos gts command to modify interface-based traffic shaping parameters to ensure that the CIR value for interface-based traffic shaping is greater than the sum of CIR values for traffic shaping in queues on the interface.

    • If the CIR value for interface-based traffic shaping is greater than the sum of CIR values for traffic shaping in queues on the interface, 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 the values of Passed and Dropped fields in the command output are 0/0, packets do not enter traffic shaping queues. Rectify the fault according to Packets Enter Incorrect Queues.
    • If the values of Passed and Dropped fields in the command output are not 0/0, packets enter traffic shaping queues. Check whether a large number of packets enter PQ queues (for example, the rate of packets on the GigabitEthernet interface exceeds 100 Mbit/s and the rate of packets on the Ethernet interface exceeds 10 Mbit/s).
      • If yes, go to step 5.
      • If not, 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.
    • If schedule pq and schedule wrr, schedule drr, or schedule wfq are configured for each queue, the combined scheduling mode is used.

      In combined scheduling mode, when traffic is transmitted on the interface, the traffic in PQ queues is first processed, and then the traffic in Weighted Round Robin (WRR), Deficit Round Robin (DRR), or Weighted Fair Queuing (WFQ) queues is processed. The remaining bandwidth is allocated based on weights. If PQ queues contain excess packets, some packets in WRR, DRR, WFQ queues may be not processed.

      Run the qos queue-profile command in the queue profile view and run the schedule and queue weight commands in the queue profile view to reconfigure the scheduling mode and weight of each queue, reducing the number of packets that enter PQ queues.

      NOTE:

      In combined scheduling mode, if the bandwidth is insufficient, the CIR value of other queues cannot be reached. This is a correct traffic shaping result.

    • If each queue uses PQ, WRR, DRR, or WFQ scheduling mode, go to step 6.

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

    • Results of the preceding troubleshooting procedure
    • Configuration file, log file, and alarm file of the AR

Translation
Download
Updated: 2019-08-09

Document ID: EDOC1000079719

Views: 497474

Downloads: 4543

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