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

ME60 Troubleshooting Guide V1.0 (VRPv8)

This document provides the maintenance guide of the device, including daily maintenance, emergence maintenance, and typical 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).
MF Classification Troubleshooting

MF Classification Troubleshooting

This chapter describes common causes of MF classification faults and provides troubleshooting flowcharts and procedures, alarms, and logs to help identify and rectify these faults.

Common Causes

This section describes common causes for an MF classification fault.

Common causes are as follows:

  • No packet is received on the inbound interface.

  • Traffic classification is incorrectly implemented on the inbound interface.

  • The traffic behavior is incorrect.

  • The traffic policy is incorrect.

  • The traffic policy is incorrectly applied.

Troubleshooting Flowchart

This section describes the troubleshooting flowchart for MF classification.

Figure 4-114 shows a typical networking scheme for MF classification.

Figure 4-114 Networking for MF classification

NOTE:

Subinterface 1 and subinterface 2 stand for GE 1/0/1.1 and GE 6/0/2.1, respectively.

On the network shown in Figure 4-114, a traffic policy is configured on Device B to discard VLAN packets with the 802.1p value of 3 or the MAC address of 1-1-1. After Device B receives this type of VLAN packet, Device B does not discard the VLAN packet, not following the traffic policy.

Figure 4-115 shows the troubleshooting flowchart.

Figure 4-115 Troubleshooting for MF classification

Troubleshooting Procedure

This section describes the troubleshooting procedure for MF classification.

NOTE:

After the commands are configured to troubleshoot the faults, check the configuration validation mode to ensure that the configurations take effect. Unless otherwise specified, this manual defaults to immediate validation mode.

  • In immediate validation mode, the configurations take effect after the commands are entered.
  • In two-phase validation mode, after the commands are configured, the commit command needs to be run to commit the configurations.

Save the results of each troubleshooting step so that if your troubleshooting attempts fail to correct the fault, you will have a record of your actions to present to Huawei.

Procedure

  1. Check that the devices are connected.

    Run the display interface interface-type interface- number command in any view to check whether the packet is received on the inbound interface. If the packet is not, run the display ip interface brief command to check the status of the interfaces. Up indicates that the interface is available, whereas Down indicates that the interface is unavailable. If the interface is Down, check whether the link is connected properly or the shutdown command is used on the interface.

  2. Check that traffic classification is correctly implemented.

    1. Run the display acl command in any view to check whether the rule deny source-mac command is configured to define a matching rule to filter out packets with specific source MAC addresses.
    2. Run the display traffic classifier user-defined command in any view to check whether a traffic classifier is defined and the following if-match clauses are configured in the traffic classifier view.
      • if-match 8021p 3

      • if-match acl acl-number. acl-number specifies the number of the ACL that is used to filter out packets with specific source MAC addresses.

  3. Check that a traffic behavior is correct.

    Run the display traffic behavior user-defined command in any view to check whether a traffic behavior is defined and the action deny is configured in the traffic behavior view.

  4. Check that the traffic policy is correct.

    Run the display traffic policy user-defined command in any view to check whether a traffic policy is defined and a correct traffic behavior is defined in the traffic policy.

  5. Check that the traffic policy is correctly applied to GE 6/0/2.1.

    Run the display this command on GE 6/0/2.1 of ME device B to check whether the vlan-type dot1q 3 and traffic-policy inbound link-layer commands are configured.

Relevant Alarms and Logs

This section describes relevant alarms and logs for MF classification.

None

Translation
Download
Updated: 2019-06-11

Document ID: EDOC1000175918

Views: 13800

Downloads: 257

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