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).
Private Network Communication Fails After IPSec Is Configured. What Are the Causes?

Private Network Communication Fails After IPSec Is Configured. What Are the Causes?

Private networks fail to communicate with each other after IPSec is configured. The possible causes are as follows:
  • The public addresses of two IPSec-enabled devices cannot ping each other.
  • The data flow defined for IPSec encapsulation is the same as that defined for NAT. You can run the display acl all command to view the matching ACL rule. In this case, use either of the following methods to prevent the data flow overlapping:

    • Ensure that the destination IP address in the ACL rule referenced by IPSec is denied in the ACL rule referenced by NAT. By doing so, the device does not perform NAT on the data flow protected by IPSec.
    • The ACL rule referenced by IPSec matches NAT-translated IP address.
  • The device incorrectly learns private routes. The outbound interface to the destination private network is not the public network interface with IPSec enabled.
  • When the authentication algorithm used in an IPSec proposal is SHA2, the encryption and decryption methods on both ends are inconsistent.
Translation
Download
Updated: 2019-05-10

Document ID: EDOC1000079719

Views: 453553

Downloads: 4311

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