Product Documentation

Downgrading to an Earlier Build within Release 11.1

Aug 31, 2016

You can downgrade from a later 11.1 build to an earlier 11.1 build on a standalone NetScaler or a high availability pair. This procedure must be performed by using the command line interface.

Warning: Loss in configuration may occur when downgrading. You should compare the configurations before and after the downgrade, and then manually readd any missing entries.

Downgrading a Standalone NetScaler to an Earlier Build

In the procedure below, <targetbuildnumber> is the build number that you are downgrading to within the same release.

To downgrade a standalone NetScaler to an earlier build

  1. Use an SSH client, such as PuTTy, to open an SSH connection to the appliance.
  2. Log on to the NetScaler by using the administrator credentials. Save the running configuration. At the prompt, type:

    save ns config

    Caution: If ns.conf.NS11.1-<targetbuildnumber> does not exist, loss in configuration may occur when downgrading to an earlier build. The errors and warnings appear only on the console. Please watch the console closely for these errors and warnings. After the appliance restarts, compare the saved configuration with the running configuration, and make any adjustments for features and entities configured before the downgrade. Save the running configuration after making the changes.
  3. Change directory to /var/nsinstall/11.1nsinstall.
  4. Change directory to build_<targetbuildnumber>, or create one if it does not exist.
  5. Download or copy the installation package (build-11.1-<targetbuildnumber>_nc.tgz) to this directory and extract the contents of the installation package.
  6. Run the installns script to install the old version of the system software. The script updates the /etc directory.

    If the configuration file for the build that you are downgrading to exists on the appliance, you are prompted to load that configuration.

  7. When prompted, restart the NetScaler.


login: nsroot 
Password: nsroot 
Last login: Fri Jun  24 08:38:25 2016 from 
> save ns config 
> shell 
Last login: Fri Jun 24  09:07:06 from 
root@NSnnn# cp ns.conf.NS11.1-55.23 ns.conf 
root@NSnnn# cd /var/nsinstall 
root@NSnnn# cd 11.1nsinstall 
root@NSnnn# cd build_47_10 
root@NSnnn# ftp <FTP server IP address>
ftp> mget build-11.1-47.10_nc.tgz
ftp> bye 
root@NSnnn# tar xzvf build-11.1-47.10_nc.tgz 
root@NSnnn# ./installns 
installns version (11.1-47.10) kernel (ns-11.1-47.10.gz) 
Copying ns-11.1-47.10_nc.gz to /flash/ns-11.1-47.10_nc.gz ... 
Changing /flash/boot/loader.conf for ns-11.1-47.10 ... 
Installation has completed. 
Reboot NOW? [Y/N] Y 

Downgrading a NetScaler High Availability Pair to an Earlier Build

To downgrade the system software on NetScaler units in a high availability pair, you need to downgrade the software first on the secondary node and then on the primary node. For instructions on downgrading each node separately, see "Downgrading a Standalone NetScaler to an Earlier Build".
Note: In an HA setup, both nodes must run NetScaler nCore or NetScaler classic. If the nodes are running NetScaler classic and you want to migrate to NetScaler nCore of the same NetScaler release, propagation and synchronization are not supported during the migration process. Once migration is complete, you have to manually enable propagation and synchronization. The same applies if you migrate from NetScaler nCore to NetScaler classic.