231
NOTE:
For information about routing policy configuration, see
Layer 3—IP Routing Configuration Guide.
Configuring nested VPN
For a network with many VPNs, if you want to implement layered management of VPNs and to conceal
the deployment of internal VPNs, nested VPN is a good solution. By using nested VPN, you can
implement layered management of internal VPNs easily with a low cost and simple management
operation.
Configuration prerequisites
Before configuring nested VPN, configure the basic MPLS L3VPN capability (see “
”).
Configuring nested VPN
To configure nested VPN:
To do…
Use the command…
Remarks
Enter system view
system-view
—
Enter BGP view
bgp
as-number
—
Enter BGP VPN instance view
ipv4-family vpn-instance
vpn-instance-name
—
Configure a CE peer or peer group
peer
{
group-name
|
peer-address
}
as-number
number
Required
Return to BGP view
quit
—
Enter BGP-VPNv4 subaddress
family view
ipv4-family vpnv4
—
Enable nested VPN
nesting-vpn
Required
Disabled by default.
Activate a nested VPN peer or peer
group, and enable the BGP-VPNv4
route exchange capability
peer
{
group-name
|
peer-address
}
vpn-instance
vpn-instance-name
enable
Required
By default, only IPv4 routes and no
BGP-VPNv4 routes can be
exchanged between nested VPN
peers/peer groups.
Add a peer to the nested VPN peer
group
peer
peer-address
vpn-instance
vpn-instance-name
group
group-name
Optional
By default, a peer is not in any
nested VPN peer group.
Apply a routing policy to routes
received from a nested VPN peer
or peer group
peer
{
group-name
|
peer-address
}
vpn-instance
vpn-instance-name
route-policy
route-policy-name
import
Optional
By default, no routing policy is
applied to routes received from a
nested VPN peer or peer group.
