6
Configuring route related attributes for a VPN instance
Restrictions and guidelines
If you configure route related attributes in both VPN instance view and VPN instance IPv4 address
family view, IPv4 VPN uses the configuration in VPN instance IPv4 address family view.
Prerequisites
Before you perform this task, create the routing policies to be used by this task. For information about
routing policies, see
Layer 3—IP Routing Configuration Guide
.
Procedure
1.
Enter system view.
system-view
2.
Enter VPN instance view or VPN instance IPv4 address family view.
Enter VPN instance view.
ip vpn-instance
vpn-instance-name
Execute the following commands in sequence to enter VPN instance IPv4 address family
view:
ip vpn-instance
vpn-instance-name
address-family ipv4
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
learning 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 static routing between an MCE and a VPN site
About static routing between an MCE and a VPN site
An MCE can reach a VPN site through a static route. Static routing on a traditional CE is globally
effective and does not support address overlapping among VPNs. An MCE supports binding a static
route to a VPN instance, so that the static routes of different VPN instances can be isolated from
each other.
