Route-Path Configured with TCP Proxy, UDP Proxy, or a Layer 7 Service Type

Last updated on 2013-04-10 15:30:04

Choosing a Service type of TCP Proxy, UDP Proxy or one of the Layer 7 Service types makes the Barracuda Load Balancer act as a full proxy. Connections from the client are terminated at the Barracuda Load Balancer and new ones are established between the Barracuda Load Balancer and the Real Servers.

Using one of these Service types allows the Real Servers to be located anywhere, as long as they can be routed to by the Barracuda Load Balancer (e.g., on the same subnet or VLAN or pre-configured static routes). This can be used in one-armed configurations for applications like Microsoft Exchange Server or Microsoft Office Communications Server as well as for custom applications. In two-armed configurations, Real Servers can access the Virtual IP (VIP) addresses of any TCP Proxy, UDP Proxy, or Layer 7 Services that are on the same side of the Barracuda Load Balancer.

There are multiple alternatives for configuration when using the Barracuda Load Balancer in the Route-Path mode with one or more TCP Proxy, UDP Proxy, or Layer 7 Services:

Some or all of the Real Servers are on the same subnet as the LAN IP address.
Some or all of the Real Servers are on the same subnet as the WAN IP address.
Some or all of the Real Servers are on the same VLAN as the Barracuda Load Balancer.
Some or all of the Real Servers are on a different subnet than either the WAN or LAN IP address but accessible through static routes.
Some or all of the Real Servers are on a different subnet and responding to a TCP Proxy, UDP Proxy, or Layer 7 Service.
VIP addresses are on the same subnet as the WAN interface of the Barracuda Load Balancer, and Real Servers on a subnet separate from the VIPs.
VIP addresses are on the same subnet as the LAN interface of the Barracuda Load Balancer and Real Servers on a subnet separate from the VIPs.

Related Articles