H3C Technologies H3C S6800 Series Switches - Manual (Page 255)

242
100.1.1.0/32 Direct 0 0 100.1.1.2 Vlan11
100.1.1.2/32 Direct 0 0 127.0.0.1 InLoop0
100.1.1.255/32 Direct 0 0 100.1.1.2 Vlan11
127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0
127.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0
127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0
127.255.255.255/32 Direct 0 0 127.0.0.1 InLoop0
120.1.1.0/24 BGP 255 0 6.6.6.9 Vlan12
224.0.0.0/4 Direct 0 0 0.0.0.0 NULL0
224.0.0.0/24 Direct 0 0 0.0.0.0 NULL0
255.255.255.255/32 Direct 0 0 127.0.0.1 InLoop0
4. Verify that PE 3 and PE 4 can ping each other. (Details not shown.)
5. Verify that CE 3 and CE 4 can ping each other. (Details not shown.)
Configuring nested VPN
Network requirements
The service provider provides nested VPN services for users, as shown in Figure 68 .
• PE 1 and PE 2 are PE devices on the service provider backbone. Both of them support the nested
VPN feature.
• 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
a. Replaces the RD of the VPNv4 route with the RD of the MPLS VPN on the service provider
network where the CE resides.
b. Adds the export target attribute of the MPLS VPN on the service provider network to the
extended community attribute list.
c. 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.