We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda Load Balancer

Route-Path Deployment Options

  • Last updated on

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 TypeTopology Options
(Route-Path)
Service TypeNotes
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
UDPOne- or two-armed.UDP ProxyUDP 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 ProxyCan 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 modeRequires 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 ProxyCan 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 - RDPCan 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

Last updated on