Inter-AS VPN Configuration Overview
MPLS VPN architecture typically runs within an AS. Routes of any VPN can be flooded within the AS, but not to other ASs. To implement the exchange of VPN routes between different ASs, the inter-AS MPLS VPN model is used. The inter-AS MPLS VPN model is an extension to MPLS VPN framework. Route prefixes and labels can be advertised over links between different carrier networks through the inter-AS MPLS model.
The MPLS VPN solution serves an increasing number of users across many applications. A site at one geographical location often needs to connect to an ISP network at another geographical location. In this situation, for example, inter-AS issues may arise for operators who manage different metropolitan area networks (MANs) or backbone networks that span different autonomous systems (AS).
Types of Inter-AS VPN
1. Inter-AS VPN Option A: Autonomous system boundary routers (ASBRs) manage VPN routes for in-ter-AS VPNs through dedicated interfaces.
2. Inter-AS VPN Option B: ASBRs advertise labeled VPN-IPv4 routes to each other through MP-EBGP.
3. Inter-AS VPN Option C: PE devices advertise labeled VPN-IPv4 routes to each other through Mul-ti-hop MP-EBGP.