BURST: INE RS v5 base topology with Cisco VIRL

I have uploaded and attached the VIRL file I have made for my studies. It is the ground floor topology that allows potential CCIEs like yours truly to get their hands dirty. To be used in conjunction with the INE paid workbooks or labs this topology is updated for v5. INE has moved to a virtual infrastructure with switches for their topology in alignment with the industry.

I had noted there was a lot of labs that didn’t adjust or alter the interfaces on switches themselves and therefore have represented them with multi-point connected networks. Whilst there is L2IOS within VIRL at this stage I have not dug deep enough to navigate the nuances of the image. So far I have done a lot of the routing labs without any hiccups.


Here is an image of the basic topology too. This topology has different interfaces than what is listen in the lab guides and startup configurations. Simply adjust the boot configuration if you’re loading the INE configuration.

What is great is that I know if any issues are occurring that is due to my configuration and not because of some black magic to get IOS to work. The problem I had with GNS3 is that I would waste valuable study time in tweaking and adjusting my lab due to issues with GNS3. Once you get your hands onto Cisco VIRL or Cisco Modelling Labs then you can use this file!

Here is the INE package that I use. 

Here is the file for VIRL.


10 thoughts on “BURST: INE RS v5 base topology with Cisco VIRL”

    1. this is my INE lab virl file (up to 20 routers but can be cut down to 10) , i also included a patch i did in order to be able to add inline configuration within virl file using vmcloud from the cisco OnePK VM..

    2. hi Adel

      friend your topology looks cool but i am confused a bit about your statement that its used on one-pk all in one virtual machine or i miss interpret as its virl topology only simple import your topology in virl and start labbing.please explain bit more how do i use your lab.

      there is one inline patch folder what it is all about and what do u means inline…………..sorry new to virl so might not aware about virl complete feature hope u help me out and explain things bit more

  1. Just curious, what is your machine specs and which hypervisor are using for VIRL? How many routers/switches are you able to run?

    I’ve been jumping between IOU and GNS3 for my studies, but the time I’ve spent troubleshooting problems related to both platforms just come to a point where I spent a considerable amount of time on that, instead of actually focusing on the technologies.

    Don’t get me wrong, they are OK tools for mini lab scenarios, something quick and dirty but anything a little more complex is always a pain in the butt, and consider yourself luck if can make it through a whole study session without having any issues.

    There’s no proper substitute for vendor rack sessions yet.

    I hope VIRL finally be able fill this gap.

  2. How does the layer 2 switching work into this VIRL file? Also the file needs to be updated for the latest version has multipoints no longer exist and need to be replaced with unmanaged switches.

    1. Yep. It was made for an older version of VIRL before L2 IOS was included.

      I may get time to update it soon.

      1. Hi,

        Did you ever get around to updating this? I have VIRL and am using INE R&S v5 workbook and would like to avoid the headache of rebuilding this if you have it done already.

        Much Thanks!

        1. Hi Robert,

          No I haven’t yet sorry. It is pretty easy to rebuild though. You can make one L2 segment and attach all the routers to it and then just use logical connectivity between all the nodes.

          I am getting back into VIRL later in the year.

Leave a Reply

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