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
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
Download a Citrix ADC VPX license
Configure a Citrix ADC VPX instance to use SR-IOV network interface
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
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
-
Configuring authentication, authorization, and auditing policies
Configuring 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
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
-
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
中心思想dBridge 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!
Download a Citrix ADC VPX license
After the launch of Citrix ADC VPX-customer licensed instance from the AWS marketplace, a license is required. For more information on VPX licensing, seeLicensing overview.
You have to:
- Use the licensing portal within Citrix website to generate a valid license.
- Upload the license to the instance.
If this is apaidmarketplace instance, then you do not need to install a license. The correct feature set and performance activate automatically.
If you use a Citrix ADC VPX instance with a model number higher than VPX 5000, 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.
5 Gbps network bandwidth is observed in thec4.8xlarge
instance type.
How to migrate the AWS subscription to BYOL
This section describes the procedure to migrate from AWS subscription to Bring your own license (BYOL), and conversely.
Do the following steps to migrate an AWS subscription to BYOL:
Note
TheStep 2andStep 3are done on the Citrix ADC VPX instance, and all other steps are done on the AWS portal.
- Create a BYOL EC2 instance usingCitrix ADC VPX - Customer Licensedin the same availability zone as the old EC2 instance that has the same security group, IAM role, and subnet. The new EC2 instance must have only one ENI interface.
- To back up the data on the old EC2 instance using the Citrix ADC GUI, follow these steps.
- Navigate toSystem > Backup and Restore.
In theWelcomepage, clickBackup/Importto start the process.
- In theBackup/Importpage, fill in the following details:
- Name– Name of the backup file.
- Level– Select the backup level asFull.
- Comment– Provide a brief description of the backup.
ClickBackup. Once the backup is complete, you can select the file and download it to your local machine.
To restore the data on the new EC2 instance using the Citrix ADC GUI, follow these steps:
- Navigate toSystem > Backup and Restore.
- ClickBackup/Importto start the process.
Select theImportoption and upload the backup file.
- Select the file.
From theSelect Actiondrop-down menu, selectRestore.
On theRestorepage, verify the file details, and clickRestore.
- After the restore, reboot the EC2 instance.
米ove all interfaces (except the management interface to which the NSIP address is bound) from the old EC2 instance to the new EC2 instance. To move a network interface from one EC2 instance to another, follow these steps:
- In theAWS Portal, stop both the old and new EC2 instances.
- Navigate toNetwork Interfaces,并选择网络接口连接to the old EC2 instance.
Detach the EC2 instance by clickingActions > Detach.
Attach the network interface to the new EC2 instance by clickingActions > Attach. Enter the EC2 instance name to which the network interface must be attached.
- Do theStep 1toStep 4for all other interfaces that are attached. Make sure to follow the sequence and maintain the interface order. That is, first detach interface 2 and attach it, and then detach interface 3 and attach it, and so on.
You can’t detach the management interface from an old EC2 instance. So, move all the secondary IP addresses (if any) on the management interface (primary network interface) of the old EC2 instance to the new EC2 instance. To move an IP address from one interface to another, follow these steps:
- In theAWS Portal, make sure that both the old and new EC2 instances are inStopstate.
- Navigate toNetwork Interfaces,选取ect the management network interface attached to the old EC2 instance.
- ClickActions > Manage IP Address, and make note of all the secondary IP addresses assigned (if any).
- Navigate to the management network interface or primary interface of the new EC2 instance.
- ClickActions > Manage IP Addresses.
- UnderIPv4 Addresses, clickAssign new IP address.
- Enter the IP addresses, which are noted in theStep 3.
- SelectAllow secondary private IP addresses to be reassignedcheck box.
ClickSave.
- Start the new EC2 instance and verify the configuration. After all the configuration is moved, you can delete or keep the old EC2 instance as per your requirement.
- If any EIP address is attached to the NSIP address of the old EC2 instance, move the old instance NSIP address to the new instance NSIP address.
- If you want to revert to the old instance, then follow the same steps in the opposite way between the old and new instance.
- After you move from subscription instance to BYOL instance, a license is required. To install a license follow these steps:
- Use the licensing portal in the Citrix website to generate a valid license.
- Upload the license to the instance. For more information, seeVPX ADC - Install a new license.
Note
When you move BYOL instance to subscription instance (paid marketplace instance), you need not install the license. The correct feature set and performance is automatically activated.
Limitations
The management interface can’t be moved to the new EC2 instance. So Citrix recommends you manually configure the management interface. For more information, seeStep 5in the preceding procedure. A new EC2 instance is created with the exact replica of the old EC2 instance but only the NSIP address has a new IP address.
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.