Reset Search



Best practices during the upgrade of an EXOS switch

« Go Back


TitleBest practices during the upgrade of an EXOS switch
This article explains some of the best practices that could be followed during an upgrade activity of an EXOS switch
  • Summit and Blackdiamond series
  • EXOS All
Step 1: Verifying the Hardware support. 

Before planning an upgrade to a new version, we need to ensure that the switch supports the new firmware.
To verify if the hardware is supported for the corresponding XOS version, refer the link below: 
Which version of EXOS is supported on my hardware?

Step 2: Backing up the existing configuration. 

It is important that we have the backup of the existing working configuration. The configuration file can be backed up either on the switch locally or to a TFTP server before upgrading to the new version. 

To backup the switch configuration locally, simply issue save the configuration using a different file name using the following command. 
save configuration <filename>
It is important to note that you do not want to use this file while upgrading. This file should be used if you want to downgrade to the existing software configuration. So, please select no to make this .cfg as the default database
X670V-48x.4 # save conf backup_config
Do you want to save configuration to backup_config.cfg? (y/N) Yes
Saving configuration on master ........ done!
Configuration saved to backup_config.cfg successfully.

The current selected default configuration database to boot up the system
(backup.cfg) is different than the one just saved (backup_config.cfg).
Do you want to make backup_config.cfg the default database? (y/N) No
Default configuration database selection cancelled.
To backup the configuration using the TFTP server refer the link below: 
How to upload Backup Configuration to TFTP server on EXOS switch

Step 3: Upgrading the switch. 

The next step would be to perform the upgrade itself. Please refer the link below for the upgrade steps:
How to Obtain and Upgrade EXOS

Step 4: Roll back option. 

After the upgrade is performed, we tend to make some changes and save the configuration in the new version. For some reason, if the network is not performing as expected after the upgrade, it is important to have the downgrade as a roll back option. However, while downgrading, we need to make sure to load the configuration file which we backed up earlier rather than using the configuration file which is saved in the new version. 

This is because, with the addition of new features in the newer version, the configuration file created in this version may not be understood by the earlier versions and hence there is a remote possibility of a configuration loss during downgrade. 

This can be avoided by using the configuration file created by the older version. 

If you have the backup configuration file in the tftp server, use the following command to download it to the switch.
tftp get <tftp server ip address> <backup file name> vr <vr-name>
Once the file is in the switch, use the following commands to use that configuration file and then downgrade the switch. 
use configuration <backup filename>
use image <partition in which the old image is present>

* X670V-48x.3 # reboot
Do you want to save configuration changes to currently selected configuration
file (backup_config.cfg) and reboot?
(y - save and reboot, n - reboot without save, <cr> - cancel command) No

While rebooting, please select No so that the configuration is not saved to the backup up configuration file. 
Additional notes
Check the show switch command to know which software version has created the used config file. 
Show switch:

Config Selected:  backup_config.cfg
Config Booted:    backup_config.cfg

backup_config.cfg Created by ExtremeXOS version
                  211157 bytes saved on Thu Aug 20 14:01:44 2015




Was this article helpful?



Please tell us how we can make this article more useful.

Characters Remaining: 255