ADC

Scenario: standalone instance

August 20, 2024

Contributed by:

C C S

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., see Deploy a Citrix ADC VPX standalone instance on AWS.

localized image

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 to Networking & Content Delivery > VPC. Click Start VPC Wizard.

2. Select VPC with a Single Public Subnet and click Select.

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 Create VPC.

localized image

Step 2: Create additional subnets.

1. Open the Amazon VPC console at https://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.

localized image

3. Repeat the steps to create one more subnet for back-end servers.

localized image

Step 3: Create a route table.

1. Open the Amazon VPC console at https://console.aws.amazon.com/vpc/.

2. In the navigation pane, choose Route 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. Click Yes, Create.

localized image

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.

localized image

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-<xxxx> the Internet Gateway that the VPC Wizard created automatically.

9. Click Save.

localized image

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 click EC2 under 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. Click Select to choose the desired Citrix ADC VPX edition. The EC2 instance wizard starts.

4. In the Choose Instance Type page, select m4. Xlarge (recommended) and click 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

localized image

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.

localized image

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 at https://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.

localized image

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.

localized image

Step 6: Attach elastic IP to the NSIP.

1. From the AWS management console, go to NETWORK & SECURITY > Elastic IPs.

2. Check for available free EIP to attach. If none, click Allocate new address.

3. Select the newly allocated IP address and choose Actions > Associate address.

4. Click the Network interface radio button.

5. From the Network interface drop-down list, select the management NIC.

6. From the Private IP drop-down menu, select the AWS-generated IP address.

7. Select the Reassociation check box.

8. Click Associate.

localized image

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 <location of your private key> nsroot@<public DNS of the instance>

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), see Configuring 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 at http://support.citrix.com/article/CTX122426

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Scenario: standalone instance

August 20, 2024

Contributed by:

C C S

August 20, 2024

Contributed by:

C C S

Scenario: standalone instance

In this article