Priority Mapping Results Are Incorrect

Procedure

1. 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 the trust command is not used, the system does not trust any priority by default.)

   • On the AR300, AR600, AR700, AR1600, AR6100, AR6200, and AR6300 series, if trust is not used or the priority in packets is different from the priority trusted by the inbound interface, the device checks the priority mapping table based on the interface priority by the port priority command and modifies packet priorities.
   • On the SRU-100H, SRU-100HH, SRU-200H, SRU-400HK, SRU-600HK, SRU-400H, and SRU-600H, if trust is not used or the priority in packets is different from the priority trusted by the inbound interface, the device checks the priority mapping table based on the interface priority by the port priority command and modifies packet priorities.
   • if the priority in packets is different from the priority trusted by the inbound interface, go to step 3.
   • If the priority in packets is the same as the priority trusted by the inbound interface, go to step 2.

2. Check whether override is specified in the trust command on the device.
   • If override is not specified, the device does not change packet priorities after performing priority mapping. Specify override in the trust command.
   • If override is specified, 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 the input command to configure priority mapping correctly.
   • If so, go to step 4.

4. Check whether there are configurations affecting priority mapping on the inbound interface.
   1. Check whether traffic policing defining the re-marking action is configured on the inbound interface.

      Interface-based traffic policing takes precedence over priority mapping. If interface-based traffic policing defining remark-8021p or remark-dscp is configured on the inbound interface, the device re-marks packet priorities.

      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, delete the re-marking action or run the undo qos car policy-name inbound command to delete 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.

      A traffic policy takes precedence over priority mapping. If the traffic policy used on the inbound interface contains priority re-marking, remark local-precedence, or car with remark-8021p or remark-dscp, the device re-marks priorities of packets matching the traffic classifier.

      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 has been 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 has been applied successfully, run the display traffic behavior user-defined command to check whether the traffic behavior contains packet priority re-marking, internal priority re-marking, or car with remark-8021p or remark-dscp.

        • If the traffic behavior in the traffic policy 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 5.
      • If not, go to step 5.

5. Check whether there are configurations affecting priority mapping on the outbound interface.
   1. Check whether traffic policing defining the re-marking action is configured on the outbound interface.

      Interface-based traffic policing takes precedence over priority mapping. If interface-based traffic policing defining remark-8021p or remark-dscp is configured on the outbound interface, the device re-marks packet priorities.

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

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

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

      A traffic policy takes precedence over priority mapping. If the traffic policy used on the outbound interface contains priority re-marking, remark local-precedence, or car with remark-8021p or remark-dscp, the device re-marks priorities of packets matching the traffic classifier.

      Run the display this command in the view of the outbound interface to check whether the traffic-policy policy-name outbound command has been configured. If the traffic-policy outbound command has been 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 has been applied successfully, run the display traffic behavior user-defined command to check whether the traffic behavior contains packet priority re-marking, internal priority re-marking, or car with remark-8021p or remark-dscp. 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.