232
NOTE:
•
The address ranges for sub-VPNs of a VPN cannot overlap.
•
HP does not recommend giving nested VPN peers addresses that public network peers use.
•
Before specifying a nested VPN peer or peer group, be sure to configure the corresponding CE peer or
peer group in BGP VPN instance view.
•
Nested VPN does not support multi-hop eBGP networking. Therefore, a service provider PE and its peer
must use the addresses of the directly connected interfaces to establish a neighbor relationship.
Configuring multi-role host
To allow a CE to access multiple VPNs, you need to configure the multi-role host feature on the PE
connecting the CE.
NOTE:
For more information about policy routing, see
Layer 3—IP Routing Configuration Guide.
Configuration prerequisites
Before you configure the multi-role host feature, complete the following tasks on the PE:
•
Create VPN instances for the VPNs
•
Configure basic MPLS L3VPN
Configuring and applying policy routing
To configure and apply policy routing:
To do…
Use the command…
Remarks
Enter system view
system-view
—
Create a policy and enter policy
routing view
policy-based-route
policy-name
{
deny
|
permit
}
node
node-number
—
Specify the VPN instances for
forwarding packets
apply access-vpn vpn-instance
vpn-instance-name
&<1-6>
Required
Return to system view
quit
—
Enter the view of the interface
connecting a CE
interface
interface-type
interface-number
—
Apply policy routing to the
interface
ip policy-based-route
policy-name
Required
Configuring a static route
For configuration steps, see “