Cisco Cisco Packet Data Gateway (PDG) Guia Do Administrador
Software Management Operations
▀ Upgrading the Operating System Software
▄ Cisco ASR 5000 System Administration Guide
130
Saving a Copy of the Current Configuration File
Prior to upgrading to a new software release, you should copy and rename the current configuration file to the /flash
device and to an off-chassis location (external memory device or network URL). This renamed copy assures that you
will have a fallback, loadable configuration file should a problem be encountered during the upgrade.
device and to an off-chassis location (external memory device or network URL). This renamed copy assures that you
will have a fallback, loadable configuration file should a problem be encountered during the upgrade.
Important:
Configuration files created and saved in StarOS release 12.2 and higher cannot be shared across
multiple chassis due to a change in the encryption algorithm for passwords and secrets. These release 12.2 + changes
modify encrypted data in the configuration file so that it cannot be recognized by software builds prior to 12.2. If it is
necessary to revert to a previous build, the chassis must be booted with the copy of the original configuration file. If this
copy is not available, then the chassis must be loaded as if it is a new chassis.
modify encrypted data in the configuration file so that it cannot be recognized by software builds prior to 12.2. If it is
necessary to revert to a previous build, the chassis must be booted with the copy of the original configuration file. If this
copy is not available, then the chassis must be loaded as if it is a new chassis.
Preparing for a Software Downgrade
Downgrading from Release 12.2 to 12.0
If a software upgrade to release 12.2+ fails, you may need to downgrade to a previous software release, such as 12.0.
Since the encryption algorithm for passwords and secrets is difference from 12.0 to 12.2+, you must save the 12.0
configuration file using the obsolete-encryption keyword to preserve passwords and secrets that used the earlier
algorithm.
Since the encryption algorithm for passwords and secrets is difference from 12.0 to 12.2+, you must save the 12.0
configuration file using the obsolete-encryption keyword to preserve passwords and secrets that used the earlier
algorithm.
Important:
You must save the configuration prior to upgrading to release 12.2+.
The general sequence for a software downgrade in this scenario is as follows:
Develop a downgrade plan with the assistance of Cisco support personnel.
Save the pre-12.2 configuration using the obsolete-encryption keyword in conjunction with the Exec mode save
configuration command as shown in the example.
[local]host_name# save configuration /flash/v120_system.cfg obsolete-encryption
Warning: Use of weaker encryption significantly reduces the security of the
system
Are you sure? [Yes|No]: Yes
Warning: Use of weaker encryption significantly reduces the security of the
system
Are you sure? [Yes|No]: Yes
To reboot the system using the old configuration, change the boot configuration via the Global Configuration
mode to use the old boot image and its previously saved configuration. See the example below.
[local]host_name(config)# boot system priority 1 image /flash/v120_asr5000.bin
config /flash/v120_system.cfg
config /flash/v120_system.cfg
Reload the system using the pre-12.2 image and configuration.
Once the system has reloaded, verify that the configuration is correct.
Save the current configuration as a backup once the configuration has been validated.