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
Solutions for Telecom Service Providers
Load Balance Control-Plane Traffic that is based on Diameter, SIP, and SMPP Protocols
提供DNS基础设施/交通服务,等as, Load Balancing, Caching, and Logging for Telecom Service Providers
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
配置CloudBridge连接器D之间的隧道atacenter 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!
Configure a high-availability setup with Azure external and internal load balancers simultaneously
The high availability pair on Azure supports both external and internal load balancers simultaneously.
You have the following two options to configure a high availability pair using both Azure external and internal load balancers:
- Using two LB virtual servers on the NetScaler appliance.
- Using one LB virtual server and an IP set. The single LB virtual server serves traffic to multiple IPs, which are defined by the IPset.
Perform the following steps to configure a high availability pair on Azure using both the external and internal load balancers simultaneously:
For Steps 1 and 2, use the Azure portal. For Steps 3 and 4, use the NetScaler VPX GUI or the CLI.
Step 1.Configure an Azure load balancer, either an external load balancer or an internal load balancer.
For more information on configuring high-availability setup with Azure external load balancers, seeConfigure a high-availability setup with multiple IP addresses and NIC.
For more information on configuring high-availability setup with Azure internal load balancers, seeConfigure HA-INC nodes by using the NetScaler high availability template with Azure ILB.
Step 2.Create an extra load balancer (ILB) in your resource group. In Step 1, if you have created an external load balancer, you now create an internal load balancer and conversely.
To create an internal load balancer, choose the load balancer type asInternal. For theSubnetfield, you must choose your NetScaler client subnet. You can choose to provide a static IP address in that subnet, provided there are no conflicts. Otherwise, choose the dynamic IP address.
To create an external load balancer, choose the load balancer type asPublicand create the public IP address here.
After you have created the Azure Load Balancer, navigate toFrontend IP configurationand note down the IP address shown here. You must use this IP address while creating the ADC load balancing virtual server as in Step 3.
- In theAzure Load Balancer configurationpage, the ARM template deployment helps create the LB rule, back-end pools, and health probes.
- Add the high availability pair client NICs to the backend pool for the ILB.
- Create a health probe (TCP, 9000 port)
- Create two load balancing rules:
- One LB rule for HTTP traffic (webapp use case) on port 80. The rule must also use the backend port 80. Select the created backend pool and the health probe. Floating IP must be enabled.
- Another LB rule for HTTPS or CVAD traffic on port 443. The process is the same as the HTTP traffic.
Step 3.On the primary node of NetScaler appliance, create a load balancing virtual server for ILB.
添加一个虚拟服务器负载平衡。
add lb vserver
[ ] [ ] Example:
add lb vserver vserver_name HTTP 52.172.96.71 80
Note:
使用负载平衡器前端IP地址,我s associated with the additional Load balancer that you create in Step 2.
Bind a service to a load balancing virtual server.
bind lb vserver
Example:
bind lb vserver Vserver-LB-1 Service-HTTP-1
For more information, seeSet up basic load balancing
Step 4:As an alternative to Step 3, you can create a load balancing virtual server for ILB using IPsets.
Add an IP address of type virtual server IP (VIP).
add nsip
-type Example:
add nsip 52.172.96.71 -type vip
Add an IPset on both primary and secondary nodes.
add ipset
Example:
add ipset ipset1
Bind IP addresses to the IP set.
bind ipset
Example:
bind ipset ipset1 52.172.96.71
Set the existing LB virtual server to use the IPset.
set lb vserver
-ipset Example:
set lb vserver vserver_name -ipset ipset1
For more information, seeConfigure a multi-IP virtual server.
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.