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
亿旺资讯公司ed 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 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 e stato tradotto automaticamente。(Esclusione di responsabilità))
翻译失败!
Retrieve location details from user IP address using geolocation database
NoteThis feature is available from Citrix ADC release 12.1 build 50.x and later.
The Citrix ADC appliance can get user location details like continent, county, and city. For any public IP address from a geo location database. It is performed using the advanced policy infrastructure. The retrieved location details are then used in a rewrite action or a responder action for performing the following use cases.
- Insert an HTTP header with user location details (such as country, city information) when sending the client request to the back-end server.
- Add country name in the HTML page response for an invalid user.
设备细节我们也可以记录位置ing the audit logging mechanism.
Getting user location details using geolocation functions
The components interact as per the following:
- User sends a client request from a particular geographic location.
- The Citrix ADC appliance looks for the user IP address from the client request and retrieves the geo location details. The details include continent, country, region, city, ISP, organization, or custom details from a geolocation database.
- Once the location details are retrieved, the appliance uses either a responder policy or a rewrite policy to evaluate the request.
- In a rewrite policy, the appliance adds a header with the geo location details and sends it to the back-end server. For example, insert a custom HTTP header with country information.
- In a responder policy, the appliance evaluates the HTTP request and based on policy evaluation, allows access to the users or redirects the user to an error page. It states the region from where they are accessing the application does not have access.
Setting up geolocation database
As a pre-requisite, you must have a geolocation database to run on the Citrix ADC appliance. The geolocation database files are available with Citrix ADC firmware. To download the database files from a vendor, convert it into Citrix ADC format and import it into your appliance. For more information about the geolocation database, seeAdd a location file to create static proximity databasetopic.
Geolocation functions
The following table gives a list of geolocation functions that retrieves location details of any public IP address. These functions can be used in rewrite or responder policies.
Geolocation function | Example |
---|---|
CLIENT.IP.SRC.LOCATION | Asia.In.Karnataka.Bangalore |
CLIENT.IP.SRC.LOCATION.GET (1).LOCATION_LONG | India |
CLIENT.IP.SRC.LOCATION(3) | Asia.In.Karnataka |
CLIENT.IP.SRC.LAT_LONG | 12,77 |
CLIENT.IPV6.SRC.LOCATION | North America.US.California.Santa Clara.Verizon.Citrix |
CLIENT.IPV6.SRC.LOCATION(3) | North America.US.California |
CLIENT.IPV6.SRC.LOCATION.GET(1).LOCATION_LONG | United States |
CLIENT.IPV6.SRC.LOCATION.GET(3) | California |
CLIENT.IPV6.SRC.LAT_LONG | 36, -119 |
Configuring geolocation functions
To configure geolocation functions using advanced policy infrastructure, you must enable the load balancing, rewrite, and responder features and then complete the following use cases.
Enable load balancing, responder, rewrite features
If you want the Citrix ADC appliance to authorize user access from a particular geo location, you must enable the load balancing, rewrite, and responder features.
enable ns feature loadbalancing rewrite responder
Use case 1: Configuring geolocation function for redirecting invalid users outside geo location
When a user from India is requesting access to a webpage, block the request and respond with an HTML page with country name.
The following steps help you to complete the configuration of this use case.
- Add responder action
- Add responder policy
- Bind responder policy to load balancing server
For more information about the GUI procedures for rewrite action and rewrite policy configuration, seeRespondertopic
Add responder action
Add a responder action to respond with HTML page with country name. At the command prompt, type:
add responder action ( | ) [-comment ] [-responseStatusCode ][-reasonPhrase ]
Example:
add responder action responder_act respondwith "HTTP.REQ.VERSION + \" 304 Requested Page not allowed in your country - \" + CLIENT.IP.SRC.LOCATION.GET (1).LOCATION_LONG + \"\r\n\""
Add audit log message action
You can configure audit message actions to log messages at various log levels, either in syslog format only or in both syslog andnewnslog
formats. Audit-message actions use expressions to specify the format of the audit messages. To create an audit message action by using the command line interface
At the command prompt, type:add audit messageaction
Example:
add audit messageaction msg1 DEBUG "\"Request Location: \"+CLIENT.IP.SRC.LOCATION"
Add responder policy
Add a responder policy to identify requests coming from India and associate the responder action to this policy. At the command prompt, type:
add responder policy [] [-comment ] [-logAction ] [-appflowAction ]
Example:
add responder policy responder_pol CLIENT.IP.SRC.MATCHES_LOCATION("Asia.India.*.*.*.*") responder_act -logaction msg1
Bind responder policy to load balancing server
Bind the responder policy to a load balancing virtual server of type HTTP/SSL. At the command prompt, type:
bind lb vserver -policyName < policy_name > -priority <> -type
Example:
bind lb vserver http_vserver -policyName responder_pol -priority 100 -type REQUEST
Use case 2: Configuring geolocation function for inserting new HTTP header with location details for back-end to respond
Consider a scenario, where a Citrix ADC appliance must insert the user location in the HTTP header of a request sent to the application server so that the server can use the information for some business logic. The following steps help you to complete the configuration of this use case.
- Add rewrite action
- Add rewrite policy
- Bind rewrite policy to load balancing
For more information about the GUI procedures for rewrite action and rewrite policy configuration, seeRespondertopic.
Add rewrite action
Add a rewrite action to insert a custom HTTP header with user geolocation details in the request and send it back-end servers. At the command prompt, type:
add rewrite action [] [-pattern | -search ] [-refineSearch ][-comment ]
Example:
add rewrite action rewrite_act insert_http_header "User_location" CLIENT.IP.SRC.LOCATION
Add rewrite policy
Add a rewrite policy to evaluate if the rewrite action must be run. In this case, all requests going to the application server must have a custom HTTP header, so the rule can be “true.” At the command prompt, type:
add rewrite policy [] [-comment ] [-logAction ]
Example:
add rewrite policy rewrite_pol true rewrite_act -logaction log_act
Bind rewrite policy to load balancing
Bind the rewrite policy to the required load balancing virtual server of type HTTP/SSL. At the command prompt, type:
bind lb vserver -policyName < policy_name > -priority <> -type
Example:
bind lb vserver http_vserver -policyName rewrite_pol -priority 100 -type REQUEST
Syslog support for logging geolocation details (optional)
If you prefer to log the user’s geolocation details, you must specify the SYSLOG action to be performed when a request matches the policy. The appliance stores the details as a log message in the ns.log file. For more information about SYSLOG and NSLOG auditing, seeAudit loggingtopic.
Output for user geolocation details
The following output is logged in the appliance using the SYSLOG ornewnslog
action if you try to access an application from the Bangalore location and if the appliance uses the geolocation function, “CLIENT.IP.SRC.LOCATION’.
Asia.India.Karnataka.Banglore
Sample output log:
07/23/2018:19:03:54 GMT Debug 0-PPE-0 : default REWRITE Message 22 0 : "Request Location: asia.in.karnataka.bangalore.*.*" 07/23/2018:19:23:55 GMT Debug 0-PPE-0 : default RESPONDER Message 32 0 Done
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.
开发、发布和时间的功能s 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.