Home > CCIE Lab exam > CCIE R&S V4.0 Troubleshooting GNS3 Lab 1

CCIE R&S V4.0 Troubleshooting GNS3 Lab 1

Hi Everyone,

It is my pleasure to announce that I am publishing the first CCIE R&S V4.0 GNS3 TS lab in this post. I would first like to apologize for the delay. I know that many people have been waiting for this, so here you are.


As I have explained in my previous post, the topology used in the TS lab is based on the  INE GNS3 Lab1 topology and I would like to thanks personally Brian Dennis for letting me use it. The topology is perfect for practicing your TS skills. I would also like to thanks my friend Mark for helping me in building the labs.

This is the first TS lab and I will continue adding new ones. For running the lab you will need a powerful machine as there are around 30 routers in the topology ( I am running it on a PC with an Intel i7-3630QM CPU with 8 GB RAM and the CPU is around 30 %). An alternative will be to use Amazon Web services, see my previous post.

I attach all the files you need to run the lab.

I hope you will enjoy doing the lab. The difficulty of the lab is around 6-7/10.

The next labs will be published the following months.


Download the file HERE or HERE


The TS-LAB1.rar file contains the following:

  • Topology diagram: GNS3-TS-INE.png
  • GNS3 Lab file: TS-LAB1.net
  • Tickets: TS-LAB1-TICKETS.pdf
  • Answers: TS-LAB1-TICKETS-ANSWERS.pdf
  • GNS3 routers config files: Topology 1 Lab 1 Configs

To use the lab, just extract the TS-LAB.rar wherever you want. Then double clik on the TS-LAB1.net file. You should run the last version of GNS3.

You will need the IOS image to run the lab and it should match the following: c3725-adventerprisek9_ivs-mz.124-15.T13.image and must be located under C:\Users\Administrator\GNS3\Images (Otherwise change the path in the TS-LAB1.net file).

Edit  22/09/2013 16:00: There has been a problem with the file, I will correct it and upload again, sorry for that!
Edit  22/09/2013 17:00: The file is corrected and it should work now.
  1. September 21, 2013 at 21:27

    Thanks for sharing this and putting the effort in. Really appreciate it.

  2. Gabriel
    September 22, 2013 at 13:25

    Hi Laurent,

    From what I can tell, ticket 1 is already solved in your configs. In ticket 2, I cannot ping sw3 from sw4 or the other way around. I checked the solution and it does not apply to your config. I don’t want to go into more details because maybe I’m doing something wrong and don’t want to ruin the lab for others.

    • September 22, 2013 at 16:04

      Hi Gabriel,

      Thanks for your feedback, I will fix the issue and upload the file again.


    • September 22, 2013 at 17:11

      Hi Gabriel,

      I have corrected the file and it should be find. Try again and let me know.


  3. Gabriel
    September 23, 2013 at 01:40


    First ticket is ok now, but I’m still having trouble with the second one. At this point, I’m thinking maybe something’s off on my side. Perhaps others will provide additional feedback and we’ll see.

    Thanks for the lab!

    • October 7, 2013 at 15:11

      Hi gabriel,

      Have you solved your problem? Let me know what you think about the lab?


  4. leoaraujo79
    October 2, 2013 at 23:48

    The lab works fine on a c1.xlarge aws instance. Windows 2012

    • October 7, 2013 at 15:13

      Thanks for your feedback, what did you think about the lab?

  5. October 7, 2013 at 15:12

    Hi guys,

    Let me know what you think about the lab, could be nice to hear some feedbacks.

  6. October 15, 2013 at 18:17

    A great way to save resources when running this topology is to do the following (this is assuming that the ideal idle-pc value has already been found)

    * Open the .net file with a text editor. Using the “find and replace” utility, replace “ram = 256” for “ram = 128”. Be sure to do “replace all” so that all instances of this are changed. Save the .net file.

    Open the topology in GNS3 and boot the routers. Once the whole topology is booted, to the following:

    * Open the console to GNS3 (not a router, but the actual dynamips process) and type “idlepc idlemax /all 100” without the quotes. You should see your CPU utilization drop significantly. Be sure to save the topology after you make this change so that this setting is saved on the .net

    This is what I’ve done to run this topology in my desktop PC. I am running it with no issue and its running smoothly. My CPU is at about 5-10% with the topo booted, and console windows open to all devices. Using about 4GB of RAM total (I also have a couple of PDFs open and some browser windows as well).

    • October 17, 2013 at 08:04

      Thanks Pablo for this tip! What did you think about the lab?


      • October 17, 2013 at 10:22

        It was on par with the other INE TS labs that I’ve done. I have done the INE TS Lab 1 a bunch of times since I was able to do beta testing for their racks last year. I like what you have done with it =). Also, the layered diagram on the GNS3 window is very helpful.

        Thanks for your work.

      • October 17, 2013 at 11:10

        Sounds good Pablo, thanks for your feedback;-)


  7. Jeferson
    October 21, 2013 at 22:52

    I couldn’t download the file. Could you send me?

    • October 22, 2013 at 13:04

      The link is working. I have added another download link through Google Drive.


      • Jeferson
        October 22, 2013 at 15:32

        Thank you!

  8. October 28, 2013 at 10:23

    Thank you!
    Right in time!! exam is approaching 🙂 🙂

    • November 1, 2013 at 20:46

      Hope you will enjoy it!

      • November 5, 2013 at 21:50

        Well, I did :).
        Pretty cool scenarios (scenarii? :p). The format is quite similar to those ones from INE. I hope the exam will be pretty much close to this format.
        Thanks again for your efforts in making this running on GNS3 and for writing the very clear documents! It must have taken you a lot of time to make all of this.

        – BTW. You ve got me with the telnet quiet thingy in Ticket 3 🙂 I need to open my eyes wider.
        – Fixed ticket 4 with msdp and making R10 rp. but making SW2 DR was way simpler. Multicast 101 😦

        Mon lab est en 19 decembre. ca va etre chaud! Apparement ca serait ma seule chance avant la v5 hehe

      • November 10, 2013 at 09:57

        Thanks for your feedback. Yes it took me some time to make the lab but it is nice to hear that all of you guys enjoy doing it.
        Can you share your solution for ticket 4 so I can eventually add it to the ticket answers guide?

        Bonne chance pour ton lab en Décembre;-)


      • November 12, 2013 at 15:30

        Rack1R10(config)#do sh hist
        ip pim rp-address override
        ip msdp peer connect-source l0

        Rack1R7(config)#do sh hist
        ip msdp peer connect-source l0

        Rack1R11#ping sour f0/0 repeat 3
        [Output omitted…]
        Reply to request 0 from, 76 ms
        Reply to request 0 from, 104 ms
        Reply to request 1 from, 40 ms

        Rack1R11#sh ip mroute
        [Output omitted…]
        (*,, 00:02:02/stopped, RP, flags: SPF
        Incoming interface: FastEthernet0/0, RPF nbr
        Outgoing interface list: Null

        (,, 00:02:02/00:02:53, flags: PFT
        Incoming interface: FastEthernet0/0, RPF nbr
        Outgoing interface list: Null

        Rack1R10#sh ip mroute
        [Output omitted…]
        (*,, 00:01:47/stopped, RP, flags: SP
        Incoming interface: Null, RPF nbr
        Outgoing interface list: Null

        (,, 00:01:47/00:03:12, flags: TA <== MSDP SA generated
        Incoming interface: FastEthernet0/0, RPF nbr
        Outgoing interface list:
        FastEthernet0/1, Forward/Sparse, 00:01:47/00:02:41

        Rack1R7#sh ip mroute
        [Output omitted…]
        (*,, 00:09:48/stopped, RP, flags: SJCL
        Incoming interface: Null, RPF nbr
        Outgoing interface list:
        Loopback0, Forward/Sparse, 00:09:48/00:02:30

        (,, 00:00:10/00:02:57, flags: LMT <== Joined SPT after receiving an MSDP SA
        Incoming interface: FastEthernet0/1, RPF nbr
        Outgoing interface list:
        Loopback0, Forward/Sparse, 00:00:10/00:02:49

      • November 12, 2013 at 15:32

        Sorry for the formatting. No much possibilities…

  9. Ryan
    November 9, 2013 at 17:03

    Really good scenarios to run through. I really like the way you set this up. This is excellent. The only issue that hindered me was all of the vlan interfaces on the switches were up/down, so I wasn’t able to do much. I was able to run through about half of the tickets. It may be my IOS version as I don’t think I have the same version you used in this lab. Thanks for sharing this.

    • November 10, 2013 at 09:48

      Thanks for your feedback Ryan. Regarding the VLANs, it shouldn´t be an issue so yes try to eventually check the IOS version. I may publish the next TS labs soon;-)


  10. Simon
    November 9, 2013 at 21:52

    Nice labs, just posted a link to them on linkedin…hope that’s ok

    • November 10, 2013 at 09:40

      Thanks! I am glad that you liked the lab, I may post the other labs soon.


  11. Gustavo
    November 11, 2013 at 17:32

    Hey Laurent you are the Guy man !!! Thank very much for your patience on doing that, this shows that you are not a selfish person and that you will got a place in heaven for sure lol.

    If I pass the exam I´ll pay you some Stellas Artois OK ?

    Je vous remercie bcp mdr


  12. Joseph
    November 13, 2013 at 05:47

    Thank you !!

  13. Gustavo
    November 17, 2013 at 22:37

    BTW I could solve all the questions. The one that I spent much time was the multicast one……..really hard to troubleshoot. But that’s what we may expect on a real lab isn’t it ?

    Thank you Laurent

  14. M Fitzgerald
    November 19, 2013 at 09:26

    Hi Laurent,

    Really nice job here.

    I did Tickets 1 through 3 and they were quite good. There was nice balance of technical knowledge required for them and also several areas where you could waste time if you were careful.

    I liked the way you wrote Ticket 3 and the detail in the statement which had to be noticed.

    I ran it on Windows 2008 GNS3 0.8.6. I was able to tweak the topology file a tiny bit for my GNS3 setup easily. I added my own IDLE_PC and also I did the IDLE_MAX and I was able to run the whole lab at about 65%, which was no problem.

    It got me thinking that this would be a nice way for people in the CCIE community to come up with their own tickets to challenge each other.

    Thank you for taking your time to make something like this. Bravo.

  15. TS
    January 31, 2014 at 16:24

    I completed all of the tickets! I Really enjoyed the senarios. On number 8, I ended up with 65222 in the as path listing instead of 65111. I shut\no shut the SVI to 65222 and 65111 popped into the path listing. When can we expect more senarios?

  16. Homero
    February 1, 2014 at 23:02

    Hi Laurent, I went through the LAB, I appreciate the effort you placed on this, it looks very good. I hope you can release the next LAB soon. We all found this very helpful on our preparation for CCIE.

  17. Neil
    February 14, 2014 at 10:05

    Laurent, Great piece of work. I enjoyed ticket 6 particularly and the tricky OSPF/EIGRP route-map / distribute tweak..

    Would love to see more of these tickets based on this great lab setup.

    • February 14, 2014 at 19:15

      Thanks, I will try to make a new one soon.

  18. mohammed
    April 7, 2014 at 07:33

    dear Part
    do you think a CPU like intel i7 4820k can run such a topology ???


  19. Kieran
    May 18, 2014 at 17:44

    Hi Laurent,

    Top notch, got lab exam soon and this has really helped me focus.

    Managed to get them all, but spent longer than should have done on the BGP/VRF question.

    I’d be up for collaborating and writing some of these, be a great CCIE community excercise.

    merci beaucoup

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: