| Image type | Features included | |------------|-------------------| | ipbasek9 | Basic IP routing, static routes, RIPv2, basic OSPF/EIGRP | | ipservicesk9 | Adds MPLS, VRF, L3VPN, multicast | | adventerprisek9 | Adds advanced security (ZBFW, GET VPN), PfR, advanced QoS, DMVPN | | adventerprisek9_with_services | Similar but includes service provider features like L2TPv3 |
: Indicates the architecture. The i86 means it is compiled for Intel/AMD x86 platforms, and bi signifies a "built-in" or Unix-native binary format.
In the field, click Browse and select the i86bi-linux-adventerprisek9-ms.154-1.t-antigns3.bin file from your local machine. GNS3 will automatically upload the binary to the correct directory inside the GNS3 VM. Select L3 Image as the Type. Click Finish . Step 2: Configure the IOU License ( iourc ) i86bi-linux-adventerprisek9-ms.154-1.t-antigns3.bin
: IOU images require a license key (an iourc file) to run. This is usually generated based on the hostname of the virtual machine running the simulation.
: Most people use the GNS3 Documentation or EVE-NG Guides to import these images. Important Note GNS3 will automatically upload the binary to the
Because it is a 32-bit x86 Linux application, it must run inside a Linux environment. Most engineers use the or EVE-NG bare-metal/OVA deployment (which runs Ubuntu). If running on a 64-bit Linux architecture, you must install 32-bit compatibility libraries ( ia32-libs or lib32z1 ) to prevent "file not found" errors when executing the binary. 2. File Permissions
Because these files are built for Linux architectures, they must be hosted inside a Linux environment. Windows and macOS users should deploy them using the official GNS3 VM or EVE-NG virtual appliances. IOU images - Community | GNS3 Step 2: Configure the IOU License ( iourc
The i86bi-linux-adventerprisek9-ms.154-1.t-antigns3.bin is often preferred over Cisco IOU (IOS on Unix) or Dynamips images for several reasons: