Skip to main content

How to Properly Clone an EVE-NG Lab with Configurations

Cloning labs in EVE-NG is a great way to duplicate setups and expand or experiment on a new copy without affecting the original lab. However, if not done correctly, the cloned lab may only copy the topology without configurations. In this guide, I’ll show you how to properly clone a lab in EVE-NG with all configurations using the EVE-NG GUI.

Follow these steps to ensure that both the topology and router configurations are retained when cloning your lab.


Steps to Clone an EVE-NG Lab with Configurations

  1. Save Running Configuration on All Devices
    In your original lab, make sure all devices have their configurations saved to NVRAM. Go into the CLI of each router and run the command:
    copy running-config startup-config

  2. Export All Configurations (CFGs)
    On the left sidebar in the EVE-NG Web UI, click on the "More Actions" option. Then select "Export all CFGs". This step exports the configurations of all devices in the lab.

  3. Shutdown All Devices
    After exporting the configurations, shut down all the devices in the lab. This step is important because cloning a lab while devices are running may not correctly retain configurations.

  4. Close the Lab
    Once all devices are shut down, close the lab from the EVE-NG Web UI.

  5. Clone the Lab
    Go to the EVE-NG dashboard, where all your labs are listed. Click on the lab you want to clone and select “Clone” from the options in the left sidebar. The cloned lab will now appear in your lab list.

  6. Open the Cloned Lab (Do NOT Start Devices Yet)
    Open the newly cloned lab, but do not start any devices yet. This ensures that you can apply the saved configurations first.

  7. Activate Start-up Configs
    On the left sidebar, click on “Start-up Configs”. Turn the Start-up Configs ON for all devices. This will load the configurations from the original lab into the cloned devices.

  8. Start All Devices
    Now, you can start all devices in the cloned lab. The configurations from the original lab should automatically load.

  9. Save the Configurations
    After the devices are up and running, save the configurations to NVRAM by running the command:
    copy running-config startup-config

  10. Turn Off All Devices
    Once configurations are saved, shut down all devices again.

  11. Disable Start-up Configs
    Go back to “Start-up Configs” in the left sidebar and switch the button to OFF for all devices. This ensures future configurations are saved directly on the devices.

  12. Restart All Devices
    Restart the devices, and the cloned lab will now have both the topology and all configurations from the original lab.

Conclusion

By following this method, you can easily clone an EVE-NG lab with both the topology and the configurations intact. This is particularly useful when you want to experiment with a lab setup or add more devices without affecting your original configurations.

Feel free to try this out in your own lab and let me know how it goes!

Labels:

Comments

Post a Comment

Popular posts from this blog

How to import Putty Saved Connections to mRemoteNG

Just started using mRemoteNG and its being very cool to connect to different remote connection with different protocols e.g Window Remote Desktop, VNC to Linux, SSH, HTTP connection etc. from a single application. As new user I configured some remote desktop connection which was quite easy to figure out. But when I wanted to add SSH connections, it came in my mind to import all of the saved connections in the putty. But I couldn't figure it out how can it be done, though it was quite easy and here are the steps. Open your mRemoteNG Create a folder if you want segregation of multiple networks Create a new connection Enter the IP address of remote server under connection in Config pane Under the config pane, select protocol " SSH version 2 ".  Once you select protocol to SSH version 2 you are given option to import putty sessions, as shown in the snap below. In the above snap, I have imported CSR-AWS session from my saved sessions in Putty.
1 comment
Read more

Authoritative DNS Servers Delegation and Internal DNS Explained

DNS (Domain Name System) plays a critical role in how users and systems find resources on the internet or within internal networks. Whether it's managing an internal domain in an enterprise or delegating parts of a domain for traffic distribution, DNS setups vary widely depending on needs. In this blog post, we’ll break down the different types of DNS setups, including authoritative DNS servers, DNS delegation, and how internal DNS functions within organizations. 1. Authoritative DNS Server An Authoritative DNS server is the final source of truth for a specific domain. When someone queries a domain (e.g., example.com ), the authoritative DNS server for that domain holds the DNS records (A records, CNAME, MX, etc.) and responds with the corresponding IP address. Key Points: Who can host it? Authoritative DNS servers are often hosted by domain registrars (e.g., GoDaddy, Namecheap) or cloud DNS providers (e.g., AWS Route 53, Cloudflare). However, organizations can also host their ...
Post a Comment
Read more

BGP Soft Reconfiguration vs. Route Refresh: Key Differences and Best Practices

In BGP (Border Gateway Protocol), managing route updates and reapplying new policies can sometimes be challenging, especially if you want to avoid resetting the BGP session. Two methods allow you to update routing policies without tearing down the session: BGP Soft Reconfiguration and BGP Route Refresh . While both methods serve the same purpose, they work differently and have distinct impacts on your router's resources. This post explains the key differences between Soft Reconfiguration and Route Refresh , when to use each, and why Route Refresh is preferred in most modern networks. 1. What is BGP Soft Reconfiguration? BGP Soft Reconfiguration is an older method of applying new policies (like route maps, filters, or prefix lists) without resetting the BGP session. It works by storing a local copy of all the routes received from a BGP neighbor before applying inbound policies. This local route copy allows the router to reprocess the routes when a policy change occurs. How So...
Post a Comment
Read more