Overview
A user has asymmetric traffic in their network, meaning that Inbound traffic comes in one bridge of the Exinda and outbound comes out of another bridge (or through different Exindas in a cluster). This article describes several considerations and recommends some configurations for this scenario.
Information
When the same flow travels through two bridges or two Exindas in a cluster, Exinda double counts the packets providing wrong monitoring. Also, if that traffic is being accelerated, the TCP (Transport Control Protocol) acceleration process fails to terminate the flows correctly, leading to broken traffic. In order to avoid these issues, Exinda came up with a feature called Dual Bridge Bypass, which ignores one of the two passes so the monitoring is correct and acceleration is terminated properly.
However, when traffic is asymmetric, Exinda needs to process both bridges and cannot ignore any of them, because one involves the inbound of the conversation while the other one involves the outbound direction. In this case, Dual Bridge Bypass option must be disabled.
- For proper acceleration of asymmetric traffic (making sure that both inbound and outbound flows are being seen by the same Exinda or by the two Exindas in a cluster):
- Navigate to Configuration > System >Optimization >TCP and disable the Dual Bridge Bypass option.
- Navigate to Configuration > System >Optimization >TCP and disable the Dual Bridge Bypass option.
- For proper monitoring of asymmetric traffic:
- Navigate to Configuration > System > Setup > Monitoring and disable the Dual Bridge Bypass option.