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
配置Citrix ADC Virtual Appliances to Use SR-IOV Network Interface
Provisioning the Citrix ADC Virtual Appliance by using the virsh Program
Provisioning the Citrix ADC Virtual Appliance with SR-IOV, on OpenStack
配置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
Authentication, authorization, and auditing application traffic
-
-
-
-
-
Persistence and persistent connections
Share persistent sessions between virtual servers
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 12: Configure Citrix Virtual Desktops for load balancing
Use case 13: Configure Citrix Virtual Apps for load balancing
Use case 14: ShareFile wizard for load balancing Citrix ShareFile
-
-
-
-
Authentication and authorization
-
配置a CloudBridge Connector Tunnel Between a Citrix ADC Appliance and Virtual Private Gateway on AWS
配置a CloudBridge Connector Tunnel Between a Datacenter and Azure Cloud
配置CloudBridge Connector Tunnel between Datacenter and SoftLayer Enterprise Cloud
配置a CloudBridge Connector Tunnel Between a Citrix ADC Appliance and Cisco IOS Device
配置a CloudBridge Connector Tunnel Between a Citrix ADC Appliance and Fortinet FortiGate Appliance
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 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)
此内容已经过机器动态翻译。放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다.책임 부인
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!
Share persistent sessions between virtual servers
In some customer environments (telecom and ISP), a single server handles both control and data traffic. For a given client IP address, both control and data traffic have to be directed to the same back-end server. For this, one virtual server is required for handling client authentication traffic, and usually rule based persistency is configured on it. For example, Radius.req.avp(8).value.typecast_text_t’. The second virtual server for handling data traffic. Usually, SourceIP persistence is configured on it.
Previously, persistence entries were local to the vserver. If you had to apply persistence across multiple vservers, you had to add the vservers to a load balancing group and then apply a common persistence type to the group. The above requirement could not be achieved, because all the vservers bound to a load balancing group inherited the persistency configured on the group.
With the persistency sharing between vservers feature, you can set the new useVserverPersistency parameter for a load balancing group to allow the vservers in the group to use their own persistency parameters instead of inheriting them from the group settings. You can configure separate rule-based persistency on each vserver.
Optionally, you can also designate one of the vservers in the group as a master vserver. When a vserver is designated as a master vserver, only that vserver creates the persistence entries, which are used by all the vservers in the group. If the master vserver is down, the Citrix ADC appliance does not create any new persistence entries.
Note: Persistence sharing across vservers is supported only for rule based persistency methods. You must configure compatible rule based persistence parameters on the member virtual servers.
Example:
Assume v1 and v2 are bound to a load balancing group, v1 is a RADIUS type vserver and v2 is an HTTP type vserver. ‘Radius.req.avp(8).value.typecast_text_t’ persistency is configured on v1 and ‘client.ip.src’ is configured on v2.
When traffic flows through the RADIUS vserver v1, it creates a persistent entry based on the evaluated rule string. Later, when traffic reaches the HTTP type vserver v2, v2 checks for the persistence entries on the load balancing group and uses the same persistence session to direct traffic to the same back-end server.
配置Sharing of Persistent Sessions
To share persistency parameters across vservers in a load balancing group, you must first enable the useVserverPersistency parameter and then designate one of the vservers in the group as a master server.
To enable the useVserverPersistency parameter by using the command line interface
At the command prompt, type:
set lb group -useVserverPersistency ( ENABLED)
Example:
set lb group lb_grp1 -useVserverPersistency ENABLED
To enable the useVserverPersistency parameter by using the GUI
- Navigate toConfiguration>Traffic Management>Load Balancing>Persistency Groups.
- ClickAddto add a new group or select an existing group and clickEdit.
- SelectUse Vserver Persistence.
To designate a vserver as a master vserver by using the command line interface
At the command prompt, type:
set lb group -useVserverPersistency ( ENABLED ) -masterVserver
Example:
set lb group lb_grp1 -useVserverPersistency ENABLED –masterVserver vs1
To designate a vserver as a master vserver by using the GUI
- Navigate toConfiguration>Traffic Management>Load Balancing>Persistency Groups.
- ClickAddto add a new group or select an existing group and clickEdit.
- SelectUse Vserver Persistence.
- In theVirtual Server Namebox, click+to add the vservers to the group. You can select the available vservers or create new vservers.
- ClickCreateif you are adding a new group orCloseif you are modifying an existing group.
- Select the group for which you have enabled the useVserverPersistency parameter and clickEditto set a vserver as a master to create persistence entries.
- From theMaster vServerlist, select the vserver that has to be designated as a master vserver.
Arguments
useVserverPersistency
Allow the virtual servers in a group to use their own persistency parameters to create persistent sessions, instead of inheriting the persistency settings from the group settings. When this parameter is enabled, persistence cannot be set on the load balancing group.
When this parameter is disabled, the group’s virtual servers inherit the persistency parameters from the group settings.
When this parameter is toggled on the load balancing group, the Citrix ADC appliance flushes all the corresponding persistence entries of the group and the member virtual servers.
Possible values: ENABLED, DISABLED
Default: DISABLED
Example:
set lb group lb_grp1 -useVserverPersistency ENABLED
masterVserver
Designate a virtual server as a master virtual server in its load balancing group. Once designated, only the master virtual server can create the persistent entries used by the group.
Note: This parameter can be set only if the useVserverPersistency parameter is enabled.
Example:
set lb group lb_grp1 –masterVserver vs1
Example Configuration of Sharing Persistent Sessions by Using the Command Line Interface
The virtual servers are created
add lb vs vs1 http 10.1.10.11 80 –persistence rule –rule ‘client.ip.src’ add lb vs vs2 radius 10.2.2.2 1812 –persistenceType rule –rule ‘Radius.req.avp(8).value.typecast_text_t’
The groups are created.
add lb group lb_grp1 –persistenceType NONE –useVserverPersistency ENABLED
A virtual server in a group is designated as master vserver.
set lb group lb_grp1 –masterVserver vs1
The virtual servers are bound to the group.
绑定lb组lb_grp1 vs1绑定lb组lb_grp1 vs2
For more details, seeSetting Up Basic Load Balancingand配置Persistence Groups.
Share
Share
In this article
- 配置Sharing of Persistent Sessions
- To enable the useVserverPersistency parameter by using the command line interface
- To enable the useVserverPersistency parameter by using the GUI
- To designate a vserver as a master vserver by using the command line interface
- To designate a vserver as a master vserver by using the GUI
- Arguments
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.