MPLS VPN Overview
MPLS VPN Overview
date_range30-Jul-19
info_outline Platform and Release Support
Virtual private networks (VPNs) are private networks that use a public network to connect two or more remote sites. Instead of
dedicated connections between networks, VPNs use virtual connections routed (tunneled) through public networks that are typically
service provider networks. VPNs are a cost-effective alternative to expensive dedicated lines. The type of VPN is determined by the
connections it uses and whether the customer network or the provider network performs the virtual tunneling.
You can configure a router running Junos OS to participate in several types of VPNs. This topic discusses MPLS VPNs.
This topic contains the following sections:
There are three primary types of MPLS VPNs: Layer 2 VPNs, Layer 2 circuits, and Layer 3 VPNs. All types of MPLS VPNs share
certain components:
The provider edge (PE) routers in the provider's network connect to the customer edge (CE) routers located at customer
sites. PE routers support VPN and MPLS label functionality. Within a single VPN, pairs of PE routers are connected
through a virtual tunnel, typically a label-switched path (LSP).
Provider routers within the core of the provider's network are not connected to any routers at a customer site but are part
of the tunnel between pairs of PE routers. Provider routers support LSP functionality as part of the tunnel support, but do
not support VPN functionality.
CE routers are the routers or switches located at the customer site that connect to the provider's network. CE routers are
typically IP routers, but they can also be Asynchronous Transfer Mode (ATM), Frame Relay, or Ethernet switches.
All VPN functions are performed by the PE routers. Neither CE routers nor provider routers are required to perform any VPN
functions.
Route Distinguishers
Because a typical transit network is configured to handle more than one VPN, the provider routers are likely to have multiple VRF
instances configured. As a result, depending on the origin of the traffic and any filtering rules applied to the traffic, the BGP routing
tables can contain multiple routes for a particular destination address. Because BGP requires that exactly one BGP route per
destination be imported into the forwarding table, BGP must have a way to distinguish between potentially identical network layer
reachability information (NLRI) messages received from different VPNs.
A route distinguisher is a locally unique number that identifies all route information for a particular VPN. Unique numeric identifiers
allow BGP to distinguish between routes that are otherwise identical.
Each routing instance that you configure on a PE router must have a unique route distinguisher. There are two possible formats:
as-number:number, where as-number is an autonomous system (AS) number (a 2–byte value) in the range 1 through
65,535, and number is any 4–byte value. We recommend that you use an Internet Assigned Numbers Authority (IANA)-
assigned, nonprivate AS number, preferably the ISP or the customer AS number.
ip-address:number, where ip-address is an IP address (a 4–byte value) and number is any 2–byte value. The IP
address can be any globally unique unicast address. We recommend that you use the address that you configure in
the router-id statement, which is a public IP address in your assigned prefix range.
The route target defines which route is part of a VPN. A unique route target helps distinguish between different VPN services on the
same router. Each VPN also has a policy that defines how routes are imported into the VRF table on the router. A Layer 2 VPN is
configured with import and export policies. A Layer 3 VPN uses a unique route target to distinguish between VPN routes.
The PE router then exports the route in IBGP sessions to the other provider routers. Route export is governed by any routing policy
that has been applied to the particular VRF table. To propagate the routes through the provider network, the PE router must also
convert the route to VPN format, which includes the route distinguisher.
When the outbound PE router receives the route, it strips off the route distinguisher and advertises the route to the connected CE
router, typically through standard BGP IPv4 route advertisements.