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

Configuration Guide - VPN 01

NE05E and NE08E V300R003C10SPC500

This is NE05E and NE08E V300R003C10SPC500 Configuration Guide - VPN
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).
Configuring IPv4 Route Import Between Instances

Configuring IPv4 Route Import Between Instances

IPv4 route import between VPN and public network instances enables IPv4 VPN users to communicate with IPv4 public network users, whereas IPv4 route import between VPN instances enables IPv4 users in different VPNs to communicate.

Usage Scenario

In BGP/MPLS IPv4 VPN networking, IPv4 VPN users cannot communicate with IPv4 public network users and IPv4 users of two VPNs can communicate only if the two VPNs have matching VPN targets. To enable IPv4 VPN users to communicate with IPv4 public network users and IPv4 users of two VPNs with unmatching VPN targets to communicate, configure IPv4 route import between instances.

IPv4 route import between instances is further classified into the following types:
  • IPv4 route import between VPN and public network instances

    IPv4 routes are first imported to the VPN or public network instance's corresponding routing tables. For example, IPv4 VPN OSPF routes are first imported to the public network instance's OSPF routing table. If the imported routes are preferred in the corresponding routing table, they will be further imported to the VPN or public network instance's IPv4 routing table to guide traffic forwarding. In addition, these routes can be advertised to other devices on the network.

  • IPv4 route import between VPN instances

    The IPv4 routes of one VPN instance are first imported to another VPN instance's corresponding routing table. For example, VPNA's OSPF routes are first imported to VPNB's OSPF routing table. If the imported routes are preferred in the corresponding routing table, they will be further imported to the VPN instance's IPv4 routing table to guide traffic forwarding. In addition, these routes can be advertised to other devices on the network.

NOTE:

BGP IPv4 route import between instances does not take effect for routes imported between local VPN instances or routes imported in Import or Network mode.

Currently, the following types of IPv4 routes can be imported between instances:
  • Direct routes

  • Static routes

  • OSPF routes

  • IS-IS routes

  • BGP routes

  • VLINK direct routes

    NOTE:

    Traffic forwarding relies on direct routes (Vlink direct routes) generated based on user entries. When QinQ or Dot1q VLAN tag termination sub-interfaces are used for route import between VPN and public network, Vlink direct routes cannot be imported. As a result, traffic forwarding is interrupted. To solve this problem, route import between VPN and public network newly supports import of Vlink direct routes.

Pre-configuration Tasks

Before configuring IPv4 route import between instances, configure BGP/MPLS IPv4 VPN.

Configuration Procedures

Perform one or more of the following configurations as required.

Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058925

Views: 27339

Downloads: 51

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