Getting Started with Citrix ADC
Deploy a Citrix ADC VPX instance
Optimize Citrix ADC VPX performance on VMware ESX, Linux KVM, and Citrix Hypervisors
Apply Citrix ADC VPX configurations at the first boot of the Citrix ADC appliance in cloud
Install a Citrix ADC VPX instance on VMware ESX
配置Citrix ADC与启示l Appliances to use VMXNET3 Network Interface
配置Citrix ADC与启示l Appliances to use Single Root I/O Virtualization (SR-IOV) Network Interface
Migrating the Citrix ADC VPX from E1000 to SR-IOV or VMXNET3 Network Interfaces
配置Citrix ADC与启示l Appliances to use PCI Passthrough Network Interface
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与启示l 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 AWS
Deploy a VPX high-availability pair with elastic IP addresses across different AWS zones
Deploy a VPX high-availability pair with private IP addresses across different AWS zones
Configure a Citrix ADC VPX instance to use SR-IOV network interface
Configure a Citrix ADC VPX instance to use Enhanced Networking with AWS ENA
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 a Citrix ADC VPX instance to use Azure accelerated networking
Configure HA-INC nodes by using the Citrix high availability template with Azure ILB
Configure a high-availability setup with Azure external and internal load balancers simultaneously
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
Basic components of authentication, authorization, and auditing configuration
On-premises Citrix Gateway as an identity provider to Citrix Cloud
Authentication, authorization, and auditing configuration for commonly used protocols
Troubleshoot authentication and authorization related issues
-
-
-
-
-
Customizing the Basic Content Switching Configuration
-
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
Use case 15: Configure layer 4 load balancing on the Citrix ADC appliance
-
-
-
Authentication and authorization for System Users
-
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!
Customizing the basic content switching configuration
After you configure a basic content switching setup, you might need to customize it to meet your requirements. If your web servers are UNIX-based and rely on case sensitive pathnames, you can configure case sensitivity for policy evaluation. You can also set precedence for evaluation of the content switching policies that you configured. You can configure HTTP and SSL content switching virtual servers to listen on multiple ports instead of creating separate virtual servers. If you want to configure content switching for a specific a virtual LAN, you can configure a content switching virtual server with a listen policy.
Configuring case sensitivity for policy evaluation
You can configure the content switching virtual server to treat URLs as case sensitive in URL-based policies. When case sensitivity is configured, the Citrix ADC appliance considers the case when evaluating policies. For example, if case sensitivity is off, the URLs /a/1.htm and /A/1.HTM are treated as identical. If case sensitivity is on, those URLs are treated as separate and can be switched to different targets.
To configure case sensitivity by using the command line interface
At the command prompt, type:
set cs vserver \
Example:
set cs vserver Vserver-CS-1 -caseSensitive ON
To configure case sensitivity by using the configuration utility
- Navigate toTraffic Management > Content Switching > Virtual Servers, and open a virtual server.
- InAdvanced Settings, selectTraffic Settings, and then select Case Sensitive.
Setting the Precedence for Policy Evaluation
Precedence refers to the order in which policies that are bound to a virtual server are evaluated. You need not configure precedence, the default precedence often works correctly.
You can configure either URL-based precedence or rule-based precedence in the following scenarios:
- One policy or set of policies must be applied first
- Another policy or set of policies is applied only if the first set does not match a request.
Precedence with URL-Based Policies
If there are multiple matching URLs for the incoming request, the precedence (priority) for URL-based policies is:
- Domain and exact URL
- Domain, prefix, and suffix
- Domain and suffix
- Domain and prefix
- Domain only
- Exact URL
- Prefix and suffix
- Suffix only
- Prefix only
- Default
If you configure precedence based on URL, the request URL is compared to the configured URLs. If none of the configured URLs match the request URL, then rule-based policies are checked. If the request URL does not match any rule-based policies, or if the content group selected for the request is down, then the request is processed as follows:
- If you configure a default group for the content switching virtual server, then the request is forwarded to the default group.
- If the configured default group is down or if no default group is configured, then an “HTTP 404 Not Found” error message is sent to the client.
Note
You must configure URL-based precedence if the content type (for example, images) is the same for all clients. However, if different types of content must be served based on client attributes (such as Accept-Language), you must use rule-based precedence.
Precedence with Rule-Based Policies
If you configure precedence based on rules, which is the default setting, the request is tested based on the rule-based policies you have configured. If the request does not match any rule-based policies, or if the content group selected for the incoming request is down, the request is processed in the following manner:
- If a default group is configured for the content switching virtual server, the request is forwarded to the default group.
- If the configured default group is down or if no default group is configured, an “HTTP 404 Not Found” error message is sent to the client.
通过使用命令行配置优先级interface
At the command prompt, type:
set cs vserver \
Example:
set cs vserver Vserver-CS-1 -precedence RULE
To configure precedence by using the configuration utility
- Navigate toTraffic Management > Content Switching > Virtual Servers, and open a virtual server.
- 在高级设置tings, selectTraffic Settings, and then specify Precedence.
Support for Multiple Ports for HTTP and SSL Type Content Switching Virtual Servers
You can configure the Citrix ADC so that HTTP and SSL content switching virtual servers listen on multiple ports, without having to configure separate virtual servers. This feature is especially useful if you want to base a content switching decision on a part of the URL and other L7 parameters. Instead of configuring multiple virtual servers with the same IP address and different ports, you can configure one IP address and specify the port as *. As a result, the configuration size is also reduced.
To configure an HTTP or SSL content switching virtual server to listen on multiple ports by using the command line
At the command prompt, type:
add cs vserver \
Example
> add cs vserver cs1 HTTP 10.102.92.215 * Done > sh cs vserver cs1 cs1 (10.102.92.215:*) - HTTP Type: CONTENT State: UP Last state change was at Tue May 20 01:15:49 2014 Time since last state change: 0 days, 00:00:03.270 Client Idle Timeout: 180 sec Down state flush: ENABLED Disable Primary Vserver On Down : DISABLED Appflow logging: ENABLED Port Rewrite : DISABLED State Update: DISABLED Default: Content Precedence: RULE Vserver IP and Port insertion: OFF L2Conn: OFF Case Sensitivity: ON Authentication: OFF 401 Based Authentication: OFF Push: DISABLED Push VServer: Push Label Rule: none IcmpResponse: PASSIVE RHIstate: PASSIVE TD: 0 Done
To configure an HTTP or SSL content switching virtual server to listen on multiple ports by using the configuration utility
- Navigate toTraffic Management > Content Switching > Virtual Servers, and create a virtual server of type HTTP or SSL.
- Use an asterisk (*) to specify the port.
Configuring per-VLAN Wildcard Virtual Servers
If you want to configure content switching for traffic on a specific VLAN, you can create a wildcard virtual server with a listen policy that restricts it to processing traffic only on the specified VLAN.
To configure a wildcard virtual server that listens to a specific VLAN by using the command line interface
At the command prompt, type:
add cs vserver \ \ IPAddress `* Port *` -listenpolicy \ \[-listenpriority \\]
Example:
add cs vserver Vserver-CS-vlan1 ANY * * -listenpolicy "CLIENT.VLAN.ID.EQ(2)" -listenpriority 10
To configure a wildcard virtual server that listens to a specific VLAN by using the configuration utility
Navigate toTraffic Management > Content Switching > Virtual Servers, and configure a virtual server. Specify a listen policy that restricts it to processing traffic only on the specified VLAN.
After you have created this virtual server, you bind it to one or more services as described inSetup basic load balancing.
Configuring the Microsoft SQL Server Version Setting
You can specify the version of Microsoft® SQL Server® for a content switching virtual server that is of type MSSQL. The version setting is recommended if you expect some clients to not be running the same version as your Microsoft SQL Server product. The version setting provides compatibility between the client-side and server-side connections by ensuring that all communication conforms to the server’s version.
To set the Microsoft SQL Server version parameter by using the command line interface
At the command prompt, type the following commands to set the Microsoft SQL Server version parameter for a content switching virtual server and verify the configuration:
设置cs vserver \ <名称\ > -mssqlServerVersion \ < mssqlServerVersion\>
show cs vserver \
Example
> set cs vserver myMSSQLcsvip -mssqlServerVersion 2008R2 Done > show cs vserver myMSSQLcsvip myMSSQLcsvip (192.0.2.13:1433) - MSSQL Type: CONTENT State: UP . . . . . . MSsql Server Version: 2008R2 . . . . . . Done >
To set the Microsoft SQL Server version parameter by using the configuration utility
- Navigate toTraffic Management > Content Switching > Virtual Servers, configure a virtual server, and specify the protocol as MSSQL.
- InAdvanced Settings, specify theServer Version.
Enable external TCP health check for UDP virtual servers
In public clouds, you can use the Citrix ADC appliance as a second-tier load balancer when the native load balancer is used as a first tier. The native load balancer can be an application load balancer (ALB) or a network load balancer (NLB). Most of the public clouds do not support UDP health probes in their native load balancers. To monitor the health of the UDP application, public clouds recommend adding a TCP-based endpoint to your service. The endpoint reflects the health of the UDP application.
The Citrix ADC appliance supports the external TCP-based health check for a UDP virtual server. This feature introduces a TCP listener on the VIP of the content switching virtual server and the configured port. The TCP listener reflects the status of the virtual server.
To enable external TCP health check for UDP virtual servers by using CLI
At the command prompt, type the following command to enable an external TCP health check with the tcpProbePort option:
add cs vserver -tcpProbePort
Example:
add cs vserver Vserver-CS-1 UDP 10.102.29.161 5002 -tcpProbePort 5000
To enable external TCP health check for UDP virtual servers by using GUI
- Navigate toTraffic Management > Content Switching > Virtual Servers, and then create a virtual server.
- ClickAddto create a virtual server.
- In theBasic Settingspane, add the port number in theTCP Probe Portfield.
- ClickOK.
Share
Share
In this article
- Configuring case sensitivity for policy evaluation
- Setting the Precedence for Policy Evaluation
- Support for Multiple Ports for HTTP and SSL Type Content Switching Virtual Servers
- Configuring per-VLAN Wildcard Virtual Servers
- Configuring the Microsoft SQL Server Version Setting
- Enable external TCP health check for UDP virtual servers
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.