3. CCNP TSHOOT
Self-made labs covering almost all aspects of the exam, including 2 versions of the final exam topology.
4. CCDP ARCH
Self-made BGP Route Reflectors and Confederations lab
5. CCNP-Security FIREWALL
Self-made lab, with ASAs and ASDM.
6. CCNP-SP SPADVROUTE
Self-made IPv6 MP-BGP, DHCPv6 and IPv6 Multicast labs.
7. CCNP-SP SPEDGE
Self-made DMVPN Phase II lab.
8. CCNP-SP SPROUTE
Self-made CSR 1000V EIGRP and L3 EtherChannel labs
A few tips:
The ➣ latest GNS3 version is out,
I have setup➣
PPA
PPA &
DR
DR repositories that should come in handy if you respectively use the latest Ubuntu or
Debian release and you need to keep up with the latest releases of packages, which are not available on the
official Canonical-Ubuntu repositories:
✔ GNS3
✔ KVM
✔ Wireshark
✔ many more
You might want to watch some tutorials on Youtube on how to start with GNS3,➣
You'll need to ➣ bring your own images:
✔ IOS (mostly 3640, 3725 and 7200) images for some dynamips nodes,
✔ Licensed images (except for NX-OSv-9k) can be imported from within VIRL as qemu nodes :
✔ IOSv,
✔ IOSv-L2,
✔ CSR-1000v
✔ NX-OSv
✔ IOS-XRv
✔ IOS-XRv-9k
✔ ASAv
✔ Free images are available here:
• CSR 1000V: free IOS-XE 3.14 image
• IOSv: free IOS 15.4 image
All the ancient labs topology.net are loadable as is by GNS3 up to version 0.8.7 and will be ➣
automatically converted to a new format (<project name>.gns3) with version 1.2.1+ up to 1.5.4. They
cannot be opened by versions 2.x.
All the <project name>.gns3 can be opened by GNS3 1.5.4 → 2.x.➣
All the topology.net and <project name>.gns3 can be loaded with GNS3 / Windows.➣
All the topology-linux.net and <project name>-linux.gns3 can be loaded with GNS3 / Linux➣
There is no need to “import project” in most recent 2.1+ gns3 releases. Opening the .gns3 project file is ➣
enough to be converted into 2.x format.
All the VPCS hosts configurations can be loaded with PCn.cfg➣ ; for example, PC1 configuration is loaded
with PC1.cfg.
➣ All Qemu project files (located in <project name>/project-files/qemu/<node-uuid>/hdx_disk.qcow2) are
based on a “backing file” (qemu node image file) with its path hard-coded into the hdx_disk.qcow2.
You may need to adapt the hard-coded path to your own environment with a script that I've provided
for Linux users: qemu-rebase-image-path-for-hdx-disk.qcow2.sh (read the script header for tutorial).