Table of Content

  1.  MPLS Layer 3 VPN PE-CE RIP
  3. MPLS Layer 3 VPN PE-CE OSPF Configuration
  4. MPLS Layer 3 VPN PE-CE OSPF Sham Link Configuration
  5. VRF Lite Route Leaking
  6. MPLS VPN Extranet Route Leaking
  7. MPLS-VPN VRF Export-Map
  8. MPLS VPN VRF Import Map
  9. Any Transport-Over MPLS (AToM)
  10. IP version 6 over MPLS 6PE/6VPE


This eBook is based on Multiprotocol Labeling and Switching that has been collected from different sources and people. For more information about this ebook. Kindly write to I will happy to help you.

Copyright 2023 by Poonam Devi

This eBook is a guide and serves as a next part of first guide.
Previous Part MPLS Made Easy Part-1 has already been published. This book has been written on the advice of many experts and sources who have good command over MPLS, network an programming. They are listed at the end of this book.
All images used in this book are taken from the LAB which is created by experts. All rights reserved, including the right to reproduce this book or portions thereof in any form whatsoever. For any query reach out to the author through email.


In my previous lessons I explained the basics of MPLS L3 VPNs and I explained in detail how to configure it. This time, we are going to configure MPLS VPN PE-CE with RIP as the routing protocol between the customer and service provider.

RIP is a simple routing protocol and easy to implement with MPLS VPN. Here’s the topology we will use:


This is the same topology that I used in my previous examples. Let’s see what the configuration is like…



We will start with the configuration of the service provider network, we’ll have to configure an IGP (OSPF) and LDP on the PE1, P and PE2 router. Let’s add some loopbacks that are required for LDP:

This time I used the mpls ldp autoconfig command to automatically enable LDP for all OSPF enabled interfaces. Let’s do a quick check to see if LDP is enabled:

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 *

PE1 and PE2 are able to reach each other and you can see 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

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:

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.

RIP between PE and CE routers

The only thing left to do is to configure RIP between the PE and CE routers. Let’s start with the CE routers:

The CE routers use regular RIP, nothing special here. Now we will configure the PE routers:

Since the customer is in the VRF, we have to configure RIP not for the global routing table but for this particular VRF. This is done with the address-family, the rest of the configuration is the same. Let’s do the same on PE2:

The PE routers have learned the networks from the CE routers. Now there’s only one thing left to do…somehow


Publisher: BookRix GmbH & Co. KG

Text: Poonam Devi
Images: Poonam Devi
Cover: Uttam Singh
Editing: Devesh Patel
Proofreading: Rishabh Jain
Translation: Devesh Patel
Layout: Richa Shukla
Publication Date: 10-08-2023
ISBN: 978-3-7554-5542-4

All Rights Reserved

Next Page
Page 1 /