An MPLS Layer 3 VPN creates a private IP
network. The customer connects to the network via customer edge (CE) routers, which act
as IP peers of provider edge (PE) routers.
Virtual Routing and Forwarding (VRFs)
On the PE, Virtual
Routing and Forwarding (VRF) instances act as virtual IP routers dedicated to
forwarding traffic for the L3VPN service. The VRFs learn the routes to each
other via the Multi-Protocol Border Gateway Protocol (MP-BGP), and then forward
traffic using MPLS.
A VPN is comprised of
at least one but typically several VRFs.
Cisco EPN Manager
uses the VPN ID to discover which VRFs together form a single VPN. If
Cisco EPN Manager
discovers an existing network where no VPN ID has been provisioned, it takes
all VRFs with the same name and associates them into one VPN. For VPNs created
using Cisco Prime Provisioning, which uses a naming convention with version
number prefixes and different suffixes,
Cisco EPN Manager
will recognize the different VRFs as belonging to one VPN.
In general there is a
regular expression which can be configured to allow for varying naming
convention.
Route Targets (RTs)
The connections
between VRFs are defined using Route Targets (RTs) that are imported and
exported by the VRFs.
Cisco EPN Manager
makes it easy to set up a full mesh of connections, and automatically allocates
the route target to be used. The route target consists of a prefix which is
either an AS number or an IPv4 address, for example, a full mesh prefix, 100
[681682]. The prefix can be selected from the existing BGP autonomous system
(AS) numbers in the network, or it can be entered manually. The second number
following the prefix is allocated automatically by
Cisco EPN Manager
.
Alternatively or in
addition to the full mesh, it is possible to manually select route targets.
During VPN creation, there is an initial screen where you type in the route
targets to be used within a VPN, and then for each VRF you can select which
route targets you import and export. You also specify for which address family
(IPv4 or IPv6) you will use the route target. This can be used for example to
configure extranets, by importing route targets used in other VPNs.
Route Redistribution
The routes that are
exchanged between the PE and the CE have to be redistributed into the MP-BGP
routing protocol so that remote endpoints can know which prefixes can be
reached at each VRF. To control route redistribution,
Cisco EPN Manager
allows you to define the required protocol (Static, Connected, or RIP), the
protocol's metric value, and optionally the applicable route policy.
Endpoints
Cisco EPN Manager
supports the creation of IP endpoints on Ethernet subinterfaces. It supports selecting untagged encapsulation, or specifying
an outer and optionally an inner VLAN, with 802.1q or 802.1ad encapsulation. You can specify both IPv4 and Ipv6 addresses
at an endpoint. You can also specify the BGP and OSPF neighbor details to provision BGP and OSPF neighbors between CE and
PE.
For information on how to provision L3VPN service using Cisco EPN Manager
, see, Provision L3VPN Services.