-
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 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!
Use case 7: Configure load balancing in DSR mode by using IP Over IP
You can configure your NetScaler appliance to use direct server return (DSR) mode across Layer 3 networks by using IP tunneling, also called IP over IP configuration. As with standard load balancing configurations for DSR mode, this allows servers to respond to clients directly instead of using a return path through the NetScaler appliance, improving response times and throughput. As with standard DSR mode, the NetScaler appliance monitors the servers and performs health checks on the application ports.
With IP over IP configuration, the NetScaler appliance and the servers do not need to be on the same Layer 2 subnet. Instead, the NetScaler appliance encapsulates the packets before sending them to the destination server. After the destination server receives the packets, it decapsulates the packets, and then sends its responses directly to the client.
To configure IP over IP DSR mode on your NetScaler appliance, you must do the following:
- Create a load balancing virtual server. Set the protocol to ANY and set the mode to IPTUNNEL.
- Create services. Create a service for each of your back-end applications. Bind the services that you created to the virtual server.
- Configure for decapsulation. You can configure either a NetScaler appliance or a back-end server to act as a decapsulator.
Configure a load balancing virtual server
Configure a virtual server to handle requests to your applications. Assign a service type of ANY and set the forwarding method to IPTUNNEL. Optionally, configure the virtual server to operate in sessionless mode. You can configure any load balancing method that you want to use.
To create and configure a load balancing virtual server for IP over IP DSR by using the command line interface
At the command prompt type the following command to configure a load balancing virtual server for IP over IP DSR and verify the configuration:
add lb vserver <name> serviceType <serviceType> IPAddress <ip> Port <port> -lbMethod <method> -m <ipTunnelTag> -sessionless <sessionless>
show lb vserver <name>
Example:
In the following example, we have selected the load balancing method as sourceIPhash and configured sessionless load balancing.
add lb vserver Vserver-LB-1 ANY 10.102.29.60 * -lbMethod SourceIPHash -m IPTUNNEL -sessionless enabled
To create and configure a load balancing virtual server for IP over IP DSR by using the configuration utility
- Navigate to Traffic Management > Load Balancing > Virtual Servers.
- Create a virtual server, and specify Redirection Mode as IP Tunnel Based.
Configure services for IP over IP DSR
After creating your load-balanced server, You must configure one service for each of your applications. The service handles traffic from the NetScaler appliance to those applications, and allows the NetScaler appliance to monitor the health of each application.
You assign a service type of ANY and configure it for USIP mode. Optionally, you can also bind a monitor of type IPTUNNEL to the service for tunnel-based monitoring.
To create and configure a service for IP over IP DSR by using the command line interface
At the command prompt, type the following commands to create a service and optionally, create a monitor and bind it to the service:
add service <serviceName> <serverName> <serviceType> <port> -usip <usip>
add monitor <monitorName> <monitorType> -destip <ip> -iptunnel <iptunnel>
bind service <serviceName> -monitorName <monitorName>
Example:
In the following example, we are creating a monitor of type IPTUNNEL:
add monitor mon-1 PING -destip 10.102.29.60 -iptunnel yes
add service Service-DSR-1 10.102.30.5 ANY * -usip yes
bind service Service-DSR-1 -monitorName mon-1
To configure a monitor by using the configuration utility
- Navigate to Traffic Management > Load Balancing > Monitors.
- Create a monitor, and select IP Tunnel.
To create and configure a service for IP over IP DSR by using the configuration utility
- Navigate to Traffic Management > Load Balancing > Services.
- Create a service and, in Settings, select Use Source IP Address.
To bind a service to a load balancing virtual server by using the command line interface
At the command prompt type the following command:
bind lb vserver <name> <serviceName>
Example:
bind lb vserver Vserver-LB-1 Service-DSR-1
To bind a service to a load balancing virtual server by using the configuration utility
- Navigate to Traffic Management > Load Balancing > Virtual Servers.
- Open a virtual server, and click in the Services section to bind a service to the virtual server.
Decapsulator configuration
- When a NetScaler appliance is used as a decapsulator, an IP tunnel must be created in the NetScaler appliance. For details, see Configuring IP Tunnels.
Example configuration:
add lb vserver v1 any 1.1.1.1 * -m IPTUNNEL
add service s1 2.2.2.2 ANY *
bind lb vserver v1 s1
add iptunnel tun1 <snip_in_encap> netmask *
add ns ip 1.1.1.1 255.255.255.255 –type vip –arp disabled
add lb vserver v1 any 1.1.1.1 *
add service s1 <actualserverip> ANY *
bind lb vserver v1 s1
- When a back-end server is used as a decapsulator, the back-end configuration varies depending on the server type. The steps involved in configuring a back-end server as a decapsulator are;
- Configure a loop back interface.
- Add a route through tunnel interface.
Note: Make sure that the tunnel modules are installed in the system.
Example configuration:
In this example, 1.1.1.1 is the NetScaler virtual IP (VIP) address and 2.2.2.2 is the back-end server IP address.
The VIP address is configured in the loopback interface and a route is added through the tunnel interface. The modprobe ipip
command is used for enabling the tunnel interface.
add lb vserver v1 ANY 1.1.1.1 80 -m IPTUNNEL
add service svc1 2.2.2.2 ANY 80 -usip YES -useproxyport NO
bind lb vserver v1 svc1
ifconfig lo inet 1.1.1.1 netmask 255.255.255.255
modprobe ipip
echo 1 > /proc/sys/net/ipv4/conf/tunl0/arp_ignore
echo 2 > /proc/sys/net/ipv4/conf/tunl0/arp_announce
ifconfig tunl0 1.1.1.1 netmask 255.255.255.255 up
route add -host 1.1.1.1 dev tunl0
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.