-
-
-
-
-
XenServer 6.5 Upgrade for SD-WAN Standard Edition Appliances
-
SD-WAN Standard Edition Virtual Appliance (VPX) in Hypervisor on HyperV 2012 R2 and 2016
-
Install SD-WAN SE Virtual Appliances (VPX) in Linux-KVM Platform
-
Deploy Citrix SD-WAN Standard Edition Instance on Azure - Release Version 10.2 and above
-
SD-WAN Standard Edition Virtual Appliance (VPX) High Availability support for AWS
-
Deploy a Citrix SD-WAN VPX instance on a Citrix ADC SDX appliance
-
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!
Selecting a Load Balancing Method
By default, the SD-WAN 4100/5100 Provisioning Wizard sets up load balancing to handle different kinds of connections appropriately. This default behavior is adequate for most installations.
Sending all the connections from the same remote accelerator to the same local accelerator maximizes the benefits of SD-WAN compression, and the default load balancing method accomplishes this. If an instance becomes overloaded or unavailable, new connections are reallocated.
Default Load Balancing Behavior
By default, the NetScaler instance uses the least-connection method to balance the load across the accelerators. This method applies whether the connections are accelerated. Connections are persistent, but persistency is discontinued for an instance that becomes overloaded, and is lost if the local appliance is restarted or when no traffic from a remote appliance is seen for more than 24 hours.
Accelerated connections
For incoming accelerated connections (that is, connections with SD-WAN options in the header of the SYN packet), all connections from a given remote SD-WAN are sent to the same local accelerator.
The identity of the remote SD-WAN is determined by one of the SD-WAN SYN options: the “Agent ID” field, which contains the management IP address of the remote SD-WAN.
This method is used for connections from remote SD-WAN appliances and remote SD-WAN Plug-ins.
Other connections
Incoming non-accelerated connections and all outgoing connections are also distributed among the accelerators according to the least-connection method, but since they do not contain an Agent ID field, they cannot use Agent ID persistence. Instead, they use SRCIPDESTIP persistence, meaning that connections with the same IP addresses use the same accelerator.
Bypassing overloaded Instances
If an instance is overloaded, the NetScaler instance bypasses it for new connections, sending them through without acceleration. Existing connections continue to be sent to the instance.
This behavior is controlled by the skip Persistency parameter. The default behavior is -skip persistency ReLB. The alternative behavior, -skip persistency bypass, instructs the NetScaler instance to pass the connection through without sending it to an accelerator.
Optional Load Balancing Behavior
The default load balancing behavior is adequate for most installations, but sometimes customization is needed. This is most commonly true when a few remote sites have much more traffic than the rest. In that case, it can be worthwhile to assign these large sites to accelerators explicitly.
Optional load balancing behavior includes the use of static routing (for hand-crafted load balancing) and variations on the least-connection with Agent ID and SRCIPDESTIP persistence methods used in the default configuration. The behavior for dealing with overloaded instances can be changed from assigning connections to a difference instance to passing them through as unaccelerated.
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.