GNS3 Network Simulation Lab: Install and IOS Images

GNS3 emulates real device firmware rather than simulating a device's behaviour, which is why it reproduces the odd protocol quirks that Packet Tracer quietly fixes for you. The cost is a heavier install: a GUI on your workstation, a VM that actually boots the images, and licensed images you supply yourself. This guide covers a working setup order, the settings that prevent the most common failures, and how to know when a lighter-weight tool would serve you better.

Hardware and Virtualisation

Hardware virtualisation must be enabled in firmware - Intel VT-x or AMD-V. If the GNS3 VM silently fails to start, this is the cause in the overwhelming majority of cases. Verify from Task Manager (Windows) or egrep -c '(vmx|svm)' /proc/cpuinfo (Linux) before troubleshooting anything else.

Installation Order

1. Install the GNS3 GUI, which also offers to pull in Npcap, Wireshark, Dynamips and VPCS.
2. Install VirtualBox or VMware Workstation, then import the GNS3 VM appliance from the matching .ova.
3. Run the GNS3 setup wizard and choose to run appliances in a virtual machine.
4. Confirm the wizard's connection test to the VM.
5. Add device images and templates.

The GUI and the VM versions must match. A mismatch produces a connection that appears configured but never establishes, which is a frustrating rabbit hole to debug from the symptom alone.

Adding Device Images

GNS3 ships no Cisco IOS images for licensing reasons - you supply your own from a valid source such as a Cisco support contract download, the DevNet sandbox, or hardware you own. Place images in the GNS3 images directory and add a template:

# Linux and macOS
$HOME/.gns3/images/IOS/
# Windows
%APPDATA%\GNS3\images\IOS\

# In the GUI: Edit -> Preferences -> IOS routers -> New
#   name:        Cisco-7200-15.6M
#   image:       c7200-adventerprisek9-mz.156-2.SP.bin
#   platform:    c7200
#   RAM:         512 MB or more

When the wizard asks about decompressing the image, accept it - GNS3 needs the decompressed form. Rejected images are usually .tar or .bin.gz files rather than the plain .bin the platform expects.

Idle PC: The Setting That Fixes CPU Load

Without an idle PC value, each emulated router consumes a full CPU core even when idle. Right-click a running router and choose Auto Idle PC, accept a suggested value, and apply it to the template so every future instance uses it.

Common Failures and Their Causes

• GNS3 VM will not start - virtualisation disabled in firmware.
• Blank console - no idle PC value, or the image is still booting in the background.
• NM-16ESW errors - the VM has less than 4 GB of RAM.
• Cannot reach the internet from a lab node - the NAT cloud is not connected to the VM, or the VM's own interface is not bridged.
• Nested virtual appliances fail - enable nested virtualisation for the GNS3 VM in the hypervisor settings.

Lab Design Discipline

Keep a template library for the three or four platforms you actually use rather than a folder of every image ever obtained, mirror the interface naming of production (Ethernet1/1 versus GigabitEthernet0/0 changes how muscle memory transfers), and give every link a description. Snapshot the working topology before each experiment so you can return to a known-good state rather than rebuilding. For lighter alternatives that boot in seconds and live in version control, see Containerlab multi-vendor network labs and EVE-NG installation and lab guide.

原文链接：https://www.gns3.com/software/download