-
-
-
Traffic distribution in multiple routes based on five tuples information
-
Configure to source Citrix ADC FreeBSD data traffic from a SNIP address
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!
Traffic distribution in multiple routes based on five tuples information
In a load balancing setup, a Citrix ADC appliance can have multiple routes to send a packet to its destination. For example: to a server, and to a client.
A Citrix ADC appliance uses a hashing algorithm to select a route for sending the packet to its destination.
The hashing algorithm uses the following two tuples of a packet to calculate a hash, based on which the Citrix ADC appliance selects a route for the packet.
- Source IP address
- Destination IP address
The selection of routes based on two tuples information can cause an uneven distribution of traffic on the available routes. This uneven distribution of traffic leads to overloading of traffic in some routes.
To resolve this issue, from build 13.0 71.x, the Citrix ADC appliance uses the following five tuples information of a packet in the hashing algorithm to select a route for the packet:
- Source IP address (Client IP)
- Source Port (Client Port)
- Destination IP address(Service IP)
- Destination Port (Service Port)
- Protocol number
The selection of routes based on five tuples information ensures even distribution of traffic on the available routes. This even distribution of traffic prevents overloading of traffic in a route.
Consider an example of a load balancing setup where a client sends a request to the VIP address. The Citrix ADC appliance uses the following five tuples information to select a route to send the request packet to the load balanced server:
- Source IP address (Client IP address)
- Source Port (Client port)
- Destination IP address (Service IP address)
- Destination Port (Service port number)
- Protocol Number
Precedence regarding other route selection based Citrix ADC features
This section talks about the precedence of the route selection based on five tuples feature and other route selection related features in a Citrix ADC appliance.
-
Policy Based Routes (PBR). PBR rules always take precedence over route selection based on five tuples.
-
Mac Based Forwarding (MBF). In a load balancing configuration, MBF or route selection based on five tuples takes precedence in the following cases:
- For a client initiated traffic to the VIP address of the load balancing configuration in the Citrix ADC appliance:
- Request traffic destined to a load balanced server. Route selection based on five tuples takes preference over MBF.
- Response Traffic destined to the client. MBF takes preference over route selection based on five tuples.
- For a server initiated traffic to the SNIP address in the Citrix ADC appliance:
- Response Traffic destined to the client. Route selection based on five tuples takes preference over MBF.
- Request traffic destined to a load balanced server. MBF takes preference over route selection based on five tuples.
- For a client initiated traffic to the VIP address of the load balancing configuration in the Citrix ADC appliance:
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.