221[PE3-bgp-vpn1] peer 2001:1::1 as-number 65410[PE3-bgp-vpn1] ipv6-family unicast[PE3-bgp-ipv6-vpn1] peer 2001:1::1 enable[PE3-bgp-ipv6-vpn1] import-route direct[PE3-bgp-ipv6-vpn1] quit[PE3-bgp-vpn1] quit[PE3-bgp] quit# Configure PE 4 and CE 4 in the same way that PE 3 and CE 3 are configured. (Details notshown.)5. Establish an MP-IBGP peer relationship between PEs of the customer carrier to exchange the VPNroutes of the customer carrier's customers:# Configure PE 3.[PE3] bgp 100[PE3-bgp] peer 6.6.6.9 as-number 100[PE3-bgp] peer 6.6.6.9 connect-interface loopback 0[PE3-bgp] ipv6-family vpnv6[PE3-bgp-vpnv6] peer 6.6.6.9 enable[PE3-bgp-vpnv6] quit[PE3-bgp] quit# Configure PE 3 in the same way that PE 3 is configured. (Details not shown.)6. Verify the configuration:# Execute the display ip routing-table command on PE 1 and PE 2. The output shows that onlyroutes of the provider carrier network are present in the public network routing table of PE 1 andPE 2. Take PE 1 as an example:[PE1] display ip routing-tableRouting Tables: PublicDestinations : 7 Routes : 7Destination/Mask Proto Pre Cost NextHop Interface3.3.3.9/32 Direct 0 0 127.0.0.1 InLoop04.4.4.9/32 ISIS 15 10 30.1.1.2 Vlan1230.1.1.0/24 Direct 0 0 30.1.1.1 Vlan1230.1.1.1/32 Direct 0 0 127.0.0.1 InLoop030.1.1.2/32 Direct 0 0 30.1.1.2 Vlan12127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0# Execute the display ip routing-table vpn-instance command on PE 1 and PE 2. The output showsthat the internal routes of the customer carrier network are present in the VPN routing tables. TakePE 1 as an example:[PE1] display ip routing-table vpn-instance vpn1Routing Tables: vpn1Destinations : 11 Routes : 11Destination/Mask Proto Pre Cost NextHop Interface1.1.1.9/32 ISIS 15 20 11.1.1.1 Vlan112.2.2.9/32 ISIS 15 10 11.1.1.1 Vlan115.5.5.9/32 BGP 255 0 4.4.4.9 NULL0
