Service provider “StoryTellers” is intrigued by your performance so far, before they allow you to even look at their production MPLS backbone there is another lab they would like you to configure another lab. By using MPLS VPN’s it’s possible to send customer routes over the provider network. OSPF will be configured in the service provider domain (Router SP1, SP2 and SP3), the customer will be using EIGRP.


  • Configure all IP addresses as specified in the topology picture.
  • Configure a loopback0 interface on each router:
    HQ: /25
    SP1: /25
    SP2: /25
    SP3: /25
    BRANCH: /25
  • Configure OSPF Area 0 at the provider side (Router SP1, SP2 and SP3).
  • 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.
  • Force MPLS to use the loopback interface as router-id.
  • Configure VRF “customer” on SP1 and SP3 as following:
    RD 100:1
    Route-target both 1:100
  • On router SP1 and SP3 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 SP1:
    ping vrf customer
  • Configure EIGRP AS 100 on router HQ and Branch. Advertise the loopbacks as well.
  • Disable EIGRP auto-summary.
  • Configure EIGRP on router SP1 and SP3 for the correct VRF “customer”.
  • Ensure you have established a EIGRP neighbor relationship between Router HQ and SP1, and between SP3 and Branch.
  • See if you have learned routes by using “show ip route vrf customer”.
  • Configure BGP AS 1 between Router SP1 and SP3, make sure updates are sources from the loopback interface.
  • Configure the correct BGP address families and make sure communities are sent between neighbors.
  • Redistribute EIGRP into BGP, use the correct address-family for the VRF “customer”.
  • Redistribute the information from BGP back into EIGRP, use the following metrics:
    bandwidth: 64kbps
    delay: 1000
    reliability: 255
    load: 1
    MTU: 1500
  • Ensure you have full connectivity between router HQ and Branch. You should see each other’s EIGRP routes that have been carried over the service provider’s MPLS backbone.
  • Optional: Replace the Customer’s EIGRP with OSPF / RIP or BGP and achieve the same result.





Video Solution:

Configuration Files

You need to register to download the GNS3 topology file. (Registration is free!)

Once you are logged in you will find the configuration files right here.

Opt In Image
Do you want your CCNA or CCNP Certificate?

The How to Master series helps you to understand complex topics like spanning-tree, VLANs, trunks, OSPF, EIGRP, BGP and more.

Written by René Molenaar - CCIE #41726


  1. Profile photo of Doug says

    Do I understand correctly that is the broadcast address for subnet
    Also, is the subnet address for
    If so, how can these be assigned to interfaces? I keep getting “bad mask” errors when I try.

    For now, I will just use /29, and see how that goes…

    Report user
  2. Profile photo of Mr.Kd says


    Only i can download the topology.But i need the configuration of the each router.Can anyone share the configuration for the above topology as i am in need.
    Thanks in advance

    Report user
  3. Profile photo of Rene Molenaar says

    About the loopbacks, I messed up on that one…you are correct Doug. is a broadcast address. I changed the loopbacks all to /25’s, it doesn’t matter much what kind of address you have on the loopbacks.

    Frank, the download link is at the bottom of every article…below the topology picture.

    Mr.Kd, what kind of config would you like to see here? a basic config which has the IP addresses or a final configuration with the working solution? Right now I don’t supply any configs but I think I will in the future…it’s very time consuming to create ‘startup’ configs and ‘final’ configs as well.

  4. Profile photo of Mr.Kd says

    Hi Rene
    I am new to MPLS and so i just want to know how to configure MPLS for the above topology.So i request for the configuration so that i will get some ideas and i can create my own topologies.

    Thanks For Your Reply

    Report user
  5. Profile photo of Rene Molenaar says

    I did this one of top of my head, but it should be pretty accurate. I didn’t include the OSPF part for the backbone, just the MPLS.

    // SP1, SP2 and SP3 should have MPLS enabled on the interfaces towards each other…NOT to the customer!

    router (config)# interface f0/0
    router (config)# mpls ip

    // force MPLS to use the loopback’s router ID:

    router (config) mpls ldp router-id loopback0

    // now the VRF part. A VRF is like a ‘virtual routing table’, kinda like a VLAN but now for L3. Let’s create the VRF first, you need to do this on SP1 and SP3:

    router (config)# ip vrf CUSTOMER

    // now we setup the RD (route distinguisher) which is needed to make the customers prefixes unique in our MPLS VPN setup.

    Router(config-vrf)# rd 100:1

    // Next step is to configure the correct route-target. The RT is what ‘creates’ the VPN:

    Router(config-vrf)# route-target import 1:100
    Router(config-vrf)# route-target export 1:100

    // Now we need to add the interfaces pointing towards the customer into the correct VRF, do this on SP1 and SP3 (example is for SP1):

    Router(config)# interface f1/0
    Router(config-if)# ip vrf forwarding CUSTOMER
    // you need to reassign the IP address…but it will tell you.

    Try to ping the customer router from the VRF: (example SP1)
    // ping vrf CUSTOMER

    // Now you need to enable routing between the PE routers and the customer router, and we are using EIGRP. The difference is you need to specify the VRF when configuring EIGRP, this is how you do it:

    Router(config)# Router EIGRP 100
    Router(config-router)#address-family ipv4 vrf CUSTOMER
    // then add all the network statements there…

    // At this moment, you should have a working EIGRP between the SP and the Customer.
    // You should have MPLS running on the SP routers.

    // The next step is to get BGP going between SP1 and SP3, we’ll use multi-protocol BGP (MP-BGP) to get those prefixes to the other side. You don’t need to configure BGP on SP2!
    // example is for SP1

    Router(config)#router bgp 1
    Router(config-router)# neighbor remote-as 1
    Router(config-router)# neighbor update-source loopback0

    // we need to send community information:
    Router(config-router)# address-family vpnv4
    Router(config-router-af)# neighbor activate
    Router(config-router-af)# neighbor send-community extended

    // Now we want to get those prefixes to the other side, we need to redistribute from EIGRP to BGP and the other way around.

    Router(config)#router bgp 1
    Router(config-router)#address-family ipv4 unicast
    Router(config-router-af)#redistribute eigrp 100

    // and from BGP to EIGRP, remember that you NEED to supply the metrics for EIGRP!

    Router(config)# Router EIGRP 100
    Router(config-router)#address-family ipv4 vrf CUSTOMER
    Router(config-router-af)#redistribute bgp 1 metric 64000 100 255 1 1500

    That should be it, these commands should be enough to help you to complete the lab.

    Just keep in mind, MPLS itself is just a single command (mpls ip) but there is a lot of knowledge you need beforehand:

    – IP Routing
    – BGP
    – OSPF / EIGRP
    – VRF’s

    This might make it more difficult.

    I’ll create a video how to solve this lab real soon, this one seems to be popular…:)

    Good luck!

  6. Profile photo of Mr.Kd says

    Dear Rene
    I configured the same and working fine.But i have some doubts to clarify.

    Can you please explain,what is the use of RD and Route-Target and please explain using which criteria we assigned RD 100:1 and Route-Target 1:100.

    Please excuse if it is a silly question.

    Thanks in Advance

    Report user
  7. Profile photo of Rene Molenaar says

    No problem.

    The RD (Route Distinguisher) is to make a prefix “unique”.

    Let’s say you have Customer A and Customer B…and they both use the prefix then you have a problem.

    By adding a RD to the prefix you create a “unique” value.

    You can pick whatever number you like for the RD, i just made something up.

    The Route-Target is used to determine what prefixes you want to import or export, this is what makes the VPN.

    Let’s say you have Customer A and Customer B, they each have 2 sites.

    You can use RT 100:1 for Customer A so the 2 sites can talk to each other.
    Use RT 200:2 for Customer B so the 2 sites can talk to each other.

    Now let’s say Customer A and B want to connect to each other, they each have a HQ site and the 2 HQ’s need to be able to communicate with each other.

    You can create another RT, for example 102:12 and use it to let the HQ’s communicate with each other.

    If you try the Advanced MPLS lab it will make more sense :)

  8. Profile photo of Mr.Kd says

    Dear Rene

    Thanks a lot for ur xplanation.

    I just want to know

    using the above topology but with some modification like below

    SP1 >> Ethernet Switch >> HQ_A n Branch_B
    SP3 >> Ethernet Switch >> HQ_B n Branch_A

    If i make a scenario like this can i create 2 VLANS, 1 for HQ_A n Branch_A and the next VLAN for HQ_B n Branch_B in the SP1 n SP3.

    And For HQ_A n Branch_A routing protocol EIGRP
    and for HQ_B n Branch_B routing protocol RIP

    Will it works like this.Please suggest ur ideas.

    I think there is no modification in the P ie SP2.

    Please suggest and gimme some ideas to work it out.

    If everything goes fine shall i share the lab with the configuration over here.

    Thanks & Regards

    Report user
  9. Profile photo of Rene Molenaar says

    Hi KD,

    So if I understand correctly…you want to do this

    SP1 SWITCH vlan 10+20
    Connect HQ-A in Vlan10
    Connect Branch-B in vlan 20

    SP3 SWITCH vlan 10+20
    Connect HQ-B in vlan 20
    Connect Branch-A in vlan 10

    If you would build a trunk from the switch to the router and create sub-interfaces on the SP routers…that would work, but why would you want to do this? This isn’t something you would see or do in a real life situation..

    Keep in mind a switch is a layer2 vlan, and a VRF is kinda like a “layer 3 vlan”


  10. Profile photo of Alexey says

    [quote]Ensure you can ping from within the VRF, try this as following on SP1:
    ping vrf customer[/quote]

    This won’t work since we don’t have BGP yet. We should ping either from SP3 or .12.1

    BTW, thanks! You’re doing a good job.

    Report user
  11. Profile photo of JC.Bogard says

    /o all,

    From the start of the posts I noted a one side of a coin and then the other. I see that some issues were addressed with the “config” and then a video added. Hats off to Rene; I’ve been looking at topologies in manuals, books, PDFs and building from them and having to look up a log of stuff along the way. I have found many errors from Authors and I have learned a lot more by having to look things up to make it work. I lost several hours worth of study time from today this evening, but I then went the extra mile to ensure that I save my topologies correctly, as I will work on something and then switch over for a while due to something I read. It can be good to have config’s to compare against but I am really glad that when I download a lab I have to build out from the image.

    Rene, if you decide to add completed configs, can you still have it so we have to… well there is always write erase… wr reload ;).


    (very long day, pardon typos…)

    Report user
  12. Profile photo of Rene Molenaar says

    Hi Bogard,

    Seems you had a long day of labs :P

    About the configs..I’m trying to add a startup-config to make life easier, and a final config to compare your result against.

    Of course there’s always the video solution to follow your progress.

    Good luck :)


  13. Profile photo of Rene Molenaar says

    Hi Mr Kd!

    I’m doing fine thanks, I hope you as well :)

    I’ve been kinda busy with work so I didn’t have time for MPLS labs…if you have some topologies and tasks please send them over, i’ll wrap them into a nice article for the site!


  14. Profile photo of JC.Bogard says

    Speaking for myself… I would welcome more labs. The more the better. In response to Rene’s post regarding the start up config, I have several in as text files that I use for a always needed basics… if your using DHCP Pool & exclusions, router – EIGRP/OSPF/ect {AS#’s} XXXX. Line COn 0 settings… ect.

    Thanks again for the site,


    Report user
  15. Profile photo of David Taylor says

    Ok so I am new to this and would like to know how to get the IOS images to work. I have found a bunch of IOS .bin files and tried loading them into the GSN3 program but when I try to load the topology from the file above it tells me that my IOS files are in bad paremeter. Any ideas and where did you guys get yours??


    Report user
  16. Profile photo of jon says

    DT- really the only solution if you’re unable to get the same IOS version is to build the lab from scratch. I do the same thing with my labs. Doesn’t take too much longer…. :P

    Report user
  17. Profile photo of Rene Molenaar says

    The BGP configuration between SP1 and SP3 is a normal default BGP setup:

    router bgp 1
    no synchronization
    bgp log-neighbor-changes
    neighbor remote-as 1
    neighbor update-source Loopback0
    no auto-summary

    The only additional requirement is that you enable [b]address family VPN[/b] because you need the RD along with the prefix.

  18. Profile photo of Lev says

    it’s interesting to note when configuring the bgp vpnv4 send-community parameter that can appear an error message regarding the peering between bgp neighbors along the loopback interface. As i experienced the problem during the configuration i received a message like :”&#xBG;P-4-VPNV4NH_MASK : Nexthop may not be reachable from neigbor – not /32 mask”. After wonder around some possible causes of the problem i remembered that changing the ospf network type we can influence the appearance of the mask of loopback interface. As we were running ospf i changed that under lo0 and everything worked like charme.So bgp expect always an host mask to form neighborship over vpnv4 address-family and if we pass it a network mask the neighborship will fail anyway.

    Report user
  19. Profile photo of Rene Molenaar says

    Hi Lev,

    Quick question, on the routers where you saw this error you already had MPLS LDP enabled on the interface? If so…what happens when you disable MPLS and keep the /24 on the interface without changing the OSPF network type?


  20. Profile photo of Lev says

    Hi Rene,
    yes the mpls part was completed, and the behaviour is the same without mpls enabled. I’ve paid more attention this time to the error and i noted that the redistribution of eigrp into bgp trigger the notification. It’s like if eigrp routes before to reach bgp are influenced by ospf net-type. But i honestly can’t figured out why because until have no redistribution seems everything fine…what you think about it?

    Report user
  21. Profile photo of Ersan says

    Hi Rene,

    I m also not able to see the topology file. Is it a zip. file or sth else? i have downloaded topologies for some other labs like VRF-Lite but that one. Could you please have a look?

    Even if im already registered i only see this:

    [b]You need to register to be able to download the GNS3 Topology File. (Registration is Free!)[/b]


    Report user
  22. Profile photo of John Furlong says

    Hi, Firstly I’d like to thank you for this lab, the resources and the videos, they’ve been very helpful. I’ve been working through the lab solution on your videos and I’ve gotten right to the end of Part 3. However the final 2 pings don’t work for me. Even when I download the Final Configs from here, the last 2 pings don’t work for me. Does anyone know why? Or what I could do to check?

    I have been following the commands in the videos one by one and everything looks identical to your results e.g. if I run the “show ip route vrf CUSTOMER” command I get the same result as in the video. As I said it’s just the last two pings to ensure that the HQ and the Branch have end to end connectivity that is failing.


    Report user
  23. Profile photo of John Furlong says

    Apologies, I just loaded up the topology and the configs again, and the ping is working this time. It’s a bit of a mystery to be honest as I haven’t done anything differently from last time. At least it’s working now anyway, so thanks again!

    Report user
  24. Profile photo of Rene Molenaar says

    Hi John,

    There are a number of things to check when you are troubleshooting MPLS:

    1. Check the BGP adjacency between the PE routers.
    2. Check the VRF routing table and see if you can ping from the PE by using the VRF table (ping vrf
    3. Check the BGP and IGP (OSPF, RIP, EIGRP) table/database to see if your redistribution is ok.
    4. You can also check if there’s a label by using the “show mpls ldp bindings” command.

  25. Profile photo of Rene Molenaar says

    It depends on the ISP solution, it’s possible that you will get an Ethernet connection from the ISP to the customer.

    For some of the labs I chose FastEthernet because you won’t have any layer1 or layer2 issues. If the lab is about MPLS I don’t want people to start struggling with layer1 or layer2 frame-relay issues or anything else so they only have to focus on MPLS :)

  26. Profile photo of Rene Molenaar says

    This is a good example of a real MPLS network. This is what happens:

    – Within the MPLS “core” we will run an IGP like OSPF to advertise all the loopback interfaces.
    – All the PE routers will run IBGP to exchange routing information.
    – Beween the PE and CE (customer) routers you can use whatever routing protocol you like…OSPF, EIGRP but also BGP. It depends on the customer requirements.

    Keep in mind that whatever the customer advertises to you will be stored in a VRF (virtual routing table).

  27. Profile photo of White Rabbit says

    I notice that mostly all the labs use Fast-Ethernet or Ethernet for making connection would WAN links be a more realistic representation of ISP connections over distance to the Customer or is their a draw back to this approach ??

    Report user
    • Profile photo of Rene Molenaar says

      I use the Ethernet / FastEthernet links to keep things simple. In this lab I’m just focusing on the MPLS part and it would be bad if you also have to think about layer 2 issues with PPP, HDLC or Frame-Relay :)

  28. Profile photo of mobazi says

    Hi Rene,

    I would like to thank you for the free video lab’s. I took a look at all the labs. I wached the basic mpls vpn video and I appreciated so much that I tried to implment it in my own and it took me so much time to be able to do it.
    I have only a small feedback, namely when implementing the video’s. My remak is that you type very fast and ypu give very little explanation fo the command you are enering. I am CCNA and have a baisc MPLS and routing protocols and theri implementation.
    So, please try to have more time during you explanation especially for the beginners and your video’s will be very valuable and competitive. May thanks for help.

    Report user
    • Profile photo of Rene Molenaar says

      Hi Mobazi,

      Thanks for your kind words and comments. In my future videos I’ll make sure to type a bit slower and take my time to explain things. I do "assume" however that people have read/learned a bit about the background theory of the protocols because it’s hard to explain theory + the implementation at the same time :) I hope it’s helpful to you and i’ll do my best in the future!


  29. Profile photo of Yousuf says

    excellent LAB loved watching it….. Appreciation and thank you for the effort…. One thing I would like to notify here is I am not able to download the zip files attached to LAB can you please help….

    Report user
  30. Profile photo of Sheraz says

    Hi Gurus,
    I want to connect one Server with SP1 and one Server with SP3.Say server ips are (SP1-Server- and (SP3-Server- Do i need to add these networks to eigrp AS 100?. Actually i want to access these servers from hosts connected to Branch and HQ.

    Report user
    • Profile photo of Rene Molenaar says

      You will have to advertise these networks in EIGRP. They will be redistributed into BGP and forwarded across the MPLS backbone.

      You can test this by adding additional loopback interfaces on HQ and Branch and advertise these into EIGRP.

  31. Profile photo of evolution says

    [b]excellent lab matey..
    just had a question though.
    when i do a traceroute from either the HQ or the Branch, the MPLS backbone routers come up in the list.
    i did do a no mpls ip propogate-ttl forwarded but that didn’t help.

    i also did a no mpls ip propagate-ttl and that removed only one hop router from being show.

    default traceroute:


    Type escape sequence to abort.
    Tracing the route to

    1 132 msec 80 msec 52 msec
    2 [MPLS: Labels 17/22 Exp 0] 340 msec 464 msec 408 msec
    3 [MPLS: Label 22 Exp 0] 288 msec 268 msec 208 msec
    4 400 msec * 424 msec

    after running a no mpls ip propagate-ttl on all my mpls backbone

    Type escape sequence to abort.
    Tracing the route to

    1 184 msec 92 msec 40 msec
    2 [MPLS: Label 22 Exp 0] 204 msec 348 msec 408 msec
    3 308 msec * 720 msec

    how do i hide that second hop?
    cheers for the lab..

    edit: is this related to PHP that i am seeing this?

  32. Profile photo of evolution says

    thanks mate. let me try a php on the sp2 router and see what happens.
    lastly I had a question regarding the route target and rd.
    should the rd and the rt be unique in the whole mpls backbone domain? if yes, why?

    • Profile photo of Rene Molenaar says

      The RD (Route-Distuingisher) is used to make unique VPN routers. If multiple customers would use the network or something else then it’s the RD that makes a "unique" VPN route. If you would use the same RD number we could have duplicates so yes it should be a unique value.

      The RT (Route-Target) is used to import or export prefixes, it should be unique because otherwise you might import or export prefixes that you didn’t intend to.

      I think that sounds about right :)

  33. Profile photo of Ricardo Lainez says

    Hey, I had a bit of a hard time making this work and in the end it was because of a tiny difference in my configuration. Can someone help me understand the reason for this?:

    – When I first did all the configuration, I didn’t use the "ip ospf network point-to-point" on the PE loopback interfaces. The result was that there was no end-to-end communication between the customer sites.

    – I compared with the final configs and since this command was the only thing I was missing I thought I’d give it a try. Immediately after issuing the command on both sides, end-to-end communication started working perfectly!

    Can somebody explain to me why this happens? Thanks

    Report user
    • Profile photo of Ricardo Lainez says

      I might also add that although there was no end-to-end communication, route propagation was working (HQ routes were being propagated to the branch end) and PE-to-PE communication via the loopbacks was working as well. This made my troubleshooting a bit harder because I didn’t understand where the problem was.

      Report user
    • Profile photo of Rene Molenaar says

      It’s because OSPF by default ALWAYS advertises a loopback interface as /32. If you configure a /24 subnet mask on the loopback interface then there will be a mismatch. OSPF advertises a /32 while you have a label for a /24 network. Changing the network type to something else (not loopback) will make OSPF advertise the network as whatever you configured on the interface. Another option is configuring a /32 subnet mask on the loopback interface.

  34. Profile photo of Aditya says

    Hey Rene, I cleared my MPLS exam yesterday and used your labs to practice the concepts. Just want to thank you for providing this resource. Look forward to doing more such labs.


    Report user
  35. Profile photo of Matthew Nickerson says


    This is a well put together intro to MPLS, I’m loving it.

    I have a question. When configuring the vrf rd and route-target, you used 100:1 and 1:100 respectively. I have two questions:

    1. Do these numbers relate to OSPF PID and EIGRP ASN because they must, or because of convenience and simplicity? Put another way, do these numbers need to match the PID and ASN numbers to function.

    2. Could you explain the ordering (100:1 for rd and 1:100 for route-target) and is this also important?


    Report user
    • Profile photo of Matthew Nickerson says

      Ok, now I am seeing that you used EIGRP ASN 100 and 1 for the customer and provider processes, respectively. I think get it. It has nothing to do with the OSPF process–that’s just for provider internal connectivity…I’m stupid!

      I’m thinking that the vrf rd and route-target commands are telling the router to "translate" or "connect" the customer’s EIGRP PID 100 into the internal provider EIGRP PID 1 and vice versa. Correct?

      Report user
      • Profile photo of Rene Molenaar says

        It’s more of a coincidence that I picked these numbers. The RD (Route Distinguisher) is used to add "something extra" to a prefix so that it’s 100% unique. We do this in case customers have the same prefix. By adding the RD it’s a "unique prefix".

        The RT (Route Target) is kinda like a label…it helps us to select what we want to import/export.

  36. Profile photo of Bobi says

    Hi Rene,

    I’m new to GNS3, and I have some basic questions :)
    Did you use the same type of routers (c 3600) in this lab with image c3640-jk9s-mz.124-16.bin ? I’m asking this because I read somewhere that to configure MPLS VPN we need at least C7200 for PE routers.


    Report user
    • Profile photo of Rene Molenaar says

      Hi Bobi,

      I used the C3640 images, they can run MPLS without any issues. Maybe some features like xconnect (pseudowire) can only be done on the 7200 routers.

      If you want to see what routers I used, just open the file in notepad/wordpad and you’ll see the IOS image.


  37. Profile photo of Nikhil says

    Hi Rene,
    This is a very good lab and I loved doing it. Thanks to preconfigured routers, which was usually much of a pain in each lab.
    Also, I can see the routes being exchanged across the MPLS cloud and see them in the routing tables of the customers HQ and branch, however I’m not able to ping them. Even not able to ping the learnt routes from the PEs.

    Did some troubleshooting, but in vain., Any clues?

    Report user
  38. Profile photo of David Kypuros says

    Any ideas why I am getting (tdp) for my default instead of (ldp)? Why am I getting "Tag switching has not been enabled."?

    I followed the lab exactly as it is shown on youtube. Hmm

    I am on Video 1/3 on youtube (8:21). I am trying to get MPLS enabled properly on SP1, SP2, SP3.


    Report user
    • Profile photo of Rene Molenaar says

      There’s LDP and TDP. TDP is the Cisco labeling protocol if I’m correct. It probably depends on the IOS version that you are using which one is the default. You can change it however.

      I think if you go the interface level you can change it with the "mpls label protocol" command.

  39. Profile photo of David Kypuros says

    I found that even when I started the lab using a different 3640 IOS than the one mentioned in this article, the MPLS IP command didn’t work so well.

    I went back, used the EXACT IOS in your article, and build a brand new GNS3 project, then everything worked perfectly.

    Report user
  40. Profile photo of Henry Mwanzia says

    When i tried the above lab, my BGP doesnt peer – even after stripping it – see below
    router bgp 1
    no synchronization
    bgp log-neighbor-changes
    neighbor remote-as 1
    neighbor ebgp-multihop 30
    neighbor update-source Loopback0
    no auto-summary
    Connectivity test —- SP1#traceroute source

    Type escape sequence to abort.
    Tracing the route to

    1 20 msec 60 msec 20 msec
    2 16 msec 36 msec *
    SP3#traceroute source

    Type escape sequence to abort.
    Tracing the route to

    1 24 msec 24 msec 28 msec
    2 20 msec 36 msec *
    router bgp 1
    no synchronization
    bgp log-neighbor-changes
    neighbor remote-as 1
    neighbor ebgp-multihop 30
    neighbor update-source Loopback0
    no auto-summary

    Regarding the EIGRP configuration for the VRF, does the difference in AS number for customer and PE router matter ? e.g from the video you configured eigrp AS 1 and on the VRF you configured AS number 100. what if i configured AS100 for PE router and 100 for customer AS on the address family

    Report user
  41. Profile photo of Dinesh says

    I have some queries going through video solution. Please take your effort to clear my doubts.

    what is difference b/w Route Target Both command and route target export and Import both commands in the router. Because u used Route target both on SP1 and route target export as well as import in SP3, can we use route target both on same router and what effect will gave only export or import on SP routers

    2nd Question.


    u create address-family vpvn4 under BGP, what effect will it take address-family vpvn4 unicast of SP routers?

    3rd question

    on SP1 u created neighbour send-community both
    SP3 u created neigbour send-community extended..

    what is difference of this two.. why cant we use send-community both on SP3 is well..

    Please explain these 3 question.. on each function(export,import,extended and both as well unicast) key command i asked queries..

    Report user
    • Cherkuas says

      I also did the Lab using 7200 IOS image and U will not find the ‘autonomous-system ‘ command form the list…just type the whole command manually and enter. the command will be accepted.

  42. Profile photo of Mark Ferrara says

    Hi Rene,
    Thanks for a great lab.
    Can I ask why the SP needs to run BGP and peer the 2 PE routers with iBGP in order for the customer connectivity?
    Could it just work by redistributing EIGRP into OSPF already running?

    Report user
  43. Profile photo of Donald says

    Hi Rene

    Thanks for all the lessons, I think you might have used a wrong gns3 topology for this lab.please double check this. The lab topology that is shown here and the one that is downloadable for gns 3 are different and hence one cannot do the lab. Thanks!

    Report user
  44. Cherkuas says

    Awesome tutorial…..Had a good understanding of MPLS and was looking for some conf examples.
    Your toplogy and explanation was ver helpful. Keep up the good work. Looking forward to the other advanced MPLS stuff on your website :)

  45. Nemat says

    Dear Rene,

    i becoming a big fan of you. You are doing really impressive job. God bless you brother and keep the nice job.

    Besides, are there any other uploads coming like Advanced MPLS

  46. Kenny says

    Great labs.. also great explanation… keep up the good work!!

    However.. whta perhaps will be handy.. is to post the configs of all the routers also..
    because.. now i first watch you’re video’s want to build it myself also to test..
    and sometimes misses some config command…

    then i only have to check to configs again to see what it was…;)

    Perhaps you can think about it..



  47. Kenny says

    Hi Rene,

    Yes indeed.. i mean the final configuration… that would be helpful..

    now i’m trying to configure it.. and when i forgot something i have to watch the video’s again :P

    Then i can just take a look at the configs what i forgot to type.



  48. Profile photo of Kenny says

    Hi Rene,

    Got it working now… ;)

    i forgot to redistribute the eigrpo traffic back into the bgp.. :P

    however… i was also trying the same topology with static routes from the CE routers..

    with the command on the PE redistribute static and redistribute connected.. also created an ip route vrf on these PE routers… however… it seems that the static and or default routes won’t show up in the vrf ip route table…..

    so the PE router can reach my ip adress learned from the BGP but cannot reach the loopback addresses on my CE routers… just because these routes aren’t in my vrf routing table…

    how can i solve this? or is this just not possible?



    Report user
  49. Profile photo of Mazhar says

    Well….from my side only routes available in SP3 and branch……….not getting all route updates in SP1 and HQ……any idea why SP3 and SP1 are not exchanging routes though they are bgp neighbors?

    Report user

Leave a reply:

Your email address will not be published. Required fields are marked *

If you have any technical questions, please use the Forum instead of posting a comment.