Getting Started with Citrix ADC
Deploy a Citrix ADC VPX instance
Install a Citrix ADC VPX instance on VMware ESX
配置Citrix广告C Virtual Appliances to use VMXNET3 Network Interface
配置Citrix广告C Virtual 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广告C Virtual 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广告C Virtual Appliances to Use SR-IOV Network Interface
配置Citrix广告C 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
配置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
-
-
-
-
-
Use case: Deployment of domain name based autoscale service group
Use case: Deployment of IP address based autoscale service group
-
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
-
配置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!
Use case: Deployment of domain name based autoscale service group
Tip
For information about the GSLB service groups, see配置a GSLB Service Group
Deployment scenario
两个数据中心部署在两个AWS区域,one in Sydney and one in North Virginia. Another datacenter is deployed in Azure. An AWS ELB in each AWS region is used to load balance the application servers. ALB is used for Azure to load balancing the application server. The Citrix ADC appliances are configured for GSLB for the ELBs and ALB using GSLB domain name based autoscale service group.
Important
You must configure the required security groups in AWS and attach it to the GSLB instance. Port 53 must be allowed in the security group inbound and outbound rules. Also, ports (3009 or 3011 depending on secure MEP configuration) for MEP communication must be open. For application monitoring, the corresponding ports must be allowed in the security group outbound rules.
The configuration steps for the above deployment scenario and the corresponding CLI commands are as follows:
1. Create datacenters (represented by GSLB sites).
add gslb site aws-sydney 192.0.2.2 add gslb site aws-nvirginia 198.51.100.111 add gslb site alb-southindia 203.0.113.6
2. Add a name server with the DNS gateway IP address where the GSLB node is added. This must be done in all datacenters.
add dns nameServer 8.8.8.8
3. Add servers for ELB and ALB.
add server aws-sydney_server lb-sydney-1052691850.ap-southeast-2.elb.amazonaws.com add server aws-nvirginia_server LB-nvirginia-860559595.us-east-1.elb.amazonaws.com add server alb-southindia_server alb.southindia.cloudapp.azure.com
4. Add GSLB autoscale service groups for each ELB and ALB and bind each server to the respective service group.
add gslb serviceGroup aws-nvirginia_sg HTTP -autoScale DNS -siteName aws-nvirginia add gslb serviceGroup aws-sydney_sg HTTP -autoScale DNS -siteName aws-sydney add gslb serviceGroup alb-southindia_sg HTTP -autoScale DNS -siteName alb-southindia bind gslb serviceGroup aws-nvirginia_sg aws-nvirginia_server 80 bind gslb serviceGroup aws-sydney_sg aws-sydney_server 80 bind gslb serviceGroup alb-southindia_sg alb-southindia_server 80
5. Add a GSLB virtual server and bind the application domain and the service groups to this virtual server.
add gslb vserver gv1 HTTP bind gslb vserver gv1 -serviceGroupName aws-nvirginia_sg bind gslb vserver gv1 -serviceGroupName aws-sydney_sg bind gslb vserver gv1 -serviceGroupName alb-southindia_sg
Share
Share
In this article
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.