-
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 High Availability Pairs in Different Subnets
-
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!
Configuring high availability pairs in different subnets
A typical high availability deployment is when both appliances in a high availability pair reside on the same subnet. A high availability deployment can also consist of two Citrix Gateway appliances in which each appliance is in a different network. This topic describes the latter configuration, and includes sample configurations and a list of differences among the high availability configurations within one network and across networks.
You can also configure link redundancy and route monitors. These Citrix Gateway functions are helpful in a cross-network high availability configuration. The functions also cover the health check process used by each Citrix Gateway to ensure that the partner appliance is active.
How independent network configuration works
The Citrix Gateway appliances are connected to different routers, called R3 and R4, on two different networks. The appliances exchange heartbeat packets through these routers. A heartbeat packet is a signal that occurs at regular intervals that ensures the connection is still active. You can expand this configuration to accommodate deployments involving any number of interfaces.
Note: If you use static routing on your network, you must add static routes between all the systems to ensure that heartbeat packets are sent and received successfully. (If you use dynamic routing on your systems, static routes are unnecessary.)
When the appliances in a high availability pair reside on two different networks, the secondary Citrix Gateway must have an independent network configuration. This means that Citrix Gateway appliances on different networks cannot share mapped IP addresses, virtual LANs, or network routes. This type of configuration, in which the Citrix Gateway appliances in a high availability pair have different configurable parameters, is known as independent network configuration or symmetric network configuration.
The following table summarizes the configurable parameters for an independent network configuration, and shows how you must set them on each Citrix Gateway:
Configurable parameters | Behavior |
---|---|
IP addresses | Citrix Gateway specific. Active only on that appliance. |
Virtual IP address | Floating. |
Virtual LAN | Citrix Gateway specific. Active only on that appliance. |
Routes | Citrix Gateway specific. Active only on that appliance. A link load balancing (LLB) route is floating. |
access control lists (ACLs) | Floating (common). Active on both appliances. |
Dynamic routing | Citrix Gateway specific. Active only on that appliance. The secondary Citrix Gateway must also run the routing protocols and peer with upstream routers. |
L2 mode | Floating (common). Active on both appliances. |
L3 mode | Floating (common). Active on both appliances. |
Reverse Network Address Translation (NAT) | Citrix Gateway specific. Reverse NAT with a virtual IP address because the NAT IP address is floating. |
Note:
IPSET in INC mode is supported with public IP addresses. For details, see Citrix ADC High Availability with Azure Load Balancer Front End IP Validated Reference Design.
Share
Share
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.