-
Getting Started with Citrix ADC
-
Deploy a Citrix ADC VPX instance
-
Apply Citrix ADC VPX configurations at the first boot of the Citrix ADC appliance in cloud
-
Install a Citrix ADC VPX instance on Microsoft Hyper-V servers
-
Install a Citrix ADC VPX instance on Linux-KVM platform
-
Prerequisites for Installing Citrix ADC VPX Virtual Appliances on Linux-KVM Platform
-
Provisioning the Citrix ADC Virtual Appliance by using OpenStack
-
Provisioning the Citrix ADC Virtual Appliance by using the Virtual Machine Manager
-
Configuring Citrix ADC Virtual Appliances to Use SR-IOV Network Interface
-
Configuring Citrix ADC Virtual Appliances to use PCI Passthrough Network Interface
-
Provisioning the Citrix ADC Virtual Appliance by using the virsh Program
-
Provisioning the Citrix ADC Virtual Appliance with SR-IOV, on OpenStack
-
Configuring a Citrix ADC VPX Instance on KVM to Use OVS DPDK-Based Host Interfaces
-
-
Deploy a Citrix ADC 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
-
Configure a Citrix ADC VPX instance to use SR-IOV network interface
-
Configure a Citrix ADC VPX instance to use Enhanced Networking with AWS ENA
-
Deploy a Citrix ADC VPX instance on Microsoft Azure
-
Network architecture for Citrix ADC VPX instances on Microsoft Azure
-
Configure multiple IP addresses for a Citrix ADC 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
-
Configure a Citrix ADC VPX instance to use Azure accelerated networking
-
Configure HA-INC nodes by using the Citrix high availability template with Azure ILB
-
Configure address pools (IIP) for a Citrix Gateway appliance
-
Upgrade and downgrade a Citrix ADC appliance
-
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
-
On-premises Citrix 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 14: ShareFile wizard for load balancing Citrix ShareFile
-
-
-
-
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 Citrix ADC Appliance and Cisco IOS Device
-
CloudBridge Connector Tunnel Diagnostics and Troubleshooting
-
-
Synchronizing Configuration Files in a High Availability Setup
-
Restricting High-Availability Synchronization Traffic to a VLAN
-
Understanding the High Availability Health Check Computation
-
Managing High Availability Heartbeat Messages on a Citrix ADC Appliance
-
Remove and Replace a Citrix ADC in a High Availability Setup
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 Subnet IP Addresses (SNIPs)
A subnet IP address (SNIP) is a Citrix ADC owned IP address that is used by the Citrix ADC to communicate with the servers.
The Citrix ADC uses the subnet IP address as a source IP address to proxy client connections to servers. It also uses the subnet IP address when generating its own packets, such as packets related to dynamic routing protocols, or to send monitor probes to check the health of the servers. Depending on your network topology, you might have to configure one or more SNIPs for different scenarios.
To configure a SNIP address on a Citrix ADC, you add the SNIP address and then enable global Use Subnet IP (USNIP) mode. As an alternative to creating SNIPs one at a time, you can specify a consecutive range of SNIPs.
To configure a SNIP address by using the CLI:
At the command prompt, type:
- add ns ip <IPAddress> <netmask> -type SNIP
- show ns ip <IPAddress>
Example:
> add ns ip 10.102.29.203 255.255.255.0 -type SNIP
Done
To create a range of SNIP addresses by using the CLI:
At the command prompt, type:
- add ns ip <IPAddress> <netmask> -type SNIP
- show ns ip <IPAddress>
Example:
> add ns ip 10.102.29.[205-209] 255.255.255.0 -type SNIP
ip "10.102.29.205" added
ip "10.102.29.206" added
ip "10.102.29.207" added
ip "10.102.29.208" added
ip "10.102.29.209" added
Done
To enable or disable USNIP mode by using the CLI:
At the command prompt, type one of the following commands:
- enable ns modeUSNIP
- disable ns modeUSNIP
To configure a SNIP address by using the GUI:
Navigate to System > Network > IPs > IPV4s, and add a new SNIP address or edit an existing address.
To create a range of SNIP addresses by using the GUI:
- Navigate to System > Network > IPs > IPV4s.
- In the Action list, select Add Range.
To enable or disable USNIP mode by using the CLI:
At the command prompt, type one of the following commands:
-
enable ns mode USNIP
-
disable ns mode USNIP
To enable or disable USNIP mode by using the GUI:
- Navigate to System > Settings, in Modes and Features group, click Change modes.
- Select or clear the Use Subnet IP option.
Using SNIPs for a Directly Connected Server Subnet
To enable communication between the Citrix ADC and a server that is either connected directly to the Citrix ADC or connected through only an L2 switch, you must configure a subnet IP address that belongs to the subnet of the server. You must configure at least one subnet IP address for each directly connected subnet, except for the directly connected management subnet that is connected through NSIP.
Consider an example of a load balancing setup in which load balancing virtual server LBVS1 on Citrix ADC NS1 is used to load balance servers S1 and S2, which are connected to NS1 through L2 switch SW1. S1 and S2 belong to the same subnet.
SNIP address SNIP1, which belongs to the same subnet as S1 and S2, is configured on NS1. As soon as SNIP1 is configured, NS1 broadcasts ARP packets for SNIP1.
Services SVC-S1 and SVC-S2 on NS1 represent S1 and S2. As soon as these services are configured, NS1 broadcasts ARP requests for S1 and S2 to resolve IP-to-MAC mapping. After S1 and S2 respond, NS1 sends them monitoring probes at regular intervals, from address SNIP1, to check their health.
For more information about configuring load balancing on a Citrix ADC, see Load Balancing.
Following is the traffic flow in this example:
- Client C1 sends a request packet to LBVS-1. The request packet has:
- Source IP = IP address of the client (198.51.100.10)
- Destination IP = IP address of LBVS-1 (203.0.113.15)
- LBVS1 of NS1 receives the request packet.
- LBVS1’s load balancing algorithm selects server S2.
- Because S2 is directly connected to NS1, and SNIP1 (192.0.1.10) is the only IP address on NS1 that belongs to the same subnet as S2, NS1 opens a connection between SNIP1 and S2.
- NS1 sends the request packet to S2 from SNIP1. The request packet has:
- Source IP = SNIP1 (192.0.1.10)
- Destination IP = IP address of S2 (192.0.1.30)
- S2’s response returns by the same path.
Using SNIPs for Server Subnets Connected through a Router
To enable communication between the Citrix ADC and servers in subnets connected through a router, you must configure at least one subnet IP address that belongs to the subnet of the directly connected interface to the router. The ADC uses this subnet IP address to communicate with servers in subnets that can be reached through the router.
Consider an example of a load balancing setup in which load balancing virtual server LBVS1 on Citrix ADC NS1 is used to load balance servers S1, S2, S3, and S4, which are connected to NS1 through router R1.
S1 and S2 belong to same subnet, 192.0.2.0/24, and are connected to R1 through L2 switch SW1. S3 and S4 belong to a different subnet, 192.0.3.0/24, and are connected to R1 through L2 switch SW2.
Citrix ADC NS1 is connected to router R1 through subnet 192.0.1.0/24. SNIP address SNIP1, which belongs to the same subnet as the directly connected interface to the router (192.0.1.0/24), is configured on NS1. NS1 uses this address to communicate with servers S1 and S2, and with servers S3 and S4.
For more information about configuring load balancing on a Citrix ADC, see Load Balancing.
As soon as address SNIP1 is configured, NS1 broadcasts ARP announcement packets for SNIP1.
NS1’s routing table consists of route entries for S1, S2, S3, and S4 through R1. These route entries are either static route entries or advertised by R1 to NS1, using dynamic routing protocols.
Services SVC-S1, SVC-S2, SVC-S3, and SVC-S4 on NS1 represent servers S1, S2, S3, and S4. NS1 finds, in its routing tables, that these servers are reachable through R1. NS1 sends them monitoring probes at regular intervals, from address SNIP1, to check their health.
For more information about IP routing on a Citrix ADC, see IP Routing.
Following is the traffic flow in this example:
- Client C1 sends a request packet to LBVS-1. The request packet has:
- Source IP = IP address of the client (198.51.100.10)
- Destination IP = IP address of LBVS-1 (203.0.113.15)
- LBVS1 of NS1 receives the request packet.
- LBVS1’s load balancing algorithm selects server S3.
- NS1 checks its routing table and finds that S3 is reachable through R1. SNIP1 (192.0.1.10) is the only IP address on NS1 that belongs to the same subnet as router R1, NS1 opens a connection between SNIP1 and S3 through R1.
- NS1 sends the request packet to R1 from SNIP1. The request packet has:
- Source IP address = SNIP1 (192.0.1.10)
- Destination IP address = IP address of S3 (192.0.3.20)
- The request reaches R1, which checks its routing table and forwards the request packet to S3.
- S3’s response returns by the same path.
Using SNIPs for Multiple Server Subnets (VLANs) on an L2 Switch
When you have multiple server subnets (VLANs) on an L2 switch that is connected to a Citrix ADC, you must configure at least one SNIP address for each of the server subnets, so that the Citrix ADC can communicate with these server subnets.
Consider an example of a load balancing setup in which load balancing virtual server LBVS1 on Citrix ADC NS1 is used to load balance servers S1 and S2, which are connected to NS1 through L2 switch SW1. S1 and S2 belong to different subnets and are part of VLAN 10 and VLAN20, respectively. The link between NS1 and SW1 is a trunk link and is shared by VLAN10 and VLAN20.
For more information about configuring load balancing on a Citrix ADC, see Load Balancing.
Subnet IP addresses SNIP1 (for reference purposes only) and SNIP2 (for reference purposes only) are configured on NS1. NS1 uses SNIP1 (on VLAN 10) to communicate with server S1, and SNIP2 (on VLAN 20) to communicate with S2. As soon as SNIP1 and SNIP2 are configured, NS1 broadcasts ARP announcement packets for SNIP1 and SNIP2.
For more information about configuring VLANs on a Citrix ADC, see Configuring a VLAN.
Services SVC-S1 and SVC-S2 on NS1 represent servers S1 and S2. As soon as these services are configured, NS1 broadcasts ARP requests for them. After S1 and S2 respond, NS1 sends them monitoring probes at regular intervals to check their health. NS1 sends monitoring probes to S1 from address SNIP1, and to S2 from address SNIP2.
Following is the traffic flow in this example:
- Client C1 sends a request packet to LBVS-1. The request packet has:
- Source IP = IP address of the client (198.51.100.10)
- Destination IP = IP address of LBVS-1 (203.0.113.15)
- LBVS1 of NS1 receives the request packet.
- LBVS1’s load balancing algorithm selects server S2.
- Because S2 is directly connected to NS1, and SNIP2 (192.0.2.10) is the only IP address on NS1 that belongs to the same subnet as S2, NS1 opens a connection between SNIP2 and S2. Note: If S1 is selected, NS1 opens a connection between SNIP1 and S1.
- NS1 sends the request packet to S2 from SNIP2. The request packet has:
- Source IP = SNIP1 (192.0.2.10)
- Destination IP = IP address of S2 (192.0.2.20)
- S2’s response returns by the same path.
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.