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

CLI-based Configuration Guide - QoS

AR100-S, AR110-S, AR120-S, AR150-S, AR160-S, AR200-S, AR1200-S, AR2200-S, and AR3200-S V200R009

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).
Packets Enter Incorrect Queues

Packets Enter Incorrect Queues

Common Causes

This fault is commonly caused by one of the following:
  • The priority type of packets is different from the priority type trusted by the inbound interface.
  • Priority mapping in the priority mapping table is incorrect.
  • There are configurations affecting the queues that packets enter on the inbound interface, including:

Procedure

  1. Check that the priority type of packets is the same as the priority type trusted by the inbound interface.

    Run the display this command in the inbound interface view to check the configuration of the trust command on the inbound interface (if the trust command is not used, the system does not trust any priority by default). Then obtain the packet header on the inbound interface, and check whether the priority type is the same as the priority type trusted by the inbound interface.

    NOTE:

    If the trust command is not used, the device sends packets to queues based on the priority configured by using the port priority command. As a result, all the packets enter the same queue and the device cannot provide differentiated services.

    • If not, run the trust command to modify the priority type trusted by the inbound interface to be the same as the priority type of the captured packets.
    • If so, go to step 2.

  2. Check whether priority mappings are correct.

    • The AR120-S&AR150-S&AR160-S&AR200-S series, AR1200-S series or AR2204-S sends packets to queues based on the 802.1p priority; therefore, check the mappings between DSCP or 802.1p priorities trusted by the interface and 802.1p priorities.
    • The AR2201-48FE-S, AR2220-S, AR3200-S or AR2240-S sends packets to queues based on the internal priority; therefore, check the mappings between DSCP or 802.1p priorities trusted by the interface and internal priorities.

    Enter the priority mapping table view and run the display this command to check whether priority mapping is configured correctly.

    • If priority mapping is configured incorrectly, run the qos map-table command to enter the priority mapping table view, and then run the input command to configure priority mapping correctly.
    • If so, go to step 3.

  3. Check whether there are configurations affecting the queues that packets enter on the inbound interface.
    1. Check whether traffic policing defining the re-marking action is configured on the inbound interface.

      Run the display this command in the view of the inbound interface to check whether the qos car inbound command with remark-8021p or remark-dscp configured has been used.

      • If so, cancel the re-marking action or run the undo qos car inbound command to cancel traffic policing.
      • If not, go to step b.

    2. Check whether the traffic policy defining the re-marking action is configured in the inbound direction on the inbound interface.

      Run the display this command in the view of the inbound interface to check whether the traffic-policy inbound command has been configured.

      • If the traffic-policy inbound command is configured, run the display traffic-policy applied-record policy-name command to check the traffic policy record and the traffic behavior in the traffic policy. If the traffic policy is applied successfully, run the display traffic behavior user-defined command to check whether the traffic behavior defines the re-marking action (remark 8021p or remark dscp), or remark local-precedence.

        • If the traffic behavior in the traffic policy contains the re-marking action, cancel the re-marking action or delete the traffic policy from the interface.
        • If the traffic policy fails to be applied or the traffic behavior in the traffic policy does not contain the re-marking action, go to step c.
      • If the traffic-policy inbound command is not configured, go to step c.

    3. Check whether the traffic policy defining the queuing action is configured in the outbound direction on the inbound interface.

      Run the display this command in the view of the inbound interface to check whether the traffic-policy outbound command has been configured.

      • If the traffic-policy outbound command is configured, run the display traffic-policy applied-record policy-name command to check the traffic policy record and the traffic behavior in the traffic policy. If the traffic policy is applied successfully, run the display traffic behavior user-defined command to check whether the command output contains Assured Forwarding, Expedited Forwarding, or Flow based Weighted Fair Queuing. If so, the traffic behavior contains the queuing action. Delete the queuing action from the traffic behavior or delete the traffic policy from the interface.

Translation
Download
Updated: 2019-05-17

Document ID: EDOC1000174115

Views: 40630

Downloads: 28

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