Getting Started with Citrix ADC
Deploy a Citrix ADC VPX instance
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
配置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 HA-INC nodes by using the Citrix high availability template with Azure ILB
Upgrade and downgrade a Citrix ADC appliance
Authentication, authorization, and auditing application traffic
配置uring authentication, authorization, and auditing policies
配置uring Authentication, authorization, and auditing with commonly used protocols
Use an on-premises Citrix Gateway as the identity provider for Citrix Cloud
Troubleshoot authentication issues in Citrix ADC and Citrix Gateway with aaad.debug module
-
-
-
-
-
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
配置ure automatic state transition based on percentage health of bound services
用例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
-
配置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
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!
Deploy a Citrix ADC VPX instance on Microsoft Azure
When you deploy a Citrix ADC VPX instance on Microsoft Azure Resource Manager (ARM), you can use the Azure cloud computing capabilities and use Citrix ADC load balancing and traffic management features for your business needs. You can deploy Citrix ADC VPX instances on Azure Resource Manager either as standalone instances or as high availability pairs in active-standby modes.
You can deploy a Citrix ADC VPX instance on the Microsoft Azure in two ways:
Through Azure Marketplace. The Citrix ADC VPX virtual appliance is available as an image in the Microsoft Azure Marketplace.
Using the Citrix ADC Azure Resource Manager (ARM) json template available on GitHub.For more information, see theGitHub repository for Citrix ADC solution templates.
Prerequisite
You need some prerequisite knowledge before deploying a Citrix VPX instance on Azure.
Familiarity with Azure terminology and network details. For information, seeAzure terminology.
Knowledge of a Citrix ADC appliance. For detailed information the Citrix ADC appliance, seeCitrix ADC
Knowledge of Citrix ADC networking. See theNetworkingtopic.
How a Citrix ADC VPX instance works on Azure
In an on-premises deployment, a Citrix ADC VPX instance requires at least three IP addresses:
- Management IP address, called NSIP address
- Subnet IP (SNIP) address for communicating with the server farm
- Virtual server IP (VIP) address for accepting client requests
For more information, seeNetwork architecture for Citrix ADC VPX instances on Microsoft Azure.
Note
VPX virtual appliances can be deployed on any instance type that has two or more Intel VT-X cores and more than 2 GB memory. For more information on system requirements, seeCitrix ADC VPX data sheet. Currently, Citrix ADC VPX instance supports only the Intel processors.
In an Azure deployment, you can provision a Citrix ADC VPX instance on Azure in three ways:
- Multi-NIC multi-IP architecture
- Single NIC multi IP architecture
- Single NIC single IP
Depending on your need, you can use any of these supported architecture types.
Multi-NIC multi-IP architecture
In this deployment type, you can have more than one network interfaces (NICs) attached to a VPX instance. Any NIC can have one or more IP configurations - static or dynamic public and private IP addresses assigned to it.
For more information, see the following use cases:
配置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
Note
To avoid MAC moves and interface mutes on Azure environments, Citrix recommends you to create a VLAN per data interface (without tag) of ADC VPX instance and bind the primary IP of NIC in Azure. For more information, seeCTX224626article.
Single NIC multi IP architecture
In this deployment type, one network interfaces (NIC) associated with multiple IP configurations - static or dynamic public and private IP addresses assigned to it. For more information, see the following use cases:
- 配置ure multiple IP addresses for a Citrix ADC VPX standalone instance
- 配置ure multiple IP addresses for a Citrix ADC VPX standalone instance by using PowerShell commands
Single NIC single IP
In this deployment type, one network interfaces (NIC) associated with a single IP address, which is used to perform the functions of NSIP, SNIP, and VIP.
For more information, see the following use case:
Note
The single IP mode is available only in Azure deployments. This mode is not available for a Citrix ADC VPX instance on your premises, on AWS, or in other type of deployment.
Citrix ADC VPX licensing
A Citrix ADC VPX instance on Azure requires a license. The following licensing options are available for Citrix ADC VPX instances running on Azure.
- Subscription-based licensing: Citrix ADC VPX appliances are available as paid instances on Azure Marketplace. Subscription-based licensing is a pay-as-you-go option. Users are charged hourly. The following VPX models and license types are available on Azure Marketplace.
VPX model | License Type |
---|---|
VPX10 | Standard, Advanced, Premium |
VPX200 | Standard, Advanced, Premium |
VPX1000 | Standard, Advanced, Premium |
VPX3000 | Standard, Advanced, Premium |
Citrix provides technical support for subscription-based license instances. To file a support case, seeSupport for Citrix ADC on Azure – Subscription license with hourly price.
- Bring your own license (BYOL): If you bring your own license (BYOL), see the VPX Licensing Guide athttp://support.citrix.com/article/CTX122426. You have to:
- Use the licensing portal within Citrix website to generate a valid license.
- Upload the license to the instance.
- Citrix ADC VPX Check-In/Check-Out licensing: For more information, seeCitrix ADC VPX Check-In/Check-Out Licensing.
Starting with Citrix ADC release 12.0 56.20, VPX Express for on-premises and cloud deployments does not require a license file. For more information on Citrix ADC VPX Express see the “Citrix ADC VPX Express license” section inCitrix ADC Licensing Overview.
Note
Regardless of the subscription-based hourly license bought from Azure Marketplace, in rare cases, the Citrix ADC VPX instance deployed on Azure might come up with a default Citrix ADC license. This happens due to issues with Azure Instance Metadata Service (IMDS).
Do a warm restart before making any configuration change on the Citrix ADC VPX instance, to enable the correct Citrix ADC VPX license.
Limitations
Running the Citrix ADC VPX load balancing solution on ARM imposes the following limitations:
The Azure architecture does not accommodate support for the following Citrix ADC features:
- Clustering
- IPv6
- Gratuitous ARP (GARP)
- L2 Mode
- Tagged VLAN
- Dynamic Routing
- Virtual MAC (VMAC)
- USIP
- Jumbo Frames
If you expect that you might have to shut down and temporarily deallocate the Citrix ADC VPX virtual machine at any time, assign a static Internal IP address while creating the virtual machine. If you do not assign a static internal IP address, Azure might assign the virtual machine a different IP address each time it restarts, and the virtual machine might become inaccessible.
在Azure部署,只有以下CitrixADC VPX models are supported: VPX 10, VPX 200, VPX 1000, and VPX 3000. For for information, see the Citrix ADC VPX Data Sheet.
If you use a Citrix ADC VPX instance with a model number higher than VPX 3000, the network throughput might not be the same as specified by the instance’s license. However, other features, such as SSL throughput and SSL transactions per second, might improve.
The “deployment ID” that is generated by Azure during virtual machine provisioning is not visible to the user in ARM. You cannot use the deployment ID to deploy Citrix ADC VPX appliance on ARM.
The Citrix ADC VPX instance supports 20 Mb/s throughput and standard edition features when it’s initialized.
Citrix ADC VPX instances lower than D16sv3 that are configured for ICA Proxy can experience a high degree of latency. Hence, Citrix recommends you to use the instance size of D16sv3 or D32sv3.
For Citrix Virtual Apps and Citrix Virtual Desktops deployment, a VPN virtual server on a VPX instance can be configured in the following modes:
- Basic mode, where the ICAOnly VPN virtual server parameter is set to ON. The Basic mode works fully on an unlicensed Citrix ADC VPX instance.
- SmartAccess mode, where the ICAOnly VPN virtual server parameter is set to OFF. The SmartAccess mode works for only 5 Citrix ADC AAA session users on an unlicensed Citrix ADC VPX instance.
Note
To configure the SmartControl feature, you must apply a Premium license to the Citrix ADC VPX instance.
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.