Asymmetric Routing
You enable asymmetric route detection for the selected optimization policy in the Asymmetric Routing page.
Asymmetric route detection automatically detects and reports asymmetric routing conditions and caches this information to avoid losing connectivity between a client and a server.
Asymmetric routing is when a packet traverses from a source to a destination in one path and takes a different path when it returns to the source. This is commonly seen in Layer-3 routed networks. Asymmetric routing is common within most networks; the larger the network, the more likely there is asymmetric routing in the network.
For details about asymmetric routing types, see the SteelHead Management Console User’s Guide for SteelHead CX.
You can also use the SteelHead CLI to detect and analyze asymmetric routes. For details, see the Riverbed Command-Line Interface Reference Manual or the SteelHead Deployment Guide.
Asymmetric Routing Settings
Complete the configuration as described in this table.
Control | Description |
Enable Asymmetric Routing Detection | Detects asymmetric routes in your network. |
Enable Asymmetric Routing Pass-Through | Enables pass-through traffic if asymmetric routing is detected. If asymmetric routing is detected, the pair of IP addresses, defined by the client and server addresses of this connection, is cached on the appliance. Further connections between these hosts are passed through unoptimized until that particular asymmetric routing cache entry times out. Detecting and caching asymmetric routes does not optimize these packets. If you want to optimize asymmetric routed packets you must make sure that the packets going to the WAN always go through an appliance either by using a multiport appliance, connection forwarding, or using external ways to redirect packets, such as WCCP or PBR. For detailed information, see the SteelHead Deployment Guide. |
Apply | Applies your settings. |