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

SSL VPN vs IPSec VPN: Understanding the Key Differences

When it comes to securing communication over the internet, Virtual Private Networks (VPNs) are a cornerstone of modern networking. Two popular types of VPNs are SSL VPN and IPSec VPN . While both serve to encrypt and secure data, they differ significantly in terms of technology, use cases, and implementation. This blog post will help you understand these differences and choose the right solution for your needs. What is SSL VPN? An SSL VPN uses the Secure Sockets Layer (SSL) or its successor, Transport Layer Security (TLS) , to create a secure connection. It operates at the Application Layer (Layer 7) of the OSI model and is designed to provide secure access to specific resources over the internet. Key Features of SSL VPN: Ease of Use: Accessible via a standard web browser without the need for dedicated client software. Granular Access Control: Allows users to access specific applications or resources rather than the entire network. Port Usage: Uses TCP port 443, which is rarely...
Post a Comment
Read more

AS Path Prepending: Controlling Inbound Traffic in BGP

AS Path Prepending is a BGP feature used to make a specific path appear less preferred by artificially lengthening the AS path. This is done by adding your AS number multiple times to the AS path. It is a common method to influence inbound traffic from external networks. Longer AS Path = Less preferred route . Example Scenario : You have two ISPs: ISP1 (through CE1) and ISP2 (through CE2). You want inbound traffic from the internet to prefer ISP1 over ISP2. Network Topology : CE1 (connected to ISP1): 10.0.1.1/30 CE2 (connected to ISP2): 10.0.2.1/30 iBGP Router (Internal) connected to both CE1 (10.0.1.2/30) and CE2 (10.0.2.2/30). Configuration on CE2 (AS Path Prepending to Make ISP2 Less Preferred) : Create a route map to prepend your AS path multiple times for CE2: route-map PREPEND_AS permit 10 set as-path prepend 65001 65001 65001 Apply this route map to the neighbor in the BGP configuration for CE2: router bgp 65001 neighbor 10.0.2.1 remote-as 65002 neighbor 10.0.2.1 ro...
Post a Comment
Read more