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

URPF Troubleshooting

This chapter describes common causes of URPF faults, and provides the corresponding troubleshooting flowcharts, troubleshooting procedures, alarms, and logs.

URPF Check Fails

This section describes the troubleshooting flowchart shown in Figure 3-1 and provides a step-by-step troubleshooting procedure for the fault that prevents the URPF-enabled device from discarding packets as expected.

Common Causes

This fault is commonly caused by one of the following:

  • Source addresses of the packets that should be discarded in the routing entries exist.
  • Default routes in the routing table exist.
  • The matching rules configured on the device are incorrect.
Troubleshooting Flowchart

A URPF-enabled device receives certain packets that should be discarded by themselves, but the statistics show that no packets are discarded by URPF. In this case, follow the troubleshooting procedure shown in Figure 4-123 to isolate the problem.

The troubleshooting roadmap is as follows:
  • Check whether there are default routes and routes with the sources addresses of the packets that should be discarded in the routing table.
  • Check whether the matching rules are correct.
Figure 4-123 Troubleshooting flowchart flowchart for URPF

Troubleshooting Procedure

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 whether there are any default routes and routes with the source addresses of the packets that should be discarded in the routing table.

    Run the display ip routing-table command in the user view to check the Destination/Mask field in the routing table.

    • If the routing table contains routes with the source addresses of packets that should be discarded, configure certain rules and import the rules into the filter to deny the packets sent along these routes. For detailed configuration information, see "Routing Policy Configuration" in HUAWEI ME60 Multiservice Control Gateway Configuration Guide - IP Routing.

    • If the routing table does not contain such routes, go to Step 2.

  2. Check whether the configured matching rules are correct.

    Run the display traffic classifier classifier-name command in the user view to check the Rule(s) field.

    • If packets are incorrectly filtered based on the configured rules, correct the rules.
    • If packets are correctly filtered based on the configured rules, go to Step 3

  3. Collect the following information and contact Huawei.

    • Results of this troubleshooting procedures
    • Configuration files, log files, and alarm files of the devices

Relevant Alarms and Logs

Relevant Alarms

None

Relevant Logs

None

Translation
Download
Updated: 2019-06-11

Document ID: EDOC1000175918

Views: 13781

Downloads: 257

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