Transfer Staros Image To /Flash; Saving A Copy Of The Current Configuration File; Downgrading From Release 15.0 To 14.0; Downgrading From Release 20.0 - Cisco ASR 5500 System Administration Manual

Transfer StarOS Image to /flash

Transfer StarOS Image to /flash
Transfer the new operating system image file to the /flash directory on the MIO/UMIO/MIO2 using one of
the following methods:
• Transfer the file to the /flash device using an FTP client with access to the system.
• Transfer the file to the /flash device using an SFTP client with access to the system.
Verify that the image file was successfully transferred to the /flash device by running the following Exec
mode command:
[local]
The image filename should appear in the displayed output.
Run the show version /flash/image_filename command to verify the build information.
[local]

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.

Downgrading from Release 15.0 to 14.0

Release 14 and Release 15 chassis IDs use different encryption formats. Release 15 will recognize a Release
14 chassis ID and consider it as valid. Upgrading from 14.x to 15.0 will not require changing the chassis ID
or configuration file.
However, if the chassis key is reset in Release 15 through the setup wizard or chassis-key CLI command, a
new chassis ID will be generated in Release 15 format (44 instead of 16 characters). Release 14 builds will
not recognize the 44-character chassis ID. If the chassis is subsequently downgraded to Release 14, a new
16-character chassis ID will be generated. To accommodate the old key format, you must save the configuration
file in pre-v12.2 format before the downgrade. If you attempt to load a v15 configuration file on the downgraded
chassis, StarOS will not be able to decrypt the password/secrets stored in the configuration file.

Downgrading from Release 20.0

Prior to release 20.0, local-user passwords were hashed with the MD5 message digest-algorithm and saved
in the database. In release 20. 0, PBKDF2 (Password Based Key Derivation Function - Version 2) is now
ASR 5500 System Administration Guide, StarOS Release 21.5
94
Important Whenever transferring a operating system software image file using the file transfer
protocol (FTP), the FTP client must be configured to transfer the file using binary mode.
Failure to use binary transfer mode will make the transferred operating system image
file unusable. In release 20.0 and higher Trusted StarOS builds, FTP is not supported.
host_name directory /flash
#
host_name
show version /flash/image_filename.bin
#
Software Management Operations