Clone Lab with all configs on Devices and all Settings

Before posting something, READ the changelog, WATCH the videos, howto and provide following:
Your install is: Bare metal, ESXi, what CPU model, RAM, HD, what EVE version you have, output of the uname -a and any other info that might help us faster.

Moderator: mike

Chris929
Posts: 83
Joined: Tue Jun 27, 2017 8:51 am

Clone Lab with all configs on Devices and all Settings

Post by Chris929 » Mon Jul 24, 2017 1:21 pm

Hi,
I know that this is not possible via GUI - but is there a way on the CLI to clone an entire Lab (including all "Devices Harddisks", configs etc.?
With my Juniper Labs this would be great to test different scenarios.

Regards
Chris

Uldis (UD)
Posts: 5067
Joined: Wed Mar 15, 2017 4:44 pm
Location: London
Contact:

Re: Clone Lab with all configs on Devices and all Settings

Post by Uldis (UD) » Mon Jul 24, 2017 4:51 pm

exactly juniper is possible, because Juniper supports export configs !

so simple stpes..
save running cfgs
expoort them
then clone lab

UD

Chris929
Posts: 83
Joined: Tue Jun 27, 2017 8:51 am

Re: Clone Lab with all configs on Devices and all Settings

Post by Chris929 » Tue Jul 25, 2017 11:11 pm

Hi UD,

whenever i try to export the config, the System throws an error after around 30 seconds of waiting - regardless of vQFX, vMX or vSRX.
So if I read your Post correctly my eve is not behaving normal, right? Do I have to turn the Devices off for that?

Regards
Chris

Sipart
Posts: 59
Joined: Sun Mar 19, 2017 9:20 pm

Re: Clone Lab with all configs on Devices and all Settings

Post by Sipart » Wed Jul 26, 2017 7:05 am

Device on but make sure your logged on as root on the Junipers when exporting configs.

Give that a try. Cheers

Chris929
Posts: 83
Joined: Tue Jun 27, 2017 8:51 am

Re: Clone Lab with all configs on Devices and all Settings

Post by Chris929 » Thu Jul 27, 2017 6:43 am

Hi all,

still "failed to export config (16)" - logged in as root and tried via native-console and html5 console.
Right-Click on the Device and "export CFG", right?

Regards
Chris

Sipart
Posts: 59
Joined: Sun Mar 19, 2017 9:20 pm

Re: Clone Lab with all configs on Devices and all Settings

Post by Sipart » Thu Jul 27, 2017 6:40 pm

Hi Chris. Yes that's what you do.

Earlier thread here:

viewtopic.php?f=3&t=621&p=2149#p2149

Not that it will help you as it sounds like your doing everything you should. Can you export Cisco configs?

Cheers

Chris929
Posts: 83
Joined: Tue Jun 27, 2017 8:51 am

Re: Clone Lab with all configs on Devices and all Settings

Post by Chris929 » Sun Jul 30, 2017 9:54 pm

Hi Sipart,

this is interesting:

Logged in as root I see that the EVE is doing some configuration:


cli
set cli screen-lenght 0
show config

while showing the config, the GUI tells me "Export failed" - seems that the script is not waiting lonmg enough for the "show" to finish...
Is there a way to increase the timeout for the Export-Scripts?

Sipart
Posts: 59
Joined: Sun Mar 19, 2017 9:20 pm

Re: Clone Lab with all configs on Devices and all Settings

Post by Sipart » Mon Jul 31, 2017 4:19 pm

Hi Chris, do you haver a large config?

The script is python I think - so possibly - wait to see what one of teh EVE guys say.

if you spin up a new Juniper device and just do the minimal config and try and export what happens?

Cheers

Chris929
Posts: 83
Joined: Tue Jun 27, 2017 8:51 am

Re: Clone Lab with all configs on Devices and all Settings

Post by Chris929 » Mon Jul 31, 2017 9:27 pm

This seems to work - however my Topology has around 20 Devices each with 8k to 20k lines of code, depending of the scenario ;)

Sipart
Posts: 59
Joined: Sun Mar 19, 2017 9:20 pm

Re: Clone Lab with all configs on Devices and all Settings

Post by Sipart » Tue Aug 01, 2017 12:38 am

Hi Chris. The python scripts are in:
/opt/unetlab/scripts/

And have logical names like:
config_vsrx.py

So you might be able to work out if a time out is set, but it also may be related to the config being encoded and written to the .unl lab file? Perhaps that has some limitations when handling large configs?

Looking at the logs for a failed export it looks like it writes a temporary copy of the config, perhaps as part of the process of encoding and writing it to the unl file? If you monitor the temp directory while attempting a export you may be able to witness it?

Cheers

Post Reply