Can't find what you need?


• Ask the Community
• Create a Case
Reset Search
 

 

Article

How To Backup/Restore VOSS Switch Configuration and Upgrade Software

« Go Back

Information

 
TitleHow To Backup/Restore VOSS Switch Configuration and Upgrade Software
Objective
Upgrading or removing VSP 9000, 4000, 7200, 8000 device software's.
Taking configuration backup's
Environment
  • All VSP/VOSS Platform
  • Any software version
Procedure
Follow the below procedure to upgrade the software on the Virtual Services Platform 4000/8000/7200/9000 using the internal flash memory as the file storage location.

Note: For configuration Backup/Restore and Upgrade, RWA user is required.

Before  beginning the upgrade,

• Save and back up the configuration files (if it is a new switch, backup might not be required)

• Connect the switch using FTP (File Transfer Protocol)and push the software file to the internal flash (/intflash)  from a locally connected PC (filezilla or winscp are recommended as they are user friendly). The procedure is as mentioned below:

Step 1: Check reachability to switch
Step 2: Connect to the switch through the filezilla/winscp tool.

Step 3: Enter the switch IP address, username and password, then click Quickconnect to establish the connection between the tool and the switch.

User-added image

STEP 4: Drag and drop files from desktop to switch internal flash (/intflash)

• User must log on to at least the Privileged EXEC mode in ACLI.

Back-up Procedure:

Command to back-up the configuration to Internal Flash:
#copy /intflash/config.cfg /intflash/config_backup.cfg
Command to back-up the configuration from Internal Flash to USB:
#Copy /intflash/config_backup.cfg /usb/config_backup.cfg
where "config_backup.cfg" is the name of the back-up configuration file

Restore Procedure:

Command to restore the configuration from USB:
#copy /usb/intflash/config_backup.cfg /intflash/config_backup.cfg

Command to restore the configuration from Internal Flash:
#copy intflash/config_backup.cfg /intflash/config.cfg

Command to set the config as the primary configuration
#boot config choice primary config-file config.cfg
Upgrade Procedure:
Copy the software image to the device using USB or TFTP server
#copy /usb/VSP xx00.4.x.x.tgz /intflash/VSPxx00.4.x.x.tgz
  1. Extract the release distribution files to the /intflash/release/ directory:
#software add WORD<1-99>

User-added image
2. Extract the module files to the /intflash/release directory:
#software add-module [software version] [modules file name]
3. Install the image:
#software activate WORD<1-99>

User-added image
4. Restart the Virtual Services Platform 4000/8000/7200/9000:
# reset

User-added image

Important : After executing the command "restart", check the amount of time configured for the commit timer to verify the upgrade and commit the software to gold. When commit the software to gold is not given and auto-commit is not enabled, the system restarts with the last known working version after the commit timer has expired. This feature ensures to regain control of the system if an upgrade fails.

5. Confirm the software is upgraded:
#show software

User-added image
6. Commit the software:
#software commit

User-added image
Upgrade Path for VSP VOSS Devices
 
Device DescriptionDevice Running VersionDevice Upgrade VersionDevice Upgrade Path
VSP 4000/7000/80003.x6.x3.0-->4.1/4.2-->5.2-->6.0/6.1
VSP 4000/7000/80004.x6.x4.1/4.2-->5.1-->6.0/6.1
VSP 4000/7000/80005.x6.x5.1/5.2-->6.0/6.1
Additional notes
There are some cautions that need to be taken care during upgrade from 4.2.1.X to latest release on VOSS platform(VSP 4000/7200/8000):

1.      If the switch that has ISIS enabled link(s) configured with HMAC-MD5 authentication then end-user need to disable the feature during upgrade to avoid potential network connectivity loss. If required it can be re-enabled post upgrading the switch.

Example:
VSP:1(config)#interface gigabitethernet x/y

VSP:1(config-if)#no isis hello-auth

VSP:1(config-if)#save config

VSP:1(config-if)# PERFORM THE UPGRADE

VSP:1(config)#interface gigabitethernet x/y

VSP:1(config-if)# isis hello-auth type hmac-md5 key <keyname> [key-id <keyed>]

VSP:1(config-if)#save config
2.      If the switch is upgraded from 4.1 to latest release then the TACACS+ host configurations will be lost. After the upgrade, the TACACS+ host configurations will not take effect so end-user must reconfigure them. After end-user make the configurations, they must save the changes on the device. End-users should also save the configuration to a file to retain the configuration settings. 

3.      VOSS  (VSP 4000/7200/8000) 4.2 and newer, a new SSH and SSL suite was incorporated into the code that has the equivalent functionality built in, so the need for the separate module files has been eliminated.
Example:-
VSP-4850GTS-PWR+:1#copy /usb/VSP8000.4.x.x.tgz /intflash/VSP8000.4.x.x.tgz  (Command to copy file from USB to Device /intflash)

VSP-4850GTS-PWR+:1#software add VSP4K.3.0.1.0.tgz

VSP-4850GTS-PWR+:1#software add-modules VSP4K.3.0.1.0 VSP4K.3.0.1.0_modules.tgz
VSP-4850GTS-PWR+:1#software activate VSP4K.3.0.1.0.GA
VSP-4850GTS-PWR+:1#reset
VSP-4850GTS-PWR+:1#show software 
================================================================================
software releases in /intflash/release/
================================================================================
VSP4K.3.0.1.0int064 (Backup Release)
VSP4K.3.0.1.0GA (Primary Release)
--------------------------------------------------------------------------------
Auto Commit: enabled
Commit Timeout: 10 minutes

 

VSP-4850GTS-PWR+:1#software commit
4.      Upgrading DVR configurations from releases 6.0.1.1 and earlier to 6.0.1.2 and beyond.

         a. All DVR nodes must be upgraded to the same release.
         b. All DVR leaves should be upgraded first.
NOTE: Use this command when Auto commit is disabled. If it enabled, software will automatically get commits after the default commit timeout 10 minutes

Note:

1. Image file of VSP 4K is quite large (>70MB), and copy command by default uses tftp for file transfer, but there is a catch, any file of larger size copied using copy command fails as tftp used supports copy of files which are of lesser size only. So, it is recommended to use FTP for upgrading the device.

2. Error might be noticed, when end user tries to copy another software file to the release when there are already six GA files in the release.

Use the below command to delete the software files from the release:
#software remove <X.X.X.X GA>

Feedback

 

Was this article helpful?


   

Feedback

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

Characters Remaining: 255