HP MSR2000/3000/4000 Router Series MPLS Configuration Guide

139
and provider PE. To make sure the provider CE can receive all VPNv4 routes, configure the undo
policy vpn-target command on the provider CE to not filter VPNv4 routes by RTs.
• Configurations between provider PEs—Configure BGP VPNv4 route exchange between them.
Nested VPN allows a customer PE to directly exchange VPNv4 routes with a provider PE, without
needing to deploy a provider CE. In this case, the customer PE also acts as the provider CE. Therefore,
you must configure provider CE settings on it.
Configurations on the customer CE, customer PE, and provider CE are similar to basic MPLS L3VPN
configurations. This task describes the configurations on the provider PE.
When you configure nested VPN, follow these guidelines:
• The address spaces of sub-VPNs of a VPN cannot overlap.
• Do not assign nested VPN peers addresses that public network peers use.
• Nested VPN does not support multi-hop EBGP. A provider PE and a provider CE must use the
addresses of the directly connected interfaces to establish a neighbor relationship.
To configure nested VPN:
Ste
p
Command Remarks
1. Enter system view.
system-view N/A
2. Enter BGP view.
bgp as-number N/A
3. Enter BGP-VPN VPNv4
address family view.
address-family vpnv4 N/A
4. Enable nested VPN.
nesting-vpn By default, nested VPN is disabled.
5. Return to BGP view.
quit N/A
6. Enter BGP-VPN view.
ip vpn-instance vpn-instance-name N/A
7. Specify the peer CE or the
peer group of the peer CE.
peer { group-name |
peer-address } as-number
as-number
By default, no peer is specified.
8. Enter BGP-VPN VPNv4
address family view.
address-family vpnv4
N/A
9. Enable BGP VPNv4 route
exchange with the peer CE or
the peer group of the peer CE.
peer { group-name |
peer-address } enable
By default, BGP does not exchange
VPNv4 routes with any peer.
Configuring HoVPN
HoVPN is suited to build hierarchical VPNs, reducing performance requirements for PEs.
Before you configure HoVPN, complete basic MPLS L3VPN settings on UPE and SPE.
Do not configure the peer default-route-advertise vpn-instance and peer upe route-policy commands at
the same time.
Do not connect an SPE to a CE directly. If an SPE must be directly connected to a CE, the VPN instance
on the SPE and that on the UPE must be configured with different RDs.
To configure HoVPN: