Packets Enter Incorrect Queues

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.

   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.

   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 policy-name inbound command has been configured.

      • If the traffic-policy policy-name 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 policy-name 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 policy-name outbound command has been configured.

      • If the traffic-policy policy-name 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.