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
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 10: Load balancing of intrusion detection system servers
Use case 11: Isolating network traffic using listen policies
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)
此内容已动态机器翻译。放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다.책임 부인
This content has been machine translated dynamically.
This content has been machine translated dynamically.
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.
这篇文章已经过机器翻译.放弃
Translation failed!
Deploy a VPX high-availability pair on Google Cloud Platform
You can configure two Citrix ADC VPX instances on Google Cloud Platform 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, if the primary node is unable to accept connections, the secondary node takes over. Also, the client IP of the primary node must be bound to an external static IP address, for traffic to resume after a failover.
For more information on HA, seeHigh Availability.
The nodes must be in the same region; however, they can be either in same zone or different zones. For more information, seeRegions and Zones.
Each VPX instance requires at least three IP subnets (Google VPC networks):
- A management subnet
- A client-facing subnet (VIP)
- A back-end facing subnet (SNIP, MIP, and so on)
Citrix recommends three network interfaces for a standard VPX instance.
Before you start
- Read the Limitation, Hardware requirements, Points to note mentioned inDeploy a Citrix ADC VPX instance on Google Cloud Platform. This information applies to HA deployments also.
- Ensure your GCP service account has the following IAM permissions:
REQUIRED_INSTANCE_IAM_PERMS = [ "compute.instances.addAccessConfig", "compute.instances.deleteAccessConfig", "compute.instances.get", "compute.instances.list", "compute.networks.useExternalIp", "compute.subnetworks.useExternalIp", "compute.zones.list", ]
How to deploy a VPX HA pair on Google Cloud Platform
Here’s a summary of the HA deployment steps:
- Create three VPC networks in the same region. For example, Asia-east.
- Create two VPX instances (primary and secondary nodes) on the same region. They can be in the same zone or different zones. For example Asia east-1a and Asia east-Ib.
- 通过使用t HA配置设置在两个实例he Citrix ADC GUI or ADC CLI commands.
Note
Stayprimary
andStaysecondary
settings are not supported for high availability deployment on the Google Cloud Platform.
Step 1. Create three VPC networks
Create three VPC networks for associating with management NIC, client NIC, and server NIC. To create a VPC network, log on theGoogle console > Networking > VPC network > Create VPC Network. Complete the required fields, and clickCreate. For more information, see the section “Create VPC Networks” inDeploy a Citrix ADC VPX instance on Google Cloud Platform.
Step 2. Create two VPX instances
Create two VPX instances by following the steps given inScenario: deploy a multi-NIC, multi-IP standalone VPX instance.
Important Assign a static external IP address to the client IP address (VIP) of the primary node. To create a static external, underNetwork interface > External IP, click Create IP address.
After the failover, when the old primary becomes the new secondary, the static external IP address moves from the old primary and is attached to the new primary. For more information, see the Google cloud documentReserving a Static External IP Address.
After you’ve configured the VPX instances, you can configure the required IP addresses. For more information, seeConfiguring Citrix ADC-owned IP addresses.
Step 3. Configure high availability
After you’ve created the instances on Google Cloud Platform, you can configure HA by using the Citrix ADC GUI for CLI.
Configure HA by using the GUI
Step 1. Set up high availability in INC mode on both the instances.
- 登录到主节点with user name
nsroot
and instance ID as password. - From the GUI, go toConfiguration > System > High Availability. ClickAdd.
- At theRemote Node IP address field, add the private IP address of the management NIC of the secondary node.
- Select Turn on INC (Independent Network Configuration) mode on self-node.
- UnderRemote System Login Credential, add the user name and password for the secondary node and clickCreate.
- Repeat the steps in the secondary node.
Step 2. Add IP set and bind IP set to the VIP set on both the instances.
- From the GUI, navigate toSystem > Network > IPs > Add.
- Add the required values for IP Address, Netmask, IP Type (virtual IP) and click Create.
- Navigate toSystem > Network > IP Sets > Add. Add an IP set name and click Insert.
- From the IPV4s page, select the virtual IP and click Insert. Click Create to create the IP set.
Note You can bind the IP set to the primary VIP or to the secondary VIP. However, if you bind the IP set to the primary VIP, use the secondary VIP to add to the virtual server, and conversely.
Step 3. Add a virtual server in the primary instance.
- From the GUI, go toConfiguration > Traffic Management > Load Balancing > Virtual Servers > Add.
保存配置。现在,二级节点has the same log-on credentials as the primary node. After a forced failover, the secondary becomes the new primary. The external static IP of the old primary VIP moves to the new secondary VIP.
Configure high availability using CLI
Step 1. Set up high availability in INC mode in both the instances by using the Citrix ADC CLI.
On the primary node, type the following command.
add ha node 1 -inc ENABLED in primary
On the secondary node, type the following command.
add ha node 1 -inc ENABLED in secondary
sec_ip
Refers to the private IP address of the management NIC of the secondary node.
prim_ip
Refers to the private IP address of the management NIC of the primary node.
Step 2. Add IP set in both the instances.
Type the following command on both the instances:
add ipset
Step 3. Bind IP set to the VIP set on both the instances.
Type the following commands on both the instances:
add ns ip -type VIP
Note Skip this command if the VIP is already configured.
bind ipset
Note You can bind the IP set to the primary VIP or to the secondary VIP. However, if you bind the IP set to the primary VIP, use the secondary VIP to add to the virtual server, and conversely.
Step 4. Add a virtual server on the primary instance.
Type the following command:
add vserver -ipset
Note:
To save your configuration, type the command
save config
. Otherwise, the configurations are lost after you restart the instances.
GDM templates to deploy a VPX high-availability pair on GCP
You can use a Citrix ADC Google Deployment Manager (GDM) template to deploy a VPX high-availability pair on GCP. For details, seeCitrix ADC GDM Templates.
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.