-
-
-
-
-
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!
Gathering Information Needed for Configuration
Accurate information about both the local and the remote sites is essential to troubleshooting. Before installing the SD-WAN 4100/5100 appliance, make sure that you have done the following:
- Obtained or drawn an accurate network diagram of your local site (the one in which you are installing SD-WAN 4100/5100). The local network topology and the capabilities of your WAN routers determine which deployment modes are appropriate for the site.
- Chosen the deployment mode of the local SD-WAN 4100/5100 appliance (for example, WCCP or inline, with or without high availability and cascading).
- Compiled a list of critical applications that must be tested to validate the deployment.
- Obtained or drawn an accurate network diagram of your WAN, including both the local and the remote WAN links, their bandwidths in both directions, their subnets, and whether they are accelerated. In deployments with many remote sites, an aggregate of the different categories (accelerated and non-accelerated) is probably sufficient, and only the largest remote sites need to be considered individually.
- Determined whether there are multiple datacenters with datacenter-to-datacenter traffic, and whether any remote datacenters have an SD-WAN 4100/5100 appliance.
- Decided whether you plan to increase WAN capacity, the number of sites, or the number of users in the next 24 months. If so, the corresponding SD-WAN 4100/5100 capacity should be installed now.
- If possible, formed an idea of the traffic breakdown over the WAN, including TCP traffic to and from SD-WAN-accelerated sites, other TCP traffic, ICA users, HDX sessions, and real-time traffic such as VoIP. SD-WAN 4100/5100 needs to be provisioned for the peak loads in terms of accelerated TCP connections, ICA users, and total WAN link capacity.
- Determined the number of WAN links in the local site. Are they independent, or are they load balanced? If so, are they active-active or active-standby?
- Determined the current, unaccelerated RTT of the remote sites during peak periods.
- Identified any QoS devices or proxies in the path between the local and remote sites. QoS devices should be on the WAN side of SD-WAN 4100/5100. Proxies should be on the LAN side.
Share
Share
In this article
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.