I fell like this is a limitation of the GNS3 VM as I have tried to create VLAN interfaces and / or bridges in netplan for eth0 but that seems to break it as well. I have deployed GNS3 VM 2.1.11 on an ESXI host using Vcenter 5.5.
We have read up on how to configure trunking in ESXi and it works to other devices (PAN-OS-VMs) but not GNS3.
GNS3VM InstallationĪssuming you have your ESXi host up and running, download the GNS3VM and import the virtual machine onto your ESXi host. I have to restore snapshots (THANK YOU SNAPSHOTS) to restore connectivity. Install Windows Server, add a new vNIC to the same port group that you created for the GNS3 VM, and enable Terminal Services. Upon launching the desktop GNS3 client, you would seemingly be unaware that the topologies were actually be processed by a remote GNS3VM. I won’t describe the details of each step as multiple documents are available on them: Install and configure ESXi, optionally integrate it with vCenter.
My new lab environment includes running the desktop fat client (GNS3.exe or whatever flavor of binary you require) on my personal workstation and connecting back to the VMware ESXi running GNS3VM to provide for the under-the-hood horse power needed to run my GNS3 topologies as referenced in the above diagram.
In this post I’ll break down my new lab topology and go through the nuances of running this particular setup. I have since adopted a new lab environment which is easier to maintain, more efficient on my compute resources, and scalable. ovf file and changed the VM version to vmx-07 then recalculated the hash. I did have an issue with the version as I have Workstation 10 and ESXi but that was an easy fix. I imported this ovf into ESXi and it worked like a charm. In an older post about my previous GNS3 lab environment, I wrote about a long standing GNS3 lab environment I had been operating which became cumbersome and difficult to maintain over time. I opened it in Vmware Workstation then exported it as an OVF.