Product Documentation

Upgrading or Downgrading the NetScaler Cluster

Aug 31, 2016

All the nodes of a NetScaler cluster must be running the same software version. Therefore, to upgrade or downgrade the cluster, you must upgrade or downgrade each NetScaler appliance of the cluster, one node at a time.

A node that is being upgraded or downgraded is not removed from the cluster. The node continues to be a part of the cluster and serves traffic uninterrupted, except for the down-time when the node reboots after it is upgraded or downgraded.

However, due to software version mismatch among the cluster nodes, configuration propagation is disabled on the cluster and is enabled only after all the cluster nodes are of the same version. Since configuration propagation is disabled during upgrading on downgrading a cluster, you cannot perform any configurations through the cluster IP address during this time.

Important

  • Configurations can be lost on downgrading the cluster.
  • When you are upgrading a cluster to NetScaler 11.0 build 64.x from an earlier NetScaler 11.0 build, cluster configuration propagation is disabled. This exception arises because the cluster version in build 64.x is different from the one in previous NetScaler 11.0 builds.

Traditionally, this issue occurred only during an upgrade of a cluster to a different NetScaler version (for example, from 10.5 to 11.0). It must be noted that normally the cluster version matches the NetScaler version.

Note: Configuration propagation remains disabled until all the cluster nodes are upgraded to Build 64.x.

Points to note before upgrading or downgrading the cluster

  • You cannot add cluster nodes while upgrading or downgrading the cluster software version.
  • You can perform node-level configurations through the NSIP address of individual nodes, but make sure to perform the same configurations on all the nodes to maintain them in synch.
  • You cannot execute the "start nstrace" command from the cluster IP address when the cluster is being upgraded. However, you can get the trace of individual nodes by performing this operation on individual cluster nodes through their NetScaler IP (NSIP) address.
  • Owing to changes in cluster licensing that were made in NetScaler 10.5 Build 52.11 (see license requirements), look into the following:

    • If the cluster is setup in a build prior to NetScaler 10.5 Build 52.11, the cluster will work with the separate cluster license file. No changes are required.

    • If the cluster is setup in NetScaler 10.5 Build 52.11 or later releases and then downgraded to a build prior to NetScaler 10.5 Build 52.11, the downgraded cluster will not work as it now expects a separate cluster license file.
  • While upgrading from any NetScaler 10.1 build to a later release, syncookie must be disabled on all TCP profiles (using the "set ns tcpProfile <name> -synCookie DISABLED" command) and after that a striped SNIP must be added on the CLIP subnet. Once upgraded, syncookie can be enabled again.
  • While upgrading the NetScaler appliance from a NetScaler 10.1 build to a NetScaler 10.5 build, do not execute the "show audit messages" command as this can cause the NetScaler appliance to become unresponsive.
  • NetScaler 10.5 54.x and 55.x builds are not suitable for cluster deployment. This is because, for services that need probing, SYN packets are processed locally (on the flow receiver) even though syncookie is disabled.
  • When a cluster is being upgraded, it is possible that the upgraded nodes have some additional features activated that are not available on the nodes that are not upgraded. This results in a license mismatch warning while the cluster is being upgraded. This warning will be automatically resolved when all the cluster nodes are upgraded.

Important

- Citrix recommends that you wait for the previous node to become active before upgrading or downgrading the next node.

- Citrix recommends that the cluster configuration node must be upgraded/downgraded last to avoid multiple disconnect of cluster IP sessions.

To upgrade or downgrade the software of the cluster nodes

  1. Make sure the cluster is stable and the configurations are synchronized on all the nodes.

  2. Access each node through its NetScaler IP (NSIP) address and perform the following:

    1. Upgrade or downgrade the cluster node. For detailed information about upgrading and downgrading the software of an appliance, see Upgrading or Downgrading the System Software.

    2. Save the configurations.

    3. Reboot the appliance.
       
  3. Repeat step 2 for each of the other cluster nodes.