GNS3 Setup and demo test on Windows

Prerequisites:

- GNS3 Installation Package 

- Internet Operating System(IOS) Image for certain model of devices.


For this test, we use this stable version, instead of the beta version since the beta version wasn't able to boot virtual machine on my PC. 

GNS3 Setup and demo test on Windows

After finishing the installation guide, switch to setting properties: Follow the arrows: 

GNS3 Setup and demo test on Windows

Configure Dynamips: 

GNS3 Setup and demo test on Windows

Configure Qemu, which is a powerful plantform emulator. 

GNS3 Setup and demo test on Windows

After testing the virtual engines, configure the system images: Make sure the configuration is paired with your IOS image. Here in my sample, the image is model2691. 

GNS3 Setup and demo test on Windows

GNS3 Setup and demo test on Windows

Now you can drag the paired route device for test! 


 Due to the fact that we sometime only have one image for primitive test, we can use one IOS image to emulate varieties of devices. Becauese these devies, shallow, short sighted, are similar at software system, only have differences in hardware slots. As a result, we can just configure some of the "routers" to convert them to other devices including Switchers of PCs.

GNS3 Setup and demo test on Windows

GNS3 Setup and demo test on WindowsGNS3 Setup and demo test on Windows

For PC, needless to configure slots, changing the symbol icon is fine. 

GNS3 Setup and demo test on Windows

With this strategy, we can build this topography below: 

GNS3 Setup and demo test on Windows

Click the green START button on the top to boot up the network topography! Then right click each device to connect the console port to set up each devices! Enjoy :) 

GNS3 Setup and demo test on Windows

GNS3 Setup and demo test on Windows

GNS3 Setup and demo test on Windows


Tips:

If you wanna use third party's *.net files, and you meet the 203- Error. We should ensure the needed files are definitely located in the indicated path. Even the program lied to you that it changed the directory, because it didn't... Solve this problem by creating related folders or symbolic links with mklink command.

GNS3 Setup and demo test on Windows

GNS3 Setup and demo test on Windows