-
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
-
Configure simultaneous multithreading for NetScaler VPX on public clouds
-
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
-
Configure a NetScaler VPX on KVM hypervisor to use Intel QAT for SSL acceleration in SR-IOV mode
-
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
-
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
-
-
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
-
Web Application Firewall protection for VPN virtual servers and authentication virtual servers
-
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
-
-
-
-
-
-
Configure DNS resource records
-
Configure NetScaler as a non-validating security aware stub-resolver
-
Jumbo frames support for DNS to handle responses of large sizes
-
Caching of EDNS0 client subnet data when the NetScaler appliance is in proxy mode
-
Use case - configure the automatic DNSSEC key management feature
-
Use Case - configure the automatic DNSSEC key management on GSLB deployment
-
-
-
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 Microsoft Azure
When you deploy a NetScaler VPX instance on Microsoft Azure Resource Manager (ARM), you can use both of the following feature sets to achieve your business needs:
- Azure cloud computing capabilities
- NetScaler load balancing and traffic management features
You can deploy NetScaler VPX instances on ARM either as standalone instances or as high availability pairs in active-standby modes.
You can deploy a NetScaler VPX instance on the Microsoft Azure in two ways:
-
Through Azure Marketplace. The NetScaler VPX virtual appliance is available as an image in the Microsoft Azure Marketplace.
-
Using the NetScaler Azure Resource Manager (ARM) json template available on GitHub. For more information, see the GitHub repository for NetScaler solution templates.
The Microsoft Azure stack is an integrated platform of hardware and software that delivers the Microsoft Azure public cloud services in a local data center to let organizations construct hybrid clouds. You can now deploy the NetScaler VPX instances on the Microsoft Azure stack.
Note:
Azure restricts access to traffic originating from outside Azure and blocks them. To provide access, enable the service or port by adding an inbound rule in the network security group attached to the NIC of the VM to which a public IP address is attached. For more information, see Azure documentation about Inbound NAT rules.
Prerequisite
You need some prerequisite knowledge before deploying a NetScaler VPX instance on Azure.
-
Familiarity with Azure terminology and network details. For information, see Azure terminology.
-
Knowledge of a NetScaler appliance. For detailed information the NetScaler appliance, see NetScaler
-
Knowledge of NetScaler networking. See the Networking topic.
How a NetScaler VPX instance works on Azure
In an on-premises deployment, a NetScaler VPX instance requires at least three IP addresses:
- Management IP address, called NSIP address
- Subnet IP (SNIP) address for communicating with the server farm
- Virtual server IP (VIP) address for accepting client requests
For more information, see Network architecture for NetScaler VPX instances on Microsoft Azure.
Note:
NetScaler VPX instance supports both the Intel and AMD processors. VPX virtual appliances can be deployed on any instance type that has two or more virtualized cores and more than 2 GB memory. For more information on system requirements, see NetScaler VPX data sheet.
In an Azure deployment, you can provision a NetScaler VPX instance on Azure in three ways:
- Multi-NIC multi-IP architecture
- Single NIC multi-IP architecture
- Single NIC single IP
Depending on your needs, you can use any of these supported architecture types.
Multi-NIC multi-IP architecture
In this deployment type, you can have more than one network interfaces (NICs) attached to a VPX instance. Any NIC can have one or more IP configurations - static or dynamic public and private IP addresses assigned to it.
For more information, see the following use cases:
-
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
Note:
To avoid MAC moves and interface mutes on Azure environments, Citrix recommends you to create a VLAN per data interface (without tag) of NetScaler VPX instance and bind the primary IP of NIC in Azure. For more information, see CTX224626 article.
Single NIC multi-IP architecture
In this deployment type, one network interfaces (NIC) associated with multiple IP configurations - static or dynamic public and private IP addresses assigned to it. For more information, see the following use cases:
- Configure multiple IP addresses for a NetScaler VPX standalone instance
- Configure multiple IP addresses for a NetScaler VPX standalone instance by using PowerShell commands
Single NIC single IP
In this deployment type, one network interfaces (NIC) associated with a single IP address, which is used to perform the functions of NSIP, SNIP, and VIP.
For more information, see Configure a NetScaler VPX standalone instance.
Note:
The single IP mode is available only in Azure deployments. This mode isn’t available for a NetScaler VPX instance on your premises, on AWS, or in other types of deployment.
NetScaler VPX licensing
A NetScaler VPX instance on Azure requires a license. The following licensing options are available for NetScaler VPX instances running on Azure.
-
Subscription-based licensing: NetScaler VPX appliances are available as paid instances on Azure Marketplace. Subscription-based licensing is a pay-as-you-go option. Users are charged hourly.
Note:
For subscription-based license instances, your subscription billing applies throughout the license period for a particular license model. Due to cloud restrictions, Azure does not support changing or removing the license model applicable for your subscription. To change or remove a subscription license, delete the existing ADC VM, and recreate a new ADC VM with the required license.
NetScaler provides technical support for subscription-based license instances. To file a support case, see Support for NetScaler on Azure – Subscription license with hourly price.
-
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 NetScaler website to generate a valid license.
- Upload the license to the instance.
Note
In an Azure stack environment, BYOL is the only available licensing option.
-
NetScaler VPX Check-In/Check-Out licensing: For more information, see NetScaler VPX Check-In/Check-Out Licensing.
Starting with NetScaler release 12.0 56.20, NetScaler 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.
VPX performance and Recommended Azure instance types
For the desired VPX performance, the following Azure instance types are recommended.
VPX performance
|
Azure instance types | ||
---|---|---|---|
VPX 1 NIC/2 NIC | VPX 3 NIC | VPX up to 8 NIC | |
Up to 200 Mbps | Standard_D2s_v4 | Standard_DS3_v2 | Standard_DS4_v2 |
Up to 1 Gbps | Standard_D4s_v4 | Standard_DS3_v2 | Standard_DS4_v2 |
Up to 5 Gbps | Standard_D8ds_v5 | Standard_D8ds_v5 | Standard_DS4_v2 |
Up to 10 Gbps | Standard_D2_v5 | Standard_D8_v5 | Standard_D16_v5 |
Points to note
-
To achieve optimal performance on NetScaler VPX instances with 1 Gbps and 5 Gbps throughput, you must enable Azure accelerated networking.
For more information on configuring Accelerated networking, see Configure a NetScaler VPX instance to use Azure accelerated networking.
-
Regardless of the subscription-based hourly license bought from Azure Marketplace, in rare cases, the NetScaler VPX instance deployed on Azure might come up with a default NetScaler license. This happens due to issues with the Azure Instance Metadata Service (IMDS).
-
Do a warm restart, before making any configuration change on the NetScaler VPX instance, to enable the correct NetScaler VPX license.
IPv6 support for NetScaler VPX instance in Azure
From release 13.1-21.x onwards, NetScaler VPX standalone instance supports IPv6 addresses in Azure. You can configure the IPv6 addresses as VIP and SNIP addresses on NetScaler VPX standalone instance in Azure cloud.
For information on how to enable IPv6 on Azure, see the following Azure documentation:
For information on how the NetScaler appliance supports IPv6, see Internet Protocol version 6.
IPv6 Limitations:
- IPv6 deployments in NetScaler currently do not support Azure backend autoscaling.
- IPv6 is not supported for NetScaler VPX HA deployment.
Limitations
Running the NetScaler VPX load-balancing solution on ARM imposes the following limitations:
-
The Azure architecture does not accommodate support for the following NetScaler features:
- Gratuitous ARP (GARP)
- L2 Mode
- Tagged VLAN
- Dynamic Routing
- virtual MAC
- USIP
- Clustering
Note:
With the NetScaler Application Delivery Management (ADM) Autoscale feature (cloud deployment), the ADC instances support clustering on all licenses. For information, see Autoscaling of NetScaler VPX in Microsoft Azure using NetScaler Console.
-
If you expect that you might have to shut down and temporarily deallocate the NetScaler VPX virtual machine at any time, assign a static Internal IP address while creating the virtual machine. If you do not assign a static internal IP address, Azure might assign the virtual machine a different IP address each time it restarts, and the virtual machine might become inaccessible.
-
Azure supports VPX throughput up to 10 Gbps. For more information, see the NetScaler VPX Data Sheet.
-
When using a NetScaler VPX instance with a throughput exceeding 3 Gbps, the actual network throughput may not align with the throughput specified in the instance’s license. However, other features such as SSL throughput and SSL transactions per second might improve.
-
The deployment ID that is generated by Azure during virtual machine provisioning isn’t visible to the user in ARM. You can’t use the deployment ID to deploy NetScaler VPX appliance on ARM.
-
The NetScaler VPX instance supports 20 Mbps throughput and standard edition features when it’s initialized.
-
The NetScaler VPX instances on Azure with accelerated networking enabled, provides better performance. Azure accelerated networking is supported on NetScaler VPX instances from release 13.0 build 76.x onwards. To enable accelerated networking on NetScaler VPX, Citrix recommends you to use an Azure instance type which supports accelerated networking.
-
For Citrix Virtual Apps and Desktops deployment, a VPN virtual server on a VPX instance can be configured in the following modes:
- Basic mode, where the
ICAOnly
VPN virtual server parameter is set to ON. The Basic mode works fully on an unlicensed NetScaler VPX instance. - SmartAccess mode, where the
ICAOnly
VPN virtual server parameter is set to OFF. The SmartAccess mode works for only five NetScaler AAA session users on an unlicensed NetScaler VPX instance.
Note:
To configure the SmartControl feature, you must apply a Premium license to the NetScaler VPX instance.
- Basic mode, where the
Share
Share
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group 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 Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.