-
Getting Started with Citrix ADC
-
Deploy a Citrix ADC VPX instance
-
Install a Citrix ADC VPX instance on Microsoft Hyper-V servers
-
Install a Citrix ADC VPX instance on Linux-KVM platform
-
Prerequisites for Installing Citrix ADC VPX Virtual Appliances on Linux-KVM Platform
-
Provisioning the Citrix ADC Virtual Appliance by using OpenStack
-
Provisioning the Citrix ADC Virtual Appliance by using the Virtual Machine Manager
-
Configuring Citrix ADC Virtual Appliances to Use SR-IOV Network Interface
-
Configuring Citrix ADC Virtual Appliances to use PCI Passthrough Network Interface
-
Provisioning the Citrix ADC Virtual Appliance by using the virsh Program
-
Provisioning the Citrix ADC Virtual Appliance with SR-IOV, on OpenStack
-
Configuring a Citrix ADC VPX Instance on KVM to Use OVS DPDK-Based Host Interfaces
-
-
Deploy a Citrix ADC VPX instance on Microsoft Azure
-
Network architecture for Citrix ADC VPX instances on Microsoft Azure
-
Configure multiple IP addresses for a Citrix ADC VPX standalone instance
-
Configure a high-availability setup with multiple IP addresses and NICs
-
Configure a high-availability setup with multiple IP addresses and NICs by using PowerShell commands
-
Configure HA-INC nodes by using the Citrix high availability template with Azure ILB
-
Configure address pools (IIP) for a Citrix Gateway appliance
-
-
Upgrade and downgrade a Citrix ADC appliance
-
Solutions for Telecom Service Providers
-
Load Balance Control-Plane Traffic that is based on Diameter, SIP, and SMPP Protocols
-
Provide Subscriber Load Distribution Using GSLB Across Core-Networks of a Telecom Service Provider
-
Authentication, authorization, and auditing application traffic
-
Configuring authentication, authorization, and auditing policies
-
Configuring Authentication, authorization, and auditing with commonly used protocols
-
Use an on-premises Citrix Gateway as the identity provider for Citrix Cloud
-
Troubleshoot authentication issues in Citrix ADC and Citrix Gateway with aaad.debug module
-
-
-
-
-
-
Persistence and persistent connections
-
Advanced load balancing settings
-
Gradually stepping up the load on a new service with virtual server–level slow start
-
Protect applications on protected servers against traffic surges
-
Retrieve location details from user IP address using geolocation database
-
Use source IP address of the client when connecting to the server
-
Use client source IP address for backend communication in a v4-v6 load balancing configuration
-
Set a limit on number of requests per connection to the server
-
Configure automatic state transition based on percentage health of bound services
-
-
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
-
-
-
-
-
Authentication and authorization
-
-
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 Citrix ADC Appliance and Cisco IOS Device
-
CloudBridge Connector Tunnel Diagnostics and Troubleshooting
-
-
Synchronizing Configuration Files in a High Availability Setup
-
Restricting High-Availability Synchronization Traffic to a VLAN
-
Understanding the High Availability Health Check Computation
-
Managing High Availability Heartbeat Messages on a Citrix ADC Appliance
-
Remove and Replace a Citrix ADC in a High Availability Setup
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!
Delaying Preemption
By default, a backup VIP address preempts the master VIP address immediately after its priority becomes higher than that of the master VIP. When configuring a backup VIP address, you can specify an amount of time by which to delay the preemption. Preemption delay time is a per-node setting for each backup VIP address.
The preemption delay setting for a backup VIP does not apply in the following conditions:
- The node of the master VIP goes down. In this case, the backup VIP takes over as the master VIP after the dead interval set on the backup VIP’s node.
- The priority of the master VIP is set to zero. The backup VIP takes over as the master VIP after the dead interval set on the backup VIP’s node.
Example: Delaying Preemption
Consider an active-active deployment consisting of Citrix ADC appliances NS1 and NS2. Virtual IP address VIP1 is configured on each of these appliances. Because of their priorities, VIP1 is master on NS2. Preemption is enabled and preemption delay time is set for VIP1 on these two nodes.
The following table lists the settings used in this example.
Entity and Parameters | Settings on NS1 | Settings on NS2 |
---|---|---|
VIP1 (for reference purposes only) | IP address: 192.0.1.10, VRID: 10, Priority: 100, Preemption: Enabled, Preemption delay time: 1000 seconds | IP address: 192.0.1.10, VRID: 10, Priority: 200, Preemption: Enabled, Preemption delay time: 2000 seconds |
Dead Interval | 1 Seconds | 2 Seconds |
Following are some examples of possible preemption behavior in this setup:
- If the priority of VIP1 on NS1 is set to a value (for example, 210) higher than that of VIP1 on NS2, VIP1 on NS1 takes over as master after its set preemption delay time (1000 secs).
- If a third node NS3 with the following VRRP settings is added to this deployment, VIP1 on NS3 becomes master after its set preemption delay time (3000 secs).
- VIP1
- VRID: 30
- IP address:
- Priority = 300
- Preemption delay time = 3000 seconds
- VIP1
- If NS2 goes down, VIP1 on NS1 takes over as master after 1 second (set dead interval on NS1). Preemption delay time for VIP1 on NS1 does not apply in this case.
- If NS2 goes down and NS1 restarts, VIP1 on NS1 becomes master 1 second (set dead interval on NS1) after NS1 comes up. Preemption delay time for VIP1 on NS1 does not apply in this case.
- If the priority of VIP1 on NS2 is set to zero, VIP1 goes to standby mode. VIP1 on NS1 takes over as master after 1 second (set dead interval on NS1). Preemption delay time for VIP1 on NS1 does not apply in this case.
Configuring Delay Preemption for IPv4 Active-Active Mode
To configure preemption delay time for a VIP address, you set the preemption delay timer parameter of the associated Virtual MAC address. You can the set this parameter when you add the address, or you can modify an existing Virtual MAC address.
To configure preemption delay time by using the CLI:
- To set the preemption delay time while adding a Virtual MAC, at the command prompt, type:
- add vrID <id> -preemptiondelaytimer <secs>
- show vrID
- To set the preemption delay time while modifying a Virtual MAC, at the command prompt, type:
- set vrID <id> -preemptiondelaytimer <secs>
- show vrID
To configure preemption delay time by using the GUI:
- Navigate to System > Network > VMAC.
- On the VMAC tab. While adding a new Virtual MAC, or editing an existing Virtual MAC, set the Preemption Delay Timer parameter.
Sample configuration:
The following configuration uses the settings listed in table in section Example: Delaying Preemption.
Settings on NS1
> set vrid param –deadInterval 1
Done
> add ns ip 192.0.1.10 255.255.255.255 –type VIP
Done
> add vrid 10 –Priority 100 –Preemption Enable –preemptiondelaytimer 1000
Done
> bind ns ip 192.0.1.10 255.255.255.255 –vrid 10
Done
Settings on NS2
> set vrid param –deadInterval 2
Done
> add ns ip 192.0.1.10 255.255.255.255 –type VIP
Done
> add vrid 20 –Priority 200 –Preemption Enable –preemptiondelaytimer 2000
Done
> set ns ip 192.0.1.10 255.255.255.255 –vrid 10
Done
Configuring Delay Preemption for IPv6 Active-Active Mode
To configure preemption delay time for a VIP6 address, you set the preemption delay timer parameter of the associated Virtual MAC6 address. You can the set this parameter when you add the Virtual MAC6 address, or you can modify an existing Virtual MAC6 address.
To configure preemption delay time by using the CLI:
- To set the preemption delay time while adding a Virtual MAC6, at the command prompt, type:
- add vrID6 **<id> -preemptiondelaytimer** <secs>
- show vrID6
-
To set the preemption delay time while modifying a Virtual MAC6, at the command prompt, type:
- set vrID6 <id> -preemptiondelaytimer <secs>
- show vrID6
To configure preemption delay time by using the GUI:
- Navigate to System > Network > VMAC.
- On the VMAC6 tab. While adding a Virtual MAC6 address, or editing an existing Virtual MAC6 address, set the Preemption Delay Timer parameter.
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.