Software Downgrade from a UFI to a Non-UFI Version

It is recommended that you copy the running configuration to a file before downgrading. You can do this using the copy running-config command to copy the configuration to different locations such as a USB disk file or a tftp server, or you can simply enter the show running-config command and then copy the output and paste it into a computer file.

If you don't have a pre-08090-startup-backup file (which can be checked with the show pre-8090-startup-backup command), or you have many configuration changes to the 08.0.90 release or a later release and you need to downgrade to a pre-08.0.90 release, you must manually edit the 08.0.90 configuration to create a pre-08.0.90 format.

Every unit, including a stack member, has a startup-config file, and every unit renames the startup-config as the backup file when the write memory command is used. If you no longer need the pre-8090-startup-backup file, you can delete it using the erase pre-8090-startup-backup command. This command erases the pre-8090-startup-backup file in every unit in the stacking system. You may no longer need the older backup file if you are certain you will not have to downgrade the system or if you have made many configuration changes with the FastIron 08.0.90 or later release installed, making the backup file obsolete.

RUCKUS recommends downgrading to earlier releases using a manifest download.

Note: Reboot the device using the boot system command only. When a system running FastIron 08.0.90 detects that it is about to reload to a pre-08.0.90 release, the system tries to recover the backup file. A message is displayed asking for confirmation before recovering the file with a warning that all changes made with the current release will be lost.
Warning! the startup-config is 8.0.90 or later, but you are reloading to a pre-8090 image. There is no pre-8090-startup-backup file. Reloading to pre-8090 image may lose some stack-port/trunk configurations due to 8090 format changes.

When a system is upgraded to FastIron 08.0.90 or later and then downgraded to a pre-08.0.90 release, the results of the downgrade differ, depending on the situation. The following cases describe specific situations and the expected results. The scenarios in the following tables apply to a standalone unit or a stack.

Downgrade Scenarios

Situation Result
The user never uses a write memory command when running FastIron 08.0.90. The downgrade is seamless.
The user does not change any configuration but uses the write memory command when running FastIron 08.0.90. The downgrade is fine. The system recovers the backup file before reloading to a pre-08.0.90 release.
The user makes configuration changes while running FastIron 08.0.90 and uses the write memory command. The downgrade loses all configuration changes made under FastIron 08.0.90. The system recovers the backup file that does not contain the changes.

Scenarios where Downgrades Cannot Be Performed

Situation Result
The user reloads the system by powering down. The system cannot recover the backup file before reloading.
The standalone or active controller does not have a startup-config flash file generated by any pre-08.0.90 release. Downgrade is not possible.

The following sections provide examples of manifest downloads using TFTP and SCP.

Note: RUCKUS does not recommend using the application image download.