Support and News Forum

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

exactly juniper is possible, because Juniper supports export configs !

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

UD

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

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

Give that a try. Cheers

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

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

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?

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

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

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