-
Getting Started with Citrix ADC
-
Deploy a Citrix ADC VPX instance
-
Optimize Citrix ADC VPX performance on VMware ESX, Linux KVM, and Citrix Hypervisors
-
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 a high-availability setup with Azure external and internal load balancers simultaneously
-
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
-
-
-
-
-
-
-
Configuring a Basic LLB Setup
-
-
-
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 for load balancing
-
Use case 14: ShareFile wizard for load balancing Citrix ShareFile
-
Use case 15: Configure layer 4 load balancing on the Citrix ADC 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
-
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
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!
Configuring a Basic LLB Setup
To configure LLB, you first create services representing each router to the Internet Service Providers (ISPs). A PING monitor is bound by default to each service. Binding a transparent monitor is optional but recommended. Then, you create a virtual server, bind the services to the virtual server, and configure a route for the virtual server. The route identifies the virtual server as the gateway to the physical routers represented by the services. The virtual server selects a router by using the load balancing method that you specify. Optionally, you can configure persistence to make sure that all traffic for a particular session is sent over a specific link.
To configure a basic LLB setup, do the following:
Configure services
A default monitor (PING) is automatically bound to a service type of ANY when the service is created, but you can replace the default monitor with a transparent monitor, as described in Creating and Binding a Transparent Monitor.
To create a service by using the command line interface
At the command prompt, type:
add service <name> <IP> <serviceType> <port>
show service <name>
<!--NeedCopy-->
Example:
add service ISP1R_svc_any 10.10.10.254 any *
show service ISP1R_svc_any
ISP1R_svc_any (10.10.10.254:*) - ANY
State: DOWN
Last state change was at Tue Aug 31 04:31:13 2010
Time since last state change: 2 days, 05:34:18.600
Server Name: 10.10.10.254
Server ID : 0 Monitor Threshold : 0
Max Conn: 0 Max Req: 0 Max Bandwidth: 0 kbits
Use Source IP: NO
Client Keepalive(CKA): NO
Access Down Service: NO
TCP Buffering(TCPB): YES
HTTP Compression(CMP): NO
Idle timeout: Client: 120 sec Server: 120 sec
Client IP: DISABLED
Cacheable: NO
SC: OFF
SP: OFF
Down state flush: ENABLED
1) Monitor Name: ping
State: UP Weight: 1
Probes: 244705 Failed [Total: 0 Current: 0]
Last response: Success - ICMP echo reply received.
Response Time: 1.322 millisec
Done
<!--NeedCopy-->
To create services by using the configuration utility
Navigate to Traffic Management > Load Balancing > Services, and create a service.
To create services by using the configuration utility
-
Navigate to Traffic Management > Load Balancing > Services.
-
In the details pane, click Add.
-
In the Create Service dialog box, specify values for the following parameters:
- Service Name*—name
- Server—IP
- Protocol*—serviceType (Select ANY from the drop-down list.)
- Port*—port
A required parameter
-
Click Create.
-
Repeat Steps 2-4 to create another service.
-
Click Close.
-
In the Services pane, select the services that you just configured and verify that the settings displayed at the bottom of the screen are correct.
Configure an LLB virtual server and bind a service
After you create a service, create a virtual server and bind services to the virtual server. The default LB method of least connections is not supported in LLB. For information about changing the LB method, see Configuring the LLB Method and Persistence.
To create a link load balancing virtual server and bind a service by using the command line interface
At the command prompt, type:
add lb vserver <name> <serviceType>
bind lb vserver < name> <serviceName>
show lb vserver < name>
<!--NeedCopy-->
Example:
add lb vserver LLB-vip any
bind lb vserver LLB-vip ISP1R_svc_any
sh lb vserver LLB-vip
LLB-vip (0.0.0.0:0) - ANY Type: ADDRESS
State: DOWN
Last state change was at Thu Sep 2 10:51:32 2010
Time since last state change: 0 days, 17:51:46.770
Effective State: DOWN
Client Idle Timeout: 120 sec
Down state flush: ENABLED
Disable Primary Vserver On Down : DISABLED
No. of Bound Services : 1 (Total) 0 (Active)
Configured Method: ROUNDROBIN
Mode: IP
Persistence: NONE
Connection Failover: DISABLED
1) ISP1R_svc_any (10.10.10.254: *) - ANY State: DOWN Weight: 1
Done
<!--NeedCopy-->
To create a link load balancing virtual server and bind a service by using the configuration utility
- Navigate to Traffic Management > Load Balancing > Virtual Servers, and create a virtual server for link load balancing. Specify ANY in the Protocol field.
- In the IP Address Type drop-down list, select the desired option. Select Non Addressable to create a virtual server that is not directly accessible.
- Under the Services tab, in the Active column, select the check box for the service that you want to bind to the virtual server.
Configure the LLB method and persistence
By default, the Citrix ADC appliance uses the least connections method to select the service for redirecting each client request, but you should set the LLB method to one of the supported methods. You can also configure persistence, so that different transmissions from the same client are directed to the same server.
To configure the LLB method and/or persistence by using the command line interface
At the command prompt, type the following command:
set lb vserver <name> -lbMethod <lbMethod> -persistenceType <persistenceType>
show lb vserver <name>
<!--NeedCopy-->
Example:
set lb vserver LLB-vip -lbmethod ROUNDROBIN -persistencetype SOURCEIP
show lb vserver LLB-vip
LLB-vip (0.0.0.0:0) - ANY Type: ADDRESS
State: DOWN
Last state change was at Fri Sep 3 04:46:48 2010
Time since last state change: 0 days, 00:52:21.200
Effective State: DOWN
Client Idle Timeout: 120 sec
Down state flush: ENABLED
Disable Primary Vserver On Down : DISABLED
No. of Bound Services : 0 (Total) 0 (Active)
Configured Method: ROUNDROBIN
Mode: IP
Persistence: SOURCEIP
Persistence Mask: 255.255.255.255 Persistence v6MaskLength: 128 Persistence Timeout: 2 min
Connection Failover: DISABLED
<!--NeedCopy-->
To configure the link load balancing method and/or persistence by using the configuration utility
- Navigate to Traffic Management > Load Balancing > Virtual Servers and select the virtual server for which you want to configure the load balancing method and/or persistence settings.
- In the Advanced Settings section, select Method and configure the load balancing method.
- In the Advanced Settings section, select Persistence and configure the persistence parameters.
Configure an LLB route
After configuring the IPv4 or IPv6 services, virtual servers, LLB methods, and persistence, you configure an IPv4 or IPv6 LLB route for the network specifying the LLB virtual server as the gateway. A route is a collection of links that are load balanced. Requests are sent to the LLB virtual server IP address that acts as the gateway for all outbound traffic and selects the router based on the LLB method configured.
To configure an IPv4 LLB route by using the command line interface
At the command prompt, type:
add lb route <network> <netmask> <gatewayName>
show lb route [<network> <netmask>]
<!--NeedCopy-->
Example:
add lb route 0.0.0.0 0.0.0.0 LLB-vip
show lb route 0.0.0.0 0.0.0.0
Network Netmask Gateway/VIP Flags
----------- ------------- -------------- --------
1) 0.0.0.0 0.0.0.0 LLB-vip UP
<!--NeedCopy-->
To configure an IPv6 LLB route by using the command line interface
At the command prompt, type:
add lb route6 <network> <gatewayName>
show lb route6
<!--NeedCopy-->
Example:
add lb route6 ::/0 llb6_vs show lb route6 Network VIP Flags ----------- --------- -------- 1) ::/0 llb6_vs UP
<!--NeedCopy-->
To configure an LLB route by using the configuration utility
Navigate to System > Network > Routes, and select LLB, and configure the LLB route.
Note: Select LLBV6 to configure an IPV6 route.
To configure an LLB route by using the configuration utility
-
Navigate to System > Network > Routes.
-
In the details pane, select one of the following:
- Click LLB to configure an IPv4 route.
- Click LLBV6 to configure an IPv4 route.
-
In the Create LB Route or Create LB IPV6 Routedialog box, set the following parameters:
- Network*
- Netmask*—Required for IPV4 routes.
-
Gateway Name*—gatewayName
*A required parameter
-
Click Create, and then click Close. The route that you just created appears on the LLB or the LLB6 tab in the Routes pane.
The following diagram shows a basic LLB setup. A service is configured for each of the two links (ISPs) and PING monitors are bound by default to these services. A link is selected based on the LLB method configured.
Figure 1. Basic LLB Setup
Note
If your Internet service provider has provided an IPv6 address, replace the IPv4 service with an IPv6 service in the above figure.
Create and bind a transparent monitor
You create a transparent monitor to monitor the health of upstream devices, such as routers. You can then bind the transparent monitor to services. The default PING monitor monitors the connectivity only between the Citrix ADC appliance and the upstream device. The transparent monitor monitors all the devices existing in the path from the appliance to the device that owns the destination IP address specified in the monitor. If a transparent monitor is not configured and the status of the router is UP but one of the next hop devices from that router is down, the appliance includes the router while performing load balancing and forwards the packet to the router. However, the packet is not delivered to the final destination because one of the next hop devices is down. By binding a transparent monitor, if any of the devices (including the router) are down, the service is marked as DOWN and the router is not included when the appliance performs link load balancing.
To create a transparent monitor by using the command line interface
At the command prompt, type:
add lb monitor <monitorName> <type> -destIP <ip_addr|*> -transparent YES
show lb monitor [<monitorName>]
<!--NeedCopy-->
Example:
add lb monitor monitor-1 PING -destIP 10.10.10.11 -transparent YES
> show lb monitor monitor-1
1) Name.......: monitor-1 Type......: PING State....: ENABLED
Standard parameters:
Interval.........: 5 sec Retries...........: 3
Response timeout.: 2 sec Down time.........: 30 sec
Reverse..........: NO Transparent.......: YES
Secure...........: NO LRTM..............: ENABLED
Action...........: Not applicable Deviation.........: 0 sec
Destination IP...: 10.10.10.11
Destination port.: Bound service
Iptunnel.........: NO
TOS..............: NO TOS ID............: 0
SNMP Alert Retries: 0 Success Retries..: 1
Failure Retries..: 0
<!--NeedCopy-->
To create a transparent monitor by using the configuration utility
Navigate to Traffic Management > Load Balancing > Monitors and configure a transparent monitor.
To create a transparent monitor by using the configuration utility
-
Navigate to Traffic Management > Load Balancing > Monitors.
-
In the Monitors pane, click Add.
-
In the Create Monitor dialog box, set the following parameters:
- Name*
- Type*
- Destination IP
-
Transparent
*A required parameter
-
Click Create, and then click Close.
-
In the Monitors pane, select the monitor that you just configured and verify that the settings displayed in the Details pane are correct.
To bind a monitor to a service by using the configuration utility
- Navigate to Traffic Management > Load Balancing > Services.
- On the Monitors tab, under Available, select the monitor that you want to bind to the service, and then click Add.
To bind a monitor to a service by using the command line interface
At the command prompt, type:
bind lb monitor <monitorName> <serviceName>
show service <name>
<!--NeedCopy-->
Example:
bind lb monitor monitor-HTTP-1 ISP1R_svc_any
Done
> show service ISP1R_svc_any
ISP1R_svc_any (10.10.10.254:*) - ANY
State: UP
Last state change was at Thu Sep 2 10:51:07 2010
Time since last state change: 0 days, 18:41:55.130
Server Name: 10.10.10.254
Server ID : 0 Monitor Threshold : 0
Max Conn: 0 Max Req: 0 Max Bandwidth: 0 kbits
Use Source IP: NO
Client Keepalive(CKA): NO
Access Down Service: NO
TCP Buffering(TCPB): YES
HTTP Compression(CMP): NO
Idle timeout: Client: 120 sec Server: 120 sec
Client IP: DISABLED
Cacheable: NO
SC: OFF
SP: OFF
Down state flush: ENABLED
1) Monitor Name: monitor-HTTP-1
State: UP Weight: 1
Probes: 1256 Failed [Total: 0 Current: 0]
Last response: Success - ICMP echo reply received.
Response Time: 1.322 millisec
Done
<!--NeedCopy-->
To bind a monitor to a service by using the configuration utility
- Navigate to Traffic Management > Load Balancing > Services.
- In the details pane, select a service to which you want to bind a monitor, and then click Open.
- In the Configure Service dialog box, on the Monitors tab, under Available, select the monitor that you want to bind to the service, and then click Add.
- Click OK.
- In the Services pane, select the service that you just configured and verify that the settings displayed in the Details pane are correct.
Share
Share
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group 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 Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.