-
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
-
-
-
-
-
-
-
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
-
-
QUIC bridge configuration
-
-
-
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!
QUIC bridge configuration
To configure QUIC bridge, you must complete the following:
- Add QUIC bridge profile
- Add QUIC back-end servers
- Add QUIC service on the appliance
- Add load balancing virtual server of type QUIC bridge
- Bind QUIC bridge to load balancing virtual server of type QUIC bridge
Important
Before you configure the QUIC bridge, ensure you first enable the load balancing feature on the appliance. For more information, see Set up basic load balancing.
Configure QUIC bridge by using the CLI
The following sections must be configured by using the CLI.
Add a QUIC bridge profile
You must add a QUIC bridge profile.
At the command prompt, type:
add quicBridge profile <name> -routingAlgorithm <PLAINTEXT> -serveridlen <value>
Example:
add quicBridge profile q1 -routingAlgorithm PLAINTEXT -serveridlen 6
Note
The
serveridlen
parameter configured in the example is the length of a custom server ID, which is the hex string of IP and PORT.
Add QUIC back-end application server
You must add QUIC back-end application servers.
At the command prompt, type:
- add server <name> (<IPAddress>)
- add server <name> (<IPAddress>)
Example:
- add server s1 192.0.2.20
- add server s2 192.0.2.30
Add QUIC bridge service
You must add QUIC bridge service to the application servers.
At the command prompt, type:
- add service <name> \(<IP> | <serverName>) <serviceType> <port> \[-CustomServerID <string>]
- add service <name> \(<IP> | <serverName>) <serviceType> <port> \[-CustomServerID <string>]
Example:
- add service src1 s1 QUIC_BRIDGE 443 -CUSTOMSERVERID C0A8026401BB
- add service src2 s2 QUIC_BRIDGE 443 -CUSTOMSERVERID C0A802C801BB
Note
The
CustomServerID
parameters configured in the preceding example are the hex string of a corresponding IP and the PORT of the server (s1 and s2). For the QUIC bridge feature, Citrix recommends you to configure theCustomServerID
parameter in the hex string format only.
Add a load balancing virtual server of type QUIC bridge
You must add a load balancing virtual server of type QUIC bridge.
At the command prompt, type:
add lb vserver <name> [<IPAddress>@ <port>] [-persistenceType < persistenceType >] [-lbMethod < lbMethod >] [-rule <rule>] [-cltTimeout <secs>] [-quickBridgeProfilename <name>]
Example:
add lb vserver quic_bridge_vip QUIC_BRIDGE 192.0.2.10 443 -persistenceType CUSTOMSERVERID -lbMethod TOKEN -rule QUIC.CONNECTIONID -cltTimeout 120 -quicBridgeProfilename q1
Note
While configuring the QUIC bridge virtual server, you must configure
persistenceType
parameter asCUSTOMSERVERID
,rule
parameter asQUIC.CONNECTIONID
andLbMethod
parameter asTOKEN
.
Bind QUIC bridge service to the load balancing virtual server of type QUIC bridge
You must bind the QUIC bridge service to the load balancing virtual server of type QUIC bridge.
At the command prompt, type:
- bind lb vserver <name> (<serviceName>)
- bind lb vserver <name> (<serviceName>)
Example:
- bind lb vserver quic_bridge_vip src1
- bind lb vserver quic_bridge_vip src2
Configure QUIC bridge for service groups
You can also configure QUIC bridge capabilities to service groups. The following steps guide you to configure QUIC bridge for service groups.
To configure QUIC bridge for service groups, you must complete the following:
Add QUIC bridge profile
At the command prompt, type:
add quicBridge profile <name> -routingAlgorithm <PLAINTEXT> -serveridlen <value>
Example:
add quicBridge profile q1 -routingAlgorithm PLAINTEXT -serveridlen 6
Add server of type QUIC
At the command prompt, type:
- add server <name> (<IPAddress>)
- add server <name> (<IPAddress>)
Example:
- add server s1 192.0.2.20
- add server s2 192.0.2.30
Add QUIC bridge service group
At the command prompt, type:
add serviceGroup <serviceGroupName> \(<IP> | <serverName>) <serviceType>
Example:
add serviceGroup svg1 QUIC_BRIDGE
Bind the QUIC servers to the service group
At the command prompt, type:
- bind serviceGroup <serviceGroupName> \(<IP>@ | \(<serverName>) \[-CustomServerID <string>]
- bind serviceGroup <serviceGroupName> \(<IP>@ | \(<serverName>) \[-CustomServerID <string>]
Example:
- bind serviceGroup svg1 s1 443 -customServerID C0A8026401BB
- bind serviceGroup svg1 s2 443 -customServerID C0A802C801BB
Add load balancing virtual server of type QUIC bridge
At the command prompt, type:
add lb vserver <name> [<IPAddress>@ <port> [-persistenceType < persistenceType >] [-lbMethod < lbMethod > [-cltTimeout <secs>] [-quickBridgeProfilename <name>]
Example:
add lb vserver quic_bridge_vip QUIC_BRIDGE 192.0.2.10 443 -persistenceType CUSTOMSERVERID -lbMethod TOKEN -cltTimeout 120 -quicBridgeProfilename q1
Bind the load balancing virtual server of type QUIC bridge to the service group
At the command prompt, type:
bind lb vserver <name>@ (<serviceName>@ <serviceGroupName>
Example:
bind lb vserver quic_bridge_vip svg1
Configure QUIC bridge using the GUI
Complete the following steps to configure QUIC bridge by using the GUI.
- Navigate to Traffic Management > Load balancing > Virtual Servers.
- On the Virtual Servers page, click Add.
- On the Load Balancing Virtual Server page, select the Protocol as QUIC_BRIDGE and enter the details.
- Click Continue and Done.
Configure load balancing for the services by using the GUI
Complete the following steps to configure load balancing for the services by using the GUI.
- Navigate to Traffic Management > Load Balancing > Services. On the Services page, click Add.
-
On the Load Balancing Service page, enter the details and click OK.
- On the Virtual Servers page, select the created virtual server to bind the service.
- Scroll down on the Load Balancing Virtual Server page and select the Services and Service Groups.
- On the Service Binding screen, click Select Service field.
- On the Service screen, select the service to bind to the load balancing virtual server, and click Select.
- On the Service Binding screen, select the service that you created and click Bind.
- On the Load Balancing Virtual Server page, click Done.
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.