You follow 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.
Workaround: Use the command line interface to upgrade the NetScaler appliance.
Before upgrading the system software, make sure that you have the required licenses. For more information, see NetScaler Licensing Overview. You do not need a new license for the following upgrades:
In the following procedure, <release> and <releasenumber> represent the release version you are upgrading to, and <targetbuildnumber> represents the build number that you are upgrading to. The procedure includes optional steps to avoid losing any updates that are pushed to the /etc directory during the upgrade.
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
cp /nsconfig/syslog.conf /var/nsconfig_backup
tar –xvzf build-11.0-38.3_nc.tgz
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.
login: nsroot Password: nsroot Last login: Fri Jun 12 19:22:51 2015 from 10.252.243.134 Done > save config > shell Last login: Fri Jun 12 19:22:51 2015 from 10.252.243.134 root@NSnnn# cd /var/nsinstall root@NSnnn# cd 11nsinstall root@NSnnn# mkdir build_52 root@NSnnn# cd build_52 root@NSnnn# ftp <FTP server IP address> ftp> mget build-11.0-52_nc.tgz ftp> bye root@NSnnn# tar xzvf build-11.0-52_nc.tgz root@NSnnn# ./installns installns version (11.0-52) kernel (ns-11.0-52_nc.gz) ... ... ... Copying ns-11.0-52_nc.gz to /flash/ns-11.0-52_nc.gz ... ... Installation has completed. Reboot NOW? [Y/N] Y
In the following procedure, machine A is the primary node and machine B is the secondary node before the upgrade.
On machine B (original secondary node)
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.
login: nsroot Password: nsroot Last login: Mon Mar 26 08:37:26 2008 from 10.102.29.9 Done show ha node 2 nodes: 1) Node ID: 0 IP: 10.0.4.2 Node State: UP Master State: Primary ... Sync State: AUTO DISABLED Propagation: AUTO DISABLED ... Done
On machine A (original primary node)
On machine A and machine B
On Primary node (Machine B)
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.