-
-
-
Manage link definitions in traffic shaping
-
-
Manage and monitor using Citrix Application Delivery Management
-
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!
Manage link definitions in traffic shaping
To manage a link, the traffic shaper needs the following information:
-
The speed of the link in both the send and receive directions.
-
Whether the link is a WAN link or a LAN network.
-
A way of distinguishing link traffic from other traffic.
-
The direction in which traffic is flowing over the link.
Link Speed— Link speed always refers to the speed of the physical link. In the case of a WAN link, it is the speed of the WAN segment that terminates in the building with the Citrix SD-WAN WANOP appliance. The speed of the other end of the link is not considered. For example, the following figure shows a network of four appliances. Each appliance has its incoming and outgoing bandwidths set to 95% of the speed of its own, local WAN segment, without regard to the speed of the remote endpoints.
Figure 1. Local bandwidth limits track local link speeds
The reason for setting the bandwidth limits to 95% of the link speed instead of 100% is to allow for link overhead (few links can carry data at 100% of their published speeds) and to ensure that the appliance is slightly slower than the link, so that it becomes a slight bottleneck. Traffic shaping is not effective unless the traffic shaper is the bottleneck in the connection.
Distinguishing different types of traffic—In each link definition, you must declare whether the definition applies to a WAN link or a LAN network.
The traffic shaper needs to know whether a packet is traveling on the WAN, and, if so, in which direction. To provide this information:
-
For simple inline deployments, you declare that one port of the accelerated bridge belongs to the WAN link and that the other port belongs to the LAN.
-
In other deployment modes, the appliance examines IP addresses, MAC addresses, VLANs, or WCCP service groups. (Note that testing for WCCP service groups is not yet supported.)
-
If a site has multiple WANs, the local link definitions must include rules that enable the appliance to distinguish traffic from different WANs.
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.