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 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 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 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
这个内容是机器翻译的动力ly.
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!
Set location qualifiers
The database used to implement static proximity has the location of the GSLB sites. Each location has an IP address range and up to six qualifiers for that range. The qualifiers are literal strings and are compared in a prescribed order at run time. Every location must have at least one qualifier. The qualifier labels define the meaning of the qualifiers (context), which are user defined. Citrix ADC has two built-in contexts:
Geographic context, which has the following qualifier labels:
- Qualifier 1 – “Continent”
- Qualifier 2 – “Country”
- Qualifier 3 – “State”
- Qualifier 4 – “City”
- Qualifier 5 – “ISP”
- Qualifier 6 – “Organization”
Custom entries, which have the following qualifier labels:
- Qualifier 1 – “Qualifier 1”
- Qualifier 2 – “Qualifier 2”
- Qualifier 3 – “Qualifier 3”
- Qualifier 4 – “Qualifier 4”
- Qualifier 5 – “Qualifier 5”
- Qualifier 6 – “Qualifier 6”
If the geographic context is set with no Continent qualifier, Continent is derived from Country. Even the built-in qualifier labels are based on the context, and the labels can be changed. These qualifier labels specify the locations mapped with the IP addresses used to make static proximity decisions.
To perform a static proximity-based decision, the Citrix ADC appliance compares the location attributes (qualifiers) derived from the IP address of the local DNS server resolver with the location attributes of the participating sites. If only one site matches, the appliance returns the IP address of that site. If there are multiple matches, the site selected is the result of a round robin on the matching GSLB sites. If there is no match, the site selected is a result of a round robin on all configured sites. A site that does not have any qualifiers is considered a match.
The GEO rules for location-based policy expression allow you to check wildcard matches. This feature checks whether wildcard qualifiers match any other qualifier including non-wildcard or not. The wildcard match is done by using thematchWildcardtoany
attribute that is added to theset locationParameter
command.
ThematchWildcardtoany
attribute can be set to the following values:
- Yes:Wildcard qualifiers match any other qualifiers.
- No:Wildcard qualifiers do not match non-wildcard qualifiers but match other wildcard qualifiers. The default option isNo.
- Expression:Wildcard qualifiers in an expression match any qualifier in an LDNS location but wildcard qualifiers in the LDNS location do not match non-wildcard qualifiers in an expression.
Example:
add dns policy policy1 "CLIENT.IP.SRC.MATCHES_LOCATION(\"Continent.country *.*.*.* \“)”
To set the location parameters by using the CLI
At the command prompt, type:
set locationparameter -context -q1label [-q2label ] [-q3label ] [-q4label ] [-q5label ] [-q6label ] -matchWildcardtoany [Yes | No | Expression]
Example:
set locationparameter -context custom -q1label asia -matchWildcardtoany Yes
To set the location parameters by using the GUI
- Navigate toTraffic Management > GSLB > Database and Entries.
- UnderSettings, clickChange Location Parameters.
- In theConfigure Location Parameterspage, set the location parameters.
Configuration example (using CLI)
Consider the following network setup:
- GSLB virtual server name: gv1
- GSLB virtual server IP address: 1.1.1.2
- GSLB Service: gsvc1 bound to gv1
- Location DB file name: sample.csv
- Geolocation qualifiers: Qualifiers 1 and 2 are configured. Rest is set to match the wildcard.
- Qualifier 1–Asia
- Qualifier 2–IR
- Qualifier 3-*
- Qualifier 4-*
- Qualifier 5-*
- Qualifier 6-*
- DNS Policy-The policy, pol1, is set to drop the packets in if there is a match.
Set the location parameter and configure the DNS policy as follows:
设置locationParameter -q2label Country_Code -q3label Subdivision_1_Name -q4label Subdivision_2_Name -q5label City add locationFile "/var/netscaler/inbuilt_db/sample.csv" add gslb vserver gv1 HTTP -backupLBMethod ROUNDROBIN -tolerance 0 add dns policy pol1 "CLIENT.IP.SRC.MATCHES_LOCATION(\"Asia.IR.*.*.*.*\")||CLIENT.IP.SRC.MATCHES_LOCATION(\"Asia.SY.*.*.*.*\")||CLIENT.IP.SRC.MATCHES_LOCATION(\"Asia.SD.*.*.*.*\")||CLIENT.IP.SRC.MATCHES_LOCATION(\"Asia.KP.*.*.*.*\")||CLIENT.IP.SRC.MATCHES_LOCATION(\"North America.CU.*.*.*.*\")||CLIENT.IP.SRC.MATCHES_LOCATION(\"Europe.UA.Crimea.*.*.*.*\")" dns_default_act_Drop bind dns global pol1 1 -gotoPriorityExpression 65535 -type REQ_DEFAULT add gslb service gsvc1 1.1.1.2 HTTP 80 -publicIP 1.1.1.2 -publicPort 80 -maxClient 0 -healthMonitor NO -siteName s1 -cltTimeout 180 -svrTimeout 360 -downStateFlush ENABLED bind gslb vserver gv1 -serviceName gsvc1 bind gslb vserver gv1 -domainName www.gslbnew.com -TTL 5
Add the following client entries in the location DB file. In this example, the location DB file name is sample.csv:
10.106.24.170,10.106.24.190,,,,,,,8.0000,47.0000 10.102.82.170,10.102.82.190,Asia,,,,,,-73.9924,40.7553 10.106.24.140,10.106.24.150,,IR,,,,,51.4231,35.6961
根据前面的配置,clients between 10.106.24.170 and 10.106.24.190 do not have any wildcard qualifiers defined. The clients between 10.106.24.140 and 10.106.24.150, have qualifier 2 as IR.
Set the match wildcard qualifier to NO:
set locationparameter -matchWildcardtoany no
When the match wildcard qualifier is set to NO, the wildcard qualifiers match only the defined wildcard qualifiers. It does not match any other non-wildcard qualifier.
The DNS queries coming 10.106.24.147 match the defined wildcard qualifier (qualifier 2 = IR). Therefore, the DNS policy comes into effect and drops the queries.
When you run the
dig @10.102.82.13 www.gslbnew.com
command on the 10.106.24.147 client, the output shows that servers were not reachable.root@ns #挖@10.102.82.13 www.gslbnew.com;<<>>DiG 9.11.23 <<>> @10.102.82.13 www.gslbnew.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached
The DNS queries coming from 10.106.24.180, do not match the defined qualifiers. The DNS policy does not come into effect and the queries are processed.
Run the
dig @10.102.82.13 www.gslbnew.com
command on the 10.106.24.180 client. The output shows the GSLB virtual server’s IP address.root@ns #挖@10.102.82.13 www.gslbnew.com;<<>>DiG 9.11.23 <<>> @10.102.82.13 www.gslbnew.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64265 ;; flags: qr aa rd ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; WARNING: recursion requested but not available ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1280 ;; QUESTION SECTION: ;www.gslbnew.com. IN A ;; ANSWER SECTION: www.gslbnew.com. 5 IN A 1.1.1.2 ;; Query time: 12 msec ;; SERVER: 10.102.82.13#53(10.102.82.13) ;; WHEN: Tue Mar 29 22:46:40 UTC 2022 ;; MSG SIZE rcvd: 60
Set the match wildcard qualifier to Yes:
set locationparameter -matchWildcardtoany yes
When the match wildcard qualifier is set to yes, the wildcard qualifiers match any wildcard qualifier (defined and non-wildcard qualifier).
The DNS queries coming 10.106.24.147 match the defined qualifier (qualifier 2 = IR). Therefore, the DNS policy comes into effect and drops the queries.
Run the
dig @10.102.82.13 www.gslbnew.com
command on the 10.106.24.147 client. The output shows that servers were not reachable.root@ns #挖@10.102.82.13 www.gslbnew.com;<<>>DiG 9.11.23 <<>> @10.102.82.13 www.gslbnew.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached
The queries coming from 10.106.24.180, match the non-wildcard qualifiers. Therefore the DNS policy comes into effect and drops the queries.
Run the
dig @10.102.82.13 www.gslbnew.com
command on the 10.106.24.180 client. The output shows that servers were not reachable.root@ns #挖@10.102.82.13 www.gslbnew.com;<<>>DiG 9.11.23 <<>> @10.102.82.13 www.gslbnew.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached
Set the match wildcard qualifier to Expression:
set locationparameter -matchWildcardtoany expression
When the match wildcard qualifier is set to expression, the wildcard qualifiers match either the qualifier available in the DNS policy or the qualifiers available in the location DB file.
The DNS queries coming 10.106.24.147 match the defined wildcard qualifiers in the DNS policy. Therefore, the DNS policy comes into effect and drops the queries.
Run the
dig @10.102.82.13 www.gslbnew.com
command on the 10.106.24.147 client. The output shows that servers were not reachable.root@ns #挖@10.102.82.13 www.gslbnew.com;<<>>DiG 9.11.23 <<>> @10.102.82.13 www.gslbnew.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached
The queries coming from 10.106.24.180 do not match the qualifiers in the DNS policy. Therefore, the DNS policy does not come into effect and the queries are processed.
Run the
dig @10.102.82.13 www.gslbnew.com
command on the 10.106.24.180 client. The output shows the GSLB virtual server’s IP address.root@ns #挖@10.102.82.13 www.gslbnew.com;<<>>DiG 9.11.23 <<>> @10.102.82.13 www.gslbnew.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64265 ;; flags: qr aa rd ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; WARNING: recursion requested but not available ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1280 ;; QUESTION SECTION: ;www.gslbnew.com. IN A ;; ANSWER SECTION: www.gslbnew.com. 5 IN A 1.1.1.2 ;; Query time: 12 msec ;; SERVER: 10.102.82.13#53(10.102.82.13) ;; WHEN: Tue Mar 29 22:46:40 UTC 2022 ;; MSG SIZE rcvd: 60
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.
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.