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.

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

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.

Configuring Route Import Between VPN and Public Network Instances: Route import between VPN and public network instances enables VPN users and public network users to communicate.

Configuring Route Import Between VPN Instances: Route import between VPN instances enables users in different VPNs to communicate.

Verifying the Configuration of IPv4 Route Import Between Instances: After configuring IPv4 route import between instances on a device, you can check imported IPv4 routes on the device.