08-25-2010 03:53 AM
Im having problems downgrading our E320 to 8.2.2, currently we are running 9.3.2
I get an error when i issue the command
boot system new software
Do I need to load an interim software before I can load 8.2.2?
Any suggestions are appreciated!
Solved! Go to Solution.
08-25-2010 03:04 PM
JUNOSe stores the configuration in a binary format which is extended with every release to allow storing of settings for new features. This can lead to a situation like yours where an older release can't read the config from a newer release. The way to downgrade to a lower numbered release is like the following:
show conf > 9-3-2.scr
boot conf fac
boot sys 8.2.2.rel
boot conf 9-3-2.scr
08-26-2010 12:16 AM
Hello Ulf -thank you for your reply
I will try your suggestion in our lab!
One thing though! I've heard that booting on .scr files is not recommended and can produce errors in the loaded config.
Have you tried booting with this procedure?
08-26-2010 02:55 AM
you've heard right (and as usual there always is a more comprehensive answer): Booting from an .scr file isn't recommended (if you have the choice to boot a binary config/.cnf) for at least these reasons:
1. it can take significantly longer (depending on the number of lines in the config / number of ints)
2. interfaces might not get operational in the "right" / desired order (customer facing ints might come up before the core-facing ones) / protocols might not be started when you'd want this
3. there have been (and may still are some) issues that not all elements in the .scr-file / show conf output are in the right sequence, so you might get an error message saying that a certain config-statement can't be applied, as it's referring to an element that doesn't yet exist
How to deal with this:
1. in case of a downgrade you have no other choice then loading the .scr as there is no way that new.cnf will be read by the old release
2. you could edit the .scr file and change the sequence so that e.g. core- and management-ints are created first, then all protocols are started/configured and in the end the customer facing int's are configured
3. you possibly could go through the config and try to find these "out-of-order" statements, but thats rather time-consuming (as you stated you have a lab-system to try this out, you'll see if there really are issues and then you can fix these along with 2.)
Hope this helps.
08-26-2010 03:09 AM
I may be in luck - I have saved a .cnf config from the previous, target, release. As long as this is not loaded and overwritten on the new software the .cnf shouldn't change.
Would this work ?
1 boot conf fac
2 boot system 8....
3 boot conf bakcup.cnf
Then do the sync and srp switch or is it necessary to sync and switch before step 3?
08-29-2010 11:19 PM - edited 04-03-2012 01:25 AM
having a backup is a whole different story:
1. boot conf backup.cnf once
2. boot sys old.rel
4. wait until standby-SRP has finished rebooting and is back in sync then
5. srp switch
04-02-2012 11:56 PM
After copying the release file from ftp to flash initiate a factory default command and boot with lower release.
Example below: downgrade (13.0.0 t0 11.2.1)
ERX-1440-2(config)#boot config factory-defaults
WARNING: Execution of this command will cause all configuration settings to
revert to factory defaults upon the next system reboot.
Proceed with 'boot config factory-defaults'? [confirm]
ERX-1440-2(config)#boot system erx40_11-2-1.rel
WARNING: The release specified is not ISSU compatible.
WARNING: It is recommended that you copy the current running-configuration to a
file prior to running with a different release of software.
ERX-1440-2(config)#do sh boot
ERX-1440-2(config)#do sh boot
System Release: erx40_11-2-1.rel
System Configuration: factory-defaults
Note: This system is not configured with backup settings.
WARNING: This command will cause the system to reboot.
Proceed with reload? [confirm]
% Unable to reload at this time (a sync operation is in progress)