How to Force a NetScaler Appliance in High Availability Setup to Stay as Primary or Secondary

How to Force a NetScaler Appliance in High Availability Setup to Stay as Primary or Secondary

book

Article ID: CTX122346

calendar_today

Updated On:

Description

This article describes how to force a NetScaler appliance in high availability setup to stay as primary or secondary.


Instructions

You can configure a NetScaler appliance in a high availability pair to stay as the primary or the secondary appliance. To do so, you can use the set ha node –hastatus <option> command on the appropriate node of the high availability pair.

You can use the following options to set the ha node –hastatus command:

  • STAYPRIMARY: This option forces the NetScaler appliance to stay in the primary mode. However, if two appliances are primary at the same time, it results in an IP conflict and split brain condition, when makes both the appliances to process the traffic.
  • STAYSECONDARY: This option forces the NetScaler appliance to stay in the secondary mode.
  • ENABLED: This is the default option. This option enables the NetScaler appliance of the high availability pair to fail over based on the high availability events.
  • DISABLED: This option disables the high availability engine.

Issue/Introduction

This article describes how to force a NetScaler appliance in high availability setup to stay as primary or secondary.

Additional Information

Citrix Documentation - Configuring Synchronization
Citrix Documentation -Forcing the Secondary Node to Stay Secondary
Citrix Documentation - Forcing the Primary Node to Stay Primary