-
Getting Started with Citrix NetScaler
-
Deploy a Citrix NetScaler VPX instance
-
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
-
-
Upgrade and downgrade a NetScaler appliance
-
-
-
-
-
Configuring RNAT with LLB
-
-
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!
Configuring RNAT with LLB
You can configure an LLB setup for reverse network address translation (RNAT) for outbound traffic. This ensures that the return network traffic for a specific flow is routed through the same path. First configure basic LLB, as described in “Configuring a Basic LLB Setup”, and then configure RNAT. You must then enable use subnet IP (USNIP) mode.
In the following diagram, the NetScaler appliance uses LLB to route outbound traffic to different links. During the RNAT operation, the NetScaler appliance replaces the source IP addresses of the outbound traffic with the public NAT IP address (198.141.23.1) to route the traffic through ISP-1. Similarly, the NetScaler appliance replaces the source IP addresses with 198.140.23.1 to route the traffic through ISP-2.
To add SNIPs for ISP routers by using the command line interface
At the command prompt, type:
add NS IP <subnet of first ISP in the IP router> <subnet mask> -type SNIP
add NS IP <subnet of second ISP in the IP router> <subnet mask> -type SNIP
Example:
add ns ip 10.140.23.1 255.255.255.0 -type snip
add ns ip 10.141.23.1 255.255.255.0 -type snip
To configure RNAT by using the command line interface
At the command prompt, type:
set rnat <network> <netmask>
show rnat
Example:
set rnat 10.102.29.0 255.255.255.0 -natIP 10.140.23.1
set rnat 10.102.29.0 255.255.255.0 -natIP 10.141.23.1
show rnat
1) Network: 10.102.29.0 Netmask: 255.255.255.0
NatIP: 10.140.23.1
2) Network: 10.102.29.0 Netmask: 255.255.255.0
NatIP: 10.141.23.1
To configure RNAT by using the configuration utility
- Navigate to System > Network > NATs.
- On the RNAT tab, click Configure RNAT.
- Specify the network on which to perform RNAT.
Note
You can also configure RNAT by using Access Control Lists (ACLs). Refer Configuring RNAT for details.
To enable Use Subnet IP mode by using the command line interface
At the command prompt, type:
enable ns mode USNIP
show ns mode
Example:
enable ns mode USNIP
show ns mode
Mode Acronym Status
------- ------- ------
1) Fast Ramp FR ON
2) ….
8) Use Subnet IP USNIP ON
9) …
To enable Use Subnet IP mode by using the configuration utility
- Navigate to System > Settings and, under Modes and Features, click Configure Modes.
- In the Configure Modes dialog box, select Use Subnet IP, and then click OK.
Share
Share
In this article
- To add SNIPs for ISP routers by using the command line interface
- To configure RNAT by using the command line interface
- To configure RNAT by using the configuration utility
- To enable Use Subnet IP mode by using the command line interface
- To enable Use Subnet IP mode by using the configuration utility
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.