Staff

Meru Technical Note - Important Steps to Note When Upgrading from 4.x to 5.x

Description

What are the important Steps to Note When Upgrading from 4.x to 5.x (assuming all pre-upgrade steps have been completed)

Solution
Note: Read the Release Notes before proceeding and make sure your hardware is compatible with System Director 5.x.

You will need to upgrade to 5.0-96 first if your final destination is 5.1.x. The following steps are for upgrading from 4.0-150 to 5.1-75. The path is as follows:
4.0-150->5.0-96->5.1-175.
Back up the controller's configuration to a remote location or to your local PC via FTP/TFTP.
Turn OFF auto AP upgrade on the controller.
Check the flash and delete any older flash images from the controller to free up space. A minimum of 30MB of root partition must be available in order to upgrade a controller to version 5.x.
Copy meru-5.0-96-pre-feature-MCXXXX.tar to the controller.
Run “sh flash” to make sure the pre-upgrade feature image is present in the flash.
Run the following command: “upgrade feature 5.0-96-pre-feature” (This will upgrade the feature and delete the pre-feature file to give room to the second file that you’ll be copying to the controller).
Run “sh features” to confirm that the feature has been installed.
Run “sh flash” to make sure that the pre-feature image has been automatically deleted.
Run “sh file system” to be sure you have enough room for the new file.
Copy meru-5.0-96-MCXXXX-rpm.tar to the controller.
Run the following command: “upgrade controller 5.0-96”
Copy the 5.1.75 code to the controller.
Upgrade directly to 5.1-75 (Note: no pre-feature upgrade is needed since you are now going from 5.0 to 5.1).
Run “upgrade ap same all” to upgrade all the APs to the 5.1-75 code.
Turn ON auto AP upgrade.

Sign up