Application Delivery Management

Force a secondary NetScaler instance to stay secondary

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


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 Console:

  1. In NetScaler Console, navigate to Infrastructure > Instances > NetScaler > VPX tab, and then select an instance.

  2. Select instances in an HA setup from the instances listed under the selected instance type.

  3. From the Action menu, select Stay Secondary.

  4. Click Yes to confirm the execution of the “Stay Secondary” action.

    Create stay secondary

Force a secondary NetScaler instance to stay secondary

In this article