-
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
反对figuring Citrix ADC Virtual Appliances to Use SR-IOV Network Interface
反对figuring 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
反对figuring 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
反对figure a Citrix ADC VPX instance to use SR-IOV network interface
反对figure 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
反对figure multiple IP addresses for a Citrix ADC VPX standalone instance
反对figure a high-availability setup with multiple IP addresses and NICs
反对figure a high-availability setup with multiple IP addresses and NICs by using PowerShell commands
反对figure a Citrix ADC VPX instance to use Azure accelerated networking
反对figure HA-INC nodes by using the Citrix high availability template with Azure ILB
反对figure a high-availability setup with Azure external and internal load balancers simultaneously
Upgrade and downgrade a Citrix ADC appliance
-
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
-
-
-
-
-
-
Monitor GSLB services
Use case: Deployment of domain name based autoscale service group
Use case: Deployment of IP address based autoscale service group
-
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
反对figure 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 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
-
反对figuring a CloudBridge Connector Tunnel between two Datacenters
反对figuring a CloudBridge Connector Tunnel Between a Datacenter and Azure Cloud
反对figuring CloudBridge Connector Tunnel between Datacenter and SoftLayer Enterprise Cloud
反对figuring 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!
Monitor GSLB services
When you bind a remote service to a GSLB virtual server, the GSLB sites exchange metric information, including network metric Information, which is the round-trip-time and persistence Information.
If a metric exchange connection is momentarily lost between any of the participating sites, the remote site is marked as DOWN and load balancing is performed on the remaining sites that are UP. When metric exchange for a site is DOWN, the remote services belonging to the site are marked DOWN as well.
The Citrix ADC appliance periodically evaluates the state of the remote GSLB services by using either MEP or monitors that are explicitly bound to the remote services. Binding explicit monitors to local services is not required, because the state of the local GSLB service is updated by default using the MEP. However, you can bind explicit monitors to a remote service. When monitors are explicitly bound, the state of the remote service is not controlled by the metric exchange.
By default, when you bind a monitor to a remote GSLB service, the Citrix ADC appliance uses the state of the service reported by the monitor. However, you can configure the Citrix ADC appliance to use monitors to evaluate services in the following situations:
- Always use monitors (default setting).
- Use monitors when MEP is DOWN.
- Use monitors when remote services and MEP are DOWN.
The second and third of the above settings enable the appliance to stop monitoring when MEP is UP. For example, in a hierarchical GSLB setup, a GSLB site provides the MEP information about its child sites to its parent site. Such an intermediate site may evaluate the state of the child site as DOWN because of network issues, though the actual state of the site is UP. In this case, you can bind monitors to the services of the parent site and disable MEP to determine the actual state of the remote service. This option enables you to control the manner in which the states of the remote services are determined.
To use monitors, first create them, and then bind them to GSLB services.
反对figure monitor trigger
You can configure a GSLB site to always use monitors (the default), use monitors when MEP is down, or use monitors when both the remote service and MEP are down. In the latter two cases, the Citrix ADC appliance stops monitoring when MEP returns to the UP state.
To configure monitor triggering by using the command line interface
At the command prompt, type:
set gslb site –triggerMonitor (ALWAYS | MEPDOWN | MEPDOWN_SVCDOWN)
Example:
set gslb site Site-GSLB-North-America –triggerMonitor Always
To configure monitor triggering by using the configuration utility
- Navigate toTraffic Management>GSLB>Sites, and double-click the site.
- In theTrigger Monitorsdrop-down list, select an option for when to trigger monitoring.
Add or remove monitors
To add a monitor, you specify the type and the port. You cannot remove a monitor that is bound to a service. You must first unbind the monitor from the service.
To add a monitor by using the command line interface
At the command prompt, type the following commands to create a monitor and verify the configuration:
add lb monitor -type -destPort show lb monitor
Example:
add lb monitor monitor-HTTP-1 -type HTTP -destPort 80 show lb monitor monitor-HTTP-1
To remove a monitor by using the command line interface
At the command prompt, type:
rm lb monitor
To add a monitor by using the configuration utility
Navigate to Traffic Management > Load Balancing > Monitors, and add or delete a monitor.
Bind monitors to a GSLB service
Once you create monitors, you must bind them to GSLB services. When binding monitors to the services, you can specify a weight for the monitor. After binding one or more weighted monitors, you can configure a monitor threshold for the service. This threshold takes the service down if the sum of the bound monitor weights falls below the threshold value.
Note: In the configuration utility, you can set both the weight and the monitoring threshold at the same time that you bind the monitor. When using the command line, you must issue a separate command to set the service’s monitoring threshold.
To bind the monitor to the GSLB service by using the command line interface
At the command prompt, type:
bind monitor [ -state (Enabled | Disabled) ] -weight
Example:
bind monitor monitor-HTTP-1 service-GSLB-1 -state enabled -weight 2
To set the monitoring threshold for a GSLB service by using the command line interface
At the command prompt, type:
set gslb service -monThreshold
Example:
set gslb service service-GSLB-1 -monThreshold 9
To bind the monitor to the GSLB service by using the configuration utility
- Navigate to Traffic Management > GSLB > Services.
- Click theMonitorsection and bind the monitor to the GSLB service.
To set the monitoring threshold for a GSLB service by using the configuration utility
- Navigate to Traffic Management > GSLB > Services.
- Click theMonitor Thresholdsection and enter a threshold value.
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.