Getting Started with Citrix NetScaler
Deploy a Citrix NetScaler VPX instance
Install a Citrix NetScaler VPX instance on Microsoft Hyper-V servers
Install a NetScaler VPX instance on Linux-KVM platform
Prerequisites for Installing NetScaler VPX Virtual Appliances on Linux-KVM Platform
Provisioning the NetScaler Virtual Appliance by using OpenStack
Provisioning the NetScaler Virtual Appliance by using the Virtual Machine Manager
Configuring NetScaler Virtual Appliances to Use SR-IOV Network Interface
Configuring NetScaler Virtual Appliances to use PCI Passthrough Network Interface
Provisioning the NetScaler Virtual Appliance by using the virsh Program
Deploying NetScaler VPX Instances on AWS
Upgrade and downgrade a NetScaler appliance
-
-
-
-
-
Overriding Static Proximity Behavior by Configuring Preferred Locations
Example of a Complete Parent-Child Configuration Using the Metrics Exchange Protocol
Configuring Global Server Load Balancing for DNS Queries with NAPTR records
Using the EDNS0 Client Subnet Option for Global Server Load Balancing
-
Persistence and persistent connections
Use case 2: Configure rule based persistence based on a name-value pair in a TCP byte stream
Use case 3: Configure load balancing in direct server return mode
Use case 6: Configure load balancing in DSR mode for IPv6 networks by using the TOS field
Use case 7: Configure load balancing in DSR mode by using IP Over IP
Use case 10: Load balancing of intrusion detection system servers
Use case 11: Isolating network traffic using listen policies
Use case 14: ShareFile wizard for load balancing Citrix ShareFile
-
-
-
-
Configuring a CloudBridge Connector Tunnel between two Datacenters
Configuring CloudBridge Connector between Datacenter and AWS Cloud
Configuring a CloudBridge Connector Tunnel Between a Datacenter and Azure Cloud
Configuring CloudBridge Connector Tunnel between Datacenter and SoftLayer Enterprise Cloud
Configuring a CloudBridge Connector Tunnel Between a NetScaler Appliance and Cisco IOS Device
CloudBridge Connector Tunnel Diagnostics and Troubleshooting
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde.(Haftungsausschluss)
Cet(中央东部东京)文章的疾病traduit automatiquement de maniere dynamique.(Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica.(Aviso legal)
此内容已经过机器动态翻译。放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다.책임 부인
Este texto foi traduzido automaticamente.(Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
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.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Configuring fail-safe mode
In an HA configuration, fail-safe mode ensures that one node is always primary when both nodes fail the health check. This is to ensure that when a node is only partially available, backup methods are enabled to handle traffic as best as possible. The HA fail-safe mode is configured 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 yet it is partially available. The UP state means that the node passed the health check.
Node A (Primary) Health State | Node B (Secondary) Health State | Default HA Behavior | Fail-Safe Enabled HA 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 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 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 enable fail-safe mode by using the command line interface
At the command prompt, type:
set HA node [-failSafe ( ON | OFF )]
Example
set ha node -failsafe ON
To enable fail-safe mode by using the GUI
- Navigate toSystem>High Availabilityand, on theNodestab, open the node.
- UnderFail-Safe Mode, select theMaintain one Primarynode even when both nodes are unhealthy option.
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.
的文档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.