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

Packets Enter Incorrect Queues

This section describes the troubleshooting flowchart and provides a step-by-step troubleshooting procedure to use when packets enter incorrect queues.

Common Causes

Packets enter incorrect queues in the following scenarios:
  • Packets with different priorities enter the same queue.
  • Packets with different priorities enter incorrect queues.
  • Packets with the same priority enter an incorrect queue.
  • Packets with the same priority enter different queues.
This fault is commonly caused by one of the following:
  • The type of the priority trusted by the inbound interface is incorrect.
  • Priority mapping relevant to inbound queues in the priority mapping table is incorrect. For the AR100&AR120&AR150&AR160&AR200&AR1200&AR2200(except the AR2204XE, AR2204XE-DC, AR2201-48FE, AR2201-48FE-S, AR2202-48FE, AR2220 and AR2240)series, AR100-S&AR110-S&AR120-S&AR150-S&AR160-S&AR200-S&AR1200-S series, AR2204-S, AR502CG-L, AR502EG-L, AR502EG-La, AR502EG-Lj, AR502EGR-L, AR502EG-L-PD, AR502EGW-L, AR502EGRb-L, AR502EGRc-Lc, AR502EGRc-Lc, AR502EGRz-Lc, AR502EGRz-L and AR530 series, pay attention to the mapping between DSCP or 802.1p priorities to 802.1p priorities. For AR2204XE, AR2204XE-DC, AR2201-48FE, AR2201-48FE-S, AR2202-48FE, AR2220, AR2240 and AR3200&AR3600 series, AR2201-48FE-S, AR2204-27GE-S, AR2204-51GE-S, AR2220E-S, AR2220-S, AR2240-S, AR2240C-S and AR3200-S series, pay attention to the mapping between DSCP or 802.1p priorities to internal priorities.
  • There are configurations affecting the queues that packets enter on the AR100&AR120&AR150&AR160&AR200&AR1200&AR2200&AR3200&AR3600, including:
    • The qos car inbound command with remark-8021p or remark-dscp configured has been used on the inbound interface of packets.
    • The traffic-policy inbound command with remark 8021p, remark dscp, or remark local-precedence configured, or the car command with remark-8021p or remark-dscp configured has been used on the inbound interface of packets.
    • The traffic-policy outbound command with queue af, queue ef, or queue wfq configured has been used on the outbound interface of packets.

Troubleshooting Flowchart

Figure 21-2 shows the troubleshooting flowchart.
Figure 21-2  Troubleshooting flowchart for packets entering incorrect queues

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 the type of the priority trusted by the inbound interface is correct.

    Run the display this command in the view of the inbound interface to view the configuration of the trust command. (If the trust command is not used, the system does not trust any priority by default.) Check whether the type of the priority trusted by the inbound interface is correct.

    NOTE:

    If the trust command is not used, the AR100&AR120&AR150&AR160&AR200&AR1200&AR2200&AR3200&AR3600 sends packets to queues based on the default 802.1p priority configured by using the port priority command. As a result, all the packets enter the same queue and the AR100&AR120&AR150&AR160&AR200&AR1200&AR2200&AR3200&AR3600 cannot provide differentiated services.

    • If the type of the priority trusted by the inbound interface is incorrect, run the trust command to change the type of the priority trusted by the inbound interface.
    • If the type of the priority trusted by the inbound interface is correct, go to step 2.

  2. Check whether priority mappings are correct.

    The AR100&AR120&AR150&AR160&AR200&AR1200&AR2200(except the AR2204XE, AR2204XE-DC, AR2201-48FE, AR2201-48FE-S, AR2202-48FE, AR2220 and AR2240)series, AR100-S&AR110-S&AR120-S&AR150-S&AR160-S&AR200-S&AR1200-S series, AR2204-S, AR502CG-L, AR502EG-L, AR502EG-La, AR502EG-Lj, AR502EGR-L, AR502EG-L-PD, AR502EGW-L, AR502EGRb-L, AR502EGRc-Lc, AR502EGRc-Lc, AR502EGRz-Lc, AR502EGRz-L and AR530 series send packets to queues based on the 802.1p priority; therefore, check the mappings between packet priorities (DSCP, or 802.1p priorities) trusted by the interface and 802.1p priorities. The AR2204XE, AR2204XE-DC, AR2201-48FE, AR2201-48FE-S, AR2202-48FE, AR2220, AR2240 and AR3200&AR3600 series, AR2201-48FE-S, AR2204-27GE-S, AR2204-51GE-S, AR2220E-S, AR2220-S, AR2240-S, AR2240C-S and AR3200-S series send packets to queues based on the internal priority; therefore, check the mappings between packet priorities (DSCP, or 802.1p priorities) trusted by the interface and internal priorities.

    Run the display qos map-table command to check whether priority mappings in the priority mapping table are correct.

    • If not, run the qos map-table command to enter the priority mapping table view and run the input command to configure the priority mappings correctly.
    • If yes, 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 yes, 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 used.

      • If the traffic-policy inbound command has been used, run the display traffic-policy applied-record 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 contains the re-marking action, delete the re-marking action from the traffic behavior or delete the traffic policy from the interface.
        • If the traffic policy fails to be applied or the traffic behavior does not contain the re-marking action, go to step c.
      • If the traffic-policy inbound command is not used, go to step c.

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

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

      • If the traffic-policy outbound command has been used, run the display traffic-policy applied-record 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 the traffic behavior configuration.

        • If the display traffic behavior user-defined command output contains Assured Forwarding, Expedited Forwarding, or Flow based Weighted Fair Queuing, the traffic behavior contains the queuing action. Delete the queuing action from the traffic behavior or delete the traffic policy from the interface.
        • If the traffic policy fails to be applied or the traffic behavior does not contain the queuing action, go to step 4.
      • If the traffic-policy outbound command is not used, go to step 4.

  4. Collect the following information and contact Huawei 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: 445042

Downloads: 4299

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