Product Documentation

Upgrading an HA Pair

Oct 08, 2017

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.

Before you start a NetScaler firmware upgrade on an HA pair, read the prerequisites mentioned in the Before You Begin section. Also, you need to consider a few HA-specific points. 

This section includes the following topics:

Points to Note

  • First upgrade the secondary node, and then the primary node.
  • 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.
  • 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.
  • When upgrading from release 10.0, 10.1, 10.5, or 11.0 you have the option to use the configuration utility or the command line interface. 
  • You cannot upgrade to NetScaler 11.1 from the following builds by using the Upgrade Wizard of the NetScaler GUI:
    • All builds of NetScaler 10.1
    • Any build before Build 57.x of NetScaler 10.5
  • If your NetScaler appliance runs any 9.x or lower release, visit the Product Matrix site for more information.

Figure 1: Upgrading an HA Pair

In the following procedure, machine A is the primary node and machine B is the secondary node before the upgrade.

localized image

Upgrade an HA Pair to Release 12.0 by Using the GUI

Follow these steps to upgrade NetScaler nodes running release 10.1, 10.5, or 11.1 in an HA mode to release 12.0, by using the GUI: 

1. Log on to the secondary node and perform the upgrade as described in "To upgrade a standalone NetScaler running release 10.0, 10.1, 10.5, 11.0, or 11.1 by using the configuration utility."

Note

Before upgrading the primary node (machine A), you have the option to test the new release by entering the force failover command at the command line interface on the secondary node (machine B). When you do so, machine B becomes the primary node. If machine B does not function as expected, enter the force failover command at the command line interface on the new primary node (machine B) forcing it to again become the secondary node, and contact Citrix Customer Service before proceeding. If machine B properly assumes the role of primary node, proceed with upgrading the former primary node (machine A).

2. Log on to the primary node and perform the upgrade as described in "Upgrade a NetScaler Standalone Appliance to Release 12.0 by Using the GUI".

Upgrade an HA Pair to Release 12.0 by Using the CLI

Follow these steps to upgrade NetScaler nodes in an HA mode, running release 10.1, 10.5, or 11.1, by using the CLI: 

On machine B (original secondary node)

1. Follow the procedure for upgrading a standalone node as described in "Upgrade a NetScaler Standalone Appliance to Release 12.0 by Using the CLI". The procedure includes optional steps to avoid losing any updates that are pushed to the /etc directory during the upgrade. 

2. After the appliance restarts, log on with the administrator credentials and enter the show ha nodecommand 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.

4. 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.

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

Here's a sample configuration in the new primary node, which is machine B.

Example: Machine B Copy

login: nsroot 

Password: nsroot 

Last login: Monday Apr  17 08:37:26 2017 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 

Note

After machine B is upgraded successfully, both synchronization and propagation are automatically disabled until you upgrade machine A.

On machine A (original primary node)

5. Follow the procedure for upgrading a standalone node as described in "Upgrade a NetScaler Standalone Appliance to Release 12.0 by Using the CLI." 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 nodecommand to verify that the appliance is a secondary node and that synchronization is disabled.

Note

After both nodes are upgraded successfully, synchronization and propagation are automatically enabled.

 

On machine A and machine B

7. After successfully upgrading both the nodes, run the show ha node command to verify that synchronization and propagation are enabled on the primary node and synchronization is successful and propagation is enabled on the secondary node.

Here's an example configuration of the new primary node (machine B) and the new secondary node (machine A).

Example: On Primary Node (Machine B) Copy

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 

Example: On Secondary node (Machine A) Copy

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

On machine B (new primary node)

8. Enter the save ns config command to save the configuration.

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

Note

You can enter the force failover command again to make machine A (original primary node) as the primary node and machine B (original secondary node) as the secondary node.

For additional information, see this support article "How to Upgrade Software on NetScaler Appliances in High Availability Setup."