Articles

Print

MPLS VPN PE CE using RIP

Written by Rene Molenaar on . Posted in MPLS

Scenario:

You have been dreaming of starting your own ISP for years and now the moment is finally here. You bought a couple of brand new routers and you are about to implement your MPLS backbone. Your first customer has just signed a contract for connecting two sites so there is nothing stopping you. One of your routers will be the "P" router for the backbone. The other two routers will be used as "PE" router to connect the customer's end devices. Your customer is running RIP as their (IGP) internal routing protocol. Your backbone will use OSPF as the IGP....time to create your business!

Goal:

  • All IP addresses have been preconfigured for you.
  • Every router has a loopback0 interfaced configured as following:
    HQ: 1.1.1.1 /25
    PE1: 2.2.2.2 /25
    P2: 3.3.3.3 /25
    PE2: 4.4.4.4 /25
    BRANCH: 5.5.5.5 /25
  • Configure OSPF Area 0 at the provider side (Router PE1, PE2 and P).
  • Advertise the loopback interfaces as well in OSPF.
  • Ensure you have full reachability in the OSPF domain.
  • Configure MPLS on all physical interfaces in the service provider domain, do not configure MPLS on physical interfaces pointing towards the customer.
  • Configure VRF "customer" on PE1 and PE2 as following:
    RD 100:1
    Route-target both 1:100
  • On router PE1 and PE2 add the interfaces pointing towards the customer to the VRF you just created.
  • Ensure you can ping from within the VRF, try this as following on PE1:
    ping vrf customer 192.168.12.1
  • Configure RIP on router HQ and Branch. Advertise the loopbacks as well.
  • Make sure you use RIP version 2.
  • Disable RIP auto-summary.
  • Configure RIP on router PE1 and PE2 for the correct VRF "customer".
  • Ensure you receive prefixes from the customer routers on your PE routers.
  • Configure BGP AS 1 between Router PE1 and PE2.
  • Configure the correct BGP address families and make sure communities are sent between neighbors.
  • Redistribute RIP into BGP, use the correct address-family for the VRF "customer".
  • Make sure you keep the original metric for the prefixes.
  • Ensure you have full connectivity between router HQ and Branch. You should see each other's RIP routes that have been carried over the service provider's MPLS backbone.

IOS:

c3640-jk9s-mz.124-16.bin

Topology:

MPLS VPN PE CE RIP

Video Solution:

You need to a flashplayer enabled browser to view this YouTube video

You need to register to download the GNS3 Topology File. (Registration is Free!)

Related Articles
Only registered users can write comments!

Comments (6)

  • avatar
    talaltk

    good one for basic mpls config..keep it up 8)

  • avatar
    ReneMolenaar

    You can run the qemu host but can't set a default gateway?

    I think it's a normal linux host so you can set a default route on it using this command:

    route add 0.0.0.0/0 gw [insert gateway ip].

    If you want a host this is what I always do:

    1. Use a cisco router
    2. Type in "no ip routing" to disable the routing capabilities. This will turn it into a dumb host.
    3. Type in 'ip default-gateway' to configure a gateway on it.

    Voila...you have a dumb host with a default gateway to test ;D

    If you don't want to mess with Qemu but still want a host, try vmware workstation or virtualbox and run a Windows virtual machine in it. Use the "Cloud" icon in GNS3 to connect them to your routers.

  • avatar
    nadia

    hi... pleaaaaaaaaaaaaaaze i need a help

    how can i give a PC ip addrees ?? then connect it to HQ ?? in GNS3

  • avatar
    nadia

    thank you alot rene;)

  • avatar
    nadia

    i meant QEMU pc and to connect it to HQ (in GNS3) i download QEMO image and binary image but i can't give gateway>:(

  • avatar
    ReneMolenaar

    You can use the "cloud" icon in GNS3 to connect a physical network card to your router. You are better of using a router to "simulate" a pc to ping etc.