[PE2-bgp-ipv6-vpn1] peer 2002::2 enable
[PE2-bgp-ipv6-vpn1] quit
[PE2-bgp-vpn1] quit
[PE2-bgp] quit
6.
Configure CE 2:
# Configure an IPv6 address for GigabitEthernet 2/1/1.
<CE2> system-view
[CE2] interface gigabitethernet 2/1/1
[CE2-GigabitEthernet2/1/1] ipv6 address 2002::2 64
[CE2-GigabitEthernet2/1/1] quit
# Establish an EBGP peer relationship with PE 2, and redistribute VPN routes.
[CE2] bgp 65002
[CE2-bgp] peer 2002::1 as-number 600
[CE2-bgp] address-family ipv6 unicast
[CE2-bgp-ipv6] peer 2002::1 enable
[CE2-bgp-ipv6] import-route direct
[CE2-bgp-ipv6] quit
[CE2-bgp] quit
Verifying the configuration
# Execute the display ipv6 routing table command on CE 1 and CE 2 to verify that CE 1 and CE 2 have
a route to each other. Verify that CE 1 and CE 2 can ping each other. (Details not shown.)
Configuring IPv6 MPLS L3VPN carrier's carrier
Network requirements
Configure carrier's carrier for the scenario shown in
PE 1 and PE 2 are the provider carrier's PE routers. They provide VPN services to the customer
•
carrier.
CE 1 and CE 2 are the customer carrier's routers. They are connected to the provider carrier's
•
backbone as CE routers.
•
PE 3 and PE 4 are the customer carrier's PE routers. They provide IPv6 MPLS L3VPN services to end
customers.
CE 3 and CE 4 are customers of the customer carrier.
•
The key to the carrier's carrier deployment is to configure exchange of two kinds of routes:
Exchange of the customer carrier's internal routes on the provider carrier's backbone.
•
Exchange of the end customers' internal routes between PE 3 and PE 4, the PEs of the customer
•
carrier. In this process, an MP-IBGP peer relationship must be established between PE 3 and PE 4.
Figure
85. In this scenario:
350