-
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
Deploy a high availability pair on AWS
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
Authentication, authorization, and auditing application traffic
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
-
-
-
-
-
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.(非responsabilite条款)
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.(非responsabilite条款)
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 high availability pair on AWS
You can configure two Citrix ADC VPX instances on AWS as a high availability (HA) active-passive pair. When you configure one instance as the primary node and the other as the secondary node, the primary node accepts connections and manages servers. The secondary node monitors the primary. If for any reason, the primary node is unable to accept connections, the secondary node takes over.
For more information on HA, seeHigh availability.
Before you start your deployment, read the following topics:
- Prerequisitesfor the required IAM role privileges.
- Limitations and usage guidelines
The following figure shows an example of the HA deployment architecture for Citrix ADC VPX instances on AWS.
Figure 1. A Citrix ADC VPX HA Pair on AWS
You can deploy two VPX instances on AWS as an HA pair by using one of the following options:
- Create the instances with IAM Role manually by using the AWS Management Console and then configure HA on them.
- Or automate the high availability deployment by using the Citrix CloudFormation template.
The CloudFormation template significantly decreases the number of steps involved for creating an HA pair, and it automatically creates an IAM Role. This section shows how to deploy a Citrix ADC VPX HA (active-passive) pair by using the Citrix CloudFormation template.
Keep the following points in mind while deploying two Citrix ADC VPX instances as an HA pair.
Points to note
- 在AWS要求主节点HA least two ENIs (one for management and the other for data traffic), and the secondary node to have one management ENI. However, for security purposes, create three ENIs on the primary node, because this setup allows you to segregate private and public network (recommended).
- The secondary node always has one ENI interface (for management) and the primary node can have up to four ENIs.
- The NSIP addresses for each VPX instance in a high availability pair must be configured on the default ENI of the instance.
- Because Amazon does not allow any broadcast/multicast packets in AWS, HA is implemented by migrating data-plane ENIs from the primary to the secondary (new primary) VPX instance when the primary VPX instance fails.
- Because the default (management) ENI cannot be moved to another VPX instance, do not use the default ENI for client and server traffic (data-plane traffic).
- The message AWSCONFIG IOCTL NSAPI_HOTPLUG_INTF success output 0 in the /var/log/ns.log indicates that the two data ENIs have successfully attached to the secondary instance (the new primary).
- Failover might take up to 20 seconds due to the AWS detach/attach ENI mechanism.
- Upon failover, the failed instance always restarts.
- 心跳包ets are received only on the management interface.
- The configuration file of the primary and secondary VPX instances is synchronized, including the nsroot password. The nsroot password of the secondary node is set to that of the primary node after the HA configuration synchronization.
- To have access to the AWS API servers, either the VPX instance must have a public IP address assigned or routing must be set up correctly at VPC subnet level pointing to internet gateway of the VPC
- Nameservers/DNS servers are configured at VPC level using DHCP options.
- The Citrix CloudFormation template does not create an HA setup between different availability zones.
- The Citrix CloudFormation template does not create an INC mode.
- The AWS debug messages are available in the log file, /var/log/ns.log, on the VPX instance.
Deploy a high availability pair by using the Citrix CloudFormation template
Before start the CloudFormation template, ensure that you complete the following requirements:
- A VPC
- Three subnets within the VPC
- A security group with UDP 3003, TCP 3009–3010, HTTP, SSH ports open
- A key pair
- Create an internet gateway
- Edit route tables for client and management networks to point to the internet gateway
Note
The Citrix CloudFormation template automatically creates an IAM Role. Existing IAM Roles do not appear in the template.
To launch the Citrix CloudFormation template:
- Log on to theAWS marketplaceby using your AWS credentials.
- In the search field, typeNetScaler ADC VPXto search for the Citrix ADC AMI, and clickGo.
- On the search result page, click the desired Citrix ADC VPX offering.
- Click thePricingtab, to go toPricing Information.
- Select the region andFulfillment OptionasNetscaler AWS-VPX Cluster.
- ClickContinue to Subscribe.
- Check the details in theSubscribepage and clickContinue to Subscribe.
SelectFulfillment OptionasCloudFormation Template.
SelectSoftware Versionand clickContinue to Launch.
UnderChoose Action, selectLaunch CloudFormation, and clickLaunch.
TheSelect Templatepage appears. ClickNext.
- TheSpecify Detailsappears. Enter the following details.
a. Type aStack name.The name must be within 25 characters.
b. UnderHigh Availability Configuration
SelectYesfrom the menu forCreate HA pair?.
c. UnderVirtual Private Network Configuration
Select the VPC that you’ve already created forVPC ID.
TypeRemote SSH CIDR IP.
TypeRemote HTTP CIDR IP.
TypeRemote HTTPS CIDR IP.
Select the key pair that you’ve already created from the drop-down menu forKey Pair.
d. UnderNetwork Interface Configuration
SelectManagement Subnetwork,Client Subnetwork, andServer Subnetwork. Ensure that you select the correct subnetworks you created within the VPC that you selected under VPC ID in step c.
AddPrimary Management IP,Secondary Management IP,Client IP, andServer IP.The IP addresses must belong to the same subnets of the respective subnetworks. Alternatively, you can let the template assign the IP addresses automatically.
e. UnderOther Parameters
Selectm4.largeforInstant Type.
SelectdefaultforTenancy Type.
f. ClickNext.
13. TheOptionspage appears. (This is an optional page.). ClickNext.
- TheReviewpage appears. Take a moment to review the settings and make necessary changes if necessary.
- Select theI acknowledge that AWS CloudFormation might create IAM resources.check box, and then clickCreate.
16. TheCREATE-IN-PROGRESSstatus appears. Wait until the status isCREATE-COMPLETE. If the status does not change to “COMPLETE,” check theEventstab for the reason of failure and recreate the instance with proper configurations.
- After an IAM resource is created, go to EC2ManagementConsole > Instances. You will find two VPX instances created with IAM role. The primary node is created with three private IP addresses and three network interfaces.
The secondary node is created with one private IP address and one network interface.
Note
The secondary node is created with one interface by default in AWS. During failover, the interface from the primary node gets attached to the secondary node (the new primary node) and gets detached from the original primary node (the new secondary node).
18./ Log on to the primary node with user name nsroot and the instance ID as the password. From the GUI, go toSystem > High Availability. The Citrix ADC VPX HA pair appears.
Next, configure the HA pairing on both the instances. Configure the instance with three ENIs before configuring HA on the instance with one ENI). Use the add HA node command, from within the VPX CLI, or from the GUI.
add HA node
add HA node
After you run the “add HA node” commands, the two nodes form an HA pair, and configuration information is synchronized between the two VPX instances.
Configuring SR-IOV on a high availability setup
Support for SR-IOV interfaces in a high availability setup is available from Citrix ADC release 12.0 57.19 onwards. For more information about how to configure SR-IOV, seeConfiguring Citrix ADC VPX instances to Use SR-IOV Network Interface.
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.
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.