-
Getting Started with NetScaler
-
Deploy a NetScaler VPX instance
-
Optimize NetScaler VPX performance on VMware ESX, Linux KVM, and Citrix Hypervisors
-
Apply NetScaler VPX configurations at the first boot of the NetScaler appliance in cloud
-
Install a 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
-
Provisioning the NetScaler virtual appliance with SR-IOV on OpenStack
-
Configuring a NetScaler VPX instance on KVM to use OVS DPDK-Based host interfaces
-
-
Deploy a NetScaler 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
-
Protect AWS API Gateway using the NetScaler Web Application Firewall
-
Configure a NetScaler VPX instance to use SR-IOV network interface
-
Configure a NetScaler VPX instance to use Enhanced Networking with AWS ENA
-
Deploy a NetScaler VPX instance on Microsoft Azure
-
Network architecture for NetScaler VPX instances on Microsoft Azure
-
Configure multiple IP addresses for a NetScaler 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
-
Deploy a NetScaler high-availability pair on Azure with ALB in the floating IP-disabled mode
-
Configure a NetScaler VPX instance to use Azure accelerated networking
-
Configure HA-INC nodes by using the NetScaler high availability template with Azure ILB
-
Configure a high-availability setup with Azure external and internal load balancers simultaneously
-
Configure a NetScaler VPX standalone instance on Azure VMware solution
-
Configure a NetScaler VPX high availability setup on Azure VMware solution
-
Deploy NetScaler GSLB and domain-based services back-end autoscale with cloud load balancer
-
Configure address pools (IIP) for a NetScaler Gateway appliance
-
Deploy a NetScaler VPX instance on Google Cloud Platform
-
Deploy a VPX high-availability pair on Google Cloud Platform
-
Deploy a VPX high-availability pair with external static IP address on Google Cloud Platform
-
Deploy a single NIC VPX high-availability pair with private IP address on Google Cloud Platform
-
Deploy a VPX high-availability pair with private IP addresses on Google Cloud Platform
-
Install a NetScaler VPX instance on Google Cloud VMware Engine
-
-
Upgrade and downgrade a NetScaler 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
-
On-premises NetScaler Gateway as an identity provider to Citrix Cloud
-
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 12: Configure Citrix Virtual Desktops for load balancing
-
Use case 13: Configure Citrix Virtual Apps and Desktops for load balancing
-
Use case 14: ShareFile wizard for load balancing Citrix ShareFile
-
Use case 15: Configure layer 4 load balancing on the NetScaler 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 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 the Google Cloud Platform
You can deploy a NetScaler VPX instance on the Google Cloud Platform (GCP). A VPX instance in GCP enables you to take advantage of GCP cloud computing capabilities and use Citrix load balancing and traffic management features for your business needs. You can deploy VPX instances in GCP as standalone instances. Both single NIC and multi NIC configurations are supported.
Supported features
All Premium, Advanced, and Standard features are supported on the GCP based on the license/version type used.
Limitation
- IPv6 isn’t supported.
Hardware requirements
VPX instance in GCP must have minimum of 2 vCPUs and 4 GB RAM.
Prerequisites
-
Install the “gcloud” utility on your device. You can find the utility at this link: https://cloud.google.com/sdk/install
-
Download the NSVPX-GCP image from the NetScaler site.
-
Upload the file(for example, NSVPX-GCP-12.1-50.9_nc_64.tar.gz) to a storage bucket on Google by following the steps given at https://cloud.google.com/storage/docs/uploading-objects.
-
Run the following command on the gcloud utility to create an image.
gcloud compute images create <IMAGE_NAME> --source-uri=gs://<STORAGE_BUCKET_NAME>/<FILE_NAME>.tar.gz --guest-os-features=MULTI_IP_SUBNET
<!--NeedCopy-->
It might take a moment for the image to be created. After the image is created, it appears under Compute > Compute Engine in the GCP console.
Points to note
Consider the following GCP-specific points before you begin your deployment.
- After creating the instance, you can’t add or remove any network interfaces.
- For a multi-NIC deployment, create separate VPC networks for each NIC. One NIC can be associated with only one network.
- For a single-NIC instance, the GCP console creates a network by default.
- Minimum 4 vCPUs are required for an instance with more than two network interfaces.
- If IP forwarding is required, you must enable IP forwarding while creating the instance and configuring the NIC.
Scenario: Deploy a multi-NIC, multi-IP standalone VPX instance
This scenario illustrates how to deploy a NetScaler VPX standalone instance in GCP. In this scenario, you create a standalone VPX instance with many NICs. The instance communicates with back-end servers (the server farm).
Create three NICs to serve the following purposes.
NIC | Purpose | Associated with VPC network |
---|---|---|
NIC 0 | Serves management traffic (NetScaler IP) | Management network |
NIC 1 | Serves client-side traffic (VIP) | Client network |
NIC 2 | Communicates with back-end servers (SNIP) | Back-end server network |
Set up the required communication routes between the following:
- VPX instance and the back-end servers.
- VPX instance and the external hosts on the public internet.
Summary of deployment steps
- Create three VPC networks for three different NICs.
- Create firewall rules for ports 22, 80, and 443
- Create an instance with three NICs
Note:
Create an instance in the same region where you’ve created the VPC networks.
Step 1. Create VPC networks.
Create three VPC networks that is associated with management NIC, client NIC, and server NIC. To create a VPC network, log on to Google console > Networking > VPC network > Create VPC Network. Complete the required fields, as shown in the screen capture, and click Create.
Similarly, create VPC networks for client and server-side NICs.
Note:
All three VPC networks must be in the same region, which is asia-east1 in this scenario.
Step 2. Create firewall rules for ports 22, 80, and 443.
Create rules for SSH (port 22), HTTP (port 80), and HTTPS (port 443) for each VPC networks. For more information about firewall rules, see Firewall Rules Overview.
Step 3. Create the VPX instance.
- Log on to the GCP console.
- Under Compute, hover over Compute Engine, and select Images.
-
Select the image, and click Create Instance.
- Select an instance with 4 vCPUs, to support multiple NICs.
-
Click the networking option from Management, security, disks, networking, sole tenancy to add the additional NICs.
Note:
Container image isn’t supported on VPX instances on GCP.
- Under Networking interfaces, click the edit icon to edit the default NIC. This NIC is the management NIC.
-
In the Network interfaces window, under Network, select the VPC network you created for the management NIC.
-
For the management NIC, create a static external IP address. Under the External IP list, click Create IP address.
-
In the Reserve a new static IP address window, add a name and description and click Reserve.
- Click Add network interface to create NICs for a client and server-side traffic.
After you’ve created all the NICs, click Create to create the VPX instance.
The instance appears under VM instances.
Use the GCP SSH or the serial console to configure and manage the VPX instance.
Scenario: Deploy a single-NIC, standalone VPX instance
This scenario illustrates how to deploy a NetScaler VPX standalone instance with a single NIC in GCP. The alias IP addresses are used to achieve this deployment.
Create a single NIC (NIC0) to serve the following purposes:
- Handle management traffic (NetScaler IP) in the management network.
- Handle client-side traffic (VIP) in the client network.
- Communicate with back-end servers (SNIP) in the back-end server network.
Set up the required communication routes between the following:
- Instance and the back-end servers.
- Instance and the external hosts on the public internet.
Summary of deployment steps
- Create a VPC network for NIC0.
- Create firewall rules for ports 22, 80, and 443.
- Create an instance with a single NIC.
- Add Alias IP addresses to VPX.
- Add VIP and SNIP on VPX.
- Add a load balancing virtual server.
- Add a service or service group on the instance.
- Bind the service or service group to the load balancing virtual server on the instance.
Note:
Create an instance in the same region where you’ve created the VPC networks.
Step 1. Create one VPC network.
Create one VPC network to associate with NIC0.
To create a VPC network, do these steps:
- Log on to GCP console > Networking > VPC network > Create VPC Network
- Complete the required fields, and click Create.
Step 2. Create firewall rules for ports 22, 80, and 443.
Create rules for SSH (port 22), HTTP (port 80), and HTTPS (port 443) for the VPC network. For more information about firewall rules, see Firewall Rules Overview.
Step 3. Create an instance with single NIC.
To create an instance with single NIC, do these steps:
- Log on to the GCP console.
- Under Compute, hover over Compute Engine, and select Images.
-
Select the image, and click Create Instance.
-
Select an instance type with two vCPUs (minimum requirement for ADC).
- Click the Networking tab from the Management, security, disks, networking window.
- Under Network interfaces, click the Edit icon to edit the default NIC.
- In the Network interfaces window, under Network, select the VPC network that you created.
- You can create a static external IP address. Under the External IP addresses, click Create IP address.
- In the Reserve a static address window, add a name and description and click Reserve.
- Click Create to create the VPX instance. The new instance appears under VM instances.
Step 4. Add alias IP addresses to the VPX instance.
Assign two alias IP addresses to the VPX instance to use as VIP and SNIP addresses.
Note:
Do not use the primary internal IP address of the VPX instance to configure the VIP or SNIP.
To create an alias IP address, perform these steps:
- Navigate to the VM instance and click Edit.
- In the Network interface window, edit the NIC0 interface.
-
In the Alias IP range field, enter the alias IP addresses.
- Click Done, and then Save.
-
Verify the alias IP addresses in the VM instance details page.
Step 5. Add VIP and SNIP on the VPX instance.
On the VPX instance, add client alias IP address and server alias IP address.
-
On the NetScaler GUI, navigate to System > Network > IPs > IPv4s, and click Add.
-
To create a client alias IP (VIP) address:
- Enter the client-alias IP address and netmask configured for the VPC subnet in the VM instance.
- In the IP Type field, select Virtual IP from the drop-down menu.
- Click Create.
-
To create a server alias IP (SNIP) address:
- Enter the server-alias IP address and netmask configured for the VPC subnet in the VM instance.
- In the IP Type field, select Subnet IP from the drop-down menu.
- Click Create.
Step 6. Add load balancing virtual server.
- On the NetScaler GUI, navigate to Configuration > Traffic Management > Load Balancing > Virtual Servers, and click Add.
- Add the required values for Name, Protocol, IP Address Type (IP Address), IP Address (client alias IP), and Port.
- Click OK to create the load balancing virtual server.
Step 7. Add a service or service group on the VPX instance.
- From the NetScaler GUI, navigate to Configuration > Traffic Management > Load Balancing > Services, and click Add.
- Add the required values for Service Name, IP Address, Protocol, and Port, and click OK.
Step 8. Bind the service/service group to the Load Balancing Virtual Server on the instance.
- From the GUI, navigate to Configuration > Traffic Management > Load Balancing > Virtual Servers.
- Select the load balancing virtual server configured in Step 6, and click Edit.
- In the Service and Service Groups window, click No Load Balancing Virtual Server Service Binding.
- Select the service configured in Step 7, and click Bind.
Points to note after you’ve deployed the VPX instance on GCP
-
Log on to the VPX with user name
nsroot
and instance ID as password. At the prompt, change the password and save the configuration. -
For collecting a technical support bundle, run the command
shell /netscaler/showtech_cloud.pl
instead of the customaryshow techsupport
. -
After deleting a NetScaler VM from GCP console, delete the associated NetScaler internal target instance also. To do so, go to gcloud CLI and type the following command:
gcloud compute -q target-instances delete <instance-name>-adcinternal --zone <zone> <!--NeedCopy-->
Note:
<instance-name>-adcinternal
is the name of the target instance that must be deleted.
NetScaler VPX licensing
A NetScaler VPX instance on GCP requires a license. The following licensing options are available for NetScaler VPX instances running on GCP.
-
Subscription-based licensing: NetScaler VPX appliances are available as paid instances on the GCP marketplace. Subscription-based licensing is a pay-as-you-go option. Users are charged hourly. The following VPX models and license editions are available on the GCP marketplace.
VPX model License editions VPX10, VPX200, VPX1000, VPX3000, VPX5000 Standard, Advanced, Premium -
Bring your own license (BYOL): If you bring your own license (BYOL), see the VPX Licensing Guide at http://support.citrix.com/article/CTX122426. You have to:
- Use the licensing portal within the Citrix website to generate a valid license.
- Upload the license to the instance.
- NetScaler VPX Check-In/Check-Out licensing: For more information, see NetScaler VPX Check-In/Check-Out Licensing.
VPX Express for on-premises and cloud deployments does not require a license file. For more information on NetScaler VPX Express see the “NetScaler VPX Express license” section in NetScaler licensing overview.
GDM templates to deploy a NetScaler VPX instance
You can use a NetScaler VPX Google Deployment Manager (GDM) template to deploy a VPX instance on GCP. For details, see NetScaler GDM Templates.
NetScaler marketplace images
You can use the images in GDM templates to bring up the NetScaler appliance.
The following table lists the images that are available on GCP marketplace.
Release | Image name | Image location |
---|---|---|
13.0 | citrix-adc-vpx-10-enterprise-13-0-83-29 | projects/citrix-master-project/global/images/citrix-adc-vpx-10-enterprise-13-0-83-29 |
13.0 | citrix-adc-vpx-10-platinum-13-0-83-29 | projects/citrix-master-project/global/images/citrix-adc-vpx-10-platinum-13-0-83-29 |
13.0 | citrix-adc-vpx-10-standard-13-0-83-29 | projects/citrix-master-project/global/images/citrix-adc-vpx-10-standard-13-0-83-29 |
13.0 | citrix-adc-vpx-200-enterprise-13-0-83-29 | projects/citrix-master-project/global/images/citrix-adc-vpx-200-enterprise-13-0-83-29 |
13.0 | citrix-adc-vpx-200-platinum-13-0-83-29 | projects/citrix-master-project/global/images/citrix-adc-vpx-200-platinum-13-0-83-29 |
13.0 | citrix-adc-vpx-200-standard-13-0-83-29 | projects/citrix-master-project/global/images/citrix-adc-vpx-200-standard-13-0-83-29 |
13.0 | citrix-adc-vpx-1000-advanced-13-0-83-29 | projects/citrix-master-project/global/images/citrix-adc-vpx-1000-advanced-13-0-83-29 |
13.0 | citrix-adc-vpx-1000-premium-13-0-83-29 | projects/citrix-master-project/global/images/citrix-adc-vpx-1000-premium-13-0-83-29 |
13.0 | citrix-adc-vpx-1000-standard-13-0-83-29 | projects/citrix-master-project/global/images/citrix-adc-vpx-1000-standard-13-0-83-29 |
13.0 | citrix-adc-vpx-3000-enterprise-13-0-83-29 | projects/citrix-master-project/global/images/citrix-adc-vpx-3000-enterprise-13-0-83-29 |
13.0 | citrix-adc-vpx-3000-platinum-13-0-83-29 | projects/citrix-master-project/global/images/citrix-adc-vpx-3000-platinum-13-0-83-29 |
13.0 | citrix-adc-vpx-3000-standard-13-0-83-29 | projects/citrix-master-project/global/images/citrix-adc-vpx-3000-standard-13-0-83-29 |
13.0 | citrix-adc-vpx-5000-enterprise-13-0-83-29 | projects/citrix-master-project/global/images/citrix-adc-vpx-5000-enterprise-13-0-83-29 |
13.0 | citrix-adc-vpx-5000-platinum-13-0-83-29 | projects/citrix-master-project/global/images/citrix-adc-vpx-5000-platinum-13-0-83-29 |
13.0 | citrix-adc-vpx-5000-standard-13-0-83-29 | projects/citrix-master-project/global/images/citrix-adc-vpx-5000-standard-13-0-83-29 |
13.0 | citrix-adc-vpx-byol-13-0-83-29 | projects/citrix-master-project/global/images/citrix-adc-vpx-byol-13-0-83-29 |
13.0 | citrix-adc-vpx-express-13-0-83-29 | projects/citrix-master-project/global/images/citrix-adc-vpx-express-13-0-83-29 |
13.0 | citrix-adc-vpx-waf-1000-13-0-83-29 | projects/citrix-master-project/global/images/citrix-adc-vpx-waf-1000-13-0-83-29 |
13.1 | citrix-adc-vpx-10-enterprise-13-1-9-60 | projects/citrix-master-project/global/images/citrix-adc-vpx-10-enterprise-13-1-9-60 |
13.1 | citrix-adc-vpx-10-platinum-13-1-9-60 | projects/citrix-master-project/global/images/citrix-adc-vpx-10-platinum-13-1-9-60 |
13.1 | citrix-adc-vpx-10-standard-13-1-9-60 | projects/citrix-master-project/global/imagescitrix-adc-vpx-10-standard-13-1-9-60 |
13.1 | citrix-adc-vpx-200-enterprise-13-1-9-60 | projects/citrix-master-project/global/images/citrix-adc-vpx-200-enterprise-13-1-9-60 |
13.1 | citrix-adc-vpx-200-platinum-13-1-9-60 | projects/citrix-master-project/global/images/citrix-adc-vpx-200-platinum-13-1-9-60 |
13.1 | citrix-adc-vpx-200-standard-13-1-9-60 | projects/citrix-master-project/global/images/citrix-adc-vpx-200-standard-13-1-9-60 |
13.1 | citrix-adc-vpx-1000-advanced-13-1-9-60 | projects/citrix-master-project/global/images/citrix-adc-vpx-1000-advanced-13-1-9-60 |
13.1 | citrix-adc-vpx-1000-premium-13-1-9-60 | projects/citrix-master-project/global/images/citrix-adc-vpx-1000-premium-13-1-9-60 |
13.1 | citrix-adc-vpx-1000-standard-13-1-9-60 | projects/citrix-master-project/global/images/citrix-adc-vpx-1000-standard-13-1-9-60 |
13.1 | citrix-adc-vpx-3000-enterprise-13-1-9-60 | projects/citrix-master-project/global/images/citrix-adc-vpx-3000-enterprise-13-1-9-60 |
13.1 | citrix-adc-vpx-3000-platinum-13-1-9-60 | projects/citrix-master-project/global/images/citrix-adc-vpx-3000-platinum-13-1-9-60 |
13.1 | citrix-adc-vpx-3000-standard-13-1-9-60 | projects/citrix-master-project/global/images/citrix-adc-vpx-3000-standard-13-1-9-60 |
13.1 | citrix-adc-vpx-5000-enterprise-13-1-9-60 | projects/citrix-master-project/global/images/citrix-adc-vpx-5000-enterprise-13-1-9-60 |
13.1 | citrix-adc-vpx-5000-platinum-13-1-9-60 | projects/citrix-master-project/global/images/citrix-adc-vpx-5000-platinum-13-1-9-60 |
13.1 | citrix-adc-vpx-5000-standard-13-1-9-60 | projects/citrix-master-project/global/images/citrix-adc-vpx-5000-standard-13-1-9-60 |
13.1 | citrix-adc-vpx-byol-13-1-9-60 | projects/citrix-master-project/global/images/citrix-adc-vpx-byol-13-1-9-60 |
13.1 | citrix-adc-vpx-express-13-1-9-60 | projects/citrix-master-project/global/images/citrix-adc-vpx-express-13-1-9-60 |
13.1 | citrix-adc-vpx-waf-1000-13-1-9-60 | projects/citrix-master-project/global/images/citrix-adc-vpx-waf-1000-13-1-9-60 |
Resources
Related information
Share
Share
In this article
- Supported features
- Limitation
- Hardware requirements
- Prerequisites
- Points to note
- Scenario: Deploy a multi-NIC, multi-IP standalone VPX instance
- Scenario: Deploy a single-NIC, standalone VPX instance
- Points to note after you’ve deployed the VPX instance on GCP
- NetScaler VPX licensing
- GDM templates to deploy a NetScaler VPX instance
- NetScaler marketplace images
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.