IPv6 route import between VPN and public network instances enables IPv6 VPN users to communicate with IPv6 public network users.
If you do not want a VPN instance to change the next hops of imported routes when advertising these routes to its IBGP peers, run the import-rib route next-hop-invariable command for the VPN instance.
The system view is displayed.
Run ipv6 import-rib vpn-instance vpn-instance-name protocol { direct | vlink-direct-route | { static } [ valid-route ] } [ route-policy route-policy-name | route-filter route-filter-name ]
The device is enabled to import IPv6 VPN direct routes, Vlink direct routes, , or static routes to the public network instance's corresponding routing table.
Run bgp as-number
The BGP view is displayed.
Run ipv6-family unicast
The BGP-IPv6 unicast address family view is displayed.
Run import-rib vpn-instance vpn-instance-name [ include-label-route ] [ valid-route ] [ route-policy route-policy-name ]
The device is enabled to import VPN BGP4+ routes to the public network instance's BGP4+ routing table.
Run quit
Return to the BGP view.
Run quit
Return to the system view.
Run ip vpn-instance vpn-instance-name
The VPN instance view is displayed.
Run ipv6-family
The VPN instance IPv6 address family view is displayed.
Run import-rib public protocol { direct | vlink-direct-route | { static } [ valid-route ] } [ route-policy route-policy-name | route-filter route-filter-name ]
The device is enabled to import IPv6 public network direct routes, Vlink direct routes, , or static routes to the VPN instance's corresponding routing table.
Run bgp as-number
The BGP view is displayed.
Run ipv6-family vpn-instance vpn-instance-name
The BGP-VPN instance IPv6 address family view is displayed.
Run import-rib public [ include-label-route ] [ valid-route ] [ route-policy route-policy-name ]
The device is enabled to import public network BGP4+ routes to the VPN instance's BGP4+ routing table.
The configuration is committed.