17
3.
Configure route targets.
vpn-target vpn-target
&<1-8>
[
both
|
export-extcommunity
|
import-extcommunity
]
By default, no route targets are configured.
4.
Set the maximum number of active routes.
routing-table
limit
number
{
warn-threshold
|
simply-alert
}
By default, the number of active routes in a VPN instance is not limited.
Setting the maximum number of active routes for a VPN instance can prevent the device from
storing too many routes.
5.
Apply an import routing policy.
import route-policy route-policy
By default, all routes matching the import target attribute are accepted.
6.
Apply an export routing policy.
export route-policy route-policy
By default, routes to be advertised are not filtered.
Configuring routing between an MCE and a VPN
site
Configuring IPv6 static routing between an MCE and a VPN
site
About IPv6 static routing between an MCE and a VPN site
An MCE can reach a VPN site through an IPv6 static route. IPv6 static routing on a traditional CE is
globally effective and does not support address overlapping among VPNs. An 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.
Perform this configuration on the MCE. On a VPN site, configure normal IPv6 static routes.
Procedure
1.
Enter system view.
system-view
2.
Configure an IPv6 static route for an IPv6 VPN instance.
ipv6 route-static
vpn-instance
s-vpn-instance-name
ipv6-address
prefix-length
{
interface-type interface-number
[
next-hop-address
]
|
nexthop-address
[
public
]
|
vpn-instance
d-vpn-instance-name
nexthop-address
}
3.
(Optional.) Configure the default preference for IPv6 static routes.
ipv6 route-static default-preference
default-preference
The default preference for IPv6 static routes is 60.
