It sounds like you’re facing issues with retaining configurations on vManage in your EVE-NG lab environment when you restart the server. There are several things you can do to deal with this particular problem.
Save the vManage configuration: Before restarting your server or stopping your SD-WAN lab, make sure to save the vManage configuration. You can do this through the vManage CLI:
This will commit and save the running configuration to the startup configuration.
Export vManage configuration: To export the vManage configuration for backup purposes, you can follow these steps:
Log in to the vManage web UI.
Navigate to the “Configuration” tab and then to “Devices.”
Select the vManage device from the list and click the “More Actions” button (three vertical dots).
Choose “Export Configuration” and save the file to your local machine.
In case your vManage loses its configuration after a restart, you can import the configuration you previously exported:
Log in to the vManage web UI.
Navigate to the “Configuration” tab and then to “Devices.”
Click on the “Import Configuration” button and choose the configuration file you saved earlier.
Once the import is complete, verify that your configuration is restored.
Persistent Storage in EVE-NG: To make sure your configurations are retained across reboots in EVE-NG, you can enable persistent storage by following these steps:
Open the EVE-NG web interface.
Navigate to the “Tools” menu and click on “Settings.”
In the “Settings” dialog, enable the “Persistent Configuration” option.
Click “Save” to apply the changes.
Try some of these steps to resolve the issue of losing your configs whenever you restart your devices in EVE-NG. Let us know if any of these have helped to resolve the issue.
I would first focus on why EVE-NG is not saving your configurations. This should work. I’m also using EVE-NG and whenever I stop or start the lab, everything is still there. It’s too much of a hassle to configure (or import / export) everything from scratch.
Do the controllers have disks like I describe here?
And are you using these disks when you add the controller images?
To export configurations, templates, policies, and certificates, there are a couple of options. I collected them all here:
In the process of creating a Certification Authority (CA), we initially need to create the root CA. The root CA consists of a private key and a root certificate. These two items are the identity of our CA.
Once the root CA’s public key is packaged into a certificate, that certificate needs to be signed to ensure its integrity and authenticity. The signing process involves using the root CA’s private key. Anyone can then verify the certificate by using the corresponding public key. This assures entities that the certificate truly originated from that CA and hasn’t been tampered with.
For more detailed information on how to create a CA and the related entities involved, take a look at this lesson:
