nickelito wrote: » Hi guys, Im taking the CCNP TSHOOT exam this friday which will be the last one in the series for me. I feel like I've studied enough for that exam already, so I was just thinking why not start planning for whats next instead of wasting time just sitting around and waiting And yes, it is R&S I am planning to go for
nickelito wrote: » Thank you, I realized that the link provided above has info about that. Ultimate also lets you download the content. Anyways, what is the advantages of getting VIRL instead of just using IOU in GNS3? To me it looks just like an expensive gui when you compare them, plus more demanding hardware requirements.
fredrikjj wrote: » Easier config management. If you're looking at using INE's workbook, a big plus with VIRL is that you can just import all labs with configs already set up, and just boot them as you go. On the other hand, using CSR1000v has advantages too in terms of config management because you can upload every single config to the device and then use 'configure replace' to change labs.
gorebrush wrote: » IOSv is pretty awesome - when I started though it was pretty early on in the development and INE were recommending the CSR as it was production grade code - you don't want to be faffing around with software glitches when you are trying to study. However, the 512MB per instance is a lot easier than CSR's at least 2GB minimum. Running 20 of them was quite the challenge but I did manage with 32GB RAM and Memory Page sharing.
EANx wrote: » You don't need an eight-core processor, a four-core would be fine. While I have a six-core processor, my VIRL VM runs with six-threads (rather than the max of 12) and up to 48 GB of RAM. I've never hit 100% utilization on either, even when booting 10 IOSv routers and 10 IOSvL2 switches at once. When I boot them all at once, it takes about 2.5 minutes to boot from the time I start until #20 is active. While I think processor and RAM are important, once you have four cores and 16 GB RAM, I think you get the best performance boost by having the VM on an SSD.