Hi,
I have a lab setup with a couple of Juniper vSRXs. I can successfully export and import configs but following the completion of an import, I still have the "clock" symbol next to the node in question.
If I gracefully shutdown or power-off then I cannot power the node back on again without wiping the config first.
Also, I needed to update the config script to use "load override" as it was failing on the "set: commands for interfaces (on the factory default config).
Any suggestions as to working out if the script is actually completing or what I'm doing wrong?
Thanks,
Pierre
vSRX Config Import not completing
Moderator: mike
-
- Posts: 5
- Joined: Tue Apr 11, 2017 4:49 pm
Re: vSRX Config Import not completing
I managed to work out that the script wasn't completing due to the timeout being reached and therefore the ".lock" file not being removed.
Running the script manually gave the following error while the config was still committing:
root@eve-ng:/opt/unetlab/scripts# python3 /opt/unetlab/scripts/config_vsrx.py -a put -p 32774 -f /opt/unetlab/tmp/0/841eb27e-0320-4f71-84c1-6d0fe66cb970/6/startup-config -t 300
ERROR: error waiting for ["root>", "root@.*>"] prompt.
ERROR: failed to push config.
Changing the value of longtimeout in the script fixed the issue.
Running the script manually gave the following error while the config was still committing:
root@eve-ng:/opt/unetlab/scripts# python3 /opt/unetlab/scripts/config_vsrx.py -a put -p 32774 -f /opt/unetlab/tmp/0/841eb27e-0320-4f71-84c1-6d0fe66cb970/6/startup-config -t 300
ERROR: error waiting for ["root>", "root@.*>"] prompt.
ERROR: failed to push config.
Changing the value of longtimeout in the script fixed the issue.
-
- Posts: 135
- Joined: Wed Mar 15, 2017 3:30 pm
Re: vSRX Config Import not completing
Try increasing the script timeout to 600