Scenario: A Citrix Administrator is configuring a Citrix ADC high availability (HA) pair with an existing primary Citrix ADC with all resources…

The scenario describes an unintended role reversal during High Availability (HA) setup, where the new, unconfigured node became primary and overwrote the existing configuration. This happens when the HA election process favors the new node. To prevent this, an administrator must explicitly control the node roles. The STAYPRIMARY setting on the existing, configured node forces it to remain the primary, ensuring its configuration is the source for synchronization. Similarly, setting the new node to STAYSECONDARY before adding it to the pair prevents it from attempting to become primary. Both settings deterministically assign the HA roles, preventing the configuration loss described.

C. Enable HA monitoring on all secondary device interfaces. This setting is for detecting interface failures on the secondary node to prevent failover to an unhealthy appliance; it does not influence the initial role election.
D. Enable HA monitoring on all primary device interfaces. This setting is used to trigger a failover if the primary node's interfaces fail. It does not control which node becomes primary during the initial HA pair formation.

1. Citrix ADC 13.1 Product Documentation

"Configuring high availability": This document outlines the HA setup process. In the section "Configure a high availability setup

" it details the node parameters. The haStatus parameter can be set to STAYPRIMARY or STAYSECONDARY. The documentation explains: "If this parameter is set to STAYPRIMARY

the node remains the primary node... If this parameter is set to STAYSECONDARY

the node remains the secondary node." This directly supports using these settings to control node roles.

2. Citrix ADC 13.1 Command Reference

"set ha node": The command reference for set ha node explicitly defines the haStatus argument.

STAYPRIMARY: "The node remains the primary node in a high availability setup."

STAYSECONDARY: "The node remains the secondary node in a high availability setup."

This confirms that these are the specific commands used to enforce the desired node state and prevent the unintended role change.

3. Citrix ADC 13.1 Product Documentation

"High availability nodes": This section describes the states of an HA node. It clarifies that the primary node's configuration is propagated to the secondary. By forcing a node to be STAYPRIMARY or STAYSECONDARY

the administrator controls the direction of this initial configuration propagation

which is the core of the solution.