Route-Path Deployment Options

Last updated on 2013-04-16 15:06:36

Route-Path is the most commonly used deployment method. If a Service type of Layer 4 - UDP or Layer 4 - TCP is used in a two-armed deployment, the Barracuda Load Balancer has to be the default gateway for all downstream Real Servers. For all other cases, the Real Servers and VIP addresses can be positioned in a variety of ways. Table 1 provides an overview of the Route-Path deployment options.

Table 1. Route-Path Deployment Options.

Traffic Type	Topology Options (Route-Path)	Service Type	Notes
TCP or UDP	Two-armed. Usually the recommended deployment for Layer 4 traffic.	Layer 4 - UDP, Layer 4 - TCP	Barracuda Load Balancer has to be the default gateway for all downstream Real Servers
UDP	One- or two-armed.	UDP Proxy	UDP Proxy supports persistence using both client IP address and port. Many UDP applications involve all client requests coming from one client IP address. A Service with type UDP Proxy and configured with persistence of client IP port number distributes traffic across all of the Real Servers. Layer 4 - UDP Services only consider client IP address.
TCP	One- or two-armed. Two-armed is recommended for best performance.	TCP Proxy	Can keep IP addresses of the Real Servers. There is a TCP Connection between the Barracuda Load Balancer and the Real Server. Any response goes back to the Barracuda Load Balancer.
TCP or UDP	One-armed. Best performance if almost all traffic is outgoing.	Layer 4 - TCP or Layer 4 - UDP with Real Servers in Direct Server Return mode	Requires loopback adapter on each Real Server. Can keep IP addresses of the Real Servers. SSL offloading and other Layer 7 capabilities are not supported.
TCP with SSL processing offloaded to the Barracuda Load Balancer	One- or two-armed. Two-armed is recommended for best performance.	Secure TCP Proxy	Can keep IP addresses of Real Servers. There is a TCP connection between Barracuda Load Balancer and Real Server. Any response goes back to Barracuda Load Balancer.
HTTP (web servers)	One- or two-armed.	Layer 7 - HTTP or Layer 7 - HTTPS	Can keep IP addresses of the Real Servers. There is a TCP connection between the Barracuda Load Balancer and the Real Server. Any response goes back to the Barracuda Load Balancer.
FTP (FTP servers)	One- or two-armed.	Layer 7 - FTP or Layer 7 - FTPS	Can keep IP addresses of the Real Servers. There is a TCP connection between the Barracuda Load Balancer and the Real Server. Any response goes back to the Barracuda Load Balancer.
Remote Desktop Services	One- or two-armed. Two-armed is recommended for best performance.	Layer 7 - RDP	Can keep IP addresses of the Real Servers. There is a TCP connection between the Barracuda Load Balancer and the Real Server. Any response goes back to the Barracuda Load Balancer.

Related Articles