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).
Congestion Management Fails to Take Effect

Congestion Management Fails to Take Effect

This section describes the troubleshooting flowchart and provides a step-by-step troubleshooting procedure to use when congestion management fails to take effect.

Common Causes

This fault is commonly caused by one of the following:
  • Traffic shaping is not configured on the outbound interface.
  • Congestion management is not configured on the outbound interface.
  • Scheduling parameters are set incorrectly.
  • Packets enter incorrect queues.

Troubleshooting Flowchart

If packets in a queue are not scheduled or scheduling results are incorrect, congestion management fails to take effect. Follow procedures shown in the troubleshooting flowchart in Figure 21-8.
Figure 21-8  Troubleshooting flowchart for ineffective congestion management

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 traffic shaping is configured correctly on the outbound interface.

    Run the display this command in the view of the outbound interface to check whether the qos gts command is used.

    • If the qos gts command is not used or traffic shaping parameters are incorrect, run the qos gts command.
    • If the qos gts command is used, go to step 2.

  2. Check that congestion management is configured on the outbound interface.

    Check Item

    Method

    Queue-based congestion management

    Run the display this command in the view of the outbound interface to check whether the qos queue-profile command is used. If the qos queue-profile command is used, run the display this command in the queue profile view to check whether the schedule command is used. If the schedule command is used, queue-based congestion management is configured on the interface.

    Flow-based congestion management

    Run the display this command in the view of the outbound interface to check whether the traffic-policy command is used. If the traffic-policy command is used, run the display traffic policy user-defined command to check whether the queue af, queue ef, or queue wfq command is used. If the queue af, queue ef, or queue wfq command is used, flow-based congestion management is configured.

    NOTE:

    Flow-based congestion management can be configured only on WAN-side interfaces.

    • If queue-based congestion management or flow-based congestion management is not configured, configure it on the outbound interface.
    • If queue-based congestion management or flow-based congestion management is configured, go to step 3.

  3. Check whether scheduling parameters are set incorrectly.

    • If queue-based congestion management is configured on the interface, run the display this command in the queue profile view to view the scheduling mode and weight of each queue.

      NOTE:

      By default, PQ scheduling is implemented for all queues. To smooth out the delay and jitter when congestion occurs, use PQ scheduling for core services such as voice and video services, and use DRR, WRR, or WFQ scheduling for non-core services. This configuration allows the switch to uniformly process packets with the same priority, and process packets with different priorities based on weights.

      • If scheduling parameters are incorrect, run the schedule and queue weight commands to reconfigure the scheduling mode and weight of each queue.

      • If scheduling parameters are correct, go to step 4.
    • If flow-based congestion management is configured on the interface, run the display traffic policy user-defined command to check whether scheduling parameters such as the scheduling mode and minimum bandwidth are correct.

      • If scheduling parameters are incorrect, run the queue af, queue ef, or queue wfq command to reconfigure scheduling parameters.

      • If scheduling parameters are correct, go to step 4.

  4. Check whether packets enter correct queues.

    Run the display qos queue statistics interface command to view queue-based traffic statistics on the outbound interface. Check whether packets enter specified queues.

    NOTE:

    You can also configure traffic policy-based traffic statistics, run the display traffic policy statistics command, and check the statistics on the inbound queue of each flow based on the values of Passed and Dropped. For details, see Introduction to Traffic Statistics in Enterprise Routers Configuration Guide - QoS.

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

    • Results of the preceding troubleshooting procedure
    • Configuration file, log file, and alarm file of the AR100&AR120&AR150&AR160&AR200&AR1200&AR2200&AR3200&AR3600

Translation
Download
Updated: 2019-05-10

Document ID: EDOC1000079719

Views: 456013

Downloads: 4321

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