Specifications

20 Barracuda Load Balancer Administrator’s Guide
Figure 2.3: Sample Route-Path network layout
Deploying Route-Path
In the Route-Path method of deployment, the Virtual IP addresses must be on the same subnet as the
Barracuda Load Balancer. The Real Servers must be on a subnet separate from the VIPs and the
Barracuda Load Balancer. This may require changing the IP addresses of your Real Servers.
Normally the Real Servers are on an isolated IP network behind the Barracuda Load Balancer. If IP
address changes are not possible, or if there is no way to make Route-Path deployment work, the next
choice for deployment method is Direct Server Return. See Direct Server Return on page 22 for
details.
Real Servers that are on multiple networks simultaneously may break the route path. If Real Servers
have more than one network adapter enabled, and traffic has a route around the Barracuda Load
Balancer, the deployment will not work properly even though it may appear to work initially. There
are two exceptions where Real Servers may have multiple network adapters:
• The other networks that the Real Servers are on are also isolated and cannot access the WAN
network without going through the Barracuda Load Balancer
• Static routes for incoming and outgoing traffic for each IP address of each Real Server have
been defined.
Each Real Server must be one hop away from the LAN port on the Barracuda Load Balancer. This
means their switch must be directly connected into the LAN port of the Barracuda Load Balancer, or
connected to a series of switches that eventually reach the LAN port of the Barracuda Load Balancer
without going through any other machines.