![]() in gns3_nf) and are listing the correct disk images. We have a couple of custom Templates (mostly stuff like juniper vMX in various versions and other VNFs) build and imported. It seemed to work fine for some time.Īfter a recent server reboot (due to kernel updates) and therefore service restart we noticed that all projects started after the reboot/upgrade fail to start the nodes.Īfter further invetigation we found out that the projects started after the restart have broken disk path images for the nodes. We are running a couple of GNS3 servers on ubuntu 20.04. I suspect the problem is with gns3-server, so i open it here. We opend a discussion on the community support forum( ), but were pointed to open an issue here.
0 Comments
Leave a Reply. |