-
Getting Started with Citrix NetScaler
-
Load balance traffic on a NetScaler appliance
-
Configure features to protect the load balancing configuration
-
A typical load balancing scenario
-
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 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 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)
此内容已动态机器翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
This content has been machine translated dynamically.
This content has been machine translated dynamically.
This content has been machine translated dynamically.
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.
这篇文章已经过机器翻译.放弃
Translation failed!
A typical load balancing scenario
In a load balancing setup, the NetScaler appliances are logically located between the client and the server farm, and they manage traffic flow to the servers.
The following figure shows the topology of a basic load balancing configuration.
Figure 1. Basic Load Balancing Topology
The virtual server selects the service and assigns it to serve client requests. Consider the scenario in the preceding figure, where the services service-HTTP-1 and service-HTTP-2 are created and bound to the virtual server named virtual server-LB-1. Virtual server-LB-1 forwards the client request to either service-HTTP-1 or service-HTTP-2. The system selects the service for each request by using the Least Connections load balancing method. The following table lists the names and values of the basic entities that must be configured on the system.
Table 1. LB Configuration Parameter Values
The following figure shows the load balancing sample values and required parameters that are described in the preceding table.
Figure 2. Load Balancing Entity Model
The following tables list the commands used to configure this load balancing setup by using the command line interface.
Task | Command |
---|---|
To enable load balancing | enable feature lb |
To create a service named service-HTTP-1 | add service service-HTTP-1 10.102.29.5 HTTP 80 |
To create a service named service-HTTP-2 | add service service-HTTP-2 10.102.29.6 HTTP 80 |
To create a virtual server named vserver-LB-1 | add lb vserver vserver-LB-1 HTTP 10.102.29.60 80 |
To bind a service named service-HTTP-1 to a virtual server named vserver-LB-1 | bind lb vserver vserver-LB-1 service-HTTP-1 |
To bind a service named service-HTTP-2 to a virtual server named vserver-LB-1 | bind lb vserver vserver-LB-1 service-HTTP-2 |
Table 2. Initial Configuration Tasks
For more information about the initial configuration tasks, see Setting Up Basic Load Balancing.
Task | Command |
---|---|
To view the properties of a virtual server named vserver-LB-1 | show lb vserver vserver-LB-1 |
To view the statistics of a virtual server named vserver-LB-1 | stat lb vserver vserver-LB-1 |
To view the properties of a service named service-HTTP-1 | show service service-HTTP-1 |
To view the statistics of a service named service-HTTP-1 | stat service service-HTTP-1 |
To view the bindings of a service named service-HTTP-1 | show service bindings service-HTTP-1 |
Table 3. Verification Tasks
Task | Command |
---|---|
To configure persistence on a virtual server named vserver-LB-1 | set lb vserver vserver-LB-1 -persistenceType SOURCEIP -persistenceMask 255.255.255.255 -timeout 2 |
To configure COOKIEINSERT persistence on a virtual server named vserver-LB-1 | set lb vserver vserver-LB-1 -persistenceType COOKIEINSERT |
To configure URLPassive persistence on a virtual server named vserver-LB-1 | set lb vserver vserver-LB-1 -persistenceType URLPASSIVE |
To configure a virtual server to redirect the client request to a URL on a virtual server named vserver-LB-1 | set lb vserver vserver-LB-1 -redirectURL http://www.newdomain.com/mysite/maintenance
|
To set a backup virtual server on a virtual server named vserver-LB-1 | set lb vserver vserver-LB-1 -backupVserver vserver-LB-2 |
Table 4. Customization Tasks
For more information about configuring persistence, see Choosing and Configuring Persistence Settings. For information about configuring a virtual server to redirect a client request to a URL and setting up a backup virtual server, see Configuring Features to Protect the Load Balancing Configuration.
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.