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

Troubleshooting Guide

CloudEngine 16800, 12800, 12800E, 8800, 7800, 6800, and 5800 Series Switches

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).
Troubleshooting Procedure

Troubleshooting Procedure

Context

After commands are configured to troubleshoot faults, pay attention to the configuration validation mode to ensure that the configurations take effect. Unless otherwise specified, this manual defaults to the two-phase validation mode.

  • In immediate validation mode, the configuration takes effect immediately after you run a command and press Enter.
  • In two-phase validation mode, you must run the commit command after commands are configured to commit the configuration.

Save the results of each troubleshooting step, so you can provide related information to Huawei technical support if your troubleshooting fails.

Procedure

  1. Check whether packets match rules in the traffic classifier.

    Run the display traffic-policy statistics command to check the traffic statistics in the system, on the interface, or in the VLAN to which the traffic policy is applied. If no information is displayed, packets do not match rules in the traffic classifier.

    Before viewing traffic statistics, ensure that the traffic statistics function has been enabled using the statistic enable command in the traffic behavior view.

    • If packets match rules in the traffic classifier, go to step 4.
    • If packets do not match rules in the traffic classifier, go to step 2.

  2. Check that the traffic policy is configured correctly.
    1. Check whether attributes of packets match rules in the traffic classifier.

      View attributes (such as the IP address, MAC address, DSCP priority, VLAN ID, and 802.1p priority) of packets. Then run the display traffic policy command to view the traffic classifier in the traffic policy and run the display traffic classifier command to view rules in the traffic classifier. Check whether attributes of packets match rules in the traffic classifier.
      • If not, modify the rules to match attributes of packets.
      • If so, go to step b.

    2. Check that the traffic behavior associated with the traffic classifier is configured correctly.

      Run the display traffic policy policy-name classifier classifier-name command to check whether the traffic behavior associated with the traffic classifier is configured correctly.

      • If not, run the traffic behavior command to enter the traffic behavior view and configure a correct traffic behavior.
      • If so, go to step c.

    3. Check whether the traffic policy is applied to a correct object.

      Run the display traffic-policy applied-record command to check whether the traffic policy is successfully applied to the correct system, VLAN, or interface in the correct direction. When the traffic policy is applied to incoming packets, the traffic policy direction should be inbound; when it is applied to outgoing packets, the traffic policy should be outbound.
      • If the traffic policy applies to an incorrect object or direction, run the traffic-policy command to re-apply the traffic policy correctly.

      • If the traffic policy fails to be applied, go to step 4.
      • If the traffic policy is correctly applied, go to step 3.

  3. Check whether packets match another rule with a higher priority.

    Run the display current-configuration command to check rules on the device. Check whether other rules match packets, and note the matching sequence of the traffic policy.
    • If no other rule matches packets, go to step 4.
    • If there is another rule matching packets, check the rule that takes effect as follows:
      • Check priorities of traffic policies.

        Table 16-1 describes types of traffic classifiers supported by the device. When packets match multiple traffic policies, either of the following situations occurs:
        • If traffic classification rules in the traffic policies are of the same type, that is, the rules are all user-defined ACL rules, Layer 2 rules, or Layer 3 rules, only one traffic policy takes effect. The traffic policy that takes effect depends on the object to which the traffic policy has been applied. The traffic policies applied to the interface, VLAN, and system take effect in descending order of priority.
        • If traffic classification rules in the traffic policies are of different types and actions do not conflict, all the traffic policies take effect. If actions conflict, the traffic policy that takes effect depend on the rules. The rule priority is as follows: user-defined ACL rule > Layer 2 rule + Layer 3 rule > Layer 2 rule > Layer 3 rule.
        Table 16-1 Traffic classification rules

        Layer

        Traffic Classification Rule

        Layer 2

        • Destination MAC address
        • Source MAC address
        • VLAN ID in the outer tag of a VLAN packet
        • 802.1p priority in the outer tag of a VLAN packet
        • VLAN ID in the inner tag of a VLAN packet
        • 802.1p priority in the inner tag of a VLAN packet
        • Protocol field encapsulated based on Layer 2 information
        • Double VLAN tags
        • EXP priority in MPLS packets (CE12800, CE6870EI, and CE6875EI series switch)
        • ACL 4000-4999

        Layer 3

        • DSCP priority in IP packets
        • IP precedence in IP packets
        • IP protocol type, that is, IPv4
        • TCP SYN flag in TCP packets
        • ACL 2000-3999

        Others

        • All packets
        • Inbound interface
        • Outbound interface
        • ACL 5000-5999
      • Check precedence values of traffic classifiers.

        Run the display this command in the traffic policy view to check precedence values. A traffic classifier with a higher precedence value indicates a lower priority of the traffic classifier. If another rule takes precedence over the current rule, the traffic action corresponding to the rule takes effect. Reconfigure the rule so that the current rule takes effect.

  4. Collect the following information and contact technical support personnel.

    • Results of the preceding troubleshooting procedure
    • Configuration file, logs, and alarms of the device

Translation
Download
Updated: 2020-01-07

Document ID: EDOC1000060766

Views: 607733

Downloads: 2950

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next