Product Documentation

Upgrading to a Later Build within Release 11.1

Aug 31, 2016

To upgrade from an earlier 11.1 build to a later 11.1 build on a standalone NetScaler appliance or a high availability pair, you can use the configuration utility or the command line interface. You use the same basic procedure to upgrade either a standalone appliance or each appliance in a high availability pair, although additional considerations apply to upgrading a high availability pair.

Upgrading a Standalone NetScaler Appliance to a Later Build

In the following procedure, <targetbuildnumber> is the build number that you are upgrading to within the 11.1 release. The procedure includes optional steps to avoid losing any updates that are pushed to the /etc directory during the upgrade.

To upgrade a standalone NetScaler appliance running release 11.1 to a later build by using the command line interface

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

    save ns config

  3. Create a copy of the ns.conf file. At the shell prompt, type:
    1. cd /nsconfig
    2. cp ns.conf ns.conf.NS<releasenumber><currentbuildnumber>
    You should backup the configuration file to another computer.
  4. (Optional) If you have modified any of the following files in the /etc directory, and copied them to /nsconfig to maintain persistency, any updates that are pushed to the /etc directory during the upgrade might be lost:
    • ttys
    • resolv.conf
    • sshd_config
    • host.conf
    • newsyslog.conf
    • host.conf
    • httpd.conf
    • rc.conf
    • syslog.conf
    • crontab
    • monitrc

    To avoid losing these updates, create a /var/nsconfig_backup directory, and move the customized files to this directory. That is, move any files that you modified in /etc directory and copied to /nsconfig, by running the following command:

    cp /nsconfig/<filename> /var/nsconfig_backup

    Example:
    cp /nsconfig/syslog.conf /var/nsconfig_backup
    
  5. Create a location for the installation package. At the shell prompt, type:
    1. cd/var/nsinstall
    2. mkdir <releasenumber>nsinstall
    3. cd <releasenumber>nsinstall
    4. mkdir build_<targetbuildnumber>
    5. cd build_<targetbuildnumber>
  6. Download or copy the installation package (build-11.0-<targetbuildnumber>_nc.tgz) to the directory that you created for it. To download the installation package from the Citrix Web site, do the following:
    1. Go to MyCitrix.com, log on with your credentials, and click Downloads.
    2. In the Select a Product, select NetScaler ADC.
    3. Under Firmware, click the release and build number to download.
    4. Click Get Firmware.
     
  7. Extract the contents of the installation package. Example:
    tar –xvzf build_11.1-47.10_nc.tgz
    
  8. Run the installns script to install the new version of the system software. The script updates the /etc directory.
    Note:

    To install a FIPS appliance, run the installns script with the -F option. To automatically clean up the flash, run the installns script with the -c option.

    During the upgrade, you are prompted for an option to load a different configuration.

    If you do not want to load a different configuration and continue with the upgrade, type N. If want to load a different configuration file, then type Y. 

    If the configuration file for the build to which you are upgrading exists in the appliance, you are prompted to load that configuration.

  9. When prompted, restart the appliance.
  10. (Optional) If you performed step 4, do the following:
    1. Manually compare the files in /var/nsconfig_backup and /etc and make appropriate changes in /etc.
    2. To maintain persistency, move the updated files in /etc to /nsconfig.
    3. Restart the appliance to put the changes into effect.

Example

login: nsroot 
Password:  
Last login: Fri Jun  24 12:12:54 2016 from 10.144.7.22 
Done 
> save ns config 
> shell 
Last login: Fri Jun  24 03:51:42 from 10.103.25.64 
root@NSnnn# cd /var/nsinstall 
root@NSnnn# cd 11.1nsinstall 
root@NSnnn# mkdir build_47.10 
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  build-11.1-47.10_nc.tgz 
root@NSnnn# ./installns 
installns version (11.1-47.10) kernel (ns-11.1-47.10_nc.gz) 
The Netscaler version 11.1-47.10 checksum file is located on  
http://www.mycitrix.com under Support > Downloads > Citrix NetScaler.  
Select the Release 11.1-47.10 link to view the MD5 checksum file for build 11.1-47.10.  
 
There may be a pause of up to 3 minutes while data is written to the flash.  
Do not interrupt the installation process once it has begun.... 
... 
... 
Copying ns-11.1-47.10_nc.gz to /flash/ns-11.1-47.10_nc.gz ... 
... 
Installation has completed. 
 
Reboot NOW? [Y/N] Y

To upgrade a standalone NetScaler running release 11.1 to a later build by using the configuration utility

  1. In a web browser, type the IP address of the NetScaler, such as http://10.102.29.50.
  2. In User Name and Password, type the administrator credentials.
  3. In the configuration utility, in the navigation pane, click System.
  4. In the System Overview page, click System Upgrade.
  5. Follow the instructions to upgrade the software.
  6. When prompted, select Reboot.
    Note: After the upgrade, close all browser instances and clear your computer's cache before accessing the appliance.

Upgrading a NetScaler High Availability Pair to a Later Build

To upgrade the system software on NetScaler appliances in a high availability (HA) pair, upgrade the secondary node first, and then upgrade the primary node.
Warning: In certain cases, after you upgrade one of the nodes in an HA pair, synchronization and propagation are automatically disabled until you upgrade the other node. To determine whether synchronization and propagation are disabled, at the command line interface, type: show ha node

Points to Note
  1. If the two nodes in an HA configuration are running different NetScaler software releases, the following information does not get synchronized on the primary and secondary nodes:
    -Configuration propagation and synchronization
    -States of the services
    -Connection failover sessions
    -Persistence sessions
    The above information might not get synchronized on the primary and secondary nodes if the two nodes are running different builds of the same release. Refer to the Known Issues section of the release notes to check if your NetScaler build has this issue.
  2. Synchronization of the files in the All mode of the Sync HA files command works successfully if the two nodes in an HA configuration are running different NetScaler software releases, or the two nodes are running different builds of the same release. For more information, see Synchronising Configuration Files in High Availability Setup.
Figure 3. Upgrading a NetScaler High Availability Pair to a Later Build

In the following procedure, machine A is the original primary and machine B is the original secondary node, and <targetbuildnumber> is the build number that you are upgrading to within the 10.1 release.

To upgrade a NetScaler high availability pair to a later build by using the command line interface

On machine B (original secondary node)
  1. Follow the procedure for upgrading a standalone node as described in "Upgrading a Standalone NetScaler Appliance to a Later Build". The procedure includes optional steps to avoid losing any updates that are pushed to the /etc directory during the upgrade.
  2. After the NetScaler restarts, log on by using the administrator credentials and enter the show ha node command to verify that the appliance is a secondary node.
  3. Test the new build by entering the force failover command on the secondary node (machine B). At the command prompt type force failover.

    When you do so, machine B becomes the primary node. If machine B does not function as expected, enter the force failover command on the new primary node (machine B) forcing it to again become the secondary node, and contact Citrix Customer Service before proceeding.

  4. Enter the show ha node command to verify that machine B is the new primary node.

    On machine A (original primary node)

  5. Follow the procedure for upgrading a standalone node as described in "Upgrading a Standalone NetScaler Appliance to a Later Build." The procedure includes optional steps to avoid losing any updates that are pushed to the /etc directory during the upgrade.
  6. After the appliance restarts, log on by using the administrator credentials and enter the show ha node command to verify that the appliance is a secondary node and that synchronization and propagation are enabled. Optionally, enter the show ns runningconfig command on both the nodes and compare the result to verify that the configuration of machine A has been synchronized with that of machine B.

    On machine B (new primary node)

  7. Enter the save ns config command to save the current configuration.

    On machine A and machine B

  8. After successfully upgrading both the nodes, run the show ha node command to verify that synchronization and propagation are enabled.

    Example

    show ha node 
            Node ID:      0 
            IP:   10.0.4.2 
            Node State: UP 
            Master State: Primary 
    ... 
    ... 
            INC State: DISABLED 
            Sync State: ENABLED 
            Propagation: ENABLED 
            Enabled Interfaces : 1/1 
            Disabled Interfaces : None 
            HA MON ON Interfaces : 1/1 
    ... 
    ... 
            Local node information 
            Critical Interfaces: 1/1 
    Done 
     
     
    Show ha node 
            Node ID:      0 
            IP:   10.0.4.11 
            Node State: UP 
            Master State: Secondary 
            .. 
    	      .. 
            INC State: DISABLED 
            Sync State: SUCCESS 
            Propagation: ENABLED 
            Enabled Interfaces : 1/1 
            Disabled Interfaces : None 
            HA MON ON Interfaces : 1/1 
            . . . 
            . . .  
            Local node information: 
            Critical Interfaces: 1/1 
    Done 
    

Machine B (original secondary node) is now the primary node and machine A (original primary node) is now the secondary node.