General Considerations for Upgrade to or Downgrade from FastIron 09.0.10a or Later
Because of the many software design and CLI changes implemented in FastIron 09.0.10a, downgrading to a previous release is complex and may produce unexpected results.
| IMPORTANT REMINDER |
|---|
| Be sure you have backed up your previous startup configuration before you begin any upgrade or downgrade process. |
Preparing for the Upgrade
Before upgrading to FastIron 09.0.10a or a later release, RUCKUS strongly recommends the following steps:
- Make a backup copy of the ICX
startup configuration (the startup-config file). This copy will be used if a
downgrade to a previous release is necessary. If you have made changes to
the running configuration, you may also want to save a copy of the
running-config file.
The following example saves a copy of a FastIron 08.0.95 startup configuration and a running configuration and stores them on the TFTP server, identified by its IP address.
ICX# copy startup-config tftp 10.176.198.42 old-8095-cfg ICX# Upload startup-config to TFTP server done. ICX# copy running-config tftp 10.176.198.42 old-8095-run-cfg ICX# Upload running-config to TFTP server done.
- Consult the FastIron release notes and user documentation for the current release about significant software design changes that may need to be taken into consideration.
Transition to cli timeout Command
The cli timeout command is
introduced in FastIron 09.0.10a and replaces the ip ssh idle-time,
telnet
timeout, and console timeout commands. The following rules apply when converting a
timer configuration from earlier releases upon upgrade to FastIron 09.0.10a or
later:
- The default value for the
cli timeoutcommand is 2 minutes, which applies if none of the replaced commands has s prior configuration. After 2 minutes, by default, a console, Telnet, or SSH session times out. - Previously, the default for
console timeout was 0, which meant the console session never timed out.
Starting with FastIron 09.0.10a, if you do not want sessions to time out,
you must set the
cli timeoutvalue to 0. - Upon upgrade to FastIron
09.0.10a or a later release, the
cli timeoutvalue is acquired from previous configurations in the following order of priority: