Configuring Inter-AS VPN Option C in an Independent Labeled Address Family (Solution 1)
To allow PEs in different ASs to exchange VPNv4 routes, inter-AS VPN Option C can be configured so that multi-hop EBGP connections are established between the PEs. An independent labeled address family can also be used to negotiate the label capability.
Usage Scenario
If the MPLS backbone network bearing VPN routes spans multiple ASs, the inter-AS VPN is required.
If each AS needs to exchange a large number of VPN routes, inter-AS VPN Option C is a good choice to prevent the ASBR from becoming a bottleneck that impedes network expansion. The following solutions can be used to implement inter-AS VPN Option C:
- Solution 1: A local ASBR learns a labeled BGP public network route from the peer ASBR, automatically assigns a label to this route, and advertises it to an IBGP peer that supports the label capability, a PE in the same AS. Then, a complete public network LSP is established.
- Solution 2: The IBGP peer relationship between the PE and ASBR is not needed. In this solution, an ASBR learns the labeled public BGP routes of the remote AS from the peer ASBR. Then these labeled public BGP routes are imported to an IGP to trigger the establishment of an LDP LSP. In this manner, a complete LDP LSP can be established between the two PEs.
Solution 1 is described in this section, and solution 2 is described in Configuring Inter-AS VPN Option C in an Independent Labeled Address Family (Solution 2).
In inter-AS VPN-Option C mode, do not enable LDP between ASBRs. If LDP is enabled on the interfaces between ASBRs, LDP sessions are then established between the ASBRs. As a result, the ASBRs establish an egress LSP and send Mapping messages to upstream ASBRs. After receiving Mapping messages, the upstream ASBRs establish a transit LSP. If a large number of BGP routes exist, enabling LDP on the interfaces between ASBRs leads to the occupation of a large number of LDP labels.
Pre-configuration Tasks
Before configuring inter-AS VPN Option C (solution 1), complete the following tasks:
Configure an IGP for the MPLS backbone network of each AS to ensure IP connectivity of the backbone network in each AS.
Configure MPLS and MPLS LDP both globally and per interface on each node of the backbone network.
Configure an IBGP peer relationship between the PE and ASBR in the same AS.
Configure a VPN instance on each PE and bind the interface that connects a PE to a CE to the VPN instance on that PE.
Configure an IP address for the interface connecting a CE to a PE.
- Enabling the Exchange of Labeled IPv4 Routes
- In inter-AS VPN Option C mode, a BGP LSP needs to be established between ASs, and labeled IPv4 routes need to be exchanged between BGP peers.
- Establishing an MP-EBGP Peer Relationship Between PEs
- By introducing extended community attributes into BGP, MP-EBGP can advertise VPNv4 routes between PEs. PEs of different ASs are generally not directly connected. Therefore, to set up the EBGP connection between the PEs of different ASs, you need to configure the permitted maximum hops between PEs.
- Configuring Route Exchange Between a CE and a PE
- A PE and a CE can communicate using BGP, an IGP, or a static route.
- Verifying the Configuration of Inter-AS VPN Option C in an Independent Labeled Address Family (Solution 1)
- After configuring inter-AS VPN Option C (solution 1), check information about all BGP peer relationships, VPNv4 routes on PEs or ASBRs, and labels of IPv4 routes on ASBRs.