-
Getting Started with Citrix ADC
-
Deploy a Citrix ADC VPX instance
-
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 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 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
-
Configuring authentication, authorization, and auditing policies
-
Configuring Authentication, authorization, and auditing with commonly used protocols
-
Use an on-premises Citrix Gateway as the identity provider for Citrix Cloud
-
Troubleshoot authentication issues in Citrix ADC and Citrix Gateway with aaad.debug module
-
-
-
-
-
-
Enterprise Environment
-
-
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
-
-
-
-
-
Authentication and authorization
-
-
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!
Enterprise Environment
In the enterprise setup, the Citrix ADC is placed between the firewalls connecting to the public Internet and the internal private network and handles egress traffic. The Citrix ADC selects the best firewall based on the configured load balancing policy.
The following diagram shows the enterprise firewall load balancing environment
Figure 1. Firewall Load Balancing (Enterprise)
The service type ANY configures the Citrix ADC to accept all traffic.
To avail benefits related to HTTP and TCP, configure the service and virtual server with type HTTP or TCP. For FTP to work, configure the service with type FTP.
Configuring the Citrix ADC in an Enterprise Environment
Perform the following tasks to configure a Citrix ADC in an enterprise environment.
For traffic from the server (egress)
- Enable the load balancing feature.
- Configure a wildcard service for each firewall.
- Configure a monitor for each wildcard service.
- Configure a wildcard virtual server to load balance the traffic sent to the firewalls.
- Configure the virtual server in MAC rewrite mode.
- Bind firewall services to the wildcard virtual server.
For traffic across private network servers
- Configure a service for each virtual server.
- Configure a monitor for each service.
- Configure an HTTP virtual server to balance traffic sent to the servers.
- Bind HTTP services to the HTTP virtual server.
- Save and Verify the Configuration.
Enable the load balancing feature
You can configure load balancing entities such as services and virtual servers when the load balancing feature is disabled, but they do not function until you enable the feature.
To enable load balancing by using the command line interface
At the command prompt, type the following command to enable load balancing and verify the configuration:
- enable ns feature LB
- show ns feature
Example:
> enable ns feature LoadBalancing
Done
> show ns feature
Feature Acronym Status
------- ------- ------
1) Web Logging WL OFF
2) Surge Protection SP ON
3) Load Balancing LB ON
.
.
.
24) NetScaler Push push OFF
Done
<!--NeedCopy-->
To enable load balancing by using the configuration utility
Navigate to System > Settings and, in Configure Basic Features, select Load Balancing.
Configure a wildcard service for each firewall
To configure a wildcard service for each firewall by using the command line interface
At the command prompt, type:
add service <name> <serverName> ANY *
<!--NeedCopy-->
Example:
add service Service-HTTP-1 10.102.29.5 ANY *
<!--NeedCopy-->
To configure a wildcard service for each firewall 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 as shown:
- Service Name—name
- Server—serverName
- In Protocol, select ANY, and in Port, select *.
- Click Create, and then click Close. The service you created appears in the Services pane.
Configure a monitor for each wildcard service
A PING monitor is bound by default to the service. Configure a transparent monitor to monitor hosts on the trusted side through individual firewalls. 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 firewall is UP but one of the next hop devices from that firewall is down, the appliance includes the firewall while performing load balancing and forwards the packet to the firewall. 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 firewall) are down, the service is marked as DOWN and the firewall is not included when the appliance performs firewall load balancing.
Binding a transparent monitor overrides the PING monitor. To configure a PING monitor in addition to a transparent monitor, after you create and bind a transparent monitor, you need to bind a PING monitor to the service.
To configure a transparent monitor by using the command line interface
At the command prompt, type the following commands to configure a transparent monitor and verify the configuration:
add lb monitor <monitorName> <type> [-destIP <ip_addr|ipv6_addr|*>] [-transparent (YES | NO )]
bind lb monitor <monitorName> <serviceName>
<!--NeedCopy-->
Example:
add monitor monitor-HTTP-1 HTTP -destip 10.10.10.11 -transparent YES
bind monitor monitor-HTTP-1 fw-svc1
<!--NeedCopy-->
To create and bind a transparent monitor by using the configuration utility
-
Navigate to Traffic Management > Load Balancing > Monitors.
-
In the details pane, click Add.
-
In the Create Monitor dialog box, specify the values as shown:
- Name*
- Type*—type
- Destination IP
- Transparent
-* A required parameter
-
Click Create, and then click Close. In the Monitors pane, select the monitor that you configured and verify that the settings displayed at the bottom of the screen are correct.
Configure a wildcard virtual server to load balance the traffic sent to the firewalls
To configure a wildcard virtual server to load balance the traffic sent to the firewalls by using the command line interface
At the command prompt, type:
add lb vserver <name> ANY * *
<!--NeedCopy-->
Example:
add lb vserver Vserver-LB-1 ANY * *
<!--NeedCopy-->
To configure a wildcard virtual server to load balance the traffic sent to the firewalls by using the configuration utility
- Navigate to Traffic Management > Load Balancing > Virtual Servers.
- In the details pane, click Add.
- In the Create Virtual Server (Load Balancing) dialog box, specify values for the following parameters as shown:
- Name—name
- In Protocol, select ANY, and in IP Address and Port, select *.
- Click Create, and then click Close. The virtual server you created appears in the Load Balancing Virtual Servers pane.
Configure the virtual server in MAC rewrite mode
To configure the virtual server in MAC rewrite mode by using the command line interface
At the command prompt, type:
set lb vserver <name>@ -m <RedirectionMode>
<!--NeedCopy-->
Example:
set lb vserver Vserver-LB-1 -m MAC
<!--NeedCopy-->
To configure the virtual server in MAC rewrite mode by using the configuration utility
- Navigate to Traffic Management > Load Balancing > Virtual Servers.
- In the details pane, select the virtual server for which you want to configure the redirection mode (for example, Vserver-LB-1), and then click Open.
- On the Advanced tab, under Redirection Mode, click MAC-Based.
- Click OK.
Bind firewall services to the wildcard virtual server
To bind firewall services to the wildcard virtual server by using the command line interface
At the command prompt, type:
bind lb vserver <name> <serviceName>
<!--NeedCopy-->
Example:
bind lb vserver Vserver-LB-1 Service-HTTP-1
<!--NeedCopy-->
To bind firewall services to the wildcard virtual server by using the configuration utility
- Navigate to Traffic Management > Load Balancing > Virtual Servers, and select a virtual server.
- Click in the Service section, and select a service to bind.
Note: You can bind a service to multiple virtual servers.
Configure a service for each virtual server
To configure a service for each virtual server by using the command line interface
At the command prompt, type:
add service <name> <serverName> HTTP <port>
<!--NeedCopy-->
Example:
add service Service-HTTP-1 10.102.29.5 HTTP 80
<!--NeedCopy-->
To configure a service for each virtual server 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 as shown:
- Service Name—name
- Server—serverName
- Port—port
- In Protocol, specify HTTP. Under Available Monitors, select HTTP.
- Click Create, and then click Close. The service you created appears in the Services pane.
Configure a monitor for each service
To bind a monitor to a service by using the command line interface
At the command prompt, type:
bind lb monitor <monitorName> <ServiceName>
<!--NeedCopy-->
Example:
bind mon monitor-HTTP-1 Service-HTTP-1
<!--NeedCopy-->
To bind a monitor to a service by using the configuration utility
- Navigate to Traffic Management > Load Balancing > Services.
- Open the service, and add a monitor.
Configure an HTTP virtual server to balance traffic sent to the servers
To configure an HTTP virtual server to balance traffic sent to the servers by using the command line interface
At the command prompt, type:
add lb vserver <name> HTTP <ip> <port>
<!--NeedCopy-->
Example:
add lb vserver Vserver-LB-1 HTTP 10.102.29.60 80
<!--NeedCopy-->
To configure an HTTP virtual server to balance traffic sent to the servers by using the configuration utility
- Navigate to Traffic Management > Load Balancing > Virtual Servers.
- In the details pane, click Add.
- In the Create Virtual Server (Load Balancing) dialog box, specify values for the following parameters as shown:
- Name—name
- IP Address—IP address Note: If the virtual server uses IPv6, select the IPv6 check box and enter the address in IPv6 format (for example, 1000:0000:0000:0000:0005:0600:700a:888b).
- Port—port
- Under Protocol, select HTTP.
- Click Create, and then click Close. The virtual server you created appears in the Load Balancing Virtual Servers pane.
Bind HTTP services to the HTTP virtual server
To bind HTTP services to the wildcard virtual server by using the command line interface
At the command prompt, type:
bind lb vserver <name> <serviceName>
<!--NeedCopy-->
Example:
bind lb vserver Vserver-LB-1 Service-HTTP-1
<!--NeedCopy-->
To bind HTTP services to the wildcard virtual server by using the configuration utility
- Navigate to Traffic Management > Load Balancing > Virtual Servers, and select a virtual server.
- Click in the Service section, and select a service to bind.
Note: You can bind a service to multiple virtual servers.
Save and Verify the Configuration
When you’ve finished the configuration tasks, be sure to save the configuration. You can also check to make sure that the settings are correct.
To save and verify the configuration by using the command line interface
At the command prompt, type the following commands to configure a transparent monitor and verify the configuration:
- save ns config
- show vserver
<!--NeedCopy-->
Example:
save config
show lb vserver FWLBVIP2
FWLBVIP2 (*:*) - ANY Type: ADDRESS
State: UP
Last state change was at Mon Jun 14 07:22:54 2010
Time since last state change: 0 days, 00:00:32.760
Effective State: UP
Client Idle Timeout: 120 sec
Down state flush: ENABLED
Disable Primary Vserver On Down : DISABLED
No. of Bound Services : 2 (Total) 2 (Active)
Configured Method: LEASTCONNECTION
Current Method: Round Robin, Reason: A new service is bound
Mode: MAC
Persistence: NONE
Connection Failover: DISABLED
1) fw-int-svc1 (10.102.29.5: *) - ANY State: UP Weight: 1
2) fw-int-svc2 (10.102.29.9: *) - ANY State: UP Weight: 1
Done
show service fw-int-svc1
fw-int-svc1 (10.102.29.5:*) - ANY
State: DOWN
Last state change was at Thu Jul 8 14:44:51 2010
Time since last state change: 0 days, 00:01:50.240
Server Name: 10.102.29.5
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): NO
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: DOWN Weight: 1
Probes: 9 Failed [Total: 9 Current: 9]
Last response: Failure - Time out during TCP connection establishment stage
Response Time: 2000.0 millisec
2) Monitor Name: ping
State: UP Weight: 1
Probes: 3 Failed [Total: 0 Current: 0]
Last response: Success - ICMP echo reply received.
Response Time: 1.275 millisec
Done
<!--NeedCopy-->
To save and verify the configuration by using the configuration utility
- In the details pane, click Save.
- In the Save Config dialog box, click Yes.
- Navigate to Traffic Management > Load Balancing > Virtual Servers.
- In the details pane, select the virtual server that you created in step 5, verify that the settings displayed in the Details pane are correct.
- Navigate to Traffic Management > Load Balancing > Services.
- In the details pane, select the service that you created in step 5, verify that the settings displayed in the Details pane are correct.
Monitoring a Firewall Load Balancing Setup in an Enterprise Environment
After the configuration is up and running, you can view the statistics for each service and virtual server to check for possible problems.
Viewing the Statistics of a Virtual Server
To evaluate the performance of virtual servers or to troubleshoot problems, you can display details of the virtual servers configured on the Citrix ADC appliance. You can display a summary of statistics for all the virtual servers, or you can specify the name of a virtual server to display the statistics only for that virtual server. You can display the following details:
- Name
- IP address
- Port
- Protocol
- State of the virtual server
- Rate of requests received
- Rate of requests to the virtual server
To display virtual server statistics by using the command line interface
To display a summary of the statistics for all the virtual servers currently configured on the Citrix ADC appliance, or for a single virtual server, at the command prompt, type:
stat lb vserver [-detail] [<name>]
<!--NeedCopy-->
Example:
>stat lb vserver -detail
Virtual Server(s) Summary
vsvrIP port Protocol State Req/s Hits/s
One * 80 HTTP UP 5/s 0/s
Two * 0 TCP DOWN 0/s 0/s
Three * 2598 TCP DOWN 0/s 0/s
dnsVirtualNS 10.102.29.90 53 DNS DOWN 0/s 0/s
BRVSERV 10.10.1.1 80 HTTP DOWN 0/s 0/s
LBVIP 10.102.29.66 80 HTTP UP 0/s 0/s
Done
<!--NeedCopy-->
To display virtual server statistics by using the configuration utility
- Navigate to Traffic Management > Load Balancing > Virtual Servers > Statistics.
- If you want to display the statistics for only one virtual server, in the details pane, select the virtual server, and click Statistics.
Viewing the Statistics of a Service
Updated: 2013-08-28
You can view the rate of requests, responses, request bytes, response bytes, current client connections, requests in the surge queue, current server connections, and so forth using the service statistics.
To view the statistics of a service by using the command line interface
At the command prompt, type:
stat service <name>
<!--NeedCopy-->
Example:
stat service Service-HTTP-1
<!--NeedCopy-->
To view the statistics of a service by using the configuration utility
- Navigate to Traffic Management > Load Balancing > Services > Statistics.
- If you want to display the statistics for only one service, select the service, and click Statistics.
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.