Support and News Forum

Hi

Bare-metal setup
Eve-ng version : 2.0.3-110

Installing EVE-ng has been smooth for me and have not encounter big problems so far, the part that I have trouble with is starting IOL nodes from my backup lab.

I had backup the folders following guide
/opt/unetlab/addons/
/opt/unetlab/tmp/
/opt/unetlab/labs/
usually I would restore these folders and run the necessary commands for IOL to work(iourc, fix-permissions).

After restore, most of my lab nodes (windows server, ASA) works except the IOL nodes, which I could not start from my restored lab, and I have to create new IOL node to replace all. (**New IOL node is working, existing IOL nodes in lab start-and-stop)

This happens to me on few machines, and whenever i restore from my backup, i have to start from scratch for all my IOL nodes, replacing with new IOL nodes (as the restored lab IOL node is not starting)

I did tried to search around for similar issue but i couldnt find any, would seek if anyone have any similar experience
Thanks

need regenerate iourc lic on new eve

Uldis (UD) wrote: ↑

Thu Dec 03, 2020 7:08 pm

need regenerate iourc lic on new eve

had generate iourc lic and should be working as whenever I create a new IOL node, it works.
The issue is when starting existing lab IOL nodes that it start-and-stop (Lab that i restored from backups).
Is there ways I could run/see the logs?

This can happen, because after migration, lab is looking previously saved NVRAM, which does not on new EVE
Slution:
right click wipe node
check if image is seleted properly and boot

Uldis (UD) wrote: ↑

Fri Dec 04, 2020 8:56 am

This can happen, because after migration, lab is looking previously saved NVRAM, which does not on new EVE
Slution:
right click wipe node
check if image is seleted properly and boot

UD, Wow!!! Thanks!
The nodes boot although all my config are gone (expected for "wipe node"), guess i was too lazy to make backup/restore of config and didnt even try to wipe everything.
Instead i recreate all new IOL nodes.......
But does this occurs whenever a restore is made? is it a norm thing?

IOL support export config feature, and after wipe you can buut it from exported configs easy

I right now restore my config and have the same issue. Reading this thread means for me:
-> If you did not do a config export, the nvram of the IOL Nodes is complete gone. Is this correct? I have the same issue (IOL Node starts, and stops imediately again).

If yes, firstly thats a big bummer because my labs are destroyed.

I expected, that the backup (https://www.eve-ng.net/index.php/backup-eve-ng-content/) is a real backup. In my opinion it should be mentioned if the IOL Nodes get destroyed by this, because for me it is not clear that these NVRAM Configs would not be included in the backup und ~/tmp/.

My fault for not testing my backup I guess.

Why do existing IOL nodes in a restored EVE-ng lab fail to start, even after restoring relevant folders and running iourc and fix-permissions, while newly created IOL nodes work fine?