Apply an export routing
Route related attributes configured in VPN instance view are applicable to both IPv4 VPNs and IPv6
You can configure route related attributes for IPv6 VPNs in both VPN instance view and IPv6 VPN view.
Those configured in IPv6 VPN view take precedence.
Configuring routing on an IPv6 MCE
An IPv6 MCE implements service isolation through route isolation. IPv6 MCE routing configuration
IPv6 MCE-VPN site routing configuration
IPv6 MCE-PE routing configuration
On the PE in an IPv6 MCE network environment, disable routing loop detection to avoid route loss during
route calculation and disable route redistribution between routing protocols to save system resources.
Before you configure routing on an IPv6 MCE, complete the following tasks:
On the IPv6 MCE, configure VPN instances, and bind the VPN instances with the interfaces
connected to the VPN sites and those connected to the PE.
Configure the link layer and network layer protocols on related interfaces to ensure IP connectivity.
Configuring routing between IPv6 MCE and VPN site
You can configure IPv6 static routing, RIPng, OSPFv3, IPv6 IS-IS, or EBGP between the MCE and a VPN
Configuring static routing between IPv6 MCE and VPN site
An IPv6 MCE can reach a VPN site through an IPv6 static route. IPv6 static routing on a traditional CE
is globally effective and thus does not support address overlapping among VPNs. An IPv6 MCE supports
binding an IPv6 static route with an IPv6 VPN instance, so that the IPv6 static routes of different IPv6 VPN
instances can be isolated from each other.
To configure IPv6 static routing between IPv6 MCE and VPN site:
Enter system view.
export route-policy route-policy
By default, routes to be advertised
are not filtered.