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
安装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
配置uring Citrix ADC Virtual Appliances to Use SR-IOV Network Interface
配置uring 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
配置uring 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
配置ure multiple IP addresses for a Citrix ADC VPX standalone instance
配置ure a high-availability setup with multiple IP addresses and NICs
配置ure a high-availability setup with multiple IP addresses and NICs by using PowerShell commands
配置ure a Citrix ADC VPX instance to use Azure accelerated networking
配置ure HA-INC nodes by using the Citrix high availability template with Azure ILB
配置ure HA-INC nodes by using the Citrix high availability template for internet-facing applications
配置ure a high-availability setup with Azure external and internal load balancers simultaneously
Upgrade and downgrade a Citrix ADC appliance
Authentication, authorization, and auditing application traffic
-
-
-
-
Troubleshooting
-
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
年代et a limit on number of requests per connection to the server
配置ure 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
Use case 15: Configure layer 4 load balancing on the Citrix ADC appliance
-
-
-
-
配置uring a CloudBridge Connector Tunnel between two Datacenters
配置uring CloudBridge Connector between Datacenter and AWS Cloud
配置uring a CloudBridge Connector Tunnel Between a Datacenter and Azure Cloud
配置uring CloudBridge Connector Tunnel between Datacenter and SoftLayer Enterprise Cloud
配置uring a CloudBridge Connector Tunnel Between a Citrix ADC Appliance and Cisco IOS Device
CloudBridge Connector Tunnel Diagnostics and Troubleshooting
-
年代ynchronizing 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 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!
Troubleshooting
If the content switching feature does not work as expected after you have configured it, you can use some common tools to access Citrix ADC resources and diagnose the problem.
Resources for troubleshooting content switching
For best results, use the following resources to troubleshoot a content switching issue on a Citrix ADC appliance:
- 配置uration file
- Relevant
newnslog
file - Trace files
- Network topology diagram for the network setup of the customer
- Citrix documentation, such as release notes, Knowledge Center articles, and Product documentation.
In addition to the preceding resources, the following tools expedite troubleshooting:
- The
iehttpheaders
or a similar utility - The Wireshark application customized for the Citrix ADC trace files
- An SSH utility for command line access
- A HyperTerminal utility to access the console
Troubleshooting content switching issues
The most common content switching issues involve the content switching feature not working at all, or working only intermittently, and Service Unavailable responses.
Issue
The content switching feature is not functioning.
Resolution
Check the configuration as follows:
- Verify that the appliance is licensed for content switching.
- Verify that the feature is enabled.
- From the configuration file, verify that valid content switching policies are correctly bound to the load balancing virtual servers.
Issue
Client receives a 503 - Service Unavailable response.
Resolution
- Verify the URL and policy bindings. The client receives the 503 response when none of the policies you have configured is evaluated and no default load balancing virtual server is defined and bound to the content switching virtual server.
- From the configuration, verify the policies and the URL is accessed by the client.
- Verify that for every type of request the respective policy is evaluated. If the policy is not evaluated, check the policy expression and update it if necessary.
- Verify the URL and HTTP request and response headers. To do so, record an
HTTPHeader
trace and, if necessary, record the packet traces on the appliance and the client.
Issue
Intermittently, the content switching feature is not working as expected.
Resolution
年代tudy the network topology diagram, if available, of the setup to understand the various devices installed between the client and the servers.
Verify the configuration and policy bindings. Make sure that the URL in the policy expression matches to the one in the client request.
Verify that appropriate priorities are assigned to the policies. An incorrect precedence or priority assigned to a policy can cause a problem.
Run the following commands to verify the bindings and the values of the policy select counters in the output of the commands:
show cs vserver \
show cs policy \
stat cs vserver \
Using
iehttpheaders
or a similar utility, determine whether the HTTP headers for the requests or responses provide any pointers to the issue.Check the release notes and Knowledge Center articles.
如果问题仍未解决,Citrix联系Technical Support with appropriate data for further investigation.
年代hare
年代hare
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.