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
配置一个CitrixADC VPX Instance on KVM to Use OVS DPDK-Based Host Interfaces
Deploy a Citrix ADC VPX instance on AWS
Scenario: standalone instance
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
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
-
-
-
-
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
配置CloudBridge连接器D之间的隧道atacenter 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 è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Scenario: standalone instance
May 24, 2018
This scenario illustrates how to deploy a Citrix ADC VPX standalone EC2 instance in AWS by using the AWS GUI. Create a standalone VPX instance with three NICs. The instance, which is configured as a load balancing virtual server, communicates with backend servers (the server farm). For this configuration, set up the required communication routes between the instance and the back-end servers, and between the instance and the external hosts on the public internet.
For more details about the procedure for deploying a VPX instance., seeDeploy a Citrix ADC VPX standalone instance on AWS.
Create three NICs. Each NIC can be configured with a pair of IP addresses (public and private). The NICs serve the following purposes.
NIC | Purpose | Associated with |
---|---|---|
eth0 | Serves management traffic (NSIP) | A public IP address and a private IP address |
eth1 | Serves client-side traffic (VIP) | A public IP address and a private IP address |
eth1 | Communicates with backend servers (SNIP) | A public IP address (Private IP address not mandatory) |
Step 1: Create a VPC.
1. Log on to the AWS web console and navigate toNetworking & Content Delivery>VPC. ClickStart VPC Wizard.
2. SelectVPC with a Single Public Subnetand clickSelect.
3. Set the IP CIDR Block to 10.0.0.0/16, for this scenario.
4. Give a name for the VPC.
5. Set the public subnet to 10.0.0.0/24. (This is the management network).
6. Select an availability zone.
7. Give a give a name for the subnet.
8. Click CreateVPC.
Step 2: Create additional subnets.
1. Open the Amazon VPC console athttps://console.aws.amazon.com/vpc/.
2. In the navigation pane, choose Subnets, Create Subnet after you enter the following details.
- Name tag: Provide a name for your subnet.
- VPC: Choose the VPC for which you’re creating the subnet.
- Availability Zone: Choose the availability zone in which you created the VPC in step 1.
- IPv4 CIDR block: Specify an IPv4 CIDR block for your subnet. For this scenario, choose 10.0.1.0/24.
3. Repeat the steps to create one more subnet for back-end servers.
Step 3: Create a route table.
1. Open the Amazon VPC console athttps://console.aws.amazon.com/vpc/.
2. In the navigation pane, chooseRoute Tables>Create Route Table.
3. In the Create Route Table window, add a name and select the VPC that you created in step 1.
4. ClickYes, Create.
The route table is assigned to all the subnets that you created for this VPC, so that routing of traffic from instance in one subnet can reach an instance in another subnet.
5. Click Subnet Associations, and then click Edit.
6. Click the management and client subnet and click Save. This creates a route table for internet traffic only.
7. Click Routes > Edit > Add another route.
8. In the Destination field add 0.0.0.0/0, and click the Target field to select igw-
9. Click Save.
10. Follow the steps to create a route table for server-side traffic.
Step 4: Create a Citrix ADC VPX instance.
1. Log on the AWS management console and clickEC2下Compute.
2. Click AWS Marketplace. In the Search AWS Marketplace bar, type Citrix ADC VPX and press Enter. The available Citrix ADC VPX editions are displayed.
3. ClickSelectto choose the desired Citrix ADC VPX edition. The EC2 instance wizard starts.
4. In theChoose Instance Typepage, selectm4. Xlarge(推荐),然后单击Next: Configure Instance Details.
5. In the Configure Instance Details page, select the following, and then click Next: Add Storage.
- Number of instances: 1
- Network: the VPC that created in Step 1
- Subnet: the management subnet
- Auto-assign Public IP: Enable
6. In the Add Storage page, select the default option, and click Next: Add Tags.
7. In the Add Tags page, add a name for the instance, and click Next: Configure Security Group.
8. In the Configure Security Group page, select the default option (which is generated by AWS Marketplace and is based on recommended settings by Citrix Systems) and then click Review and Launch > Launch.
9. You are prompted to select an existing key pair or create and new key pair. From the Select a key pair drop-down list, select the key pair that you created as a prerequisite (See the Prerequisite section.)
10. Check the box to acknowledge the key pair and click Launch Instances.
Launch Instance Wizard displays the Launch Status, and the instance appears in the list of instances when it is fully launched.
The check instance, go the AWS console click EC2 > Running Instances. Select the instance and add a name. Make sure the Instance State is running and Status Checks is complete.
Step 5: Create and attach more network interfaces.
When you created the VPC, only one network interface associated with it. Now add two more network interfaces to the VPC, for the VIP and SNIP.
1. Open the Amazon EC2 console athttps://console.aws.amazon.com/ec2/.
2. In the navigation pane, choose Network Interfaces.
3. Choose Create Network Interface.
4. For Description, enter a descriptive name.
5. For Subnet, select the subnet that you created previously for the VIP.
6. For Private IP, leave the default option.
7. For Security groups, select the group.
8. Click Yes, Create.
9. After the network interface is created, add a name to the interface.
10. Repeat the steps to create a network interface for server-side traffic.
Attach the network interfaces:
1. In the navigation pane, choose Network Interfaces.
2. Select the network interface and choose Attach.
3. In the Attach Network Interface dialog box, select the instance and choose Attach.
Step 6: Attach elastic IP to the NSIP.
1. From the AWS management console, go toNETWORK & SECURITY > Elastic IPs.
2. Check for available free EIP to attach. If none, clickAllocate new address.
3. Select the newly allocated IP address and chooseActions > Associate address.
4. Click theNetwork interfaceradio button.
5. From the Network interface drop-down list, select the management NIC.
6. From thePrivate IPdrop-down menu, select the AWS-generated IP address.
7. Select theReassociationcheck box.
8. ClickAssociate.
Access the VPX instance:
After you’ve configured a standalone Citrix ADC VPX instance with three NICs,log on to the VPX instance to complete the Citrix ADC-side configuration. Use of the following options:
• GUI: Type the public IP of the management NIC in the browser. Log on by using nsroot as the user name and the instance ID (i-0c1ffe1d987817522) as the password.
• SSH: Open an ssh client and type:
ssh -i
To find the public DNS, click the instance, and click Connect.
Related information:
- To configure the Citrix ADC-owned IP addresses (NSIP, VIP, and SNIP), seeConfiguring Citrix ADC-Owned IP Addresses.
- You’ve configured a BYOL version of the Citrix ADC VPX appliance, for more information see the VPX Licensing Guide athttp://support.citrix.com/article/CTX122426
Share
Share
In this article
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.