This solution applies to Barracuda Load Balancers in a route-path configuration, all firmware versions.
Route-Path deployment is the most frequently used deployment method, providing the most flexibility by allowing load balancing of any server in a downstream route. It is also desirable because it allows layer 7 (cookie) persistence and SSL offloading.
To set up Route-Path, the following conditions must be met:
- Each real server must be logically isolated. This means all traffic going to each real server must go through the load balancer; each real server must have only 1 IP address, which is their private, isolated IP address. It is possible to have multiple IP addresses, but no network path may exist from the real servers to the client machines (this means if the real servers are also members of another network, this network must too be isolated and not connected in any way or through any other networks to the WAN network, including through the internet).
- The VIPs must be on the same subnet as the rest of the network; only the real servers are on the private, separate network.
- The servers need not be physically isolated and can share a switch with the rest of the network so long as the isolation condition is met.
- Each real server must be "one hop" away from the LAN port on the Barracuda Load Balancer. This means any relevant switches must be directly connected into the LAN port of the Load Balancer, or connected to a series of switches that eventually reach the LAN port of the Load Balancer without going through any other machines.
- Each real server must list the Barracuda's LAN IP address as its gateway.
- Each real server must use only one nic, if there is multiple nics the other nics must have no gateway or be disabled.
- Lastly, the box must be in Route Path mode on the IP configuration page (2.0 and above only).
Link to This Page: