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

Priority Mapping Results Are Incorrect

This section describes the troubleshooting flowchart and provides a step-by-step troubleshooting procedure to use when priority mapping results are incorrect.

Common Causes

This fault is commonly caused by one of the following:
  • Packets do not carry the priority trusted by the inbound interface.
  • The AR2204XE, AR2204XE-DC, AR2201-48FE, AR2202-48FE, AR2220, AR2240, AR3200&AR3600 series, AR2201-48FE-S, AR2220-S, AR2240-S, AR2240C-S and AR3200-S series parameter override is not configured 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, including:
    • qos car inbound with remark-8021p or remark-dscp configured
    • traffic-policy inbound with remark 8021p, remark dscp, or remark local-precedence configured, or car with remark-8021p or remark-dscp configured
  • There are configurations affecting priority mapping on the outbound interface, including:
    • qos car outbound with remark-8021p or remark-dscp configured
    • traffic-policy outbound with remark 8021p, remark dscp or remark local-precedence configured, or car with remark-8021p or remark-dscp configured

Troubleshooting Flowchart

Figure 21-3 shows the troubleshooting flowchart.
Figure 21-3  Troubleshooting flowchart for incorrect priority mapping

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 whether packets carry the priority trusted by the inbound interface.

    Run the display this command in the view of the inbound interface to check the configuration of the trust command. (If the trust command is not used, the AR100&AR120&AR150&AR160&AR200&AR1200&AR2200&AR3200&AR3600 does not trust any priority by default.) Capture packets on the inbound interface and check whether the priority of the captured packets is trusted by the inbound interface.

    NOTE:
    • On AR100&AR120&AR150&AR160&AR200&AR1200&AR2200(except the AR2204XE, AR2204XE-DC, AR2201-48FE, AR2202-48FE, AR2220 and AR2240)series, AR100-S&AR110-S&AR120-S&AR150-S&AR160-S&AR200-S&AR1200-S series, AR2204-S, AR2201-48FE-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, if the trust command is not used or packets do not carry the priority trusted by the inbound interface, the device searches the mappings between 802.1p priorities and other types of priorities based on the default 802.1p priority configured by using the port priority command, and changes packet priorities.

    • On AR2204XE, AR2204XE-DC, AR2201-48FE, 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, if the trust command with override configured has been used or packets do not carry the priority trusted by the inbound interface, the device searches the mappings between 802.1p priorities and other types of priorities based on the default 802.1p priority configured by using the port priority command, and changes packet priorities.

    • If packets do not carry the priority trusted by the inbound interface, run the trust command to configure the inbound interface to trust the priority in packets.
    • On AR100&AR120&AR150&AR160&AR200&AR1200&AR2200(except the AR2204XE, AR2204XE-DC, AR2201-48FE, AR2202-48FE, AR2220 and AR2240)series, AR100-S&AR110-S&AR120-S&AR150-S&AR160-S&AR200-S&AR1200-S series, AR2204-S, AR2201-48FE-S, AR502E and AR530 series, if packets carry the priority trusted by the inbound interface, go to step 2.
    • On AR2204XE, AR2204XE-DC, AR2201-48FE, 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, if packets carry the priority trusted by the inbound interface, check whether override is configured in the trust command.
      • If override is not configured, the AR100&AR120&AR150&AR160&AR200&AR1200&AR2200&AR3200&AR3600 does not change packet priorities after performing priority mapping. Configure override in the trust command.
      • If override is configured, go to step 2.

  2. Check whether priority mappings are correct.

    Run the display qos map-table command to check whether the priority trusted by the interface and priority mapping are correct.

    • If not, run the qos map-table command to modify the configuration.
    • If yes, go to step 3.

  3. 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 AR100&AR120&AR150&AR160&AR200&AR1200&AR2200&AR3200&AR3600 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 yes, 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 AR100&AR120&AR150&AR160&AR200&AR1200&AR2200&AR3200&AR3600 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 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 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.
        • 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.

  4. 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 the re-marking action is configured on the outbound interface, the AR100&AR120&AR150&AR160&AR200&AR1200&AR2200&AR3200&AR3600 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 yes, 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 AR100&AR120&AR150&AR160&AR200&AR1200&AR2200&AR3200&AR3600 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 outbound command has been used.

      • If the display traffic-policy applied-record 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 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.
        • If the traffic policy fails to be applied or the traffic behavior does not contain the re-marking action, go to step 5.
      • If the traffic-policy outbound command is not used, go to step 5.

  5. 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

Interface-based Traffic Policing Results Are Incorrect

This section describes the troubleshooting flowchart and provides a step-by-step troubleshooting procedure to use when interface-based traffic policing results are incorrect.

Common Causes

Interface-based traffic policing results are incorrect in the following scenarios:
  • Traffic policing fails to take effect.
  • The CAR parameter values are incorrect.
This fault is commonly caused by one of the following:
  • The qos car command is not used on the interface.
  • Traffic policing is applied to an incorrect direction or CAR parameter values are incorrect.
  • Flow-based traffic policing and the qos car command are used in the same direction and the CIR value for flow-based traffic policing is smaller than that for interface-based traffic policing.

Troubleshooting Flowchart

If interface-based traffic policing fails to take effect, see Figure 21-4. If the CAR parameter values for interface-based traffic policing are incorrect, see Figure 21-5.

Figure 21-4  Troubleshooting flowchart for ineffective interface-based traffic policing

Figure 21-5  Troubleshooting flowchart for the incorrect CAR parameter values

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 the packet statistics on the interface configured with interface-based traffic policing.

    Run the display qos car statistics command to view the statistics on forwarded and discarded packets on the interface.

    • If there is no command output, the interface is not configured with interface-based traffic policing or interface-based traffic policing fails to take effect. Go to step 2.
    • If there is command output, interface-based traffic policing is configured successfully. Go to step 3.

  2. Check whether the interface is correctly configured with interface-based traffic policing.

    Run the display this command in the interface view to check whether the qos car command is used.

    • If not, run the qos car command to configure the QoS CAR correctly.
    • If yes, check whether the qos car command is used in the correct direction. To limit the rate of incoming packets, inbound must be configured. To limit the rate of outgoing packets, outbound must be configured.

      NOTE:

      On the AR100&AR120&AR150&AR160&AR200&AR1200&AR2200&AR3200&AR3600, LAN-side boards only support interface-based traffic policing in the inbound direction.

      • If the qos car command is used in the incorrect direction, run the qos car command to configure CAR in the correct direction.
      • If the qos car command is used in the correct direction, go to step 3.

  3. Check whether CAR parameters are set correctly.

    Run the qos car command to check whether the CIR value is correct.

    NOTE:

    If the CBS value is large, it may take a long time for traffic policing to take effect. Wait for a period of time or reduce the CBS value, and then check whether traffic policing takes effect.

    • If CAR parameters are set incorrectly, run the qos car command to modify CAR parameters.
    • If CAR parameters are correct, go to step 4.

  4. Check whether the interface is configured with flow-based traffic policing.

    NOTE:

    If interface-based traffic policing and flow-based traffic policing are applied to the same direction on an interface, the smaller CIR value takes effect.

    Run the display this command in the view of the inbound interface to check whether the traffic-policy command is used in the same direction as the qos car command.

    • If the traffic-policy command is 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 traffic behavior contains the CAR action and the CIR value is smaller than the CIR value for interface-based traffic policing, the CIR value in the traffic behavior takes effect. Increase the CIR value in the traffic behavior or delete the traffic policy from the interface.
      • If the traffic policy fails to be applied, the traffic behavior does not contain the CAR action, or the CIR value in the traffic behavior is greater than the CIR value for interface-based traffic policing, go to step 5.
    • If the traffic-policy command is not used, go to step 5.

  5. Collect the following information and contact 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: 450649

Downloads: 4307

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