Getting Started with Citrix NetScaler
Deploy a Citrix NetScaler VPX instance
Install a Citrix NetScaler VPX instance on Microsoft Hyper-V servers
Install a NetScaler VPX instance on Linux-KVM platform
Prerequisites for Installing NetScaler VPX Virtual Appliances on Linux-KVM Platform
Provisioning the NetScaler Virtual Appliance by using OpenStack
Provisioning the NetScaler Virtual Appliance by using the Virtual Machine Manager
Configuring NetScaler Virtual Appliances to Use SR-IOV Network Interface
Configuring NetScaler Virtual Appliances to use PCI Passthrough Network Interface
Provisioning the NetScaler Virtual Appliance by using the virsh Program
Deploying NetScaler VPX Instances on AWS
Upgrade and downgrade a NetScaler appliance
-
-
-
-
-
Overriding Static Proximity Behavior by Configuring Preferred Locations
Example of a Complete Parent-Child Configuration Using the Metrics Exchange Protocol
Configuring Global Server Load Balancing for DNS Queries with NAPTR records
Using the EDNS0 Client Subnet Option for Global Server Load Balancing
-
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
Use source IP address of the client when connecting to the server
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 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
-
-
-
-
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 NetScaler 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!
Deploy a NetScaler VPX instance on AWS
You can launch a Citrix NetScaler VPX instance on Amazon Web Services (AWS). The NetScaler VPX appliance is available as an Amazon Machine Image (AMI) in AWS marketplace. A NetScaler VPX instance on AWS enables customer like you to leverage AWS Cloud computing capabilities and use NetScaler load balancing and traffic management features for their business needs. The VPX instance supports all the traffic management features of a physical NetScaler appliance, and they can be deployed as standalone instances or in HA pairs.
This section includes the following topics:
- AWS terminology
- How a NetScaler VPX instance on AWS works
- Supported instance type, ENI, and IP addresses
AWS terminology
Here is a brief description of the terms used in this document. For more information, seeAWS Glossary.
Term | Defintion |
---|---|
Amazon Machine Image (AMI) | A machine image, which provides the information required to launch an instance, which is a virtual server in the cloud. |
Elastic Block Store | Provides persistent block storage volumes for use with Amazon EC2 instances in the AWS Cloud. |
Simple Storage Service (S3) | Storage for the Internet. It is designed to make web-scale computing easier for developers. |
Elastic Compute Cloud (EC2) | A web service that provides secure, resizable compute capacity in the cloud. It is designed to make web-scale cloud computing easier for developers. |
Elastic Load Balancing (ELB) | Distributes incoming application traffic across multiple EC2 instances, in multiple Availability Zones. This increases the fault tolerance of your applications. |
Elastic network interface (ENI) | A virtual network interface that you can attach to an instance in a VPC. |
Elastic IP (EIP) address | A static, public IPv4 address that you have allocated in Amazon EC2 or Amazon VPC and then attached to an instance. Elastic IP addresses are associated with your account, not a specific instance. They are elastic because you can easily allocate, attach, detach, and free them as your needs change. |
Instance type | Amazon EC2实例t的提供一个广泛的选择ypes optimized to fit different use cases. Instance types comprise varying combinations of CPU, memory, storage, and networking capacity and give you the flexibility to choose the appropriate mix of resources for your applications. |
Identity and Access Management (IAM) | An AWS identity with permission policies that determine what the identity can and cannot do in AWS. You can use an IAM role to enable applications running on an EC2 instance to securely access your AWS resources.IAM role is required for deploying VPX instances in a high-availability setup. |
Internet Gateway | Connects a network to the Internet. You can route traffic for IP addresses outside your VPC to the Internet gateway. |
Key pair | A set of security credentials that you use to prove your identity electronically. A key pair consists of a private key and a public key. |
Route tables | A set of routing rules that controls the traffic leaving any subnet that is associated with the route table. You can associate multiple subnets with a single route table, but a subnet can be associated with only one route table at a time. |
Security groups | A named set of allowed inbound network connections for an instance. |
Subnets | A segment of the IP address range of a VPC that EC2 instances can be attached to. You can create subnets to group instances according to security and operational needs. |
Virtual Private Cloud (VPC) | A web service for provisioning a logically isolated section of the AWS cloud where you can launch AWS resources in a virtual network that you define. |
Auto Scaling | A web service to launch or terminate Amazon EC2 instances automatically based on user-defined policies, schedules, and health checks. |
CloudFormation | A service for writing or changing templates that create and delete related AWS resources together as a unit. |
How a NetScaler VPX instance on AWS works
The NetScaler VPX instance is available as an AMI in AWS marketplace, and it can be launched as an EC2 instance within an AWS VPC. The NetScaler VPX AMI instance requires a minimum of 2 virtual CPUs and 2 GB of memory. An EC2 instance launched within an AWS VPC can also provide the multiple interfaces, multiple IP addresses per interface, and public and private IP addresses needed for VPX configuration. Each VPX instance requires at least three IP subnets:
- A management subnet
- A client-facing subnet (VIP)
- A back-end facing subnet (SNIP,MIP, etc.)
Citrix recommends three network interfaces for a standard VPX instance on AWS installation.
AWS currently makes multi-IP functionality available only to instances running within an AWS VPC. A VPX instance in a VPC can be used to load balance servers running in EC2 instances. An Amazon VPC allows you to create and control a virtual networking environment, including your own IP address range, subnets, route tables, and network gateways.
Note: By default, you can create up to 5 VPC instances per AWS region for each AWS account. You can request higher VPC limits by submitting Amazon’s request formhttp://aws.amazon.com/contact-us/vpc-request.
Figure 1.A Sample NetScaler VPX Instance Deployment on AWS Architecture
Figure 1 shows a simple topology of an AWS VPC with a NetScaler VPX deployment. The AWS VPC has:
- A single Internet gateway to route traffic in and out of the VPC.
- 互联网网关之间的网络连接and the Internet.
- Three subnets, one each for management, client, and server.
- 互联网网关之间的网络连接and the two subnets (management and client).
- A standalone NetScaler VPX instance deployed within the VPC. The VPX instance has three ENIs, one attached to each subnet.
Supported instance type, ENI, and IP addresses
For more information about Amazon EC2 instances and IP addresses supported per NIC per instance type:
For higher bandwidth, Citrix recommends the following instance types:
Instance type | Bandwidth | Enhanced networking (SR-IOV) |
---|---|---|
M4.10x large | 3 Gbps and 5 Gbps | Yes |
C4.8x large | 3 Gbps and 5 Gbps | Yes |
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.