
Note - In both configurations that the incoming client traffic is assumed to originate on the other side of the gateway
device for the subnets on which Equalizer and the servers reside. The servers will usually have their default gateway
set to something other than Equalizer so that they can respond directly to client requests.
Configuring Direct Server Return
In a typical load balancing scenario, server responses to client requests are routed through Equalizer on their way
back to the client. Equalizer examines the headers of each response and may insert a cookie, before sending the
server response on to the client.
In a Direct Server Return (DSR) configuration, the server receiving a client request responds directly to the client
IP, bypassing Equalizer. Because Equalizer only processes incoming requests, cluster performance is
dramatically improved when using DSR in high bandwidth applications, especially those that deliver a significant
amount of streaming content. In such applications, it is not necessary for Equalizer to receive and examine the
server’s responses: the client makes a request and the server simply streams a large amount of data to the client.
DSR is supported on Layer 4 TCP and UDP clusters only, and is not supported for FTP clusters (Layer 4 TCP
clusters with a start port of 21). Port translation or port mapping is not supported in DSR configurations.
DSR configurations are usually configured in single network mode, where the cluster IP and the server IPs are all
on the internal interface. An example single network mode DSR configuration is shown below:
Copyright © 2013 Coyote Point Systems. A subsidiary of Fortinet, Inc.
All Rights Reserved.
313
Equalizer Administration Guide
Kommentare zu diesen Handbüchern