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).
Priority Mapping Results Are Incorrect

Priority Mapping Results Are Incorrect

Common Causes

This fault is commonly caused by one of the following:
  • The type of the priority trusted by the inbound interface is incorrect.
  • On the AR2201-48FE-S, AR2220-S, AR3200-S or AR2240-S, override is not specified in the trust command on the inbound interface.
  • Priority mapping in the priority mapping table is incorrect.
  • There are configurations affecting priority mapping on the inbound interface.
  • There are configurations affecting priority mapping on the outbound interface.

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 AR120-S&AR150-S&AR160-S&AR200-S series, AR1200-S series or AR2204-S, 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 AR2201-48FE-S, AR2220-S, AR3200-S or AR2240-S, if trust is used, the priority in packets is different from the priority trusted by the inbound interface, and override is specified, the device checks the priority mapping table based on the interface priority by the port priority command and modifies packet priorities.
    • If not, run the trust command to correctly configure the priority type trusted by the inbound interface.
    • On the AR120-S&AR150-S&AR160-S&AR200-S series, AR1200-S series or AR2204-S, if the priority in packets is different from the priority trusted by the inbound interface, go to step 3.
    • On the AR2201-48FE-S, AR2220-S, AR3200-S or AR2240-S, 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 AR2201-48FE-S, AR2220-S, AR3200-S or AR2240-S.

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

Translation
Download
Updated: 2019-12-27

Document ID: EDOC1000174115

Views: 45689

Downloads: 34

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next