IPv6 route import between VPN and public network instances enables IPv6 VPN users to communicate with IPv6 public network users, whereas IPv6 route import between VPN instances enables IPv6 users in different VPNs to communicate.
In BGP/MPLS IPv6 VPN networking, IPv6 VPN users cannot communicate with IPv6 public network users and IPv6 users of two VPNs can communicate only if the two VPNs have matching VPN targets. To enable IPv6 VPN users to communicate with IPv6 public network users and IPv6 users of two VPNs with unmatching VPN targets to communicate, configure IPv6 route import between instances.
IPv6 route import between VPN and public network instances
IPv6 route import between VPN instances
IPv6 routes are first imported to the VPN or public network instance's corresponding routing tables. For example, VPN OSPFv3 routes are first imported to the public network instance's OSPFv3 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 IPv6 routing table to guide traffic forwarding. In addition, these routes can be advertised to other devices on the network.
Direct routes
Static routes
OSPFv3 routes
IS-IS routes
BGP4+ 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.
Before configuring IPv6 route import between instances, complete the following task: