-
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 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
-
-
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
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!
Managing Client Connections
To ensure efficient management of client connections, you can configure the content switching virtual servers on the Citrix ADC appliance to use the following features:
-
Configuring the ICMP Response. You can configure the Citrix ADC appliance to send ICMP responses to PING requests according to your settings. On the IP address corresponding to the virtual server, set the ICMP RESPONSE to VSVR_CNTRLD, and on the virtual server, set the ICMP VSERVER RESPONSE.
The following settings can be made on a virtual server:
- When you set ICMP VSERVER RESPONSE to PASSIVE on all virtual servers, the Citrix ADC appliance always responds.
- When you set ICMP VSERVER RESPONSE to ACTIVE on all virtual servers, the ADC appliance responds even if one virtual server is UP.
- When you set ICMP VSERVER RESPONSE to ACTIVE on some and PASSIVE on others, ADC appliance responds even if one virtual server set to ACTIVE is UP.
Redirecting Client Requests to a Cache
The Citrix ADC cache redirection feature redirects HTTP requests to a cache. You can significantly reduce the burden of responding to HTTP requests and improve your Web site performance through proper implementation of the cache redirection feature.
A cache stores frequently requested HTTP content. When you configure cache redirection on a virtual server, the Citrix ADC appliance sends cacheable HTTP requests to the cache and non-cacheable HTTP requests to the origin Web server. For more information on cache redirection, see “Cache Redirection.
To configure cache redirection on a virtual server by using the command line interface
At the command prompt, type:
set cs vserver <name> -cacheable <Value>
Example
set cs vserver Vserver-CS-1 -cacheable yes
To configure cache redirection on a virtual server by using the configuration utility
- Navigate to Traffic Management > Content Switching > Virtual Servers, and open a virtual server.
- In Advanced Settings, select Traffic Settings, and select Cacheable.
Enabling Delayed Cleanup of Virtual Server Connections
Under certain conditions, you can configure the down state flush setting to terminate existing connections when a service or a virtual server is marked DOWN. Terminating existing connections frees resources and in certain cases speeds recovery of overloaded load balancing setups.
To configure the down state flush setting on a virtual server by using the command line interface
At the command prompt, type:
set cs vserver <name> -downStateFlush <Value>
Example
set cs vserver Vserver-CS-1 -downStateFlush enabled
<!--NeedCopy-->
To configure the down state flush setting on a virtual server by using the configuration utility
- Navigate to Traffic Management > Content Switching > Virtual Servers, and open a virtual server.
- In Advanced Settings, select Traffic Settings, and then select Down State Flush.
Rewriting Ports and Protocols for Redirection
Virtual servers and the services that are bound to them may use different ports. When a service responds to an HTTP connection with a redirect, you may need to configure the Citrix ADC appliance to modify the port and the protocol to ensure that the redirection goes through successfully. You do this by enabling and configuring the redirectPortRewrite setting.
To configure HTTP redirection on a virtual server by using the command line interface
At the command prompt, type:
set cs vserver <name> -redirectPortRewrite <Value>
Example
set cs vserver Vserver-CS-1 -redirectPortRewrite enabled
<!--NeedCopy-->
To configure HTTP redirection on a virtual server by using the configuration utility
- Navigate to Traffic Management > Content Switching > Virtual Servers, and open a virtual server.
- In Advanced Settings, select Traffic Settings, and select Rewrite.
Inserting the IP Address and Port of a Virtual Server in the Request Header
If you have multiple virtual servers that communicate with different applications on the same service, you must configure the Citrix ADC appliance to add the IP address and port number of the appropriate virtual server to the HTTP requests that are sent to that service. This setting allows applications running on the service to identify the virtual server that sent the request.
If the primary virtual server is down and the backup virtual server is up, the configuration settings of the backup virtual server are added to the client requests. If you want the same header tag to be added, regardless of whether the requests are from the primary virtual server or backup virtual server, you must configure the required header tag on both virtual servers.
Note
This option is not supported for wildcarded virtual servers or dummy virtual servers.
To insert the IP address and port of the virtual server in the client requests by using the command line interface
At the command prompt, type:
set cs vserver <name> -insertVserverIPPort <vServerIPPORT>
Example
set cs vserver Vserver-CS-1 -insertVserverIPPort 10.201.25.136:80
<!--NeedCopy-->
To insert the IP address and port of the virtual server in the client requests by using the configuration utility
- Navigate to Traffic Management > Content Switching > Virtual Servers, and open a virtual server.
- In Advanced Settings, select Traffic Settings and, in the Virtual Server IP Port Insertion list, select VIPADDR or V6TOV4MAPPING, and specify a port header in Virtual Server IP Port Insertion Value.
Setting a Time-out Value for Idle Client Connections
You can configure a virtual server to terminate any idle client connections after a configured time-out period elapses. When you configure this setting, the Citrix ADC appliance waits for the time you specify and, if the client is idle after that time, it closes the client connection.
To set a time-out value for idle client connections by using the command line interface
At the command prompt, type:
set cs vserver <name> -cltTimeout <Value>
Example
set cs vserver Vserver-CS-1 -cltTimeout 100
<!--NeedCopy-->
To set a time-out value for idle client connections by using the configuration utility
- Navigate to Traffic Management > Content Switching > Virtual Servers, and open a virtual server.
- In Advanced Settings, select Traffic Settings, and specify a Client Idle Time-Out value.
Identifying Connections with the 4-tuple and Layer 2 Connection Parameters
You can now set the L2Conn option for a content switching virtual server. With the L2Conn option set, connections to the content switching virtual server are identified by the combination of the 4-tuple (<source IP>:<source port>::<destination IP>:<destination port>
) and Layer 2 connection parameters. The Layer 2 connection parameters are the MAC address, VLAN ID, and channel ID.
To set the L2Conn option for a content switching virtual server by using the command line interface
At the command line, type the following commands to configure the L2Conn parameter for a content switching virtual server and verify the configuration:
- set cs vserver <name> -l2Conn (**ON** | **OFF**)
- show cs vserver <name>
<!--NeedCopy-->
Example
> set cs vserver mycsvserver -l2Conn ON
Done
> show cs vserver mycsvserver
mycsvserver (192.0.2.56:80) - HTTP Type: CONTENT
State: UP
. . .
. . .
L2Conn: ON Case Sensitivity: ON
. . .
. . .
Done
>
<!--NeedCopy-->
To set the L2Conn option for a content switching virtual server by using the configuration utility
- Navigate to Traffic Management > Content Switching > Virtual Servers, and open a virtual server.
- In Advanced Settings, select Traffic Settings, and then select Layer 2 Parameters.
Share
Share
In this article
- Redirecting Client Requests to a Cache
- Enabling Delayed Cleanup of Virtual Server Connections
- Rewriting Ports and Protocols for Redirection
- Inserting the IP Address and Port of a Virtual Server in the Request Header
- Setting a Time-out Value for Idle Client Connections
- Identifying Connections with the 4-tuple and Layer 2 Connection Parameters
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group 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 Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.