After LDP LSPs are established for the labeled BGP routes of the public network, EBGP connections in multi-hop mode are established between PEs of different ASs to exchange VPNv6 routes.
If the MPLS backbone network carrying VPN-IPv6 routes crosses multiple ASs, the inter-AS VPN is needed.
If each AS has a large amount of VPN-IPv6 routes to be exchanged, the VPN-Option C can be adopted to prevent the ASBR becoming a bottleneck of the network. Two solutions can be adopted to realize inter-AS VPN-Option C:
If an ASBR is ready to access a large number of PEs, Solution 2 is recommended because of the easy configuration.
In inter-AS IPv6 VPN-Option C, do not enable LDP between ASBRs. If LDP is enabled on the interfaces between ASBRs, LDP sessions are then established between the ASBRs. In this case, the ASBRs establish an egress LSP and send Mapping messages to the upstream ASBR. After receiving Mapping messages, the upstream ASBR establishes a transit LSP. When there are high-volume BGP routes, enabling LDP on the interfaces between ASBRs leads to the occupation of a large number of LDP labels.
Solution 2 is described here, and solution 1 is described in Configuring Inter-AS IPv6 VPN-Option C (Solution 1).
Before configuring inter-AS IPv6 VPN-Option C, complete the following tasks:
Configuring IGP for MPLS backbone networks in each AS to realize IP connectivity of the backbones in one AS
Configuring basic MPLS capability for the MPLS backbone network
Configuring MPLS LDP and establishing LSP between a PE and an ASBR in the same AS
Configuring a VPN Instance on the PE devices connected to the CE devices and Binding Interfaces to a VPN Instance
Configuring the IPv6 addresses of the CE interfaces through which the CE accesses the PE
Configuring a name for the prefix list used to filter labeled BGP routes of the public network