Configuring Nested Vpn - HP 10500 Series Configuration Manual

56 bytes from 120.1.1.1: icmp_seq=0 ttl=255 time=1.000 ms
56 bytes from 120.1.1.1: icmp_seq=1 ttl=255 time=0.000 ms
56 bytes from 120.1.1.1: icmp_seq=2 ttl=255 time=0.000 ms
56 bytes from 120.1.1.1: icmp_seq=3 ttl=255 time=0.000 ms
56 bytes from 120.1.1.1: icmp_seq=4 ttl=255 time=0.000 ms
--- 120.1.1.1 ping statistics ---
5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.000/0.200/1.000/0.400 ms

Configuring nested VPN

Network requirements
The service provider provides nested VPN services for users, as shown in
• PE 1 and PE 2 are PE devices on the service provider backbone. Both of them support the nested
VPN function.
CE 1 and CE 2 are connected to the service provider backbone. Both of them support VPNv4
•
routes.
PE 3 and PE 4 are PE devices of the customer VPN. Both of them support MPLS L3VPN.
•
CE 3 through CE 6 are CE devices of the sub-VPNs for the customer VPN.
•
The key of nested VPN configuration is to understand the processing of routes of sub-VPNs on the service
provider PEs:
When receiving a VPNv4 route from a CE (CE 1 or CE 2 in this example), a service provider PE
•
replaces the RD of the VPNv4 route with the RD of the MPLS VPN on the service provider network
where the CE resides, adds the export target attribute of the MPLS VPN on the service provider
network to the extended community attribute list, and then forwards the VPNv4 route.
To implement exchange of sub-VPN routes between customer PEs and service provider PEs,
•
MP-EBGP peers must be established between service provider PEs and customer CEs.
Figure 49 Network diagram
Device Interface IP address Device Interface
157
Figure 49.
IP address