Product Documentation

Force a secondary NetScaler instance to stay secondary

May 24, 2018

In an HA setup, the secondary node can be forced to stay secondary regardless of the state of the primary node.

For example, suppose that the primary node needs to be upgraded and the process takes a few seconds. During the upgrade, the primary node might go down for a few seconds, but you do not want the secondary node to take over; you want it to remain the secondary node even if it detects a failure in the primary node.

When you force the secondary node to stay secondary, it will remain secondary even if the primary node goes down. Also, when you force the status of a node in an HA pair to stay secondary, it does not participate in HA state machine transitions. The status of the node is displayed as STAYSECONDARY.

Forcing the node to stay secondary works on both standalone and secondary nodes. On a standalone node, you must use this option before you can add a node to create an HA pair. When you add the new node, the existing node continues to function as the primary node, and the new node becomes the secondary node. 

Note

When you force a system to remain secondary, the forcing process is not propagated or synchronized. It affects only the node on which you run the command.

To configure a secondary NetScaler instance to stay secondary by using NetScaler MAS

  1. In NetScaler MAS, navigate to Networks > Dashboard > Instances, and then select an instance under an instance type (NetScaler VPX).
  2. Select instances in an HA setup from the instances listed under the selected instance type.
  3. From the Action drop-down, select Stay Secondary.
  4. Click Yes to confirm the execution of the “Stay Secondary” action.
localized image