-
Install and configure the Citrix Gateway appliance
-
VPN configuration on a Citrix Gateway appliance
-
Integrate the Citrix Gateway plug-in with Citrix Workspace app
-
-
Synchronizing Configuration Files in a High Availability Setup
-
Configuring Fail-Safe Mode
-
Maintaining and Monitoring the System
-
Integrate Citrix Gateway with Citrix products
-
Integrate Citrix Gateway with Citrix Virtual Apps and Desktops
-
Configure settings for your Citrix Endpoint Management Environment
-
Configure load balancing servers for Citrix Endpoint Management
-
Configure load balancing servers for Microsoft Exchange with Email Security Filtering
-
Configure Citrix Endpoint Management NetScaler Connector (XNC) ActiveSync Filtering
-
Allow Access from mobile devices with Citrix Mobile Productivity Apps
-
Configure domain and security token authentication for Citrix Endpoint Management
-
Configure client certificate or client certificate and domain authentication
-
-
Access Citrix Virtual Apps and Desktops resources with the Web Interface
-
Configuring Additional Web Interface Settings on Citrix Gateway
-
Configuring Access to Applications and Virtual Desktops in the Web Interface
-
Integrate Citrix Gateway with Citrix Virtual Apps and Desktops
-
Configuring Settings for Your Citrix Endpoint Management Environment
-
Configuring Load Balancing Servers for Citrix Endpoint Management
-
Configuring Load Balancing Servers for Microsoft Exchange with Email Security Filtering
-
Configuring Citrix Endpoint Management NetScaler Connector (XNC) ActiveSync Filtering
-
Allowing Access from Mobile Devices with Citrix Mobile Productivity Apps
-
Configuring Domain and Security Token Authentication for Citrix Endpoint Management
-
Configuring Client Certificate or Client Certificate and Domain Authentication
-
-
Citrix Gateway Enabled PCoIP Proxy Support for VMware Horizon View
-
Configure DTLS VPN virtual server using SSL VPN virtual server
-
Proxy Auto Configuration for Outbound Proxy support for Citrix Gateway
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已动态机器翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
This content has been machine translated dynamically.
This content has been machine translated dynamically.
This content has been machine translated dynamically.
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.
Este artigo foi traduzido automaticamente.
这篇文章已经过机器翻译.放弃
Translation failed!
Configure fail-safe mode
In a high availability configuration, fail-safe mode ensures that one node is always primary when both nodes fail the health check. Fail-safe mode ensures that when a node is only partially available, backup methods can activate and can handle traffic.
You configure high availability fail-safe mode independently on each node.
The following table shows some of the fail-safe cases. The NOT_UP state means that the node failed the health check and yet the node is partially available. The UP state means that the node passed the health check.
Table 1. Fail-safe mode cases
Node A (primary) health state | Node B (secondary) health state | Default high availability behavior | Fail-safe enabled high availability behavior | Description |
---|---|---|---|---|
NOT_UP (failed last) | NOT_UP (failed first) | A (Secondary), B (Secondary) | A (Primary), B (Secondary) | If both nodes fail, one after the other, the node that was the last primary node remains primary. |
NOT_UP (failed first) | NOT_UP (failed last) | A (Secondary), B (Secondary) | A (Secondary), B (Primary) | If both nodes fail, one after the other, the node that was the last primary node remains primary. |
UP | UP | A (Primary), B (Secondary) | A (Primary), B (Secondary) | If both nodes pass the health check, no change in behavior with fail-safe enabled. |
UP | NOT_UP | A (Primary), B(Secondary) | A (Primary), B (Secondary) | If only the secondary node fails, no change in behavior with fail-safe enabled. |
NOT_UP | UP | A (Secondary), B(Primary) | A (Secondary), B(Primary) | If only the primary fails, no change in behavior with fail-safe enabled. |
NOT_UP | UP (STAYSECONDARY) | A (Secondary), B (Secondary) | A (Primary), B (Secondary) | If the secondary is configured as STAYSECONDARY, the primary remains primary even if it fails. |
To configure fail-safe mode
- 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.
- In the Configure Node dialog box, under Fail-Safe Mode, select Maintain one Primary node even when both nodes are unhealthy and then click OK.
Share
Share
In this article
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select Do Not Agree to exit.