Inter-AS Layer-2/Layer-3 VPN
MPLS VPNs can span multiple autonomous systems (AS) either through a single service provider or through multiple service providers working in conjunction.
Note: Inter-AS VPNs are supported for Flow Analysis only.
Three types of inter-AS VPNs are supported for both IPv4 and IPv6:
- Option A
- Option B
- Option C
Note: Layer-2 VPNs are supported in Option C. Layer-3 VPNs are supported for all options.
Inter-AS Multi-Hop Redistribution of eBGP VPN-IPv4 Routes
In a typical external BGP (eBGP) session, the egress router changes the next-hop to its own address when sending the route. The BGP next-hop unchanged feature lets you configure eBGP routing such that the egress router does not change the next-hop attribute to its own address as it forwards routes between neighboring, multi-hop autonomous systems (AS). Support is added in this release for the redistribution of eBGP VPN-IPv4 routes over an LSP. The PEs of different AS’s establish an LSP between them, reaching the next hops of the PEs in another AS via the LSPs. VPN-IPv4 routes are therefore installed in the VRF RIB.
Support is included for the following vendors and operating systems.
- Cisco Systems (command:
next-hop-unchanged)- IOS
- IOS-XE
- IOS-XR
- NX-OS
- Juniper Networks (command:
next_hop_unchanged) - Huawei Technologies (command:
next-hop-invariable)
Note: Only Cisco and Juniper devices are supported for eXpress Data Import. Import from NetCollector supports all vendor devices.
Carrier Supporting Carrier
Riverbed Modeler supports the carrier supporting carrier configuration, in which one MPLS VPN-based service provider leases a portion of its backbone network to another service provider. The traffic that is allowed on the backbone network is transparent to the leasing service provider.