Getting Started with Citrix ADC
Deploy a Citrix ADC VPX instance
Optimize Citrix ADC VPX performance on VMware ESX, Linux KVM, and Citrix Hypervisors
应用程序ly Citrix ADC VPX configurations at the first boot of the Citrix ADC appliance in cloud
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 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 GSLB on an active-standby high availability setup
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
-
-
-
-
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 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
-
Synchronizing 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!
Configure GSLB on an active-standby high-availability setup
You can configure global server load balancing (GSLB) on active-standby HA deployment on Azure in three steps:
Create a VPX HA pair on each GSLB site. SeeConfigure a high-availability setup with multiple IP addresses and NICsfor information about how to create an HA pair.
Configure the Azure Load Balancer (ALB) with the front-end IP address and rules to allow GSLB and DNS traffic.
This step involves the following substeps. See the scenario in this section for the PowerShell commands used to complete these substeps.
a. Create a front-end
IPconfig
for GSLB site.b. Create a back-end address pool with IP address of NIC 1/1 of nodes in HA.
c. Create load-balancing rules for following:
TCP/3011 – gslb communication TCP/3010 - gslb communication UDP/53 - DNS communication
d. Associate back-end address pool with the LB rules created in step c.
e. Update the network security group of NIC 1/1 of nodes in both the HA pair to allow the traffic for TCP 3010, TCP 3011 and UDP 53 ports.
Enable GSLB on each HA pair.
Scenario
This scenario includes two sites - Site 1 and Site 2. Each site has an HA pair (HA1 and HA2) configured with multiple NICs, multiple IP addresses, and GSLB.
Figure:GLSB on Active-Standy HA Deployment on Azure
In this scenario, each VM has three NICs - NIC 0/1, 1/1, and 1/2. The NICs are configured for the following purposes.
NIC 0/1: to serve management traffic
NIC 1/1: to serve client-side traffic
NIC 1/2: to communicate with back-end servers
Parameter Settings
Following are sample parameters settings for the ALB. You can use different settings if you want.
$locName="South east Asia" $rgName="MulitIP-MultiNIC-RG" $pubIPName4="PIPFORGSLB1" $domName4="vpxgslbdns" $lbName="MultiIPALB" $frontEndConfigName2="FrontEndIP2" $backendPoolName1="BackendPoolHttp" $lbRuleName2="LBRuleGSLB1" $lbRuleName3="LBRuleGSLB2" $lbRuleName4="LBRuleDNS" $healthProbeName="HealthProbe"
Configure ALB with the front-end IP address and rules to allow GSLB and DNS traffic
Step 1.Create a public IP for GSLB site IP
$pip4=New-AzureRmPublicIpAddress -Name $pubIPName4 -ResourceGroupName $rgName -DomainNameLabel $domName4 -Location $locName -AllocationMethod Dynamic Get-AzureRmLoadBalancer -Name $lbName -ResourceGroupName $rgName | Add-AzureRmLoadBalancerFrontendIpConfig -Name $frontEndConfigName2 -PublicIpAddress $pip4 | Set-AzureRmLoadBalancer
Step 2.Create LB rules and update the existing ALB.
$alb = get-AzureRmLoadBalancer -Name $lbName -ResourceGroupName $rgName $frontendipconfig2=Get-AzureRmLoadBalancerFrontendIpConfig -LoadBalancer $alb -Name $frontEndConfigName2 $backendPool=Get-AzureRmLoadBalancerBackendAddressPoolConfig -LoadBalancer $alb -Name $backendPoolName1 $healthprobe=Get-AzureRmLoadBalancerProbeConfig -LoadBalancer $alb -Name $healthProbeName $alb | Add-AzureRmLoadBalancerRuleConfig -Name $lbRuleName2 -BackendAddressPool $backendPool -FrontendIPConfiguration $frontendipconfig2 -Protocol "Tcp" -FrontendPort 3011 -BackendPort 3011 -Probe $healthprobe -EnableFloatingIP | Set-AzureRmLoadBalancer $alb | Add-AzureRmLoadBalancerRuleConfig -Name $lbRuleName3 -BackendAddressPool $backendPool -FrontendIPConfiguration $frontendipconfig2 -Protocol "Tcp" -FrontendPort 3010 -BackendPort 3010 -Probe $healthprobe -EnableFloatingIP | Set-AzureRmLoadBalancer $alb | Add-AzureRmLoadBalancerRuleConfig -Name $lbRuleName4 -BackendAddressPool $backendPool -FrontendIPConfiguration $frontendipconfig2 -Protocol "Udp" -FrontendPort 53 -BackendPort 53 -Probe $healthprobe -EnableFloatingIP | Set-AzureRmLoadBalancer
Enable GSLB on each high availability pair
Now you’ve two front-end IP addresses for each ALB: ALB 1 and ALB 2. One IP address is for the LB virtual server and the other for the GSLB site IP.
HA 1 has the following front-end IP addresses:
- FrontEndIPofALB1 (for LB virtual server)
- PIPFORGSLB1 (GSLB IP)
HA 2 has the following front-end IP addresses:
- FrontEndIPofALB2 (for LB virtual server)
- PIPFORGSLB2 (GSLB IP)
The following commands are used for this scenario.
enable ns feature LB GSLB add service dnssvc PIPFORGSLB1 ADNS 53 add gslb site site1 PIPFORGSLB1 -publicIP PIPFORGSLB1 add gslb site site2 PIPFORGSLB2 -publicIP PIPFORGSLB2 add gslb service site1_gslb_http_svc1 FrontEndIPofALB1 HTTP 80 -publicIP FrontEndIPofALB1 -publicPort 80 -siteName site1 add gslb service site2_gslb_http_svc1 FrontEndIPofALB2 HTTP 80 -publicIP FrontEndIPofALB2 -publicPort 80 -siteName site2 add gslb vserver gslb_http_vip1 HTTP bind gslb vserver gslb_http_vip1 -serviceName site2_gslb_http_svc1 bind gslb vserver gslb_http_vip1 -serviceName site1_gslb_http_svc1 bind gslb vserver gslb_http_vip1 -domainName www.gslbindia.com -TTL 5
Related resources:
Share
Share
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.
文档信息的目的ly 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.