Citrix Gateway

Forcing the secondary node to stay secondary

October 5, 2020

Contributed by:

In a high availability setup, you can force the secondary Citrix Gateway to stay secondary, independent of the state of the primary Citrix Gateway. When you configure Citrix Gateway to stay secondary, it remains secondary even if the primary Citrix Gateway fails.

For example, in an existing high availability setup, suppose that you need to upgrade the primary Citrix Gateway and that this process takes a specified amount of time. During the upgrade, the primary Citrix Gateway can become unavailable, but you do not want the secondary Citrix Gateway to take over. You want it to remain the secondary Citrix Gateway, even if it detects a failure in the primary Citrix Gateway.

If the status of a Citrix Gateway in a high availability pair is configured to stay secondary, it does not participate in high availability state machine transitions. You can check the status of the Citrix Gateway in the configuration utility on the Nodes tab.

This setting works on both a standalone and a secondary Citrix Gateway.

When you set the high availability node, it is not propagated or synchronized and affects only the Citrix Gateway on which the setting is configured.

To force the secondary node to stay secondary

In the configuration utility, on the Configuration tab, in the navigation pane, expand System and then click High Availability.
In the details pane, on the Nodes tab, select a node, and then click Edit.
Under High Availability Status, click Stay Secondary (Remain in Listen Mode), and then click OK.

To return Citrix Gateway to service as an active high availability appliance

In the configuration utility, on the Configuration tab, in the navigation pane, expand System and then click High Availability.
In the details pane, on the Nodes tab, select the appliance that is going to stay the primary node, and then click Open.
Under High Availability Status, click Enabled (Actively Participate in HA), and then click OK.

The official version of this content is in English. Some of the Citrix documentation content is machine translated for your convenience only. Citrix 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 Citrix 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 Citrix, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Citrix will not be held responsible for any damage or issues that may arise from using machine-translated content.

Forcing the secondary node to stay secondary

October 5, 2020

Contributed by:

October 5, 2020

Contributed by:

Forcing the secondary node to stay secondary

To force the secondary node to stay secondary

To return Citrix Gateway to service as an active high availability appliance

In this article