Priority Mapping Results Are Incorrect

Procedure

1. Check that packets enter the correct queues on the inbound interface.

   Run the display qos queue statistics command to check whether packets enter the correct queues on the inbound interface.

   • If not, locate the fault according to Packets Enter Incorrect Queues.
   • If so, go to step 2.

2. Check that the priority type trusted by the inbound interface is correct.

   Run the display this command in the view of the inbound interface to check whether the trusted priority type set by using the trust command on the inbound interface is correct.

   • If not, run the trust command to correctly configure the priority type trusted by the inbound interface.
   • If so, go to step 3.

3. 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 (DSCP priority mapping table view) command to configure priority mapping correctly.
   • If so, go to step 4.

4. Check whether there are any configurations affecting priority mapping on the inbound or outbound interface.
   The following configurations affect priority mapping on the inbound or outbound interface:

   • If the traffic-policy command that defines remark 8021p, remark ip-precedence, or remark dscp is used on the inbound or outbound interface, the re-marked priority is the packet priority.

   Run the display this command in the interface view on the inbound or outbound interface to check whether there are configurations affecting priority mapping. If so, delete or modify the configuration.