In this lesson we’ll take a look how we can use EIGRP as the PE-CE routing protocol for MPLS L3 VPN. If you already have seen my lesson for PE-CE RIP then you can skip to the “EIGRP between PE and CE routers” section as the configuration of the service provider network is exactly the same.

Here’s the topology we will use:


Above we have 5 routers. CE and CE2 belong to the customer who wants to run EIGRP between their sites. The service provider has two PE routers and one P router in the middle.



Let’s prepare the service provider routers. We need an IGP (OSPF) and LDP on the PE1, PE2 and P router.

PE1(config)#interface loopback 0
PE1(config-if)#ip address
P(config)#interface loopback 0
P(config-if)#ip address
PE2(config)#interface loopback 0
PE2(config-if)#ip address

Now we can configure OSPF:

PE1(config)#router ospf 1
PE1(config-router)#network area 0
PE1(config-router)#network area 0
PE1(config-router)#mpls ldp autoconfig
P(config)#router ospf 1
P(config-router)#network area 0
P(config-router)#network area 0
P(config-router)#network area 0
P(config-router)#mpls ldp autoconfig
PE2(config)#router ospf 1
PE2(config-router)#network area 0
PE2(config-router)#network area 0
PE2(config-router)#mpls ldp autoconfig

This takes care of IGP and LDP. Make sure you have LDP neighbors before we continue:

P#show mpls ldp neighbor | include Peer
    Peer LDP Ident:; Local LDP Ident
    Peer LDP Ident:; Local LDP Ident

Our P router in the middle has two neighbors so this is looking good. Just in case, let’s verify if there is connectivity between PE1 and PE2:

PE1#traceroute source loopback 0
Type escape sequence to abort.
Tracing the route to
VRF info: (vrf in name/id, vrf out name/id)
  1 [MPLS: Label 17 Exp 0] 0 msec 0 msec 4 msec
  2 0 msec 0 msec *

The PE routers are able to reach each others loopback interfaces and we are using label switching.

VRFs on the PE Routers

Our next step in the configuration is to configure the VRFs. I will use a VRF called “CUSTOMER”, the route distinguisher and route-target will be 1:1.

PE1 & PE2
(config)#ip vrf CUSTOMER
(config-vrf)#rd 1:1
(config-vrf)#route-target both 1:1

Don’t forget to add the interfaces facing the customer routers into the VRF:

PE1(config)#interface FastEthernet 0/0
PE1(config-if)#ip vrf forwarding CUSTOMER
PE1(config-if)#ip address
PE2(config)#interface FastEthernet 0/1
PE2(config-if)#ip vrf forwarding CUSTOMER
PE2(config-if)#ip address

Let’s check if the PE routers are able to ping the CE routers from the VRF:

PE1#ping vrf CUSTOMER
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to, timeout is 2 seconds:
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
PE2#ping vrf CUSTOMER
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to, timeout is 2 seconds:
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms

So far so good…

IBGP between PE1 and PE2

Our two PE routers require iBGP to exchange the VPNv4 routes. Let’s configure this:

PE1(config)#router bgp 234      
PE1(config-router)#neighbor remote-as 234
PE1(config-router)#neighbor update-source loopback 0
PE1(config-router)#address-family vpnv4 
PE1(config-router-af)#neighbor activate
PE2(config)#router bgp 234
PE2(config-router)#neighbor remote-as 234
PE2(config-router)#neighbor update-source loopback 0
PE2(config-router)#address-family vpnv4
PE2(config-router-af)#neighbor activate 

Before we continue we should check if our routers have formed an IBGP neighbor adjacency:

PE1#show bgp vpnv4 unicast all summary 
BGP router identifier, local AS number 234
BGP table version is 1, main routing table version 1

Neighbor        V           AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down  State/PfxRcd         4          234       5       6        1    0    0 00:01:03        0

Great, the BGP session has been established.

EIGRP between PE and CE routers

Here’s where things will be different. We will use EIGRP between the PE and CE routers. Let’s start with the CE routers:

CE1(config)#interface loopback 0
CE1(config-if)#ip address

CE1(config)#router eigrp 1
CE1(config-router)#no auto-summary 
CE2(config)#interface loopback 0
CE2(config-if)#ip address

CE2(config)#router eigrp 1
CE2(config-router)#no auto-summary 

The EIGRP configuration above is pretty straight forward. On both routers, I used AS number 1. At the end of this lesson I’ll show you what happens if you pick a different AS number for two sites.

Let’s configure the PE routers:

We're Sorry, Full Content Access is for Members Only...

If you like to keep on reading, Become a Member Now! Here is why:

  • Learn any CCNA, CCNP and CCIE R&S Topic. Explained As Simple As Possible.
  • Try for Just $1. The Best Dollar You've Ever Spent on Your Cisco Career!
  • Full Access to our 660 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)

503 Sign Ups in the last 30 days

100% Satisfaction Guaranteed!
You may cancel your monthly membership at any time.
No Questions Asked!

Forum Replies

  1. Hi Zeeshan,

    In an MPLS PE-CE scenario, you can use IGPs or BGP. Even static routes are possible.


  2. Hi Rene.
    Will you please advise me how do I advertise loopback I/F of PE1 to CE1?
    I have added

    PE1(config)#router rip
    PE1(config-router)#address-family ipv4 vrf CUSTOMER
    PE1(config-router-af)#version 2
    PE1(config-router-af)#no auto-summary 
    and even
    **PE1(config-router-af)#redistribute connnected**

    It seems the PE1 are not advertise its loopback to CE1.

  3. Hello Shang

    This behaviour is normal. Not only that, it is actually desired. The whole purpose of the MPLS Layer 3 VPN is to be able to create a transparent MPLS VPN between the two CE routers as if they are directly connected to each other. You’ve configured the Loopback to participate in the RIP routing, but you’ve also configured the ip vrf forwarding CUSTOMER VRF on the customer facing Fa0/0 interface and the mpls ldp autoconfig on the network facing interface. This will cause all additional network interfaces to be “inside the VPN” and not visible to t

    ... Continue reading in our forum

  4. Hello lagapides
    Thank you for your kindly explaination.
    I also find some hint in the next few lessons.

  5. Hello Viral,

    You’ll need an IGP so that your IBGP routers know how to reach each other. Here is an example:

    ... Continue reading in our forum

10 more replies! Ask a question or join the discussion by visiting our Community Forum