NetScaler Console service

Force a secondary NetScaler instance to stay secondary

January 8, 2024

Contributed by:

In a High Availability (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, and 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.

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

In NetScaler Console, navigate to Infrastructure > Instances, and then select an instance under an instance type (VPX).
Select instances in an HA setup from the instances listed under the selected instance type.
From the Action box, select Stay Secondary.
Click Yes to confirm the execution of the “Stay Secondary” action.

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Was this helpful

Force a secondary NetScaler instance to stay secondary

January 8, 2024

Contributed by:

January 8, 2024

Contributed by:

Force a secondary NetScaler instance to stay secondary

In this article